Socket 1155 support?
-
I tried PF 2.0 AMD64 latest on a Supermicro 1155 board with a Xeon E3 1280. PF did not detect the 82579LM, but did detect the 82574L. I did a quick test with 2 vlan's off the 82574L and it worked. It was only a 30 minute test but did seem to work.
I am sure eventually the 82579 will be supported.
John
It occurred to me that a Supermicro X9SCM-F with 2100T low-power core i3 processor would provide outstanding processing speed while using little more electricity than an atom.
Anyone use this board with pfSense? Too bleeding edge? What about the different NICs; Intel 82579LM and 82574L?
Edit: Gigabyte GA-6UASL3 looks like a nice dual Intel LAN board.
-
It is likely that if it isn't supported in 2.0 RC1 it won't be supported in the final release of 2.0 either. It would involve upgrading the underlying version of FreeBSD to add new hardware support, which I'd expect to be highly unlikely this far into the release process.
-
I'd think a sandybridge i3 would be massive overkill for anything but the heaviest of loads. Like hundreds of megabits of traffic over many interface, with squid, SSL, etc. On the other hand, they are pretty cheap :)
These new sandy bridge CPUs are ridiculously fast. I picked up a budget 3.1ghz motherboard/cpu/memory for about 150..
-
I'm contemplating using an i3 2100 with a MSI H61M-P23 (B3), but will pfSense work with UEFI?
Also, anybody have any numbers for how much power an i3 2100 pulls? It's 65W TDP, but what's the idle load like?
-
From what I can see, FreeBSD 8.2 supports the 82579LM NIC, but not FreeBSD 8.1. Sadly, I have a motherboard with two gigabit intel NIC, one a 82579L and one 82579LM. I wanted to pass the LM thru to my virtualized pfsense, but no point trying that until a driver is available, so for now, I have a pci-e 82579L NIC plugged in.
-
There's a good chance that backported drivers already exist for this NIC.
That said, if you can get an updated if_msk.ko compiled on an 8.1 system from an updated driver source, you can likely use that via loader.conf.local to override the in-kernel driver.
We've done this before for customers with quirky em/igb cards before.
Steve
Edit: Perhaps this one. I guess you would need the igb driver though.
-
@Bai:
I'm contemplating using an i3 2100 with a MSI H61M-P23 (B3), but will pfSense work with UEFI?
Also, anybody have any numbers for how much power an i3 2100 pulls? It's 65W TDP, but what's the idle load like?
Huh. I completely forgot that I posted this.
I ended up getting an i3 2100 with a Intel DH67CL. It's running a 2.5" drive with 3 Intel PCI gig nics. I don't have anything else connected to it.
It was pulling about 40W at idle, but I haven't swapped it over to actual use yet.
-
@Bai:
@Bai:
I'm contemplating using an i3 2100 with a MSI H61M-P23 (B3), but will pfSense work with UEFI?
Also, anybody have any numbers for how much power an i3 2100 pulls? It's 65W TDP, but what's the idle load like?
Huh. I completely forgot that I posted this.
I ended up getting an i3 2100 with a Intel DH67CL. It's running a 2.5" drive with 3 Intel PCI gig nics. I don't have anything else connected to it.
It was pulling about 40W at idle, but I haven't swapped it over to actual use yet.
For power consumption, you should had gone with the 2100T… I have small server running windows home server that I built for my house with a 2100T, 3 harddrives, lcd display, 2 fans.... about 35w without a load..
-
For power consumption, you should had gone with the 2100T… I have small server running windows home server that I built for my house with a 2100T, 3 harddrives, lcd display, 2 fans.... about 35w without a load..
Yeah, but it was more of a PITA to get, plus finding a full size motherboard for it. Getting just a regular 2100 was easier, and the extra power isn't a huge difference.
-
I just built a Sandy Bridge Pfsense 2 box, but instead of using an i3-2100, i used the cheaper, Pentium G620.
It's dual-core/2 threads, 2.6Ghz Sandy Bridge processor.
-
I built a i5 Sandy Bridge pfSense a couple of weeks back. Runs well.. except for the processor running hot due to poor air ventilation in my mini-ITX thermaltake enclosure.
