Bug#353942: marked as done (SATA CD-ROM drives unnecessarily hard to get working)
Your message dated Wed, 22 Feb 2006 16:45:37 +0100
with message-id <200602221645.38440.aragorn@tiscali.nl>
and subject line Bug#353942: SATA CD-ROM drives unnecessarily hard to get working
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: debian-installer
Version: 21-Feb-2006
My wife just got a shiny new Fujitsu Lifebook P7120 (thanks to Joey
Hess raving about it on Planet the other day). I downloaded the latest
nightly build for Etch and tried to install it. This far too much fun,
thanks to the SATA CD-ROM drive.
You see, to enable support for SATA CD-ROM drives, you have to set the
libata module parameter 'atapi_enabled=1'. If libata were built in,
that would be the simple matter of passing 'libata.atapi_enabled=1'.
But it's a module, and even in expert mode, libata is loaded before
you get to a shell. Busybox doesn't seem to have an rmmod command,
so you can't unload it and then load it with the option specified.
So you have to boot with BOOT_DEBUG=3 to get a shell prompt where you
'modprobe libata atapi_enabled=1'.
If this doesn't get fixed, the workaround needs to be documented.
I expect Fujitsu won't be the only people shipping SATA CD-ROMs during
the lifecycle of Etch.
--- End Message ---
--- Begin Message ---
On Wednesday 22 February 2006 04:54, Matthew Wilcox wrote:
> If this doesn't get fixed, the workaround needs to be documented.
> I expect Fujitsu won't be the only people shipping SATA CD-ROMs during
> the lifecycle of Etch.
We expect Etch to ship with 2.6.16 or even later and have been told this
SATA ATAPI support should be enabled by default in 2.6.16.
So this is a temporary problem only.
Closing your bug as we're well aware of this issue and tracking it in the
BTS has IMHO no added value (and if it does, I can refer you to several
open installation reports on the subject if you like).
Cheers,
FJP
--- End Message ---
Reply to: