Jump to content

2,198 posts in this topic

Recommended Posts

17 hours ago, Sniki said:

Hi @vit9696

It's a Haswell laptop not ivy bridge.

Intel Core i5 4300U

Hmm, I rechecked your panic screen, and to be honest it does not even look like a CFG Lock (or any MSR stuff), more like dereferencing null pointer. Perhaps you should consider looking somewhere else.

 

16 hours ago, STLVNUB said:

I think the idea is to bless bootx64.efi then it loads by itself

 

Correct, and you use a separate GUID space with FwRuntimeServices.efi to avoid other options getting into your way of running.

Share this post


Link to post
Share on other sites
Advertisement

Sorry @PMheart , but I think this fragment has to be corrected:

 

call in XNU kernel. Normally it is only the value of \texttt{EAX} that needs to be taken care of,
which represents the exact CPUID. And the remainders are to be left as zeroes.
For instance, \texttt{A9 06 03 00} stands for CPUID \texttt{0x0306A9} (Ivy Bridge).
A good example can be found at
\href{https://github.com/acidanthera/bugtracker/issues/365}{acidanthera/bugtracker\#365}.

(See \texttt{Special NOTES for Haswell+ low-end})

 

I used to boot my Intel Pentium Haswell with fake CPUID Ivy Bridge 0x0306A0

Share this post


Link to post
Share on other sites
33 minutes ago, hardcorehenry said:

Sorry @PMheart , but I think this fragment has to be corrected:

  

call in XNU kernel. Normally it is only the value of \texttt{EAX} that needs to be taken care of,
 which represents the exact CPUID. And the remainders are to be left as zeroes.
For instance, \texttt{A9 06 03 00} stands for CPUID \texttt{0x0306A9} (Ivy Bridge).
A good example can be found at
\href{https://github.com/acidanthera/bugtracker/issues/365}{acidanthera/bugtracker\#365}.

(See \texttt{Special NOTES for Haswell+ low-end})

  

I used to boot my Intel Pentium Haswell with fake CPUID Ivy Bridge 0x0306A0

Hello,

 

Sorry, I didn't quite catch that. Could you please point out the changes that I am supposed to handle? Thanks!

Share this post


Link to post
Share on other sites
Posted (edited)

"For instance, \texttt{A0 06 03 00} stands for CPUID \texttt{0x0306A0} (Ivy Bridge)" , thou I'm not using fake CPUID in favor of cpu family kernel patch(VDA decoding:)), it was the only fake CPUID I was able to boot my hackintosh:)

Edited by hardcorehenry

Share this post


Link to post
Share on other sites
Posted (edited)
2 hours ago, vit9696 said:

does not even look like a CFG Lock (or any MSR stuff), more like dereferencing null pointer. Perhaps you should consider looking somewhere else.

Thanks @vit9696

Do you have any suggestions/hint on where the problem could be ?

I checked configuration.pdf many times but can't find any reference related to this problem

 

Any idea ?

I had the OC folder attached as well,

Let me know if you need more files/logs for troubleshooting.

Edited by Sniki

Share this post


Link to post
Share on other sites
Posted (edited)
5 hours ago, tunglamvghy1210 said:

I've the same issue but it stop booting. Have you fix it yet?

Yes it seems the problem was Rehabman version of voodoops2. Now i'm using Acidanthera version and the error is gone :

https://github.com/acidanthera/VoodooPS2

 

Mattia

Edited by tmbt
writing error

Share this post


Link to post
Share on other sites
5 minutes ago, bronxteck said:

I did not try re enabling sip as. it does not bother me being disabled

 

I ran SIP disabled for 3 years, and decided to enable it when I moved to OC. The only difference has been theoretical :)

Share this post


Link to post
Share on other sites

Would anyone know the decimal number to use to in Scan Policy to enable USB scanning but not show EFI please? 

 

I currently have it set at 0 which works but also shows EFI, I also tried 5,177,603 but that didn't show any more and also gave an error before the boot selector screen.

Share this post


Link to post
Share on other sites
Posted (edited)
11 hours ago, STLVNUB said:

Can you please share your OC, mine does nothing

all i did was use opencore configurator made a new config disabled anything that was default in all option menus.

 

in smbios i just populated the generic section with the info i needed changed like serial and had to put a mac identifier if not OC defaults to mac pro 6,1 i selected all the check mark options across the bottom  and set auto to auto instead of create. the other thing it needed was applepolicy checked like i explained in my previous post. i am not using any drivers or kexts just config with the smbios info i want changed deleted everything else oh and i set the gui text mode stuff for the bootpicker

Edited by bronxteck

Share this post


Link to post
Share on other sites
2 hours ago, D-an-W said:

Would anyone know the decimal number to use to in Scan Policy to enable USB scanning but not show EFI please? 

 

I currently have it set at 0 which works but also shows EFI, I also tried 5,177,603 but that didn't show any more and also gave an error before the boot selector screen.

 

Try 3080451

(default + USB)

Or 2818307

(default + USB - SCSI) Do people still use SCSI? (Really?) :)

Share this post


Link to post
Share on other sites
Posted (edited)
1 hour ago, bronxteck said:

all i did was use opencore configurator made a new config disabled anything that was default in all option menus.

 

in smbios i just populated the generic section with the info i needed changed like serial and had to put a mac identifier if not OC defaults to mac pro 6,1 i selected all the check mark options across the bottom  and set auto to auto instead of create. the other thing it needed was applepolicy checked like i explained in my previous post. i am not using any drivers or kexts just config with the smbios info i want changed deleted everything else oh and i set the gui text mode stuff for the bootpicker

Ok, I used DEBUG version, maybe that exasperated the problem

THANKS

 

edit:

I'm a lazy SOAB, could you please give me your OC without serial etc.

Edited by STLVNUB

Share this post


Link to post
Share on other sites

when I get home I guess.

that's funny because the only thing my config is being used for is the serial number LOL. my SMC was replaced and it came with no serial. that's the reason I attempted to try OC on the iMac. apple serializer is too old to run on my machine to fix the issue and I already closed the machine so can't dump then edit and re upload the rom. unless serializer can be modified to run on new systems.

Share this post


Link to post
Share on other sites
Posted (edited)
1 hour ago, bronxteck said:

when I get home I guess.

that's funny because the only thing my config is being used for is the serial number LOL. my SMC was replaced and it came with no serial. that's the reason I attempted to try OC on the iMac. apple serializer is too old to run on my machine to fix the issue and I already closed the machine so can't dump then edit and re upload the rom. unless serializer can be modified to run on new systems.

All good, sorted it out myself, thanks for your help

 

edit:

still no go, what you using it on.

Stick with Clover for time being.

Edited by STLVNUB

Share this post


Link to post
Share on other sites
2 hours ago, canyondust said:

 

Try 3080451

(default + USB)

Or 2818307

(default + USB - SCSI) Do people still use SCSI? (Really?) :)

 

Neither works, just gives an error "OCS: Failed to parse real field of type 1" on the screen before the boot picker and no additional entries.

 

Will stick to 0 for now.

Share this post


Link to post
Share on other sites
3 hours ago, bronxteck said:

all i did was use opencore configurator made a new config disabled anything that was default in all option menus.

 

in smbios i just populated the generic section with the info i needed changed like serial and had to put a mac identifier if not OC defaults to mac pro 6,1 i selected all the check mark options across the bottom  and set auto to auto instead of create. the other thing it needed was applepolicy checked like i explained in my previous post. i am not using any drivers or kexts just config with the smbios info i want changed deleted everything else oh and i set the gui text mode stuff for the bootpicker

You should not be using any OpenCore configurator right now, none of them work properly for creating a proper config. Plain and simple.

Share this post


Link to post
Share on other sites
1 minute ago, Pavo said:

You should not be using any OpenCore configurator right now, none of them work properly for creating a proper config. Plain and simple.

Did you read it???

We using it on Apple, no real need for ANY config

Share this post


Link to post
Share on other sites
2 hours ago, D-an-W said:

 

Neither works, just gives an error "OCS: Failed to parse real field of type 1" on the screen before the boot picker and no additional entries.

 

Will stick to 0 for now.

Interesting. I used the old pdf. I’ll double check that the bitmap hasn’t changed.

Share this post


Link to post
Share on other sites
Posted (edited)
3 hours ago, D-an-W said:

 

Neither works, just gives an error "OCS: Failed to parse real field of type 1" on the screen before the boot picker and no additional entries.

 

Will stick to 0 for now.

Try 3080963 (default + usb + hfs)

 

EDIT: Or 2687750 (Scan FS Lock, Scan Device Lock, Allow APFS, Allow HFS, Allow Sata, Allow NMVE, Allow USB)

Edited by canyondust

Share this post


Link to post
Share on other sites
14 hours ago, hardcorehenry said:

"For instance, \texttt{A0 06 03 00} stands for CPUID \texttt{0x0306A0} (Ivy Bridge)" , thou I'm not using fake CPUID in favor of cpu family kernel patch(VDA decoding:)), it was the only fake CPUID I was able to boot my hackintosh:)

Sorry for my stupidness. I still didn't get it. Might you want to make this patch a quirk or?

Share this post


Link to post
Share on other sites
1 hour ago, Download-Fritz said:

@D-an-W as the error says, you end up having a *real* field, so remove punctuation

 

Good morning @Download-Fritz I assume that means the commas I put in there to make it look the same as before I changed it?  For example I entered 5,177,603 and should have maybe just typed 5177603?

Share this post


Link to post
Share on other sites
6 hours ago, PMheart said:

Sorry for my stupidness. I still didn't get it. Might you want to make this patch a quirk or?

Sorry for not being precise, I meant there's probably misprint Ivy Bridge is 0x0306A0 not 0x0306A9. Sorry for the confusion I made.

Share this post


Link to post
Share on other sites
7 hours ago, canyondust said:

Try 3080963 (default + usb + hfs)

 

EDIT: Or 2687750 (Scan FS Lock, Scan Device Lock, Allow APFS, Allow HFS, Allow Sata, Allow NMVE, Allow USB)

 

BINGO!

 

3080963 did the trick along with the tip from @Download-Fritz as I was wrongly add the commas but should just have let Xcode do that for me.

 

Many thanks @canyondust & @Download-Fritz :thumbsup_anim:

Share this post


Link to post
Share on other sites
Posted (edited)
On 8/27/2019 at 4:36 PM, STLVNUB said:

All good, sorted it out myself, thanks for your help

 

edit:

still no go, what you using it on.

Stick with Clover for time being.

ok here it goes

EFI.zip

 

looks like you have to re bless OC after apple updates. 

sudo bless --device /dev/disk0s1 --file BOOTx64.efi --setBoot

 

Edited by bronxteck

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By notiflux
      Unfortunately, this project has come to a halt, at least for now. I don't have enough time to work on the project and it's lacking behind, so please don't use it for configuring OpenCore, it will produce broken configuration files.
      I will leave the source code on GitHub, so in case someone wants to take over the project, they can.
       
      original post:
      OpenCore Configurator Source
    • By clockT
      sono un pò arrugginito ..e volevo chiedere un aiuto su come installare opencore anzichè clover. ho provato ma dopo il post installazione riesco solo a far partire catalina tramite pendrive. quale congifurazione sbaglio?
      EFI.zip

    • By MaLd0n
      ---TUTORIAL---

      https://olarila.com/forum/viewtopic.php?f=50&t=8685
       
      --Original Post--
       
      https://olarila.com/forum/viewtopic.php?f=97&t=11237
       
      --Bios/UEFI Settings--
       
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
       
      Extreme Memory Profile (X.M.P.) - Profile 1
       
      2- Go to BIOS tab
       
      CSM Support - Disabled
       
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
       
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
       
      4- Go to Chipset tab
       
      Internal Graphics - Enable
       
      ---CLOVER FOLDER---
      https://olarila.com/files/Clover.Folder/EFI CLOVER Z390 DESIGNARE.zip
      *Use this folder with FULL DSDT PATCHED
       
      ---OPENCORE FOLDER---
      https://olarila.com/forum/download/file.php?id=24376
      *Use this folder with FULL DSDT PATCHED
       
       
      ---Extract one Full dump for DSDT edits, post files---
       
      RunMe.app
       
       
       
      ---HARDWARE---
       
      --MOBO

      GIGABYTE Z390 DESIGNARE
      -Link
      https://www.amazon.com/Z390-DESIGNARE-Gigabyte-Thunderbolt-Motherboard/dp/B07K8RJZRG/ref=sr_1_1?keywords=Z390+DESIGNARE&qid=1565492390&s=electronics&sr=1-1

      --PROCESSOR

      Intel Core i9-9900K
      -Link
      https://www.amazon.com/Intel-i9-9900K-Desktop-Processor-Unlocked/dp/B005404P9I/ref=sr_1_1_sspa?keywords=Intel+Core+i9-9900K&qid=1553358099&s=gateway&sr=8-1-spons&psc=1

      --COOLER

      CORSAIR H100i RGB PLATINUM AIO Liquid CPU Cooler
      -Link
      https://www.amazon.com/CORSAIR-H100i-PLATINUM-Liquid-Cooler/dp/B07JWB5BSN/ref=sr_1_4?keywords=WATER+COOLER+CPU&qid=1565492509&s=gateway&sr=8-4

      --MEMORY

      Corsair CMW32GX4M2C3200C16 Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600)
      -Link
      https://www.amazon.com/Corsair-CMW32GX4M2C3200C16-Vengeance-PC4-25600-Desktop/dp/B07GTG2T7L/ref=sr_1_15?keywords=memory+ddr4+32&qid=1553358238&s=gateway&sr=8-15

      --GPU

      MSI RX Vega 64 AIR Boost 8G OC
      -Link
      https://www.amazon.com/MSI-RX-64-AIR-8G/dp/B07DH7S1X1/ref=sr_1_2?keywords=vega+64+gigabyte&qid=1565492819&s=electronics&sr=1-2

      --SSD

      Samsung 970 EVO 1TB SSD (MZ-V7E1T0BW) NVMe M.2 V-NAND
      -Link
      https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=s+samsung+970+evo+1tb&qid=1565493002&s=electronics&sr=1-1

      --POWER SUPPLY

      EVGA Supernova 1000 P2 80+ Platinum, 1000W ECO Mode Fully Modular 
      -Link
      https://www.amazon.com/EVGA-Supernova-Platinum-Crossfire-220-P2-1000-XR/dp/B00EKJQM5E/ref=sr_1_3?keywords=power+supply+1000w&qid=1565493196&s=gateway&sr=8-3

      --WIRELESS

      TP-Link Archer T9E
      -Link
      https://www.amazon.com/TP-Link-Archer-T9E-Beamforming-Technology/dp/B00TQEX7AQ/ref=sr_1_1?keywords=TP-Link+Archer+T9E&qid=1553358397&s=gateway&sr=8-1

      --CASE

      Thermaltake Core P5 Tempered Glass Black Edition ATX Open Frame Panoramic Viewing
      -Link
      https://www.amazon.com/Thermaltake-Tempered-Panoramic-Certified-CA-1E7-00M1WN-03/dp/B01N4IGVSC/ref=sr_1_2?keywords=Thermaltake+Core+P5&qid=1565493567&s=gateway&sr=8-2

      --DSDT Patches--
      -FIX ACPI ERRORS -FIX OEM SSDTs to AVOID ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA -DMAC -REMOVE PROBLEMATIC AND UNUSED DEVICES -FIX K.P in REBOOT -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -FWHD -USBX -PMCR -PPMC -XSPI -CNVW -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES ---SCREENSHOTs---




















      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By rusty-bits
      Command line tool that will build a working EFI folder based on the settings in the config.plist file.
      https://github.com/rusty-bits/OC-tool
       
       
      you can also copy your config.plist to the RELEASE folder and double-click OC-tool  
      this is the same as running
      ./OC-tool -uo build release from the command line  
       
      see the wiki for more info  
       
      https://github.com/rusty-bits/OC-tool/wiki
       
      added functionality to the -T option  (update ver 1.6pt)  

      TUI (Text based User Interface) now has limited functionality  
      kexts, drivers, tools and quirks can be toggled on or off, then by pressing g an EFI folder will be created based on what you set  
       
       
      working:  
      - BOOT/BOOTx64.efi built automatically  
      - OC/OpenCore.efi build automatically
      - OC/ACPI folder built automatically from settings in ACPI/Add section of config.plist  
      - - the tool can compile .dsl to .aml on the fly if iasl is present, but I recommend compiling them to .aml yourself for the tool to move over  
      - OC/Drivers folder built automatically from settings in UEFI/Drivers section of config.plist  
      - OC/kexts folder built automatically from settings in Kernel/Add section of config.plist  
      - OC/Tools/Shell.efi built automatically from setings in Misc/Tools section of config.plist  
      - OC/vault.plist and OC/vault.sig are built automatically from the Misc/Security/RequireVault setting in config.plist  
      - can specify debug or release version of resources to be built  
      - parses plist files internally, no longer needs to call /usr/libexec/PlistBuddy which may not exist on Catalina  
      - kexts, drivers, tools and quirks can be enabled or disabled before building the EFI by using the -T option  
       
×