Wireless switch doesn't work after upgrade/dist-upgrade
After the last upgrade/dist-upgrade the wireless switch (Fn-F2) on my
Asus W7j doesn't seem to be able to switch on the wireless anymore, it
does still togle the bluetooth but at max only lets the wireless led blink.
I can get the wireless led on with echo 1 > /proc/acpi/asus/wled, but
that doesn't make the card work
When I cat that file before and after pressing the switch combination it
always says 0.
I'm using debian lenny, atm 2.6.22-3-amd64, wireless card:
06:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG
Network Connection (rev 02)
Also, the switch seems to work during the startup, untill just before gdm starts (but it probably isn't gdm, since that didn't start at first because I had to reinstall nvidia module, and then the wireless switch didn't work either)
During poweroff sequence it seems to work also
This seems particulary strange to me
Any ideas where to look for a solution?
Sorry to ask something like that, but did you check if the connection actually worked while the LED didn't? I read something similar just recently - it appears to be happening sometimes with Intel chipsets... (I think it was Ubuntu and not Debian, though).
If that's not the case I'd say look at the output of lsmod, iwconfig and possibly ifconfig to determine to what extend things work or don't...
Yes, it doesn't work.
lsmod |grep 3945 gives:
ipw3945 209316 1
ieee80211 38600 1 ipw3945
firmware_class 15360 1 ipw3945
lo no wireless extensions.
eth1 no wireless extensions.
eth2 no wireless extensions.
eth1 Link encap:Ethernet HWaddr 00:18:f3:6a:60:9d
inet addr:192.168.1.103 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::218:f3ff:fe6a:609d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14224 errors:0 dropped:0 overruns:0 frame:0
TX packets:11826 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:12664098 (12.0 MiB) TX bytes:1611779 (1.5 MiB)
Interrupt:17 Base address:0xc000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:700 (700.0 B) TX bytes:700 (700.0 B)
I'm connected through eth1 now, this is wired.
Normally (and as it seems to do so on startup), the wireless connection is renamed to eth2 (from eth0 if I'm not mistaking)
Any ideas where it might go wrong?
Oh, it seems I was mistaking, the bluetooth doesn't seem to switch either atm...
The renaming (and reordering) of the devices is strange enough as it is (where's eth0 - have you done ifup eth0 just for the sake of trying); anyhow, the kernel modules are there, and complete, at that (including firmware) - did you check if the modules are okay (they sure should be)?
Whatever happens here seems to happen early - try dmesg | grep eth (you can also grep for "ipw"). But frankly, I don't see why something like this should happen. At least, kernel-wise, everything seems to be okay, networking's basically working... Maybe some hardware recognition conflict (too many tools in place)? Does all other hardware work as expected?
ifup eth0 doesn't do anything:
Output of dmesg:
udev: renamed network interface eth0 to eth1
udev: renamed network interface eth0 to eth2
Is it correct that it seems to rename the same interface twice?
What I also tried:
Thanks for the sugestions already
Oh, and I didn't notice anything else not working (except the webcam, that didn't work to start with), only a warning sometimes about a low capacity of my battery and that it might be broken, which is very strange. And my processors seem to run at 1Mhz at the moment, but this just adjusts itself when I open more processes, so no worries there.
One odd thing is that my bar that shows the open programs minimized (gnome-panel?), seems to stop working sometimes... quite annoying.
Yes, udev acts strangely: It seems to "recognize" the Intel chipset as a RealTek one if I'm not mistaken. After that, it tries to rearrange devices - "working" ones first (eth0 can't go to eth1 since that place is already taken by the ethernet device, thus landing the wireless one on eth2). That at least can be seen as "logical" (why it should be of any help remains a mystery). The whole point seems to be that at the moment of network configuration, the kernel module for the Intel chipset is still missing. However installing it later should have made the chipset work - but maybe the device is still "configured" by the wrong driver - lsmod | grep rtl may reveal that. If it's the case, try modprobe -r the module ("rt(l)8168(b)" something?).
lsmod | grep rtl doesn't give anything, just to be sure I did lsmod:
Oh, wait, the realtek is the wired connection it seems:
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
06:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
Okay, now I'm definitely at a loss. You're right about the wired/wireless chipsets, so from what you report, everything *appears* to be in order. But since it doesn't work, it isn't :/ Besides, the Realtek NIC's module is "r8169", which is a bit confusing, but seems to be correct.
The only hunch I've left is that there's something wrong with the module loading on boot up, but it beats me why this should happen or not be corrected later, respectively. I'm afraid we'll have to ask someone else to sort this out... I'm sorry.
No problem, a big thank you for trying to help!
Is there anyone with other sugestions? The problem still remains
eth2 says it is up and listening but has received no dhcpoffers.
Just a thought: do you have MAC address filtering enabled on your router? I get messages like that if I have to change out a card and forget to add the new MAC address to the router's list.
It's not a router problem, I can't even get the card to show up in iwconfig. If it would be a router problem, the card would show up in iwconfig and I could scan for routers with iwlist. At least that's what makes sense to me...
Thanks already, more sugestions still welcome
|All times are GMT -5. The time now is 11:18 PM.|