Re: Installation woes

[Michel <mi...@da...>]

On Sun, 2003-01-26 at 18:41, Kulwant Bhogal wrote: 
> 
> >> Yes, it starts to boot up but I get a kernel panic when it tries to set
> >> the system clock from the hardware clock. 
> 
> > Doing anything more with the installer is unlikely to change that.
> 
> Well I was told an more recent kernel might help, so was only trying to use
> the installer to install a more up to date kernel - except I'm not sure if I
> am starting with the right files as the installer always complains in one
> way or another (e.g. debootsrap exited with an error (return value 1) or
> can't find basedebs.tar or file not found on http:http.us.debian.org/debian). 

You don't really need to installer for that as the kernel itself is
needed on the AmigaOS side (the installer may help for installing the
modules, in case you need one of those for booting into the base system,
but you certainly don't need the base system steps of the installer to
do it).


> >> kernel) and renamed vmlinuz to linux.bin (because I read in one of the 
> >> archived mails that vmlinux is the linux.bin file) 
> 
> > Yes, it's the kernel image, but you need not rename it, just change the
> > argument to bootstrap.
> 
> Well in any case it simply kernel panics at an even earlier stage than the
> clock bit so something somewhere is not right. 

Hard to say anything about that without dmesg output at least.


> >> I have been going through the archived mails to this ML and I saw
> >> somewhere  that I could remove the commands from the boot scripts to
> >> stop it trying  to set the system clock, but I have not figured out how
> >> to do this yet.  
> 
> > Try mv /etc/init.d/hwclock* /root/ .
> 
> OK, I tried this and the system still crashes when it tried to set the
> system clock. I rebooted again into bash and the hwclock* files were back in
> /etc/init.d
> 
> I remember somebody saying that Linux has to be told to save all changes to
> disk. How do I do this? 

With sync, for example, but that's not necessary when the filesystem is
unmounted cleanly, i.e. you reboot cleanly.


> Are there any negative consequences to be expected from not having the
> hwclock stuff run at startup? 

Yes, the system time will likely be off. :)

> Why does Linux not trust the HWClock to do it's job? 

It does, that's why it tries to read the time from the hw clock...


-- 
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast