-
-
Notifications
You must be signed in to change notification settings - Fork 651
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Legion 16irx8h Speaker Issue #1039
Comments
Running this script https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/6/8306.2pa_2D00_byps.sh as root via |
Another related discussion including several hacks https://forums.lenovo.com/t5/Ubuntu/Ubuntu-and-legion-pro-7-16IRX8H-audio-issues/m-p/5210709?page=32 |
Same issue here with my Lenovo Legion Pro 7 16IRX9H. Maybe related: https://discourse.nixos.org/t/sound-speaker-problem-after-connect-bluetooth-device/52443 (no solution). |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/sound-speaker-problem-after-connect-bluetooth-device/52443/1 |
I found a (temporary?) solution at: New Lenovo Legion 7 Pro (2023) no sound from speakers in Linux (Reddit) It worked to me. I added it to my configuration file:
PR: #1227 |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/sound-speaker-problem-after-connect-bluetooth-device/52443/2 |
Using the nixos-hardware/lenovo/legion/16irx8h with latest (6.9.8) linux kernel. Speaker seem to work for a few minutes after boot, then get disabled/shutdown. I could not find any related logs in journalctl -b.
I tried the default kernel 6.6 as well, same result. There is a firmware specified in https://forums.lenovo.com/t5/Ubuntu/Ubuntu-and-legion-pro-7-16IRX8H-audio-issues/m-p/5210709?page=22#6155866 firmware-TAS-2781... However this requires copying to /lib/firmware normally. I'm not very familiar with NixOS architecture just yet, any help is appreciated to make the 16irx8h work perfectly.
Another related discussion here clearlinux/distribution#2992
The text was updated successfully, but these errors were encountered: