VirtualBox for Slackware Users

FTIO · 05-18-2021, 01:40 PM

Well, I just didn't know about it or what it did, and figured Pat's 'readme' for it would cover what needed to be done...which, by the way, I seem to have screwed up anyway as my system with the kernels from /testing (5.12.x) that I used in an 'upgradepkg' in konsole, then changed to /boot and did this:

Code:

mkinitrd -c -k 5.12.4* -m reiserfs

(all as root, of course, and because I use reiserfs on all my drives/systems), then rebooted - didn't. It got to vmlinuz and then initrd then just hung there forever, so I figure I screwed something up, lol.

So how am I supposed to do this? Do I do the 'upgradepkg' with those kernels, then cd to /boot and then use that command you showed or is there some step somewhere I'm missing? Can this all be done in konsole, or should I not be in X at all? Told ya I get confused easily, heh.

MDKDIO · 05-18-2021, 02:44 PM

All commands run as root (su)

The steps I take when upgrading a kernel (or installing a dif kernel from what is the main kernel in Slackware at the moment):

First, I do run 5.12.x (5.11.x before this, as I had too many problems with 5.10.x)

I download the (4) packages needed from a mirror.
Run installpkg kernel-* (from within the directory containing the kernel files).
Once completed, I run
/usr/shar/mkinitrd/mkinitrd_command_generator.sh

Yes, it is just a suggestion for what command to run, but I've done this for years and it has never failed so far.

Code:

mkinitrd -c -k 5.12.4 -f ext4 -r /dev/nvme0n1p2 -m xhci-pci:ohci-pci:ehci-pci:xhci-hcd:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-asus:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:jbd2:mbcache:ext4 -u -o /boot/initrd.gz

This is what I get when using the mkinitrd_command_generator.sh script

Example:
If I have just installed kernel 5.12.5, I'd have to change that command line, by two things:
1. mkinitrd -c -k 5.12.4 changed to 5.12.5
2. /boot/initrd.gz to /boot/initrd-5.12.5.gz

So the suggested command (see code section above), is changed to this:

Code:

mkinitrd -c -k 5.12.5 -f ext4 -r /dev/nvme0n1p2 -m xhci-pci:ohci-pci:ehci-pci:xhci-hcd:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-asus:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:jbd2:mbcache:ext4 -u -o /boot/initrd-5.12.5.gz

Next, I'll have to copy two files from /boot to /boot/efi/EFI/Slackware/
cp /boot/vmlinuz-generic-5.12.4 /boot/efi/EFI/Slackware/
cp /boot/initrd-5.12.5.gz /boot/efi/EFI/Slackware/

Finally:
edit the file /boot/efi/EFI/Slackware/elilo.conf (nano /boot/efi/EFI/Slackware/elilo.conf as an example)

Either add a new section, or edit the previous (in my above example, 5.12.4) section
elilo.conf looks something like this:

Code:

chooser=simple
delay=5
timeout=5
default=generic1
#
image=vmlinuz-generic-5.12.4
        label=generic1
        initrd=initrd-5.12.4.gz
        read-only
        append="root=/dev/nvme0n1p2 vga=normal ro"

So what I have to edit here, is
image=vmlinuz-generic-5.12.4 to image=vmlinuz-generic-5.12.5
and
initrd=initrd-5.12.4.gz to initrd=initrd-5.12.5.gz

IF I am not updating a kernel as above, but adding a new kernel instead. I would have to add a new section to elilo.conf
Copy the default section, make sure you change the label=It's_Name AND make sure the default= points to that newly added sections label=

And yes, all of this can be done in konsole while in X (KDE in my case), it makes it easier as you can just copy/paste the mkinitrd command
(ctrl+shift+c to copy, ctrl+shift+v to paste into konsole, of course by first selecting the command line by using the mouse (or highlight it for another word)

Hope that helps a bit on your way

FTIO · 05-19-2021, 09:45 AM

I'll give it another shot, can't hurt, right? Thank you, also, for taking the time to try and help this idiot out with this, I can imagine it's probably frustrating, heh.

MDKDIO · 05-19-2021, 01:44 PM

Quote:

Originally Posted by FTIO

I'll give it another shot, can't hurt, right? Thank you, also, for taking the time to try and help this idiot out with this, I can imagine it's probably frustrating, heh.

You'll get it sorted, you'll see

And no, it's not frustrating

cwizardone · 06-09-2021, 09:39 AM

A new test build, 6.1.23-145004 and extension pack version 6.1.23-145002, have been posted at, https://www.virtualbox.org/wiki/Testbuilds

FTIO · 06-12-2021, 11:31 AM

That test build is working on the latest Slackware current! So it seems the problems I was having with Virtualbox not working on my system was kernel 5.10.x. WOOHOO!

MDKDIO · 06-12-2021, 02:44 PM

Quote:

Originally Posted by FTIO

That test build is working on the latest Slackware current! So it seems the problems I was having with Virtualbox not working on my system was kernel 5.10.x. WOOHOO!

Great news!!
Good reading it finally got sorted, just hope it'll keep working for you in the future as well

cwizardone · 06-18-2021, 11:32 AM

A new test build, 6.1.23-145165, has been posted at, https://www.virtualbox.org/wiki/Testbuilds

Just installed it on this box and it is working as it should with extension pack version 6.1.23-145002.

Daedra · 06-18-2021, 02:39 PM

I still can't build guest additions on 32bit Slckware-current, otherwise Virtualbox has been working fine.

EDIT: The build errors, but I still get working shared folders and 3d acceleration. But everything I transfer through the shared folders gets corrupted or changed. Not really an issue, I just use ssh as a workaround. I only use the VM for testing Slackbuilds.

MDKDIO · 06-18-2021, 02:44 PM

Quote:

Originally Posted by Daedra

I still can't build guest additions on 32bit Slckware-current, otherwise Virtualbox has been working fine.

What version of VirtualBox are you installing on your 32-bit system?

The last version of VirtualBox working on a 32-bit system was 5.2, but that support ended July 2020

Daedra · 06-18-2021, 02:51 PM

Quote:

Originally Posted by MDKDIO

What version of VirtualBox are you installing on your 32-bit system?

The last version of VirtualBox working on a 32-bit system was 5.2, but that support ended July 2020

The latest testbuild that cwizardone posted above. Here is build log...
https://pastebin.com/j2CUigyw

MDKDIO · 06-19-2021, 03:41 AM

@Daedra
Guessing now, but are you trying this by building the guest addition using the SlackBuild?

Daedra · 06-19-2021, 03:51 AM

Quote:

Originally Posted by MDKDIO

@Daedra
Guessing now, but are you trying this by building the guest addition using the SlackBuild?

No, I'm using the testbuilds guest additions.

MDKDIO · 06-19-2021, 06:51 AM

On a 64-bit current installation, I've installed latest testbuild of VirtualBox.
Added a "Machine" (SlackCurrent32) and attached current-live-xfce (32-bit) AND VboxGuestAdditions (latest).
This seems to be working just fine, no errors at least.

Installed 32-bit live with xfce, it went ok as well.

Boots fine

But I'm guessing you have a full install of 32-bit current, and not using a live ISO?

marav · 06-20-2021, 01:41 PM

VBox test build 6.1.23-145165
with extension pack version 6.1.23-145002

Kernel 5.12.12

working fine here