TTY "Login incorrect" after booting up with DP 2nd -

vi_me · 2021-01-18 04:14:54

Laptop Lenovo Legion Y540
Monitor Asus BE27A series (2560x1440)

Laptop has a miniDP and it is connected to a full size DP on a monitor.
Whenever I try to log in (using tty) every time I get "Login incorrect".
I checked in "login" section all password characters seem to be correct characters...
Every time I have Monitor ON and connected via DP(monitor)-miniDP(laptop) the issue occurs.
If I turn off display or disconnect it before providing credentials, I can log in just fine, and after running startx issue disappears completely in tty2, 3, etc... after that external monitor just mirrors the main monitor of my laptop in tty.
In addition same monitor provokes no such issue when connected via HDMI.

Any help appreciated

seth · 2021-01-18 08:25:46

sudo libinput list-devices

Does anything there look like it's coming from the monitor (when attached via DP)

vi_me · 2021-01-19 16:24:29

seth wrote:

sudo libinput list-devices
Does anything there look like it's coming from the monitor (when attached via DP)

Device:           Video Bus
Kernel:           /dev/input/event3
Group:            1
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           Power Button
Kernel:           /dev/input/event1
Group:            2
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           Lid Switch
Kernel:           /dev/input/event0
Group:            3
Seat:             seat0, default
Capabilities:     switch
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           Integrated Camera: Integrated C
Kernel:           /dev/input/event26
Group:            5
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           ITE Tech. Inc. ITE Device(8910) Keyboard
Kernel:           /dev/input/event27
Group:            6
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           ITE Tech. Inc. ITE Device(8910) Consumer Control
Kernel:           /dev/input/event28
Group:            6
Seat:             seat0, default
Capabilities:     keyboard pointer 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    disabled
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           ITE Tech. Inc. ITE Device(8910) Wireless Radio Control
Kernel:           /dev/input/event29
Group:            6
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           MSFT0001:01 04F3:309E Mouse
Kernel:           /dev/input/event6
Group:            7
Seat:             seat0, default
Capabilities:     pointer 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   *button
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   flat *adaptive
Rotation:         n/a

Device:           MSFT0001:01 04F3:309E Touchpad
Kernel:           /dev/input/event7
Group:            7
Seat:             seat0, default
Size:             96x48mm
Capabilities:     pointer gesture
Tap-to-click:     disabled
Tap-and-drag:     enabled
Tap drag lock:    disabled
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   *two-finger edge 
Click methods:    none
Disable-w-typing: enabled
Accel profiles:   flat *adaptive
Rotation:         n/a

Device:           Ideapad extra buttons
Kernel:           /dev/input/event4
Group:            8
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           AT Translated Set 2 keyboard
Kernel:           /dev/input/event2
Group:            9
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           ckb2: CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard vKB
Kernel:           /dev/input/event24
Group:            10
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           ckb2: CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard vM
Kernel:           /dev/input/event25
Group:            11
Seat:             seat0, default
Capabilities:     pointer 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: disabled
Calibration:      n/a
Scroll methods:   button
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   flat *adaptive
Rotation:         n/a

seth · 2021-01-19 16:37:53

udevadm monitor

Attach the output, note the device IDs and create a udev rule that sets ID_INPUT=0
https://wiki.archlinux.org/index.php/Udev

vi_me · 2021-01-21 14:46:37

seth wrote:

udevadm monitor
Attach the output, note the device IDs and create a udev rule that sets ID_INPUT=0
https://wiki.archlinux.org/index.php/Udev

I don't get any output from

❯ udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

seth · 2021-01-21 15:06:06

There's no whatsoever output from that when (re-)attaching the monitor to the display port?
Is the device from post #3 also there when you use HDMI?

vi_me · 2021-01-21 18:56:17

seth wrote:

There's no whatsoever output from that when (re-)attaching the monitor to the display port?
Is the device from post #3 also there when you use HDMI?

Turns out it's not enough to "Turn if off and on again.", I had to physically disconnect and re-connect the cable.

❯ udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[11110.764356] online   /devices/system/container/PRP00001:00 (container)
UDEV  [11110.767475] online   /devices/system/container/PRP00001:00 (container)
KERNEL[11116.657326] online   /devices/system/container/PRP00001:00 (container)
UDEV  [11116.660242] online   /devices/system/container/PRP00001:00 (container)

vi_me · 2021-01-21 21:42:42

seth wrote:

There's no whatsoever output from that when (re-)attaching the monitor to the display port?
Is the device from post #3 also there when you use HDMI?

Can you help with the udev rule part? Frankly I've never done it before...

seth · 2021-01-21 21:55:38

There doesn't seem to be an input device event with this - is the device there when you use HDMI?
(Webcams often come with a keyboard device)

Along the requirement to have the output activated to generate a false login (on tty only), this is pretty weird.

If you login, then switch the DP output on and run "sudo libinput debug-events", do you get spurios input?
Also: does passing creds to sudo fail likewise or is it just the getty login?

vi_me · 2021-01-21 22:17:44

seth wrote:

There doesn't seem to be an input device event with this - is the device there when you use HDMI?
(Webcams often come with a keyboard device)
Along the requirement to have the output activated to generate a false login (on tty only), this is pretty weird.
If you login, then switch the DP output on and run "sudo libinput debug-events", do you get spurios input?
Also: does passing creds to sudo fail likewise or is it just the getty login?

I can't even run the command... it gives problems with sudo too...
Thing is when I do startx I have some xrandr calls to set up my outputs and they seem to fix the issue.
The only other clue I have is that when I try to either log in or use sudo and entering a password, it reports a wrong password and

^@

characters appear.

I managed to run "libinput debug-events" and this starts periodically logged when I connect a monitor via DP

Last edited by vi_me (2021-01-21 22:28:18)

seth · 2021-01-21 22:45:51

https://bbs.archlinux.org/viewtopic.php … 6#p1740276

It would seem the WMI ("lsmod | grep wmi") starts "pressing" the key that switches the output mode when you attach a DP output and that is unhandled on the console, resulting in the null character being passed through…

vi_me · 2021-01-21 22:59:45

seth wrote:

https://bbs.archlinux.org/viewtopic.php … 6#p1740276
It would seem the WMI ("lsmod | grep wmi") starts "pressing" the key that switches the output mode when you attach a DP output and that is unhandled on the console, resulting in the null character being passed through…

Do you have any suggestions on how to solve it?

seth · 2021-01-21 23:01:18

Did you check the link I posted?
Also what's the output of the lsmod grep?

vi_me · 2021-01-21 23:08:22

seth wrote:

Did you check the link I posted?
Also what's the output of the lsmod grep?

I checked the link posted... and I ASSUME you suggest blacklisting wmi?

Output:
Sorry it's pretty uncomfortable to post output from a tty

vi_me · 2021-01-22 00:13:07

seth wrote:

Did you check the link I posted?
Also what's the output of the lsmod grep?

What do you suggest, from the link you posted?

seth · 2021-01-22 08:26:15

1. please don't bump. simply edit yoru last post unless somebody has replied
2. to upload output from a terminal, see the first link in my signature. Also the terminal wasn't relevant here at all (ie. you could have done that from a gnome terminal or whatever)
3. The link clearly suggests to blacklist input_polldev, see https://wiki.archlinux.org/index.php/Ke … acklisting and check "lsmod" to ensure the module was indeed not loaded.

vi_me · 2021-01-22 17:28:58

seth wrote:

1. please don't bump. simply edit yoru last post unless somebody has replied
2. to upload output from a terminal, see the first link in my signature. Also the terminal wasn't relevant here at all (ie. you could have done that from a gnome terminal or whatever)
3. The link clearly suggests to blacklist input_polldev, see https://wiki.archlinux.org/index.php/Ke … acklisting and check "lsmod" to ensure the module was indeed not loaded.

Problem is "input_polldev" is never loaded on my system even without me blacklisting it...
Checked booth by

lsmod

as well as by

mkinitcpio -M

seth · 2021-01-22 20:32:25

You can try to blacklist intel_wmi_thunderbolt (just a hunch), possibly ideapad_laptop - but those might have undesired side-effects (like some other features not being available, you won't break anything)

Alternatively unmap the keycode: https://bbs.archlinux.org/viewtopic.php?id=220444 (what will make it unavailable in X11 as well!)

vi_me · 2021-01-22 22:34:42

seth wrote:

You can try to blacklist intel_wmi_thunderbolt (just a hunch), possibly ideapad_laptop - but those might have undesired side-effects (like some other features not being available, you won't break anything)
Alternatively unmap the keycode: https://bbs.archlinux.org/viewtopic.php?id=220444 (what will make it unavailable in X11 as well!)

I added a udev rule to ignore this event in libinput.
Now the events aren't in log but it just prints "^@" all the time... issue with sudo and login tty screen persists...
What is weird is that xrandr activation and config of the monitor on startx resolves the issue...

seth · 2021-01-23 09:40:39

What kind of udev rule?
The linked post suggests to alter the hwdb?

Did you try to blacklist the wmi/ideapad modules?

Either the randr output configuration makes the output stop yelling "HELLOHELLOHELLO!" or the key event is handled and ignored by X11 (did you check "libinput debug-events" in an X11 session to see whether it still occurs?)

vi_me · 2021-01-25 19:01:38

The solution was to disable "DDC/CI" and "Auto Source Detection" on my monitor.

seth · 2021-01-25 21:12:55

Cool.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2021-01-18 04:14:54

TTY "Login incorrect" after booting up with DP 2nd -

#2 2021-01-18 08:25:46

Re: TTY "Login incorrect" after booting up with DP 2nd -

#3 2021-01-19 16:24:29

Re: TTY "Login incorrect" after booting up with DP 2nd -

#4 2021-01-19 16:37:53

Re: TTY "Login incorrect" after booting up with DP 2nd -

#5 2021-01-21 14:46:37

Re: TTY "Login incorrect" after booting up with DP 2nd -

#6 2021-01-21 15:06:06

Re: TTY "Login incorrect" after booting up with DP 2nd -

#7 2021-01-21 18:56:17

Re: TTY "Login incorrect" after booting up with DP 2nd -

#8 2021-01-21 21:42:42

Re: TTY "Login incorrect" after booting up with DP 2nd -

#9 2021-01-21 21:55:38

Re: TTY "Login incorrect" after booting up with DP 2nd -

#10 2021-01-21 22:17:44

Re: TTY "Login incorrect" after booting up with DP 2nd -

#11 2021-01-21 22:45:51

Re: TTY "Login incorrect" after booting up with DP 2nd -

#12 2021-01-21 22:59:45

Re: TTY "Login incorrect" after booting up with DP 2nd -

#13 2021-01-21 23:01:18

Re: TTY "Login incorrect" after booting up with DP 2nd -

#14 2021-01-21 23:08:22

Re: TTY "Login incorrect" after booting up with DP 2nd -

#15 2021-01-22 00:13:07

Re: TTY "Login incorrect" after booting up with DP 2nd -

#16 2021-01-22 08:26:15

Re: TTY "Login incorrect" after booting up with DP 2nd -

#17 2021-01-22 17:28:58

Re: TTY "Login incorrect" after booting up with DP 2nd -

#18 2021-01-22 20:32:25

Re: TTY "Login incorrect" after booting up with DP 2nd -

#19 2021-01-22 22:34:42

Re: TTY "Login incorrect" after booting up with DP 2nd -

#20 2021-01-23 09:40:39

Re: TTY "Login incorrect" after booting up with DP 2nd -

#21 2021-01-25 19:01:38

Re: TTY "Login incorrect" after booting up with DP 2nd -

#22 2021-01-25 21:12:55

Re: TTY "Login incorrect" after booting up with DP 2nd -

Board footer