Christer Solskogen

Results 45 comments of Christer Solskogen

You'll probably have a better time with amiberry instead of FS-UAE on the Pi.

"BOOT FAILED. EFI Hard drive"

This is probably the same problem as I've reported here: https://github.com/raspberrypi/Raspberry-Pi-OS-64bit/issues/157 Try installing pulseaudio, see if that works.

kms. Sound works fine with fkms. pi@raspberrypi:~ $ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM vc4-hdmi-hifi-0 [MAI PCM vc4-hdmi-hifi-0] Subdevices:...

Oh, sorry. This is a Raspberry Pi 400.

`console=serial0,115200 console=tty1 root=PARTUUID=34d911c0-02 rootfstype=ext4 elevator=deadline rootwait quiet ` But /proc/cmdline says: `coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:D2:C2:C3 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=34d911c0-02 rootfstype=ext4 elevator=deadline rootwait quiet`

This is 2021-05-07-raspios-buster-arm64-lite, but fully updated. I'm getting the same output as you of aplay -l if I use fkms instead of kms. But kms is the default.

`dtoverlay=vc4-kms-v3d` is the default setting in config.txt on 2021-05-07-raspios-buster-arm64-lite

Pi4 is also affected.

For some odd reason, installing pulseaudio fixes this...