Same problem here with an Acer Travelmate 4000. The upgrade from Feisty was flawless but the problem first appeared after a hard restart: eth1 was disabled and "cat /sys/bus/pci/drivers/ipw2200/*/rf_kill" reported 2 instead of 0. This has always happened since the Dapper days (eth1 disabled after a hard restart, that is) but it wasn't a problem since the wireless switch button always worked so pressing it solved the issue and wireless always worked again.
However, in Gutsy the button doesn't work at all so the only way to make wireless work again is by using the acerhk module (editing /proc/driver/acerhk/wirelessled ); the weird thing is that even after the acerhk module is loaded and wireless is running, the button only works when switching off wireless, it doesn't switch it on again, therefore a new editing of /proc/driver/acerhk/wirelessled is needed to make wireless work again. It is needless to say that this is a regression from old versions and the only solution available at the moment is a hack. [EMAIL PROTECTED]:~% uname -a Linux laptop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux [EMAIL PROTECTED]:~% lspci | grep -i "wireless" 02:04.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05) [EMAIL PROTECTED]:~% cat /proc/driver/acerhk/info Acer hotkeys version 0.5.34 Model(Type) : TravelMate 4000(Dritek) request handler : 0xc00fddc0 CMOS index : not available kernel polling : active autoswitch wlan : disabled use of Dritek EC: enabled -- ipw2200 kill switch disables but won't enable (Asus M5200A) https://bugs.launchpad.net/bugs/119835 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
