Open devrosx opened 7 months ago
My RG353VS has the same issue described above. I installed the stable release from the Batocera.org download page instead of the BETA release, as used above. It seems with the BETA version, Windows read the boot partition of the micro sd card, and I could access the file system to rename the DTB file to use the V2 screen driver (in my case the V2 driver had no sound but the screen displayed fine. Not garbled like in the first post). With the stable release I used, I cannot access the Boot partition of the sd card with Windows anymore. I guess I'll have to wait until this issue is addressed before I can use Batocera. Sadly.
So there are two version of the RG353VS
is this what you're saying?
Therefore it requires a different dtb?
yes looks like its same or similar problem
but with arkos my rg353vs works without problem
I have the same issue
I have the RG 353V, and it doesn't look much different for me.
Theres a few dtb files including a v2 dtb file for the 353v...you have to rename the right dtb file
I had to mount the SD card on a Linux pc delete the 353v dtb file under /boot and rename the one that has "v2" in it to match the old 353v non v2 file name.
Just checking here, but this issue has been acknowledged and is being worked on?
We don't have the device to confirm a fix. Until that happens it will be guess work.
I have a 353vs I can donate. Contact me on discord and we can make shipping arrangements.
same issue with 353v seem like dtb
For the 353v (non vs version) in the boot directory there are several prestaged dtb files... Rename the 353v2 file to rk3566-rg353v-linux.dtb and the device will boot properly.
@paronowitz yea did that. most things works so far. Shutdown is broken at the moment
Yes I have the same problem with shutdown/reboot as well as the wifi doesnt always start... understanding this is early release and issues to be expected
I tried to re name the dtb file in the boot folder to v2 the screen image was fixed but the sound was not working in v1 the sound is working but the screen is not
I did not have that issue at all, however there were some similar issues with arkos/jelos. 1st go into the system settings and make sure you dont have hdmi selected under the auto device... 2nd plug in wired headset and unplug it (thats what solved my issue when i was using arkos)
Just checking back to see how progress is going. Still have a unit to donate if needed.
i have a 353VS and, having just discovered batocera, was googling whether it could be used on the handheld. But alas found this thread. Hoping it might come to fruition!
Any updates about this issue? Even with replacing the files in the boot folder don't work.
Can confirm the graphics driver work after replacing the dtb, but no sound. Using an RG353VS
Can confirm the graphics driver work after replacing the dtb, but no sound. Using an RG353VS
Try a few things
1)Make sure the correct audio out is selected in system settings 2)Plug in headphones then unplug them
Is the shutdown an issue across all RGXX3 devices? I burnt the RGXX3 image last night - works on my RG503 but shutdown doesn't work. I tried the RG353M but just get a blank screen.
Batocera build version
39-20240229
Your architecture
rg353vs
Your Graphic Processor Unit(s) (GPU)
-
Issue description
Hello looks like GPU driver is broken on rg353vs, broken image after boot, sound is working, and buttons works too.. (maybe it use driver rg353v which is probably different and has touch support)
thanks
Detailed reproduction steps
flashed this beta version https://mirrors.o2switch.fr/batocera/anbernic-rgxx3/butterfly/last/
Details of any attempts to fix this yourself
No response
Details of any modifications you have made to Batocera.
no just flash and boot
Logs and data
No response