about linux-2.6.17

Michael S. Zick mszick at morethan.org
Sun Jul 16 12:54:16 UTC 2006


On Sat July 15 2006 23:42, Mark wrote:
> Hello,all:
>     I have ported the 2.6.17 kernel to the smdk2410 board recently.And I'm
> using busybox-1.00 and the NFS.
>     But when the kernel booted the messages are like this:
> 
> Looking up port of RPC 100003/2 on 10.10.10.100
> Looking up port of RPC 100005/1 on 10.10.10.100
> VFS: Mounted root (nfs filesystem).
> Freeing init memory: 88K
>     And it hang,nothing else to be printed.
>     Since the nfs has been mounted ,the problem should be in the root
> filesystem.
>     And in 2.6.x kernel,the parameter of the console has been changed from
> ttyS0 to ttySAC0,do you think this has
> something to do with the hang problem?And does anybody know how to deal with
> it?
>

The device name used is determined by the code in the kernel's console driver.
Possibly modified by a kernel configuration option at build time.

If your kernel's console driver for that system has not been terribly re-written...

You should still be able to set the console device on the kernel boot, command line:
with a "console=/dev/whatever" option.  

It is hardware dependent if what you select for that option will work. Best bet is
to stick with whatever was coded in the kernel for your system.

> 
> PS  when I compiled the busybox-1.2.0 and 1.1.3(with arm-linux-gcc 3.4.1),there
> always errors after:
>     LINK busybox_unstrpped
> Is it beacause the compiler?
>

More likely the compiler installation - it needs to search for its own startup
library objects.  You can set V=1 on the make command line to get more information.

That will give you the full command line being used to compile and link.

To also find where your compiler is searching for the startup objects, add "-v" to
the CFLAGS.

Mike



More information about the busybox mailing list