Skip to content

HP Elitebook X (Panther Lake) - no sound. #5760

New issue
New issue
Closed
Closed
HP Elitebook X (Panther Lake) - no sound.#5760

Description

@Fiedzia
Fiedzia
opened on May 5, 2026

I am trying to get sound on my new laptop, but it is silent so far. Bluetooth headphones work fine.
Kubuntu 26.04, kernel 7.1-rc1 (7.0 doesn't work either)

All relevant log files (cannot paste here due to size limit):
https://github.com/Fiedzia/HP-Elitebook-X-Panther-Lake-info

---alsainfo---
Your ALSA information is located at http://alsa-project.org/db/?f=d62e2163decda1e2c0649814646c2effe658ef94
---lspci---
0:00.0 Host bridge: Intel Corporation Device b001 (rev 04)
0:02.0 VGA compatible controller: Intel Corporation Panther Lake [Arc B390] (rev 04)
0:04.0 Signal processing controller: Intel Corporation Panther Lake Innovation Platform Framework Processor Participant (rev 04)
0:05.0 Multimedia controller: Intel Corporation Panther Lake IPU (rev 04)
0:06.0 PCI bridge: Intel Corporation Device e461 (rev 01)
0:07.0 PCI bridge: Intel Corporation Device e44e
0:07.2 PCI bridge: Intel Corporation Device e460
0:0a.0 Signal processing controller: Intel Corporation Panther Lake Platform Monitoring Technology (PMT) (rev 04)
0:0b.0 Processing accelerators: Intel Corporation Panther Lake NPU (rev 04)
0:0d.0 USB controller: Intel Corporation Device e431
0:0d.2 USB controller: Intel Corporation Device e433
0:0d.3 USB controller: Intel Corporation Device e434
0:12.0 Serial controller: Intel Corporation Device e445 (rev 01)
0:13.0 Communication controller: Intel Corporation Device e462 (rev 01)
0:14.0 USB controller: Intel Corporation Device e47d (rev 01)
0:14.2 RAM memory: Intel Corporation Device e47f (rev 01)
0:14.3 Network controller: Intel Corporation Device e440 (rev 01)
0:14.7 Bluetooth: Intel Corporation Device e476 (rev 01)
0:15.0 Serial bus controller: Intel Corporation Device e478 (rev 01)
0:15.1 Serial bus controller: Intel Corporation Device e479 (rev 01)
0:15.2 Serial bus controller: Intel Corporation Device e47a (rev 01)
0:15.3 Serial bus controller: Intel Corporation Device e47b (rev 01)
0:16.0 Communication controller: Intel Corporation Device e470 (rev 01)
0:18.0 Communication controller: Intel Corporation Device e45d (rev 01)
0:1c.0 PCI bridge: Intel Corporation Device e43a (rev 01)
0:1f.0 ISA bridge: Intel Corporation Device e402 (rev 01)
0:1f.3 Multimedia audio controller: Intel Corporation Device e428 (rev 01)
0:1f.4 SMBus: Intel Corporation Device e422 (rev 01)
0:1f.5 Serial bus controller: Intel Corporation Device e423 (rev 01)
1:00.0 Non-Volatile memory controller: SK hynix PVC10 NVMe Solid State Drive (DRAM-less)
6:00.0 Cellular controller/modem: MEDIATEK Corp. T700 5G Modem [5G Solution 5000] (rev 01)

Activity

  1. bardliao commented on May 7, 2026

    @bardliao
    bardliao
    on May 7, 2026
    Collaborator

    @Fiedzia It looks like your playback devices are listed. Can you try aplay -Dhw:0,0 file.wav to polay the wav file via headphone jack?

    **** List of PLAYBACK Hardware Devices ****
card 0: sofsoundwire [sof-soundwire], device 0: Jack Out (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsoundwire [sof-soundwire], device 5: HDMI1 (*) [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsoundwire [sof-soundwire], device 6: HDMI2 (*) [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsoundwire [sof-soundwire], device 7: HDMI3 (*) [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsoundwire [sof-soundwire], device 31: Deepbuffer Jack Out (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

    Also, please rename sof-dyndbg.conf.txt to sof-dyndbg.conf and put it in the /etc/modprobe.d/ folder, and get the dmesg log after reboot?

  2. bardliao commented on May 7, 2026

    @bardliao
    bardliao
    on May 7, 2026
    Collaborator
    !!ACPI SoundWire Device Status Information
!!---------------

TI 0x0002390102000001
TI 0x00023a0102000001
TI 0x00023c0102000001
TI 0x00023d0102000001
Realtek 0x000330025d071201

    And the Speaker device is not listed.
    @niranjanhyti FYI

  3. niranjanhyti commented on May 7, 2026

    @niranjanhyti
    niranjanhyti
    on May 7, 2026
    Collaborator
    2026-05-05T21:44:42.817984+01:00 maciej-hp kernel: acpi device:1d: function type only supported as DisCo constant
2026-05-05T21:44:42.818987+01:00 maciej-hp kernel: acpi device:1f: function type only supported as DisCo constant
2026-05-05T21:44:42.818998+01:00 maciej-hp kernel: acpi device:21: function type only supported as DisCo constant
2026-05-05T21:44:42.819000+01:00 maciej-hp kernel: acpi device:23: function type only supported as DisCo constant

    Could we please also get the acpi dump ?

    sudo apt install acpica-tools
sudo acpidump > acpitable.dat

    Please share acpitable.dat

  4. Fiedzia commented on May 8, 2026

    @Fiedzia
    Fiedzia
    on May 8, 2026
    Author

    aplay file.wav
    works with headphone jack.
    aplay -Dhw:0,0 file.wav
    does not:

    Playing WAVE '/usr/share/sounds/sound-icons/trumpet-1.wav' : Signed 16 bit Little Endian, Rate 16000 Hz, Mono
    aplay: set_params:1404: Channels count not available

    (I'm using kubuntu with pipewire)

    updated logs and acpitable.dat:
    https://github.com/Fiedzia/HP-Elitebook-X-Panther-Lake-info

  5. charleskeepax commented on May 8, 2026

    @charleskeepax
    charleskeepax
    on May 8, 2026

    I don't know if your device intends to use non-DC function types, but a decision was made fairly early on in the SoundWire stuff to not support that. Which is what this message is complaining about:

    2026-05-05T21:44:42.819000+01:00 maciej-hp kernel: acpi device:23: function type only supported as DisCo constant

    There was some debate about this, and I was slightly concerned we would see devices with more dynamic functions. But it was decided to go this route such that the functions could be parsed before the devices were available to allow the handling of quirks (see sdca_device.c).

  6. Fiedzia commented on May 9, 2026

    @Fiedzia
    Fiedzia
    on May 9, 2026
    Author

    Is there something I can do to?

  7. Fiedzia commented on May 11, 2026

    @Fiedzia
    Fiedzia
    on May 11, 2026
    Author

    I've found ubuntu work on this issue:
    https://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg6271242.html

  8. Fiedzia commented on May 11, 2026

    @Fiedzia
    Fiedzia
    on May 11, 2026
    Author

    I've got the patch from the thread mentioned above and the sound is now working.
    It turned out that for this specific device, it is necessary to assume function_type = SDCA_FUNCTION_TYPE_SMART_AMP if reading mipi-sdca-control-dc-value fails.
    Now aplay -l lists speaker device that previously wasn't there. I will create PR for that.

  9. niranjanhyti commented on May 12, 2026

    @niranjanhyti
    niranjanhyti
    on May 12, 2026
    Collaborator

    I don't know if your device intends to use non-DC function types, but a decision was made fairly early on in the SoundWire stuff to > not support that. Which is what this message is complaining about:

    Thanks.
    I think the BIOS which is being was prepared for other OS and being used for Ubuntu as well.
    In the recent BIOS we have been updating these to use DC value instead of read only values for this.

    The solution would be to update the BIOS
    change mipi-sdca-control-0x5-subproperties for both the addresses below
    Name (_ADR, 0x0002390102000001)
    Name (_ADR, 0x00023D0102000001)

    from

     Package (0x02)
{ "mipi-sdca-control-access-mode", 0x03 }

    to

     Package (2) {"mipi-sdca-control-access-mode", 5},
Package (2) {"mipi-sdca-control-dc-value", 1}

  10. Fiedzia commented on May 13, 2026

    @Fiedzia
    Fiedzia
    on May 13, 2026
    Author

    Updated bios also solved the problem

  11. bardliao commented on May 27, 2026

    @bardliao
    bardliao
    on May 27, 2026
    Collaborator

    @Fiedzia Can we close the issue?

  12. bardliao
    closed this as completedon Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions