Bug#363290: kernel option not available in kernel module
This is a spin-off of #345999.
On Mon, Apr 17, 2006 at 11:48:40AM +0200, Fredrik Olofsson wrote:
> On Saturday, April 15, 2006 at 18:23:28 +0200, Geert Stappers wrote:
> > On Fri, Apr 14, 2006 at 12:00:50AM +0200, Fredrik Olofsson wrote:
> > > Hi.
> > >
> > > An even simpler solution is to boot the installer with:
> > >
> > > install libata.atapi_enabled=1.
> > >
> > > This will correctly propagate to the installed system as well.
> > Thanks for telling, it is documented
> > at http://wiki.debian.org/DebianInstaller/SataAtapiHowto
> But I have realised that it does not work after the reboot. The
> installer adds the option to the kernel command line, but libata does
> not care. So you still have to add the option for modprobe before
> the cdrom can be used in the newly installed system.
<summary what="previous on firstname.lastname@example.org.">
Kernels with build-in module libata do handle libata.atapi_enabled=1 option.
Debian kernels have libata as a module.
The option libata.atapi_enabled does _not_ work for modules.
Debian-installer has "S02modules-params"
The feedback from Fredrik do I read as
There is no S02modules-params in the rebooted system.
Or something else that wents wrong at reboot which needs love.
So what to do with kernel options that are not available in kernel module?