|
|
|
date: Tue, 22 Apr 2008 16:46:11 +0100,
group: uk.comp.os.linux
back
ubunty wifi: cant acquire IP address
Running Ubuntu 8.04 (Hardy Heron) on a desktop PC using (or trying to) a
Linksys WMP54G PCI wifi card (that uses a Broadcom BCM4306 chipset.)
Trying to connect to a Netgear DG834 adsl router.
It works using windows xp just fine.
It doesn't in Ubuntu no matter what I seem to do, althugh it's fine using a
wired connection.
Tried latest "restricted" Broadcom drivers in Ubuntu and even compiled them
myself to check.
lspci gives:
(cut version)
00:0f.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless
LAN Controller (rev 03)
00:11.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
From which I assume the card and drivers are okay????
But using wifi radar or wicd I can't establish an ip address.
Now iwconfig says there is a card there but states encrypt is off , even
though I have setup WEP with a password (to avoid WPA added complications at
this time.)
Also it seems to say RX is invalid??? Dont know what that means.
Here it is:
IEEE 802.11g ESSID:"sally000"
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Also the PC is next to the wireless router (2 feet away) so is the signal
level rather low? But it does work with XP as I said above..
Can ping the router using wired connection but not with wireless. The PC
sees the MAC address of the router but the router doesn't see the wireless
card.
Have another wifi device (a usb asustek which uses rt73 drivers and although
it connects intially it then disconnects and also seems to stop the wired
connection to my other pc running xp, so I don't feel it's a viable option.
Totally frustrated and out of ideas. All help appreciated.
Cheers
Dave
date: Tue, 22 Apr 2008 16:46:11 +0100
author: David lid
|
Re: ubunty wifi: cant acquire IP address
"David" <dave@antispam.invalid> writes:
> Running Ubuntu 8.04 (Hardy Heron) on a desktop PC using (or trying to) a
> Linksys WMP54G PCI wifi card (that uses a Broadcom BCM4306 chipset.)
> Trying to connect to a Netgear DG834 adsl router.
> It works using windows xp just fine.
> It doesn't in Ubuntu no matter what I seem to do, althugh it's fine using a
> wired connection.
>
> Tried latest "restricted" Broadcom drivers in Ubuntu and even compiled them
> myself to check.
>
> lspci gives:
> (cut version)
> 00:0f.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless
> LAN Controller (rev 03)
> 00:11.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL-8139/8139C/8139C+ (rev 10)
> From which I assume the card and drivers are okay????
Nope. They probably are OK, but you tell that by the fact the they
have brought up an interface (see later). The above is taken from a
table and just identifies the hardware.
> But using wifi radar or wicd I can't establish an ip address.
What happens if you try to let Ubuntu do it all itself? I.e. can't
the network manager get you connected?
> Now iwconfig says there is a card there but states encrypt is off , even
> though I have setup WEP with a password (to avoid WPA added complications at
> this time.)
> Also it seems to say RX is invalid??? Dont know what that means.
Rx is receive (as opposed to Tx -- transmit) so...
> Here it is:
> IEEE 802.11g ESSID:"sally000"
> Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
> Tx-Power=27 dBm
> Retry min limit:7 RTS thr:off Fragment thr=2346 B
> Encryption key:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
this says there have been 0 receive errors (none due to invalid nwid,
none due to invalid frag, etc).
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> Also the PC is next to the wireless router (2 feet away) so is the signal
> level rather low? But it does work with XP as I said above..
Yes. It looks like either the driver does not report the signal
strength (unlikely) or it is not really working. What does dmsg have
to say about the driver. For example, I need the ipw2200 driver and I
get:
$ dmesg | grep ipw
[ 7.682082] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
[ 7.682088] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[ 7.684676] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[ 5.223188] ipw2200: Detected geography ZZD (13 802.11bg channels, 0 802.11a channels)
I do all this sort of stuff with WEP off to start with. From the
bottom up you need:
- The driver to find some hardware it understands.
- The hardware to associate with the right AP
- The interface to be given an address (often just by using DHCP).
- The routing tables to be correctly set up
- The right DNS server.
If the hardware is working, I'd expect
$ iwlist scan
to show your AP. Does it?
--
Ben.
date: Tue, 22 Apr 2008 19:05:56 +0100
author: Ben Bacarisse
|
Re: ubunty wifi: cant acquire IP address
Ben Bacarisse wrote:
> "David" <dave@antispam.invalid> writes:
>
>> Running Ubuntu 8.04 (Hardy Heron) on a desktop PC using (or trying to) a
>> Linksys WMP54G PCI wifi card (that uses a Broadcom BCM4306 chipset.)
>> Trying to connect to a Netgear DG834 adsl router.
>> It works using windows xp just fine.
>> It doesn't in Ubuntu no matter what I seem to do, althugh it's fine using a
>> wired connection.
>>
>> Tried latest "restricted" Broadcom drivers in Ubuntu and even compiled them
>> myself to check.
>>
>> lspci gives:
>> (cut version)
>> 00:0f.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless
>> LAN Controller (rev 03)
>> 00:11.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
>> RTL-8139/8139C/8139C+ (rev 10)
>> From which I assume the card and drivers are okay????
>
> Nope. They probably are OK, but you tell that by the fact the they
> have brought up an interface (see later). The above is taken from a
> table and just identifies the hardware.
>
>> But using wifi radar or wicd I can't establish an ip address.
>
> What happens if you try to let Ubuntu do it all itself? I.e. can't
> the network manager get you connected?
>
>> Now iwconfig says there is a card there but states encrypt is off , even
>> though I have setup WEP with a password (to avoid WPA added complications at
>> this time.)
>> Also it seems to say RX is invalid??? Dont know what that means.
>
> Rx is receive (as opposed to Tx -- transmit) so...
>
>> Here it is:
>> IEEE 802.11g ESSID:"sally000"
>> Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
>> Tx-Power=27 dBm
>> Retry min limit:7 RTS thr:off Fragment thr=2346 B
>> Encryption key:off
>> Link Quality:0 Signal level:0 Noise level:0
>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>
> this says there have been 0 receive errors (none due to invalid nwid,
> none due to invalid frag, etc).
>
>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>>
>> Also the PC is next to the wireless router (2 feet away) so is the signal
>> level rather low? But it does work with XP as I said above..
>
> Yes. It looks like either the driver does not report the signal
> strength (unlikely) or it is not really working. What does dmsg have
> to say about the driver. For example, I need the ipw2200 driver and I
> get:
>
> $ dmesg | grep ipw
> [ 7.682082] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
> [ 7.682088] ipw2200: Copyright(c) 2003-2006 Intel Corporation
> [ 7.684676] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
> [ 5.223188] ipw2200: Detected geography ZZD (13 802.11bg channels, 0 802.11a channels)
>
> I do all this sort of stuff with WEP off to start with. From the
> bottom up you need:
>
> - The driver to find some hardware it understands.
> - The hardware to associate with the right AP
> - The interface to be given an address (often just by using DHCP).
> - The routing tables to be correctly set up
> - The right DNS server.
>
> If the hardware is working, I'd expect
>
> $ iwlist scan
>
> to show your AP. Does it?
>
What does the output of a 'dmesg' command have to say about your
BCM4306? The lspci output only shows that the card is plugged in. Most
of the useful stuff is in the system logs that you can access from
dmesg (for the current boot) or from /var/log/messages (for the
current boot and before).
I guess that you will see messages about missing firmware. You did
turn bcm43xx debugging on, or didn't you?
Larry
date: Tue, 22 Apr 2008 19:03:46 GMT
author: Larry Finger
|
Re: ubunty wifi: cant acquire IP address
"Ben Bacarisse" wrote in message
news:87od81epdn.fsf@bsb.me.uk...
> "David" <dave@antispam.invalid> writes:
>
>> Running Ubuntu 8.04 (Hardy Heron) on a desktop PC using (or trying to) a
>> Linksys WMP54G PCI wifi card (that uses a Broadcom BCM4306 chipset.)
>> Trying to connect to a Netgear DG834 adsl router.
>> It works using windows xp just fine.
>> It doesn't in Ubuntu no matter what I seem to do, althugh it's fine using
>> a
>> wired connection.
>>
>> Tried latest "restricted" Broadcom drivers in Ubuntu and even compiled
>> them
>> myself to check.
>>
>> lspci gives:
>> (cut version)
>> 00:0f.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
>> Wireless
>> LAN Controller (rev 03)
>> 00:11.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
>> RTL-8139/8139C/8139C+ (rev 10)
>> From which I assume the card and drivers are okay????
>
> Nope. They probably are OK, but you tell that by the fact the they
> have brought up an interface (see later). The above is taken from a
> table and just identifies the hardware.
>
>> But using wifi radar or wicd I can't establish an ip address.
>
> What happens if you try to let Ubuntu do it all itself? I.e. can't
> the network manager get you connected?
>
>> Now iwconfig says there is a card there but states encrypt is off , even
>> though I have setup WEP with a password (to avoid WPA added complications
>> at
>> this time.)
>> Also it seems to say RX is invalid??? Dont know what that means.
>
> Rx is receive (as opposed to Tx -- transmit) so...
>
>> Here it is:
>> IEEE 802.11g ESSID:"sally000"
>> Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
>> Tx-Power=27 dBm
>> Retry min limit:7 RTS thr:off Fragment thr=2346 B
>> Encryption key:off
>> Link Quality:0 Signal level:0 Noise level:0
>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>
> this says there have been 0 receive errors (none due to invalid nwid,
> none due to invalid frag, etc).
>
>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>>
>> Also the PC is next to the wireless router (2 feet away) so is the signal
>> level rather low? But it does work with XP as I said above..
>
> Yes. It looks like either the driver does not report the signal
> strength (unlikely) or it is not really working. What does dmsg have
> to say about the driver. For example, I need the ipw2200 driver and I
> get:
>
> $ dmesg | grep ipw
> [ 7.682082] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver,
> 1.2.2kmprq
> [ 7.682088] ipw2200: Copyright(c) 2003-2006 Intel Corporation
> [ 7.684676] ipw2200: Detected Intel PRO/Wireless 2200BG Network
> Connection
> [ 5.223188] ipw2200: Detected geography ZZD (13 802.11bg channels, 0
> 802.11a channels)
>
> I do all this sort of stuff with WEP off to start with. From the
> bottom up you need:
>
> - The driver to find some hardware it understands.
> - The hardware to associate with the right AP
> - The interface to be given an address (often just by using DHCP).
> - The routing tables to be correctly set up
> - The right DNS server.
>
> If the hardware is working, I'd expect
>
> $ iwlist scan
>
> to show your AP. Does it?
>
> --
> Ben.
Ben,
Really appreciate your help.
Answering your questions:
1.Just using net manager didn't help. Same "cant establish an IP" issue.
2.Yes I knew what rx and tx stand for but wasn't sure what this all meant. I
guess no errors is because there isn't any comunication going on.
3.Tried dmesg | grep ipw with and without sudo but got no response, just
threw me back to the prompt.
4.Have tried with and without WEP but no difference.
5.iwlist scan gives:
--------------------
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
wmaster0 Interface doesn't support scanning.
wlan0 Scan completed :
Cell 01 - Address: 00:18:4D:49:2C:0E
ESSID:"sally000"
Mode:Master
Channel:5
Frequency:2.432 GHz (Channel 5)
Quality=81/100 Signal level=-45 dBm Noise level=-68
dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=00000005d64ca233
Cell 02 - Address: 00:01:38:8F:A8:8C
ESSID:"zoom"
Mode:Master
Channel:10
Frequency:2.457 GHz (Channel 10)
Quality=55/100 Signal level=-68 dBm Noise level=-68
dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=00000001225691da
---------------------------
My wireless net SSID is sally000. The unprotected "zoom" is next door. I
have told them about this before!! They are lucky it's me that's their
neighbour! and not someone less scrupulous.!
So iwlist doesn't seem to show my AP.
I even reseated the PCI card, rebooted and did this all again.
Then did a sudo iwconfig which gave:
---------
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:"sally000"
Mode:Managed Frequency:2.432 GHz Access Point: 00:18:4D:49:2C:0E
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:A7C3-E7FF-5E
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
--------
Note encryption now seems to be recognised. This is what I am uneasy about.
How things seems to change back and forth. Flaky.
In addition: I tried to connect using a static IP. Using wifi radar it said
it had connected to the IP I had set up but when I disconnected the wired
LAN cable I found the connection didn't work.
As an aside must I unplug the network cable if I try to use wireless?
Does this help you to help me. Just ask if you need more clues.
Thanks again
Dave
date: Tue, 22 Apr 2008 20:13:00 +0100
author: David lid
|
Re: ubunty wifi: cant acquire IP address
"David" <dave@antispam.invalid> wrote in message
news:480e38b9$0$10643$fa0fcedb@news.zen.co.uk...
>
> "Ben Bacarisse" wrote in message
> news:87od81epdn.fsf@bsb.me.uk...
>> "David" <dave@antispam.invalid> writes:
>>
>>> Running Ubuntu 8.04 (Hardy Heron) on a desktop PC using (or trying to) a
>>> Linksys WMP54G PCI wifi card (that uses a Broadcom BCM4306 chipset.)
>>> Trying to connect to a Netgear DG834 adsl router.
>>> It works using windows xp just fine.
>>> It doesn't in Ubuntu no matter what I seem to do, althugh it's fine
>>> using a
>>> wired connection.
>>>
>>> Tried latest "restricted" Broadcom drivers in Ubuntu and even compiled
>>> them
>>> myself to check.
>>>
>>> lspci gives:
>>> (cut version)
>>> 00:0f.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
>>> Wireless
>>> LAN Controller (rev 03)
>>> 00:11.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
>>> RTL-8139/8139C/8139C+ (rev 10)
>>> From which I assume the card and drivers are okay????
>>
>> Nope. They probably are OK, but you tell that by the fact the they
>> have brought up an interface (see later). The above is taken from a
>> table and just identifies the hardware.
>>
>>> But using wifi radar or wicd I can't establish an ip address.
>>
>> What happens if you try to let Ubuntu do it all itself? I.e. can't
>> the network manager get you connected?
>>
>>> Now iwconfig says there is a card there but states encrypt is off , even
>>> though I have setup WEP with a password (to avoid WPA added
>>> complications at
>>> this time.)
>>> Also it seems to say RX is invalid??? Dont know what that means.
>>
>> Rx is receive (as opposed to Tx -- transmit) so...
>>
>>> Here it is:
>>> IEEE 802.11g ESSID:"sally000"
>>> Mode:Managed Frequency:2.412 GHz Access Point:
>>> Not-Associated
>>> Tx-Power=27 dBm
>>> Retry min limit:7 RTS thr:off Fragment thr=2346 B
>>> Encryption key:off
>>> Link Quality:0 Signal level:0 Noise level:0
>>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>>
>> this says there have been 0 receive errors (none due to invalid nwid,
>> none due to invalid frag, etc).
>>
>>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>>>
>>> Also the PC is next to the wireless router (2 feet away) so is the
>>> signal
>>> level rather low? But it does work with XP as I said above..
>>
>> Yes. It looks like either the driver does not report the signal
>> strength (unlikely) or it is not really working. What does dmsg have
>> to say about the driver. For example, I need the ipw2200 driver and I
>> get:
>>
>> $ dmesg | grep ipw
>> [ 7.682082] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver,
>> 1.2.2kmprq
>> [ 7.682088] ipw2200: Copyright(c) 2003-2006 Intel Corporation
>> [ 7.684676] ipw2200: Detected Intel PRO/Wireless 2200BG Network
>> Connection
>> [ 5.223188] ipw2200: Detected geography ZZD (13 802.11bg channels, 0
>> 802.11a channels)
>>
>> I do all this sort of stuff with WEP off to start with. From the
>> bottom up you need:
>>
>> - The driver to find some hardware it understands.
>> - The hardware to associate with the right AP
>> - The interface to be given an address (often just by using DHCP).
>> - The routing tables to be correctly set up
>> - The right DNS server.
>>
>> If the hardware is working, I'd expect
>>
>> $ iwlist scan
>>
>> to show your AP. Does it?
>>
>> --
>> Ben.
>
> Ben,
> Really appreciate your help.
> Answering your questions:
> 1.Just using net manager didn't help. Same "cant establish an IP" issue.
> 2.Yes I knew what rx and tx stand for but wasn't sure what this all meant.
> I guess no errors is because there isn't any comunication going on.
> 3.Tried dmesg | grep ipw with and without sudo but got no response, just
> threw me back to the prompt.
> 4.Have tried with and without WEP but no difference.
> 5.iwlist scan gives:
> --------------------
> lo Interface doesn't support scanning.
>
> eth0 Interface doesn't support scanning.
>
> wmaster0 Interface doesn't support scanning.
>
> wlan0 Scan completed :
> Cell 01 - Address: 00:18:4D:49:2C:0E
> ESSID:"sally000"
> Mode:Master
> Channel:5
> Frequency:2.432 GHz (Channel 5)
> Quality=81/100 Signal level=-45 dBm Noise level=-68
> dBm
> Encryption key:on
> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
> 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
> 48 Mb/s; 54 Mb/s
> Extra:tsf=00000005d64ca233
> Cell 02 - Address: 00:01:38:8F:A8:8C
> ESSID:"zoom"
> Mode:Master
> Channel:10
> Frequency:2.457 GHz (Channel 10)
> Quality=55/100 Signal level=-68 dBm Noise level=-68
> dBm
> Encryption key:off
> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
> 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
> 48 Mb/s; 54 Mb/s
> Extra:tsf=00000001225691da
>
> ---------------------------
> My wireless net SSID is sally000. The unprotected "zoom" is next door. I
> have told them about this before!! They are lucky it's me that's their
> neighbour! and not someone less scrupulous.!
> So iwlist doesn't seem to show my AP.
>
> I even reseated the PCI card, rebooted and did this all again.
> Then did a sudo iwconfig which gave:
> ---------
> lo no wireless extensions.
>
> eth0 no wireless extensions.
>
> wmaster0 no wireless extensions.
>
> wlan0 IEEE 802.11g ESSID:"sally000"
> Mode:Managed Frequency:2.432 GHz Access Point:
> 00:18:4D:49:2C:0E
> Tx-Power=27 dBm
> Retry min limit:7 RTS thr:off Fragment thr=2346 B
> Encryption key:A7C3-E7FF-5E
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
> --------
>
> Note encryption now seems to be recognised. This is what I am uneasy
> about. How things seems to change back and forth. Flaky.
>
>
> In addition: I tried to connect using a static IP. Using wifi radar it
> said it had connected to the IP I had set up but when I disconnected the
> wired LAN cable I found the connection didn't work.
> As an aside must I unplug the network cable if I try to use wireless?
>
> Does this help you to help me. Just ask if you need more clues.
> Thanks again
> Dave
>
>
Think I was being stupid earlier on when I said didn't get anything from
dmesg | grep iwp as I think that was your particular wireless board.
Mine uses a broadcom 4306 and b43-fwcutter so i got a response when i used
dmesg | grep b43
This is it:
--------------------------
[ 54.575135] b43-phy0: Broadcom 4306 WLAN found
[ 70.172030] input: b43-phy0 as /devices/virtual/input/input6
[ 72.206158] Registered led device: b43-phy0:tx
[ 72.207040] Registered led device: b43-phy0:rx
[ 72.207678] Registered led device: b43-phy0:radio
[ 77.695944] input: b43-phy0 as /devices/virtual/input/input7
[ 80.038241] Registered led device: b43-phy0:tx
[ 80.038761] Registered led device: b43-phy0:rx
[ 80.039016] Registered led device: b43-phy0:radio
------------------
Doesn't say anything to me but you experts will no doubt hopefully see the
light.
Cheers
date: Tue, 22 Apr 2008 20:41:30 +0100
author: David lid
|
Re: ubunty wifi: cant acquire IP address
"Larry Finger" wrote in message
news:mEqPj.232096$cQ1.88204@bgtnsc04-news.ops.worldnet.att.net...
> Ben Bacarisse wrote:
>> "David" <dave@antispam.invalid> writes:
>>
>>> Running Ubuntu 8.04 (Hardy Heron) on a desktop PC using (or trying to) a
>>> Linksys WMP54G PCI wifi card (that uses a Broadcom BCM4306 chipset.)
>>> Trying to connect to a Netgear DG834 adsl router.
>>> It works using windows xp just fine.
>>> It doesn't in Ubuntu no matter what I seem to do, althugh it's fine
>>> using a wired connection.
>>>
>>> Tried latest "restricted" Broadcom drivers in Ubuntu and even compiled
>>> them myself to check.
>>>
>>> lspci gives:
>>> (cut version)
>>> 00:0f.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
>>> Wireless LAN Controller (rev 03)
>>> 00:11.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
>>> RTL-8139/8139C/8139C+ (rev 10)
>>> From which I assume the card and drivers are okay????
>>
>> Nope. They probably are OK, but you tell that by the fact the they
>> have brought up an interface (see later). The above is taken from a
>> table and just identifies the hardware.
>>
>>> But using wifi radar or wicd I can't establish an ip address.
>>
>> What happens if you try to let Ubuntu do it all itself? I.e. can't
>> the network manager get you connected?
>>
>>> Now iwconfig says there is a card there but states encrypt is off , even
>>> though I have setup WEP with a password (to avoid WPA added
>>> complications at this time.)
>>> Also it seems to say RX is invalid??? Dont know what that means.
>>
>> Rx is receive (as opposed to Tx -- transmit) so...
>>
>>> Here it is:
>>> IEEE 802.11g ESSID:"sally000"
>>> Mode:Managed Frequency:2.412 GHz Access Point:
>>> Not-Associated
>>> Tx-Power=27 dBm
>>> Retry min limit:7 RTS thr:off Fragment thr=2346 B
>>> Encryption key:off
>>> Link Quality:0 Signal level:0 Noise level:0
>>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>>
>> this says there have been 0 receive errors (none due to invalid nwid,
>> none due to invalid frag, etc).
>>
>>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>>>
>>> Also the PC is next to the wireless router (2 feet away) so is the
>>> signal level rather low? But it does work with XP as I said above..
>>
>> Yes. It looks like either the driver does not report the signal
>> strength (unlikely) or it is not really working. What does dmsg have
>> to say about the driver. For example, I need the ipw2200 driver and I
>> get:
>>
>> $ dmesg | grep ipw
>> [ 7.682082] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver,
>> 1.2.2kmprq
>> [ 7.682088] ipw2200: Copyright(c) 2003-2006 Intel Corporation
>> [ 7.684676] ipw2200: Detected Intel PRO/Wireless 2200BG Network
>> Connection
>> [ 5.223188] ipw2200: Detected geography ZZD (13 802.11bg channels, 0
>> 802.11a channels)
>>
>> I do all this sort of stuff with WEP off to start with. From the
>> bottom up you need:
>>
>> - The driver to find some hardware it understands.
>> - The hardware to associate with the right AP
>> - The interface to be given an address (often just by using DHCP).
>> - The routing tables to be correctly set up
>> - The right DNS server.
>>
>> If the hardware is working, I'd expect
>>
>> $ iwlist scan
>>
>> to show your AP. Does it?
>>
>
> What does the output of a 'dmesg' command have to say about your BCM4306?
> The lspci output only shows that the card is plugged in. Most of the
> useful stuff is in the system logs that you can access from dmesg (for the
> current boot) or from /var/log/messages (for the current boot and before).
>
> I guess that you will see messages about missing firmware. You did turn
> bcm43xx debugging on, or didn't you?
>
> Larry
Hi Larry,
dmsg gives me 10 feet of stuff but I have narrowed it down by dmsg | grep
b43 to get
-------
[ 54.575135] b43-phy0: Broadcom 4306 WLAN found
[ 70.172030] input: b43-phy0 as /devices/virtual/input/input6
[ 72.206158] Registered led device: b43-phy0:tx
[ 72.207040] Registered led device: b43-phy0:rx
[ 72.207678] Registered led device: b43-phy0:radio
[ 77.695944] input: b43-phy0 as /devices/virtual/input/input7
[ 80.038241] Registered led device: b43-phy0:tx
[ 80.038761] Registered led device: b43-phy0:rx
[ 80.039016] Registered led device: b43-phy0:radio
------------------
Does this help?
If you really want the full output I can send it.
What is bcm43xx debugging????
I am not using the bcm43xx-fwcutter but the newer b4-fwcutter as per the
recent threads I have read. Also
http://linuxwireless.sipsolutions.net/en/users/Drivers/b43
Is this wrong?
Is there life after wireless?
Cheers
date: Tue, 22 Apr 2008 20:47:33 +0100
author: David lid
|
Re: ubunty wifi: cant acquire IP address
David wrote:
> "Larry Finger" wrote in message
> news:mEqPj.232096$cQ1.88204@bgtnsc04-news.ops.worldnet.att.net...
>> Ben Bacarisse wrote:
>>> "David" <dave@antispam.invalid> writes:
>>>
>>>> Running Ubuntu 8.04 (Hardy Heron) on a desktop PC using (or trying to) a
>>>> Linksys WMP54G PCI wifi card (that uses a Broadcom BCM4306 chipset.)
>>>> Trying to connect to a Netgear DG834 adsl router.
>>>> It works using windows xp just fine.
>>>> It doesn't in Ubuntu no matter what I seem to do, althugh it's fine
>>>> using a wired connection.
>>>>
>>>> Tried latest "restricted" Broadcom drivers in Ubuntu and even compiled
>>>> them myself to check.
>>>>
>>>> lspci gives:
>>>> (cut version)
>>>> 00:0f.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
>>>> Wireless LAN Controller (rev 03)
>>>> 00:11.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
>>>> RTL-8139/8139C/8139C+ (rev 10)
>>>> From which I assume the card and drivers are okay????
>>> Nope. They probably are OK, but you tell that by the fact the they
>>> have brought up an interface (see later). The above is taken from a
>>> table and just identifies the hardware.
>>>
>>>> But using wifi radar or wicd I can't establish an ip address.
>>> What happens if you try to let Ubuntu do it all itself? I.e. can't
>>> the network manager get you connected?
>>>
>>>> Now iwconfig says there is a card there but states encrypt is off , even
>>>> though I have setup WEP with a password (to avoid WPA added
>>>> complications at this time.)
>>>> Also it seems to say RX is invalid??? Dont know what that means.
>>> Rx is receive (as opposed to Tx -- transmit) so...
>>>
>>>> Here it is:
>>>> IEEE 802.11g ESSID:"sally000"
>>>> Mode:Managed Frequency:2.412 GHz Access Point:
>>>> Not-Associated
>>>> Tx-Power=27 dBm
>>>> Retry min limit:7 RTS thr:off Fragment thr=2346 B
>>>> Encryption key:off
>>>> Link Quality:0 Signal level:0 Noise level:0
>>>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>>> this says there have been 0 receive errors (none due to invalid nwid,
>>> none due to invalid frag, etc).
>>>
>>>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>>>>
>>>> Also the PC is next to the wireless router (2 feet away) so is the
>>>> signal level rather low? But it does work with XP as I said above..
>>> Yes. It looks like either the driver does not report the signal
>>> strength (unlikely) or it is not really working. What does dmsg have
>>> to say about the driver. For example, I need the ipw2200 driver and I
>>> get:
>>>
>>> $ dmesg | grep ipw
>>> [ 7.682082] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver,
>>> 1.2.2kmprq
>>> [ 7.682088] ipw2200: Copyright(c) 2003-2006 Intel Corporation
>>> [ 7.684676] ipw2200: Detected Intel PRO/Wireless 2200BG Network
>>> Connection
>>> [ 5.223188] ipw2200: Detected geography ZZD (13 802.11bg channels, 0
>>> 802.11a channels)
>>>
>>> I do all this sort of stuff with WEP off to start with. From the
>>> bottom up you need:
>>>
>>> - The driver to find some hardware it understands.
>>> - The hardware to associate with the right AP
>>> - The interface to be given an address (often just by using DHCP).
>>> - The routing tables to be correctly set up
>>> - The right DNS server.
>>>
>>> If the hardware is working, I'd expect
>>>
>>> $ iwlist scan
>>>
>>> to show your AP. Does it?
>>>
>> What does the output of a 'dmesg' command have to say about your BCM4306?
>> The lspci output only shows that the card is plugged in. Most of the
>> useful stuff is in the system logs that you can access from dmesg (for the
>> current boot) or from /var/log/messages (for the current boot and before).
>>
>> I guess that you will see messages about missing firmware. You did turn
>> bcm43xx debugging on, or didn't you?
>>
>> Larry
>
> Hi Larry,
>
> dmsg gives me 10 feet of stuff but I have narrowed it down by dmsg | grep
> b43 to get
>
> -------
> [ 54.575135] b43-phy0: Broadcom 4306 WLAN found
> [ 70.172030] input: b43-phy0 as /devices/virtual/input/input6
> [ 72.206158] Registered led device: b43-phy0:tx
> [ 72.207040] Registered led device: b43-phy0:rx
> [ 72.207678] Registered led device: b43-phy0:radio
> [ 77.695944] input: b43-phy0 as /devices/virtual/input/input7
> [ 80.038241] Registered led device: b43-phy0:tx
> [ 80.038761] Registered led device: b43-phy0:rx
> [ 80.039016] Registered led device: b43-phy0:radio
>
> ------------------
> Does this help?
> If you really want the full output I can send it.
>
> What is bcm43xx debugging????
As you are using the b43 driver, please select the debug option for
both b43 and the Silicon Sonics driver. No, I don't need the full
dmesg output.
Larry
date: Tue, 22 Apr 2008 20:11:31 GMT
author: Larry Finger
|
Re: ubunty wifi: cant acquire IP address
"Larry Finger" wrote in message
news:TDrPj.119995$D_3.68523@bgtnsc05-news.ops.worldnet.att.net...
> David wrote:
>> "Larry Finger" wrote in message
>> news:mEqPj.232096$cQ1.88204@bgtnsc04-news.ops.worldnet.att.net...
>>> Ben Bacarisse wrote:
>>>> "David" <dave@antispam.invalid> writes:
>>>>
>>>>> Running Ubuntu 8.04 (Hardy Heron) on a desktop PC using (or trying to)
>>>>> a Linksys WMP54G PCI wifi card (that uses a Broadcom BCM4306 chipset.)
>>>>> Trying to connect to a Netgear DG834 adsl router.
>>>>> It works using windows xp just fine.
>>>>> It doesn't in Ubuntu no matter what I seem to do, althugh it's fine
>>>>> using a wired connection.
>>>>>
>>>>> Tried latest "restricted" Broadcom drivers in Ubuntu and even compiled
>>>>> them myself to check.
>>>>>
>>>>> lspci gives:
>>>>> (cut version)
>>>>> 00:0f.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
>>>>> Wireless LAN Controller (rev 03)
>>>>> 00:11.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
>>>>> RTL-8139/8139C/8139C+ (rev 10)
>>>>> From which I assume the card and drivers are okay????
>>>> Nope. They probably are OK, but you tell that by the fact the they
>>>> have brought up an interface (see later). The above is taken from a
>>>> table and just identifies the hardware.
>>>>
>>>>> But using wifi radar or wicd I can't establish an ip address.
>>>> What happens if you try to let Ubuntu do it all itself? I.e. can't
>>>> the network manager get you connected?
>>>>
>>>>> Now iwconfig says there is a card there but states encrypt is off ,
>>>>> even though I have setup WEP with a password (to avoid WPA added
>>>>> complications at this time.)
>>>>> Also it seems to say RX is invalid??? Dont know what that means.
>>>> Rx is receive (as opposed to Tx -- transmit) so...
>>>>
>>>>> Here it is:
>>>>> IEEE 802.11g ESSID:"sally000"
>>>>> Mode:Managed Frequency:2.412 GHz Access Point:
>>>>> Not-Associated
>>>>> Tx-Power=27 dBm
>>>>> Retry min limit:7 RTS thr:off Fragment thr=2346 B
>>>>> Encryption key:off
>>>>> Link Quality:0 Signal level:0 Noise level:0
>>>>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>>>> this says there have been 0 receive errors (none due to invalid nwid,
>>>> none due to invalid frag, etc).
>>>>
>>>>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>>>>>
>>>>> Also the PC is next to the wireless router (2 feet away) so is the
>>>>> signal level rather low? But it does work with XP as I said above..
>>>> Yes. It looks like either the driver does not report the signal
>>>> strength (unlikely) or it is not really working. What does dmsg have
>>>> to say about the driver. For example, I need the ipw2200 driver and I
>>>> get:
>>>>
>>>> $ dmesg | grep ipw
>>>> [ 7.682082] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver,
>>>> 1.2.2kmprq
>>>> [ 7.682088] ipw2200: Copyright(c) 2003-2006 Intel Corporation
>>>> [ 7.684676] ipw2200: Detected Intel PRO/Wireless 2200BG Network
>>>> Connection
>>>> [ 5.223188] ipw2200: Detected geography ZZD (13 802.11bg channels, 0
>>>> 802.11a channels)
>>>>
>>>> I do all this sort of stuff with WEP off to start with. From the
>>>> bottom up you need:
>>>>
>>>> - The driver to find some hardware it understands.
>>>> - The hardware to associate with the right AP
>>>> - The interface to be given an address (often just by using DHCP).
>>>> - The routing tables to be correctly set up
>>>> - The right DNS server.
>>>>
>>>> If the hardware is working, I'd expect
>>>>
>>>> $ iwlist scan
>>>>
>>>> to show your AP. Does it?
>>>>
>>> What does the output of a 'dmesg' command have to say about your
>>> BCM4306? The lspci output only shows that the card is plugged in. Most
>>> of the useful stuff is in the system logs that you can access from dmesg
>>> (for the current boot) or from /var/log/messages (for the current boot
>>> and before).
>>>
>>> I guess that you will see messages about missing firmware. You did turn
>>> bcm43xx debugging on, or didn't you?
>>>
>>> Larry
>>
>> Hi Larry,
>>
>> dmsg gives me 10 feet of stuff but I have narrowed it down by dmsg | grep
>> b43 to get
>>
>> -------
>> [ 54.575135] b43-phy0: Broadcom 4306 WLAN found
>> [ 70.172030] input: b43-phy0 as /devices/virtual/input/input6
>> [ 72.206158] Registered led device: b43-phy0:tx
>> [ 72.207040] Registered led device: b43-phy0:rx
>> [ 72.207678] Registered led device: b43-phy0:radio
>> [ 77.695944] input: b43-phy0 as /devices/virtual/input/input7
>> [ 80.038241] Registered led device: b43-phy0:tx
>> [ 80.038761] Registered led device: b43-phy0:rx
>> [ 80.039016] Registered led device: b43-phy0:radio
>>
>> ------------------
>> Does this help?
>> If you really want the full output I can send it.
>>
>> What is bcm43xx debugging????
>
> As you are using the b43 driver, please select the debug option for both
> b43 and the Silicon Sonics driver. No, I don't need the full dmesg output.
>
> Larry
Yes using b43 as thats what
http://linuxwireless.sipsolutions.net/en/users/Drivers/b43 and soem googled
outputs have recommende and tht's what is the default on Ubuntu 8.04.
But still don't underatydnm what you mean by debug option. Sory to be thinck
but no idea what this and where.
Also not sure why you say to use silicon sonics drivers. Its a broadcom chip
so using broadcom firmware. Have I lost the plot? Sorry to be a noob.
Cheers
date: Tue, 22 Apr 2008 21:21:51 +0100
author: David lid
|
Re: ubunty wifi: cant acquire IP address
On Tue, 22 Apr 2008 20:13:00 +0100, David wrote:
> Channel:5
> Frequency:2.432 GHz (Channel 5)
It's a silly question but your AP is on Ch 5 isn't it? Yes, I know it
works in doze, but maye be doze quietly overides defaults or ubunty
does...
> Quality=81/100 Signal level=-45 dBm Noise level=-68 dBm
It appears to be seeing something but is it your AP?
--
Cheers
Dave.
date: Tue, 22 Apr 2008 21:59:43 +0100 (BST)
author: Dave Liquorice
|
Re: ubunty wifi: cant acquire IP address
"David" <dave@antispam.invalid> writes:
<snip>
> 5.iwlist scan gives:
> --------------------
> lo Interface doesn't support scanning.
>
> eth0 Interface doesn't support scanning.
>
> wmaster0 Interface doesn't support scanning.
>
> wlan0 Scan completed :
> Cell 01 - Address: 00:18:4D:49:2C:0E
> ESSID:"sally000"
> Mode:Master
> Channel:5
> Frequency:2.432 GHz (Channel 5)
> Quality=81/100 Signal level=-45 dBm Noise level=-68
> dBm
> Encryption key:on
> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
> 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
> 48 Mb/s; 54 Mb/s
> Extra:tsf=00000005d64ca233
> Cell 02 - Address: 00:01:38:8F:A8:8C
> ESSID:"zoom"
> Mode:Master
> Channel:10
> Frequency:2.457 GHz (Channel 10)
> Quality=55/100 Signal level=-68 dBm Noise level=-68
> dBm
> Encryption key:off
> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
> 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
> 48 Mb/s; 54 Mb/s
> Extra:tsf=00000001225691da
>
> ---------------------------
> My wireless net SSID is sally000. The unprotected "zoom" is next door. I
> have told them about this before!! They are lucky it's me that's their
> neighbour! and not someone less scrupulous.!
> So iwlist doesn't seem to show my AP.
>
> I even reseated the PCI card, rebooted and did this all again.
> Then did a sudo iwconfig which gave:
> ---------
> lo no wireless extensions.
>
> eth0 no wireless extensions.
>
> wmaster0 no wireless extensions.
>
> wlan0 IEEE 802.11g ESSID:"sally000"
> Mode:Managed Frequency:2.432 GHz Access Point: 00:18:4D:49:2C:0E
> Tx-Power=27 dBm
> Retry min limit:7 RTS thr:off Fragment thr=2346 B
> Encryption key:A7C3-E7FF-5E
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
> --------
>
> Note encryption now seems to be recognised. This is what I am uneasy about.
> How things seems to change back and forth. Flaky.
It may seem flaky and firm up when you get a feel for what is going
on. I am in the dark here as I don't know this driver but all the
above looks good except for the signal level. I found this:
http://linuxwireless.sipsolutions.net/en/users/Drivers/b43/faq
that says:
If iwconfig shows
* Link Quality:0 Signal level:0
then you may have wireless disabled in the BIOS. Check for things like
"Wireless : Application Control".
Is that a possibility?
--
Ben.
date: Tue, 22 Apr 2008 22:17:57 +0100
author: Ben Bacarisse
|
Re: ubunty wifi: cant acquire IP address
"Dave Liquorice" wrote in message
news:nyyfbegfubjuvyypbz.jzr9jj2.pminews@srv1.howhill.net...
> On Tue, 22 Apr 2008 20:13:00 +0100, David wrote:
>
>> Channel:5
>> Frequency:2.432 GHz (Channel 5)
>
> It's a silly question but your AP is on Ch 5 isn't it? Yes, I know it
> works in doze, but maye be doze quietly overides defaults or ubunty
> does...
>
>> Quality=81/100 Signal level=-45 dBm Noise level=-68 dBm
>
> It appears to be seeing something but is it your AP?
>
> --
> Cheers
> Dave.
>
At this stage I don't think anything is a silly question Dave! Yes my AP is
on ch5 and I have incidentally changed it from ch 11 just in case there was
soem weird channel issue. The AP is talking happily to other devices
wirelessly. I've also tried to use auto for channel selection.
I agree its seeing something and I am pretty sure it's my AP.
Any ideas?
Cheers
dave
date: Tue, 22 Apr 2008 22:54:03 +0100
author: David lid
|
Re: ubunty wifi: cant acquire IP address
"Ben Bacarisse" wrote in message
news:87bq41eghm.fsf@bsb.me.uk...
> "David" <dave@antispam.invalid> writes:
>
> <snip>
>> 5.iwlist scan gives:
>> --------------------
>> lo Interface doesn't support scanning.
>>
>> eth0 Interface doesn't support scanning.
>>
>> wmaster0 Interface doesn't support scanning.
>>
>> wlan0 Scan completed :
>> Cell 01 - Address: 00:18:4D:49:2C:0E
>> ESSID:"sally000"
>> Mode:Master
>> Channel:5
>> Frequency:2.432 GHz (Channel 5)
>> Quality=81/100 Signal level=-45 dBm Noise level=-68
>> dBm
>> Encryption key:on
>> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
>> 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
>> 48 Mb/s; 54 Mb/s
>> Extra:tsf=00000005d64ca233
>> Cell 02 - Address: 00:01:38:8F:A8:8C
>> ESSID:"zoom"
>> Mode:Master
>> Channel:10
>> Frequency:2.457 GHz (Channel 10)
>> Quality=55/100 Signal level=-68 dBm Noise level=-68
>> dBm
>> Encryption key:off
>> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
>> 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
>> 48 Mb/s; 54 Mb/s
>> Extra:tsf=00000001225691da
>>
>> ---------------------------
>> My wireless net SSID is sally000. The unprotected "zoom" is next door. I
>> have told them about this before!! They are lucky it's me that's their
>> neighbour! and not someone less scrupulous.!
>> So iwlist doesn't seem to show my AP.
>>
>> I even reseated the PCI card, rebooted and did this all again.
>> Then did a sudo iwconfig which gave:
>> ---------
>> lo no wireless extensions.
>>
>> eth0 no wireless extensions.
>>
>> wmaster0 no wireless extensions.
>>
>> wlan0 IEEE 802.11g ESSID:"sally000"
>> Mode:Managed Frequency:2.432 GHz Access Point:
>> 00:18:4D:49:2C:0E
>> Tx-Power=27 dBm
>> Retry min limit:7 RTS thr:off Fragment thr=2346 B
>> Encryption key:A7C3-E7FF-5E
>> Link Quality:0 Signal level:0 Noise level:0
>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>> --------
>>
>> Note encryption now seems to be recognised. This is what I am uneasy
>> about.
>> How things seems to change back and forth. Flaky.
>
> It may seem flaky and firm up when you get a feel for what is going
> on. I am in the dark here as I don't know this driver but all the
> above looks good except for the signal level. I found this:
>
> http://linuxwireless.sipsolutions.net/en/users/Drivers/b43/faq
>
> that says:
>
> If iwconfig shows
>
> * Link Quality:0 Signal level:0
>
> then you may have wireless disabled in the BIOS. Check for things like
> "Wireless : Application Control".
>
> Is that a possibility?
>
> --
> Ben.
Hi Ben,
Yes I've seen that url but the log I attached most recently now shows a
signal is present.
I guess that narrows down things.
It's a desk top so I doubt there is any wifi on-off facility.
Now trying PCLinuxOS as an alternative.
Cheers
date: Tue, 22 Apr 2008 23:00:26 +0100
author: David lid
|
Re: ubunty wifi: cant acquire IP address
"David" <dave@antispam.invalid> writes:
>Running Ubuntu 8.04 (Hardy Heron) on a desktop PC using (or trying to) a
>Linksys WMP54G PCI wifi card (that uses a Broadcom BCM4306 chipset.)
Broadcom tends to be a bastard of a card for linux.
a) modprobe nameofdriver
and then look at
dmesg|tail
for error messages
b) iwlist s
to see if anything is reported by the card. If it is, then the card should
work.
c) If nothing else, use ndiswrapper with the Windows driver.
>Trying to connect to a Netgear DG834 adsl router.
>It works using windows xp just fine.
>It doesn't in Ubuntu no matter what I seem to do, althugh it's fine using a
>wired connection.
modprobe
>Tried latest "restricted" Broadcom drivers in Ubuntu and even compiled them
>myself to check.
>lspci gives:
>(cut version)
>00:0f.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless
>LAN Controller (rev 03)
>00:11.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
>RTL-8139/8139C/8139C+ (rev 10)
>From which I assume the card and drivers are okay????
>But using wifi radar or wicd I can't establish an ip address.
>Now iwconfig says there is a card there but states encrypt is off , even
>though I have setup WEP with a password (to avoid WPA added complications at
>this time.)
>Also it seems to say RX is invalid??? Dont know what that means.
>Here it is:
> IEEE 802.11g ESSID:"sally000"
> Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
> Tx-Power=27 dBm
> Retry min limit:7 RTS thr:off Fragment thr=2346 B
> Encryption key:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>Also the PC is next to the wireless router (2 feet away) so is the signal
>level rather low? But it does work with XP as I said above..
>Can ping the router using wired connection but not with wireless. The PC
>sees the MAC address of the router but the router doesn't see the wireless
>card.
>Have another wifi device (a usb asustek which uses rt73 drivers and although
>it connects intially it then disconnects and also seems to stop the wired
>connection to my other pc running xp, so I don't feel it's a viable option.
>Totally frustrated and out of ideas. All help appreciated.
>Cheers
>Dave
date: Tue, 22 Apr 2008 22:36:42 GMT
author: Unruh
|
Re: ubunty wifi: cant acquire IP address
"David" <dave@antispam.invalid> writes:
> "Ben Bacarisse" wrote in message
> news:87bq41eghm.fsf@bsb.me.uk...
>> "David" <dave@antispam.invalid> writes:
>>
>> <snip>
>>> 5.iwlist scan gives:
>>> --------------------
>>> wlan0 Scan completed :
>>> Cell 01 - Address: 00:18:4D:49:2C:0E
>>> ESSID:"sally000"
>>> Mode:Master
>>> Channel:5
>>> Frequency:2.432 GHz (Channel 5)
>>> Quality=81/100 Signal level=-45 dBm Noise level=-68
>>> dBm
>>> Encryption key:on
>>> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
>>> 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
>>> 48 Mb/s; 54 Mb/s
>>> Extra:tsf=00000005d64ca233
<snip>
>>> ---------------------------
<snip>
>>> wlan0 IEEE 802.11g ESSID:"sally000"
>>> Mode:Managed Frequency:2.432 GHz Access Point:
>>> 00:18:4D:49:2C:0E
>>> Tx-Power=27 dBm
>>> Retry min limit:7 RTS thr:off Fragment thr=2346 B
>>> Encryption key:A7C3-E7FF-5E
>>> Link Quality:0 Signal level:0 Noise level:0
>>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
<snip>
>> It may seem flaky and firm up when you get a feel for what is going
>> on. I am in the dark here as I don't know this driver but all the
>> above looks good except for the signal level. I found this:
>>
>> http://linuxwireless.sipsolutions.net/en/users/Drivers/b43/faq
>>
>> that says:
>>
>> If iwconfig shows
>>
>> * Link Quality:0 Signal level:0
>>
>> then you may have wireless disabled in the BIOS. Check for things like
>> "Wireless : Application Control".
>>
>> Is that a possibility?
> Yes I've seen that url but the log I attached most recently now shows a
> signal is present.
I don't think it does. The scan shows different data to that shown by
iwconfig. The driver may well get the data in quite different ways
(I don't know). If you are still seeing
Link Quality:0 Signal level:0 Noise level:0
in the iwconfig output, then I would check your BIOS settings. It
can't hurt.
> I guess that narrows down things.
The driver is still show no signal from the associated access point.
That is a key indicator. Sadly, I don't know exactly what it indicates!
--
Ben.
date: Tue, 22 Apr 2008 23:58:16 +0100
author: Ben Bacarisse
|
Re: ubunty wifi: cant acquire IP address
David wrote:
>
> Yes using b43 as thats what
> http://linuxwireless.sipsolutions.net/en/users/Drivers/b43 and soem googled
> outputs have recommende and tht's what is the default on Ubuntu 8.04.
> But still don't underatydnm what you mean by debug option. Sory to be thinck
> but no idea what this and where.
> Also not sure why you say to use silicon sonics drivers. Its a broadcom chip
> so using broadcom firmware. Have I lost the plot? Sorry to be a noob.
Debug is a kernel configuration option. The Broadcom chip connects to
the main computer bus through a Sonics Silicon Backplane using the ssb
driver. Both are there and both are needed.
Larry
date: Tue, 22 Apr 2008 23:57:32 GMT
author: Larry Finger
|
Re: ubunty wifi: cant acquire IP address
Ben Bacarisse wrote:
> "David" <dave@antispam.invalid> writes:
>
>> "Ben Bacarisse" wrote in message
>> news:87bq41eghm.fsf@bsb.me.uk...
>>> "David" <dave@antispam.invalid> writes:
>>>
>>> <snip>
>>>> 5.iwlist scan gives:
>>>> --------------------
>>>> wlan0 Scan completed :
>>>> Cell 01 - Address: 00:18:4D:49:2C:0E
>>>> ESSID:"sally000"
>>>> Mode:Master
>>>> Channel:5
>>>> Frequency:2.432 GHz (Channel 5)
>>>> Quality=81/100 Signal level=-45 dBm Noise level=-68
>>>> dBm
>>>> Encryption key:on
>>>> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
>>>> 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
>>>> 48 Mb/s; 54 Mb/s
>>>> Extra:tsf=00000005d64ca233
> <snip>
>>>> ---------------------------
> <snip>
>>>> wlan0 IEEE 802.11g ESSID:"sally000"
>>>> Mode:Managed Frequency:2.432 GHz Access Point:
>>>> 00:18:4D:49:2C:0E
>>>> Tx-Power=27 dBm
>>>> Retry min limit:7 RTS thr:off Fragment thr=2346 B
>>>> Encryption key:A7C3-E7FF-5E
>>>> Link Quality:0 Signal level:0 Noise level:0
>>>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>>>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
David - please ignore most of the "advice" that you are getting. These
guys don't have the slightest idea what is going on.
Your iwconfig output will not show any signal, noise, or link quality
until it actually authenticates. If you are using NetworkManager with
a normal configuration, then the presence of a ESSID name and/or an
Access Point MAC indicates that the device has associated with the AP.
Please send the output of 'dmesg | grep wlan0'.
Larry
date: Wed, 23 Apr 2008 00:07:38 GMT
author: Larry Finger
|
Re: ubunty wifi: cant acquire IP address
"Larry Finger" wrote in message
news:MXuPj.233185$cQ1.142542@bgtnsc04-news.ops.worldnet.att.net...
> David wrote:
>>
>> Yes using b43 as thats what
>> http://linuxwireless.sipsolutions.net/en/users/Drivers/b43 and soem
>> googled outputs have recommende and tht's what is the default on Ubuntu
>> 8.04.
>> But still don't underatydnm what you mean by debug option. Sory to be
>> thinck but no idea what this and where.
>> Also not sure why you say to use silicon sonics drivers. Its a broadcom
>> chip so using broadcom firmware. Have I lost the plot? Sorry to be a
>> noob.
>
> Debug is a kernel configuration option. The Broadcom chip connects to the
> main computer bus through a Sonics Silicon Backplane using the ssb driver.
> Both are there and both are needed.
>
> Larry
Still not at all sure I understand what this means so looks like I will need
to spend a lot of tomorrow reading up about it all. I also now see that some
articles say I should use b43 and others b43-legacy as I have rev 3 of the
card. Very very confusing and certainly not what I was hoping of Ubuntu 's
new release.
Thanks for giving me a point in (hopefully) the right direction.
Cheers
Dave
date: Wed, 23 Apr 2008 01:20:10 +0100
author: David lid
|
Re: ubunty wifi: cant acquire IP address
"Larry Finger" wrote in message
news:e5vPj.120439$D_3.55473@bgtnsc05-news.ops.worldnet.att.net...
> Ben Bacarisse wrote:
>> "David" <dave@antispam.invalid> writes:
>>
>>> "Ben Bacarisse" wrote in message
>>> news:87bq41eghm.fsf@bsb.me.uk...
>>>> "David" <dave@antispam.invalid> writes:
>>>>
>>>> <snip>
>>>>> 5.iwlist scan gives:
>>>>> --------------------
>>>>> wlan0 Scan completed :
>>>>> Cell 01 - Address: 00:18:4D:49:2C:0E
>>>>> ESSID:"sally000"
>>>>> Mode:Master
>>>>> Channel:5
>>>>> Frequency:2.432 GHz (Channel 5)
>>>>> Quality=81/100 Signal level=-45 dBm Noise
>>>>> level=-68
>>>>> dBm
>>>>> Encryption key:on
>>>>> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6
>>>>> Mb/s
>>>>> 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36
>>>>> Mb/s
>>>>> 48 Mb/s; 54 Mb/s
>>>>> Extra:tsf=00000005d64ca233
>> <snip>
>>>>> ---------------------------
>> <snip>
>>>>> wlan0 IEEE 802.11g ESSID:"sally000"
>>>>> Mode:Managed Frequency:2.432 GHz Access Point:
>>>>> 00:18:4D:49:2C:0E
>>>>> Tx-Power=27 dBm
>>>>> Retry min limit:7 RTS thr:off Fragment thr=2346 B
>>>>> Encryption key:A7C3-E7FF-5E
>>>>> Link Quality:0 Signal level:0 Noise level:0
>>>>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>>>>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> David - please ignore most of the "advice" that you are getting. These
> guys don't have the slightest idea what is going on.
>
> Your iwconfig output will not show any signal, noise, or link quality
> until it actually authenticates. If you are using NetworkManager with a
> normal configuration, then the presence of a ESSID name and/or an Access
> Point MAC indicates that the device has associated with the AP.
>
> Please send the output of 'dmesg | grep wlan0'.
>
> Larry
Here is sudo dmesg | grep wlan0
[ 128.781880] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 364.328612] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Hope this helps.
Cheers
date: Wed, 23 Apr 2008 01:27:15 +0100
author: David lid
|
Re: ubunty wifi: cant acquire IP address
David wrote:
> Still not at all sure I understand what this means so looks like I will need
> to spend a lot of tomorrow reading up about it all. I also now see that some
> articles say I should use b43 and others b43-legacy as I have rev 3 of the
> card. Very very confusing and certainly not what I was hoping of Ubuntu 's
> new release.
> Thanks for giving me a point in (hopefully) the right direction.
Your card uses b43 and not b43legacy. In fact, the ssb driver looks at
the PHY revision of your card, and loads the correct driver. If you
had a BCM4306 rev 2, the it would need b43legacy. I know that is
correct as I'm the one who converted bcm43xx into b43legacy!
Did you build the kernel you are running, or are you using the one
that Ubuntu built? If the latter, I understand why the appropriate
debugging options have not been set. I have been trying to get Ubuntu
to set the debugging options for a long time, but the idiots don't
seem to get the word!
If you built your own keernel, then you need to run 'make xconfig' and
select the debugging options.
Larry
date: Wed, 23 Apr 2008 02:10:45 GMT
author: Larry Finger
|
Re: ubunty wifi: cant acquire IP address
David wrote:
> "Larry Finger" wrote in message
> news:e5vPj.120439$D_3.55473@bgtnsc05-news.ops.worldnet.att.net...
>> Ben Bacarisse wrote:
>>> "David" <dave@antispam.invalid> writes:
>>>
>>>> "Ben Bacarisse" wrote in message
>>>> news:87bq41eghm.fsf@bsb.me.uk...
>>>>> "David" <dave@antispam.invalid> writes:
>>>>>
>>>>> <snip>
>>>>>> 5.iwlist scan gives:
>>>>>> --------------------
>>>>>> wlan0 Scan completed :
>>>>>> Cell 01 - Address: 00:18:4D:49:2C:0E
>>>>>> ESSID:"sally000"
>>>>>> Mode:Master
>>>>>> Channel:5
>>>>>> Frequency:2.432 GHz (Channel 5)
>>>>>> Quality=81/100 Signal level=-45 dBm Noise
>>>>>> level=-68
>>>>>> dBm
>>>>>> Encryption key:on
>>>>>> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6
>>>>>> Mb/s
>>>>>> 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36
>>>>>> Mb/s
>>>>>> 48 Mb/s; 54 Mb/s
>>>>>> Extra:tsf=00000005d64ca233
>>> <snip>
>>>>>> ---------------------------
>>> <snip>
>>>>>> wlan0 IEEE 802.11g ESSID:"sally000"
>>>>>> Mode:Managed Frequency:2.432 GHz Access Point:
>>>>>> 00:18:4D:49:2C:0E
>>>>>> Tx-Power=27 dBm
>>>>>> Retry min limit:7 RTS thr:off Fragment thr=2346 B
>>>>>> Encryption key:A7C3-E7FF-5E
>>>>>> Link Quality:0 Signal level:0 Noise level:0
>>>>>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>>>>>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>> David - please ignore most of the "advice" that you are getting. These
>> guys don't have the slightest idea what is going on.
>>
>> Your iwconfig output will not show any signal, noise, or link quality
>> until it actually authenticates. If you are using NetworkManager with a
>> normal configuration, then the presence of a ESSID name and/or an Access
>> Point MAC indicates that the device has associated with the AP.
>>
>> Please send the output of 'dmesg | grep wlan0'.
>>
>> Larry
>
> Here is sudo dmesg | grep wlan0
>
> [ 128.781880] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [ 364.328612] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>
These results give me an idea. Please run the command
sudo cat $(find /sys -name ssb_sprom)
and send me that long string of hex digits that follow.
Thanks,
Larry
date: Wed, 23 Apr 2008 02:13:57 GMT
author: Larry Finger
|
Re: ubunty wifi: cant acquire IP address
"Larry Finger" wrote in message
news:FXwPj.233674$cQ1.162054@bgtnsc04-news.ops.worldnet.att.net...
> David wrote:
>> "Larry Finger" wrote in message
>> news:e5vPj.120439$D_3.55473@bgtnsc05-news.ops.worldnet.att.net...
>>> Ben Bacarisse wrote:
>>>> "David" <dave@antispam.invalid> writes:
>>>>
>>>>> "Ben Bacarisse" wrote in message
>>>>> news:87bq41eghm.fsf@bsb.me.uk...
>>>>>> "David" <dave@antispam.invalid> writes:
>>>>>>
>>>>>> <snip>
>>>>>>> 5.iwlist scan gives:
>>>>>>> --------------------
>>>>>>> wlan0 Scan completed :
>>>>>>> Cell 01 - Address: 00:18:4D:49:2C:0E
>>>>>>> ESSID:"sally000"
>>>>>>> Mode:Master
>>>>>>> Channel:5
>>>>>>> Frequency:2.432 GHz (Channel 5)
>>>>>>> Quality=81/100 Signal level=-45 dBm Noise
>>>>>>> level=-68
>>>>>>> dBm
>>>>>>> Encryption key:on
>>>>>>> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6
>>>>>>> Mb/s
>>>>>>> 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36
>>>>>>> Mb/s
>>>>>>> 48 Mb/s; 54 Mb/s
>>>>>>> Extra:tsf=00000005d64ca233
>>>> <snip>
>>>>>>> ---------------------------
>>>> <snip>
>>>>>>> wlan0 IEEE 802.11g ESSID:"sally000"
>>>>>>> Mode:Managed Frequency:2.432 GHz Access Point:
>>>>>>> 00:18:4D:49:2C:0E
>>>>>>> Tx-Power=27 dBm
>>>>>>> Retry min limit:7 RTS thr:off Fragment thr=2346 B
>>>>>>> Encryption key:A7C3-E7FF-5E
>>>>>>> Link Quality:0 Signal level:0 Noise level:0
>>>>>>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>>>>>>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>>> David - please ignore most of the "advice" that you are getting. These
>>> guys don't have the slightest idea what is going on.
>>>
>>> Your iwconfig output will not show any signal, noise, or link quality
>>> until it actually authenticates. If you are using NetworkManager with a
>>> normal configuration, then the presence of a ESSID name and/or an Access
>>> Point MAC indicates that the device has associated with the AP.
>>>
>>> Please send the output of 'dmesg | grep wlan0'.
>>>
>>> Larry
>>
>> Here is sudo dmesg | grep wlan0
>>
>> [ 128.781880] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>> [ 364.328612] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>>
>
> These results give me an idea. Please run the command
>
> sudo cat $(find /sys -name ssb_sprom)
>
> and send me that long string of hex digits that follow.
>
> Thanks,
>
> Larry
Hi Larry,
You may have noticed I am in the UK and it was after 3am when I gave up last
night. So just seen your message.
The cmd gives:
014000001300371720430080020002000010001800000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF0F007466A59AFFFFFFFFFFFFFFFFFFFFFFFFFFFF4510A01277FBACFEFFFFFFFF3C000000000000003E000D00FFFF00000000000000000194
I feel we are now in the land of voodoo. FYI I'm not a computer pro just an
amateur willing to learn and who hates giving up.
Thanks once again for your support.
Dave
date: Wed, 23 Apr 2008 10:21:57 +0100
author: David lid
|
Re: ubunty wifi: cant acquire IP address
"Larry Finger" wrote in message
news:FUwPj.233661$cQ1.100201@bgtnsc04-news.ops.worldnet.att.net...
> David wrote:
>> Still not at all sure I understand what this means so looks like I will
>> need to spend a lot of tomorrow reading up about it all. I also now see
>> that some articles say I should use b43 and others b43-legacy as I have
>> rev 3 of the card. Very very confusing and certainly not what I was
>> hoping of Ubuntu 's new release.
>> Thanks for giving me a point in (hopefully) the right direction.
>
> Your card uses b43 and not b43legacy. In fact, the ssb driver looks at the
> PHY revision of your card, and loads the correct driver. If you had a
> BCM4306 rev 2, the it would need b43legacy. I know that is correct as I'm
> the one who converted bcm43xx into b43legacy!
>
> Did you build the kernel you are running, or are you using the one that
> Ubuntu built? If the latter, I understand why the appropriate debugging
> options have not been set. I have been trying to get Ubuntu to set the
> debugging options for a long time, but the idiots don't seem to get the
> word!
>
> If you built your own keernel, then you need to run 'make xconfig' and
> select the debugging options.
>
> Larry
I was going by some of what I had read. Most did say use b43 but some
articles said b43-legacy for rev3. Now I know for sure it one less variable.
Some even said use bcm43xx or ndiswrapper but I felt this to be giving up.
I have nver built a kernel in my life so am running 2.6.24-16-generic at the
mo. But had same probs with the beta release and 2.6.24-others
Also I used the b43 in ubuntu initially but also tried building my own but
no difference.
The positive side of all this is that it's usually the best way to learn how
thongs work.
Cheers
Dave
date: Wed, 23 Apr 2008 10:33:26 +0100
author: David lid
|
Re: ubunty wifi: cant acquire IP address
David wrote:
> "Larry Finger" wrote in message
>>
>> sudo cat $(find /sys -name ssb_sprom)
>>
>> and send me that long string of hex digits that follow.
>>
>> Thanks,
>>
>> Larry
>
> Hi Larry,
>
> You may have noticed I am in the UK and it was after 3am when I gave up last
> night. So just seen your message.
>
> The cmd gives:
> 014000001300371720430080020002000010001800000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF0F007466A59AFFFFFFFFFFFFFFFFFFFFFFFFFFFF4510A01277FBACFEFFFFFFFF3C000000000000003E000D00FFFF00000000000000000194
>
> I feel we are now in the land of voodoo. FYI I'm not a computer pro just an
> amateur willing to learn and who hates giving up.
>
> Thanks once again for your support.
We are in the land of voodoo. That string of digits is the dump of the
SPROM on the device. The translation of the interesting parts of it are:
SPROM(0x04, Subsytem product ID) = 0x0013
SPROM(0x06, Subsystem vendor ID) = 0x1737
SPROM(0x08, PCI Product ID) = 0x4320
SPROM(0x38, High 16 bits of Boardflags) = 0xFFFF
SPROM(0x72, Low 16 bits of Boardflags) = 0x000D
SPROM(0x48, MAC address for 802.11b/g) = 00:0f:66:74:9a:a5
SPROM(0x4E, MAC address for ethernet) = ff:ff:ff:ff:ff:ff
SPROM(0x54, MAC address for 802.11a) = ff:ff:ff:ff:ff:ff
SPROM(0x5A, Ethernet phy settings (0)) = 0x1F
SPROM(0x5A, Ethernet phy settings (1)) = 0x1F
SPROM(0x5B, et0mdcport) = ON
SPROM(0x5B, et1mdcport) = ON
SPROM(0x5C, Board revision) = 0x05
SPROM(0x5C, Locale / Country Code) = 0x0
SPROM(0x5C, B/G PHY antenna 0 available) = OFF
SPROM(0x5C, B/G PHY antenna 1 available) = ON
SPROM(0x5C, A PHY antenna 0 available) = OFF
SPROM(0x5C, A PHY antenna 1 available) = ON
SPROM(0x74, B/G PHY antenna gain) = 0xFF
SPROM(0x75, A PHY antenna gain) = 0x00
SPROM(0x5E, pa0b0) = 0x12A0
SPROM(0x60, pa0b1) = 0xFB77
SPROM(0x62, pa0b2) = 0xFEAC
SPROM(0x6A, pa1b0) = 0x0000
SPROM(0x6C, pa1b1) = 0x0000
SPROM(0x6E, pa1b2) = 0x0000
SPROM(0x64, LED 0 behaviour) = 0xFF
SPROM(0x65, LED 1 behaviour) = 0xFF
SPROM(0x66, LED 2 behaviour) = 0xFF
SPROM(0x67, LED 3 behaviour) = 0xFF
SPROM(0x68, B/G PHY max powerout) = 0x3C
SPROM(0x69, A PHY max powerout) = 0x00
SPROM(0x70, B/G PHY idle TSSI target) = 0x3E
SPROM(0x71, A PHY idle TSSI target) = 0x00
SPROM(0x7E, SPROM version) = 0x01
Most of this is OK, but we have had some vendors incorrectly coding
the data in the low-order 16 bits of the board flags. To check this
out, I would like you to change one of the routines in the file main.c
for the b43 driver. I am not sure what the path is in your version of
the driver source code. In any case, the routine
b43_bluetooth_coext_enable should be changed from
static void b43_bluetooth_coext_enable(struct b43_wldev *dev)
{
struct ssb_sprom *sprom = &dev->dev->bus->sprom;
u32 hf;
if (!(sprom->boardflags_lo & B43_BFL_BTCOEXIST))
return;
if (dev->phy.type != B43_PHYTYPE_B && !dev->phy.gmode)
return;
hf = b43_hf_read(dev);
if (sprom->boardflags_lo & B43_BFL_BTCMOD)
hf |= B43_HF_BTCOEXALT;
else
hf |= B43_HF_BTCOEX;
b43_hf_write(dev, hf);
//TODO
}
to
static void b43_bluetooth_coext_enable(struct b43_wldev *dev)
{
}
In other words, please remove all content from this routine, then
rebuild the driver. This is not the "correct" fix, but it should let
us test if the board flags are the problem.
Thanks,
Larry
date: Wed, 23 Apr 2008 16:17:03 GMT
author: Larry Finger
|
Re: ubunty wifi: cant acquire IP address
"Larry Finger" wrote in message
news:3iJPj.236670$cQ1.146337@bgtnsc04-news.ops.worldnet.att.net...
> David wrote:
>> "Larry Finger" wrote in message
>>>
>>> sudo cat $(find /sys -name ssb_sprom)
>>>
>>> and send me that long string of hex digits that follow.
>>>
>>> Thanks,
>>>
>>> Larry
>>
>> Hi Larry,
>>
>> You may have noticed I am in the UK and it was after 3am when I gave up
>> last night. So just seen your message.
>>
>> The cmd gives:
>> 014000001300371720430080020002000010001800000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF0F007466A59AFFFFFFFFFFFFFFFFFFFFFFFFFFFF4510A01277FBACFEFFFFFFFF3C000000000000003E000D00FFFF00000000000000000194
>>
>> I feel we are now in the land of voodoo. FYI I'm not a computer pro just
>> an amateur willing to learn and who hates giving up.
>>
>> Thanks once again for your support.
>
> We are in the land of voodoo. That string of digits is the dump of the
> SPROM on the device. The translation of the interesting parts of it are:
>
> SPROM(0x04, Subsytem product ID) = 0x0013
> SPROM(0x06, Subsystem vendor ID) = 0x1737
> SPROM(0x08, PCI Product ID) = 0x4320
> SPROM(0x38, High 16 bits of Boardflags) = 0xFFFF
> SPROM(0x72, Low 16 bits of Boardflags) = 0x000D
> SPROM(0x48, MAC address for 802.11b/g) = 00:0f:66:74:9a:a5
> SPROM(0x4E, MAC address for ethernet) = ff:ff:ff:ff:ff:ff
> SPROM(0x54, MAC address for 802.11a) = ff:ff:ff:ff:ff:ff
> SPROM(0x5A, Ethernet phy settings (0)) = 0x1F
> SPROM(0x5A, Ethernet phy settings (1)) = 0x1F
> SPROM(0x5B, et0mdcport) = ON
> SPROM(0x5B, et1mdcport) = ON
> SPROM(0x5C, Board revision) = 0x05
> SPROM(0x5C, Locale / Country Code) = 0x0
> SPROM(0x5C, B/G PHY antenna 0 available) = OFF
> SPROM(0x5C, B/G PHY antenna 1 available) = ON
> SPROM(0x5C, A PHY antenna 0 available) = OFF
> SPROM(0x5C, A PHY antenna 1 available) = ON
> SPROM(0x74, B/G PHY antenna gain) = 0xFF
> SPROM(0x75, A PHY antenna gain) = 0x00
> SPROM(0x5E, pa0b0) = 0x12A0
> SPROM(0x60, pa0b1) = 0xFB77
> SPROM(0x62, pa0b2) = 0xFEAC
> SPROM(0x6A, pa1b0) = 0x0000
> SPROM(0x6C, pa1b1) = 0x0000
> SPROM(0x6E, pa1b2) = 0x0000
> SPROM(0x64, LED 0 behaviour) = 0xFF
> SPROM(0x65, LED 1 behaviour) = 0xFF
> SPROM(0x66, LED 2 behaviour) = 0xFF
> SPROM(0x67, LED 3 behaviour) = 0xFF
> SPROM(0x68, B/G PHY max powerout) = 0x3C
> SPROM(0x69, A PHY max powerout) = 0x00
> SPROM(0x70, B/G PHY idle TSSI target) = 0x3E
> SPROM(0x71, A PHY idle TSSI target) = 0x00
> SPROM(0x7E, SPROM version) = 0x01
>
> Most of this is OK, but we have had some vendors incorrectly coding the
> data in the low-order 16 bits of the board flags. To check this out, I
> would like you to change one of the routines in the file main.c for the
> b43 driver. I am not sure what the path is in your version of the driver
> source code. In any case, the routine b43_bluetooth_coext_enable should be
> changed from
>
> static void b43_bluetooth_coext_enable(struct b43_wldev *dev)
> {
> struct ssb_sprom *sprom = &dev->dev->bus->sprom;
> u32 hf;
>
> if (!(sprom->boardflags_lo & B43_BFL_BTCOEXIST))
> return;
> if (dev->phy.type != B43_PHYTYPE_B && !dev->phy.gmode)
> return;
>
> hf = b43_hf_read(dev);
> if (sprom->boardflags_lo & B43_BFL_BTCMOD)
> hf |= B43_HF_BTCOEXALT;
> else
> hf |= B43_HF_BTCOEX;
> b43_hf_write(dev, hf);
> //TODO
> }
>
> to
>
> static void b43_bluetooth_coext_enable(struct b43_wldev *dev)
> {
> }
>
> In other words, please remove all content from this routine, then rebuild
> the driver. This is not the "correct" fix, but it should let us test if
> the board flags are the problem.
>
> Thanks,
>
> Larry
Larry,
I searched for a file main.c but can't find one.
When I search for b43 I get these results
/lib/firmware/b43
and several (5 in all) under
/lib/modules/2.6.24/kernel/drivers/net/wireless/b43
and also /usr/share/b43-fwcutter
b43-legacy etc
But nowhere can I find a "main.c" file
Am I being stupid here?
Cheers
date: Wed, 23 Apr 2008 19:20:57 +0100
author: David lid
|
Re: ubunty wifi: cant acquire IP address
David wrote:
>
> I searched for a file main.c but can't find one.
> When I search for b43 I get these results
> /lib/firmware/b43
> and several (5 in all) under
> /lib/modules/2.6.24/kernel/drivers/net/wireless/b43
> and also /usr/share/b43-fwcutter
> b43-legacy etc
>
> But nowhere can I find a "main.c" file
> Am I being stupid here?
> Cheers
Did you rebuild the b43 driver? Was that from source, or did you just
link the b43 objects against your kernel? If from source, the file
should be in the directory with the source files. If you linked from
object files, please get me the ls output from that directory.
Larry
date: Wed, 23 Apr 2008 18:30:52 GMT
author: Larry Finger
|
Re: ubunty wifi: cant acquire IP address
On Tue, 22 Apr 2008 16:46:11 +0100, David wrote:
> Running Ubuntu 8.04 (Hardy Heron) on a desktop PC using (or trying to) a
> Linksys WMP54G PCI wifi card (that uses a Broadcom BCM4306 chipset.)
> Trying to connect to a Netgear DG834 adsl router. It works using windows
> xp just fine.
> It doesn't in Ubuntu no matter what I seem to do, althugh it's fine
> using a wired connection.
David, having read through this thread I think you are spending more time
on this than is worthwhile. Just buy a cheap USB wifi dongle from an ebay
seller for about a fiver. This will almost certainly use the zd1211rw
kernel module and will Just Work. Life's too short :-)
Paul
date: Wed, 23 Apr 2008 20:24:21 +0000 (UTC)
author: Paul Sherwin
|
Re: ubunty wifi: cant acquire IP address
"Paul Sherwin" wrote in message
news:fuo5tl$alc$1$8302bc10@news.demon.co.uk...
> On Tue, 22 Apr 2008 16:46:11 +0100, David wrote:
>
>> Running Ubuntu 8.04 (Hardy Heron) on a desktop PC using (or trying to) a
>> Linksys WMP54G PCI wifi card (that uses a Broadcom BCM4306 chipset.)
>> Trying to connect to a Netgear DG834 adsl router. It works using windows
>> xp just fine.
>> It doesn't in Ubuntu no matter what I seem to do, althugh it's fine
>> using a wired connection.
>
> David, having read through this thread I think you are spending more time
> on this than is worthwhile. Just buy a cheap USB wifi dongle from an ebay
> seller for about a fiver. This will almost certainly use the zd1211rw
> kernel module and will Just Work. Life's too short :-)
>
> Paul
Hi Paul,
I hate it when some thing that is "supposed" to work doesn't but I think you
are correct.
Some folk here have been very helpful but the bottom line seems to be that
unless one picks the right wifi device it can be hell.
I do have an AsusTek WL-167g USB stick (uses rt73 drivers) which again is
supposed to work but I haven't had any luck with it either so far.
Tried that tonight, along with another PC even, but the same old c**p.
Okay...I'll take your advise.... so now the question is do you (or anyone
else here) have the name of a particular model of usb stick that uses said
kernel module and that you know works well with Ubuntu Hardy.
I did a quick google and came up with a few candidates but also saw several
bug reports even with zd1211rw and Ubuntu. So I assume that it's not just a
matter of what basic chip set each manufacturer uses but also how well they
implement their design.
Cheers
Dave
date: Wed, 23 Apr 2008 22:05:34 +0100
author: David lid
|
Re: ubunty wifi: cant acquire IP address
"David" <dave@antispam.invalid> wrote in message
news:480fa4a3$0$26085$db0fefd9@news.zen.co.uk...
>
> "Paul Sherwin" wrote in message
> news:fuo5tl$alc$1$8302bc10@news.demon.co.uk...
>> On Tue, 22 Apr 2008 16:46:11 +0100, David wrote:
>>
>>> Running Ubuntu 8.04 (Hardy Heron) on a desktop PC using (or trying to) a
>>> Linksys WMP54G PCI wifi card (that uses a Broadcom BCM4306 chipset.)
>>> Trying to connect to a Netgear DG834 adsl router. It works using windows
>>> xp just fine.
>>> It doesn't in Ubuntu no matter what I seem to do, althugh it's fine
>>> using a wired connection.
>>
>> David, having read through this thread I think you are spending more time
>> on this than is worthwhile. Just buy a cheap USB wifi dongle from an ebay
>> seller for about a fiver. This will almost certainly use the zd1211rw
>> kernel module and will Just Work. Life's too short :-)
>>
>> Paul
>
> Hi Paul,
> I hate it when some thing that is "supposed" to work doesn't but I think
> you are correct.
> Some folk here have been very helpful but the bottom line seems to be that
> unless one picks the right wifi device it can be hell.
>
> I do have an AsusTek WL-167g USB stick (uses rt73 drivers) which again is
> supposed to work but I haven't had any luck with it either so far.
> Tried that tonight, along with another PC even, but the same old c**p.
>
> Okay...I'll take your advise.... so now the question is do you (or anyone
> else here) have the name of a particular model of usb stick that uses said
> kernel module and that you know works well with Ubuntu Hardy.
> I did a quick google and came up with a few candidates but also saw
> several bug reports even with zd1211rw and Ubuntu. So I assume that it's
> not just a matter of what basic chip set each manufacturer uses but also
> how well they implement their design.
>
> Cheers
> Dave
>
Just got wifi working using my USB stick (AsusTek WL-167g) this is using
Gutsy and another PC so it's back to the original PC and Heron later to
check it will work there. But SUCCESS.
Seemed to work using bog standard network-manager and after doing:
sudo ifdown wlan0
then ifup wlan0
Still interested in any recommendations from those who have "real"
experience of actual PCI cards (prefer those) or USB sticks that work with
Ubuntu 8.04.
Thanks for the input.
cheers
dave
date: Wed, 23 Apr 2008 22:54:59 +0100
author: David lid
|
Re: ubunty wifi: cant acquire IP address
"Larry Finger" wrote in message
news:wfLPj.237149$cQ1.60732@bgtnsc04-news.ops.worldnet.att.net...
> David wrote:
>>
>> I searched for a file main.c but can't find one.
>> When I search for b43 I get these results
>> /lib/firmware/b43
>> and several (5 in all) under
>> /lib/modules/2.6.24/kernel/drivers/net/wireless/b43
>> and also /usr/share/b43-fwcutter
>> b43-legacy etc
>>
>> But nowhere can I find a "main.c" file
>> Am I being stupid here?
>> Cheers
>
> Did you rebuild the b43 driver? Was that from source, or did you just link
> the b43 objects against your kernel? If from source, the file should be in
> the directory with the source files. If you linked from object files,
> please get me the ls output from that directory.
>
> Larry
>
>
Larry, as I am a novice at linux and wifi so have been struggling to
understand all this and as I had spent too much time trying to get this to
work I decided to use a USB wifi stick I had and it worked. I do appreciate
your help however.
Cheers
Dave
date: Wed, 23 Apr 2008 22:58:13 +0100
author: David lid
|
Re: ubunty wifi: cant acquire IP address
David wrote:
> Larry, as I am a novice at linux and wifi so have been struggling to
> understand all this and as I had spent too much time trying to get this to
> work I decided to use a USB wifi stick I had and it worked. I do appreciate
> your help however.
> Cheers
I'm a little disappointed that you bailed out at this point. I think
we were close to a solution, but I guess you have other things to do.
We'll just have to wait for some other user to have the same difficulty.
I have one further question. In your very first message, you stated
"Tried latest "restricted" Broadcom drivers in Ubuntu and even
compiled them myself to check." Where did you get those drivers. I
looked all over the Ubuntu web site without success. I have even
loaded Ubuntu 8.04-rc onto my machine, but I don't find anything for
"restricted" Broadcom anywhere in the package manager.
Larry
date: Thu, 24 Apr 2008 00:27:38 GMT
author: Larry Finger
|
Re: ubunty wifi: cant acquire IP address
"Larry Finger" wrote in message
news:_tQPj.238410$cQ1.179447@bgtnsc04-news.ops.worldnet.att.net...
> David wrote:
>> Larry, as I am a novice at linux and wifi so have been struggling to
>> understand all this and as I had spent too much time trying to get this
>> to work I decided to use a USB wifi stick I had and it worked. I do
>> appreciate your help however.
>> Cheers
>
> I'm a little disappointed that you bailed out at this point. I think we
> were close to a solution, but I guess you have other things to do. We'll
> just have to wait for some other user to have the same difficulty.
>
> I have one further question. In your very first message, you stated "Tried
> latest "restricted" Broadcom drivers in Ubuntu and even compiled them
> myself to check." Where did you get those drivers. I looked all over the
> Ubuntu web site without success. I have even loaded Ubuntu 8.04-rc onto my
> machine, but I don't find anything for "restricted" Broadcom anywhere in
> the package manager.
>
> Larry
Hi Larry,
It's 1:33am here in the UK and another late night. It was after 3am when I
gave up last night. Hence my chickening out and deciding to try to get my
USB stick to work. Which it now does and I've tried it in 2 different
machines now with 7.10 and 8.04rd versions of Ubuntu.
But back to Broadcom.
I agree I was not clear in describing what I had done in my first
post...mainly being a noob and npt knowing the terminology too well.
What I did was initially use "b43" that comes with Ubuntu 8.04 (which they
variously term restricted or proprietary drivers.)
If you install the PCI card they pop up in System>Administration>Hardware
Drivers.
When that didn't work I found
http://linuxwireless.sipsolutions.net/en/users/Drivers/b43 and used their
recipe:
---------------------------------------
If you are using the b43 driver from linux-2.6.24, follow these
instructions.
Use version 011 of b43-fwcutter.
Download, extract the b43-fwcutter tarball and build it:
wget http://bu3sch.de/b43/fwcutter/b43-fwcutter-011.tar.bz2
tar xjf b43-fwcutter-011.tar.bz2
cd b43-fwcutter-011
make
cd ..
Use version 4.80.53.0 of Broadcom's proprietary driver.
Download and extract the firmware from this driver tarball:
export FIRMWARE_INSTALL_DIR="/lib/firmware"
wget http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2
tar xjf broadcom-wl-4.80.53.0.tar.bz2
cd broadcom-wl-4.80.53.0/kmod
sudo ../../b43-fwcutter-011/b43-fwcutter -w "$FIRMWARE_INSTALL_DIR"
wl_apsta.o
-----------------------------
Since getting wifi running with the USB stick I did just venture back and
installed the Broadcom card back into another PC running windows XP and
found that
I couldn't get it to run on that either. So now I am wondering if the card
went bad during all my experimentation!
If after all that you still would like me to try to get it working then I am
willing to give it a last shot, especially as you have been so helpful to
me.
But you'll need to spell out what you want me to do. Please just let me
know.
Thanks again.
Dave
(going to bed now)
date: Thu, 24 Apr 2008 01:53:18 +0100
author: David lid
|
Re: ubunty wifi: cant acquire IP address
David wrote:
> Since getting wifi running with the USB stick I did just venture back and
> installed the Broadcom card back into another PC running windows XP and
> found that
> I couldn't get it to run on that either. So now I am wondering if the card
> went bad during all my experimentation!
>
> If after all that you still would like me to try to get it working then I am
> willing to give it a last shot, especially as you have been so helpful to
> me.
> But you'll need to spell out what you want me to do. Please just let me
> know.
> Thanks again.
> Dave
> (going to bed now)
Now I understand. When you said you downloaded and recompiled the
driver, I thought you meant b43. What you downloaded are the MIPS
drivers that contain the firmware, and then recompiled b43-fwcutter -
the program that extracts the firmware from those drivers.
With a Debian-based system, it is very difficult to compile your own
kernel. On openSUSE, which I use, it is as easy as getting the source,
configuring the options for devices and debugging, and the issuing the
commands 'make' and 'sudo make modules_install install' and a new
kernel is built and installed.
When Ubuntu has a kernel with version number 2.6.25.2 or later, your
interface should work "out of the box" except for the firmware.
Broadcom has not, and will not, cooperate with our project. As a
result, we do not have permission to distribute their firmware, which
is why you have to download a piece of their code and extract the
firmware from it.
Larry
date: Thu, 24 Apr 2008 05:21:57 GMT
author: Larry Finger
|
Re: ubunty wifi: cant acquire IP address
"Unruh" wrote in message
news:_LtPj.1499$XI1.30@edtnps91...
> "David" <dave@antispam.invalid> writes:
>
>>Running Ubuntu 8.04 (Hardy Heron) on a desktop PC using (or trying to) a
>>Linksys WMP54G PCI wifi card (that uses a Broadcom BCM4306 chipset.)
>
> Broadcom tends to be a bastard of a card for linux.
That's _really_ unfortunate as it is a very popular built in card!
date: Thu, 24 Apr 2008 08:42:12 +0100
author: jasee
|
Re: ubunty wifi: cant acquire IP address
"Larry Finger" wrote in message
news:VNUPj.239484$cQ1.87318@bgtnsc04-news.ops.worldnet.att.net...
> David wrote:
>
>> Since getting wifi running with the USB stick I did just venture back and
>> installed the Broadcom card back into another PC running windows XP and
>> found that
>> I couldn't get it to run on that either. So now I am wondering if the
>> card went bad during all my experimentation!
>>
>> If after all that you still would like me to try to get it working then I
>> am willing to give it a last shot, especially as you have been so helpful
>> to me.
>> But you'll need to spell out what you want me to do. Please just let me
>> know.
>> Thanks again.
>> Dave
>> (going to bed now)
>
> Now I understand. When you said you downloaded and recompiled the driver,
> I thought you meant b43. What you downloaded are the MIPS drivers that
> contain the firmware, and then recompiled b43-fwcutter - the program that
> extracts the firmware from those drivers.
>
> With a Debian-based system, it is very difficult to compile your own
> kernel. On openSUSE, which I use, it is as easy as getting the source,
> configuring the options for devices and debugging, and the issuing the
> commands 'make' and 'sudo make modules_install install' and a new kernel
> is built and installed.
>
> When Ubuntu has a kernel with version number 2.6.25.2 or later, your
> interface should work "out of the box" except for the firmware. Broadcom
> has not, and will not, cooperate with our project. As a result, we do not
> have permission to distribute their firmware, which is why you have to
> download a piece of their code and extract the firmware from it.
>
> Larry
My apologies Larry if I misled you (un-intentially) with an incorrect
explanation. I trust I'll get better at using the correct terminology as I
gain in experience.
All the best
Dave
date: Thu, 24 Apr 2008 09:35:26 +0100
author: David lid
|
Re: ubunty wifi: cant acquire IP address
David wrote:
> Running Ubuntu 8.04 (Hardy Heron) on a desktop PC using (or trying to) a
> Linksys WMP54G PCI wifi card (that uses a Broadcom BCM4306 chipset.)
> Trying to connect to a Netgear DG834 adsl router.
> It works using windows xp just fine.
> It doesn't in Ubuntu no matter what I seem to do, althugh it's fine using a
> wired connection.
It's probably that smelly 'avahi' stuff. (zeroconfig crap).
Just toss that away and handle your wifi through more conventional ways
(/etc/network and stuff, or just through your networking applet in gnome).
date: Thu, 24 Apr 2008 11:46:51 +0200
author: Jurgen Haan
|
Re: ubunty wifi: cant acquire IP address
"Jurgen Haan" wrote in message
news:4810570a$0$14358$e4fe514c@news.xs4all.nl...
> David wrote:
>> Running Ubuntu 8.04 (Hardy Heron) on a desktop PC using (or trying to) a
>> Linksys WMP54G PCI wifi card (that uses a Broadcom BCM4306 chipset.)
>> Trying to connect to a Netgear DG834 adsl router.
>> It works using windows xp just fine.
>> It doesn't in Ubuntu no matter what I seem to do, althugh it's fine using
>> a
>> wired connection.
>
> It's probably that smelly 'avahi' stuff. (zeroconfig crap).
> Just toss that away and handle your wifi through more conventional ways
> (/etc/network and stuff, or just through your networking applet in gnome).
Hello Jurgen,
Spent too much midnigth oil on trying to get it to work so now using an asus
USB stick.
But FWIW how do i "just toss away" the avahi stuff.
Delete it from /etc/network/..??
Cheers
dave
date: Thu, 24 Apr 2008 11:02:13 +0100
author: David lid
|
Re: ubunty wifi: cant acquire IP address
Jurgen Haan wrote:
> David wrote:
>> Running Ubuntu 8.04 (Hardy Heron) on a desktop PC using (or trying to) a
>> Linksys WMP54G PCI wifi card (that uses a Broadcom BCM4306 chipset.)
>> Trying to connect to a Netgear DG834 adsl router.
>> It works using windows xp just fine.
>> It doesn't in Ubuntu no matter what I seem to do, althugh it's fine using | |
