BTW, I have the exact same setup with some exceptions: -- I use 4 SATA hard drives on my RocketRAID controller. (Same as yours) and yes.... It is normal for the HPT366 module to load. And yes, it is normal for 2 instances of this to load (1 for channels 1&2 and the 2nd for 3&4)
-- I use a regular ATA hard drive to boot from 80GB Maxtor (grub&os) and use EXT3 on this drive, the other hard drives use REISERFS (2 SATA Maxtors and 2 SATA Western Digital) -- I use Dapper and that's why it still works, because my regular OS recognizes the 1st hard drive as HDA, my CDROM as HDC and my SATA's as HDE,HDG,HDK,HDI respectively. Gutsy would break this setup and I hope they fix it by Hardy! This is a "Mission Critical" box and I won't update it in a random fasion (I will dual boot or replace the primary hard drive on the regular IDE bus to check) -- The above setting/recompile of the kernel should fix this. I would even consider raising this number. What harm would 12 be? Since all drives are SDA/SDxxx anymore.\ -- This may be a bug with some 'new' 374 trickery in gutsy, which this may not work? I know I use the same card as you in Dapper there's no reference to 374 at all, only 366. -- If you use the above fix, lock (PIN in Debian terms) your kernel so it doesn't get updated!!! Or it will re-break your system on an update, unless they change/fix this by default. -- They should change this by default. -- If this doesn't help, please tell me, I am as interested in this problem as you. It's not the easiest thing to recompile the kernel. And most debian/ubuntu instructions work using 'kpkg' not make/make install should work and should update the grub menu. The thing is pointing to the proper kernel image and initrd image in the grub menu. It could be tricky, just remember, you don't need to do the menuconfig or xconfig step, just edit the config.sys file, copy it to your usr/src dir and make sure it's used in your compile instructions (Which I believe needs a good symlink named 'linux' pointed to the the kernel source (All in /usr/src BTW) Hope this helps. -- HPT366 still linked to HPT374 after blacklist https://bugs.launchpad.net/bugs/159397 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
