[Kernel-packages] [Bug 1787857] Re: USB mouse cursor lags after random time of correct behaviour
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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: Confirmed 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 1787857] Re: USB mouse cursor lags after random time of correct behaviour
Subscribing kernel team. Also, posting the difference between the kernel configurations for reference so that you can see exactly why I believe it's a hardware issue. This issue you're reporting has been reported very few times, which is why I believe there is hardware commonality and might be related to the video driver. For instance, I have issues with stuttering on my AMD video unless I add the following kernel options: radeon.cik_support=0 radeon.si_support=0 amdgpu.dc=1 amdgpu.cik_support=1 amdgpu.si_support=1 amdgpu.dpm=0 amdgpu.gpu_recovery=1 Here's the configuration file differences, which you'll find are VERY minimal: --- /home/erich/Desktop/config-5.0.0-20-generic +++ /home/erich/Desktop/config-5.0.0-20-lowlatency @@ -1,6 +1,6 @@ # # Automatically generated file; DO NOT EDIT. -# Linux/x86 5.0.0-20-generic Kernel Configuration +# Linux/x86 5.0.0-20-lowlatency Kernel Configuration # # @@ -35,7 +35,7 @@ # CONFIG_KERNEL_LZO is not set # CONFIG_KERNEL_LZ4 is not set CONFIG_DEFAULT_HOSTNAME="(none)" -CONFIG_VERSION_SIGNATURE="Ubuntu 5.0.0-20.21-generic 5.0.8" +CONFIG_VERSION_SIGNATURE="Ubuntu 5.0.0-20.21-lowlatency 5.0.8" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y @@ -63,7 +63,7 @@ CONFIG_GENERIC_IRQ_MATRIX_ALLOCATOR=y CONFIG_GENERIC_IRQ_RESERVATION_MODE=y CONFIG_IRQ_FORCED_THREADING=y -# CONFIG_IRQ_FORCED_THREADING_DEFAULT is not set +CONFIG_IRQ_FORCED_THREADING_DEFAULT=y CONFIG_SPARSE_IRQ=y # CONFIG_GENERIC_IRQ_DEBUGFS is not set CONFIG_CLOCKSOURCE_WATCHDOG=y @@ -87,8 +87,9 @@ CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y # CONFIG_PREEMPT_NONE is not set -CONFIG_PREEMPT_VOLUNTARY=y -# CONFIG_PREEMPT is not set +# CONFIG_PREEMPT_VOLUNTARY is not set +CONFIG_PREEMPT=y +CONFIG_PREEMPT_COUNT=y # # CPU/Task time and stats accounting @@ -109,7 +110,7 @@ # # RCU Subsystem # -CONFIG_TREE_RCU=y +CONFIG_PREEMPT_RCU=y # CONFIG_RCU_EXPERT is not set CONFIG_SRCU=y CONFIG_TREE_SRCU=y @@ -421,10 +422,10 @@ CONFIG_EFI_MIXED=y CONFIG_SECCOMP=y # CONFIG_HZ_100 is not set -CONFIG_HZ_250=y +# CONFIG_HZ_250 is not set # CONFIG_HZ_300 is not set -# CONFIG_HZ_1000 is not set -CONFIG_HZ=250 +CONFIG_HZ_1000=y +CONFIG_HZ=1000 CONFIG_SCHED_HRTICK=y CONFIG_KEXEC=y CONFIG_KEXEC_FILE=y @@ -864,11 +865,7 @@ CONFIG_PREEMPT_NOTIFIERS=y CONFIG_PADATA=y CONFIG_ASN1=y -CONFIG_INLINE_SPIN_UNLOCK_IRQ=y -CONFIG_INLINE_READ_UNLOCK=y -CONFIG_INLINE_READ_UNLOCK_IRQ=y -CONFIG_INLINE_WRITE_UNLOCK=y -CONFIG_INLINE_WRITE_UNLOCK_IRQ=y +CONFIG_UNINLINE_SPIN_UNLOCK=y CONFIG_ARCH_SUPPORTS_ATOMIC_RMW=y CONFIG_MUTEX_SPIN_ON_OWNER=y CONFIG_RWSEM_SPIN_ON_OWNER=y @@ -5160,6 +5157,7 @@ CONFIG_REGULATOR_WM8994=m CONFIG_CEC_CORE=y CONFIG_CEC_NOTIFIER=y +CONFIG_CEC_PIN=y CONFIG_RC_CORE=m CONFIG_RC_MAP=m CONFIG_LIRC=y @@ -5205,6 +5203,7 @@ CONFIG_MEDIA_RADIO_SUPPORT=y CONFIG_MEDIA_SDR_SUPPORT=y CONFIG_MEDIA_CEC_SUPPORT=y +# CONFIG_CEC_PIN_ERROR_INJ is not set CONFIG_MEDIA_CONTROLLER=y # CONFIG_MEDIA_CONTROLLER_DVB is not set # CONFIG_MEDIA_CONTROLLER_REQUEST_API is not set @@ -5498,6 +5497,7 @@ CONFIG_DVB_PLATFORM_DRIVERS=y CONFIG_CEC_PLATFORM_DRIVERS=y CONFIG_VIDEO_CROS_EC_CEC=m +CONFIG_CEC_GPIO=m CONFIG_VIDEO_SECO_CEC=m CONFIG_VIDEO_SECO_RC=y CONFIG_SDR_PLATFORM_DRIVERS=y @@ -9709,6 +9709,7 @@ CONFIG_SCHEDSTATS=y CONFIG_SCHED_STACK_END_CHECK=y # CONFIG_DEBUG_TIMEKEEPING is not set +# CONFIG_DEBUG_PREEMPT is not set # # Lock Debugging (spinlocks, mutexes, etc...) @@ -9753,7 +9754,7 @@ # CONFIG_NETDEV_NOTIFIER_ERROR_INJECT is not set CONFIG_FUNCTION_ERROR_INJECTION=y # CONFIG_FAULT_INJECTION is not set -# CONFIG_LATENCYTOP is not set +CONFIG_LATENCYTOP=y CONFIG_USER_STACKTRACE_SUPPORT=y CONFIG_NOP_TRACER=y CONFIG_HAVE_FUNCTION_TRACER=y @@ -9778,6 +9779,7 @@ CONFIG_FUNCTION_GRAPH_TRACER=y # CONFIG_PREEMPTIRQ_EVENTS is not set # CONFIG_IRQSOFF_TRACER is not set +# CONFIG_PREEMPT_TRACER is not set CONFIG_SCHED_TRACER=y CONFIG_HWLAT_TRACER=y CONFIG_FTRACE_SYSCALLS=y -- 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: Confirmed 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-enabl
[Kernel-packages] [Bug 1824546] Re: Intel N3060 booting into black screen with 5.0 kernel
Workaround found at https://wiki.archlinux.org/index.php/Intel_graphics#Xorg_configuration ** Also affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Also affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1824546 Title: Intel N3060 booting into black screen with 5.0 kernel Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: New Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: I updated xubuntu 19.04 to the new 5.0 kernel and it no longer boots, staying on a black screen with stable cursor. I can however select 4.18 kernel from grub and it boots perfectly. I am using Intel Celeron N3060 CPU. Please find attached the dmesg output. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1085 F pulseaudio DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=6dc53e52-37f1-4a3c-aef7-5dedb4684c69 InstallationDate: Installed on 2016-08-27 (957 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160824) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9404 Suyin Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire one 1-431 Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=25f4f2d4-2c0a-4661-bfde-bee6253caff5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-03-16 (27 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/28/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Oxford dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd12/28/2015:svnAcer:pnAspireone1-431:pvrV1.10:rvnAcer:rnOxford:rvrV1.10:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire one 1-431 dmi.product.sku: AO1-431_106D_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824546/+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 1821820] Re: Cannot boot or install - have to use nomodeset
@robstrube It is currently in disco-proposed as well. :) -- 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/1821820 Title: Cannot boot or install - have to use nomodeset Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Committed Bug description: On this 19.04 beta I have to use nomodeset to boot & install Ubuntu Budgie. This is different behaviour from 18.04 and 18.10 where it booted and installed just fine without nomodeset. Without nomodeset, grub/efi disappears, and after a while a solid rather than blinking cursor on a black screen is seen. It does not boot into a live session, nor displays the ubiquity window ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Mar 26 23:40:49 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf] InstallationDate: Installed on 2019-03-26 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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/1821820/+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 1821820] Re: Cannot boot or install - have to use nomodeset
I wouldn't worry about that. If it's in disco-proposed, it'll likely land before the first RC spins even happen. The release team is considering this a serious bug. -- 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/1821820 Title: Cannot boot or install - have to use nomodeset Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Committed Bug description: On this 19.04 beta I have to use nomodeset to boot & install Ubuntu Budgie. This is different behaviour from 18.04 and 18.10 where it booted and installed just fine without nomodeset. Without nomodeset, grub/efi disappears, and after a while a solid rather than blinking cursor on a black screen is seen. It does not boot into a live session, nor displays the ubiquity window ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Mar 26 23:40:49 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf] InstallationDate: Installed on 2019-03-26 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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/1821820/+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 1804804] Re: Screen rotation does not rotate all input devices and needs custom user commands (iio-sensor-proxy or libinput should probably handle this?)
Also experiencing same problem on a Dell Inspiron 3168. Seems as though what should be handled by iio-sensor-proxy is not being handled for the input part of the touchscreen. ** Also affects: iio-sensor-proxy (Ubuntu) Importance: Undecided Status: New ** Changed in: iio-sensor-proxy (Ubuntu) Status: New => Confirmed ** Also affects: libinput (Ubuntu) Importance: Undecided Status: New ** Changed in: libinput (Ubuntu) Status: New => Confirmed -- 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/1804804 Title: Screen rotation does not rotate all input devices and needs custom user commands (iio-sensor-proxy or libinput should probably handle this?) Status in iio-sensor-proxy package in Ubuntu: Confirmed Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.10 GNOME Shell 3.30.1 Cinnamon 3.8.8 Hardware: ASUS Transformer Mini. Also confirmed problematic for Yoga Series tablet/laptop hybrids. (https://github.com/linuxmint/cinnamon-settings-daemon/issues/188) Screen rotation works fine, but tablet coords including touch screen and pen coords do not rotate with it. Gnome gets touch screen rotation correct, but not pen coords Cinnamon gets touch screen rotation and peen coords wrong User can correct using convoluted xinput commands like: xinput set-prop "ELAN22A6:00 04F3:22A6" --type=float "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1 I spoke with Mint devs who said I should file it against iio-sensor- proxy or libinput, which I assume is a better solution that asking various wm developers to fix it individually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1804804/+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 1826844] Re: nvidia-drivers-* are not on the ISO
Added ubuntustudio-meta to get this into our live session. ** Also affects: ubuntustudio-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1826844 Title: nvidia-drivers-* are not on the ISO Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in ubuntustudio-meta package in Ubuntu: New Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Released Status in ubuntustudio-meta source package in Eoan: New Bug description: On Ubuntu desktop, without a network connection, the user can select to install 3rd party drivers (which states that it'll install graphics driver) but even if he selects this option, nVidia proprietary drivers won't be installed because they are not on the pool of the ISO. also tracked in the desktop trello board as card: https://trello.com/c/rPiwDpPe/130-bug1826844-nvidia-drivers-are-not-on-the-iso Adding both ubuntu-driver-390 and ubuntu-driver-418 to the pool, adds 114MB to the ISO. Here is the list of packages that will be added to the pool: libnvidia-cfg1-390 libnvidia-cfg1-418 libnvidia-common-390 libnvidia-common-418 libnvidia-compute-390 libnvidia-compute-418 libnvidia-decode-390 libnvidia-decode-418 libnvidia-encode-390 libnvidia-encode-418 libnvidia-fbc1-390 libnvidia-fbc1-418 libnvidia-gl-390 libnvidia-gl-418 libnvidia-ifr1-390 libnvidia-ifr1-418 libvdpau1 libxnvctrl0 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-compute-utils-418 nvidia-dkms-390 nvidia-dkms-418 nvidia-driver-390 nvidia-driver-410 nvidia-driver-418 nvidia-kernel-common-390 nvidia-kernel-common-418 nvidia-kernel-source-390 nvidia-kernel-source-418 nvidia-prime nvidia-settings nvidia-utils-390 nvidia-utils-418 vdpau-driver-all xserver-xorg-video-nvidia-390 xserver-xorg-video-nvidia-418 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-390 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:22:44 2019 InstallationDate: Installed on 2014-07-15 (1749 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to eoan on 2018-03-24 (400 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1826844/+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 1826844] Re: nvidia-drivers-* are not on the ISO
** Changed in: ubuntustudio-meta (Ubuntu Eoan) Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer) ** Changed in: ubuntustudio-meta (Ubuntu Eoan) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1826844 Title: nvidia-drivers-* are not on the ISO Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in ubuntustudio-meta package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Released Status in ubuntustudio-meta source package in Eoan: In Progress Bug description: On Ubuntu desktop, without a network connection, the user can select to install 3rd party drivers (which states that it'll install graphics driver) but even if he selects this option, nVidia proprietary drivers won't be installed because they are not on the pool of the ISO. also tracked in the desktop trello board as card: https://trello.com/c/rPiwDpPe/130-bug1826844-nvidia-drivers-are-not-on-the-iso Adding both ubuntu-driver-390 and ubuntu-driver-418 to the pool, adds 114MB to the ISO. Here is the list of packages that will be added to the pool: libnvidia-cfg1-390 libnvidia-cfg1-418 libnvidia-common-390 libnvidia-common-418 libnvidia-compute-390 libnvidia-compute-418 libnvidia-decode-390 libnvidia-decode-418 libnvidia-encode-390 libnvidia-encode-418 libnvidia-fbc1-390 libnvidia-fbc1-418 libnvidia-gl-390 libnvidia-gl-418 libnvidia-ifr1-390 libnvidia-ifr1-418 libvdpau1 libxnvctrl0 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-compute-utils-418 nvidia-dkms-390 nvidia-dkms-418 nvidia-driver-390 nvidia-driver-410 nvidia-driver-418 nvidia-kernel-common-390 nvidia-kernel-common-418 nvidia-kernel-source-390 nvidia-kernel-source-418 nvidia-prime nvidia-settings nvidia-utils-390 nvidia-utils-418 vdpau-driver-all xserver-xorg-video-nvidia-390 xserver-xorg-video-nvidia-418 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-390 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:22:44 2019 InstallationDate: Installed on 2014-07-15 (1749 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to eoan on 2018-03-24 (400 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1826844/+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 1826844] Re: nvidia-drivers-* are not on the ISO
** Changed in: ubuntustudio-meta (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1826844 Title: nvidia-drivers-* are not on the ISO Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in ubuntustudio-meta package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Released Status in ubuntustudio-meta source package in Eoan: Fix Committed Bug description: On Ubuntu desktop, without a network connection, the user can select to install 3rd party drivers (which states that it'll install graphics driver) but even if he selects this option, nVidia proprietary drivers won't be installed because they are not on the pool of the ISO. also tracked in the desktop trello board as card: https://trello.com/c/rPiwDpPe/130-bug1826844-nvidia-drivers-are-not-on-the-iso Adding both ubuntu-driver-390 and ubuntu-driver-418 to the pool, adds 114MB to the ISO. Here is the list of packages that will be added to the pool: libnvidia-cfg1-390 libnvidia-cfg1-418 libnvidia-common-390 libnvidia-common-418 libnvidia-compute-390 libnvidia-compute-418 libnvidia-decode-390 libnvidia-decode-418 libnvidia-encode-390 libnvidia-encode-418 libnvidia-fbc1-390 libnvidia-fbc1-418 libnvidia-gl-390 libnvidia-gl-418 libnvidia-ifr1-390 libnvidia-ifr1-418 libvdpau1 libxnvctrl0 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-compute-utils-418 nvidia-dkms-390 nvidia-dkms-418 nvidia-driver-390 nvidia-driver-410 nvidia-driver-418 nvidia-kernel-common-390 nvidia-kernel-common-418 nvidia-kernel-source-390 nvidia-kernel-source-418 nvidia-prime nvidia-settings nvidia-utils-390 nvidia-utils-418 vdpau-driver-all xserver-xorg-video-nvidia-390 xserver-xorg-video-nvidia-418 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-390 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:22:44 2019 InstallationDate: Installed on 2014-07-15 (1749 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to eoan on 2018-03-24 (400 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1826844/+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 1826844] Re: nvidia-drivers-* are not on the ISO
** Changed in: ubuntustudio-meta (Ubuntu Eoan) Assignee: Erich Eickmeyer (eeickmeyer) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1826844 Title: nvidia-drivers-* are not on the ISO Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in ubuntustudio-meta package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Released Status in ubuntustudio-meta source package in Eoan: Fix Committed Bug description: On Ubuntu desktop, without a network connection, the user can select to install 3rd party drivers (which states that it'll install graphics driver) but even if he selects this option, nVidia proprietary drivers won't be installed because they are not on the pool of the ISO. also tracked in the desktop trello board as card: https://trello.com/c/rPiwDpPe/130-bug1826844-nvidia-drivers-are-not-on-the-iso Adding both ubuntu-driver-390 and ubuntu-driver-418 to the pool, adds 114MB to the ISO. Here is the list of packages that will be added to the pool: libnvidia-cfg1-390 libnvidia-cfg1-418 libnvidia-common-390 libnvidia-common-418 libnvidia-compute-390 libnvidia-compute-418 libnvidia-decode-390 libnvidia-decode-418 libnvidia-encode-390 libnvidia-encode-418 libnvidia-fbc1-390 libnvidia-fbc1-418 libnvidia-gl-390 libnvidia-gl-418 libnvidia-ifr1-390 libnvidia-ifr1-418 libvdpau1 libxnvctrl0 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-compute-utils-418 nvidia-dkms-390 nvidia-dkms-418 nvidia-driver-390 nvidia-driver-410 nvidia-driver-418 nvidia-kernel-common-390 nvidia-kernel-common-418 nvidia-kernel-source-390 nvidia-kernel-source-418 nvidia-prime nvidia-settings nvidia-utils-390 nvidia-utils-418 vdpau-driver-all xserver-xorg-video-nvidia-390 xserver-xorg-video-nvidia-418 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-390 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:22:44 2019 InstallationDate: Installed on 2014-07-15 (1749 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to eoan on 2018-03-24 (400 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1826844/+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 1826844] Re: nvidia-drivers-* are not on the ISO
** Changed in: ubuntustudio-meta (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1826844 Title: nvidia-drivers-* are not on the ISO Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Released Status in ubuntustudio-meta source package in Eoan: Fix Released Bug description: On Ubuntu desktop, without a network connection, the user can select to install 3rd party drivers (which states that it'll install graphics driver) but even if he selects this option, nVidia proprietary drivers won't be installed because they are not on the pool of the ISO. also tracked in the desktop trello board as card: https://trello.com/c/rPiwDpPe/130-bug1826844-nvidia-drivers-are-not-on-the-iso Adding both ubuntu-driver-390 and ubuntu-driver-418 to the pool, adds 114MB to the ISO. Here is the list of packages that will be added to the pool: libnvidia-cfg1-390 libnvidia-cfg1-418 libnvidia-common-390 libnvidia-common-418 libnvidia-compute-390 libnvidia-compute-418 libnvidia-decode-390 libnvidia-decode-418 libnvidia-encode-390 libnvidia-encode-418 libnvidia-fbc1-390 libnvidia-fbc1-418 libnvidia-gl-390 libnvidia-gl-418 libnvidia-ifr1-390 libnvidia-ifr1-418 libvdpau1 libxnvctrl0 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-compute-utils-418 nvidia-dkms-390 nvidia-dkms-418 nvidia-driver-390 nvidia-driver-410 nvidia-driver-418 nvidia-kernel-common-390 nvidia-kernel-common-418 nvidia-kernel-source-390 nvidia-kernel-source-418 nvidia-prime nvidia-settings nvidia-utils-390 nvidia-utils-418 vdpau-driver-all xserver-xorg-video-nvidia-390 xserver-xorg-video-nvidia-418 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-390 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:22:44 2019 InstallationDate: Installed on 2014-07-15 (1749 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to eoan on 2018-03-24 (400 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1826844/+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 1870395] Re: Ubuntu Studio 20.04 ZFS Option Fails to Boot
Respin already in progress. New spin has the fix. ** Project changed: ubuntustudio => syslinux (Ubuntu) ** Changed in: syslinux (Ubuntu) Status: New => Fix Released ** Package changed: syslinux (Ubuntu) => zfs-linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1870395 Title: Ubuntu Studio 20.04 ZFS Option Fails to Boot Status in zfs-linux package in Ubuntu: Fix Released Bug description: As part of installation, I selected the experimental ZFS option. Ubuntu Studio then installed without errors, however upon booting the new system there was a zpool import failure and I was prompted at the initrd to manually import the zfs datasets. The workaround at initrd was to enter the following commands: zpool import -R /root -N rpool zpool import -R /root -N bpool zfs mount -a exit The system then booted up normally, however the workaround above has to be used for each subsequent boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1870395/+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 1880325] Re: Intel Wireless Centrino N100 error in Txrate and Bitrate
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1880325 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: linux-meta (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1880325 Title: Intel Wireless Centrino N100 error in Txrate and Bitrate Status in linux-meta package in Ubuntu: Incomplete Bug description: In the last week install a Xubuntu 18.04 distro in the netbook of my brother this install all fine but the Intel Centrino Wireless N100 card doesnt work good because the Bitrate mark 24 and Txrate 14 all time the unique way to connect to the signal of router its put near this. I search in the net in Google to resolve this conflict and fix this explain in the lines below the procedure to obtain this. First this Issue affects this models of Intel Wireless: Wi-Fi 6 products Intel® Wi-Fi 6 AX200 (5.1) Intel® Wi-Fi 6 AX201 (5.2) 802.11ac products Intel® Wireless-AC 9462 (4.14) Intel® Wireless-AC 9461 (4.14) Intel® Wireless-AC 9260 (4.14) Intel® Wireless-AC 9560 (4.14) Intel® Wireless-AC 8265 (4.6) Intel® Wireless-AC 3168 (4.6) Intel® Wireless-AC 8260 (4.1) Intel® Wireless-AC 3165 (4.1) 802.11n or 802.11ac products (SKU dependent) Intel® Wireless 7265 (3.13) Intel® Wireless 7260 (3.10) Intel® Wireless 3160 (3.10) 802.11abgn products Intel® Centrino® Advanced-N 6235 (3.2) Intel® Centrino® Advanced-N 6230 (2.6.36) Intel® Centrino® Advanced-N 6205 (2.6.35) Intel® Centrino® Advance-N + WiMAX 6150 (2.6.30) Intel® Centrino® Advanced-N + WiMAX 6250 (2.6.30) Intel® Centrino® Ultimate-N 6300 (2.6.30) Intel® Centrino® Advanced-N 6200 (2.6.30) Intel® WiMAX/Wi-Fi Link 5350 (2.6.27) Intel® Ultimate N Wi-Fi Link 5300 (2.6.27) Intel® WiMAX/Wi-Fi Link 5150 (2.6.29) Intel® Wi-Fi Link 5100 Series (2.6.27) 802.11bgn products Intel® Centrino® Wireless-N 2230 (3.2) Intel® Centrino® Wireless-N 2200 (3.2) Intel® Centrino® Wireless-N 105 (3.2) Intel® Centrino® Wireless-N 135 (3.2) Intel® Centrino® Wireless-N 100 (2.6.37) Intel® Centrino® Wireless-N 130 (2.6.37) Intel® Centrino® Wireless-N 1030 (2.6.36) Intel® Centrino® Wireless-N 1000 (2.6.30) Second need to go to this page and download the firmware of the model affected: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi Third decompress the tar in the download folder and us this command in the terminal: cp iwlwifi-*.ucode /lib/firmware Later reboot the machine and enter again Four open a terminal windows and enter the following command: sudo nano /etc/NetworkManager/NetworkManager.conf put this line into the file [device] wifi.scan-rand-mac-address=no save and reboot the Network Manager or reboot the machine Five open a terminal windows and enter the following command: sudo nano /etc/network/interfaces you see hte file equal this: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp Substitute eth0 for the driver of your wireless card use in the terminal ifconfig to see Restart Network Manager services or reboot the machine Six edit DNS config file open the terminal and put the following command: sudo nano/etc/resolv.conf Add this lines to the file exactly: # Google IPv4 nameservers nameserver 8.8.8.8 nameserver 8.8.4.4 1 2 3 4 5 # Google IPv6 nameservers nameserver 2001:4860:4860:: nameserver 2001:4860:4860::8844 save and close and restart the machine Ready the Bug its fixed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1880325/+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 1856440] [NEW] cpufreq: no or unknown cpufreq driver
Public bug reported: Not sure where this goes, but no cpufreq driver is available in 19.10 or 20.04 on AMD CPUs. I'm not sure why this is happening, but no cpufreq driver gets loaded. Output of cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 2: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 3: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. Output of cpupower frequency-info analyzing CPU 0: no or unknown cpufreq driver is active on this CPU CPUs which run at the same hardware frequency: Not Available CPUs which need to have their frequency coordinated by software: Not Available maximum transition latency: Cannot determine or is not supported. Not Available available cpufreq governors: Not Available Unable to determine current policy current CPU frequency: Unable to call hardware current CPU frequency: Unable to call to kernel boost state support: Supported: yes Active: yes Boost States: 3 Total States: 8 Pstate-Pb0: 3300MHz (boost state) Pstate-Pb1: 3100MHz (boost state) Pstate-Pb2: 2800MHz (boost state) Pstate-P0: 2600MHz Pstate-P1: 2200MHz Pstate-P2: 1800MHz Pstate-P3: 1400MHz Pstate-P4: 1200MHz Issue is present in 19.10. Upgraded to 20.04 to see if issue persists and it does. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.3.0-24-lowlatency 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10 Uname: Linux 5.3.0-24-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: erich 3958 F pulseaudio /dev/snd/controlC3: erich 3958 F pulseaudio /dev/snd/controlC1: erich 3958 F pulseaudio /dev/snd/controlC0: erich 3958 F pulseaudio CurrentDesktop: GNOME Date: Sat Dec 14 20:59:10 2019 InstallationDate: Installed on 2019-02-12 (306 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) MachineType: Dell Inc. Inspiron 5576 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-lowlatency root=UUID=cbf0a967-a34d-43b1-a42e-993daa70b8f7 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-lowlatency N/A linux-backports-modules-5.3.0-24-lowlatency N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2019-12-15 (0 days ago) dmi.bios.date: 01/29/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0HJ6MY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd01/29/2018:svnDellInc.:pnInspiron5576:pvr1.0.7:rvnDellInc.:rn0HJ6MY:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5576 dmi.product.sku: 07E2 dmi.product.version: 1.0.7 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan focal ** Summary changed: - No cpufreq driver available + cpufreq: no or unknown cpufreq driver -- 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/1856440 Title: cpufreq: no or unknown cpufreq driver Status in linux package in Ubuntu: New Bug description: Not sure where this goes, but no cpufreq driver is available in 19.10 or 20.04 on AMD CPUs. I'm not sure why this is happening, but no cpufreq driver gets loaded. Output of cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 2: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 3: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. Output of cpupower frequency-info analyzing CPU 0: no or unknown cpufreq driver is active on this CPU CPUs which run at the same hardware frequency: Not Available CPUs which need to have their frequency co
[Kernel-packages] [Bug 1856440] Re: cpufreq: no or unknown cpufreq driver
It did definitely work in 19.04, but cannot find a CPU governor on 19.10 or Focal. -- 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/1856440 Title: cpufreq: no or unknown cpufreq driver Status in linux package in Ubuntu: Confirmed Bug description: Not sure where this goes, but no cpufreq driver is available in 19.10 or 20.04 on AMD CPUs. I'm not sure why this is happening, but no cpufreq driver gets loaded. Output of cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 2: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 3: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. Output of cpupower frequency-info analyzing CPU 0: no or unknown cpufreq driver is active on this CPU CPUs which run at the same hardware frequency: Not Available CPUs which need to have their frequency coordinated by software: Not Available maximum transition latency: Cannot determine or is not supported. Not Available available cpufreq governors: Not Available Unable to determine current policy current CPU frequency: Unable to call hardware current CPU frequency: Unable to call to kernel boost state support: Supported: yes Active: yes Boost States: 3 Total States: 8 Pstate-Pb0: 3300MHz (boost state) Pstate-Pb1: 3100MHz (boost state) Pstate-Pb2: 2800MHz (boost state) Pstate-P0: 2600MHz Pstate-P1: 2200MHz Pstate-P2: 1800MHz Pstate-P3: 1400MHz Pstate-P4: 1200MHz Issue is present in 19.10. Upgraded to 20.04 to see if issue persists and it does. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.3.0-24-lowlatency 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10 Uname: Linux 5.3.0-24-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: erich 3958 F pulseaudio /dev/snd/controlC3: erich 3958 F pulseaudio /dev/snd/controlC1: erich 3958 F pulseaudio /dev/snd/controlC0: erich 3958 F pulseaudio CurrentDesktop: GNOME Date: Sat Dec 14 20:59:10 2019 InstallationDate: Installed on 2019-02-12 (306 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) MachineType: Dell Inc. Inspiron 5576 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-lowlatency root=UUID=cbf0a967-a34d-43b1-a42e-993daa70b8f7 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-lowlatency N/A linux-backports-modules-5.3.0-24-lowlatency N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2019-12-15 (0 days ago) dmi.bios.date: 01/29/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0HJ6MY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd01/29/2018:svnDellInc.:pnInspiron5576:pvr1.0.7:rvnDellInc.:rn0HJ6MY:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5576 dmi.product.sku: 07E2 dmi.product.version: 1.0.7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856440/+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 1856440] Re: cpufreq: no or unknown cpufreq driver
I did a kernel bisection back to 5.0 (in disco) and the problem still persisted. It could be a firmware problem with my machine, but I'm uncertain. -- 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/1856440 Title: cpufreq: no or unknown cpufreq driver Status in linux package in Ubuntu: Confirmed Bug description: Not sure where this goes, but no cpufreq driver is available in 19.10 or 20.04 on AMD CPUs. I'm not sure why this is happening, but no cpufreq driver gets loaded. Output of cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 2: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 3: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. Output of cpupower frequency-info analyzing CPU 0: no or unknown cpufreq driver is active on this CPU CPUs which run at the same hardware frequency: Not Available CPUs which need to have their frequency coordinated by software: Not Available maximum transition latency: Cannot determine or is not supported. Not Available available cpufreq governors: Not Available Unable to determine current policy current CPU frequency: Unable to call hardware current CPU frequency: Unable to call to kernel boost state support: Supported: yes Active: yes Boost States: 3 Total States: 8 Pstate-Pb0: 3300MHz (boost state) Pstate-Pb1: 3100MHz (boost state) Pstate-Pb2: 2800MHz (boost state) Pstate-P0: 2600MHz Pstate-P1: 2200MHz Pstate-P2: 1800MHz Pstate-P3: 1400MHz Pstate-P4: 1200MHz Issue is present in 19.10. Upgraded to 20.04 to see if issue persists and it does. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.3.0-24-lowlatency 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10 Uname: Linux 5.3.0-24-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: erich 3958 F pulseaudio /dev/snd/controlC3: erich 3958 F pulseaudio /dev/snd/controlC1: erich 3958 F pulseaudio /dev/snd/controlC0: erich 3958 F pulseaudio CurrentDesktop: GNOME Date: Sat Dec 14 20:59:10 2019 InstallationDate: Installed on 2019-02-12 (306 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) MachineType: Dell Inc. Inspiron 5576 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-lowlatency root=UUID=cbf0a967-a34d-43b1-a42e-993daa70b8f7 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-lowlatency N/A linux-backports-modules-5.3.0-24-lowlatency N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2019-12-15 (0 days ago) dmi.bios.date: 01/29/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0HJ6MY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd01/29/2018:svnDellInc.:pnInspiron5576:pvr1.0.7:rvnDellInc.:rn0HJ6MY:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5576 dmi.product.sku: 07E2 dmi.product.version: 1.0.7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856440/+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 1856440] Re: cpufreq: no or unknown cpufreq driver
Found out the problem. It was indeed a firmware update with my BIOS which disabled a power-on-demand item in the ACPI. Closing this. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/1856440 Title: cpufreq: no or unknown cpufreq driver Status in linux package in Ubuntu: Invalid Bug description: Not sure where this goes, but no cpufreq driver is available in 19.10 or 20.04 on AMD CPUs. I'm not sure why this is happening, but no cpufreq driver gets loaded. Output of cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 2: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 3: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. Output of cpupower frequency-info analyzing CPU 0: no or unknown cpufreq driver is active on this CPU CPUs which run at the same hardware frequency: Not Available CPUs which need to have their frequency coordinated by software: Not Available maximum transition latency: Cannot determine or is not supported. Not Available available cpufreq governors: Not Available Unable to determine current policy current CPU frequency: Unable to call hardware current CPU frequency: Unable to call to kernel boost state support: Supported: yes Active: yes Boost States: 3 Total States: 8 Pstate-Pb0: 3300MHz (boost state) Pstate-Pb1: 3100MHz (boost state) Pstate-Pb2: 2800MHz (boost state) Pstate-P0: 2600MHz Pstate-P1: 2200MHz Pstate-P2: 1800MHz Pstate-P3: 1400MHz Pstate-P4: 1200MHz Issue is present in 19.10. Upgraded to 20.04 to see if issue persists and it does. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.3.0-24-lowlatency 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10 Uname: Linux 5.3.0-24-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: erich 3958 F pulseaudio /dev/snd/controlC3: erich 3958 F pulseaudio /dev/snd/controlC1: erich 3958 F pulseaudio /dev/snd/controlC0: erich 3958 F pulseaudio CurrentDesktop: GNOME Date: Sat Dec 14 20:59:10 2019 InstallationDate: Installed on 2019-02-12 (306 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) MachineType: Dell Inc. Inspiron 5576 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-lowlatency root=UUID=cbf0a967-a34d-43b1-a42e-993daa70b8f7 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-lowlatency N/A linux-backports-modules-5.3.0-24-lowlatency N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2019-12-15 (0 days ago) dmi.bios.date: 01/29/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0HJ6MY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd01/29/2018:svnDellInc.:pnInspiron5576:pvr1.0.7:rvnDellInc.:rn0HJ6MY:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5576 dmi.product.sku: 07E2 dmi.product.version: 1.0.7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856440/+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
** Changed in: ubuntustudio Status: Incomplete => Confirmed ** No longer affects: ubuntustudio -- 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: Confirmed Status in rtirq package in Ubuntu: Confirmed 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 1826844] Re: nvidia-drivers-* are not on the ISO
** No longer affects: ubuntustudio-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1826844 Title: nvidia-drivers-* are not on the ISO Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Released Status in ubuntustudio-meta source package in Eoan: Fix Committed Bug description: On Ubuntu desktop, without a network connection, the user can select to install 3rd party drivers (which states that it'll install graphics driver) but even if he selects this option, nVidia proprietary drivers won't be installed because they are not on the pool of the ISO. also tracked in the desktop trello board as card: https://trello.com/c/rPiwDpPe/130-bug1826844-nvidia-drivers-are-not-on-the-iso Adding both ubuntu-driver-390 and ubuntu-driver-418 to the pool, adds 114MB to the ISO. Here is the list of packages that will be added to the pool: libnvidia-cfg1-390 libnvidia-cfg1-418 libnvidia-common-390 libnvidia-common-418 libnvidia-compute-390 libnvidia-compute-418 libnvidia-decode-390 libnvidia-decode-418 libnvidia-encode-390 libnvidia-encode-418 libnvidia-fbc1-390 libnvidia-fbc1-418 libnvidia-gl-390 libnvidia-gl-418 libnvidia-ifr1-390 libnvidia-ifr1-418 libvdpau1 libxnvctrl0 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-compute-utils-418 nvidia-dkms-390 nvidia-dkms-418 nvidia-driver-390 nvidia-driver-410 nvidia-driver-418 nvidia-kernel-common-390 nvidia-kernel-common-418 nvidia-kernel-source-390 nvidia-kernel-source-418 nvidia-prime nvidia-settings nvidia-utils-390 nvidia-utils-418 vdpau-driver-all xserver-xorg-video-nvidia-390 xserver-xorg-video-nvidia-418 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-390 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:22:44 2019 InstallationDate: Installed on 2014-07-15 (1749 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to eoan on 2018-03-24 (400 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1826844/+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
Lassi, thanks for the comment. If that's the case, I'm going to go ahead and mark this bug as "Invalid" for rtirq and "Fix Released" for linux, but I'd love to see more comments first to confirm this. -- 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: Incomplete 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 1787857] Re: USB mouse cursor lags after random time of correct behaviour
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: rtirq (Ubuntu) Status: Confirmed => Invalid -- 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: Incomplete 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 1787857] Re: USB mouse cursor lags after random time of correct behaviour
In that case I'm keeping this as incomplete, especially since OP (ronso0) has failed to verify with suggestions given by kaihengfeng. I feel like there is some hardware commonality here, and would like to see some hardware specifics as previously requested to better triage this bug. -- 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: Incomplete 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 1787857] Re: USB mouse cursor lags after random time of correct behaviour
Still need to know hardware specifics. I, for one, have AMD Graphics which exhibits this behavior without some AMD-specific kernel parameters in the command line in grub. Either way, subscribing the kernel package to this as well. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: rtirq (Ubuntu) Importance: Undecided Status: New -- 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 Ubuntu Studio: Incomplete Status in linux package in Ubuntu: Confirmed Status in rtirq package in Ubuntu: Confirmed 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/ubuntustudio/+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 1787857] Re: USB mouse cursor lags after random time of correct behaviour
Also subscribing rtirq since this may be related. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: rtirq (Ubuntu) Status: New => Confirmed -- 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 Ubuntu Studio: Incomplete Status in linux package in Ubuntu: Confirmed Status in rtirq package in Ubuntu: Confirmed 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/ubuntustudio/+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 1906913] Re: IRQ conflict between Ethernet and USB with linux 5.4.0-56-lowlatency kernel
As this issue is not specific to Ubuntu Studio, and since this has *not* been verified by anybody but the bug reporter, I removed Ubuntu Studio Developers from this bug and changed it to "New". The lowlatency kernel has many, many more use cases than audio, hence it is no longer developed or managed by the Ubuntu Studio team. This is an Ubuntu kernel issue completely, and in no way should the Ubuntu Studio Development team be involved here as that is too much workload on an already strained and low-numbered team. ** Changed in: linux (Ubuntu) Status: Confirmed => New -- 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/1906913 Title: IRQ conflict between Ethernet and USB with linux 5.4.0-56-lowlatency kernel Status in linux package in Ubuntu: Confirmed Bug description: Package: linux-image-5.4.0.56.lowlatency / Focal Ubuntu Studio 20.04 WLan is working PCI Ethernet not. [ 11.223573] genirq: Flags mismatch irq 18. 00010080 (enp3s1) vs. 2080 (uhci_hcd:usb4) [ 11.299519] genirq: Flags mismatch irq 16. 00010080 (ens32) vs. 2080 (uhci_hcd:usb5) Maybe this report can helpfull for bug 1906655. sounds similar for other kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: oliver 2033 F pulseaudio /dev/snd/controlC0: oliver 2033 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (247 days ago) InstallationMedia: Ubuntu-Studio 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ECS G31T-M7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-lowlatency root=UUID=d918f4d9-9814-4dbd-a547-02a0ddc59f12 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-56.62-lowlatency 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-56-lowlatency N/A linux-backports-modules-5.4.0-56-lowlatency N/A linux-firmware 1.187.4 RfKill: StagingDrivers: r8712u Tags: focal staging Uname: Linux 5.4.0-56-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip lp lpadmin plugdev sambashare saned scanner sudo video _MarkForUpload: True dmi.bios.date: 03/01/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080014 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G31T-M7 dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080014:bd03/01/2010:svnECS:pnG31T-M7:pvr1.0:rvnECS:rnG31T-M7:rvr1.0:cvnECS:ct3:cvr1.0: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: G31T-M7 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: ECS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906913/+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 1906913] Re: IRQ conflict between Ethernet and USB with linux 5.4.0-56-lowlatency kernel
> Why is it not possible to report a bug directly to the "Ubuntu Kernel Team"? Because this way (reporting it against the package) DOES report it to the correct team. Ubuntu does stuff automatically so you don't have to. :) -- 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/1906913 Title: IRQ conflict between Ethernet and USB with linux 5.4.0-56-lowlatency kernel Status in linux package in Ubuntu: Fix Released Bug description: Package: linux-image-5.4.0.56.lowlatency / Focal Ubuntu Studio 20.04 WLan is working PCI Ethernet not. [ 11.223573] genirq: Flags mismatch irq 18. 00010080 (enp3s1) vs. 2080 (uhci_hcd:usb4) [ 11.299519] genirq: Flags mismatch irq 16. 00010080 (ens32) vs. 2080 (uhci_hcd:usb5) Maybe this report can helpfull for bug 1906655. sounds similar for other kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: oliver 2033 F pulseaudio /dev/snd/controlC0: oliver 2033 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (247 days ago) InstallationMedia: Ubuntu-Studio 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ECS G31T-M7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-lowlatency root=UUID=d918f4d9-9814-4dbd-a547-02a0ddc59f12 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-56.62-lowlatency 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-56-lowlatency N/A linux-backports-modules-5.4.0-56-lowlatency N/A linux-firmware 1.187.4 RfKill: StagingDrivers: r8712u Tags: focal staging Uname: Linux 5.4.0-56-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip lp lpadmin plugdev sambashare saned scanner sudo video _MarkForUpload: True dmi.bios.date: 03/01/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080014 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G31T-M7 dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080014:bd03/01/2010:svnECS:pnG31T-M7:pvr1.0:rvnECS:rnG31T-M7:rvr1.0:cvnECS:ct3:cvr1.0: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: G31T-M7 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: ECS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906913/+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 1895833] Re: unblock restrictions on alsa (max id of card and sample rate for alsa Loopback)
Bugs in Ubuntu are never filed against the distribution as a whole, but rather, individual components/packages. Removed affecting Ubuntu. ** No longer affects: ubuntu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1895833 Title: unblock restrictions on alsa (max id of card and sample rate for alsa Loopback) Status in ALSA Libraries: New Status in Alsa utilities: New Status in alsa-lib package in Ubuntu: New Status in alsa-utils package in Ubuntu: New Bug description: SRU Justification: [Impact] kernel, alsa-lib, alsa-utils We are using more and more cards recognized as sound peripherals. When the number of loopback and hardware cards exceeds 32, we can no longer use them. Also some new devices are already using 384khz but the limitation is for alsa Loopback. I thinks we must increse CONFIG_SND_MAX_CARDS to 256 and change 192000 sample rate value fixed in aloop.c to 384000 or 768000 to provide an additional margin in alsa Loopback. [Test Case] sudo add-apt-repository -y universe apt-get update && sudo apt-get upgrade -y sudo apt-get install alsa alsa-* shutdown -r now sudo modprobe snd-aloop sudo echo snd-aloop >> /etc/modules sudo adduser $(whoami) audio shutdown -r now sudo apt-get install -y apt-get install alsa alsa-utils libasound2-dev sudo apt-get install -y screen build-essential initramfs-tools fakeroot debconf-utils dpkg-dev debhelper bin86 flex bison pkgconf dkms python3-docutils \ libudev-dev mt-st cpufrequtils libpci-dev libssl-dev libiberty-dev libcap-dev asciidoc default-jdk libncurses-dev \ kernel-package kernel-wedge libnvpair1linux libuutil1linux libzfs2linux libzpool2linux zfs-dkms zfs-zed zfsutils-linux \ crash makedumpfile libncurses5 libncurses5-dev libelf-dev binutils-dev kexec-tools screen mkdir ~/megamod cd ~/megamod git clone git://kernel.ubuntu.com/ubuntu/ubuntu-focal.git cd ubuntu-focal sed -i 's/SNDRV_PCM_RATE_CONTINUOUS | SNDRV_PCM_RATE_8000_192000,/SNDRV_PCM_RATE_CONTINUOUS,/g' ./sound/drivers/aloop.c sed -i 's/192000/768000/g' ./sound/drivers/aloop.c grep -rnl './' -e "CONFIG_SND_MAX_CARDS=32" | xargs -i@ sed -i 's/CONFIG_SND_MAX_CARDS=32/CONFIG_SND_MAX_CARDS=256/g' @ search and replace 32 by 256 in and ./debian.master/config/annotations for CONFIG_SND_MAX_CARDS fakeroot debian/rules clean fakeroot debian/rules binary dpkg -i ../linux*5.4.0-*.deb shutdown -r now sudo systemctl disable hv-kvp-daemon.service echo "options snd-aloop \" >> /etc/modprobe.d/alsa-base.conf echo "index=10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45 \" >> /etc/modprobe.d/alsa-base.conf echo "id=lp0,lp1,lp2,lp3,lp4,lp5,lp6,lp7,lp8,lp9,lp10,lp11,lp12,lp13,lp14,lp15,lp16,lp17,lp18,lp19,lp20,lp21,lp22,lp23,lp24,lp25,lp26,lp27,lp28,lp29,lp30,lp31,lp32,lp33,lp34,lp35 \" >> /etc/modprobe.d/alsa-base.conf echo "enable=1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1 \" >> /etc/modprobe.d/alsa-base.conf echo "pcm_substreams=2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2" >> /etc/modprobe.d/alsa-base.conf sudo su sudo mkdir /usr/src/alsa cd /usr/src/alsa git clone git://git.alsa-project.org/alsa-lib.git alsa-lib cd /usr/src/alsa/alsa-lib ./gitcompile --with-max-cards=256 make install cp /usr/lib/libasound* /usr/lib/x86_64-linux-gnu/ cd /usr/src/alsa git clone git://git.alsa-project.org/alsa-utils.git alsa-utils cd /usr/src/alsa/alsa-utils ./gitcompile --with-max-cards=256 make install shutdown -r now [Regression Potential] * The regression can be considered as low, because this is because it's functional since 16.04 [Other] * This requires a patch to be included into the kernel, alsa-lib and alsa-utils package. - please see [Test Case] description for more details. * changes can be made independently and have no impact on others [Patch] In /sound/drivers/aloop.c: L555 .rates =SNDRV_PCM_RATE_CONTINUOUS | SNDRV_PCM_RATE_8000_192000, to L555 .rates =SNDRV_PCM_RATE_CONTINUOUS, In /sound/drivers/aloop.c: L557 .rate_max = 192000, to L557 .rate_max = 768000, In /sound/drivers/aloop.c: L557 uinfo->value.integer.max = 192000; to L557 uinfo->value.integer.max = 768000; In /debian.master/config/config.common.ubuntu L9069 CONFIG_SND_MAX_CARDS=32 to L9069 CONFIG_SND_MAX_CARDS=256 and update debian.master/rules.d/hooks.mk For alsa-lib and alsa-util, package can be simply update with ./gitcompile --with-max-cards=256 Thanks everybody To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-lib/+bug/1895833/+subscriptions -- Mailing list: https://launch
[Kernel-packages] [Bug 1251065] [NEW] HP Mini 1000 fails to resume from suspend
Public bug reported: Booting various kernels including the mainline 3.12 kernel, HP Mini 1000 does not resume from suspend. Problem seems to have begun following update to 13.10, including kernels 3.9, 3.10, 3.11. Ran steps on DebuggingKernelSuspend wiki page at https://wiki.ubuntu.com/DebugginKernelSuspend#A.22resume- trace.22_debugging_procedure_for_finding_buggy_drivers. Attached: dmesg.txt ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: trusty ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/bugs/1251065/+attachment/3908447/+files/dmesg.txt -- 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/1251065 Title: HP Mini 1000 fails to resume from suspend Status in “linux” package in Ubuntu: Incomplete Bug description: Booting various kernels including the mainline 3.12 kernel, HP Mini 1000 does not resume from suspend. Problem seems to have begun following update to 13.10, including kernels 3.9, 3.10, 3.11. Ran steps on DebuggingKernelSuspend wiki page at https://wiki.ubuntu.com/DebugginKernelSuspend#A.22resume- trace.22_debugging_procedure_for_finding_buggy_drivers. Attached: dmesg.txt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251065/+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 1251065] Re: HP Mini 1000 fails to resume from suspend
apport information ** Tags added: apport-collected saucy ** Description changed: Booting various kernels including the mainline 3.12 kernel, HP Mini 1000 does not resume from suspend. Problem seems to have begun following update to 13.10, including kernels 3.9, 3.10, 3.11. Ran steps on DebuggingKernelSuspend wiki page at https://wiki.ubuntu.com/DebugginKernelSuspend#A.22resume- trace.22_debugging_procedure_for_finding_buggy_drivers. Attached: dmesg.txt + --- + ApportVersion: 2.12.5-0ubuntu2.1 + Architecture: i386 + DistroRelease: Ubuntu 13.10 + EcryptfsInUse: Yes + InstallationDate: Installed on 2013-11-12 (1 days ago) + InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) + MarkForUpload: True + NonfreeKernelModules: wl + Package: linux (not installed) + Tags: saucy + Uname: Linux 3.12.0-031200-generic i686 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1251065/+attachment/3908469/+files/ProcEnviron.txt -- 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/1251065 Title: HP Mini 1000 fails to resume from suspend Status in “linux” package in Ubuntu: Incomplete Bug description: Booting various kernels including the mainline 3.12 kernel, HP Mini 1000 does not resume from suspend. Problem seems to have begun following update to 13.10, including kernels 3.9, 3.10, 3.11. Ran steps on DebuggingKernelSuspend wiki page at https://wiki.ubuntu.com/DebugginKernelSuspend#A.22resume- trace.22_debugging_procedure_for_finding_buggy_drivers. Attached: dmesg.txt --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-12 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) MarkForUpload: True NonfreeKernelModules: wl Package: linux (not installed) Tags: saucy Uname: Linux 3.12.0-031200-generic i686 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251065/+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 2000491] Re: Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non-recoverable after screen lock and screen completely fades to black or after system goes into slee
** Package changed: linux-signed-hwe-5.4 (Ubuntu) => linux-hwe-5.4 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2000491 Title: Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non- recoverable after screen lock and screen completely fades to black or after system goes into sleep Status in linux-hwe-5.4 package in Ubuntu: New Bug description: This is a fresh install of Ubuntu 18.04.6 on Dell Latitude 7390. The system is non-recoverable after it goes into sleep. Or after the screen is locked by the user and after it fades to complete black. System becomes unresponsive, no mouse or keypress will get the system back on to work. If the systemctl suspend is issued, the system will not wake up again. Hard reset is needed. If Ubuntu 18.04.6 is booted from live USB, the same is happening. Sometimes, when the system is rendered unresponsive as a result of any of the above, the power led is sending the message of "processor failure" (2 x amber blinks followed by 1 x white blink). Any help is greatly appreciated! I will keep the system as is, without applying any updates for now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-84-generic 5.4.0-84.94~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-84.94~18.04.1-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.26 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 27 01:13:12 2022 InstallationDate: Installed on 2022-12-26 (0 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/2000491/+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 2000491] Re: Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non-recoverable after screen lock and screen completely fades to black or after system goes into slee
> Sometimes, when the system is rendered unresponsive as a result of any of the above, the power led is sending the message of "processor failure" (2 x amber blinks followed by 1 x white blink). Based on this, your CPU is failing. Unfortunately, this is not something software (Ubuntu) related, but hardware related. Your Dell Latitude 7390 laptop hardware is failing and the computer motherboard likely needs replacement. Sometimes this happens from age or use, or simply manufacturer defects that don't show up for years. Sadly, I will have to close this bug as "Invalid" since it's not an Ubuntu bug, but rather a hardware failure. Additionally, this bug report is no place for such a discussion (as with any bug tracker), so unless there's further irrefutable evidence that points to this being an actual bug with Ubuntu and not a hardware failure as evidenced, please comment, otherwise keep this bug report closed. Coming to this conclusion is always hard because, from the Ubuntu side, it means there's nothing more we can do to help you. We do, however, thank you for your bug report and helping to make Ubuntu better. ** Changed in: linux-hwe-5.4 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2000491 Title: Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non- recoverable after screen lock and screen completely fades to black or after system goes into sleep Status in linux-hwe-5.4 package in Ubuntu: Invalid Bug description: This is a fresh install of Ubuntu 18.04.6 on Dell Latitude 7390. The system is non-recoverable after it goes into sleep. Or after the screen is locked by the user and after it fades to complete black. System becomes unresponsive, no mouse or keypress will get the system back on to work. If the systemctl suspend is issued, the system will not wake up again. Hard reset is needed. If Ubuntu 18.04.6 is booted from live USB, the same is happening. Sometimes, when the system is rendered unresponsive as a result of any of the above, the power led is sending the message of "processor failure" (2 x amber blinks followed by 1 x white blink). Any help is greatly appreciated! I will keep the system as is, without applying any updates for now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-84-generic 5.4.0-84.94~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-84.94~18.04.1-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.26 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 27 01:13:12 2022 InstallationDate: Installed on 2022-12-26 (0 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/2000491/+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 2016185] Re: Kernel panic at initial boot of April 13 daily 23.04 image on VirtualBox VM
-- 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/2016185 Title: Kernel panic at initial boot of April 13 daily 23.04 image on VirtualBox VM Status in linux package in Ubuntu: Confirmed Bug description: On an LG Gram running VirtualBox 7.0.6 r155176 (Windows 11 host), attempting to Try/Install the April 13 daily Lunar Lobster x64 CD image results in a kernel panic. Captured serial output: [0.00] Linux version 6.2.0-20-generic (buildd@lcy02-amd64-035) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU Binutils for Ubuntu) 2.40) #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 (Ubuntu 6.2.0-20.20-generic 6.2.6) [0.00] Command line: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash console=ttyS0 console=tty0 ignore_loglevel [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: x87 FPU will use FXSAVE [0.00] signal: max sigframe size: 1440 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009fbff] usable [0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved [0.00] BIOS-e820: [mem 0x000f-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xbffe] usable [0.00] BIOS-e820: [mem 0xbfff-0xbfff] ACPI data [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xfffc-0x] reserved [0.00] printk: debug: ignoring loglevel setting. [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.5 present. [0.00] DMI: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [0.00] Hypervisor detected: KVM [0.00] kvm-clock: Using msrs 4b564d01 and 4b564d00 [0.03] kvm-clock: using sched offset of 52229949271 cycles [0.06] clocksource: kvm-clock: mask: 0x max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns [0.09] tsc: Detected 2803.212 MHz processor [0.00] e820: update [mem 0x-0x0fff] usable ==> reserved [0.002226] e820: remove [mem 0x000a-0x000f] usable [0.002232] last_pfn = 0xbfff0 max_arch_pfn = 0x4 [0.002281] MTRRs disabled by BIOS [0.002284] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [0.002359] found SMP MP-table at [mem 0x0009fff0-0x0009] [0.002537] RAMDISK: [mem 0x26253000-0x2f120fff] [0.002546] ACPI: Early table checksum verification disabled [0.002551] ACPI: RSDP 0x000E 24 (v02 VBOX ) [0.002556] ACPI: XSDT 0xBFFF0030 3C (v01 VBOX VBOXXSDT 0001 ASL 0061) [0.002562] ACPI: FACP 0xBFFF00F0 F4 (v04 VBOX VBOXFACP 0001 ASL 0061) [0.002568] ACPI: DSDT 0xBFFF0610 002353 (v02 VBOX VBOXBIOS 0002 INTL 20100528) [0.002572] ACPI: FACS 0xBFFF0200 40 [0.002575] ACPI: FACS 0xBFFF0200 40 [0.002578] ACPI: APIC 0xBFFF0240 54 (v02 VBOX VBOXAPIC 0001 ASL 0061) [0.002582] ACPI: SSDT 0xBFFF02A0 00036C (v01 VBOX VBOXCPUT 0002 INTL 20100528) [0.002584] ACPI: Reserving FACP table memory at [mem 0xbfff00f0-0xbfff01e3] [0.002586] ACPI: Reserving DSDT table memory at [mem 0xbfff0610-0xbfff2962] [0.002587] ACPI: Reserving FACS table memory at [mem 0xbfff0200-0xbfff023f] [0.002587] ACPI: Reserving FACS table memory at [mem 0xbfff0200-0xbfff023f] [0.002588] ACPI: Reserving APIC table memory at [mem 0xbfff0240-0xbfff0293] [0.002589] ACPI: Reserving SSDT table memory at [mem 0xbfff02a0-0xbfff060b] [0.003872] No NUMA configuration found [0.003873] Faking a node at [mem 0x-0xbffe] [0.003880] NODE_DATA(0) allocated [mem 0xbffc5000-0xbffe] [0.004032] Zone ranges: [0.004033] DMA [mem 0x1000-0x00ff] [0.004035] DMA32[mem 0x0100-0xbffe] [0.004036] Normal empty [0.004037] Device empty [0.004038] Movable zone start for each node [0.004039] Early memory node ranges [0.004039] node 0: [mem 0x1000-0x0009efff] [0.004041] node 0: [mem 0x0010-0xbffe] [0.004042] Initmem setup node 0 [mem 0x1000-0xbffe
[Kernel-packages] [Bug 2016202] Re: bluetooth doesnt work properly, honor magicbook 15 amd
** Package changed: linux-signed-hwe-5.19 (Ubuntu) => linux-hwe-5.19 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2016202 Title: bluetooth doesnt work properly, honor magicbook 15 amd Status in linux-hwe-5.19 package in Ubuntu: New Bug description: bluetooth does not work on honor magicbook 15 amd ryzen ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 14 05:10:56 2023 InstallationDate: Installed on 2023-02-20 (52 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2016202/+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 2016421] Re: Hi, i have a problem (im new linux ubuntu user) i have a problem with swapfile, to be specific (Failed to activate swap /swapfile, dependency failed for Swaps), is
Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. If you would prefer live chat support, you can find an IRC support channel for your flavor of Ubuntu here: https://wiki.ubuntu.com/IRC/ChannelList. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs. ** Changed in: linux-restricted-modules-hwe-5.19 (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.19/+question/706247 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2016421 Title: Hi, i have a problem (im new linux ubuntu user) i have a problem with swapfile, to be specific (Failed to activate swap /swapfile, dependency failed for Swaps), is it connected to the fact that i download the nvidia controller for kafa23060TI? Status in linux-restricted-modules-hwe-5.19 package in Ubuntu: Invalid Bug description: Hi, i have a problem (im new linux ubuntu user) i have a problem with swapfile, to be specific (Failed to activate swap /swapfile, dependency failed for Swaps), is it connected to the fact that i download the nvidia controller for kafa23060TI? ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-nvidia-515-server-5.19.0-38-generic 5.19.0-38.39~22.04.1+1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Apr 16 17:07:31 2023 ErrorMessage: podproces zainstalowany pakiet linux-modules-nvidia-515-server-5.19.0-38-generic skrypt post-installation zwrócił kod błędu 127 InstallationDate: Installed on 2023-04-14 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-restricted-modules-hwe-5.19 Title: package linux-modules-nvidia-515-server-5.19.0-38-generic 5.19.0-38.39~22.04.1+1 failed to install/upgrade: podproces zainstalowany pakiet linux-modules-nvidia-515-server-5.19.0-38-generic skrypt post-installation zwrócił kod błędu 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.19/+bug/2016421/+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 1949258] Re: First installation of Lubuntu damaged PCIe slot assignment permanently
** Changed in: ubuntu Status: New => Invalid ** Package changed: 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/1949258 Title: First installation of Lubuntu damaged PCIe slot assignment permanently Status in linux package in Ubuntu: Invalid Bug description: PCI Express x16 Bus record disappeared in the HWInfo64 bus section after installation of Lubuntu as dual boot Notebook model is HP Pavilion - 17-ab403ng The Hwinfo64 report delivers the following results for my HP Pavilion: in the motherboard section Motherboard Slots: 2xPCI Express x1, 1xPCI Express x8, 1xPCI Express x16 in the bus section PCI Express x8 Bus #1 [J6B2] NVIDIA GeForce GTX 1050 Ti [HP] [General Information] Device Name: NVIDIA GeForce GTX 1050 Ti [HP] Original Device Name: NVIDIA GeForce GTX 1050 Ti (GP107M) Device Class: VGA Compatible Adapter Revision ID: A1 PCI Address (Bus: Device: Function) Number: 1:0:0 PCI Latency Timer:0 Hardware ID: PCI\VEN_10DE&DEV_1C8C&SUBSYS_84ED103C&REV_A1 [PCI Express] Version: 3.0 Maximum Link Width: 16x Current Link Width: 8x Maximum Link Speed: 8.0 GT/s Current Link Speed: 2.5 GT/s Device/Port Type: PCI Express Endpoint Slot Implemented: No Emergency Power Reduction:Not Supported Active State Power Management (ASPM) Support: L0s and L1 Active State Power Management (ASPM) Status: L0s and L1 Entry L0s Exit Latency: 256 - 512 ns L1 Exit Latency: 2 - 4 us Maximum Payload Size Supported: 256 bytes Maximum Payload Size: 256 bytes Resizable BAR Support:Not Supported [System Resources] Interrupt Line: N/A Interrupt Pin:INTA# Memory Base Address 0 6300 Memory Base Address 1 5000 Memory Base Address 3 6000 I/O Base Address 50 [Features] Bus Mastering:Enabled Running At 66 MHz:Not Capable Fast Back-to-Back Transactions: Not Capable [Driver Information] Driver Manufacturer: NVIDIA Driver Description: NVIDIA GeForce GTX 1050 Ti Driver Provider: NVIDIA Driver Version: 27.21.14.6627 (GeForce 466.27) Driver Date: 23-Apr-2021 DCH/UWD Driver: Capable DeviceInstanceId PCI\VEN_10DE&DEV_1C8C&SUBSYS_84ED103C&REV_A1\4&33ECA368&0&0008 Location PathsPCIROOT(0)#PCI(0100)#PCI() The PCI Express bus enumeration ends with #3 and the NVMe PCIe SSD controller is not listed. However, a Hwinfo64 report of a comparable board can be found on the Internet. There, an NVMe PCIe SSD controller is listed in the Bus section (see below) under PCI Express x4. PCI Express x4 Bus #4 Samsung NVMe PCIe SSD Controller [General Information] Device Name: Samsung NVMe PCIe SSD Controller Original Device Name: Samsung Electronics NVMe PCIe SSD Controller Device Class: NVMe Controller Revision ID: 0 PCI Address (Bus: Device: Function) Number: 4:0:0 PCI Latency Timer:0 Hardware ID: PCI\VEN_144D&DEV_A808&SUBSYS_A801144D&REV_00 [PCI Express] Version: 3.0 Maximum Link Width: 4x Current Link Width: 4x Maximum Link Speed: 8.0 GT/s Current Link Speed: 8.0 GT/s Device/Port Type: PCI Express Endpoint Slot Implemented: No Emergency Power Reduction:Not Supported Active State Power Management (ASPM) Support: L1 Active State Power Management (ASPM) Status: L1 Entry L0s Exit Latency: >4 us L1 Exit Latency: 32 - 64 us Maximum Payload Size Supported: 256 bytes Maximum Payload Size: 256 bytes [System Resources] Interrupt Line: N/A Interrupt Pin:INTA# Memory Base Address 0 AD20 [Features] Bus Mastering:Enabled Running At 66 MHz:Not Capable Fast Back-to-Back Transactions: Not Capable [Driver Information] Driver Manufacturer: Standard NVM Express Controller Driver Description: Standard NVM Express Controller Driver Provider: Microsoft Driver Version: 10.0.19041.488 Driver Date: 21-Jun-2006 DeviceInstanceId PCI\VEN_144D&DEV_A808&SUBSYS_A801144D&REV_00\4&CDF9F35&0&00DC Location PathsPCIROOT(0)#PCI(1B04)#PCI() My HP Pavilion, on the other hand, does not have a PCI Express x4 slot, but it does have a PCI Express x8 slot. According to the Hwinfo64 report of my HP Pavilion notebook, the graphics card NVIDIA GeForce GTX 1050 Ti (GP107M) sits in the PCI Express x8 slot. Specified for this graphics card is: x4. Maximum Link Width: 16x In the Hwinfo64 report of the board used for comparison, the graphics card is attached to the PCI Express x16 bus #1 (see below) as listed in the Bus section, i.e. in the correct place (16 lanes). PCI Express x16 Bus #1 NV
[Kernel-packages] [Bug 1949258] Re: First installation of Lubuntu damaged PCIe slot assignment permanently
Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs. -- 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/1949258 Title: First installation of Lubuntu damaged PCIe slot assignment permanently Status in linux package in Ubuntu: Invalid Bug description: PCI Express x16 Bus record disappeared in the HWInfo64 bus section after installation of Lubuntu as dual boot Notebook model is HP Pavilion - 17-ab403ng The Hwinfo64 report delivers the following results for my HP Pavilion: in the motherboard section Motherboard Slots: 2xPCI Express x1, 1xPCI Express x8, 1xPCI Express x16 in the bus section PCI Express x8 Bus #1 [J6B2] NVIDIA GeForce GTX 1050 Ti [HP] [General Information] Device Name: NVIDIA GeForce GTX 1050 Ti [HP] Original Device Name: NVIDIA GeForce GTX 1050 Ti (GP107M) Device Class: VGA Compatible Adapter Revision ID: A1 PCI Address (Bus: Device: Function) Number: 1:0:0 PCI Latency Timer:0 Hardware ID: PCI\VEN_10DE&DEV_1C8C&SUBSYS_84ED103C&REV_A1 [PCI Express] Version: 3.0 Maximum Link Width: 16x Current Link Width: 8x Maximum Link Speed: 8.0 GT/s Current Link Speed: 2.5 GT/s Device/Port Type: PCI Express Endpoint Slot Implemented: No Emergency Power Reduction:Not Supported Active State Power Management (ASPM) Support: L0s and L1 Active State Power Management (ASPM) Status: L0s and L1 Entry L0s Exit Latency: 256 - 512 ns L1 Exit Latency: 2 - 4 us Maximum Payload Size Supported: 256 bytes Maximum Payload Size: 256 bytes Resizable BAR Support:Not Supported [System Resources] Interrupt Line: N/A Interrupt Pin:INTA# Memory Base Address 0 6300 Memory Base Address 1 5000 Memory Base Address 3 6000 I/O Base Address 50 [Features] Bus Mastering:Enabled Running At 66 MHz:Not Capable Fast Back-to-Back Transactions: Not Capable [Driver Information] Driver Manufacturer: NVIDIA Driver Description: NVIDIA GeForce GTX 1050 Ti Driver Provider: NVIDIA Driver Version: 27.21.14.6627 (GeForce 466.27) Driver Date: 23-Apr-2021 DCH/UWD Driver: Capable DeviceInstanceId PCI\VEN_10DE&DEV_1C8C&SUBSYS_84ED103C&REV_A1\4&33ECA368&0&0008 Location PathsPCIROOT(0)#PCI(0100)#PCI() The PCI Express bus enumeration ends with #3 and the NVMe PCIe SSD controller is not listed. However, a Hwinfo64 report of a comparable board can be found on the Internet. There, an NVMe PCIe SSD controller is listed in the Bus section (see below) under PCI Express x4. PCI Express x4 Bus #4 Samsung NVMe PCIe SSD Controller [General Information] Device Name: Samsung NVMe PCIe SSD Controller Original Device Name: Samsung Electronics NVMe PCIe SSD Controller Device Class: NVMe Controller Revision ID: 0 PCI Address (Bus: Device: Function) Number: 4:0:0 PCI Latency Timer:0 Hardware ID: PCI\VEN_144D&DEV_A808&SUBSYS_A801144D&REV_00 [PCI Express] Version: 3.0 Maximum Link Width: 4x Current Link Width: 4x Maximum Link Speed: 8.0 GT/s Current Link Speed: 8.0 GT/s Device/Port Type: PCI Express Endpoint Slot Implemented: No Emergency Power Reduction:Not Supported Active State Power Management (ASPM) Support: L1 Active State Power Management (ASPM) Status: L1 Entry L0s Exit Latency: >4 us L1 Exit Latency: 32 - 64 us Maximum Payload Size Supported: 256 bytes Maximum Payload Size: 256 bytes [System Resources] Interrupt Line: N/A Interrupt Pin:INTA# Memory Base Address 0 AD20 [Features] Bus Mastering:Enabled Running At 66 MHz:Not Capable Fast Back-to-Back Transactions: Not Capable [Driver Information] Driver Manufacturer: Standard NVM Express Controller Driver Description: Standard NVM Express Controller Driver Provider: Microsoft Driver Version: 10.0.19041.488 Driver Date: 21-Jun-2006 DeviceInstanceId PCI\VEN_144D&DEV_A808&SUBSYS_A801144D&REV_00\4&CDF9F35&0&00DC Location PathsPCIROOT(0)#PCI(1B04)#PCI() My HP Pavilion, on
[Kernel-packages] [Bug 2039747] Re: snd_intel_dsp_driver_probe page fault on linux 6.2
** Package changed: linux-signed-hwe-6.2 (Ubuntu) => linux-hwe-6.2 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039747 Title: snd_intel_dsp_driver_probe page fault on linux 6.2 Status in linux-hwe-6.2 package in Ubuntu: New Bug description: Workaround snd_intel_dspcfg.dsp_driver=1 allows sound output, did not investigate further. Saw some upstream work mentioning "DSPless" mode that sounds like this might become relevant on 6.5 again. Recent 6.5 report where DSP detect worked, but sound did not: LP: #2039320 Note that kvm_intel was loaded, also: /sys/class/firmware-attributes/thinklmi/attributes/KernelDMAProtection/current_value:Enable /sys/class/firmware-attributes/thinklmi/attributes/MicrophoneAccess/current_value:Disable /sys/class/firmware-attributes/thinklmi/attributes/IntegratedAudioAccess/current_value:Enable /sys/class/firmware-attributes/thinklmi/attributes/SGXControl/current_value:Disable (in case some tool refuses parsing the dmesg cutout: I left the inserted "rmi4_smbus" message untouched) DMAR: IOMMU enabled SMT: disabled microcode: Microcode Update Driver: v2.2. [..] snd_hda_intel :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 BUG: unable to handle page fault for address: a412796b5325 #PF: supervisor read access in kernel mode #PF: error_code(0x) - not-present page PGD 10067 P4D 10067 PUD 0 Oops: [#1] PREEMPT SMP NOPTI CPU: 1 PID: 698 Comm: systemd-udevd Not tainted 6.2.0-36-generic #37~22.04.1-Ubuntu Hardware name: LENOVO 20S5GE/20S5GE, BIOS N2XET39W (1.29 ) 07/25/2023 RIP: 0010:intel_nhlt_has_endpoint_type+0x2a/0x60 [snd_intel_dspcfg] Code: 0f 1f 44 00 00 55 48 89 e5 48 85 ff 74 35 48 8d 47 25 0f b6 7f 24 85 ff 74 29 31 d2 eb 0c 8b 08 83 c2 01 48 01 c8 39 fa 74 19 <40> 38 70 04 75 ee b8 01 00 00 00 5d> RSP: 0018:a41200b778e0 EFLAGS: 00010297 RAX: a412796b5321 RBX: 889c8187d810 RCX: 796802fc RDX: 0001 RSI: 0002 RDI: 00a7 RBP: a41200b778e0 R08: R09: R10: R11: R12: a41200035000 R13: 02c8 R14: 889c819530d0 R15: c137c4b0 FS: 7f3ddea9d8c0() GS:889fce48() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: a412796b5325 CR3: 000103d1e003 CR4: 003706e0 Call Trace: ? show_regs+0x72/0x90 ? __die+0x25/0x80 ? page_fault_oops+0x79/0x190 ? search_exception_tables+0x67/0x80 ? kernelmode_fixup_or_oops+0xb2/0x140 ? __bad_area_nosemaphore+0x1a5/0x2e0 ? bad_area_nosemaphore+0x16/0x30 ? do_kern_addr_fault+0x7b/0xa0 ? exc_page_fault+0x10f/0x1b0 ? asm_exc_page_fault+0x27/0x30 ? intel_nhlt_has_endpoint_type+0x2a/0x60 [snd_intel_dspcfg] snd_intel_dsp_driver_probe.part.0+0x232/0x2a0 [snd_intel_dspcfg] snd_intel_dsp_driver_probe+0x38/0x70 [snd_intel_dspcfg] azx_probe+0x22d/0x4e0 [snd_hda_intel] local_pci_probe+0x48/0xb0 pci_call_probe+0x55/0x190 pci_device_probe+0x84/0x120 really_probe+0x1ea/0x450 __driver_probe_device+0x8a/0x190 driver_probe_device+0x23/0xd0 __driver_attach+0x10f/0x220 ? __pfx___driver_attach+0x10/0x10 bus_for_each_dev+0x80/0xe0 driver_attach+0x1e/0x30 bus_add_driver+0x152/0x250 driver_register+0x83/0x160 ? __pfx_init_module+0x10/0x10 [snd_hda_intel] __pci_register_driver+0x68/0x80 azx_driver_init+0x23/0xff0 [snd_hda_intel] do_one_initcall+0x46/0x240 ? kmalloc_trace+0x2a/0xb0 do_init_module+0x52/0x240 load_module+0xb96/0xd60 ? kernel_read_file+0x25c/0x2b0 __do_sys_finit_module+0xcc/0x150 ? __do_sys_finit_module+0xcc/0x150 __x64_sys_finit_module+0x18/0x30 do_syscall_64+0x59/0x90 ? exit_to_user_mode_prepare+0x3b/0xd0 ? syscall_exit_to_user_mode+0x38/0x60 ? do_syscall_64+0x69/0x90 ? exit_to_user_mode_prepare+0x3b/0xd0 ? syscall_exit_to_user_mode+0x38/0x60 ? do_syscall_64+0x69/0x90 ? do_syscall_64+0x69/0x90 ? do_syscall_64+0x69/0x90 ? do_syscall_64+0x69/0x90 entry_SYSCALL_64_after_hwframe+0x73/0xdd RIP: 0033:0x7f3dde91ea7d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d> RSP: 002b:7ffe1ebf2a98 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 5654c0d70fe0 RCX: 7f3dde91ea7d RDX: RSI: 7f3ddeb5c441 RDI: 0013 RBP: 0002 R08: R09: 0002 R10: 0013 R11: 0246 R12: 7f3ddeb5c441 R13: 5654c0c26000 R14: 0068 R15: 5654c0d65bb0 Modules linked in: snd_hda_intel(+) input_leds snd_intel_dspcfg rapl
[Kernel-packages] [Bug 2039744] Re: "Wi-Fi and Bluetooth drop or become unstable after updates
** 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/2039744 Title: "Wi-Fi and Bluetooth drop or become unstable after updates Status in linux package in Ubuntu: Incomplete Bug description: A few updates ago, the Wi-Fi and Bluetooth, which were working perfectly after previous fixes for the Realtek RTL8821CE 802.11ac, have become unstable again. Wi-Fi constantly drops, and Bluetooth has poor and choppy audio. I noticed this problem occurring after a few updates because everything was working perfectly (there were problems in the LTS version in the past, but they had been fixed, and in 23+, there were no issues until now). The process is as follows: I boot up the system, Wi-Fi works for a few minutes, then it drops, and no adapters are recognized. I reboot the system. Sometimes it works perfectly, other times the same issue repeats. Bluetooth doesn't drop, but with headphones, the audio keeps cutting out and is of low quality. I've observed this for about a month. Thank you for your attention. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-release-upgrader-core 1:23.04.6 ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1000:116:13148161:2023-10-14 16:11:38.138230265 -0300:2023-10-14 16:11:33.682230383 -0300:/var/crash/_opt_Mullvad VPN_mullvad-gui.1000.crash 640:1000:116:14139946:2023-10-17 20:20:44.478106198 -0300:2023-10-17 20:20:37.026158833 -0300:/var/crash/_usr_share_codium_codium.1000.crash 640:1000:116:6818241:2023-10-16 10:59:47.318844220 -0300:2023-10-16 10:59:35.422911209 -0300:/var/crash/_usr_lib_x86_64-linux-gnu_libexec_baloo_file.1000.crash CurrentDesktop: KDE Date: Wed Oct 18 19:37:32 2023 InstallationDate: Installed on 2023-10-01 (17 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1) PackageArchitecture: all ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039744/+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 2039868] Re: amdgpu reset during usage of firefox
Working with Pirouette on IRC, we determined this may be related to
https://bugzilla.kernel.org/show_bug.cgi?id=201957#c94 in which the
solution, sadly, was to add amdgpu.mcbp=0 to the kernel boot parameters.
Per that bug report, it does appear as though this might be the result
of a regression in the 6.5 kernel as they did not experience this issue
in prior kernels or Ubuntu 23.04.
They also found mentions of
https://gitlab.freedesktop.org/drm/amd/-/issues/2848 where Kernel 6.6
has a fix which we could pull a patch from, and we might have a patch
for mesa at
https://gitlab.freedesktop.org/drm/amd/-/issues/2848#note_2095536.
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
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/2039868
Title:
amdgpu reset during usage of firefox
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
New
Bug description:
Running nightly on 23.10 (since monday), I have been experiencing a
few amdgpu resets in the past hours
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 18:26:43 2023
HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
InstallationDate: Installed on 2022-07-04 (472 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A0CTO1WW
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039868/+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 2039877] Re: System crash dialogue when opening flatpak
This bug report was filed against the Linux kernel but seems to have been intended for the flatpak package touchegg. Please contact the developer of touchegg for support. Contact information for the developer seems to be at https://github.com/JoseExposito/touchegg. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/2039877 Title: System crash dialogue when opening flatpak Status in linux package in Ubuntu: Invalid Bug description: Occurred when trying to open flatpak from https://flathub.org/apps/com.github.joseexposito.touche in-between opening .flatpakref with Discover store and the Discover store fully loading. Have encountered previously with other flatpaks - usually but doesn't always crash and have installed other flatpaks from flathub after trying a few times. Everything up to date in apt. Hope this report helps in some small way! ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-35-generic 6.2.0-35.35 ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rich 3967 F wireplumber /dev/snd/seq:rich 3960 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Oct 19 19:16:57 2023 InstallationDate: Installed on 2023-07-20 (91 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) MachineType: Apple Inc. MacBookPro14,3 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=7a24893e-8dbd-4508-9f0e-725105a2ea4d ro quiet splash vt.handoff=7 initrd=\initrd.img-6.2.0-35-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-35-generic N/A linux-backports-modules-6.2.0-35-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2023 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 515.0.0.0.0 dmi.board.name: Mac-551B86E5744E2388 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro14,3 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-551B86E5744E2388 dmi.modalias: dmi:bvnAppleInc.:bvr515.0.0.0.0:bd06/02/2023:br0.1:svnAppleInc.:pnMacBookPro14,3:pvr1.0:rvnAppleInc.:rnMac-551B86E5744E2388:rvrMacBookPro14,3:cvnAppleInc.:ct9:cvrMac-551B86E5744E2388:sku: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro14,3 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039877/+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 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)
Targeted to jammy since at least one of the duplicates is specifically talking about 22.04. ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-hwe-6.2 (Ubuntu Lunar) ** No longer affects: linux (Ubuntu Jammy) ** Changed in: linux-hwe-6.2 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-hwe-6.2 (Ubuntu) Status: New => Invalid -- 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/2031537 Title: Ethernet not stable 23.04 (RTL8168/8169) Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Invalid Status in linux-hwe-6.2 source package in Jammy: Confirmed Status in linux source package in Lunar: Fix Committed Bug description: [Impact] Ethernet is unstable with Realtek RTL8168h/8111h NIC and kernel 6.2 resulting in frequent transmit queue timeouts. Related to ASPM. See 'original description' below. [Test Case] Just regular usage for an extended period of time. No transmit queue timeouts with RTL8168h/8111h NICs. [Where Problems Could Occur] Modification are isolated to the r8169 driver so only machine where that driver is loaded are affected. Issues could show up as kernel crashes, stack traces, non-fnuctional wired network. [Original Description] hello, it is my first time reporting a pug hope it is the last there is thread here https://ubuntuforums.org/showthread.php?t=2489146&p=14151513 another user experienced similar issue my network work fine at startup keep working for hours then disconnect and cannot reconnect without a restart I tested the cable using another pc and it was working repluged with no difference I thought it is caused by nvidia driver so changed it and the problem persist I use systemd-networkd uname -a Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux lspci: 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b) dmesg: [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): apparmor="ALLOWED" operation="file_perm" class="file" profile="libreoffice-oosplash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [Mon Aug 7 12:39:19 2023] [ cut here ] [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clmulni_intel rc_core [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus xhci_pci_renesas idma64 wmi pinctrl_cannonlake [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 6.2.0-26-generic #26-Ubuntu [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 2.13.1 05/10/2023 [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c
[Kernel-packages] [Bug 2061869] [NEW] Snaps unable to connect to network under linux-lowlatency 6.8.0-25.25.3
Public bug reported: After upgrading to linux-lowlatency 6.8.0-25, suddenly snaps can no longer connect to network. I tried downgrading snapd from edge, still no connectivity. Only solution was to downgrade back to 6.8.0-7. I'll also add apparmor in case this is an apparmor issue as well. Marking as "critical" priority as this affects all installs of Ubuntu Studio and affects Firefox and Thunderbird. ** Affects: apparmor (Ubuntu) Importance: Critical Status: New ** Affects: linux-lowlatency (Ubuntu) Importance: Critical Status: New ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Description changed: After upgrading to linux-lowlatency 6.8.0-25, suddenly snaps can no longer connect to network. I tried downgrading snapd from edge, still no connectivity. Only solution was to downgrade back to 6.8.0-7. I'll also add apparmor in case this is an apparmor issue as well. + + Marking as "critical" priority as this affects all installs of Ubuntu + Studio and affects Firefox and Thunderbird. ** Changed in: apparmor (Ubuntu) Importance: Undecided => Critical ** Changed in: linux-lowlatency (Ubuntu) Importance: Undecided => Critical ** Changed in: apparmor (Ubuntu) Milestone: None => ubuntu-24.04 ** Changed in: linux-lowlatency (Ubuntu) Milestone: None => ubuntu-24.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2061869 Title: Snaps unable to connect to network under linux-lowlatency 6.8.0-25.25.3 Status in apparmor package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: After upgrading to linux-lowlatency 6.8.0-25, suddenly snaps can no longer connect to network. I tried downgrading snapd from edge, still no connectivity. Only solution was to downgrade back to 6.8.0-7. I'll also add apparmor in case this is an apparmor issue as well. Marking as "critical" priority as this affects all installs of Ubuntu Studio and affects Firefox and Thunderbird. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2061869/+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 2052856] Re: Ubuntu Studio 22.04 Kernel 6.5-Invisible Mouse Cursor
Just moving to the correct package since the signed kernel is merely derived. ** Package changed: linux-signed-lowlatency-hwe-6.2 (Ubuntu) => linux- lowlatency-hwe-6.2 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2052856 Title: Ubuntu Studio 22.04 Kernel 6.5-Invisible Mouse Cursor Status in linux-lowlatency-hwe-6.2 package in Ubuntu: New Bug description: Upon a fresh install on a System76 Thelio Mira, the mouse has functionality (can click, drag, select, etc.) but the cursor is not visible. Dropping to 6.2 restores the cursor visibility, but still not sure how to fix on kernel 6.5. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-1009-lowlatency 6.2.0-1009.9~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Feb 10 09:14:11 2024 InstallationDate: Installed on 2024-02-10 (0 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) SourcePackage: linux-signed-lowlatency-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency-hwe-6.2/+bug/2052856/+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 1970065] Re: System not going to be completly powered off
** Package changed: 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/1970065 Title: System not going to be completly powered off Status in linux package in Ubuntu: Incomplete Bug description: When i shutdown (Apr 23 23:15), it seems everything powered of except the keyboard lights. Then, i try to power on again, but, nothing happened because the notebook are still powered on. So, it's never powered off correctly? Now i force power off (Apr 23 23:20). After Start, the logs look like this: Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Stopped Create System Users. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: swapfile.swap: Deactivated successfully. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Deactivated swap /swapfile. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Reached target Unmount All Filesystems. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: systemd-remount-fs.service: Deactivated successfully. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Stopped Remount Root and Kernel File Systems. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Reached target System Shutdown. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Reached target Late Shutdown Services. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: systemd-poweroff.service: Deactivated successfully. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Finished System Power Off. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Reached target System Power Off. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Shutting down. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd-shutdown[1]: Syncing filesystems and block devices. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd-shutdown[1]: Sending SIGTERM to remaining processes... Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd-journald[258]: Journal stopped -- Boot 286bc7f0640748e9996bbc70b090eb57 -- Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: microcode: microcode updated early to revision 0xea, date = 2021-01-25 Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: Linux version 5.15.0-25-generic (buildd@ubuntu) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #25-Ubuntu SMP Wed Mar 30 > Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=945f3621-37dd-40d0-be8d-295ac422c82f ro quiet splash vt.handoff=7 Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: KERNEL supported cpus: Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: Intel GenuineIntel Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: AMD AuthenticAMD Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: Hygon HygonGenuine Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: Centaur CentaurHauls Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: zhaoxin Shanghai Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: signal: max sigframe size: 2032 Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-provided physical RAM map: Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-e820: [mem 0x-0x00057fff] usable Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-e820: [mem 0x00058000-0x00058fff] reserved Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-e820: [mem 0x00059000-0x0009cfff] usable Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-e820: [mem 0x0009d000-0x000f] reserved Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-e820: [mem 0x0010-0xc3eecfff] usable It seems to me nothing bad? OS: Distributor ID: Ubuntu Description: Ubuntu 22.04 LTS Release: 22.04 Codename: jammy My Sy
[Kernel-packages] [Bug 1970125] Re: suspend drains battery
** Package changed: 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/1970125 Title: suspend drains battery Status in linux package in Ubuntu: Incomplete Bug description: My notebook is fully loadet. After finished some surfing with chromium i closed the cover. 8 hours later i open the cover again, notebook is powered off. I can't power on. I plugin power adapter and i see, battery is 0. Ubuntu 5.15.0-25.25-generic 5.15.30 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:1904] (rev 08) Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [17aa:2238] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2238] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR- 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled, AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec+ Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped- Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911] Subsystem: Lenovo Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [17aa:2238] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend- LnkCap: Port #1, Speed 8GT/s, Width x1, ASPM L1, Exit Latency L1 <16us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 5GT/s (downgraded), Width x1 (ok) TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt- SltCap: A
[Kernel-packages] [Bug 1971117] Re: 2nd display crashed
** Package changed: kubuntu-meta (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/1971117 Title: 2nd display crashed Status in linux package in Ubuntu: New Bug description: My display stopped displaying anything. When I try to re-enable. It wouldn't work. My laptop is connected to an HDMI KVM and I had to turn off-and-on the dock to make it work again. And when I did, it didn't restore the output on my 2nd display. I had to re-enable it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: kubuntu-desktop 1.418 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Sun May 1 22:32:36 2022 InstallationDate: Installed on 2022-02-24 (66 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: kubuntu-meta UpgradeStatus: Upgraded to jammy on 2022-04-20 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971117/+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 1971573] Re: After upgrade from 20.04 to 22.04 & reboor hangs
** Package changed: 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/1971573 Title: After upgrade from 20.04 to 22.04 & reboor hangs Status in linux package in Ubuntu: Incomplete Bug description: I had a 20.04 system I "upgraded" to 22.04. > do-release-upgrade -d The upgrade went well except after reboot the system never came back up. Searching the web I found quite a few others having the same/similar problem. Troubleshooting I booted a LiveCD Ubuntu 22.04 and looked at /boot on the just upgraded system and found something really strange! There were the expected vmlinuz and initrd files but there were also 2 entries for some kind of KVM entries ?? Removing the KVM entries and rebooting the system it rebooted successfully into 22.04. I'd never seen "KVM anything" in grub boot menu before so thought I'd report it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971573/+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 1973086] Re: System won't go into suspend normally with kernel above 5.13.0-35
** Package changed: ubuntu => linux-hwe (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1973086 Title: System won't go into suspend normally with kernel above 5.13.0-35 Status in linux-hwe package in Ubuntu: New Bug description: Problem: The system does not suspend normally when using a kernel above version 5.13.0-35, and instead locks up and must be reset. 1) Ubuntu Studio 20.04 Description: Ubuntu 20.04.4 LTS Release: 20.04 2) Kernel 5.13.0-37, 5.13.0-40, 5.13.0-41 all do the same... 3) What I expect to happen: System goes into STR state normally and can be resumed upon pressing the power button. 4) What happens instead: Screen goes blank, hard drives spin down, then spin back up again, screen stays blank, system does not enter STR state (CPU, GPU, PSU fans keeps running etc), and system is now locked up and can't be recovered unless hard reset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1973086/+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 1973203] Re: Kubuntu does not shut down properly
** Package changed: 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/1973203 Title: Kubuntu does not shut down properly Status in linux package in Ubuntu: Incomplete Bug description: Hello I'm having issues with Kubuntu 22.04 on a Thinkpad X1 Carbon 4th generation. After a clean install without encryption, when I turn off the laptop, it does not shut down properly (some lights on my keyboard stay turned on even though the power button goes black), so I have to press the power button during 7 seconds to turn it off and then I can turn it on again. It seems to be a similar error to this one: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1972086 Also, the standby mode does not work: When I go into standby mode, some lights on my keyboard stay on and I can't get my laptop to exit the standby mode, unless I am turning it of by pressing the power button and then restart my system. And one more thing: When I boot into Ubuntu 22.04 or Kubuntu 22.04 using an USB stick, it takes about 5 minutes while other Linux versions (including Ubuntu 20.04 lts) it takes only a few seconds. Also there is none of the above problems in Ubuntu 20.04 lts. If you need any more information, just ask but please also give me a hint on how to get the information as I am not really familiar with linux-systems. Best regards! OS: Kubuntu 22.04 LTS x86_64 Host: 20FB0067MZ ThinkPad X1 Carbon 4th Kernel: 5.15.0-27-generic Uptime: 1 hour, 15 mins Packages: 2376 (dpkg), 7 (snap) Shell: bash 5.1.16 Resolution: 1920x1080 DE: Plasma 5.24.4 WM: KWin Theme: [Plasma], Breeze [GTK2/3] Icons: [Plasma], breeze [GTK2/3] Terminal: konsole CPU: Intel i7-6600U (4) @ 3.400GHz GPU: Intel Skylake GT2 [HD Graphics 520] Memory: 2414MiB / 15859MiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973203/+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 1973237] Re: WiFi adapter, system speakers and brightness regulation stopped working after package upgrade
** Package changed: ubuntu => linux (Ubuntu) ** Package changed: linux (Ubuntu) => unattended-upgrades (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/1973237 Title: WiFi adapter, system speakers and brightness regulation stopped working after package upgrade Status in unattended-upgrades package in Ubuntu: New Bug description: After an unattended upgrade (the packages upgraded listed at the end), at least following things crashed: - WiFi adapter - not seen by the system - system speakers - not seen - cannot regulate the brightness of my laptop screen Used system: Ubuntu 18.04.6 LTS Release: 18.04 version.log and lspci-vnvn.log in attachment --- upgraded and installed packages --- Start-Date: 2022-05-12 20:09:41 Commandline: /usr/bin/unattended-upgrade Upgrade: cron:amd64 (3.0pl1-128.1ubuntu1.1, 3.0pl1-128.1ubuntu1.2) End-Date: 2022-05-12 20:09:49 Start-Date: 2022-05-12 20:09:53 Commandline: /usr/bin/unattended-upgrade Upgrade: dnsmasq-base:amd64 (2.79-1ubuntu0.5, 2.79-1ubuntu0.6) End-Date: 2022-05-12 20:09:55 Start-Date: 2022-05-12 20:09:58 Commandline: /usr/bin/unattended-upgrade Upgrade: firefox:amd64 (99.0+build2-0ubuntu0.18.04.2, 100.0+build2-0ubuntu0.18.04.1) End-Date: 2022-05-12 20:10:11 Start-Date: 2022-05-12 20:10:15 Commandline: /usr/bin/unattended-upgrade Upgrade: firefox-locale-en:amd64 (99.0+build2-0ubuntu0.18.04.2, 100.0+build2-0ubuntu0.18.04.1) End-Date: 2022-05-12 20:10:16 Start-Date: 2022-05-12 20:10:19 Commandline: /usr/bin/unattended-upgrade Upgrade: firefox-locale-pl:amd64 (99.0+build2-0ubuntu0.18.04.2, 100.0+build2-0ubuntu0.18.04.1) End-Date: 2022-05-12 20:10:20 Start-Date: 2022-05-12 20:10:24 Commandline: /usr/bin/unattended-upgrade Upgrade: libcurl3-gnutls:amd64 (7.58.0-2ubuntu3.17, 7.58.0-2ubuntu3.18) End-Date: 2022-05-12 20:10:25 Start-Date: 2022-05-12 20:10:29 Commandline: /usr/bin/unattended-upgrade Upgrade: libnss3:amd64 (2:3.35-2ubuntu2.13, 2:3.35-2ubuntu2.14) End-Date: 2022-05-12 20:10:30 Start-Date: 2022-05-12 20:10:33 Commandline: /usr/bin/unattended-upgrade Upgrade: linux-libc-dev:amd64 (4.15.0-176.185, 4.15.0-177.186) End-Date: 2022-05-12 20:10:34 Start-Date: 2022-05-12 20:10:38 Commandline: /usr/bin/unattended-upgrade Upgrade: linux-signed-generic:amd64 (4.15.0.176.165, 4.15.0.177.166) End-Date: 2022-05-12 20:10:38 Start-Date: 2022-05-12 20:10:42 Commandline: /usr/bin/unattended-upgrade Upgrade: libcurl4:amd64 (7.58.0-2ubuntu3.17, 7.58.0-2ubuntu3.18), curl:amd64 (7.58.0-2ubuntu3.17, 7.58.0-2ubuntu3.18) End-Date: 2022-05-12 20:10:43 Start-Date: 2022-05-12 20:10:47 Commandline: /usr/bin/unattended-upgrade Install: linux-headers-4.15.0-177-generic:amd64 (4.15.0-177.186, automatic), linux-image-4.15.0-177-generic:amd64 (4.15.0-177.186, automatic), linux-headers-4.15.0-177:amd64 (4.15.0-177.186, automatic), linux-modules-4.15.0-177-generic:amd64 (4.15.0-177.186, automatic), linux-modules-extra-4.15.0-177-generic:amd64 (4.15.0-177.186, automatic) Upgrade: linux-headers-generic:amd64 (4.15.0.176.165, 4.15.0.177.166), linux-image-generic:amd64 (4.15.0.176.165, 4.15.0.177.166), linux-generic:amd64 (4.15.0.176.165, 4.15.0.177.166) End-Date: 2022-05-12 20:12:20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1973237/+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 1973216] Re: No force-feedback for Saitek Cyborg Evo Force
** Package changed: linux (Ubuntu) => joystick (Ubuntu) ** Changed in: joystick (Ubuntu) Status: Confirmed => New -- 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/1973216 Title: No force-feedback for Saitek Cyborg Evo Force Status in joystick package in Ubuntu: New Bug description: What I expected to happen: I plug in Saitek Cyborg Evo Force joystick, run ffmvforce or ffcfstress and can adjust the force-feedback. What happenend instead: No force-feedback at all. ffcfstress raises error "ERROR: device (or driver) has no constant force feedback support [ffcfstress.c:194]" although the joystick has constant force feedback support. -- Hi, The joystick is recognized by the OS and can read axis and button information. However, no force-feedback can be apply e.g. via `ffmvforce` (will not complain but does nothing) or `ffcfstress` (complains, that hardware or driver do not support force-feedback). $ ffcfstress -d /dev/input/event8 ERROR: device (or driver) has no constant force feedback support [ffcfstress.c:194] I tried to patch the iforce kernel module myself based on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/792937 and https://launchpadlibrarian.net/73006485/Linux-Force-Feedback-for-Saitek-Cyborg-Evo-Force%20%281%29.patch . My kernel module is working and loaded, however, the patch didn't enable force-feedback (probably I was missing something in the patch, since the linked patch is outdated). Since, I have absolutely no clue what else I could do, to get force-feedback working, I post this here since in an ideal world this should work plug&play. What can I do to enable force-feedback for my joystick using ubuntu? Thanks a lot! --- $ cat /proc/version_signature Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 $ lsb_release -rd Description: Ubuntu 20.04.4 LTS Release: 20.04 -- ubuntu-bug linux: ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 12 17:35:41 2022 Dependencies: adduser 3.118ubuntu2 apt 2.0.6 apt-utils 2.0.6 busybox-initramfs 1:1.30.1-4ubuntu6.4 ca-certificates 20210119~20.04.2 coreutils 8.30-3ubuntu2 cpio 2.13+dfsg-2ubuntu0.3 debconf 1.5.73 debconf-i18n 1.5.73 dmsetup 2:1.02.167-1ubuntu1 dpkg 1.19.7ubuntu3 gcc-10-base 10.3.0-1ubuntu1~20.04 gettext-base 0.19.8.1-10build1 gpgv 2.2.19-3ubuntu2.1 grub-common 2.04-1ubuntu26.15 grub-gfxpayload-lists 0.7 grub-pc 2.04-1ubuntu26.15 grub-pc-bin 2.04-1ubuntu26.15 grub2-common 2.04-1ubuntu26.15 initramfs-tools 0.136ubuntu6.7 initramfs-tools-bin 0.136ubuntu6.7 initramfs-tools-core 0.136ubuntu6.7 klibc-utils 2.0.7-1ubuntu5.1 kmod 27-1ubuntu2 libacl1 2.2.53-6 libapt-pkg6.0 2.0.6 libattr1 1:2.4.48-5 libaudit-common 1:2.8.5-2ubuntu6 libaudit1 1:2.8.5-2ubuntu6 libblkid1 2.34-0.1ubuntu9.3 libbz2-1.0 1.0.8-2 libc6 2.31-0ubuntu9.7 libcap-ng0 0.7.9-2.1build1 libcrypt1 1:4.4.10-10ubuntu4 libdb5.3 5.3.28+dfsg1-0.6ubuntu2 libdevmapper1.02.1 2:1.02.167-1ubuntu1 libefiboot1 37-2ubuntu2.2 libefivar1 37-2ubuntu2.2 libffi7 3.3-4 libfreetype6 2.10.1-2ubuntu0.1 libfuse2 2.9.9-3 libgcc-s1 10.3.0-1ubuntu1~20.04 libgcrypt20 1.8.5-5ubuntu1.1 libgmp10 2:6.2.0+dfsg-4 libgnutls30 3.6.13-2ubuntu1.6 libgpg-error0 1.37-1 libhogweed5 3.5.1+really3.5.1-2ubuntu0.2 libidn2-0 2.2.0-2 libklibc 2.0.7-1ubuntu5.1 libkmod2 27-1ubuntu2 liblocale-gettext-perl 1.07-4 liblz4-1 1.9.2-2ubuntu0.20.04.1 liblzma5 5.2.4-1ubuntu1.1 libmount1 2.34-0.1ubuntu9.3 libnettle7 3.5.1+really3.5.1-2ubuntu0.2 libp11-kit0 0.23.20-1ubuntu0.1 libpam-modules 1.3.1-5ubuntu4.3 libpam-modules-bin 1.3.1-5ubuntu4.3 libpam-runtime 1.3.1-5ubuntu4.3 libpam0g 1.3.1-5ubuntu4.3 libpcre2-8-0 10.34-7 libpng16-16 1.6.37-2 libseccomp2 2.5.1-1ubuntu1~20.04.2 libselinux1 3.0-1build2 libsemanage-common 3.0-1build2 libsemanage1 3.0-1build2 libsepol1 3.0-1ubuntu0.1 libsmartcols1 2.34-0.1ubuntu9.3 libssl1.1 1.1.1f-1ubuntu2.13 libstdc++6 10.3.0-1ubuntu1~20.04 libsystemd0 245.4-4ubuntu3.17 libtasn1-6 4.16.0-2 libtext-charwidth-perl 0.04-10 libtext-iconv-perl 1.7-7 libtext-wrapi18n-perl 0.06-9 libtinfo6 6.2-0ubuntu2 libudev1 245.4-4ubuntu3.17 libunistring2 0.9.10-2 libuuid1 2.34-0.1ubuntu9.3 libzstd1 1.4.4+dfsg-3ubuntu0.1 linux-base 4.5ubuntu3.7 linux-image-5.11.0-43-generic 5.11.0-43.47~20.04.2 linux-modules-5.11.0-43-generic 5.11.0-43.47~20.04.2 login 1:4.8.1-1ubuntu5.20.04.1 logsave 1.45.5-2ubuntu1 lsb-base 11.1.0ubuntu2 lz4 1.9.2-2ubuntu0.20.04.1 openssl 1.1.1f-1ubuntu2.13 os-prober 1.74ubuntu2 passwd 1:4.8.1-1ubuntu5.20.04.1 perl-base 5.30.0-9ubuntu0.2 sensible-
[Kernel-packages] [Bug 1947043] Re: nvidia drivers do not update initramfs properly
@xnox:
Upon investigation, and per our conversation on IRC, I did some
experimenting with the prebuilt modules. Unfortunately, these use
llvmpipe and don't interface well with nvidia-settings.
Using ubuntu-drivers to install the drivers used *the exact same
mechanism* as installing nvidia-drivers-470 directly, but also
configured our systems to use the hybrid graphics mode, which has been
known to cause performance issues on our branded CLEVO chassis computers
especially when connected to external displays.
Your suggestions were good, but in this instance they don't make a whole
lot of sense. I do, however, understand your reluctance to rebuild all
initramfs for each kernel as it might break things. I feel as though we
can probably close this bug as your rationale is sound, and the
mechanism we have works for our customers.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1947043
Title:
nvidia drivers do not update initramfs properly
Status in linux-restricted-modules package in Ubuntu:
New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
New
Status in linux-restricted-modules source package in Bionic:
New
Status in nvidia-graphics-drivers-470 source package in Bionic:
New
Status in linux-restricted-modules source package in Focal:
New
Status in nvidia-graphics-drivers-470 source package in Focal:
New
Status in linux-restricted-modules source package in Hirsute:
New
Status in nvidia-graphics-drivers-470 source package in Hirsute:
New
Status in linux-restricted-modules source package in Impish:
New
Status in nvidia-graphics-drivers-470 source package in Impish:
New
Bug description:
When Nvidia drivers are installing, they are only rebuilding the
initramfs for the currently running kernel and/or the newest kernel
when installed. Unfortunately, that means that if one has two kernel
flavors installed (such as -generic and -lowlatency) this means that
the initramfs is only getting rebuild for the currently installed
kernel flavor and its newest version. When a user then switches to the
other kernel flavor, their video fails because the kernel they
switched to does not have the kernel module in the initramfs despite
the kernel module being compiled and available.
The root cause seems to be in nvidia-kernel-common-*.postinst and
nvidia-dkms-*.postinst:
# Update initramfs so that the blacklist ends up in the initramfs
if [ -x /usr/sbin/update-initramfs ]; then
/usr/sbin/update-initramfs -u
if [ -n "$NEWEST_KERNEL" ] && [ ${CURRENT_KERNEL} !=
${NEWEST_KERNEL} ]; then
# This can fail when dealing with a chroot see LP: #556653
/usr/sbin/update-initramfs -u -k $CURRENT_KERNEL
fi
fi
Instead of looking for the conditions to be met, this should be
rebuilding for *all* installed kernels, despite the longer amount of
time needed to do so in some cases. The rationale is that systems
should work as expected and saving time, in this case, can cause that
not to happen. As such the postinst scripts should do the following in
lieu of the above:
/usr/sbin/update-initramfs -u -k all
This ensures that all installed kernel initramfs images get rebuilt,
which adds increased safety at the expense of speed during the
install. This will also prevent a race condition where, if a kernel
and the nvidia driver are updated at the same time, that the proper
initramfs image will exist despite which order the nvidia driver and
kernel get installed.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: nvidia-driver-470 470.74-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-19.19-lowlatency 5.13.14
Uname: Linux 5.13.0-19-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Oct 13 13:12:23 2021
InstallationDate: Installed on 2021-03-20 (206 days ago)
InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64
(20210320)
SourcePackage: nvidia-graphics-drivers-470
UpgradeStatus: Upgraded to impish on 2021-06-13 (122 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1947043/+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 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
Tested with 1020 kernel in focal-updates, still no-good. Tested with 1021 kernel in focal-proposed, seems to be OK. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: On many CLEVO chassis computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+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 1956393] [NEW] Bluetooth no longer recognized after update to 5.14.0-1013
Public bug reported: On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-oem-5.14 (Ubuntu) Importance: Critical Status: Confirmed ** Tags: amd64 apport-bug focal oem-priority ** Changed in: linux-signed-oem-5.14 (Ubuntu) Status: New => Confirmed ** Changed in: linux-signed-oem-5.14 (Ubuntu) Importance: Undecided => Critical ** Description changed: - On Kubuntu Focus computers with the recent update to the OEM 5.13.0-1013 + On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-signed-oem-5.14 package in Ubuntu: Confirmed Bug description: On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1956393/+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 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: linux-oem-5.14 (Ubuntu) Importance: Critical => Undecided -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+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 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
** Description changed: - On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 - kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure - why this has happened, but this is likely an API change. + On many CLEVO chassis computers with the recent update to the OEM + 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We + are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) - InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) + InstallationMedia: Kubuntu 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: On many CLEVO chassis computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+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 1968230] Re: More problem on Lenovo G50-30
Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/linux/+question/701246 -- 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/1968230 Title: More problem on Lenovo G50-30 Status in linux package in Ubuntu: Invalid Bug description: Random freeze, problems on WiFi, Cinnamon have sporadic issues. My set-up: Intel© Pentium© CPU N3540 @ 2.16GHz × 4 Cinnamon 5.2.7 Graphics Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 8 Gb RAM 256 G SSD disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968230/+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 1818811] Re: The swapfile on the Btrfs file system is not activated
** Also affects: partman-swapfile (Ubuntu) Importance: Undecided Status: New ** Changed in: ubiquity (Ubuntu) Status: Confirmed => Invalid ** Changed in: partman-swapfile (Ubuntu) Status: New => Confirmed -- 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/1818811 Title: The swapfile on the Btrfs file system is not activated Status in linux package in Ubuntu: Invalid Status in partman-swapfile package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Invalid Bug description: From 5.0 kernel is implemented support for the swapfile on Btrfs (https://patchwork.kernel.org/cover/10584515/), today arrived on the repositories of Ubuntu 19.04 proposed kernel 5.0, but the swapfile is not activated. Log: mar 06 11:17:55 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): swapfile must not be copy-on-write mar 06 11:17:55 notebook-Lenovo-V110 swapon[517]: swapon: /swapfile: swapon failed: Argomento non valido mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Activating swap /swapfile... mar 06 11:17:57 notebook-Lenovo-V110 swapon[916]: swapon: /swapfile: swapon failed: Argomento non valido mar 06 11:17:57 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): swapfile must not be copy-on-write mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Swap process exited, code=exited, status=255/EXCEPTION mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Failed with result 'exit-code'. mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Failed to activate swap /swapfile. mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Activating swap /swapfile... mar 06 11:17:57 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): swapfile must not be copy-on-write mar 06 11:17:57 notebook-Lenovo-V110 swapon[1006]: swapon: /swapfile: swapon failed: Argomento non valido mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Swap process exited, code=exited, status=255/EXCEPTION mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Failed with result 'exit-code'. mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Failed to activate swap /swapfile. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-generic 5.0.0.7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: emanu 1744 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 11:19:52 2019 InstallationDate: Installed on 2019-01-30 (34 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 13d3:5745 IMC Networks Bus 001 Device 002: ID 10c4:8105 Cygnal Integrated Products, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80TL ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-7-generic root=UUID=91fdf6c0-1b5d-4bb5-9aa4-aeb946236b8a ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.177 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 1KCN46WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V110-15ISK dmi.modalias: dmi:bvnLENOVO:bvr1KCN46WW:bd10/29/2018:svnLENOVO:pn80TL:pvrLenovoV110-15ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV110-15ISK: dmi.product.family: V110-15ISK dmi.product.name: 80TL dmi.product.sku: LENOVO_MT_80TL_BU_idea_FM_V110-15ISK dmi.product.version: Lenovo V110-15ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818811/+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 1968938] Re: Integrated webcam no longer working after latest system update (April 13, 2022).
** Package changed: ubuntu => linux-hwe-5.13 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1968938 Title: Integrated webcam no longer working after latest system update (April 13, 2022). Status in linux-hwe-5.13 package in Ubuntu: New Bug description: The 'Cheese' application states "no device found". This problem has happened before. It seems like sometimes system updates fix the issue; however, the most recent update seems to have re-broken the webcam. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: webcam (not installed) ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 13 19:39:41 2022 InstallationDate: Installed on 2022-02-16 (56 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xawtv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1968938/+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 1962373] Re: Cannot resume from suspend
** Package changed: linux-signed-hwe-5.13 (Ubuntu) => linux-hwe-5.13 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1962373 Title: Cannot resume from suspend Status in linux-hwe-5.13 package in Ubuntu: New Bug description: New HP Pavilion 15z-eh100 I am able to suspend via the power menu or by closing the laptop lid. However, I am unable to resume from suspend. Opening the lid does not do it. Hitting the power button does not do it. I have hit every key on the keyboard as well as clicked the touchpad. The power button has a slowly pulsing light, indicating it is suspended. Pressing and holding the power button for several seconds, causing the laptop to power off, is the only way I have found to get out of this state. $ cat /proc/acpi/wakeup DeviceS-state Status Sysfs node GPP1S4*disabled GP17S4*enabled pci::00:08.1 GPP0S4*disabled $ uname -a Linux pavilion 5.13.0-30-generic #33~20.04.1-Ubuntu SMP Mon Feb 7 14:25:10 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Ubuntu 20.04.4 LTS Release: 20.04 $ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge 00:02.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 7 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device 8852 03:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01) 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 164c (rev c2) 04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 1637 04:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor 04:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1 04:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1 04:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor (rev 01) 04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller Please let me know if I can provide any other details to help get this solved. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Feb 26 11:49:38 2022 InstallationDate: Installed on 2022-02-16 (10 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1962373/+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 1963568] Re: E
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1963568 Title: E Status in linux-firmware package in Ubuntu: Incomplete Bug description: QEMU/KVM VM ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220302.gitee0667aa-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marty 1634 F pipewire-media- marty 1635 F pulseaudio /dev/snd/seq:marty 1633 F pipewire CasperMD5CheckResult: pass Date: Thu Mar 3 18:39:26 2022 Dependencies: firmware-sof-signed 1.9-1ubuntu1 DuplicateSignature: package:linux-firmware:20220302.gitee0667aa-0ubuntu1 Setting up libreoffice-pdfimport (1:7.3.1~rc2-0ubuntu1) ... dpkg: error processing package linux-firmware (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2022-02-11 (20 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) IwConfig: lono wireless extensions. enp1s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) PackageArchitecture: all ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_70i6e6@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_70i6e6 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal, 3.10.1-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu5 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 20220302.gitee0667aa-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: ArchLinux 1.15.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-6.2 dmi.modalias: dmi:bvnSeaBIOS:bvrArchLinux1.15.0-1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-6.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1963568/+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 1964814] Re: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1
Allan, bsdz: thanks for the workaround(s). However, workarounds don't get to the heart of fixing the problem, which is what bug reports are intended to do. Rest assured, the people that need to fix this are working on it, hence the triage and assignment, and I would expect this to be fixed very soon. For those that would want to use this workaround, that would be done at their own risk, and those workarounds could be undone and unnecessitated by package updates. My best advice, especially if you're running Jammy, is to just wait it out and it will get fixed. These types of problems don't go unnoticed, and certainly don't stick around for long. :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1964814 Title: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: Confirmed Bug description: linux-firmware fails to upgrade with: unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg- new': No such file or directory $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: linux-firmware 1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. Need to get 0 B/238 MB of archives. After this operation, 24.9 MB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 272091 files and directories currently installed.) Preparing to unpack .../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ... Unpacking linux-firmware (20220314.gitcd01f857-0ubuntu1) over (20220302.gitee0667aa-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory No apport report written because the error message indicates an issue on the local system update-initramfs: Generating /boot/initrd.img-5.15.0-23-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. Errors were encountered while processing: /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964814/+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 1983181] Re: Cheese Internal data stream error
** Package changed: linux (Ubuntu) => cheese (Ubuntu) ** Changed in: cheese (Ubuntu) Status: Incomplete => New -- 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/1983181 Title: Cheese Internal data stream error Status in cheese package in Ubuntu: New Bug description: corrado@corrado-n4-kk-0718:~$ cheese (cheese:12091): Gdk-WARNING **: 16:18:17.659: Native Windows taller than 65535 pixels are not supported (cheese:12091): cheese-WARNING **: 16:18:48.168: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: cheese 41.1-2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 30 16:21:11 2022 InstallationDate: Installed on 2022-07-19 (11 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. RelatedPackageVersions: cheese41.1-2 cheese-common 41.1-2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: corrado1757 F wireplumber /dev/snd/controlC0: corrado1757 F wireplumber /dev/snd/seq:corrado1754 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-07-19 (11 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=2f8a8007-7685-4a68-85d3-46088d66849c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220711.gitdfa29317-0ubuntu1 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Tags: wayland-session kinetic Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo whoopsie _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1983181/+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 1915003] Re: SRU: Always update the initramfs when changing power profile
Verified on a Kubuntu Focus M1 running focal: erich@erich-KFocus:~$ apt-cache policy nvidia-settings nvidia-settings: Installed: 460.39-0ubuntu0.20.04.1 Candidate: 460.39-0ubuntu0.20.04.1 Version table: *** 460.39-0ubuntu0.20.04.1 100 100 /var/lib/dpkg/status Works exactly as expected complete with a "Please wait for the operation to complete" progress indicator. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: SRU: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in nvidia-prime source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Committed Bug description: Since we introduced support for dynamic power management, on systems with hybrid graphics (LP: #1904583), the need to load drivers with different options has become more evident. We need to make sure that the files in the initramfs are in sync with the current user selection. This is also a chance to update the old nvidia-settings release in the archive. [Impact] * If the modules list is not in sync with the selected power profile, users may experience a black screen or increased power consumption. * Updating the initramfs can take a few seconds, and we need to provide users with some form of visual feedback. [Fix] * The prime-select tool shoud update the initramfs when switching between power profiles, and provide visual feedback. * The nvidia-settings panel should provide a progress dialog, since profile switching would otherwise freeze the UI until update-initramfs completes. [Test Case] Make sure a supported nvidia driver is installed (450, 460), then install nvidia-prime and nvidia-settings from proposed, and check the following: 1) prime-select query (to check your current profile) 2) sudo prime-select on-demand (or "intel", or "nvidia", depending on your current power profile) 3) Check that the operation completes successfully. 4) Reboot your system 5) Launch the nvidia-setting panel. 6) Select a different profile from the PRIME tab, and check that a progress dialog is correctly displayed. 7) Close the nvidia-settings panel, and reboot. [Regression Risk] Medium, while the changes in prime-select are trivial, nvidia-settings needs careful testing. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+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 1928146] Re: Please SRU nvidia-modprobe 465.24 and nvidia-settings 460.73
** Changed in: nvidia-settings (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: nvidia-settings (Ubuntu Groovy)
Status: New => Fix Committed
** Changed in: nvidia-settings (Ubuntu Hirsute)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1928146
Title:
Please SRU nvidia-modprobe 465.24 and nvidia-settings 460.73
Status in nvidia-modprobe package in Ubuntu:
Fix Released
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in nvidia-modprobe source package in Focal:
Fix Committed
Status in nvidia-settings source package in Focal:
Fix Committed
Status in nvidia-modprobe source package in Groovy:
Fix Committed
Status in nvidia-settings source package in Groovy:
Fix Committed
Status in nvidia-modprobe source package in Hirsute:
Fix Committed
Status in nvidia-settings source package in Hirsute:
Fix Committed
Status in nvidia-modprobe source package in Impish:
Fix Released
Status in nvidia-settings source package in Impish:
Fix Released
Bug description:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe >= 460.73 and nvidia-settings >= 460.73.
This is impacting data scientists and deep learning customers.
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
* Ensure nvidia and libnvidia files come from the Ubuntu repository:
echo 'Package: nvidia-* libnvidia-* xserver-xorg-*
Pin: release l=NVIDIA CUDA
Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf
sudo apt-get update
* Install nvidia-driver-460 from the Ubuntu repository:
sudo apt-get install nvidia-driver-460
* Confirm that almost all Nvidia driver packages are set to the same
version (460.73.01) except for nvidia-settings and nvidia-modprobe:
dpkg --list |grep nvidia |grep ^ii |awk '{print $3"\t" $2}' |sort -n
* Attempt to install the CUDA package from Nvidia
sudo apt-get install cuda-drivers-460
* The drivers will not install due to a version mismatch as show
below:
sudo apt-get install cuda-drivers-460
...
The following packages have unmet dependencies:
cuda-drivers-460
Depends: nvidia-modprobe (>= 460.73.01) but 460.32.03-0ubuntu20.04.1 is to be
installed
Depends: nvidia-settings (>= 460.73.01) but 460.39-0ubuntu0.20.04.1 is to be
installed
E: Unable to correct problems, you have held broken packages.
[Where problems could occur]
* This may potentially cause issues with older versions of the Nvidia
driver, but this is low since this is for users of the 460 drivers.
[Other Information]
Can nvidia-modprobe and nvidia-settings be synchronized to match the
other versions provided in this and all future nvidia-drivers-*
metapackages? This should resolve the issue forever going forward.
Debdiffs:
Hirsute: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files
/nvidia-
settings_460.56-0ubuntu2_460.73.01-0ubuntu1~ubuntu21.04.1~ppa1.diff.gz
Groovy: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files
/nvidia-
settings_440.82-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.10.1~ppa1.diff.gz
Focal:
https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files/nvidia-settings_440.64-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.04.1~ppa1.diff.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-modprobe/+bug/1928146/+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 1925685] Re: [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer
Installed and ran on systems containing issue. Kernel seemed to work flawlessly. We are going to roll with this kernel and resume sales of our systems. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1925685 Title: [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Bionic: Won't Fix Status in linux-hwe-5.8 source package in Bionic: Confirmed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.8 source package in Focal: Confirmed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: Confirmed Status in linux-hwe-5.8 source package in Groovy: Confirmed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux source package in Hirsute: Confirmed Status in linux-hwe-5.8 source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-hwe-5.8 source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Bug description: Filing this with my Kubuntu Focus (kfocus.org) OEM hat on: [Impact] We are having screen flickering and glitching issues with some of our hardware upon wake from suspend. We have worked with our ODM to figure out a fix for this. They had reported there were no issues when running Windows on the same hardware. As such, we tested, and found that this issue first began as a regression in kernel 5.0 (did not exist in kernel 4.18 per our tests). We identified a patch via https://gitlab.freedesktop.org/drm/intel/-/issues/272 in which this has been solved. Per our testing by recompiling the kernel, this completely fixes our hardware issue. As of 4-21, this fix has been merged into the Linux kernel per Timo Aaltonen, and will be included in the kernel in the 5.13 release. Our hardware ships with Kubuntu 20.04 LTS, which means the 5.13 kernel will not see these machines, at least in the forseeable future. As such, we request that this patch be added to the kernel. Per our testing, this patch is straightforward to add and works flawlessly. The patch that works best was created in collaboration with Kai-Heng Feng, is attached to this bug report, and can be found here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+attachment/5491421/+files /drm-intel-both.patch Until this is fixed, we have a whole batch of hardware we cannot sell, so, as an OEM, this is a high priority. [Test Plan] * Install Kubuntu on an affected Kubuntu Focus M2 computer (not in the hands of customers at this time) * Notice screen glitching/flickering after wake-from-suspend. * Install kernel compiled with the attached patch. Boot from patched kernel. * Suspend laptop, resume. No glitches. [Where problems could occur] * Although this solves the problem for us and has been confirmed to work with the Intel developers that developed this patch, it could cause another display type to have problems. This is unlikely as it has been vetted by Intel and by the mainline Linux kernel developers. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1925685/+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 1928146] Re: Please SRU nvidia-modprobe 465.24 and nvidia-settings 460.73
** Changed in: nvidia-settings (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: nvidia-settings (Ubuntu Groovy)
Status: Fix Committed => Fix Released
** Changed in: nvidia-settings (Ubuntu Hirsute)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1928146
Title:
Please SRU nvidia-modprobe 465.24 and nvidia-settings 460.73
Status in nvidia-modprobe package in Ubuntu:
Fix Released
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in nvidia-modprobe source package in Focal:
Fix Committed
Status in nvidia-settings source package in Focal:
Fix Released
Status in nvidia-modprobe source package in Groovy:
Fix Committed
Status in nvidia-settings source package in Groovy:
Fix Released
Status in nvidia-modprobe source package in Hirsute:
Fix Committed
Status in nvidia-settings source package in Hirsute:
Fix Released
Status in nvidia-modprobe source package in Impish:
Fix Released
Status in nvidia-settings source package in Impish:
Fix Released
Bug description:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe >= 460.73 and nvidia-settings >= 460.73.
This is impacting data scientists and deep learning customers.
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
* Ensure nvidia and libnvidia files come from the Ubuntu repository:
echo 'Package: nvidia-* libnvidia-* xserver-xorg-*
Pin: release l=NVIDIA CUDA
Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf
sudo apt-get update
* Install nvidia-driver-460 from the Ubuntu repository:
sudo apt-get install nvidia-driver-460
* Confirm that almost all Nvidia driver packages are set to the same
version (460.73.01) except for nvidia-settings and nvidia-modprobe:
dpkg --list |grep nvidia |grep ^ii |awk '{print $3"\t" $2}' |sort -n
* Attempt to install the CUDA package from Nvidia
sudo apt-get install cuda-drivers-460
* The drivers will not install due to a version mismatch as show
below:
sudo apt-get install cuda-drivers-460
...
The following packages have unmet dependencies:
cuda-drivers-460
Depends: nvidia-modprobe (>= 460.73.01) but 460.32.03-0ubuntu20.04.1 is to be
installed
Depends: nvidia-settings (>= 460.73.01) but 460.39-0ubuntu0.20.04.1 is to be
installed
E: Unable to correct problems, you have held broken packages.
[Where problems could occur]
* This may potentially cause issues with older versions of the Nvidia
driver, but this is low since this is for users of the 460 drivers.
[Other Information]
Can nvidia-modprobe and nvidia-settings be synchronized to match the
other versions provided in this and all future nvidia-drivers-*
metapackages? This should resolve the issue forever going forward.
Debdiffs:
Hirsute: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files
/nvidia-
settings_460.56-0ubuntu2_460.73.01-0ubuntu1~ubuntu21.04.1~ppa1.diff.gz
Groovy: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files
/nvidia-
settings_440.82-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.10.1~ppa1.diff.gz
Focal:
https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files/nvidia-settings_440.64-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.04.1~ppa1.diff.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-modprobe/+bug/1928146/+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 1928146] Re: Please SRU nvidia-modprobe 465.24
** Summary changed:
- Please SRU nvidia-modprobe 465.24 and nvidia-settings 460.73
+ Please SRU nvidia-modprobe 465.24
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1928146
Title:
Please SRU nvidia-modprobe 465.24
Status in nvidia-modprobe package in Ubuntu:
Fix Released
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in nvidia-modprobe source package in Focal:
Fix Committed
Status in nvidia-settings source package in Focal:
Fix Released
Status in nvidia-modprobe source package in Groovy:
Fix Committed
Status in nvidia-settings source package in Groovy:
Fix Released
Status in nvidia-modprobe source package in Hirsute:
Fix Committed
Status in nvidia-settings source package in Hirsute:
Fix Released
Status in nvidia-modprobe source package in Impish:
Fix Released
Status in nvidia-settings source package in Impish:
Fix Released
Bug description:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe >= 460.73 and nvidia-settings >= 460.73.
This is impacting data scientists and deep learning customers.
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
* Ensure nvidia and libnvidia files come from the Ubuntu repository:
echo 'Package: nvidia-* libnvidia-* xserver-xorg-*
Pin: release l=NVIDIA CUDA
Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf
sudo apt-get update
* Install nvidia-driver-460 from the Ubuntu repository:
sudo apt-get install nvidia-driver-460
* Confirm that almost all Nvidia driver packages are set to the same
version (460.73.01) except for nvidia-settings and nvidia-modprobe:
dpkg --list |grep nvidia |grep ^ii |awk '{print $3"\t" $2}' |sort -n
* Attempt to install the CUDA package from Nvidia
sudo apt-get install cuda-drivers-460
* The drivers will not install due to a version mismatch as show
below:
sudo apt-get install cuda-drivers-460
...
The following packages have unmet dependencies:
cuda-drivers-460
Depends: nvidia-modprobe (>= 460.73.01) but 460.32.03-0ubuntu20.04.1 is to be
installed
Depends: nvidia-settings (>= 460.73.01) but 460.39-0ubuntu0.20.04.1 is to be
installed
E: Unable to correct problems, you have held broken packages.
[Where problems could occur]
* This may potentially cause issues with older versions of the Nvidia
driver, but this is low since this is for users of the 460 drivers.
[Other Information]
Can nvidia-modprobe and nvidia-settings be synchronized to match the
other versions provided in this and all future nvidia-drivers-*
metapackages? This should resolve the issue forever going forward.
Debdiffs:
Hirsute: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files
/nvidia-
settings_460.56-0ubuntu2_460.73.01-0ubuntu1~ubuntu21.04.1~ppa1.diff.gz
Groovy: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files
/nvidia-
settings_440.82-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.10.1~ppa1.diff.gz
Focal:
https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files/nvidia-settings_440.64-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.04.1~ppa1.diff.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-modprobe/+bug/1928146/+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 1925685] Re: [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer
Verified fixes work in Hirsute as well using above method. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/1925685 Title: [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Bionic: Won't Fix Status in linux-hwe-5.8 source package in Bionic: Confirmed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.8 source package in Focal: Confirmed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-hwe-5.8 source package in Groovy: Confirmed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Committed Status in linux-hwe-5.8 source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-hwe-5.8 source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Bug description: Filing this with my Kubuntu Focus (kfocus.org) OEM hat on: [Impact] We are having screen flickering and glitching issues with some of our hardware upon wake from suspend. We have worked with our ODM to figure out a fix for this. They had reported there were no issues when running Windows on the same hardware. As such, we tested, and found that this issue first began as a regression in kernel 5.0 (did not exist in kernel 4.18 per our tests). We identified a patch via https://gitlab.freedesktop.org/drm/intel/-/issues/272 in which this has been solved. Per our testing by recompiling the kernel, this completely fixes our hardware issue. As of 4-21, this fix has been merged into the Linux kernel per Timo Aaltonen, and will be included in the kernel in the 5.13 release. Our hardware ships with Kubuntu 20.04 LTS, which means the 5.13 kernel will not see these machines, at least in the forseeable future. As such, we request that this patch be added to the kernel. Per our testing, this patch is straightforward to add and works flawlessly. The patch that works best was created in collaboration with Kai-Heng Feng, is attached to this bug report, and can be found here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+attachment/5491421/+files /drm-intel-both.patch Until this is fixed, we have a whole batch of hardware we cannot sell, so, as an OEM, this is a high priority. [Test Plan] * Install Kubuntu on an affected Kubuntu Focus M2 computer (not in the hands of customers at this time) * Notice screen glitching/flickering after wake-from-suspend. * Install kernel compiled with the attached patch. Boot from patched kernel. * Suspend laptop, resume. No glitches. [Where problems could occur] * Although this solves the problem for us and has been confirmed to work with the Intel developers that developed this patch, it could cause another display type to have problems. This is unlikely as it has been vetted by Intel and by the mainline Linux kernel developers. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1925685/+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 1925685] Re: [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer
Verified fixes work in Groovy as well using the above method. ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- 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/1925685 Title: [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Bionic: Won't Fix Status in linux-hwe-5.8 source package in Bionic: Confirmed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.8 source package in Focal: Confirmed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-hwe-5.8 source package in Groovy: Confirmed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Committed Status in linux-hwe-5.8 source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-hwe-5.8 source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Bug description: Filing this with my Kubuntu Focus (kfocus.org) OEM hat on: [Impact] We are having screen flickering and glitching issues with some of our hardware upon wake from suspend. We have worked with our ODM to figure out a fix for this. They had reported there were no issues when running Windows on the same hardware. As such, we tested, and found that this issue first began as a regression in kernel 5.0 (did not exist in kernel 4.18 per our tests). We identified a patch via https://gitlab.freedesktop.org/drm/intel/-/issues/272 in which this has been solved. Per our testing by recompiling the kernel, this completely fixes our hardware issue. As of 4-21, this fix has been merged into the Linux kernel per Timo Aaltonen, and will be included in the kernel in the 5.13 release. Our hardware ships with Kubuntu 20.04 LTS, which means the 5.13 kernel will not see these machines, at least in the forseeable future. As such, we request that this patch be added to the kernel. Per our testing, this patch is straightforward to add and works flawlessly. The patch that works best was created in collaboration with Kai-Heng Feng, is attached to this bug report, and can be found here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+attachment/5491421/+files /drm-intel-both.patch Until this is fixed, we have a whole batch of hardware we cannot sell, so, as an OEM, this is a high priority. [Test Plan] * Install Kubuntu on an affected Kubuntu Focus M2 computer (not in the hands of customers at this time) * Notice screen glitching/flickering after wake-from-suspend. * Install kernel compiled with the attached patch. Boot from patched kernel. * Suspend laptop, resume. No glitches. [Where problems could occur] * Although this solves the problem for us and has been confirmed to work with the Intel developers that developed this patch, it could cause another display type to have problems. This is unlikely as it has been vetted by Intel and by the mainline Linux kernel developers. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1925685/+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 1928146] Re: Please SRU nvidia-modprobe 465.24
Enabled proposed for this file, does exactly what is described and
allows for CUDA library installation on Hirsute, Groovy, and Focal.
** Tags removed: verification-needed verification-needed-focal
verification-needed-groovy verification-needed-hirsute
** Tags added: verification-done verification-done-focal
verification-done-groovy verification-done-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1928146
Title:
Please SRU nvidia-modprobe 465.24
Status in nvidia-modprobe package in Ubuntu:
Fix Released
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in nvidia-modprobe source package in Focal:
Fix Committed
Status in nvidia-settings source package in Focal:
Fix Released
Status in nvidia-modprobe source package in Groovy:
Fix Committed
Status in nvidia-settings source package in Groovy:
Fix Released
Status in nvidia-modprobe source package in Hirsute:
Fix Committed
Status in nvidia-settings source package in Hirsute:
Fix Released
Status in nvidia-modprobe source package in Impish:
Fix Released
Status in nvidia-settings source package in Impish:
Fix Released
Bug description:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe >= 460.73 and nvidia-settings >= 460.73.
This is impacting data scientists and deep learning customers.
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
* Ensure nvidia and libnvidia files come from the Ubuntu repository:
echo 'Package: nvidia-* libnvidia-* xserver-xorg-*
Pin: release l=NVIDIA CUDA
Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf
sudo apt-get update
* Install nvidia-driver-460 from the Ubuntu repository:
sudo apt-get install nvidia-driver-460
* Confirm that almost all Nvidia driver packages are set to the same
version (460.73.01) except for nvidia-settings and nvidia-modprobe:
dpkg --list |grep nvidia |grep ^ii |awk '{print $3"\t" $2}' |sort -n
* Attempt to install the CUDA package from Nvidia
sudo apt-get install cuda-drivers-460
* The drivers will not install due to a version mismatch as show
below:
sudo apt-get install cuda-drivers-460
...
The following packages have unmet dependencies:
cuda-drivers-460
Depends: nvidia-modprobe (>= 460.73.01) but 460.32.03-0ubuntu20.04.1 is to be
installed
Depends: nvidia-settings (>= 460.73.01) but 460.39-0ubuntu0.20.04.1 is to be
installed
E: Unable to correct problems, you have held broken packages.
[Where problems could occur]
* This may potentially cause issues with older versions of the Nvidia
driver, but this is low since this is for users of the 460 drivers.
[Other Information]
Can nvidia-modprobe and nvidia-settings be synchronized to match the
other versions provided in this and all future nvidia-drivers-*
metapackages? This should resolve the issue forever going forward.
Debdiffs:
Hirsute: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files
/nvidia-
settings_460.56-0ubuntu2_460.73.01-0ubuntu1~ubuntu21.04.1~ppa1.diff.gz
Groovy: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files
/nvidia-
settings_440.82-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.10.1~ppa1.diff.gz
Focal:
https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files/nvidia-settings_440.64-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.04.1~ppa1.diff.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-modprobe/+bug/1928146/+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
Thank you for reporting this bug to Ubuntu. Ubuntu Studio 18.04 (bionic) reached end-of-life on January 26, 2019. 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 => 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/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in linux package in Ubuntu: Incomplete 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 1925685] [NEW] [SRU] Patch for flicker and glitching on certain hardware, intel framebuffer,
Public bug reported: Filing this with my Kubuntu Focus (kfocus.org) OEM hat on: [Impact] We are having screen flickering and glitching issues with some of our hardware upon wake from suspend. We have worked with our ODM to figure out a fix for this. They had reported there were no issues when running Windows on the same hardware. As such, we tested, and found that this issue first began as a regression in kernel 5.0 (did not exist in kernel 4.18 per our tests). We identified a patch via https://gitlab.freedesktop.org/drm/intel/-/issues/272 in which this has been solved. Per our testing by recompiling the kernel, this completely fixes our hardware issue. As of 4-21, this fix has been merged into the Linux kernel per Timo Aaltonen, and will be included in the kernel in the 5.13 release. Our hardware ships with Kubuntu 20.04 LTS, which means the 5.13 kernel will not see these machines, at least in the forseeable future. As such, we request that this patch be added to the kernel. Per our testing, this patch is straightforward to add and works flawlessly. Until this is fixed, we have a whole batch of hardware we cannot sell, so, as an OEM, this is a high priority. [Test Plan] * Install Kubuntu on an affected Kubuntu Focus M2 computer (not in the hands of customers at this time) * Notice screen glitching/flickering after wake-from-suspend. * Install kernel compiled with the attached patch. Boot from patched kernel. * Suspend laptop, resume. No glitches. [Where problems could occur] * Although this solves the problem for us and has been confirmed to work with the Intel developers that developed this patch, it could cause another display type to have problems. This is unlikely as it has been vetted by Intel and by the mainline Linux kernel developers. ** Affects: linux (Ubuntu) Importance: High Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Critical Status: Confirmed ** Affects: linux (Ubuntu Groovy) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Hirsute) Importance: High Status: Confirmed ** Tags: oem-priority ** Patch added: "Intel-developed patch to fix framebuffer flicker/glitching" https://bugs.launchpad.net/bugs/1925685/+attachment/5491120/+files/drm-intel.patch ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Critical Status: Confirmed ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Groovy) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Hirsute) Importance: Critical => High -- 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/1925685 Title: [SRU] Patch for flicker and glitching on certain hardware, intel framebuffer, Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: Filing this with my Kubuntu Focus (kfocus.org) OEM hat on: [Impact] We are having screen flickering and glitching issues with some of our hardware upon wake from suspend. We have worked with our ODM to figure out a fix for this. They had reported there were no issues when running Windows on the same hardware. As such, we tested, and found that this issue first began as a regression in kernel 5.0 (did not exist in kernel 4.18 per our tests). We identified a patch via https://gitlab.freedesktop.org/drm/intel/-/issues/272 in which this has been solved. Per our testing by recompiling the kernel, this completely fixes our hardware issue. As of 4-21, this fix has been merged into the Linux kernel per Timo Aaltonen, and will be included in the kernel in the 5.13 release. Our hardware ships with Kubuntu 20.04 LTS, which means the 5.13 kernel will not see these machines, at least in the forseeable future. As such, we request that this patch be added to the kernel. Per our testing, this patch is straightforward to add and works flawlessly. Until this is fixed, we have a whole batch of hardware we cannot sell, so, as an OEM, this is a high priority. [Test Plan] * Install Kubuntu on an affected Kubuntu Focus M2 computer (not in the hands of customers at this time) * Notice screen glitching/fl
[Kernel-packages] [Bug 1925685] Re: [SRU] Patch for flicker and glitching on certain hardware, intel framebuffer,
Hi Kai-Heng, We built a combined patch (attached) from that commit and our initial patch and tested, and it seems to work even better. We tested on only one system, but we intend to test on all the glitchy systems to ensure it is stable. That said, the commit you pointed out seems to work well in combination with our initial patch. ** Patch added: "Intel-developed patch to fix framebuffer flicker/glitching combined with presented commit" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+attachment/5491421/+files/drm-intel-both.patch -- 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/1925685 Title: [SRU] Patch for flicker and glitching on certain hardware, intel framebuffer, Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: Filing this with my Kubuntu Focus (kfocus.org) OEM hat on: [Impact] We are having screen flickering and glitching issues with some of our hardware upon wake from suspend. We have worked with our ODM to figure out a fix for this. They had reported there were no issues when running Windows on the same hardware. As such, we tested, and found that this issue first began as a regression in kernel 5.0 (did not exist in kernel 4.18 per our tests). We identified a patch via https://gitlab.freedesktop.org/drm/intel/-/issues/272 in which this has been solved. Per our testing by recompiling the kernel, this completely fixes our hardware issue. As of 4-21, this fix has been merged into the Linux kernel per Timo Aaltonen, and will be included in the kernel in the 5.13 release. Our hardware ships with Kubuntu 20.04 LTS, which means the 5.13 kernel will not see these machines, at least in the forseeable future. As such, we request that this patch be added to the kernel. Per our testing, this patch is straightforward to add and works flawlessly. Until this is fixed, we have a whole batch of hardware we cannot sell, so, as an OEM, this is a high priority. [Test Plan] * Install Kubuntu on an affected Kubuntu Focus M2 computer (not in the hands of customers at this time) * Notice screen glitching/flickering after wake-from-suspend. * Install kernel compiled with the attached patch. Boot from patched kernel. * Suspend laptop, resume. No glitches. [Where problems could occur] * Although this solves the problem for us and has been confirmed to work with the Intel developers that developed this patch, it could cause another display type to have problems. This is unlikely as it has been vetted by Intel and by the mainline Linux kernel developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+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 1925685] Re: [SRU] Patch for flicker and glitching on certain hardware, intel framebuffer,
Sadly, we can't wait that long, Kai-Heng. This is a patch that is critical to our operation and is causing money to be lost daily on machines we can't sell. There are other OEMs that are affected by this as well. The aforementioned patch is headed to kernel 5.13, due out in June. If this weren't so time-sensitive, we could have just waited for that kernel or later kernels, such as what will land in 22.04 LTS. Unfortunately, that's a year away, which is an unacceptable wait time. What you're currently asking us to do is wait until July/August for the HWE kernel to get updated prior to 20.04.3's release. That's also an unacceptable wait time as those are sales that we can't make in that time. We've been working with our ODM to try to resolve it from a hardware standpoint, but they're having a tough time accepting it as a defect since it works fine on Windows, so it must be a Linux thing (which is also unacceptable that Linux can even let this happen). So, I guess I'm asking you (or someone else on the kernel team) to do the right thing. As you can see from Mike's post above, the testing we have done is extensive and uses the 5.8 kernel, and even tested on older machines. I understand your reluctance, but we're not simply a user having trouble with their machine, we're a company trying successfully to sell Ubuntu (Kubuntu, in this case) on laptops. We have a partnership with Canonical on this as well as the Kubuntu council as the only OEM allowed to use the Kubuntu name on its products. Basically, "eventually" doesn't work for us, we need this ASAP, hence the "critical" priority. ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Importance: High => Critical -- 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/1925685 Title: [SRU] Patch for flicker and glitching on certain hardware, intel framebuffer, Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: Filing this with my Kubuntu Focus (kfocus.org) OEM hat on: [Impact] We are having screen flickering and glitching issues with some of our hardware upon wake from suspend. We have worked with our ODM to figure out a fix for this. They had reported there were no issues when running Windows on the same hardware. As such, we tested, and found that this issue first began as a regression in kernel 5.0 (did not exist in kernel 4.18 per our tests). We identified a patch via https://gitlab.freedesktop.org/drm/intel/-/issues/272 in which this has been solved. Per our testing by recompiling the kernel, this completely fixes our hardware issue. As of 4-21, this fix has been merged into the Linux kernel per Timo Aaltonen, and will be included in the kernel in the 5.13 release. Our hardware ships with Kubuntu 20.04 LTS, which means the 5.13 kernel will not see these machines, at least in the forseeable future. As such, we request that this patch be added to the kernel. Per our testing, this patch is straightforward to add and works flawlessly. Until this is fixed, we have a whole batch of hardware we cannot sell, so, as an OEM, this is a high priority. [Test Plan] * Install Kubuntu on an affected Kubuntu Focus M2 computer (not in the hands of customers at this time) * Notice screen glitching/flickering after wake-from-suspend. * Install kernel compiled with the attached patch. Boot from patched kernel. * Suspend laptop, resume. No glitches. [Where problems could occur] * Although this solves the problem for us and has been confirmed to work with the Intel developers that developed this patch, it could cause another display type to have problems. This is unlikely as it has been vetted by Intel and by the mainline Linux kernel developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+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 1925685] Re: [SRU] Patch for flicker and glitching on certain hardware, intel framebuffer,
** Patch removed: "Intel-developed patch to fix framebuffer flicker/glitching" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+attachment/5491120/+files/drm-intel.patch -- 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/1925685 Title: [SRU] Patch for flicker and glitching on certain hardware, intel framebuffer, Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: Filing this with my Kubuntu Focus (kfocus.org) OEM hat on: [Impact] We are having screen flickering and glitching issues with some of our hardware upon wake from suspend. We have worked with our ODM to figure out a fix for this. They had reported there were no issues when running Windows on the same hardware. As such, we tested, and found that this issue first began as a regression in kernel 5.0 (did not exist in kernel 4.18 per our tests). We identified a patch via https://gitlab.freedesktop.org/drm/intel/-/issues/272 in which this has been solved. Per our testing by recompiling the kernel, this completely fixes our hardware issue. As of 4-21, this fix has been merged into the Linux kernel per Timo Aaltonen, and will be included in the kernel in the 5.13 release. Our hardware ships with Kubuntu 20.04 LTS, which means the 5.13 kernel will not see these machines, at least in the forseeable future. As such, we request that this patch be added to the kernel. Per our testing, this patch is straightforward to add and works flawlessly. Until this is fixed, we have a whole batch of hardware we cannot sell, so, as an OEM, this is a high priority. [Test Plan] * Install Kubuntu on an affected Kubuntu Focus M2 computer (not in the hands of customers at this time) * Notice screen glitching/flickering after wake-from-suspend. * Install kernel compiled with the attached patch. Boot from patched kernel. * Suspend laptop, resume. No glitches. [Where problems could occur] * Although this solves the problem for us and has been confirmed to work with the Intel developers that developed this patch, it could cause another display type to have problems. This is unlikely as it has been vetted by Intel and by the mainline Linux kernel developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+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 1925685] Re: [SRU] Patch for flicker and glitching on certain hardware, intel framebuffer,
** Description changed: Filing this with my Kubuntu Focus (kfocus.org) OEM hat on: [Impact] We are having screen flickering and glitching issues with some of our hardware upon wake from suspend. We have worked with our ODM to figure out a fix for this. They had reported there were no issues when running Windows on the same hardware. As such, we tested, and found that this issue first began as a regression in kernel 5.0 (did not exist in kernel 4.18 per our tests). We identified a patch via https://gitlab.freedesktop.org/drm/intel/-/issues/272 in which this has been solved. Per our testing by recompiling the kernel, this completely fixes our hardware issue. As of 4-21, this fix has been merged into the Linux kernel per Timo Aaltonen, and will be included in the kernel in the 5.13 release. Our hardware ships with Kubuntu 20.04 LTS, which means the 5.13 kernel will not see these machines, at least in the forseeable future. As such, we request that this patch be added to the kernel. Per our testing, this patch is straightforward to add and works flawlessly. + The patch that works best was created in collaboration with Kai-Heng + Feng, is attached to this bug report, and can be found here: + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+attachment/5491421/+files + /drm-intel-both.patch + Until this is fixed, we have a whole batch of hardware we cannot sell, so, as an OEM, this is a high priority. [Test Plan] - * Install Kubuntu on an affected Kubuntu Focus M2 computer (not in the + * Install Kubuntu on an affected Kubuntu Focus M2 computer (not in the hands of customers at this time) - * Notice screen glitching/flickering after wake-from-suspend. + * Notice screen glitching/flickering after wake-from-suspend. - * Install kernel compiled with the attached patch. Boot from patched + * Install kernel compiled with the attached patch. Boot from patched kernel. - * Suspend laptop, resume. No glitches. + * Suspend laptop, resume. No glitches. [Where problems could occur] - * Although this solves the problem for us and has been confirmed to + * Although this solves the problem for us and has been confirmed to work with the Intel developers that developed this patch, it could cause another display type to have problems. This is unlikely as it has been vetted by Intel and by the mainline Linux kernel developers. -- 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/1925685 Title: [SRU] Patch for flicker and glitching on certain hardware, intel framebuffer, Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: Filing this with my Kubuntu Focus (kfocus.org) OEM hat on: [Impact] We are having screen flickering and glitching issues with some of our hardware upon wake from suspend. We have worked with our ODM to figure out a fix for this. They had reported there were no issues when running Windows on the same hardware. As such, we tested, and found that this issue first began as a regression in kernel 5.0 (did not exist in kernel 4.18 per our tests). We identified a patch via https://gitlab.freedesktop.org/drm/intel/-/issues/272 in which this has been solved. Per our testing by recompiling the kernel, this completely fixes our hardware issue. As of 4-21, this fix has been merged into the Linux kernel per Timo Aaltonen, and will be included in the kernel in the 5.13 release. Our hardware ships with Kubuntu 20.04 LTS, which means the 5.13 kernel will not see these machines, at least in the forseeable future. As such, we request that this patch be added to the kernel. Per our testing, this patch is straightforward to add and works flawlessly. The patch that works best was created in collaboration with Kai-Heng Feng, is attached to this bug report, and can be found here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+attachment/5491421/+files /drm-intel-both.patch Until this is fixed, we have a whole batch of hardware we cannot sell, so, as an OEM, this is a high priority. [Test Plan] * Install Kubuntu on an affected Kubuntu Focus M2 computer (not in the hands of customers at this time) * Notice screen glitching/flickering after wake-from-suspend. * Install kernel compiled with the attached patch. Boot from patched kernel. * Suspend laptop, resume. No glitches. [Where problems could occur] * Although this solves the problem for us and has been confirmed to work with the Intel developers that developed this patch, it could cause another display type to have problems. This is unlike
[Kernel-packages] [Bug 1925685] Re: [SRU] Patch for flicker and glitching on certain hardware, intel framebuffer,
Timo, can we get an explanation for the "Won't Fix" status as it relates to Focal? This directly affects our business as we only use LTS, therefore Focal in this case. ** Changed in: linux (Ubuntu Focal) Status: Won't Fix => Confirmed -- 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/1925685 Title: [SRU] Patch for flicker and glitching on certain hardware, intel framebuffer, Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Won't Fix Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: Filing this with my Kubuntu Focus (kfocus.org) OEM hat on: [Impact] We are having screen flickering and glitching issues with some of our hardware upon wake from suspend. We have worked with our ODM to figure out a fix for this. They had reported there were no issues when running Windows on the same hardware. As such, we tested, and found that this issue first began as a regression in kernel 5.0 (did not exist in kernel 4.18 per our tests). We identified a patch via https://gitlab.freedesktop.org/drm/intel/-/issues/272 in which this has been solved. Per our testing by recompiling the kernel, this completely fixes our hardware issue. As of 4-21, this fix has been merged into the Linux kernel per Timo Aaltonen, and will be included in the kernel in the 5.13 release. Our hardware ships with Kubuntu 20.04 LTS, which means the 5.13 kernel will not see these machines, at least in the forseeable future. As such, we request that this patch be added to the kernel. Per our testing, this patch is straightforward to add and works flawlessly. The patch that works best was created in collaboration with Kai-Heng Feng, is attached to this bug report, and can be found here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+attachment/5491421/+files /drm-intel-both.patch Until this is fixed, we have a whole batch of hardware we cannot sell, so, as an OEM, this is a high priority. [Test Plan] * Install Kubuntu on an affected Kubuntu Focus M2 computer (not in the hands of customers at this time) * Notice screen glitching/flickering after wake-from-suspend. * Install kernel compiled with the attached patch. Boot from patched kernel. * Suspend laptop, resume. No glitches. [Where problems could occur] * Although this solves the problem for us and has been confirmed to work with the Intel developers that developed this patch, it could cause another display type to have problems. This is unlikely as it has been vetted by Intel and by the mainline Linux kernel developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+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 1925685] Re: [SRU] Patch for flicker and glitching on certain hardware, intel framebuffer,
Added linux-hwe-5.8 because that's really where the issues against Focal appear. I now understand why Timo marked as "Won't fix" since that's for the 5.4 kernel in Focal. ** Also affects: linux-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: Confirmed => Won't Fix ** Changed in: linux-hwe-5.8 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-hwe-5.8 (Ubuntu Bionic) Status: New => Confirmed ** Also affects: linux (Ubuntu Impish) Importance: High Assignee: Kai-Heng Feng (kaihengfeng) Status: Confirmed ** Also affects: linux-hwe-5.8 (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux-hwe-5.8 (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Bionic) Importance: Critical => Undecided ** Changed in: linux (Ubuntu Focal) Importance: Critical => Undecided -- 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/1925685 Title: [SRU] Patch for flicker and glitching on certain hardware, intel framebuffer, Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.8 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-hwe-5.8 source package in Bionic: Confirmed Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.8 source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux-hwe-5.8 source package in Groovy: New Status in linux source package in Hirsute: Confirmed Status in linux-hwe-5.8 source package in Hirsute: New Status in linux source package in Impish: Confirmed Status in linux-hwe-5.8 source package in Impish: New Bug description: Filing this with my Kubuntu Focus (kfocus.org) OEM hat on: [Impact] We are having screen flickering and glitching issues with some of our hardware upon wake from suspend. We have worked with our ODM to figure out a fix for this. They had reported there were no issues when running Windows on the same hardware. As such, we tested, and found that this issue first began as a regression in kernel 5.0 (did not exist in kernel 4.18 per our tests). We identified a patch via https://gitlab.freedesktop.org/drm/intel/-/issues/272 in which this has been solved. Per our testing by recompiling the kernel, this completely fixes our hardware issue. As of 4-21, this fix has been merged into the Linux kernel per Timo Aaltonen, and will be included in the kernel in the 5.13 release. Our hardware ships with Kubuntu 20.04 LTS, which means the 5.13 kernel will not see these machines, at least in the forseeable future. As such, we request that this patch be added to the kernel. Per our testing, this patch is straightforward to add and works flawlessly. The patch that works best was created in collaboration with Kai-Heng Feng, is attached to this bug report, and can be found here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+attachment/5491421/+files /drm-intel-both.patch Until this is fixed, we have a whole batch of hardware we cannot sell, so, as an OEM, this is a high priority. [Test Plan] * Install Kubuntu on an affected Kubuntu Focus M2 computer (not in the hands of customers at this time) * Notice screen glitching/flickering after wake-from-suspend. * Install kernel compiled with the attached patch. Boot from patched kernel. * Suspend laptop, resume. No glitches. [Where problems could occur] * Although this solves the problem for us and has been confirmed to work with the Intel developers that developed this patch, it could cause another display type to have problems. This is unlikely as it has been vetted by Intel and by the mainline Linux kernel developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+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 1925685] Re: [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer
** Summary changed: - [SRU] Patch for flicker and glitching on certain hardware, intel framebuffer, + [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer -- 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/1925685 Title: [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.8 package in Ubuntu: Confirmed Status in linux source package in Bionic: Won't Fix Status in linux-hwe-5.8 source package in Bionic: Confirmed Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.8 source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux-hwe-5.8 source package in Groovy: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux-hwe-5.8 source package in Hirsute: Confirmed Status in linux source package in Impish: Confirmed Status in linux-hwe-5.8 source package in Impish: Confirmed Bug description: Filing this with my Kubuntu Focus (kfocus.org) OEM hat on: [Impact] We are having screen flickering and glitching issues with some of our hardware upon wake from suspend. We have worked with our ODM to figure out a fix for this. They had reported there were no issues when running Windows on the same hardware. As such, we tested, and found that this issue first began as a regression in kernel 5.0 (did not exist in kernel 4.18 per our tests). We identified a patch via https://gitlab.freedesktop.org/drm/intel/-/issues/272 in which this has been solved. Per our testing by recompiling the kernel, this completely fixes our hardware issue. As of 4-21, this fix has been merged into the Linux kernel per Timo Aaltonen, and will be included in the kernel in the 5.13 release. Our hardware ships with Kubuntu 20.04 LTS, which means the 5.13 kernel will not see these machines, at least in the forseeable future. As such, we request that this patch be added to the kernel. Per our testing, this patch is straightforward to add and works flawlessly. The patch that works best was created in collaboration with Kai-Heng Feng, is attached to this bug report, and can be found here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+attachment/5491421/+files /drm-intel-both.patch Until this is fixed, we have a whole batch of hardware we cannot sell, so, as an OEM, this is a high priority. [Test Plan] * Install Kubuntu on an affected Kubuntu Focus M2 computer (not in the hands of customers at this time) * Notice screen glitching/flickering after wake-from-suspend. * Install kernel compiled with the attached patch. Boot from patched kernel. * Suspend laptop, resume. No glitches. [Where problems could occur] * Although this solves the problem for us and has been confirmed to work with the Intel developers that developed this patch, it could cause another display type to have problems. This is unlikely as it has been vetted by Intel and by the mainline Linux kernel developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+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 1928146] [NEW] Please SRU nvidia-modprobe and nvidia-settings 460.73
Public bug reported:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe 460.73 and nvidia-settings 460.73.
This is impacting data scientists and AI learning customers, which are
target customers of the Kubuntu Focus laptops produced by
MindShareManagement
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
* Ensure nvidia and libnvidia files come from the Ubuntu repository:
echo 'Package: nvidia-* libnvidia-* xserver-xorg-*
Pin: release l=NVIDIA CUDA
Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf
sudo apt-get update
* Install nvidia-driver-460 from the Ubuntu repository:
sudo apt-get install nvidia-driver-460
* Confirm that almost all Nvidia driver packages are set to the same
version (460.73.01) except for nvidia-settings and nvidia-modprobe:
dpkg --list |grep nvidia |grep ^ii |awk '{print $3"\t" $2}' |sort -n
* Attempt to install the CUDA package from Nvidia
sudo apt-get install cuda-drivers-460
* The drivers will not install due to a version mismatch as show below:
sudo apt-get install cuda-drivers-460
...
The following packages have unmet dependencies:
cuda-drivers-460
Depends: nvidia-modprobe (>= 460.73.01) but 460.32.03-0ubuntu20.04.1 is to be
installed
Depends: nvidia-settings (>= 460.73.01) but 460.39-0ubuntu0.20.04.1 is to be
installed
E: Unable to correct problems, you have held broken packages.
[Where problems could occur]
* This may potentially cause issues with older versions of the Nvidia
driver, but this is low since this is for users of the 460 drivers.
[Other Information]
Can nvidia-modprobe and nvidia-settings be synchronized to match the
other versions provided in this and all future nvidia-drivers-*
metapackages? This should resolve the issue forever going forward.
** Affects: nvidia-modprobe (Ubuntu)
Importance: Undecided
Status: New
** Affects: nvidia-settings (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: nvidia-modprobe (Ubuntu Focal)
Importance: Undecided
Status: New
** Affects: nvidia-settings (Ubuntu Focal)
Importance: Undecided
Status: New
** Affects: nvidia-modprobe (Ubuntu Groovy)
Importance: Undecided
Status: New
** Affects: nvidia-settings (Ubuntu Groovy)
Importance: Undecided
Status: New
** Affects: nvidia-modprobe (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Affects: nvidia-settings (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Affects: nvidia-modprobe (Ubuntu Impish)
Importance: Undecided
Status: New
** Affects: nvidia-settings (Ubuntu Impish)
Importance: Undecided
Status: Fix Released
** Tags: oem-priority
** Also affects: nvidia-settings (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-settings (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nvidia-modprobe (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nvidia-settings (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: nvidia-modprobe (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: nvidia-settings (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: nvidia-modprobe (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: nvidia-settings (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: nvidia-modprobe (Ubuntu Impish)
Importance: Undecided
Status: New
** Changed in: nvidia-settings (Ubuntu Impish)
Status: New => Fix Released
** Changed in: nvidia-modprobe (Ubuntu Impish)
Status: New => Fix Released
** Description changed:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe 460.73 and nvidia-settings 460.73.
This is impacting data scientists and AI learning customers, which are
target customers of the Kubuntu Focus laptops produced by
MindShareManagement
-
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
-
* Ensure nvidia and
[Kernel-packages] [Bug 1928146] Re: Please SRU nvidia-modprobe and nvidia-settings 460.73
** Changed in: nvidia-modprobe (Ubuntu Impish)
Status: Fix Released => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1928146
Title:
Please SRU nvidia-modprobe and nvidia-settings 460.73
Status in nvidia-modprobe package in Ubuntu:
Fix Released
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in nvidia-modprobe source package in Focal:
New
Status in nvidia-settings source package in Focal:
New
Status in nvidia-modprobe source package in Groovy:
New
Status in nvidia-settings source package in Groovy:
New
Status in nvidia-modprobe source package in Hirsute:
New
Status in nvidia-settings source package in Hirsute:
New
Status in nvidia-modprobe source package in Impish:
Fix Released
Status in nvidia-settings source package in Impish:
Fix Released
Bug description:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe 460.73 and nvidia-settings 460.73.
This is impacting data scientists and deep learning customers.
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
* Ensure nvidia and libnvidia files come from the Ubuntu repository:
echo 'Package: nvidia-* libnvidia-* xserver-xorg-*
Pin: release l=NVIDIA CUDA
Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf
sudo apt-get update
* Install nvidia-driver-460 from the Ubuntu repository:
sudo apt-get install nvidia-driver-460
* Confirm that almost all Nvidia driver packages are set to the same
version (460.73.01) except for nvidia-settings and nvidia-modprobe:
dpkg --list |grep nvidia |grep ^ii |awk '{print $3"\t" $2}' |sort -n
* Attempt to install the CUDA package from Nvidia
sudo apt-get install cuda-drivers-460
* The drivers will not install due to a version mismatch as show
below:
sudo apt-get install cuda-drivers-460
...
The following packages have unmet dependencies:
cuda-drivers-460
Depends: nvidia-modprobe (>= 460.73.01) but 460.32.03-0ubuntu20.04.1 is to be
installed
Depends: nvidia-settings (>= 460.73.01) but 460.39-0ubuntu0.20.04.1 is to be
installed
E: Unable to correct problems, you have held broken packages.
[Where problems could occur]
* This may potentially cause issues with older versions of the Nvidia
driver, but this is low since this is for users of the 460 drivers.
[Other Information]
Can nvidia-modprobe and nvidia-settings be synchronized to match the
other versions provided in this and all future nvidia-drivers-*
metapackages? This should resolve the issue forever going forward.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-modprobe/+bug/1928146/+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 1928146] Re: Please SRU nvidia-modprobe and nvidia-settings 460.73
This bug was fixed in the package nvidia-modprobe - 465.24.02-1
---
nvidia-modprobe (465.24.02-1) experimental; urgency=medium
* New upstream release. (Closes: #987744)
-- Luca Boccassi Thu, 29 Apr 2021 11:48:45 +0100
** Description changed:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe 460.73 and nvidia-settings 460.73.
- This is impacting data scientists and AI learning customers, which are
- target customers of the Kubuntu Focus laptops produced by
- MindShareManagement
+ This is impacting data scientists and deep learning customers.
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
* Ensure nvidia and libnvidia files come from the Ubuntu repository:
echo 'Package: nvidia-* libnvidia-* xserver-xorg-*
Pin: release l=NVIDIA CUDA
Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf
sudo apt-get update
* Install nvidia-driver-460 from the Ubuntu repository:
sudo apt-get install nvidia-driver-460
* Confirm that almost all Nvidia driver packages are set to the same
version (460.73.01) except for nvidia-settings and nvidia-modprobe:
dpkg --list |grep nvidia |grep ^ii |awk '{print $3"\t" $2}' |sort -n
* Attempt to install the CUDA package from Nvidia
sudo apt-get install cuda-drivers-460
* The drivers will not install due to a version mismatch as show below:
sudo apt-get install cuda-drivers-460
...
The following packages have unmet dependencies:
cuda-drivers-460
Depends: nvidia-modprobe (>= 460.73.01) but 460.32.03-0ubuntu20.04.1 is to be
installed
Depends: nvidia-settings (>= 460.73.01) but 460.39-0ubuntu0.20.04.1 is to be
installed
E: Unable to correct problems, you have held broken packages.
[Where problems could occur]
* This may potentially cause issues with older versions of the Nvidia
driver, but this is low since this is for users of the 460 drivers.
[Other Information]
Can nvidia-modprobe and nvidia-settings be synchronized to match the
other versions provided in this and all future nvidia-drivers-*
metapackages? This should resolve the issue forever going forward.
** Changed in: nvidia-modprobe (Ubuntu)
Status: New => Fix Released
** Summary changed:
- Please SRU nvidia-modprobe and nvidia-settings 460.73
+ Please SRU nvidia-modprobe 465.24 and nvidia-settings 460.73
** Description changed:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
- dependency on nvidia-modprobe 460.73 and nvidia-settings 460.73.
+ dependency on nvidia-modprobe >= 460.73 and nvidia-settings >= 460.73.
This is impacting data scientists and deep learning customers.
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
* Ensure nvidia and libnvidia files come from the Ubuntu repository:
echo 'Package: nvidia-* libnvidia-* xserver-xorg-*
Pin: release l=NVIDIA CUDA
Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf
sudo apt-get update
* Install nvidia-driver-460 from the Ubuntu repository:
sudo apt-get install nvidia-driver-460
* Confirm that almost all Nvidia driver packages are set to the same
version (460.73.01) except for nvidia-settings and nvidia-modprobe:
dpkg --list |grep nvidia |grep ^ii |awk '{print $3"\t" $2}' |sort -n
* Attempt to install the CUDA package from Nvidia
sudo apt-get install cuda-drivers-460
* The drivers will not install due to a version mismatch as show below:
sudo apt-get install cuda-drivers-460
...
The following packages have unmet dependencies:
cuda-drivers-460
Depends: nvidia-modprobe (>= 460.73.01) but 460.32.03-0ubuntu20.04.1 is to be
installed
Depends: nvidia-settings (>= 460.73.01) but 460.39-0ubuntu0.20.04.1 is to be
installed
E: Unable to correct problems, you have held broken packages.
[Where problems could occur]
* This may potentially cause issues with older versions of the Nvidia
driver, but this is low since this is for users of the 460 drivers.
[Other Information]
Can nvidia-modprobe and nvidia-settings be s
[Kernel-packages] [Bug 1928146] Re: Please SRU nvidia-modprobe 465.24 and nvidia-settings 460.73
** Description changed:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe >= 460.73 and nvidia-settings >= 460.73.
This is impacting data scientists and deep learning customers.
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
* Ensure nvidia and libnvidia files come from the Ubuntu repository:
echo 'Package: nvidia-* libnvidia-* xserver-xorg-*
Pin: release l=NVIDIA CUDA
Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf
sudo apt-get update
* Install nvidia-driver-460 from the Ubuntu repository:
sudo apt-get install nvidia-driver-460
* Confirm that almost all Nvidia driver packages are set to the same
version (460.73.01) except for nvidia-settings and nvidia-modprobe:
dpkg --list |grep nvidia |grep ^ii |awk '{print $3"\t" $2}' |sort -n
* Attempt to install the CUDA package from Nvidia
sudo apt-get install cuda-drivers-460
* The drivers will not install due to a version mismatch as show below:
sudo apt-get install cuda-drivers-460
...
The following packages have unmet dependencies:
cuda-drivers-460
Depends: nvidia-modprobe (>= 460.73.01) but 460.32.03-0ubuntu20.04.1 is to be
installed
Depends: nvidia-settings (>= 460.73.01) but 460.39-0ubuntu0.20.04.1 is to be
installed
E: Unable to correct problems, you have held broken packages.
[Where problems could occur]
* This may potentially cause issues with older versions of the Nvidia
driver, but this is low since this is for users of the 460 drivers.
[Other Information]
Can nvidia-modprobe and nvidia-settings be synchronized to match the
other versions provided in this and all future nvidia-drivers-*
metapackages? This should resolve the issue forever going forward.
+
+
+ Debdiffs:
+
+ Hirsute: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files
+ /nvidia-
+ settings_460.56-0ubuntu2_460.73.01-0ubuntu1~ubuntu21.04.1~ppa1.diff.gz
+
+ Groovy: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files
+ /nvidia-
+ settings_440.82-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.10.1~ppa1.diff.gz
+
+ Focal:
+
https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files/nvidia-settings_440.64-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.04.1~ppa1.diff.gz
** Changed in: nvidia-modprobe (Ubuntu Hirsute)
Importance: Undecided => High
** Changed in: nvidia-modprobe (Ubuntu Groovy)
Importance: Undecided => High
** Changed in: nvidia-modprobe (Ubuntu Focal)
Importance: Undecided => High
** Changed in: nvidia-settings (Ubuntu Focal)
Importance: Undecided => High
** Changed in: nvidia-settings (Ubuntu Groovy)
Importance: Undecided => High
** Changed in: nvidia-settings (Ubuntu Hirsute)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1928146
Title:
Please SRU nvidia-modprobe 465.24 and nvidia-settings 460.73
Status in nvidia-modprobe package in Ubuntu:
Fix Released
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in nvidia-modprobe source package in Focal:
New
Status in nvidia-settings source package in Focal:
New
Status in nvidia-modprobe source package in Groovy:
New
Status in nvidia-settings source package in Groovy:
New
Status in nvidia-modprobe source package in Hirsute:
New
Status in nvidia-settings source package in Hirsute:
New
Status in nvidia-modprobe source package in Impish:
Fix Released
Status in nvidia-settings source package in Impish:
Fix Released
Bug description:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe >= 460.73 and nvidia-settings >= 460.73.
This is impacting data scientists and deep learning customers.
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
* Ensure nvidia and libnvidia files come from the Ubuntu repository:
echo 'Package: nvidia-* libnvidia-* xserver-xorg-*
Pin: release l=NVIDIA CUDA
Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf
sudo
[Kernel-packages] [Bug 1928146] Re: Please SRU nvidia-modprobe 465.24 and nvidia-settings 460.73
** Changed in: nvidia-modprobe (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: nvidia-modprobe (Ubuntu Groovy)
Status: New => Fix Committed
** Changed in: nvidia-modprobe (Ubuntu Hirsute)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1928146
Title:
Please SRU nvidia-modprobe 465.24 and nvidia-settings 460.73
Status in nvidia-modprobe package in Ubuntu:
Fix Released
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in nvidia-modprobe source package in Focal:
Fix Committed
Status in nvidia-settings source package in Focal:
New
Status in nvidia-modprobe source package in Groovy:
Fix Committed
Status in nvidia-settings source package in Groovy:
New
Status in nvidia-modprobe source package in Hirsute:
Fix Committed
Status in nvidia-settings source package in Hirsute:
New
Status in nvidia-modprobe source package in Impish:
Fix Released
Status in nvidia-settings source package in Impish:
Fix Released
Bug description:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe >= 460.73 and nvidia-settings >= 460.73.
This is impacting data scientists and deep learning customers.
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
* Ensure nvidia and libnvidia files come from the Ubuntu repository:
echo 'Package: nvidia-* libnvidia-* xserver-xorg-*
Pin: release l=NVIDIA CUDA
Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf
sudo apt-get update
* Install nvidia-driver-460 from the Ubuntu repository:
sudo apt-get install nvidia-driver-460
* Confirm that almost all Nvidia driver packages are set to the same
version (460.73.01) except for nvidia-settings and nvidia-modprobe:
dpkg --list |grep nvidia |grep ^ii |awk '{print $3"\t" $2}' |sort -n
* Attempt to install the CUDA package from Nvidia
sudo apt-get install cuda-drivers-460
* The drivers will not install due to a version mismatch as show
below:
sudo apt-get install cuda-drivers-460
...
The following packages have unmet dependencies:
cuda-drivers-460
Depends: nvidia-modprobe (>= 460.73.01) but 460.32.03-0ubuntu20.04.1 is to be
installed
Depends: nvidia-settings (>= 460.73.01) but 460.39-0ubuntu0.20.04.1 is to be
installed
E: Unable to correct problems, you have held broken packages.
[Where problems could occur]
* This may potentially cause issues with older versions of the Nvidia
driver, but this is low since this is for users of the 460 drivers.
[Other Information]
Can nvidia-modprobe and nvidia-settings be synchronized to match the
other versions provided in this and all future nvidia-drivers-*
metapackages? This should resolve the issue forever going forward.
Debdiffs:
Hirsute: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files
/nvidia-
settings_460.56-0ubuntu2_460.73.01-0ubuntu1~ubuntu21.04.1~ppa1.diff.gz
Groovy: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files
/nvidia-
settings_440.82-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.10.1~ppa1.diff.gz
Focal:
https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files/nvidia-settings_440.64-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.04.1~ppa1.diff.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-modprobe/+bug/1928146/+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 1915003] Re: SRU: Always update the initramfs when changing power profile
Verified on a Kubuntu Focus M1 running focal: erich@erich-KFocus:~$ apt-cache policy nvidia-settings nvidia-settings: Installed: 460.39-0ubuntu0.20.10.1 Candidate: 460.39-0ubuntu0.20.10.1 Version table: *** 460.39-0ubuntu0.20.10.1 100 100 /var/lib/dpkg/status Works exactly as expected complete with a "Please wait for the operation to complete" progress indicator. ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: SRU: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in nvidia-prime source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Committed Bug description: Since we introduced support for dynamic power management, on systems with hybrid graphics (LP: #1904583), the need to load drivers with different options has become more evident. We need to make sure that the files in the initramfs are in sync with the current user selection. This is also a chance to update the old nvidia-settings release in the archive. [Impact] * If the modules list is not in sync with the selected power profile, users may experience a black screen or increased power consumption. * Updating the initramfs can take a few seconds, and we need to provide users with some form of visual feedback. [Fix] * The prime-select tool shoud update the initramfs when switching between power profiles, and provide visual feedback. * The nvidia-settings panel should provide a progress dialog, since profile switching would otherwise freeze the UI until update-initramfs completes. [Test Case] Make sure a supported nvidia driver is installed (450, 460), then install nvidia-prime and nvidia-settings from proposed, and check the following: 1) prime-select query (to check your current profile) 2) sudo prime-select on-demand (or "intel", or "nvidia", depending on your current power profile) 3) Check that the operation completes successfully. 4) Reboot your system 5) Launch the nvidia-setting panel. 6) Select a different profile from the PRIME tab, and check that a progress dialog is correctly displayed. 7) Close the nvidia-settings panel, and reboot. [Regression Risk] Medium, while the changes in prime-select are trivial, nvidia-settings needs careful testing. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+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 1915003] Re: SRU: Always update the initramfs when changing power profile
Meant to say groovy in #15 (oops) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: SRU: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in nvidia-prime source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Committed Bug description: Since we introduced support for dynamic power management, on systems with hybrid graphics (LP: #1904583), the need to load drivers with different options has become more evident. We need to make sure that the files in the initramfs are in sync with the current user selection. This is also a chance to update the old nvidia-settings release in the archive. [Impact] * If the modules list is not in sync with the selected power profile, users may experience a black screen or increased power consumption. * Updating the initramfs can take a few seconds, and we need to provide users with some form of visual feedback. [Fix] * The prime-select tool shoud update the initramfs when switching between power profiles, and provide visual feedback. * The nvidia-settings panel should provide a progress dialog, since profile switching would otherwise freeze the UI until update-initramfs completes. [Test Case] Make sure a supported nvidia driver is installed (450, 460), then install nvidia-prime and nvidia-settings from proposed, and check the following: 1) prime-select query (to check your current profile) 2) sudo prime-select on-demand (or "intel", or "nvidia", depending on your current power profile) 3) Check that the operation completes successfully. 4) Reboot your system 5) Launch the nvidia-setting panel. 6) Select a different profile from the PRIME tab, and check that a progress dialog is correctly displayed. 7) Close the nvidia-settings panel, and reboot. [Regression Risk] Medium, while the changes in prime-select are trivial, nvidia-settings needs careful testing. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+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 1837712] Re: USB mice are jerky and laggy
*** This bug is a duplicate of bug 1787857 ***
https://bugs.launchpad.net/bugs/1787857
In the future, please report bugs against the package using "ubuntu-bug
{packagename}" in the command line. Filing bugs against Ubuntu Studio as
a whole is invalid.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntustudio
Status: New => Invalid
** This bug has been marked a duplicate of bug 1787857
USB mouse cursor lags after random time of correct behaviour
--
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/1837712
Title:
USB mice are jerky and laggy
Status in Ubuntu Studio:
Invalid
Status in linux package in Ubuntu:
New
Bug description:
Kernel is 5.0.0.20-lowlatency
64bit
I have 2 mice, one a generic USB mouse and another is a jellycomb
wireless mouse (not bluetooth), model MW156.
Both of them always give a really bad lag of the mouse.
When I switch to the 5.0.0.20-generic kernel then the issue goes away.
The issue seemed to appear in ubuntu 16.04, so I upgraded first to the
18.04 version then 19.04 - in both upgrades the issue persists.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio/+bug/1837712/+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 1837712] Re: USB mice are jerky and laggy
*** This bug is a duplicate of bug 1787857 *** https://bugs.launchpad.net/bugs/1787857 Please report that in the bug this is a duplicate of, and also mark it as affecting you. (Bug 1787857). -- 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/1837712 Title: USB mice are jerky and laggy Status in Ubuntu Studio: Invalid Status in linux package in Ubuntu: New Bug description: Kernel is 5.0.0.20-lowlatency 64bit I have 2 mice, one a generic USB mouse and another is a jellycomb wireless mouse (not bluetooth), model MW156. Both of them always give a really bad lag of the mouse. When I switch to the 5.0.0.20-generic kernel then the issue goes away. The issue seemed to appear in ubuntu 16.04, so I upgraded first to the 18.04 version then 19.04 - in both upgrades the issue persists. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntustudio/+bug/1837712/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug. Please include the information requested from the "Reporting Sound Bugs" section of https://wiki.ubuntu.com/DebuggingSoundProblems as separate attachments. This information can be gathered for you automatically by using the following command only once: apport-collect -p alsa-base 2011385 ** Also affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: New Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
Thank you for reporting this and helping make Ubuntu better. Could you please boot into a Ubuntu kernel (not third party kernel) and execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2011385 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: New Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2018200] Re: Dell XPS 15 9520 kernel 5.19.0-40-generic crashing
** Package changed: linux-meta-hwe-5.19 (Ubuntu) => linux-hwe-5.19 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2018200 Title: Dell XPS 15 9520 kernel 5.19.0-40-generic crashing Status in linux-hwe-5.19 package in Ubuntu: New Bug description: I work on a Dell XPS 15 9520 laptop half a year. I use Ubuntu 22.04.2 LTS. I didn't have any problem all this time. But after update to kernel 5.19.0-40-generic sometimes system crashes. Everything works normal if I use kernel 5.19.0-38-generic and lower. It seems like an intel graphics driver problem. When system crashes I see graphical glitches. Then updated to 5.19.0-41-generic and problem still here. The crash occurs while I am watching a video. It doesn't matter where I am watching video in a browser or a VLC player. Now I am using 5.19.0-38-generic for several days and everything is normal. I switched to 5.19.0-41-generic for creating a bug-report. I didn't find anything in the logs. When this happens, the laptop does not respond to anything. I have to turn it off by long pressing the power button. Also I checked RAM with memtestx86+. RAM is ok. CPU: 12th Gen Intel® Core™ i7-12700H × 20 RAM: Kingston 32Gb Video: Intel® Iris® Xe Graphics + Nvidia RTX 3050 (use only in games). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-generic-hwe-22.04 5.19.0.41.42~22.04.14 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 30 22:33:35 2023 InstallationDate: Installed on 2023-02-08 (81 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) 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: 2023-03-23T00:25:13.998535 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2018200/+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 2018197] Re: Ubuntu 22.04 crash when plays game in battery mode
** Package changed: linux-signed-hwe-5.19 (Ubuntu) => linux-hwe-5.19 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2018197 Title: Ubuntu 22.04 crash when plays game in battery mode Status in linux-hwe-5.19 package in Ubuntu: New Bug description: When I try to play games in battery mode, after 5-10 minutes, I see a blank screen, it's like the kernel or the whole OS crash, I can't even do Ctrl + alt + F1/F2 to change to another virtual session. It doesn't matter what game I try to play. I tried with 6.2 Linux kernel and it's making the same thing. Far as I remember, it doesn't happen in 5.15 linux kernel. Specs: CPU - AMD Ryzen 7 4800H GPU - AMD Radeon RX 5600m Motherboard - MSI Alpha 17 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 Uname: Linux 6.2.13-060213-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 30 18:34:08 2023 InstallationDate: Installed on 2021-05-24 (705 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-04-03 (391 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2018197/+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 2034636] Re: Error while updating linux-intel-iotg-tools-common
** Summary changed: - While running Updates in Discover on Ubuntu Studio 22.04, an error occures about overwiting acpidbg file + Error while updating linux-intel-iotg-tools-common -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2034636 Title: Error while updating linux-intel-iotg-tools-common Status in linux-intel-iotg package in Ubuntu: New Bug description: Error while installing package: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-83.92 The linux-intel-iotg-tools-common update fails. I am able to continue normally. I have looked at previous similarly reported bugs, most involve different versions of Kernel, linux-intel-iotg-tools-common or linux- tools-common. None appear to have a resolution. 1) lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 2) apt-cache policy linux-intel-iotg-tools-common linux-intel-iotg-tools-common: Installed: 5.15.0-1037.42 Candidate: 5.15.0-1038.43 Version table: 5.15.0-1038.43 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages *** 5.15.0-1037.42 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 100 /var/lib/dpkg/status 5.15.0-1036.41 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 5.15.0-1035.40 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 5.15.0-1034.39 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 5.15.0-1033.38 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 5.15.0-1031.36 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 5.15.0-1030.35 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 5.15.0-1028.33 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 5.15.0-1004.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages 3) I expected the update to complete successfully. 4) The update failed with an error. ProblemType: Bug DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-83.92-lowlatency 5.15.116 Uname: Linux 5.15.0-83-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 6 21:47:28 2023 InstallationDate: Installed on 2022-10-03 (338 days ago) InstallationMedia: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
[Kernel-packages] [Bug 1947043] [NEW] nvidia drivers do not update initramfs properly
Public bug reported:
When Nvidia drivers are installing, they are only rebuilding the
initramfs for the currently running kernel and/or the newest kernel when
installed. Unfortunately, that means that if one has two kernel flavors
installed (such as -generic and -lowlatency) this means that the
initramfs is only getting rebuild for the currently installed kernel
flavor and its newest version. When a user then switches to the other
kernel flavor, their video fails because the kernel they switched to
does not have the kernel module in the initramfs despite the kernel
module being compiled and available.
The root cause seems to be in nvidia-kernel-common-*.postinst and
nvidia-dkms-*.postinst:
# Update initramfs so that the blacklist ends up in the initramfs
if [ -x /usr/sbin/update-initramfs ]; then
/usr/sbin/update-initramfs -u
if [ -n "$NEWEST_KERNEL" ] && [ ${CURRENT_KERNEL} !=
${NEWEST_KERNEL} ]; then
# This can fail when dealing with a chroot see LP: #556653
/usr/sbin/update-initramfs -u -k $CURRENT_KERNEL
fi
fi
Instead of looking for the conditions to be met, this should be
rebuilding for *all* installed kernels, despite the longer amount of
time needed to do so in some cases. The rationale is that systems should
work as expected and saving time, in this case, can cause that not to
happen. As such the postinst scripts should do the following in lieu of
the above:
/usr/sbin/update-initramfs -u -k all
This ensures that all installed kernel initramfs images get rebuilt,
which adds increased safety at the expense of speed during the install.
This will also prevent a race condition where, if a kernel and the
nvidia driver are updated at the same time, that the proper initramfs
image will exist despite which order the nvidia driver and kernel get
installed.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: nvidia-driver-470 470.74-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-19.19-lowlatency 5.13.14
Uname: Linux 5.13.0-19-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Oct 13 13:12:23 2021
InstallationDate: Installed on 2021-03-20 (206 days ago)
InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320)
SourcePackage: nvidia-graphics-drivers-470
UpgradeStatus: Upgraded to impish on 2021-06-13 (122 days ago)
** Affects: nvidia-graphics-drivers-470 (Ubuntu)
Importance: Undecided
Status: New
** Affects: nvidia-graphics-drivers-470 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Affects: nvidia-graphics-drivers-470 (Ubuntu Focal)
Importance: Undecided
Status: New
** Affects: nvidia-graphics-drivers-470 (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Affects: nvidia-graphics-drivers-470 (Ubuntu Impish)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug impish oem-priority third-party-packages
** Also affects: nvidia-graphics-drivers-470 (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-470 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-470 (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-470 (Ubuntu Focal)
Importance: Undecided
Status: New
--
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/1947043
Title:
nvidia drivers do not update initramfs properly
Status in nvidia-graphics-drivers-470 package in Ubuntu:
New
Status in nvidia-graphics-drivers-470 source package in Bionic:
New
Status in nvidia-graphics-drivers-470 source package in Focal:
New
Status in nvidia-graphics-drivers-470 source package in Hirsute:
New
Status in nvidia-graphics-drivers-470 source package in Impish:
New
Bug description:
When Nvidia drivers are installing, they are only rebuilding the
initramfs for the currently running kernel and/or the newest kernel
when installed. Unfortunately, that means that if one has two kernel
flavors installed (such as -generic and -lowlatency) this means that
the initramfs is only getting rebuild for the currently installed
kernel flavor and its newest version. When a user then switches to the
other kernel flavor, their video fails because the kernel they
switched to does not have the kernel module in the initramfs despite
the kernel module being compiled and available.
The root cause seems to be in nvidia-kernel-common-*.postinst and
nvidia-dkms-*.postinst:
# Update initramfs so that the blacklist ends up in the initramfs
if [ -x /usr/sbin/update-initramfs ]; then
[Kernel-packages] [Bug 1947043] Re: nvidia drivers do not update initramfs properly
We're using whatever nvidia-driver-470 pulls in.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1947043
Title:
nvidia drivers do not update initramfs properly
Status in linux-restricted-modules package in Ubuntu:
New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
New
Status in linux-restricted-modules source package in Bionic:
New
Status in nvidia-graphics-drivers-470 source package in Bionic:
New
Status in linux-restricted-modules source package in Focal:
New
Status in nvidia-graphics-drivers-470 source package in Focal:
New
Status in linux-restricted-modules source package in Hirsute:
New
Status in nvidia-graphics-drivers-470 source package in Hirsute:
New
Status in linux-restricted-modules source package in Impish:
New
Status in nvidia-graphics-drivers-470 source package in Impish:
New
Bug description:
When Nvidia drivers are installing, they are only rebuilding the
initramfs for the currently running kernel and/or the newest kernel
when installed. Unfortunately, that means that if one has two kernel
flavors installed (such as -generic and -lowlatency) this means that
the initramfs is only getting rebuild for the currently installed
kernel flavor and its newest version. When a user then switches to the
other kernel flavor, their video fails because the kernel they
switched to does not have the kernel module in the initramfs despite
the kernel module being compiled and available.
The root cause seems to be in nvidia-kernel-common-*.postinst and
nvidia-dkms-*.postinst:
# Update initramfs so that the blacklist ends up in the initramfs
if [ -x /usr/sbin/update-initramfs ]; then
/usr/sbin/update-initramfs -u
if [ -n "$NEWEST_KERNEL" ] && [ ${CURRENT_KERNEL} !=
${NEWEST_KERNEL} ]; then
# This can fail when dealing with a chroot see LP: #556653
/usr/sbin/update-initramfs -u -k $CURRENT_KERNEL
fi
fi
Instead of looking for the conditions to be met, this should be
rebuilding for *all* installed kernels, despite the longer amount of
time needed to do so in some cases. The rationale is that systems
should work as expected and saving time, in this case, can cause that
not to happen. As such the postinst scripts should do the following in
lieu of the above:
/usr/sbin/update-initramfs -u -k all
This ensures that all installed kernel initramfs images get rebuilt,
which adds increased safety at the expense of speed during the
install. This will also prevent a race condition where, if a kernel
and the nvidia driver are updated at the same time, that the proper
initramfs image will exist despite which order the nvidia driver and
kernel get installed.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: nvidia-driver-470 470.74-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-19.19-lowlatency 5.13.14
Uname: Linux 5.13.0-19-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Oct 13 13:12:23 2021
InstallationDate: Installed on 2021-03-20 (206 days ago)
InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64
(20210320)
SourcePackage: nvidia-graphics-drivers-470
UpgradeStatus: Upgraded to impish on 2021-06-13 (122 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1947043/+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 1981930] Re: Touchpad is not detected, on Windows touchapad works
** Package changed: linux-signed-hwe-5.15 (Ubuntu) => linux-hwe-5.15 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1981930 Title: Touchpad is not detected, on Windows touchapad works Status in linux-hwe-5.15 package in Ubuntu: New Bug description: agata@agata-Aspire-E5-722:~$ cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=1 c0200 0 0 700f0203 3802078f870f401 febfffdfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=046d Product=c046 Version=0110 N: Name="Logitech USB Optical Mouse" P: Phys=usb-:00:10.0-2/input0 S: Sysfs=/devices/pci:00/:00:10.0/usb3/3-2/3-2:1.0/0003:046D:C046.0001/input/input5 U: Uniq= H: Handlers=mouse0 event5 B: PROP=0 B: EV=17 B: KEY=ff 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Acer WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input6 U: Uniq= H: Handlers=rfkill kbd event6 B: PROP=0 B: EV=13 B: KEY=1c 0 0 0 0 160080c00 30 10 0 B: MSC=10 I: Bus= Vendor= Product= Version= N: Name="HDA ATI HDMI HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:01.1/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic Front Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:14.2/sound/card1/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0003 Vendor=04f2 Product=b520 Version=0005 N: Name="HD WebCam: HD WebCam" P: Phys=usb-:00:13.0-1.2/button S: Sysfs=/devices/pci:00/:00:13.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input9 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 agata@agata-Aspire-E5-722:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 17 18:44:57 2022 InstallationDate: Installed on 2022-07-17 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1981930/+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 1981901] Re: Weird behavior on display, since kernel versions 5.15.x
RE: Comment #5 That would be getting off-topic, and support questions are no place for a bug tracker. You're better off looking for support. In your case, looking for support would be a matter of checking https://lubuntu.me/links/ for ways to get help. -- 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/1981901 Title: Weird behavior on display, since kernel versions 5.15.x Status in linux package in Ubuntu: Incomplete Bug description: Since kernel versions 5.15.x I have a problem with graphics unit and display on screen. I described it first time here https://discourse.lubuntu.me/t/lubuntu-jammy-weird-artifacts-on- display-choose-older-kernel-version-to-boot-with/3034 and recently here https://discourse.lubuntu.me/t/weird-behavior-on-display-since-kernel- versions-5-15-x/3446 Don't know what information else to provide, please advice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981901/+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
