Thanks for your help, Guillaume and Tony. It turned out that the system was frozen. Login works as expected on ttyS0. Unfortunately the kernel coming with the cubieboard-image (3.4.29) has issues but I can't tell for sure what it is. I suspect the wemac ethernet driver. I compiled a new kernel (3.4.43) from the sunxi sources at github. It works but it still has issues. Anyway I can boot beyond the login now. Johannes 2013/8/20 Johannes Nohl <johannes.nohl@gmail.com>:

Does someone know what I have to do to get a login on ttyS0? I can see cubieboard in the serial console booting, from u-boot to kernel, ending with:

[ OK ] Started D-Bus System Message Bus. [ OK ] Started Login Service. [ OK ] Started YaST2 Firstboot.

I tried to utilze systemd by adding serial-getty to the services:

ln -s /usr/lib/systemd/system/serial-getty@.service /etc/systemd/system/getty.target.wants/serial-getty@ttyS0.service

I used the image from http://download.opensuse.org/repositories/devel:/ARM:/12.3:/Contrib:/sunxi/i....

Additionally I don't get eth0 up, whether on dhcp or static. Therefore I can't ssh inside. I really need the serial console.

One of u-boot's env parameters is console=ttyS0,115200 (which isn't needed to see the boot stuff) so I guess the kernel takes this as an option.

I'm thinking I'm missing stuff here because the underlaying JeOS is pretty small. Buz e.g. agetty is installed...

Who can help me here?

Johannes -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org