Comment 15 for bug 192720

Really? My laptop is still crashing loading both modules with kernel 2.6.24-16.

Some info about my device:
:~$ lspci -vvnn -s 02:02.0
02:02.0 Network controller [0280]: Broadcom Corporation BCM4303
802.11b Wireless LAN Controller [14e4:4301] (rev 02)
 Subsystem: Hewlett-Packard Company Unknown device [103c:12f3]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
 Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
 Latency: 64
 Interrupt: pin A routed to IRQ 17
 Region 0: Memory at e0104000 (32-bit, non-prefetchable) [size=8K]

:~$ uname -a
Linux mojo 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 2008
x86_64 GNU/Linux

Rodrigo

2008/4/14 toratora <email address hidden>:
> No more problem with kernel 2.6.24-16.
> Wifi works fine with my broadcom bcm4303 rev 02
>
> Thx
>
>
>
> --
> Loading b43legacy freezes computer
> https://bugs.launchpad.net/bugs/192720
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Source Package "linux" in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: linux-image-2.6.24-8-generic
>
> # lspci -vvnn -s 02:02.0
> 02:02.0 Network controller [0280]: Broadcom Corporation BCM4303 802.11b Wireless LAN Controller [14e4:4301] (rev 02)
> Subsystem: Hewlett-Packard Company Unknown device [103c:12f3]
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 64
> Interrupt: pin A routed to IRQ 19
> Region 0: Memory at e8100000 (32-bit, non-prefetchable) [size=8K]
>
> # uname -a
> Linux pavilion 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 GNU/Linux
>
> # cat /etc/issue
> Ubuntu hardy (development branch) \n \l
>
> Loading the b43legacy driver causes a hard lockup. Magic-sysreq-key doesn't work, I have to power cycle.
> I already tried removing the firmware to see if the lockup is related to the firmware, but loading the driver still causes a crash, even when there's no firmware to load :)
>
> Loading the b43 (no legacy driver) has no effect at all (as expected).
>
> According to http://linuxwireless.org/en/users/Drivers/b43
> b43legacy is the right driver to use.
>