You are not logged in.

#1 2017-11-14 17:21:41

Martinsos
Member
From: Croatia
Registered: 2015-08-27
Posts: 61

[SOLVED] Init screen does not proceed to terminal

Hi all,
My init screen goes through all the initialization nicely but after "[OK] Started Network Manager Script Dispatcher Service" it just stops and doesn't proceed to the terminal where it should ask me for credentials and so on. Cursor is blinking.
I can switch to other terminals, so what I do is switch to tty2 and run startx and everything works fine (I am using xfce4). If I at any moment switch back to tty1, init screen is still there, with all steps being [OK] and cursor blinking.

I am guessing that everything is initialized correctly, but something goes wrong with that step where it should proceed to the terminal. Journalctl is not returning any errors (I ran it with `journalctl -b -p err`). I also did full system update but it did not help.

From what I was exploring so far, I figured out that boot loader starts init process, which is systemd in archlinux. So if I am correct, those "[OK]" messages are printed by systemd as it goes through different services and runs them. When it comes to the end, it should start terminal, and I read that is actually done by getty command. So I am guessing my systemd is not running getty when it should, but why not? I checked systemctl for any errors, and there are none.
Kernel is 4.13.12-1.

Thank you!

Last edited by Martinsos (2017-11-15 08:25:55)

Offline

#2 2017-11-14 17:28:26

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: [SOLVED] Init screen does not proceed to terminal

How have you set up starting X?


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2017-11-14 17:46:38

Martinsos
Member
From: Croatia
Registered: 2015-08-27
Posts: 61

Re: [SOLVED] Init screen does not proceed to terminal

Hi @jasonwryan, thanks for responding so quickly!
Could you please give me more information on what do you mean by "setting up starting X"?
As I mentioned, I don't even get to terminal where I can provide my credentials in order to login. If I open other tttys (2, 3, ...) I can login, but not on tty1 where init screen has cursor blinking and not proceeding. Normally, I would input my username and password and then run `startx` command. That works if I do it from tty2 for example. From what I read, that is getty, which is handling that.

Last edited by Martinsos (2017-11-14 17:47:25)

Offline

#4 2017-11-14 17:50:00

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,442
Website

Re: [SOLVED] Init screen does not proceed to terminal

Martinsos wrote:

Normally, I would input my username and password and then run `startx` command.

I suspect this is what he was looking for: if you run any display managers they would be likely suspects.

If I were you I'd try disabling a few services that aren't absolutely necessary in order to narrow down the suspect list.  I'd start with those last started, and personally I'd start with networkmanager and friends first (NetworkManager is also one of the usual suspects with boot issues).

Last edited by Trilby (2017-11-14 20:42:34)


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#5 2017-11-14 18:04:27

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,786
Website

Re: [SOLVED] Init screen does not proceed to terminal

Post the output of

systemctl status getty.target getty@tty1.service

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Online

#6 2017-11-15 07:12:30

Martinsos
Member
From: Croatia
Registered: 2015-08-27
Posts: 61

Re: [SOLVED] Init screen does not proceed to terminal

@WorMzy here it is:

● getty.target - Login Prompts
   Loaded: loaded (/usr/lib/systemd/system/getty.target; static; vendor preset: disabled)
   Active: active since Wed 2017-11-15 08:00:11 CET; 4min 49s ago
     Docs: man:systemd.special(7)
           man:systemd-getty-generator(8)
           http://0pointer.de/blog/projects/serial-console.html

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

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

Thanks @Trilby, I will try and play with the services. I actually checked journalctl and systemctl for errors, and all services load nicely without any problems, so I assumed that they are not the ones causing this, but it is worth eliminating that as a possible cause. Also, as I said I can normally login into my system from the tty2 or any other, run startx and everything works fine.

I also just did additional test: as I was going through all the units in systemd, I found one named console-getty which was disabled. I enabled it to see what happens, and what happened is that init screen actually displayed getty! However, it did not clean the services status output (as it usually does on my other machines) and after logging in successfuly it did not allow me to startx, saying that I can't do it because I am not in a console.

Last edited by Martinsos (2017-11-15 07:18:15)

Offline

#7 2017-11-15 07:19:44

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,786
Website

Re: [SOLVED] Init screen does not proceed to terminal

getty@tty1 is disabled, if you don't have anything else running on tty1, then just enabling it should be enough.


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Online

#8 2017-11-15 07:23:39

Martinsos
Member
From: Croatia
Registered: 2015-08-27
Posts: 61

Re: [SOLVED] Init screen does not proceed to terminal

@WorMzy right, that was it, now it works as expected!
Do you have any idea what might have caused this? I am sure I have not disabled getty@tty1 myself, since I didn't even know that it exists.

Offline

#9 2017-11-15 09:24:58

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,786
Website

Re: [SOLVED] Init screen does not proceed to terminal

Your pacman.log might have some clues. The systemd package's post_install scriptlet enables the service, so if this failed for whatever reason then the service wouldn't be enabled. Scriptlets log to pacman.log, so you should be able to see if the service was enabled successfully, and also whether it was later disabled by another scriptlet.

[2017-08-08 11:17] [ALPM] installed systemd (234.11-4)
[2017-08-08 11:17] [ALPM-SCRIPTLET] Initializing machine ID from random generator.
[2017-08-08 11:17] [ALPM-SCRIPTLET] Created symlink /etc/systemd/system/getty.target.wants/getty@tty1.service → /usr/lib/systemd/system/getty@.service.

If the service was disabled outside of pacman, then I'm not sure how you would investigate that. Have you run any third-party scripts or given anyone else root access to your system?


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Online

#10 2017-11-15 14:08:58

Martinsos
Member
From: Croatia
Registered: 2015-08-27
Posts: 61

Re: [SOLVED] Init screen does not proceed to terminal

Thanks, that sounds like a great idea to track this. Unfortunately, for some reason there are no logs in pacman.log mentioning getty. I explored logs regarding systemd but have not found anything unusual. One thing I found is that I used Slim before as a login manager (I forgout about that!) and that I removed it relatively recently -> might be that Slim disabled the getty for tty1 and since I removed it it was not enabled back. If not that, I assume it is something in the direction you described -> there must have been a failure during update of systemd.

Third party services -> none that I can think of (that would be suspicious). Root access -> no.

Thanks again everybody, I learned a lot and fixed the problem! I marked post as solved.

Last edited by Martinsos (2017-11-15 14:09:42)

Offline

Board footer

Powered by FluxBB