The Latest Kernel Release.

cwizardone · 01-09-2021, 05:18 PM

After installing today's -current updates VirtualBox-6.1.17-141968-Linux_amd64.run, no longer runs.
It will install, but it won't run.
It has worked just fine with the 5.10.y series, until now, so I booted back to the 5.10.5 and had the same problem. I'm guessing that means it is not the kernel(?).
Trying to run VirtualBox as root returns the following error,

Quote:

/opt/VirtualBox# VirtualBox

(process:13893): GLib-GObject-WARNING **: 15:12:50.993: cannot register existing type 'NMAgentManagerError'

(process:13893): GLib-CRITICAL **: 15:12:50.993: g_once_init_leave: assertion 'result != 0' failed

(process:13893): GLib-GObject-WARNING **: 15:12:50.993: cannot retrieve class for invalid (unclassed) type '<invalid>'
Segmentation fault

hitest · 01-09-2021, 05:30 PM

Quote:

Originally Posted by cwizardone

After installing today's -current updates VirtualBox-6.1.17-141968-Linux_amd64.run no longer runs.
It will install, but it won't run.
It has worked just fine with the 5.10.y series, until now, so I booted back to the 5.10.5 and had the same problem. I'm guessing that means it is not the kernel(?)>
Trying to run VirtualBox as root returns the following error,

Same thing happened with me after trying to install virtualbox on 5.10.5.

cwizardone · 01-09-2021, 05:40 PM

Quote:

Originally Posted by hitest

Same thing happened with me after trying to install virtualbox on 5.10.5.

Ran fine here with the 5.10.5 and earlier 5.10.y kernels until today.

andrew.46 · 01-09-2021, 06:01 PM

Quote:

Originally Posted by cwizardone

Ran fine here with the 5.10.5 and earlier 5.10.y kernels until today.

My own strategy has always been cautious with kernels and this has paid off here. I compile a slightly older version of the running kernel, (patched with a required Kindle change), and run this as my default in Lilo. At the moment this has left me with 5.10.2 as my daily kernel and lucky for me VirtualBox functions fine with this.

More luck than skill there I suspect...

cwizardone · 01-09-2021, 07:48 PM

Well, I don't think it is the kernel.
I've tried 5.10.4, 5.10.5, 5.10.6 and 5.9.16, all with the same negative result.
I can say with absolute certainty that VirtualBox-6.1.16-140961-Linux_amd64.run, worked with 5.9.y and VirtualBox-6.1.17-141968-Linux_amd64.run, worked with 5.10.y, until today.
The problem must be with something other than the kernel?

Gerswing · 01-09-2021, 09:07 PM

Quote:

Originally Posted by cwizardone

Well, I don't think it is the kernel.
I've tried 5.10.4, 5.10.5, 5.10.6 and 5.9.16, all with the same negative result.
I can say with absolute certainty that VirtualBox-6.1.16-140961-Linux_amd64.run, worked with 5.9.y and VirtualBox-6.1.17-141968-Linux_amd64.run, worked with 5.10.y, until today.
The problem must be with something other than the kernel?

You might want to try and compile your own virtualbox instead of using the pre-compiled one. After you proposed the provided the link to the pre-compiled virtualbox to me, I was able to find the SBo package version on Ponce's repository for Slackware-current. Granted, I am only using the 4.19.166 kernel, but at least compiling on your own might provide a clue to the error. If you need to, look in the "SBo scripts not building" link. I was able to add the repository to my sbopkg program.

Andersen · 01-10-2021, 02:12 AM

Quote:

Originally Posted by cwizardone

Well, I don't think it is the kernel.
I've tried 5.10.4, 5.10.5, 5.10.6 and 5.9.16, all with the same negative result.
I can say with absolute certainty that VirtualBox-6.1.16-140961-Linux_amd64.run, worked with 5.9.y and VirtualBox-6.1.17-141968-Linux_amd64.run, worked with 5.10.y, until today.
The problem must be with something other than the kernel?

Probably not the kernel. I had to switch to VB testbuild (VirtualBox-6.1.17-141968-Linux_amd64.run) when I first upgraded to 5.10. kernel, because the earlier versions just wouldn't work.

