Heads up on latest Kernel update 6.2.5.arch1-1

[Brtza]

Just installed latest one, no issues

CPU: 8-core AMD Ryzen 7 6800HS Creator Edition (-MT MCP-)
speed/min/max: 1985/1600/4784 MHz Kernel: 6.2.6-zen1-1-zen x86_64 Up: 0m
Mem: 2071.0/13660.8 MiB (15.2%) Storage: 953.87 GiB (5.1% used) Procs: 377
Shell: fish inxi: 3.3.25

also default Eos kernel worked fine, without issues

[freebird54]

Can’t see the new version - I guess it hasn’t made it through the add-zfs stage yet. However - running 6.2.5 without issue (all AMD system). Just another data point…

[ejm]

Update: This morning I’m now running 6.2.6-zen1-1-zen on my 2011 MacBookPro successfully… it boots (as did the 6.2.5 update) but now wifi works like a charm.

Many thanks for the super fast fix.

[Jendave]

Updated my MacBook Pro 2012 to 6.2.6. All better now.

[luisbello30]

Hi Joe, thank you…
What is the default kernel?
in neofetch I see 6.1.19-1-lts but the same thing keeps happening to me with screen lock
I’m already thinking that it’s not because of the kernel update.
it’s possible ?

[joekamprad]

default is 6.2.6 linux and linux-headers packages the main default kernel…

[joekamprad]

@luisbello30

I’m already thinking that it’s not because of the kernel update.
it’s possible ?

yea can be caused by something else sure… you could check logs … like `journalctl --since “6 minutes ago”

[His_Turdness]

My work computer updates daily, sooo that was a problem. Spent a few minutes chrooting and saved it though. Updated and then no issues.

[anarchoN3rd]

I seem to be having very different symptoms from others here. After the update all open windows instantly closed as if I’d just logged in. I rebooted and was greeted with this:

Loading Linux linux ...
Loading initial ramdisk ...
error: file `/boot/initramfs-linux.img' not found.
Press any key to continue ...

Pressing “any key” does nothing

I have zen, lts, and linux kernels and this occurs with all of them and their fallbacks.

I’ve arch-chrooted via live usb, downgraded, upgraded, dracut-rebuild and nothing has worked.

Any suggestions?

[r0ckhopper]

@anarchoN3rd

Press any key to continue ...

Sorry, couldn’t resist

[r0ckhopper]

@anarchoN3rd

Any suggestions?

This?

Error: file '/boot/initramfs-linux.img' not found

So I was pretty stupid today in that I started the update to 5.8.3-arch(?) and a few other things, but after 45+ minutes the complete bar in Discover was at 100% but not actually complete (i.e. the bar vanishes altogether), so I figured it was being buggy and the UI got stuck since it was in the state for a while so I did a physical power cycle. Now booting into the partition or using the failback option gives a: Loading Linux linux … Loading initial ramdisk … error: file ‘/boot/initramfs-li…

[joekamprad]

@anarchoN3rd

error: file /boot/initramfs-linux.img’ not found.`

is there now or still missing?

[joekamprad]

but i would suggest to move to a new thread… its not related to the topic…

[anarchoN3rd]

Thank you, I needed that.

[anarchoN3rd]

Just checked and yes, all files are there.

[joekamprad]

i have ended the day already… I woul suggest open a new thread I am sure we will get it back working.

[luisbello30]

@joekamprad

journalctl --since “6 minutes ago”

Thanks to your help I found this,

Mar 16 18:07:11 luis-vitp3400 kernel: traps: xfce4-screensav[5010] general protection fault ip:55e4306fdf71 sp:7ffc95e58b20 error:0 in xfce4-screensaver-dialog[55e4306f6000+b000]
Mar 16 18:07:11 luis-vitp3400 systemd[1]: Started Process Core Dump (PID 5053/UID 0).
Mar 16 18:07:11 luis-vitp3400 systemd-coredump[5054]: Removed old coredump core.xfce4-screensav.1000.59d62aafc2734024a06f3d22175f5c11.216492.1678738320000000.zst.
Mar 16 18:07:12 luis-vitp3400 systemd-coredump[5054]: Process 5010 (xfce4-screensav) of user 1000 dumped core.
                                                      
               Stack trace of thread 5010:
               #0  0x000055e4306fdf71 n/a (xfce4-screensaver-dialog + 0xef71)
                #1  0x00007f01baf3aafb g_main_context_dispatch (libglib-2.0.so.0 + 0x5aafb)
                #2  0x00007f01baf975d9 n/a (libglib-2.0.so.0 + 0xb75d9)
                #3  0x00007f01baf3a0cf g_main_loop_run (libglib-2.0.so.0 + 0x5a0cf)
                #4  0x00007f01bb3d8e4f gtk_main (libgtk-3.so.0 + 0x1d8e4f)
                #5  0x000055e4306f6208 n/a (xfce4-screensaver-dialog + 0x7208)
                #6  0x00007f01bad1c790 n/a (libc.so.6 + 0x23790)
                #7  0x00007f01bad1c84a __libc_start_main (libc.so.6 + 0x2384a)
                #8  0x000055e4306f62ce n/a (xfce4-screensaver-dialog + 0x72ce)

I’ll let you know when I’ve checked more
Disable screen lock while I figure out how to fix it

[joekamprad]

Xfce lock screen flashes erratically

Fixed on master by 7aeced1f, I’m glad I took care of it (it wasn’t crashing yet at that time). It’s an old error, but the update of a lib (GLib ?) must have woken it up There should be a version 4.18.0 in not too long I think. so check the git AUR build: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=xfce4-screensaver-git should include this change if you freshly build directly from git

[luisbello30]

ok perfect, I have no problem keeping it disabled for a some time, I hope version 4.18.0 comes out to update.

[luisbello30]

Ready to update xfce4-screensaver fixed “cannot login back”