serial console problem on imx31 target

I don't think you want runlevel 5 on an embedded host. How about runlevel 1 for now, until you get the details sorted out?
--- rod.

I still don't understand the connection between uboot and kernel when you give it a "console=ttySMX0,115200n8" kernel argument .. I know that the kernel when it sees that uses the argument as the console instead of the default tty1. But how does it know what serial port on the imx to use?

uboot will use its own independent driver, and this vanishes when the kernel in launched. You were correct about the functionality of the serial hardware earlier when you noted that the bootloader uses that hardware correctly. Your kernel commandline specifies which port to use as the console: 'console=ttySMX0,115200n8'.
I asked earlier whether there is a possibilty to specify, to the driver via kernel commandline arguments, details of the hardware. Did you explore this?

--- rod.

Ok, I have finally been able to ssh into the box. The problem was in the way I was exporting via NFS. I did not have the "norootsquash" option set in my exported directory entry in /etc/exports.

Oh, well I can login now, so I am not going to pursue the serial console problem and just go on to try and get a frame buffer or X support working.

Can anyone tell me what the steps are to get X working? I don't see the usual startx command in my Angstom-x11-image to test it.

Cheers,
bernie

Originally Posted by theNbomr . I asked earlier whether there is a possibilty to specify, to the driver via kernel commandline arguments, details of the hardware. Did you explore this?

No, how do I do that, is it just a matter of looking through the source code to see what it wants(driver/serial/imx.c), or is their an easier way?

I guess that might be the only way. There might be a readme or other documentation in the kernel sources. Documentation written in C never lies :-)

--- rod.