David wrote:
> "Larry Finger" <Larry.Finger@lwfinger.net> 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