Re: b43 problems on ubuntu gutsy. Using 2.6.24
On Friday 08 February 2008 07:45:37 Brian Lavender wrote: I downloaded the 2.6.24 kernel onto ubuntu gutsy, compiled it, installed the firmware, but I can't seem to make a connection. The bmc43xx driver seems to work, but disconnects for some reason. I noticed that while trying to set the WEP encryption key, I kept noticing it change on me. I don't know if it was something in my Ubuntu setup that was doing it. I am trying to access a 802-11b access point and I noticed the iwconfig keeps saying 802-11g. Not sure what the problem is. Here is dmesg and iwconfig output. You are using the wrong firmware version. -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Problems with BCM4306
Hi every one. Since i have upgraded my Ubuntu to the lateste Hardy version of yesterday, i cannot use my PCMCIA BEWAN Wi-Fi card... Before, it worked very good with bcm43xx-fwcutter, but now... lspci says : Broadcom Corporation BCM4306 I've tried to use http://linuxwireless.org/en/users/Drivers/b43#supported tutorial but no result... lshw -C network says *-network description: Network controller product: BCM4306 802.11b/g Wireless LAN Controller vendor: Broadcom Corporation physical id: 0 bus info: [EMAIL PROTECTED]:03:00.0 version: 03 width: 32 bits clock: 33MHz capabilities: bus_master configuration: driver=b43-pci-bridge latency=64 module=ssb *-network DISABLED description: Wireless interface physical id: 3 logical name: wlan0_rename serial: 00:0e:8e:03:22:13 capabilities: ethernet physical wireless configuration: broadcast=yes multicast=yes wireless=IEEE 802.11g And dmesg says : [ 118.782933] b43-phy0 ERROR: Firmware file b43/ucode5.fw not found or load failed. [ 118.782943] b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the correct firmware (version 4). Can someone help me, please ? Guillaume Créez votre adresse électronique [EMAIL PROTECTED] 1 Go d'espace de stockage, anti-spam et anti-virus intégrés. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Problems with BCM4306
On Friday 08 February 2008 17:17:10 Guillaume wrote: Stefano Brivio a écrit : Sure. You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the correct firmware (version 4). Does this ring a bell? OK ; it's done and it work :-P I have made a mistake because the two diods of my card are no longer lighted... Enable LED trigger support in the kernel. If you have b43 builtin, LED triggers must also be builtin. -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
[PATCH] b43: Add driver load messages
This adds printk messages with basic information about the driver being loaded.
This information includes a summary of the compiled-in features, which
simplifies bug-reporting and debugging a lot.
Also a firmware ID is printed. This is a unique identifier blob for a specific
version of the firmware. This ID is attached to a specific version of the
firmware
blob in b43-fwcutter (see fwcutter git).
This helps users to select the right firmware for their device.
This also makes it possible to use automated scripts to fetch and extract the
right
firmware for the driver. (the script will grep the .ko for the Firmware-ID:
xxx string.
While the driver might still support other versions of the firmware for backward
compatibility, this will always print out the officially supported version,
which
people _should_ use.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
---
John, as this has a negative chance of introducing regressions, I'd like
to have it in 2.6.25, even if it's not strictly a bugfix.
Stefano, we should port this to legacy. See fwcutter git for the ID I assigned
to the legacy firmware blob.
Index: wireless-2.6/drivers/net/wireless/b43/b43.h
===
--- wireless-2.6.orig/drivers/net/wireless/b43/b43.h2008-02-08
23:28:23.0 +0100
+++ wireless-2.6/drivers/net/wireless/b43/b43.h 2008-02-09 00:05:57.0
+0100
@@ -11,12 +11,18 @@
#include debugfs.h
#include leds.h
#include rfkill.h
#include lo.h
#include phy.h
+
+/* The unique identifier of the firmware that's officially supported by
+ * this driver version. */
+#define B43_SUPPORTED_FIRMWARE_ID FW13
+
+
#ifdef CONFIG_B43_DEBUG
# define B43_DEBUG 1
#else
# define B43_DEBUG 0
#endif
Index: wireless-2.6/drivers/net/wireless/b43/main.c
===
--- wireless-2.6.orig/drivers/net/wireless/b43/main.c 2008-02-08
23:28:23.0 +0100
+++ wireless-2.6/drivers/net/wireless/b43/main.c2008-02-09
00:17:12.0 +0100
@@ -4190,23 +4190,51 @@ static struct ssb_driver b43_ssb_driver
.probe = b43_probe,
.remove = b43_remove,
.suspend= b43_suspend,
.resume = b43_resume,
};
+static void b43_print_driverinfo(void)
+{
+ const char *feat_pci = , *feat_pcmcia = , *feat_nphy = ,
+ *feat_leds = , *feat_rfkill = ;
+
+#ifdef CONFIG_B43_PCI_AUTOSELECT
+ feat_pci = P;
+#endif
+#ifdef CONFIG_B43_PCMCIA
+ feat_pcmcia = M;
+#endif
+#ifdef CONFIG_B43_NPHY
+ feat_nphy = N;
+#endif
+#ifdef CONFIG_B43_LEDS
+ feat_leds = L;
+#endif
+#ifdef CONFIG_B43_RFKILL
+ feat_rfkill = R;
+#endif
+ printk(KERN_INFO Broadcom 43xx driver loaded
+ [ Features: %s%s%s%s%s, Firmware-ID:
+ B43_SUPPORTED_FIRMWARE_ID ]\n,
+ feat_pci, feat_pcmcia, feat_nphy,
+ feat_leds, feat_rfkill);
+}
+
static int __init b43_init(void)
{
int err;
b43_debugfs_init();
err = b43_pcmcia_init();
if (err)
goto err_dfs_exit;
err = ssb_driver_register(b43_ssb_driver);
if (err)
goto err_pcmcia_exit;
+ b43_print_driverinfo();
return err;
err_pcmcia_exit:
b43_pcmcia_exit();
err_dfs_exit:
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Problems with BCM4306
Stefano Brivio a écrit : Sure. You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the correct firmware (version 4). Does this ring a bell? OK ; it's done and it work :-P I have made a mistake because the two diods of my card are no longer lighted... Guillaume -- Mail garanti 0% Microsoft, envoyé sous Ubuntu Hardy Pourquoi payer des logiciels inutiles en achetant un ordinateur ? http://www.racketiciel.info http://www.detaxe.org ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Problems with BCM4306
On Fri, 8 Feb 2008 16:41:59 +0100 (CET) bou.gui [EMAIL PROTECTED] wrote: And dmesg says : [ 118.782933] b43-phy0 ERROR: Firmware file b43/ucode5.fw not found or load failed. [ 118.782943] b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the correct firmware (version 4). Can someone help me, please ? Sure. You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the correct firmware (version 4). Does this ring a bell? -- Ciao Stefano ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: BCM94311MCG Rev 2 connects then drops on HP DV6605/ AMD64 X2
glenn greenfield wrote: eth0: no link during initialization. NET: Registered protocol family 10 lo: Disabled Privacy Extensions ADDRCONF(NETDEV_UP): eth0: link is not ready ADDRCONF(NETDEV_UP): wlan0: link is not ready lp: driver loaded but no devices found ppdev: user-space parallel port driver wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:12:17:2f:bb:b6 wlan0: RX authentication from 00:12:17:2f:bb:b6 (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:12:17:2f:bb:b6 wlan0: RX AssocResp from 00:12:17:2f:bb:b6 (capab=0x411 status=0 aid=2) wlan0: associated wlan0: CTS protection enabled (BSSID=00:12:17:2f:bb:b6) wlan0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0 wlan0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0 wlan0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30 wlan0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15 ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Clocksource tsc unstable (delta = -158243821 ns) wlan0: no IPv6 routers present b43-phy0 debug: Removing Interface type 2 b43-phy0 debug: Wireless interface stopped b43-phy0 debug: DMA-64 0x0200 (RX) max used slots: 1/64 b43-phy0 debug: DMA-64 0x0340 (TX) max used slots: 0/128 b43-phy0 debug: DMA-64 0x0300 (TX) max used slots: 0/128 b43-phy0 debug: DMA-64 0x02C0 (TX) max used slots: 0/128 b43-phy0 debug: DMA-64 0x0280 (TX) max used slots: 0/128 b43-phy0 debug: DMA-64 0x0240 (TX) max used slots: 4/128 b43-phy0 debug: DMA-64 0x0200 (TX) max used slots: 0/128 input: b43-phy0 as /devices/virtual/input/input10 b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02) b43-phy0 debug: Chip initialized b43-phy0 debug: 64-bit DMA initialized Registered led device: b43-phy0:tx Registered led device: b43-phy0:rx Registered led device: b43-phy0:radio b43-phy0 debug: Wireless interface started b43-phy0 debug: Adding Interface type 2 ADDRCONF(NETDEV_UP): wlan0: link is not ready eth0: no link during initialization. ADDRCONF(NETDEV_UP): eth0: link is not ready wlan0: CTS protection enabled (BSSID=00:12:17:2f:bb:b6) wlan0: RX deauthentication from 00:12:17:2f:bb:b6 (reason=16) wlan0: deauthenticated wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:12:17:2f:bb:b6 wlan0: RX deauthentication from 00:12:17:2f:bb:b6 (reason=6) wlan0: RX authentication from 00:12:17:2f:bb:b6 (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:12:17:2f:bb:b6 wlan0: RX AssocResp from 00:12:17:2f:bb:b6 (capab=0x411 status=0 aid=2) wlan0: associated wlan0: CTS protection enabled (BSSID=00:12:17:2f:bb:b6) wlan0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0 wlan0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0 wlan0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30 wlan0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15 ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready wlan0: no IPv6 routers present nvidia: module license 'NVIDIA' taints kernel. ACPI: PCI Interrupt Link [LGPU] enabled at IRQ 16 ACPI: PCI Interrupt :00:12.0[A] - Link [LGPU] - GSI 16 (level, low) - IRQ 16 PCI: Setting latency timer of device :00:12.0 to 64 NVRM: loading NVIDIA UNIX x86_64 Kernel Module 169.09 Fri Jan 11 14:04:37 PST 2008 b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error printk: 9 messages suppressed. b43-phy0 ERROR: PHY transmission error printk: 9 messages suppressed. b43-phy0 ERROR: PHY transmission error printk: 3 messages suppressed. b43-phy0 ERROR: PHY transmission error printk: 2 messages suppressed. b43-phy0 ERROR: PHY transmission error printk: 5 messages suppressed. b43-phy0 ERROR: PHY transmission error printk: 3 messages suppressed. b43-phy0 ERROR: PHY transmission error printk: 2 messages suppressed. b43-phy0 ERROR: PHY transmission error printk: 1 messages suppressed. b43-phy0 ERROR: PHY transmission error printk: 2 messages suppressed. b43-phy0 ERROR: PHY transmission error printk: 5 messages suppressed. b43-phy0 ERROR: PHY transmission error printk: 2 messages suppressed. b43-phy0 ERROR: PHY transmission error Perhaps I have the wrong firmware? I used what was in Debian on my first attempts but it seems that version is outdated or just incorrect for my wireless card. So I tried this: wget http://mirror2.openwrt.org/sources/broadcom-wl-4.150.10.5.tar.bz2 tar xjvf broadcom-wl-4.150.10.5.tar.bz2 cd broadcom-wl-4.150.10.5 b43-fwcutter -w /lib/firmware driver/wl_apsta_mimo.o Sorry, the
[PATCH] b43legacy: Add driver load messages
This adds printk messages with basic information about the driver being loaded.
This information includes a summary of the compiled-in features, which
simplifies bug-reporting and debugging a lot.
Also a firmware ID is printed. This is a unique identifier blob for a specific
version of the firmware. This ID is attached to a specific version of the
firmware
blob in b43-fwcutter (see fwcutter git).
This helps users to select the right firmware for their device.
This also makes it possible to use automated scripts to fetch and extract the
right
firmware for the driver. (The script will grep the .ko for the Firmware-ID:
xxx string.)
While the driver might still support other versions of the firmware for backward
compatibility, this will always print out the officially supported version,
which
people _should_ use.
Signed-off-by: Stefano Brivio [EMAIL PROTECTED]
---
Index: wireless-2.6/drivers/net/wireless/b43legacy/b43legacy.h
===
--- wireless-2.6.orig/drivers/net/wireless/b43legacy/b43legacy.h
+++ wireless-2.6/drivers/net/wireless/b43legacy/b43legacy.h
@@ -23,6 +23,10 @@
#include phy.h
+/* The unique identifier of the firmware that's officially supported by this
+ * driver version. */
+#define B43legacy_SUPPORTED_FIRMWARE_IDFW10
+
#define B43legacy_IRQWAIT_MAX_RETRIES 20
#define B43legacy_RX_MAX_SSI 60 /* best guess at max ssi */
Index: wireless-2.6/drivers/net/wireless/b43legacy/main.c
===
--- wireless-2.6.orig/drivers/net/wireless/b43legacy/main.c
+++ wireless-2.6/drivers/net/wireless/b43legacy/main.c
@@ -3,7 +3,7 @@
* Broadcom B43legacy wireless driver
*
* Copyright (c) 2005 Martin Langer [EMAIL PROTECTED]
- * Copyright (c) 2005-2007 Stefano Brivio [EMAIL PROTECTED]
+ * Copyright (c) 2005-2008 Stefano Brivio [EMAIL PROTECTED]
* Copyright (c) 2005, 2006 Michael Buesch [EMAIL PROTECTED]
* Copyright (c) 2005 Danny van Dyk [EMAIL PROTECTED]
* Copyright (c) 2005 Andreas Jaggi [EMAIL PROTECTED]
@@ -3847,6 +3847,32 @@ static struct ssb_driver b43legacy_ssb_d
.resume = b43legacy_resume,
};
+static void b43legacy_print_driverinfo(void)
+{
+ const char *feat_pci = , *feat_leds = , *feat_rfkill = ,
+ *feat_pio = , *feat_dma = ;
+
+#ifdef CONFIG_B43LEGACY_PCI_AUTOSELECT
+ feat_pci = P;
+#endif
+#ifdef CONFIG_B43LEGACY_LEDS
+ feat_leds = L;
+#endif
+#ifdef CONFIG_B43LEGACY_RFKILL
+ feat_rfkill = R;
+#endif
+#ifdef CONFIG_B43LEGACY_PIO
+ feat_pio = I;
+#endif
+#ifdef CONFIG_B43LEGACY_DMA
+ feat_dma = D;
+#endif
+ printk(KERN_INFO Broadcom 43xx driver loaded
+ [ Features: %s%s%s%s%s, Firmware-ID:
+ B43legacy_SUPPORTED_FIRMWARE_ID ]\n,
+ feat_pci, feat_leds, feat_rfkill, feat_pio, feat_dma);
+}
+
static int __init b43legacy_init(void)
{
int err;
@@ -3857,6 +3883,8 @@ static int __init b43legacy_init(void)
if (err)
goto err_dfs_exit;
+ b43legacy_print_driverinfo();
+
return err;
err_dfs_exit:
--
Ciao
Stefano
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [PATCH] b43: Add driver load messages
Am Samstag 09 Februar 2008 schrieb Michael Buesch:
+static void b43_print_driverinfo(void)
+{
+ const char *feat_pci = , *feat_pcmcia = , *feat_nphy = ,
+*feat_leds = , *feat_rfkill = ;
+
+#ifdef CONFIG_B43_PCI_AUTOSELECT
+ feat_pci = P;
+#endif
+#ifdef CONFIG_B43_PCMCIA
+ feat_pcmcia = M;
+#endif
+#ifdef CONFIG_B43_NPHY
+ feat_nphy = N;
+#endif
+#ifdef CONFIG_B43_LEDS
+ feat_leds = L;
+#endif
+#ifdef CONFIG_B43_RFKILL
+ feat_rfkill = R;
+#endif
+ printk(KERN_INFO Broadcom 43xx driver loaded
+[ Features: %s%s%s%s%s, Firmware-ID:
+B43_SUPPORTED_FIRMWARE_ID ]\n,
+feat_pci, feat_pcmcia, feat_nphy,
+feat_leds, feat_rfkill);
This has the disadvantage that you have to load the driver to see that it
fails, then unload it, boot a working kernel (if WLAN is the only connection
method), download the right firmware, reboot the wanted kernel.
This would be shorter if this information can be presented in the output
of 'modinfo /lib/modules/2.6.??/kernel/drivers/net/wireless/b43/b43.ko'
HS
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
