Dell 1350 Wireless Will Not Connect

I read the thread about the b43-tools but the git command on there fails.

git clone http://git.bu3sch.de/git/b43-tools.git
Initialized empty Git repository in /sbin/b43-tools/.git/
fatal: http://git.bu3sch.de/git/b43-tools.git/info/refs not found: did you run git update-server-info on the server?

I am assuming the server is them not me?

I have installed the firmware per my dmeg request. And the firmware is installed correctly.

108.340105] b43 ssb0:0: firmware: requesting b43/ucode5.fw
108.445064] b43 ssb0:0: firmware: requesting b43/pcm5.fw
108.464310] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
108.472379] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
108.600082] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)

The card works it just will not connect. I think I have that rev 3 issue where I need to edit the SPROM but I can not seem to get the b43-tools installed.

On 02/12/2011 05:36 PM, psytropic wrote:
>
> I read the thread about the b43-tools but the git command on there
> fails.
>
> git clone http://git.bu3sch.de/git/b43-tools.git
> Initialized empty Git repository in /sbin/b43-tools/.git/
> fatal: http://git.bu3sch.de/git/b43-tools.git/info/refs not found: did
> you run git update-server-info on the server?
>
> I am assuming the server is them not me?

Yes. You have old instructions. The server has been moved from http to git. Make
that change in the line above, and you will have the tools.

> I have installed the firmware per my dmeg request. And the firmware is
> installed correctly.
>
> 108.340105] b43 ssb0:0: firmware: requesting b43/ucode5.fw
> 108.445064] b43 ssb0:0: firmware: requesting b43/pcm5.fw
> 108.464310] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
> 108.472379] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
> 108.600082] b43-phy0: Loading firmware version 478.104 (2008-07-01
> 00:50:23)
>
> The card works it just will not connect. I think I have that rev 3
> issue where I need to edit the SPROM but I can not seem to get the
> b43-tools installed.

I doubt that you will need to rewrite the SPROM. That was a technique used for
only a short time. If you are talking about the bluetooth coexistence, you can
test it with the following:


sudo /sbin/modprobe -rv b43
sudo /sbin/modprobe -v b43_btcoex = 0

If your connection works after doing that, then it is possible that you might
want to reflash the SPROM; however, do you want to brick your device? That is
the downside of doing it wrong.

Well I tried that sudo /sbin/modprobe -v b43 btcoex =0 and still a no go, connection keeps popping up asking for my WPA key so I give up. My ralink based Zonet works flawlessly but it is bulky and not suitable for travel.

Any other ideas for this Dell 1350? Maybe ndiswrapper?

On 02/13/2011 02:36 AM, psytropic wrote:
>
> Well I tried that sudo /sbin/modprobe -v b43 btcoex =0 and still a no
> go, connection keeps popping up asking for my WPA key so I give up. My
> ralink based Zonet works flawlessly but it is bulky and not suitable for
> travel.
>
> Any other ideas for this Dell 1350? Maybe ndiswrapper?

If you want system crashes, go ahead.

If the btcoex bit did not work, then rewriting the SPROM will do nothing. Try
the connection again with b43 and report the output of the following:


sudo /usr/sbin/iwlist scan
/usr/sbin/iwconfig
dmesg | egrep "ssb|b43|phy"

matt@linux-4b7i:~> sudo /usr/sbin/iwlist scan

lo        Interface doesn't support scanning.



eth0      Interface doesn't support scanning.



wlan0     No scan results



matt@linux-4b7i:~> /usr/sbin/iwconfig

lo        no wireless extensions.



eth0      no wireless extensions.



wlan0     IEEE 802.11bg  ESSID:off/any  

          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   

          Retry  long limit:7   RTS thr:off   Fragment thr:off

          Power Management:off

          

