Re: Version(s) working with BlizzardPPC

[Andreas <aw...@sw...>]

Hi Kulwant

On Sun, 2003-12-14 at 23:16, Kulwant Bhogal wrote:

> Hello Andi, 
> 
> > Though in /drivers/char/rtc.c there's a comment mentioning something
> > about periodic syncs (every 11 min) by time.c (line 54).. So you're
> > system should at least run for 11 min uninterrupted..
> 
> See below. 
> 
> > What you could also do is to
> 
> >   # mv /sbin/hwclock /sbin/OFFhwclock
> 
> > although this is really really ugly!! But it should prevent the system
> > from interacting with the hardware clock.
> 
> Ok, I did this. And no crashes.

Cool!

> It went on to configuring the base system
> etc. But I didn't really know what I was doing so I have quit out of that
> without installing or deleting anything. I didn't get to a shell either so I
> couldn't set the date even manually (as you suggested below).

Just Ctrl-Alt-F2 and there should be a shell IIRC.

> > Afterwards set the system clock using
> 
> >   # date 1214200003
> 
> Well the system did run in the configure base system section for ages (I
> left it alone for over an hour) and I didn't get any problems associated
> with the 11 min interupt you suggested above.

This is good news! Also that this clearly isolates the system crashes to
the hardware clock reads.

> > But this is definitely not how a productive system should be run! So,
> > try to get the dmesg output anyway and post it.
> 
> Try as I might I just don't get any debug output from dmesg. It simply says:
> 
> Searching for SAVEBOOT magic...
> Not found
> 
> I have tried starting wth no startup-sequence and before the reset from
> OS3.9 but still no joy. I inserted the -d in my start script like so: 
> 
> bootstrap --apus -k linux.bin -d -v root=/dev/hda2 rw nobats video=pm2fb:mode:1024x768-75
> 
> not sure what the -v is for.

The -v option stands for verbose IIRC (I guess it activates some
additional information for boothack, NOT the kernel itself).

> Is the -d in the right place?

Don't know about the place, but there's definitely something lacking,
you forgot to add the debug=mem part (or better, I didn't tell you about
it..). Please do like this:

bootstrap --apus -k linux.bin -v root=/dev/hda2 rw nobats
video=pm2fb:mode:1024x768-75 -d debug=mem

C.f. http://linux-apus.sourceforge.net/FAQ.html for full description.

> I did notice that I do get more prompts on running that script with the -d
> option in there.

I guess that's correct.

> So I think it is doing something. But Dmesg doesn't find
> any debug information after a reset.

Because you didn't tell it to save the stuff in the memory. Well, I
guess it was me who forgot to mention it in the last mail anyway..

> The other question is, is there a way
> of resetting the Linux side which cleanly unmounts my hda2 partition?

After the crash? I don't think so. Except if you can get a debug monitor
running maybe, but this is over my head ATM.

> And is there a way of resetting which will save the debug information too?

Well, I think debug=mem will do. It was just that this was lacking.
Sorry for that!

-- 
Best wishes,
Andi