Problems detecting intel network adapter
-
Heh guys !
Nice to see this thread is getting some attention !
I found the drivers on intel's page : http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=3024&DwnldID=15815&lang=eng
So there must be some hope even if the driver is not included in the stock kernel right ?!
I'm a big freebsd neewb but shouldn't it be possible to do like jneves10 and compile the driver on another machine and copy the driver to the pfsense installation and load it ?
I understand this could only be a temporary solution before upstream includes this driver but it could take months before those cards actually work out of the box and it would really be ashame to have to replace those expensive cards with something else:(
I also understand this is not pfsense's team's job to fix our problem here but if we are all in the same boat why not try to help out each other :P
Have a good weekend guys !
-
i'll have to withdraw my earlier comment. my dual port copper gig card is working now. i setup a second system (same motherboard) as a test bed for the primary pfsense box.
the chip is intel FW82546EB. i booted off the 1.2.3-RC1 live cd just now and I was able to detect both cards, each with 2 ports for a total of 4 gig ports. it's a PCIX133 card but runs at other speeds and can be had for very little on ebay. it uses the standard em0 intel gigabit driver automatically. no fiddling involved.
i'll try to do more testing to find why these didn't originally work when i was setting up my first pfsense box.
after further testing, the card works in both motherboards (tyan S2510). the bios revision is the same, the bios settings are very similar. i can only chalk this up to user error on my part.
-
Hello all, good news ! We managed to make it work, here is the procedure for people who are interested :
-1 Build yourself a freebsd 7.2 32bits box
-2 Build the intel drivers
-3 Copy the resulting .ko modules in the /boot/kernel/ and /boot/modules of the target pfsense box (we used 1.2.3RC3)
-4 Edit the /boot/loader.conf and add the if_igb_load="YES"You might need to clear some routes by using "route flush" and "route add default gateway_ip"
Reboot and enjoy !
Note : There might be an easier method to achieve this but this one worked for us :)
-
Hello all, good news ! We managed to make it work, here is the procedure for people who are interested :
-1 Build yourself a freebsd 7.2 32bits box
-2 Build the intel drivers
-3 Copy the resulting .ko modules in the /boot/kernel/ and /boot/modules of the target pfsense box (we used 1.2.3RC3)
-4 Edit the /boot/loader.conf and add the if_igb_load="YES"You might need to clear some routes by using "route flush" and "route add default gateway_ip"
Reboot and enjoy !
Note : There might be an easier method to achieve this but this one worked for us :)
This suggests igb is not built into the pfSense kernel. (If the igb driver was built into the kernel I would expect an error on loading the igb module due to duplicate symbols. But maybe the "Intel drivers" use carefully chosen symbol names to avoid conflict with those of the standard FreeBSD driver.)
-
Hi all,
Hope this is not too late to chime in.
I'm also using an Intel E1G42ET dual-port copper card (i believe it's an 82576 chip) with 1.2.3-RC3. I didn't need to do anything special as it detected the cards without any issues. The card is picked up as igb0 and igb1. No need to build the drivers.
All previous versions of pfsense would not detect the card.
However, my biggest beef with the igb driver is that VLANs and Traffic shaping will not work at all!!! I hope that these issues can be resolved soon or with 2.0 as I was hoping to use this card to handle more of the heavier traffic rather than relying on a pair of Intel CT desktop cards that I've stuffed into the box for "temporary" use. I'm still testing to see what works and what doesn't. So far everything is okay but it's unfortunate that these features are unavailable at the moment.
Oh well…...
-
However, my biggest beef with the igb driver is that VLANs and Traffic shaping will not work at all!!! I hope that these issues can be resolved soon or with 2.0 as I was hoping to use this card to handle more of the heavier traffic rather than relying on a pair of Intel CT desktop cards that I've stuffed into the box for "temporary" use. I'm still testing to see what works and what doesn't. So far everything is okay but it's unfortunate that these features are unavailable at the moment.
It looks like the arrays that keep track of this functionality were updated to include igb. You can edit /etc/inc/globals.inc and add igb to the list for vlans on line 79. You can then edit /etc/inc/interfaces.inc and add igb to the list starting on line 1511.
If you add it there and it works fine for both, then you may want to open a ticket at http://redmine.pfsense.org - although there are no plans for future 1.2.x releases, it may still get worked in somehow.
The detection in 2.0 is automatic, so these lists aren't used, so it would probably work there without any additional issues.
-
Thank you so much!!! I added igb to the two lines and both functions are working now. You've made a generally miserable grey day a little bit brighter.
I'll look forward to playing with 2.0 when time allows.
:D
-
Does anybody have the modules need, to get this to work? Or do I have to setup at FreeBSD 7.2 and make my own?
-
Does anybody have the modules need, to get this to work? Or do I have to setup at FreeBSD 7.2 and make my own?
A previous reply suggests the necessary driver is already built into pfSense 1,2.3 (lavinia 31-Dec-2009) but if you want VLANs or traffc shaping you will have to tweak a couple of text files. (See jimp's reply 31-Dec).
Have you tried pfSense 1.2.3 and found your NICs are not recognised?
-
Yes.
I have just recieved 2 x Dell PowerEdge R210 each with one Intel Gigabit ET Quad Port Server Adapter PCIe
I have installed pfSense 1.2.3 and can only find the onboard NIC's, then I have tryed with the 2.0 beta version and it can find the cards. What am I doing wrong?
-
I only have the 1.2.3 version from 08. dec 2009 http://pfsense.nsa.co.il/downloads/
Where do I find the 31. dec version?
-
I only have the 1.2.3 version from 08. dec 2009 http://pfsense.nsa.co.il/downloads/
Where do I find the 31. dec version?
The replies were date 31-Dec-2009 and I quoted that date to help you find the relevant replies. I didn't mean to imply there was a particular pfSense 1.2.3 build of 31-Dec-2009.
I have just recieved 2 x Dell PowerEdge R210 each with one Intel Gigabit ET Quad Port Server Adapter PCIe
I have installed pfSense 1.2.3 and can only find the onboard NIC's, then I have tryed with the 2.0 beta version and it can find the cards. What am I doing wrong?
Probably nothing. As time goes by manufacturers release NICs that are slightly different from previous versions (e.g. bug correction) and they have different identification codes from previous versions and so older drivers don't recognise them. If you post the dmesg output from the pfSense 1.2.3 startup 'll take a look and see if thats the problem.
-
Were going to buy one of these in combinaison of a good cpu, in a rackmount server.
The reference is E1G44ET, if anyone has feedback with QUAD Intel PCI-E card please help.
The vendor already has other reference as :
Intel PRO/1000 PT and Intel PRO/1000 GT.
The GT version seems a little less performance (no dedicated CPU hash), but seems more standard.The Intel PRO/1000 MT is in there too.
Any feedback on theses cards is highly appreciated, and please give the date of buy.
Many thanks, -
Ok i found several topics about theses cards, question seems common but scattered in multiple topics.
I will try my best to gather everything.I will post a new topic when all the hardware is working, in hope helping community. ;)
-
Wallabybob:
Sorry for the late reply, but I have tryed with many versions. It works just fine with version 2.0 but not 1.2.3
DMESG OUTPUT:
dmesg
Copyright
1992-2009 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.2-RELEASE-p5 #0: Sun Dec 6 23:20:31 EST 2009
sullrich@FreeBSD_7.2_pfSense_1.2.3_snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.7
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz (2394.00-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x106e5 Stepping = 5
Features=0xbfebfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>Features2=0x98e3fd <sse3,dtes64,mon,ds_cpl,vmx,smx,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,sse4.2,popcnt>AMD Features=0x28100000 <nx,rdtscp,lm>AMD Features2=0x1 <lahf>Cores per package: 8
Logical CPUs per core: 2
real memory = 3211366400 (3062 MB)
avail memory = 3136741376 (2991 MB)
ACPI APIC Table: <dell pe_sc3 ="">FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 2
cpu2 (AP): APIC ID: 4
cpu3 (AP): APIC ID: 6
ioapic0 <version 2.0="">irqs 0-23 on motherboard
wlan: mac acl policy registered
kbd1 at kbdmux0
cryptosoft0: <software crypto="">on motherboard
padlock0: No ACE support.
acpi0: <dell pe_sc3="">on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
unknown: I/O range not supported
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
acpi_hpet0: <high precision="" event="" timer="">iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
pci0: <acpi pci="" bus="">on pcib0
pcib1: <acpi pci-pci="" bridge="">at device 3.0 on pci0
pci1: <acpi pci="" bus="">on pcib1
pcib2: <pci-pci bridge="">at device 0.0 on pci1
pci2: <pci bus="">on pcib2
pcib3: <pci-pci bridge="">at device 2.0 on pci2
pci3: <pci bus="">on pcib3
pci3: <network, ethernet="">at device 0.0 (no driver attached)
pci3: <network, ethernet="">at device 0.1 (no driver attached)
pcib4: <pci-pci bridge="">at device 4.0 on pci2
pci4: <pci bus="">on pcib4
pci4: <network, ethernet="">at device 0.0 (no driver attached)
pci4: <network, ethernet="">at device 0.1 (no driver attached)
pci0: <base peripheral=""> at device 8.0 (no driver attached)
pci0: <base peripheral=""> at device 8.1 (no driver attached)
pci0: <base peripheral=""> at device 8.2 (no driver attached)
pci0: <base peripheral=""> at device 8.3 (no driver attached)
pci0: <base peripheral=""> at device 16.0 (no driver attached)
pci0: <base peripheral=""> at device 16.1 (no driver attached)
ehci0: <ehci (generic)="" usb="" 2.0="" controller="">mem 0xde8fa000-0xde8fa3ff irq 22 at device 26.0 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb0: waiting for BIOS to give up control
usb0: EHCI version 1.0
usb0: <ehci (generic)="" usb="" 2.0="" controller="">on ehci0
usb0: USB revision 2.0
uhub0: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usb0
uhub0: 2 ports with 2 removable, self powered
uhub1: <vendor 2="" 9="" 0x8087="" product="" 0x0020,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">on uhub0
uhub1: single transaction translator
uhub1: 6 ports with 6 removable, self powered
pcib5: <acpi pci-pci="" bridge="">at device 28.0 on pci0
pci5: <acpi pci="" bus="">on pcib5
bce0: <broadcom netxtreme="" ii="" bcm5716="" 1000base-t="" (c0)="">mem 0xd8000000-0xd9ffffff irq 16 at device 0.0 on pci5
miibus0: <mii bus="">on bce0
ukphy0: <generic ieee="" 802.3u="" media="" interface="">PHY 1 on miibus0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
bce0: Ethernet address: 00:26:b9:8a:4e:f8
bce0: [ITHREAD]
bce0: ASIC (0x57092008); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C (0x05000B05); Flags( MFW MSI )
bce1: <broadcom netxtreme="" ii="" bcm5716="" 1000base-t="" (c0)="">mem 0xda000000-0xdbffffff irq 17 at device 0.1 on pci5
miibus1: <mii bus="">on bce1
ukphy1: <generic ieee="" 802.3u="" media="" interface="">PHY 1 on miibus1
ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
bce1: Ethernet address: 00:26:b9:8a:4e:f9
bce1: [ITHREAD]
bce1: ASIC (0x57092008); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C (0x05000B05); Flags( MFW MSI )
ehci1: <ehci (generic)="" usb="" 2.0="" controller="">mem 0xde8fc000-0xde8fc3ff irq 22 at device 29.0 on pci0
ehci1: [GIANT-LOCKED]
ehci1: [ITHREAD]
usb1: EHCI version 1.0
usb1: <ehci (generic)="" usb="" 2.0="" controller="">on ehci1
usb1: USB revision 2.0
uhub2: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usb1
uhub2: 2 ports with 2 removable, self powered
uhub3: <vendor 2="" 9="" 0x8087="" product="" 0x0020,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">on uhub2
uhub3: single transaction translator
uhub3: 8 ports with 8 removable, self powered
ukbd0: <logitech 0="" 3="" logitech="" illuminated="" keyboard,="" class="" 0,="" rev="" 2.00="" 55.00,="" addr="">on uhub3
kbd2 at ukbd0
uhid0: <logitech 0="" 3="" logitech="" illuminated="" keyboard,="" class="" 0,="" rev="" 2.00="" 55.00,="" addr="">on uhub3
uhub4: <vendor 4="" 9="" 0x0424="" product="" 0x2514,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">on uhub3
uhub4: multiple transaction translators
uhub4: 4 ports with 4 removable, self powered
pcib6: <acpi pci-pci="" bridge="">at device 30.0 on pci0
pci6: <acpi pci="" bus="">on pcib6
vgapci0: <vga-compatible display="">mem 0xd7800000-0xd7ffffff,0xdc7fc000-0xdc7fffff,0xdc800000-0xdcffffff irq 19 at device 3.0 on pci6
isab0: <pci-isa bridge="">at device 31.0 on pci0
isa0: <isa bus="">on isab0
atapci0: <intel ahci="" controller="">port 0xdcd0-0xdcd7,0xdcc8-0xdccb,0xdcd8-0xdcdf,0xdccc-0xdccf,0xdce0-0xdcff mem 0xde8fe000-0xde8fe7ff irq 20 at device 31.2 on pci0
atapci0: [ITHREAD]
atapci0: AHCI Version 01.30 controller with 6 ports detected
ata2: <ata 0="" channel="">on atapci0
ata2: [ITHREAD]
ata3: <ata 1="" channel="">on atapci0
ata3: [ITHREAD]
ata4: <ata 2="" channel="">on atapci0
ata4: [ITHREAD]
ata5: <ata 3="" channel="">on atapci0
ata5: [ITHREAD]
ata6: <ata 4="" channel="">on atapci0
ata6: [ITHREAD]
ata7: <ata 5="" channel="">on atapci0
ata7: [ITHREAD]
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
sio0: [FILTER]
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
sio1: [FILTER]
cpu0: <acpi cpu="">on acpi0
est0: <enhanced speedstep="" frequency="" control="">on cpu0
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 13
device_attach: est0 attach returned 6
p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
cpu1: <acpi cpu="">on acpi0
est1: <enhanced speedstep="" frequency="" control="">on cpu1
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 13
device_attach: est1 attach returned 6
p4tcc1: <cpu frequency="" thermal="" control="">on cpu1
cpu2: <acpi cpu="">on acpi0
est2: <enhanced speedstep="" frequency="" control="">on cpu2
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 13
device_attach: est2 attach returned 6
p4tcc2: <cpu frequency="" thermal="" control="">on cpu2
cpu3: <acpi cpu="">on acpi0
est3: <enhanced speedstep="" frequency="" control="">on cpu3
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 13
device_attach: est3 attach returned 6
p4tcc3: <cpu frequency="" thermal="" control="">on cpu3
pmtimer0 on isa0
orm0: <isa option="" roms="">at iomem 0xc0000-0xc7fff,0xc8000-0xc8fff,0xec000-0xeffff pnpid ORM0000 on isa0
ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0
ata0: [ITHREAD]
ata1 at port 0x170-0x177,0x376 irq 15 on isa0
ata1: [ITHREAD]
sc0: <system console="">at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounters tick every 1.000 msec
IPsec: Initialized Security Association Processing.
ad4: 152587MB <wdc wd1602abks-18n8a0="" 02.03b04="">at ata2-master SATA300
acd0: DVDROM <teac dvd-rom="" dv-28sw="" r.2a="">at ata5-master SATA150
SMP: AP CPU #2 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #1 Launched!
Trying to mount root from ufs:/dev/ad4s1a
pflog0: promiscuous mode enabled
bce0: link state changed to UP</teac></wdc></generic></system></isa></cpu></enhanced></acpi></cpu></enhanced></acpi></cpu></enhanced></acpi></cpu></enhanced></acpi></ata></ata></ata></ata></ata></ata></intel></isa></pci-isa></vga-compatible></acpi></acpi></vendor></logitech></logitech></vendor></intel></ehci></ehci></generic></mii></broadcom></generic></mii></broadcom></acpi></acpi></vendor></intel></ehci></ehci></network,></network,></pci></pci-pci></network,></network,></pci></pci-pci></pci></pci-pci></acpi></acpi></acpi></acpi></high></dell></software></version></dell ></lahf></nx,rdtscp,lm></sse3,dtes64,mon,ds_cpl,vmx,smx,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,sse4.2,popcnt></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe> -
If it helps, i can put it online and give you root access. But i need a solution i Can replicate ok more serveres. Right now i have 2 serveres where i have this setup.
-
The drivers included in pfSense 1.2.3 don't recognise your NICs. The drivers in pfSense 2.0 BETA do recognise your NICs. Go with pfSense 2.0 BETA or backport the FreeBSD 8.0 driver to FreeBSD 7.2 and build your own variant of pfSense 1.2.3.
-
Wallabybob: Thanks for you reply.
I don't think the 2.0 beta will be the best choise, because it should be used in a production enviroment for our hosting facilities.
Im not a FreeBSD guru so i need som help creating my own drivers for it. Have you an guide for doing that or maybe another who have created the driver will sent it to me?
-
Im not a FreeBSD guru so i need som help creating my own drivers for it. Have you an guide for doing that or maybe another who have created the driver will sent it to me?
The drivers are built into the kernel. Though FreeBSD supports loadable drivers I don't know if its possible to load a driver to supersede one already built into the kernel. In this case probe order wouldn't be a problem since the driver in the kernel doesn't recognise your NICs. But maybe the module loader would choke on trying to load a kernel module with global symbols that already exist in the kernel. Since the driver is built from a number of source files it almost has global symbols to allow calls "between the source files".
I suspect creating your own driver to replace one already built into the kernel is "unexplored territory" and consequently could turn out to relatively easy or quite involved. I suspect its unlikely you will find a guide covering exactly this circumstance.
