Larry Finger <Larry.Finger@...> writes:
>
> Markus wrote:
> > Hello,
> >
> >
> > after MacOSX Airport firmware update 5.10.38.35
> >
> > (bcm43xx/ Macbook Core2Duo SR)
> >
> > I cannot connect to my Wlan-Router anymore.
> >
> >
> > The b43-module gets modprobed without errors
> >
> > and nm-applet shows my Access-Points SSID.
> >
> > Alas, it won't establish a connection to it.
> >
> >
> > Any clues?
>
> Please post all items in dmesg that pertain to ssb or b43 using
>
> dmesg | egrep "ssb|b43"
>
> Larry
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@...
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--------------------------
dmesg | egrep "ssb|b43"
[ 101.205300] b43-pci-bridge 0000:02:00.0: PCI
INT A -> GSI 16 (level, low) -> IRQ 16
[ 101.205322] b43-pci-bridge 0000:02:00.0: setting
latency timer to 64
[ 101.272313] ssb: Sonics Silicon Backplane found
on PCI device 0000:02:00.0
----------------
lspci | egrep BCM
02:00.0 Network controller: Broadcom Corporation
BCM4328 802.11a/b/g/n (rev 03)
---------------------------
BTW I don't know if the b43 official Kernel Module ever worked
with my WIFI Controller. I'm using Ubuntu and as with kernel
2.28 I could enable the proprietary Broadcom Driver via
the "Restricted Drivers Manager". And that Driver doesn't seem
to work now anymore.
The above command outputs are nevertheless produced using
Kernel 2.6.30 and the official b43 module.
Is my BCM-Chip supported by the official driver anyway?
iwconfig can't find a wireless-supporting device either.
Only eth0, loopback and the (fw-controller?)
The proprietary driver lists eth1 in addition to that.
Markus wrote:
> Larry Finger <Larry.Finger@...> writes:
>
>> Markus wrote:
>>> Hello,
>>>
>>>
>>> after MacOSX Airport firmware update 5.10.38.35
>>>
>>> (bcm43xx/ Macbook Core2Duo SR)
>>>
>>> I cannot connect to my Wlan-Router anymore.
>>>
>>>
>>> The b43-module gets modprobed without errors
>>>
>>> and nm-applet shows my Access-Points SSID.
>>>
>>> Alas, it won't establish a connection to it.
>>>
>>>
>>> Any clues?
>> Please post all items in dmesg that pertain to ssb or b43 using
>>
>> dmesg | egrep "ssb|b43"
>>
>> Larry
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to majordomo@...
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
> --------------------------
>
> dmesg | egrep "ssb|b43"
>
>
> [ 101.205300] b43-pci-bridge 0000:02:00.0: PCI
> INT A -> GSI 16 (level, low) -> IRQ 16
>
> [ 101.205322] b43-pci-bridge 0000:02:00.0: setting
> latency timer to 64
>
> [ 101.272313] ssb: Sonics Silicon Backplane found
> on PCI device 0000:02:00.0
>
>
> ----------------
>
> lspci | egrep BCM
>
>
> 02:00.0 Network controller: Broadcom Corporation
> BCM4328 802.11a/b/g/n (rev 03)
>
>
> ---------------------------
>
> BTW I don't know if the b43 official Kernel Module ever worked
>
> with my WIFI Controller. I'm using Ubuntu and as with kernel
>
> 2.28 I could enable the proprietary Broadcom Driver via
>
> the "Restricted Drivers Manager". And that Driver doesn't seem
>
> to work now anymore.
>
>
>
> The above command outputs are nevertheless produced using
> Kernel 2.6.30 and the official b43 module.
>
> Is my BCM-Chip supported by the official driver anyway?
>
>
>
> iwconfig can't find a wireless-supporting device either.
>
> Only eth0, loopback and the (fw-controller?)
>
> The proprietary driver lists eth1 in addition to that.
As it says in the wiki, an interface with the 0x4328 ID is not
supported. You need to use the Broadcom wl driver, which is
proprietary. I suppose that this was the "Restricted Driver" from
Ubuntu. Your other option would be to get the driver from Broadcom and
build it on your system.
We are in the process of doing the reverse engineering on the N-PHY
devices, but it does not have high priority at the moment.
Larry