[cobalt-users] Qube Update Qube3-All-Kernel-2.0.1-2.216C32-2III killed my Std Qube3

[Malcolm McLeary <mmcleary@xxxxxxx>]

Hi Guys,

I have a Std Qube3 which I got around to updating today ... the first update
went ok, the Qube rebooted and all services appeared to be ok.  After the
second update (Qube3-All-Kernel-2.0.1-2.216C32-2III), the Qube3 did not come
back ... it just sat there saying its booting.

As its a clients Qube3 I have extracted the disk and have installed it in a
Qube3 Pro Ed chassis.  The situation is now worse ... it still won't boot
but it now just says its Loading Kernel ... then cycles again, and again,
and again ...

Is it possible that a disk from a Std Qube3 is completely incompatible with
the Pro Ed hardware?

Is the previous kernel kept somewhere so it can be copied back if necessary?

Is there a way to boot from an alternate kernel?

Can I do a Std Qube3 OS restore on fresh disk in a Qube3 Pro Ed, put both
disks into the chassis and mount the "dead" filesystem with the view to copy
a working kernel onto it?

The LCD has an option to boot from ROM ... does this actually work?  Is it
possible to boot from ROM and replace the problem?

Cheers,  Malcolm