Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am having difficulty getting any version/distribution of Linux to run on my desktop machine. This has been an ongoing problem now for some time. I am wondering how to determine what is the cause of this instability.
The machine is a 64 bit machine built by myself. I have an AMD 3800 dual core 64 bit processor with an MSI board. I have it dual booting between Linux and Windows XP. XP runs without any problems.
For a while now, I have been running Fedora 13. I had stability problems and kept updating the kernel until I finally found one that was stable on this machine. I stayed with it for some time. I wanted to upgrade my system so I tried Fedora 15. I cannot even get the kernel the installer uses to run. The 64 bit installation crashes every time. I tried installing from the second DVD drive and it still behaves the same. I also tried one of the live CDs and they will crash before totally booting. I then went back to Fedora 14 and was able to install it without issue, but the kernel will crash at least once a day.
Next, I tried to go back to Fedora 15, but install the 32bit installation. I installed it but still occasionally get crashes/kernel panics.
I have the bios flashed with the latest update.
I do not believe this is distribution related. While I haven't tried recently, in the past I have tried other distributions and got the same behavior.
Does anyone have any suggestions how I solve this? I felt it was hardware but why does Windows and that one Linux kernel run without issue? Could there be any setting in my bios I should change?
What do you mean with crashing? Post the error messages you get, or we have to guess what is going on.
If you think that it is hardware do some basic tests, like Memtest86+ and the harddisk manufacturers diagnosis tool.
You also may want to set the BIOS settings to their default value and try some kernel parameters, like noacpi, noapic and so on.
I really think that diagnostics should be run on the hardware to rule that issue out.
UBCD Ultimate Boot CD allows users to run floppy-based diagnostic tools from most CDROM drives on Intel-compatible machines, no operating system required. The CD includes many diagnostic utilities. Memtest86+ is on UBCD, run that for a few passes or overnight if possible.
I believe this issue is hardware & possibly the way you have configured things. If it is a intermittent hardware issue then you do have a lot of work ahead.
Moved this thread to <Linux-Hardware> to provide a broader audience that may help you to solve the issue(s).
Distribution: Cinnamon Mint 20.1 (Laptop) and 20.2 (Desktop)
Posts: 1,672
Rep:
Quote:
The machine is a 64 bit machine built by myself. I have an AMD 3800 dual core 64 bit processor with an MSI board. I have it dual booting between Linux and Windows XP. XP runs without any problems.
Sounds just like my set up,AMD 3800, MSI board, I've been running Ubuntu (10.10 now)on it for quite some time. What's the Mobo part No.? Can you also give us the spec of any other added cards?
Linux may never work correctly. It was never tested on linux at the factory.
I'd at least set bios to failsafe or default settings and be sure that you have best quality ide or sata cables. Run memtest for a few days too. Re-check any voltages and memory timings.
What's the Mobo part No.? Can you also give us the spec of any other added cards?
+1. Without more information, we are just guessing.
Copying the ouput from 'lspci' and 'lshw' would help. BTW, please paste the output from those commands into 'code'tags, it keeps the thread tidy.
Quote:
Originally Posted by jefro
Linux may never work correctly. It was never tested on linux at the factory.
LMAO.
How many manufacturers test motherboards with linux distros? Offically, not 'techies playing with the hardware in the backroom'. Virtually none I'll bet.
My Motherboard is a K8N Neo4 Platinum (PCB 3.0), MS-7125. I have 4 GB of memory in it (4 - 1 GB sticks), 2 sets of Corsair Dual channel. I have an Nvidia GeForce 6600 GT video card. I am using the nouveav driver.
I say that I get kernel crashes, but perhaps this isn't a proper description. The majority of the time, my system just locks up or freezes. Nothing responds; the console or the network cards. I have to hit the reset button on the case. I cannot find anything in any logs.
In Fedora 15, I do get a little different behavior. I have started getting kernel panics. F15 64 bit will not install, so I cannot get any screen shots or stack traces of the kernel panic I get during the install. I was able to get F15 32 bit installed. I did find this under /var/spool/abrt.
I did a bit of a search, and I didnt find any major problems with that motherboard and linux. Its possible that you have slightly 'sick' hardware. A few things you can try-
Change nouveav to the closed source nvidia drivers.
Remove the side from the case and point a desktop fan into the case. This should help if your problem is heat related.
Unpower 1 of the 2 HDDs, and 1 of the 2 DVD drives.
Thanks for the suggestions. I have already tried most of them in some form or fashion.
I tried the Nvidia proprietary driver and the machine froze with it also.
I removed 2 of the sticks of ram. When it still failed, I replaced them with the other two. Still failed.
I unplugged the Windows drive and the system failed. I also unplugged the two drives and switched their cables. Still same result. I even tried unplugging both and starting the install on Fedora 15 without any drives and it crashed like always, without even getting to the graphical install.
I have been watching CPU temp and it pretty much stays at 36 C. I have used lm_sensors to watch it and have never been a problem. I guess it doesn't mean it still couldn't be heat, but I am having my doubts.
I also changed the memory timings from letting the board do it (i.e. "auto"), to setting them by hand (2-3-3-6) as Corsair states. Still getting the same system freeze and panics. I am currently running Memtest86 all weekend. So far no errors, but I will let it go another 24 hours and see what happens.
The only thing I have left is the Motherboard and the Video card. I do not have access to any other video card that is PCIe x16. Any other way I can rule it out? I am feeling it is the motherboard. I have seen kernel panics stating "could not load page into memory". This has nothing to do with Video. The machine is so old (5 years) that I cannot just replace a component of it without upgrading a bunch. I am preparing to replace board, processor, and memory, as well as the video card.
I still do not understand why Windows XP and Fedora 13 with a particular kernel are stable, but all other installations of Linux are not. I do not believe this is Linux's fault, but I still cannot understand why Linux is the only thing it has a problem with. Its just driving me nuts......
I have my memory settings at 2-3-3-6, which is what Corsair recommends for my memory. They also recommend 2.75 volts. My board is set at 2.65v. When I set the bios to 2.75, I get a flashing warning "Not recommended - system may be unstable".
Who is right? Its Corsair's memory. So shouldn't they know what their memory can handle? Could this be my problem all along?
Both are right, your BIOS and Corsair. While the specification says that standard conform RAM has to have 2.6V (+-0.1V) for DDR1-400 you seem to have overclocker-RAM which can only (in most cases) bring its specified speed and timings with 2.75V.
So go for 2.75V and see what happens.
Thanks for the suggestions. I have already tried most of them in some form or fashion.
Oh well, probably better than none of those solutions worked, if you can track down what the issue is.
Quote:
Originally Posted by zeigleml
The only thing I have left is the Motherboard and the Video card. I do not have access to any other video card that is PCIe x16. Any other way I can rule it out? I am feeling it is the motherboard. I have seen kernel panics stating "could not load page into memory". This has nothing to do with Video. The machine is so old (5 years) that I cannot just replace a component of it without upgrading a bunch. I am preparing to replace board, processor, and memory, as well as the video card.
I still do not understand why Windows XP and Fedora 13 with a particular kernel are stable, but all other installations of Linux are not. I do not believe this is Linux's fault, but I still cannot understand why Linux is the only thing it has a problem with. Its just driving me nuts......
That, and the voltage issue makes me think it could well be RAM related. Its possible that XP and fedora 13 are less agressive with memory, and thats why they run OK.
+1 to TobiSGD, try it at 2.75v. If that fails, try it at 2.8v (nowhere near as risky as you might guess) or drop the timings and/or speed.
I had similar problems I couldn't diagnose; nothing would run on my box except WinXP and Debian. I swapped out everything I could, checked everything, still had problems. In the end it turned out it was the motherboard.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.