Issue: RG351v white screen #662
Comments
|
Does this happen using AmberElec or uOS as well? |
|
I tried amberelec and lakka. Both showed the same behavior. I can try uOS right now and get back to you. |
|
Same behavior on uOS. |
|
Yes they would. Please provide them along with the boot.ini file. |
|
Great. Thank you. |
|
Try copying the |
|
Looks like that worked! It's went through what I'm assuming is a normal installation process. Booting runs the rumble motor for about 15 seconds. Got to emulationstation, motor stopped, and the display looks correct. Maybe that rk3326-anbernic-st7703.dtb I uploaded should be packaged in as a separate dtb.v2 file the same as the rg353v. Thanks for your quick help! Anything else I can do? |
|
Good and bad problem is that it's too many steps. Going to see if at least this one can be accomodated without needing to swap that file. Going to run some tests on my end to see if this can be easily accomodated. Thanks for your help on this. |
|
Comment back if you'd like me to test anything in the future! Thanks again |
|
I really can't believe there's another one of these to deal with.. what a pain .I grabbed that zip for uOS to work on it . I'll get to it soon |
|
I use this for Jelos. It can boot up, but it doesn't have sound. |
|
Might be related, after running into the same issue I attempted this fix and got past the white screen. When trying to connect to wifi, however, no buttons work and I need to reset the device. |
Rebooting while having a Nintendo Switch Pro Controller connected via usbc lets me navigate the wifi menu, though that disables control in the filesystem menu, requiring a reboot without the controller connected for that to work. Again, may or may not be related to the new hardware. Thought it would be worth mentioning. |
|
Thanks to this thread and to rezicG here for the assistance. Could not mount the boot drive on Windows 11. Could not assign a letter to it with Disc Management. Found the Root Partition in Ubuntu and via rezics help found the boot partition. Had to force mount the partition in Ubuntu and use sudo to copy and rename the folders. Commands for reference: Eject the SD and boot up ARKOS. |
|
i'm trying currently to run headless on my RG351V via arkOS. i'm experiencing the white screen on boot. where do i go from here? really looking forward to a response! |
Idk what u mean headless, but the white screen can be fixed by downloading this This dtb and replacing the one on the ArkOS SD card u have now.. It's the dtb with the fix for the screen.. The directions to replace it are above |
i tried a few times & realized i was doing it completely wrong! it is now working, thank you so much! |
|
Good to hear . Enjoy |
|
If possible, can someone test the attached file on a rg351v with a v2 screen. Hopefully it works and brings working volume button control and wifi. Make sure to rename the existing rk3326-rg351v-linux.dtb file on the ArkOS installation in the BOOT partition to something else first. Then copy the file within the attached zip file to the BOOT partition and rename it to |
|
I can test this in the next few days, I’ll test volume and wifi as well.
…On Mon, Apr 17, 2023 at 11:13 AM christianhaitian ***@***.***> wrote:
If possible, can someone test the attached file on a rg351v with a v2
screen. Hopefully it works and brings working volume button control and
wifi.
Make sure to rename the existing rk3326-rg351v-linux.dtb file on the ArkOS
installation in the BOOT partition to something else first. Then copy the
file within the attached zip file to the BOOT partition and rename it to
rk3326-rg351v-linux.dtb then try to boot ArkOS again and report what
happens.
rk3326-rg351v-linux-v2.zip
<https://github.com/christianhaitian/arkos/files/11254144/rk3326-rg351v-linux-v2.zip>
—
Reply to this email directly, view it on GitHub
<#662 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A6OBJXF24H4H2HSE7FZQ3Q3XBWB25ANCNFSM6AAAAAAVYDT5KY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Using the 2.0_03112023 build, looks like the v2 .dtb works on my RG351V. Screen confirmed working correctly. Volume buttons confirmed working correctly. I don't use the wifi on any of my emulation devices so I might not be the best person to confirm. I was able to add a wifi connection but that doesn't seem to do anything and wifi in the status screen still shows "down". I think I'm doing it wrong. |
I got a replacement unit with the new screen that is currently running version 2.0 01152023-1. The new file seems to work. The startup is quicker and the device doesn't vibrate that long anymore. The volume button works and also the wifi is up again. My router shows the RG351V as connected device and downloading new themes is also working. Thanks for the effort! |
|
Excellent. Thank you for confirming the functionality. Next step is to integrate this so that manually changing this file will no longer be necessary. |
|
The above worked for me on AmberElec as well, though volume buttons do not on that firmware. Thanks for the updated driver @christianhaitian ! |
|
One more update, the rk3326-rg351v-linux.dtb.v2 found in https://drive.google.com/drive/folders/1kHrVOAlIDt1I9Lkjzp-6Ptigcq2E55OT (from AmberELEC discord) also works, the volume rockers and wifi work as well. |
That's my dtb from uOS, mine and Christain's are identical so u know |
|
Interesting! In my last build I renamed |
Honestly who knows lol. There's so much that can go wrong and not play well together.. Esp when we start playing with device trees etc..I notice issues esp when the dtb isn't built with the image from the start . Sometimes it needs to be replaced for some reason.. But the same dtb built with the image has no issues.. Strange .. And thanks for the support |
|
I ran into the issue where the screen is white/flashing colors with a black bar on the side as well, leading me to this page but, I don’t know what i’m doing. The solutions above saying replace some files in the BOOT partition, I assumed this meant a BOOT folder but I don’t have one, and I apologize for sounding really dumb right now. I don’t see what anyone is talking about, the root folder is simply EASYROMS (D:) after flashing the 351v img of ArkOS to the MicroSD card. Everything in the root folder is just folders for other emulators. I wasn’t expecting to get in over my head with technical issues. All the research I did before buying this device made everything look as simple as dragging and dropping or using programs to flash but I keep running into problems. I’ve modded all my retro consoles just fine without any issues like this (Wii, Vita, PSP, 3DS) |
It usually is as simple as flashing an OS to a sd card but the manufacturer has changed the screen on this device due to supply issues and has not shared how to boot more than 1 screen type in a single image. So what you have to do for what we call a v2 screen is to replace a dtb file that is on the boot partition of the sd card once you've flashed ArkOS to a MicroSD card. If you're only seeing one partition, then either Windows has not assigned a drive letter to your fat32 boot partition for the sd card, or you used Balena Etcher to flash the sd card which causes issues. Once you can see the fat32 partition, it should be as simple as following the directions here: (#662 (comment)) to replace a single file than boot the device. |
I used Rufus as the tutorial instructed, as it did mention the problems with Balena Etcher. I’ll try Win32DiskImager that is also linked in the tutorial. Thank you for your fast reply, I hope I can get it figured out EDIT: Took some trial and error and other troubleshooting but everything worked! The first file replacement got the screen right but took away the volume and wifi just as other people reported, but the second file replacement fixed that as well. Thank you so much, I was sure I'd just not be able to use my new device! |
|
hi guys, followed this feed to get past the white screen issue but still having the sound rocker issue on Amberelec, was there a fix for this operating system at all? any help is much appreciated. |
|
Sorry just had a re-read and seen this has already been answered and it has fixed it, thanks for the thread guys, you life savers. |
|
Not to re-open this issue but I wanted to add an updated fix for anyone still struggling to fix the white or yellow screen issue on your RG351V, even after swapping out the dtb file in boot with the v2 from this thread:
It should work now |
Describe the Issue (If applicable)
Got a new RG351V, looks like a new display panel may be included so there may have been a hardware revision. Looks identical to the previous display issue seen with the RG353V.
How can the issue be reproduced? (If applicable)
Any new install causes a white screen with a vertical black bar on the left.
What device are you using?
RG351v
What version of ArkOS are you on?
the 2.0 package from 01/15
Anything else you'd like to include that may help to review this issue or feature request?
The text was updated successfully, but these errors were encountered: