Pi 4 - Bullseye Support

Hi All,

I absolutely love the SATA hat but I’m curious how many of you have upgraded from Raspbian Buster to Bullseye on the Raspberry Pi 4B and how well supported it is with the SATA hat?

I’m trying to determine if it’s worth the upgrade because if it gives too much trouble with the SATA hat it might be better to stick to Buster for now.

Cheers
Anigai

Hello, I will test it in two days.

Great to hear, thank you setq :smiley:

I upgraded my Raspbian OS from Buster to Bullseye.
I had to reinstall the SATA HAT “driver”, but it’s working fine for me.

Only annoying thing: The CPU fan start spin with white noise, when I log in over SSH or over Desktop.
And it never stop. Only if you reboot your system and don’t log in again.

On Buster, I had this problem only when I logged in over Desktop.
But now, the problem is present when you log in over SSH.

Imagine, if you log in over SSH you have to reboot your system after you did what you want.

I tried to investigate the case more than many days.
It has something to do with the pulseaudio.

If the top fan starts to spin faster (at 100%), there is not noise.
But after it spin down a little, you can hear it again.

I don’t know what the pulseaudio doing in the background or why.

@setq do you have any idea what could be the problem or do you try to investigate the case?

Here is the journalctl log about this:

nov 22 12:46:41 raspberry-pi-4 sshd[8138]: Accepted publickey for pi from 192.168.0.100 port 57171 ssh2: RSA SHA256:6gcS5Zn0rMPXn6SAymABm2TNr4mYYnE9DRAHGR/J+e4
nov 22 12:46:41 raspberry-pi-4 sshd[8138]: pam_unix(sshd:session): session opened for user pi(uid=1000) by (uid=0)
nov 22 12:46:42 raspberry-pi-4 systemd-logind[420]: New session 288 of user pi.
nov 22 12:46:42 raspberry-pi-4 systemd[1]: Created slice User Slice of UID 1000.
nov 22 12:46:42 raspberry-pi-4 systemd[1]: Starting User Runtime Directory /run/user/1000...
nov 22 12:46:42 raspberry-pi-4 systemd[1]: Finished User Runtime Directory /run/user/1000.
nov 22 12:46:42 raspberry-pi-4 systemd[1]: Starting User Manager for UID 1000...
nov 22 12:46:42 raspberry-pi-4 systemd[8174]: pam_unix(systemd-user:session): session opened for user pi(uid=1000) by (uid=0)
nov 22 12:46:43 raspberry-pi-4 systemd[8174]: Queued start job for default target Main User Target.
nov 22 12:46:43 raspberry-pi-4 systemd[8174]: Created slice User Application Slice.
nov 22 12:46:43 raspberry-pi-4 systemd[8174]: Reached target Paths.
nov 22 12:46:43 raspberry-pi-4 systemd[8174]: Reached target Timers.
nov 22 12:46:43 raspberry-pi-4 systemd[8174]: Starting D-Bus User Message Bus Socket.
nov 22 12:46:43 raspberry-pi-4 systemd[8174]: Listening on GnuPG network certificate management daemon.
nov 22 12:46:43 raspberry-pi-4 systemd[8174]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
nov 22 12:46:43 raspberry-pi-4 systemd[8174]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
nov 22 12:46:43 raspberry-pi-4 systemd[8174]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
nov 22 12:46:43 raspberry-pi-4 systemd[8174]: Listening on GnuPG cryptographic agent and passphrase cache.
nov 22 12:46:43 raspberry-pi-4 systemd[8174]: Listening on Multimedia System.
nov 22 12:46:43 raspberry-pi-4 systemd[8174]: Listening on debconf communication socket.
nov 22 12:46:43 raspberry-pi-4 systemd[8174]: Listening on Sound System.
nov 22 12:46:43 raspberry-pi-4 systemd[8174]: Listening on D-Bus User Message Bus Socket.
nov 22 12:46:43 raspberry-pi-4 systemd[8174]: Reached target Sockets.
nov 22 12:46:43 raspberry-pi-4 systemd[8174]: Reached target Basic System.
nov 22 12:46:43 raspberry-pi-4 systemd[1]: Started User Manager for UID 1000.
nov 22 12:46:43 raspberry-pi-4 systemd[1]: Started Session 288 of user pi.
nov 22 12:46:43 raspberry-pi-4 systemd[8174]: Started Multimedia Service.
nov 22 12:46:43 raspberry-pi-4 systemd[8174]: Starting Sound Service...
nov 22 12:46:43 raspberry-pi-4 pipewire[8200]: could not set nice-level to -11: No such file or directory
nov 22 12:46:43 raspberry-pi-4 pipewire[8200]: could not make thread realtime: No such file or directory
nov 22 12:46:44 raspberry-pi-4 systemd[8174]: Started D-Bus User Message Bus.
nov 22 12:46:44 raspberry-pi-4 pipewire[8200]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
nov 22 12:46:44 raspberry-pi-4 pipewire-media-session[8211]: could not set nice-level to -11: No such file or directory
nov 22 12:46:44 raspberry-pi-4 pipewire-media-session[8211]: could not make thread realtime: No such file or directory
nov 22 12:46:44 raspberry-pi-4 kernel: hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
nov 22 12:46:44 raspberry-pi-4 kernel: hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
nov 22 12:46:44 raspberry-pi-4 kernel: hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
nov 22 12:46:44 raspberry-pi-4 kernel: hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
nov 22 12:46:44 raspberry-pi-4 kernel: hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
nov 22 12:46:44 raspberry-pi-4 kernel: hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
nov 22 12:46:44 raspberry-pi-4 pulseaudio[8201]: Failed to find a working profile.
nov 22 12:46:44 raspberry-pi-4 pulseaudio[8201]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="platform-fef00700.hdmi" card_name="alsa_card.platform-fef00700.hdmi" namereg_fail=false tsched=no fixed_latency_ra>
nov 22 12:46:44 raspberry-pi-4 kernel: hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
nov 22 12:46:44 raspberry-pi-4 kernel: hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
nov 22 12:46:44 raspberry-pi-4 kernel: hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
nov 22 12:46:44 raspberry-pi-4 kernel: hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
nov 22 12:46:44 raspberry-pi-4 kernel: hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
nov 22 12:46:44 raspberry-pi-4 kernel: hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
nov 22 12:46:44 raspberry-pi-4 pulseaudio[8201]: Failed to find a working profile.
nov 22 12:46:44 raspberry-pi-4 pulseaudio[8201]: Failed to load module "module-alsa-card" (argument: "device_id="2" name="platform-fef05700.hdmi" card_name="alsa_card.platform-fef05700.hdmi" namereg_fail=false tsched=no fixed_latency_ra>
nov 22 12:46:44 raspberry-pi-4 systemd[8174]: Started Sound Service.
nov 22 12:46:44 raspberry-pi-4 systemd[8174]: Reached target Main User Target.
nov 22 12:46:44 raspberry-pi-4 systemd[8174]: Startup finished in 2.029s.
nov 22 12:46:44 raspberry-pi-4 bluetoothd[833]: Endpoint registered: sender=:1.100 path=/MediaEndpoint/A2DPSink/sbc
nov 22 12:46:44 raspberry-pi-4 bluetoothd[833]: Endpoint registered: sender=:1.100 path=/MediaEndpoint/A2DPSource/sbc
nov 22 12:46:44 raspberry-pi-4 kernel: Bluetooth: RFCOMM TTY layer initialized
nov 22 12:46:44 raspberry-pi-4 kernel: Bluetooth: RFCOMM socket layer initialized
nov 22 12:46:44 raspberry-pi-4 kernel: Bluetooth: RFCOMM ver 1.11

It’s a NAS solution, what do you need PulseAudio for anyway?
Why not remove anything to do with making the server produce audio except dependencies? Remove those after the fact with apt.

This is the default OS installation, and I understand your standpoint.
I think defaultly, there shouldn’t be any issue with the CPU fan and pulseaudio.
But yes, this could be a solution, if you remove pulseaudio and also pipewire.

Any suggestion which not affect the default packages?

Not until I get better at Linux I’m afraid no.