I'm still using 5.10 kernel, and 6.1.17 worked with every one from that branch. Today I installed the latest changes for Slackware64 -current (so now I have 5.10.6 kernel), and VirtualBox 6.1.17 still works as usual.

andrew.46 · 01-10-2021, 02:32 AM

Quote:

Originally Posted by Andersen

I'm still using 5.10 kernel, and 6.1.17 worked with every one from that branch. Today I installed the latest changes for Slackware64 -current (so now I have 5.10.6 kernel), and VirtualBox 6.1.17 still works as usual.

Indeed. I have just booted into the stock 5.10.6 kernel and VBox 6.1.17r141968 works fine.

_peter · 01-10-2021, 11:49 AM

it works here for a desktop usage w/ libreoffice

Code:

Kernel: Linux 5.10.6 x86_64
CPU: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz

BrunoLafleur · 01-10-2021, 11:59 AM

Quote:

Sat Jan 9 20:53:30 UTC 2021
a/aaa_elflibs-15.0-x86_64-29.txz: Rebuilt.
Upgraded: libcap.so.2.46, libkeyutils.so.1.10, libglib-2.0.so.0.6600.4,
libgmodule-2.0.so.0.6600.4, libgobject-2.0.so.0.6600.4,
libgthread-2.0.so.0.6600.4, libtiff.so.5.6.0, libtiffxx.so.5.6.0,
libusb-1.0.so.0.3.0.
Added: libzstd.so.1.4.8.

Is there an incompatibility with the new libglib (.4) and nm ?

Maybe some dependencies have to be recompiled ?

cwizardone · 01-10-2021, 12:15 PM

Quote:

Originally Posted by cwizardone

Well, I don't think it is the kernel.
I've tried 5.10.4, 5.10.5, 5.10.6 and 5.9.16, all with the same negative result.
I can say with absolute certainty that VirtualBox-6.1.16-140961-Linux_amd64.run, worked with 5.9.y and VirtualBox-6.1.17-141968-Linux_amd64.run, worked with 5.10.y, until today.
The problem must be with something other than the kernel?

OK. Using this information from board member glorsplitz, https://www.linuxquestions.org/quest...lt-4175657749/
I was able to get version to 6.1.17-141968 to run as user. It still won't run as root, for whatever reason, but as long as I can use it as user, this will do.

cwizardone · 01-10-2021, 12:22 PM

Quote:

Originally Posted by BrunoLafleur

Is there an incompatibility with the new libglib (.4) and nm ?

Maybe some dependencies have to be recompiled ?

In an effort to solve my virtualbox problem, I reverted to the previous version, aaa_elflibs-15.0-x86_64-28.txz and even tried version -27. Didn't help. The problem remained.

cwizardone · 01-10-2021, 04:44 PM

5.11-rc3

Release Candidate 3, for the 5.11 "mainline" development kernel has been been made available for testing.

The tarball, https://git.kernel.org/torvalds/t/linux-5.11-rc3.tar.gz

Mr. Torvalds' announcement, http://lkml.iu.edu/hypermail/linux/k...1.1/01744.html

Aeterna · 01-10-2021, 06:15 PM

Quote:

Originally Posted by cwizardone

OK. Using this information from board member glorsplitz, https://www.linuxquestions.org/quest...lt-4175657749/
I was able to get version to 6.1.17-141968 to run as user. It still won't run as root, for whatever reason, but as long as I can use it as user, this will do.

I don't have any problems with VBox host installation and kernel 5.10.x (currently 5.10.6). However none of VBoxClientAdditions works with the kernel 5.10.x so for now I keep clients running 5.9.16 (or 5.4.x).

Your errors may be fixable by complete removal of current installed version of VB host, reboot without VB, then install new version of VB for host.
I noticed that once in a while VB gets messed up, if I run upgrades only without cleaning up the system once in a while. I guess VB does not clean leftovers of the previous installation.

This approach works for me (mixing different host and client versions of VB is safe by the way).

rdsherman · 01-10-2021, 07:33 PM

Installed KV 5.10.6.

Absolutely no improvement!

No surprise; nothing in the changelog addresses the problem.

Ran for many hours. Last few just on idle (no human input).

Then, abruptly, the fan(s) started to spin with rapidly increasing noise representing a heavy load on the 8 cpus.

Anyone else seen this?