Hi Juergen, Thank you for your answer.
2014-05-05 10:01 GMT+02:00 Juergen Borleis <[email protected]>: > Hi Guillermo, > > On Friday 02 May 2014 09:52:14 Guillermo Rodriguez wrote: > > I need to use serial port 0 for my application and thus I wanted to avoid > > the kernel from using ttySAC0 as a console. > > > > In barebox I edited /env/config and replaced console=ttySAC0,115200 with > > console=null in bootargs. > > > > The system starts to boot OK but at some point it seems to stop. I try to > > connect via telnet but it seems that telnetd was never started. > > > > If I set console=ttySAC1 or console=ttySAC2 instead all works fine. But > > somehow it doesn't like console=null > > > > Any hints on what may be happening? Is there something in the boot/init > > process that expects a non-null console setting? > > Did you try with "console=" instead as well? > Yes, I had tried both console=null and console= and got the same results. > > And did you also disable the login? > I just found out that the problem is fixed by modifying the standard /etc/inittab file in ${PTXDIST}/projectroot. I just removed the "console" id from the sysinit and respawn lines and left the id field empty: ::sysinit:/etc/init.d/rcS ::respawn:/sbin/getty -L 115200 ttySAC0 vt100 (of course this still starts a shell on ttySAC0 but that's expected) Not sure why this makes a difference (according to the comments in the example inittab file from Busybox [1] I would interpret that leaving it empty would be equivalent to specifying "console"), but now it works both with the default bootargs (console=ttySAC0,115200) and with console=null (or just "console="). Since the standard inittab example from Busybox also leaves the id field empty for the sysinit line and for the login shell on the default console, you may want to do the same in ptxdist. [1] http://git.busybox.net/busybox/tree/examples/inittab Thank you, Guillermo
