* Re: broadcom 4306 rev. 3 uses b43 instead of b43legacy [not found] <30761.30943.qm@web52411.mail.re2.yahoo.com> @ 2008-07-30 15:26 ` Larry Finger 0 siblings, 0 replies; 4+ messages in thread From: Larry Finger @ 2008-07-30 15:26 UTC (permalink / raw) To: rschneiderman; +Cc: wireless Richard Schneiderman wrote: > Larry, > Thanks for the reply. Ok, I read the documentation again. It does say that the b43 driver is for my chipset > > The problem I'm having is that that while I can see my wireless connection (using iwlist wlan0 scan), I can't connect to it. In iwconfig with Suse, it doesn't show the access point. In iwconfig in Ubuntu, I get the AP shown but still can't get a dhcp connection. > > This card worked fine in Suse 10.2, 10.3 and Ubuntu 7.10. What do you think my step in resolving this may be? > > If this needs to into the listserv, i'll resend it there. In general, this type of mail should be sent to linux-wireless. Are you trying to use the traditional method with ifup, or are you using NetworkManager? Have you configured the card with YaST? Larry ^ permalink raw reply [flat|nested] 4+ messages in thread
* broadcom 4306 rev. 3 uses b43 instead of b43legacy
@ 2008-07-30 4:07 Richard Schneiderman
2008-07-30 4:31 ` Pavel Roskin
2008-07-30 7:53 ` Holger Schurig
0 siblings, 2 replies; 4+ messages in thread
From: Richard Schneiderman @ 2008-07-30 4:07 UTC (permalink / raw)
To: linux-wireless
Is this known bug? I can see my wireless network using wlist wlan0 scan.
How do I make it use the b43legacy instead of b43. I'm using opensuse 11 and have compiled the latest code and it is still not working.
This worked BTW, in 10.2 and 10.3 with no problems and the card is currently working in vista (ugh).
Thank you from your time.
Richard Schneiderman
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: broadcom 4306 rev. 3 uses b43 instead of b43legacy 2008-07-30 4:07 Richard Schneiderman @ 2008-07-30 4:31 ` Pavel Roskin 2008-07-30 7:53 ` Holger Schurig 1 sibling, 0 replies; 4+ messages in thread From: Pavel Roskin @ 2008-07-30 4:31 UTC (permalink / raw) To: rschneiderman; +Cc: linux-wireless Quoting Richard Schneiderman <rschneiderman@yahoo.com>: > Is this known bug? I can see my wireless network using wlist wlan0 scan. It's not a bug. It's meant to be this way. > How do I make it use the b43legacy instead of b43. I'm using > opensuse 11 and have compiled the latest code and it is still not > working. It should work with b43. If it doesn't work for you, please report it as a bug. -- Regards, Pavel Roskin ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: broadcom 4306 rev. 3 uses b43 instead of b43legacy 2008-07-30 4:07 Richard Schneiderman 2008-07-30 4:31 ` Pavel Roskin @ 2008-07-30 7:53 ` Holger Schurig 1 sibling, 0 replies; 4+ messages in thread From: Holger Schurig @ 2008-07-30 7:53 UTC (permalink / raw) To: linux-wireless, rschneiderman > Is this known bug? I can see my wireless network using wlist > wlan0 scan. This card (which seems to be a 4306 rev 3 like yours), works for me: 03:00.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03) Subsystem: Melco Inc Unknown device [1154:0324] Flags: bus master, fast devsel, latency 64, IRQ 11 Memory at 5c000000 (32-bit, non-prefetchable) [size=8K] I'm currently associated via WPA2 to an AP. Inserting the card: pccard: CardBus card inserted into slot 0 b43-pci-bridge 0000:03:00.0: enabling device (0000 -> 0002) ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11 PCI: Setting latency timer of device 0000:03:00.0 to 64 ssb: Sonics Silicon Backplane found on PCI device 0000:03:00.0 b43-phy0: Broadcom 4306 WLAN found phy0: Selected rate control algorithm 'pid' Broadcom 43xx driver loaded [ Features: PML, Firmware-ID: FW13 ] Associating: firmware: requesting b43/ucode5.fw firmware: requesting b43/pcm5.fw firmware: requesting b43/b0g0initvals5.fw firmware: requesting b43/b0g0bsinitvals5.fw b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) Registered led device: b43-phy0::tx Registered led device: b43-phy0::rx phy0: HW CONFIG: freq=2412 phy0: HW CONFIG: freq=2412 phy0: HW CONFIG: freq=2417 phy0: HW CONFIG: freq=2422 phy0: HW CONFIG: freq=2427 phy0: HW CONFIG: freq=2432 phy0: HW CONFIG: freq=2437 phy0: HW CONFIG: freq=2442 phy0: HW CONFIG: freq=2447 phy0: HW CONFIG: freq=2452 phy0: HW CONFIG: freq=2457 phy0: HW CONFIG: freq=2462 phy0: HW CONFIG: freq=2412 phy0: HW CONFIG: freq=2437 phy0: HW CONFIG: freq=2437 eth1: authenticate with AP 00:13:19:80:da:30 eth1: authenticated eth1: associate with AP 00:13:19:80:da:30 eth1: RX AssocResp from 00:13:19:80:da:30 (capab=0x11 status=0 aid=2) eth1: associated phy0: Allocated STA 00:13:19:80:da:30 phy0: Inserted STA 00:13:19:80:da:30 eth1: switched to short barker preamble (BSSID=00:13:19:80:da:30) eth1: switched to long barker preamble (BSSID=00:13:19:80:da:30) > How do I make it use the b43legacy This is for a different card / firmware. Please refer to http://wireless.kernel.org/en/users/Drivers/b43 for more information. There's a section there "bcm43xx, b43legacy, b43, softmac,... the full story". b43legacy won't solve your problem. > I'm using opensuse 11 and have compiled the latest code and it > is still not working. This worked BTW, in 10.2 and 10.3 with no > problems and the card is currently working in vista (ugh). Then it's a SuSE-Problem and you should ask your vendor. However, you wrote "I compiled latest code" without specifing what "latest" is. I'm using almost-latest-code (tm), e.g. I used for my test wireless-testing, git describe "v2.6.26-rc9-14207-ga520bdb". ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-07-30 15:26 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <30761.30943.qm@web52411.mail.re2.yahoo.com>
2008-07-30 15:26 ` broadcom 4306 rev. 3 uses b43 instead of b43legacy Larry Finger
2008-07-30 4:07 Richard Schneiderman
2008-07-30 4:31 ` Pavel Roskin
2008-07-30 7:53 ` Holger Schurig
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).