Sabayon 5.0 - Atheros AR5001

[schweickism]

Hi,

I just installed Sabayon 5.0 and so far everything's great except I can't get wireless working.

I saw the article on the new B43 driver here: http://wiki.sabayonlinux.org/index.php? ... b43_driver

That article says to run lspci | grep b43 and that makes me think this B43 driver is for a specific wireless card and maybe I should be following similar directions but not with B43?

I ran lspci which shows me this line:
Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)

So I did some searching and found this thread viewtopic.php?f=52&t=16574 but skiman is in a different situation since he upgraded the kernel and I am working off a fresh install of the latest version, so I am not sure which of the updates he talked about I would already have or whether that post is even relevant at all?

A little guidance here would be greatly appreciated, as I'm a little wary of messing this up after having failed miserably at getting wireless to work on another distro.

Thanks!

[micia]

can you provide the output of:

Code: Select all

iwconfig


as root?

Your card should work with the ath_pci module.

[schweickism]

This is the output:

Code: Select all

lo        no wireless extensions.

eth0      no wireless extensions.

wmaster0  no wireless extensions.

wlan0     IEEE 802.11bg  ESSID:""
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated
          Tx-Power=20 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

[micia]

Your wireless card is recognized (as you can see, it is the wlan0 device), you have to just setup the network.
NetworkManager is installed by default, the GUI for it depends on your Desktop Environment,
nm-applet if you are on Gnome, plasma-widget-networkmanager or something like it if you are on KDE4,
open up one of those GUIs, select the appropriate network, setup the encryption key (if any)
and try to connect to it.

[schweickism]

It doesn't connect though. It shows the available networks and everything, but when I try to get on one it always times out. The computer is dual booted with Windows, so I know the hardware works and I have the right password and stuff. I've even tried several other networks and I haven't been able to connect except with a wired connection.

I'm using KDE 4 and there is an icon in the system tray that appeared since the first time I started up that says "Network Management" and can be accessed from the System Settings as well. It isn't very verbose, but it never connects and just comes back up with the dialog where you enter what type of network it is, encryption type, password, etc. I know I'm putting in the right details because I can get it to work on other OS's.

There is another thing called wicd, and when I open it I get an error message that says "Could not connect to wicd's D-Bus interface. Check the wicd log for error messages." When I try to connect it comes back with "Connection failed: Unable to get IP Address."

Here is what turns up in the wicd.log file:

Code: Select all

