Thread: how to troubleshoot boot sequence?
View Single Post
fanoush is offline fanoush
2008-02-02 , 11:32
Posts: 2,152 | Thanked: 1,490 times | Joined on Jan 2006 @ Czech Republic
#2
instead of editing each script in /etc/init.d you may try to edit /etc/init.d/rc and add debug code to startup() function like this

Code:
#
# Start script or program.
#
dbgout(){
chroot /mnt/initfs text2screen -x 0 -y 60 -w 800 -h 20 -c
chroot /mnt/initfs text2screen -s 2 -H center -y 60 -T 0 -t "$@"
}

startup() {
dbgout "$@"
  case "$1" in
        *.sh)
                $debug sh "$@"
                ;;
        *)
                $debug "$@"
                ;;
  esac
}
then you see nicely what runs at startup and where it stops

you can also install syslog and see /var/log/syslog after unsuccessful boot

to install something to nonbooting system first boot working system, connect to network, mount nonbooting system and chroot to it
Code:
mount /dev/mmcblk0p2 /opt
chroot /opt
then you can 'apt get install sysklogd' from maemo repository, exit shell, unmount it and try to boot it again, wait until it hangs or reboots, boot working system, mount bad system and see end of /var/log/syslog

If there is no /var/log/syslog you may create it first time (not sure about this)
__________________
Newbies click here before posting. Thanks.

If you really need to PM me with troubleshooting question please consider posting it to the forum instead. It is OK to PM me a link to such post then. Thank you.
Last edited by fanoush; 2008-03-05 at 08:21. Reason: sysklogd not syslog
 

The Following 6 Users Say Thank You to fanoush For This Useful Post: