Jump to content

hoffsta

Members
  • Content Count

    20
  • Joined

  • Last visited

About hoffsta

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Male
  • Location
    Oregon

Recent Profile Visitors

1,370 profile views
  1. hoffsta

    OpenCore Discussion

    I'm unable to boot into my Catalina recovery partition from OpenCore 0.5.4. Even with boot flags: -v keepsyms=1 debug=0x100, I get an immediate kernel panic/reboot, with no verbose or log info, as soon as I select the recovery partition at picker. Using Clover on the same system boots recovery fine. Any ideas? EFI.zip
  2. Thank you for the help with this problem. I tried the DSDT and unfortunately it doesn't solve this issue. The 3rd party controllers do show up as "Intel 77 Series Chipset" in System Info now, but the problem with booting in OpenCore persists. It appears this is now a known bug with OpenCore: https://github.com/acidanthera/bugtracker/issues/669
  3. hoffsta

    OpenCore Discussion

    Haha- {censored} man! It’s always the little things that steal the most hours away. Thank you for the second set of eyes. I’m back in business. Cheers Andrey
  4. hoffsta

    OpenCore Discussion

    Question/Issue with PlatformInfo: I followed the OpenCore Vanilla Desktop Guide, which directed me to fill in the following info for PlatformInfo section: Automatic: True Generic: MLB: C02221405J9F2FR1M (iMac13,2 via GenSMBIOS) Rom: (mac address) SpoofVendor: True SupportsCSM: False SystemProductName: iMac13,2 SystemSerialNumber: C02HR7Z3DNCW (iMac13,2 via GenSMBIOS) SystemUUID: 197A98EE-127B-471E-B4DD-A3F3E0433A5D (iMac 13,2 via GenSMBIOS) UpdateDataHub: True UpdateNVRAM: True UpdateSMBIOS: True UpdateSMBIOSMode: Create (also tried Overwrite) My assumption was OC would insert this information only, or possibly use a database to generate other fields (Product Name, Version, Chassis Handle, Type, etc.) However, when I run dmidecode, the output finds a bunch of info for a Macbook10,1 # dmidecode 3.2b Scanning I/O Registry for entry point. SMBIOS 3.2 present. 54 structures occupying 2353 bytes. Table at 0xD9134000. Handle 0x0001, DMI type 0, 26 bytes 0000: 00 1a 01 00 01 02 00 00 03 7f 80 98 8b 3f 01 00 0010: 00 00 03 0d 04 06 ff ff 00 00 BIOS Information Vendor: Acidanthera Version: 183.0.0.0.0 Release Date: 10/30/2019 ROM Size: 8 MB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 4.6 Handle 0x0002, DMI type 1, 27 bytes 0000: 01 1b 02 00 01 02 03 04 ee 98 7a 19 7b 12 1e 47 0010: b4 dd a3 f3 e0 43 3a 5d 06 00 05 System Information Manufacturer: Acidanthera Product Name: iMac13.2 Version: 1.0 Serial Number: C02HR7Z3DNCW UUID: 197a98ee-127b-471e-b4dd-a3f3e0433a5d Wake-up Type: Power Switch SKU Number: Not Specified Family: MacBook Handle 0x0003, DMI type 2, 15 bytes 0000: 02 0f 03 00 01 02 03 04 00 09 05 04 00 0a 00 Base Board Information Manufacturer: Acidanthera Product Name: Mac-EE2EBD4B90B839A8 Version: MacBook10,1 Serial Number: C02221405J9F2FR1M Asset Tag: Not Specified Features: Board is a hosting board Board is replaceable Location In Chassis: Part Component Chassis Handle: 0x0004 Type: Motherboard Contained Object Handles: 0 Handle 0x0004, DMI type 3, 22 bytes 0000: 03 16 04 00 01 09 02 03 04 03 03 03 03 00 00 00 0010: 00 00 01 00 00 00 Chassis Information Manufacturer: Acidanthera Type: Laptop Lock: Not Present Version: Mac-EE2EBD4B90B839A8 Serial Number: C02HR7Z3DNCW Asset Tag: MacBook-Aluminum Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 SKU Number: Not Specified * Where is OpenCore getting the Macbook10,1 info from and how do I update it? * Is the Automatic setting not able to populate the correct information for the additional fields, or is it broken/misconfigured? * If that is not the role of 'Automatic' can I assume I am expected to enter all of those additional fields manually into config.plist? * If so, what is a good source to find the correct values for each field? * Should the Desktop Guide be updated to include a solution for this issue? Thanks!
  5. Hey thanks for helping out! I went ahead and rebooted with your Clover folder before RunMe to ensure a clean scan. Here's the file that it spit out: Cheers Send me OfficeHackintosh.zip
  6. Hey there- I have a Gigabyte GA-X77X-UD5H, rev. 1.1, bios F16j. I recently set it up with OpenCore and it mostly runs great, however there’s one big problem: the system won’t boot when any drives are connected to the Marvel 88SE9172 SATA controller. Actually it will eventually boot, but it takes almost 20 mins to reach the picker menu. BIOS recognized the drive and I can even boot to Windows from it. Clover will even boot fine, but I have some old kexts and patches I don’t even understand. In MacOS, the controller is simply listed as “generic AHCI controller” I haven’t had any luck asking for help on the OpenCore forum so I thought I’d post here. Is there a chance some DSDT/SSDT patch would help this controller be recognized? If so, where would I start? I’ve searched high and low for help on this but haven’t had any luck. Here’s a link to my EFI folder and Bios settings: https://github.com/partytimeexcellent/Hackintosh-OpenCore-GA-Z77X-UD5H-3770K-HD4000?files=1
  7. hoffsta

    OpenCore Discussion

    Is is possible to get good performance from OC when booting from a on-board Marvell 88SE9172 SATA Controller on Z77X-UD5H board? When boot drive is connected to this controller, loading to the OC picker menu takes 20+ minutes. Using Intel 7 series port takes seconds. Clover doesn't have this problem so it seems it must be related to some differences in .efi drivers. I currently have only ApfsDriverLoader, FWRuntimeServices, & HFSPlus drivers on OC 0.5.4. Do I need other drivers?
  8. hoffsta

    OpenCore Discussion

    Anyone have an idea why my OC stalls out when I connect a second bootable SATA SSD to the motherboard? Used with just one SATA drive, I can boot perfectly into Mojave in about 13 seconds and everything work perfectly. If I connect a second SSD with Windows or another MacOS install, OC takes over 4 minutes to reach the picker menu. I also can't boot up Windows if I try. If I use a Clover USB stick, I can see and boot from both drives fast and without issue. Here is my EFI folder Here is a log of a fast, single drive boot. Here is a log of a stalled, dual drive boot. I added the photo of my monitor because there is more info displayed at the point it gets stuck than what's written to the log. How could I get the log to write even more? I have debug target set to <75> This EFI and config were made following the Vanilla Desktop Guide to the best of my abilities. I also tried this without the UsbKbDxe.efi and I tried swapping the VBoxHfs.efi for HFSPlus.efi with no change. Thank you for any insight!
  9. I have a perfectly working OC EFI to boot Mojave from a SATA SSD that I built with the Vanilla guide. Anytime I plug-in another SATA SSD with a GUID Windows10 install, OC fails to process to the picker menu. I'm not even trying to boot Windows from OC, just want to use the computer with both drives attached. This has to be a problem with my config or possibly BIOS settings but I have no idea what would cause this in BIOS. Using a USB stick with a Clover EFI works as expected and I can boot into either system without issue. Anyone have guidance on what I'm missing? Attached is my config. Thanks! config.plist Full EFI folder EDIT: Actually it looks like this problem is occurring any time there's a second bootable SATA drive connected, not just Windows. I plugged in a backup drive with Mojave on it and the same problem occurs.
  10. That's what I suspected. Thanks!
  11. Hey there, I have a Z77X-UD5H board which has a total of 14 USB ports (counting USB3 as 2x ports). Is there still any need to use USBInjectAll.kext or to make a USB map? Running OpenCore with Lilu, VirtualSMC, WhateverGreen, AppleALC, AtherosE2200Ethernet, IntelMausiEthernet, RealtekRLT8111 kexts. Thanks
  12. hoffsta

    Working OpenCore in Z77 hackintosh

    Hi there, I'm trying to get my Z77 (Gigabyte Z77X-UD5H) board up and running on my first go at OpenCore. I took a look at your config and noticed you don't have your DSDT.aml file enabled, nor many of the SSDTs. I'm curious why you don't use them and how you determine which ones you need? Thanks
  13. hoffsta

    OpenCore fails to start

    Hey there- I meticulously followed the vanilla guide and built what I thought was a pretty kick-ass EFI folder on my EFI partition of a USB stick. Unfortunately, when I try to run it, my motherboard insists there’s no bootable drive available. What are some common issues that would prevent OpenCore from even starting up? This is the latest version, I have all the proper drivers & kexts loaded, a DSDT, a couple SSDT from the guide. Thanks
  14. I can't get this guide to work, following your guide. MacPwn did it's thing but I can't get it to boot from the USB stick. I have these options from the bios boot selection: Built-In EDK Shel Samsung SSD 860 EVO 1TB Install macOS Mojave I select the "Install macOS Mojave" but then I get the circle with a slash through it. No other way to proceed. Does MacPwn create other bootable partitions? If so, the Bios can't see them. EDIT- Yep, I checked with Clover Configurator on another install and the MacPwn didn't create any UEFI partitions on the USB, just the install Mojave partition.
  15. Also, the Ozmosis BIOS is from 2013. Any reason the latest Gigabyte 16j from Nov. 2017 wouldn't work or be better?
×