LxPupSc64 SlackwareCurrent LXDE Woof-CE build 17-Nov-24

[Clarity]

Works here too.

[Splinterina32]

how many ram i need for run this o.s lxpupsc64?

[Clarity]

It boots within 1GB on my configs. I have a swap partition on my HDD that matches my PC's RAM.

But, RAM use is dependent on my browser use,mainly.

[Marv]

Kernel bump to 5.14.8-lxpup64 from 5.14.7 in my 'experimental' LxPupSc64 21.04 +3 install. Hardware the usual i5 based Fujitsu S761. As with all the 5.14.x versions I've run on this hardware/OS combo it has no issues with resource use, no wifi connection issues, clean dmesg, good glxgears FPS running the intel_pstate schedutil governor, and no observed day-to-day issues. I'm presently running the current 64 bit Slimjet (run-as-spot, SFS) and a chromium 91 based un-googled (run-as-spot, portable) browsers on that install. That install and my minimized savefile-less LXDE'd fossapup64 share the daily driver spot (on two of the Fujitsus).

Thanks,

Update on 02-Oct-2021: That was quick! Onward to 5.14.9, both in the usual LxPupSc64 21.04 +3 per the above and in my minimized savefile-less ydrv driven fossapup64 9.5. Usual system checks and a bit of daily use fine in both. PeasyWifi really makes the kernel bumps easier, I'm using v4.6 across the board and pretty much without exception it just connects post bump just as it did pre bump.

Update as of 09-Oct-2021: Now up to 5.14.10 in both the LxPupSc64 21.04 +3 and the fossapup64 9.5 on a couple of the Fujitsu S761s. Both system level tests and daily use fine in both.

[Marv]

Updated my 21.04 install to 21.04 +4 on two Fujitsu S761s. First a pristine install with all the usual system checks done as above. No hitches or glitches noted, clean dmesg, good idle resource use, excellent glxgears FPS, SNS used for wifi connection. Once that was done I scrubbed the 21.04 savefile, swapped in the 5.14.15 kernel, and rebooted. Nice clean boot, all test parameters again fine, PWF 4.6 preserved the network connection with no fiddling, and normal daily use seems fine. Same browsers as pre-update, Slimjet 32.0.2.0 and un-googled chromium Version 91.0.4472.101, both run-as-spot. Posting from the update now, it (and a minimized fossapup64 9.5 with LXDE and no savefile install) share daily duties about 50/50.

Thanks,

[Marv]

Kernel bump to 5.15.0 from 5.14.15 on one of the i5 based Fujitsu S761s (circa 2012, legacy bios). The install is LxPupSc64 21.04 +4, Grub4Dos frugal to SSD. Initial boot uneventful, one new warning in dmesg

Code: Select all

# dmesg | grep -i warning
[    0.791597] ntfs3: Warning: Activated 64 bits per cluster. Windows does not support this

No failures seen in dmesg (as in 5.14.15). Idle resource pretty much unchanged from the install running 5.14.15 (1% and 277MB vs 1% and 261MB under 5.14.15). Lid Suspend fine, PWF 4.6 WiFi connect came through the bump intact. glxgears FPS continues to be stellar for this hardware using the intel video driver

Code: Select all

Video-Info 1.5.1 - Wed 3 Nov 2021 on LxPupSc64 21.04 - Linux 5.15.0-lxpup64 x86_64
   
  Chip description:
    2.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)  
   
  X Server: Xorg  Driver used: intel
  X.Org version: 1.20.13
    dimensions:    1366x768 pixels (361x203 millimeters)
    depth of root window:    24 planes 

and schedutil as the intel_pstate governor. I'll leave this up for now as the daily on this laptop (has a ditzy bios so I seldom reboot it - usually just run my fossapup64 install 24/7 on it and go to another laptop running LxPupSc64 if I need something I didn't put in the ydrv. I have no NTFS filesystems or windows (since Saluki v23) so I'm out of any testing on that.

Thanks,

Update on 06/11/2021: Kernel bump to 5.15.1 on the install above. Dmesg now clean, quick look at system checks and resource use, glxgears FPS, lidsuspend, and browser use seem fine.

Update on 02/12/2021: An uneventful bump to 5.15.6 per the above. All the usual checks are good and daily use seems fine. Running Slimjet 32.0.4.0 as my main browser now (packaged as an SFS). A combination of a patch to fix youtube crashes on Slimjets' part in the 32.0.4.0 release and a couple of bodges on mine to force ALSA use and disable apulse has video clips displaying correctly in the LxPupSc64 install. Still running a portable Un-Googled Version 91.0.4472.101 and MetaGer as the fallback.

Update on 11/12/2021: 5.15.7 kernel swapped into the 'Experimental' LxPupSc64 21.04 +4 install on all of the i5 based laptops (Fujitsu S761s. Yawn! I guess that's good. The 5.15.6 kernel is now in use in all of the other installs (minimized fossapup64 9.5, LxPupSc 21.04 +4, and the user LxPupSc64 21.04 +4) except the one remaining LXDE Bionic install on my wifes' S761 and the ScPup64 install I use for compiling occasionally.
Browsers remain as immediately above.

Update on 12/27/2021: Somewhat belatedly bumped the kernel in the LxPupSc64 'Experimental' install to peebees 5.15.11 kernel. Dmesg remains squeaky clean, idle resource good and basically unchanged, glxgears FPS stays excellent just under 10k. On-line multimedia ok, no CD or DVD tests yet. No change in browsers from above. I've been restarting my home filesharing server on my remaining BayTrail desktop. Using the 64b LxPup 21.04 +4 install with the 5.15.7 kernel. Gave up on samba a while back for throughput and lockup issues. A complete round robin of tests, Rsync, NFS, Lan-Share, the httpd server in busybox, forget what else. Got them all running and they were either limited or 'clunky'. Back to samba again. No more than the usual hairpulling getting the server running but the client side stunk -til I reverted to YASSM version 2.91- Working perfectly now as in days of yore. Haven't pushed on the throughput yet but glad to have it back. Sneakernet with USB3 SSDs works but is a bit too holographic.

Update on 01/10/2022: Kernel bump from 5.15.11 to 5.16.0 in my 'Experimental LxPupSc 21.04 +4 as above. Uneventful boot, squeaky clean dmesg, all other tests good. The install now has the libinput touchpad patches I've been playing around with and now -in a minute or two- Slimjet 33.0.0, a chrome v94 based bump. The screenie shows why I like the LxPupSc64 as a work platform, libinput lumps and all

Screenshot.png (289.78 KiB) Viewed 5110 times

[Marv]

Ah! Back to the stone age. Finally got the synaptics driver to control the touchpad. Libinput everything else. Working in LxPupSc64 21.04 +4 with the 5.15.7 kernel on the Fujitsu S761/S762 i5 based lappies.

My cribnotes are below, the key was coming up with a driver compiled for the Xorg in the current LxPupSc64. The version in the Slackware repos was too old and crashed X as soon as the cursor was moved. Version 1.9.1 from the fossapup64 repos matched but I had to rearrange the 64b lib structure a bit to match what Slacko wanted (Why ):

OBVIOUSLY work on an expendable savefile copy with the original readily available on boot.

Use a pet, a slightly modified xserver-xorg-input-synaptics_1.9.1-1ubuntu3_amd64 download, to reinstall the synaptics driver.

Don't touch xorg.conf.

Add 60-synaptics.conf to /etc/X11/xorg.conf.d, highest number trumps. I moved all else in there to a 'hidden' directory as none applied in my case.

install flsynclient_0.6.0_patched using the pet. Installs to /usr/bin where it has a higher priority than the 'flsynclient' link to libinput config now in /usr/local/bin. Could remove that one...

Put a startup script in /root/Startup containing flsynclient -s (.flsynclient is in /root after first run of flsynclient and can be easily edited).

Save and reboot. ctrl-alt-backspace should get you out to look at /var/logs/Xorg.0.log if necessary. My second go followed these notes and went smoothly on the ALPS smutchpad machine.

Libinput continues to handle all but the touchpad.

The pets I used are attached as examples.

Hurrah, posting from the Alps padded S762 now. Much much better acceleration and hysteresis control and no X restart needed to invoke changes.

Edited once: Meant to say libinput in line 1, typed libevent. Corrected.

[Marv]

Kernel in the above LxPupSc64 21.04 +4 install on one of my Fujitsu S761s bumped from 5.16.2 to 5.16.5. Clean boot, clean dmesg, excellent glxgears FPS, unchanged idle resource use, PWF again nicely survives the bump with no intervention. SlimJet64 33.0.0 and un-googled Version 91.0.4472.101, the last one I've gotten to run in this slackware deriv, are fine. Nothing else to report.

Code: Select all

# uname -a
Linux puppypc2965 5.16.5-lxpup64 #1 SMP PREEMPT Wed Feb 2 07:40:22 GMT 2022 x86_64 Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz GenuineIntel GNU/Linux

mitigation on this 2nd gen i5 shows:

Code: Select all

Frequency governor   : schedutil
Freq. scaling driver : intel_cpufreq

CPU Vulnerabilities:
 itlb_multihit:KVM: Mitigation: VMX unsupported
 l1tf:Mitigation: PTE Inversion
 mds:Mitigation: Clear CPU buffers; SMT vulnerable
 meltdown:Mitigation: PTI
 spec_store_bypass:Mitigation: Speculative Store Bypass disabled via prctl
 spectre_v1:Mitigation: usercopy/swapgs barriers and __user pointer sanitization
 spectre_v2:Mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
 srbds:Not affected
 tsx_async_abort:Not affected

Cheers,

[peebee]

2a072bddde8fadb95fde552f19449240 LxPupSc64-22.02+0-T.iso

is released based on Slackware64-15.0 - see post #1

There seems to be a small problem with pupevent handling so CDs/DVDs have to be played manually.

Also a bit of a problem with some flat-remix icons that the new librsvg in these builds doesn't like....

[Marv]

Updated my LxPupSc64 21.04 +4 install with the 5.16.5 kernel to 22.02 on the usual Fujitsu S761, i5 based all intel laptop.

# inxi -b
System: Host: puppypc2965 Kernel: 5.16.7-lxpup64 x86_64 (64 bit) Desktop: LXDE (Openbox 3.6.1)
Distro: LxPupSc64 22.02
Machine: Device: laptop System: FUJITSU product: LIFEBOOK S761 serial: R1Y00453
Mobo: FUJITSU model: FJNB225 UEFI [Legacy]: FUJITSU // Phoenix v: Version 1.17 date: 03/14/2012
Battery CMB1: charge: 56.8 Wh 100.0% condition: 56.8/67.0 Wh (85%)
CPU: Dual core Intel Core i5-2520M (-HT-MCP-) speed/max: 800/3200 MHz
Graphics: Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller
Display Server: X.org 1.20.14 driver: intel tty size: 134x35 Advanced Data: N/A for root
Network: Card: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) driver: ath9k
Drives: HDD Total Size: 250.1GB (27.7% used)
Info: Processes: 165 Uptime: 19 min Memory: 361.9/5779.7MB Client: Shell (bash) inxi: 2.3.8

Far less breakage than I expected. First a pristine boot. Clean, clean dmesg -no failures, usual warnings- , unchanged idle resource use and glxgear FPS, setup through SNS connection (Atheros card, direct support in kernel) fine. Than updated a scrubbed 21.04 +4 savefile to 22.02. Clean boot, PWF connection, overall look&feel, panel setups, intel_pstate governor, synaptics touchpad driver, drives on desktop, Lx-rightclicks, etc. all survived the update just fine. No auto play on CD or DVD noted, both play ok in gnome mplayer. The following in dmesg after that test:

# dmesg | grep -i fail
[ 761.950315] sr 1:0:0:0: [sr0] tag#20 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[ 761.990251] sr 1:0:0:0: [sr0] tag#21 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s

Mitigation unchanged on this hardware:

Frequency governor : schedutil
Freq. scaling driver : intel_cpufreq

CPU Vulnerabilities:
itlb_multihit:KVM: Mitigation: VMX unsupported
l1tf:Mitigation: PTE Inversion
mds:Mitigation: Clear CPU buffers; SMT vulnerable
meltdown:Mitigation: PTI
spec_store_bypass:Mitigation: Speculative Store Bypass disabled via prctl
spectre_v1:Mitigation: usercopy/swapgs barriers and __user pointer sanitization
spectre_v2:Mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
srbds:Not affected
tsx_async_abort:Not affected

I see the missing svg icons but had to go looking. None of my usuals affected.

Slimjet64 v33.0.0.0 from SFS runs, posting from it now and un-googled remains stubbornly at v91 in these slackware derivs, v98 runs well in VoidPup64 and fossapup64. Not a library thing, haven't been able to sort it.

First look looks good here,

Thanks,

Update as of 4 March 2022: Kernel bump to 5.16.12 in the 'Experimental' LxPupSc64 22.02 +2 install above. Boring is good. Clean boot, dmesg, idle resource use, glxgears FPS all good. No change from the browsers above. I'll check CD/DVD later. Sharing time with VoidPup64 RC1 as the daily.

Kernel bump on 17 March 2022: In the install immediately above, bumped the kernel from 5.16.13 (5.16.12 AUFS patched and 5.16.13 were fine) to 5.16.15. Clean boot, dmesg, unchanged idle resource use, good glxgears FPS, and a couple of test shutdowns thrown in. All seems fine. No change here in browsers at this time. Again, I'll take boring. It'll get used as my daily, timesharing with VoidPup64 22.02 +1.

Update as of 25 March 2022: Bumped the kernel from 5.16.15 to 5.17.0 in the 'Experimental' LxPup64 22.02 +2 install on two all intel intel S761 laptops. All the usual checks and light daily use show no issues so far. Still sharing the spotlight with VoidPup64 22.02 +3 on these laptops.

Update as of 30 March 2022: Kernel bump from 5.17.0 to 5.17.1 in the installs above. No changes seen in boot, shutdown, system checks or performance. Using it as the daily now -timesharing with VoidPup64-

Cheers,

[TDRR]

Hey. This Puppy looks amazing and seems like it'd perform really nicely! No trouble with drivers so far.
Unfortunately though, just installing a browser has proven very difficult. I tried downloading both the Firefox and Vivaldi SFS from the LxPup SourceForge, but neither works at all. Firefox says "/opt/firefox/firefox: no such file or directory" even if the file exists and is visible with dir and PCManFM, and even running it directly from there as ./firefox reports the same error. Practically the same issue with Vivaldi.

Installing Firefox through the package manager also doesn't work and is missing a lot of dependencies:

Code: Select all

libgdk-3
libgtk-3
libmozavutil
libmozgtk
libmozsandbox
libmozwayland

What can I do? Pale Moon works, but Firefox would be nicer to have if possible.
Also, the exact same happens in ScPup64 22.02, so sadly that's not an option either.

[peebee]

Hey. This Puppy looks amazing and seems like it'd perform really nicely! No trouble with drivers so far.
Unfortunately though, just installing a browser has proven very difficult. I tried downloading both the Firefox and Vivaldi SFS from the LxPup SourceForge, but neither works at all. Firefox says "/opt/firefox/firefox: no such file or directory" even if the file exists and is visible with dir and PCManFM, and even running it directly from there as ./firefox reports the same error. Practically the same issue with Vivaldi.

Installing Firefox through the package manager also doesn't work and is missing a lot of dependencies:

Code: Select all

libgdk-3
libgtk-3
libmozavutil
libmozgtk
libmozsandbox
libmozwayland

What can I do? Pale Moon works, but Firefox would be nicer to have if possible.
Also, the exact same happens in ScPup64 22.02, so sadly that's not an option either.

Guess?.. are you installing 32-bit sfs on a 64-bit system?

There is no Vivaldi 64-bit on Sourceforge... so you may be in the wrong place

Use the Internet -> Get Web browser menu item to get 64-bit browser sfs - Chrome, Chromium, Firefox, Palemoon

[TDRR]

Guess?.. are you installing 32-bit sfs on a 64-bit system?

There is no Vivaldi 64-bit on Sourceforge... so you may be in the wrong place

Yeah, that was it, my bad!
I'll keep testing it, thank you for the quick reply and this Pup!

[Marv]

Finally tore myself away from VoidPup to check the kernel update in LxPupSc64 22.02 +2 on a Fujitsu S761 laptop. The bump was from 5.17.1 to 5.17.3. Clean boot, Idle resource use good, dmesg clean, glxgears FPS excellent, lidsuspend and resume fine. Running Slimjet Version 34.0.1.0 (based on Chromium 98.0.4758.9) as the primary browser (run-as-spot from SFS as usual). Looks fine, I'll test shutdown and restart on this frugal install with savefile in a bit. I continue to use the synaptics driver for touchpads instead of libinput on both LxPupSc64 and VoidPup64.

Belatedly thanks,

Update on 12 May 2022: Kernel bump to 5.17.6 in the LxPupSc64 install above. Totally uneventful, all the usual system checks ok, light daily use ok also.

Update as of 18 June 2022: Kernel 5.18.0 run for a fair time in the LxPupSc64 install above, then bumped to 5.18.5 today. No issues with either system checks or daily use with either. Lid suspend good on both with no tinkering.

Update as of 24 June 2022: Kernel bumped to 5.18.6 in the LxPupSc64 install. No issues noted with system checks or normal operation. Nice fast clean boot and excellent FPS in glxgears as I've come to expect. A bonus: the current VoidPup64 runs excellently with this kernel also. Nice clean lidsuspend there with this kernel to boot

Thanks,

[charlie6]

Hi peebee,
many thanks for this LxPupSc64 !
Have got a try on the LxPupSc64-22.02+3-T.iso which md5sum matches the LxPupSc64-22.02+3-T.iso.md5.txt, running on a more than 10 years old HP2530 elitebook.
All went right except that the shutdown process seems to freeze. No message about unmounted partitions nor effective shutdown of the machine.
After a few minutes, I have had to stop the machine by pressing the on/off power switch.
Although, a pupsave has been created after a second boot up and a possibly sufficient long wait time before performing the power shutdown.
I neither did not found a fix on this forum.
Any help would be appreciated.
(sorry for my poor english)
Best regards
Charlie

[Clarity]

https://www.smokey01.com/peebee/LxPupSc64-22.02.htm is only giving me "+02". Is the +3 ISO officially available OR are we required to go back to +0 and make a +3 version?

[charlie6]

Hi Clarity,
Yes , to get +03.iso you indeed have to load both the base +0.iso version and the +03.delra from the sourceforge repo (look for the md5sum.txt file for checking the loaded .iso and .delta files).
Load both in /mnt/home where tou are sure having enough memory available. Running the +0 version, open the /mnt/home directory, and just click on the +03.delta file...and wait till it's done ! Do not forget to verify the +03.isos md5sum.
All this already described on pages bottom here https://sourceforge.net/projects/lxpup/ ... 4/updates/ (click button «click button to open updates folder»
Hope this helps.
Charlie

[peebee]

.... the shutdown process seems to freeze.

Hi @charlie6

Not sure what your problem might be...........

It may be kernel related? Are you able to try a different one? You can get 64-bit 5.18.5 from:

https://sourceforge.net/projects/lxpup/ ... /interims/

or you can get the latest 5.10 or 5.15 from:

https://github.com/puppylinux-woof-CE/w ... el-kit.yml

but you will need to be registered with GitHub to download. If this is a problem you could download the VoidPup64 iso and use the kernel within.

You will need to extract the vmlinuz**** and kernel_modules**** files and then rename them to vmlinuz and zdrv.

[peebee]

Clarification.......

+2 is the latest release (releases have even numbers)

+3 is an interim release in preparation for +4 (interims have odd numbers) and is only available as as a delta to be applied to +0

[charlie6]

.... the shutdown process seems to freeze.

Hi @charlie6

Not sure what your problem might be...........

It may be kernel related? Are you able to try a different one? You can get 64-bit 5.18.5 from:

https://sourceforge.net/projects/lxpup/ ... /interims/

or you can get the latest 5.10 or 5.15 from:

https://github.com/puppylinux-woof-CE/w ... el-kit.yml

but you will need to be registered with GitHub to download. If this is a problem you could download the VoidPup64 iso and use the kernel within.

You will need to extract the vmlinuz**** and kernel_modules**** files and then rename them to vmlinuz and zdrv.

Hi Peebee, thanks for your answer
I did not register to github and didn't try the 5.10 or 5.15 kernels (...I believe I couldn't even if I could login... I presume those kernels need to be compiled or something like that...? )
But I tried all the other suggestions without improvment.
I also installed VoidPup64 and got the same behaviour.
Thanks anyway for your time,
Charlie

[peebee]

Hi Peebee, thanks for your answer
I did not register to github and didn't try the 5.10 or 5.15 kernels (...I believe I couldn't even if I could login... I presume those kernels need to be compiled or something like that...? )
But I tried all the other suggestions without improvment.
I also installed VoidPup64 and got the same behaviour.
Thanks anyway for your time,
Charlie

The GitHub kernels are ready to use - no building required.

However the test with VoidPup64 probably rules out the kernel.

It would be good to find out what the problem is - but I can't think of what you can do to provide more evidence.....

You could try replacing /usr/bin/wmexit with a version from a Puppy that does shutdown OK to see if it is the problem. Do this on a pristine initial install with pfix=ram.

[bigpup]

charlie6,

All went right except that the shutdown process seems to freeze. No message about unmounted partitions nor effective shutdown of the machine.
After a few minutes, I have had to stop the machine by pressing the on/off power switch.

For strange issues like the one you are having, if peebee does not think a bug has gotten into +3 version.

I would first try to do a completely fresh install.
Delete the install with the issue.
If possible do a fresh format of the partition it is being installed on.
(if the format is fat32 or ntfs the file system can get fragmented. A new formatting will fix this)
Download a fresh ISO and delta.
Do a clean new install.

I have seen bad downloads and installs cause all kinds of issues.

If nothing else it would eliminate this possible cause.

[Clarity]

@peebee, although I understand your design and have been using it for several years for delta-upgrades, I wonder if you might comment on this: For example:

• If I rename the +02 ISO to +0, would the delta apply itself to it creating a new +03 ISO? Would that have a negative impact, in your opinion?

Thanks in advance, for your insights

[peebee]

• If I rename the +02 ISO to +0, would the delta apply itself to it creating a new +03 ISO? Would that have a negative impact, in your opinion?

Thanks in advance, for your insights

No - the delta can only be applied to the REAL +0 - what I do provide are reverse_updates that will produce a REAL +0 from a +2 (for example)
e.g. see
https://sourceforge.net/projects/lxpup/ ... e_updates/

[Marv]

Hi Peebee, thanks for your answer
I did not register to github and didn't try the 5.10 or 5.15 kernels (...I believe I couldn't even if I could login... I presume those kernels need to be compiled or something like that...? )
But I tried all the other suggestions without improvment.
I also installed VoidPup64 and got the same behaviour.
Thanks anyway for your time,
Charlie

@charlie6 Try the 5.18.6 kernel from here: https://sourceforge.net/projects/lxpup/ ... /interims/ I have perfect suspend and shutdown with it on my i5 based laptops. Also excellent idle resource use and glxgears FPS on both the current LxPupSc64 and VoidPup64 installs. Ya, I know hardware is hardware, but different kernels handle hardware very differently and it's a simple 'no compile' test to do.

[charlie6]

@ Marv

@charlie6 Try the 5.18.6 kernel from here: https://sourceforge.net/projects/lxpup/ ... /interims/ I have perfect suspend ...

Thanks for your suggestion ! Got it a try but no change upon shutdown.

@ Peebee,
also thanks about /usr/bin/wmexit exchange idea: I copied the one from Fossapup64 and replace the existing one into a fresh frugal install of LxPupSc64: again no change upon shutdown process.
wmexit in LxPupSc64 differs only on line 74 from the one in Fossa: extra commands in LxPupSc64:« Xwayland labwc »
line74 in wmexit/Fossa:

Code: Select all

for i in xfce4-panel lxsession lxqt-session `cat /etc/windowmanager` jwm icewm openbox X Xorg

line74 in wmexit/LxPupSc64:

Code: Select all

for i in xfce4-panel lxsession lxqt-session `cat /etc/windowmanager` jwm icewm openbox X Xorg Xwayland labwc

To notice:
in all cases, the name of the pupsave is recorded upon first shutdown even if the shutdown process does not end completely. At next bootup, that pupsave file is loaded, BUT again the first-run settings is performed as on a very first bootup (looks like those settings were not memorized).

Best regards, Charlie

[peebee]

@charlie6

Can you provide more information about how your system is configured please?

What kind of install? What kind of pupsave? where are the files located? how are the partitions formatted?

Has any version of LxPupSc64 shutdown correctly for you? Does 22.02+0 have the problem?

We cannot duplicate your problem on our systems so it must be something specific to your hardware and how you have installed Puppy.

[charlie6]

I did not register to github and didn't try the 5.10 or 5.15 kernels (...I believe I couldn't even if I could login... I presume those kernels need to be

...The GitHub kernels are ready to use - no building required....

Hi again,
now cannot succeed in trying to get kernels 5.10 or 5.15 from github...I believe I'm well registered...but cannot find any way to download something. All I could find is to download materials to compile the kernel: build.sh, config files, etc... But nothing ready to use OOTB....???
I believe I have missed something....
Charlie

[charlie6]

Hi peebee,

I did not register to github and didn't try the 5.10 or 5.15 kernels (...I believe I couldn't even if I could login... I presume those kernels need to be

...The GitHub kernels are ready to use - no building required....

Hi again,
Yesss... could download the 263Mb sized kernel-kit-output-5.10.x-x86_64.zip archive and unzip it; aftrwds from there renamed and got the
relevant fdrv_***.sfs, zdrd***.sfs and vmlinuz files. Reboot...Bootup on the previuosly created pupsave-with -kernel-5.18.6-pupsave-with-1srRunSettingsKept; and reboot again...and...it shutdowns as expected
Again many thanks
Have a nice sunday afternoon !
Charlie

[charlie6]

Hi,
just one thing ... LxPupSc64 still runs fine here on my HP elitebook 2530p with kernel 5.10.123, but cannot get a wifi connection.
I cannot find a k5.10.123 bcm4312 driver (802.11) source archive in order to compile it.
Nor a wl driver alternative.

Code: Select all

# lspci -nn -d 14e4:
02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
# 

Any idea?
Thanks in advance for any help.
Charlie