I have updated my system today. The kernel was upgraded from
6.17.0-8-generic to 6.17.0-14-generic. After the update and a reboot,
the touchpad no longer freezes after periods of inactivity. The issue
appears to be completely resolved in this kernel version. Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142386
Title:
Touchpad SYNA3602:00 stops responding to movement after 5-10 minutes
of inactivity (kernel 6.17.0-8-generic)
Status in linux package in Ubuntu:
New
Bug description:
After upgrading to Ubuntu 25.10 with kernel 6.17.0-8-generic, the
built-in touchpad (SYNA3602:00 093A:0255) stops responding to movement
after about 5-10 minutes of inactivity.
Symptoms:
- Touching the pad wakes up the screen (backlight turns on), but the cursor does not move
- Physical clicks on the touchpad stop working
- Tap-to-click (сенсорный клик) still works
- Only a full system reboot restores functionality
What I've observed:
- `libinput debug-events` shows NO events when moving finger on dead touchpad
- Device is still visible in `libinput list-devices` with correct capabilities
- This is a regression — did not happen on previous Ubuntu versions (24.10, 24.04)
Hardware:
- Laptop: KVADRA NAU LE14U
- Touchpad: SYNA3602:00 093A:0255 (I2C HID v1.00)
- Kernel: 6.17.0-8-generic
- Ubuntu: 25.10
Steps to reproduce:
1. Boot Ubuntu 25.10 with kernel 6.17.0-8-generic
2. Do not touch the touchpad for 5-10 minutes
3. Try to move the cursor — it does not respond
4. Only reboot fixes the issue temporarily
Expected behavior:
Touchpad should remain functional after periods of inactivity.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142386/+subscriptions
воскресенье
[Bug 2141216] Re: Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT (andgpu SMU resume failure)
Did you run update grub after changing?
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141216
Title:
Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT
(andgpu SMU resume failure)
Status in linux package in Ubuntu:
New
Status in linux source package in Questing:
Triaged
Bug description:
Summary: Suspend/resume broken after latest Ubuntu update on AMD RX
What Happens: After suspend, system wakes but display remains black. VT switching (Ctrl–Alt–F3) does not work. Only hard reboot recovers.
Regression: This started immediately after a recent Ubuntu update
Hardware: AMD RX 960 XT (Nav 44) + AMD Raphael iGPU
Relevant logs: SMU resume failure. GPU ring timeouts, GPU ring timeouts, devcoredump created (already captured by ubuntu-bug tool)
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-12-generic 6.17.0-12.12
ProcVersionSignature: Ubuntu 6.17.0-12.12-generic 6.17.2
Uname: Linux 6.17.0-12-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 7 17:54:17 2026
InstallationDate: Installed on 2025-10-20 (110 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: ASUS System Product Name
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-12-generic root=UUID=3412c7b3-e116-4927-b603-3da7641a647b ro quiet splash mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2025
dmi.bios.release: 32.65
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3265
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B650E-E WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3265:bd06/11/2025:br32.65:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650E-EWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141216/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141216
Title:
Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT
(andgpu SMU resume failure)
Status in linux package in Ubuntu:
New
Status in linux source package in Questing:
Triaged
Bug description:
Summary: Suspend/resume broken after latest Ubuntu update on AMD RX
What Happens: After suspend, system wakes but display remains black. VT switching (Ctrl–Alt–F3) does not work. Only hard reboot recovers.
Regression: This started immediately after a recent Ubuntu update
Hardware: AMD RX 960 XT (Nav 44) + AMD Raphael iGPU
Relevant logs: SMU resume failure. GPU ring timeouts, GPU ring timeouts, devcoredump created (already captured by ubuntu-bug tool)
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-12-generic 6.17.0-12.12
ProcVersionSignature: Ubuntu 6.17.0-12.12-generic 6.17.2
Uname: Linux 6.17.0-12-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 7 17:54:17 2026
InstallationDate: Installed on 2025-10-20 (110 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: ASUS System Product Name
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-12-generic root=UUID=3412c7b3-e116-4927-b603-3da7641a647b ro quiet splash mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2025
dmi.bios.release: 32.65
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3265
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B650E-E WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3265:bd06/11/2025:br32.65:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650E-EWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141216/+subscriptions
[Bug 2141216] Re: Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT (andgpu SMU resume failure)
Mario:
Good point. No I did not, so I nano'd my way back from:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=s2idle" to:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
I also hadn't removed 6.17.0-15-generic #15afaina1-Ubuntu, and since I
now automatically go to the GRUB menu when I re-start and can select the
kernel I want, I went back to the test kernel and forced another
suspend. Still didn't resume I'm afraid. I'm back on -14 now because
of the ethernet issue, but am willing to switch if there is something
else useful you guys would like me to test.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141216
Title:
Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT
(andgpu SMU resume failure)
Status in linux package in Ubuntu:
New
Status in linux source package in Questing:
Triaged
Bug description:
Summary: Suspend/resume broken after latest Ubuntu update on AMD RX
What Happens: After suspend, system wakes but display remains black. VT switching (Ctrl–Alt–F3) does not work. Only hard reboot recovers.
Regression: This started immediately after a recent Ubuntu update
Hardware: AMD RX 960 XT (Nav 44) + AMD Raphael iGPU
Relevant logs: SMU resume failure. GPU ring timeouts, GPU ring timeouts, devcoredump created (already captured by ubuntu-bug tool)
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-12-generic 6.17.0-12.12
ProcVersionSignature: Ubuntu 6.17.0-12.12-generic 6.17.2
Uname: Linux 6.17.0-12-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 7 17:54:17 2026
InstallationDate: Installed on 2025-10-20 (110 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: ASUS System Product Name
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-12-generic root=UUID=3412c7b3-e116-4927-b603-3da7641a647b ro quiet splash mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2025
dmi.bios.release: 32.65
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3265
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B650E-E WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3265:bd06/11/2025:br32.65:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650E-EWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141216/+subscriptions
Good point. No I did not, so I nano'd my way back from:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=s2idle" to:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
I also hadn't removed 6.17.0-15-generic #15afaina1-Ubuntu, and since I
now automatically go to the GRUB menu when I re-start and can select the
kernel I want, I went back to the test kernel and forced another
suspend. Still didn't resume I'm afraid. I'm back on -14 now because
of the ethernet issue, but am willing to switch if there is something
else useful you guys would like me to test.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141216
Title:
Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT
(andgpu SMU resume failure)
Status in linux package in Ubuntu:
New
Status in linux source package in Questing:
Triaged
Bug description:
Summary: Suspend/resume broken after latest Ubuntu update on AMD RX
What Happens: After suspend, system wakes but display remains black. VT switching (Ctrl–Alt–F3) does not work. Only hard reboot recovers.
Regression: This started immediately after a recent Ubuntu update
Hardware: AMD RX 960 XT (Nav 44) + AMD Raphael iGPU
Relevant logs: SMU resume failure. GPU ring timeouts, GPU ring timeouts, devcoredump created (already captured by ubuntu-bug tool)
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-12-generic 6.17.0-12.12
ProcVersionSignature: Ubuntu 6.17.0-12.12-generic 6.17.2
Uname: Linux 6.17.0-12-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 7 17:54:17 2026
InstallationDate: Installed on 2025-10-20 (110 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: ASUS System Product Name
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-12-generic root=UUID=3412c7b3-e116-4927-b603-3da7641a647b ro quiet splash mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2025
dmi.bios.release: 32.65
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3265
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B650E-E WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3265:bd06/11/2025:br32.65:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650E-EWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141216/+subscriptions
[Bug 2142389] Re: amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot
Título: Suspensão da AMDGPU → tela preta/sem vídeo após retomada na
Radeon R9 380 (sem leitura de EDID)
Resumo:
Após a suspensão do sistema no Zorin OS 18 (baseado no Ubuntu 24.10, kernel 6.17.0-14), o sistema às vezes retoma, mas a tela permanece preta (sem sinal). O sistema continua funcionando (ventoinhas/LEDs ativos), mas o monitor não exibe imagem. Somente uma reinicialização forçada restaura o vídeo.
Passos para reproduzir:
Inicie o Zorin OS 18 (Ubuntu 24.10, kernel 6.17).
Suspenda o sistema (por exemplo, pelo menu "Suspender" do GNOME).
Aguarde um curto período.
Tente retomar (mouse/teclado).
O sistema desperta, mas a tela exibe vídeo distorcido ou nenhuma imagem.
Comportamento observado:
O sistema parece não ter travado (ventoinhas/LEDs/teclado continuam
funcionando).
A tela permanece preta ou exibe resquícios, mas nenhum vídeo utilizável.
Às vezes, a retomada funciona, outras vezes falha.
Trecho relevante do log:
amdgpu 0000:01:00.0: [drm] *ERRO* Nenhum EDID lido.
Hardware:
Placa-mãe: Gigabyte B450 AORUS PRO WIFI
CPU: AMD Ryzen 5 5500
GPU: AMD Radeon R9 380 Series (Tonga, driver amdgpu)
Ambiente de software:
Zorin OS 18 Core (baseado no Ubuntu 24.10)
Kernel: 6.17.0-14-generic
Sessão X11
Solução alternativa aplicada atualmente:
Suspensão desativada. O sistema permanece estável sem a suspensão.
Observação: O bug parece estar relacionado à retomada do vídeo, e não ao
congelamento do sistema; o subsistema de exibição (handshake EDID) pode
falhar após a suspensão.
Informações adicionais:
Existem relatos semelhantes de problemas de tela preta/suspensão em GPUs AMD (por exemplo, Launchpad #2141216) e discussões na comunidade sobre a retomada da tela preta após a suspensão em GPUs AMD.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142389
Title:
amdgpu (R9 380) fails to resume from suspend (deep sleep) – black
screen, requires hard reboot
Status in linux package in Ubuntu:
New
Bug description:
AMDGPU suspend → display black / no video after resume on Radeon R9
380 (No EDID read)
Summary:
After system suspend from Zorin OS 18 (Ubuntu 24.10 base, kernel 6.17.0-14), the system sometimes resumes but the display remains black (no signal). System continues running (fans/LEDs active), but monitor shows no output. Only hard reboot restores video.
Steps to reproduce:
Boot Zorin OS 18 (Ubuntu 24.10 kernel 6.17).
Suspend system (e.g., via GNOME "Suspend").
Wait short period.
Attempt to resume (mouse/keyboard).
System wakes but display either shows garbled video or no output.
Observed behavior:
System appears not crashed (fans/LEDs/keyboard continue).
Screen stays black or displays remnants but no usable video.
Sometimes resume works, sometimes fails.
Relevant log excerpt:
amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read.
Hardware:
Motherboard: Gigabyte B450 AORUS PRO WIFI
CPU: AMD Ryzen 5 5500
GPU: AMD Radeon R9 380 Series (Tonga, amdgpu driver)
Software environment:
Zorin OS 18 Core (Ubuntu 24.10 base)
kernel: 6.17.0-14-generic
X11 session
Workaround currently applied:
Suspend disabled. System remains stable without suspend.
Note: Bug appears related to video resume rather than system freeze;
display subsystem (EDID handshake) may fail after suspend.
Additional info:
Similar reports of amdgpu black screen / suspend issues exist (e.g., Launchpad #2141216) and community discussions on black screen resume after suspend for AMD GPUs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142389/+subscriptions
Radeon R9 380 (sem leitura de EDID)
Resumo:
Após a suspensão do sistema no Zorin OS 18 (baseado no Ubuntu 24.10, kernel 6.17.0-14), o sistema às vezes retoma, mas a tela permanece preta (sem sinal). O sistema continua funcionando (ventoinhas/LEDs ativos), mas o monitor não exibe imagem. Somente uma reinicialização forçada restaura o vídeo.
Passos para reproduzir:
Inicie o Zorin OS 18 (Ubuntu 24.10, kernel 6.17).
Suspenda o sistema (por exemplo, pelo menu "Suspender" do GNOME).
Aguarde um curto período.
Tente retomar (mouse/teclado).
O sistema desperta, mas a tela exibe vídeo distorcido ou nenhuma imagem.
Comportamento observado:
O sistema parece não ter travado (ventoinhas/LEDs/teclado continuam
funcionando).
A tela permanece preta ou exibe resquícios, mas nenhum vídeo utilizável.
Às vezes, a retomada funciona, outras vezes falha.
Trecho relevante do log:
amdgpu 0000:01:00.0: [drm] *ERRO* Nenhum EDID lido.
Hardware:
Placa-mãe: Gigabyte B450 AORUS PRO WIFI
CPU: AMD Ryzen 5 5500
GPU: AMD Radeon R9 380 Series (Tonga, driver amdgpu)
Ambiente de software:
Zorin OS 18 Core (baseado no Ubuntu 24.10)
Kernel: 6.17.0-14-generic
Sessão X11
Solução alternativa aplicada atualmente:
Suspensão desativada. O sistema permanece estável sem a suspensão.
Observação: O bug parece estar relacionado à retomada do vídeo, e não ao
congelamento do sistema; o subsistema de exibição (handshake EDID) pode
falhar após a suspensão.
Informações adicionais:
Existem relatos semelhantes de problemas de tela preta/suspensão em GPUs AMD (por exemplo, Launchpad #2141216) e discussões na comunidade sobre a retomada da tela preta após a suspensão em GPUs AMD.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142389
Title:
amdgpu (R9 380) fails to resume from suspend (deep sleep) – black
screen, requires hard reboot
Status in linux package in Ubuntu:
New
Bug description:
AMDGPU suspend → display black / no video after resume on Radeon R9
380 (No EDID read)
Summary:
After system suspend from Zorin OS 18 (Ubuntu 24.10 base, kernel 6.17.0-14), the system sometimes resumes but the display remains black (no signal). System continues running (fans/LEDs active), but monitor shows no output. Only hard reboot restores video.
Steps to reproduce:
Boot Zorin OS 18 (Ubuntu 24.10 kernel 6.17).
Suspend system (e.g., via GNOME "Suspend").
Wait short period.
Attempt to resume (mouse/keyboard).
System wakes but display either shows garbled video or no output.
Observed behavior:
System appears not crashed (fans/LEDs/keyboard continue).
Screen stays black or displays remnants but no usable video.
Sometimes resume works, sometimes fails.
Relevant log excerpt:
amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read.
Hardware:
Motherboard: Gigabyte B450 AORUS PRO WIFI
CPU: AMD Ryzen 5 5500
GPU: AMD Radeon R9 380 Series (Tonga, amdgpu driver)
Software environment:
Zorin OS 18 Core (Ubuntu 24.10 base)
kernel: 6.17.0-14-generic
X11 session
Workaround currently applied:
Suspend disabled. System remains stable without suspend.
Note: Bug appears related to video resume rather than system freeze;
display subsystem (EDID handshake) may fail after suspend.
Additional info:
Similar reports of amdgpu black screen / suspend issues exist (e.g., Launchpad #2141216) and community discussions on black screen resume after suspend for AMD GPUs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142389/+subscriptions
[Bug 2142389] [NEW] amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot
Public bug reported:
AMDGPU suspend → display black / no video after resume on Radeon R9 380
(No EDID read)
Summary:
After system suspend from Zorin OS 18 (Ubuntu 24.10 base, kernel 6.17.0-14), the system sometimes resumes but the display remains black (no signal). System continues running (fans/LEDs active), but monitor shows no output. Only hard reboot restores video.
Steps to reproduce:
Boot Zorin OS 18 (Ubuntu 24.10 kernel 6.17).
Suspend system (e.g., via GNOME "Suspend").
Wait short period.
Attempt to resume (mouse/keyboard).
System wakes but display either shows garbled video or no output.
Observed behavior:
System appears not crashed (fans/LEDs/keyboard continue).
Screen stays black or displays remnants but no usable video.
Sometimes resume works, sometimes fails.
Relevant log excerpt:
amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read.
Hardware:
Motherboard: Gigabyte B450 AORUS PRO WIFI
CPU: AMD Ryzen 5 5500
GPU: AMD Radeon R9 380 Series (Tonga, amdgpu driver)
Software environment:
Zorin OS 18 Core (Ubuntu 24.10 base)
kernel: 6.17.0-14-generic
X11 session
Workaround currently applied:
Suspend disabled. System remains stable without suspend.
Note: Bug appears related to video resume rather than system freeze;
display subsystem (EDID handshake) may fail after suspend.
Additional info:
Similar reports of amdgpu black screen / suspend issues exist (e.g., Launchpad #2141216) and community discussions on black screen resume after suspend for AMD GPUs.
** 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/2142389
Title:
amdgpu (R9 380) fails to resume from suspend (deep sleep) – black
screen, requires hard reboot
Status in linux package in Ubuntu:
New
Bug description:
AMDGPU suspend → display black / no video after resume on Radeon R9
380 (No EDID read)
Summary:
After system suspend from Zorin OS 18 (Ubuntu 24.10 base, kernel 6.17.0-14), the system sometimes resumes but the display remains black (no signal). System continues running (fans/LEDs active), but monitor shows no output. Only hard reboot restores video.
Steps to reproduce:
Boot Zorin OS 18 (Ubuntu 24.10 kernel 6.17).
Suspend system (e.g., via GNOME "Suspend").
Wait short period.
Attempt to resume (mouse/keyboard).
System wakes but display either shows garbled video or no output.
Observed behavior:
System appears not crashed (fans/LEDs/keyboard continue).
Screen stays black or displays remnants but no usable video.
Sometimes resume works, sometimes fails.
Relevant log excerpt:
amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read.
Hardware:
Motherboard: Gigabyte B450 AORUS PRO WIFI
CPU: AMD Ryzen 5 5500
GPU: AMD Radeon R9 380 Series (Tonga, amdgpu driver)
Software environment:
Zorin OS 18 Core (Ubuntu 24.10 base)
kernel: 6.17.0-14-generic
X11 session
Workaround currently applied:
Suspend disabled. System remains stable without suspend.
Note: Bug appears related to video resume rather than system freeze;
display subsystem (EDID handshake) may fail after suspend.
Additional info:
Similar reports of amdgpu black screen / suspend issues exist (e.g., Launchpad #2141216) and community discussions on black screen resume after suspend for AMD GPUs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142389/+subscriptions
AMDGPU suspend → display black / no video after resume on Radeon R9 380
(No EDID read)
Summary:
After system suspend from Zorin OS 18 (Ubuntu 24.10 base, kernel 6.17.0-14), the system sometimes resumes but the display remains black (no signal). System continues running (fans/LEDs active), but monitor shows no output. Only hard reboot restores video.
Steps to reproduce:
Boot Zorin OS 18 (Ubuntu 24.10 kernel 6.17).
Suspend system (e.g., via GNOME "Suspend").
Wait short period.
Attempt to resume (mouse/keyboard).
System wakes but display either shows garbled video or no output.
Observed behavior:
System appears not crashed (fans/LEDs/keyboard continue).
Screen stays black or displays remnants but no usable video.
Sometimes resume works, sometimes fails.
Relevant log excerpt:
amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read.
Hardware:
Motherboard: Gigabyte B450 AORUS PRO WIFI
CPU: AMD Ryzen 5 5500
GPU: AMD Radeon R9 380 Series (Tonga, amdgpu driver)
Software environment:
Zorin OS 18 Core (Ubuntu 24.10 base)
kernel: 6.17.0-14-generic
X11 session
Workaround currently applied:
Suspend disabled. System remains stable without suspend.
Note: Bug appears related to video resume rather than system freeze;
display subsystem (EDID handshake) may fail after suspend.
Additional info:
Similar reports of amdgpu black screen / suspend issues exist (e.g., Launchpad #2141216) and community discussions on black screen resume after suspend for AMD GPUs.
** 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/2142389
Title:
amdgpu (R9 380) fails to resume from suspend (deep sleep) – black
screen, requires hard reboot
Status in linux package in Ubuntu:
New
Bug description:
AMDGPU suspend → display black / no video after resume on Radeon R9
380 (No EDID read)
Summary:
After system suspend from Zorin OS 18 (Ubuntu 24.10 base, kernel 6.17.0-14), the system sometimes resumes but the display remains black (no signal). System continues running (fans/LEDs active), but monitor shows no output. Only hard reboot restores video.
Steps to reproduce:
Boot Zorin OS 18 (Ubuntu 24.10 kernel 6.17).
Suspend system (e.g., via GNOME "Suspend").
Wait short period.
Attempt to resume (mouse/keyboard).
System wakes but display either shows garbled video or no output.
Observed behavior:
System appears not crashed (fans/LEDs/keyboard continue).
Screen stays black or displays remnants but no usable video.
Sometimes resume works, sometimes fails.
Relevant log excerpt:
amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read.
Hardware:
Motherboard: Gigabyte B450 AORUS PRO WIFI
CPU: AMD Ryzen 5 5500
GPU: AMD Radeon R9 380 Series (Tonga, amdgpu driver)
Software environment:
Zorin OS 18 Core (Ubuntu 24.10 base)
kernel: 6.17.0-14-generic
X11 session
Workaround currently applied:
Suspend disabled. System remains stable without suspend.
Note: Bug appears related to video resume rather than system freeze;
display subsystem (EDID handshake) may fail after suspend.
Additional info:
Similar reports of amdgpu black screen / suspend issues exist (e.g., Launchpad #2141216) and community discussions on black screen resume after suspend for AMD GPUs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142389/+subscriptions
[Bug 2141985] Re: Dell Latitude5590 Ubuntu25.10中按下Super+L会睡眠且无法唤醒
我通过journalctl获取了一些日志，供分析参考，另外journalctl的-g选项报错"Failed to open files: 没有那个文件或目录"
larry-li@larry-li-Latitude-5590:~/text$ sudo journalctl --since "2026-02-13 0:00" --until "2026-02-22 0:00" --output=short-full | grep -iE "sleep|suspend|resume|wake|hibernate|thaw|freeze|standby|S3|S4|ACPI|PM|Dell|failure|error|timeout|hang" > sleep-range.log
larry-li@larry-li-Latitude-5590:~/text$ journalctl --version
systemd 257 (257.9-0ubuntu2.1)
+PAM +AUDIT +SELINUX +APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +BTF -XKBCOMMON -UTMP +SYSVINIT +LIBARCHIVE
larry-li@larry-li-Latitude-5590:~/text$
** Attachment added: "journalctl | grep 获取的睡眠相关日志，供分析睡眠问题和 journalctl -g 异常时参考"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141985/+attachment/5947744/+files/sleep-range.log
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141985
Title:
Dell Latitude5590 Ubuntu25.10中按下Super+L会睡眠且无法唤醒
Status in linux package in Ubuntu:
New
Bug description:
硬件型号：Dell Latitude 5590
系统版本：Ubuntu 25.10
内核版本：6.17.0-14-generic
问题描述：
执行 systemctl suspend、合盖后或按下 Super+L时，系统进入睡眠（效果类似于 shutdown -H now），黑屏且无法唤醒，只能长按电源键强制重启。
已尝试的修复措施：
更新 BIOS 到最新版本（通过 Dell 官网下载的 .rcv 文件更新）。
在GRUB内核参数中添加：
acpi_sleep=s3_mode acpi_sleep=s3_bios acpi_osi=Linux acpi_osi="!Windows 2020"
确认系统支持S3,cat /sys/power/state 输出包含 mem
larry-li@larry-li-Latitude-5590:~$ cat /sys/power/state
freeze mem
larry-li@larry-li-Latitude-5590:~$
附加信息：
该问题在同一电脑 Ubuntu 24.04、Ubuntu 25.10，内核 6.14或6.17上均存在，可能与 ACPI 实现有关，另外这台电脑是通过Ubuntu的启动盘装的系统，预装Windows 10，但已被Ubuntu替代。
相关日志已通过 ubuntu-bug linux 自动收集并附加。
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-14-generic 6.17.0-14.14
ProcVersionSignature: Ubuntu 6.17.0-14.14-generic 6.17.9
Uname: Linux 6.17.0-14-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: larry-li 2570 F.... wireplumber
/dev/snd/controlC1: larry-li 2570 F.... wireplumber
/dev/snd/seq: larry-li 2551 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 17 11:20:00 2026
InstallationDate: Installed on 2026-02-13 (4 days ago)
InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 046d:082b Logitech, Inc. Webcam C170
Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications
Bus 001 Device 004: ID 413c:301a Dell Computer Corp. Dell MS116 Optical Mouse
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: Dell Inc. Latitude 5590
ProcEnviron:
LANG=zh_CN.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-14-generic root=UUID=e880bf76-78c5-450e-b1aa-c147ded3f816 ro quiet splash acpi_sleep=s3_mode acpi_sleep=s3_bios acpi_osi=Linux "acpi_osi=!Windows 2020" crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: Upgraded to questing on 2026-02-16 (1 days ago)
dmi.bios.date: 04/09/2025
dmi.bios.release: 1.41
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.41.0
dmi.board.name: 0MM81M
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.41.0:bd04/09/2025:br1.41:svnDellInc.:pnLatitude5590:pvr:rvnDellInc.:rn0MM81M:rvrA00:cvnDellInc.:ct10:cvr:sku0817:
dmi.product.family: Latitude
dmi.product.name: Latitude 5590
dmi.product.sku: 0817
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141985/+subscriptions
larry-li@larry-li-Latitude-5590:~/text$ sudo journalctl --since "2026-02-13 0:00" --until "2026-02-22 0:00" --output=short-full | grep -iE "sleep|suspend|resume|wake|hibernate|thaw|freeze|standby|S3|S4|ACPI|PM|Dell|failure|error|timeout|hang" > sleep-range.log
larry-li@larry-li-Latitude-5590:~/text$ journalctl --version
systemd 257 (257.9-0ubuntu2.1)
+PAM +AUDIT +SELINUX +APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +BTF -XKBCOMMON -UTMP +SYSVINIT +LIBARCHIVE
larry-li@larry-li-Latitude-5590:~/text$
** Attachment added: "journalctl | grep 获取的睡眠相关日志，供分析睡眠问题和 journalctl -g 异常时参考"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141985/+attachment/5947744/+files/sleep-range.log
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141985
Title:
Dell Latitude5590 Ubuntu25.10中按下Super+L会睡眠且无法唤醒
Status in linux package in Ubuntu:
New
Bug description:
硬件型号：Dell Latitude 5590
系统版本：Ubuntu 25.10
内核版本：6.17.0-14-generic
问题描述：
执行 systemctl suspend、合盖后或按下 Super+L时，系统进入睡眠（效果类似于 shutdown -H now），黑屏且无法唤醒，只能长按电源键强制重启。
已尝试的修复措施：
更新 BIOS 到最新版本（通过 Dell 官网下载的 .rcv 文件更新）。
在GRUB内核参数中添加：
acpi_sleep=s3_mode acpi_sleep=s3_bios acpi_osi=Linux acpi_osi="!Windows 2020"
确认系统支持S3,cat /sys/power/state 输出包含 mem
larry-li@larry-li-Latitude-5590:~$ cat /sys/power/state
freeze mem
larry-li@larry-li-Latitude-5590:~$
附加信息：
该问题在同一电脑 Ubuntu 24.04、Ubuntu 25.10，内核 6.14或6.17上均存在，可能与 ACPI 实现有关，另外这台电脑是通过Ubuntu的启动盘装的系统，预装Windows 10，但已被Ubuntu替代。
相关日志已通过 ubuntu-bug linux 自动收集并附加。
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-14-generic 6.17.0-14.14
ProcVersionSignature: Ubuntu 6.17.0-14.14-generic 6.17.9
Uname: Linux 6.17.0-14-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: larry-li 2570 F.... wireplumber
/dev/snd/controlC1: larry-li 2570 F.... wireplumber
/dev/snd/seq: larry-li 2551 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 17 11:20:00 2026
InstallationDate: Installed on 2026-02-13 (4 days ago)
InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 046d:082b Logitech, Inc. Webcam C170
Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications
Bus 001 Device 004: ID 413c:301a Dell Computer Corp. Dell MS116 Optical Mouse
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: Dell Inc. Latitude 5590
ProcEnviron:
LANG=zh_CN.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-14-generic root=UUID=e880bf76-78c5-450e-b1aa-c147ded3f816 ro quiet splash acpi_sleep=s3_mode acpi_sleep=s3_bios acpi_osi=Linux "acpi_osi=!Windows 2020" crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: Upgraded to questing on 2026-02-16 (1 days ago)
dmi.bios.date: 04/09/2025
dmi.bios.release: 1.41
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.41.0
dmi.board.name: 0MM81M
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.41.0:bd04/09/2025:br1.41:svnDellInc.:pnLatitude5590:pvr:rvnDellInc.:rn0MM81M:rvrA00:cvnDellInc.:ct10:cvr:sku0817:
dmi.product.family: Latitude
dmi.product.name: Latitude 5590
dmi.product.sku: 0817
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141985/+subscriptions
[Bug 2141216] Re: Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT (andgpu SMU resume failure)
Did you drop the mem asleep default change from your kernel command
line?
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141216
Title:
Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT
(andgpu SMU resume failure)
Status in linux package in Ubuntu:
New
Status in linux source package in Questing:
Triaged
Bug description:
Summary: Suspend/resume broken after latest Ubuntu update on AMD RX
What Happens: After suspend, system wakes but display remains black. VT switching (Ctrl–Alt–F3) does not work. Only hard reboot recovers.
Regression: This started immediately after a recent Ubuntu update
Hardware: AMD RX 960 XT (Nav 44) + AMD Raphael iGPU
Relevant logs: SMU resume failure. GPU ring timeouts, GPU ring timeouts, devcoredump created (already captured by ubuntu-bug tool)
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-12-generic 6.17.0-12.12
ProcVersionSignature: Ubuntu 6.17.0-12.12-generic 6.17.2
Uname: Linux 6.17.0-12-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 7 17:54:17 2026
InstallationDate: Installed on 2025-10-20 (110 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: ASUS System Product Name
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-12-generic root=UUID=3412c7b3-e116-4927-b603-3da7641a647b ro quiet splash mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2025
dmi.bios.release: 32.65
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3265
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B650E-E WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3265:bd06/11/2025:br32.65:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650E-EWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141216/+subscriptions
line?
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141216
Title:
Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT
(andgpu SMU resume failure)
Status in linux package in Ubuntu:
New
Status in linux source package in Questing:
Triaged
Bug description:
Summary: Suspend/resume broken after latest Ubuntu update on AMD RX
What Happens: After suspend, system wakes but display remains black. VT switching (Ctrl–Alt–F3) does not work. Only hard reboot recovers.
Regression: This started immediately after a recent Ubuntu update
Hardware: AMD RX 960 XT (Nav 44) + AMD Raphael iGPU
Relevant logs: SMU resume failure. GPU ring timeouts, GPU ring timeouts, devcoredump created (already captured by ubuntu-bug tool)
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-12-generic 6.17.0-12.12
ProcVersionSignature: Ubuntu 6.17.0-12.12-generic 6.17.2
Uname: Linux 6.17.0-12-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 7 17:54:17 2026
InstallationDate: Installed on 2025-10-20 (110 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: ASUS System Product Name
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-12-generic root=UUID=3412c7b3-e116-4927-b603-3da7641a647b ro quiet splash mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2025
dmi.bios.release: 32.65
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3265
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B650E-E WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3265:bd06/11/2025:br32.65:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650E-EWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141216/+subscriptions
[Bug 2142386] [NEW] Touchpad SYNA3602:00 stops responding to movement after 5-10 minutes of inactivity (kernel 6.17.0-8-generic)
Public bug reported:
After upgrading to Ubuntu 25.10 with kernel 6.17.0-8-generic, the built-
in touchpad (SYNA3602:00 093A:0255) stops responding to movement after
about 5-10 minutes of inactivity.
Symptoms:
- Touching the pad wakes up the screen (backlight turns on), but the cursor does not move
- Physical clicks on the touchpad stop working
- Tap-to-click (сенсорный клик) still works
- Only a full system reboot restores functionality
What I've observed:
- `libinput debug-events` shows NO events when moving finger on dead touchpad
- Device is still visible in `libinput list-devices` with correct capabilities
- This is a regression — did not happen on previous Ubuntu versions (24.10, 24.04)
Hardware:
- Laptop: KVADRA NAU LE14U
- Touchpad: SYNA3602:00 093A:0255 (I2C HID v1.00)
- Kernel: 6.17.0-8-generic
- Ubuntu: 25.10
Steps to reproduce:
1. Boot Ubuntu 25.10 with kernel 6.17.0-8-generic
2. Do not touch the touchpad for 5-10 minutes
3. Try to move the cursor — it does not respond
4. Only reboot fixes the issue temporarily
Expected behavior:
Touchpad should remain functional after periods of inactivity.
** 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/2142386
Title:
Touchpad SYNA3602:00 stops responding to movement after 5-10 minutes
of inactivity (kernel 6.17.0-8-generic)
Status in linux package in Ubuntu:
New
Bug description:
After upgrading to Ubuntu 25.10 with kernel 6.17.0-8-generic, the
built-in touchpad (SYNA3602:00 093A:0255) stops responding to movement
after about 5-10 minutes of inactivity.
Symptoms:
- Touching the pad wakes up the screen (backlight turns on), but the cursor does not move
- Physical clicks on the touchpad stop working
- Tap-to-click (сенсорный клик) still works
- Only a full system reboot restores functionality
What I've observed:
- `libinput debug-events` shows NO events when moving finger on dead touchpad
- Device is still visible in `libinput list-devices` with correct capabilities
- This is a regression — did not happen on previous Ubuntu versions (24.10, 24.04)
Hardware:
- Laptop: KVADRA NAU LE14U
- Touchpad: SYNA3602:00 093A:0255 (I2C HID v1.00)
- Kernel: 6.17.0-8-generic
- Ubuntu: 25.10
Steps to reproduce:
1. Boot Ubuntu 25.10 with kernel 6.17.0-8-generic
2. Do not touch the touchpad for 5-10 minutes
3. Try to move the cursor — it does not respond
4. Only reboot fixes the issue temporarily
Expected behavior:
Touchpad should remain functional after periods of inactivity.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142386/+subscriptions
After upgrading to Ubuntu 25.10 with kernel 6.17.0-8-generic, the built-
in touchpad (SYNA3602:00 093A:0255) stops responding to movement after
about 5-10 minutes of inactivity.
Symptoms:
- Touching the pad wakes up the screen (backlight turns on), but the cursor does not move
- Physical clicks on the touchpad stop working
- Tap-to-click (сенсорный клик) still works
- Only a full system reboot restores functionality
What I've observed:
- `libinput debug-events` shows NO events when moving finger on dead touchpad
- Device is still visible in `libinput list-devices` with correct capabilities
- This is a regression — did not happen on previous Ubuntu versions (24.10, 24.04)
Hardware:
- Laptop: KVADRA NAU LE14U
- Touchpad: SYNA3602:00 093A:0255 (I2C HID v1.00)
- Kernel: 6.17.0-8-generic
- Ubuntu: 25.10
Steps to reproduce:
1. Boot Ubuntu 25.10 with kernel 6.17.0-8-generic
2. Do not touch the touchpad for 5-10 minutes
3. Try to move the cursor — it does not respond
4. Only reboot fixes the issue temporarily
Expected behavior:
Touchpad should remain functional after periods of inactivity.
** 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/2142386
Title:
Touchpad SYNA3602:00 stops responding to movement after 5-10 minutes
of inactivity (kernel 6.17.0-8-generic)
Status in linux package in Ubuntu:
New
Bug description:
After upgrading to Ubuntu 25.10 with kernel 6.17.0-8-generic, the
built-in touchpad (SYNA3602:00 093A:0255) stops responding to movement
after about 5-10 minutes of inactivity.
Symptoms:
- Touching the pad wakes up the screen (backlight turns on), but the cursor does not move
- Physical clicks on the touchpad stop working
- Tap-to-click (сенсорный клик) still works
- Only a full system reboot restores functionality
What I've observed:
- `libinput debug-events` shows NO events when moving finger on dead touchpad
- Device is still visible in `libinput list-devices` with correct capabilities
- This is a regression — did not happen on previous Ubuntu versions (24.10, 24.04)
Hardware:
- Laptop: KVADRA NAU LE14U
- Touchpad: SYNA3602:00 093A:0255 (I2C HID v1.00)
- Kernel: 6.17.0-8-generic
- Ubuntu: 25.10
Steps to reproduce:
1. Boot Ubuntu 25.10 with kernel 6.17.0-8-generic
2. Do not touch the touchpad for 5-10 minutes
3. Try to move the cursor — it does not respond
4. Only reboot fixes the issue temporarily
Expected behavior:
Touchpad should remain functional after periods of inactivity.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142386/+subscriptions
[Bug 2126636] Re: ACPI interrupt storm on Asus [Your Exact Laptop Model] causes 100% CPU, `acpi=noirq` workaround breaks audio
Solution Found: Disable GPE 0x6F
After months of living with this bug, I finally found a targeted fix
that resolves the 100% CPU usage without breaking sound or any other
functionality.
Root cause: GPE (General Purpose Event) 0x6F fires continuously because
the BIOS fan status method \_SB.PC00.LPCB.H_EC.TFN1._FST references a
symbol CFSP that doesn't exist in the ACPI tables. Each failed call
triggers another interrupt, creating the storm visible in
/proc/interrupts (113+ million hits on IRQ 9).
Diagnosis:
# Check which GPE is responsible for the storm:
cat /sys/firmware/acpi/interrupts/gpe_all # shows millions
cat /sys/firmware/acpi/interrupts/gpe6F # same number = culprit
Immediate fix (no reboot needed):
echo "disable" | sudo tee /sys/firmware/acpi/interrupts/gpe6F
CPU usage drops to normal instantly. Sound, EC, keyboard, trackpad,
everything else works fine. GPE 0x6E (the EC) is unaffected.
Permanent fix (survives reboot):
Create /etc/systemd/system/disable-gpe6f.service:
[Unit]
Description=Disable ACPI GPE 0x6F (broken fan status on Asus ExpertBook P3605CVA)
After=sysinit.target
[Service]
Type=oneshot
ExecStart=/bin/bash -c 'echo "disable" > /sys/firmware/acpi/interrupts/gpe6F'
[Install]
WantedBy=multi-user.target
Then enable it:
sudo systemctl daemon-reload
sudo systemctl enable disable-gpe6f.service
Environment: Kernel 6.18.7 on Ubuntu, but this should work on any kernel version since the issue is in the ASUS BIOS ACPI tables (P3605CVA BIOS version 302).
Note: The proper fix would be for ASUS to release a BIOS update that
defines the missing CFSP symbol, or for the kernel to handle the
AE_NOT_FOUND error more gracefully instead of letting the GPE re-fire
indefinitely. Until then, disabling GPE 0x6F is a clean workaround with
no side effects.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2126636
Title:
ACPI interrupt storm on Asus [Your Exact Laptop Model] causes 100%
CPU, `acpi=noirq` workaround breaks audio
Status in linux package in Ubuntu:
New
Bug description:
On my ASUSTeK COMPUTER INC. ASUS EXPERTBOOK P3605CVA, a single CPU
core is constantly at 100% usage. The `ps` command shows this is
caused by `kworker/kacpi_notify` and `irq/9-acpi`.
The kernel log shows a recurring ACPI error:
`ACPI Error: Aborting method \_SB.PC00.LPCB.H_EC.TFN1._FST due to previous error (AE_NOT_FOUND)`
Troubleshooting Steps Taken:
- A BIOS update is not available from Asus.
- Upgrading to mainline kernel 6.17.0 did not fix the issue.
- The following kernel parameters did not fix the CPU issue: `acpi_rev_override=1`, `acpi_ec_poll=1`, `acpi_osi=! acpi_osi='Windows 2021'`.
- The `nolapic` parameter causes the system to hang on a black screen during boot.
- The `acpi=noirq` parameter successfully fixes the 100% CPU issue, but it causes the internal sound card ("Speaker - Raptor Lake-P/U/H cAVS") to disappear, resulting in no sound.
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: linux-image-6.14.0-33-generic 6.14.0-33.33
ProcVersionSignature: Ubuntu 6.14.0-33.33-generic 6.14.11
Uname: Linux 6.14.0-33-generic x86_64
ApportVersion: 2.32.0-0ubuntu5.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: aurelien 2784 F.... pipewire
aurelien 2792 F.... wireplumber
/dev/snd/seq: aurelien 2784 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 2 16:57:29 2025
InstallationDate: Installed on 2025-10-01 (1 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3)
MachineType: ASUSTeK COMPUTER INC. ASUS EXPERTBOOK P3605CVA
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-33-generic root=UUID=151bb0ce-de78-41e4-8bc4-09f7b8050d63 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.14.0-33-generic N/A
linux-backports-modules-6.14.0-33-generic N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/17/2025
dmi.bios.release: 5.32
dmi.bios.vendor: ASUSTeK COMPUTER INC. (Licensed by AMI, LLC.)
dmi.bios.version: P3605CVA.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: P3605CVA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.17
dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.(LicensedbyAMI,LLC.):bvrP3605CVA.302:bd05/17/2025:br5.32:efr3.17:svnASUSTeKCOMPUTERINC.:pnASUSEXPERTBOOKP3605CVA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnP3605CVA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ASUS EXPERTBOOK
dmi.product.name: ASUS EXPERTBOOK P3605CVA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2126636/+subscriptions
After months of living with this bug, I finally found a targeted fix
that resolves the 100% CPU usage without breaking sound or any other
functionality.
Root cause: GPE (General Purpose Event) 0x6F fires continuously because
the BIOS fan status method \_SB.PC00.LPCB.H_EC.TFN1._FST references a
symbol CFSP that doesn't exist in the ACPI tables. Each failed call
triggers another interrupt, creating the storm visible in
/proc/interrupts (113+ million hits on IRQ 9).
Diagnosis:
# Check which GPE is responsible for the storm:
cat /sys/firmware/acpi/interrupts/gpe_all # shows millions
cat /sys/firmware/acpi/interrupts/gpe6F # same number = culprit
Immediate fix (no reboot needed):
echo "disable" | sudo tee /sys/firmware/acpi/interrupts/gpe6F
CPU usage drops to normal instantly. Sound, EC, keyboard, trackpad,
everything else works fine. GPE 0x6E (the EC) is unaffected.
Permanent fix (survives reboot):
Create /etc/systemd/system/disable-gpe6f.service:
[Unit]
Description=Disable ACPI GPE 0x6F (broken fan status on Asus ExpertBook P3605CVA)
After=sysinit.target
[Service]
Type=oneshot
ExecStart=/bin/bash -c 'echo "disable" > /sys/firmware/acpi/interrupts/gpe6F'
[Install]
WantedBy=multi-user.target
Then enable it:
sudo systemctl daemon-reload
sudo systemctl enable disable-gpe6f.service
Environment: Kernel 6.18.7 on Ubuntu, but this should work on any kernel version since the issue is in the ASUS BIOS ACPI tables (P3605CVA BIOS version 302).
Note: The proper fix would be for ASUS to release a BIOS update that
defines the missing CFSP symbol, or for the kernel to handle the
AE_NOT_FOUND error more gracefully instead of letting the GPE re-fire
indefinitely. Until then, disabling GPE 0x6F is a clean workaround with
no side effects.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2126636
Title:
ACPI interrupt storm on Asus [Your Exact Laptop Model] causes 100%
CPU, `acpi=noirq` workaround breaks audio
Status in linux package in Ubuntu:
New
Bug description:
On my ASUSTeK COMPUTER INC. ASUS EXPERTBOOK P3605CVA, a single CPU
core is constantly at 100% usage. The `ps` command shows this is
caused by `kworker/kacpi_notify` and `irq/9-acpi`.
The kernel log shows a recurring ACPI error:
`ACPI Error: Aborting method \_SB.PC00.LPCB.H_EC.TFN1._FST due to previous error (AE_NOT_FOUND)`
Troubleshooting Steps Taken:
- A BIOS update is not available from Asus.
- Upgrading to mainline kernel 6.17.0 did not fix the issue.
- The following kernel parameters did not fix the CPU issue: `acpi_rev_override=1`, `acpi_ec_poll=1`, `acpi_osi=! acpi_osi='Windows 2021'`.
- The `nolapic` parameter causes the system to hang on a black screen during boot.
- The `acpi=noirq` parameter successfully fixes the 100% CPU issue, but it causes the internal sound card ("Speaker - Raptor Lake-P/U/H cAVS") to disappear, resulting in no sound.
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: linux-image-6.14.0-33-generic 6.14.0-33.33
ProcVersionSignature: Ubuntu 6.14.0-33.33-generic 6.14.11
Uname: Linux 6.14.0-33-generic x86_64
ApportVersion: 2.32.0-0ubuntu5.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: aurelien 2784 F.... pipewire
aurelien 2792 F.... wireplumber
/dev/snd/seq: aurelien 2784 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 2 16:57:29 2025
InstallationDate: Installed on 2025-10-01 (1 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3)
MachineType: ASUSTeK COMPUTER INC. ASUS EXPERTBOOK P3605CVA
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-33-generic root=UUID=151bb0ce-de78-41e4-8bc4-09f7b8050d63 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.14.0-33-generic N/A
linux-backports-modules-6.14.0-33-generic N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/17/2025
dmi.bios.release: 5.32
dmi.bios.vendor: ASUSTeK COMPUTER INC. (Licensed by AMI, LLC.)
dmi.bios.version: P3605CVA.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: P3605CVA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.17
dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.(LicensedbyAMI,LLC.):bvrP3605CVA.302:bd05/17/2025:br5.32:efr3.17:svnASUSTeKCOMPUTERINC.:pnASUSEXPERTBOOKP3605CVA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnP3605CVA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ASUS EXPERTBOOK
dmi.product.name: ASUS EXPERTBOOK P3605CVA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2126636/+subscriptions
[Bug 2142384] [NEW] ELAN2514:00 (04F3:4428) stylus report rate extremely low (~10–25 Hz) on Ubuntu 24.04 kernel 6.17
Public bug reported:
The active stylus on my HP OmniBook x Flip Ultra 14 reports at extremely
low frequency (~10–25 Hz) under Ubuntu 24.04.4 LTS with kernel
6.17.0-14-generic. The pen input is choppy and unusable, while touch
input works normally.
The pen is a HP MPP tilt pen 2.0
Steps to Reproduce:
Boot Ubuntu 24.04.4 LTS on HP OmniBook x Flip Ultra 14.
Ensure kernel 6.17.0-14-generic is in use.
Run:
sudo libinput debug-events
And then i move the pen and compare the input events with touch on my
screen. The timestamps of the pen are 40-100 ms apart, which makes it
unusable.
I think this is the stylus in libinput:
Device: ELAN2514:00 04F3:4428 Stylus
Kernel: /dev/input/event7
Group: 5
Seat: seat0, default
Size: 300x188mm
Capabilities: tablet
Accel profiles: none
Other relevant info:
lsmod | grep hid
hid_sensor_prox 20480 0
hid_sensor_trigger 20480 3 hid_sensor_prox
hid_sensor_iio_common 24576 2 hid_sensor_trigger,hid_sensor_prox
industrialio 139264 4 industrialio_triggered_buffer,hid_sensor_trigger,hid_sensor_prox,kfifo_buf
intel_hid 32768 0
sparse_keymap 12288 2 hp_wmi,intel_hid
mac_hid 12288 0
hid_sensor_hub 28672 3 hid_sensor_trigger,hid_sensor_iio_common,hid_sensor_prox
usbhid 77824 0
hid_multitouch 36864 0
hid_generic 12288 0
i2c_hid_acpi 12288 0
i2c_hid 40960 1 i2c_hid_acpi
hid 262144 6 i2c_hid,usbhid,hid_multitouch,hid_sensor_hub,snd_soc_sdca,hid_generic
cat /sys/bus/i2c/devices/i2c-ELAN2514:00/power/control
on
Ubuntu 24.04.4 LTS
Kernel: 6.17.0-14-generic
** 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/2142384
Title:
ELAN2514:00 (04F3:4428) stylus report rate extremely low (~10–25 Hz)
on Ubuntu 24.04 kernel 6.17
Status in linux package in Ubuntu:
New
Bug description:
The active stylus on my HP OmniBook x Flip Ultra 14 reports at
extremely low frequency (~10–25 Hz) under Ubuntu 24.04.4 LTS with
kernel 6.17.0-14-generic. The pen input is choppy and unusable, while
touch input works normally.
The pen is a HP MPP tilt pen 2.0
Steps to Reproduce:
Boot Ubuntu 24.04.4 LTS on HP OmniBook x Flip Ultra 14.
Ensure kernel 6.17.0-14-generic is in use.
Run:
sudo libinput debug-events
And then i move the pen and compare the input events with touch on my
screen. The timestamps of the pen are 40-100 ms apart, which makes it
unusable.
I think this is the stylus in libinput:
Device: ELAN2514:00 04F3:4428 Stylus
Kernel: /dev/input/event7
Group: 5
Seat: seat0, default
Size: 300x188mm
Capabilities: tablet
Accel profiles: none
Other relevant info:
lsmod | grep hid
hid_sensor_prox 20480 0
hid_sensor_trigger 20480 3 hid_sensor_prox
hid_sensor_iio_common 24576 2 hid_sensor_trigger,hid_sensor_prox
industrialio 139264 4 industrialio_triggered_buffer,hid_sensor_trigger,hid_sensor_prox,kfifo_buf
intel_hid 32768 0
sparse_keymap 12288 2 hp_wmi,intel_hid
mac_hid 12288 0
hid_sensor_hub 28672 3 hid_sensor_trigger,hid_sensor_iio_common,hid_sensor_prox
usbhid 77824 0
hid_multitouch 36864 0
hid_generic 12288 0
i2c_hid_acpi 12288 0
i2c_hid 40960 1 i2c_hid_acpi
hid 262144 6 i2c_hid,usbhid,hid_multitouch,hid_sensor_hub,snd_soc_sdca,hid_generic
cat /sys/bus/i2c/devices/i2c-ELAN2514:00/power/control
on
Ubuntu 24.04.4 LTS
Kernel: 6.17.0-14-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142384/+subscriptions
The active stylus on my HP OmniBook x Flip Ultra 14 reports at extremely
low frequency (~10–25 Hz) under Ubuntu 24.04.4 LTS with kernel
6.17.0-14-generic. The pen input is choppy and unusable, while touch
input works normally.
The pen is a HP MPP tilt pen 2.0
Steps to Reproduce:
Boot Ubuntu 24.04.4 LTS on HP OmniBook x Flip Ultra 14.
Ensure kernel 6.17.0-14-generic is in use.
Run:
sudo libinput debug-events
And then i move the pen and compare the input events with touch on my
screen. The timestamps of the pen are 40-100 ms apart, which makes it
unusable.
I think this is the stylus in libinput:
Device: ELAN2514:00 04F3:4428 Stylus
Kernel: /dev/input/event7
Group: 5
Seat: seat0, default
Size: 300x188mm
Capabilities: tablet
Accel profiles: none
Other relevant info:
lsmod | grep hid
hid_sensor_prox 20480 0
hid_sensor_trigger 20480 3 hid_sensor_prox
hid_sensor_iio_common 24576 2 hid_sensor_trigger,hid_sensor_prox
industrialio 139264 4 industrialio_triggered_buffer,hid_sensor_trigger,hid_sensor_prox,kfifo_buf
intel_hid 32768 0
sparse_keymap 12288 2 hp_wmi,intel_hid
mac_hid 12288 0
hid_sensor_hub 28672 3 hid_sensor_trigger,hid_sensor_iio_common,hid_sensor_prox
usbhid 77824 0
hid_multitouch 36864 0
hid_generic 12288 0
i2c_hid_acpi 12288 0
i2c_hid 40960 1 i2c_hid_acpi
hid 262144 6 i2c_hid,usbhid,hid_multitouch,hid_sensor_hub,snd_soc_sdca,hid_generic
cat /sys/bus/i2c/devices/i2c-ELAN2514:00/power/control
on
Ubuntu 24.04.4 LTS
Kernel: 6.17.0-14-generic
** 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/2142384
Title:
ELAN2514:00 (04F3:4428) stylus report rate extremely low (~10–25 Hz)
on Ubuntu 24.04 kernel 6.17
Status in linux package in Ubuntu:
New
Bug description:
The active stylus on my HP OmniBook x Flip Ultra 14 reports at
extremely low frequency (~10–25 Hz) under Ubuntu 24.04.4 LTS with
kernel 6.17.0-14-generic. The pen input is choppy and unusable, while
touch input works normally.
The pen is a HP MPP tilt pen 2.0
Steps to Reproduce:
Boot Ubuntu 24.04.4 LTS on HP OmniBook x Flip Ultra 14.
Ensure kernel 6.17.0-14-generic is in use.
Run:
sudo libinput debug-events
And then i move the pen and compare the input events with touch on my
screen. The timestamps of the pen are 40-100 ms apart, which makes it
unusable.
I think this is the stylus in libinput:
Device: ELAN2514:00 04F3:4428 Stylus
Kernel: /dev/input/event7
Group: 5
Seat: seat0, default
Size: 300x188mm
Capabilities: tablet
Accel profiles: none
Other relevant info:
lsmod | grep hid
hid_sensor_prox 20480 0
hid_sensor_trigger 20480 3 hid_sensor_prox
hid_sensor_iio_common 24576 2 hid_sensor_trigger,hid_sensor_prox
industrialio 139264 4 industrialio_triggered_buffer,hid_sensor_trigger,hid_sensor_prox,kfifo_buf
intel_hid 32768 0
sparse_keymap 12288 2 hp_wmi,intel_hid
mac_hid 12288 0
hid_sensor_hub 28672 3 hid_sensor_trigger,hid_sensor_iio_common,hid_sensor_prox
usbhid 77824 0
hid_multitouch 36864 0
hid_generic 12288 0
i2c_hid_acpi 12288 0
i2c_hid 40960 1 i2c_hid_acpi
hid 262144 6 i2c_hid,usbhid,hid_multitouch,hid_sensor_hub,snd_soc_sdca,hid_generic
cat /sys/bus/i2c/devices/i2c-ELAN2514:00/power/control
on
Ubuntu 24.04.4 LTS
Kernel: 6.17.0-14-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142384/+subscriptions
[Bug 2131689] Re: No internal audio on Dell Alienware 18 (Intel Arrow Lake, 8086:7f50, 1028:0ccd) – only NVIDIA HDMI detected on Ubuntu 24.04 (6.14.0-1015-oem)
Patch still not upsteam. Duplicate bug confirms problem still present in
6.17
** Package changed: linux-oem-6.14 (Ubuntu) => linux (Ubuntu)
** Summary changed:
- No internal audio on Dell Alienware 18 (Intel Arrow Lake, 8086:7f50, 1028:0ccd) – only NVIDIA HDMI detected on Ubuntu 24.04 (6.14.0-1015-oem)
+ No internal audio on Dell Alienware 18 Area-51 AA18250 (Intel Arrow Lake, 8086:7f50, 1028:0ccd)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2131689
Title:
No internal audio on Dell Alienware 18 Area-51 AA18250 (Intel Arrow
Lake, 8086:7f50, 1028:0ccd)
Status in linux package in Ubuntu:
Confirmed
Bug description:
Summary
-------
On a new Dell Alienware 18 (2024) laptop running Ubuntu 24.04 with OEM kernel
(6.14.0-1015-oem), the internal audio (speakers / headphone jack) does not work
at all.
Only NVIDIA HDMI audio is detected by ALSA and PipeWire. The Intel on-board
audio controller is visible on PCI and a SOF driver is attached, but ALSA
creates no PCM devices for it, so there is no internal sound output.
This looks like missing or incomplete support for Intel Arrow Lake audio
(8086:7f50, subsystem 1028:0ccd) in the current Ubuntu kernel / SOF stack.
System information
------------------
Laptop: Dell Alienware 18 (2024 model)
OS: Ubuntu 24.04 LTS
Kernel: 6.14.0-1015-oem (linux-oem-24.04)
Audio stack: PipeWire (pipewire, pipewire-pulse, wireplumber)
PCI audio devices:
$ lspci -nnk | grep -A3 -E 'Audio|Multimedia'
02:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:22e9] (rev a1)
Subsystem: NVIDIA Corporation Device [10de:0000]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
--
80:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:7f50] (rev 10)
Subsystem: Dell Device [1028:0ccd]
Kernel driver in use: sof-audio-pci-intel-mtl
Kernel modules: snd_hda_intel, snd_sof_pci_intel_mtl
So the Intel Arrow Lake audio controller is detected and bound to
sof-audio-pci-intel-mtl, but ALSA does not expose any devices for it.
ALSA output
-----------
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
There is no "HDA Intel", "PCH", "sof-hda-dsp" or any internal analog device.
Only the NVIDIA HDMI devices are present.
PipeWire output
---------------
$ pactl list short sinks
33 auto_null PipeWire float32le 2ch 48000Hz SUSPENDED
PipeWire only creates the auto_null sink because there are no real
audio devices from ALSA.
Packages and firmware
---------------------
The following packages are installed and up to date:
- linux-firmware
- firmware-sof-signed
- alsa-ucm-conf
- pipewire
- pipewire-pulse
- wireplumber
- alsa-utils
- libasound2-plugins
PulseAudio is disabled and PipeWire is running as the primary audio
server.
What I have tried
-----------------
- Updated to the OEM kernel: linux-oem-24.04 (6.14.0-1015-oem)
- Reinstalled linux-firmware
- Installed firmware-sof-signed and alsa-ucm-conf
- Disabled PulseAudio (masked user pulseaudio services/sockets)
- Enabled PipeWire and pipewire-pulse and restarted WirePlumber
- Removed any custom modprobe configs and blacklists I had tried
- Reinstalled NVIDIA drivers; video stack is now working correctly
- Checked BIOS/UEFI: audio is enabled
Despite all this, the Intel audio device (8086:7f50 / 1028:0ccd) never
produces any PCM devices in ALSA. aplay -l always only shows the NVIDIA
HDMI card.
Expected behavior
-----------------
- The Intel on-board audio (Realtek/Intel codec behind 8086:7f50 / 1028:0ccd)
should be fully supported.
- ALSA should expose at least one PCM device for analog output
(speakers / headphone jack).
- PipeWire should see these devices and create one or more real sinks
instead of auto_null.
- Sound should play through the laptop's internal speakers and headphone jack.
Actual behavior
---------------
- Only the NVIDIA HDMI HDA controller is usable (card 0).
- The Intel Arrow Lake audio controller is detected but never exposes
any ALSA PCM devices.
- PipeWire only shows the auto_null sink.
- Internal speakers and headphone jack are completely unusable on Ubuntu 24.04
with the current OEM kernel.
Request
-------
This appears to be missing or incomplete support for the Intel Arrow Lake
audio device:
8086:7f50 (Intel)
1028:0ccd (Dell Alienware 18)
I would kindly ask:
- Is support for this audio device already present in any newer Ubuntu kernel
or SOF firmware, and if so, which version(s) should I test?
- If not yet supported, could this device ID be added to the appropriate
SOF / ASoC machine driver / UCM configuration?
- Are there any known workarounds (e.g. specific kernel parameters, alternative
SOF topology, or test patches) that I could try on this system?
I am happy to provide additional logs (dmesg, alsa-info, pw-dump) and to test
development kernels or patches if needed.
Thank you for your help.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.14.0-1015-oem 6.14.0-1015.15
ProcVersionSignature: Ubuntu 6.14.0-1015.15-oem 6.14.11
Uname: Linux 6.14.0-1015-oem x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: alexander 3121 F.... wireplumber
/dev/snd/seq: alexander 3117 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 17 20:09:43 2025
InstallationDate: Installed on 2025-11-07 (10 days ago)
InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
IwConfig:
lo no wireless extensions.
wlp131s0f0 no wireless extensions.
MachineType: Alienware Alienware 18 Area-51 AA18250
ProcEnviron:
LANG=ru_RU.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 nvidia-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-1015-oem root=UUID=7322735b-2b07-4fdb-8145-76ac3f0a900d ro quiet splash intel_iommu=igfx_off vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.14.0-1015-oem N/A
linux-backports-modules-6.14.0-1015-oem N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.19
SourcePackage: linux-oem-6.14
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2025
dmi.bios.release: 1.6
dmi.bios.vendor: Alienware
dmi.bios.version: 1.6.1
dmi.board.name: 0D469V
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Alienware
dmi.ec.firmware.release: 1.4
dmi.modalias: dmi:bvnAlienware:bvr1.6.1:bd07/25/2025:br1.6:efr1.4:svnAlienware:pnAlienware18Area-51AA18250:pvr:rvnAlienware:rn0D469V:rvrA00:cvnAlienware:ct10:cvr:sku0CCD:
dmi.product.family: Alienware
dmi.product.name: Alienware 18 Area-51 AA18250
dmi.product.sku: 0CCD
dmi.sys.vendor: Alienware
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2131689/+subscriptions
6.17
** Package changed: linux-oem-6.14 (Ubuntu) => linux (Ubuntu)
** Summary changed:
- No internal audio on Dell Alienware 18 (Intel Arrow Lake, 8086:7f50, 1028:0ccd) – only NVIDIA HDMI detected on Ubuntu 24.04 (6.14.0-1015-oem)
+ No internal audio on Dell Alienware 18 Area-51 AA18250 (Intel Arrow Lake, 8086:7f50, 1028:0ccd)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2131689
Title:
No internal audio on Dell Alienware 18 Area-51 AA18250 (Intel Arrow
Lake, 8086:7f50, 1028:0ccd)
Status in linux package in Ubuntu:
Confirmed
Bug description:
Summary
-------
On a new Dell Alienware 18 (2024) laptop running Ubuntu 24.04 with OEM kernel
(6.14.0-1015-oem), the internal audio (speakers / headphone jack) does not work
at all.
Only NVIDIA HDMI audio is detected by ALSA and PipeWire. The Intel on-board
audio controller is visible on PCI and a SOF driver is attached, but ALSA
creates no PCM devices for it, so there is no internal sound output.
This looks like missing or incomplete support for Intel Arrow Lake audio
(8086:7f50, subsystem 1028:0ccd) in the current Ubuntu kernel / SOF stack.
System information
------------------
Laptop: Dell Alienware 18 (2024 model)
OS: Ubuntu 24.04 LTS
Kernel: 6.14.0-1015-oem (linux-oem-24.04)
Audio stack: PipeWire (pipewire, pipewire-pulse, wireplumber)
PCI audio devices:
$ lspci -nnk | grep -A3 -E 'Audio|Multimedia'
02:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:22e9] (rev a1)
Subsystem: NVIDIA Corporation Device [10de:0000]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
--
80:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:7f50] (rev 10)
Subsystem: Dell Device [1028:0ccd]
Kernel driver in use: sof-audio-pci-intel-mtl
Kernel modules: snd_hda_intel, snd_sof_pci_intel_mtl
So the Intel Arrow Lake audio controller is detected and bound to
sof-audio-pci-intel-mtl, but ALSA does not expose any devices for it.
ALSA output
-----------
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
There is no "HDA Intel", "PCH", "sof-hda-dsp" or any internal analog device.
Only the NVIDIA HDMI devices are present.
PipeWire output
---------------
$ pactl list short sinks
33 auto_null PipeWire float32le 2ch 48000Hz SUSPENDED
PipeWire only creates the auto_null sink because there are no real
audio devices from ALSA.
Packages and firmware
---------------------
The following packages are installed and up to date:
- linux-firmware
- firmware-sof-signed
- alsa-ucm-conf
- pipewire
- pipewire-pulse
- wireplumber
- alsa-utils
- libasound2-plugins
PulseAudio is disabled and PipeWire is running as the primary audio
server.
What I have tried
-----------------
- Updated to the OEM kernel: linux-oem-24.04 (6.14.0-1015-oem)
- Reinstalled linux-firmware
- Installed firmware-sof-signed and alsa-ucm-conf
- Disabled PulseAudio (masked user pulseaudio services/sockets)
- Enabled PipeWire and pipewire-pulse and restarted WirePlumber
- Removed any custom modprobe configs and blacklists I had tried
- Reinstalled NVIDIA drivers; video stack is now working correctly
- Checked BIOS/UEFI: audio is enabled
Despite all this, the Intel audio device (8086:7f50 / 1028:0ccd) never
produces any PCM devices in ALSA. aplay -l always only shows the NVIDIA
HDMI card.
Expected behavior
-----------------
- The Intel on-board audio (Realtek/Intel codec behind 8086:7f50 / 1028:0ccd)
should be fully supported.
- ALSA should expose at least one PCM device for analog output
(speakers / headphone jack).
- PipeWire should see these devices and create one or more real sinks
instead of auto_null.
- Sound should play through the laptop's internal speakers and headphone jack.
Actual behavior
---------------
- Only the NVIDIA HDMI HDA controller is usable (card 0).
- The Intel Arrow Lake audio controller is detected but never exposes
any ALSA PCM devices.
- PipeWire only shows the auto_null sink.
- Internal speakers and headphone jack are completely unusable on Ubuntu 24.04
with the current OEM kernel.
Request
-------
This appears to be missing or incomplete support for the Intel Arrow Lake
audio device:
8086:7f50 (Intel)
1028:0ccd (Dell Alienware 18)
I would kindly ask:
- Is support for this audio device already present in any newer Ubuntu kernel
or SOF firmware, and if so, which version(s) should I test?
- If not yet supported, could this device ID be added to the appropriate
SOF / ASoC machine driver / UCM configuration?
- Are there any known workarounds (e.g. specific kernel parameters, alternative
SOF topology, or test patches) that I could try on this system?
I am happy to provide additional logs (dmesg, alsa-info, pw-dump) and to test
development kernels or patches if needed.
Thank you for your help.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.14.0-1015-oem 6.14.0-1015.15
ProcVersionSignature: Ubuntu 6.14.0-1015.15-oem 6.14.11
Uname: Linux 6.14.0-1015-oem x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: alexander 3121 F.... wireplumber
/dev/snd/seq: alexander 3117 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 17 20:09:43 2025
InstallationDate: Installed on 2025-11-07 (10 days ago)
InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
IwConfig:
lo no wireless extensions.
wlp131s0f0 no wireless extensions.
MachineType: Alienware Alienware 18 Area-51 AA18250
ProcEnviron:
LANG=ru_RU.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 nvidia-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-1015-oem root=UUID=7322735b-2b07-4fdb-8145-76ac3f0a900d ro quiet splash intel_iommu=igfx_off vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.14.0-1015-oem N/A
linux-backports-modules-6.14.0-1015-oem N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.19
SourcePackage: linux-oem-6.14
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2025
dmi.bios.release: 1.6
dmi.bios.vendor: Alienware
dmi.bios.version: 1.6.1
dmi.board.name: 0D469V
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Alienware
dmi.ec.firmware.release: 1.4
dmi.modalias: dmi:bvnAlienware:bvr1.6.1:bd07/25/2025:br1.6:efr1.4:svnAlienware:pnAlienware18Area-51AA18250:pvr:rvnAlienware:rn0D469V:rvrA00:cvnAlienware:ct10:cvr:sku0CCD:
dmi.product.family: Alienware
dmi.product.name: Alienware 18 Area-51 AA18250
dmi.product.sku: 0CCD
dmi.sys.vendor: Alienware
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2131689/+subscriptions
[Bug 2131689] [NEW] No internal audio on Dell Alienware 18 (Intel Arrow Lake, 8086:7f50, 1028:0ccd) – only NVIDIA HDMI detected on Ubuntu 24.04 (6.14.0-1015-oem)
You have been subscribed to a public bug:
Summary
-------
On a new Dell Alienware 18 (2024) laptop running Ubuntu 24.04 with OEM kernel
(6.14.0-1015-oem), the internal audio (speakers / headphone jack) does not work
at all.
Only NVIDIA HDMI audio is detected by ALSA and PipeWire. The Intel on-board
audio controller is visible on PCI and a SOF driver is attached, but ALSA
creates no PCM devices for it, so there is no internal sound output.
This looks like missing or incomplete support for Intel Arrow Lake audio
(8086:7f50, subsystem 1028:0ccd) in the current Ubuntu kernel / SOF stack.
System information
------------------
Laptop: Dell Alienware 18 (2024 model)
OS: Ubuntu 24.04 LTS
Kernel: 6.14.0-1015-oem (linux-oem-24.04)
Audio stack: PipeWire (pipewire, pipewire-pulse, wireplumber)
PCI audio devices:
$ lspci -nnk | grep -A3 -E 'Audio|Multimedia'
02:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:22e9] (rev a1)
Subsystem: NVIDIA Corporation Device [10de:0000]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
--
80:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:7f50] (rev 10)
Subsystem: Dell Device [1028:0ccd]
Kernel driver in use: sof-audio-pci-intel-mtl
Kernel modules: snd_hda_intel, snd_sof_pci_intel_mtl
So the Intel Arrow Lake audio controller is detected and bound to
sof-audio-pci-intel-mtl, but ALSA does not expose any devices for it.
ALSA output
-----------
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
There is no "HDA Intel", "PCH", "sof-hda-dsp" or any internal analog device.
Only the NVIDIA HDMI devices are present.
PipeWire output
---------------
$ pactl list short sinks
33 auto_null PipeWire float32le 2ch 48000Hz SUSPENDED
PipeWire only creates the auto_null sink because there are no real
audio devices from ALSA.
Packages and firmware
---------------------
The following packages are installed and up to date:
- linux-firmware
- firmware-sof-signed
- alsa-ucm-conf
- pipewire
- pipewire-pulse
- wireplumber
- alsa-utils
- libasound2-plugins
PulseAudio is disabled and PipeWire is running as the primary audio
server.
What I have tried
-----------------
- Updated to the OEM kernel: linux-oem-24.04 (6.14.0-1015-oem)
- Reinstalled linux-firmware
- Installed firmware-sof-signed and alsa-ucm-conf
- Disabled PulseAudio (masked user pulseaudio services/sockets)
- Enabled PipeWire and pipewire-pulse and restarted WirePlumber
- Removed any custom modprobe configs and blacklists I had tried
- Reinstalled NVIDIA drivers; video stack is now working correctly
- Checked BIOS/UEFI: audio is enabled
Despite all this, the Intel audio device (8086:7f50 / 1028:0ccd) never
produces any PCM devices in ALSA. aplay -l always only shows the NVIDIA
HDMI card.
Expected behavior
-----------------
- The Intel on-board audio (Realtek/Intel codec behind 8086:7f50 / 1028:0ccd)
should be fully supported.
- ALSA should expose at least one PCM device for analog output
(speakers / headphone jack).
- PipeWire should see these devices and create one or more real sinks
instead of auto_null.
- Sound should play through the laptop's internal speakers and headphone jack.
Actual behavior
---------------
- Only the NVIDIA HDMI HDA controller is usable (card 0).
- The Intel Arrow Lake audio controller is detected but never exposes
any ALSA PCM devices.
- PipeWire only shows the auto_null sink.
- Internal speakers and headphone jack are completely unusable on Ubuntu 24.04
with the current OEM kernel.
Request
-------
This appears to be missing or incomplete support for the Intel Arrow Lake
audio device:
8086:7f50 (Intel)
1028:0ccd (Dell Alienware 18)
I would kindly ask:
- Is support for this audio device already present in any newer Ubuntu kernel
or SOF firmware, and if so, which version(s) should I test?
- If not yet supported, could this device ID be added to the appropriate
SOF / ASoC machine driver / UCM configuration?
- Are there any known workarounds (e.g. specific kernel parameters, alternative
SOF topology, or test patches) that I could try on this system?
I am happy to provide additional logs (dmesg, alsa-info, pw-dump) and to test
development kernels or patches if needed.
Thank you for your help.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.14.0-1015-oem 6.14.0-1015.15
ProcVersionSignature: Ubuntu 6.14.0-1015.15-oem 6.14.11
Uname: Linux 6.14.0-1015-oem x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: alexander 3121 F.... wireplumber
/dev/snd/seq: alexander 3117 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 17 20:09:43 2025
InstallationDate: Installed on 2025-11-07 (10 days ago)
InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
IwConfig:
lo no wireless extensions.
wlp131s0f0 no wireless extensions.
MachineType: Alienware Alienware 18 Area-51 AA18250
ProcEnviron:
LANG=ru_RU.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 nvidia-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-1015-oem root=UUID=7322735b-2b07-4fdb-8145-76ac3f0a900d ro quiet splash intel_iommu=igfx_off vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.14.0-1015-oem N/A
linux-backports-modules-6.14.0-1015-oem N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.19
SourcePackage: linux-oem-6.14
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2025
dmi.bios.release: 1.6
dmi.bios.vendor: Alienware
dmi.bios.version: 1.6.1
dmi.board.name: 0D469V
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Alienware
dmi.ec.firmware.release: 1.4
dmi.modalias: dmi:bvnAlienware:bvr1.6.1:bd07/25/2025:br1.6:efr1.4:svnAlienware:pnAlienware18Area-51AA18250:pvr:rvnAlienware:rn0D469V:rvrA00:cvnAlienware:ct10:cvr:sku0CCD:
dmi.product.family: Alienware
dmi.product.name: Alienware 18 Area-51 AA18250
dmi.product.sku: 0CCD
dmi.sys.vendor: Alienware
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Chris Chiu (mschiu77)
Status: Confirmed
** Tags: amd64 apport-bug kernel-daily-bug noble
--
No internal audio on Dell Alienware 18 (Intel Arrow Lake, 8086:7f50, 1028:0ccd) – only NVIDIA HDMI detected on Ubuntu 24.04 (6.14.0-1015-oem)
https://bugs.launchpad.net/bugs/2131689
You received this bug notification because you are subscribed to linux in Ubuntu.
Summary
-------
On a new Dell Alienware 18 (2024) laptop running Ubuntu 24.04 with OEM kernel
(6.14.0-1015-oem), the internal audio (speakers / headphone jack) does not work
at all.
Only NVIDIA HDMI audio is detected by ALSA and PipeWire. The Intel on-board
audio controller is visible on PCI and a SOF driver is attached, but ALSA
creates no PCM devices for it, so there is no internal sound output.
This looks like missing or incomplete support for Intel Arrow Lake audio
(8086:7f50, subsystem 1028:0ccd) in the current Ubuntu kernel / SOF stack.
System information
------------------
Laptop: Dell Alienware 18 (2024 model)
OS: Ubuntu 24.04 LTS
Kernel: 6.14.0-1015-oem (linux-oem-24.04)
Audio stack: PipeWire (pipewire, pipewire-pulse, wireplumber)
PCI audio devices:
$ lspci -nnk | grep -A3 -E 'Audio|Multimedia'
02:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:22e9] (rev a1)
Subsystem: NVIDIA Corporation Device [10de:0000]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
--
80:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:7f50] (rev 10)
Subsystem: Dell Device [1028:0ccd]
Kernel driver in use: sof-audio-pci-intel-mtl
Kernel modules: snd_hda_intel, snd_sof_pci_intel_mtl
So the Intel Arrow Lake audio controller is detected and bound to
sof-audio-pci-intel-mtl, but ALSA does not expose any devices for it.
ALSA output
-----------
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
There is no "HDA Intel", "PCH", "sof-hda-dsp" or any internal analog device.
Only the NVIDIA HDMI devices are present.
PipeWire output
---------------
$ pactl list short sinks
33 auto_null PipeWire float32le 2ch 48000Hz SUSPENDED
PipeWire only creates the auto_null sink because there are no real
audio devices from ALSA.
Packages and firmware
---------------------
The following packages are installed and up to date:
- linux-firmware
- firmware-sof-signed
- alsa-ucm-conf
- pipewire
- pipewire-pulse
- wireplumber
- alsa-utils
- libasound2-plugins
PulseAudio is disabled and PipeWire is running as the primary audio
server.
What I have tried
-----------------
- Updated to the OEM kernel: linux-oem-24.04 (6.14.0-1015-oem)
- Reinstalled linux-firmware
- Installed firmware-sof-signed and alsa-ucm-conf
- Disabled PulseAudio (masked user pulseaudio services/sockets)
- Enabled PipeWire and pipewire-pulse and restarted WirePlumber
- Removed any custom modprobe configs and blacklists I had tried
- Reinstalled NVIDIA drivers; video stack is now working correctly
- Checked BIOS/UEFI: audio is enabled
Despite all this, the Intel audio device (8086:7f50 / 1028:0ccd) never
produces any PCM devices in ALSA. aplay -l always only shows the NVIDIA
HDMI card.
Expected behavior
-----------------
- The Intel on-board audio (Realtek/Intel codec behind 8086:7f50 / 1028:0ccd)
should be fully supported.
- ALSA should expose at least one PCM device for analog output
(speakers / headphone jack).
- PipeWire should see these devices and create one or more real sinks
instead of auto_null.
- Sound should play through the laptop's internal speakers and headphone jack.
Actual behavior
---------------
- Only the NVIDIA HDMI HDA controller is usable (card 0).
- The Intel Arrow Lake audio controller is detected but never exposes
any ALSA PCM devices.
- PipeWire only shows the auto_null sink.
- Internal speakers and headphone jack are completely unusable on Ubuntu 24.04
with the current OEM kernel.
Request
-------
This appears to be missing or incomplete support for the Intel Arrow Lake
audio device:
8086:7f50 (Intel)
1028:0ccd (Dell Alienware 18)
I would kindly ask:
- Is support for this audio device already present in any newer Ubuntu kernel
or SOF firmware, and if so, which version(s) should I test?
- If not yet supported, could this device ID be added to the appropriate
SOF / ASoC machine driver / UCM configuration?
- Are there any known workarounds (e.g. specific kernel parameters, alternative
SOF topology, or test patches) that I could try on this system?
I am happy to provide additional logs (dmesg, alsa-info, pw-dump) and to test
development kernels or patches if needed.
Thank you for your help.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.14.0-1015-oem 6.14.0-1015.15
ProcVersionSignature: Ubuntu 6.14.0-1015.15-oem 6.14.11
Uname: Linux 6.14.0-1015-oem x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: alexander 3121 F.... wireplumber
/dev/snd/seq: alexander 3117 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 17 20:09:43 2025
InstallationDate: Installed on 2025-11-07 (10 days ago)
InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
IwConfig:
lo no wireless extensions.
wlp131s0f0 no wireless extensions.
MachineType: Alienware Alienware 18 Area-51 AA18250
ProcEnviron:
LANG=ru_RU.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 nvidia-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-1015-oem root=UUID=7322735b-2b07-4fdb-8145-76ac3f0a900d ro quiet splash intel_iommu=igfx_off vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.14.0-1015-oem N/A
linux-backports-modules-6.14.0-1015-oem N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.19
SourcePackage: linux-oem-6.14
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2025
dmi.bios.release: 1.6
dmi.bios.vendor: Alienware
dmi.bios.version: 1.6.1
dmi.board.name: 0D469V
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Alienware
dmi.ec.firmware.release: 1.4
dmi.modalias: dmi:bvnAlienware:bvr1.6.1:bd07/25/2025:br1.6:efr1.4:svnAlienware:pnAlienware18Area-51AA18250:pvr:rvnAlienware:rn0D469V:rvrA00:cvnAlienware:ct10:cvr:sku0CCD:
dmi.product.family: Alienware
dmi.product.name: Alienware 18 Area-51 AA18250
dmi.product.sku: 0CCD
dmi.sys.vendor: Alienware
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Chris Chiu (mschiu77)
Status: Confirmed
** Tags: amd64 apport-bug kernel-daily-bug noble
--
No internal audio on Dell Alienware 18 (Intel Arrow Lake, 8086:7f50, 1028:0ccd) – only NVIDIA HDMI detected on Ubuntu 24.04 (6.14.0-1015-oem)
https://bugs.launchpad.net/bugs/2131689
You received this bug notification because you are subscribed to linux in Ubuntu.
[Bug 2142377] Re: Dell Alienware 18 (1028:0CCD): internal speakers broken - sof_sdw RT1320 Speaker Switch duplicate registration causes EBUSY on ARL-S platform
*** This bug is a duplicate of bug 2131689 ***
https://bugs.launchpad.net/bugs/2131689
See workaround:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.14/+bug/2131689/comments/8
** This bug has been marked a duplicate of bug 2131689
No internal audio on Dell Alienware 18 (Intel Arrow Lake, 8086:7f50, 1028:0ccd) – only NVIDIA HDMI detected on Ubuntu 24.04 (6.14.0-1015-oem)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142377
Title:
Dell Alienware 18 (1028:0CCD): internal speakers broken - sof_sdw
RT1320 Speaker Switch duplicate registration causes EBUSY on ARL-S
platform
Status in linux package in Ubuntu:
New
Bug description:
Ubuntu Release: Ubuntu 24.04.4 LTS
Kernel: 6.17.0-14-generic
SOF Firmware package: firmware-sof-signed 2023.12.1-1ubuntu1.10
Hardware: Dell Alienware 18 Area-51 AA18250
Intel Audio Chipset: 8086:7F50 (Arrow Lake, ARL-S)
Dell Subsystem ID: 1028:0CCD
Expected behavior: Internal laptop speakers produce audio output.
Actual behavior: Internal speakers produce no audio. The sof_sdw driver fails to initialize due to duplicate Speaker Switch registration. Bluetooth audio and NVIDIA HDMI audio function correctly. Only internal speakers are affected.
The following errors appear in dmesg at every boot:
sof_sdw sof_sdw: control 2:0:0:Speaker Switch:0 is already present
sof_sdw sof_sdw: ASoC: Failed to add Speaker Switch: -16
sof_sdw sof_sdw: 0x1320 controls addition failed: -16
SDW2-Playback-SmartAmp: ASoC error (-16): at snd_soc_link_init() on SDW2-Playback-SmartAmp
sof_sdw sof_sdw: error -EBUSY: snd_soc_register_card failed -16
sof_sdw sof_sdw: probe with driver sof_sdw failed with error -16
The RT1320 amplifier Speaker Switch control is being registered twice during driver initialization, causing an EBUSY conflict that fails the entire audio card registration. No user-level workaround has been found.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142377/+subscriptions
https://bugs.launchpad.net/bugs/2131689
See workaround:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.14/+bug/2131689/comments/8
** This bug has been marked a duplicate of bug 2131689
No internal audio on Dell Alienware 18 (Intel Arrow Lake, 8086:7f50, 1028:0ccd) – only NVIDIA HDMI detected on Ubuntu 24.04 (6.14.0-1015-oem)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142377
Title:
Dell Alienware 18 (1028:0CCD): internal speakers broken - sof_sdw
RT1320 Speaker Switch duplicate registration causes EBUSY on ARL-S
platform
Status in linux package in Ubuntu:
New
Bug description:
Ubuntu Release: Ubuntu 24.04.4 LTS
Kernel: 6.17.0-14-generic
SOF Firmware package: firmware-sof-signed 2023.12.1-1ubuntu1.10
Hardware: Dell Alienware 18 Area-51 AA18250
Intel Audio Chipset: 8086:7F50 (Arrow Lake, ARL-S)
Dell Subsystem ID: 1028:0CCD
Expected behavior: Internal laptop speakers produce audio output.
Actual behavior: Internal speakers produce no audio. The sof_sdw driver fails to initialize due to duplicate Speaker Switch registration. Bluetooth audio and NVIDIA HDMI audio function correctly. Only internal speakers are affected.
The following errors appear in dmesg at every boot:
sof_sdw sof_sdw: control 2:0:0:Speaker Switch:0 is already present
sof_sdw sof_sdw: ASoC: Failed to add Speaker Switch: -16
sof_sdw sof_sdw: 0x1320 controls addition failed: -16
SDW2-Playback-SmartAmp: ASoC error (-16): at snd_soc_link_init() on SDW2-Playback-SmartAmp
sof_sdw sof_sdw: error -EBUSY: snd_soc_register_card failed -16
sof_sdw sof_sdw: probe with driver sof_sdw failed with error -16
The RT1320 amplifier Speaker Switch control is being registered twice during driver initialization, causing an EBUSY conflict that fails the entire audio card registration. No user-level workaround has been found.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142377/+subscriptions
Подписаться на:
Комментарии (Atom)