Leap 15.0 , Console login problem

Hi,

I have a very strange problem and i can not find anything for my situation.
The problem is that i can not login as user or root in run level 3. I enter username and when i am prompted
for password , i give it but nothing happens, after 60 sec it is timing out and i am prompted for user name again.
In kde i can login ok. Also in run level 1 i can login as root ok. I am using nvidia drivers from nvidia site compiled for the kernel.

uname -a
Linux xxxxxx 4.12.14-lp150.12.25-default #1 SMP Thu Nov 1 06:14:23 UTC 2018 (3fcf457) x86_64 x86_64 x86_64 GNU/Linux

the driver is
NVIDIA-Linux-x86_64-340.107.run

Nvidia card is
VGA compatible controller: NVIDIA Corporation G96 [GeForce 9500 GT] (rev a1)

Some errors i found with journalctl are the following.

systemd[1]: getty@tty1.service: Service has no hold-off time (RestartSec=0), scheduling restart.
systemd[1]: Stopped Getty on tty1.
systemd[1]: Started Getty on tty1.
-----------------------
[ 11.531029] NVRM: Your system is not currently configured to drive a VGA console
[ 11.531032] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[ 11.531034] NVRM: requires the use of a text-mode VGA console. Use of other console
[ 11.531036] NVRM: drivers including, but not limited to, vesafb, may result in
[ 11.531037] NVRM: corruption and stability problems, and is not supported.
--------------------------------------------------
systemctl cat getty@tty1.service

# /usr/lib/systemd/system/getty@.service
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.

[Unit]
Description=Getty on %I
Documentation=man:agetty(8) man:systemd-getty-generator(8)
Documentation=http://0pointer.de/blog/projects/serial-console.html
After=systemd-user-sessions.service plymouth-quit-wait.service
After=rc-local.service

# If additional gettys are spawned during boot then we should make
# sure that this is synchronized before getty.target, even though
# getty.target didn't actually pull it in.
Before=getty.target
IgnoreOnIsolate=yes

# IgnoreOnIsolate causes issues with sulogin, if someone isolates
# rescue.target or starts rescue.service from multi-user.target or
# graphical.target.
Conflicts=rescue.service
Before=rescue.service

# On systems without virtual consoles, don't start any getty. Note
# that serial gettys are covered by serial-getty@.service, not this
# unit.
ConditionPathExists=/dev/tty0

[Service]
# the VT is cleared by TTYVTDisallocate
# The '-o' option value tells agetty to replace 'login' arguments with an
# option to preserve environment (-p), followed by '--' for safety, and then
# the entered username.
ExecStart=-/sbin/agetty -o '-p -- \\u' --noclear %I $TERM
Type=idle
Restart=always
RestartSec=0
UtmpIdentifier=%I
TTYPath=/dev/%I
TTYReset=yes
TTYVHangup=yes
TTYVTDisallocate=yes
KillMode=process
IgnoreSIGPIPE=no
SendSIGHUP=yes

# Unset locale for the console getty since the console has problems
# displaying some internationalized messages.
Environment=LANG= LANGUAGE= LC_CTYPE= LC_NUMERIC= LC_TIME= LC_COLLATE= LC_MONETARY= LC_MESSAGES= LC_PAPER= LC_NAME= LC_ADDRESS= LC_TELEPHONE= LC_MEASUREMENT= LC_IDENTIFICATION=

[Install]
WantedBy=getty.target
DefaultInstance=tty1

# /usr/lib/systemd/system/getty@tty1.service.d/noclear.conf
[Service]
# ensure tty1 isn't cleared (bnc#804158)
TTYVTDisallocate=no

i must also say that i have configured 2 screens and working as expected, first main screen is a 1920x1080 and the second is a 1680x1050

I also have a look at https://doc.opensuse.org/documentati...a.trouble.html but did not find something relevant
Any help would be appreciated.
thank you.

@akarako:
Have you checked the “System Keyboard layout”?

The culprit may well be the value of the “KEYTABLE=” parameter defined in the file ‘/etc/sysconfig/keyboard’ …

• Your ‘root’ user's password may well be incorrectly mapped by the system's keyboard configuration …

