>> I searched the kernel sources and I found this is the "multiple >> devices" driver. That handles disk striping (RAID 0), RAID 5, etc. >> >> I have never heard of this problem, nor do I have any insight as to >> what might cause this error. I was taught to disconnect unnecessary >> devices when things like this happened, reconnect cables and check >> master/slave settings, but maybe you already did that. I do see they use >> different driver versions, and if 0.36.3 works, then perhaps you need >> 0.36.3 for your box. The nature of drivers is to evolve and support more >> devices, after all. I have kernel 2.0.36 (from slink) installed (on hamm) >> and md is version 0.36.3. > >I tried booting with SoundBlaster, CD-ROM and SyJet disabled, but it didn't >seem to help. And all the devices work fine under another O/S (that dare not >speak its name on this list), so I don't think the actual hardware's at fault.
This is not related to this problem, but I thought I'd just throw in some ideas... I have an Adaptec 2940UW, and when I upgraded my motherboard and cpu, I put it in PCI slot #1. Debian cd boot up hung somewhere. (I think at the scsi init area). That "other" O/S still worked perfectly though. But, I switched the adaptec to slot #2, and the video card to slot #1, and everything was fine and dandy again. Reason? I still don't know. Does anyone? maybe you could try removing your hardware and you might find something quirky...