from:"Ubfan"

[Kernel-packages] [Bug 2051457] Re: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series

2024-02-05 Thread Ubfan

A just finished test install of the (same) Ubuntu 22.04.1 Desktop ISO
now resulted in the gcc-12 being automatically installed, and the Nvidia
545 driver modules successfully compiling. After a fresh install, set up
wireless, installed build-essential, and then used software &
Updates/Additional drivers to select the Nvidia 545 driver, which
successfully compiled (gcc 11.4) under the 5.15 kernel.  Ran apt update,
and the new 6.5 kernel and gcc-12 were downloaded, and the nvidia 545
modules successfully compiled with the gcc-12. Looks a fix has been
applied to get the gcc-12.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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:
  Confirmed
Status in gcc-defaults package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

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=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

[Kernel-packages] [Bug 2051457] Re: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series

2024-01-31 Thread Ubfan

Testing was done with the Ubuntu 22.04.1 ISO, booted off disk, no persistence.
The Nvidia GPU was an RTX 3080 (mobile).
The gcc-12 and the generic hwe packages were installed, then the Nvidia
driver 535 selected in the Software & Updates/Additional Drivers tab.  Clicked
the apply button, and the nvidia.ko module(s) build successfully using gcc-12.
The build was done while running the default 5.15 kernel, and succeeded whether 
or
not gcc-11 was even present. 

Steps Taken
1)Boot the Ubuntu 22.04.1 Desktop ISO. The default kernel used is 5.15.
2)Set up wireiess.
3)In Software & Updates, add the universe and multiverse repositories. Click on
"update" button when presented.
4)sudo apt update  (Just in case)
5)sudo apt install gcc-12 build-essential
(Note, the Nvidia module will still build without the build-essential package, 
and its /bin/gcc link. )
6)Install the generic hwe packages. Note, using the hwe packages without 
"generic" in their
names immediately failed on the Nvidia module creation step. This installed the 
6.5.0-15 kernel.
sudo apt install linux-generic-hwe-22.04 linux-headers-generic-hwe-22.04 
linux-image-generic-hwe-22.04
7)In Software & Updates, under the Additional Drivers tab, select Nvidia 535. 
Click on the apply button, and watch the progress bar. No errors should occur.
8)Examine the nvidia.ko module created.
strings /lib/modules/6.5.0-15-generic/kernel/nvidia-535/nvidia.ko |grep gcc
The output should include that gcc 12.3 was used. (Whether or not /bin/gcc 
->gcc-11 is even present.)

Did not try a reboot, since persistence was not even used.  The test was
quick since everything is in memory.

It looks like just the presence of gcc-12 will solve this problem, and
that may be addressed by adding a dependency on it to some (hwe, kernel
?) package.

-- 
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=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

[Kernel-packages] [Bug 2051457] Re: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series

2024-01-30 Thread Ubfan

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=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

[Kernel-packages] [Bug 1990750] Re: Boot issue with Ubuntu 22.10 Kinetic Kudu since Kernel 5.19.0.15.15, now hanging with blinking cursor after update to Kernel 5.19.0.21.21

2023-03-04 Thread Ubfan

Yesterday, running the 5.19.0-35 kernel and Nvidia 525.76... driver, an
update held back several Nvidia 525 packages (the 525.85.05 versions).
That in itself was not a problem, but the existing Nvidia modules for
that kernel got deleted! Rebooting, the laptop was running off the intel
GPU. The Software & Updates/Additional Drivers thought the nvidia 525
driver was selected and in use, but lsmod did not show it, and anything
needing the nvidia modules like nvidia-settings or nvidia-smi could not
communicate with the driver (the .ko driver files in
/lib/modules/5.19.0-35-generic/kernel/nvidia-525 were missing. Booting
a former kernel (with the 525.76.. driver still worked. Rather than
forcing the issue (doing an explicit install of the held back nvidia
packages), I just waited a day, and the phasing (which was at 70%)
caught up, the sudo apt full-upgrade succeeded, the modules got rebuilt,
and everything worked again. Just wait a bit and see if things correct
themselves when you run the upgrade.

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1990750

Title:
Boot issue with Ubuntu 22.10 Kinetic Kudu since Kernel 5.19.0.15.15,
now hanging with blinking cursor after update to Kernel 5.19.0.21.21

Status in linux package in Ubuntu:
Confirmed

Bug description:
When starting the PC, the splash screen freezes with the motherboard logo
displayed.
As my disk is encrypted the decryption field does not appear below the logo.

By typing [ALT] + [CTRL] + [DEL] then the splash screen appears again
followed by a start-up menu with the following line:
*Ubuntu
Advanced options for Ubuntu

By selecting 'Advanced options for Ubuntu' the following submenu appears:
*Ubuntu, with Linux5.19.0-15-generic
Ubuntu, with Linux5.19.0-15-generic (recovery mode)

Selecting the second option, then the system starts loading with the initial
lines of code:
Loading Linux 5.19.0-15-generic ...
Loading initial ramdisk ...

When code has finished loading, the last line at the bottom of the screen is
for unlocking the disk:
Begin: Mounting root fie system ... Begin Running /script/local-top ...
Please unlock disk nvme0n1p3_crypt:

Then i type in the code and hit [return] and more code is loading, until a
recovery menu with purple background appears, with the title:
Recovery Menu (filesystem state: read-only).

I select the first menu item:
resume Resume normal boot
and hit [return].

The menu changes to the notification:
You are now going to exit the recovery mode bla bla bla
with the [OK] button below it.

I hit the [OK] button and then the login screen finally appears.

I will post a video of the complete boot sequence later on as I need
to install a softaware to edit the video.

It is noteworthy that on my previous Ubuntu 22.04 install the same
issue with the frozen splash screen occurred when my system was
updated with Kernel 5.15.5, but then I did not try out to execute the
[ALT] + [CTRL] + [DEL] command.

Therefore the bug is probably affecting all kernels from 5.15.5
upwards.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-15-generic 5.19.0-15.15
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset wl nvidia
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 25 08:30:29 2022
InstallationDate: Installed on 2022-09-24 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220920)
MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic
root=/dev/mapper/vgubuntu-root ro recovery nomodeset dis_ucode_ldr
RelatedPackageVersions:
linux-restricted-modules-5.19.0-15-generic N/A
linux-backports-modules-5.19.0-15-generic N/A
linux-firmware 20220923.gitf09bebf3-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/03/2015
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F10
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97X-UD5H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name:

[Kernel-packages] [Bug 1990750] Re: Boot issue with Ubuntu 22.10 Kinetic Kudu since Kernel 5.19.0.15.15, now hanging with blinking cursor after update to Kernel 5.19.0.21.21

2023-03-04 Thread Ubfan

Note that the Nvidia packaging does not play well with phased updates.
For kernel 519.0-35, the Nvidia 525-76.. driver got removed, but then
phasing held back some nvidia 525-85 packages necessary to rebuild the
nvidia modules -- leaving the currently running kernel without an Nvidia
driver. A day later the phasing caught up, all the Nvidia packages
downloaded, and the modules rebuilt successfully.