Installation

I have been successful write embeded-1.33.img onto 512M CF card.
My Hardward is topfilter 7504-antivirus, a product from chinese's company.
when it boot up, the console message show as follow:
Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.4-RELEASE-p5 #0: Sun Jan  9 22:24:57 CET 2011
    root@mb64.neon1.net:/usr/src/sys/i386/compile/M0N0WALL_EMBEDDED
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Celeron(R) M processor         1.50GHz (1499.96-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x6d8  Stepping = 8
  Features=0xafe9fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE>
  AMD Features=0x100000<NX>
real memory  = 1072693248 (1023 MB)
avail memory = 1039798272 (991 MB)
MPTable: <OEM00000 PROD00000000>
ioapic0: Assuming intbase of 0
ioapic0 <Version 2.0> irqs 0-23 on motherboard
wlan: mac acl policy registered
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
cpu0 on motherboard
pcib0: <Host to PCI bridge> pcibus 0 on motherboard
pir0: <PCI Interrupt Routing Table: 13 Entries> on motherboard
pci0: <PCI bus> on pcib0
pci0: <base peripheral> at device 0.1 (no driver attached)
pci0: <base peripheral> at device 0.3 (no driver attached)
pci0: <display, VGA> at device 2.0 (no driver attached)
pci0: <display> at device 2.1 (no driver attached)
pci0: <serial bus, USB> at device 29.0 (no driver attached)
ehci0: <Intel 82801DB/L/M (ICH4) USB 2.0 controller> mem 0xe8200000-0xe82003ff irq 7 at device 29.7 on pci0
ehci0: [GIANT-LOCKED]
usb0: EHCI version 1.0
usb0: wrong number of companions (1 != 0)
usb0: <Intel 82801DB/L/M (ICH4) USB 2.0 controller> on ehci0
usb0: USB revision 2.0
uhub0: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
pcib1: <PCIBIOS PCI-PCI bridge> at device 30.0 on pci0
pci1: <PCI bus> on pcib1
pci1: <network, ethernet> at device 4.0 (no driver attached)
pci1: <network, ethernet> at device 5.0 (no driver attached)
pci1: <network, ethernet> at device 6.0 (no driver attached)
pci1: <network, ethernet> at device 7.0 (no driver attached)
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH4 UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
pmtimer0 on isa0
orm0: <ISA Option ROM> at iomem 0xc0000-0xcc7ff on isa0
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A, console
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
unknown: <PNP0c01> can't assign resources (memory)
unknown: <PNP0501> can't assign resources (port)
unknown: <PNP0501> can't assign resources (port)
Timecounter "TSC" frequency 1499957873 Hz quality 800
Timecounters tick every 1.000 msec
Fast IPsec: Initialized Security Association Processing.
IP Filter: v4.1.33 initialized.  Default = block all, Logging = enabled
ad0: 488MB <SanDisk SDCFB-512 HDX 2.15> at ata0-master PIO4

Manual root filesystem specification:
  <fstype>:<device>  Mount <device> using filesystem <fstype>
                       eg. ufs:da0s1a
  ?                  List valid disk boot devices
  <empty line>       Abort manual input

mountroot>

what's wrong with the boot process? how to fix it?

Try the generic-pc (or generic-pc-serial) image first - embedded is only for Soekris and PC Engines boxes, and will probably not support the network controllers of your box.

well, I have been try generic-pc-serial-1.33 already, but it display nothing on my SecuCRT(serial) windows. so I switch to embeded version.

I am running m0n0wall on GTA GB-1000 hardware. The serial console does not work for me either with the generic-pc-serial image.

I worked around the problem booting the CF card on another system that has the same ethernet adapters as the GB-1000 and doing the minimal configuration there (assign interfaces and LAN IP address). Then I move the CF card back to the GB-1000 and complete the configuration via the now reachable web GUI.

I wish I could get the console working, but I can live without it. Maybe in a future release? Console does work with pfsense 1.2.3, and the original GB-1000 software, so the hardware is known good.

Good luck.

brilliant method!
I will try it when I back home.

brilliant method!
I will try it when I back home.

Our most helpful member brushedmoss suggested that method to me. It saved the hardware for m0n0wall usage. pfsense works with console, but I'd don't need all that.

 
actually, I success installed pfsense-1.2.2 onto the werid appliance last night, but failed to installed 1.2.3 version, encounter this error:
elf32_loadimage: read failed

you may have a bad media or image. 

if 1.2.2 worked put 1.2.2 back on, and check your interface names.  you could then edit default.xml on your m0n0wall media to use these interface names instead of the default.  This is what fredg achieved with his method....

serial seems to not work as expected on all platforms, it did work on various hardware I tested, but they are not appliances of this nature ...

you may have a bad media or image. 

if 1.2.2 worked put 1.2.2 back on, and check your interface names.  you could then edit default.xml on your m0n0wall media to use these interface names instead of the default.  This is what fredg achieved with his method....

nope, I mean pfsense 1.2.2 could be installed and boot successfully, but pfsense 1.2.3 failed to boot correctly, there is nothing to do with media, actually, the error was caused by freebsd 7.2.

pfsense 1.2.2 based on 7.0, 1.2.3 based on 7.2