Jump to content

1,003 posts in this topic

Recommended Posts

@Pavo, OpenCore should be able to determine ProcessorType for your if you use automatic PlatformInfo generation or provide 0.

More details can be found here:

https://github.com/acidanthera/OcSupportPkg/blob/master/Library/OcCpuLib/OcCpuLib.c

https://github.com/acidanthera/EfiPkg/blob/master/Include/IndustryStandard/AppleSmBios.h

Share this post


Link to post
Share on other sites
Advertisement
1 hour ago, vit9696 said:

@Pavo, OpenCore should be able to determine ProcessorType for your if you use automatic PlatformInfo generation or provide 0.

More details can be found here:

https://github.com/acidanthera/OcSupportPkg/blob/master/Library/OcCpuLib/OcCpuLib.c

https://github.com/acidanthera/EfiPkg/blob/master/Include/IndustryStandard/AppleSmBios.h

We tried and that didnt work 

Share this post


Link to post
Share on other sites
1 hour ago, vit9696 said:

@Pavo, OpenCore should be able to determine ProcessorType for your if you use automatic PlatformInfo generation or provide 0.

More details can be found here:

https://github.com/acidanthera/OcSupportPkg/blob/master/Library/OcCpuLib/OcCpuLib.c

https://github.com/acidanthera/EfiPkg/blob/master/Include/IndustryStandard/AppleSmBios.h

I thought it would have been able to also, but as WarDoc said, we tried 0 and it didn't work. I had to convert the hex 0a0a to decimal 2750 into order to get it to work.

Share this post


Link to post
Share on other sites
8 minutes ago, vit9696 said:

Well, if you provide CPUID dumps, SMBIOS dumps with automatic detection, and OpenCore logs in acidanthera bugtracker, we may be able to improve the situation.

Yeah I am trying to figure out how to dump OpenCore logs as we speak, I am trying to send them to DataHub but no output from the command line after. If you can give me instructions on providing all those dumps and logs I will send them right over.

Share this post


Link to post
Share on other sites

Also to add if we use 0x40 in the Target it converts to 64 under xcode, but theres nothing in the PDF to state if this is correct. for File Logging.

and this is what its doing under ProcessorType.

Share this post


Link to post
Share on other sites
8 minutes ago, MacFriedIntel said:

Also to add if we use 0x40 in the Target it converts to 64 under xcode, but theres nothing in the PDF to state if this is correct. for File Logging.

and this is what its doing under ProcessorType.

Also add masks 0x01 and 0x02.

Share this post


Link to post
Share on other sites
41 minutes ago, vit9696 said:

Well, if you provide CPUID dumps, SMBIOS dumps with automatic detection, and OpenCore logs in acidanthera bugtracker, we may be able to improve the situation.

Added to bugtracker

Share this post


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

Also to add if we use 0x40 in the Target it converts to 64 under xcode, but theres nothing in the PDF to state if this is correct. for File Logging.

and this is what its doing under ProcessorType.

 

 0x01 — Enable logging, otherwise all log is discarded.

 0x02 — Enable basic console (onscreen) logging.
 0x04 — Enable logging to Data Hub.
 0x08 — Enable serial port logging.

 0x10 — Enable UEFI variable logging.
 0x20 — Enable non-volatile UEFI variable logging.

 0x40 — Enable logging to file.  

 

You need to use DEBUG or NOOPT OC version.

target = 0x45 equal decimal 69 (Xcode view)

it means you will be able to get  OpenCore.log in ESP /  and Data Hub log with this cmd

ioreg -lw0 -p IODeviceTree | grep boot-log | sort | sed 's/.*<\(.*\)>.*/\1/' | xxd -r -p

 

For processor type I see some thing just like 1,541 no it's 1541 = 0x605 = core i5 ( 6*256 + 0*16 + 1*5)

All value are give in hexadecimal take a look at code value in cpu.c. take a look here

https://sourceforge.net/p/cloverefiboot/code/HEAD/tree/rEFIt_UEFI/Platform/cpu.c#l1370

you will find all processor value used in clover.

 

 

Fred

Edited by FredWst

Share this post


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

That is a good list but I am assuming the intent for that list is for CPUs that Apple actually uses. Where some users like myself would like to add CPUs that aren't listed natively from Apple but are within the same family type. Example would be my Xeon E5-2670v2 CPUs which are Ivy Bridge-EP, they are of type 0x0a0a where as the list you linked only supports Xeon of type 0x0501 and Xeon E5 of type 0x0a01.

Share this post


Link to post
Share on other sites
Posted (edited)
4 minutes ago, Pavo said:

That is a good list but I am assuming the intent for that list is for CPUs that Apple actually uses. Where some users like myself would like to add CPUs that aren't listed natively from Apple but are within the same family type. Example would be my Xeon E5-2670v2 CPUs which are Ivy Bridge-EP, they are of type 0x0a0a where as the list you linked only supports Xeon of type 0x0501 and Xeon E5 of type 0x0a01.

A reasonable list would be ark.intel.com, which is multilingual simultaneously. :D

Look the platform up there, and find the appropriate type on my table. That's it. It looks like a switch from Intel-based type to Apple-based type to me.

 

EDIT: What we really want is to make the process automatic instead of helping users find the correct type...

Edited by PMheart

Share this post


Link to post
Share on other sites
13 minutes ago, PMheart said:

A reasonable list would be ark.intel.com, which is multilingual simultaneously. :D

Look the platform up there, and find the appropriate type on my table. That's it. It looks like a switch from Intel-based type to Apple-based type to me.

Ok.... If I go off the list in your table then my cpu-type should be 0x0A01 since my CPU falls in the AppleProcessorTypeXeonE5 platform. If I set my cpu-type to 2561 which is the decimal conversion of 0x0A01 in OC config, System Profiler shows Unknown as CPU name. If I use OC auto detection it detects my cpu-type as AppleProcessorTypeXeon and again System Profiler says Unknown as CPU name. But if I use 2570 decimal conversion of 0x0A0A which is XeonE5Type2 platform which your list doesn't have System Profiler shows 10-Core Intel Xeon E5 as CPU name which is correct. 

Share this post


Link to post
Share on other sites
Posted (edited)

Hi all of you dev guys my request is can any of you explain how to use Duet Pkg with OC bootLoader for Legacy booting 

i have created USB thumb drive with OC bootloader but i don't know where to place  the Duet Pkg

Edited by Rockey12

Share this post


Link to post
Share on other sites
10 hours ago, Rockey12 said:

Hi all of you dev guys my request is can any of you explain how to use Duet Pkg with OC bootLoader for Legacy booting 

i have created USB thumb drive with OC bootloader but i don't know where to place  the Duet Pkg

 

+1

 

Also, an installer or a helper app (for legacy installation) would be very helpful. Even for advanced users.

Share this post


Link to post
Share on other sites
21 hours ago, Rockey12 said:

Hi all of you dev guys my request is can any of you explain how to use Duet Pkg with OC bootLoader for Legacy booting 

i have created USB thumb drive with OC bootloader but i don't know where to place  the Duet Pkg

Duet from Duet Pkg will not work, it requires a lot of fixes

Use boot6 from Clover distribution

Share this post


Link to post
Share on other sites

to install

sudo fdisk -f boot0af -u -y /dev/rdiskX;
sudo boot1-install -f boot1f32 /dev/rdiskXs1;

all files are from Clover

for MBR flash drive make it active

sudo fdisk -e /dev/rdiskX
p
f 1
w
y
q

then copy boot6 to drive root folder: boot

Share this post


Link to post
Share on other sites
On 5/12/2019 at 9:42 PM, Pavo said:

We should probably compile a list of CPU Types for people.

<key>ProcessorType</key>
            <integer>3841</integer>

Corresponds to Hex 0x0F01

 

"Intel Xeon W"

Share this post


Link to post
Share on other sites

Resolution is no longer working for me and logo on boot screen disappears since updating this morning and the log is displaying 00:002 00:002 OC: Changed resolution to 0x0@0 (max: 1) from Max - Unsupported

Share this post


Link to post
Share on other sites
Posted (edited)
48 minutes ago, MacFriedIntel said:

Resolution is no longer working for me and logo on boot screen disappears since updating this morning and the log is displaying 00:002 00:002 OC: Changed resolution to 0x0@0 (max: 1) from Max - Unsupported

In my case it is working as before 

I have followed your previous instruction posted some messages ago

 

Edited by fabiosun

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

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Slice
      OK, 4988 released.
      Now, @vector sigma, what have we do to update translations?
    • By dracoflar
      So you've been reading the forum on this brand new boot loader called OpenCore hoping to try it out but you take one look at the configurations PDF and take a step back in shock at the complexity! Well if you've been feeling a bit intimidated by the DOCS well you've come to the right place:
       
      OpenCore Vanilla Desktop Guide
       
      If you have any issues or suggestions please feel free to comment
       
      - Your local neighbourhood Hackintosh Slav
    • By vit9696
      OpenCorePkg / Documentation / Configuration Template / Bugtracker   Discussion and installation should be done in a separate thread! This thread is for development only!
      Current status as of April 2019: Support for UEFI and DuetPkg (legacy) booting APFS and HFS+ compatibility ACPI patcher (adding, dropping, binary patching, relocation) Apple-compatible bless implementation DeviceProperties injection DataHub and SMBIOS generation Symbolic kext and kernel patcher Direct kext injection/patching/blocking within prelinkedkernel Installation/Recovery/FileVault 2 support  Configuration in config.plist with open documentation Simple boot picker for quick launch Direct boot from dmg images  
      Known defects live here.  
      For those, who are not familiar with the history, OpenCore is a project initially born in HermitCrabs Lab that unfortunately almost died before its birth. This release is both a rebirth and a complete rewrite of OpenCore, which brings a number of new ideas, and tries to preserve the smart moves incorporated by iNDi and his team. Other than that, I wish to express my deepest words of gratitude to Acidanthera and WWHC members: your participation was and remains the key for project success, and you are simply the best.
×