public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <larry.finger@lwfinger.net>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	bcm43xx devel <Bcm43xx-dev@lists.berlios.de>
Subject: Re: Need help with modules loading
Date: Fri, 17 Aug 2007 09:51:46 -0500	[thread overview]
Message-ID: <46C5B602.2060706@lwfinger.net> (raw)
In-Reply-To: <3ae72650708170055p51846c6dp8d8e5b22138f627a@mail.gmail.com>

Kay Sievers wrote:
> On 8/17/07, Larry Finger <Larry.Finger@lwfinger.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.

Thanks for the help. A new rule in sysconfig.rules took care of the problem.

I added the bcm43xx developers mailing list to this reply. For their benefit, this is the patch that 
fixed my system:

Index: /etc/udev/rules.d/80-sysconfig.rules
===================================================================
--- /etc/udev/rules.d.orig/80-sysconfig.rules
+++ /etc/udev/rules.d/80-sysconfig.rules
@@ -15,5 +15,6 @@ SUBSYSTEM=="pnp", ACTION=="add", RUN+="/
  SUBSYSTEM=="ide", ACTION=="add", RUN+="/sbin/hwup ide-devpath-%p -o hotplug"
  SUBSYSTEM=="input", KERNEL=="input[0-9]*", ACTION=="add", RUN+="/sbin/hwup input-devpath-%p -o 
hotplug"
  SUBSYSTEM=="platform", ACTION=="add", RUN+="/sbin/hwup platform-devpath-%p -o hotplug"
+SUBSYSTEM=="ssb", ACTION=="add", ENV{MODALIAS}=="?*", RUN+="/sbin/modprobe $env{MODALIAS}"

  LABEL="sysconfig_end"


Larry

      reply	other threads:[~2007-08-17 14:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-17  2:33 Need help with modules loading Larry Finger
2007-08-17  7:55 ` Kay Sievers
2007-08-17 14:51   ` Larry Finger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46C5B602.2060706@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=Bcm43xx-dev@lists.berlios.de \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox