Originally Posted by
mdlueck
The update of Kernel and nvidia 470 drivers also killed my VirtualBox kernel drivers.
Something about the forced upgrade of nvidia 465 to nvidia 470 and the kernel update really went wrong.
Here is the results of purging off VirtualBox, IPL, then reinstalling the latest package of VirtualBox again....
Code:
$ sudo dpkg -i virtualbox-6.1_6.1.26-145957~Ubuntu~eoan_amd64.deb
Selecting previously unselected package virtualbox-6.1.
(Reading database ... 258128 files and directories currently installed.)
Preparing to unpack virtualbox-6.1_6.1.26-145957~Ubuntu~eoan_amd64.deb ...
Unpacking virtualbox-6.1 (6.1.26-145957~Ubuntu~eoan) ...
Setting up virtualbox-6.1 (6.1.26-145957~Ubuntu~eoan) ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
This system is currently not set up to build kernel modules.
Please install the gcc make perl packages from your distribution.
This system is currently not set up to build kernel modules.
Please install the gcc make perl packages from your distribution.
There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root. If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.
Processing triggers for systemd (245.4-4ubuntu3.11) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for shared-mime-info (1.15-1) ...
Something in either/both the nvidia 465 to nvidia 470 or the latest kernel update killed both that each require interacting with the Kernel.
Suggestions how to alert the correct group within Ubuntu?
I am thankful,
Bookmarks