Crashing
-
yes, because I posted the link and you left the forum....
I know Win7 is no longer supported and is not an important OP system, but I didn't want everyone to download this key.I intended it only for you to help
I will reupload when you are online again
(then I pay attention to your activity) -
Found this https://www.reddit.com/r/PFSENSE/comments/frac4z/245_and_intel_pro1000_vt_quad_not_friends_anymore/
I have switched over to the built in nics (bce) and a fresh load to see if that makes a difference.
-
Now you are here?
-
-
Regardless, what I wrote is valid!
These are the Dell hardware FW upgrades under Win7 that need to be done, intel.inf, etc -
@DaddyGo Yes very valid!
-
-
-
@DaddyGo got it thanks a million
-
You welcome
if the FWs are out of date, FreeBSD cannot handle them
-
when you are done with the task, I will be at your disposal if you have any questions
-
Got everything I could update taken care of. The lifecycle controller would not run on win7pro. The intel card would not update, not support on that model. No update for the sata controller. BIOS has the latest update. On board NICs updated (going to disable them asap, they use a lot of cpu, suricata running). How do I switch the drivers from igb to em)? I am also open to any tips also.
Thanks
-
All right,
yes not everything can be updated, but the essential parts is done
have you just done a fresh installation from pfSense 2.4.5 and the automatic hardware detection add igb(4) to your Intel NIC?this may be interesting:
https://www.reddit.com/r/freebsd/comments/alpt9j/freebsd_112_to_120_upgrade_igb_moved_to_em/ -
yes fresh load
-
there are problems with the auto-selection for igb (4) driver?
do you experience the problem outlined in your first post?the igb(4) driver kit almost always works perfectly
-
@DaddyGo I don't know if it the card or the driver as it is still crashing , as I have stated above. Want to try a different driver, as I can not get another card right now.
-
it's harder to persuade pfSense not to use the automatically selected driver, since this will involve editing /boot/loader.conf.local file
edit: (you can load a driver module at boot (/boot/loader.conf.local) and it will override the in kernel auto - driver select.. It's obviously not recommended, but it is not impossible)
I would first do it to filter out any hardware failure so:
-remove the Intel card as I know exactly that (bce) Broadcom LOM works perfectly in the pfSense + Dell R210II configuration (as I mentioned in my configurations there are Broadcom ethernet controllers)
then we will know if Intel NIC alone or Intel NIC + Dell PCI bus compatibility is causing your issue
edit: as each operates separately on its own
-
Running fine on the built-in nic's.
-
perfect
You see, it's already clear what's wrong...
You can do two things:
- you experiment, but it can cost useless money, if it doesn't work and you buy one this (the compatibility of the I350 is legendary):
https://www.dell.com/en-au/work/shop/dell-intel-ethernet-i350-t-quad-port-1-gigabit-server-adapter-low-profile/apd/540-11333/networking
or
https://www.bargainhardware.co.uk/intel-i350-t4-quad-port-rj45-1gbps-low-profile-pcie-x4-nic
-or you go that way, which I have already experienced and you use a Broadcom T4 NIC (bce4), I know for sure it works:
https://www.bargainhardware.co.uk/broadcom-bcm5709-quad-port-rj45-1gbps-low-profile-pcie-x4-nic
(we use it without any problems)I'm sure with such a strong CPU, the (bce4) driver has no disadvantages when running pfSense
- you experiment, but it can cost useless money, if it doesn't work and you buy one this (the compatibility of the I350 is legendary):
