Hello, I just installed EndeavourOS on a Raspberry Pi500… using a 256GB Samsung Pro Plus A2 class SD card. I’m getting a dmesg log full of “mmc0: running CQE recovery” messages.
I found a note on Jeff Gerling’s site to add a dtparam=sd_cqe parameter to the /boot/config.txt file, since my A2 class SD card should support it. On boot I see the dmesg saying Command Queue Engine enabled, 31 tags.
However, I continue to get a log full of the CQE recovery messages, which I believe is really slowing done my machine.
I have succesfully installed EnOS on RPi 5 with a Samsung Pro Plus 128 GB uSD, a Samsung T7 500 GB USB SSD, and a Sans Disk 500 GB NVME.
I also have a couple Samsung Pro Plus 256 GB uSDs. It has been my experience with 256 GB uSD is very sketchy. Not as stable as 128 GB.
I would suggest using a Samsung Pro Plus 128 GB uSD if available. That was been rock solid for me.
HTH
Let us know how things turn out.
Pudge
EDIT:
I support 6 different images that I refresh every 1 to 2 weeks. Every time I do a test install of every image before Release on github. Here is a pic of my work bench with the uSDs I use for testing.
i check my note… note is old , i do write down where thread was.
it last post on page 5
Re: Testing class A2 SD cards with Command Queueing on Pi 5
Quote
Mon Nov 25, 2024 6:46 pm
To date there have been no Samsung A2 cards that work with CQ mode - typically because they break when a filesystem cache flush occurs. Therefore they're masked out by that quirk flag (bit 15).
Also flash capacities in datasheets are usually minima - there's a certain number of bad blocks that the manufacturer is willing to tolerate which will vary between each card.
Thanks for the feed back. I have not obtained a RPi 500 yet, next month maybe.
Glad to hear the RPi 5 image works without intervention.
If you have the time, inclination, and spare uSD card, here is the procedure for creating an RPi 5 image with btrfs. It will be a few weeks before I can actually test this on a RPi 500.