Re: No sound unless I toggle a GPIO pin
Paul Menzel <[email protected]> Wed, 28 Apr 2021 14:19:30 +0200
| Newsgroups | gmane.linux.alsa.user |
|---|---|
| Message-ID | <[email protected]> |
Dear Paul, Am 28.04.21 um 13:15 schrieb Paul Koster: > Hope you can help with me this. Got myself a brand new HP ENVY > all-in-One with B&O speakers built-in. No sound at all whereas all > controls and settings seem to work without hiccups. Turns out a GPIO pin > needs to be set. Found this out using hda-analyzer python script. Now I > execute this script on start-up to make it work: > > /usr/bin/hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x04 > /usr/bin/hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIRECTION 0x04 > /usr/bin/hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x04 > > The strange thing is, when I close applications using sound, the system > goes mute within a minute or so and I have to run hda-analyzer to toggle > the 'enable' settings of this GPIO pin. > > For now I run the gnome settings widget at startup, displaying the sound > settings and running the hda-verb commands above. This seems enough to > leave the sound on. Nice analysis. > Is there a better solution to work around this GPIO pin issue? Yes, it should be fixed in the Linux kernel. Please create an issue in the Linux Bugzilla [1] as described in [1], and attach the `alsa-info.sh` output there. Kind regards, Paul PS: I recommend to only buy systems with official GNU/Linux support like Google Chromebooks, Puri.sm, System76, Dell, Lenovo (and probably others). That way the right companies get your money. [1]: https://www.alsa-project.org/wiki/Bug_Tracking