Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hi all, I am running a dual opeteron 64-bit machine, with 4gb of RAM, and 6 Ultra SCSI IBM 140GB Hard Drives on two seperate UltraSCSI cards. The OS is fedora core 3 x86-64, setup with 100mb boot, 4gb swap, and the rest of one of the disks for / . It seems to boot fine, then shortly after it freezes and I have to reboot the computer s (sometimes before, sometimes after logging in).
I was wondering if anyone had any ideas that could help me out on the problem.
Thanks, I booted into Knoppix and am testing the memory right now... everything so far has been good. (using memtest) I haven't had a freeze either... which = good news. Are there are any knoppix programs that will test my CPU's out? Or let me know that both are working properly?
I want to make sure it's the OS and not the hardware.
if memtest (can it handle 64bit well?) doesn't report errors check that there is no hardware problem like to much heat causing this. if everything seem to work here, but the message stays - try to exclude acpi related problems. if it keep failing and you think hw is alright - disable mce kernel support. maybe this can be done by passing "nomce" to your kernel at boottime.
however, faulty mem modules can show their errors quite randomly - so i suggest running a few find in / and compile a few kernels (put io&mem load on the machine) to be sure. afaik memtest86 can be booted directly and can check all your mem. use it, if it works on your machine.
re-plug your ram modules for better mechanical contact.
I have had no luck in being able to mount the SCSI drives in knoppix, strangely, since they are both fairly new Ultra SCSI's from adaptec... although, I have been able to boot into both the Fedora rescue thing (where I was missing the nessacary libraries to compile the kernel), knoppix, and knoppix-x86-64 for long periods of time without a freeze.
I was using the hard drives in the fedora rescue too; so I don't think they are bad, and it seems like the CPu and memory are fine.
So, do I conclude it's just the kernel, and find a way to recompile it?
did i get your right?
you disabled mce error checking and ran a memtest where no errors showed up, but your machine keep freezing after random uptime.
btw. a 20minutes check will not give you reliable results. i once had faulty modules and a 1 1/2 day run showed them all (memtest86).
you should be able to get a environment for building a kernel with the development packets from your distribution.
than get the kernelsource from your distr. or download the pristine one from ftp.kernel.org . i don't suggest using 2.6 yet, but it may be necessary to get your hardware supported for sure.. get 2.6.9 which seems to work (for one of my servers).
you can also try just another prebuild kernel from your distribution.
you said your scsi controller is quite new, so google if there are problems with kernel support here. but i can hardly think of a relation between your hangs and a failing scsi-controller(driver).
to actually build a kernel change to the kernel source directory and "make menuconfig". select everything you need and build your kernel. there are instructions about that on the net.
you can also build it on another machine and later install it on the box too.
I haven't disabled MCE error checking; I don't know how to. I was under the impression in was a kernel option. I haven't been able to recompile the kernel because I only have one x86-64 machine, which is the one that keeps freezing, and I thought, to get an accurate view of the problem, that I needed to recompile within the platform. Would I be able to test it accuratly with a 32-bit compilation of the kernel, or do I need a 64-bit one?
Unfortunatly, the machine will run maybe 5 minutes before it freezes. I then tried knoppix, but no luck with the scsi hard drives. I did a google search, which turned up nothing for me, so I thought I would ask this forum, since there are many bright minds that have helped me in the past.
I will also try to find a prebuilt kernel; something I hadn't thought of before; and if that doesn't work I can let memtest86 run over the weekend.
i too come to the impression it has nothing to do with your hardware. so maybe just get a new kernel. i use debian myself, so i can only tell you where to go for a prebuild one from debian. normally you should be able to download one from fedora. have a look at their homepage and ftp-server (there likely will be one where you can get updates).
you can built a kernel on a 32bit maschine, but you can't test it there and it's quite complex since you need all the 64bit-libs and have to customize the kernel's makefile; likely some other things too..
so i think it's best to get a prebuild one and install it first next to your current one to see if it fixes the problem.