Re: BCM4312 (14e4:4315) in Lenovo Ideapad S12 cannot scan with 2.6.33

2010-03-16 Thread Marc Haber
Hi,

On Mon, Mar 15, 2010 at 07:41:02PM -0500, Larry Finger wrote:
 On 03/15/2010 06:20 PM, Marc Haber wrote:
  On Thu, Mar 04, 2010 at 06:54:23PM +0100, Marc Haber wrote:
  when the broadcom-sta driver didn't compile with 2.6.33 I decided to
  give b43 a new try. I have a Lenovo Ideapad S12, which has a BCM4312
  with LP Phy (14e4:4315). I am using Debian unstable.
 
  When I load the module, a new interface wlan0 appears, but iwlist scan
  says Interface doesn't support scanning. Looks like the device isn't
  properly initialized.
  
  The issue was that CRDA is not yet in Debian, and thus the kernel
  needs to have CONFIG_WIRELESS_OLD_REGULATORY=y. With this setting, the
  interface can scan. There should be a clearer error message about this.
 
 I feel that Debian should get their act together. The old regulatory method 
 was
 left in the kernel for several cycles so that the distros could adapt. Only
 Debian failed to do so.

Debian has a severe manpower problem in many fields.

  However, the interface doesn't work. Most prominent error is:
  Mar 15 18:27:12 feather kernel: [  505.012549] b43-phy0 ERROR: PHY 
  transmission error
  (this is with he chip forced to PIO).
 
 Are there lots of PHY Transmission errors, os just a few? We have never
 understood why these errors occur in the firmware.

grep ERROR: PHY syslog | wc -l
10

 What version are you using?

Mar 15 18:27:45 feather kernel: [  538.208462] b43-phy0: Loading firmware 
version 478.104 (2008-07-01 00:50:23)

I don't have the system in question at hand now and therefore cannot
check where the actual file is pulled from, but I clearly remember
building b43-firmwarecutter from the VCS and using it on the exact
version of the broadcom driver package mentioned in the instructions.

I'll check back later today, probably.

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: Suspend/hibernate broken in 2.6.33

2010-03-16 Thread Chris Vine
On Mon, 8 Mar 2010 17:22:26 +
Chris Vine ch...@cvine.freeserve.co.uk wrote:
 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:

[snip]

I am still getting this with kernel-2.6.33.1 and I have also managed to
reproduce a suspension writing to CMOS in a way which permanently
disables my wireless unless I reset the BIOS to its defaults.

This may not be the write mailing list to report this true.  If so,
what would be the correct one - the acpi list?

Chris


___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev