HEADS UP: Updated em/igb/ixgbe back in snapshots

darioj · Feb 23, 2014, 12:21 AM

Do you plan to list the cases these nics are considered stable or should we avoid them untill 2.2?

Thanks for trying!

Cheers
Dario

jason0 · Feb 24, 2014, 4:10 PM

Hello,

I have been having difficulties with the em drivers and bridging in 2.1-RELEASE. Does your message mean you are reverting to THESE drivers, or the ones before 2.1-RELEASE?

Thanks for your time!

–jason

stephenw10 · Feb 24, 2014, 4:37 PM

There were issues with bridging some types of interface, including em, that have been fixed in 2.1.1. These were independent of the driver version. You should try a 2.1.1 snapshot.
https://forum.pfsense.org/index.php/topic,66908.msg386279.html#msg386279

Steve

jimp · Feb 24, 2014, 4:35 PM

The em/igb/ixgbe drivers on 2.1.1 will be the same as those on 2.1-RELEASE

jason0 · Feb 24, 2014, 4:54 PM

I will try a snapshot very soon.

Thanks for your reply!

–jason

dostrow · Mar 3, 2014, 6:56 AM

A quick question looking for advice here. We had just purchased $25K worth of gear all with 4 ixgbe dual 10 gig card in them with the intention of using pfsense as our primary firewall going forward, this way was way more economical than going the Cisco/Juniper/Whathaveyou route given our need for 10 gig interfaces. All was well and good until we tried to get things working when the gear arrived last week. We were immediately hit by bug 3250 with 2.1-REL. Hearing that the drivers were more stable in 2.0.x we tried installing 2.0.3 only to find out that there was not adequate support for our RAID controllers and thus could not install. With previous 2.1.1 snapshots we got further but still suffered from the mbuf leak that eventually caused the systems to panic and crash. Now that the decision has been made to revert to the 2.1-REL versions of the drivers (which I agree is the right call to have made), we are basically stuck needing 2.2 (for which I can find no builds publicly available) for these boxes which were slated to go into production within a week. If you were in my shoes, had hardware which was already purchased and cannot be returned and a deadline that really can't move…what would you do?

Supermule · Mar 3, 2014, 7:38 AM

Run it en ESXi on your new hardware. Then it works fine.

dostrow · Mar 3, 2014, 8:15 AM

Definitely something to try, though somehow running my edge devices under a hypervisor makes me a little queasy, not to mention setting things up with BGP and CARP over virtual interfaces all running at 10 gig adds some odd complexity but if it is my only option so be it.

stephenw10 · Mar 3, 2014, 11:56 AM

Do you have a support subscription? If so I'd go straight to ESF who will have a much better handle on what can/can't be achieved by using whichever driver version might be available.
Do they run OK in 2.0.3? You could maybe reconfigure the disk controllers into some mode that is supported or there maybe backported drivers for 8.1.

Steve

athurdent · Mar 3, 2014, 1:09 PM

Maybe running pfSense from USB flash is an option?

qseb · Mar 4, 2014, 11:32 AM

Hello

is it still possible to insert manually new igb drivers to boot.conf for next 2.1.1 snaphots?
Currently, I have a 2.1.1 from january with new igb, how to extract modules?

stephenw10 · Mar 4, 2014, 11:46 AM

The drivers are compiled into the kernel so you can't extract them as modules. However if you did get hold of the modules there should be no problem loading them via loader.conf.local.

Steve

demco · Mar 4, 2014, 12:18 PM

Hi,

Anyone know if the snapshot dated 20140217-1607 contains the newer driver?

Tried the image on a Rangeley box and boot log seem to indicate no network driver.

pci0: <network, ethernet="">at device 20.0 (no driver attached)
pci0: <network, ethernet="">at device 20.1 (no driver attached)
pci0: <network, ethernet="">at device 20.2 (no driver attached)
pci0: <network, ethernet="">at device 20.3 (no driver attached)

Just want to confirm that it is the driver and not something else, before trying to build the new driver.

full boot log attached.

Thanks.

bootlog.txt</network,></network,></network,></network,>

qseb · Mar 4, 2014, 1:39 PM

@stephenw10:

The drivers are compiled into the kernel so you can't extract them as modules. However if you did get hold of the modules there should be no problem loading them via loader.conf.local.

Steve

Yes I saw kldstat not returning modules. How to get the igb module file?

stephenw10 · Mar 4, 2014, 1:50 PM

Compile it yourself.
Ask ESF nicely.
Search the forum, I think a few others have compiled newer modules but I also think that the version included in earlier 2.1.1 snapshots had patches.

They were removed from 2.1.1 for good reason though. I guess if it works at all for you that's better than than nothing.

Steve

eri-- · Mar 10, 2014, 9:28 PM

The drivers from HEAD have been enabled again in the snapshots after fixing the cause of panics.

Please try them again in later snapshots.

stephenw10 · Mar 10, 2014, 9:43 PM

Woot! ;D
Great news. Updating…
They are in current snapshots I presume? (08-Mar-2014) Or wait for new builds?

Steve

maverick_slo · Mar 11, 2014, 8:12 AM

So NEW drivers are again included?
Also em drivers?

Thanks!

maverick_slo · Mar 11, 2014, 3:51 PM

Huh only March 8 snapshots are available…
Something went wrong?

stephenw10 · Mar 11, 2014, 4:41 PM

The build server maybe not running for some other reason. The new drivers may be in the 8/3/14 build. Unfortunately we I …uh...can't check the (cough) tools. ;)
Logs show it built images successfully yesterday but hasn't uploaded them.
I'll check my test box.

Looks 8/3/14 is still using the 7.3.2 em driver so wait for a new snapshot.

[2.1.1-PRERELEASE][root@pfsense.localdomain]/root(1): uname -a
FreeBSD pfsense.localdomain 8.3-RELEASE-p14 FreeBSD 8.3-RELEASE-p14 #0: Sat Mar  8 12:47:31 EST 2014     root@snapshots-8_3-i386.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386  i386
[2.1.1-PRERELEASE][root@pfsense.localdomain]/root(2): sysctl dev.em
dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 7.3.2
dev.em.0.%driver: em

Steve