Sorry for the double post, but I used gmane to post this to debian-boot so there was no copy in bugs.debian.org.
> > Mensaje citado por Pelayo Gonzalez <pelayog <at> telecable.es>: > > > Mensaje citado por Frans Pop <aragorn <at> tiscali.nl>: > > > > Thanks for your work on this. > > You welcome!. > > > We will discuss the option of adding this in modprobe.conf somehow. > > Main questions there are: > > - when to do it > > - do we want to do it by default or only if reading the CD without the > > option fails > > My 2 cents: > > Before CDROM detection, check if there are an ATAPI CDROM conected to SATA: > > if test `lsmod | grep '^libata' > then > # There are one or more ATAPI devices disabled? > if [ `dmesg | grep -q '^ata.*WARNING: ATAPI is disabled, device ignored.$'` > ] > then > rmmod all_the_modules_that_depend_on_libata > rmmod libata > echo 'options libata atapi_enabled=1' >> /etc/modprobe.d > modprobe libata > modprobe all_the_modules_that_depend_on_libata > LIBATA_HAS_ATAPI=1 > else > LIBATA_HAS_ATAPI=0 > fi > fi > Before you waste your time this doesn't work. Once installed libata removing and reinstalling them has no effect :-(. So I suggest two options: 1 - Ubuntu way: Enable ATAPI by default both in installer and in the target initrd. Ubuntu does this since hoary (kernel 2.6.10) without problems in my Dell Inspiron 9300. (I Can't say nothing about other hardware). 2 - Carefull way Enable atapi in the installer, detect CDROMS and if any of them is connected to SATA enable ATAPI support in the target initrd. Anyway I think ATAPI support will be enabled by default in 2.6.16 kernels as it is considered production quality in 2.6.15rcX, see: http://linux.yyz.us/sata/software-status.html Cheers Pelayo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]