[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Emdebian - ttyS0 and login incorrect error



On Thu, 2009-05-28 at 12:23 -0300, Amandeep Bhullar wrote:
> Hi,
> 
> I have been trying to boot my AT91SAM9263EK with Emdebian for a while
> now but it keeps giving me errors. After mounting the filesystem, it
> keeps giving error regarding ttyS2 - no file or directory.
> 
> I have used sudo emsandbox -a arm --create to create the tarball.
> Copied the tarball to my target system running linux; and gave
> following commands:
> mkdir emrootfs
> cd emrootfs
> tar -xzpf emdebian-arm.tgz
> ./emsecondstage
> 
> Since ttyS0 and ttyS2 are missing, i created them
> cd dev
> mknod ttyS2 c 4 65
> mknod ttyS0 c 4 64
> chown root.tty tty*
> 
> Next, I create the filesystem
> cd /
> mkfs.jffs2 -e 0x20000 -s 0x800 -r /emrootfs -o emdebian.jffs2 -l -n
> 
> I use U-boot nand utility to write this filesystem to nand flash. I am
> looking for your help to fix follwoing two errors:
> 
> 1. When I boot it wil my Linux kernel, this is what it comes up with
> on my serial console:
> ............
> VFS: Mounted root (jffs2 filesystem).
> Freeing init memory: 124K
> init started: BusyBox v1.11.1 (2008-08-08 18:56:00 ART)
> starting pid 378, tty '': '/etc/init.d/rcS'
> .udev/ already exists on the static /dev! (warning).
> Starting the hotplug events dispatcher: udevd.
> Synthesizing the initial hotplug events...done.
> Waiting for /dev to be fully populated...done.
> Setting hostname to 'emdebian-arm'...done.
> Activating swap:.
> FATAL: Could not load /lib/modules/2.6.27/modules.dep: No such file or
> directory
If you want to get rid of that create an empty modules.dep unless you
have kernel modules to load at startup.

> 
> Can't open /dev/ttyS2: No such file or directory
> process '/sbin/getty -L ttyS2 115200 vt100' (pid 891) exited.
> Scheduling for res
> tart.
> Can't open /dev/ttyS2: No such file or directory
> process '/sbin/getty -L ttyS2 115200 vt100' (pid 907) exited.
> Scheduling for res
> tart.
Check yout /etc/inittab, I had a couple of ttyxys that where not
physically there:

# Set up a couple of getty's                             
#tty1::respawn:/sbin/getty 38400 tty1
#tty2::respawn:/sbin/getty 38400 tty2         
# Put a getty on the serial port
#ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100
commenting them out worked for me.

> ................
> 
> 2. But on the LCD of the target device, I do see the emdebian-arm
> login prompt, but 
> emdebian-arm login: root
> Password:
> Login incorrect.

I had the same thing, the workaround which Neil Williams told me was to
chroot into the new emdebian tree (after you executed the secondstage
script) and execute passwd.
This will modify the password file data on the newly created emdebian
fs. Now create a JFFS2 image and use it with u-boot.

I hope this helps,
Marco





Reply to: