linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hauke Mehrtens <hauke@hauke-m.de>
To: tim.gardner@canonical.com
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
	Bryan Wu <bryan.wu@canonical.com>,
	Mauro Di Domenico <didomauro@tiscali.it>,
	bcm43xx-dev@lists.berlios.de,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: A problem loading ssb module
Date: Sat, 26 Sep 2009 17:15:47 +0200	[thread overview]
Message-ID: <4ABE3023.3020006@hauke-m.de> (raw)
In-Reply-To: <4ABC0B60.5070909@canonical.com>

[-- Attachment #1: Type: text/plain, Size: 3080 bytes --]

Tim Gardner wrote:
> Luis R. Rodriguez wrote:
>> On Thu, Sep 24, 2009 at 5:04 PM, Tim Gardner
>> <tim.gardner@canonical.com> wrote:
>>> Luis R. Rodriguez wrote:
>>>> On Thu, Sep 24, 2009 at 11:33 AM, Hauke Mehrtens <hauke@hauke-m.de>
>>>> wrote:
>>>>> Bryan Wu wrote:
>>>>>> Mauro Di Domenico wrote:
>>>>>>> Hi,
>>>>>>> I'm testing new b43 modules for my 14e4:4315 broadcom card.
>>>>>>> I've compiled and installed compat-wireless-2009-09-16 in a debian
>>>>>>> machine with kernel version 2.6.30-6.
>>>>>>>
>>>>>>> During the boot I experience this problem:
>>>>>>>
>>>>>>> $ dmesg|egrep "b43|ssb"
>>>>>>>
>>>>>>> [    2.384463] b43-pci-bridge 0000:06:00.0: PCI INT A -> GSI 17
>>>>>>> (level,
>>>>>>> low) -> IRQ 17
>>>>>>> [    2.384477] b43-pci-bridge 0000:06:00.0: setting latency timer
>>>>>>> to 64
>>>>>>> [    2.544344] ssb: Sonics Silicon Backplane found on PCI device
>>>>>>> 0000:06:00.0
>>>>>>> [    6.968981] b43: disagrees about version of symbol
>>>>>>> ssb_device_is_enabled
>>>>>>> [    6.968986] b43: Unknown symbol ssb_device_is_enabled
>>>>>>> [    6.969280] b43: Unknown symbol ssb_pmu_set_ldo_paref
>>>>>>> [    6.969407] b43: disagrees about version of symbol
>>>>>>> ssb_pcicore_dev_irqvecs_enable
>>>>>>> [    6.969410] b43: Unknown symbol ssb_pcicore_dev_irqvecs_enable
>>>>>>> .....
>>>>>>> ....
>>>>>>> ...
>>>>>>>
>>>>>> I faced the exactly same issue as Mauro did. +1 from me, but
>>>>>> currently
>>>>>> have
>>>>>> no time to take a deeper look.
>>>>>>
>>>>>> Thanks
>>>>> Hi,
>>>>>
>>>>> I had the same problem with the ssb module and compat-wireless in
>>>>> ubuntu
>>>>> 9.04. The problem is that the ssb module is integrated into the
>>>>> initramfs image. The version out of the initramfs image is loaded on
>>>>> startup and not the version of compat-wireless. Running "sudo
>>>>> update-initramfs -u" after installing compat-wireless and restaing the
>>>>> system fixes the problem for me. Either Debian/Ubuntu should remove
>>>>> ssb
>>>>> form default initramfs image or compat-wireless should update the
>>>>> image
>>>>> with the install command. At least the compat-wireless documentation
>>>>> needs an update.
>>>>>
>>>>> Hauke
>>>>>
>>>>> (adding Luis and linux-wireless list)
>>>> Tim, do you guys update the initramfs upon installation of lbm? If a
>>>> user does not use lbm and uses compat-wireless I suppose we need to do
>>>> something similar.
>>>>
>>>>  Luis
>>> No, initramfs is not updated when LBM is installed. I think maybe its
>>> a bug
>>> that ssb is in the initramfs modules list since AFAIK its not a boot
>>> essential device. Even in the netboot case, ssb/b44 should be in a udeb.
>>
>> That would make life much easier.
>>
>>   Luis
>>
> 
> I'm looking at the Karmic initramfs-tools package and am not seeing
> _any_ reference to ssb or b44.
> 
Hi Tim,

I have decompressed initrd.img-2.6.31-11-generic from karmic and
initrd.img-2.6.28-15-generic form jaunty. In both packages I found the
ssb.ko and b44.ko module.

Hauke


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 898 bytes --]

  parent reply	other threads:[~2009-09-26 15:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1253811559.4579.44.camel@pc3.dido>
     [not found] ` <4ABBAB47.8040300@canonical.com>
2009-09-24 18:33   ` A problem loading ssb module Hauke Mehrtens
2009-09-24 18:37     ` Luis R. Rodriguez
2009-09-25  0:04       ` Tim Gardner
2009-09-25  0:08         ` Luis R. Rodriguez
2009-09-25  0:14           ` Tim Gardner
2009-09-25  0:53             ` Luis R. Rodriguez
2009-09-26 15:15             ` Hauke Mehrtens [this message]
2009-09-27 15:15       ` Clyde McPherson
2009-09-27 19:50         ` Luis R. Rodriguez
2009-09-27 21:02           ` Luis R. Rodriguez
2009-09-28 19:55             ` Luis R. Rodriguez
2009-09-28 20:00             ` Tim Gardner
2009-09-28 20:07               ` Luis R. Rodriguez
2009-09-28 20:38                 ` Tim Gardner
2009-09-28 21:00                   ` Luis R. Rodriguez
2009-09-30 16:59                     ` Tim Gardner

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=4ABE3023.3020006@hauke-m.de \
    --to=hauke@hauke-m.de \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=bryan.wu@canonical.com \
    --cc=didomauro@tiscali.it \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    --cc=tim.gardner@canonical.com \
    /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;
as well as URLs for NNTP newsgroup(s).