[BusyBox] Start up problems

Greg Lindberg gl4jalopi at earthlink.net
Thu Jul 21 23:53:35 UTC 2005


Here is what I'm doing to build the /dev directory:

mknod -m 777 ram0 b 1 0
mknod -m 777 ram1 b 1 1
mknod -m 777 ram2 b 1 2
mknod -m 777 ram3 b 1 3
mknod -m 777 initrd b 1 250
mknod -m 600 mem c 1 1
mknod -m 666 null c 1 3
mknod -m 666 zer0 c 1 5
mknod -m 644 random c 1 8
mknod -m 600 tty0 c 4 0
mknod -m 600 ttyS0 c 4 64
mknod -m 600 ttyS2 c 4 65
mknod -m 600 ttyS3 c 4 66
mknod -m 666 tty c 5 0
#mknod -m 600 console c 5 1
ln /dev/ttyS0 console

I also had the same problem when specifying 'console=ttyS0' on the Linux
command line.

Greg

> -----Original Message-----
> From: busybox-bounces at mail.busybox.net
> [mailto:busybox-bounces at mail.busybox.net]On Behalf Of Craig Skinner
> Sent: Thursday, July 21, 2005 12:08 PM
> Cc: busybox at mail.busybox.net
> Subject: Re: [BusyBox] Start up problems
>
>
> Greg Lindberg wrote:
> > I'm trying to bring up Busybox on an Intel PXA255 based board running
> > Linux-2.6.12-rc4.  I've compiled everything with gcc-3.3.4 using
> > glibc-2.3.2.  I booting Linux with u-boot, built from a recent
> cvs pull.  If
> > I start Busybox as /bin/sh I get no output.  If I start Busybox
> as either
> > /linuxrc or /sbin/init with no inittab of an inittab with just an
> > ::askfirst:-/bin/sh entry I get 'Please press Enter to activate this
> > console.' and when I press enter it repeats the output.
>
> What is in /dev/?
> _______________________________________________
> busybox mailing list
> busybox at mail.busybox.net
> http://busybox.net/mailman/listinfo/busybox




More information about the busybox mailing list