SOLVED: Nc380t not working after 2.2 upgrade

stephenw10

Well interesting that your box finds the Intel NICs no problem. Can you change the slot the card is in?
If you look at the logs the OS finds PCI bus 2 and fails to allocate some memory. Then it finds a bce NIC on PCI bus 2 and fails to attach to it. Then it finds PCI bus and again fails to allocate memory before finding another bce NIC on it and failing to attach.

Steve

keithmcp

It is interesting that it does that. Almost like it is trying to start but can't and tries again. Unfortunately, I cannot change slots as this system has only one PCI Express slot. Maybe something with the driver in Freebsd 10.1 versus 8.3?

keithmcp

Should I file a bug report on this one?

stephenw10

This is almost certainly a FreeBSD bug rather than a pfSense bug. If you can, try running FreeBSD 10.1. If that does exactly the same thing then file a bug report there.

Steve

charliem

@stephenw10:

Looks like you may have hit the same thing as this:
https://forum.pfsense.org/index.php?topic=84909.0
I don't think a solution has been found yet. :(

Steve

Edit: Typo

Yes, a workaround solution was found, suggested by John Baldwin:
https://forum.pfsense.org/index.php?topic=84909.msg475793#msg475793 Specifically:

hint.agp.0.disabled=1
in loader.conf fixes the problem. :)

Interesting, both systems have the same agp0 video device, and the comments in the bug report implicate agp, so maybe that will work here too. If that doesn't work, you could instead try:

debug.acpi.disabled="hostres"

I'm not sure debug.acpi.disabled is still an option on FreeBSD 10.1; it was on 9.0. Even if it doesn't fix the problem, looking at the dmesg difference with and without the debug option set may provide some insight. Oh, and those changes should go into /boot/loader.conf.local rather than /boot/loader.conf (otherwise the change(s) would not survive an upgrade).

stephenw10

That was only a few weeks ago. Clearly my memory is failing. ::)

Steve

keithmcp

Thanks charliem that did the trick. ;D

Yes, a workaround solution was found, suggested by John Baldwin:
https://forum.pfsense.org/index.php?topic=84909.msg475793#msg475793 Specifically:
Quote

hint.agp.0.disabled=1
in loader.conf fixes the problem. :)

The card is now found and working just like before. dmesg.boot now shows the card and both interfaces are showing up in pfsense. Thanks to John Baldwin too. My pfsense box is back!!

stephenw10

Nice. :)
You should put that in /boot/loader.conf.local, create the file. That gets copied across an update and is intended for custom loader tweaks like this.

Steve

keithmcp

I originally had it in the loader.conf and then read the entire post and saw that it should be in the .local file (as you mentioned). I created the .local file and added that plus the Intel license ack stuff also. So faro so good. :D

rekd0514

This fix does not seem to be working for me with a EXPI9301CT card. Any other ideas?

stephenw10

You're seeing the same memory allocation error in the boot log?

Steve

rekd0514

Never mind, I think the NIC randomly died on me. It is not being detected in Windows on another PC either now.

Just for future reference, how would you go about getting the dmesg.boot file or edit the loader.conf if you don't have access to the GUI. Can you do this by shell/SSH somehow? I don't have a VLAN capable switch, so I don't think I can get access to pfsense with only 1 NIC installed in it.

stephenw10

Yes, if you have ssh access you can use SCP to get the files directly from a connected client.

If you only have local console access you can view the boot files like:

cat /var/log/dmesg.boot

Or edit the loader.conf (or better loader.conf.local) like:

ee /boot/loader.conf.local

That will use the built in EasyEditor but you could use vi instead.

Steve