matt@linux-4b7i:~> dmesg | egrep "ssb|b43|phy"

    0.000000] BIOS-provided physical RAM map:

    0.000000] modified physical RAM map:

   12.796153] b43-pci-bridge 0000:02:03.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19

   12.796207] ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x04, vendor 0x4243)

   12.796216] ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x05, vendor 0x4243)

   12.796224] ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x02, vendor 0x4243)

   12.796232] ssb: Core 3 found: V90 (cc 0x807, rev 0x02, vendor 0x4243)

   12.796240] ssb: Core 4 found: PCI (cc 0x804, rev 0x09, vendor 0x4243)

   12.799610] ssb: Sonics Silicon Backplane found on PCI device 0000:02:03.0

   13.338690] b43-phy0: Broadcom 4306 WLAN found (core revision 5)

   13.848866] phy0: Selected rate control algorithm 'minstrel'

   13.849636] Registered led device: b43-phy0::tx

   13.849657] Registered led device: b43-phy0::rx

   13.849679] Registered led device: b43-phy0::radio

   53.136091] b43 ssb0:0: firmware: requesting b43/ucode5.fw

   53.189377] b43 ssb0:0: firmware: requesting b43/pcm5.fw

   53.213470] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw

   53.237927] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw

   53.712066] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)

On 02/13/2011 01:36 PM, psytropic wrote:
>
> Code:
> --------------------
> matt@linux-4b7i:~> sudo /usr/sbin/iwlist scan
>
> lo Interface doesn’t support scanning.
>
>
>
> eth0 Interface doesn’t support scanning.
>
>
>
> wlan0 No scan results
>
>
>
> matt@linux-4b7i:~> /usr/sbin/iwconfig
>
> lo no wireless extensions.
>
>
>
> eth0 no wireless extensions.
>
>
>
> wlan0 IEEE 802.11bg ESSID:off/any
>
> Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
>
> Retry long limit:7 RTS thr:off Fragment thr:off
>
> Power Management:off
>
>
>
> matt@linux-4b7i:~> dmesg | egrep “ssb|b43|phy”
>
> 0.000000] BIOS-provided physical RAM map:
>
> 0.000000] modified physical RAM map:
>
> 12.796153] b43-pci-bridge 0000:02:03.0: PCI INT A → GSI 19 (level, low) → IRQ 19
>
> 12.796207] ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x04, vendor 0x4243)
>
> 12.796216] ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x05, vendor 0x4243)
>
> 12.796224] ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x02, vendor 0x4243)
>
> 12.796232] ssb: Core 3 found: V90 (cc 0x807, rev 0x02, vendor 0x4243)
>
> 12.796240] ssb: Core 4 found: PCI (cc 0x804, rev 0x09, vendor 0x4243)
>
> 12.799610] ssb: Sonics Silicon Backplane found on PCI device 0000:02:03.0
>
> 13.338690] b43-phy0: Broadcom 4306 WLAN found (core revision 5)
>
> 13.848866] phy0: Selected rate control algorithm ‘minstrel’
>
> 13.849636] Registered led device: b43-phy0::tx
>
> 13.849657] Registered led device: b43-phy0::rx
>
> 13.849679] Registered led device: b43-phy0::radio
>
> 53.136091] b43 ssb0:0: firmware: requesting b43/ucode5.fw
>
> 53.189377] b43 ssb0:0: firmware: requesting b43/pcm5.fw
>
> 53.213470] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
>
> 53.237927] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
>
> 53.712066] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
> --------------------

All is OK except for the “no scan results”.

Does this computer have a switch to turn off the radio?

Please install the rfkill package and post the output of the rfkill command using:


sudo zypper in rfkill
/usr/sbin/rfkill list

linux-4b7i:/home/matt # /usr/sbin/rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

On 02/13/2011 09:36 PM, psytropic wrote:
>
> linux-4b7i:/home/matt # /usr/sbin/rfkill list
> 0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no

You said earlier that the card “works”. To me it looks broken. I see no reason
why it cannot scan, but until it does, it will not connect.

Please output the results of these commands:


SPROM=$(find /sys -name ssb_sprom)
sudo cat $SPROM

