-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Morning all, i've been trying to make wireless work on my Asus EeePC, but no luck.
Below is some diagnostic output:
[root@localhost ~]# ifconfig eth0 Link encap:Ethernet HWaddr 00:1F:C6:D8:E9:9F ~ inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0 ~ inet6 addr: fe80::21f:c6ff:fed8:e99f/64 Scope:Link ~ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ~ RX packets:97 errors:0 dropped:0 overruns:0 frame:0 ~ TX packets:106 errors:0 dropped:0 overruns:0 carrier:2 ~ collisions:0 txqueuelen:1000 ~ RX bytes:24327 (23.7 KiB) TX bytes:0 (0.0 b) ~ Memory:fbfc0000-fc000000
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:1604 errors:0 dropped:0 overruns:0 frame:0 ~ TX packets:1604 errors:0 dropped:0 overruns:0 carrier:0 ~ collisions:0 txqueuelen:0 ~ RX bytes:80360 (78.4 KiB) TX bytes:80360 (78.4 KiB)
wlan0 Link encap:Ethernet HWaddr 00:15:AF:A7:87:5F ~ UP BROADCAST MULTICAST MTU:1500 Metric:1 ~ RX packets:0 errors:0 dropped:0 overruns:0 frame:0 ~ TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 ~ collisions:0 txqueuelen:1000 ~ RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wmaster0 Link encap:UNSPEC HWaddr 00-15-AF-A7-87-5F-F4-FF-00-00-00-00-00-00-00-00 ~ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ~ RX packets:0 errors:0 dropped:0 overruns:0 frame:0 ~ TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 ~ collisions:0 txqueuelen:1000 ~ RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
[root@localhost ~]# lsmod | grep ath ath5k 111240 0 mac80211 174312 1 ath5k cfg80211 24584 2 ath5k,mac80211
[root@localhost ~]# tail -f /var/log/messages Oct 13 10:06:26 localhost NetworkManager: <info> wlan0: driver supports SSID scans (scan_capa 0x01). Oct 13 10:06:26 localhost NetworkManager: <info> Found new 802.11 WiFi device 'wlan0'. Oct 13 10:06:26 localhost NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_15_af_a7_87_5f_0 Oct 13 10:06:30 localhost NetworkManager: <info> (wlan0): device state change: 1 -> 2 Oct 13 10:06:30 localhost NetworkManager: <info> (wlan0): bringing up device. Oct 13 10:06:30 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready Oct 13 10:06:30 localhost NetworkManager: <info> (wlan0): preparing device. Oct 13 10:06:30 localhost NetworkManager: <info> (wlan0): deactivating device. Oct 13 10:06:30 localhost NetworkManager: <info> (wlan0): device state change: 2 -> 3 Oct 13 10:06:30 localhost NetworkManager: <info> (wlan0): supplicant interface state change: 1 -> 2.
[root@localhost ~]# rpm -q kernel kernel-2.6.26.5-45.fc9.i686
Now everything looks good except the line Oct 13 10:06:30 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
I have another laptop with Atheros card with the same software configuration (F9 + latest updates) and it just works fine while on the eeepc NM doesn't detect any wireless networks. I wasn't able to find any useful information on the web except installing mad-wifi which I think is not needed with the latest kernel anymore. Any help is appreciated.
Thanks, Alexander.
On Mon, Oct 13, 2008 at 10:15:49AM +0300, Alexander Todorov wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Morning all, i've been trying to make wireless work on my Asus EeePC, but no luck.
- latest updates) and it just works fine while on the eeepc NM doesn't detect
any wireless networks. I wasn't able to find any useful information on the web except installing mad-wifi which I think is not needed with the latest kernel anymore. Any help is appreciated.
If you mean the 2.6.27-x kernels, you are correct, you will not need MadWifi drivers, though you might have to manually insert the ath5k module.
However, at least one other person, as well as myself, had the following experience with F10 and the Aspire One, which uses the same AR5007EG card. (I'm not really familiar with the Asus line. I assume the 4 gig surf is one of the earlier ones with that card. The newest 901 and 1000 use a Realtek card.)
The card would be recognized, but would only work with unencrypted networks with the live CD. We had to upgrade the kernel before it would work properly.
For what it's worth, though I've had no trouble with the builtin 2.6.27 ath5k driver after the upgrade, some people on the Aspire One forums have found, with Ubuntu at least, that though it would sometimes work, they were better off still using the latest MadWifi snapshots. However, with the 2.6.27 kernels, this shouldn't be necessary. So, you might try that if all else fails. I have a page on it that some folks have found helpful, which goes through the steps of installing the MadWifi drivers (though the page mentions that I haven't found it necessary with 2.6.27) at http://home.nyc.rr.com/computertaijutsu/rhwireless.html#5007
(Although I haven't yet found what sysctl values replace the old ones that got the LED to work. In the 2.6.26 kernels it was dev.wifi.ledpin and dev.wifi.softled.)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Scott Robbins wrote: | If you mean the 2.6.27-x kernels, you are correct, you will not need | MadWifi drivers, though you might have to manually insert the ath5k | module. |
After installing kernel 2.6.27-0.398.rc9.fc10.i686 from Rawhide (+ dependencies) it seems to work (at least iwlist wlan0 scan shows networks available). The problem is now Plymouth which doesn't start GDM. I'll have to debug this a bit more.
Thanks, Alexander.
Alexander Todorov wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Scott Robbins wrote: | If you mean the 2.6.27-x kernels, you are correct, you will not need | MadWifi drivers, though you might have to manually insert the ath5k | module. |
After installing kernel 2.6.27-0.398.rc9.fc10.i686 from Rawhide (+ dependencies) it seems to work (at least iwlist wlan0 scan shows networks available). The problem is now Plymouth which doesn't start GDM. I'll have to debug this a bit more.
Thanks, Alexander. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org
iD8DBQFI8w32hmd3WOiFct4RCqafAJ4tE6x9QzTfsgCdiy3No4bJ+4SSRwCfda6B cQKpd8zbr7gzZ/H5nRayeMQ= =obUY -----END PGP SIGNATURE-----
You can disable kms by adding the nomodeset kernel parameter.
JBG.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Alexander Todorov wrote: | Scott Robbins wrote: | | If you mean the 2.6.27-x kernels, you are correct, you will not need | | MadWifi drivers, though you might have to manually insert the ath5k | | module. | | | | After installing kernel 2.6.27-0.398.rc9.fc10.i686 from Rawhide (+ | dependencies) | it seems to work (at least iwlist wlan0 scan shows networks available). The | problem is now Plymouth which doesn't start GDM. I'll have to debug this | a bit more. |
Upgrading all bits to rawhide fixed it for me. Looks like I didn't pick up some dependencies with the first upgrade.
- -- Alexander.
On Mon, 2008-10-13 at 03:57 -0400, Scott Robbins wrote:
If you mean the 2.6.27-x kernels, you are correct, you will not need MadWifi drivers, though you might have to manually insert the ath5k module.
If you have to manually insert the ath5k module, that is a bug. The module should have a module alias for all pci ids that it supports (and afaik, it does). If you have to manually insert the module, please file a bug in bugzilla with the output of lspci -n for your system and dmesg from before you insert ath5k.
Jeremy
Alexander Todorov wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Morning all, i've been trying to make wireless work on my Asus EeePC, but no luck.
Below is some diagnostic output:
[root@localhost ~]# ifconfig eth0 Link encap:Ethernet HWaddr 00:1F:C6:D8:E9:9F ~ inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0 ~ inet6 addr: fe80::21f:c6ff:fed8:e99f/64 Scope:Link ~ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ~ RX packets:97 errors:0 dropped:0 overruns:0 frame:0 ~ TX packets:106 errors:0 dropped:0 overruns:0 carrier:2 ~ collisions:0 txqueuelen:1000 ~ RX bytes:24327 (23.7 KiB) TX bytes:0 (0.0 b) ~ Memory:fbfc0000-fc000000
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:1604 errors:0 dropped:0 overruns:0 frame:0 ~ TX packets:1604 errors:0 dropped:0 overruns:0 carrier:0 ~ collisions:0 txqueuelen:0 ~ RX bytes:80360 (78.4 KiB) TX bytes:80360 (78.4 KiB)
wlan0 Link encap:Ethernet HWaddr 00:15:AF:A7:87:5F ~ UP BROADCAST MULTICAST MTU:1500 Metric:1 ~ RX packets:0 errors:0 dropped:0 overruns:0 frame:0 ~ TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 ~ collisions:0 txqueuelen:1000 ~ RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wmaster0 Link encap:UNSPEC HWaddr 00-15-AF-A7-87-5F-F4-FF-00-00-00-00-00-00-00-00 ~ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ~ RX packets:0 errors:0 dropped:0 overruns:0 frame:0 ~ TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 ~ collisions:0 txqueuelen:1000 ~ RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
[root@localhost ~]# lsmod | grep ath ath5k 111240 0 mac80211 174312 1 ath5k cfg80211 24584 2 ath5k,mac80211
[root@localhost ~]# tail -f /var/log/messages Oct 13 10:06:26 localhost NetworkManager: <info> wlan0: driver supports SSID scans (scan_capa 0x01). Oct 13 10:06:26 localhost NetworkManager: <info> Found new 802.11 WiFi device 'wlan0'. Oct 13 10:06:26 localhost NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_15_af_a7_87_5f_0 Oct 13 10:06:30 localhost NetworkManager: <info> (wlan0): device state change: 1 -> 2 Oct 13 10:06:30 localhost NetworkManager: <info> (wlan0): bringing up device. Oct 13 10:06:30 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready Oct 13 10:06:30 localhost NetworkManager: <info> (wlan0): preparing device. Oct 13 10:06:30 localhost NetworkManager: <info> (wlan0): deactivating device. Oct 13 10:06:30 localhost NetworkManager: <info> (wlan0): device state change: 2 -> 3 Oct 13 10:06:30 localhost NetworkManager: <info> (wlan0): supplicant interface state change: 1 -> 2.
[root@localhost ~]# rpm -q kernel kernel-2.6.26.5-45.fc9.i686
Now everything looks good except the line Oct 13 10:06:30 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
I have another laptop with Atheros card with the same software configuration (F9
- latest updates) and it just works fine while on the eeepc NM doesn't
detect any wireless networks. I wasn't able to find any useful information on the web except installing mad-wifi which I think is not needed with the latest kernel anymore. Any help is appreciated.
Thanks, Alexander. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org
iD8DBQFI8vWlhmd3WOiFct4RCjNWAJ9gvdTa12LN3qZ6fACpaOGY9ZzGDgCfaQib Xd1UwybNR/TuxJgNlbxTa44= =NR6x -----END PGP SIGNATURE-----
I have a eeePC 702 and it works perfect on FC10 the kernel-2.6.27, I don't know what WiFi the 1000 uses but the eeePC 700 series runs the Atheros AR5007EG wireless, and it won't work in the 2.6.26 kernels FC 8 - 9 . The rpm from Livna will also give you problems. All hardware on my E works perfect on FC10 , most of all the Webcam.
On Mon, Oct 13, 2008 at 08:12:50AM -0400, Jim wrote:
I have a eeePC 702 and it works perfect on FC10 the kernel-2.6.27, I don't know what WiFi the 1000 uses but the eeePC 700 series runs the Atheros AR5007EG wireless, and it won't work in the 2.6.26 kernels FC 8
- 9 .
The rpm from Livna will also give you problems.
The livna rpm usually works, however, from time to time, they fall behind in kernel versions. They were having some issues which are probably fixed by now. (I haven't been running F9 on anything save a workstation which has no wireless, so I haven't kept up.)
The Asus 901 and 1000 (I'm not sure about the 900) are using a Realtek card. Someone on fedoraforums has posted a howto about it, but not having the machine, I have no idea how well it does or doesn't work. There are also articles on the Fedora wiki about the EEE if I'm not mistaken. (However, not having that machine and planning to get an Acer Aspire One, I'm no expert.)