Re: [Bug 182716] Re: bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentication with AP doesn't work.
On Sat, Aug 16, 2008 at 2:29 PM, Larry Finger <[EMAIL PROTECTED]> wrote: > I don't think that is a b43 problem. I don't use Gnome so I'm not sure > what is available, but under KDE, the wireless connection has an > "Autoconnect" button that needs to be checked when the connection is > edited. When that is done, the system will look to the wireless before > the wired interface. > > Is your wire plugged in? > > Larry > It used to autoconnect when I was using the bcm43xx driver, and once I kill and start NetworkManager it autoconnects. No, I don't have wireline connected. regards, Ben -- bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentication with AP doesn't work. https://bugs.launchpad.net/bugs/182716 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 182716] Re: bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentication with AP doesn't work.
Hi Larry, On Tue, Aug 12, 2008 at 7:28 AM, Larry Finger <[EMAIL PROTECTED]> wrote: > Ben, > > That is the one. My code assumed that you were running ssb and b43. You > have bcm43xx loaded. The new version is > > 014003002810204300800200021000189000B096D54F44309A1193FBA5FE3C003E000C0001B1 > > Try writing this one back to that location using the command > > sudo cp new_data $SPROM > > The essential difference has to do with Bluetooth coexistence. In the > original, there was a string "0D00" that has been changed to > "0C00" - that small difference should do the trick. Of course it > isn't quite this simple as the file needs to have a proper CRC. The last > two characters are the checksum that changed as well. > The b43 driver seems to be working now, but only after I restart NetworkManager. When ubuntu first boots, only the 'Wired Network' part of the GUI is visible. If I kill NetworkManager and start it, I'm connected to my AP. On the surface, this seems unrelated to the problem with b43, but maybe not? thanks, Ben -- bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentication with AP doesn't work. https://bugs.launchpad.net/bugs/182716 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 182716] Re: bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentication with AP doesn't work.
Hi Larry, Larry Finger wrote: > > For Ben Warren: > > Your device may have the same problem, but it is not one of the units > that is fixed by the patch. For you, we will need to try the SPROM patch > method. What I would like you to do enter the following commands in a > terminal: > > SPROM=$(find /sys/device -name ssb_sprom) > sudo cat $SPROM > sprom.dat > I didn't find that file, but how about this one: [EMAIL PROTECTED]:/sys/module/bcm43xx/drivers/pci:bcm43xx/:02:03.0$ sudo cat sprom 014003002810204300800200021000189000B096D54F44309A1193FBA5FE3C003E000D000185 regards, Ben -- bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentication with AP doesn't work. https://bugs.launchpad.net/bugs/182716 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 182716] Re: bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentication with AP doesn't work.
Larry Finger wrote: > In a terminal, please enter the command '/sbin/lspci -nnv' and post the > first two lines of the output for your BCM4306. > > 02:03.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03) Subsystem: Dell Wireless 1350 WLAN Mini-PCI Card [1028:0003] Flags: bus master, fast devsel, latency 32, IRQ 5 Memory at fafee000 (32-bit, non-prefetchable) [size=8K] > We have found a number of devices with the SPROM incorrectly coded. A > fix has been entered into both the Hardy and Intrepid code base, but the > above data will show if your card will be fixed. > > fingers crossed, Ben -- bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentication with AP doesn't work. https://bugs.launchpad.net/bugs/182716 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 182716] Re: bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentication with AP doesn't work.
Hi Larry, As requested: [EMAIL PROTECTED]:~$ dmesg | grep b43 [ 89.647611] b43-phy0: Broadcom 4306 WLAN found [ 89.695716] b43-phy0 debug: Found PHY: Analog 2, Type 2, Revision 2 [ 89.695773] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2 [ 318.416438] input: b43-phy0 as /devices/virtual/input/input9 [ 319.717479] b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02) [ 138.583575] b43-phy0 debug: !WARNING! Idle-TSSI phy->cur_idle_tssi measuring failed. (cur=37, tgt=62). Disabling TX power adjustment. [ 138.583727] b43-phy0 debug: Chip initialized [ 138.584244] b43-phy0 debug: 30-bit DMA initialized [ 138.585106] Registered led device: b43-phy0:tx [ 138.585155] Registered led device: b43-phy0:rx [ 138.585206] Registered led device: b43-phy0:radio [ 138.585308] b43-phy0 ERROR: PHY transmission error [ 138.585489] b43-phy0 debug: Wireless interface started [ 138.585503] b43-phy0 debug: Adding Interface type 2 [ 138.714058] b43-phy0 ERROR: PHY transmission error [ 138.714278] b43-phy0 ERROR: PHY transmission error [ 194.489854] b43-phy0 debug: Removing Interface type 2 [ 194.629854] b43-phy0 debug: Wireless interface stopped [ 194.630197] b43-phy0 debug: DMA-32 0x0200 (RX) max used slots: 1/64 [ 194.630336] b43-phy0 debug: DMA-32 0x02A0 (TX) max used slots: 0/128 [ 194.648528] b43-phy0 debug: DMA-32 0x0280 (TX) max used slots: 0/128 [ 194.667202] b43-phy0 debug: DMA-32 0x0260 (TX) max used slots: 0/128 [ 194.685859] b43-phy0 debug: DMA-32 0x0240 (TX) max used slots: 0/128 [ 194.704545] b43-phy0 debug: DMA-32 0x0220 (TX) max used slots: 2/128 [ 194.723189] b43-phy0 debug: DMA-32 0x0200 (TX) max used slots: 0/128 - I'd never used it before, but apparently this laptop has a radio enable/disable bound to Fn+F2. Toggling this function and reloading b43 doesn't seem to make a difference (same dmesg), so I don't know if the key combination is being detected correctly. Thanks for the background information. Of course I want to help to get b43 working rather than using a deprecated driver. regards, Ben -- bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentication with AP doesn't work. https://bugs.launchpad.net/bugs/182716 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 182716] Re: bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentication with AP doesn't work.
Just echoing what everybody else says, b43 doesn't seem to work. $ uname -a Linux pippin 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686 GNU/Linux version: Ubuntu 8.04 standard i386, up-to-date as of 7/6/2008 computer type: Dell D600 laptop, circa 2005 $lspci -vvv 02:03.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03) Subsystem: Dell Wireless 1350 WLAN Mini-PCI Card Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- I get it to work by $ sudo modprobe -r b43 $ sudo modprobe bcm43xx Note: blacklisting b43 and whitelisting bcm43xx doesn't work for me, I need to start the driver once the system is up and running. regards, Ben -- bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentication with AP doesn't work. https://bugs.launchpad.net/bugs/182716 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
