Hello!
Did kernel should be updated during moving from latest OMV 5.x to the OMV 6.x using the command omv-release-upgrade. Mine does not, I am stuck with Linux 5.10.0-0.bpo.9-amd64. I am trying to install the nvidia driver for transcoding in Plex using below tutorial:
but I am getting some weird problems with mismatched kernel while installing nvidia driver?
Which kernel do you expect?
Which kernel do you expect?
Linked tutorial is mentioning about Kernel 5.16.0-0.bpo.4-amd64 on the author machine.
apt update then apt dist-upgrade.
apt update then apt dist-upgrade.
Unfortunately it does not work for me. I am still on Linux 5.10.0-0.bpo.9-amd64. I have attached the complete log file (sorry, it is partially in Polish, I need to change it to English...).
Następujące pakiety zostały zainstalowane automatycznie i nie są już więcej wymagane:
linux-headers-5.10.0-13-amd64 linux-headers-5.10.0-13-common linux-kbuild-5.10
Aby je usunąć należy użyć "apt autoremove".
Zostaną zainstalowane następujące NOWE pakiety:
linux-headers-5.16.0-0.bpo.4-amd64 linux-headers-5.16.0-0.bpo.4-common linux-kbuild-5.16
Następujące pakiety zostaną zaktualizowane:
cifs-utils dpkg dpkg-dev gzip libavcodec58 libavformat58 libavresample4 libavutil56 libcups2
libdpkg-perl libldap-2.4-2 libldap-common liblzma5 libntfs-3g883 libssl1.1 libswresample3 libtiff5
libxml2 linux-compiler-gcc-10-x86 linux-headers-amd64 linux-kbuild-5.10 linux-libc-dev ntfs-3g openssl
rsyslog xz-utils zlib1g zlib1g-dev
28 aktualizowanych, 3 nowo instalowanych, 0 usuwanych i 0 nieaktualizowanych.
Konieczne pobranie 32,7 MB archiwów.
Po tej operacji zostanie dodatkowo użyte 60,0 MB miejsca na dysku.So new packages linux-headers-5.16.0-0.bpo.4-amd64 linux-headers-5.16.0-0.bpo.4-common linux-kbuild-5.16 should be installed but:
dkms: running auto installation service for kernel 5.16.0-0.bpo.4-amd64:
Kernel preparation unnecessary for this kernel. Skipping...Some additional steps are required?
Make sure the the files in /etc/apt/sources.list and /etc/apt/sources.list.d/ refer to bullseye and not buster,
apt clean all
apt update
apt dist-upgrade
If that doesn't get it.
apt install linux-headers-5.16.0-0.bpo.4-amd64 linux-headers-5.16.0-0.bpo.4-common linux-kbuild-5.16
nano /etc/apt/sources.list
/etc/apt/sources.list.d/ ls
Output of given commands:
root@baranki:/etc/apt/sources.list.d# apt clean all
root@baranki:/etc/apt/sources.list.d# apt update
(...)
Pobrano 403 kB w 3s (128 kB/s)
Czytanie list pakietów... Gotowe
Budowanie drzewa zależności... Gotowe
Odczyt informacji o stanie... Gotowe
All packages are up to date.
root@baranki:/etc/apt/sources.list.d# apt dist-upgrade
Czytanie list pakietów... Gotowe
Budowanie drzewa zależności... Gotowe
Odczyt informacji o stanie... Gotowe
Obliczanie aktualizacji... Gotowe
Następujące pakiety zostały zainstalowane automatycznie i nie są już więcej wymagane:
linux-headers-5.10.0-13-amd64 linux-headers-5.10.0-13-common linux-kbuild-5.10
Aby je usunąć należy użyć "apt autoremove".
0 aktualizowanych, 0 nowo instalowanych, 0 usuwanych i 0 nieaktualizowanych.
root@baranki:/etc/apt/sources.list.d# apt autoremove
Czytanie list pakietów... Gotowe
Budowanie drzewa zależności... Gotowe
Odczyt informacji o stanie... Gotowe
Następujące pakiety zostaną USUNIĘTE:
linux-headers-5.10.0-13-amd64 linux-headers-5.10.0-13-common linux-kbuild-5.10
0 aktualizowanych, 0 nowo instalowanych, 3 usuwanych i 0 nieaktualizowanych.
Po tej operacji zostanie zwolnione 60,3 MB miejsca na dysku.
Kontynuować? [T/n] T
(Odczytywanie bazy danych ... 107293 pliki i katalogi obecnie zainstalowane.)
Usuwanie pakietu linux-headers-5.10.0-13-amd64 (5.10.106-1) ...
dpkg: ostrzeżenie: podczas usuwania pakietu linux-headers-5.10.0-13-amd64, katalog "/lib/modules/5.10.0-13-amd64" nie był pusty, więc nie został usunięty
Usuwanie pakietu linux-headers-5.10.0-13-common (5.10.106-1) ...
Usuwanie pakietu linux-kbuild-5.10 (5.10.120-1) ...
root@baranki:/etc/apt/sources.list.d#As you can see (again partialy in Polish :D) above the packages linux-headers-5.10.0-13-amd64 linux-headers-5.10.0-13-common linux-kbuild-5.10 will be deleted (confirmed by user). But there is an error (?) that directory "/lib/modules/5.10.0-13-amd64" from package linux-headers-5.10.0-13-amd64 is not empty and will not be deleted.
Below is the information that packages linux-headers-5.10.0-13-common (5.10.106-1) and linux-kbuild-5.10 (5.10.120-1) are being deleted.
While performing apt dist-upgrade nothing new happens:
root@baranki:~# apt dist-upgrade
Czytanie list pakietów... Gotowe
Budowanie drzewa zależności... Gotowe
Odczyt informacji o stanie... Gotowe
Obliczanie aktualizacji... Gotowe
0 aktualizowanych, 0 nowo instalowanych, 0 usuwanych i 0 nieaktualizowanych.And for apt install linux-headers-5.16.0-0.bpo.4-amd64 linux-headers-5.16.0-0.bpo.4-common linux-kbuild-5.16:
root@baranki:/etc/apt/sources.list.d# apt install linux-headers-5.16.0-0.bpo.4-amd64 linux-headers-5.16.0-0.bpo.4-common linux-kbuild-5.16
Czytanie list pakietów... Gotowe
Budowanie drzewa zależności... Gotowe
Odczyt informacji o stanie... Gotowe
linux-headers-5.16.0-0.bpo.4-amd64 is already the newest version (5.16.12-1~bpo11+1).
linux-headers-5.16.0-0.bpo.4-amd64 zaznaczony jako zainstalowany ręcznie.
linux-headers-5.16.0-0.bpo.4-common is already the newest version (5.16.12-1~bpo11+1).
linux-headers-5.16.0-0.bpo.4-common zaznaczony jako zainstalowany ręcznie.
linux-kbuild-5.16 is already the newest version (5.16.12-1~bpo11+1).
linux-kbuild-5.16 zaznaczony jako zainstalowany ręcznie.
0 aktualizowanych, 0 nowo instalowanych, 0 usuwanych i 0 nieaktualizowanych.system indicates, that all packages are installed. But after reboot I am still on Version 6.0.28-3 (Shaitan) Kernel Linux 5.10.0-0.bpo.9-amd64:
Other question is why I don't have a menu entry Kernel in my System settings?
Edit:
I have fixed my Plugins issue (not displayed on the list), installed Kernel plugin and as you can see new kernel is also not available from here:
What is the output of: sudo update-grub
What is the output of: sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.10.0-0.bpo.9-amd64
Found initrd image: /boot/initrd.img-5.10.0-0.bpo.9-amd64
doneDid you change your boot drive? It looks like grub is not looking at the right drive.
Did you change your boot drive? It looks like grub is not looking at the right drive.
Not intentialy. Last day I messed up my grub, as far as I remember with some of the update command. There was a blue screen where I need to choose proper boot device and I've choosen the whole drive with my OMV partition (there was also the partition available to choose). From this time I was unable to boot properly to the system (grub rescue). I have managed to resolve this issue using below tutorial:
https://askubuntu.com/question…fter-ubuntu-19-10-upgrade
(the second answer in this thread, author yorch).
Some time ago I have moved my OMV system from HDD to SSD, the whole system drive (3 partitions).
You need to set your grub drive and /boot drive back to the same drive. This might involve changing the bios to boot from the proper drive.
You need to set your grub drive and /boot drive back to the same drive. This might involve changing the bios to boot from the proper drive.
So linked tutorial did not do the job?
# So we can run the next commands as `root`:
sudo su
# To figure which partition had my Xubuntu installation (partition type `Linux`)
# in my case it was `/dev/sda1`, we can use:
fdisk -l
# Let's mount a few things:
mount /dev/sda1 /mnt
mount --bind /dev /mnt/dev
mount --bind /dev/pts /mnt/dev/pts
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
chroot /mnt
# Now let's try to fix Grub:
grub-install /dev/sda# To change back chroot:
exit
# And now we can umount all:
umount /mnt/dev/pts
umount /mnt/dev
umount /mnt/proc
umount /mnt/sys
umount /mnt
# Now we can reboot:
rebootMy system boots without problems from this time.
My boot drive was sda, with one partition for OMV system, second for OMV backups and third for Docker containers & configurations.
That is the proper procedure from a rescue disk. If your system is booted, you can just run grub-install /dev/sdX then update-grub. Is /dev/sda the correct drive though? Is /boot on /dev/sda?
This is my grub boot selection:
And this is all my disks and partitions:
The sda is my main disk:
There are no any other disk or systems on this machine.
What is the output of:
ls -al /boot
sudo grub-install /dev/sda
sudo update-grub
That is the proper procedure from a rescue disk. If your system is booted, you can just run grub-install /dev/sdX then update-grub. Is /dev/sda the correct drive though? Is /boot on /dev/sda?
Does not help. Still the same results.
What is the output of:
ls -al /boot
sudo grub-install /dev/sda
sudo update-grub
root@baranki:~# ls -al /boot
total 762544
drwxr-xr-x 3 root root 4096 Jun 15 22:33 .
drwxrwxr-x 23 root root 4096 Jun 14 22:14 ..
-rw-rw-rw- 1 root root 273678336 Jan 8 2019 clonezilla-live-2.6.0-37-amd64.iso
-rw-r--r-- 1 root root 236037 Oct 10 2021 config-5.10.0-0.bpo.9-amd64
-rw-rw-rw- 1 root root 405798912 Jan 26 2021 gparted-live-1.2.0-1-amd64.iso
drwxr-xr-x 5 root root 4096 Jun 16 19:15 grub
-rw-r--r-- 1 root root 47225147 Jun 15 22:33 initrd.img-5.10.0-0.bpo.9-amd64
-rw-r--r-- 1 root root 47049606 Nov 8 2021 initrd.img-5.10.0-0.bpo.9-amd64.old-dkms
-rw-r--r-- 1 root root 83 Oct 10 2021 System.map-5.10.0-0.bpo.9-amd64
-rw-r--r-- 1 root root 6829312 Oct 10 2021 vmlinuz-5.10.0-0.bpo.9-amd64root@baranki:~# sudo grub-install /dev/sda
Installing for i386-pc platform.
Installation finished. No error reported.root@baranki:~# sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.10.0-0.bpo.9-amd64
Found initrd image: /boot/initrd.img-5.10.0-0.bpo.9-amd64
doneDoes not help. Still the same results.
Look at the contents of your /boot. grub is doing exactly what it should. What is the output of: dpkg -l | grep linux-image
Look at the contents of your /boot. grub is doing exactly what it should. What is the output of: dpkg -l | grep linux-image
root@baranki:~# dpkg -l | grep linux-image
ic linux-image-5.10.0-0.bpo.8-amd64 5.10.46-4~bpo10+1 amd64 Linux 5.10 for 64-bit PCs (signed)
ii linux-image-5.10.0-0.bpo.9-amd64 5.10.70-1~bpo10+1 amd64 Linux 5.10 for 64-bit PCs (signed)
ic linux-image-amd64 5.10.70-1~bpo10+1 amd64 Linux for 64-bit PCs (meta-package)ok. The older one is not in fully installed. But you don't really want it anyway. What is the output of:
apt-cache policy linux-image-amd64
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!