linux-kernel - Re: Need help with modules loading

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3ae72650708170055p51846c6dp8d8e5b22138f627a@mail.gmail.com>
Date:	Fri, 17 Aug 2007 09:55:22 +0200
From:	"Kay Sievers" <kay.sievers@...y.org>
To:	"Larry Finger" <Larry.Finger@...inger.net>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Need help with modules loading

On 8/17/07, Larry Finger <Larry.Finger@...inger.net> wrote:
> A new driver for the Broadcom BCM43xx devices has been written that uses mac80211, rather than
> softmac. The newest versions of the Broadcom firmware does not support all the BCM devices.
> Accordingly, a separate driver is being prepared that will use an older version of the firmware and
> support these legacy devices. Unfortunately, there is not a clean separation based on PCI id's;
> however, the revision level of the 802.11 wireless core can be used to determine which driver should
> be used. The scheme works on most systems, but not mine and I need some help to discover why.

> The 'MODALIAS=ssb:v4243id0812rev0A' line is correct for my device. In fact issuing a modprobe
> "ssb:v4243id0812rev0A" command results in the loading of the module. For some reason, this does not
> happen automatically.
>
> Initially, I suspected that my version of udev (103-13) was too old; however, upgrading to version
> 114 did not help. My module-init-tools are V 3.2.2 and my distro is the x86_64 version of openSUSE 10.2.

openSUSE 10.2 used a whitelist of buses which trigger module loading.
It's in the udev sysconfig. rules and /sbin/hwup.

The easiest is probably to add a rule for that bus:
  ACTION=="add", SUBSYSTEM=="ssb", ENV{MODALIAS}=="?*",
RUN+="/sbin/modprobe $env{MODALIAS}"

openSUSE 10.3 will call modprobe directly, the whitelist and the whole
hwup logic is removed in the meantime.

Kay
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/