Wireless issues on the HP nc6000 [SOLVED]

[edgevision]

Following this guide:

http://gentoo-wiki.com/HOWTO_Install_Gentoo_On_Hp_Compaq_NC6000_Laptop

KNetworkManager scans and successfully detects available wireless networks. However, when attempting to connect to a network it will not progress past 28%, with the message Activation stage: Configuring device.

Help please?

[WarraWarra]

Knetwork manager is unhappy because of below. I ended up disabling knetwork manager and only do it manually.

Problem = /etc/resolv.conf is empty or wrong "nameserver 192.168.34.1"

Fix = as root in terminal:
"net-setup"

Then follow the options to the best of what you know or suspect and then once complete type "ifconfig"

Problem might still be in 3.4 loop2 = mDNSResponder or avahi is uninstalled or unhappy and both clash with each other when trying to update.

Might be able to work without mDNSResponder but not without avahi last time I tried. Think there is a fix / update for this problem already not sure.

Helpfull link's:
Here is some info that can help as well.
http://www.gentoo.org/doc/en/handbook/h ... art1_chap3

And 8B in below link:
http://www.gentoo.org/doc/en/handbook/h ... art1_chap8

[praxis]

thx i was having the same problems and couldnt figure out why. using 3.4loop3.
i finally said heck with it. iwlist and iwconfig do the job.

[anfernio]

I am having the same problem with my Cisco Aironet 340 wireless card.

I do not know anything about linux, so those documentation files are like another language to me. Can someone point me toward some simple instructions?

My wireless card has lights flashing on it, so it is not broken, and it is working right now on another OS. However, it is not assigned an IP address, and KnetworkManager will look for a network and stop at 28 percent also.

Any help would be greatly appreciated. I will be waiting here impatiently for the next release of Sabayon.

[edgevision]

KNetworkManager is still young and appears to have this problem quite often. Just try to be patient with it, even cards that work perfectly (my girlfriend's laptop uses the ipw2200 drivers on an Intel Pro) still run into this every once in a while.

anfernio, what is the the output of the following (as root in a console):

Code: Select all

lspci | grep net

[WarraWarra]

I am having the same problem with my Cisco Aironet 340 wireless card.

I do not know anything about linux, so those documentation files are like another language to me. Can someone point me toward some simple instructions?

My wireless card has lights flashing on it, so it is not broken, and it is working right now on another OS. However, it is not assigned an IP address, and KnetworkManager will look for a network and stop at 28 percent also.

Any help would be greatly appreciated. I will be waiting here impatiently for the next release of Sabayon.

Temporary fix:
Easiest quickest way to get it working:
Open terminal program and type "su" + password you specified for root user.
If you forgot it type "sudo passwd" and type in new password for root user .

As root user type "net-setup" and follow the questions with answers you know works for your wifi config.

then type "ifconfig" and it should show a 192.168.*.* type adress for the wlan0 or eth1 or whatever name it assigned to the wireless device.

I presume that the flashing light = it already has a working driver for it but no IP. To check driver "lspci"

Next fire up firefox and use the internet.

If still o internet and the ip router / wifi is correct then check /etc/resolv.conf as this file should have the dns name servers ip for your ISP internet service provider.

nameserver 24.119.x.x
nameserver 209.33.77.x

or something looking like this in resolv.conf

Might be able to have the wifi working automatically with knetworkmanager thingy next to the time top right of screen next time you boot or not. If not just run "net-setup" again.

Hope this helps.

[edgevision]

For anyone still having trouble, you might want to have a look at this. It appears that Avahi and mDNSResponder are conflicting packages. When mDNSResponder is unmerged and Avahi is re-emerged with compatibility useflags for mDNSResponder, I am no longer experiencing wireless issues with KNetworkManager.

[anfernio]

Sorry it took so long to respond to this post.

I tried what you told me to do WarraWarra, but it did not work.

lspci | grep net
0a:08.0 Ethernet controller: Intel Corporation PRO/100 VE Network Connection (rev 02)

That is what the output is even after I try everything to get my laptop to use the wireless card.

Also, /etc/resolv.conf has nothing in it.

The funny thing is that the card will partially work on the liveDVD. Some websites will show up in a web browser, but most won't. I thought that perhaps it was just random information stored in a cache, but I was actually able to log into myspace and among all of the jibberish I saw, I was able to see names of people that I know.

I'm going to try what edgevision said, hopefully that will work.

[WarraWarra]

Not 100% sure but your lspci is showing the onboard cable lan connection.

If this is the case then you would need to load a driver / module for the wifi card.

For 2200 intel card "modprobe ipw2200" for intel 3945 card "modprobe ipw3945" for broadcom 43?? type card's "modprobe bcm43xx"

Alternatively you can use "ndiswrapper --help" and then browse to the windows install folder for the card then get the something.inf to work with ndiswrapper.

How:
"ndiswrapper -i something.inf" replacing something with actual driver name.
Mine = "ndiswrapper -i bcmwl5.inf"
Then type "ndiswrapper -m"
then "ndiswrapper -ma"
then "ndiswrapper -mi"

Next to load ndiswrapper module "modprobe ndiswrapper" and it will load.

To check if it loaded "lsmod" and look for the ndiswrapper with some numbers next to it. = happy / loaded.

Once ndiswrapper is loaded you should be able to run "net-setup" and then see the card as wlan0 or something similar with a name and some model number next to it.

PS> if using lsmod and seeing ndiswrapper before adding the windows driver you would have to unload and reload the ndiswrapper module after installing the windows driver.

" modprobe - r ndiswrapper " = unload and reload = "modprobe ndiswrapper"
Or
"modprobe -r ndiswrapper ; modprobe ndiswrapper" unload + load in one action

Livedvd:
It has most drivers for the wifi card. Might just need to manually load the drive / module again.
The resolv.conf on the livedvd had the last time I checked a ip in the resolv.conf some dns in europe not sure.

If you need a dns then this ip's would work likely.
http://www.dyndns.com/services/dns/recu ... howto.html
Bottom of page by linux/unix = example.

Code: Select all

nameserver 63.208.196.113
nameserver 63.208.196.114


This looks like a lot of info but it is actually very easy end quick.

[anfernio]

It doesn't seem like anything is going to work for me. I think I'm going to give up for now. I'll see if I can get another wireless card. Thanks for all of the help though.