LxPupSc64 SlackwareCurrent LXDE Woof-CE build 23-Feb-24

[Marv]

Downloaded delta, iso generated, md5sum correct. LxPupSc64 +1 updated to +1d, small test USB stick (4 GB) reformatted to GPT/EXFAT using gparted. Mounted correctly, directories & files transferred to it, symlinks to them made on desktop. All seems to be working. I don't think I'd ever use it as from what I read it doesn't support internal symlinks but I can see the utility in dealing with new/dwindlecentric storage.

Thanks,

[Marv]

Kernel test of the new 6.2.0 64b in LxPupSc64 23.01 +1d. The usual hardware, Fujitsu S761, 2nd gen i5 laptop. The usual install, frugal to SSD, This pup chosen because except for my synaptics touchpad drivers, it's pretty close to stock. Almost everything of any size run portable. Savefile carefully cleaned, including a cache scrubbing before kernel swap.

Clean boot, clean dmesg, both checked for fails and warnings. Normal daily operation but I think I'm going to sit this one out as there were multiple performance fallbacks from 6.1.10:

Idle CPU use up from 5% to 7%
Idle memory use up from 227MB to 270MB
Video driver used on boot is Intel in 6.1.10, Fbuffer & mode setting in 6.2.0
It can be set to intel with xorgwizard but...

glxgears FPS down from 11,500 FPS in 6.1.10 to 6500 in 6.2 0, with either mode setting or intel driver.

Apples to apples test, repeated twice. I hadn't seen mode setting in a loong time but I also am seeing it
in jammypup64 Ai, A2, and A3 isos, there with a stock 5.15.80 kernel and with @peebee 6.1.10.

Jim

Update 02/25/2023: All clear with the kernel kit built k6.1.13 with Lxpup64 settings. Run with all the usual system checks etc. in the most recent builds of LxPupSc64, S15Pup64, VoidPup64, F96-CE_1, and with zdrv structure tweaked for 'ubuntu compatibility' and punionfs=overlay passed as a kernel parameter, in jammypup64 iso B1, an overlayfs pup. idle CPU and memory use and glxgears FPS pretty much unchanged from 6.1.10 in all. Posting from Brave portable in the install of S15pup64 with the usual LXDE ydrv and my synaptics touchpad drivers.

again, Thanks

[muggins]

Hello Peebee,

Just curious if I'm only one experiencing xlock password not working. If I set a password, reopening lid just restarts xserver, without asking for pword. S15
works OK for me, but I prefer your Lx64 series. The screenlock last worked for me with LxPupSc64-21.04.

[muggins]

Also, has anyone had success with bluetooth in LxPup64?

[peebee]

Hello Peebee,

Just curious if I'm only one experiencing xlock password not working. If I set a password, reopening lid just restarts xserver, without asking for pword. S15
works OK for me, but I prefer your Lx64 series. The screenlock last worked for me with LxPupSc64-21.04.

Try editing /etc/acpi/acpi.conf line 6 to:
#DISABLE_LOCK='yes'

[muggins]

Hello Peebee,

altering /etc/acpi/acpi.conf as you suggested didn't work, but you put me on the right path. I did a diff between suspend.sh, from directory /etc/acpi/actions,
from my current LxPupSc64_23.01, where xlock wasn't working, and same file from LxPupSc64_21.04, where xlock does work.

Altering line 61 to:

Code: Select all

#restartwm

and now it works. Cheers.

[peebee]

ebe491ee06b8cc8312417498ccdba378 LxPupSc64-23.01+4-T.iso

[mistfire]

@peebee Did you have linux kernel 6.5.x compiled?

[Marv]

Back running the most recent kernels in my LxPupSc64 installs after skipping 6.2.0 due to a couple of performance issues. Kernel version 6.5.2 fixed those and I've been running it for a bit now with no issues.

Kernel test of the new 6.6.0 64b kernel in LxPupSc64 23.01 +4 (an update from the 6.5.2 kernel on that).The usual hardware, Fujitsu S761, 2nd gen i5 laptop. The usual install, frugal to SSD, This pup chosen because except for my synaptics touchpad drivers, it's pretty close to stock. Almost everything of any size is run portable. Savefile carefully cleaned, including a cache scrubbing before kernel swap.

Clean boot, clean dmesg, both checked for fails and warnings. Idle resource use and glxgears FPS both ok now, normal daily operation and 'feel' fine. All three portable browsers (current Brave, SlimJet, and ungoogled-chromium) and my portable Sylpheed continue to run well. No CD or DVD use of note.

I have been using my savefile-less installs as my daily drivers, the robustness of them when tinkering is addictive, but my other supported users are all on LxPupSc64 at this time. Surprisingly few requests for help from them.

Still here, thanks!

Update 24 December, 2023:

Kernel testing with a bump from @peebee 6.6.1 to 6.6.8 pretty much across all my pups. Posted here because I think 'announcements' should be kept as such and because LxPupSc64 leads the pack in these tests. At any rate, same hardware as above, the LxPupSc64 23.01 +4 savefile scrubbed and checked prior to the bump.

Clean boot there, clean dmesg, good idle resource use and continued excellent glxgears FPS. Continued normal daily operation with current Brave, Slimjet, ungoogled-chromium, sylpheed, all run as portables. As usual, no CD or DVD use to report on as yet. Basically all good there so far.

Ditto for the current VoidPup64 install, a pretty traditional frugal using a savefile. Basically no changes noted from the 6.6.1 kernel.

Also run in my savefile-less LXDE'd install of @ozsouths' Fossapup64-9.5-23 with no changes in system level checks or daily operation there. I'm still running his fossapup64-9.5-less-2 with the stock 5.10.182 kernel, also a savefile-less LXDE'd install.

Onward to BookwormPup64 10.0.3. Structure adjusted to usrmerge and that savefile-less LXDE'd install booted and ran perfectly! Yes, Lidsuspend (no patches now required) and all on this hardware. A very positive outcome indeed. I'll note that over in the appropriate thread.

Thanks, Jim

[mistfire]

@peebee

Hello, could you please include meson and ninja in your lxpupsc devx? thank you

[Jasper]

@mistfire

If you need to use Ninja, you can grab the pre-compiled binary from here:

https://github.com/ninja-build/ninja/re ... -linux.zip

It needs to be placed in

/usr/bin

Also, if you need Meson you can download it and install it directly using terminal

pip install--upgrade --force-reinstall meson

[mistfire]

@Jasper

Much better if it was included in the devx by default

@peebee

Any news about kernel 6.7.x aufs-patched release?

[peebee]

@Jasper

Much better if it was included in the devx by default

@peebee

Any news about kernel 6.7.x aufs-patched release?

1. Will investigate
2. aufs-6.7 is unlikely to be available for some time

[peebee]

@peebee

Hello, could you please include meson and ninja in your lxpupsc devx? thank you

https://sourceforge.net/projects/lxpup/ ... s/download

[peebee]

@mistfire

I have done a test kernel-6.7 build using the (untested, significant) patches from TomBriden from:
https://github.com/sfjro/aufs-standalon ... 1895345977

