Siduction Forum > Upgrade Warnings

 New kernel 5.8.3-towo.1-siduction-amd64 fails to build virtualbox-6.1.12 modules

(1/5) > >>

paco:
Be careful,the new kernel 5.8.3-towo.1-siduction-amd64 fails to build virtualbox-6.1.12 modules!
--- Code: ---Building module:cleaning build area...
make -j12 KERNELRELEASE=5.8.3-towo.1-siduction-amd64 -C /lib/modules/5.8.3-towo.1-siduction-amd64/build M=/var/lib/dkms/virtualbox/6.1.12/build....(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.8.3-towo.1-siduction-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.12/build/make.log for more information.
.
Setting up linux-image-5.8.3-towo.1-siduction-amd64 (5.8-3) ...
I: /vmlinuz is now a symlink to boot/vmlinuz-5.8.3-towo.1-siduction-amd64
I: /initrd.img is now a symlink to boot/initrd.img-5.8.3-towo.1-siduction-amd64
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 5.8.3-towo.1-siduction-amd64:
Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j12 KERNELRELEASE=5.8.3-towo.1-siduction-amd64 -C /lib/modules/5.8.3-towo.1-siduction-amd64/build M=/var/lib/dkms/virtualbox/6.1.12/build....(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.8.3-towo.1-siduction-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.12/build/make.log for more information.
--- End code ---

sunrat:
This often happens with major point upgrades eg. 5.7 to 5.8. Nvidia drivers almost always have the same problem.
Lucky you still have the 5.7 kernel to boot while you are waiting for VBox to catch up.  ;)

axt:

--- Quote from: sunrat ---This often happens with major point upgrades
--- End quote ---

Right. But this time, kernel 5.8, it takes a long time until a fixed VBox appears.


--- Quote from: paco ---fails to build virtualbox-6.1.12 modules
--- End quote ---

As long as not even the original has completely usable fixes (they don't really take it seriously here), nothing will be solved. Nevertheless you should use the original, but current 6.1.13 test builds.

Linux host with kernel 5.8.3 (in my case Arch based) and Linux VMs →OK

But Win10 20h1 in a VM not only freezes the VM, but brutally freezes the entire system. Reproducible, after one minute at the latest (logs or workloads show nothing abnormal). No matter which settings or tricks are used for testing.

The same VM runs without issues with kernel 5.4 (LTS kernel) and before with 5.7.

In short words: You can use Linux/Linux.

samoht:
@axt,

--- Quote ---... But Win10 20h1 in a VM not only freezes the VM, but brutally freezes the entire system ...
--- End quote ---
Bad luck for you, with your arch kernel.
I use the latest towo kernel, as usual in siduction.
Here Win 10 runs stable in a current Oracle vbox testbuild.

Mte90:
I had to remove the 5.8.3 kernel and also
--- Code: ---linux-headers-siduction-amd64
--- End code ---
package to be able to
--- Code: ---apt install virtualbox-dkms --reinstall
--- End code ---
So the modules is compiled right also for the other kernel versions.

Navigation

[0] Message Index

[#] Next page