WatchGuard x750e Hard drive install
-
As Requested:
ad1: setting UDMA33
ad1: 28615MB <ic25n030atmr04 0="" moaoad0a="">at ata0-slave UDMA33
ad1: 58605120 sectors [58140C/16H/63S] 16 sectors/interrupt 1 depth queue
ad1: Intel check1 failed
ad1: Adaptec check1 failed
ad1: LSI (v3) check1 failed
ad1: LSI (v2) check1 failed
ad1: FreeBSD check1 failedRebooting... /boot.config: -D Consoles: internal video/keyboard serial port BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS 638kB/515072kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 (root@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org, Mon Dec 12 17:10:52 EST 2011) Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x8a1d18 data=0x3c9e54+0x9b6a0 syms=[0x4+0x94100+0x4+0xcaf47] / ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ ³ ³ ³ ³ ³ ³ Welcome to pfSense! ³ ³ ³ ______ ³ ³ / \ ³ 1\. Boot pfSense [default] ³ _____/ f \ ³ 2\. Boot pfSense with ACPI enabled ³ / \ / ³ 3\. Boot pfSense using USB device ³ / p \______/ Sense ³ 4\. Boot pfSense in Safe Mode ³ \ / \ ³ 5\. Boot pfSense in single user mode ³ \_____/ \ ³ 6\. Boot pfSense with verbose logging ³ \ / ³ 7\. Escape to loader prompt ³ \______/ ³ 8\. Reboot ³ ³ ³ ³ ³ ³ ³ ³ Select option, [Enter] for default ³ ³ or [Space] to pause timer 1 ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ Type '?' for a list of commands, 'help' for more detailed help. OK OK 7 OK boot -v SMAP type=01 base=0000000000000000 len=000000000009f800 SMAP type=02 base=00000000000f0000 len=0000000000010000 SMAP type=02 base=00000000fec00000 len=0000000000001000 SMAP type=02 base=00000000fee00000 len=0000000000001000 SMAP type=02 base=00000000ffb00000 len=0000000000500000 SMAP type=02 base=00000000e0000000 len=0000000010000000 SMAP type=02 base=000000000009f800 len=0000000000000800 SMAP type=01 base=0000000000100000 len=000000001f700000 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-p6 #0: Mon Dec 12 17:33:39 EST 2011 root@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_wrap.8.i386 i386 Preloaded elf kernel "/boot/kernel/kernel" at 0xc1269000. Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 1300053505 Hz CPU: Intel(R) Celeron(R) M processor 1300MHz (1300.05-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x695 Family = 6 Model = 9 Stepping = 5 Features=0xa7e1fbbf <fpu,vme,de,pse,tsc,msr,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,dts,acpi,mmx,fxsr,sse,sse2,tm,pbe>Instruction TLB: 4 KB Pages, 4-way set associative, 128 entries Data TLB: 4 KB Pages, 4-way set associative, 128 entries Instruction TLB: 4 MB pages, fully associative, 2 entries 2nd-level cache: 512 KB, 4-way set associative, 64 byte line size 1st-level instruction cache: 32 KB, 8-way set associative, 64 byte line size Data TLB: 4 MB Pages, 4-way set associative, 8 entries 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size real memory = 528482304 (504 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000001426000 - 0x000000001eeddfff, 497778688 bytes (121528 pages) avail memory = 498069504 (474 MB) ACPI Error: A valid RSDP was not found (20100331/tbxfroot-309) MP Configuration Table version 1.4 found at 0xc00f0c00 APIC: Using the MPTable enumerator. SMP: Added CPU 0 (BSP) MPTable: <oem00000 prod00000000="">bios32: Found BIOS32 Service Directory header at 0xc00f9930 bios32: Entry = 0xf9f40 (c00f9f40) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0x9f70 pnpbios: Found PnP BIOS data at 0xc00faa60 pnpbios: Entry = f0000:aa90 Rev = 1.0 Other BIOS signatures found: ULE: setup cpu 0 ioapic0: Assuming intbase of 0 ioapic0: Routing external 8259A's -> intpin 0 ioapic0: Routing IRQ 0 -> intpin 2 lapic: Routing ExtINT -> LINT0 lapic: Routing NMI -> LINT1 ioapic0 <version 2.0="">irqs 0-23 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 netisr_init: forcing maxthreads to 1 and bindthreads to 0 for device polling firmware: 'mxge_ethp_z8e' version 377876: 117102 bytes loaded at 0xc0f5d1e0 firmware: 'mxge_rss_eth_z8e' version 553468: 154580 bytes loaded at 0xc0f79be0 firmware: 'mxge_rss_ethp_z8e' version 563868: 155786 bytes loaded at 0xc0f9f840 firmware: 'iwn1000fw' version 0: 335056 bytes loaded at 0xc0d8ca30 firmware: 'iwn4965fw' version 0: 187972 bytes loaded at 0xc0dde778 wlan: mac acl policy registered firmware: 'iwn5000fw' version 0: 353240 bytes loaded at 0xc0e0c634 firmware: 'iwn5150fw' version 0: 337400 bytes loaded at 0xc0e62a84 wlan: <802.11 Link Layer> firmware: 'rt2561fw' version 0: 8192 bytes loaded at 0xc0fc9070 firmware: 'rt2561sfw' version 0: 8192 bytes loaded at 0xc0fcb0e8 firmware: 'rt2661fw' version 0: 8192 bytes loaded at 0xc0fcd160 firmware: 'rt2860fw' version 0: 8192 bytes loaded at 0xc0fcf1d8 firmware: 'iwn6000fw' version 0: 462280 bytes loaded at 0xc0eb50f4 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, 0xc0710010, 0) error 1 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, 0xc07100b0, 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, 0xc0883050, 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, 0xc0710150, 0) error 1 firmware: 'mw88W8363fw' version 0: 94940 bytes loaded at 0xc0f28ca4 firmware: 'mwlboot' version 0: 2280 bytes loaded at 0xc0f3ff80 firmware: 'mxge_eth_z8e' version 367564: 116477 bytes loaded at 0xc0f40a60 random: <entropy source,="" software,="" yarrow="">mem: <memory>Pentium Pro MTRR support enabled nfslock: pseudo-device crypto: <crypto core="">io: _null: <null device,="" zero="" device="">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. npx0: INT 16 interface cryptosoft0: <software crypto="">on motherboard crypto: assign cryptosoft0 driver id 0, flags 100663296 crypto: cryptosoft0 registers alg 1 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 2 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 3 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 4 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 5 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 16 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 6 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 7 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 18 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 19 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 20 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 8 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 15 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 9 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 10 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 13 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 14 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 11 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 21 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 17 flags 0 maxoplen 0 padlock0: No ACE support. pci_open(1): mode 1 addr port (0x0cf8) is 0x8000f904 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=25908086) pcibios: BIOS version 3.00 PCIe: Memory Mapped configuration base @ 0xe0000000 pcib0: <mptable host-pci="" bridge="">pcibus 0 on motherboard pci0: <pci bus="">on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x8086, dev=0x2590, revid=0x04 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x2090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x2592, revid=0x04 domain=0, bus=0, slot=2, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0xd0500000, size 19, enabled map[14]: type I/O Port, range 32, base 0xea00, size 3, enabled map[18]: type Prefetchable Memory, range 32, base 0xc0000000, size 28, enabled map[1c]: type Memory, range 32, base 0xd0580000, size 18, enabled pcib0: slot 2 INTA routed to irq 16 found-> vendor=0x8086, dev=0x2660, revid=0x04 domain=0, bus=0, slot=28, func=0 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0107, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message pcib0: slot 28 INTA routed to irq 16 found-> vendor=0x8086, dev=0x2662, revid=0x04 domain=0, bus=0, slot=28, func=1 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0107, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) intpin=b, irq=12 powerspec 2 supports D0 D3 current D0 MSI supports 1 message pcib0: slot 28 INTB routed to irq 17 found-> vendor=0x8086, dev=0x2664, revid=0x04 domain=0, bus=0, slot=28, func=2 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0107, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) intpin=c, irq=5 powerspec 2 supports D0 D3 current D0 MSI supports 1 message pcib0: slot 28 INTC routed to irq 18 found-> vendor=0x8086, dev=0x2666, revid=0x04 domain=0, bus=0, slot=28, func=3 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0107, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) intpin=d, irq=10 powerspec 2 supports D0 D3 current D0 MSI supports 1 message pcib0: slot 28 INTD routed to irq 19 found-> vendor=0x8086, dev=0x2658, revid=0x04 domain=0, bus=0, slot=29, func=0 class=0c-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=9 map[20]: type I/O Port, range 32, base 0xeb00, size 5, enabled pcib0: slot 29 INTA routed to irq 23 unknown: Reserved 0x20 bytes for rid 0x20 type 4 at 0xeb00 found-> vendor=0x8086, dev=0x2659, revid=0x04 domain=0, bus=0, slot=29, func=1 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=10 map[20]: type I/O Port, range 32, base 0xed00, size 5, enabled pcib0: slot 29 INTB routed to irq 19 unknown: Reserved 0x20 bytes for rid 0x20 type 4 at 0xed00 found-> vendor=0x8086, dev=0x265a, revid=0x04 domain=0, bus=0, slot=29, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=5 map[20]: type I/O Port, range 32, base 0xe800, size 5, enabled pcib0: slot 29 INTC routed to irq 18 unknown: Reserved 0x20 bytes for rid 0x20 type 4 at 0xe800 found-> vendor=0x8086, dev=0x265b, revid=0x04 domain=0, bus=0, slot=29, func=3 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=11 map[20]: type I/O Port, range 32, base 0xe900, size 5, enabled pcib0: slot 29 INTD routed to irq 16 unknown: Reserved 0x20 bytes for rid 0x20 type 4 at 0xe900 found-> vendor=0x8086, dev=0x265c, revid=0x04 domain=0, bus=0, slot=29, func=7 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=9 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0xd05c0000, size 10, enabled pcib0: slot 29 INTA routed to irq 23 unknown: Reserved 0x400 bytes for rid 0x10 type 3 at 0xd05c0000 found-> vendor=0x8086, dev=0x2448, revid=0xd4 domain=0, bus=0, slot=30, func=0 class=06-04-01, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x2641, revid=0x04 domain=0, bus=0, slot=31, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0107, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x266f, revid=0x04 domain=0, bus=0, slot=31, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0288, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 map[20]: type I/O Port, range 32, base 0xf000, size 4, enabled found-> vendor=0x8086, dev=0x266a, revid=0x04 domain=0, bus=0, slot=31, func=3 class=0c-05-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=10 map[20]: type I/O Port, range 32, base 0x500, size 5, port disabled pcib0: slot 31 INTB routed to irq 19 vgapci0: <vga-compatible display="">port 0xea00-0xea07 mem 0xd0500000-0xd057ffff,0xc0000000-0xcfffffff,0xd0580000-0xd05bffff irq 16 at device 2.0 on pci0 pcib1: <mptable pci-pci="" bridge="">irq 16 at device 28.0 on pci0 pcib1: domain 0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0x8000-0x8fff pcib1: memory decode 0xd0000000-0xd00fffff pcib1: no prefetched decode pci1: <pci bus="">on pcib1 pci1: domain=0, physical bus=1 found-> vendor=0x11ab, dev=0x4362, revid=0x19 domain=0, bus=1, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 MSI supports 2 messages, 64 bit map[10]: type Memory, range 64, base 0xd0020000, size 14, enabled pcib1: requested memory range 0xd0020000-0xd0023fff: good map[18]: type I/O Port, range 32, base 0x8000, size 8, enabled pcib1: requested I/O range 0x8000-0x80ff: in range pcib1: slot 0 INTA routed to irq 16 mskc0: <marvell yukon="" 88e8053="" gigabit="" ethernet="">port 0x8000-0x80ff mem 0xd0020000-0xd0023fff irq 16 at device 0.0 on pci1 mskc0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xd0020000 mskc0: MSI count : 2 mskc0: attempting to allocate 1 MSI vectors (2 supported) msi: routing MSI IRQ 256 to local APIC 0 vector 48 mskc0: using IRQ 256 for MSI mskc0: RAM buffer size : 48KB mskc0: Port 0 : Rx Queue 32KB(0x00000000:0x00007fff) mskc0: Port 0 : Tx Queue 16KB(0x00008000:0x0000bfff) msk0: <marvell technology="" group="" ltd.="" yukon="" ec="" id="" 0xb6="" rev="" 0x02="">on mskc0 msk0: bpf attached miibus0: <mii bus="">on msk0 e1000phy0: <marvell 88e1111="" gigabit="" phy="">PHY 0 on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto mskc0: [MPSAFE] mskc0: [ITHREAD] pcib2: <mptable pci-pci="" bridge="">irq 17 at device 28.1 on pci0 pcib2: domain 0 pcib2: secondary bus 2 pcib2: subordinate bus 2 pcib2: I/O decode 0x9000-0x9fff pcib2: memory decode 0xd0100000-0xd01fffff pcib2: no prefetched decode pci2: <pci bus="">on pcib2 pci2: domain=0, physical bus=2 found-> vendor=0x11ab, dev=0x4362, revid=0x19 domain=0, bus=2, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=12 powerspec 2 supports D0 D1 D2 D3 current D0 MSI supports 2 messages, 64 bit map[10]: type Memory, range 64, base 0xd0120000, size 14, enabled pcib2: requested memory range 0xd0120000-0xd0123fff: good map[18]: type I/O Port, range 32, base 0x9000, size 8, enabled pcib2: requested I/O range 0x9000-0x90ff: in range pcib2: slot 0 INTA routed to irq 17 mskc1: <marvell yukon="" 88e8053="" gigabit="" ethernet="">port 0x9000-0x90ff mem 0xd0120000-0xd0123fff irq 17 at device 0.0 on pci2 mskc1: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xd0120000 mskc1: MSI count : 2 mskc1: attempting to allocate 1 MSI vectors (2 supported) msi: routing MSI IRQ 257 to local APIC 0 vector 50 mskc1: using IRQ 257 for MSI mskc1: RAM buffer size : 48KB mskc1: Port 0 : Rx Queue 32KB(0x00000000:0x00007fff) mskc1: Port 0 : Tx Queue 16KB(0x00008000:0x0000bfff) msk1: <marvell technology="" group="" ltd.="" yukon="" ec="" id="" 0xb6="" rev="" 0x02="">on mskc1 msk1: bpf attached miibus1: <mii bus="">on msk1 e1000phy1: <marvell 88e1111="" gigabit="" phy="">PHY 0 on miibus1 e1000phy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto mskc1: [MPSAFE] mskc1: [ITHREAD] pcib3: <mptable pci-pci="" bridge="">irq 18 at device 28.2 on pci0 pcib3: domain 0 pcib3: secondary bus 3 pcib3: subordinate bus 3 pcib3: I/O decode 0xa000-0xafff pcib3: memory decode 0xd0200000-0xd02fffff pcib3: no prefetched decode pci3: <pci bus="">on pcib3 pci3: domain=0, physical bus=3 found-> vendor=0x11ab, dev=0x4362, revid=0x19 domain=0, bus=3, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 powerspec 2 supports D0 D1 D2 D3 current D0 MSI supports 2 messages, 64 bit map[10]: type Memory, range 64, base 0xd0220000, size 14, enabled pcib3: requested memory range 0xd0220000-0xd0223fff: good map[18]: type I/O Port, range 32, base 0xa000, size 8, enabled pcib3: requested I/O range 0xa000-0xa0ff: in range pcib3: slot 0 INTA routed to irq 18 mskc2: <marvell yukon="" 88e8053="" gigabit="" ethernet="">port 0xa000-0xa0ff mem 0xd0220000-0xd0223fff irq 18 at device 0.0 on pci3 mskc2: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xd0220000 mskc2: MSI count : 2 mskc2: attempting to allocate 1 MSI vectors (2 supported) msi: routing MSI IRQ 258 to local APIC 0 vector 52 mskc2: using IRQ 258 for MSI mskc2: RAM buffer size : 48KB mskc2: Port 0 : Rx Queue 32KB(0x00000000:0x00007fff) mskc2: Port 0 : Tx Queue 16KB(0x00008000:0x0000bfff) msk2: <marvell technology="" group="" ltd.="" yukon="" ec="" id="" 0xb6="" rev="" 0x02="">on mskc2 msk2: bpf attached miibus2: <mii bus="">on msk2 e1000phy2: <marvell 88e1111="" gigabit="" phy="">PHY 0 on miibus2 e1000phy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto mskc2: [MPSAFE] mskc2: [ITHREAD] pcib4: <mptable pci-pci="" bridge="">irq 19 at device 28.3 on pci0 pcib4: domain 0 pcib4: secondary bus 4 pcib4: subordinate bus 4 pcib4: I/O decode 0xb000-0xbfff pcib4: memory decode 0xd0300000-0xd03fffff pcib4: no prefetched decode pci4: <pci bus="">on pcib4 pci4: domain=0, physical bus=4 found-> vendor=0x11ab, dev=0x4362, revid=0x19 domain=0, bus=4, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 MSI supports 2 messages, 64 bit map[10]: type Memory, range 64, base 0xd0320000, size 14, enabled pcib4: requested memory range 0xd0320000-0xd0323fff: good map[18]: type I/O Port, range 32, base 0xb000, size 8, enabled pcib4: requested I/O range 0xb000-0xb0ff: in range pcib4: slot 0 INTA routed to irq 19 mskc3: <marvell yukon="" 88e8053="" gigabit="" ethernet="">port 0xb000-0xb0ff mem 0xd0320000-0xd0323fff irq 19 at device 0.0 on pci4 mskc3: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xd0320000 mskc3: MSI count : 2 mskc3: attempting to allocate 1 MSI vectors (2 supported) msi: routing MSI IRQ 259 to local APIC 0 vector 54 mskc3: using IRQ 259 for MSI mskc3: RAM buffer size : 48KB mskc3: Port 0 : Rx Queue 32KB(0x00000000:0x00007fff) mskc3: Port 0 : Tx Queue 16KB(0x00008000:0x0000bfff) msk3: <marvell technology="" group="" ltd.="" yukon="" ec="" id="" 0xb6="" rev="" 0x02="">on mskc3 msk3: bpf attached miibus3: <mii bus="">on msk3 e1000phy3: <marvell 88e1111="" gigabit="" phy="">PHY 0 on miibus3 e1000phy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto mskc3: [MPSAFE] mskc3: [ITHREAD] uhci0: <intel 82801fb="" fr="" fw="" frw="" (ich6)="" usb="" controller="" usb-a="">port 0xeb00-0xeb1f irq 23 at device 29.0 on pci0 ioapic0: routing intpin 23 (PCI IRQ 23) to lapic 0 vector 49 uhci0: [MPSAFE] uhci0: [ITHREAD] usbus0: <intel 82801fb="" fr="" fw="" frw="" (ich6)="" usb="" controller="" usb-a="">on uhci0 uhci1: <intel 82801fb="" fr="" fw="" frw="" (ich6)="" usb="" controller="" usb-b="">port 0xed00-0xed1f irq 19 at device 29.1 on pci0 ioapic0: routing intpin 19 (PCI IRQ 19) to lapic 0 vector 51 uhci1: [MPSAFE] uhci1: [ITHREAD] usbus1: <intel 82801fb="" fr="" fw="" frw="" (ich6)="" usb="" controller="" usb-b="">on uhci1 uhci2: <intel 82801fb="" fr="" fw="" frw="" (ich6)="" usb="" controller="" usb-c="">port 0xe800-0xe81f irq 18 at device 29.2 on pci0 ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 53 uhci2: [MPSAFE] uhci2: [ITHREAD] usbus2: <intel 82801fb="" fr="" fw="" frw="" (ich6)="" usb="" controller="" usb-c="">on uhci2 uhci3: <intel 82801fb="" fr="" fw="" frw="" (ich6)="" usb="" controller="" usb-d="">port 0xe900-0xe91f irq 16 at device 29.3 on pci0 ioapic0: routing intpin 16 (PCI IRQ 16) to lapic 0 vector 55 uhci3: [MPSAFE] uhci3: [ITHREAD] usbus3: <intel 82801fb="" fr="" fw="" frw="" (ich6)="" usb="" controller="" usb-d="">on uhci3 ehci0: <intel 82801fb="" (ich6)="" usb="" 2.0="" controller="">mem 0xd05c0000-0xd05c03ff irq 23 at device 29.7 on pci0 ehci0: [MPSAFE] ehci0: [ITHREAD] usbus4: EHCI version 1.0 usbus4: <intel 82801fb="" (ich6)="" usb="" 2.0="" controller="">on ehci0 pcib5: <mptable pci-pci="" bridge="">at device 30.0 on pci0 pcib5: domain 0 pcib5: secondary bus 5 pcib5: subordinate bus 5 pcib5: I/O decode 0xc000-0xdfff pcib5: memory decode 0xd0400000-0xd04fffff pcib5: no prefetched decode pcib5: Subtractively decoded bridge. pci5: <pci bus="">on pcib5 pci5: domain=0, physical bus=5 found-> vendor=0x11ab, dev=0x4320, revid=0x13 domain=0, bus=5, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02b0, cachelnsz=8 (dwords) lattimer=0x60 (2880 ns), mingnt=0x17 (5750 ns), maxlat=0x1f (7750 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xd042c000, size 14, enabled pcib5: requested memory range 0xd042c000-0xd042ffff: good map[14]: type I/O Port, range 32, base 0xc000, size 8, enabled pcib5: requested I/O range 0xc000-0xc0ff: in range pcib5: slot 0 INTA routed to irq 16 found-> vendor=0x11ab, dev=0x4320, revid=0x13 domain=0, bus=5, slot=1, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02b0, cachelnsz=8 (dwords) lattimer=0x60 (2880 ns), mingnt=0x17 (5750 ns), maxlat=0x1f (7750 ns) intpin=a, irq=12 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xd0420000, size 14, enabled pcib5: requested memory range 0xd0420000-0xd0423fff: good map[14]: type I/O Port, range 32, base 0xc400, size 8, enabled pcib5: requested I/O range 0xc400-0xc4ff: in range pcib5: slot 1 INTA routed to irq 17 found-> vendor=0x11ab, dev=0x4320, revid=0x13 domain=0, bus=5, slot=2, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02b0, cachelnsz=8 (dwords) lattimer=0x60 (2880 ns), mingnt=0x17 (5750 ns), maxlat=0x1f (7750 ns) intpin=a, irq=5 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xd0424000, size 14, enabled pcib5: requested memory range 0xd0424000-0xd0427fff: good map[14]: type I/O Port, range 32, base 0xc800, size 8, enabled pcib5: requested I/O range 0xc800-0xc8ff: in range pcib5: slot 2 INTA routed to irq 18 found-> vendor=0x11ab, dev=0x4320, revid=0x13 domain=0, bus=5, slot=3, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02b0, cachelnsz=8 (dwords) lattimer=0x60 (2880 ns), mingnt=0x17 (5750 ns), maxlat=0x1f (7750 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xd0428000, size 14, enabled pcib5: requested memory range 0xd0428000-0xd042bfff: good map[14]: type I/O Port, range 32, base 0xcc00, size 8, enabled pcib5: requested I/O range 0xcc00-0xccff: in range pcib5: slot 3 INTA routed to irq 19 found-> vendor=0x177d, dev=0x0003, revid=0x00 domain=0, bus=5, slot=4, func=0 class=10-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02b0, cachelnsz=8 (dwords) lattimer=0x60 (2880 ns), mingnt=0x40 (16000 ns), maxlat=0x40 (16000 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type I/O Port, range 32, base 0xd000, size 8, enabled pcib5: requested I/O range 0xd000-0xd0ff: in range map[18]: type I/O Port, range 32, base 0xd400, size 8, enabled pcib5: requested I/O range 0xd400-0xd4ff: in range pcib5: slot 4 INTA routed to irq 20 skc0: <marvell gigabit="" ethernet="">port 0xc000-0xc0ff mem 0xd042c000-0xd042ffff irq 16 at device 0.0 on pci5 skc0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xd042c000 skc0: interrupt moderation is 100 us skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) skc0: chip ver = 0xb1 skc0: chip rev = 0x09 skc0: SK_EPROM0 = 0x10 skc0: SRAM size = 0x010000 sk0: <marvell semiconductor,="" inc.="" yukon="">on skc0 sk0: bpf attached miibus4: <mii bus="">on sk0 e1000phy4: <marvell 88e1011="" gigabit="" phy="">PHY 0 on miibus4 e1000phy4: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto skc0: [MPSAFE] skc0: [ITHREAD] skc1: <marvell gigabit="" ethernet="">port 0xc400-0xc4ff mem 0xd0420000-0xd0423fff irq 17 at device 1.0 on pci5 skc1: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xd0420000 skc1: interrupt moderation is 100 us skc1: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) skc1: chip ver = 0xb1 skc1: chip rev = 0x09 skc1: SK_EPROM0 = 0x10 skc1: SRAM size = 0x010000 sk1: <marvell semiconductor,="" inc.="" yukon="">on skc1 sk1: bpf attached miibus5: <mii bus="">on sk1 e1000phy5: <marvell 88e1011="" gigabit="" phy="">PHY 0 on miibus5 e1000phy5: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto ioapic0: routing intpin 17 (PCI IRQ 17) to lapic 0 vector 56 skc1: [MPSAFE] skc1: [ITHREAD] skc2: <marvell gigabit="" ethernet="">port 0xc800-0xc8ff mem 0xd0424000-0xd0427fff irq 18 at device 2.0 on pci5 skc2: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xd0424000 skc2: interrupt moderation is 100 us skc2: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) skc2: chip ver = 0xb1 skc2: chip rev = 0x09 skc2: SK_EPROM0 = 0x10 skc2: SRAM size = 0x010000 sk2: <marvell semiconductor,="" inc.="" yukon="">on skc2 sk2: bpf attached miibus6: <mii bus="">on sk2 e1000phy6: <marvell 88e1011="" gigabit="" phy="">PHY 0 on miibus6 e1000phy6: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto skc2: [MPSAFE] skc2: [ITHREAD] skc3: <marvell gigabit="" ethernet="">port 0xcc00-0xccff mem 0xd0428000-0xd042bfff irq 19 at device 3.0 on pci5 skc3: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xd0428000 skc3: interrupt moderation is 100 us skc3: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) skc3: chip ver = 0xb1 skc3: chip rev = 0x09 skc3: SK_EPROM0 = 0x10 skc3: SRAM size = 0x010000 sk3: <marvell semiconductor,="" inc.="" yukon="">on skc3 sk3: bpf attached miibus7: <mii bus="">on sk3 e1000phy7: <marvell 88e1011="" gigabit="" phy="">PHY 0 on miibus7 e1000phy7: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto skc3: [MPSAFE] skc3: [ITHREAD] pci5: <encrypt decrypt,="" network="" computer="" crypto="">at device 4.0 (no driver attached) isab0: <pci-isa bridge="">at device 31.0 on pci0 isa0: <isa bus="">on isab0 atapci0: <intel ich6="" udma100="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 31.1 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xf000 ata0: <ata 0="" channel="">on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=50 ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: stat1=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=50 devices=0x3 ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 0 vector 57 ata0: [MPSAFE] ata0: [ITHREAD] ata1: <ata 1="" channel="">on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=00 ostat0=ff ostat1=ff ioapic0: routing intpin 15 (ISA IRQ 15) to lapic 0 vector 58 ata1: [MPSAFE] ata1: [ITHREAD] pci0: <serial bus,="" smbus="">at device 31.3 (no driver attached) cpu0 on motherboard ahc_isa_probe 12: ioport 0xcc00 alloc failed ahc_isa_probe 14: ioport 0xec00 alloc failed pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete pnpbios: 14 devices, largest 92 bytes PNP0200: adding dma mask 0x10 PNP0200: adding io range 0-0xf, size=0x10, align=0 PNP0200: adding io range 0x81-0x83, size=0x3, align=0 PNP0200: adding io range 0x87-0x87, size=0x1, align=0 PNP0200: adding io range 0x89-0x8b, size=0x3, align=0 PNP0200: adding io range 0x8f-0x91, size=0x3, align=0 PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0 pnpbios: handle 1 device ID PNP0200 (0002d041) PNP0100: adding irq mask 0x1 PNP0100: adding io range 0x40-0x43, size=0x4, align=0 pnpbios: handle 2 device ID PNP0100 (0001d041) PNP0b00: adding irq mask 0x100 PNP0b00: adding io range 0x70-0x71, size=0x2, align=0 pnpbios: handle 3 device ID PNP0b00 (000bd041) PNP0303: adding irq mask 0x2 PNP0303: adding io range 0x60-0x60, size=0x1, align=0 PNP0303: adding io range 0x64-0x64, size=0x1, align=0 pnpbios: handle 4 device ID PNP0303 (0303d041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0 pnpbios: handle 5 device ID PNP0800 (0008d041) PNP0c04: adding irq mask 0x2000 PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0 pnpbios: handle 6 device ID PNP0c04 (040cd041) INT0800: adding fixed memory32 range 0xffb80000-0xffbfffff, size=0x80000 pnpbios: handle 7 device ID INT0800 (0008d425) PNP0c01: adding fixed memory32 range 0-0x9ffff, size=0xa0000 PNP0c01: adding fixed memory32 range 0xffb00000-0xffb7ffff, size=0x80000 PNP0c01: adding fixed memory32 range 0xfff00000-0xffffffff, size=0x100000 PNP0c01: adding fixed memory32 range 0xfec00000-0xfec0ffff, size=0x10000 PNP0c01: adding fixed memory32 range 0xfee00000-0xfee0ffff, size=0x10000 PNP0c01: adding fixed memory32 range 0x100000-0xffffff, size=0xf00000 pnpbios: handle 8 device ID PNP0c01 (010cd041) PNP0c02: adding fixed memory32 range 0xf0000-0xf3fff, size=0x4000 PNP0c02: adding fixed memory32 range 0xf4000-0xf7fff, size=0x4000 PNP0c02: adding fixed memory32 range 0xf8000-0xfffff, size=0x8000 PNP0c02: adding fixed memory32 range 0xce800-0xcffff, size=0x1800 pnpbios: handle 9 device ID PNP0c02 (020cd041) PNP0a03: adding io range 0x294-0x297, size=0x4, align=0 PNP0a03: adding io range 0x4d0-0x4d1, size=0x2, align=0 PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0 PNP0a03: adding io range 0x400-0x4bf, size=0xc0, align=0 pnpbios: handle 10 device ID PNP0a03 (030ad041) PNP0501: adding irq mask 0x10 PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0 pnpbios: handle 12 device ID PNP0501 (0105d041) PNP0400: adding irq mask 0x80 PNP0400: adding io range 0x378-0x37f, size=0x8, align=0 PNP0400: adding io range 0x778-0x77b, size=0x4, align=0 pnpbios: handle 13 device ID PNP0400 (0004d041) PNP0501: adding irq mask 0x8 PNP0501: adding io range 0x2f8-0x2ff, size=0x8, align=0 pnpbios: handle 15 device ID PNP0501 (0105d041) isa_probe_children: disabling PnP devices atrtc0: <at realtime="" clock="">at port 0x70-0x71 irq 8 pnpid PNP0b00 on isa0 atrtc0: registered as a time-of-day clock (resolution 1000000us) unknown: <at real="" time="" clock="">failed to probe at port 0x60,0x64 irq 1 pnpid PNP0303 on isa0 unknown: <at real="" time="" clock="">failed to probe at port 0x61 pnpid PNP0800 on isa0 unknown: <at real="" time="" clock="">failed to probe at iomem 0xffb80000-0xffbfffff pnpid INT0800 on isa0 unknown: <pnp0c01>can't assign resources (memory) unknown: <pnp0c01>at iomem 0-0x9ffff pnpid PNP0c01 on isa0 uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 flags 0x10 pnpid PNP0501 on isa0 ioapic0: routing intpin 4 (ISA IRQ 4) to lapic 0 vector 59 uart0: [FILTER] uart0: fast interrupt uart0: console (9600,n,8,1) ppc0: using extended I/O port range ppc0: SPP ppc0: <standard parallel="" printer="" port="">at port 0x378-0x37f,0x778-0x77b irq 7 pnpid PNP0400 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ioapic0: routing intpin 7 (ISA IRQ 7) to lapic 0 vector 60 ppc0: [MPSAFE] ppc0: [ITHREAD] ppbus0: <parallel port="" bus="">on ppc0 ppi0: <parallel i="" o="">on ppbus0 uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 pnpid PNP0501 on isa0 ioapic0: routing intpin 3 (ISA IRQ 3) to lapic 0 vector 61 uart1: [FILTER] uart1: fast interrupt ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it atrtc: atrtc0 already exists; skipping it ppc: ppc0 already exists; skipping it uart: uart0 already exists; skipping it uart: uart1 already exists; skipping it isa_probe_children: probing non-PnP devices orm0: <isa option="" rom="">at iomem 0xc0000-0xce7ff pnpid ORM0000 on isa0 atkbdc0 failed to probe at port 0x60 on isa0 fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 sc0 failed to probe on isa0 isa_probe_children: probing PnP devices unknown: <pnp0c01>can't assign resources (memory) unknown: <pnp0c01>at iomem 0-0x9ffff pnpid PNP0c01 on isa0 Device configuration finished. procfs registered lapic: Divisor 2, Frequency 50002060 Hz Timecounter "TSC" frequency 1300053505 Hz quality 800 Timecounters tick every 10.000 msec vlan: initialized, using hash tables with chaining crypto: <crypto device="">IPsec: Initialized Security Association Processing. pflog0: bpf attached lo0: bpf attached pfsync0: bpf attached enc0: bpf attached ata0: Identifying devices: 00000003 ata0: New devices: 00000003 usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 ugen0.1: <intel>at usbus0 uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0 ugen1.1: <intel>at usbus1 uhub1: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus1 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 12Mbps Full Speed USB v1.0 ugen2.1: <intel>at usbus2 uhub2: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus2 ugen3.1: <intel>at usbus3 uhub3: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus3 usbus4: 480Mbps High Speed USB v2.0 ata0-slave: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire ugen4.1: <intel>at usbus4 uhub4: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus4 uhub0: 2 ports with 2 removable, self powered ata0-master: pio=PIO4 wdma=UNSUPPORTED udma=UNSUPPORTED cable=40 wire uhub1: 2 ports with 2 removable, self powered ad0: setting PIO4 ad0: 245MB <sandisk sdcfj-256="" hdx="" 4.06="">at ata0-master PIO4 ad0: 501760 sectors [980C/16H/32S] 4 sectors/interrupt 1 depth queue uhub2: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered ad0: Intel check1 failed GEOM: new disk ad0 ad0: Adaptec check1 failed ad0: LSI (v3) check1 failed ad0: LSI (v2) check1 failed ad0: FreeBSD check1 failed ata0: DMA limited to UDMA33, controller found non-ATA66 cable ad1: setting UDMA33 ad1: 28615MB <ic25n030atmr04 0="" moaoad0a="">at ata0-slave UDMA33 ad1: 58605120 sectors [58140C/16H/63S] 16 sectors/interrupt 1 depth queue ad1: Intel check1 failed ad1: Adaptec check1 failed ad1: LSI (v3) check1 failed ad1: LSI (v2) check1 failed ad1: FreeBSD check1 failed ata1: Identifying devices: 00000000 ata1: New devices: 00000000 ATA PseudoRAID loaded GEOM: new disk ad1 GEOM: ad1s1: geometry does not match label (15h,63s != 16h,63s). Root mount waiting for: usbus4 Root mount waiting for: usbus4 uhub4: 8 ports with 8 removable, self powered Trying to mount root from ufs:/dev/ad0s1a ROOT MOUNT ERROR: If you have invalid mount options, reboot, and first try the following from the loader prompt: set vfs.root.mountfrom.options=rw and then remove invalid mount options from /etc/fstab. Loader variables: vfs.root.mountfrom=ufs:/dev/ad0s1a vfs.root.mountfrom.options=rw Manual root filesystem specification: <fstype>:<device>Mount <device>using filesystem <fstype>eg. ufs:/dev/da0s1a eg. cd9660:/dev/acd0 This is equivalent to: mount -t cd9660 /dev/acd0 / ? List valid disk boot devices <empty line="">Abort manual input mountroot> ? List of GEOM managed disk devices: ufsid/50b4cee13a7e71f6 ad1s1b ad1s1a ad1s1 ad1 ad0s8 ad0s7 ad0s6 ad0s5 ad0s4 ad0s3 ad0s2 ad0s1 ad0 Loader variables: vfs.root.mountfrom=ufs:/dev/ad0s1a vfs.root.mountfrom.options=rw Manual root filesystem specification: <fstype>:<device>Mount <device>using filesystem <fstype>eg. ufs:/dev/da0s1a eg. cd9660:/dev/acd0 This is equivalent to: mount -t cd9660 /dev/acd0 / ? List valid disk boot devices <empty line="">Abort manual input mountroot></empty></fstype></device></device></fstype></empty></fstype></device></device></fstype></ic25n030atmr04></sandisk></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></crypto></pnp0c01></pnp0c01></isa></parallel></parallel></standard></pnp0c01></pnp0c01></at></at></at></at></serial></ata></ata></intel></isa></pci-isa></encrypt></marvell></mii></marvell></marvell></marvell></mii></marvell></marvell></marvell></mii></marvell></marvell></marvell></mii></marvell></marvell></pci></mptable></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></marvell></mii></marvell></marvell></pci></mptable></marvell></mii></marvell></marvell></pci></mptable></marvell></mii></marvell></marvell></pci></mptable></marvell></mii></marvell></marvell></pci></mptable></vga-compatible></pci></mptable></software></null>_</crypto></memory></entropy></version></oem00000></fpu,vme,de,pse,tsc,msr,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,dts,acpi,mmx,fxsr,sse,sse2,tm,pbe> ``` _Regards Neil_</ic25n030atmr04>
-
Did you try my suggestion?: ufs:/dev/ad1s1a
Steve
-
Indeed
mountroot> ufs:/dev/ad1s1a Trying to mount root from ufs:/dev/ad1s1a Loader variables: vfs.root.mountfrom=ufs:/dev/ad0s1a vfs.root.mountfrom.options=rw Manual root filesystem specification: <fstype>:<device>Mount <device>using filesystem <fstype>eg. ufs:/dev/da0s1a eg. cd9660:/dev/acd0 This is equivalent to: mount -t cd9660 /dev/acd0 / ? List valid disk boot devices <empty line="">Abort manual input t mountroot>t</empty></fstype></device></device></fstype>
However no success as of yet :'(
So what next batman?
Neil
-
Hmm, well try ad1s1b since that's the only other likely thing listed.
Otherwise it's back to bat cave for testing! ;)Steve
-
I take it this is the root cause,
ad0: Intel check1 failed GEOM: new disk ad0 ad0: Adaptec check1 failed ad0: LSI (v3) check1 failed ad0: LSI (v2) check1 failed ad0: FreeBSD check1 failed ata0: DMA limited to UDMA33, controller found non-ATA66 cable ad1: setting UDMA33 ad1: 28615MB <ic25n030atmr04 0="" moaoad0a="">at ata0-slave UDMA33 ad1: 58605120 sectors [58140C/16H/63S] 16 sectors/interrupt 1 depth queue ad1: Intel check1 failed ad1: Adaptec check1 failed ad1: LSI (v3) check1 failed ad1: LSI (v2) check1 failed ad1: FreeBSD check1 failed ata1: Identifying devices: 00000000 ata1: New devices: 00000000</ic25n030atmr04>
-
No I don't think so though info on that seems to be sparse. I think that's just FreeBSD checking for specific hardware that would require some sort of quirky handling. If you remove verbose boot logging I imagine that would not appear.
Does your harddrive have it's real geometry written on it? Does it agree with either the BIOS or the pfSesne boot log?I.e. The cause is more likely:
ad1: 58605120 sectors [58140C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad1 GEOM: ad1s1: geometry does not match label (15h,63s != 16h,63s).
So it is having a problem mounting ad1s1 (a or b)
Steve
-
Does your harddrive have it's real geometry written on it? Does it agree with either the BIOS or the pfSesne boot log?
Im afraid your going to have to dumb this down, its not any of that fake geometry malarkey
**** BIOS Ver.ETAC0017 mod V1.3 console 115200 on com1 **** IDE Channel 0 Master : SanDisk SDCFJ-256 HDX 4.06 IDE Channel 0 Slave : IC25N030ATMR04-0 MOAOAD0A Phoenix Technologies, LTD System Configurations +==============================================================================+ | CPU Type : Genuine Intel(R) processor Base Memory : 640K | | CPU ID/uco: 0695/45 Extended Memory : 515072K | | CPU Clock : 1.30GHz Cache Memory : 512K | |------------------------------------------------------------------------------| | Pri. Master Disk : LRG,PIO 4, 256MB Display Type : EGA/VGA | | Pri. Slave Disk : LRG,PIO 4,30007MB Serial Port(s) : 3F8 2F8 | | Sec. Master Disk : None Parallel Port(s) : 378 | | Sec. Slave Disk : None DDR2 at Bank(s) : 0 | +==============================================================================+ PCI device listing ... Bus No. Device No. Func No. Vendor/Device Class Device Class IRQ -------------------------------------------------------------------------------- 0 2 0 8086 2592 0300 Display Cntrlr 11 0 29 0 8086 2658 0C03 USB 1.0/1.1 UHCI Cntrlr 9 0 29 1 8086 2659 0C03 USB 1.0/1.1 UHCI Cntrlr 10 0 29 2 8086 265A 0C03 USB 1.0/1.1 UHCI Cntrlr 5 0 29 3 8086 265B 0C03 USB 1.0/1.1 UHCI Cntrlr 11 0 29 7 8086 265C 0C03 USB 2.0 EHCI Cntrlr 9 0 31 3 8086 266A 0C05 SMBus Cntrlr 10 1 0 0 11AB 4362 0200 Network Cntrlr 11 2 0 0 11AB 4362 0200 Network Cntrlr 12 3 0 0 11AB 4362 0200 Network Cntrlr 5 4 0 0 11AB 4362 0200 Network Cntrlr 10 5 0 0 11AB 4320 0200 Network Cntrlr 11 5 1 0 11AB 4320 0200 Network Cntrlr 12 5 2 0 11AB 4320 0200 Network Cntrlr 5 5 3 0 11AB 4320 0200 Network Cntrlr 10 5 4 0 177D 0003 1000 En/Decryption Cntrlr 11
Surely its somethiing daft that i have done, i may well end up keeping the CF install i have…...
-
About the only other thing I am seeing commonly in FreeBSD problem threads are odd problems caused by a bad cable. How have you attached the drive?
Just a bad drive? That Hitachi must quite old by now. :-\I think I'm going to have to pull out an old laptop drive and give this a go myself. I've only tried it once, it was a long while ago and I only did it as an experiment. I don't remember it being too difficult though.
Steve
-
You know what the jumper on the drive protrudes a little pit causing the IDE -> Whatever FB converter to be a little insecure (well not as tight as it could be) be right back after i have snippered it.
also i have another drive to try
-
Hmm,
Nope I can't make it boot from the HD. :-
The best result I had was booting to the mountroot> prompt but the drive, ad1, wasn't detected. That was either with the setting carried over from the 2GB CF I had been using where it was detected as primary master but much smaller capacity. Or when the jumper on the drive set to slave and a CF card in the slot.
I was sure I had booted from a HD before. Maybe it was on a different Watchguard box. :-
Other users have done it successfully though. I'll have to read back through the very long thread to see if anyone posted specifics.Steve
-
Success! :D but weird behaviour. :P
Ok so I have an X750e that can, reliably and repeatedly, boot from a HD connected via the rear drive bay caddy connector.
Here's what I did:
Put the drive in a laptop and boot the laptop from the pfSense 2.0.1 i386 install CD.
Select straight to install and the prompt (I), choose the default settings for everything and the SMP kernel (the standard kernel).
Boot the laptop into pfSense and setup one interface sufficient that you can reach the webgui.
In the webgui enable serial port console in System: Advanced: Admin Access:
Could you do those steps from the CLI negating any hassles with laptop NICs? Probably.
Shut down the laptop and tranfer the drive to the Watchguard box.
In order for the drive to boot at all it must be set as slave using the drive jumpers. Cable select doesn't work.
There must be a CF card in the slot. I used a random <512MB card. I haven't tried a larger card.
In the bios set everything on both drives to auto and make sure harddisk boot priority is set to the detected slave HD.
Boot the box. You will see that the green 'Storage' LED stays lit far longer than usual.
Now here's the weird part: you must select verbose boot (option 6) at the menu. The default boot won't correctly detect the HD as ad1.
When it fails at the mountroot> enter ufs:/dev/ad1s1a
The box should boot correctly from here, mine does.
When it has booted you must edit /etc/fstab and change the references to ad0 to ad1. You can do that either via the edit file page in the webgui or from the command line using: ee /etc/fstab (or vi if you're a masochist).
In order to make it boot verbose every time you need to add boot_verbose="1" to /boot/loader.conf.local. You can do it easily from the command line:echo 'boot_verbose="1"' > /boot/loader.conf.local
Having done those steps my box boots from the HD every time but I'm at a loss to explain why. :-
This may be a clue: http://forums.freebsd.org/showthread.php?t=20693
I think there are two separate quirks at work here: buggy bios and FreeBSD weirdness.
It's quite possible you could remove the CF card and set the drive as master as long as you have to right CHS settings. My drive initially booted when the BIOS still had the previous settings for a 4GB CF card. It seems possible that it will boot any drive as long as it appears less than 512MB.Steve
I am using a Toshiba 20GB drive, MK2018GAP. -
Having done those steps my box boots from the HD every time but I'm at a loss to explain why. :-\
It might not be relevant but due to the extra console output a verbose boot will proceed more slowly than a standard boot, possibly giving more time for hardware to get into the state anticipated by software.
Maybe the kern.cam.delay boot variable could be used to accomplish the same result.
-
Good suggestion, didn't work. ::)
I was quite confident but no dice.
More research needed.Steve
-
It's been awhile since I've done this and when I did it was still just 1.2.3 version. Really the easiest and less modification needing is if you can attach a CD drive and a video card/serial console and install it directly from the Firebox.
-
Most X-Core-E boxes do not have the IDE header populated as far as I know. 1 out of 4 I've looked in.
Here's the dmesg.boot from a successful boot for anyone looking for clues.
Steve
-
Hi Steve,
Thanks for this I will have a go tomorrow, and let you know how it goes.
Success! :D but weird behaviour. :P
Ok so I have an X750e that can, reliably and repeatedly, boot from a HD connected via the rear drive bay caddy connector.
Here's what I did:
Put the drive in a laptop and boot the laptop from the pfSense 2.0.1 i386 install CD.
Select straight to install and the prompt (I), choose the default settings for everything and the SMP kernel (the standard kernel).
Boot the laptop into pfSense and setup one interface sufficient that you can reach the webgui.
In the webgui enable serial port console in System: Advanced: Admin Access:
Could you do those steps from the CLI negating any hassles with laptop NICs? Probably.
Shut down the laptop and tranfer the drive to the Watchguard box.
In order for the drive to boot at all it must be set as slave using the drive jumpers. Cable select doesn't work.
There must be a CF card in the slot. I used a random <512MB card. I haven't tried a larger card.
In the bios set everything on both drives to auto and make sure harddisk boot priority is set to the detected slave HD.
Boot the box. You will see that the green 'Storage' LED stays lit far longer than usual.
Now here's the weird part: you must select verbose boot (option 6) at the menu. The default boot won't correctly detect the HD as ad1.
When it fails at the mountroot> enter ufs:/dev/ad1s1a
The box should boot correctly from here, mine does.
When it has booted you must edit /etc/fstab and change the references to ad0 to ad1. You can do that either via the edit file page in the webgui or from the command line using: ee /etc/fstab (or vi if you're a masochist).
In order to make it boot verbose every time you need to add boot_verbose="1" to /boot/loader.conf.local. You can do it easily from the command line:echo 'boot_verbose="1"' > /boot/loader.conf.local
Having done those steps my box boots from the HD every time but I'm at a loss to explain why. :-
This may be a clue: http://forums.freebsd.org/showthread.php?t=20693
I think there are two separate quirks at work here: buggy bios and FreeBSD weirdness.
It's quite possible you could remove the CF card and set the drive as master as long as you have to right CHS settings. My drive initially booted when the BIOS still had the previous settings for a 4GB CF card. It seems possible that it will boot any drive as long as it appears less than 512MB.Steve
I am using a Toshiba 20GB drive, MK2018GAP. -
Steve, wallabybob you have been complete gents this is now up and working :-) thank you.
I have quietened it down with WGXepc, i have a sort of working LCD display though it doesn't seem to be controllable but it looks better than "booting watch os",
Regards Neil
-
Excellent. :)
Steve
-
Just to follow up here I had some time to run a few further tests this afternoon.
I have found:
The bios will boot from a hard drive or CF card that is set as master as long as it sees it as less than 512MB. When I say boot I mean it correctly passes the address of the MBR to the processor and the pfSense (or whatever) bootloader is run.pfSense will not be able to correctly detect and mount root unless something resembling the correct geometry is passed to it. And then only when booted in verbose logging mode, which I still find just bizarre. :-\
The procedure I outlined earlier in this thread is the only way I have found to correctly boot pfSense on ans X-Core-e box.
It's strange because GEOM has not problem seeing and mounting rooting correctly from a large CF card even though you have to fudge the CHS figures to make it less than 512MB.
It would be very intersting to look inside a Watchguard SSL box (SSL100, 500 or 1000) to see how they did it. Those boxes have HDs but I'm unsure if they had a CF as well. They might have even had a fixed bios. ;)
Steve
-
About the only other thing I am seeing commonly in FreeBSD problem threads are odd problems caused by a bad cable. How have you attached the drive?
Just a bad drive? That Hitachi must quite old by now. :-\I think I'm going to have to pull out an old laptop drive and give this a go myself. I've only tried it once, it was a long while ago and I only did it as an experiment. I don't remember it being too difficult though.
Steve
I'm Currently running PFsense full install on an 80Gb HDD in an X750e with NO CF card installed.
here's the steps that i took to get the system running.
load spare 80Gb HDD into a laptop (used a HP NC6120)
load pfsense full 2.0.1 cd and boot from cd.
I was presented with an error on boot up to press R to enter recovery console or press I to enter installer mode.
Press I to enter installer mode. Pfsense installer launched.
select defaults for the VGA and Keyboard options.
select quick/standard install of PFsense. accepted defaults all way through.
selected embedded kernel. no VGA or keyboard.
Pfsense requires reboot after install. At this point shut down clean and power off laptop.
remove HDD from laptop and confirm that drive is set as master.Flash bios as per Stephenw10's instructions. using X750eB6 bios image.
reset bios after flash via the cmos reset jumper on the board.
connect to firebox via serial cable 115000 8-n-1 no flow control.
press tab to enter bios and select the option to reset bios to defaults.
Shut down Firebox and install HDD
Power on Firebox and enter bios.
Select autodetect for HDD, and accept the findings. no changes made to heads or sectors.
at this point you can enter other parts of the bios and switch off devices that are not required, (eg com2 serial port parallel port etc)
DONT Disable com1 or you will loose your connection and will have to reset bios to defaults again to get back in.
Save changes and reboot box.connect via com port at 115200 to confirm HDD detected
At PCI device listing change com port to 9600 8n1
let Pfsense boot as normal.
initial configuration done through serial, then via web configuration page.Attached image showing storage devices attached to system.
hope this helps someone.
Colin
-
Ah interesting.
Differences I can see between what you did and what I did:
You used the embedded kernel, I used the standard (SMP) kernel.
You disabled stuff in the bios, I didn't.I chose to use the standard kernel since most people who want to do a full install do so because they want to use all the packages. None of which are available with the embedded kernel. Why are you using a HD?
I may have to go back and test again. Thanks for your results.
Steve
-
steve, i dont think the stuff that i disabled in the bios would make much difference, i only disabled the stuff that wasnt required like LPT1 and com2. guess its my old throw back to the old DOS days, trying to free up memory resources. As im new to freebsd i wasnt sure on how it managed its memory, even though i have 1Gb of ram installed in the box.
The reason i moved over to a HDD was that even though having a 16Gb sandisk CF card installed. i was running in to issues trying to load packages, i was attempting to run snort and dansguardian and the HVAP antivirus. but for some reason everytime HVAP would try and update it would overload the log files and use all the available memory and then crash the box.
Even though im using the embedded kernel, it looks like thier are more packages available, than what thier is on the nano CF card images. As i have noticed that freeswitch is now available for install. i will need to do a comparison between the nano and full installs to find out whats available, package wise that is.
Btw just seen the pic that you uploaded of your firebox setup. you need help ;D
im sure thier is bound to be a support group some of some kind for that kind of fixation lol.
do watchguard phone you up if they are looking for spares.Colin
-
Ah. Well that's interesting about packages with the embedded kernel. I must be confusing it with the old (pre-nano) embedded install. :-\
It can't hurt to free up resources. Even if you have loads of ram that won't help when you run out of interrupts or I/O address space because some device is misbehaving.
The reason you were having trouble with HAVP is likely that it uses /tmp to download update to. In the Nano install /tmp is a ramdrive of a fixed size that can be exceeded. Having a larger CF card won't help. In fact anything over 4GB isn't used anyway unless you rolled your own image for 16GB. It is possible to set the size of /tmp larger though if you have sufficient memory.
Yes I need help. ::)
It started out that I wanted to use pfSense at home and looking for suitable hardware. I wanted as many interfaces as I could reasonably afford for maximum isolation between network segments and reading through the forums the Firebox seemed an ideal platform. I was looking at X500s and X700s and ebay for a while when the X6000 came up for very little money and I couldn't resist. Then after I got more involved on the forum people were asking questions about boxes I didn't have and they were so cheap on ebay I couldn't resist. Then I was addicted! ;D
Just a few weeks ago some XTM5 boxes sold for ~£100. It was all I could do to resist. That's just stupid cheap compared to a 7 interface firewall platform new.Steve
-
Ive just checked the amount of packages available on the full install with the embeded kernel. i have 87 packages available for install. i dont have the nano image running at the moment so cant do a direct comparison between the two. but thier is definitely more packages available.
Colin
-
I appear to have 82 available under Nano.
If you look at the list xml file: http://www.pfsense.org/packages/pkg_config.8.xml there are 6 packages marked 'noembedded':
pure-ftpd
ntop
FreeSWITCH
FreeSWITCH Dev
Lightsquid
phpSysInfoClearly I've misunderstood quite what the embedded kernel provides. :-\
Steve
-
steve
I've Just been playing about with the PHPsysinfo package, it looks quite good at reporting back some of the data from the box regarding temps and disk/memory usage. it looks like thier might be an issue with the package reading the fan data back, but i think that might just be due to the monitoring chip in the box. The speeds reported are way out. i have your WGXepc app running and have the fans throttled back to 20% of normal.
A couple of screen grabs attached of the PHPsysinfo report.
Colin
-
Forgot to attach the second screen grab.
-
Nice!
Yes the PWM employed by the SuperIO chip to control the fan speed completely screws the speed readout once you go below a certain level. Hex value BB I seem to recall. That's why you can't use a value below BB in the bios for the initial fan speed. The completely fictitious huge values crash the bios setup code.Steve