[Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

seth · 2025-11-28 16:56:39

Sorry, missed your previous post.

Attempt to revert with pacman -U 6.15.3

This is not going to work.
"-U" takes a file or url as argument, you can

pacman -U https://archive.archlinux.org/packages/l/linux/linux-6.15.3.arch1-1-x86_64.pkg.tar.zst

From the screenshots you're not booting the kernel that's installed so yes, you either forgot to mount the boot partition or are mounting a spurious boot partition.
Your "old fstab" cannot be the reason for that if you followed https://bbs.archlinux.org/viewtopic.php … 1#p2273241

I also do grub-mkconfig, which I assume is a missing step that causes the black screen. This one is wrong?

Likely. Depends on where and under what conditions you did this.
Stop. Flailing. Around!
You're creating a moving target that will be impossible to hit.

On the failing boot, from the rescue shell, run

lsblk -f; cat /proc/cmdline

and post the output so we know where we're at now.
Don't do anything else!

rebornKidz · 2026-01-11 14:24:22

I do write pacman -U 6.15.3 just to simplify the writing.
I try to tackle all at once, but it all backfires.
So sorry, sir, I am not separating the problem properly. Actually, now I was able to boot properly, but still have issues https://wiki.archlinux.org/title/KDE#Plasma as my ssdm.

seth · 2026-01-11 15:18:30

Post an updated journal and at least the outputs of

uname -a; pacman -Q linux linux-lts

rebornKidz · 2026-01-14 04:02:21

some how it's look unstable tho. now it blackscreen again, without me touching the arch environment. Will try when i got the chance, thanks Seth.

rebornKidz · 2026-01-14 07:13:23

there is no linux-lts say pacman.

Linux narayana.search 6.15.3-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 19 Jun 2025 14:41:19 +0000 x86_64 GNU/Linux
linux 6.15.3.arch1-1

i sould install the linux lts then? is it okay / possible to doing so on rescue mode?

Last edited by rebornKidz (2026-01-14 07:14:10)

seth · 2026-01-14 10:36:01

No, I just wanted to check whether you're booting an installed kernel.
So what's the status quo? You're being dropped into a rescue shell?
With what error message? (Linking a photo of your monitor is ok, don't transcribe it)

rebornKidz · 2026-01-14 11:48:14

for sure one of them is the disc check part.
the main boot process is broken, so I force restart use PC button.

confirming the fstab

Last edited by rebornKidz (2026-01-16 12:37:22)

seth · 2026-01-14 12:36:58

There's a BT error but nothing in that picture looks like major problems.
Can you boot the multi-user.target? (2nd link below)
And from there please post your complete system journal for the boot:

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

rebornKidz · 2026-01-14 17:21:37

https://0x0.st/P8mK.txt

I sould use the lts then, i want doing some work on arch T_T

seth · 2026-01-14 18:26:43

Disable iwd and systemd-networkd if you want to use networkmanager.
The colliding services alone could explain a broken network, could explain some issues w/ your DM.

But the multi-user.target obviously boots.
What is your graphical.target (GDM, SDDM, lightdm,…) and can you start it manually after booting the multi-user.target?
If not, can you still switch the VT? (ctrl+alt+f3)?
If not, setup the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) and reboot w/ sysrq+REISUB, you can then reboot into the multi-user.target and post the journal of the previous boot (w/ the bad graphical.target start)

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

rebornKidz · 2026-01-15 01:30:48

after disable it

disabling systemd-networkd but it's trigger units still active
systemd-networkd-varlink.socket and systemd-networkd.socket

it's okay to ommit?

sure i cannot use curl, got no internet access. Here is the journal log
Cannot start another VT with ctrl + alt + f3, I need to use SysRq to provide a correct/meaningful journalctl log?

I remember install and reading SDDM and plasma sir.
So ssdm it is, or should I invoke some command to be sure sir?
haven't cat the graphical.target. No, it cannot start.

The log of ssdm was yielding about locale, and sure, I was not properly setting up this one~ I tried but failed.
Do you think that one can cause the issue?

Last edited by rebornKidz (2026-01-15 09:33:55)

seth · 2026-01-15 09:36:01

https://gist.githubusercontent.com/sukr … ble-iwd.md has iwd still enabled and running next to wpa_supplicant.

Jan 15 18:01:30 narayana.search sddm-helper-start-wayland[765]: Starting Wayland process "weston --shell=kiosk" "sddm"
Jan 15 18:01:30 narayana.search sddm-helper-start-wayland[765]: Failed to start "weston --shell=kiosk": Child process set up failed: execve: No such file or directory
Jan 15 18:01:30 narayana.search sddm-helper-start-wayland[765]: SDDM was unable to start "weston --shell=kiosk"

This went wrong, you probably don't have weston installed and in doubt try to use the SDDM X1 backend.

rebornKidz · 2026-01-15 10:49:40

Yes, I don't. wdym by the SDDM X1 backend?

Ah i forgot about the iwd, now sysrq also enables but is untested.

Kindly Seth, about the locale, as a side issue.
localectl

System Locale: LANG=en-US.UTF-8
    VC Keymap: (unset)
   X11 Layout: (unset)

locale

LANG=en-US.UTF-8
LC_CTYPE="en-US.UTF-8"
LC_NUMERIC="en-US.UTF-8"
LC_TIME="en-US.UTF-8"
LC_COLLATE="en-US.UTF-8"
LC_MONETARY="en-US.UTF-8"
LC_MESSAGES="en-US.UTF-8"
LC_PAPER="en-US.UTF-8"
LC_NAME="en-US.UTF-8"
LC_ADDRESS="en-US.UTF-8"
LC_TELEPHONE="en-US.UTF-8"
LC_MEASUREMENT="en-US.UTF-8"
LC_IDENTIFICATION="en-US.UTF-8"
LC_ALL=

locale -a

C
C.utf8
POSIX

Last edited by rebornKidz (2026-01-15 12:36:19)

Scimmia · 2026-01-15 10:55:33

It was a typo, X11

seth · 2026-01-15 13:22:18

SDDM defaults to X11, see https://wiki.archlinux.org/title/SDDM#Wayland
You've not generated the US locale, https://wiki.archlinux.org/title/Locale … ng_locales

rebornKidz · 2026-01-16 05:45:43

Thanks Fellow, Seth

lasy-fail
The network still seems cause the problem. I already double check to disable systemd network and iwd. But somehow it's kinda does not do any effect.
I also enable SysRq via /etc/sysctl.d/50-default.conf , but forgot to press it on last boot to graphics.

Now i totally confuse and dont know what to do? shall I try the fallback now?

I already repeat the process of generating the locale, but the errors still persist.

localctl can be used to verify the used one then?

Last edited by rebornKidz (2026-01-16 05:51:04)

rebornKidz · 2026-01-16 09:20:21

I am boot into graphic target, then reboot with sysrec.

journal log

seth · 2026-01-16 09:48:20

SDDM now seems to work but

Jan 16 22:50:33 narayana.search systemd[1]: Started Session 1 of User plasma.
Jan 16 22:50:33 narayana.search sddm-helper[647]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: pam_sm_open_session
Jan 16 22:50:33 narayana.search sddm-helper[647]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: open_session called without kwallet5_key
Jan 16 22:50:33 narayana.search sddm-helper[647]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland"
Jan 16 22:50:33 narayana.search sddm-helper[662]: Jumping to VT 1
Jan 16 22:50:33 narayana.search sddm-helper[662]: VT mode fixed
Jan 16 22:50:33 narayana.search sddm-helper[662]: chdir( /home/plasma ) failed for user:  "plasma"
Jan 16 22:50:33 narayana.search sddm-helper[662]: verify directory exist and has sufficient permissions

You're trying to log into a user that hasn't been afforded a $HOME and the big fat DEs don't respond well to that.
https://wiki.archlinux.org/title/Users_ … management

Create the $HOME

# mkdir /home/plasma
# chown plasma:plasma /home/plasma
# chmod 700 /home/plasma

Edit, sidenote: please replace the oversized images w/ links (and optionally thumbnails) - the board as a general 250x250px limit to keep mousewheels cool.

Last edited by seth (2026-01-16 09:49:20)

rebornKidz · 2026-01-16 16:12:21

Trying the home dir, and it works. I already tried to restart, and it's still fine.

The side note, thanks. But let's keep it that way, I am in a rush to upload. Next time I should crop it on the phone first before uploading. Oh, inline css works?Oh, No
inline css, bbcode with custom height and width does not work. I have tried.

Let me ask another question: where do I miss this step?
And a more important question: is it safe to install the linux-lts and update the kernel? I want use the most recent stable one. My current state should be the fallback right if I do update the kernel?

Thanks a lot, Seth. I owe you a soul.

seth · 2026-01-16 16:33:24

You didn't issue -m w/ useradd, it's reasonable to install lts and update the regular kernel.

It's safe in that your PC will not explode (most likely) or catch fire (somewhat likely) - there may always be kernel bugs and regressions, though.
My personal advice would be to never update both kernels at the same time, update one, test it - if it's fine, you can update the other (and test that).
Otherwise you might end up w/ Murphy's law and both kernels have a fatal bug at the same time

Also make sure to not forget adding new kernels (ie. when installing other than the LTS one) to your bootloader.

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.

rebornKidz · 2026-01-16 23:16:32

useradd ? I mean the part where it was written, and I'm missing it.
Sure that's triaging concept when testing software in general, isn't?

lemme try update kernel, and will make new post if it breaks.

seth · 2026-01-17 08:56:06

https://wiki.archlinux.org/title/Instal … stallation
https://wiki.archlinux.org/title/Genera … and_groups
https://wiki.archlinux.org/title/Users_ … management

Arch Linux

#26 2025-11-28 16:56:39

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#27 2026-01-11 14:24:22

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#28 2026-01-11 15:18:30

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#29 2026-01-14 04:02:21

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#30 2026-01-14 07:13:23

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#31 2026-01-14 10:36:01

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#32 2026-01-14 11:48:14

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#33 2026-01-14 12:36:58

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#34 2026-01-14 17:21:37

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#35 2026-01-14 18:26:43

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#36 2026-01-15 01:30:48

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#37 2026-01-15 09:36:01

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#38 2026-01-15 10:49:40

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#39 2026-01-15 10:55:33

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#40 2026-01-15 13:22:18

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#41 2026-01-16 05:45:43

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#42 2026-01-16 09:20:21

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#43 2026-01-16 09:48:20

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#44 2026-01-16 16:12:21

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#45 2026-01-16 16:33:24

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#46 2026-01-16 23:16:32

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

#47 2026-01-17 08:56:06

Re: [Solved]Blackscreen after upgrade via chroot. kernel 6.12.30-1

Board footer