Re: [cobalt-developers] Need to build a RaQXTR/550 kernel

[josh <josh@xxxxxxxxxxxxxxxxxx>]

This is a little premature as I haven't had a chance to take down my
RaQXTR/550 and check out things. I've been using the ROM kernel in
production for almost five days now - the only problem is I'm using an
additional 10K of Swap each day.

As long as we are discussing ROMs - and I say this without having
had a chance to rollback to my backup yet and check out the flashtool
and alternate kernels - I would really like to know the following.

If I read the FAQ right, the 550 has only two memory slots while the
XTR has four (all filled in my case). The 550 has space for two disks
and the XTR has four (all filled in my case). I'm running romrev
2.9.34. How does the rom get the information on memory and disks? It
is not setable in my version and the rom reports only 1/4 the memory
that is really there. (based on the results of memtest which reads the
info from the ROM using the standard linux methods). The cmos commands
seem limited -- are there multiple versions of the cmos program for
the different romrevs?

On Tue, Dec 16, 2003 at 09:11:05AM -0500, Gerald Waugh wrote:
> On Mon, 15 Dec 2003, Tim Hockin wrote:
> >
> > I've started a 'Cobalt Hacking FAQ'.  I'm up for adding new items, if people
> > have good stuff to put in there ;)
> >
> > http://www.hockin.org/~thockin/cobalt-hack-faq.html
> 
> Is it possible to get a little detail on the ROM commands available when
> running in ROM mode? What does each one do?
> 
> Also, AFAIK, you can't convert a ROM version from > 2.9.x to 2.3.x using
> the flashtool. Is this true?
> 
> Gerald
> --
> http://frontstreetnetworks.com | http://store.raqware.com
>   Front Street Networks LLC, 229 Front Street, Ste.#C
>   New Haven, CT 06513-3203 | phone: +1-203-785-0699
> 
> _______________________________________________
> cobalt-developers mailing list
> cobalt-developers@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-developers

-- 
Josh Kuperman                       
josh@xxxxxxxxxxxxxxxxxx