To repair this issue, the only reliable method is to boot an installation DVD or USB-stick and enter the “system repair” mode …
The openSUSE instructions are here: <https://doc.opensuse.org/documentati...recover.rescue>.

Quote:

---

Originally Posted by dcurtisfra

@akarako:
Have you checked the “System Keyboard layout”?

The culprit may well be the value of the “KEYTABLE=” parameter defined in the file ‘/etc/sysconfig/keyboard’ …

• Your ‘root’ user's password may well be incorrectly mapped by the system's keyboard configuration …

To repair this issue, the only reliable method is to boot an installation DVD or USB-stick and enter the “system repair” mode …
The openSUSE instructions are here: <https://doc.opensuse.org/documentati...recover.rescue>.

---

Hi dcurtisfra,

Thanks for replying..
I have no parameter KEYTABLE= in file /etc/sysconfig/keyboard

cd /etc/sysconfig/
wakarako:/etc/sysconfig # cat keyboard
## Path: Hardware/Keyboard
## Description: Keyboard settings for the text console
## ServiceRestart: kbdsettings
#

## Type: integer
## Default:
#
# Keyboard delay time in ms (250, 500, 750, 1000)
KBD_DELAY=""

## Type: string(2.0,2.1,2.3,2.5,2.7,3.0,3.3,3.7,4.0,4.3,4.6,5.0,5.5,6.0,6.7,7.5,8.0,8.6,9.2,10.0,10.9,12.0,13.3,15.0,16.0,17.1,18.5,20.0,21.8,24.0,26.7,30.0)
## Default:
#
# Keyboard repeat rate (2.0 - 30.0)
KBD_RATE=""

## Type: list(bios,yes,no)
## Default: bios
#
# NumLock on? ("yes" or "no" or "bios" for BIOS setting)
# This setting may interfere with GNOME /org/gnome/settings-daemon/peripherals/keyboard/remember-numlock-state DConf key.
KBD_NUMLOCK="bios"

## Type: yesno
## Default: no
#
# ScrollLock on? ("yes" or "no")
KBD_SCRLOCK="no"

## Type: yesno
## Default: no
#
# CapsLock on? ("yes" or "no")
KBD_CAPSLOCK="no"

## Type: yesno
## Default: no
#
# Disable CAPS LOCK and make it a normal Shift key?
# (Ctrl Caps Lock will still toggle Caps Lock functionality)
# Note that you need to tweak the xkb maps or use xmodmap
# if you want to do the same under X-Windows. In ~/.Xmodmap:
# keycode 0x42 = Shift_L Shift_L
#
KBD_DISABLE_CAPS_LOCK="no"

## Type: string
## Default:
#
# ttys for the above settings
# Example: "tty1 tty2"
# "" for tty's 1-6
#
KBD_TTY=""

# The YaST-internal identifier of the attached keyboard.
#
YAST_KEYBOARD="english-us,pc104"

I don't know if this is relevant

https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15/
section 3.2.12

wakarako:/etc/sysconfig # cat /etc/vconsole.conf
KEYMAP=us
FONT=eurlatgr.psfu
FONT_MAP=none
FONT_UNIMAP=

wakarako:/etc/sysconfig # cat console
## Path: Hardware/Console
## Description: Text console settings (see also Hardware/Keyboard)
#

## Type: string
## Default: ""
#
# Console settings.
# Note: The KBD_TTY setting from Hardware/Keyboard (sysconfig/keyboard)
# also applies for the settings here.
#
# Load this console font on bootup:
# (/usr/share/kbd/consolefonts/)
#
CONSOLE_FONT=""

## Type: string
## Default: ""
#
# Some fonts come without a unicode map.
# (.psfu fonts supposedly have it, others often not.)
# You can then specify the unicode mapping of your font
# explicitly. (/usr/share/kbd/unimaps/)
# Normally not needed.
#
CONSOLE_UNICODEMAP=""

## Type: string
## Default: ""
#
# Most programs output 8 bit characters, so you need a table to
# translate those characters into unicode. That one can be specified
# here. (/usr/share/kbd/consoletrans/)
# (Note: If your console is in utf-8 mode you don't need this.)
# If your code does not use a unicode mapping at all (because you
# e.g. explicitly specified UNICODEMAP="none") you may circumvent
# the translation via unicode, but load a map which directly maps
# 8 bit output of your program to a font position.
#
CONSOLE_SCREENMAP=""