014000000300281020430080020002000010001800000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF0B001E7D14CBFFFFFFFFFFFFFFFFFFFFFFFFFFFF45309A1193FBA5FEFFFFFFFF3C000000000000003E000D00FFFF00000000000000000149

On 02/14/2011 01:06 PM, psytropic wrote:
>
> 014000000300281020430080020002000010001800000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF0B001E7D14CBFFFFFFFFFFFFFFFFFFFFFFFFFFFF45309A1193FBA5FEFFFFFFFF3C000000000000003E000D00FFFF00000000000000000149
>

The standard b43 code is clearing the BlueTooth coexistence flag already. That
is why loading with the btcoex keyword did not change anything. There is no need
to rewrite the SPROM.

I still have no explanation for the lack of scan data.

Yah it’s odd. Just some more info: my SSID is not broadcast so I turned that on just to see if it would show up and it does not. This card works in Windows XP just fine. I have a Zonet ZEW2500P that works flawlessly.

The laptop is a Dell Insipron 2000. The button for Wireless is a shared keyboard key and even that function works because it turns the radio off on the Zonet when I press it.

I think I have done everything so far that needs to be done to get the Broadcom to work. If anyone else has any ideas that would be great. lwfinger I appreciate all the help.

On 02/14/2011 03:06 PM, psytropic wrote:
>
> Yah it’s odd. Just some more info: my SSID is not broadcast so I turned
> that on just to see if it would show up and it does not. This card
> works in Windows XP just fine. I have a Zonet ZEW2500P that works
> flawlessly.
>
> The laptop is a Dell Insipron 2000. The button for Wireless is a
> shared keyboard key and even that function works because it turns the
> radio off on the Zonet when I press it.
>
> I think I have done everything so far that needs to be done to get the
> Broadcom to work. If anyone else has any ideas that would be great.
> lwfinger I appreciate all the help.

Is your hidden SSID AP the only one that you can see? If so, you get mmany
negative points for witholding information.

If the AP is broadcasting the SSID, does the Broadcom card see any scan data?

The Broadcom can not see anything, mine or anyone else. The Zonet could NOT see mine unless I connect to hidden network but it CAN see other broadcasted SSID’s. I just enabled my broadcast to see if it would help out the broadcom.

Just some more info, I was on the b43 site and looked at the hardware chart and my ID is 14e4:4320. It’s weird that everything works right but it can not scan. When I press the wireless button on the keyboard Network Manager even reports the Broadcom is disabled. This SHOULD be working and is so frustrating that I have no error messages at all. Should I post my entire dmesg in here?

Just another thing. I have completely re-installed 11.3. The ONLY thing I have done so far is
sudo /usr/sbin/install_bcm43xx_firmware

and then rebooted.

What should I do next?

Ok so I am at my wits end with this, ndiswrapper does the exact same thing, iwlist scan shows no scan data just like the b43 driver.

Is there a program that can check the state of the radio?

On 03/09/2011 03:06 PM, psytropic wrote:
>
> Ok so I am at my wits end with this, ndiswrapper does the exact same
> thing, iwlist scan shows no scan data just like the b43 driver.
>
> Is there a program that can check the state of the radio?

It is called wireshark - you need to run it on a separate computer and see what
is on the air.

Just wanted to come back by here and let you guys know how I resolved this. The built-in wireless is actually a rev 4 according to what is on the actual mini-pci card. I took that out, put in a rev 2 version from a broken HP laptop and now have built-in wireless working with b43legacy.

One of 2 things could have been the issue. The rev 4 is not compatible all the way with b43 OR the card’s radio is broken. Either way the rev 2 popped right in and worked.

That is good news. I am happy for you.

Just an amateurish thought:

Maybe it would help the developers or other users to find this post or even the answer if you would post the numeric ID/IDs of the working one? Or are they the same [14e4:4320] for both chips?

/sbin/lspci -vnn | grep 14e4

?

You may compare:

Have a lot of fun,
Martin
(pistazienfresser)

The cards are in the b43 listing, one was rev 3 one was rev 2. I think it was a hardware failure and not a fault of the b43 / b43legacy driver.