=== asac_ is now known as asac | ||
dholbach | hi guys | 07:03 |
---|---|---|
dholbach | maybe you can help me debugging why the wifi kill switch on my IBM X40 does not work any more (intrepid)? | 07:03 |
dholbach | I can load the ipw2100 module without problems, but I can't get the wifi LED to light up at all | 07:04 |
amitk | dholbach: probably best to wait for rtg to show up. He has been following the led issues closely. | 07:05 |
dholbach | amitk: it worked nicely like two days ago :) | 07:05 |
amitk | huh | 07:05 |
dholbach | amitk: I can't get wireless to work at all | 07:05 |
amitk | dholbach: does dmesg say anything about kill switch active? | 07:06 |
dholbach | I dunno if it's a hardware thing or if it just broke in intrepid, but I don't know how to debug it | 07:06 |
dholbach | daniel@lovegood:~$ dmesg | grep -i kill | 07:06 |
dholbach | daniel@lovegood:~$ | 07:06 |
dholbach | maybe I chose the wrong words... what I meant is that FN-F5 right now just toggles bluetooth on and off, it doesn't do anything regarding to wifi | 07:08 |
amitk | dholbach: what does 'modprobe -r ipw2100; modprobe ipw2100' do in dmesg? | 07:09 |
amitk | also, find /sys/ -name "*kill*" | 07:10 |
dholbach | +[ 6603.769069] ieee80211_crypt: unregistered algorithm 'NULL' | 07:10 |
dholbach | +[ 6603.799013] ieee80211_crypt: registered algorithm 'NULL' | 07:10 |
dholbach | +[ 6603.811687] ieee80211: 802.11 data/management/control stack, git-1.1.13 | 07:10 |
dholbach | +[ 6603.811699] ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com> | 07:10 |
dholbach | +[ 6603.824297] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2 | 07:10 |
dholbach | +[ 6603.824309] ipw2100: Copyright(c) 2003-2006 Intel Corporation | 07:10 |
dholbach | /sys/devices/platform/thinkpad_acpi/rfkill | 07:10 |
dholbach | /sys/devices/platform/thinkpad_acpi/rfkill/rfkill0 | 07:10 |
dholbach | /sys/class/rfkill | 07:10 |
dholbach | /sys/class/rfkill/rfkill0 | 07:10 |
dholbach | /sys/module/rfkill | 07:10 |
amitk | dholbach: what do the two rfkill0 files contain? | 07:11 |
dholbach | hang on, they're directories :) | 07:12 |
dholbach | amitk: http://paste.ubuntu.com/70342/ | 07:15 |
dholbach | seems they only contain bluetooth stuff :-/ | 07:15 |
amitk | hmm | 07:16 |
amitk | dholbach: most times the Fn+F5 is tri-state or quad-state, BT WLAN 0 0, 0 1, 1 0 and 1 1 | 07:17 |
dholbach | *nod* | 07:17 |
amitk | how does it work on yours? | 07:18 |
dholbach | I think it's quad-state too | 07:18 |
amitk | dholbach: and I guess you have cycled through all those states? | 07:23 |
dholbach | yes | 07:23 |
dholbach | check out my discussion with slangasek on #ubuntu-devel (just the last lines) | 07:24 |
=== alex_jon1 is now known as alex_joni | ||
=== lifeless_ is now known as lifeless | ||
=== rametux is now known as RameTux | ||
=== rametux_ is now known as RameTux | ||
=== rametux is now known as RameTux | ||
=== dholbach_ is now known as dholbach | ||
dholbach | amitk: seems like my issue is not fixed yet :-/ | 14:30 |
dholbach | [12405.928353] ipw2100: ***** PARITY ERROR INTERRUPT !!!! | 14:30 |
dholbach | [12405.928386] ipw2100: ***** PARITY ERROR INTERRUPT !!!! | 14:30 |
dholbach | [12405.928401] ipw2100: ***** PARITY ERROR INTERRUPT !!!! | 14:30 |
dholbach | [13512.268457] ipw2100: eth1: write index mismatch | 14:30 |
dholbach | [13512.270513] ipw2100: ***** PARITY ERROR INTERRUPT !!!! | 14:30 |
dholbach | [13512.516413] ipw2100: eth1: write index mismatch | 14:30 |
dholbach | [21216.305009] ipw2100: eth1: ipw2100_verify failed: -5 | 14:30 |
dholbach | [21216.305072] ipw2100: eth1: Failed to power on the adapter. | 14:30 |
dholbach | [21216.305077] ipw2100: eth1: Failed to start the firmware. | 14:30 |
dholbach | [21309.349497] ipw2100 0000:02:02.0: PCI INT A disabled | 14:30 |
dholbach | this makes me guess that it's a hardware problem :-/ | 14:30 |
rtg | dholbach: 'PARITY ERROR INTERRUPT' certainly makes it seem like a HW error. Can you see the same result with a Hardy Live CD? | 14:32 |
dholbach | rtg: the X40 does not have a CD drive :) | 14:33 |
amitk | dholbach: we know for a fact now that your card has dust puppy issues | 14:33 |
dholbach | rtg: I had this http://people.ubuntu.com/~dholbach/img_2498.jpg this morning | 14:33 |
amitk | dholbach: tried giving it a shower? :) | 14:33 |
dholbach | amitk: I tried that like 2 years ago, when I emptied a glass of water into the keyboard while the laptop was running | 14:33 |
dholbach | I think I need to live with the idea that the hardware is slowly dying | 14:34 |
amitk | dholbach: you wouldn't happen to have a can of compressed air handy? It is useful to clean the motherboard... | 14:34 |
dholbach | amitk: no, unfortunately not, but I could try it | 14:35 |
mjg59 | dholbach: An 1802 error means the card didn't even manage to give its PCI configuration data to the BIOS | 14:37 |
mjg59 | Or corrupted it in the process | 14:37 |
mjg59 | Take the card out, attempt to reseat it? | 14:38 |
=== rametux__ is now known as RameTux | ||
dholbach | mjg59: did that this morning - it worked until now (6-7h) | 15:23 |
=== rametux_ is now known as RameTux | ||
mjg59 | dholbach: Mm. Might be a bad contact, or might be the card dying. | 15:28 |
dholbach | mjg59: yeah, the machine is 4+ years old now :) | 15:29 |
=== fdd-0 is now known as fdd | ||
Jodoog | Hi :) | 19:21 |
Jodoog | I know it was planned for 2.6.28 in order to get Lenovo's APS working without need for a patch...but has 2.6.28-rc4 put general disc protection directly into the libata driver? | 19:21 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!