Puppy Linux Discussion Forum

SUPERSEDED.

Thanks, I'll give this one a go in my bookworm64 install in a bit. I have run your recent 6.6.8 and @peebees' 6.6.8 (both usrmerge structure adjusted, punionfs=overlay used) in that bookworm64 install with no issues at all. On my hardware (Fujitsu S761 with true synaptics touchpad), the 6.6.x series kernels are indeed more troublefee wrt suspend/resume than the 6.1.x kernels so I am running one of them. I have narrowed the touchpad issues on resume down to a timing thing and worked out a minimal patch so resume can be kernel agnostic but all in all for these laptops the 6.6.x series kernel is better.

I have -but don't normally- also run bookworm64 briefly using AUFS in this non savefile system. Operation and resource use were as expected.

The great thing about my ydrv driven savefile-less installs is that they are non mission critical by design. A simple power button push is the equivalent of duct tape. Makes pushing the envelope much more fun.

OK, swapped it into my bookworm64 10.0.4 install on the mildly problematic Fujitsu S761 hardware and it boots and runs cleanly, as well as suspending and resuming with no patches required in /etc/acpi/suspend.sh. Clean dmesg, good idle resource use and glxgears FPS. As usual punionfs=overlay used on boot.

# uname -a
Linux puppypc10215 6.6.7-64oz-aoum #1 SMP Sat Dec 30 18:08:44 AEDT 2023 x86_64 GNU/Linux

Looks good, I'll use it as my daily for a bit now. One note. The symlinks in / to /usr/lib and /usr/sbin in the zdrv aren't needed as they exist in the main SFS already. I usually don't put them in when I modify a kernel to the usrmerge structure. Boots ok with them though.

Thanks,

Edited once to clarify symlinks info.

@Marv - I put the symlinks in just for completeness, as they cause no harm if already in existence. I did the same for the kernel sources (headers didn't need it). I note that the original zdrv does not have these symlinks, so yes, is unnecessary in Bookwormpup64 zdrv & most likely any usrmerge pup's zdrv. Glad it's working well for you.

@ozsouth

My understanding is that all new kernels built from Woof-CE already include the Microcode updates.

I just wanted some reassurance that this kernel included the Nov 2023 update.

Is this correct?

@Jasper - kernels have SOME mitigations, but microcode needs to be invoked. Bookwormpup & Jammypup have microcode included in the iso, but it needs to be activated. With my kernels I have a link to description of how to use early-load microcode.

@ozsouth

The reason why I asked is that I saw this in the PPM

Let me go back to your kernel files and read the instructions

@ozsouth

I can only find these files, am I missing something? Or have I simply misunderstood your earlier post?

I have used the Cpio file that I compiled previously for Nov-14-2023 and renamed it to the corresponding file

It boots up with no issue and I used the Spectre script to see if it reported any issues

@Jasper - looks good - microcode mitigation is working correctly for you.