>>52865861 Holy shit you're fucking retarded. First of all it's not physical RAM, it's virtual memory, virtual 0x0 is most likely not mapped to physical 0x0. Secondly, the first 4k block in every process is left unmapped in order to catch common null de reference errors like this.
Go learn how computers work before you blame "meme hardware".
>>52866034 >>52866220 Holy shit I didn't think my fellow Arch users would be THIS retarded. http://wiki.osdev.org/Category:Memory_management http://wiki.osdev.org/Memory_management Go learn a thing or two.
>>52866122 RAM doesn't have to be consistently corrupted for it to be failing.
You've tried how many other distributions and how many of them were successful? If you got other x based distros working and not arch, then you definitely fucked something up. Did you use a torrent to download the ISO? This is highly recommended. Check your md5's and make sure the media isn't corrupted.
>then why is arch throwing an exception when trying to access the start of the memory? BECAUSE IT'S UNMAPPED FUCKFACE. Unmapped memory throws an exception when accessed.
Arch (read: Xorg) was not "using" 0x0, no one should EVER use 0x0 unless you want to crash. There's no user solution to OP's problem, OP is not at fault here, the fault is 100% X's fault, and OP's hardware is perfectly fine.
A null de reference is almost always programmer error.
YOU learn how computers work BEFORE you embarrass yourself.
>>52867496 Programs can crash under different environments, it's not particularly the users fault. The software should be able to handle every type of environment it supports, failure to do so is error of the program.
OP, I suggest firing up a debugger and finding out where this fault occurs, maybe you could get a hint and fix it up.
>>52867470 >not helping with your non-knowledge You mean,.... Ignorance?
Way to be a retard. It's a widely known fact that letting a browser handle an ISO download can lead to broken isos. I just had this issue with 3 separate versions of Ubuntu using Firefox and opera and when I used the torrent to download it, magically, it worked.
>>52867531 I'm not blaming OP but I'm also not going to sit by while people blame Arch. Something is surely amiss with Arch at the moment, but this is not from Arch. Arch comes out of the box with everything arch needs to run arch.
Xorg server, utils and xinit are all extra packages that need to be downloaded and ran by the user. Something went wrong in this stage.
>>52867568 I never claimed that a bad ISO could break RAM. Those are two separate issues. Surely a bad ISO could cause bad read writes which would "simulate" bad RAM. But to actually break your RAM would be a bit far fetched for anybody to claim.
Downloading more RAM however, is something that can only be done on Windows.
>>52867636 >install package that changes config files >install package that rewrites xinit or changes something that deals with DE/WM >Update system >broken >Archs fault
I'm not saying its 100% your fault. But its not archs fault that your shit is gone. It does what you tell it to do. Like I said earlier, you cant blame a mechanically sound car for breaking down when a poor mechanic goes to modify it.
Same here. That's the PC modding world. I know it's a slam to your ego to find out you're not as good as you thought. But car guys don't get defensive when their cars don't work. They just keep diagnosing and fixing the car. You should do the same.
>>52867627 >but I'm also not going to sit by while people blame Arch. You cannot be this stubborn, it is quite obviously Arch's fault, you can't spin it any other way. Or maybe it's not specifically Arch's fault, but it is definitely X's fault entirely, and it's not that surprising anyway, X is a pile os steaming garbage that desperately needs to be replaced by something that doesn't suck truckloads of cock.
>I never claimed that a bad ISO could break RAM. No you never claimed that, but you DID say that OP had bad RAM, you didn't say the bad ISO "simulated" bad RAM (lol), you specifically SAID that op HAS BAD RAM, which is just completely false.
>>52867731 Like I said, X doesn't come with arch. It may be OP's fault or X's fault. But arch does what arch is told to. Including if its told to be unstable.
I didn't say it simulated bad RAM, but if a program has an error trying to read unmapped memory consistently then you could say in layman's that the ISO is simulating bad RAM since its not accessing it the right way. A poor way of putting it but none the less that can happen. So much wild shit can happen with small chunklets of code getting corrupted.
It's objectively very easy to deal with Arch. The meme that Arch requires you to be a Linux expert or PhD CS grad needs to die.
>>52867805 >It may be OP's fault or X's fault. Definitely X's. >But arch does what arch is told to. Agreed. >Including if its told to be unstable. Right, except OP never told it to be unstable, it just told it to start X, which it should've but X fucked up.
>inb4 telling Arch to start X is telling Arch to be unstable. I agree that X is garbage but that's not completely true.
>>52867903 I have to agree. Telling x to start is not directly telling it to become unstable. But at what point did the x installation become unstable and for what reasons? I'm technically a Linux babby and I've had no issues with arch in the ~5 months I've been using it heavily. Did he screw up X or did X break itself on a fresh install?
>>52867973 For the same reason you're on Linux because Mac and Windows do far more than what you tell it to do, Fedora, *buntu, mint and every other distro do far more than what you tell it to do. Arch literally does exactly what you tell it to do. If you don't tell it to do somethings its not going to do it. That's an issue in itself if not managed properly.
>>52867425 I almost spat out the water I was drinking. The last Chevy I owned had major part failures every couple months that would take it out of commission for about a week while I tried to fix it around work.
>>52868434 Yea that's what I usually do. I'm trying to dual boot it with Windows 10 on my dell xps 13 (2015). The hard drives partition table is gpt, and usually using a bios bootloader and legacy boot should normally work but here's the kicker: for some ""security "" reasons the xps 13 won't use legacy boot if its installed on gpt.
>>52868481 I was shit failing like the fuel pump, water, pump, alternator, steering gearbox seals (that one I let sit for a couple months and just went without power steering, and other shit. Surprisingly the transmission didn't have any problems. Replaced it with a superior Japanese car that has yet to have problems.
All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.
This is a 4chan archive - all of the shown content originated from that site. This means that 4Archive shows their content, archived. If you need information for a Poster - contact them.
If a post contains personal/copyrighted/illegal content, then use the post's [Report] link! If a post is not removed within 24h contact me at [email protected] with the post's information.