Contribute
Register

HD 3000 — macOS Sierra

Status
Not open for further replies.
Alright. I learned what F4 does and when to press it. I learned my BIOS clock was wrong, updated the time. And for good measure I re-ran all the Terminal commands before reposting. This code is fresh from a booted 10.12.5 install. But was getting glitches on 10.10 and 10.11 as well.

Any insight is very much appreciated. Thanks!

Code: 
$ sudo touch /System/Library/Extensions && sudo kextcache -u /
Password:
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext RealtekRTL8111.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext realtekALC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext GenericUSBXHCI.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67054 0xFFFFFFFFFFFEFA12 for kext AppleHDA.kext
KernelCache ID: 2EA0F719AAE2DF7A4596A957E3BFFC27

Code: 
kextstat|grep -y acpiplat
   13    1 0xffffff7f828a5000 0x60000    0x60000    com.apple.driver.AppleACPIPlatform (5.0) 65E05472-6AE7-3308-8CC8-FA6CB0DB2AEE <12 11 7 6 5 4 3 1>

kextstat|grep -y appleintelcpu
   25    0 0xffffff7f824d8000 0x2b000    0x2b000    com.apple.driver.AppleIntelCPUPowerManagement (219.0.0) 24568E6C-556D-36A8-BF1F-F390B1E85C5B <7 6 5 4 3 1>
   31    0 0xffffff7f824d3000 0x3000     0x3000     com.apple.driver.AppleIntelCPUPowerManagementClient (219.0.0) B802638B-251C-3602-BA8C-001F87228765 <7 6 5 4 3 1>

kextstat|grep -y applelpc
   91    0 0xffffff7f8232f000 0x3000     0x3000     com.apple.driver.AppleLPC (3.1) F51595F0-F9B1-3B85-A1C3-F984DAD4107E <87 12 5 4 3>

kextstat|grep -y applehda
   84    1 0xffffff7f82586000 0x1d000    0x1d000    com.apple.driver.AppleHDAController (279.48) ED51F180-19C8-3DE1-AF81-0E389D98ADDE <83 82 77 12 7 6 5 4 3 1>
  112    0 0xffffff7f82708000 0xb5000    0xb5000    com.apple.driver.AppleHDA (279.48) 806B8C17-50CA-3C6B-90B3-195F38D8FB89 <111 93 84 83 82 77 6 5 4 3 1>
 

Attachments

  • BruceLee5000-Sierra.ioreg.zip
    509.5 KB · Views: 96
  • BruceLee5000-Sierra.CLOVER.zip
    1.5 MB · Views: 78
CustoMacMini 2011
GA-H67N-USB3-B3 |  i5 2500K |  HD 3000
BruceLee5000 said:
Alright. I learned what F4 does and when to press it. I learned my BIOS clock was wrong, updated the time. And for good measure I re-ran all the Terminal commands before reposting. This code is fresh from a booted 10.12.5 install. But was getting glitches on 10.10 and 10.11 as well.

Any insight is very much appreciated. Thanks!

Code: 
$ sudo touch /System/Library/Extensions && sudo kextcache -u /
Password:
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext RealtekRTL8111.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext realtekALC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext GenericUSBXHCI.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67054 0xFFFFFFFFFFFEFA12 for kext AppleHDA.kext
KernelCache ID: 2EA0F719AAE2DF7A4596A957E3BFFC27

Code: 
kextstat|grep -y acpiplat
   13    1 0xffffff7f828a5000 0x60000    0x60000    com.apple.driver.AppleACPIPlatform (5.0) 65E05472-6AE7-3308-8CC8-FA6CB0DB2AEE <12 11 7 6 5 4 3 1>

kextstat|grep -y appleintelcpu
   25    0 0xffffff7f824d8000 0x2b000    0x2b000    com.apple.driver.AppleIntelCPUPowerManagement (219.0.0) 24568E6C-556D-36A8-BF1F-F390B1E85C5B <7 6 5 4 3 1>
   31    0 0xffffff7f824d3000 0x3000     0x3000     com.apple.driver.AppleIntelCPUPowerManagementClient (219.0.0) B802638B-251C-3602-BA8C-001F87228765 <7 6 5 4 3 1>

kextstat|grep -y applelpc
   91    0 0xffffff7f8232f000 0x3000     0x3000     com.apple.driver.AppleLPC (3.1) F51595F0-F9B1-3B85-A1C3-F984DAD4107E <87 12 5 4 3>

kextstat|grep -y applehda
   84    1 0xffffff7f82586000 0x1d000    0x1d000    com.apple.driver.AppleHDAController (279.48) ED51F180-19C8-3DE1-AF81-0E389D98ADDE <83 82 77 12 7 6 5 4 3 1>
  112    0 0xffffff7f82708000 0xb5000    0xb5000    com.apple.driver.AppleHDA (279.48) 806B8C17-50CA-3C6B-90B3-195F38D8FB89 <111 93 84 83 82 77 6 5 4 3 1>
Click to expand...

