How to _not_ load ipw2200 on startup

On 26.10.2007 21:47, David W Noon wrote:

> On Friday 26 Oct 2007 11:21 in article
> <4721BFBE.1030508.DeleteThis@gaston.Weilbacher.org> of alt.os.linux.gentoo, Peter
> Weilbacher(newsspam@weilbacher.org) wrote:
>
>> radio should stay off until I tell it to come up. I already
>> managed to find out that I should add RC_PLUG_SERVICES="!net.wlan"
>> to /etc/conf.d/rc to keep udev-postmount from trying to initalize
>
> AFAIAA, the options in /etc/conf.d/rc are for init, not udev. As a
> result, I would suspect the postmount modprobes from udev to be the
> culprit in this case.
>
> Take a look at /etc/modprobe.d/blacklist and add the unwanted driver.

Thanks for the hint. Took until now to actually try it out.
Unfortunately, it didn't help. ipw2200 is still loaded after
startup.

Peter.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 09 Nov 2007 17:20 in article
<473496C7.3060101 DeleteThis @gaston.Weilbacher.org> of alt.os.linux.gentoo, Peter
Weilbacher(newsspam@weilbacher.org) wrote:

> On 26.10.2007 21:47, David W Noon wrote:
[snip]
>> Take a look at /etc/modprobe.d/blacklist and add the unwanted driver.
>
> Thanks for the hint. Took until now to actually try it out.
> Unfortunately, it didn't help. ipw2200 is still loaded after
> startup.

Did you do an update-modules before rebooting?

- --
Regards