2009/11/17 17:46:29 :: ---------------------------
2009/11/17 17:46:29 :: wicd initializing...
2009/11/17 17:46:29 :: ---------------------------
2009/11/17 17:46:29 :: wicd is version 1.6.2.2 463
2009/11/17 17:46:29 :: did not find backend in configuration, setting default external
2009/11/17 17:46:29 :: setting backend to external
2009/11/17 17:46:29 :: trying to load backend external
2009/11/17 17:46:29 :: successfully loaded backend external
2009/11/17 17:46:30 :: trying to load backend external
2009/11/17 17:46:30 :: successfully loaded backend external
2009/11/17 17:46:30 :: Automatically detected wireless interface wlan0
2009/11/17 17:46:30 :: did not find wireless_interface in configuration, setting default wlan0
2009/11/17 17:46:30 :: setting wireless interface wlan0
2009/11/17 17:46:30 :: automatically detected wired interface eth0
2009/11/17 17:46:30 :: did not find wired_interface in configuration, setting default eth0
2009/11/17 17:46:30 :: setting wired interface eth0
2009/11/17 17:46:30 :: did not find wpa_driver in configuration, setting default wext
2009/11/17 17:46:30 :: setting wpa driver wext
2009/11/17 17:46:30 :: did not find always_show_wired_interface in configuration, setting default False
2009/11/17 17:46:30 :: did not find use_global_dns in configuration, setting default False
2009/11/17 17:46:30 :: setting use global dns to False
2009/11/17 17:46:30 :: did not find global_dns_1 in configuration, setting default None
2009/11/17 17:46:30 :: did not find global_dns_2 in configuration, setting default None
2009/11/17 17:46:30 :: did not find global_dns_3 in configuration, setting default None
2009/11/17 17:46:30 :: did not find global_dns_dom in configuration, setting default None
2009/11/17 17:46:30 :: did not find global_search_dom in configuration, setting default None
2009/11/17 17:46:30 :: setting global dns
2009/11/17 17:46:30 :: global dns servers are None None None
2009/11/17 17:46:30 :: domain is None
2009/11/17 17:46:30 :: search domain is None
2009/11/17 17:46:30 :: did not find auto_reconnect in configuration, setting default True
2009/11/17 17:46:30 :: setting automatically reconnect when connection drops True
2009/11/17 17:46:30 :: did not find debug_mode in configuration, setting default False
2009/11/17 17:46:30 :: did not find wired_connect_mode in configuration, setting default 1
2009/11/17 17:46:30 :: did not find signal_display_type in configuration, setting default 0
2009/11/17 17:46:30 :: did not find dhcp_client in configuration, setting default 0
2009/11/17 17:46:30 :: Setting dhcp client to 0
2009/11/17 17:46:30 :: did not find link_detect_tool in configuration, setting default 0
2009/11/17 17:46:30 :: did not find flush_tool in configuration, setting default 0
2009/11/17 17:46:30 :: did not find sudo_app in configuration, setting default 0
2009/11/17 17:46:30 :: did not find prefer_wired in configuration, setting default False
2009/11/17 17:46:30 :: Wireless configuration file not found, creating...
2009/11/17 17:46:30 :: Wired configuration file not found, creating a default...
2009/11/17 17:46:30 :: Creating wired profile for wired-default
2009/11/17 17:46:30 :: chmoding configuration files 0600...
2009/11/17 17:46:30 :: chowning configuration files root:root...
2009/11/17 17:46:30 :: Using wireless interface...wlan0
2009/11/17 17:46:30 :: Using wired interface...eth0
2009/11/17 17:46:35 :: Autoconnecting...
2009/11/17 17:46:35 :: No wired connection present, attempting to autoconnect to wireless network
2009/11/17 17:46:36 :: Unable to autoconnect, you'll have to manually connect
2009/11/17 17:46:37 :: did not find window_width in configuration, setting default -1
2009/11/17 17:46:37 :: did not find window_height in configuration, setting default -1
2009/11/17 17:50:07 :: Connecting to wireless network *****
2009/11/17 17:50:07 :: Putting interface down
2009/11/17 17:50:07 :: Releasing DHCP leases...
2009/11/17 17:50:07 :: Setting false IP...
2009/11/17 17:50:07 :: Stopping wpa_supplicant
2009/11/17 17:50:07 :: Flushing the routing table...
2009/11/17 17:50:07 :: Putting interface up...
2009/11/17 17:50:07 :: Attempting to authenticate...
2009/11/17 17:50:07 :: Running DHCP
2009/11/17 17:50:07 :: dhcpcd: version 5.0.6 starting
2009/11/17 17:50:07 ::
2009/11/17 17:50:07 :: cat: /var/run/dhcpcd/ntp.conf.wlan0: No such file or directory
2009/11/17 17:50:07 ::
2009/11/17 17:50:07 :: dhcpcd: wlan0: waiting for carrier
2009/11/17 17:50:07 ::
2009/11/17 17:50:47 :: dhcpcd: timed out
2009/11/17 17:50:47 ::
2009/11/17 17:50:47 :: DHCP connection failed
2009/11/17 17:50:47 :: exiting connection thread
2009/11/17 17:50:48 :: Sending connection attempt result dhcp_failed
2009/11/17 17:50:59 :: Autoconnecting...
2009/11/17 17:50:59 :: No wired connection present, attempting to autoconnect to wireless network
2009/11/17 17:51:00 :: Unable to autoconnect, you'll have to manually connect
2009/11/17 17:51:04 :: Autoconnecting...
2009/11/17 17:51:04 :: No wired connection present, attempting to autoconnect to wireless network
2009/11/17 17:51:05 :: Unable to autoconnect, you'll have to manually connect
2009/11/17 17:51:09 :: Autoconnecting...
2009/11/17 17:51:09 :: No wired connection present, attempting to autoconnect to wireless network
2009/11/17 17:51:10 :: Unable to autoconnect, you'll have to manually connect
2009/11/17 17:54:29 :: Autoconnecting...
2009/11/17 17:54:29 :: No wired connection present, attempting to autoconnect to wireless network
2009/11/17 17:54:30 :: Unable to autoconnect, you'll have to manually connect
2009/11/17 17:57:54 :: Autoconnecting...
2009/11/17 17:57:54 :: No wired connection present, attempting to autoconnect to wireless network
2009/11/17 17:57:55 :: Unable to autoconnect, you'll have to manually connect
2009/11/17 18:01:19 :: Autoconnecting...
2009/11/17 18:01:19 :: No wired connection present, attempting to autoconnect to wireless network
2009/11/17 18:01:20 :: Unable to autoconnect, you'll have to manually connect


[micia]

When using wicd ensure not to be using NetworkManager too, or bad things will happen.
In order to be sure about it you should consider to close the application that use it.
Remove NetworkManager using:

Code: Select all

rc-update del NetworkManager


and set wicd to start automatically using:

Code: Select all

rc-update add wicd default


Reboot and try again, I hope this helps.

[schweickism]

Still no luck. However, I don't get the "Unable to connect to D-Bus" message when using wicd anymore--progress?

[micia]

Yes, that is a progress, is the network configured on wicd? (encryption and so on)

[schweickism]

Yes, I put in the details for my home network and it wouldn't connect. Now I'm at school which uses PEAP and WPA-2 Enterprise encryption. On NetworkManager it was clear how to connect to that (even though it didn't work), but on wicd the best I see is "Find a hidden network" and when I type in the ESSID it just shows "No wireless networks found." However, the school does have an unprotected network that is used only for displaying instructions for how to connect (which are all for Windows users, so they are no help anyway) and I was actually able to connect to that today. Maybe it just has to do with the protection?

[schweickism]

Well I've messed around with it a bit and am still unable to get the wireless to connect on any network with a password. Unfortunately though, I needed my laptop to be able to use wireless for a meeting, so I installed another distro over the Sabayon partition. But I do hope to come back to Sabayon again later though.