View Issue Details

IDProjectCategoryView StatusLast Update
0001443channel: elrepo/el9--elrepo--request-for-enhancement--public2024-08-20 21:55
Reporterpseud Assigned Totqhoang  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Platformx86-64 
Summary0001443: driver for 'Intel Corporation Broadwell-U Audio Controller [8086:160c]'?
DescriptionThis is v old snd issue with HP Spectra x360 13 circa 2015 reported (and solved) here:
https://h30434.www3.hp.com/t5/Notebook-Audio/HP-spectre-x360-on-linux/m-p/5122160/highlight/true#M66839
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1441852
I've recently had to press some old kit into operation due to new kit being underwhelming and needing return. I've had Fedora on this until about 2022, then PureOS (Debian derivative) and for it's most recent lease of life, Almalinux. I solved the sound issue years ago with the grub fix mentioned in the links above and haven't thought about it since until installing Almalinux. I believe (guess) the drivers were put in linux so the grub edits became unnecessary through my distro changes - I'm wonder if this isn't working with Alma because the machine is now so old that the drivers have come back out of linux? I've checked `8086:160c` against the DeviceIDs and found nil - but, wondered about asking here if this rings any bells?
Thanks
```
$ dmesg -t | egrep "(audio|snd|INT3438)"
DMAR: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0
snd_hda_intel 0000:00:03.0: enabling device (0000 -> 0002)
intel_catpt INT3438:00: DesignWare DMA Controller, 8 channels
snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
```
`00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller [8086:160c] (rev 09)`
TagsNo tags attached.

Activities

tqhoang

2024-04-22 16:46

manager   ~0009697

Last edited: 2024-04-22 17:19

Just adding that this issue is also tracked in Red Hat's bugzilla. Notable comments are 5, 6, and 10 with the corrected workaround.
https://bugzilla.redhat.com/show_bug.cgi?id=1220709

If the above corrected workaround doesn't work anymore, there isn't proper Linux support in the laptop's ACPI DSDT/SSDT tables.

pseud

2024-04-23 09:53

reporter   ~0009698

Thanks @tqhoang - yes, I know that bug. The workaround does still work, I'm using it. However, I haven't needed the workaround for probably 5 years - the kernel has been working without modding the the GRUB command. I had been running PureOS (Debian derivative) for a few years without issue - CentoOS and Fedora before that. So, perhaps a driver has been removed from the Alma linux, idk?

tqhoang

2024-04-29 09:59

manager   ~0009703

If the workaround does still work for you with AlmaLinux 8, then the RHEL kernel driver is present, but just buggy still.

Not sure if it's much different than editing your GRUB config, but have you tried configuring the kernel module to set the default audio output to the PCH instead of the HDMI device?
Ex: https://wiki.archlinux.org/title/Dell_XPS_13_(9343)#Audio

pseud

2024-04-29 13:24

reporter   ~0009704

Hmm, that was a mistake to report against el8 - it should have been 9... Can that be changed?
Thank you for the Arch wiki pointer - I'll follow that up and report back.

toracat

2024-04-29 13:27

administrator   ~0009705

Moved to el9.

pseud

2024-05-19 17:07

reporter   ~0009773

I notice this has been recently reassigned to @tqhoang.
I would be embarrassed if anyone spent time thinking about this before I did more thinking myself.
I have a recollection that a BIOS update sometime before I stopped using Fedora solved the problem and I wonder if I might have wiped that update through the various os changes I've gone through since.
The present BIOS is 2018 and there's a more recent one 2020. I should update to that before anything else.
Thanks.

tqhoang

2024-05-20 10:21

manager   ~0009776

Last edited: 2024-07-10 08:56

Thanks for the update @pseud. Please let us know if the latest BIOS fixes it for you.

It's out of scope for ELRepo to fix, but this is likely an issue with the ACPI DSDT and how they handle the OS string "Linux" versus some "Windows xxxx" versions. I've seen cases where there is an setup routine for "Windows xxxx" but hardly anything for "Linux". It would cause a lot of problems with audio and Bluetooth either on boot up or resume from standby.

tqhoang

2024-06-07 10:23

manager   ~0009825

@pseud - Any luck with the BIOS update?

tqhoang

2024-08-20 21:55

manager   ~0010043

Closing this ticket since this has been inactive for a few months. This is more of an issue with Red Hat's kernel and should be reported to their bug tracking system.

Issue History

Date Modified Username Field Change
2024-04-07 09:11 pseud New Issue
2024-04-07 09:11 pseud Status new => assigned
2024-04-07 09:11 pseud Assigned To => toracat
2024-04-22 16:46 tqhoang Note Added: 0009697
2024-04-22 17:19 tqhoang Note Edited: 0009697
2024-04-23 09:53 pseud Note Added: 0009698
2024-04-29 09:59 tqhoang Note Added: 0009703
2024-04-29 13:24 pseud Note Added: 0009704
2024-04-29 13:26 toracat Project channel: elrepo/el8 => channel: elrepo/el9
2024-04-29 13:27 toracat Note Added: 0009705
2024-05-16 13:01 toracat Assigned To toracat => tqhoang
2024-05-19 17:07 pseud Note Added: 0009773
2024-05-20 10:21 tqhoang Note Added: 0009776
2024-06-07 10:23 tqhoang Status assigned => feedback
2024-06-07 10:23 tqhoang Note Added: 0009825
2024-07-10 08:56 tqhoang Note Edited: 0009776
2024-08-20 21:55 tqhoang Status feedback => closed
2024-08-20 21:55 tqhoang Resolution open => no change required
2024-08-20 21:55 tqhoang Note Added: 0010043