Well... after some various testing, reburning of flash cards, etc... here is the synopsis:
Monowall 1.3b11 - crashes on boot
Monowall 1.233 - boots, passes traffic, works perfectly with no problems
pfSense 1.2-RELEASE - boots, acts a bit flakey, shows resource errors in the logs, possibly due to
low ram (128MB)
pfSense 1.2-RELEASE(6.3 Base) - boots OK until it's time to mount the root file system at which
point it fails. There seems to be an error related to the disk controller. Carsten Holbach said "2)
Beware: The latest version of m0n0wall has problems with the IDE controller in the Neoware NE2000,
at least.". It is likely that this is the root of the boot problem on this EON6000S...
So, it appears that this box will be running 1.233. I'm glad that monowall will run on it as it has
a lighter footprint and much faster boot times over it's later counterpart. If anyone is interested
in further exploring problems with the 6.2 vs 6.3 issue, I'm happy to lend my time and box. If full
logs are needed, please let me know.
Thank you all for the help and suggestions!
----- Original Message -----
From: "Chris Buechler" <cbuechler at gmail dot com>
Cc: "m0n0wall -" <m0n0wall at lists dot m0n0 dot ch>
Sent: Wednesday, May 21, 2008 8:21:12 PM GMT -06:00 Guadalajara / Mexico City / Monterrey
Subject: Re: [m0n0wall] Kernel Panic on Boot... Help?
On Wed, May 21, 2008 at 8:48 PM, Tim Nelson <tnelson at rockbochs dot com> wrote:
> I really should pick up a vlan capable switch... I'm still running a few various gross desktop
switches here and there at home... :-(
> Interestingly enough, I thought I'd give pfSense a shot for "gits and shiggles" and it boots just
fine recognizing the onboard realtek nic and the two additional interfaces on the pci card. I did
notice though that I still see a "$PIR: ROUTE_INTERRUPT failed." during bootup but it doesn't hang.
Are there significant changes between FreeBSD 6.3(base for monowall 1.3bx series) and FreeBSD
6.2(base for pfSense 1.2-RELEASE series)? I will try a current non-beta version of monowall to see
if it makes any difference.
That's strange, I figured it was either some sort of IRQ handling
issue in that board, or a bug in FreeBSD 6.x. A regression from 6.2 to
6.3 is possible. An additional test would be to try a FreeBSD
6.3/pfSense 1.2 images:
To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch