Topic: [SOLVED] Wireless dead (hardware problem?)

Dear all,
I usually work with a cable, but today I switched on for the first time the wireless of the laptop where I recently moved to CB. Actually, I tried to switch it on, because the wireless does not come to life. I have a HP 8440p, which should come with an intel wi-fi natively supported by the linux kernel (as far as I understand, at least). On the laptop, I have a button which is a hardware switch to turn on or off the wireless, but this is not working anymore, apparently. I checked in the bios and the wireless chip is activated there.
I had it switched off during installation, so maybe it wasn't detected at that time, and some packages are missing? How can I test if this is a hardware problem?

Thanks!

Last edited by sambarluc (2012-02-08 13:42:15)

Re: [SOLVED] Wireless dead (hardware problem?)

Im assuming from a quick google search, the wifi card you got is the Intel Centrino 6200.   Either way, for intel wireless check out:

http://wiki.debian.org/iwlagn

Im not the wireless guru here, but sounds like you dont have it enabled.  From the debian wiki seems it is not compilied into the kernel, just a module that you either dont have or is not loading.   Follow the advice on the wiki link I provided, its pretty simple.  If it aint working then post so a real wifi expert can help you, or post that it worked and mark solved.  Hopefully this does the trick.

Intel Pentium4-2.40GHZ RAM-1008.3MiB CrunchBang Sid Linux-3.2-6.slh.3-aptosid-686

Re: [SOLVED] Wireless dead (hardware problem?)

Plug in the ethernet cable. Install rfkill and do

sudo rfkill list

Post output here. Also, hit the switch back and forth and post output of

dmesg|tail -n20

Re: [SOLVED] Wireless dead (hardware problem?)

sudo rfkill list:

0: hp-wifi: Wireless LAN
    Soft blocked: yes
    Hard blocked: yes
1: hp-bluetooth: Bluetooth
    Soft blocked: yes
    Hard blocked: yes
2: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: yes

dmesg after switching on and off wireless:

[   15.911091] Bluetooth: RFCOMM socket layer initialized
[   15.911094] Bluetooth: RFCOMM ver 1.11
[   15.960881] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   15.960883] Bluetooth: BNEP filters: protocol multicast
[   15.987492] Bridge firewalling registered
[   18.365455] e1000e 0000:00:19.0: irq 42 for MSI/MSI-X
[   18.421262] e1000e 0000:00:19.0: irq 42 for MSI/MSI-X
[   18.422558] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   19.963076] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx
[   19.963084] e1000e 0000:00:19.0: eth0: 10/100 speed: disabling TSO
[   19.964339] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   30.556678] eth0: no IPv6 routers present
[  489.482640] atkbd serio0: Unknown key pressed (translated set 2, code 0xf8 on isa0060/serio0).
[  489.482646] atkbd serio0: Use 'setkeycodes e078 <keycode>' to make it known.
[  489.489666] atkbd serio0: Unknown key released (translated set 2, code 0xf8 on isa0060/serio0).
[  489.489672] atkbd serio0: Use 'setkeycodes e078 <keycode>' to make it known.
[  491.171115] atkbd serio0: Unknown key pressed (translated set 2, code 0xf8 on isa0060/serio0).
[  491.171121] atkbd serio0: Use 'setkeycodes e078 <keycode>' to make it known.
[  491.178122] atkbd serio0: Unknown key released (translated set 2, code 0xf8 on isa0060/serio0).
[  491.178129] atkbd serio0: Use 'setkeycodes e078 <keycode>' to make it known.

Any idea? I'm really lost in this kind of things...

Re: [SOLVED] Wireless dead (hardware problem?)

rfkill unblock all

should get rid of any soft-blocks. the hard-block is a different thing i think... you might want to check your bios for a wifi-switch or something.
i had this same type of problem when moving back and forth between Linux and Windows in a dual-boot situation? are you in such a situation?

Re: [SOLVED] Wireless dead (hardware problem?)

Yes!

rfkill unblock 

was the right trick. I do not have a dual boot system, but I suspect that the problem started when I first switched from fedora gnome to fedora lxde, and then to crunchbang. Anyway, now it's working (and the wi-fi button too).
Thanks!

Re: [SOLVED] Wireless dead (hardware problem?)

great! i always thought rfkill couldnt unblock a hardware switch, but apparently it works anyway.

Re: [SOLVED] Wireless dead (hardware problem?)

Random babbling ... probably wrong ... Oh well ... tongue

Check in network manager, the applet thingy to see if your wireless is even there. Don't quote, cuz am not an IT guru ( I just play one on an internet forum of two. lol) Wireless networking isn't always just ON, had a Dell lappy, had to push one of the F buttons to even enable the wireless networking, think it was F2, F8 or F10 can't remember. So may want to check whatever model you have of lappy about enabling wireless kinda thing.

Think it makes sense, that if either your wireless isn't enabled or there's no connection for it defined in the network manager = no wireless goodness in #!, or errrr anything else. wink



Doh !!! Read the OP, per usual ... Imma dork ! Dang it ! For the most part nevermind, arghhhhh. Note 2 self: Start reading stuff before posting. Would probably help reduce my magnificent dorkish post ratio !!! tongue

Last edited by CBizgreat! (2012-02-09 22:02:17)

Some common cbiz abbreviations. This will save me time and yet @ same time tell folks what the babble is supposed to mean.

Vll ! = ( Viva la gnu/Linux !)    Vl#!! = ( Viva la #! !)    Last but not least, UD ... OD ! = ( Use Debian ... or die !) tongue