Re: BCM4312 (14e4:4315) in Lenovo Ideapad S12 cannot scan with 2.6.33
Hi Larry, On Sat, Mar 06, 2010 at 07:57:57AM -0600, Larry Finger wrote: On 03/06/2010 04:07 AM, Marc Haber wrote: On Fri, Mar 05, 2010 at 05:54:24PM +, Chris Vine wrote: You can get the Ideapad to work by forcing use of the PIO however. How exactly do I do this? I remember trying by adding some options to /etc/modprobe.d/b43, but the module didn't seem to understand this. I don't have the ideapad at hand at the moment, so I cannot look, but I can try tonight. Unless you are getting the DMA error, choosing PIO will not help. If you are getting that error, it will say so in the dmesg output. I have looked again, and the fatal DMA error is indeed there. It suggested setting CONFIG_B43_FORCE_PIO=y, which I did despite of the very clear warnings given in the make menuconfig help. However, the DMA error has vanished, but my B43 still says that the interface doesn't support scanning. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190 ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: BCM4312 (14e4:4315) in Lenovo Ideapad S12 cannot scan with 2.6.33
On Mon, Mar 8, 2010 at 11:28 AM, Marc Haber mh+bcm43xx-...@zugschlus.de wrote: Hi Larry, On Sat, Mar 06, 2010 at 07:57:57AM -0600, Larry Finger wrote: On 03/06/2010 04:07 AM, Marc Haber wrote: On Fri, Mar 05, 2010 at 05:54:24PM +, Chris Vine wrote: You can get the Ideapad to work by forcing use of the PIO however. How exactly do I do this? I remember trying by adding some options to /etc/modprobe.d/b43, but the module didn't seem to understand this. I don't have the ideapad at hand at the moment, so I cannot look, but I can try tonight. Unless you are getting the DMA error, choosing PIO will not help. If you are getting that error, it will say so in the dmesg output. I have looked again, and the fatal DMA error is indeed there. It suggested setting CONFIG_B43_FORCE_PIO=y, which I did despite of the very clear warnings given in the make menuconfig help. However, the DMA error has vanished, but my B43 still says that the interface doesn't support scanning. That message sounds like you are using iwlist to scan - try iw instead. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things. Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190 ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: BCM4312 (14e4:4315) in Lenovo Ideapad S12 cannot scan with 2.6.33
2010/3/8 Marc Haber mh+bcm43xx-d...@zugschlus.de: Hi, On Mon, Mar 08, 2010 at 12:54:44PM +0100, Gábor Stefanik wrote: That message sounds like you are using iwlist to scan - try iw instead. Yes, I am using iwlist. Has this changed? Have the tools like wicd and/or network-manager already adapted to use the new tools/API? AFAIK not, but iw gives more meaningful error messages in case of a failure. On the box that I am currently using (which has a ipw2200, oh wonderful old times), iw list returns nl80211 not found. Which option is my kernel missing? Probably nothing - rather, your libnl is too old (older than 1.0-pre8). However, you can't use iw with ipw2200 - it only supports drivers that use cfg80211. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things. Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190 -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Suspend/hibernate broken in 2.6.33
I have noticed that although my BCM4312 802.11b/g [14e4:4315] wireless device works using the PIO option in 2.6.33, it breaks after a suspend or hibernate. Attempts to bring up the wlan0 interface with 'ifconfig wlan0 up' after suspension or hibernation results in the following message (although nothing is revealed by dmesg): SIOCSIFFLAGS: Unknown error 132 If I unload all wireless and related modules before suspending or hibernating, and then reload them on resuming, I get more information from dmesg, namely that it thinks that the wireless has been turned off by the rfkill button, which it definitely has not: * Restarting tasks ... done. cfg80211: Using static regulatory domain info cfg80211: Regulatory domain: 00 (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2000 mBm) (2457000 KHz - 2482000 KHz @ 2 KHz), (600 mBi, 2000 mBm) (2474000 KHz - 2494000 KHz @ 2 KHz), (600 mBi, 2000 mBm) (517 KHz - 525 KHz @ 4 KHz), (600 mBi, 2000 mBm) (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 2000 mBm) cfg80211: Calling CRDA to update world regulatory domain b43-pci-bridge :03:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 b43-pci-bridge :03:00.0: setting latency timer to 64 ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x16, vendor 0x4243) ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0F, vendor 0x4243) ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x0A, vendor 0x4243) ssb: Core 3 found: PCI-E (cc 0x820, rev 0x09, vendor 0x4243) ssb: Sonics Silicon Backplane found on PCI device :03:00.0 b43-phy0: Broadcom 4312 WLAN found (core revision 15) b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 1 b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 2 phy0: Selected rate control algorithm 'minstrel' Registered led device: b43-phy0::tx Registered led device: b43-phy0::rx Registered led device: b43-phy0::radio Broadcom 43xx driver loaded [ Features: PMLS, Firmware-ID: FW13 ] b43 ssb0:0: firmware: requesting b43/ucode15.fw b43 ssb0:0: firmware: requesting b43/lp0initvals15.fw b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) b43-phy0 debug: b2062: Using crystal tab entry 19200 kHz. b43-phy0 debug: Chip initialized b43-phy0 debug: PIO initialized b43-phy0 debug: QoS enabled b43-phy0 debug: Wireless interface started b43-phy0 debug: Adding Interface type 2 b43-phy0: Radio hardware status changed to DISABLED b43-phy0: Radio turned on by software b43-phy0: The hardware RF-kill button still turns the radio physically off. Press the button to turn it on. b43-phy0 debug: Removing Interface type 2 b43-phy0 debug: Wireless interface stopped * The first time this happened I got very alarmed because although a reboot into 2.6.33 would work (until there was another suspension or hibernation) rebooting into 2.6.32 or earlier kernels would not - it thought that the radio had been switched off at the outset. It appears that suspension had done something nasty to my CMOS and I had to restore all defaults in the BIOS to get it to come on again in 2.6.32 and less. (I have not been able to reproduce this again since but beware if testing this out.) This does not seem to be b43 specific, as I get exactly the same effect using the broadcom wl driver. Suspension works in kernel 2.6.32 and below, but not with kernel 2.6.33. Chris ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
