eduardofilo / RG350_adam_image

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Loading brightness setting

jcalpha opened this issue · comments

Hello friends!
I'm having trouble installing Adam on my RG 350P. It starts to load but stops with the message Loading brightness setting....
I have already tested versions 1.3, 1.4, 1.4.1 and 1.4.2.
Using another image, like Rogue, for example, works normally.
Any tips to resolve???
rg350p-load
?

Hello @jcalpha

Just to clarify...

I have already tested versions 1.3, 1.4, 1.4.1 and 1.4.2

you're getting the same exact issue with every version of Adam Image you've tried above?

Can you confirm after flashing the image you've reconnected your mircosd reader to your PC and run the select_kernel script choosing option 3 for the RG350P?

Have you tried flashing to a different microsd card? And perhaps try the microsd flashing process from a different PC? Are you using Balena Etcher (BE)? You could also try unpacking the *.img.xz file first (with 7-zip) before flashing with BE.

If you have access to a Linux PC (or make yourself a Linux live USB to boot from) check that the following file exists:
/media/data/local/etc/brightness.state
You could try deleting this file as it will be recreated at startup. You could also edit brightness.state with a different value; mine is set to 6 by default.

you're getting the same exact issue with every version of Adam Image you've tried above?

The last one was the version 1.4.2

Can you confirm after flashing the image you've reconnected your mircosd reader to your PC and run the select_kernel script choosing option 3 for the RG350P?

Yes, I´ve chosen this option (3).

Have you tried flashing to a different microsd card? And perhaps try the microsd flashing process from a different PC? Are you using Balena Etcher (BE)? You could also try unpacking the *.img.xz file first (with 7-zip) before flashing with BE.

Yes, I´ve tried flashing to another microsd card. I´m using Balena Etcher.

If you have access to a Linux PC (or make yourself a Linux live USB to boot from) check that the following file exists:
/media/data/local/etc/brightness.state
You could try deleting this file as it will be recreated at startup. You could also edit brightness.state with a different value; mine is set to 6 by default.

I´m using a Windows laptop. I´ll try to modify this file.

Thanks for your attention!

I´m using a Windows laptop. I´ll try to modify this file.

You'll need Linux to view the partition containing /media/data/local/etc/brightness.state
so you'll need to create a Linux Live USB and boot your laptop from that. SystemRescue is a good choice as it's a useful tool to have on standby anyway... and it's a relatively small download. You can use Rufus to flash the image to usb.
I choose the option to load to RAM, then you can take the USB out. Then type the command startx to launch the GUI.

Actually the problem has to be between the time the splash message is printed and the next one, which following the order of the init.d scripts should be:
"Setup permissions..."

The brightness one is related to this script:
https://github.com/OpenDingux/buildroot/blob/opendingux/board/opendingux/target_skeleton/etc/init.d/S90brightness.sh
And the permissions one is:
https://github.com/OpenDingux/buildroot/blob/opendingux/board/opendingux/target_skeleton/etc/init.d/S97perms.sh

But viewing the last one it does not do much before issuing the message. Therefore, it does seem logical to look at the previous one.
And what it does is basically:

cat /usr/local/etc/brightness.state /sys/class/backlight/backlight/brightness

Try connecting by SSH and execute that command manually. Or the entire script with sudo.
But it is weird. Surely the problem has nothing to do with these topics.

I close the issue because of its age and because it is probably a particular problem.