Jetway AD3INLANG not detected on Jetway NC9C-550-LF

Eend

Hello,

I just installed pfSense 2.0.1 i386 on my new Jetway NC9C-550-LF with a Jetway AD3INLANG daughter card. The AD3INLANG has three Intel 82541PI chips, but i can't get them to work.The two Realtek RTL8111E's on the MB are working fine.

I installed IPCop 2.0.3 i486, and it detected the daughtercard just fine.

Here is a snippet from pciconf -lv output:

re0@pci0:2:0:0: class=0x020000 card=0x816810ec chip=0x816810ec rev=0x06 hdr=0x00
    class      = network
    subclass   = ethernet
re1@pci0:3:0:0: class=0x020000 card=0x816810ec chip=0x816810ec rev=0x06 hdr=0x00
    class      = network
    subclass   = ethernet
atapci0@pci0:4:0:0:     class=0x010185 card=0x2363197b chip=0x2363197b rev=0x10 hdr=0x00
    class      = mass storage
    subclass   = ATA
none2@pci0:5:4:0:       class=0x020000 card=0x10708086 chip=0x10708086 rev=0x05 hdr=0x00
    class      = network
    subclass   = ethernet
none3@pci0:5:6:0:       class=0x020000 card=0x10708086 chip=0x10708086 rev=0x05 hdr=0x00
    class      = network
    subclass   = ethernet

I assume the none2 and none3 devices are two of the three Intel NICs on the daughterboard. But being a FreeBSD newbie i don't know what to do. Already tried to manually load the em driver:

[2.0.1-RELEASE][admin@pfsense.local]/root(1): kldload -v em
kldload: can't load em: No such file or directory

Help ???

stephenw10

The em driver is included in the kernel there is no need to load it manually.
If it isn't detected it's likely that the chip is more recent than the driver.
Interestingly the pci device ID (1070) is not listed at the pci dev database.
Try one of the 2.1 snapshots which have newer drivers.
http://snapshots.pfsense.org/
These are nightly builds that are subject to changes that may introduce bugs etc so don't use this for a production machine! ;)

Steve

Eend

I tried "pfSense-LiveCD-2.1-DEVELOPMENT-i386-20120624-2017", it's currently running from a USB CD-ROM drive. It's not a production firewall, so it doesn't really matter. As long as the basics work i'd be happy.

pciconf -lv output:


re0@pci0:2:0:0: class=0x020000 card=0x816810ec chip=0x816810ec rev=0x06 hdr=0x00
    class      = network
    subclass   = ethernet
re1@pci0:3:0:0: class=0x020000 card=0x816810ec chip=0x816810ec rev=0x06 hdr=0x00
    class      = network
    subclass   = ethernet
atapci0@pci0:4:0:0:     class=0x010185 card=0x2363197b chip=0x2363197b rev=0x10 hdr=0x00
    class      = mass storage
    subclass   = ATA
fxp0@pci0:5:4:0:        class=0x020000 card=0x10508086 chip=0x10508086 rev=0x05 hdr=0x00
    class      = network
    subclass   = ethernet
fxp1@pci0:5:6:0:        class=0x020000 card=0x10508086 chip=0x10508086 rev=0x05 hdr=0x00
    class      = network
    subclass   = ethernet

Well, i was expecting the em driver, not fxp. So i checked /var/log/dmesg.boot and found this:

fxp0: <intel 100="" 82801ba="" (d865)="" pro="" ve="" ethernet=""> port 0xec00-0xec3f mem 0xfe1000
fxp0: attaching PHYs failed
device_attach: fxp0 attach returned 6
fxp1: <intel 100="" 82801ba="" (d865)="" pro="" ve="" ethernet=""> port 0xe880-0xe8bf irq 19 at de
fxp1: attaching PHYs failed
device_attach: fxp1 attach returned 6</intel></intel>

But when i go back to the console and select option #1 "Assign Interfaces" i'm shown this:

Valid interfaces are:

re0   00:00:00:00:00:00   (up) RealTek 8168/8111 B/C/CP/D/DP/E PCIe Gigabit Ethernet
re1   00:00:00:00:00:00   (up) RealTek 8168/8111 B/C/CP/D/DP/E PCIe Gigabit Ethernet
usbus00   (up) Intel 82801G (ICH7) USB controller USB-A
usbus10   (up) Intel 82801G (ICH7) USB controller USB-B
usbus20   (up) Intel 82801G (ICH7) USB controller USB-C
usbus30   (up) Intel 82801G (ICH7) USB controller USB-D
usbus40   (up)

stephenw10

Hmm, very strange. :-\

Device drivers returning 6 means they failed to attach, which is not surprising since the fxp(4) is for 10/100 NICs only. Why it's trying to attach in the first place is because…
It's now reporting a different PCI device ID, 1050, which is wrong.

Also you shouldn't be given the choice of usb devices in the interface setup. Something odd is happening there.
I suggest you try a snapshot from, say, a week ago. I seem to remember reading about a problem with interfaces that may have been recently introduced.

Just check that you have the daughter card seated properly, there should be no way that the pci IDs get send incorrectly but perhaps a bad connection could do it. It looks to me like it should be 107C:8086.

Steve

Eend

I've found it. The daughtercard wasn't seated properly. I checked after i posted my previous message. But i shouldn't fiddle with hardware after working a 13 hour day :-[

All interfaces are up!

stephenw10

Ha! Can happen to anyone. ;)

Steve