After updating Tumbleweed to kernel 6.3.6, the VMware vmnet module gets stuck at “loading”:
grep vmnet /proc/modules
vmnet 98304 1 - Loading 0x0000000000000000 (OE+)
And ideas how to fix this?
(I already did “sudo vmware-modconfig --console --install-all”, as I do after every kernel update.)
add ibt=no to kernel startup and see if that fixes it.
FWIW, on 6.3.7-1 (which is running on my system), VMware Workstation’s modules build and load fine.
I’m running Workstation 17.0.2 build-21581411 here.
Computers that have CPU’s that have ibt instruction sets in them (like gen 11, 12 & 13 Intel) have issues running many kernel applications like VirtualBox that do indirect branches in the kernel without building an indirect branch table for permissions.
I suspect VMware does that as well. Kernel 6.3.6 has ibt enabled - previous OpenSUSE kernels did not.
The ibt was added to make it harder for Malware to take over your computer (not impossible - they will find a way like they did for UEFI).
I suspect that that will also be a requirement to run Windows 12. It is how many most Malware use DRM to get run.
ibt=off seems to have fixed it. (ibt=no did not do anything)
What CPU do you have?
Mine is 12th Gen Intel(R) Core™ i7-12700H
I suspect yours does not support IBT…
$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 85
model name : Intel(R) Core(TM) i9-10980XE CPU @ 3.00GHz
stepping : 7
10th gen, so I guess the answer is that it doesn’t. Learn something new every day.
@hendersj it’s in the flags output (ibt)…
Yeah, I was looking at the generation - it’s generation 10, and ibt comes in generation 11, doesn’t it?
Looking at the flags, ibt isn’t listed in the flags, so that’s consistent.