1 post in this topic
Recently Browsing 0 members
No registered users viewing this page.
Populating System Information - PCI via config.plist using Hackintool
Clover Configurator Mackie100
A quick guide on how to add device information into System Information - PCI with config.plist and Hackintool using Clover Configurator.
Hackintool PlistEdit Pro Clover Configurator
DOWNLOAD SAMPLE FILES
config.plist ( includes Hackintool pcidevices.plist properties export ) pcidevices.plist configArbitraryAndProperties.plist( previous config.plist using Arbitrary & Properties without use of Hackintool )
SYSTEM INFORMATION - PCI
To my knowledge, there are a few different ways to populate the System Information PCI with device information:
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.
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
DEVICES - PROPERTIES
DEVICES - PROPERTIES - HACKINTOOL
Run Hackintool, PCI tab and Update PCIIDs
Export PCI info
HOW TO SAVE pcidevices.plist Properties TO CONFIG.PLIST
Download and install
Right click and open pcidevices.plist with PlistEdit Pro
Mount EFI partition and drag and drop config.plist onto desktop. Right click, open with PlistEdit Pro
Place both PlistEdit Pro windows side by side:
Next, click Properties, copy. (pcidevices.plist)
Then, click on Devices (config.plist) so that it is highlighted and Paste As Child and Save.
Verify Properties has been added correctly to Devices inside config.plist using Clover Configurator or PlistEdit Pro
Place config.plist back inside EFI/Clover
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.
Example of optional renames done with config.plist for Aorus Z390 Pro
Save renames and then add Devices / Properties to your config.plist.
No need to rename device_type Bridge model name.
THANKS TO @headkaze & @Hervé
AND ALSO @steve3d for his post!
This project is dedicated to the memory of Mausi, the cat I loved more than anybody else.
A few days before Christmas I started my latest project, a new driver for recent Intel onboard LAN controllers. My intention was not to replace hnak's AppleIntelE1000e.kext completely but to deliver best performance and stability on recent hardware. That's why I dropped support for a number of older NICs. Currently the driver supports:
82578LM 82578LC 82578DM 82578DC 6 and 7 Series
82579LM 82579V 8 and 9 Series
I217LM I217V I218LM I218V I218LM2 I218V2 I218LM3 100 Series (since V2.1.0d0)
I219LM I219V 200 Series (since V2.3.0d0)
I219LM I219V 300 Series (since V2.4.0d0)
Key Features of the Driver
Support for multisegment packets relieving the network stack of unnecessary copy operations when assembling packets for transmission. No-copy receive and transmit. Only small packets are copied on reception because creating a copy is more efficient than allocating a new buffer. TCP, UDP and IPv4 checksum offload (receive and transmit). Support for TCP/IPv6 and UDP/IPv6 checksum offload. Makes use of the chip's TCP Segmentation Offload (TSO) feature with IPv4 and IPv6 in order to reduce CPU load while sending large amounts of data (disabled due to hardware bugs). Fully optimized for Sierra (64bit architecture) but should work with older 64bit versions of macOS too, provided you build from source with the appropriate SDK for the target OS. Support for Energy Efficient Ethernet (EEE). VLAN support is implemented but untested as I have no need for it. The driver is published under GPLv2.
The driver has been tested successfully with I217V, I218V and 82579V under 10.9.5 and above. The attached archive includes source code as well as a prebuilt binary (debug version) for Mavericks and newer versions of macOS. Known Issues
There seem to be problems while using VMware with version 1.x.x of the driver. In case you are affected use version 2.0.0 or newer.
Could you add support of for...? Well, you are probably asking me to add support for one of the older NICs like the 82571/2/3/4L or 82583 and the answer will be no as I dropped support for these chips intentionally. They are broken and I lost more than 2 weeks trying to make it work on the 82574L without success. I was asked to add support for I210, I211 and I350 but as these chips have a completely different architecture, which isn't supported by the underlying Linux driver, this is impossible, sorry. Does it work with Snow Leopard or 32 bit kernels? No and I have no plans to make a version for 32 bit kernels or anything older than Lion. WoL from S5 doesn't work with this driver but under Windows it's working. Is this a driver bug? No it isn't, the driver is working as it should because OS X doesn't support WoL from S5.
Goto /S/L/E and delete AppleIntelE1000e.kext. Recreate the kernel cache. Open System Preferences and delete the corresponding network interface, e. g. en0. Reboot. Install the new driver and recreate the kernel cache. I recommend to use Kext Wizard or a similar utility for the installation. Reboot Open System Preferences again, select Network and check if the new network interface has been created automatically or create it manually now. Configure the interface.
Help - I'm getting kernel panics!
Well, before you start complaining about bugs after you upgraded macOS and ask me to publish a driver update, you should first try to resolve the issue on your own by cleaning the system caches.
As the driver uses macOS's private network driver interface, which is supposed to be used by Apple provided drivers only, you might run into problems after an OS update because the linker may fail to recognize that IONetworking.kext has been updated and that the driver needs to be linked against the new version (Apple provided drivers avoid this problem because they are always updated together with IONetworking.kext). As a result, the linking process produces garbage and the driver may call arbitrary code when trying to call functions from IONetworking.kext. This usually results in unpredicted behavior or a kernel panic. In order to recover from such a situation, you should clean the System Caches forcing the linker to recreate it's caches:
Delete all the files in /System/Library/Caches and it's subdirectories but leave the directories and the symbolic links intact. This is very important! Reboot. Recreate the kernel cache. Reboot again.
Make sure you have followed the installation instructions especially when you have issues with certain domains while the others are working fine. Use the debug version to collect log data when trying to track down problems. The kernel log messages can be retrieved with "grep kernel /var/log/system.log" in Terminal. Starting from Sierra use "log show --predicate "processID == 0" --debug" in order to retrieve kernel logs. Include the log data when asking for support or giving feedback. I'm an engineer, not a clairvoyant. Don't copy and paste large amounts of log data to your post. Create an archive with the log data and attach it to your post. In case you don't want to make your log data publicly accessible, contact me via PM and I will provide you a mail address to send it directly to me. Check your BIOS settings. You might want to disable Network Boot and the UEFI Network Stack as these can interfere with the driver. Double check that you have removed any AppleIntelE1000e.kext from your system because it could prevent the driver from working properly. Delete the following files: /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/preferences.plist Verify your bootloader configuration, in particular the kernel flags. Avoid using npci=0x2000 or npci=0x3000. In Terminal run netstat -s in order to display network statistics. Carefully examine the data for any unusual activity like a high number of packets with bad IP header checksums, etc. In case auto-configuration of the link layer connection doesn't work it might be necessary to select the medium manually in System Preferences under Network for the interface. Use Wireshark to create a packet dump in order to collect diagnostic information. Keep in mind that there are many manufacturers of network equipment. Although Ethernet is an IEEE standard, different implementations may show different behavior causing incompatibilities. In case you are having trouble try a different switch or a different cable. Changelog
Version 2.4.0 (2018-04-14) Added support for 300 series versions of I219LM and I219V. Updated underlying Linux source code. Version 2.3.0 (2017-06-20) Added support for 200 series versions of I219LM and I219V. Version 2.2.0 (2016-09-23) Disabled TSO to work around a hardware bug. Version 2.1.0 (2016-05-24) Added support for I219LM and I219V Version 2.0.0 (2015-04-22) First official release which is identical to 2.0.0d2 (only the version number has been changed). Version 2.0.0d2 (2015-04-04) Changed the tx descriptor write back policy for 82579, I217 and I218 to prevent random tx deadlocks. Version 2.0.0d1 (2015-03-14) Uses Apple's private driver interface introduced with 10.8. Supports packet scheduling with QFQ Solves the VMware issue. Version 1.0.0d6 (2015-03-04) Reworked TSO6 support to avoid problems with VMware. Wake-on-LAN now working. Version 1.0.0d5 (2015-02-27) Reworked TSO4 support to eliminate the bug of 1.0.0d4. Added some debug code in order to collect information about the VMware related issue. Version 1.0.0d4 (2015-02-25) Set total length field of the IP-header to zero for TSO4 operations. Report EEE activation state in kernel log message when the link has been established. Version 1.0.0d3 (2015-02-11) Reworked media selection and EEE support (EEE is now activated when both link partners support it. It can be disabled selecting the medium manually). Duplex setting for 10/100 MBit connections is now reported correctly. The number of tx descriptors has been reduced from 2048 to 1024. The code has been cleaned up and obsolete files have been removed. Version 1.0.0d2 (2015-01-31) First development release. Getting the Driver
The source code can be found on GitHub: https://github.com/Mieze/IntelMausiEthernet There is also a prebuilt binary for 10.11 and above in the download section: http://www.insanelymac.com/forum/files/file/396-intelmausiethernet/ Build from Source for 10.8
Register as a developer on Apple's developer website. A free membership is sufficient. Download a copy of Xcode 5.1.1 and install it on your machine. In the project select 10.8 as the "Base SDK" and the "Deployment Target". Call "Archive" from the menu "Product" and save the built driver. Credits
Thanks to RehabMan and Yung Raj for running tests and pointing me in the right direction while I was trying to fix TSO. Special thanks to Yung Raj for motivating me when I was about to give up.
Okay So I have two PCIe controller cards, both 3rd party, unbranded from eBay.
1st runs off the Marvell 88SE92xx chipset. 4 Internal Ports.
2nd runs off the ASMedia ASM1061 chipset. 2 Internal/ 2 External Ports (selectable by jumpers)
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.
Salve a tutti ragazzi,
Mi sono appena iscritto e innanzi tutto vorrei esprimere la mia gratitudine per l'aiuto offerto. Il mio problema come da titolo riguarda il mio Pavilion Power 15 più precisamente il modello cb015nl. Ho notato che c'era un altro topic su un modello simile ma immagino che anche se i modelli sono simili non è detto che siano compatibili quindi ne ho creato uno per il mio modello. Per arrivare al dunque, sono riuscito ad installare con successo Mojave 10.14 ma ho riscontrato diversi problemi una volta avviato l'OS. Quello che non riesco a far funzionare è l'indicatore della batteria, il power managment (Stop non funziona e la luminosità), la porta ethernet e credo che la scheda wifi sia incompatibile, le gesture del trackpad, e l'audio che con una scheda audio esterna funziona a meraviglia e l'ultimo grosso problema è che non riesco a far partire clover senza la usb di installazione, ho installato clover bootoader sull'hd dove ho mojave ma niente senza la usb mi parte il bootloader di hp/windows. Premetto che sono partito con una copia di mojave scaricata dall'appstore. Vi allego il report di HackInfo sperando che possa essere d'aiuto per il troubleshooting
Recompiled v2.3.6 sources in fat-binary mode (Xcode 3.2.6, SDK 10.6, Target OS X 10.6). Fully supported in 32bit and/or 64bit mode under all OS X/macOS versions from Snow Leopard 10.6 to Mojave 10.14.
Nov 16th, 2018: updated description to extend support to Mojave 10.14