WG X1250e Question
-
Hey guys, I have a few questions I got a WG X1250e from eBay. I was not able to ever get it too boot to the bios can't see it at all…but i have the free dos on the original 256meg card.....so i was never able to get c:/ to flash bios, modified autoexec file to run awdflash and flash with b8.1, when i put pfsense on a 4gig card booted now i have Tera term 115200 8n1 hardware flow..... after about 3-5 min it finally shows it start to booting..... Is this normal? seems like it is awful slow.... I was just trying to figure out why it would take so long to boot....Also I can press the Up button to do a factory recovery it will show Recovery Version 1.00 Good Magic number WG: bad partition Verifying CHS Reading MBR WG Header etc.... Does this mean the bios may not have flashed all the way.....even after i waited 30 mins for the b8 ver. to flash I still have yet to see any screen to hit tab or any other key to get into bios any thoughts i could try
Thanks, sorry if i posted this in wrong area....Been working on this thing for 4 days almost straight
Robert
-
Hi Robert,
Hmm, well that doesn't sound good. So you never managed to boot into FreeDOS? Did you hear the three beeps?
Try a smaller CF card if you can find one, the smaller the better. My 16MB card has never failed to boot in anything.Steve
-
Yes got the 3 beeps right now i have a 4 gig booting pfsense…... but takes about 3-5 mins before umm what does it start with boot config..???? then starts to load pfsense. I have run smallwall it starts booting within about 30 sec. after seeing booting os. I used the 256 meg card that came with it i put the freedos imiage on it and the only way i could get it to flash the bios was to modify the autoexec.bat file to run awdflash i think that was all i put in the file.... it taking 3-5 mins to start booting Normal
Rob
-
Sorry forgot to ask Does the 3 beeps mean that free dos is loaded? wonder if there is any stuff i need to add or take out of the autoexec.bat file
Also I noticed that if i put m0n0 wall or small wall on the 256meg card or pfsense on the 4 gig card. While in the reader/writer i can't access it but if i load the freedos on the 256meg card i can open the flash card on the pc and look at it. Would i assume that would be correct? or should i not be able to do that with any of the images
-
That's correct the FreeDOS image is FAT (maybe FAT32?) that Windows etc can read but pfSense and others are UFS which Windows can't read.
The three beeps means it's booted the FreeDOS image and run the autoexec file. Just after that it switches to the serial console at 9600bps. If you don't see that but can see the pfSense console then you probably have a console cable without the required connections. https://doc.pfsense.org/index.php/PfSense_on_Watchguard_Firebox#Not_All_Null_Modem_Cables_are_Created_Equal.21
It's hard to say why it waits so long to boot. If you have a large amount of RAM (2GB) and set the console speed to 9600 it takes a while to count it. Maybe your console connection is causing a problem.
It shouldn't take anywhere near that long to start booting up.
Steve
-
the only way i see anything from terminal is when i have it set at 115200 8N1 hardware flow…...I do have 2 gigs in it
I just upgraded to 2.2.3 and now it just restarted when i tried to halt system....and keeps doing it Hmmm maybe a fresh install of 2.2.3 instead of udgrade???
Rob
-
It has no way to halt as the power supply doesn't have an on button. If it halted correctly you would have no way to turn it back on again.
I agree though that perhaps shouldn't reboot. Did you enable ACPI in the BIOS?If you never saw the output at 9600 from FreeDOS that it's almost certainly the cable issue.
Does it boot quicker if you don't have a serial terminal connected to it?
Steve
-
I am not able to get into the bios at all…...maybe i should order another cable......any suggestions.....I will check the load times without serial cable in
post back:
I cut my cable open LOL it has 4 wires 1 3 5 is soldered with i am guessin black one was soldered to metal case for ground. what i found out is it is a Null modem without handshaking do i need a Null modem with loop back handshaking or partial handshaking??? I have 2 ends now i can make one if need be :)
Rob
-
Ok I got everything working thus far…..2 more qustions I have 1 i noticed when i boot pfsense i get to choose either option 1 or 2 is there a way to bypass this at all? 2nd question is I have in the loading up ata0: timeout waiting to write DRQ can anyone tell me how to fix this?
I am running x1250e 4 gig (new) cf card 2 gigs ram 2.2.3 fresh install. Did i miss turning something off
Robert
Thanks for all your help guys ;D ;D ;D ;D -
Generally you need the 1 or 2 choice, it's how NanoBSD works. That's the bootloader giving you the choice of which slice to boot. It you damage one slice you need that choice there to be able to select the other slice to boot into.
I'm not familiar with that particular error do you have and further logs showing when it occurs and what the result is?
Steve
-
Generally you need the 1 or 2 choice, it's how NanoBSD works. That's the bootloader giving you the choice of which slice to boot. It you damage one slice you need that choice there to be able to select the other slice to boot into.
I'm not familiar with that particular error do you have and further logs showing when it occurs and what the result is?
Steve
Here is what I have on the boot up. If there is anything i need to fix please let me know
Robert
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel] in 4 seconds… Booting [/boot/kernel/kernel] in 3 seconds… Booting [/boot/kernel/kernel]…
|/-|/-KDB: debugger backends: ddb
KDB: current backend: ddb
ACPI BIOS Error (bug): A valid RSDP was not found (20130823/tbxfroot-223)
Copyright (c) 1992-2014 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 10.1-RELEASE-p13 #0 c77d1b2(releng/10.1)-dirty: Tue Jun 23 17:06:06 CDT 2015
root@pfs22-i386-builder:/usr/obj.i386/usr/pfSensesrc/src/sys/pfSense_wrap.10.i386 i386
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
VT: running with driver "vga".
module_register: module pci/mskc already exists!
Module pci/mskc failed to register: 17
module_register: module mskc/msk already exists!
Module mskc/msk failed to register: 17
module_register: module msk/miibus already exists!
Module msk/miibus failed to register: 17
module_register: module pci/skc already exists!
Module pci/skc failed to register: 17
module_register: module skc/sk already exists!
Module skc/sk failed to register: 17
module_register: module sk/miibus already exists!
Module sk/miibus failed to register: 17
CPU: Intel(R) Celeron(R) M processor 1300MHz (1300.07-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x695 Family = 0x6 Model = 0x9 Stepping = 5
Features=0xa7e9fbbf <fpu,vme,de,pse,tsc,msr,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,clflush,dts,acpi,mmx,fxsr,sse,sse2,tm,pbe>real memory = 2146435072 (2047 MB)
avail memory = 2071597056 (1975 MB)
MPTable: <oem00000 prod00000000="">Event timer "LAPIC" quality 400
random device not loaded; using insecure entropy
ioapic0: Assuming intbase of 0
ioapic0 <version 2.0="">irqs 0-23 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, 0xc08122b0, 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, 0xc0812360, 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, 0xc0812410, 0) error 1
iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_bss_fw, 0xc083aa40, 0) error 1
iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_ibss_fw, 0xc083aaf0, 0) error 1
iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_monitor_fw, 0xc083aba0, 0) error 1
wlan: mac acl policy registered
kbd1 at kbdmux0
random: <software, yarrow="">initialized
ACPI BIOS Error (bug): A valid RSDP was not found (20130823/tbxfroot-223)
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
vgapci0: <vga-compatible display="">port 0xea00-0xea07 mem 0xd0500000-0xd057ffff,0xc0000000-0xcfffffff,0xd0580000-0xd05bffff irq 16 at device 2.0 on pci0
agp0: <intel 82915gm="" (915gm="" gmch)="" svga="" controller="">on vgapci0
agp0: aperture size is 256M, detected 764k stolen memory
vgapci0: Boot video device
pcib1: <mptable pci-pci="" bridge="">irq 16 at device 28.0 on pci0
pci1: <pci bus="">on pcib1
mskc0: <marvell yukon="" 88e8053="" gigabit="" ethernet="" (led="" mod="" 2.2)="">port 0x8000-0x80ff mem 0xd0020000-0xd0023fff irq 16 at device 0.0 on pci1
msk0: <marvell technology="" group="" ltd.="" yukon="" ec="" id="" 0xb6="" rev="" 0x02="">on mskc0
miibus0: <mii bus="">on msk0
e1000phy0: <marvell 88e1111="" gigabit="" phy="">PHY 0 on miibus0
e1000phy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
pcib2: <mptable pci-pci="" bridge="">irq 17 at device 28.1 on pci0
pci2: <pci bus="">on pcib2
mskc1: <marvell yukon="" 88e8053="" gigabit="" ethernet="" (led="" mod="" 2.2)="">port 0x9000-0x90ff mem 0xd0120000-0xd0123fff irq 17 at device 0.0 on pci2
msk1: <marvell technology="" group="" ltd.="" yukon="" ec="" id="" 0xb6="" rev="" 0x02="">on mskc1
miibus1: <mii bus="">on msk1
e1000phy1: <marvell 88e1111="" gigabit="" phy="">PHY 0 on miibus1
e1000phy1: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
pcib3: <mptable pci-pci="" bridge="">irq 18 at device 28.2 on pci0
pci3: <pci bus="">on pcib3
mskc2: <marvell yukon="" 88e8053="" gigabit="" ethernet="" (led="" mod="" 2.2)="">port 0xa000-0xa0ff mem 0xd0220000-0xd0223fff irq 18 at device 0.0 on pci3
msk2: <marvell technology="" group="" ltd.="" yukon="" ec="" id="" 0xb6="" rev="" 0x02="">on mskc2
miibus2: <mii bus="">on msk2
e1000phy2: <marvell 88e1111="" gigabit="" phy="">PHY 0 on miibus2
e1000phy2: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
pcib4: <mptable pci-pci="" bridge="">irq 19 at device 28.3 on pci0
pci4: <pci bus="">on pcib4
mskc3: <marvell yukon="" 88e8053="" gigabit="" ethernet="" (led="" mod="" 2.2)="">port 0xb000-0xb0ff mem 0xd0320000-0xd0323fff irq 19 at device 0.0 on pci4
msk3: <marvell technology="" group="" ltd.="" yukon="" ec="" id="" 0xb6="" rev="" 0x02="">on mskc3
miibus3: <mii bus="">on msk3
e1000phy3: <marvell 88e1111="" gigabit="" phy="">PHY 0 on miibus3
e1000phy3: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
uhci0: <intel 82801fb="" fr="" fw="" frw="" (ich6)="" usb="" controller="" usb-a="">port 0xeb00-0xeb1f irq 23 at device 29.0 on pci0
usbus0 on uhci0
uhci1: <intel 82801fb="" fr="" fw="" frw="" (ich6)="" usb="" controller="" usb-b="">port 0xed00-0xed1f irq 19 at device 29.1 on pci0
usbus1 on uhci1
uhci2: <intel 82801fb="" fr="" fw="" frw="" (ich6)="" usb="" controller="" usb-c="">port 0xe800-0xe81f irq 18 at device 29.2 on pci0
usbus2 on uhci2
uhci3: <intel 82801fb="" fr="" fw="" frw="" (ich6)="" usb="" controller="" usb-d="">port 0xe900-0xe91f irq 16 at device 29.3 on pci0
usbus3 on uhci3
ehci0: <intel 82801fb="" (ich6)="" usb="" 2.0="" controller="">mem 0xd05c0000-0xd05c03ff irq 23 at device 29.7 on pci0
usbus4: EHCI version 1.0
usbus4 on ehci0
pcib5: <mptable pci-pci="" bridge="">at device 30.0 on pci0
pci5: <pci bus="">on pcib5
skc0: <marvell gigabit="" ethernet="" (led="" mod="" 2.2)="">port 0xc000-0xc0ff mem 0xd042c000-0xd042ffff irq 16 at device 0.0 on pci5
skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9)
sk0: <marvell semiconductor,="" inc.="" yukon="">on skc0
miibus4: <mii bus="">on sk0
e1000phy4: <marvell 88e1011="" gigabit="" phy="">PHY 0 on miibus4
e1000phy4: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
skc1: <marvell gigabit="" ethernet="" (led="" mod="" 2.2)="">port 0xc400-0xc4ff mem 0xd0420000-0xd0423fff irq 17 at device 1.0 on pci5
skc1: Marvell Yukon Lite Gigabit Ethernet rev. (0x9)
sk1: <marvell semiconductor,="" inc.="" yukon="">on skc1
miibus5: <mii bus="">on sk1
e1000phy5: <marvell 88e1011="" gigabit="" phy="">PHY 0 on miibus5
e1000phy5: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
skc2: <marvell gigabit="" ethernet="" (led="" mod="" 2.2)="">port 0xc800-0xc8ff mem 0xd0424000-0xd0427fff irq 18 at device 2.0 on pci5
skc2: Marvell Yukon Lite Gigabit Ethernet rev. (0x9)
sk2: <marvell semiconductor,="" inc.="" yukon="">on skc2
miibus6: <mii bus="">on sk2
e1000phy6: <marvell 88e1011="" gigabit="" phy="">PHY 0 on miibus6
e1000phy6: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
skc3: <marvell gigabit="" ethernet="" (led="" mod="" 2.2)="">port 0xcc00-0xccff mem 0xd0428000-0xd042bfff irq 19 at device 3.0 on pci5
skc3: Marvell Yukon Lite Gigabit Ethernet rev. (0x9)
sk3: <marvell semiconductor,="" inc.="" yukon="">on skc3
miibus7: <mii bus="">on sk3
e1000phy7: <marvell 88e1011="" gigabit="" phy="">PHY 0 on miibus7
e1000phy7: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
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
ata0: <ata channel="">at channel 0 on atapci0
ata1: <ata channel="">at channel 1 on atapci0
cpu0 on motherboard
p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
pmtimer0 on isa0
attimer0: <at timer="">at port 0x40-0x43 irq 0 pnpid PNP0100 on isa0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
atrtc0: <at realtime="" clock="">at port 0x70-0x71 irq 8 pnpid PNP0b00 on isa0
Event timer "RTC" frequency 32768 Hz quality 0
atkbdc0: <keyboard controller="" (i8042)="">at port 0x60,0x64 irq 1 pnpid PNP0303 on isa0
atkbd0: <at keyboard="">irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
unknown: <pnp0c01>can't assign resources (memory)
uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 flags 0x10 pnpid PNP0501 on isa0
uart0: console (115200,n,8,1)
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
ppbus0: <parallel port="" bus="">on ppc0
lpt0: <printer>on ppbus0
lpt0: Interrupt-driven port
ppi0: <parallel i="" o="">on ppbus0
uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 pnpid PNP0501 on isa0
orm0: <isa option="" rom="">at iomem 0xc0000-0xce7ff pnpid ORM0000 on isa0
unknown: <pnp0c01>can't assign resources (memory)
random: unblocking device.
usbus0: 12Mbps Full Speed USB v1.0
Timecounters tick every 1.000 msec
IPsec: Initialized Security Association Processing.
usbus1: 12Mbps Full Speed USB v1.0
usbus2: 12Mbps Full Speed USB v1.0
usbus3: 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
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
ugen4.1: <intel>at usbus4
uhub4: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus4
ada0 at ata0 bus 0 scbus0 target 0 lun 0
ada0: <cf card="" ver7.02k="">ATA-5 device
ada0: Serial Number 5B5519400
ada0: 16.700MB/s transfers (PIO4, PIO 512bytes)
ada0: 3811MB (7806960 512 byte sectors: 16H 63S/T 7745C)
ada0: Previously was known as ad0
Timecounter "TSC" frequency 1300072794 Hz quality 800
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
uhub2: 2 ports with 2 removable, self powered
uhub3: 2 ports with 2 removable, self powered
Root mount waiting for: usbus4
Root mount waiting for: usbus4
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/ufs/pfsense0 [ro,sync,noatime]…
Configuring crash dumps...
/dev/ufs/pfsense0: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/ufs/pfsense0: clean, 1433158 free (1566 frags, 178949 blocks, 0.1% fragmentation)
/dev/ufs/cf: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/ufs/cf: clean, 90663 free (47 frags, 11327 blocks, 0.0% fragmentation)
Filesystems are clean, continuing...
Mounting filesystems...
Setting up memory disks... done.___
/ f
/ p _/ Sense
_/
__/Welcome to pfSense 2.2.3-RELEASE ...
Creating symlinks......ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib
a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout
done.
External config loader 1.0 is now starting...
Launching 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.
Configuring loopback interface...done.
Starting syslog...done.
Starting Secure Shell Services...done.
Setting up polling defaults...done.
Setting up interfaces microcode...done.
Configuring loopback interface...done.
Creating wireless clone interfaces...done.
Configuring LAGG interfaces...done.
Configuring VLAN interfaces...done.
Configuring QinQ interfaces...done.
Configuring WAN interface...done.
Configuring LAN interface...done.
Configuring CARP settings...done.
Syncing OpenVPN settings...done.
Configuring firewall......done.
Starting PFLOG...done.
Setting up gateway monitors...done.
Synchronizing user settings...done.
Starting webConfigurator...done.
Configuring CRON...done.
Starting DNS Resolver...done.
Starting NTP time client...done.
Starting DHCP service...done.
Starting DHCPv6 service...done.
Configuring firewall......done.
Generating RRD graphs...done.
Starting syslog...done.
Starting CRON... done.
Jul 2 16:54:51 php-fpm[6397]: /rc.start_packages: Restarting/Starting all packages.
Starting package LCDproc-dev…done.
Starting package Shellcmd...done.
pfSense (nanobsd) 2.2.3-RELEASE i386 Tue Jun 23 16:37:33 CDT 2015
Bootup complete2nd time i rebooted i got this
Welcome to pfSense 2.2.3-RELEASE …
Creating symlinks......ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib
a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout
done.
ata0: timeout waiting for write DRQ
External config loader 1.0 is now starting...
Launching the init system...ata0: timeout waiting for write DRQ
ata0: timeout waiting for write DRQ
ata0: timeout waiting for write DRQ
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.
Configuring loopback interface...done.
Starting syslog...done.
Starting Secure Shell Services...done.
Setting up polling defaults...done.
Setting up interfaces microcode...done.
Configuring loopback interface...done.
Creating wireless clone interfaces...done.
Configuring LAGG interfaces...done.
Configuring VLAN interfaces...done.
Configuring QinQ interfaces...done.
Configuring WAN interface...done.
Configuring LAN interface...done.
Configuring CARP settings...done.
Syncing OpenVPN settings...done.
Configuring firewall......done.
Starting PFLOG...done.
Setting up gateway monitors...done.
Synchronizing user settings...done.
Starting webConfigurator...done.
Configuring CRON...done.
Starting DNS Resolver...done.
Starting NTP time client...done.
Starting DHCP service...done.
Starting DHCPv6 service...done.
Configuring firewall......done.
Generating RRD graphs...done.
Starting syslog...done.
ata0: timeout waiting for write DRQ
Starting CRON... done.
Starting package LCDproc-dev...done.
Starting package Shellcmd...done.
pfSense (nanobsd) 2.2.3-RELEASE i386 Tue Jun 23 16:37:33 CDT 2015
Bootup complete</cf></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></pnp0c01></isa></parallel></printer></parallel></standard></pnp0c01></at></keyboard></at></at></cpu></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></marvell></mii></marvell></marvell></pci></mptable></marvell></mii></marvell></marvell></pci></mptable></marvell></mii></marvell></marvell></pci></mptable></marvell></mii></marvell></marvell></pci></mptable></intel></vga-compatible></pci></mptable></software></software,></version></oem00000></fpu,vme,de,pse,tsc,msr,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,clflush,dts,acpi,mmx,fxsr,sse,sse2,tm,pbe> -
Hmm, well it seems to be complaining about the Marvel NIC kernel modules you are loading but it is loading them you can see the modified output in the boot log.
I haven't seen that DRQ error before and the only references to it imply a failing CF card however you say this is new. It may be nothing to worry about if for example the CF you're using is particularly slow for some reason. The force sync change in 2.2.3 maybe? Keep an eye on the logs for it happening during normal running.
Steve
-
What about the ACPI should i disable that. The card may have issues I am going to put in a hard drive as soon as i get my adapter in. I will keep eye out on the card who knows it could be a bad one from the start.
Also Is there a way to have both wan and lan ports open if the system crashes or something like that. To keep internet working? I have it set up this way
Modem–-------WG x1250e--------Netgear wireless router--------netgear 24port switch------To the computers,tv's etc......
Robert
Hmm, well it seems to be complaining about the Marvel NIC kernel modules you are loading but it is loading them you can see the modified output in the boot log.
I haven't seen that DRQ error before and the only references to it imply a failing CF card however you say this is new. It may be nothing to worry about if for example the CF you're using is particularly slow for some reason. The force sync change in 2.2.3 maybe? Keep an eye on the logs for it happening during normal running.
Steve
-
You should keep ACPI enabled generally. It gives you the CPU temperature among other things. Modern OSs usually expect it. I've not seen any issues using it with 2.2.X.
There is no way of having the WAN and LAN connect together within the Firebox. That feature is known as LAN By-pass and is included in some appliances. Generally you would never want that in a firewall as it exposes the LAN to whatever traffic is coming from the WAN.
Steve
-
sounds great…. just wanted to see if there was a way to keep internet up in case something happen to the box. Just put in a new processor and wainting on a new hd adapter so i can install a hard drive.
Rob