Dave [RLU#314465]
======================================================
dwnoon DeleteThis @spamtrap.ntlworld.com (David W Noon)
Remove spam trap to reply via e-mail.
======================================================

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFHNJef9MqaUJQw2MkRAq4CAJ9ow3JnJ4SiwXeTg6IK98URbpiuewCeJgpZ
JRtFtBz/ztQeVhpV1pl6KW4=
=dl+I
-----END PGP SIGNATURE-----

On 09.11.2007 18:43, David W Noon wrote:

> On Friday 09 Nov 2007 17:20 in article
> <473496C7.3060101.TakeThisOut@gaston.Weilbacher.org> of alt.os.linux.gentoo, Peter
> Weilbacher(newsspam@weilbacher.org) wrote:
>
>> On 26.10.2007 21:47, David W Noon wrote:
> [snip]
>>> Take a look at /etc/modprobe.d/blacklist and add the unwanted driver.
>>
>> Thanks for the hint. Took until now to actually try it out.
>> Unfortunately, it didn't help. ipw2200 is still loaded after
>> startup.
>
> Did you do an update-modules before rebooting?

Not initially. Didn't know about that command and still don't know
what it really does. But now I did, I even tried with -f. No change,
ipw2200 is still loaded on startup...
Peter.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 10 Nov 2007 22:45 in article
<47363489.9050502 DeleteThis @gaston.Weilbacher.org> of alt.os.linux.gentoo, Peter
Weilbacher(newsspam@weilbacher.org) wrote:

> On 09.11.2007 18:43, David W Noon wrote:
[snip]
>> Did you do an update-modules before rebooting?
>
> Not initially. Didn't know about that command and still don't know
> what it really does. But now I did, I even tried with -f.

It rebuilds /etc/modules.conf from the various Gentoo-specific lists of
device drivers. It's the step everyone forgets when changing hardware
configurations.

> No change, ipw2200 is still loaded on startup...

Can you post the syslog lines with their surrounding context? This might
give us a more precise idea when and from where the driver is being
loaded.
- --
Regards

Dave [RLU#314465]
======================================================
dwnoon DeleteThis @spamtrap.ntlworld.com (David W Noon)
Remove spam trap to reply via e-mail.
======================================================

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFHNxGg9MqaUJQw2MkRAsjqAJ47XGhpe9nJmN9y+tdE8Veeg4HlPQCfY4tt
MJvqyrNj85nwMphsD8IflSk=
=QuT/
-----END PGP SIGNATURE-----

On Sat, 10 Nov 2007 23:45:29 +0100, Peter Weilbacher wrote:

> On 09.11.2007 18:43, David W Noon wrote:
>
>> On Friday 09 Nov 2007 17:20 in article
>> <473496C7.3060101 DeleteThis @gaston.Weilbacher.org> of alt.os.linux.gentoo, Peter
>> Weilbacher(newsspam@weilbacher.org) wrote:
>>
>>> On 26.10.2007 21:47, David W Noon wrote:
>> [snip]
>>>> Take a look at /etc/modprobe.d/blacklist and add the unwanted driver.
>>>
>>> Thanks for the hint. Took until now to actually try it out.
>>> Unfortunately, it didn't help. ipw2200 is still loaded after startup.
>>
>> Did you do an update-modules before rebooting?
>
> Not initially. Didn't know about that command and still don't know what
> it really does. But now I did, I even tried with -f. No change, ipw2200
> is still loaded on startup...
> Peter.

Move the driver (or rename it) from /lib/modules/your_kernel/kernel/
drivers/net/wireless/ipw2200.ko

On 11.11.2007 15:45, David W Noon wrote:

> It rebuilds /etc/modules.conf from the various Gentoo-specific lists of
> device drivers. It's the step everyone forgets when changing hardware
> configurations.

Ah, OK. No hardware change involved here, though. And ipw2200 isn't even
listed in that file...

>> No change, ipw2200 is still loaded on startup...
>
> Can you post the syslog lines with their surrounding context? This might
> give us a more precise idea when and from where the driver is being
> loaded.

OK, pasted the stuff from startup below. Everything of that happened
within the same second (the timestamp that I stripped from the beginning
of each line didn't change).

Peter.

----------------------------- snip ---------------------------------------------
[fglrx] USWC is disabled in module parameters
[fglrx] PAT is disabled!
[fglrx] module loaded - fglrx 8.40.4 [Jul 31 2007] on minor 0
ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 19 (level, low) -> IRQ 20
PM: Adding info for No Bus:i2c-0
Device driver i2c-0 lacks bus and class support for being resumed.
ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno.DeleteThis@linux.intel.com>
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.0k
ipw2200: Copyright(c) 2003-2006 Intel Corporation
ACPI: PCI Interrupt 0000:01:02.0[A] -> GSI 17 (level, low) -> IRQ 17
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
PM: Adding info for No Bus:0000:01:02.0
Device driver 0000:01:02.0 lacks bus and class support for being resumed.
PM: Removing info for No Bus:0000:01:02.0
PM: Adding info for No Bus:eth0
Device driver eth0 lacks bus and class support for being resumed.
ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
Yenta: CardBus bridge found at 0000:01:01.0 [1043:1967]
udev: renamed network interface eth0 to lan1
Yenta: ISA IRQ mask 0x04b8, PCI irq 17
Socket status: 30000006
pcmcia: parent PCI bridge I/O window: 0xa000 - 0xafff
pcmcia: parent PCI bridge Memory window: 0xfe900000 - 0xfe9fffff
pcmcia: parent PCI bridge Memory window: 0x50000000 - 0x55ffffff
----------------------------- snip ---------------------------------------------

On 13.11.2007 05:48, nunya wrote:

> Move the driver (or rename it) from /lib/modules/your_kernel/kernel/
> drivers/net/wireless/ipw2200.ko

And then when I do want to load it move it back before doing modprobe?
I don't doubt that it works, but what an ugly hack. I really want to
understand what's going on...

Thanks anyway,
Peter.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 13 Nov 2007 14:17 in article
<4739B201.2050009 RemoveThis @gaston.Weilbacher.org> of alt.os.linux.gentoo, Peter
Weilbacher(newsspam@weilbacher.org) wrote:

> On 11.11.2007 15:45, David W Noon wrote:
>
>> It rebuilds /etc/modules.conf from the various Gentoo-specific lists
>> of device drivers. It's the step everyone forgets when changing
>> hardware configurations.
>
> Ah, OK. No hardware change involved here, though. And ipw2200 isn't
> even listed in that file...

Okay. That usually means that it is being insmod'ed as a dependency of
another driver.

[snip]
> ieee80211_crypt: registered algorithm 'NULL'
> ieee80211: 802.11 data/management/control stack, git-1.1.13
> ieee80211: Copyright (C) 2004-2005 Intel Corporation
> <jketreno RemoveThis @linux.intel.com> ipw2200: Intel(R) PRO/Wireless 2200/2915
> Network Driver, 1.2.0k ipw2200: Copyright(c) 2003-2006 Intel
> Corporation ACPI: PCI Interrupt 0000:01:02.0[A] -> GSI 17 (level, low)
> -> IRQ 17 ipw2200: Detected Intel PRO/Wireless 2200BG Network

It looks like the ieee80211 and/or ieee80211_crypt driver [probably the
former] requires a physical transportation driver. You could try adding
them to the blacklist as well.

This looks similar to the situation I had with the new Firewire stack:
the later drivers required firewire_core, so it was being loaded even
though I had blacklisted it. I simply put all 3 in the blacklist, so:

# Prevent the experimental Firewire drivers from loading.
blacklist firewire_core
blacklist firewire_ohci
blacklist firewire_sbp2

- --
Regards

Dave [RLU#314465]
======================================================
dwnoon RemoveThis @spamtrap.ntlworld.com (David W Noon)
Remove spam trap to reply via e-mail.
======================================================

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFHOdyg9MqaUJQw2MkRAg5+AJ9R6cd6jpTIQ7sKvu9+uyJ8VZ9A+QCgpXQl
leOuhZqrPDGuAbJkTQnhhYA=
=bL47
-----END PGP SIGNATURE-----

On 13.11.2007 18:45, David W Noon wrote:

> On Tuesday 13 Nov 2007 14:17 in article
> <4739B201.2050009.RemoveThis@gaston.Weilbacher.org> of alt.os.linux.gentoo, Peter
> Weilbacher(newsspam@weilbacher.org) wrote:
>
>> On 11.11.2007 15:45, David W Noon wrote:
>>
>>> It rebuilds /etc/modules.conf from the various Gentoo-specific lists
>>> of device drivers. It's the step everyone forgets when changing
>>> hardware configurations.
>>
>> Ah, OK. No hardware change involved here, though. And ipw2200 isn't
>> even listed in that file...
>
> Okay. That usually means that it is being insmod'ed as a dependency of
> another driver.

Actually, none of the four drivers I list below are in the generated
modules.conf.

> [snip]
>> ieee80211_crypt: registered algorithm 'NULL'
>> ieee80211: 802.11 data/management/control stack, git-1.1.13
>> ieee80211: Copyright (C) 2004-2005 Intel Corporation
>> <jketreno.RemoveThis@linux.intel.com> ipw2200: Intel(R) PRO/Wireless 2200/2915
>> Network Driver, 1.2.0k ipw2200: Copyright(c) 2003-2006 Intel
>> Corporation ACPI: PCI Interrupt 0000:01:02.0[A] -> GSI 17 (level, low)
>> -> IRQ 17 ipw2200: Detected Intel PRO/Wireless 2200BG Network
>
> It looks like the ieee80211 and/or ieee80211_crypt driver [probably the
> former] requires a physical transportation driver. You could try adding
> them to the blacklist as well.
>
> This looks similar to the situation I had with the new Firewire stack:
> the later drivers required firewire_core, so it was being loaded even
> though I had blacklisted it. I simply put all 3 in the blacklist, so:

Had already tried that. When I do modprobe -v ipw2200 I see

insmod /lib/modules/2.6.22-suspend2-r1/kernel/drivers/base/firmware_class.ko
insmod /lib/modules/2.6.22-suspend2-r1/kernel/net/ieee80211/ieee80211_crypt.ko
insmod /lib/modules/2.6.22-suspend2-r1/kernel/net/ieee80211/ieee80211.ko
insmod /lib/modules/2.6.22-suspend2-r1/kernel/drivers/net/wireless/ipw2200.ko

so I had added all four of them to the blacklist. But that didn't help. I
think it is actually not udev which is loading them. I see the output about
the ipw2200 driver much earlier in the boot process then I see anything
about udev...

Is there any way to actually capture the output I see on the screen during
boot? dmesg output and /var/log/messages only contain part of that stuff.

Peter.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 14 Nov 2007 10:03 in article
<473AC7D7.3050201.DeleteThis@gaston.Weilbacher.org> of alt.os.linux.gentoo, Peter
Weilbacher(newsspam@weilbacher.org) wrote:

> On 14.11.2007 02:45, David W Noon wrote:
[snip]
>> What does the firmware_class driver do? Can you add it to the
>> blacklist as well?
>
> I can only guess that it loads the firmware for the ipw2200 module,
> it's in its list in modules.dep. That firmware in turn probably comes
> from the ipw2200-firmware-3.0 package.

That would explain the dependency then.

> $ tail -6 /etc/modprobe.d/blacklist
>
> blacklist ipw2200
> blacklist ieee80211
> blacklist ieee80211_crypt
> blacklist firmware_class
>
>
>
> I now also added the funny yenta_socket and its dependencies to the
> end of the blacklist, in case it was somehow related to the WLAN
> driver. Then ran update-modules again, rebootet, noted that it didn't
> have any effect.

Does it still turn up in the udev premount output?

You might care to scan your modules.dep file to see whereabouts the
ipw2200, ieee80211 and ieee80211_crypt drivers are referenced, as they
could well have some more relatives hiding in the kernel and modules.
- --
Regards

Dave [RLU#314465]
======================================================
dwnoon.DeleteThis@spamtrap.ntlworld.com (David W Noon)
Remove spam trap to reply via e-mail.
======================================================

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFHOyYa9MqaUJQw2MkRAph/AJ4j+5VpMKJtfLTeTfm9mb1zJdE8lACggSwQ
7LKqAiHvsV3pHdFPc3GOmWQ=
=wvkW
-----END PGP SIGNATURE-----

On 14.11.2007 02:45, David W Noon wrote:

> AFAIAA, udev scans /lib/modules/${KV}/ for all *.ko files, eliminates
> those that are either in the autoload list, the ALSA list, the
> blacklist or any other more specific list of drivers, and attempts
> loading the remainder.

That can't really be true. There are plenty of other *.ko drivers in there
that do not get loaded, like
$ ls /lib/modules/2.6.22-suspend2-r1/kernel/drivers/input/keyboard/
lkkbd.ko newtonkbd.ko sunkbd.ko xtkbd.ko

Or are they listed in a file that I haven't found yet? (Not anywhere in
/etc/, that's for sure...)

Peter.

On 14.11.2007 18:14, David W Noon wrote:

>> I now also added the funny yenta_socket and its dependencies to the
>> end of the blacklist, in case it was somehow related to the WLAN
>> driver. Then ran update-modules again, rebootet, noted that it didn't
>> have any effect.
>
> Does it still turn up in the udev premount output?

Yes.

> You might care to scan your modules.dep file to see whereabouts the
> ipw2200, ieee80211 and ieee80211_crypt drivers are referenced, as they
> could well have some more relatives hiding in the kernel and modules.

Both ieee80211* drivers are listed as dependencies for ipw2200 and for
some other more specific ieee80211_crypt_* drivers which do not get
loaded. But ipw2200 is not listed anywhere else.

Peter.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 16 Nov 2007 10:43 in article
<473D7453.6000604 DeleteThis @gaston.Weilbacher.org> of alt.os.linux.gentoo, Peter
Weilbacher(newsspam@weilbacher.org) wrote:

> On 14.11.2007 18:14, David W Noon wrote:
[snip]
>> Does it still turn up in the udev premount output?
>
> Yes.

This would imply that udev can still find a dependency that requires
that driver.

>> You might care to scan your modules.dep file to see whereabouts the
>> ipw2200, ieee80211 and ieee80211_crypt drivers are referenced, as
>> they could well have some more relatives hiding in the kernel and
>> modules.
>
> Both ieee80211* drivers are listed as dependencies for ipw2200 and for
> some other more specific ieee80211_crypt_* drivers which do not get
> loaded. But ipw2200 is not listed anywhere else.

Can you please post the output from lsmod? This could also reveal some
dependency details.

You might care to add the other ieee802111_crypt_* modules to the
blacklist. I think any and all modules that you don't want loaded
should appear in the blacklist. [Obviously, those that support hardware
you don't have will usually not initialize properly, so they can safely
be omitted; indeed, they can be safely omitted from the kernel make.]
- --
Regards

Dave [RLU#314465]
======================================================
dwnoon DeleteThis @spamtrap.ntlworld.com (David W Noon)
Remove spam trap to reply via e-mail.
======================================================

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFHPa/M9MqaUJQw2MkRAiEnAKCdo3SRSXKct12eHLCxgwcT/KpmUgCfddhd
a50KuzdnoHJBXHGadpE7Q68=
=cShj
-----END PGP SIGNATURE-----