Bug 22620 - No runlevel 3 prompt in tty1 after fresh install, running "systemctl enable getty@tty1.service" fixes it.
Summary: No runlevel 3 prompt in tty1 after fresh install, running "systemctl enable g...
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: release_blocker major
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-17 15:46 CET by Bit Twister
Modified: 2018-07-04 11:25 CEST (History)
6 users (show)

See Also:
Source RPM: drakx-installer-stage2, systemd-236-4.mga7.src.rpm, initscripts-9.78-5.mga7.src.rpm
CVE:
Status comment:


Attachments
dmesg text (58.29 KB, text/plain)
2018-03-10 21:56 CET, Bit Twister
Details

Description Bit Twister 2018-02-17 15:46:40 CET
Description of problem:  7 dev0

No login prompt runlevel 3

Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. clean Mageia-Cauldron-netinstall-nonfree-x86_64.iso, all group packages and xfce only de with tainted and nonfree enabled.

2. hit ESC at grub2 boot selection.
3. add " 3" (without quotes) to end of /boot/vmlinuz line and 
remove  "splash quiet"
4. hit Ctrl+x

Once terminal quits scrolling messages, 
Note there is no login prompt, nor does one show up after hitting Enter.

 bug 22593 has attachments for journal log and report.bug.xz


Workaround:
Hit ALt+f2
log into user account
Bit Twister 2018-02-17 15:48:21 CET

Source RPM: (none) => guessing systemd-236-4.mga7.src.rpm

Comment 1 David Walser 2018-02-17 17:37:48 CET
My Mageia 5 system has a /etc/systemd/system/getty.target.wants/getty@tty1.service that is probably responsible for the tty1 getty being created.  This symlink was created the day I installed Mageia 5.  I'm not entirely sure exactly what was responsible for creating it though.  I do see that the initscripts package was installed at the same time that the symlink was created.  I don't see anything obvious in the scripts of the package that would have been responsible for creating it, but I do know that the initscripts package in Cauldron has recently undergone significant changes, so I'd guess the problem originated there.

CC: (none) => ngompa13
Assignee: bugsquad => basesystem
Source RPM: guessing systemd-236-4.mga7.src.rpm => systemd-236-4.mga7.src.rpm, initscripts-9.78-5.mga7.src.rpm

Comment 2 Bit Twister 2018-02-17 19:29:18 CET
Workaround:  systemctl enable getty@tty1.service
Comment 3 Mauricio Andrés Bustamante Viveros 2018-03-10 16:43:12 CET
If you remove the quiet kernel option, the vty1 is unable to show the login prompt because the kernel messages shown in this vty because some kernels has the debug information enabled (showing the audit messages)

Please retry the boot with runlevel 3 and without remove these kernel options "splash quiet"

Please add the kernel booted up information too

CC: (none) => neoser10

Bit Twister 2018-03-10 21:55:42 CET

Severity: normal => major
Summary: No login prompt runlevel 3 => No gui login or runlevel 3 prompt

Comment 4 Bit Twister 2018-03-10 21:56:49 CET
Created attachment 10038 [details]
dmesg text
Marja Van Waes 2018-06-04 20:23:50 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=23101

Comment 5 Marja Van Waes 2018-06-04 21:07:33 CEST
Keeping this report for the missing tty1 prompt, and bug 22593 for the other issue (the DM not starting).

We need to check whether this particular issue also happens in runlevel 3 in installs from last year.

CC: (none) => marja11
Summary: No gui login or runlevel 3 prompt => No runlevel 3 prompt in tty1, running "systemctl enable getty@tty1.service" fixes it.

Comment 6 Bit Twister 2018-06-04 22:27:30 CEST
(In reply to Marja Van Waes from comment #5)

> We need to check whether this particular issue also happens in runlevel 3 in
> installs from last year.

Installs from last year is a bit vague. If you mean mga6, we did not have the problems. I am always doing clean installs only and 6 did not have the problems.
Both problems are due to a missing systemd link because the workaround commands were not executed during install.
Comment 7 Marja Van Waes 2018-06-05 07:42:45 CEST
(In reply to Bit Twister from comment #6)
> (In reply to Marja Van Waes from comment #5)
> 
> > We need to check whether this particular issue also happens in runlevel 3 in
> > installs from last year.
> 
> Installs from last year is a bit vague. If you mean mga6, we did not have
> the problems. I am always doing clean installs only and 6 did not have the
> problems.

Too vague indeed, I should have said: cauldron installs from before systemd-236 and initscripts-9.78, that do run current systemd and initscripts 

> Both problems are due to a missing systemd link because the workaround
> commands were not executed during install.

The question was: package update install or Mageia install... if the latter, then the culprit is again stage2, like for bug 22593

It is the latter indeed, while writing this I booted an older Cauldron install (last updated last weekend, except for qt5) in runlevel 3. The prompt appears nicely in tty1. 

Reassigning

Summary: No runlevel 3 prompt in tty1, running "systemctl enable getty@tty1.service" fixes it. => No runlevel 3 prompt in tty1 after fresh install, running "systemctl enable getty@tty1.service" fixes it.
CC: (none) => alien, basesystem
Assignee: basesystem => mageiatools
Source RPM: systemd-236-4.mga7.src.rpm, initscripts-9.78-5.mga7.src.rpm => drakx-installer-stage2, systemd-236-4.mga7.src.rpm, initscripts-9.78-5.mga7.src.rpm

Marja Van Waes 2018-06-05 07:42:53 CEST

Component: RPM Packages => Installer

Bit Twister 2018-07-04 10:41:40 CEST

Priority: Normal => release_blocker

Comment 8 Charles Edwards 2018-07-04 11:25:09 CEST
Just my 2 cents.

I always, by default, boot my system to init 3 verbose and I get the login prompt on TTY2 and when I launch the DM and X it occupies TTY1.
On the rare times when boot simply appears to stop I use Ctrl-Alt-F2 and there is
the login prompt.

CC: (none) => cae


Note You need to log in before you can comment on or make changes to this bug.