*** This bug is a duplicate of bug 2136499 *** https://bugs.launchpad.net/bugs/2136499 Consult /var/lib/dkms/virtualbox/7.0.16-dfsg-2ubuntu1.1/build/make.log for more information. dkms autoinstall on 6.8.0-111-generic/x86_64 failed for virtualbox(10) ** Package changed: linux (Ubuntu) => virtualbox (Ubuntu) ** This bug has been marked a duplicate of bug 2136499 virtualbox-dkms FTBFS in Noble with the linux-6.17 kernel -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152027 Title: package linux-headers-6.8.0-111-generic 6.8.0-111.111 failed to install/upgrade: подпроцесс из пакета linux-headers-6.8.0-111-generic установлен сценарий post-installation возвратил код ошибки 11 Status in virtualbox package in Ubuntu: New Bug description: idk ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-111-generic 6.8.0-111.111 ProcVersionSignature: Ubuntu 6.14.0-37.37~24.04.1-generic 6.14.11 Uname: Linux 6.14.0-37-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.8 AptOrdering: linux-image-6.17.0-22-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Fri May 8 14:57:26 2026 ErrorMessage: подпроцесс из пакета linux-headers-6.8.0-111-generic установлен сценарий post-installation возвратил код ошибки 11 InstallationDate: Installed on 2025-11-02 (187 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: HONOR BRI-XX ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.14.0-37-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2.1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-6.8.0-111-generic 6.8.0-111.111 failed to install/upgrade: подпроцесс из пакета linux-headers-6.8.0-111-generic установлен сценарий post-installation возвратил код ошибки 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2025 dmi.bios.release: 1.9 dmi.bios.vendor: HONOR dmi.bios.version: 1.09 dmi.board.asset.tag: NA dmi.board.name: BRI-XX-PCB dmi.board.vendor: HONOR dmi.board.version: M1040 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HONOR dmi.chassis.version: M1040 dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnHONOR:bvr1.09:bd01/14/2025:br1.9:efr1.9:svnHONOR:pnBRI-XX:pvrM1040:rvnHONOR:rnBRI-XX-PCB:rvrM1040:cvnHONOR:ct10:cvrM1040:skuC233: dmi.product.family: HONOR MagicBook dmi.product.name: BRI-XX dmi.product.sku: C233 dmi.product.version: M1040 dmi.sys.vendor: HONOR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/2152027/+subscriptions
суббота
[Bug 2151831] Re: Dirty Frag LPE security vulnerability
Two CVE IDs are assigned: CVE-2026-43284, CVE-2026-43500 Source: https://www.openwall.com/lists/oss-security/2026/05/08/7 https://www.openwall.com/lists/oss-security/2026/05/08/8 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-43284 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-43500 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2151831 Title: Dirty Frag LPE security vulnerability Status in kmod package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The dirty frag vulnerability is like the copy.fail vulnerability. See: * https://www.openwall.com/lists/oss-security/2026/05/07/8 * https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md * https://askubuntu.com/q/1566558/1004020 kmod should mitigate this via `install ... /bin/false` like done for copy.fail. linux-* should receive a full patch once that's available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/2151831/+subscriptions
[Bug 2151769] Re: Lenovo Thinkpad P14s Gen6 Intel clickpad is nearly unusable
trying a sosreport attachment yet again... ** Attachment added: "sosreport-rocinante-2151769-2026-05-07-rxzkokd.tar.xz.sha256" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2151769/+attachment/5968705/+files/sosreport-rocinante-2151769-2026-05-07-rxzkokd.tar.xz.sha256 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2151769 Title: Lenovo Thinkpad P14s Gen6 Intel clickpad is nearly unusable Status in linux package in Ubuntu: New Bug description: purchased this as a corporate laptop and it is running fully updated 26.04 with linux-image-oem-24.04 (7.0). the touchpad has multiple issues. first, it fails often to register touch. I can tap or drag the finger and it does not register the finger touch so I cannot move the pointer much, if at all. it is a click pad and often will register the initial moment my finger touches the pad AND the click together treating them as a double click. It very often fails to register two finger taps, or multi finger gestures for scrolling or exposing the desktop or whatever. It is super sensitive and sometimes registers the proximity of my hand (without actually touching it) as a touch making the cursor jump around. This is incredibly frustrating as it often means I am fixing typos where the cursor jumps, or fixing issues where it regitsers an action to highlight an entire line causing me to lose the line on the next keypress (as in highlight and replace/type over. all of this is intermittent. I usually use the machine at home when docked (FYI for some reason it just triggered the highlight entire line and deleted this sentence and I had to retype it.). When docked I'm using an external BT mouse so I dont notice issues. But both times Ive traveled with this machine I've had an incredibly frustrating experience with the trackpad and how it behaves.CLOSE For context it has taken me twice as long to type this out as it should because I have to keep correcting issues where the trackpad is jumping the mouse around, and other issues. Right now, two finger scrolling is not working at all... it just randomly stopped working yesterday. Just a moment ago, it somehow started triggering moving through tabs on my browser when I used a single finger touch/drag to move the cursor through this text box... sigh... and it sometimes fails to even register the click action on the clickpad, making me instead try to remember using the actual buttons to perform click actions instead of hoping that either tap or click on the pad itself will work. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: jeffrey.lane@canonical.com 382304 F.... pipewire jeffrey.lane@canonical.com 382306 F.... wireplumber /dev/snd/seq: jeffrey.lane@canonical.com 382304 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 7 08:47:21 2026 InstallationDate: Installed on 2025-12-12 (145 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Daily amd64 (20250306) MachineType: LENOVO 21QTCTO1WW ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/bash TERM=screen-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-04-22 (14 days ago) dmi.bios.date: 08/06/2025 dmi.bios.release: 1.18 dmi.bios.vendor: LENOVO dmi.bios.version: R2WET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 21QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 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.10 dmi.modalias: dmi:bvnLENOVO:bvrR2WET36W(1.18):bd08/06/2025:br1.18:efr1.10:svnLENOVO:pn21QTCTO1WW:pvrThinkPadP14sGen6:rvnLENOVO:rn21QTCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21QT_BU_Think_FM_ThinkPadP14sGen6:pfaThinkPadP14sGen6: dmi.product.family: ThinkPad P14s Gen 6 dmi.product.name: 21QTCTO1WW dmi.product.sku: LENOVO_MT_21QT_BU_Think_FM_ThinkPad P14s Gen 6 dmi.product.version: ThinkPad P14s Gen 6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2151769/+subscriptions
[Bug 2138991] Re: Dell 16 Premium DA16250 webcam (OV02C10) not working - INT3472 GPIO type 0x02 unknown
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Noble) Status: New => Confirmed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2138991 Title: Dell 16 Premium DA16250 webcam (OV02C10) not working - INT3472 GPIO type 0x02 unknown Status in ipu6-drivers package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in ipu6-drivers source package in Noble: Confirmed Status in linux source package in Noble: Confirmed Bug description: ## Description ### Summary The integrated webcam on Dell 16 Premium (DA16250) with Intel Meteor Lake CPU does not work on Ubuntu 24.04 with OEM kernel. The camera sensor (OV02C10) is detected but fails to initialize due to unsupported GPIO type 0x02 in the INT3472 discrete driver. ### System Information - **Hardware:** Dell 16 Premium DA16250 - **CPU:** Intel Core Ultra 9 285H (Meteor Lake) - **Camera Sensor:** OmniVision OV02C10 (ACPI: OVTI02C1:00) - **OS:** Ubuntu 24.04.3 LTS - **Kernel:** 6.14.0-1019-oem ### Steps to Reproduce 1. Install Ubuntu 24.04 on Dell 16 Premium DA16250 2. Install OEM kernel: `sudo apt install linux-oem-24.04` 3. Install IPU6 modules: `sudo apt install linux-modules-ipu6-6.14.0-1019-oem` 4. Install camera HAL: `sudo apt install libcamhal-ipu6epmtl` (from OEM PPA) 5. Reboot and try to use the webcam ### Expected Behavior Webcam should be detected and functional in applications like Cheese, Firefox, Chromium. ### Actual Behavior Camera is detected by the IPU6 driver but fails to initialize. The sensor does not register in the media pipeline. ### Error Messages (from dmesg) ``` int3472-discrete INT3472:0c: GPIO type 0x02 unknown; the sensor may not work intel-ipu6 0000:00:05.0: Found supported sensor OVTI02C1:00 intel-ipu6 0000:00:05.0: Connected 1 cameras ``` ### Error Messages (from GStreamer test) ``` CamHAL[INF] aiqb file name AR0234_TGL_10bits.aiqb CamHAL[ERR] Stream config is not supported. format:V4L2_PIX_FMT_NV12 (1920x1080) ``` The camera HAL loads the wrong config file (AR0234 instead of OV02C10) because the sensor is not bound to the I2C bus. ### Diagnosis The ov02c10 kernel module is loaded but not bound to any device: ``` $ ls /sys/bus/i2c/drivers/ov02c10/ bind module uevent unbind ``` The ACPI device exists and is enabled (status 15): ``` $ cat /sys/bus/acpi/devices/OVTI02C1:00/status 15 ``` But there is no physical_node because the INT3472 GPIO initialization fails. ### Root Cause GPIO type 0x02 is a "strobe" GPIO used for LED/IR control on Meteor Lake systems. The int3472-discrete driver does not recognize this GPIO type, preventing proper camera power-up. ### Existing Kernel Patch A patch exists that adds support for GPIO type 0x02 (strobe): https://patchwork.kernel.org/project/linux-media/patch/20231007021309.9332-1-hao.yao@intel.com/ ### Related Issues - Intel IPU6 drivers: https://github.com/intel/ipu6-drivers/issues/413 - Intel IPU6 drivers: https://github.com/intel/ipu6-drivers/issues/40 - Ubuntu Bug #2117188: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2117188 ### Workarounds Attempted (None Successful) 1. Added `intel_iommu=on` to kernel parameters 2. Fixed /dev/ipu-psys0 permissions with udev rules 3. Installed libcamhal-ipu6epmtl from OEM PPA 4. Tried Dell OEM archive packages ### Request Please backport the INT3472 GPIO strobe patch to the Ubuntu OEM kernel to support Dell 16 Premium and other Meteor Lake laptops with OV02C10 cameras. ## Attachments ### uname -a ``` Linux Dell-16-Premium-DA16250 6.14.0-1019-oem #19-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 18 05:40:21 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux ``` ### CPU Info ``` vendor_id : GenuineIntel cpu family : 6 model : 197 model name : Intel(R) Core(TM) Ultra 9 285H ``` ### lspci (IPU6 device) ``` 0000:00:05.0 Multimedia controller [0480]: Intel Corporation Device [8086:7d19] (rev 05) Subsystem: Dell Device [1028:0ce7] Flags: bus master, fast devsel, latency 0, IRQ 16, IOMMU group 3 Memory at 581c000000 (64-bit, non-prefetchable) [size=16M] Kernel driver in use: intel-ipu6 Kernel modules: intel_ipu6 ``` ### dmesg (camera related) ``` [ 16.744854] int3472-discrete INT3472:0c: GPIO type 0x02 unknown; the sensor may not work [ 16.764935] intel-ipu6 0000:00:05.0: enabling device (0000 -> 0002) [ 16.781627] intel-ipu6 0000:00:05.0: Found supported sensor OVTI02C1:00 [ 16.781717] intel-ipu6 0000:00:05.0: Connected 1 cameras [ 16.784617] intel-ipu6 0000:00:05.0: Sending BOOT_LOAD to CSE [ 16.821495] intel-ipu6 0000:00:05.0: Sending AUTHENTICATE_RUN to CSE [ 16.879001] intel-ipu6 0000:00:05.0: CSE authenticate_run done [ 16.879013] intel-ipu6 0000:00:05.0: IPU6-v4[7d19] hardware version 6 [ 17.565317] intel_ipu6_psys.psys intel_ipu6.psys.40: pkg_dir entry count:8 [ 17.565808] intel_ipu6_psys.psys intel_ipu6.psys.40: psys probe minor: 0 [ 2663.927955] intel-ipu6 0000:00:05.0: IPU6 in secure mode [ 7592.628584] intel-ipu6 0000:00:05.0: IPU6 in secure mode ``` ### Installed packages (camera related) ``` ii gstreamer1.0-icamera 0~git202509260937.4fb31db~ubuntu24.04.7 amd64 ii libcamhal-common 0~git202601200757.9899efa~ubuntu24.04.1 all ii libcamhal-ipu6ep 0~git202601200757.9899efa~ubuntu24.04.1 amd64 ii libcamhal-ipu6epmtl 0~git202601200757.9899efa~ubuntu24.04.1 amd64 ii libcamhal0 0~git202601200757.9899efa~ubuntu24.04.1 amd64 ii linux-image-6.14.0-1019-oem 6.14.0-1019.19 amd64 ii linux-image-6.14.0-37-generic 6.14.0-37.37~24.04.1 amd64 ii linux-image-generic-hwe-24.04 6.14.0-37.37~24.04.1 amd64 ii linux-image-oem-24.04 6.14.0-1019.19 amd64 ii linux-modules-6.14.0-1019-oem 6.14.0-1019.19 amd64 ii linux-modules-6.14.0-37-generic 6.14.0-37.37~24.04.1 amd64 ii linux-modules-extra-6.14.0-37-generic 6.14.0-37.37~24.04.1 amd64 ii linux-modules-ipu6-6.14.0-1019-oem 6.14.0-1019.19 amd64 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2138991/+subscriptions
[Bug 2151842] [NEW] aa-rootns.c bypasses apparmor_restrict_unprivileged_userns
*** This bug is a security vulnerability *** Public security bug reported: Please find a way to stop https://github.com/0xdeadbeefnetwork/Copy_Fail2-Electric_Boogaloo/blob/main/aa- rootns.c from working. See also https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/2151831 but the apparmor_restrict_unprivileged_userns bypass is separate from the copy.fail or dirty frag vulnerabilities. This doesn't affect me because I disabled that sysctl to make unshare work, but a fix would reduce the attack surface for others. If a fix isn't readily available, then please disable that sysctl to reduce inconvenience and the illusion of security. ** Affects: apparmor Importance: Undecided Status: New ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public Security ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2151842 Title: aa-rootns.c bypasses apparmor_restrict_unprivileged_userns Status in AppArmor: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Please find a way to stop https://github.com/0xdeadbeefnetwork/Copy_Fail2-Electric_Boogaloo/blob/main/aa- rootns.c from working. See also https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/2151831 but the apparmor_restrict_unprivileged_userns bypass is separate from the copy.fail or dirty frag vulnerabilities. This doesn't affect me because I disabled that sysctl to make unshare work, but a fix would reduce the attack surface for others. If a fix isn't readily available, then please disable that sysctl to reduce inconvenience and the illusion of security. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2151842/+subscriptions
[Bug 2151831] Re: Dirty Frag LPE security vulnerability
@mhalano The rxrpc fix is yet to be merged into mainline On the other hand, I wasn't able to use `./exp` to escalate from "ubuntu" to root in my ubuntu:26.04 Docker container. That's a relief. My `unshare` and `setpriv --no-new-privs` sandbox also prevented root access, but `su` stopped asking for a password even when run outside the sandbox, so I worry whether the exploit can corrupt a running process's memory. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2151831 Title: Dirty Frag LPE security vulnerability Status in kmod package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: The dirty frag vulnerability is like the copy.fail vulnerability. See: * https://www.openwall.com/lists/oss-security/2026/05/07/8 * https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md * https://askubuntu.com/q/1566558/1004020 kmod should mitigate this via `install ... /bin/false` like done for copy.fail. linux-* should receive a full patch once that's available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/2151831/+subscriptions
[Bug 2151831] Re: Dirty Frag LPE security vulnerability
For more information: https://ubuntu.com/blog/dirty-frag-linux-vulnerability-fixes-available -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2151831 Title: Dirty Frag LPE security vulnerability Status in kmod package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: The dirty frag vulnerability is like the copy.fail vulnerability. See: * https://www.openwall.com/lists/oss-security/2026/05/07/8 * https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md * https://askubuntu.com/q/1566558/1004020 kmod should mitigate this via `install ... /bin/false` like done for copy.fail. linux-* should receive a full patch once that's available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/2151831/+subscriptions
[Bug 2152105] [NEW] i915 PSR causes display+USB+BT glitches on XPS 15 9530; kernel cmdline whitelist on 26.04 blocks i915.enable_psr=0 workaround
Public bug reported: == Hardware == - Dell XPS 15 9530 (BIOS 1.29.0) - iGPU: Intel Raptor Lake-P [Iris Xe Graphics] (device ID a7a0, integrated display version 13.00 stepping E0) - dGPU: NVIDIA RTX 4060 Max-Q (Optimus, displays driven by iGPU) - Connected: internal eDP-1 panel (PSR1 capable) + 2x DisplayPort over Dell Thunderbolt Dock == Software == - Ubuntu Desktop 26.04, snap model `ubuntu-classic-2604-amd64`, grade `signed` (FDE Enhanced, TPM-sealed LUKS) - Kernel: 7.0.0-15-generic (pc-kernel snap rev 3419, channel 26.04/stable) - Bootloader: systemd-boot via signed kernel.efi from pc-kernel snap (Secure Boot + kernel lockdown active) == Symptom == Recurring display flicker on the eDP panel together with simultaneous USB re-enumeration ("clink-clong" sound on the Dell TB Dock), USB audio interruption, and brief Bluetooth (hci0) drop. Episodes last ~1 second and repeat several times per day, more frequently when the dGPU activates (e.g. Steam/PRIME render offload). PSR debug status during the glitch shows the panel stuck in SRDENT (Self-Refresh Data Enable) with very high transition rate; counter rises ~500/s. State returns to IDLE when the symptom resolves: Source PSR/PanelReplay status: SRDENT [0x400f0009] (during glitch) Source PSR/PanelReplay status: IDLE [0x040b0001] (resolved) This matches Dell's documented hardware issue for the XPS 15 9530 panel ("LCD Screen on the XPS 15 9530 Randomly Flickers", KB 000218908) where Dell themselves recommend disabling PSR in the Intel Graphics Command Center on Windows. Was not happening on Ubuntu 24.04 with kernel 6.x — regression introduced by the move to kernel 7.0 and/or pc-kernel snap on 26.04. == Standard workaround is blocked == The well-known workaround `i915.enable_psr=0` cannot be applied on 26.04 with the current setup: 1. /etc/default/grub does not exist / is not consumed (snap-managed kernel cmdline). 2. `snap set system system.kernel.cmdline-append="i915.enable_psr=0"` fails with: "i915.enable_psr=0" is not allowed in the kernel command line by the gadget The pc gadget snap (rev 220) gadget.yaml whitelist only permits `quiet` and `splash`. 3. `system.kernel.dangerous-cmdline-append` is not usable: requires model grade `dangerous`. This system is grade `signed` (Enhanced FDE). 4. /etc/modprobe.d/i915-disable-psr.conf with `options i915 enable_psr=0` is ignored: i915 loads from the initrd embedded in kernel.efi (signed) before the encrypted rootfs is mounted, so the local modprobe.d is never consulted. Verified by reboot test (enable_psr stays at -1). 5. /sys/module/i915/parameters/enable_psr* are read-only at runtime (mode 0400 root, write returns Permission denied even with sudo). 6. /sys/kernel/debug/dri/.../i915_edp_psr_debug write is blocked by kernel lockdown (Secure Boot). Net result: a user with `signed` Enhanced FDE on this hardware has no supported way to disable a known-buggy display feature. == Request == Either: (a) Add the well-known display-related i915 parameters (i915.enable_psr, i915.enable_fbc, i915.enable_psr2_sel_fetch, i915.enable_dc) to the kernel-cmdline allow list of the `pc` gadget snap, so users on `signed` FDE Enhanced systems can apply standard hardware workarounds; or (b) Quirk-disable PSR in the i915 driver for the Dell XPS 15 9530 panel (and similar panels with documented Dell-side PSR issues), in line with Dell's own Windows guidance. == Related == - LP #2065096 — i915 Display is Laggy/Unresponsive when PSR is enabled (Dell Latitude 7430/9430, same root cause, 24.04 / kernel 6.8). Workaround there is i915.enable_psr=0 in GRUB — that escape hatch no longer exists on 26.04 with `signed` FDE. - Dell KB 000218908 — XPS 15 9530 random flickering, recommends disabling PSR. - Discourse: "The pc-kernel snap on 26.04 prevents users from installing additional firmware" — same family of customisation lock-out issues on 26.04. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic (not installed) ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 9 22:18:19 2026 IwDevWlp0s20f3Link: Not connected. MachineType: Dell Inc. XPS 15 9530 ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: snapd_recovery_mode=run console=ttyS0,115200n8 console=tty1 panic=-1 quiet splash snapd.xkb="es,pc105,," SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2025 dmi.bios.release: 1.29 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.29.0 dmi.board.name: 0P6GXD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnDellInc.:bvr1.29.0:bd12/24/2025:br1.29:efr1.17:svnDellInc.:pnXPS159530:pvr:rvnDellInc.:rn0P6GXD:rvrA00:cvnDellInc.:ct10:cvr:sku0BEB:pfaXPS: dmi.product.family: XPS dmi.product.name: XPS 15 9530 dmi.product.sku: 0BEB dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152105 Title: i915 PSR causes display+USB+BT glitches on XPS 15 9530; kernel cmdline whitelist on 26.04 blocks i915.enable_psr=0 workaround Status in linux package in Ubuntu: New Bug description: == Hardware == - Dell XPS 15 9530 (BIOS 1.29.0) - iGPU: Intel Raptor Lake-P [Iris Xe Graphics] (device ID a7a0, integrated display version 13.00 stepping E0) - dGPU: NVIDIA RTX 4060 Max-Q (Optimus, displays driven by iGPU) - Connected: internal eDP-1 panel (PSR1 capable) + 2x DisplayPort over Dell Thunderbolt Dock == Software == - Ubuntu Desktop 26.04, snap model `ubuntu-classic-2604-amd64`, grade `signed` (FDE Enhanced, TPM-sealed LUKS) - Kernel: 7.0.0-15-generic (pc-kernel snap rev 3419, channel 26.04/stable) - Bootloader: systemd-boot via signed kernel.efi from pc-kernel snap (Secure Boot + kernel lockdown active) == Symptom == Recurring display flicker on the eDP panel together with simultaneous USB re-enumeration ("clink-clong" sound on the Dell TB Dock), USB audio interruption, and brief Bluetooth (hci0) drop. Episodes last ~1 second and repeat several times per day, more frequently when the dGPU activates (e.g. Steam/PRIME render offload). PSR debug status during the glitch shows the panel stuck in SRDENT (Self-Refresh Data Enable) with very high transition rate; counter rises ~500/s. State returns to IDLE when the symptom resolves: Source PSR/PanelReplay status: SRDENT [0x400f0009] (during glitch) Source PSR/PanelReplay status: IDLE [0x040b0001] (resolved) This matches Dell's documented hardware issue for the XPS 15 9530 panel ("LCD Screen on the XPS 15 9530 Randomly Flickers", KB 000218908) where Dell themselves recommend disabling PSR in the Intel Graphics Command Center on Windows. Was not happening on Ubuntu 24.04 with kernel 6.x — regression introduced by the move to kernel 7.0 and/or pc-kernel snap on 26.04. == Standard workaround is blocked == The well-known workaround `i915.enable_psr=0` cannot be applied on 26.04 with the current setup: 1. /etc/default/grub does not exist / is not consumed (snap-managed kernel cmdline). 2. `snap set system system.kernel.cmdline-append="i915.enable_psr=0"` fails with: "i915.enable_psr=0" is not allowed in the kernel command line by the gadget The pc gadget snap (rev 220) gadget.yaml whitelist only permits `quiet` and `splash`. 3. `system.kernel.dangerous-cmdline-append` is not usable: requires model grade `dangerous`. This system is grade `signed` (Enhanced FDE). 4. /etc/modprobe.d/i915-disable-psr.conf with `options i915 enable_psr=0` is ignored: i915 loads from the initrd embedded in kernel.efi (signed) before the encrypted rootfs is mounted, so the local modprobe.d is never consulted. Verified by reboot test (enable_psr stays at -1). 5. /sys/module/i915/parameters/enable_psr* are read-only at runtime (mode 0400 root, write returns Permission denied even with sudo). 6. /sys/kernel/debug/dri/.../i915_edp_psr_debug write is blocked by kernel lockdown (Secure Boot). Net result: a user with `signed` Enhanced FDE on this hardware has no supported way to disable a known-buggy display feature. == Request == Either: (a) Add the well-known display-related i915 parameters (i915.enable_psr, i915.enable_fbc, i915.enable_psr2_sel_fetch, i915.enable_dc) to the kernel-cmdline allow list of the `pc` gadget snap, so users on `signed` FDE Enhanced systems can apply standard hardware workarounds; or (b) Quirk-disable PSR in the i915 driver for the Dell XPS 15 9530 panel (and similar panels with documented Dell-side PSR issues), in line with Dell's own Windows guidance. == Related == - LP #2065096 — i915 Display is Laggy/Unresponsive when PSR is enabled (Dell Latitude 7430/9430, same root cause, 24.04 / kernel 6.8). Workaround there is i915.enable_psr=0 in GRUB — that escape hatch no longer exists on 26.04 with `signed` FDE. - Dell KB 000218908 — XPS 15 9530 random flickering, recommends disabling PSR. - Discourse: "The pc-kernel snap on 26.04 prevents users from installing additional firmware" — same family of customisation lock-out issues on 26.04. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic (not installed) ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 9 22:18:19 2026 IwDevWlp0s20f3Link: Not connected. MachineType: Dell Inc. XPS 15 9530 ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: snapd_recovery_mode=run console=ttyS0,115200n8 console=tty1 panic=-1 quiet splash snapd.xkb="es,pc105,," SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2025 dmi.bios.release: 1.29 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.29.0 dmi.board.name: 0P6GXD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnDellInc.:bvr1.29.0:bd12/24/2025:br1.29:efr1.17:svnDellInc.:pnXPS159530:pvr:rvnDellInc.:rn0P6GXD:rvrA00:cvnDellInc.:ct10:cvr:sku0BEB:pfaXPS: dmi.product.family: XPS dmi.product.name: XPS 15 9530 dmi.product.sku: 0BEB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152105/+subscriptions
[Bug 2150769] Re: There is a conflict between the pc-kernel snap and additional firmware packages
** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150769 Title: There is a conflict between the pc-kernel snap and additional firmware packages Status in linux package in Ubuntu: Confirmed Status in linux-firmware-intel-wireless package in Ubuntu: Confirmed Bug description: I described in detail here, in case I miss anything in this description: https://discourse.ubuntu.com/t/the-pc-kernel-snap- on-26-04-prevents-users-from-installing-additional-firmware/81404 This bug report is pretty wordy so here's a top-line summary: 1. The pc-kernel snap uses an unfortunately unreliable method of including firmware, which means some firmware gets missed 2. The apt dependencies of `boot-managed-by-snapd` preclude installing `linux-firmware` but do not preclude installing any other firmware packages making it possible to break your system in a pretty dramatic way that many users might have a very difficult time figuring out or resolving. Reproduction steps: 1. Install Ubuntu using the `pc-kernel` snap rather than apt kernel packages 2. Install the `linux-firmware-intel-wireless` package Okay, now on to the verbose part of the bug report which I hope is at least partially understandable. Circumstance: 1. I'm running Ubuntu 26.04 using the pc-kernel snapo (because of hardware FDE I guess) 2. My laptop has a pretty new Arrow Lake chipset with an Intel wifi adapter 3. My wifi doesn't work What I discovered while debugging: the `iwlwifi` module won't load properly because it can't find the firmware file it wants, as it is not present in the `pc-kernel` snap, so wifi doesn't work. This took me in a few different directions and this is what I found: * Unspecified incompatibility between pc-kernel and additional firmware packages First, the pc-kernel snap creates symlinks to everything in its 'firmware' directory into the filesystem that gets mounted at /usr/lib/firmware, but it links everything at the top-level. That means firmware can be added to e.g. /usr/lib/firmware/somefile.fw, because that's a directory, but not /usr/lib/firmware/intel/somefile.fw because /usr/lib/firmware/intel is a symlink to a directory on the squashfs filesystem. This means that installing the `linux-firmware-intel-wireless` package, which has the firmware I need: 1. Breaks when trying to install because it tries to write some files to /usr/lib/firmware/intel/ 2. Refuses to uninstall until it's installed correctly, because dpkg recognizes it as being in an extremely broken state. I say 'unspecified' because `boot-managed-by-snapd` explicitly conflicts with `linux-firmware` (showing the intention to not allow both at once), but it does not conflict with any additional firmware packages. * Incomplete firmware inventory in the pc-kernel snap I dug into it a bit and found that the pc-kernel snap builds using the following steps: 1. Get the kernel and the modules together 2. Ask each module what firmware it wants (via `modinfo`) 3. Bundle those firmwares into the pc-kernel snap Unfortunately, for whatever reason, the `iwlwifi` firmware does not specify the firmware that my system seems to insist on, which is `bz-b0-fm-c0-c101.ucode`, so it does not get included into the pc- kernel snap. The `linux-firmware-intel-wireless` debian package *does* include this firmware, presumably because it just includes all available Intel wireless firmware unconditionally. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic (not installed) ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: dan 6392 F.... wireplumber /dev/snd/controlC1: dan 6392 F.... wireplumber /dev/snd/controlC0: dan 6392 F.... wireplumber /dev/snd/seq: dan 6354 F.... pipewire CasperMD5CheckMismatches: ./EFI/boot/bootx64.efi ./EFI/boot/grubx64.efi ./EFI/boot/mmx64.efi CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 10:29:41 2026 MachineType: Dell Inc. Dell Pro Max 14 Premium MA14250 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/zsh TERM=xterm-ghostty XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: snapd_recovery_mode=run console=ttyS0,115200n8 console=tty1 panic=-1 quiet splash snapd.xkb="us,pc105,," RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2025 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 06XRHN dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd12/11/2025:br1.7:efr1.6:svnDellInc.:pnDellProMax14PremiumMA14250:pvr:rvnDellInc.:rn06XRHN:rvrA02:cvnDellInc.:ct10:cvr:sku0D32:pfaDellProMaxLaptops: dmi.product.family: Dell Pro Max Laptops dmi.product.name: Dell Pro Max 14 Premium MA14250 dmi.product.sku: 0D32 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150769/+subscriptions
пятница
[Bug 2150621] Re: regression: booting instability and large variance in booting success
as mentioned above, in the meantime i observe the same behavior also on another similar thinkpad (e14 gen 6, ryzen 5, radeon). i am attaching an unsuccessful appearance of the gdm greeter and one successful one, in case the diff will give you any hints of where the race condition might be. ** Attachment added: "journal of the unsuccessful gmd start with kernel 7.0.0-15" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150621/+attachment/5968964/+files/journal-wilmon-failed_gdm_start-linux-7.0.0-15.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150621 Title: regression: booting instability and large variance in booting success Status in linux package in Ubuntu: New Bug description: fresh install of ubuntu 26.04 from the installation media works fine and flawlessly. the laptop (thinkpad e14 gen 6, ryzen 5, radeon) boots fine each time etc. but as soon as i install our usual set of packages, which includes xfce4, all hell breaks loose. xfce4 namely pulls in lightdm and even when gdb3 is chosen over it, i observe the following spiral of events: first boot after a reboot is usually fine. second boot usually gets hung on a "underscore screen of death" where only a single underscore is shown in the upper left corner and the rest is just a black screen. the kernel is still running since ctrl- alt-del works and also REISUB but one cannot do anything else with it, ie no linux console accessible. so the booting usually does not go beyond the third time. i say "usually" since to triage the problem i have now made a fresh install of ubuntu already for the 11th time. always the same story. vanilla install works fine. as soon as (i guess non-wayland x11 stuff is installed) the booting experience is very different each time and finally fails. sometimes instead of the underscore screen i end up with a message about kdump-tools being started and ucsi_acpi USBC000:00: error -ETIMEOUT: PPM failed, but sometimes not. btw, i had to remove "splash" from the kernel options to see this stuff, with splash running the boots end up either spinning for ever, or with underscore black screen, or simply frozen spinner, which unfreezes on ctrl-alt-del and spews out all the shutdown messages. this has been very frustrating indeed, but with this laptop there were glimpses of this starting already with ubuntu 25.04 and then also in 25.10. what helped there was simply to disconnect the thinkpad docking station for boot and connect it back when fully booted and the gdm3 login appears. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 09:42:06 2026 InstallationDate: Installed on 2026-04-28 (1 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp2s0Link: Not connected. MachineType: LENOVO 21M3002TGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-14-generic root=UUID=28776a6c-f402-431c-ba0d-61e0053cdb0e ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2025 dmi.bios.release: 1.16 dmi.bios.vendor: LENOVO dmi.bios.version: R2KET33W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 21M3002TGE dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrR2KET33W(1.16):bd05/09/2025:br1.16:efr1.16:svnLENOVO:pn21M3002TGE:pvrThinkPadE14Gen6:rvnLENOVO:rn21M3002TGE:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21M3_BU_Think_FM_ThinkPadE14Gen6:pfaThinkPadE14Gen6: dmi.product.family: ThinkPad E14 Gen 6 dmi.product.name: 21M3002TGE dmi.product.sku: LENOVO_MT_21M3_BU_Think_FM_ThinkPad E14 Gen 6 dmi.product.version: ThinkPad E14 Gen 6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150621/+subscriptions
[Bug 2151842] Re: aa-rootns.c bypasses apparmor_restrict_unprivileged_userns
** No longer affects: linux (Ubuntu) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2151842 Title: aa-rootns.c bypasses apparmor_restrict_unprivileged_userns Status in AppArmor: New Status in apparmor package in Ubuntu: New Bug description: Please find a way to stop https://github.com/0xdeadbeefnetwork/Copy_Fail2-Electric_Boogaloo/blob/main/aa- rootns.c from working. See also https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/2151831 but the apparmor_restrict_unprivileged_userns bypass is separate from the copy.fail or dirty frag vulnerabilities. This doesn't affect me because I disabled that sysctl to make unshare work, but a fix would reduce the attack surface for others. If a fix isn't readily available, then please disable that sysctl to reduce inconvenience and the illusion of security. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2151842/+subscriptions
[Bug 2152056] [NEW] Lenovo Legion Y9000P IAX10 (17aa:3907) speakers - missing AW88399 amp quirk
Public bug reported: Lenovo Legion Y9000P IAX10, ALC287 + AW88399 amplifier PCI SSID: 17aa:3907 dmesg: "ALC287: picked fixup for PCI SSID 17aa:0000" (no specific quirk match) Result: bottom 2 speakers (woofers) silent, only top tweeters audible Existing patch (not yet upstream): https://github.com/nadimkobeissi/16iax10h-linux-sound-saga ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152056 Title: Lenovo Legion Y9000P IAX10 (17aa:3907) speakers - missing AW88399 amp quirk Status in linux package in Ubuntu: New Bug description: Lenovo Legion Y9000P IAX10, ALC287 + AW88399 amplifier PCI SSID: 17aa:3907 dmesg: "ALC287: picked fixup for PCI SSID 17aa:0000" (no specific quirk match) Result: bottom 2 speakers (woofers) silent, only top tweeters audible Existing patch (not yet upstream): https://github.com/nadimkobeissi/16iax10h-linux-sound-saga To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152056/+subscriptions
[Bug 2138991] Re: Dell 16 Premium DA16250 webcam (OV02C10) not working - INT3472 GPIO type 0x02 unknown
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ipu6-drivers (Ubuntu Noble) Status: New => Confirmed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2138991 Title: Dell 16 Premium DA16250 webcam (OV02C10) not working - INT3472 GPIO type 0x02 unknown Status in ipu6-drivers package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in ipu6-drivers source package in Noble: Confirmed Status in linux source package in Noble: Confirmed Bug description: ## Description ### Summary The integrated webcam on Dell 16 Premium (DA16250) with Intel Meteor Lake CPU does not work on Ubuntu 24.04 with OEM kernel. The camera sensor (OV02C10) is detected but fails to initialize due to unsupported GPIO type 0x02 in the INT3472 discrete driver. ### System Information - **Hardware:** Dell 16 Premium DA16250 - **CPU:** Intel Core Ultra 9 285H (Meteor Lake) - **Camera Sensor:** OmniVision OV02C10 (ACPI: OVTI02C1:00) - **OS:** Ubuntu 24.04.3 LTS - **Kernel:** 6.14.0-1019-oem ### Steps to Reproduce 1. Install Ubuntu 24.04 on Dell 16 Premium DA16250 2. Install OEM kernel: `sudo apt install linux-oem-24.04` 3. Install IPU6 modules: `sudo apt install linux-modules-ipu6-6.14.0-1019-oem` 4. Install camera HAL: `sudo apt install libcamhal-ipu6epmtl` (from OEM PPA) 5. Reboot and try to use the webcam ### Expected Behavior Webcam should be detected and functional in applications like Cheese, Firefox, Chromium. ### Actual Behavior Camera is detected by the IPU6 driver but fails to initialize. The sensor does not register in the media pipeline. ### Error Messages (from dmesg) ``` int3472-discrete INT3472:0c: GPIO type 0x02 unknown; the sensor may not work intel-ipu6 0000:00:05.0: Found supported sensor OVTI02C1:00 intel-ipu6 0000:00:05.0: Connected 1 cameras ``` ### Error Messages (from GStreamer test) ``` CamHAL[INF] aiqb file name AR0234_TGL_10bits.aiqb CamHAL[ERR] Stream config is not supported. format:V4L2_PIX_FMT_NV12 (1920x1080) ``` The camera HAL loads the wrong config file (AR0234 instead of OV02C10) because the sensor is not bound to the I2C bus. ### Diagnosis The ov02c10 kernel module is loaded but not bound to any device: ``` $ ls /sys/bus/i2c/drivers/ov02c10/ bind module uevent unbind ``` The ACPI device exists and is enabled (status 15): ``` $ cat /sys/bus/acpi/devices/OVTI02C1:00/status 15 ``` But there is no physical_node because the INT3472 GPIO initialization fails. ### Root Cause GPIO type 0x02 is a "strobe" GPIO used for LED/IR control on Meteor Lake systems. The int3472-discrete driver does not recognize this GPIO type, preventing proper camera power-up. ### Existing Kernel Patch A patch exists that adds support for GPIO type 0x02 (strobe): https://patchwork.kernel.org/project/linux-media/patch/20231007021309.9332-1-hao.yao@intel.com/ ### Related Issues - Intel IPU6 drivers: https://github.com/intel/ipu6-drivers/issues/413 - Intel IPU6 drivers: https://github.com/intel/ipu6-drivers/issues/40 - Ubuntu Bug #2117188: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2117188 ### Workarounds Attempted (None Successful) 1. Added `intel_iommu=on` to kernel parameters 2. Fixed /dev/ipu-psys0 permissions with udev rules 3. Installed libcamhal-ipu6epmtl from OEM PPA 4. Tried Dell OEM archive packages ### Request Please backport the INT3472 GPIO strobe patch to the Ubuntu OEM kernel to support Dell 16 Premium and other Meteor Lake laptops with OV02C10 cameras. ## Attachments ### uname -a ``` Linux Dell-16-Premium-DA16250 6.14.0-1019-oem #19-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 18 05:40:21 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux ``` ### CPU Info ``` vendor_id : GenuineIntel cpu family : 6 model : 197 model name : Intel(R) Core(TM) Ultra 9 285H ``` ### lspci (IPU6 device) ``` 0000:00:05.0 Multimedia controller [0480]: Intel Corporation Device [8086:7d19] (rev 05) Subsystem: Dell Device [1028:0ce7] Flags: bus master, fast devsel, latency 0, IRQ 16, IOMMU group 3 Memory at 581c000000 (64-bit, non-prefetchable) [size=16M] Kernel driver in use: intel-ipu6 Kernel modules: intel_ipu6 ``` ### dmesg (camera related) ``` [ 16.744854] int3472-discrete INT3472:0c: GPIO type 0x02 unknown; the sensor may not work [ 16.764935] intel-ipu6 0000:00:05.0: enabling device (0000 -> 0002) [ 16.781627] intel-ipu6 0000:00:05.0: Found supported sensor OVTI02C1:00 [ 16.781717] intel-ipu6 0000:00:05.0: Connected 1 cameras [ 16.784617] intel-ipu6 0000:00:05.0: Sending BOOT_LOAD to CSE [ 16.821495] intel-ipu6 0000:00:05.0: Sending AUTHENTICATE_RUN to CSE [ 16.879001] intel-ipu6 0000:00:05.0: CSE authenticate_run done [ 16.879013] intel-ipu6 0000:00:05.0: IPU6-v4[7d19] hardware version 6 [ 17.565317] intel_ipu6_psys.psys intel_ipu6.psys.40: pkg_dir entry count:8 [ 17.565808] intel_ipu6_psys.psys intel_ipu6.psys.40: psys probe minor: 0 [ 2663.927955] intel-ipu6 0000:00:05.0: IPU6 in secure mode [ 7592.628584] intel-ipu6 0000:00:05.0: IPU6 in secure mode ``` ### Installed packages (camera related) ``` ii gstreamer1.0-icamera 0~git202509260937.4fb31db~ubuntu24.04.7 amd64 ii libcamhal-common 0~git202601200757.9899efa~ubuntu24.04.1 all ii libcamhal-ipu6ep 0~git202601200757.9899efa~ubuntu24.04.1 amd64 ii libcamhal-ipu6epmtl 0~git202601200757.9899efa~ubuntu24.04.1 amd64 ii libcamhal0 0~git202601200757.9899efa~ubuntu24.04.1 amd64 ii linux-image-6.14.0-1019-oem 6.14.0-1019.19 amd64 ii linux-image-6.14.0-37-generic 6.14.0-37.37~24.04.1 amd64 ii linux-image-generic-hwe-24.04 6.14.0-37.37~24.04.1 amd64 ii linux-image-oem-24.04 6.14.0-1019.19 amd64 ii linux-modules-6.14.0-1019-oem 6.14.0-1019.19 amd64 ii linux-modules-6.14.0-37-generic 6.14.0-37.37~24.04.1 amd64 ii linux-modules-extra-6.14.0-37-generic 6.14.0-37.37~24.04.1 amd64 ii linux-modules-ipu6-6.14.0-1019-oem 6.14.0-1019.19 amd64 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2138991/+subscriptions