-
Notifications
You must be signed in to change notification settings - Fork 139
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
No sound and alsactl init errors after updating to 1.2.13 #283
Comments
Thanks, these is the 90-alsa-restore.rules from 1.2.12:
And this is the same file from 1.2.13:
Arch Linux has not a git version, indeed it looks like f90124c and 6f7ce73 are not there yet. I just tried to manually edit the .rules file according to the second commit, it didn't work but FWIW I missed the first commit. I will try asap and let you know. |
Ok, done and reporting.
|
It's really confusing. You may check which other applications are using sound device like Also, if the mentioned information appears, UCM files are not installed or UCM code is not enabled in alsa-lib. It's not error just information. |
The only process using the device is the taskbar, killing it didn't make the difference. I also tried to run |
I think that it's a dup of alsa-project/alsa-ucm-conf#472 . UCM files must be patched, too. |
Ha ok, I saw that that issues has been fixed but just for Intel devices, right? I have an AMD chipset with Realtek ACL236 card. |
HDA config files are shared. |
My mistake, it's for Intel's SOF driver, so it won't help. |
I think I have kind of a regression after updating to the latest version. Running alsactl restore as a runit service, I have this error at startup:
And I have no sound at all. I have tried to apply the latest commit fixing the udev rule, but it didn't work. Downgrading to 1.2.12 fixes the issue.
I am running an Arch based distro (kernel 6.6) on AMD Ryzen 7 5825U CPU with Radeon graphics. My soundcard is Realtek and I have an AMD microphone array. I don't run Pulseaudio or Pipewire, just plain ALSA.
The text was updated successfully, but these errors were encountered: