And yet to me, it looks like things will just work if gcc-12 is simply installed, not as the default. Checking some file dates, I see my gcc-12 was brought (by something) in last April, and has been just sitting around. My /bin/gcc and /bin/cc links are years old (and link to gcc-11). The /lib/modules/6.5.0-14-generic/kernel/nvidia-535/bits/nvidia.o was compiled (last week) with gcc-12.3 (correct for my kernel 6.5). It looks like if gcc-12 is installed, it will be used for building an nvidia module, without changing the system /bin/gcc default of gcc-11. When you (MAFoElfen) were trying your workaround by changing links (/bin/gcc to gcc-12), did you ever try the nvidia driver install before changing links with gcc-12 present? If the right compiler gets used if present, that suggests a simple fix of adding a gcc-12 dependency on the hwe kernel package (to allow any modules to be build if they do what nvidia apparently does). I'll try out some jammy iso boots if I cannot find a spare partition to install to and see what happens (I've never bothered to figure out how to make my VMs use Nvidia). I can understand not wanting to change the default gcc, but simply adding one should not cause problems.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2051457 Title: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series Status in dkms package in Ubuntu: New Status in gcc-defaults package in Ubuntu: Won't Fix 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://ubuntuforums.org/showthread.php?t=2494273&p=14175164#post14175164 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 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2051457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
