Re: BCM94311MCG
yes the radio switcher was on...here there are new informations after upgrading the kernel,i tried first with NetworkManager and then with System-Administration-Network and then activating interface : b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02) Registered led device: b43-phy0:tx Registered led device: b43-phy0:rx b43-phy0 debug: Chip initialized b43-phy0 debug: 32-bit DMA initialized input: Unspecified device as /class/input/input10 b43-phy0 debug: Wireless interface started b43-phy0 debug: Adding Interface type 2 ADDRCONF(NETDEV_UP): wlan0: link is not ready [drm] Initialized drm 1.1.0 20060810 [drm] Initialized i915 1.6.0 20060119 on minor 0 wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authentication with AP 00:0c:41:19:2d:c1 timed out wlan0: authentication frame received from 00:0c:41:19:2d:c1, but not in authenticate state - ignored wlan0: authentication frame received from 00:0c:41:19:2d:c1, but not in authenticate state - ignored wlan0: authentication frame received from 00:0c:41:19:2d:c1, but not in authenticate state - ignored wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authentication with AP 00:0c:41:19:2d:c1 timed out wlan0: authentication frame received from 00:0c:41:19:2d:c1, but not in authenticate state - ignored wlan0: authentication frame received from 00:0c:41:19:2d:c1, but not in authenticate state - ignored wlan0: authentication frame received from 00:0c:41:19:2d:c1, but not in authenticate state - ignored wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: RX authentication from 00:0c:41:19:2d:c1 (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:0c:41:19:2d:c1 wlan0: associate with AP 00:0c:41:19:2d:c1 wlan0: authentication frame received from 00:0c:41:19:2d:c1, but not in authenticate state - ignored wlan0: authentication frame received from 00:0c:41:19:2d:c1, but not in authenticate state - ignored wlan0: RX AssocResp from 00:0c:41:19:2d:c1 (capab=0x1 status=0 aid=2) wlan0: associated ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready wlan0: disassociate(reason=3) wlan0: association frame received from 00:0c:41:19:2d:c1, but not in associate state - ignored wlan0: RX deauthentication from 00:0c:41:19:2d:c1 (reason=6) wlan0: deauthenticated wlan0: RX deauthentication from 00:0c:41:19:2d:c1 (reason=6) wlan0: RX deauthentication from 00:0c:41:19:2d:c1 (reason=6) wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: RX authentication from 00:0c:41:19:2d:c1 (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:0c:41:19:2d:c1 wlan0: RX ReassocResp from 00:0c:41:19:2d:c1 (capab=0x1 status=0 aid=3) wlan0: associated wlan0: disassociate(reason=3) wlan0: RX deauthentication from 00:0c:41:19:2d:c1 (reason=6) wlan0: deauthenticated wlan0: RX deauthentication from 00:0c:41:19:2d:c1 (reason=6) wlan0: RX deauthentication from 00:0c:41:19:2d:c1 (reason=6) wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: RX authentication from 00:0c:41:19:2d:c1 (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:0c:41:19:2d:c1 wlan0: associate with AP 00:0c:41:19:2d:c1 wlan0: associate with AP 00:0c:41:19:2d:c1 wlan0: association with AP 00:0c:41:19:2d:c1 timed out wlan0: authentication frame received from 00:0c:41:19:2d:c1, but not in authenticate state - ignored wlan0: authentication frame received from 00:0c:41:19:2d:c1, but not in authenticate state - ignored wlan0: association frame received from 00:0c:41:19:2d:c1, but not in associate state - ignored wlan0: association frame received from 00:0c:41:19:2d:c1, but not in associate state - ignored wlan0: association frame received from 00:0c:41:19:2d:c1, but not in associate state - ignored wlan0: no IPv6 routers present thanks u all for helping -- Io utilizzo la versione gratuita di SPAMfighter per utenti privati. Sino ad ora ha rimosso 831 mail spam. Gli utenti paganti non hanno questo messaggio nelle loro email . Prova gratuitamente SPAMfighter qui:http://www.spamfighter.com/lit ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Help with wireless on Fedora 8
here there are new informations after upgrading the kernel,i tried to connect first with NetworkManager and then with System-Administration-Network and then activating interface : b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02) Registered led device: b43-phy0:tx Registered led device: b43-phy0:rx b43-phy0 debug: Chip initialized b43-phy0 debug: 32-bit DMA initialized input: Unspecified device as /class/input/input10 b43-phy0 debug: Wireless interface started b43-phy0 debug: Adding Interface type 2 ADDRCONF(NETDEV_UP): wlan0: link is not ready [drm] Initialized drm 1.1.0 20060810 [drm] Initialized i915 1.6.0 20060119 on minor 0 wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authentication with AP 00:0c:41:19:2d:c1 timed out wlan0: authentication frame received from 00:0c:41:19:2d:c1, but not in authenticate state - ignored wlan0: authentication frame received from 00:0c:41:19:2d:c1, but not in authenticate state - ignored wlan0: authentication frame received from 00:0c:41:19:2d:c1, but not in authenticate state - ignored wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authentication with AP 00:0c:41:19:2d:c1 timed out wlan0: authentication frame received from 00:0c:41:19:2d:c1, but not in authenticate state - ignored wlan0: authentication frame received from 00:0c:41:19:2d:c1, but not in authenticate state - ignored wlan0: authentication frame received from 00:0c:41:19:2d:c1, but not in authenticate state - ignored wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: RX authentication from 00:0c:41:19:2d:c1 (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:0c:41:19:2d:c1 wlan0: associate with AP 00:0c:41:19:2d:c1 wlan0: authentication frame received from 00:0c:41:19:2d:c1, but not in authenticate state - ignored wlan0: authentication frame received from 00:0c:41:19:2d:c1, but not in authenticate state - ignored wlan0: RX AssocResp from 00:0c:41:19:2d:c1 (capab=0x1 status=0 aid=2) wlan0: associated ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready wlan0: disassociate(reason=3) wlan0: association frame received from 00:0c:41:19:2d:c1, but not in associate state - ignored wlan0: RX deauthentication from 00:0c:41:19:2d:c1 (reason=6) wlan0: deauthenticated wlan0: RX deauthentication from 00:0c:41:19:2d:c1 (reason=6) wlan0: RX deauthentication from 00:0c:41:19:2d:c1 (reason=6) wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: RX authentication from 00:0c:41:19:2d:c1 (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:0c:41:19:2d:c1 wlan0: RX ReassocResp from 00:0c:41:19:2d:c1 (capab=0x1 status=0 aid=3) wlan0: associated wlan0: disassociate(reason=3) wlan0: RX deauthentication from 00:0c:41:19:2d:c1 (reason=6) wlan0: deauthenticated wlan0: RX deauthentication from 00:0c:41:19:2d:c1 (reason=6) wlan0: RX deauthentication from 00:0c:41:19:2d:c1 (reason=6) wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: authenticate with AP 00:0c:41:19:2d:c1 wlan0: RX authentication from 00:0c:41:19:2d:c1 (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:0c:41:19:2d:c1 wlan0: associate with AP 00:0c:41:19:2d:c1 wlan0: associate with AP 00:0c:41:19:2d:c1 wlan0: association with AP 00:0c:41:19:2d:c1 timed out wlan0: authentication frame received from 00:0c:41:19:2d:c1, but not in authenticate state - ignored wlan0: authentication frame received from 00:0c:41:19:2d:c1, but not in authenticate state - ignored wlan0: association frame received from 00:0c:41:19:2d:c1, but not in associate state - ignored wlan0: association frame received from 00:0c:41:19:2d:c1, but not in associate state - ignored wlan0: association frame received from 00:0c:41:19:2d:c1, but not in associate state - ignored wlan0: no IPv6 routers present thanks u all for helping -- Io utilizzo la versione gratuita di SPAMfighter per utenti privati. Sino ad ora ha rimosso 831 mail spam. Gli utenti paganti non hanno questo messaggio nelle loro email . Prova gratuitamente SPAMfighter qui:http://www.spamfighter.com/lit ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
[PATCH] b43: silence a bogus gcc warning
From: Frank Lichtenheld [EMAIL PROTECTED] inititalise ret to 0 to avoid the following bogus warning: CC [M] drivers/net/wireless/b43/debugfs.o drivers/net/wireless/b43/debugfs.c: In function ‘b43_debugfs_read’: drivers/net/wireless/b43/debugfs.c:355: warning: ‘ret’ may be used uninitialized in this function Signed-off-by: Frank Lichtenheld [EMAIL PROTECTED] Signed-off-by: Michael Buesch [EMAIL PROTECTED] --- drivers/net/wireless/b43/debugfs.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/net/wireless/b43/debugfs.c b/drivers/net/wireless/b43/debugfs.c index 734e70e..d8ac058 100644 --- a/drivers/net/wireless/b43/debugfs.c +++ b/drivers/net/wireless/b43/debugfs.c @@ -352,7 +352,7 @@ static ssize_t b43_debugfs_read(struct file *file, char __user *userbuf, struct b43_wldev *dev; struct b43_debugfs_fops *dfops; struct b43_dfs_file *dfile; - ssize_t ret; + ssize_t ret = 0; char *buf; const size_t bufsize = 1024 * 128; const size_t buforder = get_order(bufsize); -- 1.5.3.4 --- -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [PATCH] b43: Output message at startup if hardware switch for radio is off
On Friday 09 November 2007 23:47:37 Larry Finger wrote: Now that the radio is controlled by rfkill, there is a potential difficulty in helping a new user get started, as it is unlikely that they will have setup rfkill. This patch prints a message if the interface is started with the hardware switch off. Signed-off-by: Larry Finger [EMAIL PROTECTED] --- John, This patch is intended for the everything branch of wireless-2.6. Larry Well... Pressing the rfkill button is the _FIRST_ thing that I would do, if the device does not work. I'm wondering why people have a problem with that. On other operating systems it's the very same. On Windows there is no dmesg. -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [PATCH] b43: silence a bogus gcc warning
On Sat, Nov 10, 2007 at 04:14:03PM +0100, Michael Buesch wrote: From: Frank Lichtenheld [EMAIL PROTECTED] inititalise ret to 0 to avoid the following bogus warning: CC [M] drivers/net/wireless/b43/debugfs.o drivers/net/wireless/b43/debugfs.c: In function ‘b43_debugfs_read’: drivers/net/wireless/b43/debugfs.c:355: warning: ‘ret’ may be used uninitialized in this function Signed-off-by: Frank Lichtenheld [EMAIL PROTECTED] Signed-off-by: Michael Buesch [EMAIL PROTECTED] Isn't this what uninitialized_var() is for? -- John W. Linville [EMAIL PROTECTED] ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [PATCH] b43: silence a bogus gcc warning
On Saturday 10 November 2007 16:25:33 John W. Linville wrote: On Sat, Nov 10, 2007 at 04:14:03PM +0100, Michael Buesch wrote: From: Frank Lichtenheld [EMAIL PROTECTED] inititalise ret to 0 to avoid the following bogus warning: CC [M] drivers/net/wireless/b43/debugfs.o drivers/net/wireless/b43/debugfs.c: In function ‘b43_debugfs_read’: drivers/net/wireless/b43/debugfs.c:355: warning: ‘ret’ may be used uninitialized in this function Signed-off-by: Frank Lichtenheld [EMAIL PROTECTED] Signed-off-by: Michael Buesch [EMAIL PROTECTED] Isn't this what uninitialized_var() is for? I'd be OK with that, too. -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: BCM94311MCG
Ruggiero wrote: i loaded the old kernel always not starting network manager...i'm able to open some websitebut connection is really...really slow...any suggestion about? Have you used ndiswrapper with this interface and AP? If so, is it also slow, or is it OK? You might try blacklisting ipv6, if you are using only ipv4. It has been known to slow down communications. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: BCM94311MCG
yes i tried with ndiswrapper in ubuntu and speed was ok and also with windows speed is ok,just now i can't get speed faster than 28kB/sec... i know that i look a bit stupid but how can i blacklist ipv6? thanks -- Io utilizzo la versione gratuita di SPAMfighter per utenti privati. Sino ad ora ha rimosso 832 mail spam. Gli utenti paganti non hanno questo messaggio nelle loro email . Prova gratuitamente SPAMfighter qui:http://www.spamfighter.com/lit ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
b43 on a Linksys WRT54GL
Hi all, The last few days I've been trying to get b43 to work on my WRT54GL wlan-router. The reason I've been trying this is because I want to use the device as a bridge between the local university wlan and my own local network. However, because the network I'm trying to connect to is part of the academic eduroam infrastructure I need 802.1x with dynamic WEP keying. The proprietary broadcom drivers do not seem to support wpa_supplicant or xsupplicant as they do not implement (much of) the standard linux wireless extensions. There is a broadcom-specific driver for wpa_supplicant, but it is broken, and it would be nice to get rid of the binary-only driver altogether, not patch it up with yet another hack. So I set out to get b43 working. After a few hours of tinkering I got the driver to insert and load the firmware: b43-phy0: Broadcom 5352 WLAN found b43-phy0 debug: Found PHY: Analog 2, Type 2, Revision 7 b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2 b43-phy0 debug: DebugFS (CONFIG_DEBUG_FS) not enabled in kernel config phy0: Selected rate control algorithm 'simple' b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02) b43-phy0 debug: Chip initialized b43-phy0 debug: 32-bit DMA initialized b43-phy0 debug: Wireless interface started b43-phy0 debug: Adding Interface type 2 So far so good, I thought. But when I tried to actually do anything with the interface this message appeared in dmesg: b43-phy0 warning: Invalid max-TX-power value in SPROM. The driver itself responds to commands, but scanning finds nothing and trying to associate to access points doesn't work either. Also, the MAC addresses for both the wmaster0 and wlan0 interfaces are zeroed out: wlan0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wmaster0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) I've tried b43 from a git tree I pulled yesterday evening on openwrt kamikaze svn trunk (r9519), running linux 2.6.23.1. My SSB info is: ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x0E, vendor 0x4243) ssb: Core 1 found: Fast Ethernet (cc 0x806, rev 0x09, vendor 0x4243) ssb: Core 2 found: MIPS 3302 (cc 0x816, rev 0x06, vendor 0x4243) ssb: Core 3 found: USB 1.1 Host (cc 0x817, rev 0x02, vendor 0x4243) ssb: Core 4 found: MEMC SDRAM (cc 0x80F, rev 0x01, vendor 0x4243) ssb: Core 5 found: IEEE 802.11 (cc 0x812, rev 0x09, vendor 0x4243) ssb: Core 6 found: Roboswitch (cc 0x81C, rev 0x02, vendor 0x4243) ssb: Initializing MIPS core... ssb: set_irq: core 0x0806, irq 2 = 2 ssb: set_irq: core 0x0817, irq 4 = 3 ssb: set_irq: core 0x0812, irq 0 = 4 ssb: Sonics Silicon Backplane found at address 0x1800 If I were to take a fairly uneducated guess, I'd say the driver is not recognizing the layout of the SPROM correctly, since it doesn't seem to be able to find correct values for the MAC address and TX-power, both of which should be stored there... Is there anyone who knows what's wrong or can provide pointers on where to look? Any help would be greatly appreciated and I wouldn't mind getting my own hands dirty to fix it. :) Maurits Dijkstra ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: BCM94311MCG
Ruggiero wrote: yes i tried with ndiswrapper in ubuntu and speed was ok and also with windows speed is ok,just now i can't get speed faster than 28kB/sec... i know that i look a bit stupid but how can i blacklist ipv6? thanks Add it to /etc/modprobe.d/blacklist. For a single trial, you could also 'modprobe -rv ipv6'. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: BCM94311MCG
i followed your suggestions...but the speed is always the same... :S have no idea of what i could do? by the way now i'm connected to the ap...if there aren't any chances i'll go back to ndiswrapper :( thanks u all for helping -- Io utilizzo la versione gratuita di SPAMfighter per utenti privati. Sino ad ora ha rimosso 832 mail spam. Gli utenti paganti non hanno questo messaggio nelle loro email . Prova gratuitamente SPAMfighter qui:http://www.spamfighter.com/lit ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 on a Linksys WRT54GL
Maurits Dijkstra wrote:
Hi all,
The last few days I've been trying to get b43 to work on my WRT54GL
wlan-router. The reason I've been trying this is because I want to use the
device as a bridge between the local university wlan and my own local
network. However, because the network I'm trying to connect to is part of
the academic eduroam infrastructure I need 802.1x with dynamic WEP keying.
The proprietary broadcom drivers do not seem to support wpa_supplicant or
xsupplicant as they do not implement (much of) the standard linux wireless
extensions. There is a broadcom-specific driver for wpa_supplicant, but it
is broken, and it would be nice to get rid of the binary-only driver
altogether, not patch it up with yet another hack. So I set out to get b43
working. After a few hours of tinkering I got the driver to insert and
load the firmware:
b43-phy0: Broadcom 5352 WLAN found
b43-phy0 debug: Found PHY: Analog 2, Type 2, Revision 7
b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
b43-phy0 debug: DebugFS (CONFIG_DEBUG_FS) not enabled in kernel config
phy0: Selected rate control algorithm 'simple'
b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
b43-phy0 debug: Chip initialized
b43-phy0 debug: 32-bit DMA initialized
b43-phy0 debug: Wireless interface started
b43-phy0 debug: Adding Interface type 2
So far so good, I thought. But when I tried to actually do anything with
the interface this message appeared in dmesg:
b43-phy0 warning: Invalid max-TX-power value in SPROM.
The driver itself responds to commands, but scanning finds nothing and
trying to associate to access points doesn't work either. Also, the MAC
addresses for both the wmaster0 and wlan0 interfaces are zeroed out:
wlan0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wmaster0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
I've tried b43 from a git tree I pulled yesterday evening on openwrt
kamikaze svn trunk (r9519), running linux 2.6.23.1. My SSB info is:
ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x0E, vendor 0x4243)
ssb: Core 1 found: Fast Ethernet (cc 0x806, rev 0x09, vendor 0x4243)
ssb: Core 2 found: MIPS 3302 (cc 0x816, rev 0x06, vendor 0x4243)
ssb: Core 3 found: USB 1.1 Host (cc 0x817, rev 0x02, vendor 0x4243)
ssb: Core 4 found: MEMC SDRAM (cc 0x80F, rev 0x01, vendor 0x4243)
ssb: Core 5 found: IEEE 802.11 (cc 0x812, rev 0x09, vendor 0x4243)
ssb: Core 6 found: Roboswitch (cc 0x81C, rev 0x02, vendor 0x4243)
ssb: Initializing MIPS core...
ssb: set_irq: core 0x0806, irq 2 = 2
ssb: set_irq: core 0x0817, irq 4 = 3
ssb: set_irq: core 0x0812, irq 0 = 4
ssb: Sonics Silicon Backplane found at address 0x1800
If I were to take a fairly uneducated guess, I'd say the driver is not
recognizing the layout of the SPROM correctly, since it doesn't seem to be
able to find correct values for the MAC address and TX-power, both of
which should be stored there...
Is there anyone who knows what's wrong or can provide pointers on where to
look? Any help would be greatly appreciated and I wouldn't mind getting my
own hands dirty to fix it. :)
In the past few days, I have discovered that the SPROM revision 3 layout
doesn't match the specs. To
dump the SPROM, I used the following patch:
Index: linux-2.6/drivers/ssb/pci.c
===
--- linux-2.6.orig/drivers/ssb/pci.c
+++ linux-2.6/drivers/ssb/pci.c
@@ -457,6 +457,7 @@ static int ssb_pci_sprom_get(struct ssb_
{
int err = -ENOMEM;
u16 *buf;
+ int i;
buf = kcalloc(SSB_SPROMSIZE_WORDS, sizeof(u16), GFP_KERNEL);
if (!buf)
@@ -467,6 +468,12 @@ static int ssb_pci_sprom_get(struct ssb_
ssb_printk(KERN_WARNING PFX
WARNING: Invalid SPROM CRC (corrupt SPROM)\n);
}
+ printk(ssb: SPROM DUMP\nssb: 0x: );
+ for (i=0; i SSB_SPROMSIZE_WORDS; i++) {
+ printk(0x%.4X, buf[i]);
+ if ((i % 8) == 7) printk(\nssb: 0x%.4X: , (i + 1) * 2);
+ }
+ printk(\n);
err = sprom_extract(bus, sprom, buf);
kfree(buf);
I think your system doesn't use PCI, so this probably won't work, but you
should be able to
implement something similar. Once you have a dump, you should be able to find
the MAC addresses of
the wireless and ethernet
Re: b43 on a Linksys WRT54GL
Larry Finger wrote: I think your system doesn't use PCI, so this probably won't work, but you should be able to implement something similar. Once you have a dump, you should be able to find the MAC addresses of the wireless and ethernet interfaces. IIRC the WRTs don't have a sprom, instead its stored in their nvram flash area: For a WRT54GS v1.1: [EMAIL PROTECTED]:~# nvram show | grep -E ^(wl0[^_]|pa0|board|et0|il0) size: 7749 bytes (25019 left) boardrev=0x10 il0macaddr=00:12:17:15:fe:9e et0macaddr=00:12:17:15:FE:9C et0mdcport=0 boardtype=0x0101 wl0id=0x4320 wl0gpio2=0 wl0gpio3=0 boardflags2=0 pa0itssit=62 pa0maxpwr=0x48 boardflags=0x0188 et0phyaddr=30 pa0b0=0x170c pa0b1=0xfa24 pa0b2=0xfe70 boardnum=42 For a WRT54GL v1.?: [EMAIL PROTECTED]:~# nvram show | grep -E ^(wl0[^_]|pa0|board|et0|il0) size: 1771 bytes (30997 left) boardrev=0x10 il0macaddr=00:13:10:3f:35:27 et0macaddr=00:13:10:3F:35:25 et0mdcport=0 boardtype=0x0708 wl0id=0x4320 wl0gpio2=0 wl0gpio3=0 boardflags2=0 pa0itssit=62 pa0maxpwr=0x4e boardflags=0x0118 et0phyaddr=30 pa0b0=0x15eb pa0b1=0xfa82 pa0b2=0xfe66 boardnum=42 An older bcm47xx patch had this part in bcm43xx_main.c to fetch the values from nvram: #ifdef CONFIG_BCM947XX /* In the case some settings are found in nvram, use them * to override those read from sprom. */ c = nvram_get(boardflags2); if (c) sprom[BCM43xx_SPROM_BOARDFLAGS2] = simple_strtoul(c, NULL, 0); c = nvram_get(boardflags); if (c) sprom[BCM43xx_SPROM_BOARDFLAGS] = simple_strtoul(c, NULL, 0); c = nvram_get(il0macaddr); if (c) bcm43xx_aton(c, (char *)(sprom[BCM43xx_SPROM_IL0MACADDR])); c = nvram_get(et1macaddr); if (c) bcm43xx_aton(c, (char *)(sprom[BCM43xx_SPROM_ET1MACADDR])); c = nvram_get(pa0b0); if (c) sprom[BCM43xx_SPROM_PA0B0] = simple_strtoul(c, NULL, 0); c = nvram_get(pa0b1); if (c) sprom[BCM43xx_SPROM_PA0B1] = simple_strtoul(c, NULL, 0); c = nvram_get(pa0b2); if (c) sprom[BCM43xx_SPROM_PA0B2] = simple_strtoul(c, NULL, 0); c = nvram_get(pa1b0); if (c) sprom[BCM43xx_SPROM_PA1B0] = simple_strtoul(c, NULL, 0); c = nvram_get(pa1b1); if (c) sprom[BCM43xx_SPROM_PA1B1] = simple_strtoul(c, NULL, 0); c = nvram_get(pa1b2); if (c) sprom[BCM43xx_SPROM_PA1B2] = simple_strtoul(c, NULL, 0); c = nvram_get(boardrev); if (c) sprom[BCM43xx_SPROM_BOARDREV] = simple_strtoul(c, NULL, 0); #endif -- Tobias PGP: http://9ac7e0bc.uguu.de このメールは十割再利用されたビットで作られています。 ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
