Arch Linux

Nono3167

Member

Registered: 2015-11-23

Posts: 19

No more tty, all filled with boot messages

Hi everyone,

I noticed a few days ago that I no longer have access to virtual TTY by doing Ctrl+Alt+Fx.
All consoles show the Archlinux Boot messages, ending with "Reached target graphical interface".

I'm running the latest Linux 4.4.22-1-lts kernel with KDE 5 as desktop environment.

I have never seen this issue before and do not really know where it can come from nor what log or software I should be looking for as culprit.

TTY1 is running X as always so I do have access to my computer. It's just all the others that seem to stop working.

If you have any idea or any suggestion on where to look I'm listening :-)

ooo

Member

Registered: 2013-04-10

Posts: 1,638

Re: No more tty, all filled with boot messages

Any modifications in /etc/systemd/logind.conf and /etc/systemd/system/getty@tty*.service.d/ should be first places to look at.

How do you login in to X? Via DM, or some other method?

Nono3167

Member

Registered: 2015-11-23

Posts: 19

Re: No more tty, all filled with boot messages

I don't remember changing anything in the logind file. All parameters seems commeted out so I assume it's default values that are used :

[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#InhibitDelayMaxSec=5
#HandlePowerKey=poweroff
#HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
#HandleLidSwitch=suspend
#HandleLidSwitchDocked=ignore
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#HoldoffTimeoutSec=30s
#IdleAction=ignore
#IdleActionSec=30min
#RuntimeDirectorySize=10%
#RemoveIPC=yes
#InhibitorsMax=8192
#SessionsMax=8192
#UserTasksMax=33%

Looking at getty, it seems that I only have one getty service set, which might explain why I don't get any other console :

$ ls -lah  /etc/systemd/system/getty.target.wants/*
lrwxrwxrwx 1 root root 38 23 août   2015 /etc/systemd/system/getty.target.wants/getty@tty1.service -> /usr/lib/systemd/system/getty@.service

For login, I use SDDM that starts automatically at bootup and then I log into KDE with my password.

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 19,785

Re: No more tty, all filled with boot messages

All consoles show the Archlinux Boot messages, ending with "Reached target graphical interface".

What happens, at that point, if you simply press return?
Are you using a display manager? (KDM, for example) Note to self -- read before posting

Last edited by ewaller (2016-09-27 21:20:40)

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Nono3167

Member

Registered: 2015-11-23

Posts: 19

Re: No more tty, all filled with boot messages

I thought I tried before posting but just to be sure I have just tried again to press return, nothing happenned unfortunately.

Head_on_a_Stick

Member

From: London

Registered: 2014-02-20

Posts: 7,732

Website

Re: No more tty, all filled with boot messages

Looking at getty, it seems that I only have one getty service set, which might explain why I don't get any other console

That is normal, under systemd (a)gettys are generated on demand.

See http://0pointer.de/blog/projects/serial-console.html & https://wiki.archlinux.org/index.php/Sy … _gettys.3F

Can we see the output of:

loginctl user-status

---

Are you infected with Wetiko?

Nono3167

Member

Registered: 2015-11-23

Posts: 19

Re: No more tty, all filled with boot messages

Alright so now I see a little bit more how things are supposed to work regarding virtual TTY and systemd, thanks.

Here it is (I took the liberty of removing all web browser related lines) :

$ loginctl user-status
Nono (1000)
           Since: mar. 2016-09-27 18:23:08 CEST; 5h 34min ago
           State: active
        Sessions: *c2
          Linger: no
            Unit: user-1000.slice
                  ├─session-c2.scope
                  │ ├─ 1176 /usr/lib/sddm/sddm-helper --socket /tmp/sddm-authb7122e23-6892-4134-8420-df1b1ad0243f --id 1 --start /usr
                  │ ├─ 1192 /bin/sh /usr/bin/startkde
                  │ ├─ 1231 /usr/lib/kf5/start_kdeinit --kded +kcminit_startup
                  │ ├─ 1232 kdeinit5: Running...
                  │ ├─ 1233 /usr/lib/kf5/klauncher --fd=9
                  │ ├─ 1236 kded5 [kdeinit5]
                  │ ├─ 1255 /usr/bin/kactivitymanagerd start-daemon
                  │ ├─ 1282 /usr/bin/kaccess
                  │ ├─ 1293 kwrapper5 /usr/bin/ksmserver
                  │ ├─ 1294 /usr/bin/ksmserver
                  │ ├─ 1313 kwin_x11
                  │ ├─ 1320 /usr/bin/krunner
                  │ ├─ 1324 /usr/bin/plasmashell --shut-up
                  │ ├─ 1329 /usr/lib/polkit-kde/polkit-kde-authentication-agent-1
                  │ ├─ 1340 /usr/bin/xembedsniproxy
                  │ ├─ 1424 ksysguardd
                  │ ├─ 2063 /usr/lib/chromium/nacl_helper
                  │ ├─ 2769 /usr/bin/konsole
                  │ ├─ 2786 /bin/bash
                  │ ├─ 5201 /bin/bash
                  │ ├─14151 /usr/bin/dolphin
                  │ ├─14156 /bin/bash
                  │ ├─14169 file.so [kdeinit5] file local:/run/user/1000/klauncherTJ1233.1.slave-socket local:/run/user/1000/dolphinj
                  │ ├─19042 /bin/bash
                  │ ├─32375 loginctl user-status
                  │ └─32376 less
                  └─user@1000.service
                    ├─at-spi-dbus-bus.service
                    │ └─3524 /usr/lib/at-spi2-core/at-spi-bus-launcher
                    ├─dbus.service
                    │ ├─1199 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation
                    │ ├─1262 /usr/bin/kglobalaccel5
                    │ ├─1285 /usr/lib/kf5/kscreen_backend_launcher
                    │ ├─1309 /usr/lib/dconf/dconf-service
                    │ ├─1383 /usr/bin/kwalletd5
                    │ ├─1504 /usr/lib/kdeconnectd
                    │ ├─1529 /usr/bin/kuiserver5
                    │ └─3563 /usr/lib/GConf/gconfd-2
                    ├─gvfs-daemon.service
                    │ └─2074 /usr/lib/gvfs/gvfsd
                    ├─gvfs-udisks2-volume-monitor.service
                    │ └─32055 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
                    ├─init.scope
                    │ ├─1177 /usr/lib/systemd/systemd --user
                    │ └─1180 (sd-pam)
                    ├─obex.service
                    │ └─1430 /usr/lib/bluetooth/obexd
                    └─pulseaudio.service
                      └─1361 /usr/bin/pulseaudio --daemonize=no

EDIT : One thing I just noticed when I tried to look at getty@tty1 is that it doesn't seem to be running. Is that expected, knowing that I have X on my tty1 ?

$ systemctl status getty@tty1.service
● getty@tty1.service - Getty on tty1                                                                                                 
   Loaded: loaded (/usr/lib/systemd/system/getty@.service; enabled; vendor preset: enabled)                                          
   Active: inactive (dead)                                                                                                           
     Docs: man:agetty(8)                                                                                                             
           man:systemd-getty-generator(8)                                                                                            
           http://0pointer.de/blog/projects/serial-console.html      

Last edited by Nono3167 (2016-09-27 22:09:17)

ooo

Member

Registered: 2013-04-10

Posts: 1,638

Re: No more tty, all filled with boot messages

EDIT : One thing I just noticed when I tried to look at getty@tty1 is that it doesn't seem to be running. Is that expected, knowing that I have X on my tty1 ?

If X is running on tty1 and started from DM, getty won't be started for that tty.
After you switch to e.g. tty2, systemd should start getty for that tty, and getty@tty2.service should be running.

Omar007

Member

Registered: 2015-04-09

Posts: 368

Re: No more tty, all filled with boot messages

Are you by any chance using the nvidia binary drivers?