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

Kernel modules can't compile natively on Debian (DKMS, Fedora gcc) #3284

Closed
tasket opened this Issue Nov 6, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@tasket

tasket commented Nov 6, 2017

Qubes OS version:

Affected TemplateVMs:

debian-8
debian-9


Steps to reproduce the behavior:

Install a dkms module like:
apt-get install wireguard-dkms

Website:
https://www.wireguard.com/install/

Expected behavior:

Module compiles and installs

Actual behavior:

DKMS make.log for wireguard-0.0.20171017-1 for kernel 4.9.56-21.pvops.qubes.x86_64 (x86_64)
cc1: error: incompatible gcc/plugin versions
cc1: error: fail to initialize plugin ./scripts/gcc-plugins/latent_entropy_plugin.so

Make install fails.

General notes:

Debian template was built using a Fedora-supplied version of gcc and Debian does not have this version in either stable, testing, etc. Failure apparently caused by gcc version mis-match.


Related issues:

@tasket

This comment has been minimized.

Show comment
Hide comment
@tasket

tasket Nov 9, 2017

I think I have an example of this happening on a Fedora template also, on R3.2 as reported by a twitter user. Appears to be a more general issue with maintaining template self-consistency.

tasket commented Nov 9, 2017

I think I have an example of this happening on a Fedora template also, on R3.2 as reported by a twitter user. Appears to be a more general issue with maintaining template self-consistency.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Nov 9, 2017

Member

This is a duplicate of #2844
See discussion there. Generally it looks like the best option (if you want to customize anything kernel related) is to use the one installed inside template, not provided by dom0. For 3.2 see https://www.qubes-os.org/doc/managing-vm-kernel/#using-kernel-installed-in-the-vm, for 4.0 it is even simpler because bootloader is already installed, it require only:

qvm-prefs vmname kernel ''
Member

marmarek commented Nov 9, 2017

This is a duplicate of #2844
See discussion there. Generally it looks like the best option (if you want to customize anything kernel related) is to use the one installed inside template, not provided by dom0. For 3.2 see https://www.qubes-os.org/doc/managing-vm-kernel/#using-kernel-installed-in-the-vm, for 4.0 it is even simpler because bootloader is already installed, it require only:

qvm-prefs vmname kernel ''

@marmarek marmarek closed this Nov 9, 2017

@marmarek marmarek added the duplicate label Nov 9, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment