Re: Installation woes

[Kulwant B. <kul...@bt...>]

Hello Michel,

>> 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). 

>> 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. 

> root.bin is the installer ramdisk, you don't need it after installation.

So can you think why 2.4.20 would crash almost straight away when 2.2 gets as far as
trying to set the system clock? 

>> 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? 

Are there any negative consequences to be expected from not having the
hwclock stuff run at startup? Why does Linux not trust the HWClock to do
it's job? 

Kulwant