Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dkms (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
gcc-defaults (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Since Jammy went to the 6.5.0 kernel series, that kernel series was compiled with gcc-12. The previous 6.2.0 series kernels were compiled with gcc-11.
The current version of gcc in jammy is 11.4.
Many NVidia drivers, wifi drivers, VirtualBox (from our Repo), etc fail to build the modules, because of a gcc compiler version mismatch between what the current running kernel was built by, and the module being built.
I recognized this while helping Users with NVidia driver compile errors on the forum, and came up with this work-around for them:
https:/
Summary:
Install gcc-12 & g++-12 on 22.04.3 and use it as the compiler.
Since then, this work-around has helped to resolve problems with running the 6.5.0 series kernels and building modules for other applications and hardware drivers: VirtualBox, WiFi Drivers, etc. for use with the 6.5.0 series.
I have run this for over a month as my default with no ill affects. I have continued to recommend this work-around to many user to solve their problems...
*** I think it is time to look at pushing through gcc-12 as the default compiler for 22.04.3 through the normal updates channel.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gcc 4:11.2.0-1ubuntu1
ProcVersionSign
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckR
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: GNOME
Date: Sun Jan 28 08:23:37 2024
InstallationDate: Installed on 2022-09-19 (496 days ago)
InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
SourcePackage: gcc-defaults
UpgradeStatus: No upgrade log present (probably fresh install)
Status changed to 'Confirmed' because the bug affects multiple users.