Jump to content

Success: AQC107 10 GbE native support in High Sierra 10.13.2

Aquantia

  • Please log in to reply
92 replies to this topic

#81
d5aqoep

d5aqoep

    InsanelyMac Protégé

  • Members
  • PipPip
  • 71 posts

Yes, I disabled onboard LAN and checked before updating: it's en0

Something wrong with your Device ID and Subsystem ID both are 0x0001

 

Compare that to my card before firmware upgrade

 

PMeqFtA.png



#82
Dogman

Dogman

    InsanelyMac Protégé

  • Members
  • Pip
  • 17 posts

Do you think I could fake my device id to 0xd107 to get the update?



#83
d5aqoep

d5aqoep

    InsanelyMac Protégé

  • Members
  • PipPip
  • 71 posts

If you can but for me and most of us, we did not need to fake any Device ID. What device ID does it show in Windows 10's Device manager?



#84
Dogman

Dogman

    InsanelyMac Protégé

  • Members
  • Pip
  • 17 posts

Windows 7 Looks fine:
PCI\VEN_1D6A&DEV_D107&SUBSYS_87411043&REV_02

Maybe it the second revision that creates the problem?

 

EDIT: now macOS displays

Vendor 0x1d6a

Device 0xd107

SubsystemVendor 0x1043 and

Subsytem id 0x8741

 

 

But my cable is still "unplugged". Will look into this later...



#85
Mieze

Mieze

    Giant Cat

  • Developers
  • 1,281 posts
  • Gender:Female
  • Location:Germany
  • Interests:Cats

Windows 7 Looks fine:
PCI\VEN_1D6A&DEV_D107&SUBSYS_87411043&REV_02

Maybe it the second revision that creates the problem?

 

EDIT: now macOS displays

Vendor 0x1d6a

Device 0xd107

SubsystemVendor 0x1043 and

Subsytem id 0x8741

 

 

But my cable is still "unplugged". Will look into this later...

As the subsystem vendor ID shows, the update failed. 0x1043 is ASUStek but it should be 0x106b for Apple after a successful firmware update.

 

Mieze



#86
d5aqoep

d5aqoep

    InsanelyMac Protégé

  • Members
  • PipPip
  • 71 posts

Windows 7 Looks fine:
PCI\VEN_1D6A&DEV_D107&SUBSYS_87411043&REV_02

Maybe it the second revision that creates the problem?

 

EDIT: now macOS displays

Vendor 0x1d6a

Device 0xd107

SubsystemVendor 0x1043 and

Subsytem id 0x8741

 

 

But my cable is still "unplugged". Will look into this later...

Try restarting macOS 2-3 times. Many have had luck once the firmware update is complete.

 

Make sure you have bare minimal clover patches and kexts in hopes that some patch or kext is preventing successful firmware update.



#87
Squuiid

Squuiid

    InsanelyMac Protégé

  • Members
  • Pip
  • 16 posts

Do you know what spi is?  These following are used to do firmware update.

 

 

 

AppleEthernetAquantiaAqtion::spi_busy()

 

AppleEthernetAquantiaAqtion::spi_cmd(unsigned char, int, int)

 

AppleEthernetAquantiaAqtion::spi_nvram_cmds_init()

 

AppleEthernetAquantiaAqtion::spi_nvr_wr_enable(int)

 

AppleEthernetAquantiaAqtion::spi_nvr_busy()

 

AppleEthernetAquantiaAqtion::spi_nvr_erase()

 

AppleEthernetAquantiaAqtion::spi_get(unsigned int, unsigned int*, unsigned long)

 

AppleEthernetAquantiaAqtion::spi_put(unsigned int, unsigned int*, unsigned long)

Might there be a way to manually invoke this update rather than relying on the OS to do it at boot time?

Beyond my technical ability to figure out unfortunately but you seem to know your stuff!



#88
Mieze

Mieze

    Giant Cat

  • Developers
  • 1,281 posts
  • Gender:Female
  • Location:Germany
  • Interests:Cats

Might there be a way to manually invoke this update rather than relying on the OS to do it at boot time?

Beyond my technical ability to figure out unfortunately but you seem to know your stuff!

It might be possible to patch the driver in a way that it performs the firmware update anyway but this would require you to reverse engineer the driver's start() function in order to find out which conditions must be met for the update to be performed. Unfortunately this is far from being trivial and not done within a weekend.

 

Mieze



#89
d5aqoep

d5aqoep

    InsanelyMac Protégé

  • Members
  • PipPip
  • 71 posts
With regards to Asrock Fatal1ty X299 Professional Gaming i9, we have a confirmation that it works OOTB from 10.13.3 and AQC107 firmware is successfully applied at boot.
 
@ everybody:
Right now in Windows, I am having 3 major issues with my ASUS XG-C100C card.
1. macOS 10.13.3 did a firmware update on the card and now it only accepts Apple's customized bootcamp drivers and refuses to install ASUS official drivers from it's support page.
2. Every 3-4 boots, the card fails to detect a link and network cable unplugged comes up. The solution is to disable and enable it from device manager. Then it works without any issues.
3. Wake on LAN (WOL) simply does not work on any of the drivers. This is pathetic as WOL is a supported feature as per Aquantia's AQC107 specifications page. Link here


#90
Mieze

Mieze

    Giant Cat

  • Developers
  • 1,281 posts
  • Gender:Female
  • Location:Germany
  • Interests:Cats

 

With regards to Asrock Fatal1ty X299 Professional Gaming i9, we have a confirmation that it works OOTB from 10.13.3 and AQC107 firmware is successfully applied at boot.
 
@ everybody:
Right now in Windows, I am having 3 major issues with my ASUS XG-C100C card.
1. macOS 10.13.3 did a firmware update on the card and now it only accepts Apple's customized bootcamp drivers and refuses to install ASUS official drivers from it's support page.
2. Every 3-4 boots, the card fails to detect a link and network cable unplugged comes up. The solution is to disable and enable it from device manager. Then it works without any issues.
3. Wake on LAN (WOL) simply does not work on any of the drivers. This is pathetic as WOL is a supported feature as per Aquantia's AQC107 specifications page. Link here

It's obvious that the drivers are still full of bugs which also explains why the Aquantia firmware is applied to cards from different vendors because flashing firmware of a card from a different vendor without explicit consent of the user and in a way that the card won't be recognized by its native drivers anymore is not only stupid but also illegal as it literally causes damage to the card.

 

Another example for Apple's excellent software quality!  :P

 

Mieze



#91
d5aqoep

d5aqoep

    InsanelyMac Protégé

  • Members
  • PipPip
  • 71 posts

It's obvious that the drivers are still full of bugs which also explains why the Aquantia firmware is applied to cards from different vendors because flashing firmware of a card from a different vendor without explicit consent of the user and in a way that the card won't be recognized by its native drivers anymore is not only stupid but also illegal as it literally causes damage to the card.

 

Another example for Apple's excellent software quality!  :P

 

Mieze

Aquantia is to blame. The latest driver on ASUS website for XG-C100C is dated around April 2017. That is almost 10 months without any driver update.

It may not be Apple's fault completely beause Apple expects only iMac Pro hardware on their macOS. They don't care about any other possible scenario and totally not concerned about Hackintosh users.

 

Station-drivers have v2.1 driver available dated Dec 2018. But it fails to install on my card with message "This device cannot start."



#92
Mieze

Mieze

    Giant Cat

  • Developers
  • 1,281 posts
  • Gender:Female
  • Location:Germany
  • Interests:Cats

Aquantia is to blame. The latest driver on ASUS website for XG-C100C is dated around April 2017. That is almost 10 months without any driver update.

10 month without update? That's nothing for a driver and provided there is no new hardware to support, no significant change in the driver interface or in OS power management, there is no need to update a properly written driver for years.


It may not be Apple's fault completely beause Apple expects only iMac Pro hardware on their macOS. They don't care about any other possible scenario and totally not concerned about Hackintosh users.

That's what the military calls collateral damage and as Macs also support Windows 10 there are several supported scenarios in which this kind of damage may occur (a Aquantia card in a TB to PCIe expansion case attached to a Mac running Win 10 and High Sierra).

 

Mieze



#93
hnak

hnak

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 323 posts
  • Gender:Male

I purchased ASUS XG-C100C (0x1d6a/0xd107) and applied 10.3.3 update so that its device ID as modified to 0x1d6a/0x07b. and

 

It works ... 

 

It is now recognized as Apple AQC107-AFW.

I did not disable on-board NIC ( 0x8086/0 x15b7 ), did not change machine type to iMac18 either ( still using iMac17,1 ).

 

As I do not have 10G switch, it is connected to a 1G switch and the connection is 100baseTX, I will switch default connection back to my on-board NIC.

 

I also confirmed ASUS Windows drives does not work as the device ID has changed.

 

EDIT: The reason of slow connection was a loose cable. I got 1G speed.







0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2017 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy