You are not logged in.

#1 2022-11-30 12:31:52

deivi
Member
Registered: 2020-05-24
Posts: 19

[SOLVED] ThinkPad X1 Carbon Gen 10 | Weird double login bug

Hi,

Recently bought this new laptop and installed plain arch linux and a WM (qtile) on it. Used my personal installation script to set up everything.

Note that, despite the errors and weird behavior, everything works just as expected, including WiFi, bluetooth, audio, screen, keyboard backlight, brightness, media keys etc.

Two major concerns I have:
- I have some errors in journal I have not been able to fix
- TTY login screen weirdly blinks when starting laptop and I have to either wait or login twice

TTY login weird bug description:
1. I turn on my computer
2. I reach usual TTY login (I don't use login/display manager, just startx when logging in)
3. I type in my username and password
4. After 2 seconds, the screen blinks in black and shows login again
5. I login again, this time normally

I noticed that it is about time, not logging in twice. There is this alternative flow:
1. I turn on my computer
2. I reach usual TTY login (I don't use login/display manager, just startx when logging in)
3. I wait, after 2-3 seconds the screen blinks in black and shows login again
4. I wait again, after 2-3 seconds screen brightness sligthly increases
5. I can now login normally

Laptop info:

bios-vendor:            LENOVO
bios-version:           N3AET65W
bios-release-date:      04/08/2022
bios-revision:          1.32
system-manufacturer:    LENOVO
system-product-name:    21CBCTO1WW
system-version:         LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10

All PCI devices:

~ ❯ lspci -v
00:00.0 Host bridge: Intel Corporation Device 4601 (rev 04)
00:02.0 VGA compatible controller: Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] (rev 0c)
00:04.0 Signal processing controller: Intel Corporation Alder Lake Innovation Platform Framework Processor Participant (rev 04)
00:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0 (rev 04)
00:07.0 PCI bridge: Intel Corporation Alder Lake-P Thunderbolt 4 PCI Express Root Port #0 (rev 04)
00:07.2 PCI bridge: Intel Corporation Alder Lake-P Thunderbolt 4 PCI Express Root Port #2 (rev 04)
00:08.0 System peripheral: Intel Corporation 12th Gen Core Processor Gaussian & Neural Accelerator (rev 04)
00:0a.0 Signal processing controller: Intel Corporation Platform Monitoring Technology (rev 01)
00:0d.0 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 USB Controller (rev 04)
00:0d.2 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 NHI #0 (rev 04)
00:0d.3 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 NHI #1 (rev 04)
00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller (rev 01)
00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01)
00:14.3 Network controller: Intel Corporation Alder Lake-P PCH CNVi WiFi (rev 01)
00:15.0 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 (rev 01)
00:15.1 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #1 (rev 01)
00:16.0 Communication controller: Intel Corporation Alder Lake PCH HECI Controller (rev 01)
00:1f.0 ISA bridge: Intel Corporation Alder Lake PCH eSPI Controller (rev 01)
00:1f.3 Audio device: Intel Corporation Alder Lake PCH-P High Definition Audio Controller (rev 01)
00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01)
00:1f.5 Serial bus controller: Intel Corporation Alder Lake-P PCH SPI Controller (rev 01)
04:00.0 Non-Volatile memory controller: Sandisk Corp Device 5017 (rev 01)

All PCI devices (verbose):

~ ❯ lspci -v
[url]https://pastebin.com/9TZ3SCe9[/url]

Journal errors:

~ ❯ journalctl -b -p 3
Nov 30 11:54:27 archa kernel: pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
Nov 30 11:54:27 archa kernel: pci 0000:00:07.2: DPC: RP PIO log size 0 is invalid
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:27 archa kernel: blacklist: Problem blacklisting hash (-13)
Nov 30 11:54:30 archa kernel: spi-nor spi0.0: unrecognized JEDEC id bytes: 3c 30 30 09 d2 38
Nov 30 11:54:34 archa kernel: usb 3-7.1: 1:1: cannot set freq 48000 to ep 0x3
Nov 30 11:54:35 archa bluetoothd[547]: src/plugin.c:plugin_init() Failed to init vcp plugin
Nov 30 11:54:35 archa bluetoothd[547]: src/plugin.c:plugin_init() Failed to init mcp plugin
Nov 30 11:54:35 archa bluetoothd[547]: src/plugin.c:plugin_init() Failed to init bap plugin
Nov 30 11:54:36 archa kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Nov 30 11:54:39 archa pipewire[925]: mod.filter-chain: error id:2 seq:18 res:-2 (No such file or directory): no node available
Nov 30 11:54:39 archa pipewire[925]: mod.filter-chain: error id:2 seq:18 res:-2 (No such file or directory): no node available
Nov 30 11:54:39 archa pipewire[925]: mod.filter-chain: error id:2 seq:18 res:-2 (No such file or directory): no node available
Nov 30 11:54:39 archa pipewire[925]: mod.filter-chain: error id:2 seq:18 res:-2 (No such file or directory): no node available
Nov 30 11:54:39 archa pipewire[925]: mod.filter-chain: error id:2 seq:18 res:-2 (No such file or directory): no node available
Nov 30 11:54:39 archa pipewire[925]: mod.filter-chain: error id:2 seq:18 res:-2 (No such file or directory): no node available
Nov 30 11:54:39 archa pipewire[925]: mod.filter-chain: error id:2 seq:18 res:-2 (No such file or directory): no node available
Nov 30 11:54:39 archa pipewire[925]: mod.filter-chain: error id:2 seq:18 res:-2 (No such file or directory): no node available

Complete journal:

~ ❯ journalctl -b 1
[url]https://pastebin.com/0xfsBg9R[/url]

Last edited by deivi (2022-11-30 14:43:41)

Offline

#2 2022-11-30 13:12:55

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,431

Re: [SOLVED] ThinkPad X1 Carbon Gen 10 | Weird double login bug

Please wrap the outputs in [ code ] instead of [ quote ] tags.

The blacklisting hash is listed if the secure boot keys of your EFI don't make sense to the kernel, but can fairly safely be ignored as can most of the errors you have here.

For the flickering issue during initial login try enabling early KMS: https://wiki.archlinux.org/title/Kernel … _KMS_start

To make more telling diagnosis we'd need an actual complete journal including kernel messages, so maybe post

sudo journalctl -b

Offline

#3 2022-11-30 13:49:30

deivi
Member
Registered: 2020-05-24
Posts: 19

Re: [SOLVED] ThinkPad X1 Carbon Gen 10 | Weird double login bug

Enabling early KMS did fix most of the login blink issue, and I say "most" because it stills takes a little bit to slightly increase brightness, allowing me to login just once. However, this is a matter of 1s, so it does not bother me much. If I still try to log in immediately I need to login twice, so no idea what is going on there. I'm happy enough though, thanks.

Although I know most journal errors can be ignored, I still want to know why are they showing up.

 ❯ sudo journalctl -b
https://pastebin.com/FXff8RM7

Offline

#4 2022-11-30 14:28:16

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,431

Re: [SOLVED] ThinkPad X1 Carbon Gen 10 | Weird double login bug

Again most of those are firmware quirks where the kernel thinks a device does not behave like the specification tells it it should. Your "safest" bet is to simply ignore them. If you want to actively do something, check whether a EFI firmware update exists that would fix things.

The first two messages are a firmware spec bug: https://bugzilla.kernel.org/show_bug.cgi?id=209943 - a patch to quirk out some faulty boards is expected to land 6.1, in general the message is harmless and doesn't affect anything.
The blacklist messages are due to secure boot keys in your firmware not matching a kernel blacklist for unsafe keys - you can "fix" this by erasing all  your secure boot keys obviously do not do this if you don't know what they are used for, you could break your system, if you don't know why lenovo set things up this way) - https://bbs.archlinux.org/viewtopic.php?id=278860
The next some quirk in the SPI device: https://de.wikipedia.org/wiki/Serial_Pe … _Interface likely irrelevant for day to day

The next is the first that I'd say may be of remote interest to a normal person not actually working on any lower level stuff, your USB audio device wasn't able to set the audio frequency to 48kHz, which can also be normal or maybe just an early boot/device init quirk, this likely correlates with the pipewire node warnings seen later, since pipewire will by default try to set up a 48kHz playback device - if there are no othe errors - again ignore the thing - if you want to check whether you can not even probe 48kHz if the device in question does not support things   https://wiki.archlinux.org/title/PipeWi … ample_rate

All next 4 are BT errors, which is likely to boil down to bluez testing whether your adapter supports the relevant protocols and then simply logging out a message if it doesn't and continuing without them - again ignore them, or configure bluez to not even try to load plugins your adapter doesn't support.

In general if you really want to know "why they happen" you need to punch them into google, interpret the results you get an then determine whether the benefits are worth the work for something that is mostly of cosmetic nature.

Last edited by V1del (2022-11-30 14:29:13)

Offline

#5 2022-11-30 14:42:48

deivi
Member
Registered: 2020-05-24
Posts: 19

Re: [SOLVED] ThinkPad X1 Carbon Gen 10 | Weird double login bug

Thanks a lot for the research and overview, it is very helpful. Marking issue as solved.

Offline

Board footer

Powered by FluxBB