Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upKernel modules can't compile natively on Debian (DKMS, Fedora gcc) #3284
Comments
andrewdavidwong
added
bug
C: Debian
C: kernel
labels
Nov 7, 2017
andrewdavidwong
added this to the Release 4.0 milestone
Nov 7, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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 ''
|
This is a duplicate of #2844
|
tasket commentedNov 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:
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: