- This topic has 7 replies, 3 voices, and was last updated Nov 27-7:42 pm by Pieter.
-
Posts
-
Pieter
I did a fresh install of antix-19_386-full on my 14 year old Acer Aspire 1684 laptop (32bit Pentium M 745, 2GB RAM, 120GB HDD, ATI Mobility Radeon 9700)
After the installation I upgaded the kernel to 4.19.83 and everything went fine.
I decided to upgrade the kernel further to 5.2.21, but during the installation process there were errors
Error! Bad return status for module build on kernel: 5.2.21-antix.2-486-smp (i686) Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more information. Error! Bad return status for module build on kernel: 5.2.21-antix.2-486-smp (i686) Consult /var/lib/dkms/ndiswrapper/1.61/build/make.log for more information.And after a reboot very early during bootup it halted with a kernel panic.
I rebooted using the previous kernel and tried to install kernel 5.2.15. During the installation process there were the same errors as with 5.2.21
Error! Bad return status for module build on kernel: 5.2.15-antix.1-486-smp (i686) Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more information. Error! Bad return status for module build on kernel: 5.2.15-antix.1-486-smp (i686) Consult /var/lib/dkms/ndiswrapper/1.61/build/make.log for more information.But after a reboot kernel 5.2.15 booted without any errors…
I’m not a diehard linux user, so I am not sure what to make of the above. Is my hardware too old for kernel 5.2.21, or is this something else?
anticapitalista
Those errors are not relevant unless you use broadcom wireless and/or ndiswrapper.
Maybe 5.2.21 is too new.
Keep to the one that works best for you.Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
I already thought those errors where not relevant because 5.2.15 had them too but booted without problems.
And indeed, I do not use broadcom hardware or ndiswrapper.I guess nothing is logged during a kernel panic, so hard to tell what the culprit is?
But what kernel would be better for me, 4.19.83 or 5.2.15?
My goal is to keep my laptop running in a secure way as long as possible.
- This reply was modified 3 years, 5 months ago by Pieter.
anticapitalista
4.19 series has long term support unlike the 5.2 one (which I note is no longer being updated over at kernel.org)
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
I will use 4.19 and keep it updated, and maybe in the future I will be able to upgrade to the next LTS kernel (or maybe not).
Thank you very much anticapitalista, and keep up te good work!
fungalnet
I would look carefully at the boot loader configuration.
What is the entry from a working kernel and what is for the one failing. There may be a format discrepancy.
Are you using -ucode (amd/intel) and is it on the boot loader’s configuration?Maybe something went wrong during the kernel image creation, have you tried running it again and watch for weird output?
anti-X - Adélie - obarun - systemd Free Space
Maybe something went wrong during the kernel image creation, have you tried running it again and watch for weird output?
Well, actually. When I got the kernel panic for the first time, I redownloaded the iso, checked the md5, wrote the iso to another dvd, and did a complete reinstall.
After this I tried updating the kernel again with the Synaptic Package Manager, and this was the output:
debconf: unable to initialize frontend: Gnome debconf: (Can't locate Gtk3.pm in @INC (you may need to install the Gtk3 module) (@INC contains: /etc/perl /usr/local/lib/i386-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/i386-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/i386-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/i386-linux-gnu/perl-base) at /usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 151, <> line 2.) debconf: falling back to frontend: Dialog Selecting previously unselected package linux-headers-5.2.21-antix.2-486-smp. (Reading database ... 218174 files and directories currently installed.) Preparing to unpack .../linux-headers-5.2.21-antix.2-486-smp_5.2.21-antix.2-486-smp-1_i386.deb ... Unpacking linux-headers-5.2.21-antix.2-486-smp (5.2.21-antix.2-486-smp-1) ... Selecting previously unselected package linux-image-5.2.21-antix.2-486-smp. Preparing to unpack .../linux-image-5.2.21-antix.2-486-smp_5.2.21-antix.2-486-smp-1_i386.deb ... Unpacking linux-image-5.2.21-antix.2-486-smp (5.2.21-antix.2-486-smp-1) ... Setting up linux-image-5.2.21-antix.2-486-smp (5.2.21-antix.2-486-smp-1) ... Error! Bad return status for module build on kernel: 5.2.21-antix.2-486-smp (i686) Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more information. Error! Bad return status for module build on kernel: 5.2.21-antix.2-486-smp (i686) Consult /var/lib/dkms/ndiswrapper/1.61/build/make.log for more information. update-initramfs: Generating /boot/initrd.img-5.2.21-antix.2-486-smp cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. I: The initramfs will attempt to resume from /dev/sda2 I: (UUID=c6e9f429-a1e6-43a9-bd6c-ebdd03bfb631) I: Set the RESUME variable to override this. Generating grub configuration file ... Found background: /usr/share/wallpaper/grub/back.png Found background image: /usr/share/wallpaper/grub/back.png Found linux image: /boot/vmlinuz-5.2.21-antix.2-486-smp Found initrd image: /boot/initrd.img-5.2.21-antix.2-486-smp Found linux image: /boot/vmlinuz-4.19.83-antix.1-486-smp Found initrd image: /boot/initrd.img-4.19.83-antix.1-486-smp Found linux image: /boot/vmlinuz-4.9.193-antix.1-486-smp Found initrd image: /boot/initrd.img-4.9.193-antix.1-486-smp Found memtest86+ image: /boot/memtest86+.bin done Setting up linux-headers-5.2.21-antix.2-486-smp (5.2.21-antix.2-486-smp-1) ...I already mentioned what I thought was weird in my first post. Maybe I can get more output when I use the terminal to update the kernel?
I would look carefully at the boot loader configuration.
What is the entry from a working kernel and what is for the one failing. There may be a format discrepancy.
Are you using -ucode (amd/intel) and is it on the boot loader’s configuration?I’m afraid I have too little experience with linux to understand what you are saying here.
Not sure if it is of some use, but this is the content of my grub config file:# If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=<code>grep PRETTY_NAME /etc/lsb-release | cut -d= -f2 | cut -d\" -f2 2> /dev/null || echo Debian</code> GRUB_CMDLINE_LINUX_DEFAULT="quiet selinux=0" GRUB_CMDLINE_LINUX="" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command 'vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" GRUB_DISABLE_OS_PROBER=false GRUB_BACKGROUND=/usr/share/wallpaper/grub/back.png- This reply was modified 3 years, 5 months ago by Pieter.
- You must be logged in to reply to this topic.
