Jump to content
glasgood

Populating System Information - PCI via config.plist using Hackintool

39 posts in this topic

Recommended Posts

Posted (edited)

 

 

    Populating System Information - PCI via config.plist using Hackintool

 

 

 

1560262886_Screenshot2019-04-24at14_27_42.png.a71899abf4f2d69101c8bb7e94f68d96.png

 

 

CREDITS

 

Hackintool @headkaze

Clover Configurator Mackie100

LSPCI

 

 

 

 

A quick guide on how to add device information into System Information - PCI with config.plist and Hackintool using Clover Configurator.  

 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

 

 

 

 

DOWNLOAD

 

 

 

 

 

DOWNLOAD SAMPLE FILES

 

 

 

 

 

SYSTEM INFORMATION - PCI

 

To my knowledge, there are a few different ways to populate the System Information PCI with device information:

 

Those are:

 

  • DSDT 
  • SSDT
  • Devices Arbitrary  ( config.plist )
  • Devices Properties ( config.plist )
  • Devices Arbitrary & Properties ( config.plist )

 

Initially,  my approach at populating System Information PCI was to add devices to Arbitrary & Properties. That approach required using other tools, some such as lspci or IOREgistryExplorer to obtain device addresses and paths, so involved some work. 

 

Then :)

 

On the 23/04/2019 @headkaze released Hackintool v2.3.4 

 

Hackintool now exports a file named pcidevices.plist, that file contains all the information needed to populate System Information PCI

 

The easy, better method used to populate System Information PCI is by using Hackintool, see DEVICES - PROPERTIES - HACKINTOOL.

 

I have documented inside DEVICES - ARBITRARY and DEVICES - PROPERTIES information on how to populate System Information PCI without using Hackintool for the sake of knowing other methods. 


 

 

 

 

DEVICES - ARBITRARY

 

Spoiler

 

 

Devices-Arbitrary.thumb.png.3eccf2861bbbb1594b08937d3f673e5a.png

 

 

 

Devices -> Arbitrary is mostly cosmetic for PCI content in System Information ( but not always cosmetic ). So Arbitrary not really necessary, but I feel it is nice to include.  When populating Arbitrary with a correct Pci Address for a device, the System Information will report Driver Installed and output other info such as Vendor ID and Device ID. 

 

 

2096059287_Screenshot2019-04-20at14_18_12.png.5eeab77b3bcf053ca9f90914cea8e9e7.png

 

 

 

 

Arbitrary information contained inside a DSDT _DSM Method ( No DSDT patching required, this guide is using Arbitrary & Properties, image below for sake of comparison  )

 

DSM.png.40713a4790e7ab62e32dd5ca73ea17c7.png

 

 

In above _DSM method, similar information is seen below in Arbitrary inside config.plist with Clover Configurator.

 

 

 

 

2098990687_Screenshot2019-04-20at09_15_02.png.d0fafddcd118fd90933db99015c27694.png

 

In the image above my Hackintosh Aorus Z390 Pro has a Broadcom BCM4331 Wireless Adapter at PciAddr* 04:00.0 

 

To add a different Wireless Adapter or other device, you first need to determine the Pci Address using using lspci.zip 

 

lspci.png.0950a82deed7388ffcf59f9496721822.png

 

See screenshot above: lspci -nn command output  listing PCI devices, notice PciAddr* 04:00.0 is for BCM4331

 

 

 

Next, you would then replace the PciAddr* 04:00.0  with PciAddr*  attached to your Wireless Adapter .

Then replace STRING value type --> "Broadcom BCM4331 Wireless Network Adapter" to match name of your replacement Wireless Adapter, in theory that String value type ( model ) name can be anything.

 

1425857277_Screenshot2019-04-20at09_27_17.png.61cdd450afad33d8b5d4237f47112c05.png

 

You don't need to add Key* device_type because it is automatically populated in System Information - PCI, but you can include the additional Key* device_type and explicitly name the device_type if you are not happy with the default device_type name.

 

Arbitrary-device_type.png.9a8ab7981839e1aaf5c665eed1ac0e70.png

 

 

By including device_type, you can then override the default device_type name "Other Network Controller" inside System Information - PCI ( images below ) and rename it to something more appropriate such as Airport Extreme. 

 

SysInfo1.png.e6d25b6ef47644d9f406bc0e8f0620a1.png

 

