[Kernel-packages] [Bug 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Same issue for me. - Kernel: 5.15.0.50-generic - Driver: 515.65.01 - Card: GTX 1660 Workarounds 1. Kernel 5.15.0.48-generic 2. GRUB "nomodeset" -- 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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1740736] Re: The it87.ko driver is too old and does not support newer chipsets (such as Z370).
https://github.com/frankcrawford/it87 The chances of mainlining aren't exactly stellar though. https://lore.kernel.org/all/0134609e-0b03-d9d2-62ba-75d8d8211...@roeck-us.net/ -- 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/1740736 Title: The it87.ko driver is too old and does not support newer chipsets (such as Z370). Status in linux package in Ubuntu: Expired Bug description: Summary: Thermal sensors are not accessible due to being unsupported by the it87.ko module in linux-image-extra which does not include the it8686 model line among others.. Expected behavior: $ journalctl | grep it87: Apr 20 21:36:00 lakshmi kernel: it87: it87 driver version v1.0-38-g948ad8d Apr 20 21:36:00 lakshmi kernel: it87: Found IT8686E chip at 0xa40, revision 2 Apr 20 21:36:00 lakshmi kernel: it87: Beeping is supported Apr 20 21:36:00 lakshmi kernel: it87: Found IT8792E/IT8795E chip at 0xa60, revision 3 Apr 20 21:36:00 lakshmi kernel: it87: Beeping is supported Actual behavior: $ journalctl | grep it87: Apr 20 20:56:31 lakshmi kernel: it87: Found IT8733E chip at 0xa60, revision 3 Apr 20 20:56:31 lakshmi kernel: it87: Beeping is supported Reproducing: sudo modprobe it87 journalctl | grep it87: Apr 20 20:56:31 lakshmi kernel: it87: Found IT8733E chip at 0xa60, revision 3 Apr 20 20:56:31 lakshmi kernel: it87: Beeping is supported ... sudo rmmod it87 git clone https://github.com/groeck/it87.git cd it87/ make sudo make install sudo modprobe it87 $ journalctl | grep it87: Apr 20 21:36:00 lakshmi kernel: it87: it87 driver version v1.0-38-g948ad8d Apr 20 21:36:00 lakshmi kernel: it87: Found IT8686E chip at 0xa40, revision 2 Apr 20 21:36:00 lakshmi kernel: it87: Beeping is supported Apr 20 21:36:00 lakshmi kernel: it87: Found IT8792E/IT8795E chip at 0xa60, revision 3 Apr 20 21:36:00 lakshmi kernel: it87: Beeping is supported Details: $ uname -rsv Linux 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018 $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic $ sudo dmidecode |grep -i product | uniq Product Name: AX370-Gaming 5 Background: Filed a bug report as per question: https://answers.launchpad.net/ubuntu/+question/662421 I'm trying to run lm_sensors on my brand new motherboard (Gigabyte Technology Co., Ltd. Z370 AORUS Ultra Gaming-CF) using the Z370 chipset, and according to the author/maintainer of lm_sensors/it87 driver, fan controls would be supported by chip it8686. Currently such chip is supported only in it87 version https://github.com/groeck/it87; unfortunately both Ubuntu's new LTS Bionic and Torvalds' repositories have got an outdated version of this driver (and possible lm_sensors itself): * http://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/tree/drivers/hwmon/it87.c * https://github.com/torvalds/linux/blob/master/drivers/hwmon/it87.c Can you please update Bionic (at least) to feature this updated driver? Controlling fans speed and other motherboard parameters would be great, especially on new hardware. Thanks! Full discussion thread with driver maintainer here: https://github.com/groeck/lm-sensors/issues/44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740736/+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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Same issue with me. - Kernel: 5.15.0-50-generic (48 also fails) - Driver: 515.76-0ubuntu0.22.04.1 amd64 - Card: RTX3060 LHR (GA106). Currently using the following workaround: - Kernel: 5.15.0-48-generic - Driver: 510.85.02-0ubuntu0.22.04.1 amd64 -- 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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1993040] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1993040 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: Incomplete Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993040/+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 1993041] [NEW] nvidia-driver-515 (515.76-0ubuntu0.22.04.1): blank screen after boot, can't log in
Public bug reported: System: Ubuntu 22.04.1 LTS (x86-64) Kernel: 5.15.0-50-generic NVIDIA card: NVIDIA Corporation GA102 [GeForce RTX 3080 Lite Hash Rate] (rev a1) Problem summary: Just updated "nvidia-driver-515" package from "515.65.01-0ubuntu0.22.04.1" to newest "515.76-0ubuntu0.22.04.1". It results in a blank screen after boot and before showing graphical login (gdm) so can't log in. Seems that keyboard doesn't work in this situation so I can't change to a text session. Instead, I used a remote ssh session to get some info: journalctl.txt, dmesg.txt, lspci.txt and nvidia-smi.txt files attached. Card is connected to monitor using HDMI output. Notes: - Previous "nvidia-driver-515" version, "515.65.01-0ubuntu0.22.04.1", worked as expected. Unfortunately I can't install that version again because it seems to be deleted from the repository. - Previous "nvidia-driver-510" version, "510.85.02-0ubuntu0.22.04.1", works as expected. ** Affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu. https://bugs.launchpad.net/bugs/1993041 Title: nvidia-driver-515 (515.76-0ubuntu0.22.04.1): blank screen after boot, can't log in Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: System: Ubuntu 22.04.1 LTS (x86-64) Kernel: 5.15.0-50-generic NVIDIA card: NVIDIA Corporation GA102 [GeForce RTX 3080 Lite Hash Rate] (rev a1) Problem summary: Just updated "nvidia-driver-515" package from "515.65.01-0ubuntu0.22.04.1" to newest "515.76-0ubuntu0.22.04.1". It results in a blank screen after boot and before showing graphical login (gdm) so can't log in. Seems that keyboard doesn't work in this situation so I can't change to a text session. Instead, I used a remote ssh session to get some info: journalctl.txt, dmesg.txt, lspci.txt and nvidia-smi.txt files attached. Card is connected to monitor using HDMI output. Notes: - Previous "nvidia-driver-515" version, "515.65.01-0ubuntu0.22.04.1", worked as expected. Unfortunately I can't install that version again because it seems to be deleted from the repository. - Previous "nvidia-driver-510" version, "510.85.02-0ubuntu0.22.04.1", works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/1993041/+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 1993040] Re: After resuming from suspend, NIC has WOL disabled
** Project changed: launchpad => linux (Ubuntu) -- 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/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: New Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993040/+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 1993040] [NEW] After resuming from suspend, NIC has WOL disabled
You have been subscribed to a public bug: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- After resuming from suspend, NIC has WOL disabled https://bugs.launchpad.net/bugs/1993040 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Same problem, Ubuntu freezes at startup before user login. - Kernel version: 5.15.0-50-generic - Nvidia driver version: 515.76 - Nvidia card: RTX3060 -- 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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1949721] Re: [HUAWAI MateBook 14 2021] Sound not working - Chip ES8336
Hello. I'm sorry, but, is link above correct for this issue? I don't understand how to install the working setup, may be there is a more detailed guide? Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1949721 Title: [HUAWAI MateBook 14 2021] Sound not working - Chip ES8336 Status in ALSA driver: New Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: WIP here https://github.com/thesofproject/linux/wiki/ES8336-support TL;DR : You need patched 5.19 kernel , alsa , and topology and Patience Original Bug report I installed Ubuntu 20.04 and the sound is not working on the fresh install. The microphone either. I have 5 computers with same hardware. Same problem everywhere. I guess there is a missing driver. Here is lspci output: 00:00.0 Host bridge: Intel Corporation Device 9a14 (rev 01) 00:02.0 VGA compatible controller: Intel Corporation Device 9a49 (rev 01) 00:04.0 Signal processing controller: Intel Corporation Device 9a03 (rev 01) 00:14.0 USB controller: Intel Corporation Device a0ed (rev 20) 00:14.2 RAM memory: Intel Corporation Device a0ef (rev 20) 00:14.3 Network controller: Intel Corporation Device a0f0 (rev 20) 00:15.0 Serial bus controller [0c80]: Intel Corporation Device a0e8 (rev 20) 00:15.1 Serial bus controller [0c80]: Intel Corporation Device a0e9 (rev 20) 00:15.2 Serial bus controller [0c80]: Intel Corporation Device a0ea (rev 20) 00:16.0 Communication controller: Intel Corporation Device a0e0 (rev 20) 00:1d.0 PCI bridge: Intel Corporation Device a0b0 (rev 20) 00:1f.0 ISA bridge: Intel Corporation Device a082 (rev 20) 00:1f.3 Multimedia audio controller: Intel Corporation Device a0c8 (rev 20) 00:1f.4 SMBus: Intel Corporation Device a0a3 (rev 20) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Device a0a4 (rev 20) 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a809 Here is lspci -v output about audio: 00:1f.3 Multimedia audio controller: Intel Corporation Device a0c8 (rev 20) Subsystem: QUANTA Computer Inc Device 1307 Flags: bus master, fast devsel, latency 32, IRQ 147 Memory at 600112 (64-bit, non-prefetchable) [size=16K] Memory at 600100 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: sof-audio-pci Kernel modules: snd_hda_intel, snd_sof_pci The pa-info output is in attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1949721/+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 1992517] Re: rtw88_8822ce: unable to ping anything, "failed to write TX skb to HCI" and "failed to pusk skb, ret -28" in dmesg
I have found out that loading rtw88_pci with disable_aspm=1 and disable_msi=1 fixes the issue. -- 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/1992517 Title: rtw88_8822ce: unable to ping anything, "failed to write TX skb to HCI" and "failed to pusk skb, ret -28" in dmesg Status in linux package in Ubuntu: Confirmed Bug description: I am able to associate with a SSID and receive an IP address, but when trying to ping anything, the ping fails and I get repeated messages in the syslog: Oct 11 22:32:29 Brutus kernel: [51072.191588] rtw_8822ce :03:00.0: failed to pusk skb, ret -28 Oct 11 22:32:30 Brutus kernel: [51073.215591] rtw_8822ce :03:00.0: failed to write TX skb to HCI Oct 11 22:32:30 Brutus kernel: [51073.215600] rtw_8822ce :03:00.0: failed to pusk skb, ret -28 Oct 11 22:32:31 Brutus kernel: [51074.119382] rtw_8822ce :03:00.0: failed to write TX skb to HCI They appear at the same rate as the ping is attempted. Ubuntu Kinetic (22.10), up-to-date as of October 11. Kernel 5.19.0-19-generic. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-19-generic 5.19.0-19.19 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kelner 4762 F wireplumber /dev/snd/seq:kelner 4758 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 11 22:28:26 2022 InstallationDate: Installed on 2020-09-12 (758 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP Pavilion Gaming Laptop 15-ec0xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=UUID=bc5eaf09-3825-4513-9cf6-b6e691ac42a6 ro quiet splash nogpumanager nvidia.NVreg_DynamicPowerManagement=0x02 intel_idle.max_cstate=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-06 (5 days ago) dmi.bios.date: 03/03/2022 dmi.bios.release: 15.13 dmi.bios.vendor: AMI dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86D6 dmi.board.vendor: HP dmi.board.version: 96.45 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 96.45 dmi.modalias: dmi:bvnAMI:bvrF.13:bd03/03/2022:br15.13:efr96.45:svnHP:pnHPPavilionGamingLaptop15-ec0xxx:pvr:rvnHP:rn86D6:rvr96.45:cvnHP:ct10:cvrChassisVersion:sku8BS92EA#AKD: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-ec0xxx dmi.product.sku: 8BS92EA#AKD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992517/+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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Confirm this. And why the change log of the kernel package all goes like 'Bump ABI xxx'? -- 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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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
Could you try booting with a daily live image, available at https://cdimage.ubuntu.com/ubuntu/daily-live/current/, and see if the issue exists with it? Thanks in advance. -- 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: Z97X-UD5H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990750/+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 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows
also affects new 520 driver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1799679 Title: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows Status in Mutter: Unknown Status in metacity package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: Nvidia driver causes Xorg to use 100% CPU and shows high lag and stutter... but only when dragging glxgears/glxheads, or any window over them. Other apps do not exhibit the problem. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Wed Oct 24 19:11:15 2018 InstallationDate: Installed on 2018-05-26 (151 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1799679/+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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Exactly the same issue. 5.15.0-50 did not boot at all. Went back to 5.15.0-48, Ubuntu software manager claimed some updates had to be done and I did them. Now 5.15.0-48 no longer boots, my machine is unusable... Not ideal at all... -- 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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1991725] Re: fails to sign kernel modules
The attachment "dkms.diff" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1991725 Title: fails to sign kernel modules Status in dkms package in Ubuntu: Confirmed Bug description: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1991725/+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 1992976] Re: Jammy update: v6.0.1 upstream stable release
** Changed in: linux-oem-6.0 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1992976 Title: Jammy update: v6.0.1 upstream stable release Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.0 source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.0.1 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992976/+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 1993028] [NEW] Jammy update: v6.0.2 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.0.2 upstream stable release from git://git.kernel.org/ ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux-oem-6.0 (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.0 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1993028 Title: Jammy update: v6.0.2 upstream stable release Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.0 source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.0.2 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1993028/+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 1986965] Re: end user has no hint on choosing the working driver and rollback if fails
For the record, someone has just joinned the Ubuntu-fr chat group and asked what driver to choose since he fear to apply one of the driver in the list without any impact ** Summary changed: - 12th gen intel PC can't boot with nvidia installed + end user has no hint on choosing the working driver and rollback if fails -- 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/1986965 Title: end user has no hint on choosing the working driver and rollback if fails Status in linux package in Ubuntu: Confirmed Bug description: Hi, Ubuntu 22.04 LTS here. I don't know if it is a bug directly linked to linux kernel but: Before my July holidays, PC booted fine, in less than 3sec, when I came back in august, there were some updates to install, including new kernel 5.15.0-46. After installing, I never was able to boot on it. - PC boot - GRUB will load - default select lastest kernel (5.15.0-46) - [see 1st attached PNG] a few line of log appears (same on working boot) - [see 2nd attached PNG] then default boot screen "MSI + ubuntu logo" appears, but "long time" - [see 3rd attached PNG] then [ OK ] linux boot log got displayed and stay on same line for few moment too. I guess that's the attached image that show the most important stuff. - [see 4th attached PNG] then black screen with top left corner with the white blinky cursor - CTRL+ALT+DEL to reboot To use my PC I have to choose additional ubuntu options and select 5.15.0-41 in grub. Using this option allow to boot normaly, and got livepatch applying an update at every reboot (so if it apply the -46, it works during live patch, but sadly not on hard reboot. Do you need more info/logs ? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_15_0_41_44_generic_88 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 18 16:18:56 2022 InstallationDate: Installed on 2022-04-29 (111 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7D25 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6e1766db-1fb6-4255-9258-a7a4c4a1f70d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2021 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.00 dmi.board.asset.tag: Default string dmi.board.name: PRO Z690-A DDR4(MS-7D25) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.00:bd09/14/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-ADDR4(MS-7D25):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D25 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986965/+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 1991725] Re: fails to sign kernel modules
If you don't want to update the dkms package version, you can apply this patch to fix the problem ** Patch added: "dkms.diff" https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1991725/+attachment/5624265/+files/dkms.diff -- 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/1991725 Title: fails to sign kernel modules Status in dkms package in Ubuntu: Confirmed Bug description: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1991725/+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] [NEW] 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
You have been subscribed to a public bug by atactic (atactic): 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: Z97X-UD5H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug kinetic -- 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 https://bugs.launchpad.net/bugs/1990750 You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. -- 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 Kernel 1 5.19.0.15.15, now hanging with blinking cursor after update to Kernel 5.19.0.21.21
** Summary changed: - Boot issue with Ubuntu 22.10 Kinetic Kudu Kernel 1 5.19.0.15.15 + Boot issue with Ubuntu 22.10 Kinetic Kudu Kernel 1 5.19.0.15.15, now hanging with blinking cursor after update to Kernel 5.19.0.21.21 ** Summary changed: - Boot issue with Ubuntu 22.10 Kinetic Kudu Kernel 1 5.19.0.15.15, now hanging with blinking cursor after update to Kernel 5.19.0.21.21 + 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 -- 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/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: Z97X-UD5H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990750/+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 Kernel 1 5.19.0.15.15
Kernel has been updated to version 5.19.0.21.21 and now during boot the system hangs with a white blinking cursor after hitting the [OK] button following the resume Resume normal boot option (see above explanations about boot sequence). I had to hard reboot the system and select instead from the 'Advanced options for Ubuntu' the 'Ubuntu, with Linux5.19.0-19-generic (recovery mode)' to be able to start the system again. Would be thankful to the forum if this bug could be addressed as issues are getting worse and worse, fearing that with the next kernel update that would remove the kernel 5.19.0.19.19 the system may not be starting at all any more due to the just described issue. -- 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/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: Z97X-UD5H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990750/+subscriptions -- Mailing list:
