From: Peter E. <Pet...@un...> - 2004-08-17 08:10:46
|
Hi, I've seen this on broken systems, that is with faulty power supply or bad condensators on the main board, etc. To figure out if this is the case, I suggest to boot some stand-alone linux on it (knoppix or some boot floppy) and do some heavy disk i/o (e.g. find) and memory test. You may also try some boot options with the CM boot kernel to turn off apm or use less memory. Another possible reason may be that your kernel didn't fit on the floppy and this is why it crashes. Best, Peter. On Mon, Aug 16, 2004 at 10:17:13PM -0700, Vipul Deokar wrote: > Thanks Michal. > > I used your suggestion, and tried booting directly off > floppy and then disk on slave from phase 2 kernel and > initrd image. However, as soon as control passes to > this kernel the system resets to the BIOS - I can't > even see the message that gets printed momentarily > before the reset. > > So, it looks like a beoboot issue for generating the > kernel. The same kernel image is running fine on the > master node, of course with a different initrd image. > Has anyone seen this? > > Thanks. > Vipul |