Porteus Kernel Builder

[roadie]

Has anyone solved VirtualBox problem wih latest kernels?
I tried the last (5.11.13), same result!

Porteus Kernel Builder (Post by AcnapyxoB #81819)

I just built the Vbox module using kernel 5.11.13 and the default choices given when building it. It seems to be running well booting a Porteus ISO, though I seldom use Vbox......I have no clue as to how to do things in it.

[beny]

the vbox version of simple package manager start but do not find the kernel header and give the error that i can't solve so i have the kernel header the crippled source kernel but no luck with seem the vbox version hate the on the go way to use.

[evergreen]

Hello @Blaze
In the current version 07-kernel-header is not longer required for dev module?

Congrats for the latest release and thanks

[Updated kernel Examples]
==== AUFS Kernel only for Porteus ====
Simple package (vmlinuz, 000-kernel.xzm, 06-crippled_sources-NNN-XXbit.xzm, 64bit.config)

[5.11.13] <-- NEW : "All patches" patching was done.

[Bob1414]

64bit-ALL-kernel5.11.13.tar (~113 M)

Privet, Blaze. I'd recently tried Porteus 4 for the 1st time, but found that it didn't have drivers for my RealTek wifi and AMD Radeon Vega graphics. So I put in 5.12, but that seemed to keep my laptop fan on most of the time. Your 5.11 seems much better on that. Thank you!

Quite lucky timing, too.

[AcnapyxoB]

@roadie can you share your k5.11.13 VirtualBox module?

[roadie]

@roadie can you share your k5.11.13 VirtualBox module?

Here you go:

https://www.mediafire.com/file/82xvybt4 ... t.xzm/file

md5sum:7fcd1c9dac7e19010ef5c65db573cf9c


EDIT: Sorry, this isn't going to work unless you have glibc-2.33 installed......my kernel was built against it. I'm getting errors about glibc-2.33 in another Porteus install.

[AcnapyxoB]

@roadie thanks!

Unfortunately the same problem:
Porteus Kernel Builder (Post by AcnapyxoB #81819)

At least with your module boot is successful !?

[beny]

hi AcnapyxoB,you need the kernel header and crippled source install the whole blaze kernel packages and try....maybe work

[AcnapyxoB]

There is no kernel header with 5.11.13.

I have found missing vboxnetadp.ko and vboxnetflt.ko in /lib/modules/5.11.13-porteus

[roadie]

@roadie thanks!

Unfortunately the same problem:
viewtopic.php?p=81819#p81819

At least with your module boot is successful !?

Try this one, kernel, crippled sources and vbox module built in Porteus-5.0-rc2 this morning and is working here.

https://www.mediafire.com/file/iu2hzmpa ... t.xzm/file

md5sum:a1cadc138d65a4462a3076a6f884038f

Something I'm not sure of is whether or not the cpu makes a difference. My vbox builder file is VirtualBox-6.1.18-142142-Linux_amd64.run.......does the amd64 bit work with Intel?

[roadie]

There is no kernel header with 5.11.13.

I have found missing vboxnetadp.ko and vboxnetflt.ko in /lib/modules/5.11.13-porteus

I don't have those modules either, only the vboxdrv.ko.

When you run /sbin/vboxconfig, what does the /var/log/vbox-setup.log show? The error in building should be there.

[AcnapyxoB]

When you run /sbin/vboxconfig, what does the /var/log/vbox-setup.log show? The error in building should be there.

Code: Select all

vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: failed: Cannot unload module vboxdrv.
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.

[roadie]

When you run /sbin/vboxconfig, what does the /var/log/vbox-setup.log show? The error in building should be there.

Code: Select all

vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: failed: Cannot unload module vboxdrv.
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.

You can't build the vbox module unless the 05-devel.xzm is activated, yet it's not finding gcc, make, and all the others......strange.

This is the way I built mine:
1: Compiled the kernel
2: Built kernel modules
3: Built crippled-source.xzm
4: Activated crippled-source.xzm......05-devel.xzm was already activated
5: Opened Vbox Builder from the menu and went with default options, except increasing the memory to 4096. I downloaded the VirtualBox-6.1.18-142142-Linux_amd64.run

https://postimg.cc/0K24qJ5y

[AcnapyxoB]

I have build virtualbox modules at least 25 times for diferent kernels (without any problems):
viewtopic.php?p=81821#p81821

[roadie]

I'm sure you know how to build it, just wondering if you did something different to the way I did mine. I can't see why yours won't build, you're doing the same steps as me except I didn't do it in Always Fresh. If anything, that should cause problems, not help.

Have you tried my build from this morning, and if so, does it work for you?