Bug#345999: installation-report: Same problem on a Dell Latitude D610

[Pelayo Gonzalez <pelayog@telecable.es>]

Mensaje citado por Frans Pop <aragorn@tiscali.nl>:

> On Sunday 29 January 2006 11:08, Pelayo Gonzalez wrote:
> > I think that we need to add the line 'options libata atapi_enabled=1'
> > to /etc/modprobe.conf in the initrd image of the debian-installer.
> 
> Could you try to do this manually first to check that it works?
> When you get the first screen of the installer (language question), switch 
> to VT2 (using atl-F2) and use 'nano /etc/modprobe.conf' to add the line.
> 
> One problem with this solution is that it only works for the installation 
> itself. The user would still have a non-working CD drive after the reboot 
> into the installed system.
> 

It's dificult to do with debian installer as libata is loaded BEFORE any user
interaction, and no rmmod is present to remove and reload the modules. 

However, I've installed debian linux-image-2.6.15-1-686 in Ubuntu Breezy,
reboot
in single user mode and CDROM was not detected. dmesg shows that device is
ignored due to ATAPI disabled in libata.

So I've added the line 'libata atapi_enabled=1' to /etc/mkinitramfs/modules,
dpkg-reconfigure linux-mage-2.6.15-1-686, reboot in single user mode and the
CDROM was detected and devices created. The difference among both initrd images
is that the working one has the line 'libata atapi_enabled=1' added to
/conf/modules. However those are initrd images from mkinitramfs in Ubuntu (from
initramfs-tools 0.32), and they are very different from debian-installer
initrd. 

Hope this help

Saludos

Pelayo