[Kernel-packages] [Bug 2065485] Re: No Audio (Speaker and Microphone) is available in New Infinix Inbook Y2 Plus Laptop
This is to let the concerned know that audio over (inbuilt) speaker is still not resolved for Infinix Inbook Y2 Plus Laptop running Linux 6.8.0-39-generic on Ubuntu 24.04 LTS. Can anyone 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/2065485 Title: No Audio (Speaker and Microphone) is available in New Infinix Inbook Y2 Plus Laptop Status in linux package in Ubuntu: New Bug description: Hello, After installing Ubuntu 24.04 LTS in new Infinix INBOOK Y2 PLUS 11th Gen Intel Corei5-1155G7 laptop, it was noticed that audio including speaker and microphone are not available. All other functionalities are available in general except the audio as mentioned. This is to be noted that audio is working completely fine in Windows 11 which is installed in other partition in the same laptop. Please investigate the issue and provide an update. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:pradip 1921 F pipewire /dev/snd/controlC0: pradip 1926 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 11 19:34:04 2024 InstallationDate: Installed on 2024-05-07 (4 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Infinix INBOOK Y2 PLUS ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=0822f9c6-1d98-4988-aa85-5f68c805b3cb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/28/2023 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: TGL_TG325_200B_IN_V5.1.12 dmi.board.asset.tag: Default string dmi.board.name: EM_TG325_200B_V1.0 dmi.board.vendor: Infinix dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrTGL_TG325_200B_IN_V5.1.12:bd04/28/2023:br5.19:efr1.10:svnInfinix:pnINBOOKY2PLUS:pvrDefaultstring:rvnInfinix:rnEM_TG325_200B_V1.0:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDEFAULT: dmi.product.family: Laptop dmi.product.name: INBOOK Y2 PLUS dmi.product.sku: DEFAULT dmi.product.version: Default string dmi.sys.vendor: Infinix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065485/+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 2064015] [NEW] I am tryed everything for enabling bluetooth but it is not working. I request to yuo please do needful action to fixing bluetooth problems.
Public bug reported: when i am try to enable Bluetooth through the terminal, its tell that "Operation not permitted ". And another problem is "unable to get on D-bus due to security policies". if any further question you can contact me on my mail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 28 19:20:13 2024 InstallationDate: Installed on 2024-04-28 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2064015 Title: I am tryed everything for enabling bluetooth but it is not working. I request to yuo please do needful action to fixing bluetooth problems. Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: when i am try to enable Bluetooth through the terminal, its tell that "Operation not permitted ". And another problem is "unable to get on D-bus due to security policies". if any further question you can contact me on my mail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 28 19:20:13 2024 InstallationDate: Installed on 2024-04-28 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2064015/+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 2061378] [NEW] [24.04]: mpi3mr: Features and Bug Fixes
Public bug reported: Below are the features which we want to add in Ubuntu24.04 kernel over mpi3mr driver v8.8.1.0.50, - 829dce7e12c2 : mpi3mr: Driver version update to 8.8.1.0.50 - 57a80be5ec6f : mpi3mr: Update MPI Headers to revision 31 - 0a2714b787b9 : mpi3mr: Debug ability improvements - e8a5a3c3eb58 : mpi3mr: Set the WriteSame Divert Capability in the IOCInit MPI Request - 31ec576ee06a : mpi3mr: Clear ioctl blocking flag for an unresponsive controller - a18f4c58372d : mpi3mr: Set MPI request flags appropriately - dd896a6b0a0d : mpi3mr: Block devices are not removed even when VDs are offlined ** Affects: linux (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/2061378 Title: [24.04]: mpi3mr: Features and Bug Fixes Status in linux package in Ubuntu: New Bug description: Below are the features which we want to add in Ubuntu24.04 kernel over mpi3mr driver v8.8.1.0.50, - 829dce7e12c2 : mpi3mr: Driver version update to 8.8.1.0.50 - 57a80be5ec6f : mpi3mr: Update MPI Headers to revision 31 - 0a2714b787b9 : mpi3mr: Debug ability improvements - e8a5a3c3eb58 : mpi3mr: Set the WriteSame Divert Capability in the IOCInit MPI Request - 31ec576ee06a : mpi3mr: Clear ioctl blocking flag for an unresponsive controller - a18f4c58372d : mpi3mr: Set MPI request flags appropriately - dd896a6b0a0d : mpi3mr: Block devices are not removed even when VDs are offlined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061378/+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 2060918] [NEW] [24.04]: mpt3sas: Feature and critical Bug fix
Public bug reported: Below are the upstream commit IDs: c0767560b012 : scsi: mpt3sas: Reload SBR without rebooting HBA ee0017c3ed8a : scsi: mpt3sas: Prevent sending diag_reset when the controller is ready a34fc8c7361c : scsi: mpt3sas: Update driver version to 48.100.00.00 ** Affects: linux (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/2060918 Title: [24.04]: mpt3sas: Feature and critical Bug fix Status in linux package in Ubuntu: New Bug description: Below are the upstream commit IDs: c0767560b012 : scsi: mpt3sas: Reload SBR without rebooting HBA ee0017c3ed8a : scsi: mpt3sas: Prevent sending diag_reset when the controller is ready a34fc8c7361c : scsi: mpt3sas: Update driver version to 48.100.00.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060918/+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 1965927] Re: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches
Hi, I have tested the mpt3sas driver embodied in the above-provided test kernel. Results are positive and no issue is found during the testing. Below are the test cases that got executed during the testing and the results of these test cases are positive, 1. All drives attached to the controller are Enumerated in OS 2. IO stress done 3. Created a filesystem and done some IO transitions 4. Controller reset and TMs and while IOs are running 5. driver load and unload Thanks, Ranjan -- 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/1965927 Title: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: [Impact] Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below, 5db207d66d mpt3sas: Fix incorrect 4gb boundary check ca23ac823c mpt3sas: Remove scsi_dma_map errors messages 9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface [Fix] Below is the summary of each of the above bug fix commits, 1. mpt3sas: Fix incorrect 4gb boundary check: Without this patch, driver was checking whether any of it's pool crosses the 4gb boundary or not using the pool's virtual address instead of using it's dma address. So some time driver may false positively assume that the pool as crossed the 4gb boundary region (as it observes that pool's virtual address is crossing the 4gb boundary) even though it is really not. 2. mpt3sas: Remove scsi_dma_map errors messages: When driver set the DMA mask to 32bit then we observe that the SWIOTLB bounce buffers are getting exhausted quickly. For most of the IOs driver observe that scsi_dma_map() API returned with failure status and hence driver was printing below error message. Since this error message is getting printed per IO and if user issues heavy IOs then we observe that kernel overwhelmed with this error message. Also we will observe the kernel panic when the serial console is enabled. So to limit this issue, we removed this error message though this patch. "scsi_dma_map failed: request for 1310720 bytes!" 3. mpt3sas: Update persistent trigger pages from sysfs interface: When user set's any diag buffer trigger conditions then driver has to save these trigger conditions in the controller Firmware's NVRAM region. So that when system reboots then driver can get these trigger conditions from Firmware's NVRAM region and set these trigger conditions automatically. so that user no need to set these conditions again. Without this patch driver was not not saving these user provided trigger conditions in the Firmware's NVRAM region. Please let me if I have missed to add any data. [Test Plan] 1. All drives attached to the controller are Enumerated in OS 2. IO stress for 5Hrs 3. Created a filesystem and done some IO transitions 4. Controller reset and TMs and while IOs are running 5. driver load and unload 6. Reboot loop 7. Verified that the diag trigger settings are persistent across the reboots. [Where problems could occur] The regression risk is low. [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpt3sas_lp_1965927 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965927/+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 1965927] Re: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches
Please provide the kernel link on which testing is needed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965927 Title: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: [Impact] Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below, 5db207d66d mpt3sas: Fix incorrect 4gb boundary check ca23ac823c mpt3sas: Remove scsi_dma_map errors messages 9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface [Fix] Below is the summary of each of the above bug fix commits, 1. mpt3sas: Fix incorrect 4gb boundary check: Without this patch, driver was checking whether any of it's pool crosses the 4gb boundary or not using the pool's virtual address instead of using it's dma address. So some time driver may false positively assume that the pool as crossed the 4gb boundary region (as it observes that pool's virtual address is crossing the 4gb boundary) even though it is really not. 2. mpt3sas: Remove scsi_dma_map errors messages: When driver set the DMA mask to 32bit then we observe that the SWIOTLB bounce buffers are getting exhausted quickly. For most of the IOs driver observe that scsi_dma_map() API returned with failure status and hence driver was printing below error message. Since this error message is getting printed per IO and if user issues heavy IOs then we observe that kernel overwhelmed with this error message. Also we will observe the kernel panic when the serial console is enabled. So to limit this issue, we removed this error message though this patch. "scsi_dma_map failed: request for 1310720 bytes!" 3. mpt3sas: Update persistent trigger pages from sysfs interface: When user set's any diag buffer trigger conditions then driver has to save these trigger conditions in the controller Firmware's NVRAM region. So that when system reboots then driver can get these trigger conditions from Firmware's NVRAM region and set these trigger conditions automatically. so that user no need to set these conditions again. Without this patch driver was not not saving these user provided trigger conditions in the Firmware's NVRAM region. Please let me if I have missed to add any data. [Test Plan] 1. All drives attached to the controller are Enumerated in OS 2. IO stress for 5Hrs 3. Created a filesystem and done some IO transitions 4. Controller reset and TMs and while IOs are running 5. driver load and unload 6. Reboot loop 7. Verified that the diag trigger settings are persistent across the reboots. [Where problems could occur] The regression risk is low. [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpt3sas_lp_1965927 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965927/+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 2054913] [NEW] package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error e
Public bug reported: i dont know ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Feb 25 10:16:02 2024 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-09-25 (517 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2054913 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: i dont know ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Feb 25 10:16:02 2024 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-09-25 (517 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2054913/+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 2003608] Re: [i915] LSPCON failure
*** This bug is a duplicate of bug 1973098 *** https://bugs.launchpad.net/bugs/1973098 ** This bug has been marked a duplicate of bug 1973098 [i915] Intermittent freezing and LSPCON init failed kernel messages -- 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/2003608 Title: [i915] LSPCON failure Status in linux package in Ubuntu: Confirmed Bug description: External monitor connected with HDMI goes black when cable is disconnected and reconnected. Same thing happens when the screen saver kicks in. Gnome still thinks that there is an external monitor and an extended desktop, but the external monitor is black. Work-around: Disconnect the HDMI cable, reboot and then connect HDMI. This is probably a duplicate of bug #1992563. I tried to run "apport-collect 1992563" bug but was rejected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 21 11:46:00 2023 DistUpgraded: 2022-04-30 16:34:04,182 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-57-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c2] InstallationDate: Installed on 2020-11-28 (783 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20TH001EMX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=fe3b788b-eaf4-4f94-b43a-4cbc16309a90 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-30 (265 days ago) dmi.bios.date: 10/27/2022 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET41W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TH001EMX dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnLENOVO:bvrN2VET41W(1.26):bd10/27/2022:br1.26:efr1.11:svnLENOVO:pn20TH001EMX:pvrThinkPadP1Gen3:rvnLENOVO:rn20TH001EMX:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20TH001EMX dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003608/+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 1973098] Re: [i915] Intermittent freezing and LSPCON init failed kernel messages
Facing same issue on 6.6.10-76060610-generic on Pop!_OS 22.04 LTS using Dell Inspiron 15 7567. Screen fails to recover after suspend/sleep giving this error, can't switch to ttys either, only solution is to force reboot, which is very annoying as I lose all my work from the session. I've seen several forums with this bug with open issue going back to several years but there seems to be no solution, is no one working on it ?... -- 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/1973098 Title: [i915] Intermittent freezing and LSPCON init failed kernel messages Status in linux package in Ubuntu: Confirmed Status in linux-signed-oem-5.14 package in Ubuntu: Confirmed Bug description: Hardware: Lenovo ThinkPad model 20ST0055AU Boot messages show: [6.397804] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [6.397901] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on minor 0 During normal operation there will intermittently be a freeze for a second or two and then more of these messages display in the kernel logs: [ 505.487006] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 505.487072] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D [ 506.747930] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 506.748018] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D The system will then become operational again. The system is still usable, but it is annoying. I've switched onto this OEM kernel from the generic kernel (5.13), as I had other problems with 5.13 regarding external displays not coming back after idle timeouts. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1036-oem 5.14.0-1036.40 ProcVersionSignature: Ubuntu 5.14.0-1036.40-oem 5.14.21 Uname: Linux 5.14.0-1036-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 12 10:29:31 2022 InstallationDate: Installed on 2021-05-05 (371 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) 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/+bug/1973098/+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 2049979] [NEW] Cursor is moving but not taking action on some part of extreme right side of the screen
Public bug reported: When I try moving the cursor to the right side of the screen, it stops taking the actions like closing, minimizing and other options like eg. in google chrome am not able to click on settings icon which is placed at this point. It is around 2 to 3 cm from the extreme right side. My Linux version is 23.04 ** Affects: linux (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/2049979 Title: Cursor is moving but not taking action on some part of extreme right side of the screen Status in linux package in Ubuntu: New Bug description: When I try moving the cursor to the right side of the screen, it stops taking the actions like closing, minimizing and other options like eg. in google chrome am not able to click on settings icon which is placed at this point. It is around 2 to 3 cm from the extreme right side. My Linux version is 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049979/+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 2046941] [NEW] [24.04]: mpt3sas: Critical Bug Fixes
Public bug reported: This update has been initiated to include a few critical bug fixes from upstream into the upcoming 24.04 kernel. Below are the upstream commit IDs: 3c978492c333 : scsi: mpt3sas: Fix loop logic 0854065092a7 : scsi: mpt3sas: Remove volatile qualifier 4ca10f3e3174 : scsi: mpt3sas: Perform additional retries if doorbell read returns 0 ** Affects: linux (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/2046941 Title: [24.04]: mpt3sas: Critical Bug Fixes Status in linux package in Ubuntu: New Bug description: This update has been initiated to include a few critical bug fixes from upstream into the upcoming 24.04 kernel. Below are the upstream commit IDs: 3c978492c333 : scsi: mpt3sas: Fix loop logic 0854065092a7 : scsi: mpt3sas: Remove volatile qualifier 4ca10f3e3174 : scsi: mpt3sas: Perform additional retries if doorbell read returns 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046941/+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 2046875] [NEW] [22.04.04]: mpt3sas: Critical Bug Fixes
Public bug reported: This update has been initiated to include a few critical bug fixes from upstream into the upcoming 22.04.04 point kernel. Below are the upstream commit IDs: 3c978492c333 : scsi: mpt3sas: Fix loop logic 0854065092a7 : scsi: mpt3sas: Remove volatile qualifier 4ca10f3e3174 : scsi: mpt3sas: Perform additional retries if doorbell read returns 0 ** Affects: linux (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/2046875 Title: [22.04.04]: mpt3sas: Critical Bug Fixes Status in linux package in Ubuntu: New Bug description: This update has been initiated to include a few critical bug fixes from upstream into the upcoming 22.04.04 point kernel. Below are the upstream commit IDs: 3c978492c333 : scsi: mpt3sas: Fix loop logic 0854065092a7 : scsi: mpt3sas: Remove volatile qualifier 4ca10f3e3174 : scsi: mpt3sas: Perform additional retries if doorbell read returns 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046875/+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 2043005] Re: mlxbf-pmc: Fix crspace event offsets
** Tags removed: verification-needed-jammy-linux-bluefield ** Tags added: verification-done-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2043005 Title: mlxbf-pmc: Fix crspace event offsets Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Currently, the offsets calculated for programming crspace type events on BlueField-3 are incorrect and this leads to a mismatch of counter numbers between the driver and actual HW where, for example, event2 in the driver is actually event4 in HW. [Fix] Fix the offset calculation for programming crspace events. [Test Case] On a BlueField-3 platform, program any valid event number to the event sysfs and check that the corresponding counter value increments. [Regression Potential] This is a bug fix and the regression potential can be considered minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2043005/+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 2043005] [NEW] mlxbf-pmc: Fix crspace event offsets
Public bug reported: SRU Justification: [Impact] Currently, the offsets calculated for programming crspace type events on BlueField-3 are incorrect and this leads to a mismatch of counter numbers between the driver and actual HW where, for example, event2 in the driver is actually event4 in HW. [Fix] Fix the offset calculation for programming crspace events. [Test Case] On a BlueField-3 platform, program any valid event number to the event sysfs and check that the corresponding counter value increments. [Regression Potential] This is a bug fix and the regression potential can be considered minimal. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2043005 Title: mlxbf-pmc: Fix crspace event offsets Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Currently, the offsets calculated for programming crspace type events on BlueField-3 are incorrect and this leads to a mismatch of counter numbers between the driver and actual HW where, for example, event2 in the driver is actually event4 in HW. [Fix] Fix the offset calculation for programming crspace events. [Test Case] On a BlueField-3 platform, program any valid event number to the event sysfs and check that the corresponding counter value increments. [Regression Potential] This is a bug fix and the regression potential can be considered minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2043005/+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 2042525] Re: mlxbf-pmc: Support 64-bit counter and counting cycles
** Tags removed: verification-needed-jammy-linux-bluefield ** Tags added: verification-done-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2042525 Title: mlxbf-pmc: Support 64-bit counter and counting cycles Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Currently, there is no method to keep track of the cycle count when an event is being monitored. And since cycle count increments quickly, the 32-bit counter values could wrap around and hence support for 64-bit counters is also needed for the same. [Fix] Expose 2 additional sysfs entries: count_clock and use_odd_counter. These fields are supported in BlueField-3 PMC hardware and each bit in count_clock corresponds to each counter, while each bit in use_odd_counter corresponds to an even counter.Exposing these fields will allow the user to program any counter of choice to monitor the cycle count for the required duration. Similarly, use_odd_counter can be set to couple 2 adjacent odd and even counters to form a 64-bit counter. [Test Case] 1. Verify that count_clock and use_odd_counter sysfs entries are created for each BlueField-3 HW block. These are not supported by BlueField-1 or BlueField-2 HW. 2. Set any bit in count_clock and check if the corresponding counter values increment after enabling. 3. Set any bit in use_odd_counter and check if the cycle count increments on 2 counters with the odd counter being the lower 32 bits and the even counter being the upper 32 bits. [Regression Potential] Can be considered minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2042525/+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 2042527] Re: mlxbf-pmc: add support for clock_measure counters
** Tags removed: verification-needed-jammy-linux-bluefield ** Tags added: verification-done-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2042527 Title: mlxbf-pmc: add support for clock_measure counters Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Currently, the counters under the clock_measure HW block are not supported by the driver and is a new requirement for calculating performance metrics. [Fix] Add support for "clock_measure" block by passing the block info via ACPI. The events monitored by these counters is added to the driver and exposed via a new sysfs sub-directory for this block. [Test Case] Read any of the registers listed under the "clock_measure" sub-directory. These fields are read-only and hence all writes will be blocked by the driver. [Regression Potential] Can be considered minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2042527/+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 2042654] [NEW] package linux-image-5.15.0-84-generic (not installed) failed to install/upgrade: unable to open '/boot/vmlinuz-5.15.0-84-generic.dpkg-new': Operation not permitte
Public bug reported: Not able to install updates of ubuntu system is getting slow ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-84-generic (not installed) ProcVersionSignature: Ubuntu 5.15.0-83.92~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-83-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 3 15:14:34 2023 DpkgHistoryLog: Start-Date: 2023-11-03 15:13:01 Commandline: apt-get install -f Requested-By: admin1 (1000) Install: linux-hwe-5.15-headers-5.15.0-88:amd64 (5.15.0-88.98~20.04.1, automatic), linux-modules-extra-5.15.0-88-generic:amd64 (5.15.0-88.98~20.04.1, automatic), linux-modules-5.15.0-88-generic:amd64 (5.15.0-88.98~20.04.1, automatic), linux-headers-5.15.0-88-generic:amd64 (5.15.0-88.98~20.04.1, automatic), linux-image-5.15.0-84-generic:amd64 (5.15.0-84.93~20.04.1, automatic), linux-image-5.15.0-86-generic:amd64 (5.15.0-86.96~20.04.1, automatic), linux-image-5.15.0-88-generic:amd64 (5.15.0-88.98~20.04.1, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.15.0.86.96~20.04.44, 5.15.0.88.98~20.04.46), linux-image-generic-hwe-20.04:amd64 (5.15.0.86.96~20.04.44, 5.15.0.88.98~20.04.46), linux-generic-hwe-20.04:amd64 (5.15.0.86.96~20.04.44, 5.15.0.88.98~20.04.46) DuplicateSignature: package:linux-image-5.15.0-84-generic:(not installed) Unpacking linux-image-5.15.0-84-generic (5.15.0-84.93~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-2gOGNH/8-linux-image-5.15.0-84-generic_5.15.0-84.93~20.04.1_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-84-generic.dpkg-new': Operation not permitted ErrorMessage: unable to open '/boot/vmlinuz-5.15.0-84-generic.dpkg-new': Operation not permitted InstallationDate: Installed on 2023-09-12 (51 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.4 SourcePackage: linux-signed-hwe-5.15 Title: package linux-image-5.15.0-84-generic (not installed) failed to install/upgrade: unable to open '/boot/vmlinuz-5.15.0-84-generic.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2042654 Title: package linux-image-5.15.0-84-generic (not installed) failed to install/upgrade: unable to open '/boot/vmlinuz-5.15.0-84-generic.dpkg- new': Operation not permitted Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Not able to install updates of ubuntu system is getting slow ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-84-generic (not installed) ProcVersionSignature: Ubuntu 5.15.0-83.92~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-83-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 3 15:14:34 2023 DpkgHistoryLog: Start-Date: 2023-11-03 15:13:01 Commandline: apt-get install -f Requested-By: admin1 (1000) Install: linux-hwe-5.15-headers-5.15.0-88:amd64 (5.15.0-88.98~20.04.1, automatic), linux-modules-extra-5.15.0-88-generic:amd64 (5.15.0-88.98~20.04.1, automatic), linux-modules-5.15.0-88-generic:amd64 (5.15.0-88.98~20.04.1, automatic), linux-headers-5.15.0-88-generic:amd64 (5.15.0-88.98~20.04.1, automatic), linux-image-5.15.0-84-generic:amd64 (5.15.0-84.93~20.04.1, automatic), linux-image-5.15.0-86-generic:amd64 (5.15.0-86.96~20.04.1, automatic), linux-image-5.15.0-88-generic:amd64 (5.15.0-88.98~20.04.1, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.15.0.86.96~20.04.44, 5.15.0.88.98~20.04.46), linux-image-generic-hwe-20.04:amd64 (5.15.0.86.96~20.04.44, 5.15.0.88.98~20.04.46), linux-generic-hwe-20.04:amd64 (5.15.0.86.96~20.04.44, 5.15.0.88.98~20.04.46) DuplicateSignature: package:linux-image-5.15.0-84-generic:(not installed) Unpacking linux-image-5.15.0-84-generic (5.15.0-84.93~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-2gOGNH/8-linux-image-5.15.0-84-generic_5.15.0-84.93~20.04.1_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-84-generic.dpkg-new': Operation not permitted ErrorMessage: unable to open '/boot/vmlinuz-5.15.0-84-generic.dpkg-new': Operation not permitted InstallationDate: Installed on 2023-09-12 (51 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A
[Kernel-packages] [Bug 2042527] [NEW] mlxbf-pmc: add support for clock_measure counters
Public bug reported: SRU Justification: [Impact] Currently, the counters under the clock_measure HW block are not supported by the driver and is a new requirement for calculating performance metrics. [Fix] Add support for "clock_measure" block by passing the block info via ACPI. The events monitored by these counters is added to the driver and exposed via a new sysfs sub-directory for this block. [Test Case] Read any of the registers listed under the "clock_measure" sub-directory. These fields are read-only and hence all writes will be blocked by the driver. [Regression Potential] Can be considered minimal. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2042527 Title: mlxbf-pmc: add support for clock_measure counters Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Currently, the counters under the clock_measure HW block are not supported by the driver and is a new requirement for calculating performance metrics. [Fix] Add support for "clock_measure" block by passing the block info via ACPI. The events monitored by these counters is added to the driver and exposed via a new sysfs sub-directory for this block. [Test Case] Read any of the registers listed under the "clock_measure" sub-directory. These fields are read-only and hence all writes will be blocked by the driver. [Regression Potential] Can be considered minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2042527/+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 2042525] [NEW] mlxbf-pmc: Support 64-bit counter and counting cycles
Public bug reported: SRU Justification: [Impact] Currently, there is no method to keep track of the cycle count when an event is being monitored. And since cycle count increments quickly, the 32-bit counter values could wrap around and hence support for 64-bit counters is also needed for the same. [Fix] Expose 2 additional sysfs entries: count_clock and use_odd_counter. These fields are supported in BlueField-3 PMC hardware and each bit in count_clock corresponds to each counter, while each bit in use_odd_counter corresponds to an even counter.Exposing these fields will allow the user to program any counter of choice to monitor the cycle count for the required duration. Similarly, use_odd_counter can be set to couple 2 adjacent odd and even counters to form a 64-bit counter. [Test Case] 1. Verify that count_clock and use_odd_counter sysfs entries are created for each BlueField-3 HW block. These are not supported by BlueField-1 or BlueField-2 HW. 2. Set any bit in count_clock and check if the corresponding counter values increment after enabling. 3. Set any bit in use_odd_counter and check if the cycle count increments on 2 counters with the odd counter being the lower 32 bits and the even counter being the upper 32 bits. [Regression Potential] Can be considered minimal. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2042525 Title: mlxbf-pmc: Support 64-bit counter and counting cycles Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Currently, there is no method to keep track of the cycle count when an event is being monitored. And since cycle count increments quickly, the 32-bit counter values could wrap around and hence support for 64-bit counters is also needed for the same. [Fix] Expose 2 additional sysfs entries: count_clock and use_odd_counter. These fields are supported in BlueField-3 PMC hardware and each bit in count_clock corresponds to each counter, while each bit in use_odd_counter corresponds to an even counter.Exposing these fields will allow the user to program any counter of choice to monitor the cycle count for the required duration. Similarly, use_odd_counter can be set to couple 2 adjacent odd and even counters to form a 64-bit counter. [Test Case] 1. Verify that count_clock and use_odd_counter sysfs entries are created for each BlueField-3 HW block. These are not supported by BlueField-1 or BlueField-2 HW. 2. Set any bit in count_clock and check if the corresponding counter values increment after enabling. 3. Set any bit in use_odd_counter and check if the cycle count increments on 2 counters with the odd counter being the lower 32 bits and the even counter being the upper 32 bits. [Regression Potential] Can be considered minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2042525/+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 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
or anydesk please ? talking regarding #106 & #108 -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 04/20/2022 dmi.bios.release: 1.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ignis_ADH dmi.board.vendor: ADL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
Giuliano, can you please guide me through teamviewer? That issue is still not getting fixed. -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 04/20/2022 dmi.bios.release: 1.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ignis_ADH dmi.board.vendor: ADL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Thanks Endre for bring up this question. I had upgraded to 23.04 few weeks ago, and when I got to know that 23.10, which is considered as development version as of now and comes with kernel 6.5 and now available in the official site, I got the previous version upgraded to this latest yesterday, and found that keyboard and touchpad issue were not addressed in that kernel yet. Many who are willing to get official update instead of applying patch by themselves, a response on tentative availability of fix through offical distribution will be helful. Regards, -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in linux-hwe-6.2 source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+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 2039561] Re: mlxbf_pmc: Replace sauce patches with upstream commits
** Tags removed: verification-needed-jammy-linux-bluefield ** Tags added: verification-done-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2039561 Title: mlxbf_pmc: Replace sauce patches with upstream commits Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] The mlxbf_pmc BlueField platform driver in the Jammy repo consists of some SAUCE patches. These need to be replaced. [Fix] The fix is to revert the four SAUCE patches, replacing them with upstream commits for the same functionality. 2 patches are from upstream linux, while the 3rd is from linux-next. [Test Case] * Boot BF2/BF3 platform, verify no new errors * Test sysfs interface exposed by driver for programming various counters and events. [Regression Potential] The upstream commits are not exactly the same as the SAUCE patches, so technically there is a chance of regression, but its been well-tested and the functionality is the same. [Other] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2039561/+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 2039561] [NEW] mlxbf_pmc: Replace sauce patches with upstream commits
Public bug reported: SRU Justification: [Impact] The mlxbf_pmc BlueField platform driver in the Jammy repo consists of some SAUCE patches. These need to be replaced. [Fix] The fix is to revert the four SAUCE patches, replacing them with upstream commits for the same functionality. 2 patches are from upstream linux, while the 3rd is from linux-next. [Test Case] * Boot BF2/BF3 platform, verify no new errors * Test sysfs interface exposed by driver for programming various counters and events. [Regression Potential] The upstream commits are not exactly the same as the SAUCE patches, so technically there is a chance of regression, but its been well-tested and the functionality is the same. [Other] n/a ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2039561 Title: mlxbf_pmc: Replace sauce patches with upstream commits Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] The mlxbf_pmc BlueField platform driver in the Jammy repo consists of some SAUCE patches. These need to be replaced. [Fix] The fix is to revert the four SAUCE patches, replacing them with upstream commits for the same functionality. 2 patches are from upstream linux, while the 3rd is from linux-next. [Test Case] * Boot BF2/BF3 platform, verify no new errors * Test sysfs interface exposed by driver for programming various counters and events. [Regression Potential] The upstream commits are not exactly the same as the SAUCE patches, so technically there is a chance of regression, but its been well-tested and the functionality is the same. [Other] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2039561/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Thanks Endre for the update, but that kernel v6.5.x was my hope to get these issues addressed. How long can we just be waiting for without any communication from the kernel development team? One option is just wait for indefinite period of time to hear from them or to take decision to invest once more in another computer which is matter of hefty amount money and making me feel low about these whole experience we are going through. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-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-signed-hwe-6.2/+bug/2034477/+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 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
I verified the issue on kernel linux/5.4.0-166.183, linux/5.15.0-88.98 and linux/6.2.0-36.37 and the issue is fixed. I was able to run enclave in debug mode in all 3 kernels. ** Tags removed: verification-needed-lunar-linux ** Tags added: verification-done-lunar-linux -- 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/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User test results pending, but its a fix commit so should likely be applied regardless. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+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 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-linux -- 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/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User test results pending, but its a fix commit so should likely be applied regardless. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+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 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
** Tags removed: verification-needed-focal-linux ** Tags added: verification-done-focal-linux -- 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/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User test results pending, but its a fix commit so should likely be applied regardless. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Exactly Endre. These are the major problems. Request to kernel team will be to address these three problems on priority. In addition to that there is one more problem that I might not have mentioned earlier and that is the issue related to system Suspend functionality. In my LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop, system does not enter into standby mode when physical power button is pressed even though the button is mapped to suspend mode done through Settings-->Power-->Power Button Behavior. This is inconveinent especially when I wish to talk for a shorter distance with just laptop lid closed, but cannot do because then the system gets unstable. So, only option left to me is to move around by keeping the laptop lid open. So, it should also be checked by others if they are experiencing the same behavior. And if so, then it could also be another concern that the kernel team might be interested to look into. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-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-signed-hwe-6.2/+bug/2034477/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
As Rayen had changed the bug status from "Confirmed" to "Fix Released" by mistake, I just changed it back to the previous one, and hope that kernel team will now pay attention, work and release an appropriate fix for the above mentioned issues at the earliest. ** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-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-signed-hwe-6.2/+bug/2034477/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Hello Endre, I have written email to Rayen to consider this bug status change and requested to let us know about the solution. Regards, Pradip Kumar Das -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Fix Released Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-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-signed-hwe-6.2/+bug/2034477/+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 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
make: Entering directory '/usr/src/linux-headers-6.2.0-33-generic' warning: the compiler differs from the one used to build the kernel The kernel was built by: x86_64-linux-gnu-gcc-11 (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0 You are using: gcc-11 (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0 scripts/Makefile.build:41: /home/souvik/Makefile: No such file or directory make[1]: *** No rule to make target '/home/souvik/Makefile'. Stop. make: *** [Makefile:2026: /home/souvik] Error 2 make: Leaving directory '/usr/src/linux-headers-6.2.0-33-generic' cp: cannot stat 'uvcvideo.ko': No such file or directory This error while running your script @giuliano69 -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware
[Kernel-packages] [Bug 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
I tested the changes today and was able to successfully run enclave in debug mode. Thanks a lot Tim. -- 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/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: In Progress Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User test results pending, but its a fix commit so should likely be applied regardless. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+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 2034477] [NEW] Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Public bug reported: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-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-signed-hwe-6.2/+bug/2034477/+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 2023496] [NEW] package linux-modules-nvidia-510-5.15.0-73-generic 5.15.0-73.80~20.04.1 failed to install/upgrade: installed linux-modules-nvidia-510-5.15.0-73-generic package po
Public bug reported: fix pls ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-modules-nvidia-510-5.15.0-73-generic 5.15.0-73.80~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-73.80~20.04.1-generic 5.15.98 Uname: Linux 5.15.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.2 AptOrdering: libmozjs-102-0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Jun 11 13:06:33 2023 ErrorMessage: installed linux-modules-nvidia-510-5.15.0-73-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-17 (206 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: linux-restricted-modules-hwe-5.15 Title: package linux-modules-nvidia-510-5.15.0-73-generic 5.15.0-73.80~20.04.1 failed to install/upgrade: installed linux-modules-nvidia-510-5.15.0-73-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to kinetic on 2023-06-01 (10 days ago) ** Affects: linux-restricted-modules-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2023496 Title: package linux-modules-nvidia-510-5.15.0-73-generic 5.15.0-73.80~20.04.1 failed to install/upgrade: installed linux- modules-nvidia-510-5.15.0-73-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules-hwe-5.15 package in Ubuntu: New Bug description: fix pls ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-modules-nvidia-510-5.15.0-73-generic 5.15.0-73.80~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-73.80~20.04.1-generic 5.15.98 Uname: Linux 5.15.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.2 AptOrdering: libmozjs-102-0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Jun 11 13:06:33 2023 ErrorMessage: installed linux-modules-nvidia-510-5.15.0-73-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-17 (206 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: linux-restricted-modules-hwe-5.15 Title: package linux-modules-nvidia-510-5.15.0-73-generic 5.15.0-73.80~20.04.1 failed to install/upgrade: installed linux-modules-nvidia-510-5.15.0-73-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to kinetic on 2023-06-01 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.15/+bug/2023496/+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 2023490] [NEW] package linux-modules-nvidia-510-5.15.0-72-generic 5.15.0-72.79~20.04.1 failed to install/upgrade: installed linux-modules-nvidia-510-5.15.0-72-generic package po
Public bug reported: Please fix this issue. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-modules-nvidia-510-5.15.0-72-generic 5.15.0-72.79~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-73.80~20.04.1-generic 5.15.98 Uname: Linux 5.15.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.2 AptOrdering: libmozjs-102-0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Jun 11 13:06:36 2023 ErrorMessage: installed linux-modules-nvidia-510-5.15.0-72-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-17 (206 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: linux-restricted-modules-hwe-5.15 Title: package linux-modules-nvidia-510-5.15.0-72-generic 5.15.0-72.79~20.04.1 failed to install/upgrade: installed linux-modules-nvidia-510-5.15.0-72-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to kinetic on 2023-06-01 (9 days ago) ** Affects: linux-restricted-modules-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2023490 Title: package linux-modules-nvidia-510-5.15.0-72-generic 5.15.0-72.79~20.04.1 failed to install/upgrade: installed linux- modules-nvidia-510-5.15.0-72-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules-hwe-5.15 package in Ubuntu: New Bug description: Please fix this issue. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-modules-nvidia-510-5.15.0-72-generic 5.15.0-72.79~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-73.80~20.04.1-generic 5.15.98 Uname: Linux 5.15.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.2 AptOrdering: libmozjs-102-0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Jun 11 13:06:36 2023 ErrorMessage: installed linux-modules-nvidia-510-5.15.0-72-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-17 (206 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: linux-restricted-modules-hwe-5.15 Title: package linux-modules-nvidia-510-5.15.0-72-generic 5.15.0-72.79~20.04.1 failed to install/upgrade: installed linux-modules-nvidia-510-5.15.0-72-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to kinetic on 2023-06-01 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.15/+bug/2023490/+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 2023185] [NEW] iostat -x doesn't give any Device utilization values for Kioxia CM7 drive while running IO
Private bug reported: Steps to Repro : 1. Configure a Poweredge system with Kioxia CM7 U.2 drive connected 2. Boot to Ubuntu 22.04.2 and verify the drives are discovered successfully. 3. Run IO to the CM7 U.2 drives. 4. Verify the device utilization using "iostat -x 1 -m /dev/nvme0n1" command Expected Result: IOSTAT should give non-zero values for Device utilization on CM7 U.2 drives. Actual Result: IOSTAT does not give any values for Device utilization on CM7 U.2 drives ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "sosreport" https://bugs.launchpad.net/bugs/2023185/+attachment/5678452/+files/sosreport-linux-ubuntuIOstat-2023-06-07-xflntiy.tar.xz ** Information type changed from Public to Private -- 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/2023185 Title: iostat -x doesn't give any Device utilization values for Kioxia CM7 drive while running IO Status in linux package in Ubuntu: New Bug description: Steps to Repro : 1. Configure a Poweredge system with Kioxia CM7 U.2 drive connected 2. Boot to Ubuntu 22.04.2 and verify the drives are discovered successfully. 3. Run IO to the CM7 U.2 drives. 4. Verify the device utilization using "iostat -x 1 -m /dev/nvme0n1" command Expected Result: IOSTAT should give non-zero values for Device utilization on CM7 U.2 drives. Actual Result: IOSTAT does not give any values for Device utilization on CM7 U.2 drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023185/+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 2017845] [NEW] package linux-modules-nvidia-510-5.15.0-71-generic 5.15.0-71.78~20.04.1 failed to install/upgrade: installed linux-modules-nvidia-510-5.15.0-71-generic package po
Public bug reported: ubuntu update failed. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-modules-nvidia-510-5.15.0-71-generic 5.15.0-71.78~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 27 00:38:21 2023 ErrorMessage: installed linux-modules-nvidia-510-5.15.0-71-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-17 (160 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.10, Python 3.10.11, python3-minimal, 3.10.6-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: linux-restricted-modules-hwe-5.15 Title: package linux-modules-nvidia-510-5.15.0-71-generic 5.15.0-71.78~20.04.1 failed to install/upgrade: installed linux-modules-nvidia-510-5.15.0-71-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to kinetic on 2023-04-20 (6 days ago) ** Affects: linux-restricted-modules-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2017845 Title: package linux-modules-nvidia-510-5.15.0-71-generic 5.15.0-71.78~20.04.1 failed to install/upgrade: installed linux- modules-nvidia-510-5.15.0-71-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules-hwe-5.15 package in Ubuntu: New Bug description: ubuntu update failed. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-modules-nvidia-510-5.15.0-71-generic 5.15.0-71.78~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 27 00:38:21 2023 ErrorMessage: installed linux-modules-nvidia-510-5.15.0-71-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-17 (160 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.10, Python 3.10.11, python3-minimal, 3.10.6-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: linux-restricted-modules-hwe-5.15 Title: package linux-modules-nvidia-510-5.15.0-71-generic 5.15.0-71.78~20.04.1 failed to install/upgrade: installed linux-modules-nvidia-510-5.15.0-71-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to kinetic on 2023-04-20 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.15/+bug/2017845/+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 2008774] Re: Ubuntu 22.04 not waking up after second suspend
I was having this exact same problem on my HP Pavilion 14 on Ubuntu 22.04. It worked fine a few days ago but I encountered this problem after an update. Lots of stack answers pointed to some problems with Nvidia drivers, but I don't have Nvidia graphics. I have an integrated AMD Radeon along with AMD Ryzen 7. What worked for me: Installing `amdgpu-install` and installing the AMD graphic cards components[1] after checking the secure boot support[2]: ``` amdgpu-install --usecase=graphics ``` [1]https://amdgpu-install.readthedocs.io/en/latest/install-overview.html [2]https://amdgpu-install.readthedocs.io/en/latest/install-installing.html#ubuntu-and-debian-based-systems -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2008774 Title: Ubuntu 22.04 not waking up after second suspend Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After the first suspend it wakes up just fine - it's the second suspend after which the screen stays blank and keyboard doesn't react (although the power LED starts glowing). It happens if I close the laptop's lid or do a manual suspend via the system menu. It happens only recently (I think after some kernel update, but I'm not sure about this) - before it worked fine for month (since I installed Ubuntu). I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the only OS (if that's important). What I tried: * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896) * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896) * I looked through the logs in /var/log but couldn't find anything obvious to me (but I'm not a Linux guru). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 28 11:02:36 2023 InstallationDate: Installed on 2022-06-14 (258 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) 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-signed-hwe-5.19/+bug/2008774/+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 2012709] Re: Ubuntu 22.04 freeze after suspend
This might help: https://bugs.launchpad.net/ubuntu/+source/linux-signed- hwe-5.19/+bug/2008774/comments/8 -- 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/2012709 Title: Ubuntu 22.04 freeze after suspend Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 on Medion Laptop. After resuming from suspend, the screen comes back as expected. The system is working for a couple of seconds then hangs/freeze and power off/power on is the only solution. The suspend was working perfectly for a long time, I start having problem (black screen after suspend) a while ago after an update. After one of the last update, screen came back as expected but freeze after a couple of seconds. According to my observation; it was working nicely since 22.04 installation but one of the update (I can't say which one) introduce the problem. This is a consistent problem; it happens every time suspend is used.. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.16 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 CrashDB: ubuntu CrashReports: 600:118:123:37:2023-03-22 07:37:27.990280875 +0100:2023-02-28 12:30:43.163165609 +0100:/var/crash/_opt_brave.com_brave_brave.1000.uploaded 640:1000:123:1967:2023-03-21 13:41:20.637726068 +0100:2023-03-21 13:42:00.146364173 +0100:/var/crash/_usr_bin_shotwell.1000.crash 664:1000:123:0:2023-03-22 07:37:21.647311793 +0100:2023-03-22 07:37:21.647311793 +0100:/var/crash/_opt_brave.com_brave_brave.1000.upload 640:1000:123:79817122:2023-03-22 07:37:20.643309831 +0100:2023-03-22 07:37:21.643309831 +0100:/var/crash/_opt_brave.com_brave_brave.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Mar 24 10:09:53 2023 InstallationDate: Installed on 2021-08-01 (599 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to jammy on 2022-05-08 (319 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012709/+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 2004235] Re: mlxbf-pmc counters not functional for llt_miss block
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2004235 Title: mlxbf-pmc counters not functional for llt_miss block Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Currently, the driver uses fixed offsets for the control and data registers in the performance counter module. However, this is not correct since the module is not uniform in all HW blocks, and in this case, the llt_miss block is different from the rest. [Fix] The number of counters present in each block is not fixed, and hence the offsets for the control and data registers should also be calculated accordingly. [Test Case] Without the fix, writing 1 to the llt_miss "enable" file will not result in any of the counters incrementing. With the fix, the counters should increment even with the default event settings. [Regression Potential] Can be considered minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2004235/+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 2002501] Re: mlxbf-pmc support for BlueField-3
** 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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2002501 Title: mlxbf-pmc support for BlueField-3 Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Currently, the mlxbf-pmc driver supports only BlueField-1 and BlueField-2 devices. BlueField-3 is not supported. [Fix] Add support for BlueField-3 devices by adding new access mechanism for programming and reading counter values as in the new design, along with the list of supported events in each HW block in BlueField-3. [Test Case] Previously, the driver would not be loaded when the OS is loaded on a BlueField-3 card. With the fix, the driver should get loaded and create sysfs entries as a hwmon device under /sys/class/hwmon/hwmon0. [Regression Potential] The ACPI table needs to be in sync with this change since it depends on newly introduces parameters such as mss_enable and llt_enable, which were not present earlier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2002501/+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 2004235] Re: mlxbf-pmc counters not functional for llt_miss block
** 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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2004235 Title: mlxbf-pmc counters not functional for llt_miss block Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Currently, the driver uses fixed offsets for the control and data registers in the performance counter module. However, this is not correct since the module is not uniform in all HW blocks, and in this case, the llt_miss block is different from the rest. [Fix] The number of counters present in each block is not fixed, and hence the offsets for the control and data registers should also be calculated accordingly. [Test Case] Without the fix, writing 1 to the llt_miss "enable" file will not result in any of the counters incrementing. With the fix, the counters should increment even with the default event settings. [Regression Potential] Can be considered minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2004235/+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 2004234] [NEW] mlxbf-pmc counters not functional for llt_miss block
Public bug reported: SRU Justification: [Impact] Currently, the driver uses fixed offsets for the control and data registers in the performance counter module. However, this is not correct since the module is not uniform in all HW blocks, and in this case, the llt_miss block is different from the rest. [Fix] The number of counters present in each block is not fixed, and hence the offsets for the control and data registers should also be calculated accordingly. [Test Case] Without the fix, writing 1 to the llt_miss "enable" file will not result in any of the counters incrementing. With the fix, the counters should increment even with the default event settings. [Regression Potential] Can be considered minimal. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2004234 Title: mlxbf-pmc counters not functional for llt_miss block Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Currently, the driver uses fixed offsets for the control and data registers in the performance counter module. However, this is not correct since the module is not uniform in all HW blocks, and in this case, the llt_miss block is different from the rest. [Fix] The number of counters present in each block is not fixed, and hence the offsets for the control and data registers should also be calculated accordingly. [Test Case] Without the fix, writing 1 to the llt_miss "enable" file will not result in any of the counters incrementing. With the fix, the counters should increment even with the default event settings. [Regression Potential] Can be considered minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2004234/+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 2004235] [NEW] mlxbf-pmc counters not functional for llt_miss block
Public bug reported: SRU Justification: [Impact] Currently, the driver uses fixed offsets for the control and data registers in the performance counter module. However, this is not correct since the module is not uniform in all HW blocks, and in this case, the llt_miss block is different from the rest. [Fix] The number of counters present in each block is not fixed, and hence the offsets for the control and data registers should also be calculated accordingly. [Test Case] Without the fix, writing 1 to the llt_miss "enable" file will not result in any of the counters incrementing. With the fix, the counters should increment even with the default event settings. [Regression Potential] Can be considered minimal. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2004235 Title: mlxbf-pmc counters not functional for llt_miss block Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Currently, the driver uses fixed offsets for the control and data registers in the performance counter module. However, this is not correct since the module is not uniform in all HW blocks, and in this case, the llt_miss block is different from the rest. [Fix] The number of counters present in each block is not fixed, and hence the offsets for the control and data registers should also be calculated accordingly. [Test Case] Without the fix, writing 1 to the llt_miss "enable" file will not result in any of the counters incrementing. With the fix, the counters should increment even with the default event settings. [Regression Potential] Can be considered minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2004235/+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 1984011] Re: [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal
All verifications have been completed w.r.t this bug. Is any action needed here? Please advise. Thanks, Karan -- 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/1984011 Title: [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: [Impact] fNIC driver controls print messages based on the flag fnic_log_level. shost_printk is not controlled via this flag. This issue is resolved by using some of the print macros that have been defined in fnic. This has negligible impact. The resid was being set irrespective of whether we saw an underflow or not. It needs to be set only when we see an underflow. The impact here is negligible. When we don't receive link events, we could go into a loop before sending fw reset. The patch for the issue resolves this, and we break out of the loop. Prior to checking the remote port, fnic driver must check if the io_req is valid. If not, there could be a crash. The patch resolves this issue. [Fix] The following patches need to be pulled from upstream to update the fnic driver to 1.6.0.53: https://marc.info/?l=linux-scsi=160591061813369=2 https://marc.info/?l=linux-scsi=160592183315837=2 https://marc.info/?l=linux-scsi=160592283315997=2 https://marc.info/?l=linux-scsi=160592363016122=2 https://marc.info/?l=linux-scsi=160592616516616=2 Here's a description of each issue: 1. https://marc.info/?l=linux-scsi=160591061813369=2 FNIC_FCS_DBG print is controlled by fnic_log_level flag. Replace shost_printk in fnic_fip_handler_timer with this print so that it can be controlled. 2. https://marc.info/?l=linux-scsi=160592183315837=2 When fnic is in TRANS ETH state, and when there are no link events, we must not loop before sending fw reset. 3. https://marc.info/?l=linux-scsi=160592283315997=2 FNIC_MAIN_DBG print is controlled by fnic_log_level flag. Replace shost_printk in fnic_handle_link with this print so that it can be controlled. 4. https://marc.info/?l=linux-scsi=160592363016122=2 Fix to set scsi_set_resid() only if FCPIO_ICMND_CMPL_RESID_UNDER is set. 5. https://marc.info/?l=linux-scsi=160592616516616=2 Check for a valid io_req before we check other data. [Test Plan] Runnings IOs with multiple link flaps would be a good test case to validate all the patches above. It is suggested to run these IOs with a data integrity check. We do this as a standard practice. [Where problems could occur] The print messages are innocuous. It is not expected to run into any issues. Problems could occur with storage arrays that have a non-standard response. If the sanity test fails, there could be issues in the scsi midlayer or fnic driver. All the patches present low regression risk. [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/fnic_cisco_ver3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984011/+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 2002500] [NEW] mlxbf-pmc support for BlueField-3
Public bug reported: SRU Justification: [Impact] Currently, the mlxbf-pmc driver supports only BlueField-1 and BlueField-2 devices. BlueField-3 is not supported. [Fix] Add support for BlueField-3 devices by adding new access mechanism for programming and reading counter values as in the new design, along with the list of supported events in each HW block in BlueField-3. [Test Case] Previously, the driver would not be loaded when the OS is loaded on a BlueField-3 card. With the fix, the driver should get loaded and create sysfs entries as a hwmon device under /sys/class/hwmon/hwmon0. [Regression Potential] The ACPI table needs to be in sync with this change since it depends on newly introduces parameters such as mss_enable and llt_enable, which were not present earlier. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2002500 Title: mlxbf-pmc support for BlueField-3 Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Currently, the mlxbf-pmc driver supports only BlueField-1 and BlueField-2 devices. BlueField-3 is not supported. [Fix] Add support for BlueField-3 devices by adding new access mechanism for programming and reading counter values as in the new design, along with the list of supported events in each HW block in BlueField-3. [Test Case] Previously, the driver would not be loaded when the OS is loaded on a BlueField-3 card. With the fix, the driver should get loaded and create sysfs entries as a hwmon device under /sys/class/hwmon/hwmon0. [Regression Potential] The ACPI table needs to be in sync with this change since it depends on newly introduces parameters such as mss_enable and llt_enable, which were not present earlier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2002500/+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 2002501] [NEW] mlxbf-pmc support for BlueField-3
Public bug reported: SRU Justification: [Impact] Currently, the mlxbf-pmc driver supports only BlueField-1 and BlueField-2 devices. BlueField-3 is not supported. [Fix] Add support for BlueField-3 devices by adding new access mechanism for programming and reading counter values as in the new design, along with the list of supported events in each HW block in BlueField-3. [Test Case] Previously, the driver would not be loaded when the OS is loaded on a BlueField-3 card. With the fix, the driver should get loaded and create sysfs entries as a hwmon device under /sys/class/hwmon/hwmon0. [Regression Potential] The ACPI table needs to be in sync with this change since it depends on newly introduces parameters such as mss_enable and llt_enable, which were not present earlier. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2002501 Title: mlxbf-pmc support for BlueField-3 Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Currently, the mlxbf-pmc driver supports only BlueField-1 and BlueField-2 devices. BlueField-3 is not supported. [Fix] Add support for BlueField-3 devices by adding new access mechanism for programming and reading counter values as in the new design, along with the list of supported events in each HW block in BlueField-3. [Test Case] Previously, the driver would not be loaded when the OS is loaded on a BlueField-3 card. With the fix, the driver should get loaded and create sysfs entries as a hwmon device under /sys/class/hwmon/hwmon0. [Regression Potential] The ACPI table needs to be in sync with this change since it depends on newly introduces parameters such as mss_enable and llt_enable, which were not present earlier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2002501/+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 1989172] Re: mlxbf-pmc: error when reading unprogrammed events
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1989172 Title: mlxbf-pmc: error when reading unprogrammed events Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Released Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] When the counters are not programmed to monitor any events, reading the "event" file results in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argument This is misleading and instead needs to indicate that the counter is currently not enabled. [Fix] * First, skip the check for whether the counter is enabled when reading the event info. If the counter is not enabled, it should return 0, which is the default value when coming out of reset. * 0 is not a valid event in most blocks as per the respective event lists, so add a "Disable" event to all the event lists. [Test Case] Without the fix, reading any "event" file right after reset when the counters are not programmed should result in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argumen With the fix, it should instead print: 0x0: DISABLE [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989172/+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 1995109] Re: bluefield-edac: Potentially overflowing expression
** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1995109 Title: bluefield-edac: Potentially overflowing expression Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Potential integer overflow in men_ctrl_idx detected by static tool analyser. [Fix] Declare as type u64 instead of type int [Test Case] NA since the variable is read from the ACPI table [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1995109/+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 1998708] [NEW] Touch pad is stop working suddnly, but wired mouse is working
Public bug reported: Touch pad is stop working suddnly, but wired mouse is working. My laptop is Model is Lenovo thinkpad edge e431. Please help me to fix it. ** Affects: linux (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/1998708 Title: Touch pad is stop working suddnly, but wired mouse is working Status in linux package in Ubuntu: New Bug description: Touch pad is stop working suddnly, but wired mouse is working. My laptop is Model is Lenovo thinkpad edge e431. Please help me to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998708/+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 1995109] [NEW] bluefield-edac: Potentially overflowing expression
Public bug reported: SRU Justification: [Impact] Potential integer overflow in men_ctrl_idx detected by static tool analyser. [Fix] Declare as type u64 instead of type int [Test Case] NA since the variable is read from the ACPI table [Regression Potential] Can be considered minimal ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1995109 Title: bluefield-edac: Potentially overflowing expression Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Potential integer overflow in men_ctrl_idx detected by static tool analyser. [Fix] Declare as type u64 instead of type int [Test Case] NA since the variable is read from the ACPI table [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1995109/+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 1991934] Re: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied error pipewire on Ubuntu kinetic
** Attachment added: "Screenshot from 2022-10-04 12-16-23.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991934/+attachment/5621897/+files/Screenshot%20from%202022-10-04%2012-16-23.png -- 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/1991934 Title: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied error pipewire on Ubuntu kinetic Status in linux package in Ubuntu: Incomplete Bug description: Started PipeWire Multimedia Service. mod.rt: Can't find xdg-portal: (null) mod.rt: found session bus but no portal mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied mod.rt: could not make thread 4909 realtime using RTKit: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991934/+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 1991936] [NEW] No AAC codec for Pipewire on Ubuntu Kinetic
Public bug reported: The AAC codec is not showing up in the sound settings when a device that is capable of that codec is connected, but other supported codecs do work.Tested using the Sony WH1000XM4 and other bluetooth devices that support the codec. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - No AAC codec for Pipewie on Ubuntu Kinetic + No AAC codec for Pipewire on Ubuntu Kinetic ** Description changed: The AAC codec is not showing up in the sound settings when a device that is capable of that codec is connected, but other supported codecs do work.Tested using the Sony WH1000XM4 and other bluetooth devices that - support that codec. + support the codec. -- 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/1991936 Title: No AAC codec for Pipewire on Ubuntu Kinetic Status in linux package in Ubuntu: New Bug description: The AAC codec is not showing up in the sound settings when a device that is capable of that codec is connected, but other supported codecs do work.Tested using the Sony WH1000XM4 and other bluetooth devices that support the codec. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991936/+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 1991934] [NEW] mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied error pipewire on Ubuntu kinetic
Public bug reported: Started PipeWire Multimedia Service. mod.rt: Can't find xdg-portal: (null) mod.rt: found session bus but no portal mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied mod.rt: could not make thread 4909 realtime using RTKit: Permission denied ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1991934 Title: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied error pipewire on Ubuntu kinetic Status in linux package in Ubuntu: Incomplete Bug description: Started PipeWire Multimedia Service. mod.rt: Can't find xdg-portal: (null) mod.rt: found session bus but no portal mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied mod.rt: could not make thread 4909 realtime using RTKit: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991934/+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 1989172] Re: mlxbf-pmc: error when reading unprogrammed events
** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1989172 Title: mlxbf-pmc: error when reading unprogrammed events Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] When the counters are not programmed to monitor any events, reading the "event" file results in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argument This is misleading and instead needs to indicate that the counter is currently not enabled. [Fix] * First, skip the check for whether the counter is enabled when reading the event info. If the counter is not enabled, it should return 0, which is the default value when coming out of reset. * 0 is not a valid event in most blocks as per the respective event lists, so add a "Disable" event to all the event lists. [Test Case] Without the fix, reading any "event" file right after reset when the counters are not programmed should result in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argumen With the fix, it should instead print: 0x0: DISABLE [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989172/+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 1989172] Re: mlxbf-pmc: error when reading unprogrammed events
** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1989172 Title: mlxbf-pmc: error when reading unprogrammed events Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] When the counters are not programmed to monitor any events, reading the "event" file results in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argument This is misleading and instead needs to indicate that the counter is currently not enabled. [Fix] * First, skip the check for whether the counter is enabled when reading the event info. If the counter is not enabled, it should return 0, which is the default value when coming out of reset. * 0 is not a valid event in most blocks as per the respective event lists, so add a "Disable" event to all the event lists. [Test Case] Without the fix, reading any "event" file right after reset when the counters are not programmed should result in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argumen With the fix, it should instead print: 0x0: DISABLE [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989172/+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 1989172] [NEW] mlxbf-pmc: error when reading unprogrammed events
Public bug reported: SRU Justification: [Impact] When the counters are not programmed to monitor any events, reading the "event" file results in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argument This is misleading and instead needs to indicate that the counter is currently not enabled. [Fix] * First, skip the check for whether the counter is enabled when reading the event info. If the counter is not enabled, it should return 0, which is the default value when coming out of reset. * 0 is not a valid event in most blocks as per the respective event lists, so add a "Disable" event to all the event lists. [Test Case] Without the fix, reading any "event" file right after reset when the counters are not programmed should result in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argumen With the fix, it should instead print: 0x0: DISABLE [Regression Potential] Can be considered minimal ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1989172 Title: mlxbf-pmc: error when reading unprogrammed events Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] When the counters are not programmed to monitor any events, reading the "event" file results in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argument This is misleading and instead needs to indicate that the counter is currently not enabled. [Fix] * First, skip the check for whether the counter is enabled when reading the event info. If the counter is not enabled, it should return 0, which is the default value when coming out of reset. * 0 is not a valid event in most blocks as per the respective event lists, so add a "Disable" event to all the event lists. [Test Case] Without the fix, reading any "event" file right after reset when the counters are not programmed should result in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argumen With the fix, it should instead print: 0x0: DISABLE [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989172/+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 1979045] Re: misleading error prints from mlx-trio
** 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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1979045 Title: misleading error prints from mlx-trio Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] TRIO IRQs are triggered during normal operation and non-error events such as mlxfwreset and the prints from the handler are misleading to users in such instances. [Fix] Replace the dev_err calls with pr_debug. This will ensure that users do not see extraneous error messages from the driver. [Test Case] Running mlxfwreset with the trio driver loaded will see a lot of error prints and this patch will fix the same. [Regression Potential] Can be considered minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1979045/+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 1979264] Re: mlx-trio module license update
** 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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1979264 Title: mlx-trio module license update Status in linux-bluefield package in Ubuntu: Fix Committed Bug description: SRU Justification: [Impact] mlx-trio module license info is currently only GPL and needs to be updated similar to other Mellanox platform drivers [Fix] Change module license from GPL to Dual BSD/GPL [Test Case] modinfo prints the updated license info [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1979264/+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 1443924] Re: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue:Warning - Queue 0 failed to flush
here you can check many post and all the posts are really good you may check https://apkshala.com/ -- 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/1443924 Title: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue:Warning - Queue 0 failed to flush Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: Philips i386 PC with rt2x00 pci is suffering loss of WiFi connectivity after installing 15.04 Beta. The system did work correctly with older Ubuntu versions (like 12.04) and had this problem show up after upgrading to Trusty (as I already reported in bug #1318837). Using Trusty the problem went away when switching from the stock 3.13.0-XX-generic kernel to builds of newer kernels (like 3.14.1-031401). Now the same problem shows up again after installing Vivid Beta. It seems to be the same problem reported for other Ubuntu releases (see bugs #1318837 and #1383555) and also the same problem of this upstream kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=61621 Someone on kernel's bug mentions turning off MSI interrupts and I can confirm it did change the situation: - normally the system looses WiFi connectivity mere seconds after boot (eg. can't ping anything after boot) - if I boot with "pci=nomsi" the system will remain connected to the WiFi for a much longer period (eg. I am able to apt-get install something after boot) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-extra-3.19.0-13-generic 3.19.0-13.13 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic i686 ApportVersion: 2.17-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luca 1997 F pulseaudio CurrentDesktop: LXDE Date: Tue Apr 14 14:19:19 2015 HibernationDevice: RESUME=UUID=cbd1e136-ffc4-48b9-b2aa-c15264b9b132 MachineType: Freeline Freeline Series ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-13-generic root=UUID=6110f881-b32b-426d-910a-c63b355c179c ro quiet splash vt.handoff=7 pci=nomsi RelatedPackageVersions: linux-restricted-modules-3.19.0-13-generic N/A linux-backports-modules-3.19.0-13-generic N/A linux-firmware 1.143 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2004 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: Freeline Series dmi.board.vendor: Freeline dmi.board.version: Ver1.0 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/29/2004:svnFreeline:pnFreelineSeries:pvrVer1.0:rvnFreeline:rnFreelineSeries:rvrVer1.0:cvn:ct3:cvr: dmi.product.name: Freeline Series dmi.product.version: Ver1.0 dmi.sys.vendor: Freeline To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1443924/+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 1443924] Re: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue:Warning - Queue 0 failed to flush
You can put up many efforts to get success in the link building, the comment one is the more effective way like https://lottery-sambad.xyz/ the blog pages and if you are talking about the post then you may also visit https://lottery-sambad.xyz/kerala-lottery-result/ to live updates. -- 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/1443924 Title: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue:Warning - Queue 0 failed to flush Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: Philips i386 PC with rt2x00 pci is suffering loss of WiFi connectivity after installing 15.04 Beta. The system did work correctly with older Ubuntu versions (like 12.04) and had this problem show up after upgrading to Trusty (as I already reported in bug #1318837). Using Trusty the problem went away when switching from the stock 3.13.0-XX-generic kernel to builds of newer kernels (like 3.14.1-031401). Now the same problem shows up again after installing Vivid Beta. It seems to be the same problem reported for other Ubuntu releases (see bugs #1318837 and #1383555) and also the same problem of this upstream kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=61621 Someone on kernel's bug mentions turning off MSI interrupts and I can confirm it did change the situation: - normally the system looses WiFi connectivity mere seconds after boot (eg. can't ping anything after boot) - if I boot with "pci=nomsi" the system will remain connected to the WiFi for a much longer period (eg. I am able to apt-get install something after boot) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-extra-3.19.0-13-generic 3.19.0-13.13 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic i686 ApportVersion: 2.17-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luca 1997 F pulseaudio CurrentDesktop: LXDE Date: Tue Apr 14 14:19:19 2015 HibernationDevice: RESUME=UUID=cbd1e136-ffc4-48b9-b2aa-c15264b9b132 MachineType: Freeline Freeline Series ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-13-generic root=UUID=6110f881-b32b-426d-910a-c63b355c179c ro quiet splash vt.handoff=7 pci=nomsi RelatedPackageVersions: linux-restricted-modules-3.19.0-13-generic N/A linux-backports-modules-3.19.0-13-generic N/A linux-firmware 1.143 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2004 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: Freeline Series dmi.board.vendor: Freeline dmi.board.version: Ver1.0 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/29/2004:svnFreeline:pnFreelineSeries:pvrVer1.0:rvnFreeline:rnFreelineSeries:rvrVer1.0:cvn:ct3:cvr: dmi.product.name: Freeline Series dmi.product.version: Ver1.0 dmi.sys.vendor: Freeline To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1443924/+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 1953554] Re: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out
Even I am also getting the same error log [ 834.879658] [ cut here ] [ 834.884279] NETDEV WATCHDOG: enx00249b305673 (ax88179_178a): transmit queue 0 timed out [ 834.892287] WARNING: CPU: 5 PID: 0 at net/sched/sch_generic.c:529 dev_watchdog+0x1fb/0x210 [ 834.900550] Modules linked in: aquantia snd_hda_codec_realtek snd_hda_codec_generic intel_rapl_msr ledtrig_audio intel_rapl_common snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_hwdep snd_pcm edac_mce_amd snd_seq_midi snd_seq_midi_event kvm_amd binfmt_misc kvm snd_rawmidi crct10dif_pclmul ghash_clmulni_intel nls_iso8859_1 aesni_intel snd_seq crypto_simd snd_rn_pci_acp3x snd_seq_device cryptd snd_timer snd_acp_config rapl wmi_bmof snd efi_pstore snd_soc_acpi joydev input_leds k10temp soundcore snd_pci_acp3x ccp ucsi_ccg typec_ucsi typec mac_hid acpi_tad hid_sensor_magn_3d hid_sensor_gyro_3d hid_sensor_accel_3d hid_sensor_trigger industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common industrialio sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4 usbhid ax88179_178a usbnet mii hid_sensor_hub hid_generic amd_sfh crc32_pclmul thunderbolt xhci_pci i2c_piix4 amd_xgbe hid xhci_pci_renesas nvme [ 834.900705] nvme_core wmi video spi_amd [ 834.991252] CPU: 5 PID: 0 Comm: swapper/5 Tainted: GW 5.18.0-4430-amd+ #4430 [ 834.999683] Hardware name: AMD Lilac-RMB/Lilac-RMB, BIOS TFX1001B 07/05/2022 [ 835.006724] RIP: 0010:dev_watchdog+0x1fb/0x210 [ 835.011170] Code: 00 e9 40 ff ff ff 4c 89 e7 c6 05 72 38 0a 01 01 e8 6a 79 f9 ff 44 89 f1 4c 89 e6 48 c7 c7 30 d8 69 8a 48 89 c2 e8 dd 68 18 00 <0f> 0b e9 22 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 0f [ 835.029917] RSP: 0018:b0d80031ce70 EFLAGS: 00010282 [ 835.035142] RAX: RBX: 8e714edf44c8 RCX: [ 835.042272] RDX: 0103 RSI: 8a5bc601 RDI: [ 835.049403] RBP: b0d80031ce90 R08: R09: dfff [ 835.056531] R10: b0d80031cc60 R11: 8a955d68 R12: 8e714edf4000 [ 835.063658] R13: 8e714edf441c R14: R15: 8e789df60c80 [ 835.070787] FS: () GS:8e789df4() knlGS: [ 835.078870] CS: 0010 DS: ES: CR0: 80050033 [ 835.084612] CR2: 7fe8541665b0 CR3: 00055a61 CR4: 00750ee0 [ 835.091740] PKRU: 5554 [ 835.094449] Call Trace: [ 835.096899] [ 835.098913] ? pfifo_fast_reset+0x130/0x130 [ 835.103098] call_timer_fn+0x2c/0x130 [ 835.106764] ? pfifo_fast_reset+0x130/0x130 [ 835.110946] __run_timers.part.0+0x1cf/0x270 [ 835.115216] ? recalibrate_cpu_khz+0x10/0x10 [ 835.119485] ? ktime_get+0x3e/0xa0 [ 835.122886] ? native_x2apic_icr_read+0x20/0x20 [ 835.127420] ? lapic_next_event+0x20/0x30 [ 835.131432] run_timer_softirq+0x35/0x70 [ 835.135356] __do_softirq+0xee/0x2eb [ 835.138934] __irq_exit_rcu+0xbd/0x110 [ 835.142684] irq_exit_rcu+0xe/0x10 [ 835.146086] sysvec_apic_timer_interrupt+0xac/0xd0 [ 835.150878] [ 835.152980] [ 835.155080] asm_sysvec_apic_timer_interrupt+0x12/0x20 [ 835.160216] RIP: 0010:cpuidle_enter_state+0xdd/0x380 [ 835.165180] Code: 00 31 ff e8 d5 5e 73 ff 80 7d d7 00 74 16 9c 58 0f 1f 40 00 f6 c4 02 0f 85 81 02 00 00 31 ff e8 f9 45 79 ff fb 0f 1f 44 00 00 <45> 85 ff 0f 88 1a 01 00 00 49 63 d7 4c 89 f1 48 2b 4d c8 48 8d 04 [ 835.183926] RSP: 0018:b0d8001bfe58 EFLAGS: 0246 [ 835.189154] RAX: 8e789df4 RBX: 0003 RCX: 001f [ 835.196286] RDX: RSI: 8a5bc601 RDI: 8a5cb28d [ 835.203415] RBP: b0d8001bfe90 R08: 00c262b48a68 R09: 000f [ 835.210545] R10: R11: 8e789df6fc44 R12: 8e714e59b000 [ 835.217673] R13: 8aa82800 R14: 00c262b48a68 R15: 0003 [ 835.224805] ? cpuidle_enter_state+0xbb/0x380 [ 835.229164] cpuidle_enter+0x2e/0x40 [ 835.232743] call_cpuidle+0x23/0x40 [ 835.236237] do_idle+0x1d8/0x250 [ 835.239467] cpu_startup_entry+0x20/0x30 [ 835.243392] start_secondary+0x117/0x140 [ 835.247317] secondary_startup_64_no_verify+0xd5/0xdb [ 835.252369] [ 835.254557] ---[ end trace ]--- -- 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/1953554 Title: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Bug description: Hi, I am facing this problem in Focal with the USB 3.0 Ethernet Gigabit adapter "ASIX Electronics Corp. AX88179 Gigabit Ethernet" (waneth is the name I assigned to this ethernet connected to the cable modem/router): [ cut here ] [94104.121581] NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0
[Kernel-packages] [Bug 1979045] [NEW] misleading error prints from mlx-trio
Public bug reported: SRU Justification: [Impact] TRIO IRQs are triggered during normal operation and non-error events such as mlxfwreset and the prints from the handler are misleading to users in such instances. [Fix] Replace the dev_err calls with pr_debug. This will ensure that users do not see extraneous error messages from the driver. [Test Case] Running mlxfwreset with the trio driver loaded will see a lot of error prints and this patch will fix the same. [Regression Potential] Can be considered minimal. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1979045 Title: misleading error prints from mlx-trio Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] TRIO IRQs are triggered during normal operation and non-error events such as mlxfwreset and the prints from the handler are misleading to users in such instances. [Fix] Replace the dev_err calls with pr_debug. This will ensure that users do not see extraneous error messages from the driver. [Test Case] Running mlxfwreset with the trio driver loaded will see a lot of error prints and this patch will fix the same. [Regression Potential] Can be considered minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1979045/+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 1912935] Re: battery drain while notebook off / shutdown
I have hp pavillion au624tx and facing the face issue, which is very annoying. It consumes 3% of my battery each hour !! I think, it is something related to power-profiles-daemon, is it possible to switch cpu frequency to balance mode while it is shutting down ? -- 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/1912935 Title: battery drain while notebook off / shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello, my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu. It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 . Tested: - with ubuntu 20.04 - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4) - no usb devices are plugged in - no wake ob lan available - no USB power when off (checked with optical mouse) - no visible LEDs are on when shutdown I reinstalled window 10, when shutdown from windows there is no (visible) battery drain (or significantly lower). Linux is unusable on this device, if the battery drains in a short time to 0% percent. This cause battery damage ... --- Tested TLP with default settings and activated DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power consumption after shutdown. Same power consumption on 20.10 (Groovy Gorilla). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test953 F pulseaudio /dev/snd/controlC0: test953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15s-eq0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 Tags: focal Uname: Linux 5.4.0-64-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 20T63EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+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 1971135] [NEW] touchpad is not working
Public bug reported: Mouse is working but touchpad is not working as soon i installed ubuntu ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rahulg0122 1649 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 2 14:37:20 2022 InstallationDate: Installed on 2022-04-29 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID :0538 USB OPTICAL MOUSE Bus 001 Device 002: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 0bda:c02f Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81W8 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=1d44890e-b168-4fda-b3e5-2c0828b11fd9 ro i8042.reset i8042.nomux i8042.nopnp i8042.noloop quiet splash psmouse.proto=bare vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2021 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN53WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.ec.firmware.release: 1.53 dmi.modalias: dmi:bvnLENOVO:bvrDKCN53WW:bd05/31/2021:br1.53:efr1.53:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL:skuLENOVO_MT_81W8_BU_idea_FM_IdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1971135 Title: touchpad is not working Status in linux package in Ubuntu: New Bug description: Mouse is working but touchpad is not working as soon i installed ubuntu ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rahulg0122 1649 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 2 14:37:20 2022 InstallationDate: Installed on 2022-04-29 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID :0538 USB OPTICAL MOUSE Bus 001 Device 002: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 0bda:c02f Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81W8 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=1d44890e-b168-4fda-b3e5-2c0828b11fd9 ro i8042.reset i8042.nomux i8042.nopnp i8042.noloop quiet splash psmouse.proto=bare vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2021 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN53WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.ec.firmware.release: 1.53 dmi.modalias:
[Kernel-packages] [Bug 1961581] Re: 'Synaptics touchpad' not detected as an input device on 'Fujitsu LIFEBOOK U7411'
@aletschius For me, running: “sudo modprobe i2c-hid-acpi” on the terminal worked. To avoid running this after every log-in, just add: “i2c-hid-acpi” in a new line to: “/etc/modules” -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1961581 Title: 'Synaptics touchpad' not detected as an input device on 'Fujitsu LIFEBOOK U7411' Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Touchpad used to work fine initially but I recently realised that it's not responding at all, since I'm mostly working with an external mouse. Therefore, I'm not sure when this problem started or what really caused it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 21 12:13:55 2022 InstallationDate: Installed on 2021-11-02 (111 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) 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-signed-hwe-5.13/+bug/1961581/+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 1961581] [NEW] 'Synaptics touchpad' not detected as an input device on 'Fujitsu LIFEBOOK U7411'
Public bug reported: Touchpad used to work fine initially but I recently realised that it's not responding at all, since I'm mostly working with an external mouse. Therefore, I'm not sure when this problem started or what really caused it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 21 12:13:55 2022 InstallationDate: Installed on 2021-11-02 (111 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "cat /proc/bus/input/devices" https://bugs.launchpad.net/bugs/1961581/+attachment/5562442/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1961581 Title: 'Synaptics touchpad' not detected as an input device on 'Fujitsu LIFEBOOK U7411' Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Touchpad used to work fine initially but I recently realised that it's not responding at all, since I'm mostly working with an external mouse. Therefore, I'm not sure when this problem started or what really caused it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 21 12:13:55 2022 InstallationDate: Installed on 2021-11-02 (111 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) 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-signed-hwe-5.13/+bug/1961581/+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
Re: [Kernel-packages] [Bug 1947188] Re: package linux-firmware 1.187.17 failed to install/upgrade: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted
yes. On Mon, Jan 17, 2022 at 4:11 PM Juerg Haefliger <1947...@bugs.launchpad.net> wrote: > Do you have anti-virus software installed? > > ** Also affects: linux-firmware (Ubuntu Focal) >Importance: Undecided >Status: New > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1947188 > > Title: > package linux-firmware 1.187.17 failed to install/upgrade: unable to > open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not > permitted > > Status in linux-firmware package in Ubuntu: > Confirmed > Status in linux-firmware source package in Focal: > New > > Bug description: > this is encountered when I tried apt upgrade > > ProblemType: Package > DistroRelease: Ubuntu 20.04 > Package: linux-firmware 1.187.17 > ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 > Uname: Linux 5.11.0-37-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.20 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: kumaradepu 2858 F pulseaudio > CasperMD5CheckResult: skip > Date: Thu Oct 14 22:53:56 2021 > Dependencies: > > ErrorMessage: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': > Operation not permitted > InstallationDate: Installed on 2021-09-24 (20 days ago) > InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 > (20210819) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 002: ID 0bda:5539 Realtek Semiconductor Corp. > Integrated_Webcam_HD >Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: Dell Inc. Latitude 5300 > PackageArchitecture: all > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic > root=UUID=f7268264-7e38-446b-b987-ce6c36322ac6 ro quiet splash vt.handoff=7 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, > 3.8.2-0ubuntu2 > PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged > RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 > SourcePackage: linux-firmware > Title: package linux-firmware 1.187.17 failed to install/upgrade: unable > to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 01/22/2021 > dmi.bios.release: 1.13 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.13.1 > dmi.board.name: 0932VT > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.13.1:bd01/22/2021:br1.13:svnDellInc.:pnLatitude5300:pvr:sku08B7:rvnDellInc.:rn0932VT:rvrA00:cvnDellInc.:ct10:cvr: > dmi.product.family: Latitude > dmi.product.name: Latitude 5300 > dmi.product.sku: 08B7 > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1947188/+subscriptions > > -- Thanks & Regards. Kumar A -- 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/1947188 Title: package linux-firmware 1.187.17 failed to install/upgrade: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Focal: New Bug description: this is encountered when I tried apt upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.17 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kumaradepu 2858 F pulseaudio CasperMD5CheckResult: skip Date: Thu Oct 14 22:53:56 2021 Dependencies: ErrorMessage: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-09-24 (20 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5539 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e007
[Kernel-packages] [Bug 1956417] [NEW] package linux-firmware 1.187.23 failed to install/upgrade: unable to open '/lib/firmware/mwl8k/helper_8687.fw.dpkg-new': Operation not permitted
Public bug reported: happened while installing the updates ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.23 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kumaradepu 2713 F pulseaudio CasperMD5CheckResult: skip Date: Wed Jan 5 11:38:04 2022 Dependencies: DpkgHistoryLog: Start-Date: 2022-01-05 11:37:38 Commandline: aptdaemon role='role-commit-packages' sender=':1.169' Upgrade: linux-libc-dev:amd64 (5.4.0-91.102, 5.4.0-92.103), libsystemd0:amd64 (245.4-4ubuntu3.13, 245.4-4ubuntu3.14), google-chrome-stable:amd64 (96.0.4664.110-1, 97.0.4692.71-1), udev:amd64 (245.4-4ubuntu3.13, 245.4-4ubuntu3.14), libudev1:amd64 (245.4-4ubuntu3.13, 245.4-4ubuntu3.14), systemd-timesyncd:amd64 (245.4-4ubuntu3.13, 245.4-4ubuntu3.14), systemd-sysv:amd64 (245.4-4ubuntu3.13, 245.4-4ubuntu3.14), libpam-systemd:amd64 (245.4-4ubuntu3.13, 245.4-4ubuntu3.14), systemd:amd64 (245.4-4ubuntu3.13, 245.4-4ubuntu3.14), libnss-systemd:amd64 (245.4-4ubuntu3.13, 245.4-4ubuntu3.14), linux-firmware:amd64 (1.187.23, 1.187.24) DuplicateSignature: package:linux-firmware:1.187.23 Unpacking linux-firmware (1.187.24) over (1.187.23) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_1.187.24_all.deb (--unpack): unable to open '/lib/firmware/mwl8k/helper_8687.fw.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/firmware/mwl8k/helper_8687.fw.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-09-24 (102 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5539 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 0461:4e54 Primax Electronics, Ltd Tiger USB Optical Mouse Bus 001 Device 004: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5300 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=f7268264-7e38-446b-b987-ce6c36322ac6 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: linux-firmware Title: package linux-firmware 1.187.23 failed to install/upgrade: unable to open '/lib/firmware/mwl8k/helper_8687.fw.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2021 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0932VT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd01/22/2021:br1.13:svnDellInc.:pnLatitude5300:pvr:sku08B7:rvnDellInc.:rn0932VT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5300 dmi.product.sku: 08B7 dmi.sys.vendor: Dell Inc. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- 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/1956417 Title: package linux-firmware 1.187.23 failed to install/upgrade: unable to open '/lib/firmware/mwl8k/helper_8687.fw.dpkg-new': Operation not permitted Status in linux-firmware package in Ubuntu: New Bug description: happened while installing the updates ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.23 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kumaradepu 2713 F pulseaudio CasperMD5CheckResult: skip Date: Wed Jan 5 11:38:04 2022 Dependencies: DpkgHistoryLog: Start-Date: 2022-01-05 11:37:38 Commandline: aptdaemon role='role-commit-packages' sender=':1.169' Upgrade: linux-libc-dev:amd64 (5.4.0-91.102, 5.4.0-92.103), libsystemd0:amd64 (245.4-4ubuntu3.13, 245.4-4ubuntu3.14), google-chrome-stable:amd64 (96.0.4664.110-1, 97.0.4692.71-1), udev:amd64 (245.4-4ubuntu3.13, 245.4-4ubuntu3.14), libudev1:amd64 (245.4-4ubuntu3.13, 245.4-4ubuntu3.14), systemd-timesyncd:amd64 (245.4-4ubuntu3.13, 245.4-4ubuntu3.14), systemd-sysv:amd64 (245.4-4ubuntu3.13,
[Kernel-packages] [Bug 1955108] [NEW] package linux-headers-5.11.0-43-generic 5.11.0-43.47~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-43-generic/include/config/te
Public bug reported: occurred during apt upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-43-generic 5.11.0-43.47~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-headers-5.11.0-43-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 17 13:28:30 2021 DpkgTerminalLog: Preparing to unpack .../linux-headers-5.11.0-43-generic_5.11.0-43.47~20.04.2_amd64.deb ... Unpacking linux-headers-5.11.0-43-generic (5.11.0-43.47~20.04.2) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-headers-5.11.0-43-generic_5.11.0-43.47~20.04.2_amd64.deb (--unpack): unable to open '/usr/src/linux-headers-5.11.0-43-generic/include/config/textsearch/fsm.h.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.11.0-43-generic/include/config/textsearch/fsm.h.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-09-24 (83 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-43-generic 5.11.0-43.47~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-43-generic/include/config/textsearch/fsm.h.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1955108 Title: package linux-headers-5.11.0-43-generic 5.11.0-43.47~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux- headers-5.11.0-43-generic/include/config/textsearch/fsm.h.dpkg-new': Operation not permitted Status in linux-hwe-5.11 package in Ubuntu: New Bug description: occurred during apt upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-43-generic 5.11.0-43.47~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-headers-5.11.0-43-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 17 13:28:30 2021 DpkgTerminalLog: Preparing to unpack .../linux-headers-5.11.0-43-generic_5.11.0-43.47~20.04.2_amd64.deb ... Unpacking linux-headers-5.11.0-43-generic (5.11.0-43.47~20.04.2) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-headers-5.11.0-43-generic_5.11.0-43.47~20.04.2_amd64.deb (--unpack): unable to open '/usr/src/linux-headers-5.11.0-43-generic/include/config/textsearch/fsm.h.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.11.0-43-generic/include/config/textsearch/fsm.h.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-09-24 (83 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-43-generic 5.11.0-43.47~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-43-generic/include/config/textsearch/fsm.h.dpkg-new': Operation not permitted 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.11/+bug/1955108/+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 1952749] [NEW] wireless wifi not showing after installing the ubuntu OS
Public bug reported: I cannot able to use the wifi wireless even i have tried some possible procedure to get it working like trying to install wifi driver ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 30 17:50:30 2021 InstallationDate: Installed on 2021-11-29 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1952749 Title: wireless wifi not showing after installing the ubuntu OS Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: I cannot able to use the wifi wireless even i have tried some possible procedure to get it working like trying to install wifi driver ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 30 17:50:30 2021 InstallationDate: Installed on 2021-11-29 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1952749/+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 1952061] [NEW] Bluetooth is not working. It is showing to connect with a Dongle.
Public bug reported: I changed from windows to Ubuntu 20.04 version. ** Affects: linux (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/1952061 Title: Bluetooth is not working. It is showing to connect with a Dongle. Status in linux package in Ubuntu: New Bug description: I changed from windows to Ubuntu 20.04 version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952061/+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 1948436] Re: Add RevID field to VPD info in EEPROM
** 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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1948436 Title: Add RevID field to VPD info in EEPROM Status in linux-bluefield package in Ubuntu: Fix Committed Bug description: SRU Justification: [Impact] Currently, the VPD info stored in the EEPROM does not include a Rev ID. This field is incremented when a PN goes through minor HW changes. Sometimes, SW needs to differentiate the two versions of the card. Hence, this field should be supported in the EEPROM MFG partition. [Fix] EC (Engineering Changes) field is used to denote the HW Revision of a PN. Add it to the EEPROM MFG and provide a sysfs entry to access the same via mlx-bootctl. [Test Case] This field is typically programmed at the manufacturing step using the bfcfg tool which uses the write mechanism in the driver and then the MFG partition is locked. Reading the "rev" sysfs will show the current value. [Regression Potential] Can be considered minimum. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1948436/+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 1948434] Re: Check if secure boot is enabled with development keys
** 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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1948434 Title: Check if secure boot is enabled with development keys Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: In Progress Bug description: SRU Justification: [Impact] Currently, there is no indication from mlx-bootctl when the user reads the lifecycle_state sysfs as to whether secure boot is enabled with development keys or production keys. In order to make this clear to the user, add a check in the driver. [Fix] Check the secure boot development mode status bit. If secure boot is enabled with the development key, then print it to the output buffer when lifecycle_state_show() is invoked. [Test Case] On a system in secure state, if it has been programmed with development keys, then reading the lifecycle_state sysfs entry in the mlx-bootctl driver should print a message that indicates the same. Similarly, a secure system which has been programmed with production keys must print the appropriate message when the lifecycle_state sysfs is read. [Regression Potential] Can be considered minimum. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1948434/+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 1948436] [NEW] Add RevID field to VPD info in EEPROM
Public bug reported: SRU Justification: [Impact] Currently, the VPD info stored in the EEPROM does not include a Rev ID. This field is incremented when a PN goes through minor HW changes. Sometimes, SW needs to differentiate the two versions of the card. Hence, this field should be supported in the EEPROM MFG partition. [Fix] EC (Engineering Changes) field is used to denote the HW Revision of a PN. Add it to the EEPROM MFG and provide a sysfs entry to access the same via mlx-bootctl. [Test Case] This field is typically programmed at the manufacturing step using the bfcfg tool which uses the write mechanism in the driver and then the MFG partition is locked. Reading the "rev" sysfs will show the current value. [Regression Potential] Can be considered minimum. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1948436 Title: Add RevID field to VPD info in EEPROM Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Currently, the VPD info stored in the EEPROM does not include a Rev ID. This field is incremented when a PN goes through minor HW changes. Sometimes, SW needs to differentiate the two versions of the card. Hence, this field should be supported in the EEPROM MFG partition. [Fix] EC (Engineering Changes) field is used to denote the HW Revision of a PN. Add it to the EEPROM MFG and provide a sysfs entry to access the same via mlx-bootctl. [Test Case] This field is typically programmed at the manufacturing step using the bfcfg tool which uses the write mechanism in the driver and then the MFG partition is locked. Reading the "rev" sysfs will show the current value. [Regression Potential] Can be considered minimum. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1948436/+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 1948434] [NEW] Check if secure boot is enabled with development keys
Public bug reported: SRU Justification: [Impact] Currently, there is no indication from mlx-bootctl when the user reads the lifecycle_state sysfs as to whether secure boot is enabled with development keys or production keys. In order to make this clear to the user, add a check in the driver. [Fix] Check the secure boot development mode status bit. If secure boot is enabled with the development key, then print it to the output buffer when lifecycle_state_show() is invoked. [Test Case] On a system in secure state, if it has been programmed with development keys, then reading the lifecycle_state sysfs entry in the mlx-bootctl driver should print a message that indicates the same. Similarly, a secure system which has been programmed with production keys must print the appropriate message when the lifecycle_state sysfs is read. [Regression Potential] Can be considered minimum. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1948434 Title: Check if secure boot is enabled with development keys Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Currently, there is no indication from mlx-bootctl when the user reads the lifecycle_state sysfs as to whether secure boot is enabled with development keys or production keys. In order to make this clear to the user, add a check in the driver. [Fix] Check the secure boot development mode status bit. If secure boot is enabled with the development key, then print it to the output buffer when lifecycle_state_show() is invoked. [Test Case] On a system in secure state, if it has been programmed with development keys, then reading the lifecycle_state sysfs entry in the mlx-bootctl driver should print a message that indicates the same. Similarly, a secure system which has been programmed with production keys must print the appropriate message when the lifecycle_state sysfs is read. [Regression Potential] Can be considered minimum. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1948434/+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 1947616] [NEW] package linux-modules-extra-5.11.0-38-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.11.0-38-generic/kernel/drivers/net/etherne
Public bug reported: This is encountered when I do apt upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.11.0-38-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 18 22:28:01 2021 ErrorMessage: unable to open '/lib/modules/5.11.0-38-generic/kernel/drivers/net/ethernet/marvell/prestera/prestera_pci.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-09-24 (24 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-modules-extra-5.11.0-38-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.11.0-38-generic/kernel/drivers/net/ethernet/marvell/prestera/prestera_pci.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1947616 Title: package linux-modules-extra-5.11.0-38-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.11.0-38-generic/kernel/drivers/net/ethernet/marvell/prestera/prestera_pci.ko.dpkg- new': Operation not permitted Status in linux-hwe-5.11 package in Ubuntu: New Bug description: This is encountered when I do apt upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.11.0-38-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 18 22:28:01 2021 ErrorMessage: unable to open '/lib/modules/5.11.0-38-generic/kernel/drivers/net/ethernet/marvell/prestera/prestera_pci.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-09-24 (24 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-modules-extra-5.11.0-38-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.11.0-38-generic/kernel/drivers/net/ethernet/marvell/prestera/prestera_pci.ko.dpkg-new': Operation not permitted 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.11/+bug/1947616/+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
Re: [Kernel-packages] [Bug 1947188] Re: package linux-firmware 1.187.17 failed to install/upgrade: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted
Hi, Please find the mentioned details of the respective directories & their permissions. /lib/firmware: *drwxr-xr-x 90 root root 36864 Oct 14 22:58 firmware* /lib/firmware/r128: *drwxr-xr-x 2 root root4096 Oct 14 22:58 r128* Same permission for */lib* as well. On Sat, Oct 16, 2021 at 1:30 PM Juerg Haefliger <1947...@bugs.launchpad.net> wrote: > Hrm. Is /lib a read-only mount? What are the file permissions of > /lib/firmware and /lib/firmware/r128? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1947188 > > Title: > package linux-firmware 1.187.17 failed to install/upgrade: unable to > open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not > permitted > > Status in linux-firmware package in Ubuntu: > New > > Bug description: > this is encountered when I tried apt upgrade > > ProblemType: Package > DistroRelease: Ubuntu 20.04 > Package: linux-firmware 1.187.17 > ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 > Uname: Linux 5.11.0-37-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.20 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: kumaradepu 2858 F pulseaudio > CasperMD5CheckResult: skip > Date: Thu Oct 14 22:53:56 2021 > Dependencies: > > ErrorMessage: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': > Operation not permitted > InstallationDate: Installed on 2021-09-24 (20 days ago) > InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 > (20210819) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 002: ID 0bda:5539 Realtek Semiconductor Corp. > Integrated_Webcam_HD >Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: Dell Inc. Latitude 5300 > PackageArchitecture: all > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic > root=UUID=f7268264-7e38-446b-b987-ce6c36322ac6 ro quiet splash vt.handoff=7 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, > 3.8.2-0ubuntu2 > PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged > RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 > SourcePackage: linux-firmware > Title: package linux-firmware 1.187.17 failed to install/upgrade: unable > to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 01/22/2021 > dmi.bios.release: 1.13 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.13.1 > dmi.board.name: 0932VT > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.13.1:bd01/22/2021:br1.13:svnDellInc.:pnLatitude5300:pvr:sku08B7:rvnDellInc.:rn0932VT:rvrA00:cvnDellInc.:ct10:cvr: > dmi.product.family: Latitude > dmi.product.name: Latitude 5300 > dmi.product.sku: 08B7 > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1947188/+subscriptions > > -- 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/1947188 Title: package linux-firmware 1.187.17 failed to install/upgrade: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted Status in linux-firmware package in Ubuntu: New Bug description: this is encountered when I tried apt upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.17 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kumaradepu 2858 F pulseaudio CasperMD5CheckResult: skip Date: Thu Oct 14 22:53:56 2021 Dependencies: ErrorMessage: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-09-24 (20 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5539 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5300 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1947188] [NEW] package linux-firmware 1.187.17 failed to install/upgrade: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted
Public bug reported: this is encountered when I tried apt upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.17 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kumaradepu 2858 F pulseaudio CasperMD5CheckResult: skip Date: Thu Oct 14 22:53:56 2021 Dependencies: ErrorMessage: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-09-24 (20 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5539 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5300 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=f7268264-7e38-446b-b987-ce6c36322ac6 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: linux-firmware Title: package linux-firmware 1.187.17 failed to install/upgrade: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2021 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0932VT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd01/22/2021:br1.13:svnDellInc.:pnLatitude5300:pvr:sku08B7:rvnDellInc.:rn0932VT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5300 dmi.product.sku: 08B7 dmi.sys.vendor: Dell Inc. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1947188 Title: package linux-firmware 1.187.17 failed to install/upgrade: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted Status in linux-firmware package in Ubuntu: New Bug description: this is encountered when I tried apt upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.17 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kumaradepu 2858 F pulseaudio CasperMD5CheckResult: skip Date: Thu Oct 14 22:53:56 2021 Dependencies: ErrorMessage: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-09-24 (20 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5539 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5300 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=f7268264-7e38-446b-b987-ce6c36322ac6 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: linux-firmware Title: package linux-firmware 1.187.17 failed to install/upgrade: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2021 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0932VT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1943425] [NEW] Touchpad is not working and detected
Public bug reported: Ubuntu 5.4.0-84.94-generic 5.4.133 Description:Ubuntu 20.04.3 LTS Release:20.04 xinput -list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Logitech Wireless Receiver Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Button id=9[slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=12 [slave keyboard (3)] ↳ Dell WMI hotkeys id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] xinput shows no touchpad Touchpad is not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-84-generic 5.4.0-84.94 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: reveur 3039 F pulseaudio /dev/snd/controlC0: reveur 3039 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Sep 13 13:46:42 2021 HibernationDevice: RESUME=UUID=0d592d53-b697-445e-a05f-df427587848e MachineType: Dell Inc. Inspiron 3558 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-84-generic root=UUID=5276c553-95fa-4b9f-aa57-08c119bd464c ro i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop RelatedPackageVersions: linux-restricted-modules-5.4.0-84-generic N/A linux-backports-modules-5.4.0-84-generic N/A linux-firmware1.187.16 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0G1TDD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd12/15/2015:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0G1TDD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.product.sku: 06B0 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug 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/1943425 Title: Touchpad is not working and detected Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 5.4.0-84.94-generic 5.4.133 Description: Ubuntu 20.04.3 LTS Release: 20.04 xinput -list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech Wireless Receiver Mouseid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=12 [slave keyboard (3)] ↳ Dell WMI hotkeysid=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] xinput shows no touchpad Touchpad is not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-84-generic 5.4.0-84.94 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: reveur 3039 F pulseaudio /dev/snd/controlC0: reveur 3039 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Sep 13 13:46:42 2021 HibernationDevice:
[Kernel-packages] [Bug 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws
Linux YOGA 5.14.0-051400rc5drmtip20210809-generic #202108082205 SMP Mon Aug 9 02:21:27 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws Status in linux package in Ubuntu: Triaged Status in linux-hwe-5.11 package in Ubuntu: Triaged Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws
Now I am able to boot into ubuntu in normal mode but there is screen glitch problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws Status in linux package in Ubuntu: Triaged Status in linux-hwe-5.11 package in Ubuntu: Triaged Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws
I have installed both files, Now what to do?? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws Status in linux package in Ubuntu: Triaged Status in linux-hwe-5.11 package in Ubuntu: Triaged Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws
before Testing one thing I want to tell you I won't able to boot in ubuntu in normal mode but in recovery mode there is no issue related to screen tearing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws Status in linux package in Ubuntu: Triaged Status in linux-hwe-5.11 package in Ubuntu: Triaged Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws
Can you tell me in brief how to test drm-tip kernal and disble PSR2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws Status in linux package in Ubuntu: Triaged Status in linux-hwe-5.11 package in Ubuntu: Triaged Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931843] Re: Update mlx-bootctl to access new fields in EEPROM MFG
** 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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1931843 Title: Update mlx-bootctl to access new fields in EEPROM MFG Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] The EEPROM MFG partition on BlueField-2 has been updated to include the VPD information for each card. In order to access these newly added fields, the mlx-bootctl driver needs to be updated to provide an access mechanism. [Fix] Add support for VPD fields in the EEPROM MFG and provide access to these via sysfs entries. The newly added sysfs entries are: sku (SKU ID), modl (Model Number), sn (Serial Number) and uuid (UUID). And the previously added opn_str sysfs has been renamed to opn. [Test Case] Though the driver provides read and write access through sysfs, the contents of the MFG partition are written during Manufacturing and then locked in order to protect the info. Writing to this partition will therefore require resetting the MFG info from the UEFI Device Manager, which will unlock the partition and allow for it to be reprogrammed. Reading the sysfs entries will print the contents of each field. It could also be empty if the field was not programmed earlier. [Regression Potential] Can be considered minimum, since the new fields have been added without interfering with the existing fields which might already be present in the EEPROM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1931843/+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 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws
yes ! I am Gonna tell you that same Now its perfectly fine no glitches and tearing issue now.But I want to Know does touchpad issue is solved in UBuntu 20.04LTS for lenovo yoga 7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws
Please tell me proper procedure to change value to zero -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws
It said -1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws
i think there is some issue with intel gpu driver because sometime ubuntu stuck on bootscreen and glitches and tearing is common in every scenario and after booting to recovery boot brightness controlling have some issue and all tends towards the ghraphics 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/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws
As you said to change the i915.enable_psr =0 i have save it to suno nano etc/kernal/cmdline after rebooting my pc there is more screen tearing problem. yeah i am using ubuntu in 2 device one in my old lenovo g570 model and new lenovo yoga 7i and in G570 there is no problem such as screen tearing or brightness every thing is perfectly fine in g570 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937072] Re: Incomplete screen redraws
List of things I have to Inform you what I have tested.I am Computer Science student but new to linux so I have tested many things. 1. I have used both x-org and nvidia GPU. After fresh installation and on reboot I got into many problem my touchpad and brightness controller were not working and screen glitch so i fixed my brightness and touchpad using ubuntu community posts. But glitch were all same I have tried many solution but not solved. so I posted ubuntu-bug. 2. I have changed setting from bios to disable NVIDIA but glitch problem not solved. And on using NVIDIA Driver there were not glitch performance were perfectly fine but on restart i got stucked on boot menu screen were blank so i ran into recovery and change my driver to x-org intel. 3. Before bug submission I have tested around 10 popular linux distro all were having same problem screen glitches. 4. only two distro have not occoured a display glitch problem one was ubuntu 20.04 LTS and ubuntu budgie 21.04 but that distro causes same touchpad and brightness controll problem that was so frustating. So I came to conclusion that my intel driver is buggy and on reboot my device alwaay fail to recognise touchpad and display 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/1937072 Title: Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931981] Re: mlx-bootctl: Fix potential buffer overflow
*** This bug is a duplicate of bug 1931843 *** https://bugs.launchpad.net/bugs/1931843 ** This bug has been marked a duplicate of bug 1931843 Update mlx-bootctl to access new fields in EEPROM MFG -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1931981 Title: mlx-bootctl: Fix potential buffer overflow Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] The sysfs store/show functions use sprintf without specifying a size which could lead to potential buffer overflow. [Fix] Replace sprintf with snprintf to avoid buffer overflow. Also, remove the redundant strlen usage since count is already available in the _store functions. [Test Plan] Read/write access to the EEPROM MFG fields can be tested via the sysfs entries that are exposed by the driver. Please note that the MFG partition is locked in order to protect the data and this could block all writes to it. In order to enable writes to the EEPROM, the MFG Info needs to be reset via the UEFI Device Manager. [Regression Potential] Can be considered minimum. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1931981/+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 1931984] Re: mlx-bootctl: Update license and version info
*** This bug is a duplicate of bug 1931843 *** https://bugs.launchpad.net/bugs/1931843 ** This bug has been marked a duplicate of bug 1931843 Update mlx-bootctl to access new fields in EEPROM MFG -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1931984 Title: mlx-bootctl: Update license and version info Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] License info needs to be updated since the current info is no longer accurate. Driver version needs to be incremented since new features have been added. [Fix] Update license info to "Dual BSD/GPL". Increment version to 1.4 [Test Plan] Verify version change [Regression Potential] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1931984/+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 1933642] Re: mlx-bootctl: Fix exclusion issues around arm_smccc_smc
*** This bug is a duplicate of bug 1931843 *** https://bugs.launchpad.net/bugs/1931843 ** This bug has been marked a duplicate of bug 1931843 Update mlx-bootctl to access new fields in EEPROM MFG -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1933642 Title: mlx-bootctl: Fix exclusion issues around arm_smccc_smc Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Exclusion is being handled around arm_smccc_smc() only in the store functions. It should be implemented in the show functions also as this call might not be thread-safe. [Fix] Add mutex_lock/unlock around arm_smccc_smc calls in the show functions. [Test Case] Multiple simultaneous accesses to a sysfs entry exposed by the driver are successful. [Regression Potential] Can be considered minimum To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1933642/+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 1933749] [NEW] nvidia-dkms-465 465.27-0ubuntu0.20.04.2: nvidia kernel module failed to build
Public bug reported: trying to sign Nvidia kernel modules, the system as some errors message poped up ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-465 465.27-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-59-generic Date: Sun Jun 27 08:34:30 2021 InstallationDate: Installed on 2021-06-23 (3 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 465.27-0ubuntu0.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: nvidia-graphics-drivers-465 Title: nvidia-dkms-465 465.27-0ubuntu0.20.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-465 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-465 in Ubuntu. https://bugs.launchpad.net/bugs/1933749 Title: nvidia-dkms-465 465.27-0ubuntu0.20.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-465 package in Ubuntu: New Bug description: trying to sign Nvidia kernel modules, the system as some errors message poped up ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-465 465.27-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-59-generic Date: Sun Jun 27 08:34:30 2021 InstallationDate: Installed on 2021-06-23 (3 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 465.27-0ubuntu0.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: nvidia-graphics-drivers-465 Title: nvidia-dkms-465 465.27-0ubuntu0.20.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-465/+bug/1933749/+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 1933642] [NEW] mlx-bootctl: Fix exclusion issues around arm_smccc_smc
Public bug reported: SRU Justification: [Impact] Exclusion is being handled around arm_smccc_smc() only in the store functions. It should be implemented in the show functions also as this call might not be thread-safe. [Fix] Add mutex_lock/unlock around arm_smccc_smc calls in the show functions. [Test Case] Multiple simultaneous accesses to a sysfs entry exposed by the driver are successful. [Regression Potential] Can be considered minimum ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1933642 Title: mlx-bootctl: Fix exclusion issues around arm_smccc_smc Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Exclusion is being handled around arm_smccc_smc() only in the store functions. It should be implemented in the show functions also as this call might not be thread-safe. [Fix] Add mutex_lock/unlock around arm_smccc_smc calls in the show functions. [Test Case] Multiple simultaneous accesses to a sysfs entry exposed by the driver are successful. [Regression Potential] Can be considered minimum To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1933642/+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 1926062] Re: [hirsute] Can't turn bluetooth on again after turning it off
I was facing the same problem. My toggle was not at all working, neither from the top bar dropdown menu nor from the settings window. Switching on the toggle did not have any effect. I had also reported this bug. Someone in the comments had suggested a workaround to type this command in the terminal: systemctl restart Bluetooth This command kind of hard restarts the Bluetooth service and works for me for the time being until the bug is fixed. It might also help someone else. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute] Can't turn bluetooth on again after turning it off Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926062/+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 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
Hi all. I am also affected by this bug. Just to be clear, Ubuntu 20.04 works with a previous version of Linux Kernel right ( <= 4.15)? I can use a downgraded version of the kernel for now if thats the only thing that can be done atm. Regards, Akash -- 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/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). WORKAROUND: I installed the 4.15 kernel, so at the moment I can work with this. Higher than 4.15 the second monitor doesn't work. Tested until 5.8 and without good results. Just with 4.15. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume
