r8723au - Githubissues

fliiiix commented 10 years ago

With 3.15.3-200.fc20.x86_64 & 3.15.4-200.fc20.x86_64 comes the r8723au.

I thought it's the same as 8723au, which work very well :thumbsup:

But with r8723au it just show a connection, but nothing happens:

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.64  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 xxxx::xxxx:xxxx:xxxx:xxxx  prefixlen 64  scopeid 0x20<link>
        ether xx:xx:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
        RX packets 3  bytes 119502 (116.7 KiB)
        RX errors 0  dropped 168  overruns 0  frame 0
        TX packets 4  bytes 46980 (45.8 KiB)
        TX errors 0  dropped 4 overruns 0  carrier 0  collisions 0

ifconfig show the interface up an running but if I try to ping something, nothing happens.

$ping google.com
ping: unknown host google.com
$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
24 packets transmitted, 0 received, 100% packet loss, time 22999ms

$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
^C  
--- 192.168.1.1 ping statistics ---
15 packets transmitted, 0 received, 100% packet loss, time 13999ms

If this is not the right place for problems with r8723au, please tell me where I should report such things.

jdgiotta commented 10 years ago

Same issue 3.15.4 & 3.15.6. Also, dmesg gives me a tainting kernel error if I attempt to compile the driver.

xcorat commented 10 years ago

Same here, 3.16.xx

lwfinger commented 10 years ago

Compiling the driver cannot taint the kernel. You need to load it for that to happen. I expect that it sets the O flag for an out-of-tree driver. That is not nearly as deadly as setting the P flag, which meanns that a proprietary driver with unseen binary code has been loaded.

As to reporting problems with the driver, keep in mind that this repo exists to help those people using kernels that do not contain this driver. As it was added to kernel 3.15, those of you using 3.15 or later should be using the in-kernel code. If your distro is one that refuses to build staging drivers, you will likely need to configure and build your own kernel. If you use such a driver, then problems should be reported to the authors shown in the output of a 'modinfo r8723au' command. You should also Cc linux-wireless@vger.kernel.org.

One other thing to try is the kernel_version branch of the repo. It does not build with kernel 3.17, but it should for 3.15 and 3.16.

jdgiotta commented 10 years ago

Thank you @lwfinger for your contribution. I wanted to also point out a "remedy" for the in-kernel version I use for Fedora 20. https://ask.fedoraproject.org/en/question/53485/how-can-i-trackdown-my-wifi-driver-issues/

Not the solution to the issue, but at least a workaround.

fliiiix commented 10 years ago

problems should be reported to the authors shown in the output of a 'modinfo r8723au'

Well I wrote a mail today, lets see if they find a solution.

jdgiotta commented 10 years ago

If it's any help, I found that not allowing my device to switch between frequencies will not cause kernel panics.

$ iwconfig freq 2.4G

This as kept me running without issue for the last 2 days.

On Mon, Oct 13, 2014 at 4:11 PM, Felix notifications@github.com wrote:

problems should be reported to the authors shown in the output of a 'modinfo r8723au'

Well I wrote a mail today, lets see if they find a solution.

— Reply to this email directly or view it on GitHub https://github.com/lwfinger/rtl8723au/issues/48#issuecomment-58947687.

lwfinger / rtl8723au

r8723au #48