This is happening only with last rc kernel. was working with previous just fine. Thanks for fast answer Darksky.
I successfully updated to the new rc from mainline, without issue. The kernel upgrade went smoothly. I reviewed dmesg and journalctl for issues but did not see anything out of the ordinary. However I do have these errors but they existed on 5.10.
Jan 07 17:14:56 future kernel: vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
Jan 07 17:14:56 future kernel: vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
Jan 07 17:14:56 future kernel: vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
Jan 07 17:14:56 future kernel: vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
Jan 07 17:14:56 future kernel: vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
A fix is in the works. It involves pulseaudio too and I do see these pulseaudio complaints:
Jan 07 17:14:56 future pulseaudio[793]: Failed to find a working profile.
Jan 07 17:14:56 future pulseaudio[793]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="platform-fef05700.hdmi" card_name="alsa_card.platform-fef05700.hdmi" namereg_fail=false tsched=no fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed.
Jan 07 17:14:56 future dbus-daemon[491]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.31' (uid=1000 pid=793 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo")
Jan 07 17:14:56 future pulseaudio[793]: module-rescue-stream is obsolete and should no longer be loaded. Please remove it from your configuration.
Jan 07 17:14:57 future pulseaudio[793]: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found.
Jan 07 17:15:00 future systemd[617]: pulseaudio.socket: Succeeded.
Jan 07 17:15:04 future plasmashell[781]: org.kde.plasma.pulseaudio: No object for name "alsa_output.platform-fef00700.hdmi.iec958-stereo.monitor"
Jan 07 17:24:09 future pulseaudio[793]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Jan 07 17:24:09 future pulseaudio[793]: Most likely this is a bug in the ALSA driver 'vc4'. Please report this issue to the ALSA developers.
Jan 07 17:24:09 future pulseaudio[793]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
But I do have working audio in chromium via HDMI and volume control in Plasma.
Thanks for reporting and your research.
sounds ok for me, thanks !
1 Like
The latest linux-rpi4-mainline / linux-rpi4-rc kernel packages and the latest 2 raspberrypi-bootloader packages has been pushed to the unstable branch when the mirrors sync.
linux-rpi4-mainline 5.10.6-1
linux-rpi4-mainline-headers 5.10.6-1
linux-rpi4-rc 5.11.rc3-1
linux-rpi4-rc-headers 5.11.rc3-1
raspberrypi-bootloader 20210111-1
raspberrypi-bootloader-x 20210111-1An upgraded rpi-eeprom-git 20210112-1 package has been pushed to the unstable branch when the mirrors sync for those who like to live on the edge. The beta firmware folder was updated to a new image yesterday:
[ray@pi4 ~]$ sudo rpi-eeprom-update -r
Removing temporary files from previous EEPROM update
[ray@pi4 ~]$
[ray@pi4 ~]$ sudo rpi-eeprom-update
BCM2711 detected
VL805 firmware in bootloader EEPROM
BOOTLOADER: up-to-date
CURRENT: Mon Jan 11 03:44:33 PM UTC 2021 (1610379873)
LATEST: Mon Jan 11 03:44:33 PM UTC 2021 (1610379873)
FW DIR: /lib/firmware/raspberrypi/bootloader/beta
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000138a1Hello! I have a quick question–I want to make sure I’m interpreting the output of rpi-eeprom-update correctly. Here’s my current output:
~]$ sudo rpi-eeprom-update
BCM2711 detected
Dedicated VL805 EEPROM detected
BOOTLOADER: up-to-date
CURRENT: Thu Sep 3 12:11:43 PM UTC 2020 (1599135103)
LATEST: Thu Sep 3 12:11:43 PM UTC 2020 (1599135103)FW DIR: /lib/firmware/raspberrypi/bootloader/stable
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000138a1
The way I’m reading it, the VL805 firmware has not changed in the beta branch, but the bootloader has?
Correct but you need to be in the beta FW directory to change it instead of stable.
Thanks. I only switched to the stable branch to get USB boot support and the 5.10 kernel. I’m wary of installing beta firmware. 
Is there a changelog somewhere for the boot loader?
Thanks!
EDIT: Since installing an SSD and booting from USB to that drive, I have run into the issue of timeouts on restart with the USB drive preventing boot.
I just switch off the Pi, then switch it back on, and it comes up fine.
Is that what the release notes for the boot loader are referring to?
Sounds like it to me.
Linuxrpi4-mainline kernel was upgraded again today. So the new kernel related packages has been pushed to the unstable branch when the mirrors sync.
No new activity involving the raspberrypi-bootloader packages as of this post.
linux-rpi4-mainline 5.10.7-1
linux-rpi4-mainline-headers 5.10.7-1
1 Like
These latest kernel/kernel-headers and rpi bootloader packages have been pushed to the unstable branch when the mirrors sync:
linux-rpi4-mainline 5.10.9-1
linux-rpi4-mainline-headers 5.10.9-1
linux-rpi4-rc 5.11.rc4-1
linux-rpi4-rc-headers 5.11.rc4-1
raspberrypi-bootloader 20210121-1
raspberrypi-bootloader-x 20210121-1
1 Like
rc and bootloader update were uneventful, thank you.
Edit: I then switch to mainline and it too went smoothly.
1 Like
5.10.10 is out.
So is 5.11-rc5. Today was my go to town day for groceries. I just got home.
The latest kernel/kernel-headers/bootloader packages has been pushed to the unstable branch when the mirrors sync.
linux-rpi4-mainline 5.10.10-1
linux-rpi4-mainline-headers 5.10.10-1
linux-rpi4-rc 5.11.rc5-1
linux-rpi4-rc-headers 5.11.rc5-1
raspberrypi-bootloader 20210125-1
raspberrypi-bootloader-x 20210125-1
1 Like
Update went smoothly, both kernels tested.
1 Like
PiOS update /lib/firmware/brcm files, which package manjaro concern?