Below, you can now see device_type changed to AirPort Extreme in System Information PCI

 

Sys-Info-PCI.png.ae8550d21c4fc4fd34f8e94a11062ccb.png

 

Also in above screenshot, the same has also been done to rename "Other Communications Device" to IMEI Controller.

 

 

To add any other new device in Arbitrary, click + button and provide the following:

 

  • PCiAddress (enter comment )

 

Arbitrary, click + button and add CustomProperties

 

  • model   ( Value, Device name, Value Type STRING or DATA )
  • AAPL,slot-name ( Value, Built-in or PCI Slot X , Value Type STRING or DATA)

 

And optionally you can include

  • device_type 

 

 

Arbitrary-config-plist.png.5970be1b8b37fba0dce5c5502a9a1a87.png

 

 

 

DEVICES - PROPERTIES

 

Spoiler

 

Sometimes adding devices to Arbitrary can cause problems ( I did mention it was not always cosmetic :D). As an example, I originally placed the Realtek ALC1120 device in Arbitrary and upon reboot the device was seen in PCI information but my sound became disabled. 

So the workaround solution was to enter that information in Properties as seen below. 

 

2064643850_Screenshot2019-04-19at19_48_04.png.5d08807b30775e8ec5a213622fc8c42d.png

  

Properties tab is different, it is a mixture of cosmetic and functional properties. The STRING value type is cosmetic, so that Intel UHD 630 is seen in System Information PCI view.  The DATA value type fixes Frame-buffer, HDMI audio and is functional.

 

Properties-Clover.png.4b9ebc4d022052cce7c2c2a598d85c34.png

 

 

 

 

 

 

 

 

DEVICES - PROPERTIES - HACKINTOOL

 

 

  • Run Hackintool, PCI tab and Update PCIIDs

 

01.thumb.png.8dc1c4748809c2c092ffd5d0830dbd81.png

 

 

  • Export PCI info

 

2.thumb.png.a28dcf0dabaf6db5dd1e15736fef4f76.png

 

 

 

HOW TO SAVE pcidevices.plist Properties TO CONFIG.PLIST

 

 

Download and install

 

 

  • Right click and open pcidevices.plist with PlistEdit Pro

 

00.png.48b3e227e241ecb733becefbf8b32943.png

 

 

  • Mount EFI partition and drag and drop config.plist onto desktop. Right click, open with PlistEdit Pro

 

1114351010_Screenshot2019-04-27at09_29_15.thumb.png.faa19940b58697523200b35ae6e6471f.png

 

 

  • Place both PlistEdit Pro windows side by side:

 

001.thumb.png.c7c2c7fc6b0039a1626584e6c5f57732.png

 

 

  • Next, click Properties, copy. (pcidevices.plist)

 

01.png.1d5d66148a61b628860982d09948c1b7.png

 

 

  • Then, click on Devices (config.plist) so that it is highlighted and Paste As Child and Save.  

02.thumb.png.90212b38a21f234294e071f0a163a82d.png

 

 

 

  • Verify Properties has been added correctly to Devices inside config.plist using Clover Configurator or PlistEdit Pro

 

CC.thumb.png.58b456aca7aa4c5ff371bd0c171a9ca2.png

 

Plist.thumb.png.b64ad2c5efa68b6505f6cb617277a1cf.png

 

 

  • Place config.plist back inside EFI/Clover

 

879154391_Screenshot2019-04-27at09_53_43.png.3a52b596fab4b9594b09d13d24bb4e56.png

 

 

  • Done!

 

 

 

 

 

Optionally you can make edits to Devices model string information, so "Cannon Lake PCH cVAs" in my config.plist has been renamed to " Realtek ALC1120-VB " 

 

 

Open pcidevices.plist with Clover Configurator.

 

03.png.7e4c45946220e6442a33cf08f75be155.png

 

 

4.thumb.png.2ef27b49004432bad92b502e9249b6c2.png

399190143_Screenshot2019-04-24at11_17_12.thumb.png.4a67c8009ffbb6bc772a81343d5bea53.png

 

 

 

Example of optional renames done with config.plist for Aorus Z390 Pro

 

Before:

 

Before.png.75e175949439b093b0e71b3030219694.png

 

 

After:

 

 

1560262886_Screenshot2019-04-24at14_27_42.png.a71899abf4f2d69101c8bb7e94f68d96.png

 

 

Save renames and then add Devices / Properties to your config.plist.

 

 

No need to rename device_type Bridge model name. 

 

Bridge.png.9a3a700819ae78fd245c3939375d02c7.png

924258719_Bridge2.png.f9df3c0a0b66577f0c6301ce9c17138c.png

 

 

 

THANKS TO @headkaze  & @Hervé

 

AND ALSO @steve3d for his post!

 

config.plist

Edited by glasgood
info about saving Properties to config.plist

Share this post


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

Good tuto...

 

Property injection is probably far better than Arbitrary since you have next to zero risk of targeting the wrong IOReg address.

Re: DSDT/SSDT patches, you forgot to specify this is done through a _DSM method. Not a trivial detail....

To identify devices in IOreg, IORegistryExplorer is a kinda de-facto standard by far and large. But there are several other tools such as good old DPCIManager. IOJones may even still work too.

 

 

Hi Hervé,

 

I was unaware of IOJones thanks, it's very similar to IORegistry. Is there a way to identify PciAddr* as  04:00.0 but not 4:0:0 when using IORegistryExplorer?

Was using lspci as it provides the  PciAddr* that can be directly used in Arbitrary.  Updated and mentioned  _DSM method in guide.

 

IOReg.thumb.png.40611d6c38b787f41b1a27a53f78306f.png

 

 

 

 

 

Edited by glasgood

Share this post


Link to post
Share on other sites
Posted (edited)
15 hours ago, Hervé said:

With IORegistryExplorer, you need to look at the pci-debug info for the parent device. Values are in decimal. But lspci command will also list each add-on hardware component's own pci-debug info under their own PCI bridge. Usually, built-in components are directly under PCIe root bridge/point 0 and register as such. Add-on cards/components usually a attach to separate PCIe points, hence what may be (erroneously) considered as discrepancies...

 

This is why you would see a wireless card listed in lspci info as attached to 02:00.0 for instance. This would simply be because that would be the 1st device @0 under PCIe point #2 which could be located at anything like, say, XX,YY.

 

Eg:

  • my DW1820 wireless card registers attached to PCIe point 02:00.0 in lspci info and, in IOReg, attached to RP03@1C,2 (which shows pci-debug=0:28:2(2:2)) -> PXSX@0
  • my RTS525a SD card reader registers attached to PCIe point 01:00.0 in lspci info and, in IOReg, attached to RP01@1C (which shows pci-debug=0:28:0(1:1)) -> PXSX@0

 

Got me thinking about this :) hence my late reply,  i'm clear on something's but not on other's. 

 

 

1050015875_Screenshot2019-04-21at09_48_37.thumb.png.f8d8791c1137e397f49fdd611879a884.png

 

 

So 1C,7 in above image is the Bridge to PXSX@0. I'm trying to figure out 4:0:0 

 

// Update

 

I see this now :)

 

PCI-.png.92bf7421594eaea7ce3cd461e0904115.png

 

PCI-1.thumb.png.45667c31029f70cb075ac176528bdcc4.png

 

 

PCI-3.thumb.png.86eb290682b22a97deb5360e555a0460.png

 

 

Thanks.

 

 

 

 

 

 

Edited by glasgood

Share this post


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

Simple... 1st of all PCIe bridge numbering and IOReg addresses all start at 0, not 1.

 

Now, looking at your IOReg info, we can see the following:

  • PCI0 is PCIe root bridge @00:00.0. Since it's the root bridge, it appears as bridge #0.
  • GIGE@1F,6 is directly under PCIe root bridge PCI0, itself a@00:00.0 on the PCIe bus; as such, LAN device shows on the PCIe bridge @00:31:6 (31=1F in hex). 
  • RP08@1C,7 is a PCIe bridge @00:28.7 (28=1C in hex) on the PCIe bus; but since it's a PCIe bridge it is listed as such and appears as bridge #4. Hence the notation 4:4 next to its actual IOReg address.
  • RP08.PXSX@0 is directly under that PCIe bridge #4. IN IOReg, it will register @1C,7 (0x001C0007 exactly) but in PCIe notation, it'll appear as 04:00.0 because it's the 1st device @0 under that PCIe bridge.
  • PEG0@1 is a PCIe bridge @00:01.00 on the PCIe bus. Since it's a PCIe bridge, it is listed as such and appears as bridge #1. Hence the notation 1:1 next to its actual IOReg address.
  • PEG0.GFX0@0 is directly under that PCIe bridge #1. In IOreg, it will register @1 (@0x00010000 exactly) but in the PCIe notation, it'll appear as 01:00.0 because it's the 1st device @0 under that PCIe bridge #4.
  • PEG0.HDAU@1 is directly under that same PCIe bridge #1. In IOReg, it will register @1,1 (0x00010001) but in PCie notation, it'll appear as 01:00.1 because it's the 2nd device @1 under that PCIe bridge #4.
  • and so on for other PCie bridges RP09 and RP17...

 

Thanks for this, great information and certainly makes things more understandable. 

 

Share this post


Link to post
Share on other sites

Thanks for this important topic, still need to know if we need to patch dsdt first then add the devices or add the devices in dsdt one by one.

thanks for the reply

Share this post


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

Thanks for this important topic, still need to know if we need to patch dsdt first then add the devices or add the devices in dsdt one by one.

thanks for the reply

 

Hello,

 

No need to patch DSDT or add devices to DSDT, in this guide devices are added inside config.plist using Clover. The end result is same, where you have the PCI info displayed inside System Information. 

So System information PCI information can be provided in config.plist OR you can patch DSDT and add  _DSM methods.  The _DSM method from DSDT in guide is used for purpose of a comparison 

between _DSM method inside DSDT and  Arbitrary and Properties inside config.plist.

 

If you want to learn about DSDT patching for adding System Information - PCI, I found the best starting point is to compare a patched DSDT with original DSDT using DiffMerge and then read forums posts about DSDT patching here on insanelymac.

The best person to approach for patched DSDT is @MaLd0n , his DSDT patching and knowledge is excellent. 

 

Best! :)

 

Edited by glasgood

Share this post


Link to post
Share on other sites
17 hours ago, steve3d said:

wish someday, hackintool can directly export the correct pci devices for clover..

I'm adding in support but I have a couple of questions for @Hervé


My questions are related to DevicePath and the _ADR value in DSDT.

 

In glasgood's example for his RP08.PXSX entry the value is 04:00.0. Would that translate to DevicePath = PciRoot(0x4)/Pci(0x0,0x0)? What would the _ADR be?

 

glasgood's ethernet entry 00:1f:6, so would  DevicePath = PciRoot(0x0)/Pci(0x1f,0x6) and _ADR 0x001f0006?

Share this post


Link to post
Share on other sites
Posted (edited)

Thanks @Hervé. I'm still not entirely sure what the correct DevicePath for devices like RP08.PXSX should be. I'm guessing the path generated by gfxutil is correct so I'm currently using the same method.

 

@glasgood @steve3d and others please try Hackintool v2.3.4 which will now export PCI info directly to Clover config.plist and dsl format.

 

The dsl I'm generating will not compile to aml without modification so this obviously needs more work.

 

Anyway I appreciate feedback on this.

Edited by headkaze

Share this post


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

 

@glasgood @steve3d and others please try Hackintool v2.3.4 which will now export PCI info directly to Clover config.plist and dsl format.

 

The dsl I'm generating will not compile to aml without modification so this obviously needs more work.

 

Anyway I appreciate feedback on this.

 

@headkaze Fantastic, works a charm and only really needs some cosmetic string edits.

 

 

Only one small thing,  the Broadcom BCM4331 IORegname is shown as pci14e4,4331 in System Infomation PCI rather than the string info within pcidecives.plist

Originally I had to add BCM4331 to Arbitrary to get the string info into PCI

 

Screen shot below from old Hackintool PCI 

644492554_Screenshot2019-04-24at06_49_21.png.4729b2d38b8135cab78ba54ec80f8942.png

 

Screenshot of new Hackintool PCI

1365172268_Screenshot2019-04-24at07_05_13.png.39e38cc5323d4a40bb03cf66151b7137.png

 

 

 

1896376487_Screenshot2019-04-24at06_55_19.png.6ba0122862198550bbf9cfebc73d1abe.png

 

 

 

 

 

 

 

Here is the result of directly adding the pcidevices.plist info to Properties in config.plist

 

1673909224_HackintoolOriginal.png.6886c19b7e109d3914038cf0b556a4ff.png

 

All in there are 20 entries within Properties see (config.plist ), and 13 are visible inside PCI. Think the other 7 are not relevant for PCI information those being Bridge and Port entries.

 

 

After renaming some strings:

 

 

Edits.png.1bbf5622a10452afcc0065862111a024.png

 

 

 

Will update guide soon and add latest Hackintool PCI export info.

 

Thanks :thumbsup_anim:

 

Attached files for perusal:

 

config.plist

pcidevices.plist

pcidevices.json

pcidevices.txt

pcidevices.dsl

 

 

 

 

 

 

Edited by glasgood

Share this post


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

Originally I had to add BCM4331 to Arbitrary to get the string info into PCI

So what we need to do is get this working using Devices/Properties. There was a bug with the Device Path generation ("PciRoot(0x0)" is obviously wrong) which should be fixed now in Hackintool v2.3.5. Please give a try.

Share this post


Link to post
Share on other sites
29 minutes ago, headkaze said:

So what we need to do is get this working using Devices/Properties. There was a bug with the Device Path generation ("PciRoot(0x0)" is obviously wrong) which should be fixed now in Hackintool v2.3.5. Please give a try.

 

 

 

@headkaze Looks like bug is fixed, all good on my Z390 Aorus Pro :thumbsup_anim:

 

1529888348_Screenshot2019-04-24at14_27_42.png.3ccc49b047b2eb6519e95b38572ecf27.png

 

 

 

Share this post


Link to post
Share on other sites
42 minutes ago, headkaze said:

So what we need to do is get this working using Devices/Properties. There was a bug with the Device Path generation ("PciRoot(0x0)" is obviously wrong) which should be fixed now in Hackintool v2.3.5. Please give a try.

 

@headkaze

 

Original information:

 

Before.png.87c59f08e0aed44f9efe3390ec0436a8.png

 

Renames:

 

After.png.a80d00443ea08b4fab07aef809f9857b.png

 

Files:

 

pcidevices.plist

pcidevices.json

pcidevices.dsl

pcidevices.txt

Share this post


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

How to fix this sub-class?

 

233441548_ScreenShot2019-04-24at19_14_20.thumb.png.77dccb7eb66052e0f31229eb58d0f7d5.png

 

It seems that when pcidevices.plist is created, that PciRoot(0x0)/Pci(0x1f,0x5) is showing the correct information within config.plist and System Information PCI.

 

2015197897_Screenshot2019-04-24at17_30_28.thumb.png.92fa60a89fcabb48e4508818c7b326fa.png

 

 

 

Edited by glasgood

Share this post


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

How to fix this sub-class?

All PCI data is stored in the pci-ids file which is being updated on a regular basis. If you ran the "Update PCIIDs" function in Hackintool and it still shows as ??? then its subclass is unknown. You can submit it to the project by following the "Submit new data" section in the link above.

Edited by headkaze

Share this post


Link to post
Share on other sites
Posted (edited)

Hi @headkaze

In first place thank you very much for the excellent tool, and I want to know why my hack in the Platform ID doesn't have any value, is an error or it is because I don't have an DGPU?

Its only my curiosity speaking...

Thanks

 

PS: Corrected in Hackintool v2.3.5...

 

Captura de ecrã 2019-04-24, às 20.41.25.png

Captura de ecrã 2019-04-24, às 20.51.09.png

Edited by MorenoAv

Share this post


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

Hi @headkaze

In first place thank you very much for the excellent tool, and I want to know why my hack in the Platform ID doesn't have any value, is an error or it is because I don't have an DGPU?

Its only my curiosity speaking...

Thanks

Do you have the Framebuffer->macOS 10.14 menu item set? I know it's confusing but even if you're not using 10.14 you should be using this setting. It is set by default now.

HackintoolFBmacOS1014.png

Edited by headkaze

Share this post


Link to post
Share on other sites

@headkaze thanks for your reply, and now I have it... and it works as it should... it was one more noob...ish error...

 

 

Share this post


Link to post
Share on other sites

Hello to everybody , i tried the method in my hack but still the devices not appear in the pci list in the system information panel, find attached my config plist , ioreg , and dsdt ssdts attached hope someone can help me , Thank you in advance.

files.zip

Share this post


Link to post
Share on other sites
5 hours ago, PC IT said:

Hello to everybody , i tried the method in my hack but still the devices not appear in the pci list in the system information panel, find attached my config plist , ioreg , and dsdt ssdts attached hope someone can help me , Thank you in advance.

files.zip

 

I have updated guide, hopefully I have made it easy to follow. 

 

Share this post


Link to post
Share on other sites

hi, good morning,

Last night, for curiosity and to see if I could populate my System Information PCI, I followed you guide and after that my UHD 630 is now mobile as you could see in the photo below and in my system information too and I don't know why, could you look into it?

And now I have some boot glitches and icons that change colors...

Thanks in Advance

Captura de ecrã 2019-04-27, às 12.08.29.png

Captura de ecrã 2019-04-27, às 12.07.25.png

config.plist.zip

CLOVER.zip

Share this post


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

hi, good morning,

Last night, for curiosity and to see if I could populate my System Information PCI, I followed you guide and after that my UHD 630 is now mobile as you could see in the photo below and in my system information too and I don't know why, could you look into it?

And now I have some boot glitches and icons that change colors...

Thanks in Advance

Captura de ecrã 2019-04-27, às 12.08.29.png

 

config.plist.zip

CLOVER.zip

 

 

Hello,

 

Remove part of the STRING Properties value (Mobile) try--->  config.plist  edit done, i.e (Mobile) removed.

 

1994527361_Screenshot2019-04-27at12_27_54.thumb.png.729bd8dfb0549dbb4f16d5c59543bd6a.png

 

Edited by glasgood

Share this post


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

 

 

And now I have some boot glitches and icons that change colors...

 

config.plist.zip

CLOVER.zip

 

 

I had a quick look at your Clover folder. You mention boot glitch, I noticed you are using EmuVariableUefi-64.efi. On some Hack's EmuVariableUefi-64.efi can cause pre-boot memory allocation errors. Not sure what your exact system specification is, but guessing it's based on Z390 chipset. Possibly my >> Mojave Hackintosh guide should be relevant for you, have a look at my config.plist and EFI. 

 

Best!

Edited by glasgood

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 valueimagery
      Okay So I have two PCIe controller cards, both 3rd party, unbranded from eBay.
       
      1st runs off the Marvell 88SE92xx chipset.  4 Internal Ports.
      https://www.ebay.com.au/itm/PCI-E-PCI-Express-to-SATA3-0-4Port-SATA-III-6G-Expansion-Controller-Card-Adapter/264029216955?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649
       
      2nd runs off the ASMedia ASM1061 chipset. 2 Internal/ 2 External Ports (selectable by jumpers)
      https://www.ebay.com.au/itm/PCI-E-To-SATA3-PCI-E-SATA3-0-6Gb-s-the-SSD-Asmedia-Chip-Expansion-Card-ASM1061/191572577652?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649
       
      The hack is running stable no issues on 10.4.2 with an i7 8700k ASUS Maximus X Code as iMac 18,3
       
      However, I wanted to add eSATA ports for some older drive enclosures I own, and some extra internal SATA ports as I've used all the SATA ports on the Motherboard.
      The 1st Marvell actually works OOB in Mac OSX.  No kexts needed.  Speeds seem good (350R/400W on an SSD 80R/W on a 5400 HDD)
       
      However, a few things don't seem perfect.
      1) the AHCI version is 1.0.  I imagine this could and should be a newer version? 1.2 or 1.31? If it should be updated, is this something only able to be flashed from a Windows OS?
      2) It can't be used as a boot option.  the Maximus doesn't recognise it as a startup option.  Is this a possible AHCI version firmware issue?  Is booting ever possible from these controllers? 
      3) TRIM was disabled in system profile. I know it automatically worked OOB for my NVME2 drives connected to the motherboard,  But to enable Trim on an SSD 860 EVO I needed to submit the terminal command:
      sudo trimforce enable
       
      Now the second ASMedia controller I haven't been able to get to work.  I've switched the jumpers (not sure which position is the 1,2,3) so I've made it so that one internal and one external will operate to test the card.
       
      System profiler sees the card like all the others as a "Generic AHCI Controller" with AHCI version 1.20 supported.
      However, I cannot get any drive to be recognised in the eSATA ports.  I haven't tested the internal ports as I don't need these.
       
      I've attempted using two kexts (attached) AHCI_3rdParty_eSATA.kext and AHCIPortInjector.kext
      When I use AHCIPortInjector.kext the SATA device is recognised in system profiler as an ASM1062.  However no drive works with this kext.  And reading the chip itself on the card it says ASM1061.  So not sure why it's preferring the 1062 entry over the 1061 since both are present in the kext.
       
      When I use AHCI_3rdParty_eSATA.kext that SATA device is not recognised at all in the system profiler.  It disappears.
       
      I'm not using a custom DSDT for this motherboard and I've attached my config.plist if anyone has some insight on either cards.
       
      Cheers,
      Shark
       
       
       
       
      config-NOSN.plist
      AHCI_3rdParty_eSATA.kext.zip
      AHCIPortInjector.kext.zip
    • By Lilith
      Hi,
      i have a little old mobo with socket 1156 no Sata 3 - biostar tpower i55 and i Was wondering if i had some chance to install a new nvme memory like Intel 760p.
      Due lack of support by my mobo i found a Pci Express card lycom dt-120 to expand my connectivity.
      After some researches i understood that i need a ‘bios support for the boot from nvme disk’. I want some of these nvme memory to install high Sierra and get a killer desktop.
      I think that i haven’t obviously a native bios support cause my mobo is pretty old, so i can’t get an nvme disk and install properly high Sierra hoping that boot?
      Or should i catch anyway? I Guess that same problem is for w10? 
      Thanks, Gabriele.
    • By ITzTravelInTime
      This is a dedicated thread about the intel 8255X based ethernet cards which, although being old (but also very cheap and easy to find used online), they still works in the latest macOS releases today i tested mine with the 64 bit compiled AppleIntel8255X kext and works like a charm! stable and withou any issues with mine 100 mbit managed ethernet switch and also without suffering of problems like connection dieing under heavy load or sleep/wake issues, so just to report that i have create this dedicated thread about and also i leave the kext as an attachment, in this post, this may be usefoul to have cheap working ethernet for hackintosh machines running the latest macOS or just to reuse old hardware some one can have laying around.
      AppleIntel8255x.kext.zip
    • By ITzTravelInTime
      I have started this thread to discuss about old and very cheap ethernet cards working in the latest macOS releases, cards who just uses old ethernet controllers or are new and cheap cards with old ethernet controllers, this thread is just to discuss about such cards and also to have a list in the first post with reported working cards with drivers linked.
      To contribute you have to report which card of this kind is working for you and which driver or method you followed to get it wo work and also which issues you have, and then it will be added in the list.
      I start reporting cards which worked for me, yours will be added in the future:
      intel 8255X based cards:
                just works using the AppleIntel8255X kext (look in the attachments) and seems to be stable with no issues
       
      And also there are some cards i am curious to see if can work with mac, so i leave this part at the end of the post, do you know if it's possible to get realtek pci (not pci express) ethernet cards working in the latest mac os? i have a few of them and i have difficulties fining drivers for mac, having a driver for the latest mac wil help me in creating also a youtube video with the cheapest hackintosh compatible ethernet cards
       
      AppleIntel8255x.kext.zip
    • By grujicic
      First I would like to thank you guys for the great community and perfect source of the informations.
       
      After a lot of struggle i've finally manage to turn this server mobo into great and powerful macpro rig. (smbios - MacPro 5,1)
      It runs sierra 10.12.12 with no errors but there is one strange catch.
       
      This mobo has 7 pcie slots, but only first - bottom three actually works !? dpcimanager don't recognise any of the pcie cards inserted into other / upper 4 pcie slots. (pretty sure that bios settings are correct, and these cards works withouth any problem under windows)
       
      I'm using dsdt (there's no way to boot macos installation or the system without one)
       


       
       
      ** quick example - kt4006 usb 3.0 card (which works oob with 10.12.12) works just fine when is inserted into 3rd pcie slot from the bottom, but doesn't work if it is inserted in any of 4 upper - marked with red - pcie ports.... Basically with this I just want to confirm that the problem is not about pcie cards and specific driver / settings related to them.. it is about slots.
       
      Maybe a few of the initial problems i had with this mobo could be a good clue... After successful sierra installation os recognized 12 cpu threads instead of 24, and 16 gb of ECC Ram instead of 32.
      Cpu cores / threads problem is fixed by adding extra cpus in my dsdt file and ram problem by adding proper slot info via clover configurator.
      Now both memory and cpu cores works perfectly.
       
       
      Supermicro X8DTH-6f http://www.supermicro.com/products/motherboard/QPI/5500/X8DTH-6F.cfm 2x Xeon e5645 32gb ecc evga GTX 960 2gb ssc  
      Thank you!
×