Neigther nvidia nor virtualbox would build/run their modules. dmesg give
Quoteversion magic '4.14.15-towo.1-siduction-amd64 SMP preempt mod_unload modversions retpoline ' should be '4.14.15-towo.1-siduction-amd64 SMP preempt mod_unload modversions '
Is this a problem with the kernel or the user?
Same her with nvidia-legacy-340xx, i must waiting for functionally patch.
I found on https://devtalk.nvidia.com/default/topic/1026911/linux/4-15-rc1-patches-for-384-98-and-340-104/post/5229739/#5229739 but I am not sure...
Did you install the RC-Kernel? The link is talking about 4.15rc1, my problem is the 4.14.15.
Sorry, i am blind.
I booting with 4.14.14-towo.2-siduction-amd64 – 4.14.15 is broken for me.
Problem found.
For now the workaround is
edit /usr/src/linux-headers-4.14.15-towo.1-siduction-amd64/include/linux/vermagic.h
remove the last line MODULE_VERMAGIC_RETPOLINE
then do
dkms uninstall for nvidia and vbox modules and build them new.
Thanks towo, your workaround works fine.
I reinstall nvidia-legacy-340xx-kernel-dkms virtualbox-dkms after editing and linux-headers-4.14.15-towo.1 booting without problem.
Excellent! Thank you @towo!
Danke towo
System: Host: x1 Kernel: 4.14.15-towo.1-siduction-amd64 x86_64 bits: 64 gcc: 7.2.0
Desktop: KDE Plasma 5.10.5 (Qt 5.9.2) dm: sddm,sddm
Distro: siduction 18.1.0 Patience - kde - (201712300939)
Machine: Device: desktop System: Gigabyte product: GA-970A-UD3 serial: N/A Chassis: type: 3 serial: N/A
Mobo: Gigabyte model: GA-970A-UD3 v: x.x serial: N/A BIOS: Award v: F7 date: 10/22/2012
Battery hidpp__0: charge: N/A condition: NA/NA Wh volts: NA
model: Logitech Performance MX serial: 101a-e9-77-6f-11 status: Discharging
CPU: Hexa core AMD FX-6300 Six-Core (-MCP-) arch: Bulldozer rev.0 cache: 12288 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 42284
clock speeds: min/max: 1400/3500 MHz 1: 2075 MHz 2: 1980 MHz 3: 1497 MHz 4: 1711 MHz 5: 1462 MHz
6: 2959 MHz
Memory: Using dmidecode: root required for dmidecode
Graphics: Card: NVIDIA GM204 [GeForce GTX 970] bus-ID: 01:00.0 chip-ID: 10de:13c2
Display Server: x11 (X.Org 1.19.5 ) drivers: nvidia (unloaded: modesetting,fbdev,vesa)
Resolution: 1920x1080@60.00hz
OpenGL: renderer: GeForce GTX 970/PCIe/SSE2
version: 4.5.0 NVIDIA 390.12 (compat-v: 4.6.0) Direct Render: Yes
Towo's fix worked for me too!
However, instead of dkms uninstall I had to use dkms remove to cleanly remove my nvidia and virtualbox drivers before reinstalling them.
Hello,
as far as Virtualbox is concerned, I can confirm that the workaround here also works: after that, a simple "dpkg-reconfigure virtualbox-dkms" fills the bill.
On the other side of the shore, VMware Workstation 14.0.0 is unaffected by the bug and works seamlessly.
Thanks towo!!!
Thanks towo, this fixed my issue where siduction is the guest OS too, removed and reinstall of virtualbox-guest-dkms and/or dpkg-reconfigure of that package then provided fully working guests.
Yes, thanks towo all seems to be working here also.
Tom
I didn't install 4.14.15 but now after d-u and the 4.15.0 kernel from towo there is no issue with VB, thanks :)
Also here no problems with kernel 4.15.0, neither with nvidia nor with VB