Bug#345999: installation-report: Same problem on a Dell Latitude D610
Mensaje citado por Pelayo Gonzalez [EMAIL PROTECTED]: Mensaje citado por Frans Pop [EMAIL PROTECTED]: 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 Continue CDROM detection. - can we somehow make sure the option is also available after rebooting into the installed system Before kernel install: if [ $LIBATA_HAS_ATAPI ]; then echo 'options libata atapi_enabled=1' /target/etc/modprobe.d/libata fi I hope yaird will pass the option to the initrd. I haven't got time to switch from Ubuntu to Debian yet, so I'm can't try this now. Saludos Pelayo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345999: installation-report: Same problem on a Dell Latitude D610
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]
Bug#345999: installation-report: Same problem on a Dell Latitude D610
Mensaje citado por Pelayo Gonzalez [EMAIL PROTECTED]: 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 Confirmed by Jeff Garzik, see: http://www.opensubscriber.com/message/[EMAIL PROTECTED]/3119024.html Cheers Pelayo González
Bug#345999: installation-report: Same problem on a Dell Latitude D610
On Tue, Jan 31, 2006 at 08:34:13PM +0100, Frans Pop wrote: On Tuesday 31 January 2006 11:20, you wrote: Mensaje citado por Frans Pop [EMAIL PROTECTED]: 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? Sorry I forgot CC you the reply. No need, I read the list where the installation reports are forwarded :-) Yes it works, I´ve posted a Howto to the thread. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=345999 Thanks for your work on this. Hi, I discovered the same problem on my Toshiba Tecra A3x expert24 worked out nice, expert26 fails on No CDROM found issue. I try the things mentioned in the Howto and will send a installation-report after that. Is there a need for an other bug report about the Toshiba since this bug is all ready reported? Greetz, Michel van der Klei
Bug#345999: installation-report: Same problem on a Dell Latitude D610
On Tuesday 31 January 2006 11:20, you wrote: Mensaje citado por Frans Pop [EMAIL PROTECTED]: 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? Sorry I forgot CC you the reply. No need, I read the list where the installation reports are forwarded :-) Yes it works, I´ve posted a Howto to the thread. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=345999 Thanks for your work on this. 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 - can we somehow make sure the option is also available after rebooting into the installed system Cheers, FJP pgpnxJjYBpU40.pgp Description: PGP signature
Bug#345999: installation-report: Same problem on a Dell Latitude D610
Mensaje citado por Pelayo Gonzalez [EMAIL PROTECTED]: Mensaje citado por Frans Pop [EMAIL PROTECTED]: 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. Well I've managed to boot with netinst daily-build (2006-01-16), and CDROM was detected. This is a micro-HowTo: 1 - boot: expert BOOT_DEBUG=3 2 - In the shell: nano /etc/modprobe.conf add the line: options libata atapi_enabled=1 save quit exit from the shell 3 - Continue the installation. After choosing your language and keyboard you can go to the shell (Alt+F2) and verify that you CDROM is there: cat /proc/scsi/scsi 4 - After installs completes don't forget to configure your mkinitrd tool in order to pass 'atapi_enabled=1' to libata, and dpkg-reconfigure linux-image-2.6.15-1-686. Note: If for mkinitramfs you should add 'libata atapi_enabled=1' to /etc/mkinitramfs/modules FixMe: How to configure yaird?. Saludos Pelayo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345999: installation-report: Same problem on a Dell Latitude D610
On Fri, Jan 27, 2006 at 08:40:26AM +0100, Alexander Wintermans wrote: Tried the following at the boot prompt: install libata.enableatapi=1 ... didn't work; same problem. This option does require 2.6.15 (or maybe 2.6.14) based installer. 2.6.12 won't do. Then Googled a bit trying to find an example of the required syntax, and tried this: install libata.atapi_enabled=1 ... didn't work; same problem. However, while surfing around I came across some comments that seem to indicate that this boot parameter only works for kernels 2.6.13 and above, and I'm assuming that the Etch installer uses a 2.6.12 kernel by default. With 2.6.12 the trick seems to be to edit the kernel header files as mentioned on the forum below (not much help in an Etch install situation though): The daily builds should have 2.6.15 I believe. Etch probably doesn't yet. Personally I had to use 2.4 kernel to install, then install a new custom built kernel with the SATA ATAPI code enabled by editing the header file in the kernel. That worked. I guess if I updated it now to 2.6.15 I could use the standard kernel finally. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345999: installation-report: Same problem on a Dell Latitude D610
Both will install 2.6.12 if you install testing...or 2.6.15 if you install unstable. Just tried the same thing with a daily-build image: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso ... same problems, same symptoms. Same problems here with Dell inspiron 9300 see Bug#344268. 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. May debian-installer developers kindly add this line for the upcoming Etch Beta2 release? For more info see http://www.thinkwiki.org/wiki/Problems_with_SATA_and_Linux#No_DMA_on_DVD_drive The reason seems to be that boot parameter 'libata.atapi_enabled=1' only works if libata is built into the kernel (not as a module). I tried to rebuild the iso image with the modified initrd with no luck (kernel panic: can't find /init), so I'm pretty sure I'm missing something creating the initrd. TIA. Regards Pelayo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345999: installation-report: Same problem on a Dell Latitude D610
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. pgpedhk6H00eK.pgp Description: PGP signature
Bug#345999: installation-report: Same problem on a Dell Latitude D610
Mensaje citado por Frans Pop [EMAIL PROTECTED]: 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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345999: installation-report: Same problem on a Dell Latitude D610
On Friday 27 January 2006 08:40, Alexander Wintermans wrote: However, while surfing around I came across some comments that seem to indicate that this boot parameter only works for kernels 2.6.13 and above, and I'm assuming that the Etch installer uses a 2.6.12 kernel by default. The daily built images use a 2.6.15 kernel during the installation. We plan to make a Etch Beta2 release next month that will be based completely on 2.6.15. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345999: installation-report: Same problem on a Dell Latitude D610
However, while surfing around I came across some comments that seem to indicate that this boot parameter only works for kernels 2.6.13 and above, and I'm assuming that the Etch installer uses a 2.6.12 kernel by default. With 2.6.12 the trick seems to be to edit the kernel header Not exactly. The installer images (daily builds you find on http://www.debian.org/devel/debian-installer) use a 2.6.15 kernel The etch beta1 images use 2.6.12 Both will install 2.6.12 if you install testing...or 2.6.15 if you install unstable. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345999: installation-report: Same problem on a Dell Latitude D610
On Fri, 2006-01-27 at 09:19 +0100, Christian Perrier wrote: However, while surfing around I came across some comments that seem to indicate that this boot parameter only works for kernels 2.6.13 and above, and I'm assuming that the Etch installer uses a 2.6.12 kernel by default. With 2.6.12 the trick seems to be to edit the kernel header Not exactly. The installer images (daily builds you find on http://www.debian.org/devel/debian-installer) use a 2.6.15 kernel The etch beta1 images use 2.6.12 Both will install 2.6.12 if you install testing...or 2.6.15 if you install unstable. Just tried the same thing with a daily-build image: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso ... same problems, same symptoms. Regards, Alexander Wintermans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345999: installation-report: Same problem on a Dell Latitude D610
Package: installation-reports Version: 2.9 Followup-For: Bug #345999 -- Package-specific info: Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/etch_d-i/beta1/i386/iso-cd/debian-testing-i386-netinst.iso Date: 26-Jan-2006 Machine: Dell Latitude D610 Partitions: Not relevant Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [E] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Installed system ok:[ ] Comments/Problems: The install runs into trouble whith a dialog 'Detect and mount CD-ROM' that shows the message 'No common CD-ROM drive was detected ... Load CD-ROM drivers from a driver floppy?' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345999: installation-report: Same problem on a Dell Latitude D610
On Thu, Jan 26, 2006 at 02:13:10PM +0100, Alexander Wintermans wrote: Package: installation-reports Version: 2.9 Followup-For: Bug #345999 -- Package-specific info: Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/etch_d-i/beta1/i386/iso-cd/debian-testing-i386-netinst.iso Date: 26-Jan-2006 Machine: Dell Latitude D610 Partitions: Not relevant Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [E] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Installed system ok:[ ] Comments/Problems: The install runs into trouble whith a dialog 'Detect and mount CD-ROM' that shows the message 'No common CD-ROM drive was detected ... Load CD-ROM drivers from a driver floppy?' My experience with the D610, is that it requires either the old piix interface from 2.4 kernels or a 2.6 kernel with LIBATA ATAPI support enabled. If the installer uses a very new 2.6 kernel, you could try the libata.enableatapi=1 (or whatever the syntax is) option at the boot prompt. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345999: installation-report: Same problem on a Dell Latitude D610
-Original Message- From: Lennart Sorensen [mailto:[EMAIL PROTECTED] Sent: Thursday, January 26, 2006 4:37 PM To: Alexander Wintermans; [EMAIL PROTECTED] Subject: Re: Bug#345999: installation-report: Same problem on a Dell Latitude D610 On Thu, Jan 26, 2006 at 02:13:10PM +0100, Alexander Wintermans wrote: ... The install runs into trouble whith a dialog 'Detect and mount CD-ROM' that shows the message 'No common CD-ROM drive was detected ... Load CD-ROM drivers from a driver floppy?' My experience with the D610, is that it requires either the old piix interface from 2.4 kernels or a 2.6 kernel with LIBATA ATAPI support enabled. If the installer uses a very new 2.6 kernel, you could try the libata.enableatapi=1 (or whatever the syntax is) option at the boot prompt. Len Sorensen Tried the following at the boot prompt: install libata.enableatapi=1 ... didn't work; same problem. Then Googled a bit trying to find an example of the required syntax, and tried this: install libata.atapi_enabled=1 ... didn't work; same problem. However, while surfing around I came across some comments that seem to indicate that this boot parameter only works for kernels 2.6.13 and above, and I'm assuming that the Etch installer uses a 2.6.12 kernel by default. With 2.6.12 the trick seems to be to edit the kernel header files as mentioned on the forum below (not much help in an Etch install situation though): http://kerneltrap.org/node/5836 Regards, Alexander Wintermans
