- This topic has 24 replies, 6 voices, and was last updated Apr 30-12:51 am by symbol.
-
Posts
-
symbol
I broke my newest kernel. Are there any save way to reinstall it.
I want a 5.10.* kernel but every time I install one I met lots of errors:ms: running auto installation service for kernel 5.10.104-antix.1-amd64-smp:Error! echo Your kernel headers for kernel 5.10.104-antix.1-amd64-smp cannot be found at /lib/modules/5.10.104-antix.1-amd64-smp/build or /lib/modules/5.10.104-antix.1-amd64-smp/source. You can use the --kernelsourcedir option to tell DKMS where it's located. Error! echo Your kernel headers for kernel 5.10.104-antix.1-amd64-smp cannot be found at /lib/modules/5.10.104-antix.1-amd64-smp/build or /lib/modules/5.10.104-antix.1-amd64-smp/source. You can use the --kernelsourcedir option to tell DKMS where it's located. Error! echo Your kernel headers for kernel 5.10.104-antix.1-amd64-smp cannot be found at /lib/modules/5.10.104-antix.1-amd64-smp/build or /lib/modules/5.10.104-antix.1-amd64-smp/source. You can use the --kernelsourcedir option to tell DKMS where it's located.Currently I have only one 4.9.0-326-antix.1-amd64-smp kernel.
$ uname -a Linux mac 4.9.0-326-antix.1-amd64-smp #1 SMP PREEMPT Fri Aug 26 21:21:08 EEST 2022 x86_64 GNU/Linux- This topic was modified 1 month, 1 week ago by symbol.
Brian Masinick
@symbol, the reason we offer multiple kernels in our package installer is that it is very difficult to support both old and new systems with a single kernel. Even two kernels won’t support everything.
We still have kernels in our repository that no longer have official security updates being applied to them, but some really old computers don’t run well on other kernels. The antiX and Debian repositories collectively offer quite a significant range of kernels.
The best suggestion is to 1) try the kernels that come packaged with the release first, then 2) check for antiX kernels using the package installer; sometimes it’s handy to 3) use synaptic and search from a graphical interface for kernel packages if the other options do not result in a usable solution.
If and only if none of those work, then look for kernels in other locations; the total range of choices is quite expansive and I recommend a wider search ONLY if all else fails because it can be both confusing and daunting to look at too many alternatives too quickly; start simple; only look as far as you have to look in order to obtain a working solution.
- This reply was modified 1 month, 1 week ago by Brian Masinick. Reason: Start SIMPLE, use antiX resources as much as possible
--
Brian MasinickRobin
Your kernel headers for kernel 5.10.104-antix.1-amd64-smp cannot be found
This implies you haven’t installed the respective headers package?
Installing the newest kernel is:
sudo apt-get update sudo apt-get install linux-headers-5.10.173-antix.1-amd64-smp linux-image-5.10.173-antix.1-amd64-smpwhich should do the trick.
Windows is like a submarine. Open a window and serious problems will start.
christophe
Error! echo
Your kernel headers for kernel 5.10.104-antix.1-amd64-smp cannot be foundAs Brian suggested, use the Package Installer (from the main menu). It will grab the kernel headers as well (which seem to be missing).
You could alternatively use
sudo cli-aptiX
There is an option to seach for antiX kernels, and it will also bring in your kernel headers.edit: Robin beat me to it – that should indeed do what you need.
- This reply was modified 1 month, 1 week ago by christophe.
- This reply was modified 1 month, 1 week ago by Brian Masinick.
confirmed antiX frugaler, since 2019
Brian Masinick
A handy way to check which antiX kernels are available on whatever version of antiX we are using is:
apt-cache search linux-image | grep antixWhen I checked this, linux-image-5.10.173-antix.1-amd64-smp is the newest Version 5.10 kernel.
On antiX 21/22 I see antiX kernels in the 4.4, 4.9, 4.19, 5.8, 5.10, and 6.1 versions, and there are two or more kernels for each of these versions.
That’s JUST antiX kernels.apt-cache search linux-headers | grep antix
provides a matching list of antiX linux-headers. A quick comparison reveals a match.For MOST of us that ought to provide working images. Instead of grep antix, pipe to more instead and you’ll see the entire list of available linux-image and linux-headers for antix, Debian and any other kernel repositories you may optionally add to your configuration. Choices are there in abundance.
--
Brian MasinickThanks Robin and Brian:
Yes, this almost works. While I found after I install the new kernel 5.10.173-antix.1-amd64-smp, it cannot connect to the wifi. While my old kernel can. Are there any way to debug through this?
The kernel that works is linux-headers-4.9.0-326-antix.1-amd64-smp while the newly-installed-kernel is linux-headers-5.10.173-antix.1-amd64-smp which does not work.$ dkms status broadcom-sta, 6.30.223.271, 4.9.0-326-antix.1-amd64-smp, x86_64: installed broadcom-sta, 6.30.223.271, 5.10.173-antix.1-amd64-smp, x86_64: installed exfat, 5.9, 4.9.0-326-antix.1-amd64-smp, x86_64: installed nvidia-current, 470.161.03, 4.9.0-326-antix.1-amd64-smp, x86_64: installed nvidia-current, 470.161.03, 5.10.173-antix.1-amd64-smp, x86_64: installedYour kernel headers for kernel 5.10.104-antix.1-amd64-smp cannot be found
This implies you haven’t installed the respective headers package?
Installing the newest kernel is:
sudo apt-get update sudo apt-get install linux-headers-5.10.173-antix.1-amd64-smp linux-image-5.10.173-antix.1-amd64-smpwhich should do the trick.
- This reply was modified 1 month, 1 week ago by symbol.
I met some errors when I build 5.10.173.I tested 5.10.57-antix.1-amd64-smp (which comes with the release) as well and met similar error. wl.ko is the key.
$ sudo apt-get install linux-headers-5.10.173-antix.1-amd64-smp linux-image-5.10.173-antix.1-amd64-smp Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: linux-headers-5.10.173-antix.1-amd64-smp linux-image-5.10.173-antix.1-amd64-smp 0 upgraded, 2 newly installed, 0 to remove and 2 not upgraded. Need to get 0 B/72.8 MB of archives. After this operation, 413 MB of additional disk space will be used. Selecting previously unselected package linux-headers-5.10.173-antix.1-amd64-smp. (Reading database ... 137890 files and directories currently installed.) Preparing to unpack .../linux-headers-5.10.173-antix.1-amd64-smp_5.10.173-antix.1-amd64-smp-1_amd64.deb ... Unpacking linux-headers-5.10.173-antix.1-amd64-smp (5.10.173-antix.1-amd64-smp-1) ... Selecting previously unselected package linux-image-5.10.173-antix.1-amd64-smp. Preparing to unpack .../linux-image-5.10.173-antix.1-amd64-smp_5.10.173-antix.1-amd64-smp-1_amd64.deb ... Unpacking linux-image-5.10.173-antix.1-amd64-smp (5.10.173-antix.1-amd64-smp-1) ... Setting up linux-image-5.10.173-antix.1-amd64-smp (5.10.173-antix.1-amd64-smp-1) ... dkms: running auto installation service for kernel 5.10.173-antix.1-amd64-smp: Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area... make -j8 KERNELRELEASE=5.10.173-antix.1-amd64-smp KVER=5.10.173-antix.1-amd64-smp...... cleaning build area... DKMS: build completed. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.10.173-antix.1-amd64-smp/updates/dkms/ depmod... Warning: Unable to find an initial ram disk that I know how to handle. Will not try to make an initrd. DKMS: install completed. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area... make -j8 KERNELRELEASE=5.10.173-antix.1-amd64-smp -C /lib/modules/5.10.173-antix.1-amd64-smp/build M=/var/lib/dkms/exfat/5.9/build....(bad exit status: 2) Error! Bad return status for module build on kernel: 5.10.173-antix.1-amd64-smp (x86_64) Consult /var/lib/dkms/exfat/5.9/build/make.log for more information.log.txt is the full process.
- This reply was modified 1 month, 1 week ago by symbol. Reason: Focus on 5.10.173-swp
- This reply was modified 1 month, 1 week ago by symbol.
- This reply was modified 1 month, 1 week ago by symbol. Reason: Tested 5.10.57 as well
Brian Masinick
@symbol: Just in case it wasn’t a typo, please note that linux-headers does not provide a kernel, the linux-image provides a kernel, and the linux-headers provides modules for the kernel. That’s why whenever you change linux-image, you also install the same version of linux-headers.
--
Brian MasinickBrian Masinick
Oh, sorry, another note shows both the linux-image and the linux-headers.
The other thing is that sometimes the automatic routines attempt to rebuild the modules and some errors show up; those errors are insignificant because a matching kernel image and kernel modules are provided.--
Brian Masinickcalciumsodium
Hello @symbol,
I have encountered something similar using the 6.1 antiX kernel in antiX 23 beta1.I think that the non-free broadcom-wl driver present in the antiX kernel is not working properly. This is a non-free proprietary driver problem, not an antiX problem.
It seems like it builds properly and installs properly. Then I see the wifi networks, but I cannot connect to them. Similar to what you observe.
There are many forks of the wl driver in github. You might want to try some of them and install them as an external kernel driver and see if you get lucky and get one of them to work on your system.
- This reply was modified 1 month, 1 week ago by calciumsodium.
Brian Masinick
As far as the issues you are facing, we know that the 4.9 kernel is working for you. That alone tells me that your hardware is probably a few to quite a few years old.
My Dell Inspiron 5558 was released roughly four or five years ago; it will run kernels as old as 4.9 just fine, but it’ll also work with the newest kernels. That particular model has strange difficulties with the 5.10 kernel; maybe your system faces the same kind of issue. Perhaps it’s worth seeing if your computer can safely install and use the linux-image-6.1.18-antix.1-amd64-smp (or whatever the correct name happens to be; I’ve found this image to work on systems ranging from new to 12-15 years old so it’s worth a try,
--
Brian MasinickConsult /var/lib/dkms/exfat/5.9/build/make.log for more information.
This suggests the exfat version present on your system is incompatible to the kernel you try to install.
One thing you could do is:
sudo apt-get purge exfat-dkmsAnd after this retry install headers and kernel with exactly the same command as before.
Another thing is to check whether there exists a newer version of exfat-dkms, so check the output of:
apt-cache policy exfat-dkmsIf so, you can try reinstalling it after the kernel upgrade.
Windows is like a submarine. Open a window and serious problems will start.
When I purged and used apt-cache policy, I think I am getting a same exfat-dkms. As time goes, antix upgrade will bring me new kernels right?
$ apt-cache policy exfat-dkms exfat-dkms: Installed: (none) Candidate: 5.9-1~contribs1 Version table: 5.9-1~contribs1 500 500 http://la.mxrepo.com/antix/bullseye bullseye/main amd64 Packages 500 http://la.mxrepo.com/antix/bullseye bullseye/main i386 PackageConsult /var/lib/dkms/exfat/5.9/build/make.log for more information.
This suggests the exfat version present on your system is incompatible to the kernel you try to install.
One thing you could do is:
sudo apt-get purge exfat-dkmsAnd after this retry install headers and kernel with exactly the same command as before.
Another thing is to check whether there exists a newer version of exfat-dkms, so check the output of:
apt-cache policy exfat-dkmsIf so, you can try reinstalling it after the kernel upgrade.
I found my issue is exactly same as this post, wonder how to fix this: https://www.antixforum.com/forums/topic/kernel-testers-needed/#post-92795
- This reply was modified 1 month, 1 week ago by symbol.
wonder how to fix this
Did you try the suggestion from my last posting?
sudo apt-get purge exfat-dkms sudo apt-get update sudo apt-get install linux-headers-5.10.173-antix.1-amd64-smp linux-image-5.10.173-antix.1-amd64-smpWindows is like a submarine. Open a window and serious problems will start.
- You must be logged in to reply to this topic.
