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

ha11oga11o

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?

mcwtim

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

ha11oga11o

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.

doktornotor

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.

stephenw10

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

mcwtim

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

ha11oga11o

oke,

i turned off machine and ON, here it is:

http://pastebin.com/g2ViZsqA

cheers :)

ha11oga11o

@mcwtim

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

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

ha11oga11o

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

Im doomed :)

mcwtim

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"

ha11oga11o

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

stephenw10

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

ha11oga11o

One warm boot log is comming:

http://pastebin.com/VUcw8L6D

ha11oga11o

This is cold boot log:

http://pastebin.com/LjY0E6hq

BTW, ist that what you are looking for?

stephenw10

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

stephenw10

When they are detected paste the output of:

sysctl dev.em.0

There are some power saving features there I think.

Steve

ha11oga11o

Here it is

http://pastebin.com/tcTBudPj

stephenw10

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

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

ha11oga11o

@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 :)