You are not logged in.

Pages: 1 2

#1 2023-12-17 13:01:29

Zibi1981
Member
From: Poland
Registered: 2008-01-31
Posts: 644

Arch is not booting, while Windows 11 has no issues.

Recently I have a very serious issue while booting Arch on my laptop - many times it just won't boot at all. The process stucks for good, even SysRq commands (which I've turned on) are not helpful (probably due to systemd not being functional at that stage of the booting process), and the only thing I can do is a hard reset. I don't even see any option how to debug this situation (accessing journal from my dual-booted Windows system?).
The only thing I see is this:

20231216-145549.jpg
20231216-145615.jpg

Any ideas? Why GRUB is able to flawlessly run W11 but not Arch? Occasionally Arch boots properly, but I don't have any idea what is the reason for this behaviour.

Last edited by Zibi1981 (2023-12-17 13:14:22)

"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."

MSI Raider GE78HX 13VI-032PL

Offline

#2 2023-12-17 13:05:56

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,732
Website

Re: Arch is not booting, while Windows 11 has no issues.

If you see a splash screen then systemd has started so there should be something in the journal you can share here. Please do so. Use a pastebin client from the live ISO and share the URL (but not ix.io, they're sulking at us for spamming them so much).

Please also replace those oversized images with thumbnails or links. We have forum users with limited bandwidth and I'm sure they don't want to waste it on those. Thanks.

EDIT: please also post the output of

lspci -knn -d ::03xx

Last edited by Head_on_a_Stick (2023-12-17 13:07:18)

Are you infected with Wetiko?

Offline

#3 2023-12-17 14:19:05

Zibi1981
Member
From: Poland
Registered: 2008-01-31
Posts: 644

Re: Arch is not booting, while Windows 11 has no issues.

Luckily I was finally able to boot into Arch installed on my disk, but the problem persists. I've seen many recently published posts/reports about similar problems, seems to be a widely present problem with some update (?).

Head_on_a_Stick wrote:

EDIT: please also post the output of

lspci -knn -d ::03xx
$ lspci -knn -d ::03xx
00:02.0 VGA compatible controller [0300]: Intel Corporation Raptor Lake-S UHD Graphics [8086:a788] (rev 04)
        DeviceName: Onboard - Video
        Subsystem: Micro-Star International Co., Ltd. [MSI] Raptor Lake-S UHD Graphics [1462:13cd]
        Kernel driver in use: i915
        Kernel modules: i915
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GN21-X11 [GeForce RTX 4090 Laptop GPU] [10de:2717] (rev a1)
        Subsystem: Micro-Star International Co., Ltd. [MSI] GN21-X11 [GeForce RTX 4090 Laptop GPU] [1462:13cd]
        Kernel driver in use: nvidia
        Kernel modules: nouveau, nvidia_drm, nvidia
Head_on_a_Stick wrote:

If you see a splash screen then systemd has started so there should be something in the journal you can share here. Please do so. Use a pastebin client


"You have exceeded the maximum size of 512 kilobytes per Paste."

The above are from a successfully booted Arch Linux system.

"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."

MSI Raider GE78HX 13VI-032PL

Offline

#4 2023-12-17 15:40:16

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,732
Website

Re: Arch is not booting, while Windows 11 has no issues.

Zibi1981 wrote:

"You have exceeded the maximum size of 512 kilobytes per Paste."

Oh shit, they're onto us yikes

Can you load up a graphical live ISO image (grml is my favourite) and use paste.debian.net instead? I'm sure they won't mind, Debian users are the best.

And I am presuming here that you've updated the system before posting and so are running kernel 6.6.7 because 6.6.5 had a wireless regression that gave booting/shutdown problems.

Are you infected with Wetiko?

Offline

#5 2023-12-17 15:54:45

Zibi1981
Member
From: Poland
Registered: 2008-01-31
Posts: 644

Re: Arch is not booting, while Windows 11 has no issues.

My kernel:

Linux MSI-Arch 6.6.7-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 14 Dec 2023 03:45:42 +0000 x86_64 GNU/Linux

I also removed quiet from kernel booting parameters in GRUB config file to be able to track down the issue, but when I regenerated grub.cfg file I've seen this

# LC_ALL=C grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/Vimix/theme.txt
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done

unknown device type nvme0n1 ???

# lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
nvme0n1     259:0    0   1,9T  0 disk 
├─nvme0n1p1 259:1    0   300M  0 part /boot
├─nvme0n1p2 259:2    0   128M  0 part 
├─nvme0n1p3 259:3    0   400G  0 part /windows_c
├─nvme0n1p4 259:4    0 981,8G  0 part 
├─nvme0n1p5 259:5    0     2G  0 part [SWAP]
├─nvme0n1p6 259:6    0   498G  0 part /
├─nvme0n1p7 259:7    0   900M  0 part /windows_x
└─nvme0n1p8 259:8    0  24,7G  0 part /windows_y

"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."

MSI Raider GE78HX 13VI-032PL

Offline

#6 2023-12-17 16:08:33

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,732
Website

Re: Arch is not booting, while Windows 11 has no issues.

Don't worry about that error, it's related to memtest and doesn't stop GRUB from adding the Windows menuentry.

So can we see the journal then? Also post /boot/grub/grub.cfg, just in case that's wrong.

Are you infected with Wetiko?

Offline

#7 2023-12-17 16:35:24

Zibi1981
Member
From: Poland
Registered: 2008-01-31
Posts: 644

Re: Arch is not booting, while Windows 11 has no issues.

After removing quiet from booting parameters and restarting the system I did see these messages being added/refreshed

20231217-171221.jpg

I don't believe my GRUB config file is the culprit as I haven't modified it recently.

There is also one other piece of information that could be useful - so far the system never hung up during boot when there was an USB stick in the port, although I have booted from the SDD.

sudo journalctl -p err..alert
gru 17 17:20:00 MSI-Arch kernel: 
gru 17 17:20:00 MSI-Arch kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  545.29.06  Thu Nov 16 01:59:08 UTC 2023
gru 17 17:20:00 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:20:00 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:20:00 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:20:01 MSI-Arch kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
gru 17 17:20:02 MSI-Arch kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
gru 17 17:20:03 MSI-Arch kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: Transport status: 0x0000004B, valid: 6
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: Loaded firmware version: 83.e8f84e98.0 so-a0-gf4-a0-83.ucode
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL    
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x000002F0 | trm_hw_status0
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x004DC1C6 | branchlink2
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x004D1A5E | interruptlink1
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x004D1A5E | interruptlink2
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00015B8A | data1
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000010 | data2
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | data3
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x003D7753 | beacon time
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00047C98 | tsf low
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | tsf hi
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | time gp1
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x0005D6E1 | time gp2
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000053 | uCode version major
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0xE8F84E98 | uCode version minor
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000430 | hw version
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00C80002 | board version
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x8001FC11 | hcmd
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00020000 | isr0
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | isr1
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x48F04802 | isr2
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00C3000C | isr3
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | isr4
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x001E0103 | last cmd Id
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00015B8A | wait_event
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_control
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_duration
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_mhvalid
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_addr_match
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000018 | lmpm_pmg_sel
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | timestamp
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00002048 | flow_handler
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: Transport status: 0x0000004B, valid: 6
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: Loaded firmware version: 83.e8f84e98.0 so-a0-gf4-a0-83.ucode
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL    
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x000002F0 | trm_hw_status0
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x004DC1C6 | branchlink2
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x004D1A5E | interruptlink1
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x004D1A5E | interruptlink2
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00015B8A | data1
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000010 | data2
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | data3
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x003D7753 | beacon time
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00047C98 | tsf low
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | tsf hi
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | time gp1
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x0005D6E1 | time gp2
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000053 | uCode version major
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0xE8F84E98 | uCode version minor
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000430 | hw version
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00C80002 | board version
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x8002FC11 | hcmd
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00020000 | isr0
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | isr1
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x48F04802 | isr2
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00C3000C | isr3
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | isr4
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | last cmd Id
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00015B8A | wait_event
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_control
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_duration
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_mhvalid
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_addr_match
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000018 | lmpm_pmg_sel
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | timestamp
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00002048 | flow_handler
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: Transport status: 0x0000004B, valid: 7
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x2010190E | ADVANCED_SYSASSERT
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x8047207C | umac branchlink2
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0xC0081560 | umac interruptlink1
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink2
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x0101C71C | umac data1
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0xDEADBEEF | umac data2
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0xDEADBEEF | umac data3
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000053 | umac major
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0xE8F84E98 | umac minor
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x0005D6DA | frame pointer
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0xC0886BE0 | stack pointer
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00220309 | last host cmd
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00020040 | isr status reg
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: IML/ROM dump:
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000B03 | IML/ROM error/state
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x000085DB | IML/ROM data1
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000090 | IML/ROM WFPM_AUTH_KEY_0
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: Fseq Registers:
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x60000000 | FSEQ_ERROR_CODE
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00510003 | FSEQ_TOP_INIT_VERSION
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x001A0003 | FSEQ_CNVIO_INIT_VERSION
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x0000A657 | FSEQ_OTP_VERSION
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000006 | FSEQ_TOP_CONTENT_VERSION
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00080401 | FSEQ_CNVI_ID
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00480410 | FSEQ_CNVR_ID
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00080401 | CNVI_AUX_MISC_CHIP
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00480410 | CNVR_AUX_MISC_CHIP
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00009061 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00000061 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x001A0003 | FSEQ_PREV_CNVIO_INIT_VERSION
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00510003 | FSEQ_WIFI_FSEQ_VERSION
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x00510003 | FSEQ_BT_FSEQ_VERSION
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: 0x000000DC | FSEQ_CLASS_TP_VERSION
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: UMAC CURRENT PC: 0x804946f4
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: LMAC1 CURRENT PC: 0xd0
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: LMAC2 CURRENT PC: 0xd0
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: FW error in SYNC CMD LINK_CONFIG_CMD
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: Failed to send LINK_CONFIG_CMD (action:2): -5
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: Failed to send LINK_CONFIG_CMD (action:2): -5
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: Failed to send LINK_CONFIG_CMD (action:2): -5
gru 17 17:20:04 MSI-Arch kernel: iwlwifi 0000:00:14.3: Scan failed! ret -5
gru 17 17:20:04 MSI-Arch kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
gru 17 17:20:07 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:20:10 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:20:10 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:20:13 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:20:33 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:20:33 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:20:33 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:20:44 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:20:44 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:20:44 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:20:48 MSI-Arch pipewire[21498]: spa.v4l2: '/dev/video0' VIDIOC_QUERYCTRL: Błąd wejścia/wyjścia
gru 17 17:20:50 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:20:50 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:20:50 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:20:50 MSI-Arch systemd[20713]: Failed to start Timed resync.
gru 17 17:20:50 MSI-Arch kernel: overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection.
gru 17 17:21:10 MSI-Arch systemd[1]: Failed to start Refresh Pacman mirrorlist with Reflector..
gru 17 17:21:10 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:21:10 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:21:15 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:21:15 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:21:15 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:23:23 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:23:23 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:23:25 MSI-Arch kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
gru 17 17:23:26 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:23:30 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:24:32 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:24:32 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:24:33 MSI-Arch kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
gru 17 17:24:33 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:24:38 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:25:11 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:25:11 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:25:11 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:25:21 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:25:35 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:25:35 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:25:35 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:26:36 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:26:36 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:26:36 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:27:09 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:27:09 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:27:09 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:27:18 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:27:18 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:27:18 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:27:38 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:27:38 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:27:38 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:27:44 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:27:44 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:27:54 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:27:54 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:27:54 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:27:59 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:27:59 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:27:59 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:28:10 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:28:10 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:28:10 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:34:40 MSI-Arch kwin_wayland[20832]: kwin_libinput: Libinput: event19 - ELAN0305:00 04F3:31FD Touchpad: kernel bug: Touch jump detected and discarded.
                                              See https://wayland.freedesktop.org/libinput/doc/1.24.0/touchpad-jumping-cursors.html for details
gru 17 17:34:42 MSI-Arch kwin_wayland[20832]: kwin_libinput: Libinput: event19 - ELAN0305:00 04F3:31FD Touchpad: kernel bug: Touch jump detected and discarded.
                                              See https://wayland.freedesktop.org/libinput/doc/1.24.0/touchpad-jumping-cursors.html for details
gru 17 17:35:00 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:35:00 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:37:42 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:37:42 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:37:42 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:38:00 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:38:00 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:38:43 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:38:43 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:38:43 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:38:58 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:38:58 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:39:23 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:39:23 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:39:23 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:39:45 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:39:45 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:39:59 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:39:59 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:39:59 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:40:16 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:40:16 MSI-Arch kernel: audit: kauditd hold queue overflow
gru 17 17:40:16 MSI-Arch kernel: audit: kauditd hold queue overflow

Last edited by Zibi1981 (2023-12-17 16:41:23)

"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."

MSI Raider GE78HX 13VI-032PL

Offline

#8 2023-12-17 16:55:02

seth
Member
Registered: 2012-09-03
Posts: 51,582

Re: Arch is not booting, while Windows 11 has no issues.

SysRq commands (which I've turned on) are not helpful (probably due to systemd not being functional at that stage of the booting process)

The sysrq isn't a systemd feature, you're talking to the kernel directly.

You have exceeded the maximum size of 512 kilobytes per Paste.

sudo journalctl -b | curl -F 'file=@-' 0x0.st

iirc the 0x0.st limit is 256 or 512 MB…

-p err..alert

That's not really helpful, you've issues w/ your wifi chip but that would not preclude a boot (it might inhibit your graphical.target DM, though)

Next to the complete journal (and ideally one from a failed boot, but you'll have to enable the sysrq via kernel parameter "sysrq_always_enabled=1") see https://wiki.archlinux.org/title/Genera … l_messages for maybe more output.
Can you reliably boot the multi-user.target (2nd link below) w/ "nomodeset"?

I hope windows fast start is (still) disabled? (3rd link below)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#9 2023-12-17 18:55:19

Zibi1981
Member
From: Poland
Registered: 2008-01-31
Posts: 644

Re: Arch is not booting, while Windows 11 has no issues.

seth wrote:

The sysrq isn't a systemd feature, you're talking to the kernel directly.

I've turned on all the SySRq features

$ sudo cat /proc/sys/kernel/sysrq
1

but still during a failed boot none of the combinations (i.e. ALT + SySRq/PRT SCR + b) seems to work - nothing happens when pressed. But previously I've made that by editing /usr/lib/sysctl.d/50-default.conf every single time systemd had been updated, now I'll added the kernel parameter.

seth wrote:
sudo journalctl -b | curl -F 'file=@-' 0x0.st

iirc the 0x0.st limit is 256 or 512 MB…

http://0x0.st/HY_3.txt    -------------------> This is from a successful boot though. Don't know how to do this while my Linux is unresponsive during boot. The only thing I could imagine is to look for the journal from W11 instance which I dual-boot with Arch.

seth wrote:

Can you reliably boot the multi-user.target (2nd link below) w/ "nomodeset"?

Recent two or three bootings were successful, so maybe in the coming days I'll give this also a try.

seth wrote:

I hope windows fast start is (still) disabled? (3rd link below)

Zrzut-ekranu-2023-12-17-185636.png

"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."

MSI Raider GE78HX 13VI-032PL

Offline

#10 2023-12-17 21:11:20

seth
Member
Registered: 2012-09-03
Posts: 51,582

Re: Arch is not booting, while Windows 11 has no issues.

gru 17 17:20:03 MSI-Arch dhcpcd[1022]: wlan0: waiting for carrier
gru 17 17:20:03 MSI-Arch NetworkManager[1067]: <info>  [1702830003.2553] dhcp: init: Using DHCP client 'internal'

Colliding network managing services.

gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
gru 17 17:20:03 MSI-Arch kernel: iwlwifi 0000:00:14.3: Start IWL Error Log Dump:

iwlwifi firmware crash.

Disable dhcpcd, on a limb, move iwlwifi and iwlmvm into the initramfs to give them a head-start over wpa_supplicant.
But I'm not sold that this is a network related issue.

Don't know how to do this while my Linux is unresponsive during boot.

Iff you can reboot w/ the magic sysrq, there's a chance the journal of  the previous boot (-b -1) will be preserved.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#11 2023-12-17 22:11:37

Zibi1981
Member
From: Poland
Registered: 2008-01-31
Posts: 644

Re: Arch is not booting, while Windows 11 has no issues.

seth wrote:

Disable dhcpcd,

Done

$ sudo systemctl status dhcpcd.service
○ dhcpcd.service - DHCP/ IPv4LL/ IPv6RA/ DHCPv6 client on all interfaces
     Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; disabled; preset: disabled)
     Active: inactive (dead)
seth wrote:

on a limb, move iwlwifi and iwlmvm into the initramfs to give them a head-start over wpa_supplicant.
But I'm not sold that this is a network related issue.

It is not, as I'm still having no-boot issues, but adding iwlmvm and iwlwifi resulted in missing WiFi capability completely from my system (KDE showed crossed out WiFi icon), so I had to revert this back.

seth wrote:

Iff you can reboot w/ the magic sysrq, there's a chance the journal of  the previous boot (-b -1) will be preserved.

After an unsuccessful boot:

$ sudo journalctl -b -1
Specifying boot ID or boot offset has no effect, no persistent journal was found.

"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."

MSI Raider GE78HX 13VI-032PL

Offline

#12 2023-12-17 22:27:06

seth
Member
Registered: 2012-09-03
Posts: 51,582

Re: Arch is not booting, while Windows 11 has no issues.

Specifying boot ID or boot offset has no effect, no persistent journal was found.

Do you have *any* older journals?

tail -n10000 /etc/systemd/journald.conf /etc/systemd/journald.conf*/*

Does the magic sysrq work (to reboot the system w/o the power button)?
Did you add https://wiki.archlinux.org/title/Genera … l_messages

seth wrote:

Can you reliably boot the multi-user.target (2nd link below) w/ "nomodeset"?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#13 2023-12-18 22:07:22

Zibi1981
Member
From: Poland
Registered: 2008-01-31
Posts: 644

Re: Arch is not booting, while Windows 11 has no issues.

seth wrote:

Do you have *any* older journals?

tail -n10000 /etc/systemd/journald.conf /etc/systemd/journald.conf*/*
# LC_ALL=C tail -n10000 /etc/systemd/journald.conf /etc/systemd/journald.conf*/*
==> /etc/systemd/journald.conf <==
#  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.
#
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file (or a copy of it placed in
# /etc/ if the original file is shipped in /usr/), or by creating "drop-ins" in
# the /etc/systemd/journald.conf.d/ directory. The latter is generally
# recommended. Defaults can be restored by simply deleting the main
# configuration file and all drop-ins located in /etc/.
#
# Use 'systemd-analyze cat-config systemd/journald.conf' to display the full config.
#
# See journald.conf(5) for details.

[Journal]
#Storage=auto
#Compress=yes
#Seal=yes
#SplitMode=uid
#SyncIntervalSec=5m
#RateLimitIntervalSec=30s
#RateLimitBurst=10000
#SystemMaxUse=
#SystemKeepFree=
#SystemMaxFileSize=
#SystemMaxFiles=100
#RuntimeMaxUse=
#RuntimeKeepFree=
#RuntimeMaxFileSize=
#RuntimeMaxFiles=100
#MaxRetentionSec=
#MaxFileSec=1month
#ForwardToSyslog=no
#ForwardToKMsg=no
#ForwardToConsole=no
#ForwardToWall=yes
#TTYPath=/dev/console
#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
#MaxLevelWall=emerg
#LineMax=48K
#ReadKMsg=yes
#Audit=yes
tail: cannot open '/etc/systemd/journald.conf*/*' for reading: No such file or directory
seth wrote:

Does the magic sysrq work (to reboot the system w/o the power button)?

Yes, after I added it to the kernel parameters in GRUB config.

seth wrote:

Yes, it now spits much more information.

seth wrote:

Can you reliably boot the multi-user.target (2nd link below) w/ "nomodeset"?

I haven't tried that one yet. What this will show?

"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."

MSI Raider GE78HX 13VI-032PL

Offline

#14 2023-12-18 22:11:16

seth
Member
Registered: 2012-09-03
Posts: 51,582

Re: Arch is not booting, while Windows 11 has no issues.

seth wrote:

Do you have *any* older journals?

journald.conf is stock (all commented)

Yes, it now spits much more information.

If it spits more info before stalling, that's probably gonna be interesting.

I haven't tried that one yet. What this will show?

If the multi-user.target boots, it's only your graphical.target (DM, display server); if it only works w/ nomodeset, it's the kernels graphics stack.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#15 2023-12-19 19:37:17

Zibi1981
Member
From: Poland
Registered: 2008-01-31
Posts: 644

Re: Arch is not booting, while Windows 11 has no issues.

seth wrote:

journald.conf is stock (all commented)

Should I uncomment the first two lines? I've never edited that file.

seth wrote:

If it spits more info before stalling, that's probably gonna be interesting.

Well, last couple bootings were successful. It seems to be a quite random issue.

Last edited by Zibi1981 (2023-12-19 19:37:58)

"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."

MSI Raider GE78HX 13VI-032PL

Offline

#16 2023-12-19 19:59:54

seth
Member
Registered: 2012-09-03
Posts: 51,582

Re: Arch is not booting, while Windows 11 has no issues.

Should I uncomment the first two lines?

No.

t seems to be a quite random issue.

Cold/warm boot issue? Literal power-off time?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#17 2023-12-19 23:56:23

Zibi1981
Member
From: Poland
Registered: 2008-01-31
Posts: 644

Re: Arch is not booting, while Windows 11 has no issues.

seth wrote:

Should I uncomment the first two lines?

No.

???

seth wrote:

Cold/warm boot issue? Literal power-off time?

Maybe, not sure. Sometimes I think it is more common when I boot Arch as first system in a while, but it's not a rule.

"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."

MSI Raider GE78HX 13VI-032PL

Offline

#18 2023-12-20 09:03:33

seth
Member
Registered: 2012-09-03
Posts: 51,582

Re: Arch is not booting, while Windows 11 has no issues.

Yo don't have to uncomment anything there, the defaults are preserving journals in permanent storage.
You could force "Storage=persistent", https://man.archlinux.org/man/journald. … en#OPTIONS

Are there files in /var/log/journal ?
Do you mount /var/log on a tmpfs?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#19 2023-12-20 09:14:54

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

Re: Arch is not booting, while Windows 11 has no issues.

Similar case as https://bbs.archlinux.org/viewtopic.php?id=285733 ?

Last edited by V1del (2023-12-20 09:15:23)

Offline

#20 2023-12-20 21:39:02

Zibi1981
Member
From: Poland
Registered: 2008-01-31
Posts: 644

Re: Arch is not booting, while Windows 11 has no issues.

seth wrote:

Are there files in /var/log/journal ?

The folder is empty.

seth wrote:

Do you mount /var/log on a tmpfs?

Nope, only those three:

# SSD tweak
tmpfs   /tmp       tmpfs   defaults,noatime,mode=1777   0  0
tmpfs   /var/spool tmpfs   defaults,noatime,mode=1777   0  0
tmpfs   /var/tmp   tmpfs   defaults,noatime,mode=1777   0  0
V1del wrote:

I don't think so.

Last edited by Zibi1981 (2023-12-20 21:39:19)

"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."

MSI Raider GE78HX 13VI-032PL

Offline

#21 2023-12-20 21:56:20

seth
Member
Registered: 2012-09-03
Posts: 51,582

Re: Arch is not booting, while Windows 11 has no issues.

systemctl status systemd-journald

Do you have otherwise issues w/ the FS or nvme, eg. stalled shutdowns that you terminate w/ the power button etc.?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#22 2023-12-21 22:22:40

Zibi1981
Member
From: Poland
Registered: 2008-01-31
Posts: 644

Re: Arch is not booting, while Windows 11 has no issues.

seth wrote:
systemctl status systemd-journald
$ systemctl status systemd-journald
● systemd-journald.service - Journal Service
     Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
     Active: active (running) since Thu 2023-12-21 23:09:16 CET; 7min ago
TriggeredBy: ● systemd-journald-dev-log.socket
             ● systemd-journald.socket
             ○ systemd-journald-audit.socket
       Docs: man:systemd-journald.service(8)
             man:journald.conf(5)
   Main PID: 529 (systemd-journal)
     Status: "Processing requests..."
      Tasks: 1 (limit: 76651)
   FD Store: 52 (limit: 4224)
     Memory: 10.9M (peak: 12.0M)
        CPU: 330ms
     CGroup: /system.slice/systemd-journald.service
             └─529 /usr/lib/systemd/systemd-journald

gru 21 23:09:16 MSI-Arch systemd-journald[529]: Collecting audit messages is disabled.
gru 21 23:09:16 MSI-Arch systemd-journald[529]: Journal started
gru 21 23:09:16 MSI-Arch systemd-journald[529]: Runtime Journal (/run/log/journal/bdcae86eee5f4008a190f524793fd81f) is 8.0M, max 3.1G, 3.1G free.
gru 21 23:09:16 MSI-Arch systemd-journald[529]: Runtime Journal (/run/log/journal/bdcae86eee5f4008a190f524793fd81f) is 8.0M, max 3.1G, 3.1G free.
gru 21 23:09:16 MSI-Arch systemd-journald[529]: Received client request to flush runtime journal.
Notice: journal has been rotated since unit was started, output may be incomplete.
seth wrote:

Do you have otherwise issues w/ the FS or nvme, eg. stalled shutdowns that you terminate w/ the power button etc.?

Well, sometimes I experience something that might be a "stalled shutdown". Usually after using Arch for a couple hours the shutdown process seems to be unable to complete and I have to do a hard reset or make us os SysRq functions. Nonetheless I haven't experienced any failed bootings after the last systemd update. Not sure if it's relevant.

$ LC_ALL=C pacman -Qi systemd
Name            : systemd
Version         : 255.1-1
Description     : system and service manager
Architecture    : x86_64
URL             : https://www.github.com/systemd/systemd
Licenses        : GPL2  LGPL2.1
Groups          : None
Provides        : nss-myhostname  systemd-tools=255.1  udev=255.1
Depends On      : acl  libacl.so=1-64  bash  cryptsetup  libcryptsetup.so=12-64  dbus  kbd  kmod  libkmod.so=2-64  hwdata  libcap  libcap.so=2-64  libgcrypt
                  libxcrypt  libcrypt.so=2-64  systemd-libs  libidn2  lz4  pam  libelf  libseccomp  libseccomp.so=2-64  util-linux  libblkid.so=1-64
                  libmount.so=1-64  xz  pcre2  audit  libaudit.so=1-64  openssl  libcrypto.so=3-64  libssl.so=3-64
Optional Deps   : libmicrohttpd: systemd-journal-gatewayd and systemd-journal-remote
                  quota-tools: kernel-level quota management
                  systemd-sysvcompat: symlink package to provide sysvinit binaries [installed]
                  systemd-ukify: combine kernel and initrd into a signed Unified Kernel Image
                  polkit: allow administration as unprivileged user [installed]
                  curl: systemd-journal-upload, machinectl pull-tar and pull-raw [installed]
                  gnutls: systemd-journal-gatewayd and systemd-journal-remote [installed]
                  qrencode: show QR codes [installed]
                  iptables: firewall features [installed]
                  libbpf: support BPF programs [installed]
                  libpwquality: check password quality
                  libfido2: unlocking LUKS2 volumes with FIDO2 token [installed]
                  libp11-kit: support PKCS#11 [installed]
                  tpm2-tss: unlocking LUKS2 volumes with TPM2 [installed]
Required By     : accountsservice  at-spi2-core  base  bluez-utils  bolt  cloud-init  colord  cups  flatpak  gcr-4  gnome-desktop-common  intel-gpu-tools
                  kjournald  libcolord  libgudev  libinput  libmbim  libpulse  mdadm  media-player-info  mkinitcpio  modemmanager  polkit
                  profile-sync-daemon  python-pyudev  rtkit  systemd-resolvconf  systemd-sysvcompat  upower  vte3  vulkan-intel  xdg-desktop-portal
                  xdg-user-dirs
Optional For    : None
Conflicts With  : nss-myhostname  systemd-tools  udev
Replaces        : nss-myhostname  systemd-tools  udev
Installed Size  : 31.26 MiB
Packager        : Christian Hesse <eworm@archlinux.org>
Build Date      : Sun Dec 17 10:49:38 2023
Install Date    : Wed Dec 20 11:21:06 2023
Install Reason  : Installed as a dependency for another package
Install Script  : Yes
Validated By    : Signature

"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."

MSI Raider GE78HX 13VI-032PL

Offline

#23 2023-12-21 22:35:59

seth
Member
Registered: 2012-09-03
Posts: 51,582

Re: Arch is not booting, while Windows 11 has no issues.

Notice: journal has been rotated since unit was started, output may be incomplete.

Probably https://github.com/systemd/systemd/issues/30092 ?

sudo journalctl | grep 'Journal file uses a different sequence number ID, rotating.'

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#24 2023-12-21 22:49:30

Zibi1981
Member
From: Poland
Registered: 2008-01-31
Posts: 644

Re: Arch is not booting, while Windows 11 has no issues.

seth wrote:
sudo journalctl | grep 'Journal file uses a different sequence number ID, rotating.'

I'm not getting any output to this command.

"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."

MSI Raider GE78HX 13VI-032PL

Offline

#25 2023-12-30 12:57:47

Zibi1981
Member
From: Poland
Registered: 2008-01-31
Posts: 644

Re: Arch is not booting, while Windows 11 has no issues.

I guess I have to reinstall Arch after all...

20231230-132743.jpg

In this state event the keyboard isn't working, but when I try to boot from USB flashed Arch ISO

20231230-134650.jpg

Any ideas?

"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."

MSI Raider GE78HX 13VI-032PL

Offline

Pages: 1 2

Board footer

Powered by FluxBB