Page 3 of 3

Posted: Mon 27 Jan 2020, 03:45
by rockedge
I was able to compile the vboxdrv module using the 4.19.25-rt16 RT kernel by these steps:

1. with a fresh Bionic64 using the kernel 4.19.23, loaded the devx and 32 bit compat libs. Then installed virtualbox-6.1_6.1.2-135662~Ubuntu~bionic_amd64.deb
2. loaded the kernel sources SFS for kernel 4.19.25-rt16
3. changed the kernel from 4.19.23 to 4.19.25-rt16
4. reboot
5. deleted the /lib/modules/4.19.25-rt16/build and /lib/modules/4.19.25-rt16/source symlinks
6. replaced with

Code: Select all

 ln -s /usr/src/linux /lib/modules/4.19.25-rt16/build
 ln -s /usr/src/linux /lib/modules/4.19.25-rt16/source
7. open /etc/modprobe.d/cdrecord.conf and comment out an erroneous entry:

Code: Select all

#sg
8. run

Code: Select all

root# /etc/init.d/vboxdrv setup
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules
root#
I then started virtualbox and set up a Racy 5.5 virtual machine which started and I was able to use GParted to format the virtual hard drive and install racy5.5

Posted: Mon 27 Jan 2020, 08:52
by paulh177
OK cool.
I'll have a look at this & try myself tonight

Posted: Mon 27 Jan 2020, 19:20
by paulh177
YAY!

Thanks.

I just deleted and remade the links as I am both impatient and had already installed the virtualbox deb.

Built without error, and I can run virtualbox fine.

However I have now discovered that I can't run 64 bit OS in vbox as tho this old machine has a 64bit processor, it doesn't have the hw virtualisation required :lol: :lol: :lol:

Still, at some stage I'll be doing all this on a much faster multicore i7 machine, so at least I know what to do then.

thanks for your support.

Posted: Mon 27 Jan 2020, 21:33
by rockedge
That's great news, good job.
I've pinpointed the problem is during the kernel sources SFS being built, the correct symlinks land in a directory called /lib/modules/4.19.25
when it should be /lib/modules/4.19.25-rt16

so you were correct that the SFS loading process then placed an extra directory /lib/modules/4.19.25 that put the correct /build and /source symlinks in the wrong place. I will fix the directory name in the main sfs for a permanent fix

Thanks for submitting the bug. Glad we could fix it.

**

Tools

Posted: Wed 19 Feb 2020, 08:18
by Smithy
Hi Rockedge, I found this set of tools, thought they might be handy in
your realtime endeavours. (You may know of these already).

https://github.com/raboof/realtimeconfigquickscan

Posted: Wed 19 Feb 2020, 13:17
by rockedge
Hello Smithy!

fantastic find! I did not run across this yet and I am about to set it up and give it run through.

Thanks for the good tip!