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

DKMS Build Failure kernel 5.3 (linux mint and possibly others) #35

Closed
drizuid opened this issue Jun 9, 2020 · 1 comment
Closed

DKMS Build Failure kernel 5.3 (linux mint and possibly others) #35

drizuid opened this issue Jun 9, 2020 · 1 comment
Labels
no-issue-activity wontfix This will not be worked on

Comments

@drizuid
Copy link
Member

drizuid commented Jun 9, 2020

This issue is for documentation purposes, the issue is upstream & not something we can fix

This issue has a potential work around for a recent DKMS build failure. This example was for linux mint, but may apply to other distributions with similar behavior. It also applies to multiple kernels, not just 5.3 as shown in these logs.

Docker logs: https://hastebin.com/oqogucikir.cs

Building module:
cleaning build area...
make -j4 KERNELRELEASE=5.3.0-51-generic -C /lib/modules/5.3.0-51-generic/build M=/var/lib/dkms/wireguard/1.0.20200520/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.3.0-51-generic (x86_64)
Consult /var/lib/dkms/wireguard/1.0.20200520/build/make.log for more information.

Contents of make.log: https://hastebin.com/govotejimu.php

end user facing this issue was able to resolve it by following the guidance in the below github closed issue.
linuxmint/linuxmint#213

@drizuid drizuid added the wontfix This will not be worked on label Jun 9, 2020
@project-bot project-bot bot added this to To do in Issue & PR Tracker Jun 9, 2020
@j0nnymoe j0nnymoe pinned this issue Jun 9, 2020
@drizuid drizuid changed the title DKMS Build Failure (linux mint and possibly others) DKMS Build Failure kernel 5.3 (linux mint and possibly others) Jul 29, 2020
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Issue & PR Tracker automation moved this from To do to Done Aug 29, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
no-issue-activity wontfix This will not be worked on
Projects
Development

No branches or pull requests

1 participant