## Type: string
## Default: ""
#
# for some fonts the console has to be initialized with CONSOLE_MAGIC.
# CONSOLE_MAGIC can be empty or have the values "(B", ")B", "(K" or ")K".
# Normally not needed (automatically handled by setfont).
#
CONSOLE_MAGIC=""

# Encoding used for output of non-ascii characters.
#
CONSOLE_ENCODING="UTF-8"

I have the same exact problem after last system upgrade. Prior to that I was running Leap 15 without problem. I have run strace on the service and it seems the terminal stops working. The read system call does not return despite typing on the console:

To see which process is got tty1

desktop32:~ # fuser /dev/tty1
/dev/tty1: 14361

desktop32:~ # strace -p 14361
strace: Process 14361 attached
select(5, [0 4], NULL, NULL, NULL

When I go to console 1 and type user and password I get lots of output, and finally stops at read

...
ioctl(0, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(0, TCGETS, {B38400 opost isig icanon echo ...}) = 0
rt_sigprocmask(SIG_BLOCK, [TSTP], [], 8) = 0
ioctl(0, SNDCTL_TMR_CONTINUE or TCSETSF, {B38400 opost isig icanon -echo ...}) = 0
write(2, "Password: ", 10) = 10
read(0,

Note that at this point I have already typed the password, but it seems read call is blocked. Then After 1 minute:

read(0, 0x7ffcaf3c13f0, 511) = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
--- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} ---
rt_sigaction(SIGALRM, {sa_handler=0x55a7daa72640, sa_mask=[ALRM], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f275c23f160}, {sa_handler=0x55a7daa72680, sa_mask=[ALRM], sa_flags=SA_RESTORER, sa_restorer=0x7f275c23f160}, 8) = 0
alarm(10) = 0
write(2, "login: timed out after 60 second"..., 33) = 33
rt_sigaction(SIGALRM, {sa_handler=SIG_IGN, sa_mask=[ALRM], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f275c23f160}, {sa_handler=0x55a7daa72640, sa_mask=[ALRM], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f275c23f160}, 8) = 0
alarm(0) = 10
ioctl(0, TCGETS, {B38400 opost isig icanon -echo ...}) = 0
ioctl(0, SNDCTL_TMR_START or TCSETS, {B38400 opost isig icanon echo ...}) = 0
exit_group(0) = ?
+++ exited with 0 +++

@akarako:

Therefore, your system is setup for a US-American console keyboard.
If you have another console keyboard layout (non-US-American keys and codes) then, that's the issue at hand …

@ akarako and juando:

Please try the following test:

• At a VT (tty1 … tty6) username prompt, type in the “root” password and check that the characters displayed are in fact those of root's password.

Same problem after upgrade to kernel 4.12.14-lp150.12.25-default
If I choose from GRUB menu to boot with previous kernel 4.12.14-lp150.12.22-default, everything works perfect.

Also after kernel upgrade I've got issues with NVidia proprietary driver - switching back and forth between tty1 and X-session eventually crashes kwin and it falls back to Xrender for desktop effects and cannot be set to use OpenGL until reboot.

Quote:

---

Originally Posted by dcurtisfra

@ akarako and juando:

Please try the following test:

• At a VT (tty1 … tty6) username prompt, type in the “root” password and check that the characters displayed are in fact those of root's password.

---

I tried it, it seems keyboard mapping is correct. I also upgraded to kernel 4.12.14-lp150.12.25-default so it seems something is broken.

Quote:

---

Originally Posted by inozemcew

Same problem after upgrade to kernel 4.12.14-lp150.12.25-default
If I choose from GRUB menu to boot with previous kernel 4.12.14-lp150.12.22-default, everything works perfect.

Also after kernel upgrade I've got issues with NVidia proprietary driver - switching back and forth between tty1 and X-session eventually crashes kwin and it falls back to Xrender for desktop effects and cannot be set to use OpenGL until reboot.

---

I can confirm. It also works for me with the old kernel.