Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exec format error on Fedora 36 (kernel: 5.19.16-200.fc36.x86_64) #173

Open
jackrendor opened this issue Oct 25, 2022 · 2 comments
Open

Exec format error on Fedora 36 (kernel: 5.19.16-200.fc36.x86_64) #173

jackrendor opened this issue Oct 25, 2022 · 2 comments

Comments

@jackrendor
Copy link

Hi. I have some issue regarding the install of the kernel module.
I made sure to switch branch (to workstation-16.2.4 which matches the current vmware installation) in order to have everything I needed to compile and install the modules.

But when I run the following commands:
modprobe -v vmmon; modprobe -v vmnet

I get the following:

modprobe: ERROR: could not insert 'vmmon': Exec format error
modprobe: ERROR: could not insert 'vmnet': Exec format error

So what am I missing out?

Not sure if this might help but my gcc version is: gcc version 12.2.1 20220819 (Red Hat 12.2.1-2) (GCC)
I followed the info in the INSTALL files (so changing branch, compiling with make, installing with make install and also signed up the files for my secure boot) yet I still have this error.

@mkubecek
Copy link
Owner

IIRC some people got this error when they had "secure boot" enabled and forgot to sign the modules. Could that the the case here?

@jackrendor
Copy link
Author

My secure boot is enabled, yes.
Also created the certificate and signed up the files with the following script:

for modfile in $(modinfo -n vmmon vmnet); do
  echo "Signing $modfile"
  /usr/src/kernels/$(uname -r)/scripts/sign-file sha256 \
                                /misc/sign-vmware-modules/MOK.priv \
                                /misc/sign-vmware-modules/MOK.der "$modfile"
done

I also "added" the cert to my "secure boot" by importing it with mokutil --import MOK.der
And after rebooting I also followed the configuration in the secure boot to properly apply the cert.

Even tho I thought secure boot was the problem, I tried to disable it and tried to run the previous modprobe commands, ending up with the same results.

Any other clue or logs that I can post here to help?

Thank you a lot for answering tho!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants