2009/9/3 Brian J. Mc Hugh <bjmch...@aya.yale.edu>:
> I went in the file /var/log/dmesg and didn't find dhclient.
>
> Does that signify failure?

You don't need to find dhclient in dmesg - the question is, what shows
up in dmesg after ifup calls dhclient?

About the Windows machine problem - try the Windows driver in ndiswrapper.

>
>
> 2009/9/2 Gábor Stefanik <netrolller...@gmail.com>
>>
>> On Wed, Sep 2, 2009 at 11:57 PM, Brian J. Mc Hugh<bjmch...@aya.yale.edu>
>> wrote:
>> > Hi Gábor and Broadcom,
>> >
>> > In essense, my card seems to be receiving signal but transmitting none.
>> >
>> > I was appreciate your help,
>> >
>> > Thanks,
>> > Brian
>> >
>> >
>> > Here are the diagnostics;
>> >
>> > #uname -r
>> > 2.6.26-2-686
>> >
>> > #dmesg | grep b43
>> > [   30.415512] b43-pci-bridge 0000:02:00.0: enabling device (0000 ->
>> > 0002)
>> > [   32.618331] b43-phy0: Broadcom 4318 WLAN found
>> > [   40.118466] input: b43-phy0 as /class/input/input6
>> > [   40.204186] firmware: requesting b43/ucode5.fw
>> > [   40.493492] firmware: requesting b43/pcm5.fw
>> > [   40.677031] firmware: requesting b43/b0g0initvals5.fw
>> > [   40.763606] firmware: requesting b43/b0g0bsinitvals5.fw
>> > [   41.036083] b43-phy0: Loading firmware version 410.2160 (2007-05-26
>> > 15:32:10)
>> > [   42.308852] Registered led device: b43-phy0::tx
>> > [   42.308934] Registered led device: b43-phy0::rx
>> > [   42.309022] Registered led device: b43-phy0::radio
>> >
>> > #lspci -vnn | grep 14e4
>> > 02:00.0 Network controller [0280]: Broadcom Corporation BCM4318
>> > [AirForce
>> > One 54g] 802.11g Wireless LAN Controller [14e4:4318] (rev 02)
>> >
>> > #lspci -nnv | grep -A1 14e4
>> > 02:00.0 Network controller [0280]: Broadcom Corporation BCM4318
>> > [AirForce
>> > One 54g] 802.11g Wireless LAN Controller [14e4:4318] (rev 02)
>> >     Subsystem: Linksys WPC54G-EU version 3 [Wireless-G Notebook Adapter]
>> > [1737:0048]
>> >
>> > #iwlist wlan0 scan
>> > wlan0     Scan completed :
>> >           Cell 01 - Address: 00:17:9A:52:34:2D
>> >                     ESSID:"dlink"
>> >                     Mode:Master
>> >                     Channel:11
>> >                     Frequency:2.462 GHz (Channel 11)
>> >                     Quality=73/100  Signal level=-42 dBm  Noise
>> > level=-63
>> > 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=00000017b3fcb180
>> >
>> > #ifdown wlan0
>> > There is already a pid file /var/run/dhclient.wlan0.pid with pid 1949
>> > killed old client process, removed PID file
>> > Internet Systems Consortium DHCP Client V3.1.1
>> > Copyright 2004-2008 Internet Systems Consortium.
>> > All rights reserved.
>> > For info, please visit http://www.isc.org/sw/dhcp/
>> >
>> > wmaster0: unknown hardware address type 801
>> > wmaster0: unknown hardware address type 801
>> > Listening on LPF/wlan0/00:18:f8:e2:1c:71
>> > Sending on   LPF/wlan0/00:18:f8:e2:1c:71
>> > Sending on   Socket/fallback
>> >
>> > #ifup wlan0
>> > Internet Systems Consortium DHCP Client V3.1.1
>> > Copyright 2004-2008 Internet Systems Consortium.
>> > All rights reserved.
>> > For info, please visit http://www.isc.org/sw/dhcp/
>> >
>> > wmaster0: unknown hardware address type 801
>> > wmaster0: unknown hardware address type 801
>> > Listening on LPF/wlan0/00:18:f8:e2:1c:71
>> > Sending on   LPF/wlan0/00:18:f8:e2:1c:71
>> > Sending on   Socket/fallback
>> > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
>> > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
>> > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
>> > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
>> > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
>> > No DHCPOFFERS received.
>> > No working leases in persistent database - sleeping.
>> >
>> >
>> >
>>
>> What's visible in dmesg after dhclient?
>>
>> Also, to rule out hardware failures - does the card work under
>> Windows? (4318s break rather easily.)
>>
>>
>> --
>> Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
>
>



-- 
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
_______________________________________________
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to