Dear all,

how to enable login on console in X86 version ?
This is my inittab

::sysinit:/etc/init.d/rcS                                                                                                 
ttyS0::askfirst:/bin/ash --login                                                                                           
tty1::askfirst:/bin/ash --login         

but  never get login prompt

Dome C.

my inittab:

::sysinit:/etc/init.d/rcS
ttyS0::askfirst:/bin/ash --login
::askfirst:/bin/ash --login

my grub/menu.lst:

#serial --unit=0 --speed=@BAUDRATE@ --word=8 --parity=no --stop=1
#terminal --timeout=10 console serial

default 0
timeout 5

title   OpenWrt
root    (hd0,0)
kernel  /boot/vmlinuz @CMDLINE@ noinitrd console=tty0 console=ttyS0,@baudrate@n8 reboot=bios
boot

title   OpenWrt (failsafe)
root    (hd0,0)
kernel  /boot/vmlinuz failsafe=true @CMDLINE@ noinitrd console=tty0 console=ttyS0,@BAUDRATE@n8 reboot=bios
boot

What files from the buildroot should I modify to make these changes persistent (not overwrite when I hit make)?

I've tried:

radu@akira trunk $ vim target/linux/x86-2.6/image/grub/menu.lst
radu@akira trunk $ vim package/base-files/files/etc/inittab

Is this ok?

Right.

But why change the files? The default files /trunk/package/base-files/files/etc/inittab and /trunk/target/linux/x86-2.6/image/grub/menu.lst should take care if you like to use the console or serial login.

Anyway. It would be a good idea if you start a new build from a clean, fresh checked out build-system.

(Last edited by forum2006 on 9 Apr 2007, 11:37)

Ok, I've got the serial console up and running. But the problem is I only get a login with the prebuilt vmware image. So I guess I'm doing something wrong so I need to dig more into this.

This are the last lines I get when I connect via the serial console on the prebuilt image:

root@OpenWrt:/# AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
/bin/ash: AT: not found
/bin/ash: c1: not found
[1] + Done(127)                  AT S7=45 S0=0 L1 V1 X4

And this is the last line I get with the image compiled from svn:

AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0

/later
I've got it working. I'm not sure what I did wrong first time...

(Last edited by kenjiru on 9 Apr 2007, 14:06)

Here is a VMware Configuration File (VMX) which I used for testing. It just works. Remember to connect to \\.\pipe\com_1 with 115200 8n1. Start and connect with PuTTY after you started VMware.

   - openwrt-x86-2.6-ext2.vmx

EDIT: and yes, I build the image by myself.

(Last edited by forum2006 on 9 Apr 2007, 15:25)

Hello forum2006 and thank you for your answers.

I haven't used so much the serial console so I'm not so comfortable about these things. The format "\\.\pipe\com_1" should be used only when connecting from a Windows host, right?

From my linux box I'm using the following configuration:
- in vmware I use "/tmp/com_1" a named pipe
- than I issue the following command:

radu@akira /trunk $ socat -d -d /tmp/com_1 PTY:
2007/04/09 19:55:22 socat[1071] N successfully connected via 
2007/04/09 19:55:22 socat[1071] N PTY is /dev/pts/5
2007/04/09 19:55:22 socat[1071] N starting data transfer loop with FDs [3,3] and [4,4]

- after that I open minicom and configure it to use the device created by socat

Is there another way?