Alsa fail first boot of the day

Just like it says. First boot of the morning. And this is with my older machine. Two years back that machine was running a Phenom II X4 CPU. However, when the SSD failed I decided to rebuild that computer with a new (used) motherboard, new SSD and a new case and CPU cooler. So now I am running a Phenom II X6 1055T CPU. The motherboard is a Biostar TA970 that has been updated to the most recent BIOS when I got it.

My son was a bit confused why I wanted to do what seemed like such a small upgrade. But it was really kind of a budget move. I could get everything quite cheap and also still use the DDR3 that I had. If I had gone further up the line then that would have meant switching over to DDR4. I considered going with a Bulldozer processor but as many of you may know the reviews for those were less than glowing.

Also it has been working quite well. It has only been recently that I have seen some issues creeping up after the first boot of the day. And after a reboot the issue went away and everything works fine.

So the issue is this… Everything booted up fine and I thought I was good to go until I noticed an issue with the volume not responding. Odd. So I went to the terminal and did a journalctl -b -p err and it showed that alsa had failed to initialize properly with the hardware. So I really don’t know why that happened. After a reboot everything is back to normal. Makes me wonder if this is an issue with the older hardware starting to get flaky or if it was maybe a timing issue. The only other issue that I had when I looked at the error messages was that xscreensaver had crashed.

Here are the error messages. Clearly alsa was not working as it should and that led to the volume control not working. Anyway, after a reboot everything is quite fine. As always. These issues always seem to happen on the first boot of the day for some reason.

Nov 05 16:18:55 fedora dbus-broker-launch[748]: Activation request for 'org.freedesktop.RealtimeKit1' failed.
Nov 05 16:18:55 fedora dbus-broker-launch[748]: Activation request for 'org.freedesktop.RealtimeKit1' failed.
Nov 05 16:18:55 fedora dbus-broker-launch[748]: Activation request for 'org.freedesktop.RealtimeKit1' failed.
Nov 05 16:18:55 fedora wireplumber[15364]: spa.alsa: error pcm info: Permission denied
Nov 05 16:18:55 fedora dbus-broker-launch[748]: Activation request for 'org.freedesktop.RealtimeKit1' failed.
Nov 05 16:18:55 fedora wireplumber[15364]: spa.alsa: error pcm info: Permission denied
Nov 05 16:18:55 fedora wireplumber[15364]: spa.alsa: error pcm info: Permission denied
Nov 05 16:18:55 fedora wireplumber[15364]: spa.alsa: Card can't get card_name from card_index 0
Nov 05 16:18:55 fedora wireplumber[15364]: spa.alsa: can't open control for card hw:0: Permission denied
Nov 05 16:18:55 fedora dbus-broker-launch[748]: Activation request for 'org.freedesktop.nm_dispatcher' failed.

I am not getting these issues on my newer computer which runs an 8 core Zen CPU and has a new motherboard in it. That one is rock solid. So possibly that points to the older hardware just not working as well. Has me thinking that maybe in the near future another upgrade might be in the works. But for now everything is working fine and I can run both computers off the same monitor and keyboard with a KVM switch. And I have backup in case one computer takes a dump.

1 Like