New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
how to upgrade to latest kernel
hyperblast
Member
in General
i do apt-get update, apt-get upgrade (and this offers a new kernel) then i do apt-get dist-upgrade... reboot but then the new kernel is not installed. still using this "old" version: Linux localhost 5.10.0-11-amd64 #1 SMP Debian 5.10.92-2 (2022-02-28) x86_64
Comments
https://www.google.com/search?hl=lv&q=how to update to latest kernel debian
Official wiki...
https://wiki.debian.org/HowToUpgradeKernel
official wiki tried.
result:
Reboot and select the new kernel in the GRUB screen over VNC.
I had this same problem. The new kernel does not show up.
This can be fixed by installing grub common and grub efi then grub-update. New kernel will appear on next reboot. But then I immideately notice a problem: network adapters refuse to go up. At this point I'm just too unbothered to go deeper into the rabbit hole, so I just restore the backup image and be content with whatever kernel the os decided to use.
thanks. i try complete reinstall of os on my buyvm vps.
https://www.linuxcapable.com/install-upgrade-to-lastest-linux-kernel-on-debian-11-bullseye/
add repositories "backports"
https://backports.debian.org/
seems to work... after reboot.. still old kernel. wtf?!
Are you on openvz or lxc?
i am on buyvm SLICE 1024.
Your network config might be using the legacy names like
eth0rather than the modern names likeens.......In my case on buyvm VPS, I had to change eth0 to ens3 over VNC after the upgrade
I don't regularly use Debian, but I don't believe they used biosdevnames. If you suspect it could be the issue (Highly doubtful if you're going from 5.10 to something like 5.18) , you can always goto GRUB and add
net.ifnames=0 biosdevname=1to kernel line to disable persistent net names (em#, enp#s#, eno#) to see if networking comes up. Also, you can check which kernel version that its loading too, get yourself two birds in one go.Personally, I'd just load up a live environment and check journal or any other logs to see wtf is going wrong on boot if KVM/IPMI isn't accessible.
If we're going based off of assumptions, I'd say you're most likely kernel panicking or its booting to another shell (busybox, emergency target).
Edit
Also I'd recommend checking to see if ifupdown is being a PITA as this tends to be a regular run in I have with stuff running on Deb. But that would still require you to have remote access, or knowing how to check with a Live OS.
try fresh install then. i do it 100 times and it works 101
Ooh thanks! thats exactly the issue. My network decided to rename itself into those disgusting ensjdggh894203 names with the latest 5.10.0-15 kernel (was stuck at 5.10.0-8). I elected to revert to the old names since there are lots of forgotten scripts relying on them somewhere in the system.
@hyperblast
Im using buyvm too. So I suspect this problem is related to the image provided by them.
I don't know exactly why, but you have to first install grub-common and grub-efi (not grub-legacy) although /sys/firmware suggests that system is currently running on legacy.
So the solution that worked for me is:
1. Install grub-efi components
apt install grub-common grub-efi2. Configure grub to use old network interfaces name in /etc/default/grub as described above by appending the parameter in GRUB_CMDLINE_LINUX line
GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=1"3. Commit the grub config changes
update-grub4. Reboot
reinstalled debian 11 x64. ran apt update and apt upgrade and now it's back to this version: Linux localhost 5.10.0-11-amd64 #1 SMP Debian 5.10.92-2 (2022-02-28) x86_64 GNU/Linux
thx @miau now latest kernel:
Linux localhost 5.10.0-15-amd64 #1 SMP Debian 5.10.120-1 (2022-06-09) x86_64 GNU/Linux
does this work on buyvm slice? https://mrpsycho.pl/cheatsheets/Bash-script-for-disabling-password-login/
i didnt get it running.
Just change the entries by hand - you could have other entries in
/etc/ssh/sshd_config.d/that may override it, so the script certainly doesn't consider all cases. It also doesn't add entries if they're missing - it just replaces them if present.thx @stevewatson301 fyi the script worked well a creanova vm. buy buyvm with debian 11 seems not to work prober.