Bug#363331: Fwd: Re: Bug#363331: installation-reports
On Tue, Apr 18, 2006 at 09:26:49PM +0200, Frans Pop wrote:
> On Tuesday 18 April 2006 20:04, Frans Pop wrote:
> > > # echo "libata.atapi_enabled=1" >/etc/modutils.d/local
> > >
> > > This file was supposed to be created by the installer, but there was
> > > an error in the code.
> >
> > Still no luck - are you sure about the directory? I had no
> > /etc/modutils.d exiting on my system prior to doing this. Putting it
> > in modprobe.d just produced a syntax error causing the line to be
> > ignored.
>
> Right, made a bit of a mess with that.
> Better do:
> # echo options libata atapi_enabled=1 >> /etc/modprobe.d/libata
> and delete whatever file that was created because of my earlier completely
> broken suggestion.
>
> Sorry about that,
> FJP
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"
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...
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.
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..
> 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.
Regards,
DigbyT
--
Digby R. S. Tarvin digbyt(at)digbyt.com
http://www.digbyt.com
Reply to: