Comparison: Intel i350-T4 Genuine vs Fake

Discussion in 'Networking' started by neo, Sep 22, 2015.

  1. canta

    canta Well-Known Member

    Joined:
    Nov 26, 2014
    Messages:
    1,012
    Likes Received:
    184
    agree wiht Neo. this is super duper fake!!

    check the labeling, cheap quality!.
    I do need to check furhter on SN and model numbering :p

    the back side has some not good soldering too!!

    yeah, ethernet transformer is low quality. they did relabel with delta
     
    #101
  2. canta

    canta Well-Known Member

    Joined:
    Nov 26, 2014
    Messages:
    1,012
    Likes Received:
    184
    #102
  3. mstone

    mstone Active Member

    Joined:
    Mar 11, 2015
    Messages:
    505
    Likes Received:
    117
    I would expect the PCI IDs to be the same as the genuine intel ones, or the cards wouldn't work with standard drivers--it would make no sense to build a counterfeit and not use intel's IDs.
     
    #103
  4. canta

    canta Well-Known Member

    Joined:
    Nov 26, 2014
    Messages:
    1,012
    Likes Received:
    184
    As I said. Manufacture has unique subsytemID <correction from device id on my first posting> . this is the regulation.

    Faked Intel nic. Hijack real Intel subsytemID <correction from device id on my first posting>. This is stealing ha-ha.

    Some subsystem id (correction) belong to Dell, Hp. Lenovo. and IBM oem...
    But faker using Intel subsystemid(correction). Many choices to make fake one
     
    #104
    Last edited: Sep 28, 2015
  5. mstone

    mstone Active Member

    Joined:
    Mar 11, 2015
    Messages:
    505
    Likes Received:
    117
    I'm having a lot of trouble parsing what you're trying to say, but I think what you're getting at is actually the "subsystem vendor ID", not the "device ID". On any of these cards (legit or not) I would expect the vendor ID to be intel's, and the device ID to be an intel part (AM4). On a legit device using an AM4 chip on an OEM board the subsystem vendor ID should belong to the OEM, and the subsystem ID will be some random number that nobody except the OEM cares about. On a counterfeit the subsystem vendor ID & subsystem ID will be copied from an actual intel part.

    "PCI ID" commonly refers to the combination of the device ID and the vendor ID. The vendor ID and subsystem vendor ID are allocated by PCI-SIG and unique to each vendor; the device ID and subsystem ID are managed by the vendors, and are not unique across vendors.
     
    #105
  6. canta

    canta Well-Known Member

    Joined:
    Nov 26, 2014
    Messages:
    1,012
    Likes Received:
    184
    thanks for correction, Hard to focus while typing on my small screen moto x .
    the format
    Vendor ID: subsystemID [deviceID], device ID can be existed or not.

    if you look on subsystem ID for I350 , there are more than one belong to Intel.
    faker copied Intel the same (subsystem) ID regardless of i340 or I350 since (on linux) the hardware uses igb module.
    on my understanding:
    Intel has release other subsystemID in the past due on hardware fix or make cheaper by removing/replace logics.
    subsystemID is needed (on linux) to make decision on the code to handle the hardware .
    worst case scenario is compatibality and performance issue.


    other story in USB ID:
    this has been an issue with fake USB-serial dongle :p. the fake dongle works on regular usage, but fail on specific commands. most on ebay USB-Serial dongle are fakes.
     
    #106
  7. RTM

    RTM Active Member

    Joined:
    Jan 26, 2014
    Messages:
    427
    Likes Received:
    142
    I came upon this post on Intels forum when I was doing research on SR-IOV for my new Fujitsu i350 NIC:
    Apparently Dell has disabled SR-IOV on some i350 NICs (9YD6K is mentioned specifically)

    From what I can see on ebay, Dell i350 NICs appear to be the rebranded Intel i350-t2/4, so if this is true, it does not make this matter any less complicated.
     
    #107
  8. neo

    neo Well-Known Member

    Joined:
    Mar 18, 2015
    Messages:
    672
    Likes Received:
    359
    Thanks for sharing this. I only briefly skimmed and did not get a chance to confirm anything. But, being such a simple option in an firmware could feasibly be modified. I am aware of various OEM firmware tools. Maybe I'll do a thorough investigation and a guide if there is enough interest.
     
    #108
  9. Nom

    Nom New Member

    Joined:
    Oct 5, 2015
    Messages:
    24
    Likes Received:
    1
    The Winyao cards are not copies of the Intel cards - take a look at - eBay Item 161414158278 - they use their own card designs, and the layouts are totally different.

    I don't know where Winyao source the Intel chips to drive their cards, but I don't class them the same as the "counterfeit" cards. Especially because Winyao is actually their real retail brand !

    DealExtreme sell both the 2 and 4 port versions, with free worldwide shipping - Winyao WYI350-T2 and Winyao WYI350-T4 if anyone is looking for a cheap not-made-by-Intel card. I've got a couple, and they work with the standard Intel ProSet driver packages.
     
    #109
    Last edited: Oct 5, 2015
  10. canta

    canta Well-Known Member

    Joined:
    Nov 26, 2014
    Messages:
    1,012
    Likes Received:
    184
    heheh, looks on PCI ID :p
    they did not spend a dome to get their own pci ID .
    it would goes to fake/counter...

    I already investigate some active component that based on their pictures, crappy quality and clones..
     
    #110
  11. neo

    neo Well-Known Member

    Joined:
    Mar 18, 2015
    Messages:
    672
    Likes Received:
    359
    Sorry, I am not going to beat a dead horse. This topic has been discussed in detail. However, you are entitled to your respective statements and I will simply end it there.

    I particularity find it suspicious you join and your first post encompasses that.
     
    #111
    Last edited: Oct 7, 2015
  12. RTM

    RTM Active Member

    Joined:
    Jan 26, 2014
    Messages:
    427
    Likes Received:
    142
    I for one don't see much a problem with Winyao NICs, while it is not super clear due to their naming conventions bearing some resemblance to Intels NICs, they are in fact different. Mind you, I don't consider them of equal quality as cards from the larger brands (Intel, Supermicro, HP, IBM, etc.), but the fact that you can distinguish them, allows you to make an educated guess as to whether or not you think they are worth buying.

    I consider them to be of same quality as Realtek based NICs, but with a better chip. And for some application this may well be acceptable.

    The cards that I would avoid are the ones that are actually fake/counterfeit, ie. the ones that are sold as real i350-t4 etc., because for obvious reasons you have no idea what you are actually getting.

    On another note, it might be interesting to compare some of the various "chinese" i350 quad port NICs, some like in post #0 are just clones of the i350-T4 but others are different, most use the MR-MACOM chips instead of Delta, but there are also these: http://i.ebayimg.com/images/g/uIgAAOSwEK9UC~1w/s-l1600.jpg
    I am not sold on your method of identifying "fake" cards, 8086:1521 appears to be very common for identifying i350 based cards.

    I have two i350 based NICs a Fujitsu quad port and a Winyao dual port (for PCIe X1 slot), both of which identify themselves as 8086:1521. The Fujitsu also mentions another value around Subsystem with "lspci -v" "11d1". If I am reading the output from pciconf (for pfsense) the Winyao uses an additional identifier of 1d1a.

    Of course even my Fujitsu card could be counterfeit, but I seriously doubt that is the case. If you think about it, it makes sense that the device first identifies itself as having an Intel device, then that it is uses an i350 chip and finally who actually made the card. All of these cards uses the same driver, and I see no reason why Intel would want to maintain a list of cards using this chip in their driver.

    This page, also indicates that the Supermicro AOC-SGP-I2, also uses 8086:1521.
     
    #112
  13. neo

    neo Well-Known Member

    Joined:
    Mar 18, 2015
    Messages:
    672
    Likes Received:
    359
    Everyone has the prerogative to purchase what they wish. I only wanted to shine light in a dim area.
     
    #113
    T_Minus and canta like this.
  14. canta

    canta Well-Known Member

    Joined:
    Nov 26, 2014
    Messages:
    1,012
    Likes Received:
    184
    Those are real Intel oem

    Those faker are using low quality components..

    If you make your own product. You have to register your own pci I'd. Since tour products are not oem

    Looks further on device Id. I know Dell and hphas unique number. Please read my previous posting.

    please let me lend my flashligh, would not you... hehehhe:
    *11d1 -> C600/X79 seriechipset PCI Express Root Port 1: your card is sitting on pci express root 1
    *1d1a ->C600/X79 series chipset PCI Express Root Port 6 : your card is sitting on pci express root 6

    8086:1521 has additional device ID.. on Intel product mostly have none ( this faker using intel PCI ID)
    some examples:
    8086:1521:1028 0602 , 1028 -> Dell product
    8086:1521:103c 2003 , 103c 0> HP product
    8086:1521:17aa 4005, 17AA -> Lenov Product

    8086:1521:8086 0002
    -> Intel product ( faker uses this pci id to piggy back intel driver update)

    some OEM product (I know IBM) using this 8086:1521:8086 XXXX , I believe they pay licenses directly to Intel instead of registering unique sub-vendor ID.

    on WinYao, I already posted, check active componets, ethernet transformer ballon on WinYao is not good as the real Intel OEM, you can find the spec in pdf.

    at the end all goes to you!.

    This page, also indicates thttp://accurev.raleigh.ibm.com:8080/accurev/WebGui.jsp?depot=OS4690&issueNum=1075&view=issuehat the Supermicro AOC-SGP-I2, also uses 8086:1521.
    8086:1521 is intel OEM product for i350... VendorID:roductID . why? this is needed for os to load appropirate kernel module/drive. EX: on linux will load igb kernel module.
     
    #114
    Last edited: Oct 6, 2015
  15. Nom

    Nom New Member

    Joined:
    Oct 5, 2015
    Messages:
    24
    Likes Received:
    1
    My WinYao cards look like the attached - their SUBSYS of 00001D1A doesn't appear in your list above. I don't know if it's unique to WinYao - anyone else have a match with a none-WinYao card ?

    There's some bad information a couple of pages back in this thread about the VendorID and the DeviceID - you should expect them to match the Intel IDs on every I350 card - genuine or fake.
    These two values are what your operating system uses to pick the correct driver - if a card is using an Intel I350 chip, then it can't change the VendorID or DeviceID - otherwise the drivers won't work !

    If you want a complete list of "supported by Intel" IDs, then you can grab the Windows drivers from Intel (I'm using the Windows 10 drivers at Download Network Adapter Driver for Windows® 10) and check out the driver .inf files. My I350 cards are using the e1r65x64.sys driver, and it's corresponding e1r65x64.inf file supports the following hardware. Note the very first line is a "catch all" of 8086 and 1521, so the driver is going to work no matter what SUBSYS lives on your card.
    The E15 code in the middle, marked "Section", is the code for which parts of the driver to implement - so all cards marked E1521.10.0.1 should be functionally identical.

    ; DisplayName Section DeviceID
    ; ----------- ------- --------
    %E1521NC.DeviceDesc% = E1521.10.0.1, PCI\VEN_8086&DEV_1521
    %E1521HPNCI4.DeviceDesc% = E1521.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_3380103C
    %E1521HPNCI2.DeviceDesc% = E1521.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_337F103C
    %E1521HPNCT2.DeviceDesc% = E1521.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_339E103C
    %E1523HPNCB2.DeviceDesc% = E1522.10.0.1, PCI\VEN_8086&DEV_1523&SUBSYS_18D1103C
    %E1523HPNCM4.DeviceDesc% = E1522.10.0.1, PCI\VEN_8086&DEV_1523&SUBSYS_339F103C
    %E1521HPNCR4.DeviceDesc% = E1521.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_17D1103C
    %E1523HPNC3I.DeviceDesc% = E1522.10.0.1, PCI\VEN_8086&DEV_1523&SUBSYS_1989103C
    %E1521HPNC7I.DeviceDesc% = E1521PM.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_2003103C
    %E1521HPNC4I.DeviceDesc% = E1521.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_2226103C
    %E1521NCELKF.DeviceDesc% = E1521.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_1F731028
    %E1521NCC.DeviceDesc% = E1521.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_008A1137
    %E1521NCC.DeviceDesc% = E1521.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_008B1137
    %E1521NCC.DeviceDesc% = E1521.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_008E1137
    %E1522NC.DeviceDesc% = E1522.10.0.1, PCI\VEN_8086&DEV_1522
    %E1521NCT4.DeviceDesc% = E1521PM.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_00018086
    %E1521NCT4.DeviceDesc% = E1521PM.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_00A18086
    %E1521NCT2.DeviceDesc% = E1521PM.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_00028086
    %E1521NCT2.DeviceDesc% = E1521PM.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_00A28086
    %E1522NCF4.DeviceDesc% = E1522PM.10.0.1, PCI\VEN_8086&DEV_1522&SUBSYS_00038086
    %E1522NCF4.DeviceDesc% = E1522PM.10.0.1, PCI\VEN_8086&DEV_1522&SUBSYS_00A38086
    %E1522NCF2.DeviceDesc% = E1522PM.10.0.1, PCI\VEN_8086&DEV_1522&SUBSYS_00048086
    %E1522NCF2.DeviceDesc% = E1522PM.10.0.1, PCI\VEN_8086&DEV_1522&SUBSYS_00A48086
    %E1522NCF1.DeviceDesc% = E1522PM.10.0.1, PCI\VEN_8086&DEV_1522&SUBSYS_00058086
    %E1521NC4P.DeviceDesc% = E1521PM.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_50018086
    %E1521NC2P.DeviceDesc% = E1521PM.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_50028086
    %E1521NCNDC4.DeviceDesc% = E1521.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_1F601028
    %E1521NCNDC2.DeviceDesc% = E1521.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_1F621028
    %E1523NC4P.DeviceDesc% = E1522.10.0.1, PCI\VEN_8086&DEV_1523&SUBSYS_1F528086
    %E1521NCLT2.DeviceDesc% = E1521.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_04CF1028
    %E1521NCLT2.DeviceDesc% = E1521.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_06021028
    %E1521NCX7NDC.DeviceDesc% = E1521.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_1F9A1028
    %E1523NCBNDC4.DeviceDesc% = E1522.10.0.1, PCI\VEN_8086&DEV_1523&SUBSYS_1F9B1028
    %E1523NC2P.DeviceDesc% = E1522.10.0.1, PCI\VEN_8086&DEV_1523&SUBSYS_06601028
    %E1521SEMT4.DeviceDesc% = E1521PM.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_7B16108E
    %E1521SLPT4.DeviceDesc% = E1521PM.10.0.1, PCI\VEN_8086&DEV_1521&SUBSYS_7B18108E
    %E1522SENF4.DeviceDesc% = E1522PM.10.0.1, PCI\VEN_8086&DEV_1522&SUBSYS_7B17108E
    %E1522SLPF2.DeviceDesc% = E1522PM.10.0.1, PCI\VEN_8086&DEV_1522&SUBSYS_7B19108E
    %E1523NC.DeviceDesc% = E1522.10.0.1, PCI\VEN_8086&DEV_1523
    %E1524NC.DeviceDesc% = E1524.10.0.1, PCI\VEN_8086&DEV_1524
    %E1533NC.DeviceDesc% = E1533.10.0.1, PCI\VEN_8086&DEV_1533
    %E1536NC.DeviceDesc% = E1536.10.0.1, PCI\VEN_8086&DEV_1536
    %E1537NC.DeviceDesc% = E1536.10.0.1, PCI\VEN_8086&DEV_1537
    %E1538NC.DeviceDesc% = E1538.10.0.1, PCI\VEN_8086&DEV_1538
    %E1533NC.DeviceDesc% = E1533.10.0.1, PCI\VEN_8086&DEV_157B
    %E1537NC.DeviceDesc% = E1536.10.0.1, PCI\VEN_8086&DEV_157C
    %E1533NCT1.DeviceDesc% = E1533.10.0.1, PCI\VEN_8086&DEV_1533&SUBSYS_00018086
    %E1533NCT1.DeviceDesc% = E1533.10.0.1, PCI\VEN_8086&DEV_1533&SUBSYS_00028086
    %E1533HPNCT1.DeviceDesc% = E1533.10.0.1, PCI\VEN_8086&DEV_1533&SUBSYS_0003103C
    %E1539NC.DeviceDesc% = E1539.10.0.1, PCI\VEN_8086&DEV_1539


    The "DisplayName" E15 codes correspond to the following hardware, as listed later in the inf file :

    E1521NC.DeviceDesc = "Intel(R) I350 Gigabit Network Connection"
    E1521NCC.DeviceDesc = "Cisco 1GigE I350 LOM"
    E1522NC.DeviceDesc = "Intel(R) I350 Gigabit Fiber Network Connection"
    E1523NC.DeviceDesc = "Intel(R) I350 Gigabit Backplane Connection"
    E1524NC.DeviceDesc = "Intel(R) I350 Gigabit Connection"
    E1521NCT4.DeviceDesc = "Intel(R) Ethernet Server Adapter I350-T4"
    E1521NCT2.DeviceDesc = "Intel(R) Ethernet Server Adapter I350-T2"
    E1521HPNCI4.DeviceDesc = "HP Ethernet 1Gb 4-port 366i Adapter"
    E1521HPNCI2.DeviceDesc = "HP Ethernet 1Gb 2-port 361i Adapter"
    E1521HPNCT2.DeviceDesc = "HP Ethernet 1Gb 2-port 361T Adapter"
    E1523HPNCB2.DeviceDesc = "HP Ethernet 1Gb 2-port 361FLB Adapter"
    E1523HPNCM4.DeviceDesc = "HP Ethernet 1Gb 4-port 366M Adapter"
    E1521HPNCR4.DeviceDesc = "HP Ethernet 1Gb 4-port 366FLR Adapter"
    E1523HPNC3I.DeviceDesc = "HP Ethernet 1Gb 2-port 363i Adapter"
    E1521HPNC7I.DeviceDesc = "HP Ethernet 1Gb 2-port 367i Adapter"
    E1521HPNC4I.DeviceDesc = "HP Ethernet 1Gb 1-port 364i Adapter"
    E1521NCELKF.DeviceDesc = "Intel(R) Gigabit 4P X520/I350 rNDC"
    E1521SEMT4.DeviceDesc = "Sun Quad Port GbE PCIe 2.0 ExpressModule, UTP"
    E1521SLPT4.DeviceDesc = "Sun Quad Port GbE PCIe 2.0 Low Profile Adapter, UTP"
    E1522SENF4.DeviceDesc = "Sun Quad Port GbE PCIe 2.0 ExpressModule, MMF"
    E1522SLPF2.DeviceDesc = "Sun Dual Port GbE PCIe 2.0 Low Profile Adapter, MMF"
    E1522NCF4.DeviceDesc = "Intel(R) Ethernet Server Adapter I350-F4"
    E1522NCF2.DeviceDesc = "Intel(R) Ethernet Server Adapter I350-F2"
    E1522NCF1.DeviceDesc = "Intel(R) Ethernet Server Adapter I350-F1"
    E1521NC4P.DeviceDesc = "Intel(R) Gigabit 4P I350-t Adapter"
    E1521NC2P.DeviceDesc = "Intel(R) Gigabit 2P I350-t Adapter"
    E1521NCNDC4.DeviceDesc = "Intel(R) Gigabit 4P I350-t rNDC"
    E1521NCNDC2.DeviceDesc = "Intel(R) Gigabit 4P X540/I350 rNDC"
    E1523NC4P.DeviceDesc = "Intel(R) Gigabit 4P I350-t Mezz"
    E1521NCLT2.DeviceDesc = "Intel(R) Gigabit 2P I350-t LOM"
    E1521NCX7NDC.DeviceDesc = "Intel(R) Gigabit 4P X710/I350 rNDC"
    E1523NCBNDC4.DeviceDesc = "Intel(R) Gigabit 4P I350 bNDC"
    E1523NC2P.DeviceDesc = "Intel(R) Gigabit 2P I350 LOM"
    E1533NC.DeviceDesc = "Intel(R) I210 Gigabit Network Connection"
    E1536NC.DeviceDesc = "Intel(R) I210 Gigabit Fiber Network Connection"
    E1537NC.DeviceDesc = "Intel(R) I210 Gigabit Backplane Connection"
    E1538NC.DeviceDesc = "Intel(R) I210 Gigabit Network Connection"
    E1533NCT1.DeviceDesc = "Intel(R) Ethernet Server Adapter I210-T1"
    E1533HPNCT1.DeviceDesc = "Intel(R) Ethernet I210-T1 GbE NIC"
    E1539NC.DeviceDesc = "Intel(R) I211 Gigabit Network Connection"

    One thing to note from this is that the DELL and Lenovo cards are probably direct clones of the Intel, because they don't need any special call-out in the driver.
    The HP cards look to use the same driver functions as their Intel counterparts, so it looks like the call-out for the HP cards is purely branding (they'll show an "HP" name in Device Manager within Windows).
     

    Attached Files:

    #115
    Last edited: Oct 6, 2015
  16. canta

    canta Well-Known Member

    Joined:
    Nov 26, 2014
    Messages:
    1,012
    Likes Received:
    184
    pci id list can be query on the net, go to linux pci id. you can see all vendor ID: product ID: device ID

    based on INF Requirements for PCI Devices - Windows 10 hardware dev
    • Device ID (DID) - 16-bit value located at offset 2
    • PCI device - An electrical component that conforms to the PCI Local Bus Specification, Revision 2.2
    • Revision ID (REV) - 8-bit value located at offset 8
    • Subsystem ID (SID) - 16-bit value located at offset 2E. The SID is the ID assigned by the manufacturer to uniquely identify the device.
    • Subsystem Vendor ID (SVID) - 16-bit value located at offset 2C. Note: The SVID is the ID assigned to the manufacturer by the PCI Special Interest Group (PCI SIG).
    • Vendor ID (VID) - 16-bit value located at offset 0.
    The following is an example of a typical PnP ID section of an INF file, with VID/DID and VID/DID/SID/SVIDentries:

    you can not find sub vendor ID (subsystem ID in Windows) : 00001D1A information.

    most driver when failed on lookup in driver installation, will land to VID/DID (microsoft way)
    Intel can lockdown, but they do not do. please look on the link on below note.

    on linux, the kernel only care vendor and product ID to load correct kernel module
    I2XX/I3XX will be loaded igb kernel module

    Iwould assume the sameway on other UN*X variances.
    note:
    I think, you should read FTDI Screws Up, Backs Down | Hackaday
    that is for USB :D, chinese maker clone well know USB ID :D, and the real chipmaker put a locked down. well at the end.. the lockdown was removed due on complains
     
    #116
    Last edited: Oct 6, 2015
  17. Nom

    Nom New Member

    Joined:
    Oct 5, 2015
    Messages:
    24
    Likes Received:
    1
    I remember that article well - they handled the situation very poorly :D

    Vendor and Device ID fiddling is well-known in the Windows world - people have been editing the .inf files for years to install chipmaker video drivers onto laptops with weird IDs etc.
    When signed-only drivers arrived in 64-bit Windows, it all got more difficult - but it is possible to change the hardware IDs yourself, on some devices, by reflashing firmware, so that you can use a different signed driver.
     
    #117
    Last edited: Oct 6, 2015
  18. canta

    canta Well-Known Member

    Joined:
    Nov 26, 2014
    Messages:
    1,012
    Likes Received:
    184
    haha, I bought a bunch of fake USB to serial :D, was scary hahah

    all is possible, when someone know on how to flash the hardware, many ghost factories in china :D and working officially on the real factory that produce intel products :D. one beauty working real and ghost area.

    I pull for newest PCI ID on linux
    1521 I350 Gigabit Network Connection
    1028 0602 Gigabit 2P I350-t LOM
    1028 1f60 Gigabit 4P I350-t rNDC
    1028 1f62 Gigabit 4P X540/I350 rNDC
    1028 ff9a Gigabit 4P X710/I350 rNDC
    103c 17d1 Ethernet 1Gb 4-port 366FLR Adapter
    103c 2003 Ethernet 1Gb 2-port 367i Adapter
    103c 2226 Ethernet 1Gb 1-port 364i Adapter
    103c 337f Ethernet 1Gb 2-port 361i Adapter
    103c 3380 Ethernet 1Gb 4-port 366i Adapter
    103c 339e Ethernet 1Gb 2-port 361T Adapter
    103c 8157 Ethernet 1Gb 4-port 366T Adapter
    108e 7b16 Quad Port GbE PCIe 2.0 ExpressModule, UTP
    108e 7b18 Quad Port GbE PCIe 2.0 Low Profile Adapter, UTP
    1093 7648 PCIe-8237R Ethernet Adapter
    1093 7649 PCIe-8236 Ethernet Adapter
    1093 76b1 PCIe-8237R-S Ethernet Adapter
    1093 775b PCIe-8237 Ethernet Adapter
    10a9 802a UV2-BaseIO dual-port GbE
    17aa 1074 ThinkServer I350-T4 AnyFabric
    17aa 4005 I350 Gigabit Network Connection
    8086 0001 Ethernet Server Adapter I350-T4
    8086 0002 Ethernet Server Adapter I350-T2
    8086 00a1 Ethernet Server Adapter I350-T4
    8086 00a2 Ethernet Server Adapter I350-T2
    8086 5001 Ethernet Server Adapter I350-T4
    8086 5002 Ethernet Server Adapter I350-T2

    as I understand, kernel only care of vendorID (8086):product ID (1521), the rest are for debunging and compatibility..

    three are 4 I350 product ID: 1521-1524 :D.
     
    #118
  19. Nom

    Nom New Member

    Joined:
    Oct 5, 2015
    Messages:
    24
    Likes Received:
    1
    Agreed - the Windows 10 drivers above support VEN_8086&DEV_1521, VEN_8086&DEV_1522, VEN_8086&DEV_1523 and VEN_8086&DEV_1524.

    The 1521 is "Intel(R) I350 Gigabit Network Connection".

    The 1522 are the Fibre cards - they're listed as "Intel(R) I350 Gigabit Fiber Network Connection" and "Intel(R) Ethernet Server Adapter I350-F1/I350-F2/I350-F4".

    The 1523 is listed as "Intel(R) I350 Gigabit Backplane Connection".

    And the 1524 is just "Intel(R) I350 Gigabit Connection".

    A fake card can potentially choose any of those four DeviceIDs and still work fine with the Intel drivers.
     
    #119
    canta likes this.
  20. canta

    canta Well-Known Member

    Joined:
    Nov 26, 2014
    Messages:
    1,012
    Likes Received:
    184
    only one I350 product ID that faker never use:
    1520 I350 Ethernet Controller Virtual Function

    this is for blade system that has fabric built-in :D


    the funny thing, I never see Broadcom fake NIC card , heheh
     
    #120
Similar Threads: Comparison Intel
Forum Title Date
Networking Intel D-1518 build for PFSense 10Gb SFP+ router Nov 8, 2019
Networking Are these Intel i350-t4 cards all fake? Nov 2, 2019
Networking Intel X710-AT2 and X710-TM4 Carlsville NICs Oct 24, 2019
Networking Intel SR-IOV VM to host switching? Oct 20, 2019
Networking Broadcom BCM57416 10Gbe vs Intel X550 10Gbe adapters? Sep 29, 2019

Share This Page