sMaX 0 Posted January 25 Share Posted January 25 Hi, I'm trying to get this old machine up to high sierra so I can then try and make a Catalina install for a new machine.. I've tried to make the EFI from scratch with the opencore install guide.... I've come across a couple of things of which I'm not to sure what to do... It starts loading after the selection/picking screen but never get 's to the installer screen. I've added the full dump from opencore. These are the last lines: 5:452 00:171 OCAK: 64-bit AppleIoMapper replace count - 1 35:561 00:108 OCAK: Patch success com.apple.iokit.IOPCIFamily AppleIoMapper 35:680 00:119 OC: Prelinked status - Success 35:871 00:191 OCSMC: SmcReadValue Key 4D535463 Size 1 35:979 00:108 OCSMC: SmcReadValue Key 4D534163 Size 2 36:088 00:108 AmiShimTimerBoostExit changed current period to 100000 I'm guessing it's Geforce related. I've always chosen the web drivers option throughout the install guide, but maybe that was a mistake.. I've tried toggling SetupVirtualMap yes/no but no difference. Anyone with more experience and knowledge have a clue or wants to have a look at my configplist? Greets opencore-2021-01-25-154402.txt config.plist Link to post Share on other sites
Hervé 2,155 Posted January 25 Share Posted January 25 You can only choose the Nvidia Web driver after you've installed macOS and installed the Web Driver. It's and add-on package, not an integrated part of the OS. As such, boot with Nvidia graphics disabled (in VESA mode) until you've completed the basic macOS installation. You'll then install the Web driver version that matches your specific High Sierra build. sMaX 1 Link to post Share on other sites
sMaX 0 Posted January 25 Author Share Posted January 25 Ok thanks so much! Like I was afraid of... Can I ask for a couple more pointers? I'm afraid I've made a couple more beginnersmistakes.... LIke the boot args for example: -v keepsyms=1 nvda_drv_vrl=1 And for : Misc/security/Securebootmodel I've also put disabled for nvidia webdrivers .... Link to post Share on other sites
Hervé 2,155 Posted January 25 Share Posted January 25 Remove boot arg nvda_drv_vrl=1 and replace with nv_disable=1 to begin with; that'll disable Nvidia graphics. Once High Sierra is installed, download and install the Web Driver relevant to your 10.13 specific build (look it up in About this Mac and click on the 10.13 version for details), then modify your config to load it (i.e. restore your initial boot arg). Follow the guidance available at Dortania. https://www.insanelymac.com/forum/topic/324195-nvidia-web-driver-updates-for-macos-high-sierra-update-nov-13-2020/ https://dortania.github.io/GPU-Buyers-Guide/misc/bootflag.html#nvidia-boot-arguments sMaX 1 Link to post Share on other sites
sMaX 0 Posted January 25 Author Share Posted January 25 Oh great info man, thanks! I was missing those pieces of the puzzle, let's give it a shot! Link to post Share on other sites
sMaX 0 Posted January 26 Author Share Posted January 26 Hi again, So I also added debug=0x100 in boot args (don't know why I didn't initially) And it showed me more info: panic cpu0 caller NO HPETs available cpu configured incorrectly This panic I found in the opencore guidehttps://dortania.github.io/OpenCore-Install-Guide/troubleshooting/extended/kernel-issues.html#kernel-panic-appleintelmcereporter Quote This is likely due to faulty or outright missing NullCPUPowerManagement. To fix the issue, remove NullCPUPowerManagement from Kernel -> Add and EFI/OC/Kexts then enable DummyPowerManagement under Kernel -> Emulate Note: On older Intel CPUs(ie. Penryn and older), it may be due to IRQ conflicts or the HPET device being disabled. To resolve, you have 2 options: SSDTTime's FixHPET Option (opens new window)SSDTTime's FixHPET Option Forcing the HPET Device on Forcing the HPET Device on is what I did since it 's quicker: Now I get to the install screen and can install but it stops at 2 minutes remaining with: an error occured while preparing the installation.. try again. (Before reboot) For this case I don't find anything in the guide.. The last lines in verbose before the gui pops up did still mention CPU unsupported (or something like that)...but no panic. Link to post Share on other sites
sMaX 0 Posted January 26 Author Share Posted January 26 Also, in BIOS HPET support is enabled and HPET Mode: 32bit (should this be 64bit?) Link to post Share on other sites
sMaX 0 Posted January 26 Author Share Posted January 26 I'm a little stuck again to fix this, Quote This is likely due to faulty or outright missing NullCPUPowerManagement. To fix the issue, remove NullCPUPowerManagement from Kernel -> Add and EFI/OC/Kexts then enable DummyPowerManagement under Kernel -> Emulate Note: On older Intel CPUs(ie. Penryn and older), it may be due to IRQ conflicts or the HPET device being disabled. To resolve, you have 2 options: SSDTTime's FixHPET Option (opens new window Forcing the HPET Device on TRIED THIS; NO LUCK So i'm trying SSDTTime's FixHPET Option: Dump DSDT(the one SSDTTime did for use will work) ----did this with sysreport quirck, because ubuntu nor windows 10 want to load/install... no idea why even those don't work, mind you the same machine is running 10.10.2... Decompile DSDT Make SSDTs based off of it(You'll need either MaciASL or a text editor for this) Compile SSDTs ...But then what? Link to post Share on other sites
sMaX 0 Posted February 1 Author Share Posted February 1 Ok, I did the fixHPET via windows and the SSDTTIme tool... But now it fails with: Target is not convertible to APFS: You may not install to this volume because it can not be converted to APFS Link to post Share on other sites
Recommended Posts