[Kernel-packages] [Bug 1937914] Re: [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older kernel versions work
*** This bug is a duplicate of bug 1939160 *** https://bugs.launchpad.net/bugs/1939160 ** This bug has been marked a duplicate of bug 1939160 [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older kernel versions work (updated system log) -- 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/1937914 Title: [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older kernel versions work Status in linux package in Ubuntu: New Bug description: While starting the my laptop (Computer Model: HP Probook 450 G6 ProdID 5YH15UT#ABA Memory: 15.5 GB Processor: Intel Core i7-8565U CPU @ 1.80GHz x 8 Graphics: NV118 / Mesa Intel UHD Graphics 620 (WHL GT2) Disk Capacity: 256.1 GB) which runs (OS Name: Ubuntu 20.04.2 LTS OS Type: 64-bit GNOME Version: 3.36.8 Windowing System: X11) the monitor turns off as soon as Ubuntu loads. The OS loads as normal and my external monitor still works, but my laptop monitor does not. I was able to fix the problem by pressing ESC as soon as the HP logo appears during start-up, then selecting "Advanced Ubuntu Options", then choosing an older version of Ubuntu (currently that's ...5.4.0-48..., while I believe the latest version is ...5.8.0-66...). It seems clear that this problem is caused by a bug that was introduced in one of the more recent updates (...5.8.0-59..., maybe?). I am not at all sure that the problem is in xorg; the package identification webpage just suggested that, if the monitor is blank when I would expect to see the Ubuntu logo during startup, then I should say that the relevant package is xorg. I am more than happy to run additional diagnostics that you would recommend if that would help you diagnose and fix the problem. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 24 14:28:51 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:8538] Subsystem: Hewlett-Packard Company GM108M [GeForce MX130] [103c:8542] InstallationDate: Installed on 2021-07-06 (17 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00b7 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b66a Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 004: ID 0bda:b00b Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=8bde40df-a693-4c3a-b5be-05611212add4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2020 dmi.bios.vendor: HP dmi.bios.version: R71 Ver. 01.11.01 dmi.board.name: 8538 dmi.board.vendor: HP dmi.board.version: KBC Version 51.2A.00 dmi.chassis.asset.tag: 5CD9308H3X dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:svnHP:pnHPProBook450G6:pvr:rvnHP:rn8538:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 450 G6 dmi.product.sku: 5YH15UT#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937914/+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 1939211] [NEW] [Dell XPS 13 9380] Screen flickering after upgrading from 5.8 kernel to 5.11 kernel
You have been subscribed to a public bug: Hello! After the upgrade to the 5.8 series kernel to the 5.11 series kernel, I have noticed some screen flickering. I had the same problem previously on Fedora after upgrading to the 5.0 series kernel, but this was not present on Ubuntu 20.04 on either the 5.4 or 5.8 series kernels. On Fedora, it was fixed by turning off panel self-refresh on my Dell XPS 13 9380. I can try that again here if you all think it would be a useful piece of information. In the Fedora bug, it was reported that this problem is fixed in the 5.13 kernel. Let me know whatever else I can do. Thanks! Ben ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 7 18:56:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2021-06-24 (44 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 13 9380 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_l80o1s@/vmlinuz-5.11.0-25-generic root=ZFS=rpool/ROOT/ubuntu_l80o1s ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2021 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd05/27/2021:br1.14:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu -- [Dell XPS 13 9380] Screen flickering after upgrading from 5.8 kernel to 5.11 kernel https://bugs.launchpad.net/bugs/1939211 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 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 1939228] [NEW] screen tearing and redraw in ubuntu 20.04 LTS
You have been subscribed to a public bug: I have used ubuntu 21.04 before on this device and reported a bug and it is solved by making psr value to 0. but in ubuntu 20.04LTS is not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..30.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:30:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.91.03 Fri Jul 2 06:04:10 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sun Aug 8 13:57:13 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-08-08 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82A1 ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=24316984-3147-43ba-aac0-f4497301192e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN32WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN32WW:bd05/27/2021:br1.32:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu -- screen tearing and redraw in ubuntu 20.04 LTS https://bugs.launchpad.net/bugs/1939228 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 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 1912673] Re: sounds not working on Dell XPS 17 (9700)
@Stephane, just run $sudo apt-get update;$sudo apt install linux- image-5.11.0-$(latest version)-generic; linux-modules- extra-5.11.0-$(latest version)-generic;reboot ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/1912673 Title: sounds not working on Dell XPS 17 (9700) Status in linux package in Ubuntu: Fix Released Status in linux package in Debian: Fix Released Bug description: My investigation process: Dell XPS 17 (9700) comes with Windows 10 preinstalled, where sounds worked. I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm headphones, using linux-image-5.4.0-42-generic, I did not try blutooth. I sudo apt upgrade, dist-upgrade to get kernels linux-image-5.8.0-38-generic linux-image-5.8.0-40-generic Sounds did not work. I download linux-image-unsigned-5.10.9-051009-generic. Sounds did not work. I upgrade Dell XPS 9700 firmware from 1.3 to 1.63. Sounds did not work. After googling I found this solution in the comments: https://askubuntu.com/questions/1270442/no-sound-on-xps-17-9700 """ Download and install dkms module: https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/pc-oem- dkms/+packages Alternatively, you can install linux-oem-20.04, it will install the 5.6 kernel with the above driver. Your system may be more stable with 5.4 kernel since it is in wide use. Manually install sof-firmware from Arch Linux: https://archlinux.pkgs.org/rolling/archlinux-extra-x86_64/sof- firmware-1.5.1-1-any.pkg.tar.zst.html You will need to delete the existing "sof" and "sof-tplg" files from the Ubuntu linux-firmware package first. Note if this package gets updated from Canoncial and they don't update these, you will have to delete and then reextract. Files go into the /usr/lib/firmware/intel/sof and /usr/lib/firmware/intel/sof-tplg folders. Manually install the ucm2 files: http://xps17.ddns.net/sof-soundwire.zip These go into /usr/share/alsa/ucm2/sof-soundwire. Delete the contents of the existing sof-soundwire folder (if you have it) and replace them with the ones from the archive. Reboot. You should now have all your audio devices available. If speakers do not play, you may need to run alsamixer (non-root) from a terminal and unmute and set the mixer levels all the way up. """ This solution worked for me on linux-image-5.6.0-1042-oem AFTER manually opening alsa-mixer and changing soundcard to sof. The sound would otherwise just show 'dummy'. My sounds still do not work on 5.8 or 5.10, full name listed above. I did not get to test this temporary fix with 5.4. my full alsa-info: http://alsa-project.org/db/?f=6a638be0cfbe8ed08a010eb26a7702e324dce5ff based on some google research, this seems to be a common problem: https://www.reddit.com/r/Dell/comments/hj8oxw/xps_17_9700_no_audio_on_linux_also_hardware_is/ https://www.reddit.com/r/Dell/comments/hge2yo/no_audio_on_linux_ubuntu_2004_xps_17_9700_realtek/ https://www.reddit.com/r/Dell/comments/j2kdjw/xps_17_9700_on_linux_audio_issue/ etc... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.10 ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19 Uname: Linux 5.6.0-1042-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: neoh 1786 F pulseaudio /dev/snd/pcmC1D0p: neoh 1786 F...m pulseaudio /dev/snd/controlC0: neoh 1786 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 12:08:45 2021 InstallationDate: Installed on 2021-01-20 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0CXCCY dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0CXCCY:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-20 (1 days
[Kernel-packages] [Bug 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws
** Tags added: focal ** Also affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-5.11 (Ubuntu) Importance: Undecided => High ** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Triaged -- 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/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws Status in linux package in Ubuntu: Triaged Status in linux-hwe-5.11 package in Ubuntu: Triaged Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1939228] Re: screen tearing and redraw in ubuntu 20.04 LTS
*** This bug is a duplicate of bug 1937072 *** https://bugs.launchpad.net/bugs/1937072 The kernel in Ubuntu 20.04 got upgraded recently, so now it has the same bug as 21.04 :( Please keep using bug 1937072 ** Package changed: xorg (Ubuntu) => linux-hwe-5.11 (Ubuntu) ** This bug has been marked a duplicate of bug 1937072 [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939228 Title: screen tearing and redraw in ubuntu 20.04 LTS Status in linux-hwe-5.11 package in Ubuntu: New Bug description: I have used ubuntu 21.04 before on this device and reported a bug and it is solved by making psr value to 0. but in ubuntu 20.04LTS is not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..30.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:30:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.91.03 Fri Jul 2 06:04:10 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sun Aug 8 13:57:13 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-08-08 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82A1 ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=24316984-3147-43ba-aac0-f4497301192e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN32WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN32WW:bd05/27/2021:br1.32:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939228/+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 1938823] Re: package nvidia-dkms-470 470.57.02-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error e
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1938823 Title: package nvidia-dkms-470 470.57.02-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: Error when installing driver ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-470 470.57.02-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 3 17:39:22 2021 ErrorMessage: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-08-03 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-470 Title: package nvidia-dkms-470 470.57.02-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1938823/+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 1872431] Re: ubuntu_bpf failed to build on 5.0 OEM-OSP1
5.0 OEM EOL ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux-oem-osp1 (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1872431 Title: ubuntu_bpf failed to build on 5.0 OEM-OSP1 Status in ubuntu-kernel-tests: Won't Fix Status in linux-oem-osp1 package in Ubuntu: Won't Fix Bug description: Test build failed with: undefined reference to `RET_IF' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests' stderr: /bin/sh: 1: llvm-readelf: not found /bin/sh: 1: llvm-readelf: not found Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from latest version at 'include/uapi/linux/bpf.h' Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs from latest version at 'include/uapi/linux/if_link.h' test_select_reuseport.c: In function 'cleanup_per_test': test_select_reuseport.c:619:3: warning: implicit declaration of function 'RET_IF' [-Wimplicit-function-declaration] RET_IF(err, "reset elem in result_map", ^~ /tmp/ccvA9FfO.o: In function `main': test_select_reuseport.c:(.text.startup+0x8ad): undefined reference to `RET_IF' test_select_reuseport.c:(.text.startup+0x8ed): undefined reference to `RET_IF' collect2: error: ld returned 1 exit status make[1]: *** [/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_select_reuseport] Error 1 make: *** [all] Error 2 Possible fix: https://lists.ubuntu.com/archives/kernel-team/2020-April/108912.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1872431/+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 1939251] [NEW] nvidia driver crashes after kernel upgrade
You have been subscribed to a public bug: My two older Zotacs use the NV 340.108 driver and both are having the same issue. After the latest dist-upgrade they boot fine but don't display video, just a blank black screen with a randomly blinking cursor. They're headless but I got into both with ssh in order to uninstall the NV driver and now both boot normally but just use the Nuveau default driver. Unfortunately I can't use either computer like this (no NV driver). Afterward, I tried installing the NV driver with Software-Updater but then received this warning after a few minutes: Error while applying changes pk-client-error-quark: Error while installing package: installed nvidia-340 package post-installation script subprocess returned error exit status 10(313) OK ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.35 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 18:05:04 2021 InstallationDate: Installed on 2021-02-24 (165 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.update-manager.release-upgrades: 2021-02-24T10:56:52.723450 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug dist-upgrade focal -- nvidia driver crashes after kernel upgrade https://bugs.launchpad.net/bugs/1939251 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 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws
Please test latest drm-tip kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ Headers are not needed. -- 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/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws Status in linux package in Ubuntu: Triaged Status in linux-hwe-5.11 package in Ubuntu: Triaged Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1939052] Re: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2
@Cameron, How did you find those verbs? And could you please also take a look at this bug: https://bugzilla.kernel.org/show_bug.cgi?id=203409 could you please find a workable verbs for lenovo c930 as well? ** Bug watch added: Linux Kernel Bug Tracker #203409 https://bugzilla.kernel.org/show_bug.cgi?id=203409 -- 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/1939052 Title: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2 Status in linux package in Ubuntu: New Bug description: All 3 models need the appropriate HDA verbs sent to properly initialize the sound hardware. Additionally, the Legion 15IMHG05 needs automute disabled otherwise speaker output will not return after removing headphones. The good news is that I have working patches for all 3. However, the 13s Gen2 reportedly has some weirdness on the volume control. I don't have this model of laptop so there's not a lot I can do. It seems tuning the volume up and down using the keys on the keyboard can jump the volume up and down in large increments. Volume adjustments via a GUI do not have this issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hiryu 7243 F pulseaudio /dev/snd/controlC0: hiryu 7243 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 5 10:17:57 2021 InstallationDate: Installed on 2021-04-23 (104 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82K6 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash nvidia-drm.modeset=0 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 bluetooth.disable_ertm acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2021 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: H1CN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ITHg6 dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrH1CN33WW:bd07/18/2021:br1.33:efr1.33:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6: dmi.product.family: Legion 7 16ITHg6 dmi.product.name: 82K6 dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6 dmi.product.version: Legion 7 16ITHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939052/+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 1939052] Re: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2
Some info is here: https://github.com/thiagotei/linux-realtek-alc287 You can run a VM using someone's fork of of Qemu (which just adds a bit of logging) with PCIE passthrough of your sound card. Then you can narrow down exactly which verbs are needed. It seems that some of the people in your linked bug are attempting the exact same method already. This is all assuming you're simply missing the verb initialization sequence for your laptop's hardware. For example, the 2021 Lenovo Legion's (both the AMD and Intel models) have a separate issue where the speakers are controlled by a Cirrus Logic (CS35L51) amplifier chip that currently has no support in Linux. I can't do this, because I don't have this model of laptop, and I don't really have anymore time to dedicate to this. I've attempted to send the patches upstream. I never got a response. Not even the slightest amount of feedback. Considering this is something I've done on the side and that I have a lot of other responsibilities, I think this is as likely as far as this is going to go. Good luck on the Lenovo c930. -- 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/1939052 Title: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2 Status in linux package in Ubuntu: New Bug description: All 3 models need the appropriate HDA verbs sent to properly initialize the sound hardware. Additionally, the Legion 15IMHG05 needs automute disabled otherwise speaker output will not return after removing headphones. The good news is that I have working patches for all 3. However, the 13s Gen2 reportedly has some weirdness on the volume control. I don't have this model of laptop so there's not a lot I can do. It seems tuning the volume up and down using the keys on the keyboard can jump the volume up and down in large increments. Volume adjustments via a GUI do not have this issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hiryu 7243 F pulseaudio /dev/snd/controlC0: hiryu 7243 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 5 10:17:57 2021 InstallationDate: Installed on 2021-04-23 (104 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82K6 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash nvidia-drm.modeset=0 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 bluetooth.disable_ertm acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2021 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: H1CN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ITHg6 dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrH1CN33WW:bd07/18/2021:br1.33:efr1.33:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6: dmi.product.family: Legion 7 16ITHg6 dmi.product.name: 82K6 dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6 dmi.product.version: Legion 7 16ITHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939052/+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 1939251] Re: nvidia driver crashes after kernel upgrade
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please don't post/attach a .crash file. The crash file should be submitted using the `ubuntu-bug /var/crash/[filename].crash` which gathers more details and populates fields making the .crash file much easier to explore. I suggest you submit that file, as this report is incomplete; you've tagged it related to `ubuntu-release-upgrader` but you've not used that tool (it would have upgraded your system to 20.10; ie. it's the tool that upgrades you from one release to the next (20.04 to 20.10, or 20.04 to 22.04.1) and doesn't relate to a normal 'dist-upgrade'. This issue likely relates to the HWE kernel, as recently the 5.8 kernel stack (from 20.10) was moved to 5.11 (from 21.04) and thus package likely should have been `linux-generic-hwe-20.04` (ie. switch to newer 5.11 is your issue). (LTS releases have two kernel stack choices; GA the more stable stays on 5.4, HWE upgrades during the first ~two years of life). I'll mark this 'incomplete' allowing you to submit your crash file and create a new bug. If you believe I've in error, or made an error, please leave a comment saying why, and the bug report status can be returned to "New". ** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu) ** 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/1939251 Title: nvidia driver crashes after kernel upgrade Status in linux package in Ubuntu: Incomplete Bug description: My two older Zotacs use the NV 340.108 driver and both are having the same issue. After the latest dist-upgrade they boot fine but don't display video, just a blank black screen with a randomly blinking cursor. They're headless but I got into both with ssh in order to uninstall the NV driver and now both boot normally but just use the Nuveau default driver. Unfortunately I can't use either computer like this (no NV driver). Afterward, I tried installing the NV driver with Software-Updater but then received this warning after a few minutes: Error while applying changes pk-client-error-quark: Error while installing package: installed nvidia-340 package post-installation script subprocess returned error exit status 10(313) OK ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.35 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 18:05:04 2021 InstallationDate: Installed on 2021-02-24 (165 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.update-manager.release-upgrades: 2021-02-24T10:56:52.723450 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939251/+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 1939205] Re: sound dummy output 21.04
If you plug a headphone to the Front Headphone Jack or Lineout Jack, could you see a output device? -- 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/1939205 Title: sound dummy output 21.04 Status in linux package in Ubuntu: New Bug description: no more sound device /output since dist upgrade from 20.10 to 21.04 tried both official ubuntu kernel 5.11.0.26 and newer 5.13.8-051308-generic alsa log: http://alsa-project.org/db/?f=07dfaad1d5d30948449dc36f0caaf39c99145cce lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 apt-cache policy pkgname N: Unable to locate package pkgname ubuntu-bug linux: package not installed cat /proc/version_signature > version.log cat: /proc/version_signature: No such file or directory sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error be descriptive in helping as im a newbie to linux troubleshoot :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939205/+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 1939052] Re: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2
Well noted, thanks for sharing the info. -- 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/1939052 Title: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2 Status in linux package in Ubuntu: New Bug description: All 3 models need the appropriate HDA verbs sent to properly initialize the sound hardware. Additionally, the Legion 15IMHG05 needs automute disabled otherwise speaker output will not return after removing headphones. The good news is that I have working patches for all 3. However, the 13s Gen2 reportedly has some weirdness on the volume control. I don't have this model of laptop so there's not a lot I can do. It seems tuning the volume up and down using the keys on the keyboard can jump the volume up and down in large increments. Volume adjustments via a GUI do not have this issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hiryu 7243 F pulseaudio /dev/snd/controlC0: hiryu 7243 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 5 10:17:57 2021 InstallationDate: Installed on 2021-04-23 (104 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82K6 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash nvidia-drm.modeset=0 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 bluetooth.disable_ertm acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2021 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: H1CN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ITHg6 dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrH1CN33WW:bd07/18/2021:br1.33:efr1.33:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6: dmi.product.family: Legion 7 16ITHg6 dmi.product.name: 82K6 dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6 dmi.product.version: Legion 7 16ITHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939052/+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 1936708] Re: Wobbly graphics on built-in display since linux-image-5.11.0-22-generic
** Description changed: + == SRU Justification == + + [Impact] + Wobbly graphics after a kernel update. + + [Fix] + Older panels may require more bandwidth then advertised, so we need to + use max params for them. + + [Test] + Multiple users tested with positive result. + + [Where problems could occur] + This patch reverts to the old behavior, which is to use max parameters, + for older panels. If there's any new panel reports with older DP + version, this might change the behavior on it. + + == Original Bug Report == + Lenovo laptop with Intel + Nvidia graphics. Since booting from linux-image-5.11.0-22-generic, the built-in display is unusable, with wobbling horizontal stripes from the disk decryption prompt onwards: https://www.youtube.com/watch?v=LyRTuPzCe2I HDMI output works fine. If I boot from linux-image-5.11.0-18-generic instead, all is well. If I use Recovery mode with linux-image-5.11.0-22-generic and continue bootup, it's usable but there's no HDMI output. I think others may be having this issue too: https://askubuntu.com/questions/1351188/weird-graphical-glitches-appears-only-on-integrated-display-on-any-ubuntu-base# ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 1598 F pulseaudio /dev/snd/controlC0: alex 1598 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 17 09:50:31 2021 InstallationDate: Installed on 2021-01-03 (194 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 80DU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-22 (55 days ago) dmi.bios.date: 08/18/2014 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN31WW(V1.14) dmi.board.asset.tag: 31900058WIN dmi.board.name: Lenovo Y70-70 Touch dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y70-70 Touch dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvr9ECN31WW(V1.14):bd08/18/2014:br1.49:efr1.49:svnLENOVO:pn80DU:pvrLenovoY70-70Touch:rvnLENOVO:rnLenovoY70-70Touch:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY70-70Touch: dmi.product.family: IDEAPAD dmi.product.name: 80DU dmi.product.sku: LENOVO_MT_80DU_BU_idea_FM_Lenovo Y70-70 Touch dmi.product.version: Lenovo Y70-70 Touch dmi.sys.vendor: LENOVO ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.13 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided => Medium -- 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/1936708 Title: Wobbly graphics on built-in display since linux- image-5.11.0-22-generic Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Bug description: == SRU Justification == [Impact] Wobbly graphics after a kernel update. [Fix] Older panels may require more bandwidth then advertised, so we need to use max params for them.
Re: [Kernel-packages] [Bug 1939251] Re: nvidia driver crashes after kernel upgrade
Chris, I followed your instructions but it didn't work complaining about a permission issue. So I ran it with sudo and it seemed to work. $ sudo ubuntu-bug /var/crash/nvidia-340.0.crash But it still appears that the bug didn't attached the crash report. Sorry, I tried. On 8/8/21 6:30 PM, Chris Guiver wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. > > Please don't post/attach a .crash file. The crash file should be > submitted using the `ubuntu-bug /var/crash/[filename].crash` which > gathers more details and populates fields making the .crash file much > easier to explore. > > I suggest you submit that file, as this report is incomplete; you've > tagged it related to `ubuntu-release-upgrader` but you've not used that > tool (it would have upgraded your system to 20.10; ie. it's the tool > that upgrades you from one release to the next (20.04 to 20.10, or 20.04 > to 22.04.1) and doesn't relate to a normal 'dist-upgrade'. > > This issue likely relates to the HWE kernel, as recently the 5.8 kernel > stack (from 20.10) was moved to 5.11 (from 21.04) and thus package > likely should have been `linux-generic-hwe-20.04` (ie. switch to newer > 5.11 is your issue). (LTS releases have two kernel stack choices; GA > the more stable stays on 5.4, HWE upgrades during the first ~two years > of life). > > I'll mark this 'incomplete' allowing you to submit your crash file and > create a new bug. If you believe I've in error, or made an error, > please leave a comment saying why, and the bug report status can be > returned to "New". > > ** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu) > > ** 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/1939251 Title: nvidia driver crashes after kernel upgrade Status in linux package in Ubuntu: Incomplete Bug description: My two older Zotacs use the NV 340.108 driver and both are having the same issue. After the latest dist-upgrade they boot fine but don't display video, just a blank black screen with a randomly blinking cursor. They're headless but I got into both with ssh in order to uninstall the NV driver and now both boot normally but just use the Nuveau default driver. Unfortunately I can't use either computer like this (no NV driver). Afterward, I tried installing the NV driver with Software-Updater but then received this warning after a few minutes: Error while applying changes pk-client-error-quark: Error while installing package: installed nvidia-340 package post-installation script subprocess returned error exit status 10(313) OK ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.35 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 18:05:04 2021 InstallationDate: Installed on 2021-02-24 (165 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.update-manager.release-upgrades: 2021-02-24T10:56:52.723450 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939251/+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 1924624] Re: After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics a lot of glitches render screen unusable
There are countless different ways a GPU HANG can occur so let's assume it's a new problem. Please open a new bug by running: ubuntu-bug linux-image-5.11.0-25-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1924624 Title: After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics a lot of glitches render screen unusable Status in linux package in Ubuntu: Fix Released Status in linux-meta-hwe-5.8 package in Ubuntu: Fix Released Bug description: After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was suddenly extremely glitchy. Icons from the desktop flash through the browser, windows top bar gets distorted, all sort of glitches appear, parts of characters are missing in terminal, scrolling is inconsistent and the whole desktop becomes unusable. Under wayland the graphics are a bit more stable, but lots of glitches appear anyway, video reproduction in browser is stuttering and wobbly. Booting with previous kernel 5.8.0-48 seems to fix the issues. 5.8.0-50 is broken as well. this is the result of 'sudo lshw -c video' on my hp Elitebook 8470: *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:33 memory:d400-d43f memory:c000-cfff ioport:4000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+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 1937321] Re: System freeze (amdgpu kernel crash on resume from suspend)
The "invalid signature" problem I think is caused by Secure Boot. Try disabling Secure Boot in your BIOS. Also sorry again because it sounds like that libc6 problem is going to keep getting in the way. But good news: Kernel 5.11 has now been officially released to Ubuntu 20.04 updates. So you can delete the test kernel packages with: sudo dpkg -P PACKAGENAME1 PACKAGENAME2 and then do a system update to get the official update to 5.11: sudo apt update sudo apt full-upgrade -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1937321 Title: System freeze (amdgpu kernel crash on resume from suspend) Status in linux-hwe-5.8 package in Ubuntu: Incomplete Bug description: System freezes after I close the lid on the laptop and leave it closed overnight. It doesn't respond to any key presses or mouse clicks including Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the "suspend" screen showing but mostly it's just black. The Power settings -Dim screen when inactive = yes Blank screen = never Wifi and Bluetooth can be turned off to save power = yes Automatic suspend on battery power = yes Power button action = Power off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 22 17:34:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87cf] InstallationDate: Installed on 2021-06-30 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15-ef1xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2021 dmi.bios.release: 15.34 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.19 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.19 dmi.modalias: dmi:bvnAMI:bvrF.34:bd03/10/2021:br15.34:efr37.19:svnHP:pnHPLaptop15-ef1xxx:pvr:rvnHP:rn8707:rvr37.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-ef1xxx dmi.product.sku: 27A48UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1937321/+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 1939211] Re: [Dell XPS 13 9380] Screen flickering after upgrading from 5.8 kernel to 5.11 kernel
Yes please try turning off panel self refresh again by adding this kernel parameter: i915.enable_psr=0 ** Summary changed: - Screen flickering after upgrading from 5.8 kernel to 5.11 kernel + [Dell XPS 13 9380] Screen flickering after upgrading from 5.8 kernel to 5.11 kernel ** Package changed: xorg (Ubuntu) => linux-hwe-5.11 (Ubuntu) ** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Incomplete ** Tags added: regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939211 Title: [Dell XPS 13 9380] Screen flickering after upgrading from 5.8 kernel to 5.11 kernel Status in linux-hwe-5.11 package in Ubuntu: Incomplete Bug description: Hello! After the upgrade to the 5.8 series kernel to the 5.11 series kernel, I have noticed some screen flickering. I had the same problem previously on Fedora after upgrading to the 5.0 series kernel, but this was not present on Ubuntu 20.04 on either the 5.4 or 5.8 series kernels. On Fedora, it was fixed by turning off panel self-refresh on my Dell XPS 13 9380. I can try that again here if you all think it would be a useful piece of information. In the Fedora bug, it was reported that this problem is fixed in the 5.13 kernel. Let me know whatever else I can do. Thanks! Ben ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 7 18:56:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2021-06-24 (44 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 13 9380 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_l80o1s@/vmlinuz-5.11.0-25-generic root=ZFS=rpool/ROOT/ubuntu_l80o1s ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2021 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd05/27/2021:br1.14:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939211/+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 1844384] Re: Display bug with kernel 5.2/5.3 on Dell XPS 13
Thank you for reporting this bug to Ubuntu. Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- 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/1844384 Title: Display bug with kernel 5.2/5.3 on Dell XPS 13 Status in linux package in Ubuntu: Won't Fix Bug description: Hello, I use in multiboot Ubuntu and Archlinux, I had the opportunity to use many kernels and I notice a random display problem (see screenshot) that happens from time to time on my Dell XPS but only from kernel 5.2 (and following). Under Ubuntu 19.04 with the 5.0 kernel I don't have this problem, under Archlinux with the old kernels (4.19LTS, 5.0, 5.1) I didn't have this problem either. But since 5.2 whether it is under Ubuntu or Archlinux, I have noticed this problem which is difficult to describe, it is a kind of band that appears at the top of the screen with a different size (sometimes very wide). The problem occurs randomly, sometimes it can go 30 minutes without seeing it appear and sometimes it can appear full of times for a few minutes. The problem is not specific to Ubuntu but to the kernel since 5.2 and following. Under the 19.10 of Ubuntu in development with the 5.3 kernel, the problem is still present. Could you please forward this bug to the team that deals with the linux kernel. (the 2 screenshots were taken under Ubuntu 19.10 with the 5.3 kernel but under Archlinux it's the same thing. Configuration : Dell XPS 13 model 2019 (9380) Graphics chipset: Intel® UHD 620 (Whiskey Lake 3x8 GT2) Noted that this problem can occur regardless of the activity on the desktop (browser, video player...), sometimes the screen skips completely for a tenth of a second. Please correct the problem quickly capture1: https://nsa40.casimages.com/img/2019/09/17/190917050728230823.jpg capture2: https://nsa40.casimages.com/img/2019/09/17/190917050801231741.jpg --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: simon 22176 F pulseaudio /dev/snd/pcmC0D0p: simon 22176 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-07-18 (60 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic root=UUID=d10cf0fc-051d-4ccd-b2da-e944d0ddd735 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: eoan Uname: Linux 5.3.0-10-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-17 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/05/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2019-07-18T20:23:25.974818 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844384/+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 1939052] Re: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2
@Cameron, These patches need to be sent to upstream first. thx. -- 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/1939052 Title: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2 Status in linux package in Ubuntu: New Bug description: All 3 models need the appropriate HDA verbs sent to properly initialize the sound hardware. Additionally, the Legion 15IMHG05 needs automute disabled otherwise speaker output will not return after removing headphones. The good news is that I have working patches for all 3. However, the 13s Gen2 reportedly has some weirdness on the volume control. I don't have this model of laptop so there's not a lot I can do. It seems tuning the volume up and down using the keys on the keyboard can jump the volume up and down in large increments. Volume adjustments via a GUI do not have this issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hiryu 7243 F pulseaudio /dev/snd/controlC0: hiryu 7243 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 5 10:17:57 2021 InstallationDate: Installed on 2021-04-23 (104 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82K6 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash nvidia-drm.modeset=0 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 bluetooth.disable_ertm acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2021 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: H1CN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ITHg6 dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrH1CN33WW:bd07/18/2021:br1.33:efr1.33:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6: dmi.product.family: Legion 7 16ITHg6 dmi.product.name: 82K6 dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6 dmi.product.version: Legion 7 16ITHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939052/+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 1938408] Re: EHL board does not support soft reboot
Hi @Doug, The same test kernel has been built. Please refer to bug 1938413 comment #17. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1938408 Title: EHL board does not support soft reboot Status in intel: New Status in linux-intel package in Ubuntu: In Progress Bug description: [Summary]Telling the EHL board to reboot from within Ubuntu causes it to hang, forcing you to do a hard reboot. [Steps to reproduce] 1. Open terminal window. 2. $ reboot [Expected result] System should gracefullyl reboot. [Actual result] Screen goes blank except for a cursor. System does not reboot. You must hard reboot (pull the plug) [Failure rate]100% [Additional information] CID: 202105-29063 SKU: system-manufacturer: Intel Corporation system-product-name: Elkhart Lake Embedded Platform bios-version: EHLSFWI1.R00.2091.A00.2002250754 CPU: Genuine Intel(R) CPU @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] kernel-version: 5.11.0-1009-intel To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938408/+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 1938413] Re: Shutdown hangs on EHL board
Hi @Doug, I have uploaded a new test kernel on my ppa, please refer to [1] or follow the steps below to verify: [Installation steps] $ sudo add-apt-repository ppa:shanelin/linux-intel $ sudo apt-get update $ sudo apt-get install linux-image-unsigned-5.11.0-1011-intel=5.11.0-1011.13+lp1938408~lp1938413~0805 linux-modules-5.11.0-1011-intel=5.11.0-1011.13+lp1938408~lp1938413~0805 linux-modules-extra-5.11.0-1011-intel=5.11.0-1011.13+lp1938408~lp1938413~0805 --- [1] https://launchpad.net/~shanelin/+archive/ubuntu/linux-intel [2] Test passed (5/5) for: CID: 202105-29064 BIOS: EHLSFWI1.R00.2091.A00.2002250754 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1938413 Title: Shutdown hangs on EHL board Status in intel: New Status in linux-intel package in Ubuntu: In Progress Bug description: [Summary]Go to Power -> Shutdown and the screen goes blank, but the system does not shut down. You cannot recover and have to perform a hard reboot. [Steps to reproduce] 1. Boot up Ubuntu 2. Power -> Shutdown (click ok) [Expected result] System should cleanly shut down. [Actual result] Screen blanks with a blinking cursor, the system does not shut down, the fan is still on. System is unresponsive, forcing you to do a hard reset. [Failure rate]100% [Additional information] CID: 20215-29063 SKU: system-manufacturer: Intel Corporation system-product-name: Elkhart Lake Embedded Platform bios-version: EHLSFWI1.R00.2091.A00.2002250754 CPU: Genuine Intel(R) CPU @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] kernel-version: 5.11.0-1009-intel [Stage] Device froze, issue reported and logs collected right after a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938413/+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 1926597] Re: Linux 5.10.0-1024.25 breaks HDMI with Intel i915
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1926597 Title: Linux 5.10.0-1024.25 breaks HDMI with Intel i915 Status in linux package in Ubuntu: Expired Bug description: Hi, [Thinkpad T480s, Intel iGPU 8550u, Ubuntu Focal up-to-date, GNOME Wayland session] Previous 5.10.0-1023.24 was ok. Kernel 5.8 HWE is ok. I did not test a X session. Plugging HDMI after GNOME is loaded fails to display anything on the HDMI display. Plugging HDMI at boot or at GDM screen makes the HDMI display works as usual. Unplugging HDMI (display only on this one) during GNOME session does not update displays state. Nothing happens. I have to press the switch-display-key on my laptop to actualize the setup and make my laptop's display active. When I unplug HDMI during GNOME session, nothing appears in logs. My laptop fails to enter sleep after having unplugged the HDMI. Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926597/+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 1787857] Re: USB mouse cursor lags after random time of correct behaviour
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in linux package in Ubuntu: Expired Status in rtirq package in Ubuntu: Invalid Bug description: I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I noticed the following behaviour: after havig logged in, my USB mouse works normally for about ten seconds, then the cursor starts lagging a lot which makes the mouse pretty much unusable. The last dmesg always contain lines these: (more in attached file) [<9e659b0c>] irq_default_primary_handler threaded [] usb_hcd_irq [<9e659b0c>] irq_default_primary_handler threaded [ ] _rtl_pci_interrupt [rtl_pci] Disabling IRQ #18 Out of frustration & curiosity I disabled most autostart apps (Settings > Session ... > Autostart) and re-enabled them after rebooting. Since then I rarely encounter the lagging cursor. If I open Settings > Mouse & Touchpad and toggle any option on/off the cursor starts lagging. How can make the cursor work reliably? Some comment in dmesg mentions "irqpoll" boot option Ubuntu Studio 18.04.1 4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+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 1939251] Re: nvidia driver crashes after kernel upgrade
*** This bug is a duplicate of bug 1939254 *** https://bugs.launchpad.net/bugs/1939254 Re-filed as https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-340/+bug/1939254 ** This bug has been marked a duplicate of bug 1939254 nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build -- 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/1939251 Title: nvidia driver crashes after kernel upgrade Status in linux package in Ubuntu: Incomplete Bug description: My two older Zotacs use the NV 340.108 driver and both are having the same issue. After the latest dist-upgrade they boot fine but don't display video, just a blank black screen with a randomly blinking cursor. They're headless but I got into both with ssh in order to uninstall the NV driver and now both boot normally but just use the Nuveau default driver. Unfortunately I can't use either computer like this (no NV driver). Afterward, I tried installing the NV driver with Software-Updater but then received this warning after a few minutes: Error while applying changes pk-client-error-quark: Error while installing package: installed nvidia-340 package post-installation script subprocess returned error exit status 10(313) OK ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.35 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 18:05:04 2021 InstallationDate: Installed on 2021-02-24 (165 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.update-manager.release-upgrades: 2021-02-24T10:56:52.723450 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939251/+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 1919122] Re: net test from ubuntu_kernel_selftests / ubuntu_bpf failed to build on F-OEM-5.10 (Cannot find a vmlinux for VMLINUX_BTF)
** Summary changed: - net test from ubuntu_kernel_selftests / ubuntu_bpf failed to build on F-OEM-5.10 + net test from ubuntu_kernel_selftests / ubuntu_bpf failed to build on F-OEM-5.10 (Cannot find a vmlinux for VMLINUX_BTF) ** Tags added: sru-20210719 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1919122 Title: net test from ubuntu_kernel_selftests / ubuntu_bpf failed to build on F-OEM-5.10 (Cannot find a vmlinux for VMLINUX_BTF) Status in ubuntu-kernel-tests: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Confirmed Bug description: Issue found on 5.10.0-1017.18-oem When trying to build the prerequisite bpf test for the net test, the build failed with: *** Cannot find a vmlinux for VMLINUX_BTF at any of " ../../../../vmlinux /sys/kernel/btf/vmlinux /boot/vmlinux-5.10.0-1017-oem". Stop. This should not be considered as a regression as we didn't add ubuntu_kernel_selftest back to the test plan until recently, so it's not tested for a while. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1919122/+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 1925126] Re: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50
Reproduced today with kernel linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1: Aug 8 22:18:11 kernel: [37254.612789] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: Aug 8 22:18:11 kernel: [37254.612858] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Aug 8 22:18:11 kernel: [37254.714421] i915 :00:02.0: [drm] VMSVGA FIFO[8731] context reset due to GPU hang Aug 8 22:18:14 kernel: [37257.670342] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: Aug 8 22:18:14 kernel: [37257.670382] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Aug 8 22:18:14 kernel: [37257.773493] i915 :00:02.0: [drm] kwin_x11[7538] context reset due to GPU hang System is Asus P8Z68V-Pro Gen3, i7-3770, iGPU: 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 61 Memory at f740 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] Expansion ROM at 000c [virtual] [disabled] [size=128K] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 On first look the symptoms are identical to the already resolved issue https://bugs.launchpad.net/ubuntu/+source/linux-meta- hwe-5.8/+bug/1923844 (duplicate of https://bugs.launchpad.net/ubuntu/+source/linux-meta- hwe-5.8/+bug/1924624). Regression in latest kernel? -- 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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no
[Kernel-packages] [Bug 1924624] Re: After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics a lot of glitches render screen unusable
Today regression with kernel linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1: Aug 8 22:18:11 kernel: [37254.612789] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: Aug 8 22:18:11 kernel: [37254.612858] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Aug 8 22:18:11 kernel: [37254.714421] i915 :00:02.0: [drm] VMSVGA FIFO[8731] context reset due to GPU hang Aug 8 22:18:14 kernel: [37257.670342] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: Aug 8 22:18:14 kernel: [37257.670382] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Aug 8 22:18:14 kernel: [37257.773493] i915 :00:02.0: [drm] kwin_x11[7538] context reset due to GPU hang System is Asus P8Z68V-Pro Gen3, i7-3770, iGPU HD4000: 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 61 Memory at f740 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] Expansion ROM at 000c [virtual] [disabled] [size=128K] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 Was the fix of this bug properly ported to 5.11? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1924624 Title: After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics a lot of glitches render screen unusable Status in linux package in Ubuntu: Fix Released Status in linux-meta-hwe-5.8 package in Ubuntu: Fix Released Bug description: After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was suddenly extremely glitchy. Icons from the desktop flash through the browser, windows top bar gets distorted, all sort of glitches appear, parts of characters are missing in terminal, scrolling is inconsistent and the whole desktop becomes unusable. Under wayland the graphics are a bit more stable, but lots of glitches appear anyway, video reproduction in browser is stuttering and wobbly. Booting with previous kernel 5.8.0-48 seems to fix the issues. 5.8.0-50 is broken as well. this is the result of 'sudo lshw -c video' on my hp Elitebook 8470: *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:33 memory:d400-d43f memory:c000-cfff ioport:4000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+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 1939246] [NEW] With the proprietary nvidia drivers, suspend fails if I try to suspend while the connected monitors are powered off
Public bug reported: As the title says, I'm unable to suspend if I have monitors connected which don't have power. I hit the suspend button (or run `pm-suspend`), and the computer just becomes unresponsive, stops reacting to input, shows nothing on the screen (if I turn the monitors on again), is unreachable through SSH, but the fans are still running, LEDs still glowing, and it can't be waken up by any other means than a force restart through cutting power or holding down the power button. I followed this guide to debug this problem: https://wiki.ubuntu.com/DebuggingKernelSuspend - the relevant part of the dmesg output is: [0.756829] PM: Magic number: 0:484:522 [0.756830] PM: hash matches drivers/base/power/main.c:1598 [0.756849] pci :07:00.0: hash matches That :07:00.0 device is my nvidia GPU (a GTX 1080Ti). --- 1. Which part of the process does the issue occur with, the suspend to ram, or resuming from? The issue seems to happen during suspend. I believe this because during a normal suspend, the GPU's RGB LEDs will turn off while the machine is suspended, but when this issue occurs, the GPU's RGB LEDs stay on. (I knew those RGB LEDs would come in useful some day!) 2. Please advise how you suspended specifically. While reproducing the issue for this bug report, I've been using `pm-suspend`. But it also happens when clicking the suspend button on my keyboard. 3. Please advise how you resumed specifically. When this issue occurs, I can't resume. I hold the power button in until the system powers off and then I boot as normal. --- I'm unable to respond to the points which require running the latest kernel, since the proprietary drivers don't seem to work on the latest kernel (or maybe they're running in some form of fallback mode? I see a 640x480 output on one of my monitors). And, as a final note, I'm sorry about this bug report. I know there's probably nothing anybody can do about a bug in the proprietary drivers. That sucks. I wish we didn't have to deal with bad proprietary graphics drivers anymore. But I figured it's better to report the issue than to not report it. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nvidia-driver-470 470.57.02-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 23:03:57 2021 InstallationDate: Installed on 2021-06-10 (59 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1939246 Title: With the proprietary nvidia drivers, suspend fails if I try to suspend while the connected monitors are powered off Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: As the title says, I'm unable to suspend if I have monitors connected which don't have power. I hit the suspend button (or run `pm- suspend`), and the computer just becomes unresponsive, stops reacting to input, shows nothing on the screen (if I turn the monitors on again), is unreachable through SSH, but the fans are still running, LEDs still glowing, and it can't be waken up by any other means than a force restart through cutting power or holding down the power button. I followed this guide to debug this problem: https://wiki.ubuntu.com/DebuggingKernelSuspend - the relevant part of the dmesg output is: [0.756829] PM: Magic number: 0:484:522 [0.756830] PM: hash matches drivers/base/power/main.c:1598 [0.756849] pci :07:00.0: hash matches That :07:00.0 device is my nvidia GPU (a GTX 1080Ti). --- 1. Which part of the process does the issue occur with, the suspend to ram, or resuming from? The issue seems to happen during suspend. I believe this because during a normal suspend, the GPU's RGB LEDs will turn off while the machine is suspended, but when this issue occurs, the GPU's RGB LEDs stay on. (I knew those RGB LEDs would come in useful some day!) 2. Please advise how you suspended specifically. While reproducing the issue for this bug report, I've been using `pm-suspend`. But it also happens when clicking the suspend button on my keyboard. 3. Please advise how you resumed specifically. When this issue occurs, I can't resume. I hold the power button in until the system powers off and then I boot as normal. --- I'm unable to respond to the points which require running the latest
[Kernel-packages] [Bug 1939246] Re: With the proprietary nvidia drivers, suspend fails if I try to suspend while the connected monitors are powered off
** Attachment added: "I forgot to add the dmesg log, sorry" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939246/+attachment/5516692/+files/dmesg-hash-matches-nvidia.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1939246 Title: With the proprietary nvidia drivers, suspend fails if I try to suspend while the connected monitors are powered off Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: As the title says, I'm unable to suspend if I have monitors connected which don't have power. I hit the suspend button (or run `pm- suspend`), and the computer just becomes unresponsive, stops reacting to input, shows nothing on the screen (if I turn the monitors on again), is unreachable through SSH, but the fans are still running, LEDs still glowing, and it can't be waken up by any other means than a force restart through cutting power or holding down the power button. I followed this guide to debug this problem: https://wiki.ubuntu.com/DebuggingKernelSuspend - the relevant part of the dmesg output is: [0.756829] PM: Magic number: 0:484:522 [0.756830] PM: hash matches drivers/base/power/main.c:1598 [0.756849] pci :07:00.0: hash matches That :07:00.0 device is my nvidia GPU (a GTX 1080Ti). --- 1. Which part of the process does the issue occur with, the suspend to ram, or resuming from? The issue seems to happen during suspend. I believe this because during a normal suspend, the GPU's RGB LEDs will turn off while the machine is suspended, but when this issue occurs, the GPU's RGB LEDs stay on. (I knew those RGB LEDs would come in useful some day!) 2. Please advise how you suspended specifically. While reproducing the issue for this bug report, I've been using `pm-suspend`. But it also happens when clicking the suspend button on my keyboard. 3. Please advise how you resumed specifically. When this issue occurs, I can't resume. I hold the power button in until the system powers off and then I boot as normal. --- I'm unable to respond to the points which require running the latest kernel, since the proprietary drivers don't seem to work on the latest kernel (or maybe they're running in some form of fallback mode? I see a 640x480 output on one of my monitors). And, as a final note, I'm sorry about this bug report. I know there's probably nothing anybody can do about a bug in the proprietary drivers. That sucks. I wish we didn't have to deal with bad proprietary graphics drivers anymore. But I figured it's better to report the issue than to not report it. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nvidia-driver-470 470.57.02-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 23:03:57 2021 InstallationDate: Installed on 2021-06-10 (59 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939246/+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 1939222] Re: DisplayPort over USB-C not working after release update
** Package changed: ubuntu-release-upgrader (Ubuntu) => 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/1939222 Title: DisplayPort over USB-C not working after release update Status in linux package in Ubuntu: Confirmed Bug description: After (automated) update from 5.8.0-63 to 5.11.0.-25 the displayport over usb-c (Thinkpad e15gen2 i5-1135G7 / GeForce MX450/PCIe/SSE2) is not working properly. Revert to 5.8.0-63 resolves the problem. The problem is independent of nvdia-drivers (tried 470, 460 and intel only drivers). Same Monitors connected over HDMI work properly. Problem is limited to displayport over usb-c. Problem symptoms: Monitor atttached over displayport allows only VGA resolution(1024 * 768) and flickers (on/off periodically). no special error messages found in dmesg except for abundance of "i915 :00:02.0: [drm] *ERROR* failed to enable link training" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.35 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 09:12:10 2021 InstallationDate: Installed on 2021-06-14 (54 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IL:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939222/+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 1939225] [NEW] kernel NULL pointer dereference, address: 0000000000000000
Public bug reported: There was a null pointer error. I attached the error log from journal control. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 09:54:04 2021 SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "error.txt" https://bugs.launchpad.net/bugs/1939225/+attachment/5516592/+files/error.txt -- 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/1939225 Title: kernel NULL pointer dereference, address: Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: There was a null pointer error. I attached the error log from journal control. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 09:54:04 2021 SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939225/+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 1939222] [NEW] DisplayPort over USB-C not working after release update
You have been subscribed to a public bug: After (automated) update from 5.8.0-63 to 5.11.0.-25 the displayport over usb-c (Thinkpad e15gen2 i5-1135G7 / GeForce MX450/PCIe/SSE2) is not working properly. Revert to 5.8.0-63 resolves the problem. The problem is independent of nvdia-drivers (tried 470, 460 and intel only drivers). Same Monitors connected over HDMI work properly. Problem is limited to displayport over usb-c. Problem symptoms: Monitor atttached over displayport allows only VGA resolution(1024 * 768) and flickers (on/off periodically). no special error messages found in dmesg except for abundance of "i915 :00:02.0: [drm] *ERROR* failed to enable link training" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.35 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 09:12:10 2021 InstallationDate: Installed on 2021-06-14 (54 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IL:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug dist-upgrade focal -- DisplayPort over USB-C not working after release update https://bugs.launchpad.net/bugs/1939222 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 1769236] Re: CPU frequency stuck at minimum value
Thermald 1.9.1-1ubuntu0.4 contains the backport of the adaptive engine, see bug https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186 Thermald 1.9.1-1ubuntu.05 contains the following fixes that may also be useful: - Disable legacy rapl cdev when rapl-mmio is in use This will prevent PL1/PL2 power limit from MSR based rapl, which may not be the correct one. - Delete all trips from zones before psvt install Initially zones has all the trips from sysfs, which may have wrong settings. Instead of deleting only for matched psvt zones, delete or all zones. In this way only zones which are in PSVT will be present. - Check for alternate names for B0D4 device B0D4 can be named as TCPU or B0D4. So search for both names if failed to find one. - Fix error for condition names The current code caps the max name as the last condition name, which is "Power_Slider". So any condition more than 56 will be printing error, with "Power_Slider" as condition name. For example for condition = 57: Unsupported condition 57 (Power_slider) - Set a very high RAPL MSR PL1 with --adaptive After upgrading Dell Latitude 5420, again noticed performance degradation. The PPCC power limit for MSR RAPL PL1 is reduced to 15W. Even though we disable MSR RAPL with --adaptive option, it is not getting disabled. So MSR RAPL limits still playing role. To fix that set a very high MSR RAPL PL1 limit so that it never causes throttling. All throttling with --adaptive option is done using RAPL-MMIO. - Special case for default PSVT When there are no adaptive tables and only one default PSVT table is present with just one entry with MAX type. Add one additional entry as done for non default case. - Increase power limit for disabled RAPL-MMIO Increase 100W to 200W as some desktop platform already have limit more than 100W. - Use Adaptive PPCC limits for RAPL MMIO Set the correct device name as RAPL-MSR so that RAPL-MMIO can also set the correct default power limits. So first step is to see if thermald 1.9.1-1ubuntu0.5 helps. ** Changed in: thermald (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Incomplete Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu
[Kernel-packages] [Bug 400297] Re: patch for JMicron jmc250 and jmc260 ethernet card
*** This bug is a duplicate of bug 1497005 *** https://bugs.launchpad.net/bugs/1497005 I'm installing Linux Mint 20.2 Cinnamon on a Shuttle XS35V2. I've got a Jmicron JMC250 network card 197b:0250 (rev 03). It doesn't work, until I change speed from 1 Gbit/s to 100 Mbits/s : sudo ethtool -s xx speed 100 duplex full So, this bug seems to be still here in last version of Debian, Ubuntu and Mint :( -- 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/400297 Title: patch for JMicron jmc250 and jmc260 ethernet card Status in linux package in Ubuntu: Expired Bug description: It seems that Ubuntu 9.04 haven't has a patch for JMicron jmc250/jmc260 ethernet card like stated on http://cooldavid.org/download/jme.netdev-2.6.20080823.patch. I have a problem to connect to the net with my atom netbook which is using this ethernet chipset. The Network Manager keep on trying to connect to the net and switching from "conected" and "disconected" again and again for eth0. The same situation also hapened while using static IP assignment. Comparing with F11 that use 2.6.29 kernel version I found no problem with the same hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/400297/+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 1937897] Re: GPIO error logs in start and dmesg after update of kernel
Well OK there is a module with that name, however I did blacklist it and same error still occurs. It happens very early in the boot process. Now maybe it tries to load gpio-aaeon, but still early to load modules I would say, it's still doing say GRUB kernel parameters like fsck ones. Now I have confirmed it does slow down boot pretty badly, however the HWE stack just got kernel 5.11 and although it has the same error it does seem to *almost* boot as fast as without any error. Now I tried to actually load that module, so the reverse. It simply says that no such device exists. Conclusion/TLDR: So it shouldn't try to load it in the first place. -- 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/1937897 Title: GPIO error logs in start and dmesg after update of kernel Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.11.0-22 to 5.11.0-25 i see next logs error to gpio: 5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with zero lines [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 On pc: description: Desktop Computer product: System Product Name (SKU) vendor: ASUS version: System Version serial: System Serial Number width: 64 bits capabilities: smbios-3.3.0 dmi-3.3.0 smp vsyscall32 configuration: boot=normal chassis=desktop family=To be filled by O.E.M. sku=SKU uuid=0ABCA172-BFA8-2AC5-FC37-3C7C3FD88FE4 *-core description: Motherboard product: TUF GAMING B550M-PLUS (WI-FI) vendor: ASUSTeK COMPUTER INC. physical id: 0 version: Rev X.0x serial: 201176738701636 slot: Default string *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 0 version: 2403 date: 06/16/2021 size: 64KiB capacity: 16MiB capabilities: pci apm upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi *-memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+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 1497005] Re: 197b:0250 JMicron JMC250 Gigabit ethernet doesn't work
I'm installing Linux Mint 20.2 Cinnamon on a Shuttle XS35V2. I've got a Jmicron JMC250 network card 197b:0250 (rev 03). It doesn't work, until I change speed from 1 Gbit/s to 100 Mbits/s : sudo ethtool -s xx speed 100 duplex full So, this bug seems to be still here in last version of Debian, Ubuntu and Mint :( -- 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/1497005 Title: 197b:0250 JMicron JMC250 Gigabit ethernet doesn't work Status in linux package in Ubuntu: Triaged Bug description: Laptop ASUS X52JU can't connect to the router ASUS RT-AC68U via ethernet. NetworkManager shows that cable is unplugged. Router has Gigabit ethernet ports and laptop doesn't see them. I found that it's a bug of the JMC kernel module. WORKAROUND: The following allows 100 Mbps speed: sudo ethtool -s eth0 speed 100 duplex full --- ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nick 1682 F pulseaudio /dev/snd/controlC0: nick 1682 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=b3669551-f67b-41f1-a310-6b79e24b871c InstallationDate: Installed on 2015-06-16 (93 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK Computer Inc. K52JU Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic root=UUID=c8aa6fb0-2c0a-430d-b6e5-7bb4ebb8346e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15 RelatedPackageVersions: linux-restricted-modules-3.16.0-49-generic N/A linux-backports-modules-3.16.0-49-generic N/A linux-firmware 1.127.15 Tags: trusty Uname: Linux 3.16.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K52JU.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K52JU dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK52JU.206:bd01/25/2011:svnASUSTeKComputerInc.:pnK52JU:pvr1.0:rvnASUSTeKComputerInc.:rnK52JU:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K52JU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497005/+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 926929] Re: Shuttle XS35 network interface not detected by installer
*** This bug is a duplicate of bug 1497005 *** https://bugs.launchpad.net/bugs/1497005 ** This bug is no longer a duplicate of bug 880316 Link not detected / cable seems unplugged with jme - JMicron JMC250 Gigabit Ethernet Controller ** This bug has been marked a duplicate of bug 1497005 197b:0250 JMicron JMC250 Gigabit ethernet doesn't work -- 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/926929 Title: Shuttle XS35 network interface not detected by installer Status in linux package in Ubuntu: Expired Bug description: Tried to boot Shuttle XS35 with 11.10 32bit installer over PXE, however it fails to detect the network interface so the installation cannot continue. Tried to manually load kernel module for jme driver, but it was not found. Any help would be much appreciated. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/926929/+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 880316] Re: Link not detected / cable seems unplugged with jme - JMicron JMC250 Gigabit Ethernet Controller
*** This bug is a duplicate of bug 1497005 *** https://bugs.launchpad.net/bugs/1497005 ** This bug has been marked a duplicate of bug 1497005 197b:0250 JMicron JMC250 Gigabit ethernet doesn't work -- 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/880316 Title: Link not detected / cable seems unplugged with jme - JMicron JMC250 Gigabit Ethernet Controller Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to install Ubuntu on a Shuttle XS35GTV2. The installer can't set up the network connection. I've tried Ubuntu 10.04 32 and 64 bit netinstall, minimal and server, Ubuntu 11.10 32 bit netinstall. The Debian Squeeze 64 bit netinstall installer has no problem. (I've now installed openELEC which has no problems too) I was able to install Ubuntu 10.04 64 bit server but only without network connection. I then could load the jme module: # modprobe jme # depmod -a without errors. But I can't get eth0 running. The output of lspci is: 02:00.5 Ethernet controller: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller (rev 03) 03:00.0 Network controller: Realtek Semiconductor C., Ltd Device 8176 (rev 01) # lshw -C network *-network DISABLED description: Ethernet interface product: JMC250 PCI Express Gigabit Ethernet Controller vendor: JMicron Technology Corp. physical id: 0.5 bus info: pci@:02:00.5 logical name: eth0 version: 03 serial: 80:ee:73:1f:ef:df size: 10MB/s capacity: 1GB/s width: 32 bits clock: 33MHz capabilities: pm pciexpress msix msi bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=off broadcast=yes driver=jme driverversion=1.0.5 duplex=half latency=0 link=no multicast=yes port=MII speed=10MB/s resources: irq:17 memory:feaf4000-feaf7fff ioport:dc00(size=128) ioport:d800(size=256) *-network UNCLAIMED description: Network controller product: Realtek Semiconductor Co., Ltd. vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: latency=0 resources: ioport:e800(size=256) memory:febfc000-febf I've posted my problem at the Ubuntu users mailing list: http://www.linux-archive.org/ubuntu-user/588603-jme-module-missing-netboot-installation.html Edit: Unfortunately I couldn't reassign it as it has nothing to do with gnome-nettools (see post #1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316/+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 400297] Re: patch for JMicron jmc250 and jmc260 ethernet card
*** This bug is a duplicate of bug 1497005 *** https://bugs.launchpad.net/bugs/1497005 ** This bug has been marked a duplicate of bug 1497005 197b:0250 JMicron JMC250 Gigabit ethernet doesn't work -- 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/400297 Title: patch for JMicron jmc250 and jmc260 ethernet card Status in linux package in Ubuntu: Expired Bug description: It seems that Ubuntu 9.04 haven't has a patch for JMicron jmc250/jmc260 ethernet card like stated on http://cooldavid.org/download/jme.netdev-2.6.20080823.patch. I have a problem to connect to the net with my atom netbook which is using this ethernet chipset. The Network Manager keep on trying to connect to the net and switching from "conected" and "disconected" again and again for eth0. The same situation also hapened while using static IP assignment. Comparing with F11 that use 2.6.29 kernel version I found no problem with the same hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/400297/+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 1929504] Re: Add support for IO functions of AAEON devices
OK, but don't try to load the gpio-aaeon module on PCs that, if simply one tries to load it manually, it simply says that no such device exists... It shows twice in the boot log (dmesg + journalctl -b) but even worse also on the monitors, although GRUB has "quiet" specified (no splash). Worst of all, on my Ryzen 3950X (16C/32T) with 5.5 GB/s PCIe4 NVMes you get used to 1-2 second boot speed. But this actually reduces it significantly compared to that. However it seems to be faster now that the 5.11 kernel is the HWE one. The last 5.8 one introduced this bug for me. https://bugs.launchpad.net/bugs/1937897 -- 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/1929504 Title: Add support for IO functions of AAEON devices Status in linux package in Ubuntu: In Progress Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: In Progress Bug description: [Impact] Require drivers to enable AAEON devices. [Fix] AAEON provides a series of patches to support its GPIO/LED/Watchdog/HWMON devices. https://www.spinics.net/lists/linux-gpio/msg61301.html [Test] Verified on AAEON platform. [Where problems could occur] No, they are new drivers, should not introduce any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929504/+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
