Arch Linux

Eschatokyrios

Member

Registered: 2007-09-22

Posts: 51

module explicitly blacklisted in rc.conf loads anyway

I don't want to load the bcm43xx module at startup. I have the line MOD_BLACKLIST(bcm43xx) in rc.conf, and no mention of that module in the MODULES line, but it loads anyway. I also tried adding !bcm43xx to MODULES, but that didn't work either (I'm not sure what the difference between !modname in MODULES and modname in MOD_BLACKLIST is anyway, if there even is a difference). Anyway, I have to manually rmmod bcm43xx every time I log in which is annoying, so how do I make it not load?

lilsirecho

Veteran

Registered: 2003-10-24

Posts: 5,000

Re: module explicitly blacklisted in rc.conf loads anyway

Post rc.conf....

EDIT:  Also run find for the module and discover how many entries there are....it may be a dependency for anothermodule.

Last edited by lilsirecho (2007-12-14 21:25:38)

---

Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Eschatokyrios

Member

Registered: 2007-09-22

Posts: 51

Re: module explicitly blacklisted in rc.conf loads anyway

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
TIMEZONE="Canada/Pacific"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

#
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=(bcm43xx)
#
# Modules to load at boot-up (in this order)
#   - prefix a module with a ! to blacklist it
#
MODULES=(r8169 slhc snd-mixer-oss snd-pcm-oss !bcm43xx snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore ndiswrapper)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="archhost-new"
#
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available
# interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
eth0="eth0 192.168.1.5 netmask 255.255.255.0 broadcast 192.168.1.255"
INTERFACES=(lo eth0)
#
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
#
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network-profiles
#
#NET_PROFILES=(main)

#
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng network netfs crond network-function-ec)


# End of file

On a slightly related note, is there any harm in arbitrarily changing the hostname entry to something different?

lilsirecho

Veteran

Registered: 2003-10-24

Posts: 5,000

Re: module explicitly blacklisted in rc.conf loads anyway

You may change the hostname to "George Bush" if you like!! Or mebbe "SantaClaus"

Merry christmas!!!

---

Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Eschatokyrios

Member

Registered: 2007-09-22

Posts: 51

Re: module explicitly blacklisted in rc.conf loads anyway

Post rc.conf....

EDIT:  Also run find for the module and discover how many entries there are....it may be a dependency for anothermodule.

I ran find bcm43xx, it said there was no such file or directory.

lilsirecho

Veteran

Registered: 2003-10-24

Posts: 5,000

Re: module explicitly blacklisted in rc.conf loads anyway

Also try lsmod for the entire module listing.

---

Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Eschatokyrios

Member

Registered: 2007-09-22

Posts: 51

Re: module explicitly blacklisted in rc.conf loads anyway

What should I be looking for in lsmod? By now I've rmmoded bcm43xx and nothing seems broken. It's a driver for my wlan card, so it shouldn't be a dependancy for anything. Except possibly ndiswrapper, but ndiswrapper works fine without it (in fact, ndiswrapper won't load wlan0 properly unless I remove bcm43xx and reload ndiswrapper, which is why I'm wondering about this in the first place).

lilsirecho

Veteran

Registered: 2003-10-24

Posts: 5,000

Re: module explicitly blacklisted in rc.conf loads anyway

Lsmod should show the module in question if it is indeed loaded.  If not, it isn't.

---

Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Eschatokyrios

Member

Registered: 2007-09-22

Posts: 51

Re: module explicitly blacklisted in rc.conf loads anyway

bcm43xx definately loads at startup, as shown by lsmod. I have to remove it manually with rmmod. I don't want it to load at startup, and that's what I'm trying to stop. I thought that by adding "bcm43xx" to rc.conf, that would stop the module from loading, but it didn't, the module loads anyway. That's the problem I'm trying to fix.

Korey Kaczynski

Member

Registered: 2007-11-30

Posts: 36

Re: module explicitly blacklisted in rc.conf loads anyway

Maybe bcm43xx is loaded in mkinitcpio.conf?  I'm not exactly sure if that can happen, but I guess any help is useful.

It's possible that another mod loads it,but I doubt that's the case with bcm43xx.

Last edited by Korey Kaczynski (2007-12-15 02:12:17)

lilsirecho

Veteran

Registered: 2003-10-24

Posts: 5,000

Re: module explicitly blacklisted in rc.conf loads anyway

It is now apparent that the module in question is not being removed by the MODULE _BLACKLIST nor by the inclusion of ! in the list of modules.

Therefore the problem must be introduced by incorrect versions of init within his system.

Perhaps a :

     

   pacman -Syu

This will load all pertinent elements to correct the discrepancy.  It may produce some errors while in the install portion.  These can be overriden with:
   

pacman -Syuf

The result will be the install from cache of the packages downloaded and a possible correction of the discrepancy.

---

Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

bender02

Member

From: UK

Registered: 2007-02-04

Posts: 1,328

Re: module explicitly blacklisted in rc.conf loads anyway

Have a look at /etc/rc.sysinit (bash init script) on how are the modules loaded. As Korey noted, if your module gets loaded by initcpio script (ie before rc.sysinit), then it does NOT get unloaded even if you blacklist it. You can check by running zcat /boot/kernel26.img | cpio -tv if it is included in your initcpio image. That said, I would be really surprised if it is there.

Second thing, you can try to blacklist the module in /etc/modprobe.conf (man modprobe.conf), that way no program should be able to insert the module.

Eschatokyrios

Member

Registered: 2007-09-22

Posts: 51

Re: module explicitly blacklisted in rc.conf loads anyway

zcat /boot/kernel26.img | cpio -tv | grep bcm43xx gets me:

drwxr-xr-x   2 root     root            0 Dec  1 07:07 /lib/modules/2.6.22-ARCH/kernel/drivers/net/wireless/bcm43xx
-rw-r--r--   1 root     root       220008 Aug  2 10:34 /lib/modules/2.6.22-ARCH/kernel/drivers/net/wireless/bcm43xx/bcm43xx.ko

I put a line "blacklist bcm43xx" in modprobe.conf, that didn't do anything.

bender02

Member

From: UK

Registered: 2007-02-04

Posts: 1,328

Re: module explicitly blacklisted in rc.conf loads anyway

Well, modprobe.conf affects things *after* booting the kernel and running the initcpio; so apparently some initcpio hook loads the module. Have a look at mkinitcpio (that's the program that gets run after each update of kernel26 package and generates the initcpio), at /etc/mkinitcpio.conf. I think the hook "autodetect" or "udev" might be the one that pulls in the unwanted module. When I think about it now, maybe it's enough now to run mkinitcpio to have it create the initcpio again, as you've disabled the module in modprobe.conf. Maybe also unload the module before creating it. The command should be mkinitcpio -p kernel26.

Eschatokyrios

Member

Registered: 2007-09-22

Posts: 51

Re: module explicitly blacklisted in rc.conf loads anyway

Making a new initcpio worked, thanks muchly.