[systemd-devel] Question on debugging getty 'runlevel 3' issue.

[Ben Greear]

I'm using Fedora 19 on a 32-bit dual-core Atom system.

I installed Mate, various other packages, and among other configuration,
tried to put the system into the equivalent of 'runlevel 3'.

The system boots to black console as expected, but it will not
give a prompt, except on 'alt F2' window.

On clean bootup, if I ssh in, I there are no getty processes running:

[root at ct520-128-6034 ~]# ps -auxww|grep getty
root      2699  0.0  0.0   4940   860 pts/1    S+   15:03   0:00 grep --color=auto getty


[root at ct520-128-6034 ~]# grep -i getty /var/log/messages
[root at ct520-128-6034 ~]# ls -l /etc/systemd/system/getty.target.wants/
total 0
lrwxrwxrwx. 1 root root 38 Jun 27 10:12 getty at tty1.service -> /usr/lib/systemd/system/getty at .service

[root at ct520-128-6034 ~]# ls -l /usr/lib/systemd/system/getty at .service
-rw-r--r--. 1 root root 1662 Jun 24 08:30 /usr/lib/systemd/system/getty at .service

[root at ct520-128-6034 ~]# systemctl status getty at tty1.service
getty at tty1.service - Getty on tty1
    Loaded: loaded (/usr/lib/systemd/system/getty at .service; enabled)
    Active: inactive (dead)
      Docs: man:agetty(8)
            man:systemd-getty-generator(8)
            http://0pointer.de/blog/projects/serial-console.html


A 64-bit server-class system installed in same manner works fine.


Any ideas on how to debug this further?

Thanks,
Ben

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com