Jump to content

Intel82574L - Impossible to get at 1GB


Ashmodai
 Share

8 posts in this topic

Recommended Posts

I have a strange issue with my onboard intel networking chip. It used to work very well before I upgrade to El Capitan (and Clover by the same occasion).

I had to patch the device id directly in the Intel82574L.kext for the card to be recognised (as before under Yosemite)  but no way, it is only detected as a 100MB card ... impossible to get it to work a Gibabit speed which is a hell of a pain.

 

Extract of the ioreg -lw0  results where we see clearly that the device is supposed to be not capable of better (argh)

 

Did anyone faced such an issue and find a solution ?

Thanks a lot in advance !

 

 

    | |   |     +-o Intel82574L  <class Intel82574L, id 0x10000068e, !registered, !matched, active, busy 0 (1 ms), retain 7>

    | |   |       | {

    | |   |       |   "IOClass" = "Intel82574L"

    | |   |       |   "IOActiveMedium" = "00500026"

    | |   |       |   "IOResourceMatch" = "IOKit"

    | |   |       |   "EN Number" = 0

    | |   |       |   "IOMinPacketSize" = 64

    | |   |       |   "IOPowerManagement" = {"CapabilityFlags"=32768,"MaxPowerState"=1,"CurrentPowerState"=1}

    | |   |       |   "IOProviderClass" = "IOPCIDevice"

    | |   |       |   "IOLinkStatus" = 3

    | |   |       |   "IOVendor" = "Intel"

    | |   |       |   "IOPacketFilters" = {"IONetworkFilterGroup"=275,"IOEthernetDisabledWakeOnLANFilterGroup"=0,"IOEthernetWakeOnLANFilterGroup"=1}

    | |   |       |   "Driver Parameters" = {"Maximum Interrupt Rate"=8000,"RxAbsoluteTimer100"=300,"RxAbsoluteTimer10"=300,"RxDelayTimer1000"=0,"RxDelayTimer100"=25,"Offload TCP/IP Checksum"=Yes,"Enable TSO"=No,"Flow Control"="Transmit and Receive","TxDescriptorCount"=1024,"RxDescriptorCount"=1024,"RxAbsoluteTimer1000"=64,"RxDelayTimer10"=25}

    | |   |       |   "IOProbeScore" = 0

    | |   |       |   "Partner-Capabilities" = {"Pause"=Yes,"Asymmetric-Pause"=Yes,"100BaseTX-Half-Duplex"=Yes,"10BaseT-Full-Duplex"=Yes,"1000BaseT-Full-Duplex"=No,"100BaseTX-EEE"=No,"1000BaseT-EEE"=No,"10BaseT-Half-Duplex"=Yes,"100BaseTX-Full-Duplex"=Yes}

    | |   |       |   "IOMediumDictionary" = {"08000026"={"Index"=9,"Type"=134217766,"Flags"=0,"Speed"=100000000},"00500026"={"Index"=8,"Type"=5242918,"Flags"=0,"Speed"=100000000},"00100026"={"Index"=7,"Type"=1048614,"Flags"=0,"Speed"=100000000},"00200023"={"Index"=2,"Type"=2097187,"Flags"=0,"Speed"=10000000},"00000020"={"Index"=1,"Type"=32,"Flags"=0,"Speed"=0},"08000023"={"Index"=5,"Type"=134217763,"Flags"=0,"Speed"=10000000},"00500023"={"Index"=4,"Type"=5242915,"Flags"=0,"Speed"=10000000},"00100023"={"Index"=3,"Type"=1048611,"Flags"=0,"Speed"=10000000},"00000022"={"Index"=0,"Type"=34,"Flags"=0,"Speed"=0},"00500030"={"Index"=11,"Type"=5242928,"Flags"=0,"Speed"=1000000000},"00100030"={"Index"=10,"Type"=1048624,"Flags"=0,"Speed"=1000000000},"08000030"={"Index"=12,"Type"=134217776,"Flags"=0,"Speed"=1000000000},"00200026"={"Index"=6,"Type"=2097190,"Flags"=0,"Speed"=100000000}}

    | |   |       |   "IOMACAddress" = <0026186dc9fb>

    | |   |       |   "IOMatchCategory" = "IODefaultMatchCategory"

    | |   |       |   "CFBundleIdentifier" = "com.apple.driver.Intel82574L"

    | |   |       |   "IOMaxPacketSize" = 9018

    | |   |       |   "IOModel" = "82574L"

    | |   |       |   "IOSelectedMedium" = "00500030"

    | |   |       |   "IOLinkSpeed" = 100000000

    | |   |       |   "IOPCITunnelCompatible" = Yes

    | |   |       |   "IOPCIMatch" = "0x104b8086 0x10f68086"

    | |   |       |   "IOFeatures" = 10

 
 

 

Link to comment
Share on other sites

Thanks a lot to both of you. I will go thru these both threads. I am not sure about the flashing since mine is onboard on an Asus dual xenon mainboard.

For faking the device id actually this is what I am doing now and the card does work ... But only as a 100mb/s card instead of a gb/s ... And on a server this is embarrassing:-)

and frustrating !

Just to clarify when I say that faking the device Id is what I do I mean by using clover and editing kext which is very different from the method described in the mentioned threads :-)

Link to comment
Share on other sites

In case someone ever face the same issue I found out the what was causing it for me ... A boot parameter that I had always to put in the last for my machine to boot and which in this case seems was creating a conflict of some sort ...

Npci=0x2000

Just removed it and my network card is now working like a charm again ...

Link to comment
Share on other sites

 Share

×
×
  • Create New...