-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Operation not supported on arm #5
Comments
Hi, Is the driver working anyway ? Please check also the wireless-ext.branch. master is currently not updated, to maintain it pullable. |
Doesn't seem to work. I'd love to try wireless-ext. Will do today. |
Tried wireless-ext on the latest kernel version and I'm getting the same thing. iw list is empty, and iwconfig prints "no wireless extensions" |
Hi, I made some tests on laptop running Sabayon Linux/Limbo aka testing Other HW some Zyxel NSA 325 with Marvell Kirkwood Kernel v4.6.2 This error is part of wireless-ext in /core of the driver and this directory Only /rtl8821au will survive and currently this can't be pushed Ticked closed |
Well... You haven't suggested how to fix this and I can no longer get your driver working at all so im probably going to just switch to some other fork... |
@paralin Perhaps worth checking out upstream's http://lxr.free-electrons.com/source/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c
|
On the other hand |
Switching to the rtl8821au fork at github.com/abperiasamy/rtl8812AU_8821AU_linux. - The current fork we are using is maintained by 1 person. - The current fork does not work, and there are no plans to fix this: - ulli-kroll/rtl8821au#5 - ulli-kroll/rtl8821au#6 - In practice, the current fork has numerous instability issues. - Our lab switched to the abperiasamy fork a couple months ago and have been very happy with it. - The contributor list for the abperiasamy fork contains 21 well-known individuals in the community. - The raspberry pi community recommends the abperiasamy fork and uses it extensively. - Firmware blobs are not necessary with the new fork. Signed-off-by: Christian Stewart <christian@paral.in>
Switching to the rtl8821au fork at github.com/abperiasamy/rtl8812AU_8821AU_linux. - The current fork we are using is maintained by 1 person. - The current fork does not work, and there are no plans to fix this: - ulli-kroll/rtl8821au#5 - ulli-kroll/rtl8821au#6 - In practice, the current fork has numerous instability issues. - Our lab switched to the abperiasamy fork a couple months ago and have been very happy with it. - The contributor list for the abperiasamy fork contains 21 well-known individuals in the community. - The raspberry pi community recommends the abperiasamy fork and uses it extensively. - Firmware blobs are not necessary with the new fork. Signed-off-by: Christian Stewart <christian@paral.in>
Switching to the rtl8821au fork at github.com/abperiasamy/rtl8812AU_8821AU_linux. - The current fork we are using is maintained by 1 person. - The current fork does not work, and there are no plans to fix this: - ulli-kroll/rtl8821au#5 - ulli-kroll/rtl8821au#6 - In practice, the current fork has numerous instability issues. - Our lab switched to the abperiasamy fork a couple months ago and have been very happy with it. - The contributor list for the abperiasamy fork contains 21 well-known individuals in the community. - The raspberry pi community recommends the abperiasamy fork and uses it extensively. - Firmware blobs are not necessary with the new fork. Signed-off-by: Christian Stewart <christian@paral.in>
Switching to the rtl8821au fork at github.com/abperiasamy/rtl8812AU_8821AU_linux. - The current fork we are using is maintained by 1 person. - The current fork does not work, and there are no plans to fix this: - ulli-kroll/rtl8821au#5 - ulli-kroll/rtl8821au#6 - In practice, the current fork has numerous instability issues. - Our lab switched to the abperiasamy fork a couple months ago and have been very happy with it. - The contributor list for the abperiasamy fork contains 21 well-known individuals in the community. - The raspberry pi community recommends the abperiasamy fork and uses it extensively. - Firmware blobs are not necessary with the new fork. Signed-off-by: Christian Stewart <christian@paral.in> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
I'm getting the following errors trying to use wpa_supplicant in wext mode:
Same in all the other driver modes.
iwconfig returns:
iw list returns:
... nothing
And lsmod:
dmesg | grep 8821
Any ideas?
The text was updated successfully, but these errors were encountered: