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

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

jimp · Mar 11, 2014, 5:09 PM

Builder VMs are offline at the moment, shuffling some things around again completely unrelated to anything else. Once things settle we'll fire them back up and get new snapshots out.

stephenw10 - you can get access to the tools repo if you follow the instructions on the list, mail in a copy of your ssh public key to the address given on the list in the thread.

stephenw10 · Mar 11, 2014, 5:43 PM

Yes, I realise I could but thanks. I haven't done so because this is the first time I've had reason to look at the tools repo. I have (currently) no need to modify or compile the code only occasionally reviewing what's been changed.

Steve

jasonlitka · Mar 12, 2014, 12:53 AM

@ermal:

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

Please try them again in later snapshots.

SWEET!

I'll update to a newer snapshot next week. Right now I'm in the middle of trying to migrate about 55TB of data from two failed storage arrays…

stephenw10 · Mar 13, 2014, 3:10 AM

em drivers back to current. :)

[2.1.1-PRERELEASE][root@pfsense.localdomain]/root(3): sysctl dev.em.0
dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 7.3.8

Steve

jasonlitka · Mar 13, 2014, 8:45 PM

@Jason:

SWEET!

I'll update to a newer snapshot next week. Right now I'm in the middle of trying to migrate about 55TB of data from two failed storage arrays…

So the good news is that it's not crashing any more.

The bad news is that I still seem to be hitting a pretty hard wall at ~2.1Gbit/s across 10Gb ix interfaces (tried both SFP+ Direct Attach and Intel SR optics with a 1M OM3 patch). Anyone have any thoughts on that? It's 2.1Gbit/s of TOTAL throughput, not in each direction.

sebastiannielsen · Mar 15, 2014, 10:19 PM

Shouldnt the first post and/or the thread title be edited to tell that the issue is now fixed and the drivers will be included in 2.1.1 then?

jimp · Mar 17, 2014, 12:55 PM

@sebastiannielsen:

Shouldnt the first post and/or the thread title be edited to tell that the issue is now fixed and the drivers will be included in 2.1.1 then?

Good point. I'll fix it.

adam65535 · Mar 18, 2014, 9:45 AM

Is there a way we can monitor major changes like this in drivers? Normally we would just follow the pfsense-tools git branch but I don't see that anymore.