Trouble with em devices in Nokia IP1260
-
I received a Nokia IP1260, but without any harddisks or CF card installed. I feared it was just a lump of iron, but then found out about pfSense. I've installed the embedded i386 version of pfSense 2.03. It works ok with the 10/100MB ports that are built in (4 fxp devices), but I can't get the four 1000-BASE-SX ports (Intel Pro/1000, em devices) on the option cards to work at all. pfSense insists that I can choose from 10-base-T, 100-base-TX or 1000-base-T. If I try to set the nics to 1000basesx using ifconfig, I get a ifconfig: SIOCSIFMEDIA (media): Device not configured error message, even if I specify full-duplex explicitly. Any ideas on how to fix this?
Cheers,
Camiel
-
And before you ask… Here's the dmesg output (with two of the 1000-BASE-SX ports removed because of mac address conflicts):
Copyright (c) 1992-2010 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 8.1-RELEASE-p13 #0: Fri Apr 12 11:10:09 EDT 2013
root@snapshots-8_1-i386.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386 i386
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2794.59-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0xf29 Family = f Model = 2 Stepping = 9
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=0x4400 <cnxt-id,xtpr>real memory = 1073741824 (1024 MB)
avail memory = 1032175616 (984 MB)
ACPI Error: A valid RSDP was not found (20100331/tbxfroot-309)
MPTable: <oem id ="" product="">FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 HTT threads
cpu0 (BSP): APIC ID: 0
cpu1 (AP/HT): APIC ID: 1
ioapic0: Assuming intbase of 0
ioapic1: Assuming intbase of 16
ioapic2: Assuming intbase of 32
ioapic2 <version 1.1="">irqs 32-47 on motherboard
ioapic1 <version 1.1="">irqs 16-31 on motherboard
ioapic0 <version 1.1="">irqs 0-15 on motherboard
ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_bss_fw, 0xc0712580, 0) error 1
wlan: mac acl policy registered
ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc0712620, 0) error 1
ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_monitor_fw, 0xc07126c0, 0) error 1
wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.
wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (wpi_fw, 0xc0891ba0, 0) error 1
ACPI Error: A valid RSDP was not found (20100331/tbxfroot-309)
ACPI: Table initialisation failed: AE_NOT_FOUND
ACPI: Try disabling either ACPI or apic support.
cryptosoft0: <software crypto="">on motherboard
padlock0: No ACE support.
pcib0: <mptable host-pci="" bridge="">pcibus 0 on motherboard
pci0: <pci bus="">on pcib0
pcib0: unable to route slot 4 INTA
pcib0: unable to route slot 4 INTB
cbb0: <ti1420 pci-cardbus="" bridge="">irq 12 at device 4.0 on pci0
cardbus0: <cardbus bus="">on cbb0
pccard0: <16-bit PCCard bus> on cbb0
cbb0: [FILTER]
cbb1: <ti1420 pci-cardbus="" bridge="">irq 12 at device 4.1 on pci0
cardbus1: <cardbus bus="">on cbb1
pccard1: <16-bit PCCard bus> on cbb1
cbb1: [FILTER]
pcib5: <mptable pci-pci="" bridge="">at device 5.0 on pci0
pci1: <pci bus="">on pcib5
pcib5: unable to route slot 4 INTA
pcib5: unable to route slot 5 INTA
pcib5: unable to route slot 6 INTA
pcib5: unable to route slot 7 INTA
fxp0: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0xec00-0xec3f mem 0xf0000000-0xf0000fff,0xf0020000-0xf003ffff irq 12 at device 4.0 on pci1
miibus0: <mii bus="">on fxp0
inphy0: <i82555 10="" 100="" media="" interface="">PHY 1 on miibus0
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: [ITHREAD]
fxp1: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0xe800-0xe83f mem 0xf0040000-0xf0040fff,0xf0060000-0xf007ffff irq 12 at device 5.0 on pci1
miibus1: <mii bus="">on fxp1
inphy1: <i82555 10="" 100="" media="" interface="">PHY 1 on miibus1
inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1: [ITHREAD]
fxp2: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0xe400-0xe43f mem 0xf0080000-0xf0080fff,0xf00a0000-0xf00bffff irq 12 at device 6.0 on pci1
miibus2: <mii bus="">on fxp2
inphy2: <i82555 10="" 100="" media="" interface="">PHY 1 on miibus2
inphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp2: [ITHREAD]
fxp3: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0xe000-0xe03f mem 0xf00c0000-0xf00c0fff,0xf00e0000-0xf00fffff irq 12 at device 7.0 on pci1
miibus3: <mii bus="">on fxp3
inphy3: <i82555 10="" 100="" media="" interface="">PHY 1 on miibus3
inphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp3: [ITHREAD]
isab0: <pci-isa bridge="">at device 15.0 on pci0
isa0: <isa bus="">on isab0
atapci0: <serverworks csb5="" udma100="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1400-0x140f at device 15.1 on pci0
ata0: <ata 0="" channel="">on atapci0
ata0: [ITHREAD]
ata1: <ata 1="" channel="">on atapci0
ata1: [ITHREAD]
pcib1: <mptable host-pci="" bridge="">pcibus 1 on motherboard
pcib2: <serverworks host="" to="" pci="" bridge(unknown="" chipset)="">pcibus 2 on motherboard
pci2: <pci bus="">on pcib2
pcib3: <mptable host-pci="" bridge="">pcibus 3 on motherboard
pci3: <pci bus="">on pcib3
pci3: <encrypt decrypt,="" network="" computer="" crypto="">at device 7.0 (no driver attached)
pcib4: <serverworks host="" to="" pci="" bridge(unknown="" chipset)="">pcibus 4 on motherboard
pci4: <pci bus="">on pcib4
pcib7: <mptable pci-pci="" bridge="">at device 6.0 on pci4
pci5: <pci bus="">on pcib7
em0: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.4="">port 0xcc00-0xcc3f mem 0xf0100000-0xf011ffff irq 25 at device 1.0 on pci5
em0: [FILTER]
em1: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.4="">port 0xc800-0xc83f mem 0xf0120000-0xf013ffff irq 26 at device 1.1 on pci5
em1: [FILTER]
pcib6: <serverworks host="" to="" pci="" bridge(unknown="" chipset)="">pcibus 6 on motherboard
pci6: <pci bus="">on pcib6
cpu0 on motherboard
cpu1 on motherboard
atrtc0: <at real="" time="" clock="">at port 0x70 irq 8 on isa0
ppc0: parallel port not found.
uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
uart0: [FILTER]
uart0: console (9600,n,8,1)
uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 on isa0
uart1: [FILTER]
RTC BIOS diagnostic error 8 <fixed_disk>Timecounters tick every 10.000 msec
IPsec: Initialized Security Association Processing.
ad0: 1953MB <sandisk sdcfx-2048="" hdx="" 3.22="">at ata0-master PIO4
SMP: AP CPU #1 Launched!
Trying to mount root from ufs:/dev/ufs/pfsense0
Configuring crash dumps…
Mounting filesystems...
Setting up embedded specific environment...
done.___
/ f \
/ p \/ Sense
\/ \
\/Welcome to pfSense 2.0.3-RELEASE ...
Creating symlinks...
.
.
.
done.
External config loader 1.0 is now starting...
ad0s3Launching the init system...
done.
Initializing...
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
done.
Starting device manager (devd)...
done.
Loading configuration...
.
.
.
done.
Updating configuration...
done.
Cleaning backup cache...
.
.
.
.
.
done.
Setting up extended sysctls...
done.
Setting timezone...
done.
Starting Secure Shell Services...
done.
Setting up polling defaults...
done.
Setting up interfaces microcode...
done.
Configuring LAGG interfaces...
done.
Configuring VLAN interfaces...
done.
Configuring QinQ interfaces...
done.
Configuring WAN interface...
done.
Configuring LAN interface...
Generating new MAC address.
done.
Syncing OpenVPN settings...
done.
Starting syslog...
done.
Configuring firewall
.
.
.
.
.
.
done.
Starting PFLOG...
done.
Setting up gateway monitors...
done.
Synchronizing user settings...
done.
Starting webConfigurator...
done.
Configuring CRON...
done.
Starting NTP time client...
Starting DNS forwarder...
done.
Configuring firewall
.
.
.
.
.
.
done.
Generating RRD graphs...
done.
Starting CRON...
done.
Bootup completeFreeBSD/i386 (nic-rtr-2.camicom.local) (console)
*** Welcome to pfSense 2.0.3-RELEASE-nanobsd (i386) on nic-rtr-2 ***
WAN (wan) -> em1 -> NONE (DHCP)
LAN (lan) -> fxp0 -> 172.16.254.253
OPT1 (opt1) -> fxp1 -> NONE
OPT2 (opt2) -> fxp2 -> NONE
OPT3 (opt3) -> fxp3 -> NONE
OPT4 (opt4) -> em0 -> NONE</sandisk></fixed_disk></at></pci></serverworks></intel(r)></intel(r)></pci></mptable></pci></serverworks></encrypt></pci></mptable></pci></serverworks></mptable></ata></ata></serverworks></isa></pci-isa></i82555></mii></intel></i82555></mii></intel></i82555></mii></intel></i82555></mii></intel></pci></mptable></cardbus></ti1420></cardbus></ti1420></pci></mptable></software></version></version></version></oem></cnxt-id,xtpr></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>
-
The standard first step for all these hardware-compatibility issues is to try pfSense 2.1-RCn (based on FreeBSD 8.3) and you might find it works. Since 2.1-RELEASE is right now in the build and final test process, if you wait 24 to 48 hours you might even have a final 2.1-RELEASE image available to try. (for hardware compatibility, 2.1-RCn and 2.1-RELEASE will be the same)
-
Downloading 2.1-RC2 now, will post results shortly…
-
Since 2.1-RELEASE is right now in the build and final test process, if you wait 24 to 48 hours you might even have a final 2.1-RELEASE image available to try.
Apologies for commenting here…
I couldn't find any post regarding pfSense 2.1 doing a final release. Could you please point me to the right post. Thanks!
-
2.1-RC2 behaves the same way…
-
The earlier Nokia boxes didn't use a standard PC BIOS so the operating system needed code that included specific platform knowledge of interrupt routing. FreeBSD doesn't include such knowledge of Nokia boxes.
There are FreeBSD loader variables that can be specified to override interrupt specifications apparently provided by the BIOS but without a fair bit of detailed knowledge of the specific hardware design you could spend many hours trying to guess the correct values.
If you want to tinker for a while to see what you can make work, by all means do so. But if you value your time and need to get something working quickly I suggest the Nokia box is not for you.