From: Kulwant B. <kul...@bt...> - 2003-12-14 03:02:35
|
Hello Andi, > Hmm, since normal booting doesn't work for you, boot with the install > image: > 1) go directly to the step of the installer where you can mount > partitions. There, you choose your root partition. IIRC it gets mounted > under /target/. > 2) go to the step where you can open a shell. Then > # cd /target/ > # cd etc/rcS.d/ > # mv S50hwclock.sh offS50hwclock.sh > "S50hwclock.sh" is in fact a link to "../init.d/hwclock.sh". > To prevent troubles during shutdown, do something similar for > rc6.d: > # cd ../rc6.d/ > # mv K25hwclock.sh offK25hwclock.sh > BTW: I have no idea why it tries to write to the clock at boot time at > all. OK, tried the above and I still get a kernel panic (which I can't capture with dmesg - it always says: "Searching for SAVEKMSG magic... Not found" I managed to write down this before it rebooted: System time was Sun Dec 14 02:45:22 UTC 2003 Setting the System Clock using the Hardware Clock as reference... NIP: C00DCA04 XER: 20000000 LR: C00DC988 REGS: c7c71d60 TRAP: 0300 There was a fair bit after that which I didn't catch. > 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. Hmmm, about to try this now....... Kind Regards, Kulwant |