Can't detect intel quad nic- help please!



  • Hi,

    I have a lenovo M73 http://support.lenovo.com/en/documents/pd029601 that I intend to use for a Pfsense box.

    I bought this nic for the setup:  Intel Pro 1000 PT Quad 4 Ports PCI-E Gigabit - IBM 39Y6138

    But it's not being detected by pfsense - I see the 4 port lights blink when the machine is first powered up but that's it.  Note the M73 has a pcie3x16 slot which is what I'm plugging the nic into.  I've tried downgrading the slot in bios to version 1 but no luck.  Maybe this card is too out of date?

    Thanks for any help - I'm looking and some dud hardware here if I can't get it running.



  • @bkandor:

    I bought this nic for the setup:  Intel Pro 1000 PT Quad 4 Ports PCI-E Gigabit - IBM 39Y6138

    Search for 39Y6138 in the pfSense forum; it's come up a number of times in the past, and nothing good has come of it I'm afraid.



  • Wow,  for some reason I actually thought this card would just plug in and work.  :(

    Now that I'm gun shy - how do I find a quad nic that will actual work in a Low Profile, PCIe 3.0 x16 (40w max) such as found in this lenovo M73?  Suddenly this sounds challenging.





  • I discovered a few things,

    1: I put this card into another system,  plugged into a pcieX16 slot and windows 7 has no trouble with it.  It shows up in the device manager ready to go.

    2: I found this page: https://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=migr-5087756  - do you think this would help get in running in the Lenovo system?

    Thanks,



  • I put this card into another system,  plugged into a pcieX16 slot and windows 7 has no trouble with it.  It shows up in the device manager ready to go.

    Well then, all you have to do is wait for pfSense to come out on Windows 7 and you're all set…  :P

    Since pfSense is built on FreeBSD 10.1, you might want to take a look at the supported hardware for FreeBSD 10.1:

    https://www.freebsd.org/relnotes/CURRENT/hardware/support.html

    For any device you want to add to that box, check the list and then buy hardware that uses the supported chipset.



  • If you are using pfsense 2.2 put

    hint.agp.0.disabled=1

    in loader.conf.local

    It worked for me with intel cards and em driver.

    You might have to add

    hw.pci.enable_msix=0
    hw.pci.enable_msi=0

    I did it.



  • I will try that - the thing is that pfsense is still stuck in the startup loop for which I can't satisfy it.  i.e. asking 'setup vlans'  input wan interface name…

    So, I have to figure out how to get to command prompt to edit said files!!  :)  Thanks.

    *edit:  I've discovered this process is complicated as my display is being overwritten all the time by these errors:

    ugen0.2: <vendor 0x17ef="">at usbus0 (disconnected)

    They overwrite whatever is going on.  But I will persevere!</vendor>



  • Rebadged Intel NICs can be hit or miss. When reading about Intel NICs from other companies like IBM or HP, Intel mentioned that while their NICs may officially support certain features, many times the other companies modify the firmware in a way that break some of those features or those companies do not keep everything up to date.



  • Hmmm,  well as soon as I find a way to edit the loader.conf.local file  I'll know if it has a chance.

    If it doesn't work, I'm willing to get a new nic but now I'm paranoid about finding one that will work on this lenovo machine.  It's the only reason I own the lenovo, it has no other purpose.

    Thanks,



  • @deltix:

    If you are using pfsense 2.2 put

    hint.agp.0.disabled=1

    in loader.conf.local

    It worked for me with intel cards and em driver.

    You might have to add

    hw.pci.enable_msix=0
    hw.pci.enable_msi=0

    I did it.

    Hi Deltix,

    I tried the first line first, no change
    I tried adding the second and third lines, no change.

    Is there anything I can do with loading the em driver help?

    Note, in order to get to a shell,  I used the onboard realtek so the pfsense had at least a wan interface registered.  That allowed the setup to complete and gave me access to shell.  I do need to resolve the issue above regarding "ugen0.2: <vendor 0x17ef="">at usbus0 (disconnected)" error messages that repeat about every 30seconds.  They overwrite the screen, even in vi making it pretty funny trying to edit files.

    Thannks!</vendor>



  • "ugen0.2: <vendor 0x17ef="">at usbus0 (disconnected)"
    Look like a the FreeBSD kernel is fiting with some USB device.
    Shut them down to the max at bios level ?</vendor>



  • Thanks,  I tried disabling legacy support and shutting down all ports except the 2 used for mouse and keyboard.  I guess once I get to webgui I can turn them all off.



  • I always disable unnecessary ports. On this specific motherboard everything is disabled except VGA, PS2 and on-board NIC (realtek). I did have issues with USB and pfsense hanging on boot. Some googling pointed to known freebsd 10.1 bug. So I'm using PS2 keyboard. Motherboard is Intel D510MO. I'm still having issues with lowest EM port (EM0) not working properly, but that might be due to my riser card I think. It's VIA riser card that is not fully compatible with this motherboard. On-board realtek and dual HP NIC with Intel chip are OK. I just have another Intel NIC (EM0) populating first riser slot, but not using it.



  • Hi,

    So I ditched the old card and replaced it with a "Intel I350-T4 PCI-Express",  but I'm having even more trouble with this card.  It causes a fatal trap 12,  EEPROM is not valid.  And wont boot  :(



  • In scenarios like this I try not to get creative.  I would only run one that someone else was already running and was working fine.

    No sense volunteering to be a crash test dummy unless you have to.



  • I'm not trying to be creative at all, just economical.  I wanted a 4 port nic,  this is my second try.  Each time I thought I was buying something that would just plug and play, since others have had success with both.  Just bad luck I guess.



  • Ok, I flashed updated firmware to the i350 t4 and it is recognized no problem.  So… now what?  :)



  • Ummmmmm….  So now you have a pfsense with a LAN / WAN and 2 OPT ports?



  • Yes, actually 5 ports total counting the on board nic,  but i'll probably disable that one.  I have dual wan and a wifi/ap.  I wonder if I should plug the wifi/ap into the pfsense box or the switch?



  • Switch.



  • I've seen switch recommended over available NIC ports several times.  Why is that the recommended way?



  • Unless you need to have your AP on a separate subnet for isolation/firewalling/etc., you're better off to have your switch manage it's traffic rather than a pfSense NIC.

    You can still manage specific rules as for any other LAN device, but you're not forcing pfSense to handle ALL the traffic from the AP.

    It makes the best use of the available horsepower in your all your network devices.

    Just my $.02 YMMV  ;)



  • Is it because it's faster or more efficient if a switch handles the traffic from the WAP when on the same subnet?

    I'm in the same boat as the OP in that I bought one of the cheap i350 4 port NICs (~$120 on Ebay) as well.  I ended up putting the WAP on the switch, but I initially intended to put it on the NIC.  At the moment, 2 ports on the NIC are not in use.  Placing it on the NIC seemed like the logical choice since that's how I set it up on every router I've used at home (D-Links to Zyxel USGs).

    Thanks for the input.



  • @Waggles:

    Is it because it's faster or more efficient if a switch handles the traffic from the WAP when on the same subnet?

    Both.

    I'm in the same boat as the OP in that I bought one of the cheap i350 4 port NICs (~$120 on Ebay) as well.  I ended up putting the WAP on the switch, but I initially intended to put it on the NIC.  At the moment, 2 ports on the NIC are not in use.  Placing it on the NIC seemed like the logical choice since that's how I set it up on every router I've used at home (D-Links to Zyxel USGs).

    Thanks for the input.

    Home/dedicated routers often have dedicated internal hardware to make the use of multiple NIC ports in a bridged fashion more efficient than the general purpose approach of pfSense.

    Passing all your NIC traffic through the internal PCI/System data bus is less efficient, but gives far more flexibility in what hardware/packages can be used with pfSense.

    I know sometimes it feels like you're "wasting" a NIC in pfSense just because it doesn't get used, but at the current price of a reasonably good switch (10's of$) it's lousy bang for the buck trying to internally bridge pfSense NIC's just to save on a switch.  ;)


Log in to reply