search

sebanc / brunch

Boot ChromeOS on x86_64 PC - Supports Intel CPU/GPU from 8th gen or AMD Ryzen
GNU General Public License v3.0
3.54k stars 387 forks source link

brunch/grub config updater not working #1252

Open poly3dfree opened 2 years ago

poly3dfree commented 2 years ago

I installed the latest brunch r93 with CrOS r93 rammus image. The android container was not starting so I seen this thing in wiki saying android_init_fix. But when I run sudo edit-brunch-config and select stuff it doesn't apply and give me this error.

Summary of the configuration: options: android_init_fix kernel: 5.4 kernel commandline parameters: enforce_hyperthreading=1 verbose mode: 0 brunch bootsplash: default_dark

cp: cannot stat '/mnt/stateful_partition/unencrypted/brunch_config/efi/boot/template.cfg': No such file or directory Brunch configuration saved. Press any key to reboot your computer...

after rebooting problem persists so I think it is not applying the configuration could you please confirm. Same thing when selecting ChromeOS(setiings) from grub.

I'm using this in MBR pc with mbr_support patch.

sebanc commented 2 years ago

Indeed, I forgot to add one file.

I have just updated the patch, could you try the new one ? (if you know how to do it, you can use "dd" to copy mbr.img from the mbr_support.tar.gz archive over partition 12)

poly3dfree commented 2 years ago

Hello sebanc, Now although its not showing error but apps are still not opening I get infinite loop of app's loading symbol it just keeps revolving and doesnt open. Could you please tell how can I confirm if changes are done. Before we could just edit boot file with the options we want, could you tell it's location so I can see? I was unable to find that file. It would be great.

PS: and trying android container to run from terminal by executing sudo android-sh gives error: find: '/run/containers/android*/': No such file or directory /usr/sbin/android-sh: Container PID file not found, is the container running?

sebanc commented 2 years ago

Restart chromeos, log-in then wait 2 minutes and post a dmesg (run "dmesg > ~/Downloads/dmesg.txt" in crosh shell and post dmesg.txt from your downloads folder.

A dmesg is the only way to see if the options... are correctly taken into account and from there I can debug it.

poly3dfree commented 2 years ago

dmesg.txt this is the log

sebanc commented 2 years ago

android apps do not work ? the log looks pretty good.

Which recovery image are you using ?

sebanc commented 2 years ago

*and everything seems ok regarding the options setup

poly3dfree commented 2 years ago

im using rammus 93 image and yes i still get that loading in apps but reading this : https://github.com/sebanc/brunch/issues/813 i think there is some preloading which is not been able to done because even after 2 mins there was disk lighting showing in CPU case which indicates something is loading i think i need to first wait for it, when it stops then im meant to login right?

sebanc commented 2 years ago

The android_init_fix option is supposed to prevent that but if it does not work I would suggest to remove the android_init_fix option and wait a few minutes at the login screen.

Did the android_init_fix option work in previous brunch versions on this machine ?

poly3dfree commented 2 years ago

How can i remove android_init_fix there is no checkmark in edit-brunch-config which i can uncheck.

Previously things were working great and i didnt applied any fixes.

sebanc commented 2 years ago

ChromeOS r92 introduced an increase in cases where the android container will fail to launch, I tried to improve the android_init_fix option to workaround that but it does not seem to work in your case. I will try to see if I can further improve it.

sebanc commented 2 years ago

Otherwise you could also help to find a way to improve the android init fix. Globally I added a script ( /usr/sbin/arc-init-wait) which runs in a loop until the android container is supposedly ready to start (line that contains "uses 32-bit capabilities" in dmesg").

You could try to see if it works better by adding an additional sleep delay or to tweak it some other way if you have ideas.

sebanc commented 2 years ago

Regarding options, the config is reset every time you run the setup menu, just run the setup menu again and don't tick android_init_fix if you don't want it.

poly3dfree commented 2 years ago

Thanks so much sebanc. I finally ran config setup and did everything default (no fix no hyperthreading) and i waited on login screen till disk indicator stopped then logged in and waited again till it stopped then i run play store and im finally able to run apps. But when I wait only on login screen and do not wait after login and open play store it doesnt work again.

So basically who has same problem should try waiting on both login and after login to finish disk loading. Again thanks so much sebanc for this wonderful project.