d5aqoep Posted January 3, 2018 Author Share Posted January 3, 2018 This is what working Aquantia AQC107 in a REAL iMac Pro shows and this is what my Hackintosh's ASUS XG-C100C shows Device ID is different so would it be possible to spoof device id with fakepciid kext and some kext patch? Link to comment Share on other sites More sharing options...
ydeng Posted January 9, 2018 Share Posted January 9, 2018 Sorry for late reply, Here is my IOReg. No idea how to get ACPI dump. The driver reads local-mac-address from IOPCDevice for mac address, if you inject this property to PEGP@0, that should set the mac address correctly. Link to comment Share on other sites More sharing options...
Dogman Posted January 9, 2018 Share Posted January 9, 2018 Is there any chance to change to EEPROM of the card to permanently change the device id? A few people did that with the Intel X540-T1 to use the SmallTree kext. ethtool -E --change-eepromIf value is specified, changes EEPROM byte for the specified network device. offset and value specify which byte and it's new value. If value is not specified, stdin is read and written to the EEPROM. The length and offset parameters allow writing to certain portions of the EEPROM. Because of the persistent nature of writing to the EEPROM, a device-specific magic key must be specified to prevent the accidental writing to the EEPROM. What do you think? Link to comment Share on other sites More sharing options...
truemac Posted January 9, 2018 Share Posted January 9, 2018 new iMacPro inject the Mac address through the SMC maybe thats help. RMAC [hex_] (bytes xx xx xx xx xx xx) Link to comment Share on other sites More sharing options...
Dogman Posted January 18, 2018 Share Posted January 18, 2018 Has anyone get the card work? Is there anything I can do to help? I'd really like to add them to my Mac Pros Link to comment Share on other sites More sharing options...
d5aqoep Posted January 18, 2018 Author Share Posted January 18, 2018 Has anyone get the card work? Is there anything I can do to help? I'd really like to add them to my Mac Pros I got it to work without any kext patch or anything. Just check the first post. 1 Link to comment Share on other sites More sharing options...
chemios Posted January 19, 2018 Share Posted January 19, 2018 Tried the method on the first post on 10.13.2 and no dice. Link to comment Share on other sites More sharing options...
ydeng Posted January 20, 2018 Share Posted January 20, 2018 Tried the method on the first post on 10.13.2 and no dice. You probably need to set the subsystem id too 0x187 . Link to comment Share on other sites More sharing options...
d5aqoep Posted January 20, 2018 Author Share Posted January 20, 2018 You probably need to set the subsystem id too 0x187 . I did not set or change any subsystem ID. It worked perfect as soon as I was on latest clover and 10.13.3 B5 To do some testing, I wiped 10.13.3 B5 and re-installed fresh version 10.13.2 and Ethernet still works and it worked OOB. It was also working during setup process. On Windows 10, I force installed the Aquantia v2 driver found in iMacPro1,1 bootcamp package. Does Windows driver update device firmware, change any SubsystemID or anything like that? For those who want to try V2 drivers for Aquantia based cards for Windows, I have extracted these drivers from iMacPro1,1 bootcamp installer package. You have to force install them manually in device manager and ignore Windows incompatibility warnings. Windows 10 X64 only http://www12.zippyshare.com/v/lAckTVG1/file.html I uninstalled the V2 drivers in Windows and something strange happened. Now the official ASUS V1 drivers are refusing to install and it is only accepting Apple's iMacPro1,1 (V2) drivers without any incompatibility warnings. Does it mean that the V2 drivers converted my card into Apple's official card? LMAO. Can someone else test this? Because the card now works perfectly/natively in macOS 12.13.2 and up. ioreg attached. d5aqoep’s iMac.zip Link to comment Share on other sites More sharing options...
chemios Posted January 20, 2018 Share Posted January 20, 2018 Fearful of breaking the card in CentOS, but what the hell. I'll report back later. Link to comment Share on other sites More sharing options...
ydeng Posted January 20, 2018 Share Posted January 20, 2018 I did not set or change any subsystem ID. It worked perfect as soon as I was on latest clover and 10.13.3 B5 To do some testing, I wiped 10.13.3 B5 and re-installed fresh version 10.13.2 and Ethernet still works and it worked OOB. It was also working during setup process. On Windows 10, I force installed the Aquantia v2 driver found in iMacPro1,1 bootcamp package. Does Windows driver update device firmware, change any SubsystemID or anything like that? For those who want to try V2 drivers for Aquantia based cards for Windows, I have extracted these drivers from iMacPro1,1 bootcamp installer package. You have to force install them manually in device manager and ignore Windows incompatibility warnings. Windows 10 X64 only http://www12.zippyshare.com/v/lAckTVG1/file.html I uninstalled the V2 drivers in Windows and something strange happened. Now the official ASUS V1 drivers are refusing to install and it is only accepting Apple's iMacPro1,1 (V2) drivers without any incompatibility warnings. Does it mean that the V2 drivers converted my card into Apple's official card? LMAO. Can someone else test this? Because the card now works perfectly/natively in macOS 12.13.2 and up. ioreg attached. Both device id and subsystem id changed. Firmware version changed too. You need to bring the device id back to 0xd107 for windows ASUS to work. Link to comment Share on other sites More sharing options...
chemios Posted January 20, 2018 Share Posted January 20, 2018 http://www12.zippyshare.com/v/lAckTVG1/file.html I uninstalled the V2 drivers in Windows and something strange happened. Now the official ASUS V1 drivers are refusing to install and it is only accepting Apple's iMacPro1,1 (V2) drivers without any incompatibility warnings. Does it mean that the V2 drivers converted my card into Apple's official card? LMAO. With the tweaked boot camp drivers, does the card still work in Windows? Link to comment Share on other sites More sharing options...
ydeng Posted January 20, 2018 Share Posted January 20, 2018 Fearful of breaking the card in CentOS, but what the hell. I'll report back later. CentOS probably not work. Apple changes the firmware. With the tweaked boot camp drivers, does the card still work in Windows? Yes, with Apple bootcamp driver. Link to comment Share on other sites More sharing options...
d5aqoep Posted January 20, 2018 Author Share Posted January 20, 2018 With the tweaked boot camp drivers, does the card still work in Windows?Those are not tweaked bootcamp drivers. They are straight from Aquantia and included in iMacPro1,1 bootcamp package by Apple themselves. They pass WHQL compatibility test. Right now, ASUS and Aquantia list V1 driver on their support sites. Bootcamp driver version is V2. Another user has confirmed that he managed to get his Gigabyte branded AQC107 to work after upgrading High Sierra 10.13.2 to 10.13.3 Beta 6. So Apple is changing the card’s firmware/subsystem ID during the update process and it becomes compatible forever. Then it also starts working on fresh install of 10.13.2 out of box. The findings are rather strange. Link to comment Share on other sites More sharing options...
chemios Posted January 20, 2018 Share Posted January 20, 2018 Those are not tweaked bootcamp drivers. They are straight from Aquantia and included in iMacPro1,1 bootcamp package by Apple themselves. They pass WHQL compatibility test. Right now, ASUS and Aquantia list V1 driver on their support sites. Bootcamp driver version is V2. Another user has confirmed that he managed to get his Gigabyte branded AQC107 to work after upgrading High Sierra 10.13.2 to 10.13.3 Beta 6. So Apple is changing the card’s firmware/subsystem ID during the update process and it becomes compatible forever. Then it also starts working on fresh install of 10.13.2 out of box. The findings are rather strange. Got it. Did the driver update in Windows but no go in 10.13.2 here. Device ID is still 0xd107. Looks like i'm waiting for 10.13.3. Thanks for all the info, you guys rock. Link to comment Share on other sites More sharing options...
ITzTravelInTime Posted January 22, 2018 Share Posted January 22, 2018 what about ASUS ROG AREION 10G? is it working in 10.13.3 beta? Is anything needed to get it to work? Link to comment Share on other sites More sharing options...
d5aqoep Posted January 22, 2018 Author Share Posted January 22, 2018 Technically it should work given it has same chipset. 1 Link to comment Share on other sites More sharing options...
Squuiid Posted January 22, 2018 Share Posted January 22, 2018 So Apple is changing the card’s firmware/subsystem ID during the update process and it becomes compatible forever. Can this really be what is happening? Why would Apple even do this? And through what mechanism? This doesn't add up for me. Any further thoughts d5aqoep? Link to comment Share on other sites More sharing options...
d5aqoep Posted January 22, 2018 Author Share Posted January 22, 2018 Can this really be what is happening? Why would Apple even do this? And through what mechanism? This doesn't add up for me. Any further thoughts d5aqoep? macOS will not be expecting any other company's AQC107 card because they don't really care about hackintosh users. If a card with Aquantia's AQC107 chipset is found, the software updater proceeds with firmware upgrade assuming it is in iMacPro. When firmware is upgraded, you get a card which not only works in macOS out of the box, but also accepts Apple's special bootcamp drivers in Windows. It may even be a pure bug that Apple is upgrading firmware regardless of different subsystem ID of our ASUS cards. 1 Link to comment Share on other sites More sharing options...
Squuiid Posted January 22, 2018 Share Posted January 22, 2018 macOS will not be expecting any other company's AQC107 card because they don't really care about hackintosh users. If a card with Aquantia's AQC107 chipset is found, the software updater proceeds with firmware upgrade assuming it is in iMacPro. When firmware is upgraded, you get a card which not only works in macOS out of the box, but also accepts Apple's special bootcamp drivers in Windows. It may even be a pure bug that Apple is upgrading firmware regardless of different subsystem ID of our ASUS cards. Thanks. I wonder if the updater specifically looks out for the Mac being an iMac or whether this would also happen when in a cMP. Link to comment Share on other sites More sharing options...
d5aqoep Posted January 22, 2018 Author Share Posted January 22, 2018 My SMBIOS was set to iMac18,1 and the firmware was updated regardless. It's too early to tell anyway. 2 Link to comment Share on other sites More sharing options...
chemios Posted January 23, 2018 Share Posted January 23, 2018 10.3.3 is out. Looks like I know what i'm doing tonight. Link to comment Share on other sites More sharing options...
chemios Posted January 24, 2018 Share Posted January 24, 2018 10.13.3 = working AQC-107 cards. Speeds over SMB suck, but AFP rocks, hitting same speeds I do on CentOS and Windows to my Freenas with Chelsio 10G-BaseT card. I'll give NFS a shot once i figure out how FSTAB works on MacOS. Today was a good day. 2 Link to comment Share on other sites More sharing options...
d5aqoep Posted January 24, 2018 Author Share Posted January 24, 2018 Smooth update to 10.13.3 and everything is working as intended. Link to comment Share on other sites More sharing options...
Dan968 Posted January 24, 2018 Share Posted January 24, 2018 Hello, the SMBIOS needs to be of iMacPro to get a working AQC-107 card? the build number of 10.13.3 is different with iMacPro (17D2047) from other SMBIOS (17D47). Thanks Link to comment Share on other sites More sharing options...
Recommended Posts