Are you on the DevTerm or uConsole? How’d you flash the image? Did you make any big changes or weird installs? Hardware add-ons?
My daughter has been playing Mine Craft, SNES, and Cave Story on mine DevTerm this weekend. While she said Mine Craft was unpleasant to play because of the screen size she said she hasn’t had any problems. I’ve tested and ran a few benchmarks without problems.
How’s the image working out for everyone who’s running it?
btw did quick test of VCMI, and got sound freezes, comparing to stock raspberry… for some reason. and retropie and retroarch does not work((( 1st one does not support wayland, 2nd… just does not start(installed from flatpak)
retropie works on wayland (i’m using sway), but you need to change the config.txt and change “#dtoverlay=vc4-kms-v3d-pi4,cma-384” to “dtoverlay=vc4-kms-v3d” for a lot of 3D software to work flawless and maybe install xwayland.
@Rex i’m on uconsole, yes. benchmarks work without problem and playing something is not a problem. the problem is when you have a long system up time with many IO operations. I can force a crash when i simply unzip a large amount of data (>10GB) on an usb drive. the errors i get are always errors which are normally associated with hardware defects, like “tag#0 access beyond end of device” on write on the attached memory or unable to release the v3d engine. Obviously on dmesg.
I can workaround the first error by simply reducing the transfer speed on the device and slowing everything down a lot. At the moment i reduced the performance to a maximum of 40mbit/s on file transfers and its working for a few hours nonstop (so far).
I was also able to identify some problems with the keyboard, when the USB bus is under heavy use - it starts stuttering and gets unusable. So maybe something wrong with the USB governor?
For the V3D i only have one solution so far: rebooting. I dont have a easy way to replicate this issue, seems a little bit random for me.
lol, now i dont have sound)
I know what you’re talking about with the IO, the same thing has been happening since kernel 6.1 with my cm4 i have in a IO board and a regular raspberry pi 4. do you have another pi to test on to verify?
I’m just on vanilla pi image on the 2.
yes, i have two other rpis, they are stable, but they are on 6.6. It’s possible it got fixed in a newer kernel or it is only with the CM4
Yes! It work better ^^, thanks. I test it, now.
I finally got a chance to try that image on a DevTerm with a CM3 module. The proper display in config.txt was already set, but that didn’t boot. I connected an external HDMI monitor and at boot, you get the color square, but that vanishes in a second or so and no text appears on either display.
I also noticed that even holding the power button down so it shuts down, the 5V system is still powered.
When I put the original SD card in with the 32 bit and booted that, then shut down, the 5V system turns off as expected.
the kernel is the same 64bit that the cm3 uses. I wonder if there’s something else for the cm3. I’ll download one of the cm3 images and check it out.
Can you put this as your config.txt in /boot and tell me if that works.
ignore_lcd=1
dtparam=audio=on
dtoverlay=vc4-kms-v3d,cma-384
dtoverlay=devterm-pmu
dtoverlay=devterm-panel
dtoverlay=devterm-wifi
dtoverlay=devterm-bt
dtoverlay=devterm-misc
gpio=5=op,dh
gpio=9=op,dh
gpio=10=ip,np
gpio=11=op,dh
enable_uart=1
dtparam=spi=on
dtoverlay=spi-gpio35-39
kernel=kernel8.img
Ok, downloaded your image from before. Used the Pi imager to write it to the system. Told it not to customize things. 32G SD card. Renamed the config.txt as configOld.txt and installed the new text as you provided.
It is really close, I did see the display come to life several times with the pi boot stuff and even the image. I expected slower boot as it resized things. I must have flashed something on the display 4 or 5 times at various points. After about 5 or 6 minutes, there is a blinking cursor in the upper left corner of the display but it looks like it is in text mode. The blink is a rather odd pattern that repeats.
After about 10 minutes, I decided that it wasn’t getting any further. A short press on the power button doesn’t do anything, so the system isn’t up. I can tell the 5V sub system is powered as the USB ports have their 5V.
Holding the power button for 30 seconds or so, the power light does go out. The charge LED was still lit as I was plugged in. Unplugging that, the 5V system is still powered up with all other indications that it is off. We had this problem long ago.
Power up again… About 45 seconds into the boot, I get the “Welcome to Raspberry Pi” display again looking good as it lists modules being loaded, but it blanks after just a couple seconds and the cursor just blinking oddly in the upper left is like it was before.
Connecting an external monitor to it and rebooting a few more times. I did get a message on both displays about not being able to enumerate a USB device, but that only happened once.
So far all attempts end with the blinking cursor in the upper left.
I yanked the sd card out while it was with the blinking cursor. Interesting that I am getting the continuous error messages from not being able to read the SD card. So the display is up and running, but in text mode.
I can do the Alt F1 → Alt F9 to see different screens, but none of them are the graphics. Error messages eventually show up in all of them (SD card still out).
What else would you like me to try?
Let me look into a few things a little later when i get a chance.
Sticking back in my old SD card with the 32 bit OS, the USB power system does shut down as expected.
Thanks a bunch. I just haven’t had time to get into it very far. It is near the end of the semester and I teach.
I also noticed that when I download the 32 bit image and run that, the USB power subsystem doesn’t shut down properly.
Might have to see if I can find a cm3 for cheapish to get to test.
fyi: short press on the power button never does anything unless you configure it
the system should show an onboarding process from raspberry pi os on first boot. what you are describing does look a lot like a kernel problem - or hardware. can you boot with the official 64bit image and get a screen output on hdmi?
Been running the 32 bit OS for years without any major modifications. With that, the power button short press would cause a safe shutdown in just 1 or 2 seconds. That still works when I put that SD card back in. I am downloading the 64 bit OS for the Pi Zero 2W as that has the same processor as the CM3. Booted as expected on the HDMI, there was an error message about not being able to enumerate USB. Keyboard and trackball on the DevTerm don’t work, but the 5V subsystem power is there and an external mouse/keyboard are fine. After the reboot, the Devterm Keyboard and trackball work just fine. The name -a command shows I am running in 64 bit mode.
The config.txt file looks like:
ignore_lcd=1
dtparam=audio=on
dtoverlay=vc4-kms-v3d,cma-384
dtoverlay=devterm-pmu
dtoverlay=devterm-panel
dtoverlay=devterm-wifi
dtoverlay=devterm-bt
dtoverlay=devterm-misc
gpio=5=op,dh
gpio=9=op,dh
gpio=10=ip,np
gpio=11=op,dh
enable_uart=1
dtparam=spi=on
dtoverlay=spi-gpio35-39
kernel=kernel8.img
Shutdown as expected doesn’t work well.
yea, if the OS is configured to power down when pressing the button, it works. this is not a hardware thing, but pure software.
ok if the general 64bit kernel works, then you can be sure it has something to do with the kernel. You would’ve need to recompile it yourself.
Does anyone know if this kernel is compiled with CONFIG_PSI enabled? ive been trying to get Waydroid working and its hanging on the binder manager which apparently needs that option enabled in the kernel. the posts im looking at are a little older but a few people mentioned they had ro recompile their kernel on raspberry pi in order to have that feature enabled, but I’m hoping it may have been enabled in this one.
The only additions to this kernel over the stock raspberry pi one is the stuff for the devices. You’d have to recompile the kernel with that enabled if the raspberry pi kernel doesn’t include it.
i had to add input_libretro_device_p1 = “1” to retroarch config to get buttons working.