A note on the ucode loading: There is not yet ucode for spectre mitigation for the 2nd gen i5 in the Jan 8 Intel update; but there is newer code than in my CPU so I can check the original microcode, force a late update (intel-ucode folder added to /lib/firmware) with

Code:

echo 1 > /sys/devices/system/cpu/microcode/reload

and see that the microcode has been updated. Once satisfied with the setup, having the relevant intel-ucode file in /lib/firmware and the code line above in rc.local will ensure late loading on boot. I'm more used to doing it that way (late) and updating the ucode pkg. is simpler for me. As of now (and maybe forever) there is no mitigation code for any of the 3 classes of intel CPUs I run. See here for an explanation of early and late ucode loading: http://www.murga-linux.com/puppy/viewtopic.php?p=980149#980149

Thanks,

Edit: Later, kernel swapped into pups listed above. All good.
Edit2: Later, above done on core 2 duo laptop and Bay Trail desktop. All OK there also. Link to jamesbonds explanation of early and late loading added.
Edit3: Later, confirmed use of 'force' line in rc.local on boot in all & added note on that._________________Pups currently in kennel LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64, and LxPupBB for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS. Now tazpup for puzzles

Apply the delta to the LxPupSc-18.01T-k64.iso to produce LxPupSc-18.01+6-k64-overlayfs.iso

Do a frugal install but in addition to the usual files copy 2 extra files into the frugal directory:
BOOT_SPECS
overlay_mods.sfs

Make sure your kernel boot line in for example menu.lst contains both pdrv= and psubdir= parameters. e.g.

Code:

kernel /overlayfs/vmlinuz pmedia=atahd pdrv=sda4 psubdir=overlayfs

where my frugal directory is overlayfs and resides on partition sda4

Note that sfs handling and shutdown are different to aufs based pups. Also initial timezone is set to Pacific-Kiritimati as recommended by @01micko.

Quote:

8. Reboot to enjoy the new working puppy.
To modify the list of extra sfs's that "init" tries to mount, use "Extra-SFS manager".
To modify the list of system sfs's that "init" tries to mount, use "System-SFS manager".
To change some of the boot characteristics, use "Pfix parameter manager".
To change "save" to a different mechanism or change the location of the savefolder, use "Saveconfig".

Quote:

What needs to be tested:

1) That it does successfully boot current woof-ce based Puppies, i.e. they boot to the desktop.

2) Are there any Puppy utilities, other than the patched ones included in "overlay_mods.sfs", that are broken by this "init"?
Please don't bother telling me about "sfs_load" or "snapmergepuppy", these are incompatible with overlayfs.

3) That the booted Puppies work the same as when they are booted with their release "init".
While I have done many, many boots as part of this project, I haven't sustainably used the resultant Puppy.
I plan to setup a Puppy I can use as my daily workhorse and boot it with this "init".

Strange, you are using a 32-bit OS but with a 64-bit kernel? I think this is the first time anyone tried to release something like this in a puppy (?), surprised it works. Wonder if this will work on my Pentium M laptop or I'll get something like this:

Strange, you are using a 32-bit OS but with a 64-bit kernel? I think this is the first time anyone tried to release something like this in a puppy (?), surprised it works. Wonder if this will work on my Pentium M laptop or I'll get something like this:

Might try it later, unless someone beats me to it.

The use of a 64-bit kernel in LxPupSc goes back to here: http://www.murga-linux.com/puppy/viewtopic.php?p=962510#962510. I've also sucessfully used the 64-bit LxPupSc kernels in a number of other pups since then, both 32-bit and 64-bit. And yep, it's only for true 64-bit CPUs so the Pentium Ms won't run it._________________Pups currently in kennel LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64, and LxPupBB for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS. Now tazpup for puzzles

+4T updated to +5T on the i5 Fujitsu S761. md5sum correct, no issues noted, using it as the main daily with your Slimjet-as-spot SFS onboard. Since mesa changed, I looked at video performance and benchmarks vs +4T since I'd just done a set and saw no differences. Kernel 4.14.14 (& 4.9.77) should have retpoline patches backported so I wanted as close to an apples-to- apples comp as I could get for when that shows up. Not testing the overlayFS fork as I use SFS-load-on-the-fly and snapmerge a LOT.

Cheers,

Edit: networked HP4500 printer continues to print fine. Doing PDF taxcrap _________________Pups currently in kennel LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64, and LxPupBB for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS. Now tazpup for puzzles

+5 (original upload) savefile scrubbed and updated to +6. md5sum correct, SNS connection, video, sound, lidsuspend, printing all ok on S761 i5 laptop. CPU & memory use at idle unchanged. No CPU race condition seen loading and using LibreOffice 5.3.7. Original +5 gave 36% on this hardware. Looking at the 4.14.14 kernel mostly. No ucode from intel for this i5 so no change on that front. The retpoline patches show up as enabled in the kernel but for full support it requires compiling with GCC compiler 8.0, probably also backported to 7.3. Those compilers may also change the Spectre 1 mitigation. FWIW the output of the spectre-meltdown-checker script is attached.

Other than chasing intels tail along with the rest of the world, it seems a happy LxSc puppy.

Edit: Using glxgears, CPU cryptohash, and FPU raytracing I see no measurable change in cryptohash or raytracing adding retpoline to kpti and a 5% increase in glxgears FPS. All pretty near noise and well less than pup-to-pup differences on this same hardware.

_________________Pups currently in kennel LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64, and LxPupBB for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS. Now tazpup for puzzles

The retpoline patches show up as enabled in the kernel but for full support it requires compiling with GCC compiler 8.0, probably also backported to 7.3. Those compilers may also change the Spectre 1 mitigation. FWIW the output of the spectre-meltdown-checker script is attached.

Hi Marv

I'm struggling to identify a 64-bit puppy with GCC-7...... All seem to have GCC-4 or GCC-5 (i.e. Fatdog, Slacko64 and XenialPup64) (Pyro64 has GCC-6.3.0 I think)......I'm currently compiling with Slacko64 which provides GCC-5.3.0 in its devx.

LxPupSc of course has GCC-7 but is 32-bit so no good for kernel compiling....

I have done a kernel compile using Porteus-v4.0-RC1 which does have the GCC-7 compiler - mainly to see if it changed the kernel size (which it didn't). Sadly I've since deleted it.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum