Oh I'm glad it worked!
You can set init=/bin/sh in order to just pull up a shell, but this will
prevent things like Ctrl+z, Ctrl+c from working. But then the next step
would be to change the default init script (if using busybox, then you
can change either /linuxrc or /etc/inittab) so that /sys, /proc, and
/dev/pts are mounted on boot.
Below is the /etc/inittab from my most recent busybox / uclibc filesystem.
~/Chris
=========================================================================
# /etc/inittab
#
# Copyright (C) 2001 Erik Andersen <>
#
# Note: BusyBox init doesn't support runlevels. The runlevels field is
# completely ignored by BusyBox init. If you want runlevels, use
# sysvinit.
#
# Format for each entry: <id>:<runlevels>:<action>:<process>
#
# id == tty to run on, or empty for /dev/console
# runlevels == ignored
# action == one of sysinit, respawn, askfirst, wait, and once
# process == program to run
# Startup the system
null::sysinit:/bin/mount -o remount,rw /
null::sysinit:/bin/mount -t proc proc /proc
null::sysinit:/bin/mount -t sysfs sysfs /sys
#null::sysinit:/bin/mount -t usbfs usbfs /proc/bus/usb
null::sysinit:/sbin/ifconfig lo 127.0.0.1 up
null::sysinit:/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
::sysinit:/etc/init.d/rcS
# Set up a couple of getty's
tty0::respawn:/sbin/getty 115200 tty0
tty1::respawn:/sbin/getty 115200 tty1
# Put a getty on the serial port
#ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100
ttyAM0::respawn:/sbin/getty -L ttyAM0 vt100
#ttyAM1::respawn:/sbin/getty -L ttyAM1 vt100
# Logging junk
#null::sysinit:/bin/touch /var/log/messages
#null::respawn:/sbin/syslogd -n -m 0
#null::respawn:/sbin/klogd -n
#tty3::respawn:/bin/tail -f /var/log/messages
# Stuff to do for the 3-finger salute
#::ctrlaltdel:/sbin/reboot
# Stuff to do before rebooting
null::shutdown:/etc/init.d/rcK
#null::shutdown:/usr/bin/killall klogd
#null::shutdown:/usr/bin/killall syslogd
null::shutdown:/bin/umount -a -r
#null::shutdown:/sbin/swapoff -a
siddh_c wrote:
> ?...?.f..~f.???f...?.x?.x...?..f.`.f.f.?.x.....~????.~f.???f...?..x?.`.`...`f.f
>> --------- Hangs here
>>
>> I did the following steps:
>> - patch as per the patch_and_build script
>> - run the ts7250_machine_id_fix.patch
>> - copied the 2.6.19.config_working_64MB config file to .config and
>> modified the following:
>> CONFIG_CMDLINE="console=ttyAM0,115200 root=/dev/mtdblock1"
>> - copy zImage via tftp followed by exec
>>
>> Any ideas where I might be going wrong ? I did the above on 2.6.19
>>
> Please ignore my previous post. The ep93xx-serial-uartbaud.diff patch
> fixed the above problem.
>
> Now I am able to see the 2.6.19 kernel boot. It fails with "Warning:
> unable to open an initial console". This is due to lack of devpts
> support as discussed in an earlier thread
> (http://tech.groups.yahoo.com/group/ts-7000/message/5668).
>
> I will try loading the rootfs via nfs with a rootfs that works with 2.6.
>
> Thanks again for all the replies. Here are my compilation steps so far
> for 2.6.19 - ts7250
>
> 1. crostools-0.38 [gcc-3.4.4-glibc-2.3.2]
> 2. Follow steps from
> http://vaiprime.visibleassets.com/~cfriedt/linux-2.6.19-ts7xxx.txt
> 2a) get linux-2.6.19
> 2b) run the patches from patch_and_build.sh
> 2c) change .config file CMDLINE options if need be
> 3. apply ts7250_machine_id_fix.patch
> 4. apply ep93xx-serial-uartbaud.diff
> 5. download yaffs2 and run the yaffs2 setup script to compile kernel
> with yaffs2 support
> 6. compile kernel
>
> -siddharth
>
>
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|