Missing et1 on FX5621 VIA EDEN (1.2.1 RC1) !SOLVED!
-
While you wait for a better answer.
If this board isn't showing up, the output of dmesg and pciconf -lv will help tremendously in tracking down what is wrong. You can run these commands using the 'Command prompt' option in pfSense.
The freebsd-net mailing list (see the FreeBSD web site for details) is probably the right place to ask questions - though it would be interesting to see the output of the two commands above, as that may help people advise you further..
As a side note is VLAN supported on FX5621?
-
dmesg:
$ dmesg
Copyright
1992-2008 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.0-RELEASE-p3 #0: Tue Jul 29 04:09:57 EDT 2008
sullrich@freebsd7-releng_1_2.geekgod.com:/usr/obj.pfSense/usr/src/sys/pfSense.7
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: VIA/IDT Unknown (997.51-MHz 686-class CPU)
Origin = "CentaurHauls" Id = 0x6d0 Stepping = 0
Features=0xa7c9bbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,cmov,pat,clflush,acpi,mmx,fxsr,sse,sse2,tm,pbe>Features2=0x4181 <sse3,est,tm2,xtpr>real memory = 503316480 (480 MB)
avail memory = 478568448 (456 MB)
MPTable:<template etemplate =""></template></sse3,est,tm2,xtpr></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,cmov,pat,clflush,acpi,mmx,fxsr,sse,sse2,tm,pbe> -
$ pciconf -lv
hostb0@pci0:0:0:0: class=0x060000 card=0x03141106 chip=0x03141106 rev=0x00 hdr=0x00
class = bridge
subclass = HOST-PCI
hostb1@pci0:0:0:1: class=0x060000 card=0x13141106 chip=0x13141106 rev=0x00 hdr=0x00
class = bridge
subclass = HOST-PCI
hostb2@pci0:0:0:2: class=0x060000 card=0x23141106 chip=0x23141106 rev=0x00 hdr=0x00
class = bridge
subclass = HOST-PCI
hostb3@pci0:0:0:3: class=0x060000 card=0x00000000 chip=0x32081106 rev=0x00 hdr=0x00
class = bridge
subclass = HOST-PCI
hostb4@pci0:0:0:4: class=0x060000 card=0x43141106 chip=0x43141106 rev=0x00 hdr=0x00
class = bridge
subclass = HOST-PCI
hostb5@pci0:0:0:7: class=0x060000 card=0x00000000 chip=0x73141106 rev=0x00 hdr=0x00
class = bridge
subclass = HOST-PCI
pcib1@pci0:0:1:0: class=0x060400 card=0x00000000 chip=0xb1981106 rev=0x00 hdr=0x01
class = bridge
subclass = PCI-PCI
rl0@pci0:0:9:0: class=0x020000 card=0x813910ec chip=0x813910ec rev=0x10 hdr=0x00
class = network
subclass = ethernet
rl1@pci0:0:10:0: class=0x020000 card=0x813910ec chip=0x813910ec rev=0x10 hdr=0x00
class = network
subclass = ethernet
rl2@pci0:0:11:0: class=0x020000 card=0x813910ec chip=0x813910ec rev=0x10 hdr=0x00
class = network
subclass = ethernet
rl3@pci0:0:12:0: class=0x020000 card=0x813910ec chip=0x813910ec rev=0x10 hdr=0x00
class = network
subclass = ethernet
atapci0@pci0:0:15:0: class=0x01018f card=0x33491106 chip=0x52871106 rev=0x00 hdr=0x00
class = mass storage
subclass = ATA
atapci1@pci0:0:15:1: class=0x01018a card=0x05711106 chip=0x05711106 rev=0x07 hdr=0x00
class = mass storage
subclass = ATA
uhci0@pci0:0:16:0: class=0x0c0300 card=0x30381106 chip=0x30381106 rev=0x90 hdr=0x00
class = serial bus
subclass = USB
ehci0@pci0:0:16:4: class=0x0c0320 card=0x31041106 chip=0x31041106 rev=0x90 hdr=0x00
class = serial bus
subclass = USB
isab0@pci0:0:17:0: class=0x060100 card=0x32871106 chip=0x32871106 rev=0x00 hdr=0x00
class = bridge
subclass = PCI-ISA
hostb6@pci0:0:17:7: class=0x060000 card=0x287e1106 chip=0x287e1106 rev=0x00 hdr=0x00
class = bridge
subclass = HOST-PCI
pcib2@pci0:0:19:0: class=0x060400 card=0x00000000 chip=0x287b1106 rev=0x00 hdr=0x01
class = bridge
subclass = PCI-PCI
vgapci0@pci0:1:0:0: class=0x030000 card=0x33441106 chip=0x33441106 rev=0x01 hdr=0x00
class = display
subclass = VGA
pcib3@pci0:128:0:0: class=0x060400 card=0x00000000 chip=0x287c1106 rev=0x00 hdr=0x01
class = bridge
subclass = PCI-PCI
pcib4@pci0:128:0:1: class=0x060400 card=0x00000000 chip=0x287d1106 rev=0x00 hdr=0x01
class = bridge
subclass = PCI-PCI
et0@pci0:130:0:0: class=0x020000 card=0xed0011c1 chip=0xed0011c1 rev=0x01 hdr=0x00
class = network
subclass = ethernet -
As a side note is VLAN supported on FX5621?
I dont know - is there an easy way for me to check it?
-
Hmm can't see in the 7.0 release note that there should be support for et(4) nic's
http://www.freebsd.org/releases/7.0R/hardware.html
OpenBSD supports it http://www.freebsd.org/cgi/man.cgi?query=et&apropos=0&sektion=4&manpath=OpenBSD+4.3&format=html -
et driver is a new addition to the FreeBSD source tree AFTER 7.0 was released.
-
Ok, have been added http://cvstrac.pfsense.com/chngview?cn=23594
So the box only shows 1 nic et0.
And pfSense shows eth0 and not et0 as my guess would be. -
Ok, have been added http://cvstrac.pfsense.com/chngview?cn=23594
So the box only shows 1 nic et0.
And pfSense shows eth0 and not et0 as my guess would be.Im not at the box right now, but it might be et0 it shows - instead of eth0 (sorry 'bout that) :)
But this first Gb port is working (its my LAN I/F), but the second one doesn't show up. -
With regard to the "missing" GigE adapter. Neither the dmesg output nor the pciconf output show a PCI device without a matching driver.
A common hardware design for multiple LAN interfaces is to provide a distinct PCI device for each interface. Another model for multiple interfaces is for a single PCI device to provide multiple interfaces, for example a single PCI IDE controller can service two disks, a "master" and a "slave". By far the most common method in the networking world is for a PCI device to provide a single interface. Sometime over the last few months I came across a single PCI device that provided two LAN interfaces. If I recall correctly it was a SysKonnect device and the reason I was investigating it was the pfSense 1.2 was seeing only one interface. The FreeBSD 6.2 sk driver in pfSense 1.2 supported only one interface per PCI device. A later version of the driver added some code to support multiple interfaces per PCI device.
PERHAPS a similar situation exists here: a single PCI device actually provides two LAN interfaces. PERHAPS (because the driver is still very new), the driver doesn't yet have the logic to deal with multiple interfaces but it was put in the FreeBSD source tree because it was useful even though not as useful as it could be.
As I've looked a bit further into the dmesg output I noticed PCI bridges at devices 0.0 and 0.1 on pci bus 128. The only visible et (GigE) device is downstream of the bridge at 0.0. Maybe there should be another one downstream of the device at 0.1. A BIOS error might be preventing an et style device downstream of the bridge at 0.1 on pci bus 128 from being seen.
You may need to raise the issue with the manufacturers or someone more familiar with the hardware design details.
-
With regard to the "missing" GigE adapter. Neither the dmesg output nor the pciconf output show a PCI device without a matching driver.
A common hardware design for multiple LAN interfaces is to provide a distinct PCI device for each interface. Another model for multiple interfaces is for a single PCI device to provide multiple interfaces, for example a single PCI IDE controller can service two disks, a "master" and a "slave". By far the most common method in the networking world is for a PCI device to provide a single interface. Sometime over the last few months I came across a single PCI device that provided two LAN interfaces. If I recall correctly it was a SysKonnect device and the reason I was investigating it was the pfSense 1.2 was seeing only one interface. The FreeBSD 6.2 sk driver in pfSense 1.2 supported only one interface per PCI device. A later version of the driver added some code to support multiple interfaces per PCI device.
PERHAPS a similar situation exists here: a single PCI device actually provides two LAN interfaces. PERHAPS (because the driver is still very new), the driver doesn't yet have the logic to deal with multiple interfaces but it was put in the FreeBSD source tree because it was useful even though not as useful as it could be.
As I've looked a bit further into the dmesg output I noticed PCI bridges at devices 0.0 and 0.1 on pci bus 128. The only visible et (GigE) device is downstream of the bridge at 0.0. Maybe there should be another one downstream of the device at 0.1. A BIOS error might be preventing an et style device downstream of the bridge at 0.1 on pci bus 128 from being seen.
You may need to raise the issue with the manufacturers or someone more familiar with the hardware design details.
Thank you for your response.
I have installed the latest build (1.2.1-RC1-20080730-0232) and now suddenly i have et1 :)
I haven't changed anything (but the sw), so it believe that it's an improvement of the code.Anyway, I'm a happy man now ;D
-
dmesg after the problem is solved:
$ dmesg
Copyright 1992-2008 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.0-RELEASE-p3 #0: Wed Jul 30 01:57:54 EDT 2008
sullrich@freebsd7-releng_1_2.geekgod.com:/usr/obj.pfSense/usr/src/sys/pfSense.7
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: VIA/IDT Unknown (997.51-MHz 686-class CPU)
Origin = "CentaurHauls" Id = 0x6d0 Stepping = 0
Features=0xa7c9bbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,cmov,pat,clflush,acpi,mmx,fxsr,sse,sse2,tm,pbe>Features2=0x4181 <sse3,est,tm2,xtpr>real memory = 503316480 (480 MB)
avail memory = 478568448 (456 MB)
MPTable:<template etemplate =""></template></sse3,est,tm2,xtpr></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,cmov,pat,clflush,acpi,mmx,fxsr,sse,sse2,tm,pbe>