ubuntu-eee-coders team mailing list archive
-
ubuntu-eee-coders team
-
Mailing list archive
-
Message #02272
[Bug 305614] [NEW] WiFi does not connect after reboot unless manually turned off and on again
Public bug reported:
I have reviewed all of the recommended patches to make WiFi (ath0
interface) work onan Asus 900 with Ubuntu EEE 8.4.
Several times I thought I had it working, but as it stands now if I shut
down and then do a reboot, the wifi comes up (blue light on) but there
is no valid connection (WPA) - IP address reported in the 169.XX range.
I can turn off the link using the Fn-F2, then turn it on again, after
which I get a valid DHCP address. It seems that the wireless interfaces
is coming on too early in the boot sequence.
I have not yet tried adding a complete wpa_supplicant.conf solution.
G. Kinal
** Affects: ubuntu-eee
Importance: Undecided
Status: New
--
WiFi does not connect after reboot unless manually turned off and on again
https://bugs.launchpad.net/bugs/305614
You received this bug notification because you are a member of Ubuntu
Eee Coders, which is subscribed to Ubuntu Eee.
Status in Ubuntu Eee: New
Bug description:
I have reviewed all of the recommended patches to make WiFi (ath0 interface) work onan Asus 900 with Ubuntu EEE 8.4.
Several times I thought I had it working, but as it stands now if I shut down and then do a reboot, the wifi comes up (blue light on) but there is no valid connection (WPA) - IP address reported in the 169.XX range.
I can turn off the link using the Fn-F2, then turn it on again, after which I get a valid DHCP address. It seems that the wireless interfaces is coming on too early in the boot sequence.
I have not yet tried adding a complete wpa_supplicant.conf solution.
G. Kinal
Follow ups
References