Contribute
Register

Reboot error: Where to Begin Troubleshooting Config.plist

Status
Not open for further replies.
Joined
Nov 2, 2018
Messages
191
Motherboard
Dell Optiplex 3090 i3 MFF
CPU
i3-10105T
Graphics
UHD 630
Mac
  1. iMac
  2. MacBook Air
Mobile Phone
  1. iOS
The goal is to enable Monterey Display 4k on a i3-10105T Optiplex Micro 3090.

An OC 8.5 example with an i3 10th get CPU was modified and tested:

https://github.com/quanghd96/Hackintosh-B460M-BAZOOKA-i3-10100-iGPU-UHD630

The Opencore picker allows the SSD volume to be selected and white Apple icon that sits atop the progress bar is returned. Unlike previous attempts, the Apple icon seems to be in 4K (smaller than 2K), which leads me to believe that the HD630 iGPU is closer to being correctly configured for 4K.

Unfortunately, the machine reboots when the progress bar reaches ~25%. .

What can be done to troubleshoot to determine what exactly is causing reboot?

The example's config.plist was modified and is attached. Any suggestions / explanation are always appreciated. Thank you
 

Attachments

  • config_02_quanghd96_redact.plist
    43.2 KB · Views: 19
  • EFI _quanghd96_B460M_Redact.zip
    6.4 MB · Views: 31
  • LogsArchive.zip
    14.9 KB · Views: 17
Add the verbose boot argument -v, keepsyms=1 and debug=0x100 to your config.plist.

This should show the verbose text on your display, including the cause of the kernel panic. Take a photo or video of the verbose text. Post a copy here and hopefully we will be able to see what needs changing to allow the system to boot to the OS.
 
@Edhawk, Thank you for the suggestion: I look forward to your reply / review of photo

Notes:
- boot arguments add to config.plist (attached): -v, keepsyms=1 and debug=0x100
- PC does not reboot now: it halts and returns contents in attached photograph
- did not return Apple Icon & Progress Bar (new boot args?)
 

Attachments

  • Screen Shot 2022-12-01 at 9.31.23 AM.png
    Screen Shot 2022-12-01 at 9.31.23 AM.png
    3.4 MB · Views: 21
  • opencore-2022-12-01-142403.txt
    256 KB · Views: 20
  • config_02_Edhawk_bootarg.plist
    43.2 KB · Views: 23
Last edited:
Just to clarify, the three boot arguments do the following:

Screenshot 2022-12-01 at 14.46.44.png

So as you can see, the boot arguments prevent the Apple Logo showing, and stop the system automatically rebooting after a kernel panic.

Was there any more text after the lot shown in the screenshot/photo you provided, or did it remain on this screen till you rebooted the system?

The error appears to be this:

ALF. old data swfs_pid_entry.....

Is the SSD you are using for the macOS installation connected internally or externally? If external, try installing macOS to an internal drive (SATA or NVME).

Apple's 'sealed volumes' can be problematic (since Big Sur) when you try to install to an external drive.
 
CONTEXT:

Q1. Was there any more text after the lot shown in the screenshot/photo you provided, or did it remain on this screen till you rebooted the system?
A1. No more text: the photo was snapped after the system halt.

Q2. Is the SSD you are using for the macOS installation connected internally or externally? If external, try installing macOS to an internal drive (SATA or NVME).
A2. The NVME SSD is installed internally.



"The error appears to be this: ALF. old data swfs_pid_entry....."

- Google returned a post, recommending that that an internal drive be used.

- The attached photo was snapped before the system halted. Hopefully it will help.


Any guidance / suggestions are appreciated. Thank you
 

Attachments

  • Screen Shot 2022-12-01 at 12.35.05 PM.png
    Screen Shot 2022-12-01 at 12.35.05 PM.png
    4 MB · Views: 21
Last edited by a moderator:
The new image in post #5 doesn't show the same 'error'. Actually I can't find a 'critical' error in the image.
  1. There are a few USB related issues, but they don't appear to have caused the KP.
  2. There are a few HFS+ mount issues, probably related to the USB issues, again not causing a KP.
  3. The APFS snapshot is shown as Clean (Blue_SN570)
  4. You seem to have gone all out with the Intel boot arguments in search of your 4K resolution.
  5. The shikigva=80 boot argument stopped working with the release of Big Sur, so It probably does nothing in Monterey. You may want to read the Shiki FAQ.

I can't read the text at the very bottom of the screen, it might be important, it might not.
 
Status
Not open for further replies.
Back
Top