Arch Linux

gtolden

Member

Registered: 2013-07-20

Posts: 13

[Solved]Still can't connect with Realtek RTL8723ae wireless driver

Hi,
I bought a new dell laptop called vostro 8460 with a Atheros AR8161 wired network controller and a Realtek RTL8723ae wireless controller. when I boot into the archiso and ran

ip link

I can only see lo and wlp2s0. since I can see the wireless controller, I ran

wifi-menu wlp2s0

and choose the SSID I want, type in the password, after about 10 seconds of blinking, it said "connnection failed". I didn't save the profile and tried more times to ensure that it wasn't a typo.
As I couldn't connect to wifi at the moment, so I tried to find the solution for my wired controller. After consulting this thread, I installed arch by archboot and reboot into it to install the alx driver, and it worked, I am connected to the wired network now. However, the wifi still doesn't work.

Since I couln't see the enpxxx thing until I installed the proper driver while I can see wlp2s0 all the time, I believe there is a driver for rel8723ae in the kernel. So I tried

wpa_supplicant -i wlp2s0 -c <(wpa_passpharse "my_ssid" "my_pass")

without -B, to see the output, and here it is:

Successfully initialized wpa_supplicant
wlp2s0: Trying to associate with 6c:e8:73:39:37:e0 (SSID='bl601' freq=2437 MHz)
ioctl[SIOCSIWFREQ]: Device or resource busy
wlp2s0: Association request to the driver failed
wlp2s0: Associated with 6c:e8:73:39:37:e0
wlp2s0: Authentication with 6c:e8:73:39:37:e0 timed out.
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=6c:e8:73:39:37:e0 reason=3 locally_generated=1
wlp2s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="bl601" auth_failures=1 duration=10
wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="bl601"
wlp2s0: Trying to associate with 6c:e8:73:39:37:e0 (SSID='bl601' freq=2437 MHz)
ioctl[SIOCSIWFREQ]: Device or resource busy
wlp2s0: Association request to the driver failed
wlp2s0: Associated with 6c:e8:73:39:37:e0
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=6c:e8:73:39:37:e0 reason=0
wlp2s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="bl601" auth_failures=2 duration=20
wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="bl601"
wlp2s0: Trying to associate with 6c:e8:73:39:37:e0 (SSID='bl601' freq=2437 MHz)
ioctl[SIOCSIWFREQ]: Device or resource busy
wlp2s0: Association request to the driver failed
wlp2s0: Associated with 6c:e8:73:39:37:e0
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=6c:e8:73:39:37:e0 reason=0
wlp2s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="bl601" auth_failures=3 duration=20
wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="bl601"
wlp2s0: Trying to associate with 6c:e8:73:39:37:e0 (SSID='bl601' freq=2437 MHz)
ioctl[SIOCSIWFREQ]: Device or resource busy
wlp2s0: Association request to the driver failed
wlp2s0: Associated with 6c:e8:73:39:37:e0
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=6c:e8:73:39:37:e0 reason=0
wlp2s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="bl601" auth_failures=4 duration=20
wlp2s0: CTRL-EVENT-TERMINATING 
.........

before I hit ctrl-c.

So what's the problem please?
Thanks!

gtolden

Last edited by gtolden (2013-07-24 07:52:27)

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,341

Website

Re: [Solved]Still can't connect with Realtek RTL8723ae wireless driver

The device or resource busy suggests one of two things (to me): either there is another network management process running, or the interface is not up.

In either case, the next step is to disable any and all network management services, then follow the manual connection steps on the wireless page of the wiki - wpa_supplicant is not the first step.

EDIT: I'm not suggesting that the manual steps are the only way you should connect - but while troubleshooting, they are the only method that will allow precise determination of which step is failing, while allowing you to check the output (and report it here) from each step.

Last edited by Trilby (2013-07-22 11:08:53)

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

gtolden

Member

Registered: 2013-07-20

Posts: 13

Re: [Solved]Still can't connect with Realtek RTL8723ae wireless driver

Thanks, I will try later. It's bed time for me now...

gtolden

Member

Registered: 2013-07-20

Posts: 13

Re: [Solved]Still can't connect with Realtek RTL8723ae wireless driver

The device or resource busy suggests one of two things (to me): either there is another network management process running, or the interface is not up.

In either case, the next step is to disable any and all network management services, then follow the manual connection steps on the wireless page of the wiki - wpa_supplicant is not the first step.

EDIT: I'm not suggesting that the manual steps are the only way you should connect - but while troubleshooting, they are the only method that will allow precise determination of which step is failing, while allowing you to check the output (and report it here) from each step.

well, I follow the wiki (https://wiki.archlinux.org/index.php/Wireless) and found that I can connect to the router when I turn off the encryption while it still turn out to be "device or resource busy" when I turn on WPA-PSK encryption. However, even though the "iwconfig" commmand showed that I was connected (with no password), the dhcp thing only worked once, while in all other cases output claimed that the router gives no ipv6 things. .

could it be due to the wireless driver, settings or my router?

Thanks,
gtolden

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,341

Website

Re: [Solved]Still can't connect with Realtek RTL8723ae wireless driver

check the output (and report it here) from each step.

Actual output will help.  Your description has a bad case of pronounitis (the dhcp thing, ipv6 things, etc) - post the actual commands you used and the output from each step.

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

gtolden

Member

Registered: 2013-07-20

Posts: 13

Re: [Solved]Still can't connect with Realtek RTL8723ae wireless driver

check the output (and report it here) from each step.

Actual output will help.  Your description has a bad case of pronounitis (the dhcp thing, ipv6 things, etc) - post the actual commands you used and the output from each step.

Sorry for that, my arch is still in tty mode...

I reset the router to factory mode and I can finally connect to the encrypted net, but it seems that it is still not very stable (maybe it's still due to the router). Any way thanks, Trilby!

Here is some output, there is still some wierd things.

$ls pci | grep -i net
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723AE PCIe Wireless Network Adapter
03:00.0 Ethernet controller: Qualcomm Atheros AR8161 Gigabit Ethernet (rev 10)

$lsusb
Bus 001 Device 002: ID 5986:0523 Acer, Inc 
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 0bda:8723 Realtek Semiconductor Corp. 

$ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT qlen 1000
    link/ether 5c:f9:dd:5d:37:fd brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 2c:d0:5a:90:8e:c3 brd ff:ff:ff:ff:ff:ff

$ip link set wlp2s0 up
$iw wlp2s0 connect bl601
(# no encryption)(no output)

$iwconfig wlp2s0

wlp2s0    IEEE 802.11bgn  ESSID:"bl601"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: 6C:E8:73:39:37:E0   
          Bit Rate=150 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr=2347 B   Fragment thr:off
          Power Management:off
          Link Quality=46/70  Signal level=-64 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

$dhcpcd wlp2s0
dhcpcd[1113]: version 5.6.8 starting
dhcpcd[1113]: wlp2s0:  sending IPv6 Router Solicitation
dhcpcd[1113]: wlp2s0:  rebinding lease of 192.168.2.100
dhcpcd[1113]: wlp2s0:  Acknowledged 192.168.2.100 from 192.168.2.1
dhcpcd[1113]: wlp2s0:  checking for 192.168.2.100
dhcpcd[1113]: wlp2s0:  sending IPv6 Router Solicitation                                # sometimes this line showed up three times and it would give "the router offered no IPv6"(this seemed not to affect the success of connecting), but I can't reproduce that.  
dhcpcd[1113]: wlp2s0:  leased 192.168.2.100 for 7200 seconds
dhcpcd[1171]: wlp2s0: wlp2s0: MTU set to 576
dhcpcd[1113]: wlp2s0:  forked to background, child pid is 1206

$dhcpcd -k wlp2s0
...# I didn't record
$ip link set wlp2s0 up
$wpa_supplicant -i wlp2s0 -c /etc/wpa_supplicant/bl601.conf

Successfully initialized wpa_supplicant 
ioctl[SIOCSIWFREQ]: Device or resource busy
wlp2s0: Trying to associate with 6c:e8:73:39:37:e0 (SSID='bl601' freq=2412 MHz)
wlp2s0: Association request to the driver failed 
wlp2s0: Associated with 6c:e8:73:39:37:e0
wlp2s0: WPA: Key negotiation completed with 6c:e8:73:39:37:e0 [PTK=CCMP GTK=CCMP]
wlp2s0: CTRL-EVENT-CONNECTED - Connection to 6c:e8:73:39:37:e0 completed [id=0 id_str=]
...

$iwconfig wlp2s0 
wlp2s0    IEEE 802.11bgn  ESSID:"bl601"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: 6C:E8:73:39:37:E0   
          Bit Rate=150 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr=2347 B   Fragment thr:off
          Power Management:off
          Link Quality=50/70  Signal level=-60 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

two weird things: 1.why are the "8723" show up both in lspci and lsusb? are they two different devices? 2.every time I use wpa_supplicant, there is device and resource busy...though no failure

Last edited by gtolden (2013-07-24 08:40:10)