-
Notifications
You must be signed in to change notification settings - Fork 139
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
Armbian(23.02.2) install #78
Comments
Hi @LittleOn Please go to the driver directory , run the following and post the results of make: make clean |
armbian:8821cu-20210916:# make clean #make -C /lib/modules/5.15.103-flippy-82+o/build M=/root/src/8821cu-20210916 clean cd hal ; rm -fr ///.mod.c ///.mod ///.o ///..cmd ///.ko cd hal ; rm -fr //.mod.c //.mod //.o //..cmd //*.ko cd hal ; rm -fr /.mod.c /.mod /.o /..cmd /.ko cd hal ; rm -fr *.mod.c *.mod .o ..cmd *.ko cd core ; rm -fr /.mod.c /.mod /.o /..cmd /.ko cd core ; rm -fr *.mod.c *.mod .o ..cmd *.ko cd os_dep/linux ; rm -fr *.mod.c *.mod .o ..cmd *.ko cd os_dep ; rm -fr *.mod.c *.mod .o ..cmd *.ko cd platform ; rm -fr *.mod.c *.mod .o ..cmd *.ko rm -fr Module.symvers ; rm -fr Module.markers ; rm -fr modules.order rm -fr *.mod.c *.mod .o ..cmd *.ko *~ rm -fr .tmp_versions armbian:8821cu-20210916:# make make ARCH=arm64 CROSS_COMPILE= -C /lib/modules/5.15.103-flippy-82+o/build M=/root/src/8821cu-20210916 modules make[1]: Entering directory '/usr/src/linux-headers-5.15.103-flippy-82+o' warning: the compiler differs from the one used to build the kernel The kernel was built by: Ubuntu clang version 14.0.0-1ubuntu1 You are using: gcc (Debian 10.2.1-6) 10.2.1 20210110 CC [M] /root/src/8821cu-20210916/core/rtw_cmd.o gcc: error: unrecognized command-line option ‘-Qunused-arguments’ gcc: error: unrecognized command-line option ‘-mno-global-merge’ gcc: error: unrecognized command-line option ‘-fsplit-lto-unit’ make[2]: *** [scripts/Makefile.build:289: /root/src/8821cu-20210916/core/rtw_cmd.o] Error 1 make[1]: *** [Makefile:1913: /root/src/8821cu-20210916] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.15.103-flippy-82+o' make: *** [Makefile:2501: modules] Error 2 |
Hi @LittleOn
It appears that this version of Armbian was compiled with clang and some of the settings that work for clang are not working for gcc. I am curreently moving and my Armbian system is packed away so my ability to look at this is limited in the short term. Let me recommend that you post the results is the |
Thanks for telling me |
-_-|| |
I have a little more time now. Is this still a problem? |
Hello~It seems that I have similar problems, could you please give me some guidance? |
My little system that runs Armbian is not setup yet and it may be a while before I can try to duplicate the problem on Armbian. It appears that Armbian has moved over to using CLANG insted of gcc and gcc is chocking on something because of it. Anyone in the Armbian forums talking about this? I'd offer guidance but I have no experience with CLANG. |
Hi~ This issue is indeed caused by the different compilers used in the kernel. I have solved it by referring to this issue:
This issue is caused by the fact that the kernel in another repository seems to have been compiled with CLANG by the same person all along.
To solve this issue, we can recompile the kernel using GCC, or directly use the dev kernel they later compiled: |
Thanks for the reply, I have solved the problem |
How does on identify how the kernel was compiled, i.e. via GCC or CLANG? If the install-driver.sh trips over the not finding the headers? Is there a CLI command that could expose this issue? # cat /proc/version Looks like the IndieDroid Nova recommended OS based on Ubuntu Jammy Jellyfish was compiled with GCC if I read the above right? |
|
Ah... so it is embedded in the make run! |
Jibun, I keep 4 versions of gcc loaded on my dev box. My experience is that it can be a good idea to use the same major version of gcc that your kernel was compiled with. https://github.com/morrownr/USB-WiFi See:
|
I think dkms really should be taking care of using the right compiler. Maybe
it doesn't know how. One would learn the result when loading the module, and
many of us just don't there.
The raspberrypi-kernel-headers just always seem broken to me.
It sure doesn't seem like it's 8821cu's fault, but until drivers can get
upstreamed, it's where everyone stubs their toes.
|
And the ARM64 support applicable to IndieDroid Nova... has a gap in that the headers are not even published via APT. But I knew that in getting the Nova and using it... I use it as an infrastructure device, and it is a beast, well suited to running QEMU/KVM and/or even Docker. |
It happens far too often.
An in-kernel driver for the 8821/11cu has been upstreamed. It happened with kernel 6.2. RasPiOS will probably move to kernel 6.6, if it is the next LTS, at some point in spring of next year. That will probably be when you see the support unless you want to compile and install 6.4 or so. I do have a guide for do so if interested. |
Just final comment... Pi OS is not at 6.6.x Typo.... SHOULD READ 'now' not 'not'. The Rock 5 based SBCs, at least the ones I have, some OS images, Debian 12 and Armbian, seem to be stuck at 5.10.x. |
Yes, it is: https://www.raspberrypi.com/software/operating-systems/ or $ sudo apt full-upgrade Now, what was the topic of this thread? |
Well, the inference was... that for my IndieDroid... it is still on a variant of Armbian that is only 5.10.x. And as you may (not?) recall I had issues finding the right kernel modules at the time to be able to compile/dkms various WiFi adapter drivers. But since I use my IndieDroid as a hypervisor, I have not been motivated to come back to the original issue... in my case. Is that what you were suggesting? :) |
Well, I gone through thousands of issues since this one was last discussed so I recall exactly nothing. I wasn't suggesting anything. I was just responding to your latest msg:
It was not clear to me what you wanted. |
Ah... no problem... just thought if someone came across the discussion, the Pi OS kernel version changed not long ago. I just realized... I had a typo in my comment! I fixed it... and qualified that Rock 5 based SBCs, at least the one I have is lagging on kernel updates. |
The text was updated successfully, but these errors were encountered: