Jump to content

9 posts in this topic

Recommended Posts

Advertisement
1 hour ago, MaLd0n said:

use DPCI MANAGER

DPCIManager.app.zip

PCI List Tab

Thanks for helping me

http://pci-ids.ucw.cz/read/PC/8086/1563

5aca5420bebc5_.thumb.png.b65b2cb0d469d6e9ce54eaadf0b20308.png

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

x540 driver ,Can modify it?

 SmallTreeIntel8259x.kext.zip

Linux:ixgbe-5.3.6.tar.zip

https://www.small-tree.com/support/download_category?cat_id=6

Adding 10 gigabit ethernet networking to your hackintosh is now extremely easy. You simply need to add these three kexts to your EFI/CLOVER/KEXTS/OTHER folder and you will have a working card! This method works so far on the following cards:

Supported devices for SmallTreeIntel8254x.kext:

  • 8086:1010 82546EB Gigabit Ethernet Controller (Copper)
  • 8086:1011 82545EM Gigabit Ethernet Controller (Fiber)
  • 8086:1012 82546EB Gigabit Ethernet Controller (Fiber)
  • 8086:101d 82546EB Gigabit Ethernet Controller
  • 8086:1026 82545GM Gigabit Ethernet Controller
  • 8086:1027 82545GM Gigabit Ethernet Controller
  • 8086:1028 82545GM Gigabit Ethernet Controller
  • 8086:105e 82571EB Gigabit Ethernet Controller (Also covered by AppleIntel8254XEthernet.kext)
  • 8086:105f 82571EB Gigabit Ethernet Controller
  • 8086:1079 82546GB Gigabit Ethernet Controller
  • 8086:107a 82546GB Gigabit Ethernet Controller
  • 8086:107b 82546GB Gigabit Ethernet Controller
  • 8086:107c 82541PI Gigabit Ethernet Controller
  • 8086:107d 82572EI Gigabit Ethernet Controller (Copper)
  • 8086:107e 82572EI Gigabit Ethernet Controller (Fiber)
  • 8086:10a4 82571EB Gigabit Ethernet Controller
  • 8086:10b5 82546GB Gigabit Ethernet Controller (Copper)
  • 8086:10b9 82572EI Gigabit Ethernet Controller (Copper)
  • 8086:10bc 82571EB Gigabit Ethernet Controller (Copper)

SmallTreeIntel82576.kext:

  • 8086:1521 I350 Gigabit Network Connection
  • 8086:1522 I350 Gigabit Fiber Network Connection
  • 8086:1533 I210 Gigabit Network Connection (Also covered by AppleIntelI210Ethernet.kext)

SmallTreeIntel8259x.kext:

  • 8086:10c6 82598EB 10-Gigabit AF Dual Port Network Connection
  • 8086:10c7 82598EB 10-Gigabit AF Network Connection
  • 8086:10c8 82598EB 10-Gigabit AT Network Connection
  • 8086:10ec 82598EB 10-Gigabit AT CX4 Network Connection
  • 8086:10d8 82599EB 10 Gigabit Network Connection
  • 8086:10fb 82599ES 10-Gigabit SFI/SFP+ Network Connection
  • 8086:10f1 82598EB 10-Gigabit AF Dual Port Network Connection
  • 8086:151c 82599 10 Gigabit TN Network Connection
  • 8086:150b 82598EB 10-Gigabit AT2 Server Adapter
  • 8086:1528 Ethernet Controller 10-Gigabit X540-AT2
  • 8086:10fc 82599 10 Gigabit Dual Port Network Connection
  • 8086:1560 Ethernet Controller X540

SmallTreeIntel8259x.kext.zip

Share this post


Link to post
Share on other sites

FakePCIID_Intel_GbX.kext  & FakePCIID.kext & SmallTreeIntel8259x.kext  in EFI\CLOVER\kexts\Other

driver controller : YES

status:cable unplugged

FakePCIID_3.zip

Untitled.thumb.jpeg.dfda48258aff241ef895fc905ee21b39.jpeg

FakePCIID_Intel_GbX.kext :IOPCIPrimaryMatch 0x15638086

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>BuildMachineOSBuild</key>
	<string>17C88</string>
	<key>CFBundleIdentifier</key>
	<string>org.rehabman.injector.FakePCIID-Intel-GbX</string>
	<key>CFBundleInfoDictionaryVersion</key>
	<string>6.0</string>
	<key>CFBundleName</key>
	<string>FakePCIID_Intel_GbX</string>
	<key>CFBundlePackageType</key>
	<string>KEXT</string>
	<key>CFBundleShortVersionString</key>
	<string>1.3.11</string>
	<key>CFBundleSupportedPlatforms</key>
	<array>
		<string>MacOSX</string>
	</array>
	<key>CFBundleVersion</key>
	<string>1.3.11</string>
	<key>DTCompiler</key>
	<string>com.apple.compilers.llvm.clang.1_0</string>
	<key>DTPlatformBuild</key>
	<string>9C40b</string>
	<key>DTPlatformVersion</key>
	<string>GM</string>
	<key>DTSDKBuild</key>
	<string>10M2518</string>
	<key>DTSDKName</key>
	<string>macosx10.6</string>
	<key>DTXcode</key>
	<string>0920</string>
	<key>DTXcodeBuild</key>
	<string>9C40b</string>
	<key>IOKitPersonalities</key>
	<dict>
		<key>Intel GbX</key>
		<dict>
			<key>CFBundleIdentifier</key>
			<string>org.rehabman.driver.FakePCIID</string>
			<key>FakeProperties</key>
			<dict>
				<key>RM,subsystem-id</key>
				<data>
				CgAAAA==
				</data>
			</dict>
			<key>IOClass</key>
			<string>FakePCIID</string>
			<key>IOMatchCategory</key>
			<string>FakePCIID</string>
			<key>IOPCIPrimaryMatch</key>
			<string>0x10c68086 0x10c78086 0x10c88086 0x10ec8086 0x10d88086 0x10fb8086 0x10f18086 0x151c8086 0x150b8086 0x15288086 0x10fc8086 0x15608086 0x15638086</string>
			<key>IOProviderClass</key>
			<string>IOPCIDevice</string>
		</dict>
	</dict>
	<key>OSBundleRequired</key>
	<string>Network-Root</string>
	<key>Source Code</key>
	<string>https://github.com/RehabMan/FakePCIID</string>
</dict>
</plist>

 

Edited by liuhongxin1993

Share this post


Link to post
Share on other sites

FakePCIID_Intel_GbX.kext  & FakePCIID.kext & SmallTreeIntel8259x.kext  in  L/E    &   S/L/E

sudo touch /System/Library/Extensions && sudo kextcache -u /

5acddb2a86c0a_1.thumb.jpeg.3d40ee380377cb703033f0d4c5b60982.jpeg

Thank you for helping me.

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 Mieze
      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:
       
      5 Series
      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)
      I219LM I219V  
      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.  
      Current Status
      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.  
      FAQ
      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.  
      Installation
      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.  
      Troubleshooting
      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.5.0 (2019-10-15) Reworked interrupt throttling code and added new configuration parameters. 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.
    • By Slice
      I want to present you updated RealtekR1000 driver. I added support for new chips according to linux's sources.
      Now it supports RTL8168E,F/8111E,F.It works for me and works better then v2.0.6 from realtek.com.tw. Now I have no problems with sleep/wake. With native driver I sometimes lose LAN after wake.With this driver never.

      UPDATE. In this version I applied my own inventions so my driver differs from native.
       
      09.10.2019
      The driver is on GitHub now, sources and release
      https://github.com/SergeySlice/RealtekLANv3

      05.05.2015
      Sorry about broken links. There is new one. My latest sources
      RealtekR1000SL_src_20.02.2014.zip
      RealtekR1000SL.kext-v312.zip

      25.04.2013
      Corrected a mistake with warm boot after Windows. Thanks for Mieze, dmazar, rehabman.
      Updated part for RTL 8105/RTL8136
      This kext is compiled under SL, XCode 3.2.5. For use in ML I'll check little later. EDITED: I checked, it works in ML 10.8.3.
       
       
      15.12.2013
      I made some changes according to official Realtek driver 8.037, newest for now. I can't say I take it as a whole. No, my driver is cropped and may not work for some chips.
      Anyway it tested for me in Mavericks.
      Change log:
      - adopted for new chips RTL8168GU/8111GU, 8411B, RTL8168EP/8111EP . But not tested
      - autolink to 1000Mb/s
      - some functions for WOL, not tested.
       
      17.12.2013
      More changes from linux sources implemented
       
      20.12.2013
      Implemented WoL as Mieze did.
       
      24.12.2013
      More codes for 8105E but not complete
    • By Teerachat
      Hi every body, I am a new user of mac os. I use IMaC late 2017 mac os high sierra 10.13.6(17G65). I want to use Titan V as an external eGPU for molecular dynamic simulation. First I download 
      Webdriver-387.10.10.15.15.108.pkg. And it cannot detect my eGPU (I use sonnet breakaway box 350 watts). My question are : i) what driver NVIDIA is suitable for this mac os version  and it should be compatible with Titan V ii) what procedures should I follow to complete installation and make it working?.
       
      Thank you so much
       
      Teerachat
    • By eliot6001
      I don't know whether my LAN device will work on MAC and Which version of mac but i still want to run MAC on my PC, Also i checked my CPU-GPU and it turned out that i can Run MAX High sierra but i realized that some people have trouble with Sound and Internet connection so Here's the NAME of my LAN device:
       
      PCI\VEN_10EC&DEV_8136&SUBSYS_012310EC&REV_05\4&45F2A70&0&00E1 as (LAN DEVICE took the name from device manager in  windows). 
      also from compatibleIds i got this:
      PCI\VEN_10EC&DEV_8136&REV_05
       
      Is it Supported on any version of macOS ?
×