in my case, read slower is like freeze but not dead.
maybe should build a f2fs img?
I would defiantly use a usb 3.0 stick plugged into the piās usb 3.0 port.
my usb stick is 3.2 printed in box.
so, maybe is Piās firmware issue?
should bought large sdcard not usb-stick 
edit,
ok, set quirks parameter to cmdline, no luck.
ADDED 01-04-2024:
These latest updated kernel packages has been pushed to the unstable branch when the mirrors sync.
@tartanpion 6by9 thinks he has ERROR Failed to allocate DLIST entry fixed here. Could you test and report your findings back to him?
https://github.com/raspberrypi/linux/issues/5674
linux-rpi4 6.1.70-2
linux-rpi4-headers 6.1.70-2
linux-rpi4-mainline 6.6.9-2
linux-rpi4-mainline-headers 6.6.9-2
linux-rpi5 6.1.70-2
linux-rpi5-headers 6.1.70-2
linux-rpi5-mainline 6.6.9-2
linux-rpi5-mainline-headers 6.6.9-2
Because of this bug, I went ahead and purchased a Pi 5. I felt a bit lonely dealing with this critical bug. Suddenly, many others started reporting the same issue, and 24 hours later, thereās a patch. The Pi 4 is now waiting on the shelf to be sold or repurposed as a pi-hole.
I have a new bug with the Pi 5: despite having the same hardware, my screen goes into sleep mode properly, but I canāt turn it back on using the mouse or keyboard. Iām forced to use the physical button on the screen, turning it off and on again manually. I have the same issue under PiOS.
Well it looks like it did not fix it. So back to the waiting game again.
where can check ādrm/v3d: CPU jobsā merge 6.8-drm-next or not?
in mesa side its already done.
Looks like it is there. The drivers/gpu/drm/v3d/Makefile Patch:
diff --git a/drivers/gpu/drm/v3d/Makefile b/drivers/gpu/drm/v3d/Makefile
index 4b21b20e4998..b7d673f1153b 100644
--- a/drivers/gpu/drm/v3d/Makefile
+++ b/drivers/gpu/drm/v3d/Makefile
@@ -12,7 +12,8 @@ v3d-y := \
v3d_perfmon.o \
v3d_trace_points.o \
v3d_sched.o \
- v3d_sysfs.o
+ v3d_sysfs.o \
+ v3d_submit.o
ok, wait 6.8-rc1 
Would this run Manjaro?
inxi -FazyG
System:
Kernel: 6.1.21+ armv6l bits: 32 compiler: gcc v: 10.2.1
parameters: coherent_pool=1M snd_bcm2835.enable_headphones=0
snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1
bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1
vc_mem.mem_base=0xec00000 vc_mem.mem_size=0x10000000 console=ttyAMA0,115200
console=tty1 root=PARTUUID=a1ddfa5e-02 rootfstype=ext4 fsck.repair=yes
rootwait quiet splash plymouth.ignore-serial-consoles
cfg80211.ieee80211_regdom=AU
Console: tty 0 DM: LightDM 1.26.0 Distro: Raspbian GNU/Linux 11 (bullseye)
Machine:
Type: ARM Device System: Raspberry Pi Model B Rev 1 details: BCM2835
rev: 0003 serial: <filter>
CPU:
Info: Single Core model: ARMv6-compatible v6l variant: arm1176jzf-s bits: 32
type: UP arch: v6l family: 7 model-id: N/A stepping: 7
features: Use -f option to see features bogomips: 697
Speed: 700 MHz max: 700 MHz Core speed (MHz): 1: 700
Vulnerabilities: No CPU vulnerability/bugs data available.
Graphics:
Device-1: bcm2708-fb driver: bcm2708_fb v: kernel bus ID: N/A
chip ID: brcm:soc class ID: fb
Device-2: bcm2835-hdmi driver: N/A bus ID: N/A chip ID: brcm:soc
class ID: hdmi
Display: server: X.org 1.20.11 driver: loaded: fbturbo tty: 102x51
Message: Advanced graphics data unavailable in console. Try -G --display
Audio:
Device-1: bcm2835-hdmi driver: N/A bus ID: N/A chip ID: brcm:soc
class ID: hdmi
Sound Server: ALSA v: k6.1.21+
Network:
Device-1: Microchip (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter
type: USB driver: smsc95xx bus ID: 1-1.1:3 chip ID: 0424:ec00 class ID: ff00
IF: eth0 state: down mac: <filter>
Device-2: Ralink RT5370 Wireless Adapter type: USB driver: rt2800usb
bus ID: 1-1.3:4 chip ID: 148f:5370 class ID: 0000 serial: <filter>
IF: wlan0 state: up mac: <filter>
Drives:
Local Storage: total: 28.97 GiB used: 3.35 GiB (11.6%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/mmcblk0 maj-min: 179:0 model: SD32G size: 28.97 GiB block size:
physical: 512 B logical: 512 B rotation: SSD serial: <filter> scheme: MBR
Partition:
ID-1: / raw size: 28.71 GiB size: 28.19 GiB (98.18%) used: 3.3 GiB (11.7%)
fs: ext4 dev: /dev/mmcblk0p2 maj-min: 179:2
ID-2: /boot raw size: 256 MiB size: 255 MiB (99.60%) used: 50.4 MiB (19.8%)
fs: vfat dev: /dev/mmcblk0p1 maj-min: 179:1
Swap:
Kernel: swappiness: 60 (default) cache pressure: 100 (default)
ID-1: swap-1 type: file size: 100 MiB used: 83.5 MiB (83.5%) priority: -2
file: /var/swap
Sensors:
System Temperatures: cpu: 44.9 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 118 Uptime: 3m Memory: 240.1 MiB used: 160.1 MiB (66.7%)
gpu: 64 MiB Init: systemd v: 247 runlevel: 5 target: graphical.target
Compilers: gcc: 10.2.1 alt: 10 Packages: apt: 1427 lib: 753 Shell: Bash
v: 5.1.4 running in: tty 0 (SSH) inxi: 3.3.01
Nope and neither will arch-arm. arch-arm supports armv7 and above. We only do armv8 64bit
The latest linux-rpi4/5 and rpi5-eeprom packages has been pushed to the unstable branch when the mirrors sync.
I have gone ahead and upgraded linux-rpi4/5 kernels from the rpi-6.1.y tree to the rpi-6.6.y LTS tree to make room for the 6.7 kernels in the linux-rpi4-mainline / linux-rpi5-mainline and the new 6.8-rc kernels when RPi updates their trees.
A couple of fixups for the pi5 with the rpi-eeprom package. See under 2024-01-05: Fix handling of FAT files without LFNs. here:
https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware-2712/release-notes.md
linux-rpi4 6.6.10-1
linux-rpi4-headers 6.6.10-1
linux-rpi5 6.6.10-1
linux-rpi5-headers 6.6.10-1
rpi5-eeprom 20240108-1
remove [kms] hook, warning is gone.
When you order Pi5 did you also have your DHL parcel on hold by DHL?
Not on hold per say but held up several days by Germany customs due to large volumes they told me when I called the pi people.
DHL was a total nightmare for me. My pi5 spent several days everytime it reached different places.
The latest linux-rpi4/5 kernel packages has been pushed to the unstable branch when the mirrors sync. I am patiently waiting for them to upgrade their 6.7.y tree. There has been no updated since -rc6.
linux-rpi4 6.6.11-1
linux-rpi4-headers 6.6.11-1
linux-rpi5 6.6.11-1
linux-rpi5-headers 6.6.11-1
1 Like
I see an error from the initramfs8 build when upgrading linux-rpi4-mainline, seems able to boot alright though
==> Using configuration file: '/etc/mkinitcpio.conf'
-> -k 6.6.8-1-MANJARO-RPI4 -c /etc/mkinitcpio.conf -g /boot/initramfs8
==> Starting build: '6.6.8-1-MANJARO-RPI4'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [kms]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs8'
==> WARNING: errors were encountered during the build. The image may not be complete.
error: command failed to execute correctly
It has been that way for a couple of months. Maybe they will fix it some day.
Or try this: