From: Andreas <aw...@sw...> - 2003-12-14 15:54:25
|
Hi Kulwant On Sun, 2003-12-14 at 04:20, Kulwant Bhogal wrote: > > If it doesn't work yet, you could also rename the hwclockfirst.sh call, > > although it doesn't seem to write to the clock. > > > # cd etc/rcS.6/ > > # mv S18hwclockfirst.sh offS18hwclockfirst.sh > > > But I would heavily advise against it, because then nothing is setting > > the system clock (system clock != hardware clock), which could lead to > > strange behaviour of the system. > > Well, I did try that (because all else before that had failed) and I got: > > Congratulations, You have successfully installed Yeah, so we've got one step further! :) > and after the message about how to revisit the setup process (by running > /usr/sbin/base-config) I got another kernel panic: > > Loading /etc/console/boottime.kmap.gz > > kernel access of bad area pc c00dca04 lr c00de9f8 address 70 tsk hwclock/230 > task = c65dc000[230] 'hwclock' ^^^^^^^^^ So you really seem to have a major problem with the hw clock! Is the contact between the ppc board and the motherboard ok? Where does the clock actually reside (motherboard or ppc)? Is it some strange non-standard chip? > mm-> pgd c6e2c000 last syscall: 6 > > GPR00: 00001072 C65DDE10 C65DC000 00000001 00008000 00000000 > C6E09D80 C980000 > > GPR08: 0000000B 00000000 C0180000 C67EC08C 2422 > > and then it rebooted before I could write down the rest of it. Can you add -d debug to your bootstrap line, and after the kernel oops reboot run dmesg > ram:output in the shell (amigaOS side)? Post the output here. I hope some of the kernel gurus can do something about it. > So I guess you were right about it leading to strange behaviour of the > system :-) Well, this wasn't particularly what I've been thinking about w.r.t. strange behaviour, because it seemed to crash again during an attempt to read the hwclock. > But it appears to be the furthest I have got so far :-) Well, the goal would be to run, not just crash every other minute.. -- Best wishes, Andi |