-
Notifications
You must be signed in to change notification settings - Fork 177
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
dkms build
looks for 'armv7l' folder instead of 'arm' folder
#103
Comments
make.log with the latest Raspbian 9.4 kernel, in my case for
|
And to bypass the error without creating the link (it's dirty, since you would need to do the same for subsequent kernel updates):
It seems to me that the problem could be at https://github.com/diederikdehaas/rtl8812AU/blob/driver-4.3.20/Makefile#L910 I wonder if Rasbian changed the way they compile the kernel, as this was working for kernel |
In fact there is no need to use This is also required for 4.3.14 (I just checked) and most probably f or 4.3.8 as well, but the README for those versions does not have it. |
Hi @juliogonzalez, I actually did change the makefile but anyway got the error. So in my case the best option for Beagle Bone Black with the newest DEBIAN stable image is making the link. |
@JackGrinningCat, what driver version are you trying to compile? You don't need to change If you use >= 4.3.14, you need to following the instructions at https://github.com/diederikdehaas/rtl8812AU/blob/driver-4.3.20/README.md#raspberry-pi The only Makefile you need to change is the one from rtl8812AU
to
That is, disabling building for i386, and enabling building for ARM on a Raspberry Pi. If that still fails for you, please share the exact steps you are following, and paste the exact error (maybe I will be able to submit a fix, even if I don't own a BeagleBone :-) |
I don't know if this is a dkms problem or the configuration problem, but when I run:
I get the error:
Unfortunately I've successfully built it since then so I don't have the errors from the 'make.log'. But the solution for me was what I saw in this Stack Overflow post, which was to make a symlink to the arm folder:
So, once you know about it the fix is relatively easy.
The text was updated successfully, but these errors were encountered: