Bug#363331: Fwd: Re: Bug#363331: installation-reports
On Wednesday 19 April 2006 00:12, Digby Tarvin wrote:
> Actually I should have mentioned that I had tried correcting
> the syntax in modprobe.d. I had changed /etc/modprobe.d/libata to
> "options libata atapi_enabled=1"
> which no longer produces a syntax warning, but I still get
> "ata1(0): WARNING: ATAPI is disabled, device ignored"
That is weird. Guess you'll need to find expert help elsewhere on this.
I haven't got a clue why the kernel is ignoring that option. I suggest you
check the kernel version and google first. I saw you've also written to
debian-laptop. Maybe ask on debian-user or even debian-kernel.
> dmesg also warns:
> "Kernel command line: root=/dev/hda6 ro libata.atapi_enabled=1"
> "Unknown boot option `libata.atapi_enabled=1': ignoring"
> which I assume was added by the install system but the syntax is not
> supported, so should be removed from my grub menu.lst... should't
> be doing any harm though...
Yes, should be removed. Will be fixed in a next upload. Thanks.
> Also grep'ed through the strings output of libata.ko which seems to
> confirm that the 'atapi_enabled' option is indeed there, so I am
> a little puzzled.
One more thing to check is the /proc/<whatever-path-to-device>/settings
file.
> This is presumably related to whatever stopped the install workaround
> for the beta 2 from working vs the daily build workaround which used
> the newer kernel command line option..
Could be though others have specifically tested that with Beta 2...
> > P.S. Please reply to the bug report, not to me privately.
> Sorry - I thought the reply address would be setup for wherever you
> wanted replies to go.
Yeah, I try to do that, but sometimes forget. It is common practice for
any Debian bug report though as that makes sure the whole history is
archived and I obviously get to read the reply anyway :-)
Reply to: