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/documentation/leap/startup/html/book.opensuse.startup/cha.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/documentation/leap/startup/html/book.opensuse.startup/cha.trouble.html#sec.trouble.data.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

[size=3]…
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,
[/size]
Note that at this point I have already typed the password, but it seems read call is blocked. Then After 1 minute:

[size=3]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 +++[/size]

@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.

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.

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

I have the same problem. I will not be able to log in from any tty (tty1-tty6).
I made a strace to the agetty command on tty1 and when it is asking for the password from fd 0, it will not receive it. So, it times out and restarts.
Doing strace on other PC with an older kernel the password is received by agetty.
So, I rebooted with the previous kernel and it works fine. I was able to log on.
THere is a problem with kernel 4.12.14-lp150.12.25-default. I guess it is the keyboard driver

I have the same problem and am unable to login on tty1 - tty6 with kernel-default version 4.12.14-lp150.12.25.1, however, everything works fine with the previous kernel(s).

This must be a kernel bug.

FYI,

Gordon

I have the same problem and am unable to login on tty1 - tty6 with kernel version 4.12.14-lp150.12.25, however, everything works fine with the 4.12.14-lp150.12.22 and earlier kernels. You type in the password and nothing returns - no error - no prompt - dead terminal.

I have the same problem with the new released kernel and am unable to login on tty1 - tty6 with kernel version 4.12.14-lp150.12.28, this version auto enters the password ( you cannot type anything ) and it says it cannot log you in and try again.

Makes you wonder if they test anything before releasing it to the masses.

Is everyone experiencing this failure using a default-based installation, meaning BTRFS / filesystem, Plymouth and Gnome/GDM or Plasma/SDDM? What about filesystem encryption? I have multiple 15.0 installations apparently working perfectly with 4.12.14-lp150.12.25.1 default kernel. None use BTRFS, Plymouth, Gnome, Plasma or encryption.

kernel-default-4.12.14-lp150.12.28.1.x86_64.rpm hit the mirrors today. PC I upgraded to it still has init3 root login working, but eth0 didn’t come up until 2nd boot using it.

Hi
No issues here with the new kernel on Leap 15 Test Machine;


System:    Host: gekkota-nagios Kernel: 4.12.14-lp150.12.28-default x86_64 bits: 64 Desktop: Gnome 3.26.2
           Distro: openSUSE Leap 15.0
Machine:   Device: unknown System: Apple product: MacBook3 1 v: 1.0 serial: N/A
           Mobo: Apple model: Mac-F22788C8 v: PVT serial: N/A
           UEFI: Apple v: MB31.88Z.008E.B02.0803051832 date: 03/05/08
Battery    BAT0: charge: 41.9 Wh 96.0% condition: 43.7/57.7 Wh (76%)
CPU:       Dual core Intel Core2 Duo T7300 (-MCP-) cache: 4096 KB
           clock speeds: max: 2000 MHz 1: 800 MHz 2: 2000 MHz
Graphics:  Card: Intel Mobile GM965/GL960 Integrated Graphics Controller (primary)
           Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 1280x800@59.91hz
           OpenGL: renderer: Mesa DRI Intel 965GM version: 2.1 Mesa 18.0.2
Audio:     Card Intel 82801H (ICH8 Family) HD Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.12.14-lp150.12.28-default
Network:   Card-1: Broadcom Limited BCM4321 802.11a/b/g/n driver: wl
           IF: wlan0 state: down mac: <filter>
           Card-2: Marvell 88E8058 PCI-E Gigabit Ethernet Controller driver: sky2
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 500.1GB (1.7% used)
           ID-1: /dev/sda model: HGST_HTS545050A7 size: 500.1GB
Partition: ID-1: / size: 40G used: 5.2G (13%) fs: btrfs dev: /dev/sda7
           ID-2: /opt size: 40G used: 5.2G (13%) fs: btrfs dev: /dev/sda7
           ID-3: /tmp size: 40G used: 5.2G (13%) fs: btrfs dev: /dev/sda7
           ID-4: /home size: 40G used: 5.2G (13%) fs: btrfs dev: /dev/sda7
           ID-5: /var size: 40G used: 5.2G (13%) fs: btrfs dev: /dev/sda7
Sensors:   System Temperatures: cpu: 46.2C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 223 Uptime: 0:08 Memory: 771.9/3919.3MB Client: Shell (bash) inxi: 2.3.40

I just updated to 4.12.14-lp150.12.28 and experienced the same problem as reported by larryr. That is, the behavior has changed but still fails. Once I enter the user name then the password prompt appears to be auto-entered (user cannot enter a password) and the login fails.

FYI,

Gordon

On Sat 15 Dec 2018 02:46:03 PM CST, gldickens3 wrote:

larryr;2888898 Wrote:
> I have the same problem with the new released kernel and am unable to
> login on tty1 - tty6 with kernel version 4.12.14-lp150.12.28, this
> version auto enters the password ( you cannot type anything ) and it
> says it cannot log you in and try again.

I just updated to 4.12.14-lp150.12.28 and experienced the same problem
as reported by larryr. That is, the behavior has changed but still
fails. Once I enter the user name then the password prompt appears to
be auto-entered (user cannot enter a password) and the login fails.

FYI,

Gordon

Hi
Is this an external keyboard? Maybe hardware info may be applicable;


hwinfo --keyboard


Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.25-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

This is not an external keyboard. This is an HP ZBook laptop. Also, this same problem occurs with my System 76 Darter laptop as well.

Output from the command “hwinfo --keyboard” on my HP ZBook laptop is as follows:

26: PS/2 00.0: 10800 Keyboard                                   
  [Created at input.226]
  Unique ID: nLyy.+49ps10DtUF
  Hardware Class: keyboard
  Model: "AT Translated Set 2 keyboard"
  Vendor: 0x0001 
  Device: 0x0001 "AT Translated Set 2 keyboard"
  Compatible to: int 0x0211 0x0001
  Device File: /dev/input/event0
  Device Number: char 13:64
  Driver Info #0:
    XkbRules: xfree86
    XkbModel: pc104
  Config Status: cfg=no, avail=yes, need=no, active=unknown

This has never been a problem in the past with other kernel versions.

FYI,

Gordon

Hi
So on my old MacBook it uses the USB driver so would have to be driver related, as a test can you connect an external keyboard and check that works?

# hwinfo --keyboard
14: PS/2 00.0: 10800 Keyboard                                   
  [Created at input.226]
  Unique ID: nLyy.+49ps10DtUF
  Hardware Class: keyboard
  Model: "AT Translated Set 2 keyboard"
  Vendor: 0x0001 
  Device: 0x0001 "AT Translated Set 2 keyboard"
  Compatible to: int 0x0211 0x0001
  Device File: /dev/input/event0
  Device Number: char 13:64
  Driver Info #0:
    XkbRules: xfree86
    XkbModel: pc104
  Config Status: cfg=no, avail=yes, need=no, active=unknown


That is what a Virtualbox Keyboard comes out as.

It does this on Dell laptops (D820, D830, 7559) Gigabyte AM3 Motherboards and All Virtualbox Opensuse 15 machines.

I have a bunch of USB Opensuse 15 that I would be happy to forward to someone to debug the problem - the USB loads fine as a USB vmdk file - it already has the virtualbox guest additions installed.