Op 23-10-2006 om 14:02 schreef Jacob L. Anawalt: > Geert Stappers wrote: > > > >It could indeed that IDE modules are not loaded for your hardware. > >When switching to VT2 is possible for you in d-i, > >then I suggest that you manual `modprobe IDE-modules`. > >(And please provide feedback.) > > > > Unfortunately I don't believe that helps as clarified by this post: > > http://www.ubuntuforums.org/showthread.php?t=249655 > > The important bit in linux-2.6-2.6.17/drivers/ide/pci/generic.c: > > #ifndef MODULE > static int __init ide_generic_all_on(char *unused) > { > [ code ] > } > __setup("all-generic-ide", ide_generic_all_on); > #endif > > So, if CONFIG_BLK_DEV_IDE is a module, all-generic-ide is a no-op as far > as the kernel is concerned. This was from linux-2.6_2.6.17.orig.tar.gz + > linux-2.6_2.6.17-9.diff.gz. That block of code is the same in > linux-2.6-2.6.16 with linux-2.6.16_2.6.16-18.diff.gz.
AFAIK should '#ifndef MODULE' be read as preprocessor, include this if MODULE is _not_ defined. I'm saying that I expect IDE module stuff to work. The idea behind "manual modprobing" the IDE modules, is that the initial RAM disk includes various kernel modules and program code to load (insmod, modprobe) modules based on a list of PCI IDs. So when your hardware has unknown PCI IDE controller, the wrong or no module will be loaded. (wrong or no module has the same effect.) Beside my original request > >When switching to VT2 is possible for you in d-i, > >then I suggest that you manual `modprobe IDE-modules`. > >(And please provide feedback.) I also would like to see (filtered) output of lspci and lsmod. Cheers Geert Stappers Who assumes this BR is about a hardware detection issue, so not re-assign to the linux-2.6 package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
