Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to boot #124

Open
mtbykn opened this issue Sep 24, 2024 · 14 comments
Open

Unable to boot #124

mtbykn opened this issue Sep 24, 2024 · 14 comments
Assignees
Labels
Help Wanted Extra attention is needed Investigating The reported issue is under investigation Need More Info Further information is requested

Comments

@mtbykn
Copy link

mtbykn commented Sep 24, 2024

Unable to boot on
Vendor: LENOVO Lenovo Legion 5 15ARH05 laptop
Crashes during boot with errors on Ventura, Monterey , Sequoia.
Errors 152 service cannot load in current environment for launchd

@mtbykn
Copy link
Author

mtbykn commented Sep 24, 2024

Also looked at Big Sur and Sonoma get same error the autopilot script worked without error messages in the log file and screen said success.

@eversiege
Copy link
Collaborator

Hello! Can I ask you to provide your system specifications and autopilot logs if possible?

@mtbykn
Copy link
Author

mtbykn commented Sep 26, 2024

Ubuntu 24.10
Lenovo Legion 5 15ARH05
8gb RAM
AMD Ryzen 5 4600H
APC_RUN_26-09-2024_09-34-17.log

@mtbykn
Copy link
Author

mtbykn commented Sep 26, 2024

Hello, please let me know if you need anything else for resolving this boot issue!

@eversiege eversiege added Help Wanted Extra attention is needed Need More Info Further information is requested Investigating The reported issue is under investigation labels Sep 26, 2024
@eversiege
Copy link
Collaborator

Hello, might need something else too - run the script back, go to Compatibility Checks... and then run System Profiler, and send the .log that it gives, please. For now can't figure out the root of the cause...

@mtbykn
Copy link
Author

mtbykn commented Sep 26, 2024

Results
All checks have been completed
Please see the second log file below this one for System Profiler,
──────────────────────────────────────────────────────────────
READY ━━━━━━━━━━ 100%
──────────────────────────────────────────────────────────────

SPT_26-09-2024_11-37-09.log
Please see attached

@eversiege
Copy link
Collaborator

So we are starting to piece some some stuff together and we see maybe this is about memory? But in order to verify that, I will (for last time I hope) ask you for your generated vm-script. It should be somewhere in your project's root directory (aka where you launch main.py at)

@mtbykn
Copy link
Author

mtbykn commented Sep 26, 2024

boot.txt

@eversiege
Copy link
Collaborator

eversiege commented Sep 26, 2024

Ah. In the boot script, you've tried to specify 4 threads on 2 cores - but QEMU multiplies the amounts together for total thread count, so think of your virtual machine using literally 8 cores. For it to launch, you will need to change this value to:

CPU_THREADS="2"

Please tell me if this fix has worked for you. Cheers!

@eversiege
Copy link
Collaborator

eversiege commented Sep 26, 2024

TODO: Write this in the GOTCHAS page

@mtbykn
Copy link
Author

mtbykn commented Sep 26, 2024

Changed to 2 threads and still get the same issue, it's nice of you for taking the effort, thanks.

@eversiege
Copy link
Collaborator

Does it straight up not boot or gets to some point on macOS bootloader?

@mtbykn
Copy link
Author

mtbykn commented Sep 27, 2024

When I run the boot.sh the system will either reboot or just stop and gives the error code listed above.

@eversiege
Copy link
Collaborator

the system will either reboot

...wait, like, the entire host system?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Help Wanted Extra attention is needed Investigating The reported issue is under investigation Need More Info Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants