2.2-RELEASE (amd64) Intel cannot initialize Intel® PRO/1000 PT Dual



  • Hello all,

    im trying to setup new pfSense to check it before i upgrade from 2.1. have another box which will be actually production one and i bought Intel® PRO/1000 PT Dual Port Server Adapter which is x4 PCIEX. Well, i put it on x16 port and on another OS like windows works fine.

    But when i install 2.2 Release, theres no WAY it start. No way to be recognized as vlan capable adapter. Sometimes, just sometimes if pfSense boot on good mood and do some cleaning, checking and asking to assign WAN again, i got it work like em0 and em1. Then after enabling it as LAN and OPT1 interface, reboot pfSense everything goes downstream. Same problems again…

    Im complete n00b about any advance consoling, digging on files on HDD with that OS, but i think i could do copy/paste :)

    Now, if someone had same issue or even have clue whats happening to me, can you please give advice or point me to right direction?

    Heres system log, but im not sure is that enough,... i filtered it with "em0" word and got this: http://pastebin.com/re48tN7G

    Many thnx in advance :)


  • Netgate Administrator

    So have you tested this on 2.1.X or just 2.2?
    Exactly what NIC is it? Please show the output of 'pciconf -lv'.
    What hardware are you testing it in?

    Steve





  • See if it can be reproduced with FreeBSD 10.1; if so, report a bug upstream.  Seems like a popular adapter to have a problem like this, so I imagine it's been seen before if it's a FreeBSD issue.



  • Hello all,

    thank you for reply. Im using Fujitsu Ethernet Controller PRO/1000PT (Fujitsu material number: 88040024) on ASUS P5GC-MX/1333. And i can fit it only on PCIE x16 slot.
    Seems when i turn off and on machine it starts NIC properly. But when it restarts it does not power it on at all.
    I have feeling its motherboard related issue. Did anyone tried to place anything on this motherboard in PCIE x16 slot? I even updated BIOS, but have same issue. Its like motherboard does not power it up after soft reset. But at another hand, shouldn't it be something in driver to do that? I have "live cable" from another PC plugged in to see will it initialize or not.

    Just now im sitting and looking mine machines monitor on live CD says
    WAN em0 - No IP 
    LAN em1 - 192.168.1.1/24

    BUT, it does not show me other two adapters broadcom and realtek anymore. One is in PCI slot, and another is integrated. Please guys, dont shoot me at wall on first sight. Im trying to understand whats happening, dont expect from me to know things :)

    Anyways if someone find suitable to reply with any kind of info, guidance you are more than welcome :)

    Cheers!


  • Banned

    Is there any Intel logo on the NIC? :P



  • Well when i replaced that hardcored old thermal paste it says intel 82571


  • Banned

    As already requested, can you post the relevant 'pciconf -lv' output?



  • @doktornotor

    I must admit that i really dont know how to do that. Im googling last hour to find out, but cant find it anywhere. Maybe im looking at it, but dont know its that what im looking for.

    If you can explain how to get it i will.

    Thnx in advance.


  • Banned

    Well, log in via SSH and type that in the shell.



  • Or if using the GUI: Diagnostics tab> Command Prompt> Execute Shell command



  • Yup, finally i got it. I learn something here, thnx

    http://pastebin.com/fyT2yvvc

    Here arre intel dual adapter in slot PCIE x16, one realtek in pci slot, and integrated one.

    Hope this could help?



  • Was your paste truncated? I don't see an em0 device listed, just realtek and Atheros network devices.



  • No its not truncated, all is there. mine problem IS that sometimes that Intel is not powered on at all. Only when i shut down machine completely and power up back it works fine untill next soft reboot when shut downs completely.


  • Banned

    Uh. We obviously need to see the state when it IS detected. When it's not detected, there no info from pciconf or anything else.


  • Netgate Administrator

    Is detected on cold boot but not detected on warm boot -> disable power saving/standby features in the BIOS.

    We need pciconfig output from both conditions to see what is actually not detected. It's possible this isn't the NIC at all but some PCI bridge that is not recovering from low power state.

    Steve



  • That particular motherboard also has an advanced bios setting called 'slot power' change it to normal or higher from the default setting of 'auto'



  • oke,

    i turned off machine and ON, here it is:

    http://pastebin.com/g2ViZsqA

    cheers :)



  • @mcwtim

    it has auto, light,norma (where it was all time), heavy, and heavier

    Ill place it on Heavier, let see what will happen.



  • Nope, none of those BIOS settings works., Same issue all time :(

    Im doomed :)



  • Did you try stephenW10's suggestion? "Is detected on cold boot but not detected on warm boot -> disable power saving/standby features in the BIOS"



  • Tried everything, without ACPI wont boot at all, says error it need it. Theres not much power setting on this board im afraid.


  • Netgate Administrator

    Can we see your dmesg.boot from /var/log from a warm boot when the NICs are not detected.
    There's a bug that I've only seen on Supermicro boards (so far) that causes the driver not to attach due to a resource allocation that could come into play here. Shows up in the boot logs though.
    https://forum.pfsense.org/index.php?topic=84909.msg475793#msg475793

    Steve



  • One warm boot log is comming:

    http://pastebin.com/VUcw8L6D



  • This is cold boot log:

    http://pastebin.com/LjY0E6hq

    BTW, ist that what you are looking for?


  • Netgate Administrator

    Yes. Disappointingly error free though.  :-
    The bridge is detected and the bus connected to it is detected but not the NICs on that bus.
    Perhaps the NICs themselves are not waking up from  some low power mode. That was a known bug if recall…
    Nope was on the 82573 not 82571 like yours.

    Steve


  • Netgate Administrator

    When they are detected paste the output of:

    sysctl dev.em.0
    

    There are some power saving features there I think.

    Steve




  • Netgate Administrator

    Hmm, I think I was thinking of eee_control which doesn't seem likely. Though the default value has changed to 1 since 8.3.

    Steve



  • @ha11oga11o:

    Hello all,

    im trying to setup new pfSense to check it before i upgrade from 2.1. have another box which will be actually production one and i bought Intel® PRO/1000 PT Dual Port Server Adapter which is x4 PCIEX. Well, i put it on x16 port and on another OS like windows works fine.

    But when i install 2.2 Release, theres no WAY it start. No way to be recognized as vlan capable adapter. Sometimes, just sometimes if pfSense boot on good mood and do some cleaning, checking and asking to assign WAN again, i got it work like em0 and em1. Then after enabling it as LAN and OPT1 interface, reboot pfSense everything goes downstream. Same problems again…

    Im complete n00b about any advance consoling, digging on files on HDD with that OS, but i think i could do copy/paste :)

    Now, if someone had same issue or even have clue whats happening to me, can you please give advice or point me to right direction?

    Heres system log, but im not sure is that enough,... i filtered it with "em0" word and got this: http://pastebin.com/re48tN7G

    Many thnx in advance :)

    I have the same problem on an old ProLiant P4 server. To solve I had to configure better the IRQ under BIOS for the x16 port… hope that will help cheers



  • @epimeteo:

    @ha11oga11o:

    Hello all,

    im trying to setup new pfSense to check it before i upgrade from 2.1. have another box which will be actually production one and i bought Intel® PRO/1000 PT Dual Port Server Adapter which is x4 PCIEX. Well, i put it on x16 port and on another OS like windows works fine.

    But when i install 2.2 Release, theres no WAY it start. No way to be recognized as vlan capable adapter. Sometimes, just sometimes if pfSense boot on good mood and do some cleaning, checking and asking to assign WAN again, i got it work like em0 and em1. Then after enabling it as LAN and OPT1 interface, reboot pfSense everything goes downstream. Same problems again…

    Im complete n00b about any advance consoling, digging on files on HDD with that OS, but i think i could do copy/paste :)

    Now, if someone had same issue or even have clue whats happening to me, can you please give advice or point me to right direction?

    Heres system log, but im not sure is that enough,... i filtered it with "em0" word and got this: http://pastebin.com/re48tN7G

    Many thnx in advance :)

    I have the same problem on an old ProLiant P4 server. To solve I had to configure better the IRQ under BIOS for the x16 port… hope that will help cheers

    Thank you for tip,

    but im not sure this s++++ty board could have that advanced feature. I saw that IRQs are shared with 4 NICs. I think 16 and 17. Ill try to fiddle with it (if there's section to do so), and post results here.

    thanks :)