News: This forum is now permanently frozen.
Pages: [1]
Topic: m0n0 hangs on boot  (Read 2230 times)
« on: August 28, 2008, 22:59:35 »
fryelectro *
Posts: 1

Hi,

I was trying to boot of from a 32 MB sandisk compactflash card using m0n0wall on an old watchguard firebox III 700 but after detecting ad0, the boot process hangs. I've copy/pasted the boot log below:

Code:
þ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.3-RELEASE-p1 #0: Sun Jul 13 11:32:41 CEST 2008

    root@mb63.neon1.net:/usr/src/sys/i386/compile/M0N0WALL_GENERIC

Timecounter "i8254" frequency 1193182 Hz quality 0

CPU: AMD-K6(tm) 3D processor (233.86-MHz 586-class CPU)

  Origin = "AuthenticAMD"  Id = 0x58c  Stepping = 12

  Features=0x8021bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX>

  AMD Features=0x80000800<SYSCALL,3DNow!>

real memory  = 134217728 (128 MB)

avail memory = 105119744 (100 MB)

wlan: mac acl policy registered

kbd1 at kbdmux0

K6-family MTRR support enabled (2 registers)

ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)

cpu0 on motherboard

pcib0: <AcerLabs M1541 (Aladdin-V) PCI host bridge> pcibus 0 on motherboard

pci0: <PCI bus> on pcib0

pcib1: <PCI-PCI bridge> at device 1.0 on pci0

pci1: <PCI bus> on pcib1

ohci0: <AcerLabs M5237 (Aladdin-V) USB controller> mem 0xc0000000-0xc0000fff irq 11 at device 2.00

ohci0: [GIANT-LOCKED]

usb0: OHCI version 1.0, legacy support

usb0: <AcerLabs M5237 (Aladdin-V) USB controller> on ohci0

usb0: USB revision 1.0

uhub0: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1

uhub0: 2 ports with 2 removable, self powered

isab0: <PCI-ISA bridge> at device 7.0 on pci0

isa0: <ISA bus> on isab0

atapci0: <AcerLabs M5229 UDMA33 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf400-0xf400

ata0: <ATA channel 0> on atapci0

ata1: <ATA channel 1> on atapci0

dc0: <Macronix 98715AEC-C 10/100BaseTX> port 0xf000-0xf0ff mem 0xc0001000-0xc00010ff irq 11 at de0

miibus0: <MII bus> on dc0

dcphy0: <Intel 21143 NWAY media interface> on miibus0

dcphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

dc0: Ethernet address: ff:ff:ff:ff:ff:ff

dc1: <Macronix 98715AEC-C 10/100BaseTX> port 0xec00-0xecff mem 0xc0001100-0xc00011ff irq 10 at de0

miibus1: <MII bus> on dc1

dcphy1: <Intel 21143 NWAY media interface> on miibus1

dcphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

dc1: Ethernet address: ff:ff:ff:ff:ff:ff

dc2: <Macronix 98715AEC-C 10/100BaseTX> port 0xe800-0xe8ff mem 0xc0001200-0xc00012ff irq 9 at dev0

miibus2: <MII bus> on dc2

dcphy2: <Intel 21143 NWAY media interface> on miibus2

dcphy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

dc2: Ethernet address: ff:ff:ff:ff:ff:ff

pmtimer0 on isa0

fdc0: <Enhanced floppy controller> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0

fdc0: [FAST]

atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0

atkbd0: <AT Keyboard> irq 1 on atkbdc0

kbd0 at atkbd0

atkbd0: [GIANT-LOCKED]

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

RTC BIOS diagnostic error 8<fixed_disk>

Timecounter "TSC" frequency 233864685 Hz quality 800

Timecounters tick every 1.000 msec

Fast IPsec: Initialized Security Association Processing.

IP Filter: v4.1.28 initialized.  Default = block all, Logging = enabled

md0: Preloaded image </mfsroot> 15728640 bytes at 0xc0a9c024

ad0: FAILURE - SETFEATURES SET TRANSFERstray irq7

 MODE status=51<READY,DSC,ERROR> error=4<ABORTED>

ad0: 30MB <SanDisk SDCFB-32 vdd 1.00> at ata0-master BIOSPIO

Trying to mount root from ufs:/dev/md0

kern.coredump: 1 -> 0

Found configuration on ad0.

Does anyone know what the reason could be ? I tried pfsense, and experience the same. DD-wrt which runs on linux boots fine, but I want to run m0n0wall Sad

Someone can help me ?

thanks

Tom
« Reply #1 on: October 16, 2008, 03:26:30 »
Radical *
Posts: 1

I have the same problem with a Firebox II

It seems to me someone else wrote about a work around for this problem on the web somewhere, guess I will have to go find the posting again.

In the mean time it would be great if some Firebox users could offer some suggestions.

Thanks,
Rad.
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines