Hm. It’s probably a whole new driver, so the mesa packages need to be adopted for it.
Let me see if I can build a package with it.
2 Likes
Thank you, I was already going to build it myself and I saw your changes haha
I figured it was specific to them
As reported by few people since previous upgrade, I’m noticing random freezes requiring a hard poweroff to recover. It also happens 100% of the time (well, 3 times out of 3) when sending the pbp to sleep, and waking it up.
Looking at kernel logs, what I see in common is first panfrost gpu errors, and then a weird zmem going to zero message:
Jul 26 06:30:35.456200 ciel kernel: panfrost ff9a0000.gpu: gpu sched timeout, js=1, config=0x3300, status=0x0, head=0x6d6d000, tail=0x6d6d000, sched_job=0000000022238a63
Jul 26 06:31:05.886187 ciel kernel: zram0: detected capacity change from 11865120 to 0
Jul 26 06:31:05.923382 ciel kernel: zram: Removed device: zram0
Jul 26 06:31:11.106292 ciel kernel: watchdog: watchdog0: watchdog did not stop!
Jul 26 06:31:11.146232 ciel systemd-shutdown[1]: Syncing filesystems and block devices.
Jul 26 06:31:11.193408 ciel systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Not sure if that’s enough information, but can propably give more if instructed! Never got such behaviour in the past either.
Raspberry Pi 4 updated but failed to start gui. Only flashing cursor.
Xorg server log complained of missing fbdev
Resolved by installing xf86-video-fbdev and xf86-video-fbturbo-git
Now xscreensaver glslideshow gives corrupted images as I have seen before with arch on a pi3+ that was resolved with a kernel update.
I’m currently using a Raspberry Pi 400 and running Manjaro-ARM KDE Plasma and the GUI works just fine. Also have MAjaro-ARM XFCE and it’s GUI works just fine. I have them both on SanDisk Extreme 64GB V30 XC1 U1 A2 cards (1 for each desktop)
KDE Plasma works fine on a Raspberry Pi 400.
About Kodi, I installed it using the Add/Remove Software way (official repositories), and it’s version 19.1.5. Do I need to re-install using the command below, is this a newer/optimized version?
sudo pacman -S kodi-rpi kodi-rpi-dev kodi-rpi-eventclients kodi-rpi-tools-texturepacker linux-rpi4 xf86-video-fbturbo-git
Also about booting straight in to Kodi, do I have to run the commands below every time I run Kodi or just once:
sudo systemctl disable lightdm.service
sudo systemctl enable kodi.service
And lastly, the last part of my config.txt looks like this:
#enable vc4
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
disable_splash=1
Should I change it like the one showed by @Strit? Or do I have to change stuff first to get this result:
#enable vc4
dtoverlay=vc4-kms-v3d,cma-512
#max_framebuffers=2 #disable cause kodi uses more
dtoverlay=rpivid-v4l2
disable_fw_kms_setup=1
Thanks.
Just had an issue come up with this recent update (Phosh Pinephone):
Connecting Bluetooth to my car stereo (Pioneer FH-X755BT Manuals | ManualsLib), the sound will stream for a variable amount of time, before a large amount of noies is emitted for a second and the playback stops. This is experienced using the Lollypop (1.4.22) app. I see some errors, executing journalctl -f:
Aug 09 19:02:59 manjaro-arm kernel: Bluetooth: hci0: Too short H5 packet
Aug 09 19:02:59 manjaro-arm kernel: Bluetooth: hci0: Out-of-order packet arrived (1 != 0)
Aug 09 19:02:59 manjaro-arm kernel: Bluetooth: hci0: Out-of-order packet arrived (2 != 0)
Aug 09 19:03:01 manjaro-arm kernel: Bluetooth: hci0: Invalid header checksum
Aug 09 19:03:01 manjaro-arm kernel: Bluetooth: hci0: Out-of-order packet arrived (6 != 5)
Aug 09 19:03:01 manjaro-arm kernel: Bluetooth: hci0: Out-of-order packet arrived (7 != 5)
Aug 09 19:03:01 manjaro-arm kernel: Bluetooth: hci0: Out-of-order packet arrived (0 != 5)
Aug 09 19:03:01 manjaro-arm kernel: Bluetooth: hci0: Invalid header checksum
Aug 09 19:03:01 manjaro-arm kernel: Bluetooth: hci0: Out-of-order packet arrived (7 != 5)
Aug 09 19:03:01 manjaro-arm kernel: Bluetooth: hci0: Out-of-order packet arrived (0 != 5)
Aug 09 19:03:01 manjaro-arm kernel: Bluetooth: hci0: Too short H5 packet
Aug 09 19:03:01 manjaro-arm kernel: Bluetooth: hci0: Too short H5 packet
Aug 09 19:03:01 manjaro-arm kernel: Bluetooth: hci0: Out-of-order packet arrived (7 != 5)
Aug 09 19:03:01 manjaro-arm kernel: Bluetooth: hci0: Out-of-order packet arrived (0 != 5)
Aug 09 19:03:02 manjaro-arm kernel: Bluetooth: hci0: Invalid header checksum
Aug 09 19:03:02 manjaro-arm kernel: Bluetooth: hci0: Out-of-order packet arrived (6 != 5)
Aug 09 19:03:02 manjaro-arm kernel: Bluetooth: hci0: Out-of-order packet arrived (7 != 5)
Aug 09 19:03:02 manjaro-arm kernel: Bluetooth: hci0: Out-of-order packet arrived (0 != 5)
Aug 09 19:04:00 manjaro-arm sm.puri.Phosh.desktop[4807]: [INFO] 2021-08-09 19:04:00 Player::_on_bus_error(): ../gst-plugins-good/ext/pulse/pulsesink.c(1750): gst_pulseringbuffer_commit (): /GstPlayBin:player/GstPlaySink:playsink/GstBin:abin/GstBin:bin0/GstAutoAudioSink:autoaudiosink0/GstPulseSink:autoaudiosink0-actual-sink-pulse
The error seems to be occuring quickly for songs with less frequent or quieter sound, but then it also depends on the time of day, so I’m not sure as to the cause. Also, just tested on other bluetooth devices and I see the same error.
Thank you, that solved my problem.
All packages should upgrade on their own to kodi-rpi-19.1-10 when all other packages upgrade.
A little bit of both. OpenELEC is constantly changing things for the pi’s.
Just once. This changes the environment for kodi to boot into so you can have HW h264 / h265 decoding. This is what the kodi-rpi packages are designed for; a stand along media server.
If you also want to boot back into Plasma then you will have to reverse the steps and disable fbturbo so you will have V3D rendering:
sudo mv /etc/X11/xorg.conf.d/99-fbturbo.conf /etc/X11/xorg.conf.d/99-fbturbo~
Be sure to reverse this again when switching back to kodi. The best thing to do is have separate installs though so you can have a media server and DE setups already configured.
Yes this has to be changed to set up the right environment. This is the reason this guide is posted on every branch update.
1 Like
My initial report of a keyring problem happened while upgrading an XFCE install. The problem has also happened while I was upgrading a plain-vanilla gnome install that was created with Manjaro ARM flasher. This error is logged twice while upgrading Manjaro-keyring 20210731-1 → 20210807-1:
pgp: Error reading key: No public key
Follow-on error messages seem to be based on those two log entries.
I’m also experiencing random freezes on PineBook Pro ARM64 and seeing similar panfrost messages. E.g.:
panfrost ff9a0000.gpu: gpu sched timeout, js=1, config=0x3300, status=0x0, head=0x71c3000, tail=0x71c3000, sched_job=000000005a2f1084
That seems to relate to the key that gets revoked by the package. The key most have been removed from the keyservers all together.
Update reports at boot that cma_alloc : cma allocation failed.
White screen appears.
Rolling back to kernel 5.10.50-2 fixes the issue.
Any pointers?
TIA
I did the downgrade Vivaldi to version 4.0.2312.41 as per
I had to use the manual downgrade as discribed in the Mahjaro Wiki
I have been talking with someone on the Vivaldi Forum in the post I entered there.
That person is on the Manjaro-ARM testing branch and says that version 4.1.2369.16 is available there. I’m now wondering when that version of Vivaldi will be available in the stable branch.
With the next stable update. 
Ok, sounds like it will be a while before that update is ready.
You could move to testing , install vivaldi,then move back to stable.
Hi, getting no eyes with the new xeyes in this update. Testing with plasma on X11 on an RPI4. Any clue?