Bug#334104: RFC: workaround for dmfe/tulip module problem
On Sun, Dec 03, 2006 at 10:58:18PM +0000, Richard Mortimer wrote:
> I've tried this and it seems to be a non-starter. It works fine when I
> use it on the modprobe commandline
>
> pingu:/sys/module/dmfe# modprobe dmfe disable=1
> dmfe: driver disabled, aborting initialization.
>
> but when I boot with dmfe.disable=1 on the commandline the driver gets
> loaded.
>
> pingu:/sys/module/dmfe# cat /proc/cmdline
> root=/dev/hda7 ro dmfe.disable=1
>
>
> Built 1 zonelists
> Kernel command line: root=/dev/hda7 ro dmfe.disable=1
> Unknown boot option `dmfe.disable=1': ignoring
> ...
> dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
> hda: ST320423A, ATA DISK drive
> ide0 at 0x1fe02010200-0x1fe02010207,0x1fe0201020a on irq 5,7cc
> hdc: ST320423A, ATA DISK drive
> ide1 at 0x1fe02010210-0x1fe02010217,0x1fe0201020e on irq 5,7cc
> eth0: Davicom DM9102 at pci0000:00:05.0, 00:00:00:00:00:00, irq 7418560.
> eth1: Davicom DM9102 at pci0000:00:0c.0, 00:00:00:00:00:00, irq 7417856.
> Linux Tulip driver version 1.1.13-NAPI (May 11, 2002)
> hda: max request size: 128KiB
>
>
> If I look the kernel documentation in
> Documentation/kernel-parameters.txt it says
>
>
> Module parameters for modules that are built into the kernel image
> are specified on the kernel command line with the module name plus
> '.' plus parameter name, with '=' and value if appropriate, such as:
>
> usbcore.blinkenlights=1
>
>
> I tried building the kernel with dmfe and tulip built in and that
> happily accepted the dmfe.disable=1 and brought the system up with the
> correct (tulip) driver loaded.
[..]
> Thus for your patch to work the tulip and dmfe drivers would need to be
> compiled in statically rather than as modules.
Hi Richard,
You are right that my patch will not help in any way when you are just
booting an already installed system. And that's fine, because it's not
a problem it is trying to solve. When you already have a working
system, you can simply prevent any driver from being loaded by doing
something like
# echo 'blacklist dmfe' > /etc/modprobe.d/dmfe-blacklist
This will prevent udev from loading the driver automatically.
What I want to achieve with the patch is the ability to disable the
module at the installation time. And there the situation is different,
because installer has its own independent logic to pass parameters
like dmfe.disable=1 to the modules (at least that's what it says in
the manual :-). I'll try to build a mini-iso installation image with
the updated modules, which you could test.
Best regards,
--
Jurij Smakov jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
Reply to: