Hi everyone!
I'm fighting with my wireless adapter over 6 months now and I always loose. The battle begun when I updated my Lucid to kernel 2.6.32-22. Since then my wireless WG111v3 USB adapter is unreliable; sometimes is operational and sometimes not - there is no logical pattern to predict this. Mostly a reboot is required to get it work but sometimes 2 or 3 reboots in a row.
So here's what it looks like when it's not working:
dmesg output regarding adapter:
Note that wireless switch thing is OFF, but my adapter has no switch of any kind on it.
So I found out that kernels above 2.6.32-21 include rfkill as a component that controls wireless adapters state, but mostly for laptops. Then I checked some rfkill commands and tried:
I assume that this is that 'rfkill mask 2' in dmesg output - binary bits: soft(0) hard(1) = 2. My guess is that mask should be 0. Then I tried:
Unfortunately that does nothing; wlan0 is still Hard blocked. If I use udevadm monitor with command above I get:
Is that where is the problem, ie. the adapter is unblocked(KERNEL) then blocked(UDEV) again?
When adapter is not blocked by rfkill, if I unplug it and then plug it in again it gets blocked and therefore is unusable.
Some senior linux users said that this could be a kernel bug and only a kernel recompilation will fix but that is beyond my abilities.
I hoped that kernel developers would be aware of that problem and had it fixed in kernel 2.6.32-23 but the problem still persists. Maybe it's not the kernel bug then. Maybe it can be solved by a simple change of one line in some config file, I don't know.
I started to learn linux 8 months ago so I'm very green and all my resource of knowledge is from internet, which is offlimits if my adapter is not working.
And by saying that I beg for tolerance If I missed to write something crucial.
Thanks.
I'm fighting with my wireless adapter over 6 months now and I always loose. The battle begun when I updated my Lucid to kernel 2.6.32-22. Since then my wireless WG111v3 USB adapter is unreliable; sometimes is operational and sometimes not - there is no logical pattern to predict this. Mostly a reboot is required to get it work but sometimes 2 or 3 reboots in a row.
So here's what it looks like when it's not working:
Code:
# sudo ifconfig wlan0 up SIOCSIFFLAGS: Unknown error 123
Code:
phy0: hwaddr 00:1e:2a:xx:xx:xx, RTL8187BvE V0 + rtl8225z2, rfkill mask 2 rtl8187: wireless switch is off
So I found out that kernels above 2.6.32-21 include rfkill as a component that controls wireless adapters state, but mostly for laptops. Then I checked some rfkill commands and tried:
Code:
# rfkill list 0: wlan0 Soft blocked: No Hard blocked: Yes
Code:
# sudo rfkill unblock 0
Code:
KERNEL[1273271499.836087] change /devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2:1.0/ieee80211/phy0/rfkill0 (rfkill) UDEV [1273271499.836347] change /devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2:1.0/ieee80211/phy0/rfkill0 (rfkill)
When adapter is not blocked by rfkill, if I unplug it and then plug it in again it gets blocked and therefore is unusable.
Some senior linux users said that this could be a kernel bug and only a kernel recompilation will fix but that is beyond my abilities.
I hoped that kernel developers would be aware of that problem and had it fixed in kernel 2.6.32-23 but the problem still persists. Maybe it's not the kernel bug then. Maybe it can be solved by a simple change of one line in some config file, I don't know.
I started to learn linux 8 months ago so I'm very green and all my resource of knowledge is from internet, which is offlimits if my adapter is not working.
And by saying that I beg for tolerance If I missed to write something crucial.
Thanks.
Comment