The latest linux-rpi4-rc kernel packages has been pushed to the unstable branch when the mirrors sync. In testing I did not see any difference than the last version.
linux-rpi4-rc 5.15.rc4-1
linux-rpi4-rc-headers 5.15.rc4-1
5.16 sounds like a big update with this feature and zstd updated to 1.4.10.
I guess that will provide some new ways for kernel image compression from Archlinux… wait & see!
pi4 boot from usb, mmc1: Controller never released inhibit bit(s)
this is quite some time, what is that?
Not really sure but researching it has appeared from different types of installs with people but in each case a fresh install fixed it. If it was me I would first try reinstalling the kernel and the 2 raspberrypi-bootloader packages. I would also switch to the stable firmware with the eeprom if you are not already there with it.
There are also some cases with bad sdcards but that does not seem to be the issue with you as you are booting with usb.
kernel & bootloader both in testing.
eeprom stable & beta both same issue message.
I boot on usb, but I have different messages:
dmesg | grep mmc1
[ 0.769758] mmc1: new high speed SDIO card at address 0001
[ 5.191383] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.bin failed with error -2
kernel 5.15.0-rc4-1
Long story short the brcmfmac43455-sdio.raspberrypi,4-model-b.bin can be ignored. It just looks for it first in /usr/lib/firmware/updates/brcm/ but winds up using brcmfmac43455-sdio.bin for wifi.
the message is on screen every booting not in log.
The latest linux-rpi4-rc kernel packages has been pushed to the unstable branch when the mirrors sync. They seem to be concentrating on the -rc kernel lately but not the others. Been over a month since a linux-rpi4 upgrade.
linux-rpi4-rc 5.15.rc5-1
linux-rpi4-rc-headers 5.15.rc5-1
The latest linux-rpi4 / linux-rpi4-mainline kernels and the 2 new raspberrypi-bootloader packages has been pushed to the unstable branch when the mirrors sync.
linux-rpi4 5.10.64-1
linux-rpi4-headers 5.10.64-1
linux-rpi4-mainline 5.14.12-1
linux-rpi4-mainline-headers 5.14.12-1
raspberrypi-bootloader 20211013-1
raspberrypi-bootloader-x 20211013-1
After the pitiful upgrade yesterday with the linux-rpi4 kernel they went whole hog today. No rest for the weary…
linux-rpi4 5.10.73-1
linux-rpi4-headers 5.10.73-1
Please refer to my post here so I do not re-type if you have a no sound issue or intermittent broken sound with fkms.
https://forum.manjaro.org/t/i-have-no-sound-output-through-hdmi-on-5-10-73-1-or-5-14-or-5-15/86485/6
With the 5.10.73 kernel
Not that it is an issue for me, but if you use fbturbo (fbdev)… there does not seem to be a good working alsa setting. Either just headphones or both alsa and hdmi.
snd-bcm2835.enable_compat_alsa=1 snd_bcm2835.enable_headphones=1
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
Subdevices: 3/3
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 IEC958/HDMI [bcm2835 IEC958/HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: ALSA [bcm2835 ALSA], device 2: bcm2835 IEC958/HDMI1 [bcm2835 IEC958/HDMI1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
card 2: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
snd-bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_headphones=1
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
This is why I used vc4 but with the v3d disabled. I would get vc4 sound and could set alsa=0.
Edit: Also the vcio rewrite was merged this morning.
Edit 2: I am going to test the sound with alsa=1. Previously the pi4 would hang if you played sound… back in a bit with the results.
Edit 3: I tested on plasma with alsa=1. I see 2 analog sound and 1 headphone. I do not have hdmi sound on this monitor but I do have headphones. I am unable to get sound out from the headphone jack. I can switch to headphones but sound is never directed out the headphones. Only the center option, one of the two Analog Sound options has a moving output level, but the level never switches to headphones. So no headphone sound.
I have been with the Rpi people for 2 days working on this sound issue that really has been going on for 2 months with the newer kernels and now has crept into 5.10. Today they pushed the fix.
https://github.com/raspberrypi/linux/issues/4634
Long story short I have pushed a new 5.10 kernel with the fix to all branches when the mirrors sync.
This new kernel will install a new cmdline.txt and back up the old one so if someone has some custom configs in it they can refer to the backup and add back to the new cmdline.txt as long as snd-bcm2835.enable_compat_alsa=whatever & snd_bcm2835.enable_headphones=1 is not added back.
I hate to mess with someone’s custom config’s but I am trying to avoid another firestorm over this yet again needed config changes and be compatible with the new images that were released yesterday because some do not like to search/read the forum before they post an issue.
With this new kernel you will do like before to switch back and forth between fkms/kms in config.txt and do not have to mess with cmdline.txt at all.
The sound cards look better now also.
FKMS:
**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
KMS:
**** List of PLAYBACK Hardware Devices ****
card 0: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 1: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
Packages Removed
New cmdline.txt, is the root=PARTUUID= desired?
root=PARTUUID= rw rootwait console=serial0,115200 console=tty1 selinux=0 plymouth.enable=0 smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 kgdboc=serial0,115200 usbhid.mousepoll=8 audit=0
If UUID= works for you it would be ok. I ran into an issue doing something I can not remember what where UUID= caused an issue. Seems like it was with one of the pi3’s.
I currently have root=PARTUUID=d819ecca-0eca-4278-a113-ae52e06de5a8. I did not think a empty partuuid would work. But I will give it a try.
I reverted back to firmware booting and performed the update, then rebooted. But then the device PARTUUID= was not found, no rootfs for switchroot. I will need to revert cmdline.txt, or edit it and add my partuuid. Folks should do that before rebooting, after the update.
Edit: After editing cmdline.txt, it booted.
Not really sure what you are referring to. Is this you booted with UEFI. I have not seen it not finding the root PARTUUID here with a regular image. The The kernel post install scripts finds it ok here. This has not changed and been there for a long time. It in the past would not mess with the cmdline.txt unless it did not exist but it has been PARTUUID in the last 3 or 4 new images released.
[ray@pi4 ~]$ cat /boot/cmdline.txt
root=PARTUUID=b75fdbb1-02 rw rootwait console=serial0,115200 console=tty1 selinux=0 plymouth.enable=0 smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 kgdboc=serial0,115200 usbhid.mousepoll=8 audit=0
The cmdline.txt file that was installed with the kernel update is not good. It will not boot with root=PARTUUID=