Discussion, talk and tips
https://forum.puppylinux.com/
12Nov24. Withdrawn. Would be ok if fix below used, but also has 'no firmware rolldown' issue.
09Nov24. This kernel has a spectre v2 vulnerability (shouldn't be catastrophic). Sorry, I missed it.
Good reason for using major distro kernels. There is a fix, but I've made adjusted kernels now.
Usrmerge structure adjusted and run sucessfully using overlayfs in my frugal LXDE'd NoblePup64-low install on the Fujitsu S761 laptop (2nd gen i5, i915 driven graphics, Atheros wifi card). Clean boot and dmesg, good idle resource use, normal lidsuspend. modesetting driver chosen by default at boot, intel available via xorgwizard. Quite minor performance difference (maybe 10% edge for intel) seen between the two either in glxgears FPS or in daily use. Pretty subtle on this hardware.
Thanks,
Later, also tested in my VoidPup64 install (most recent build) on the above hardware. also with LXDE. VoidPup64 is not usrmerge so used OOTB. punionfs=overlay passed as a kernel parameter just for clarity for me. Clean boot, excellent idle resource use, clean dmesg, Overall performance seems snappy and so far in testing on this somewhat problematic hardware wrt lidsuspend I was able to pull my patch in suspend.sh. Continued testing will show if that holds up. Hope so.
sadly error tmp bootinit dump on fossapup
@finit12
Did you 'save' the error logs?
At the bottom it tells you that you can save the error log by typing in debugsave.
Then it will ask you which partition to save it in.
Then once you have done this power off.
You can switch back to your original kernel to get back to desktop and post the error logs here.
BTW ... Which Fossapup? 95 or 96v-x-CE?
@finit12 ,
I just swapped the 6.11.5 kernel into my frugal install (to SSD) of fossapup64-small version 5 (a pruned and polished 9.5 by ozsouth). I hid my ydrive so it was a pristine boot test. Just unpacked the kernel tar.gz and renamed the two files to vmlinuz and zdrv_fossapup64_9.5.sfs and put them in the boot directory for that pup.
First a fail, much like you describe. OOPS, I was passing punionfs=aufs as a kernel parameter and this kernel is overlayfs only. Are you passing that kernel parameter?
Pulled that kermel parameter from the boot stanza and got a nice clean boot. Posting from that boot now using the current Brave portable. No issues noted at all.
Just unhid my ydrv and rebooted. Nothing else touched or tweaked. Nice clean boot into the LXDE'd pup. The fs tickler I run says at boot (of course) that the fs is overlay.,
Clean dmesg, good idle resource use, all portables etc working.
@finit12 - as Marv said, this is Overlayfs-Only. If you have fossapup64-9.5 original, you can't use this kernel, as it requires Aufs. My 6.6.58 kernel would suit that pup, as it is Aufs/Overlayfs compatible.
If you got my latest fossapup64-small (or -mid) or rockedge's fossapup64-9.6CE4, you could use this kernel, & whilst specifying punionfs=overlay in grub linux line is advisable, those puppies should pick up the fact that an overlayfs-only kernel is being used - just as long as you don't specify aufs there.