[opensuse-arm] No login with ttyS0 (JeOS for cubieboard)
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
OK. I'm a bit clueless here. It may be that YaST firstboot stops the boot process. But I can't be sure because I can't login. Anyhow when turning firstboot of there's neither network nor tty. How can I solve this? Thanks for any help. 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
Hi, Le 21/08/2013 17:29, Johannes Nohl a écrit :
OK. I'm a bit clueless here. It may be that YaST firstboot stops the boot process. But I can't be sure because I can't login. Anyhow when turning firstboot of there's neither network nor tty. How can I solve this? Thanks for any help.
Remove the file /var/lib/YaST2/reconfig_system from filesystem and try to boot. It will boot without starting firstboot. Could you also send the content of boot.script file from boot partition, please? Regards, Guillaume
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
On 08/19/2013 05:50 PM, Johannes Nohl wrote:
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
On my Pandaboard, serial console is /dev/ttyO2 I can't recall if I initially tried linking (as above), but currently I have a copy with the following differences. I stopped investigating once it worked :) If there is a cleaner way, please lmk. # diff /etc/systemd/system/getty.target.wants/getty\@ttyO2.service /usr/lib/systemd/system/getty@.service 23c23 < ConditionPathExists=/dev/ttyO2 ---
ConditionPathExists=/dev/tty0 27c27 < ExecStart=-/sbin/agetty --noclear %I 115200 linux
ExecStart=-/sbin/agetty --noclear %I 38400 linux 48c48 < Alias=getty.target.wants/getty@ttyO2.service
Alias= getty.target.wants/getty@tty1.service
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (3)
-
Guillaume Gardet -
Johannes Nohl -
Tony Jones