5.2.1 on a Cabriolet?

[Michael DeLisle]

On Mar 19, 2004, at 11:20 PM, Rob B wrote:

> Kirk Strauser wrote:
>> I'm using a PC64 (from dmesg: "Digital AlphaPC 64 274 MHz, 274MHz") 
>> with
>> three fxp cards as a firewall/router.  The machine is currently 
>> running
>> 4.9-STABLE, but I imagine that I'll be needing to upgrade to 5.x at 
>> some
>> time soon when that becomes the stable branch.
>> Right now, I'm using 5-CURRENT on a few x86 servers with great 
>> success, but
>> I don't want to attempt to upgrade my router until I feel fairly 
>> confident
>> that I can do it without too much downtime or emergency restoral from
>> backups.  So, does anyone have an opinion on whether 5.2.1 would 
>> probably be
>> stable enough to upgrade at this time, or would I be better off 
>> waiting
>> until 5-STABLE comes along?
>> On the one hand, I don't want to upgrade prematurely.  On the other 
>> hand, I
>> don't want to wait until the 4-STABLE brance is completely dead so 
>> that I
>> have no real fallback position if I encounter some weird hardware
>> incompatibility.
>
> Kirk,
>
> I was never able to get anything higher that 5.1-RELEASE booting on 
> this box
>
> I wrote:
>
> <snip>
> jumping to bootstrap code
> loading /boot/loader
> |
> halted CPU 0
>
> halt code = 2
> kernel stack not valid halt
> PC = 7000000f0000
> boot failure
>
> There doesn't appear to be a /boot/loader.old that I can load either.
>
> I'm in the process of trying John Baldwins floppies - see recent 
> posings on that
>
> cheers,
> Rob


	FWIW, I'm currently running 5.2.1 on a Cabriolet:
(from dmesg)

FreeBSD 5.2.1-RELEASE #1: Fri Feb 27 04:16:45 EST 2004
     root at alpha-trion.nexthop.net:/usr/obj/usr/src/sys/ALPHA-TRION
Preloaded elf kernel "/boot/kernel/kernel" at 0xfffffc0000770000.
EB64+
Digital AlphaPC 64 274 MHz, 274MHz

	I was able to install 5.2-release (via cdrom) and cvsup to 
5.2.1-release successfully.

	I had some problems running 5.2 as a bridging firewall, the box would 
randomly reboot on me from time to time.  I never troubleshot the 
issue, and haven't tried the bridging firewall again with 5.2.1.

	5.2.1 however has been stable enough to run my squid proxy, bind9, and 
various scripts.

--mike.d