It does boot ok but seems to have problems with my nvidia hardware so use with caution! (OK with Intel)
(Reported: https://gitlab.freedesktop.org/drm/nouveau/-/issues/310 )

https://sourceforge.net/projects/lxpup/ ... ther/test/

[peebee]

c89d6d61e6fec0a4591df156cad5c619 LxPupSc64-23.01+6-T.iso

also slightly smaller deltas from +0 & +4

see post #1

[Marv]

Downloaded full iso, md5sum check correct. Updated my +4 frugal install on the Fujitsu S761 laptop (2nd gen i5, all intel, circa 2012) to +6. The +4 install was already running the 6.6.17 kernel. The savefile was scrubbed and scrutinized prior to the update as usual.

Clean boot, wifi connection, sound, portable browsers and email all ok. No fails in dmesg, only the following warnings noted:

Code: Select all

[   34.741334] warning: `wpa_supplicant' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[  238.756817] aufs au_new_inode:465:sed[12489]: Warning: Un-notified UDBA or repeatedly renamed dir, b1, ext2, gconv-modules.cache, hi57348, i25554.

Idle resource use and glxgears FPS unchanged from +4.

I'll check CD and DVD play later, posting from Brave Version 1.62.156 run as portable in +6 now. Pretty uneventful so far and that's good. This remains my 'user' default puppy.

Thanks

[libertas]

Hi,

I still have little experience with Puppies, so maybe this is trivial, but can't find a solution to it.
I've installed LxPupSc64 to a internal hard disk in frugal mode. In this case vda2, as it's running as a KVM virtual machine.

There's an attached image that shows my config.

Screenshot_2024-03-20_22-13-44.jpg (127.39 KiB) Viewed 778 times

At a shutdown, after installing some programs, I've saved the session to a save folder LxPupSc64save-sikuli.
This folder is never loaded at boot.
What should be done for it to be loaded?
Does it need to be moved inside the LxPupSc6423.01frugal folder? I've tried it and didn't work.
Shouldn't it be recognized automatically?
Should I change any parameter of the menu.lst boot file?

As a second question: Do I need to load the firefox SFS file manually or can I load it in a more automatic way?

Thanks.

[peebee]

Hi,

I still have little experience with Puppies, so maybe this is trivial, but can't find a solution to it.
I've installed LxPupSc64 to a internal hard disk in frugal mode. In this case vda2, as it's running as a KVM virtual machine.

At a shutdown, after installing some programs, I've saved the session to a save folder LxPupSc64save-sikuli.
This folder is never loaded at boot.
What should be done for it to be loaded?
Does it need to be moved inside the LxPupSc6423.01frugal folder? I've tried it and didn't work.
Shouldn't it be recognized automatically?
Should I change any parameter of the menu.lst boot file?

As a second question: Do I need to load the firefox SFS file manually or can I load it in a more automatic way?

Thanks.

Hi - bit confused as your image shows a JWM desktop - not LXDE..... have you changed? Why?

The savefolder would normally be inside the frugal install directory......... everything else looks sensible at first glance. A saveFOLDER can only be on a Linux formatted partition - otherwise a saveFILE must be used.

Not familiar with KVM - how are the partitions formatted? Do any of the logs (dmesg or PupSysinfo) show any errors?

Once you have installed the Firefox .sfs it will be "remembered" in your savefolder and loaded on next boot BUT should also be inside the frugal install directory.

[libertas]

Hi peebee,

I changed to JWM because the change was available an JWM shows the mountable disk partitions that LXDE doesn't show, at least by default.

/dev/vda2 is a ext4 formatted partition.

I've already moved both the LxPupSc64save-sikuli directory and the firefox64-124.0-lxsc.sfs file inside the frugal directory LxPupSc6423.01frugal, as shown.

Screenshot_2024-03-21_20-33-34.jpg (67.82 KiB) Viewed 638 times

But when loading, using the first boot option, the system still begins without loading any of those.

Screenshot_2024-03-21_20-35-37.jpg (71.73 KiB) Viewed 638 times

Is there a simple way to debug why the loading of the save folder is not being done?

[libertas]

After another login, I chose the option of a save file and the script is offering this:

Screenshot_2024-03-21_21-10-17.jpg (36.1 KiB) Viewed 630 times

So, it's not offering to save inside the frugal directory as it didn't too for the save directory.

[libertas]

I can do a screen recorder video so as to show what happens.

[peebee]

Think it must be a virtualisation issue rather than specific to LxPupSc64.......
Maybe move discussion to viewforum.php?f=107
Do any other recent Pups work correctly in this environment?

@Clarity may be able to assist?

p.s. you may be better off with S15Pup64 or many others if you don't want the LXDE desktop!

[Clarity]

Hello @libertas

... At a shutdown, after installing some programs, I've saved the session to a save folder LxPupSc64save-sikuli.
This folder is never loaded at boot.
What should be done for it to be loaded?
...
Thanks.

I am going to assume, that you are continuing to use your VM.

Your session saved in "LxPupSc64save-sikuli". What is the pathname to the folder? This bit of information is always shown before Shutdown-Reboot.

AT a future start, this info will be used to steer your booting WoofCE PUP to the sessions location for PUP processing.

Here's an example.

1. I booted pristine, LxPUP64

2. I made changes during its operations

3. At shutdown, I save those changes in a folder name as "/Sessions/LxPupSc64save-sikuli" on vda2.

4. On reboot at the LxPUP64 menu for my choices, I edit the 1st choice (top line)

5. I only add a steering parameter to the linux line, then allow it to continue booting the line; namely

   Code: Select all

   psave=vda2:/Sessions/LxPupSc64save-sikuli/

LxPUP64 will continue booting, finding its session(s), to desktop

Hope this is helpful
P.S. I also use a centralized way for WoofCE session management which does NOT require you to type in a parm for PUPs to automatically find there sessions. It is a part of the PUPPY structure, so no changes when booting and saving sessions. If interested, I will add the simple step to do so.

[esos]

Should I change any parameter of the menu.lst boot file?

@libertas
Definitely you miss psave=/ boot parameter

[libertas]

Hello @libertas

... At a shutdown, after installing some programs, I've saved the session to a save folder LxPupSc64save-sikuli.
This folder is never loaded at boot.
What should be done for it to be loaded?
...
Thanks.

I am going to assume, that you are continuing to use your VM.

Yes, I can install another new one, but would like to understand what's wrong.
Puppy is wonderful, but on the other hand is so full of options that needs some time to get used to.

Your session saved in "LxPupSc64save-sikuli". What is the pathname to the folder? This bit of information is always shown before Shutdown-Reboot.

It's at the root of vda2.

AT a future start, this info will be used to steer your booting WoofCE PUP to the sessions location for PUP processing.

Here's an example.

1. I booted pristine, LxPUP64

2. I made changes during its operations

3. At shutdown, I save those changes in a folder name as "/Sessions/LxPupSc64save-sikuli" on vda2.

4. On reboot at the LxPUP64 menu for my choices, I edit the 1st choice (top line)

5. I only add a steering parameter to the linux line, then allow it to continue booting the line; namely

   Code: Select all

   psave=vda2:/Sessions/LxPupSc64save-sikuli/

LxPUP64 will continue booting, finding its session(s), to desktop

So, do we have to add manually that parameter or is automatically included?
Sorry, but I'm confused.

Right now, the boot line has:
kernel /vmlinuz pmedia=cd pfix=fsck

Hope this is helpful
P.S. I also use a centralized way for WoofCE session management which does NOT require you to type in a parm for PUPs to automatically find there sessions. It is a part of the PUPPY structure, so no changes when booting and saving sessions. If interested, I will add the simple step to do so.

Yes, please do.
Do you have a /Sessions folder for sessions of different Puppies?

[Clarity]

Forgive me as I posted an incorrect psave parm. I am correcting below
Iff, you have placed your save in the Sessions folder:
Try this boot line additions as:
kernel /vmlinuz pmedia=cd pfix=fsck psave=vda2:/Sessions/
or
linux /vmlinuz pmedia=cd pfix=fsck psave=vda2:/Sessions/

You asked

Do you have a /Sessions folder for sessions of different Puppies?

Yes! This has become a normal setup on all new PCs I rescue. I make a linux partition labeled Persistence and create a folder for keeping the sessions for ALL forum distros; it is named Sessions.

I do the same when using VMs.Thus, I treat all environments (bare-metal/VMs) alike and all sessions are "kenneled" in Sessions. An example:

BKWP64 v10.0.6(4).jpg (35.93 KiB) Viewed 315 times