Some kernel package fixups since yesterday’s releases.
dts: bcm2712: Use the new model name
drivers: media: rp1_cfe: Fix link validate test for pixel format
linux-rpi4 6.1.58-2
linux-rpi4-headers 6.1.58-2
linux-rpi5 6.1.58-2
linux-rpi5-headers 6.1.58-2
rpi-overlays 6.1.58-2
what is rpi-overlays package for?
Installs the overlays used by all RPi kernels. They were in the kernel packages but had to remove it due to 2 different kernels now living in one image at the same time. ( pi3-4/pi5) So you won’t get files exist in the file system errors.
They are in the rpi firmware repo and Ideally they could be bundled in the raspberrypi-bootloader PKGBUILD but sometimes it may be days for them to update the git so for now I am building the overlays manually and packaging them.
Hi Darksky, if I am using the 6.6 rc kernels can the overlay version rpi-overlays-6.1.58-2 coexist?
Yes. The same overlays are used with all their kernels. They are provided in RPi’s firmware git which is based on what they consider their current stable branch which is right now the 6.1.y branch until they move to the next LTS kernel.
All of the RPi kernels I provide has the rpi-overlay package as a depend.
https://github.com/raspberrypi/firmware/tree/master/boot/overlays
This time i have the log
Aucun espace disponible sur le périphérique means No space available on the device
journalctl
oct. 19 23:45:42 bloodmoon-pc firefox.desktop[10472]: Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Couldn't sanitize RENDER
ER device: V3D 4.2 (t=4116.47) |[C1][GFX1-]: Couldn't sanitize RENDERER device: V3D 4.2 (t=4122.82) |[C2][GFX1-]: Couldn't sanitize
RENDERER device: V3D 4.2 (t=4129.93) |[C3][GFX1-]: Couldn't sanitize RENDERER device: V3D 4.2 (t=4197.65) |[C4][GFX1-]: Couldn't sanitize RENDERER device: V3D 4.2 (t=5059.46) [GFX1-]: Couldn't sanitize RENDERER device: V3D 4.2
oct. 19 23:46:10 bloodmoon-pc firefox.desktop[10472]: Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Couldn't sanitize RENDERER device: V3D 4.2 (t=4116.47) |[C1][GFX1-]: Couldn't sanitize RENDERER device: V3D 4.2 (t=4122.82) |[C2][GFX1-]: Couldn't sanitize RENDERER device: V3D 4.2 (t=4129.93) |[C3][GFX1-]: Couldn't sanitize RENDERER device: V3D 4.2 (t=4197.65) |[C4][GFX1-]: Couldn't sanitize RENDERER device: V3D 4.2 (t=5059.46) |[C5][GFX1-]: Couldn't sanitize RENDERER device: V3D 4.2 (t=5088.18) [GFX1-]: Couldn't sanitize RENDERER device: V3D 4.2
oct. 19 23:46:31 bloodmoon-pc caffeine.desktop[14965]: Aucune propriété spécifiée.
oct. 19 23:48:55 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:48:55 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:48:55 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
....
oct. 19 23:48:57 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:48:57 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:48:58 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:48:58 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:48:58 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:48:58 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:48:58 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:02 bloodmoon-pc gnome-shell[9549]: Cursor update failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:02 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:02 bloodmoon-pc gnome-shell[9549]: Cursor update failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:02 bloodmoon-pc gnome-shell[9549]: Cursor update failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:02 bloodmoon-pc gnome-shell[9549]: Cursor update failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:02 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:02 bloodmoon-pc gnome-shell[9549]: Cursor update failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:02 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:02 bloodmoon-pc gnome-shell[9549]: Cursor update failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:02 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:02 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:02 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:02 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Cursor update failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Cursor update failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Cursor update failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Cursor update failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Cursor update failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Cursor update failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
oct. 19 23:49:03 bloodmoon-pc gnome-shell[9549]: Page flip failed: drmModeAtomicCommit: Aucun espace disponible sur le périphérique
:
.....
How much onboard ram does your pi4 have.
8gb. I removed all the shell extensions. I monitor htop. Under gnome x11 i don’t see
vc4-drm gpu: swiotlb buffer is full (sz: 524288 bytes), total 32768 (slots), used 2595 (slots)
What I do not understand is I can not seem to find anyone else getting the error here or the other forums I frequent. I have seen some with the error but that is 3 years ago.
I have no more the time to investigate but it’s perhaps not related to the kernel. Something eats the memory.
One thing I ran across is this but have no idea why tthis guy had to increase when no one else has to.
https://forums.raspberrypi.com/viewtopic.php?t=131079
Which leads to this:
https://unix.stackexchange.com/questions/13751/kernel-inotify-watch-limit-reached
I have held off for a couple of days updating things as Rpi just kept on with commits fixing/changing things for the pi5 in their various repo’s. I have not seen any activity today so I rebuilt several packages with the latest updates and pushed them to the unstable branch when the mirrors sync.
For the pi5 especially these packages will depend on each other to be installed to take advantage of the latest commits. I still have no clue yet how the rpi5-eeprom package will work as I do not have a pi5 yet.
firmware-raspberrypi 20231021-1
linux-rpi4 6.1.58-3
linux-rpi4-headers 6.1.58-3
linux-rpi5 6.1.58-3
linux-rpi5-headers 6.1.58-3
raspberrypi-bootloader 20231019-1
raspberrypi-bootloader-x 20231019-1
rpi-overlays 6.1.58-3
Added 10-23-2023:
RPi has depreciated their userland git as they have moved on to standard linux API’s: V4L2, DRM/KMS APIs. They have migrated what is left in the reo that is useful to a new repo raspberrypi/utils.
So I have removed the raspberrypi-userland-git package and replaced it with the raspberrypi-utils package and had to rebuild these packages and pushed all new packages to the unstable branch when the mirrors sync.
I tried to rebuild the libec-rpi-fkms package but it will not compile spitting out an error involving it’s code. I do not know if anyone uses fkms anymore as RPi considers it to be depreciated and it sometimes works along the way but keeps breaking and it is not a priority for them to fix it.
libcec-rpi 6.0.2-6
raspberrypi-utils 20231022-1
rpi4-eeprom 20231022-1
rpi5-eeprom 20231022-1
https://github.com/raspberrypi/userland/blob/master/README.md
rpi4-eeprom how to update?
You can not until you install the packages I just pushed to the unstable branch. Looks like they changed the name of a file in /etc/default. I was going to go through the steps for you here and found the issue. I had used ARCH-ARM’s PKGBUILD today to save me some time. So thanks for helping me see there was an issue.
New packages when the mirrors sync:
rpi4-eeprom 20231022-2
rpi5-eeprom 20231022-2
The process is the same as you always have on the pi4. I know nothing about the pi5; mine has not come yet.
Set your desired FIRMWARE_RELEASE_STATUS in /etc/default/rpi-eeprom-update. Either default or latest.
After install it will be set to default:
[ray@jellyfin ~]$ sudo rpi-eeprom-update
BOOTLOADER: up to date
CURRENT: Thu May 11 06:26:03 AM UTC 2023 (1683786363)
LATEST: Wed Jan 11 05:40:52 PM UTC 2023 (1673458852)
RELEASE: default (/lib/firmware/raspberrypi/bootloader/default)
VL805_FW: Using bootloader EEPROM
VL805: up to date
CURRENT: 000138c0
LATEST: 000138c0
[ray@jellyfin ~]$
Since I set mine to latest I edited this line in /etc/default/rpi-eeprom-update
FIRMWARE_RELEASE_STATUS="latest"
Now it shows I am using latest:
[ray@jellyfin ~]$ sudo rpi-eeprom-update
BOOTLOADER: up to date
CURRENT: Thu May 11 06:26:03 AM UTC 2023 (1683786363)
LATEST: Thu May 11 06:26:03 AM UTC 2023 (1683786363)
RELEASE: latest (/lib/firmware/raspberrypi/bootloader/latest)
VL805_FW: Using bootloader EEPROM
VL805: up to date
CURRENT: 000138c0
LATEST: 000138c0
[ray@jellyfin ~]$
If it needs updating:
sudo rpi-eeprom-update -a
sudo reboot
Then remove temp files in /boot and check if all is good:
sudo rpi-eeprom-update -r
sudo rpi-eeprom-update
but why is date tag 11/May, its Oct. now?
That is the date of the last current image release in latest. In default the current image date is last January. Has nothing to do with today’s date. default is now the old critical.
stable is where they move an image out of beta testing. beta is no longer in this package. They are supposed to start another repo for beta. After a while they eventually will move the image from stable to default.
So an image goes from beta → stable → default as bugs get worked out along the way.
RPi made some minor changes since yesterday’s package with the new raspberrypi-utils package. New package pushed to the unstable branch when the mirrors sync.
raspberrypi-utils 20231023-1
I just saw that. I was in the process of looking up your post to compare the errors. They seem to be different from what you posted but could be related.
Same error but only visible when I succeeded to open à tty