Well, not an oddness per se. It's more the system is shutting down at seemingly random intervals with the 6.10.3 kernel in /current.

It shows up while I am using the laptop. The GUI disappears and the shutdown scrolls up the screen, and it proceeds until the computer shuts down. Restart proceeds normally.

I am running a hybrid system -- or bastardized, if you will -- with all updates up to the most recent, 7 August, revision, with the sole exception of the 6.9.12 kernel dating from 1 August. Here in the next day or two I'll be kludging up an installation of both kernels so I can easily switch back and forth for testing and evaluation. In the meantime, though, does anybody have any suggestions? I found traces in /var/log/syslog but I haven't done anything to glark meaning from it yet.

As this seems to be a clean shutdown rather than an uncontrolled crash there might be good hope to find clues in /var/log/syslog, /var/log/messages and/or /var/log/debug.

regards Henrik

Probably so. I'll be creating a bootable USB so I can reinstall the 6.10.3 kernel then examine the logs once it stops.

This ASUS is sure keeping me from being bored.

Maybe there's a new watchdog module (I'll have to look...)? We blacklist those by default due to this exact sort of thing.

Okay. The 6.9.12 kernel worked fine. The 6.10.3 kernel gave me problems with this oddball hardware. And the 6.10.4 kernel is working fine.

/me scratches his head.

Since I couldn't mark the thread as "Overcome By Events?", I'm going to mark it as solved.

i just want to share my experience of installing Slackware-Current on ASUS Tuf A15 that I just purchased recently
I updated all the firmware from Windows (before I install Slackware on it) and then I install the latest Slackware-Current and everything worked fine afterwards
I got some issues installing GRUB at first but after few reboots, I managed to solve it and it is able to shutdown normally with latest kernel 6.10.6 installed.

to be fair, I haven't had time to test it in long period of time, but if you still have your Windows installed, try to update all the firmware first.

1 members found this post helpful.

On my A16, I have the 414 BIOS installed. The latest is 415, and ASUS has it tagged as optional. Of course they don't explain what the fixes in it are, but since the machine behaved itself with the 6.9 kernel, and the rationale is given as "optimize system performance", I think I am going to keep the BIOS/firmware update as a step to take if I have problems with the machine later.

I appreciate the thought, Willy. What do you think of your laptop?

it's working great actually, i loved the product and so far, nothing major is causing issues on my side
i documented all my work here https://slackblogs.blogspot.com/2024...ed-laptop.html

Have you tried the latest 6.10.x kernels yet?
since your CPU is newer generation, it's better to use the latest kernel to have better support

Sure did. 6.9 ran great. 6.10.<7, well, not so much. I have 6.10.7 installed now, and so far no problems.

The ridiculously long keyboard response times with Slackware64 15.0 is what actually sent me to -current. Hit a key, and start waiting for the keypress to show up. And press the next key, and wait some more. Installing it was rough. But connecting a USB keyboard made it start behaving itself. Once the kernel caught up with the hardware, I installed -current and have not looked back.

yes, i agreed that newer kernel tends to work well with modern hardware, but I never had issues with keyboard before. I'm thinking it's more like Plasma 5 still indexing in the background after fresh installation and that takes a lot of I/O cycle during process. Once it's done, you should have no issues with latency between pressing and showing in the screen.

They changed how indexing work with newer Plasma 5 in current

The slow keyboard was even during the installation. I tried OpenSUSE for a sanity check, and it did the same thing. So did GParted in the live version once it wanted interaction. That problem also took a new kernel to solve.

Ah well. It's -current; broken functions are part of the fun.

Well, not with broken key press timing