Batocera Build for the RG353V (v2 Screen) - Black Screen with rk3566-rg353v-linux-v2.dtb

Gammelstulle commented 2 months ago

Batocera build version

Newest Version 39 Build Feb 2024

Your architecture

RG353V (v2 Screen)

Your Graphic Processor Unit(s) (GPU)

RK3566 Quad-Core 64 Bit Cortex-A55 Prozessor

Issue description

Hey, somehow I not get Batocera to run on my RG 353V. I flashed the img from the website and got a white scrambled screen (A inticator that i have a v2 Screen build in) I tryed to rename the rk3566-rg353vs-linux.v2.dtb file to rk3566-rg353vs-linux.dtb and even deleted the old one, but after that my screen stays black on boot.

Detailed reproduction steps

I falshed batocera via win32DiskImgr

Details of any attempts to fix this yourself

-research -used other dtb files -Will try to use the dtb files from ArkOS (not know if this will even work in teh first place)

Details of any modifications you have made to Batocera.

no. First start.

Logs and data

i wish i can but no boot no partition build no log.

dmanlfc commented 2 months ago

Confirmed

dmanlfc commented 1 month ago

Try the image here - https://drive.google.com/drive/folders/1nDRtMMJQvETG1JMkTrDYgYvzupRsMMVQ?usp=sharing

Gammelstulle commented 1 month ago

Hi dmanifc. Thx to provide me a new build to test. Sadly /oddly it not even boot. My RG353V is directly booting in android mode if I try. (not regonize a os on the sd) I try to flash with win32diskimger and also via balenaEtcher

EDIT i will redownlaod and try a new sd card to be shure. -> No, still refuse to boot

paronowitz commented 1 month ago

Hi dmanifc. Thx to provide me a new build to test. Sadly /oddly it not even boot. My RG353V is directly booting in android mode if I try. (not regonize a os on the sd) I try to flash with win32diskimger and also via balenaEtcher

EDIT i will redownlaod and try a new sd card to be shure. -> No, still refuse to boot

You should not be using the "vs" dtb if you have a "v" model. You need to rename rk3566-rg353v-linux.v2.dtb to rk3566-rg353v-linux.dtb

Gammelstulle commented 1 month ago

Hi dmanifc. Thx to provide me a new build to test. Sadly /oddly it not even boot. My RG353V is directly booting in android mode if I try. (not regonize a os on the sd) I try to flash with win32diskimger and also via balenaEtcher EDIT i will redownlaod and try a new sd card to be shure. -> No, still refuse to boot

You should not be using the "vs" dtb if you have a "v" model. You need to rename rk3566-rg353v-linux.v2.dtb to rk3566-rg353v-linux.dtb

I mixed it up in the title, but I meant the rg353v file. (There is no file named rk3566-rg353vs-linux.v2.dtb) I even checked again if I fucked up this part on booth version but no. dmanlfc Build sadly not boot at all (directly skipt and boot to anberic android) 39 in the other hand the screen is not working. I even tryed some things ->

I used the k3566-rg353vs-linux.v2.dtb from 40 on 39, same result black screen
used the Bootfolder from 39 in 40 -> Also no boot
I use the 40 botfodler in 39 -> same results with rg353v-linux.dtb and rg353v-linux.v2.dtb.

paronowitz commented 1 month ago

Hi dmanifc. Thx to provide me a new build to test. Sadly /oddly it not even boot. My RG353V is directly booting in android mode if I try. (not regonize a os on the sd) I try to flash with win32diskimger and also via balenaEtcher EDIT i will redownlaod and try a new sd card to be shure. -> No, still refuse to boot

You should not be using the "vs" dtb if you have a "v" model. You need to rename rk3566-rg353v-linux.v2.dtb to rk3566-rg353v-linux.dtb

I mixed it up in the title, but I meant the rg353v file. (There is no file named rk3566-rg353vs-linux.v2.dtb) I even checked again if I fucked up this part on booth version but no. dmanlfc Build sadly not boot at all (directly skipt and boot to anberic android) 39 in the other hand the screen is not working. I even tryed some things ->

I used the k3566-rg353vs-linux.v2.dtb from 40 on 39, same result black screen

used the Bootfolder from 39 in 40 -> Also no boot

I use the 40 botfodler in 39 -> same results with rg353v-linux.dtb and rg353v-linux.v2.dtb.

Odd I don't experience the same issue at all. I've been using balena etcher to burn the base image and a linux host to mount the boot partition for the dtb rename.

Gammelstulle commented 1 month ago

Hi dmanifc. Thx to provide me a new build to test. Sadly /oddly it not even boot. My RG353V is directly booting in android mode if I try. (not regonize a os on the sd) I try to flash with win32diskimger and also via balenaEtcher EDIT i will redownlaod and try a new sd card to be shure. -> No, still refuse to boot

You should not be using the "vs" dtb if you have a "v" model. You need to rename rk3566-rg353v-linux.v2.dtb to rk3566-rg353v-linux.dtb

I mixed it up in the title, but I meant the rg353v file. (There is no file named rk3566-rg353vs-linux.v2.dtb) I even checked again if I fucked up this part on booth version but no. dmanlfc Build sadly not boot at all (directly skipt and boot to anberic android) 39 in the other hand the screen is not working. I even tryed some things ->

I used the k3566-rg353vs-linux.v2.dtb from 40 on 39, same result black screen

used the Bootfolder from 39 in 40 -> Also no boot

I use the 40 botfodler in 39 -> same results with rg353v-linux.dtb and rg353v-linux.v2.dtb.

Odd I don't experience the same issue at all. I've been using balena etcher to burn the base image and a linux host to mount the boot partition for the dtb rename.

Do you also have a rg353v with a v2 screen ? Maybe i have a newer revision again... But ark e.g. working fine. ._. As said if i burn the 39 the same way as 40 it boots normaly but i have the screen / blackscreen issue, 40 not boot at all ><...

paronowitz commented 4 weeks ago

Hi dmanifc. Thx to provide me a new build to test. Sadly /oddly it not even boot. My RG353V is directly booting in android mode if I try. (not regonize a os on the sd) I try to flash with win32diskimger and also via balenaEtcher EDIT i will redownlaod and try a new sd card to be shure. -> No, still refuse to boot

You should not be using the "vs" dtb if you have a "v" model. You need to rename rk3566-rg353v-linux.v2.dtb to rk3566-rg353v-linux.dtb

I mixed it up in the title, but I meant the rg353v file. (There is no file named rk3566-rg353vs-linux.v2.dtb) I even checked again if I fucked up this part on booth version but no. dmanlfc Build sadly not boot at all (directly skipt and boot to anberic android) 39 in the other hand the screen is not working. I even tryed some things ->

I used the k3566-rg353vs-linux.v2.dtb from 40 on 39, same result black screen

used the Bootfolder from 39 in 40 -> Also no boot

I use the 40 botfodler in 39 -> same results with rg353v-linux.dtb and rg353v-linux.v2.dtb.

Odd I don't experience the same issue at all. I've been using balena etcher to burn the base image and a linux host to mount the boot partition for the dtb rename.

Do you also have a rg353v with a v2 screen ? Maybe i have a newer revision again... But ark e.g. working fine. ._. As said if i burn the 39 the same way as 40 it boots normaly but i have the screen / blackscreen issue, 40 not boot at all ><...

Yes I have a 353v2. You need to rename the file rk3566-rg353v-v2-linux.dtb. If you dont see that file in your /boot directory you have not upgraded properly

batocera-linux / batocera.linux