10-25-2009,02:02 PM
@peter bostwick
in a quest to stop boot up hanging. I tried messing with ntpdate in start up. Can you get hwclock to sync with date? I could not get hwclock to respond. then afterbooting and i cant remember exactly what i did but i think i enabled hwclock.sh in /etc/init.d If i am correct ntpdate tries to go to server and update date and time.
Both ntpdate and hwclock work for me on my FAT PS2 HDD version (similar to what you have, and just tested ok now). However, I have found that kernelloader module settings have a major impact on the Real Time Clock access, including hanging. It would be useful to have you Restore Defaults under the file menu of kernelloader and try again. I have moved /etc/init.d/hwclock* to hwclock*.moved so that it only runs ntpdate as a preference to keep accurate time on startup, but you should be able to change this to remove /etc/init.d/ntpdate and use hwclock* by renaming back to original (without .moved).
all that poweroff and shutdown do is link to halt.
I had to change the shutdown since my 2008 distro (is fixed in 2009 distro - 2009_base_and_usrlocal_package directory in http://www.4shared.com/dir/10437217/...ux_Distro.html). Instead of downloading the whole distro again, you might want to set the /etc/init.d/rc6.d and rc0.d "S" links to look like: S10portmap, S20sendsigs, S30urandom, S31umountnfs.sh, S35networking, S40umountfs, S90reboot. This re-ordering might make it shut down cleaner. I remember having significant problems getting shutdown to work properly and completely. Also, once again it is CRUCIAL to have the proper kernelloader module settings to allow this to work. That means you should Restore Defaults, re-enter your kernel, kernel parameters, etc. but don't mess with the modules section. As for the fsck, I do have the newer version but haven't invested the time in updating scripts to use it as I've encountered no problems to date with the original fsck function.
PS2 v9 NTSC, PS2 v12 NTSC, PS2 v15 VESA