Thanks for your help. I was afraid that the disk may be the problem, although the only
time I get these errors is on boot. I did replace the cable with a new cable which I had
laying around. So, if it is hardware, it is the disk (ah well). The disk appeared to be
happy when no other device was on the cable with it.
I am running 2.4.16-4GB kernel. It is the stock kernel rpm from SuSE and I believe that
they have experimental support on by default. Is the Use multi-mode by default and
configuration file option or a option in the config file for compiling the kernel?
Thanks,
JIm
12/27/01 01:59:33 PM, Jon Pennington
On Thu, 2001-12-27 at 07:01, James Bliss wrote:
Thanks for your help Robert and Jon.
I hope my usefulness is not over yet... :)
I now have it up and running. I still get some: <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
I remember now. In 2.4 and the last of the 2.2 Linux kernels, if you have Experimental support on, in the IDE/ATA drivers, there's an option called "Use multi-mode by default," which should be ON. From the help on this option:
CONFIG_IDEDISK_MULTI_MODE:
If you get this error, try to say Y here:
hda: set_multmode: status=0x51 { DriveReady SeekComplete Error } hda: set_multmode: error=0x04 { DriveStatusError }
If in doubt, say N.
You still haven't mentioned which kernel your box is running. I believe that `uname -a` will tell us everything we need to know. If you're already running SuSE's Pentium-optimised kernel, you may need to recompile from source.
In the process of changing all of the drives around I made certain that each was properly set as master or slave.
Well, at this point I'm suspecting a dead cable or a dying disk. Let's have a look at that kernel, one last try from source, maybe, and then we'll get cracking on the hardware.
A short anecdote:
Just a few weeks ago, I was at our LUG meeting, and a fellow brought in his computer for us to install Linux on. He had a "new" Western Digital 6.4GB or so disk, received by him from WD as a replacement for his 3.2G only a few weeks ago. He also had a cable that was as old as the rest of his components, but not more than a year or so. Well, the Mandrake installer hung, the RH installer didn't write to the MBR, and we were all perplexed, so we took the disk out and put it in a new machine. With the new cable in the new machine, the disk appeared much happier, until it was time to reboot. The disk was bad, even though it was only a year old (by manufacturing date) and had only been in use for a few weeks!
Disks die; it's a fact of life. Mechanical parts are prone to failure, and a disk is no exception. Considering the millions upon millions of disks like Junker Jim's SO's laptop that have never needed replaced, and a disk or two that we geeks replace is nothing at all. Don't cry too many tears, but pray that it's still under warranty!
-- -=|JP|=- Need a good geek? I'm unemployed!
'01 B15 SE/PP | http://www.xanga.com/cowboydren/ | />< '95 SL2 Auto | cowboydren @ yahoo . com |
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com