dhclient output, ideas?

[igocancun]

Hi mates, I-m running kubuntu dapper rc1 and i find it quite nice, but i-m having trouble with my wireless which i didn-t have before. Here are the outputs i tried linuxant but no success either.

eth0 output
eth0 IEEE 802.11b/g ESSIDff/any Nickname:"Broadcom 4318"
Mode:Managed Access Point: Invalid Bit Rate=1 Mb/s
RTS thrff Fragment thrff
Encryption keyff
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


dhclient output
root@protoslap:/home/drprotos# dhclient
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

SIOCSIFFLAGS: No such file or directory
SIOCSIFFLAGS: No such file or directory
Listening on LPF/eth1/00:0f:b0:7a:29:98
Sending on LPF/eth1/00:0f:b0:7a:29:98
Listening on LPF/eth0/00:14:a5:23:15:31
Sending on LPF/eth0/00:14:a5:23:15:31
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
receive_packet failed on eth0: Network is down
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
send_packet: Network is down


Any ideas TIA

[eah]

Re: dhclient output, ideas?

I have the same basic problem with Dapper Drake install on my hp dv8000 laptop. nic ans wlan work fine (wlan needs ndiswrapper) in breezy. neither work in dapper.

ndiswrapper isnt in dapper by default and i cant get it w/o nic alive.

i noticed there are two 8139 modules. the 8139 recommends 8139too be used (from dmesg).

could it be the nic drivers be bad? has anyone gotten broadcom wlan and realtec nic up and running?

I noticed that if I try to use the Network app in System Settings, clicking on Enable activates the (wired) NIC for a second, then the NIC drops to disabled. dmesg and /var/log/messages say nothing.

thanks,

eah

[lexxonnet]

Re: dhclient output, ideas?

Interesting, I remember getting the same output on my friends laptop.. and I finally did manage to solve it by removing every possible instance of the NDISWrapper driver, and installing the native BCM43xx drivers.

I'm sure there's a howto on the wiki... Ah... here you go...
https://wiki.ubuntu.com/WifiDocs/Dri...=%28BCM43xx%29

Just in case, what I did was to remove all traces of NDISWrapper:

sudo modprobe -r bcmwl5
sudo rmmod ndiswrapper
sudo apt-get remove ndiswrapper-utils
sudo rm -r /etc/ndiswrapper/
sudo rm -r /etc/modprobe.d/ndiswrappe

Then,

sudo apt-get install bcm43xx-fwcutter

Then I grabbed the drivers off her windows installation, and applied them with the fwcutter. There is an automated way of doing this off the net though... as can be found in the wiki... have a read, and see if it works...

p.s. It still doesn't work too well with wpasupplicant... I even tried it with 0.5, and it didn't work well...

[eah]

Re: dhclient output, ideas?

the problem with mine is the wired nic does the same thing. i can't geth wlan or wired lan to activate. i get "function not implemented" from ifconfig up. it's one of the strangest things - i've always had linux network driver just work.