Problems:
- OsxAptioFixDrv-64.efi is missing from drivers64UEFI
- all kexts you need should be installed to the system volume, InjectKexts should be "Detect"
- patched ACPI is out of sync with native
Note:
SPEEDY-NUC origin rehabman$ diff ../origin/DSDT.dsl ../patched/DSDT.dsl |grep -y systemmemory
< OperationRegion (SMOD, SystemMemory, 0x000FF840, 0x01)
> OperationRegion (SMOD, SystemMemory, 0x000FF840, One)
< OperationRegion (ELKM, SystemMemory, 0x000FFFEA, 0x01)
> OperationRegion (ELKM, SystemMemory, 0x000FFFEA, One)
< OperationRegion (INFO, SystemMemory, 0x000FF840, 0x01)
> OperationRegion (INFO, SystemMemory, 0x000FF840, One)
< OperationRegion (IGDM, SystemMemory, 0xC0FA0800, 0x2040)
> OperationRegion (IGDM, SystemMemory, 0xFFFF0000, 0x2040)
 
Thanks Rehab!

Should I use "OsxAptioFixDrv-64.efi" if I'm on a Series 6 board? Legacy, not UEFI.

I downloaded the DSDT from the TonyMacx86 site because I followed the suggested parts precisely.
Should I replace the original with the Patched?
If it boots, does that guarantee I'm booted from the Patched DSDT? Or could it switch back and forth? That might explain why sometimes glitches, sometimes not.
Exactly what the patches are and how to manipulate them is where my Hackintosh comprehension falters.
 
CustoMacMini 2011
GA-H67N-USB3-B3 |  i5 2500K |  HD 3000
BruceLee5000 said:
Should I use "OsxAptioFixDrv-64.efi" if I'm on a Series 6 board? Legacy, not UEFI.
Click to expand...

If you're using legacy, no files required at all in drivers64UEFI.

I downloaded the DSDT from the TonyMacx86 site because I followed the suggested parts precisely.
Click to expand...

Never a good idea to use a patched DSDT from another computer...
Always patch your own...
 
RehabMan said:
If you're using legacy, no files required at all in drivers64UEFI.
Click to expand...

Hmmm... I tried removing the contents of drivers64UEFI and when I restarted Clover couldn't see any Volumes aside from it's own EFI volume. Choosing it to boot only resulted in an error.

I booted from the install USB and the Sierra volume could still boot. I pinned it down to: VBoxHfs-64.efi, if that file is not in drivers64UEFI I don't get volumes in the Clover Bootloader.

There is a drivers64 version of the same file. I tried using that instead of the drivers64UEFI version and it did not present the Volumes. Having both loaded presents the volumes.

I know my logic board and processor are Series 6. i5 2500k, Gigabyte H67MA-USB3-B3. I've been using all the Legacy settings. Not sure what's up.
 
CustoMacMini 2011
GA-H67N-USB3-B3 |  i5 2500K |  HD 3000
BruceLee5000 said:
Hmmm... I tried removing the contents of drivers64UEFI and when I restarted Clover couldn't see any Volumes aside from it's own EFI volume. Choosing it to boot only resulted in an error.
Click to expand...

Clearly what you wrote in post #33 regarding that you were using Clover legacy was inaccurate.
You must be booting UEFI, so the contents of drivers64UEFI are applicable.
 
RehabMan said:
Clearly what you wrote in post #33 regarding that you were using Clover legacy was inaccurate.
You must be booting UEFI, so the contents of drivers64UEFI are applicable.
Click to expand...

Are Gigabyte Series 6 motherboards capable of booting UEFI?

My understanding was that only Series 7/8/9 were UEFI.

I choose LEGACY when setting up with MultiBeast.
 
CustoMacMini 2011
GA-H67N-USB3-B3 |  i5 2500K |  HD 3000
BruceLee5000 said:
Are Gigabyte Series 6 motherboards capable of booting UEFI?
Click to expand...

The evidence *you* provided suggests yes.

My understanding was that only Series 7/8/9 were UEFI.

I choose LEGACY when setting up with MultiBeast.
Click to expand...

Perhaps you are continuing to provide inaccurate information.
You can clearly see legacy vs. UEFI by looking at you Clover bootlog.
 
Searching for "UEFI" produces no results, searching for "Legacy" identifies the boot volumes:
Code: 
5:498  0:000  === [ ScanVolumes ] =======================================
5:498  0:000  Found 8 volumes with blockIO
5:498  0:000  - [00]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)
5:498  0:000          Result of bootcode detection: bootable unknown (legacy)
5:498  0:000  - [01]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)
5:498  0:000          Result of bootcode detection: bootable unknown (legacy)
5:498  0:000  - [02]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0x0,0x0)
5:498  0:000          Found optical drive
5:498  0:000  - [03]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(1,GPT,2490DFAE-4F4C-4EF2-807F-21F9D0D7B676,0x28,0x64000)
5:498  0:000          Result of bootcode detection: bootable Clover (clover)
5:499  0:000          This is SelfVolume !!
5:499  0:000  - [04]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(2,GPT,3E234D6A-D333-48B9-8256-3F0E1A508409,0x64028,0x1774B290)
5:499  0:000          Result of bootcode detection: bootable unknown (legacy)
5:499  0:000  - [05]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(3,GPT,2A0B3094-8DA6-4D08-91EB-B2016FF4F6B0,0x177AF2B8,0x135F20)
5:499  0:000  - [06]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(4,GPT,E68D6627-2B76-45EE-975A-E42A5C076405,0x178E51D8,0x57AA850)
5:499  0:000  - [07]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(5,GPT,322C6783-F36E-4B52-BABA-0542295C259A,0x1D08FA28,0x135F20)
5:499  0:000  === [ InitTheme ] =========================================
 
CustoMacMini 2011
GA-H67N-USB3-B3 |  i5 2500K |  HD 3000
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top