LxPupSc: Woof-CE, Slackware-Current, LXDE build 13-Jun-2020

[Marv]

Peebee,
Updated a couple of frugal installs on the Pentium M laptop. One from 17.02.22T and one from 17.02.1T. Both the 4.10.1 and the 4.4.45 kernels boot correctly and run well in all aspects except that on that hardware the 4.10.1 kernel continues to lock up on suspend and have 1/3 the FPS compared to the 4.4.45 kernel. The same behavior as seen with all of the 4.9.x kernels. Running the version with the 4.4.45 kernel now. Perfect.

Both of the savefiles involved had had several updates and I was able to replicate, understand, and solve the lockup-on-update issue that mavrothal and I saw. The key is at having done at least one update prior to the 17.02.23T update and the files that rc.update adds into the savefile at each update. I'll PM you with the details.

Cheers,

[peebee]

Re-uploaded 4-mar-17

LxPupSc-17.03.1T is a 32-bit pae woof-ce 'testing' branch build

LxPupSc-17.03.1T.iso {devx} - does not include kernel sources or headers {kernel 4.10.1-lxpup sources}
iso md5 = f9a3f4003bfd3aa1b6cf3904551f6c7f

Delta is available

- kernel 4.10.1 (alternative kernel 4.4.52 also available)
- Made from Slackware-14.2/current as of Tue Feb 28 23:51:55 UTC 2017
- BUILD_FROM_WOOF='testing;edcbae2;2017-02-26 08:24:04 +0200' with patches
- web browser in adrv is light-48.0
- firmware is in fdrv
- alternative fall-back xorg is in ydrv (no need to install unless needed)

Woof-CE build repository is: http://smokey01.com/peebee/slackocurrent/

Chromium, Firefox, Opera, Palemoon and Seamonkey are in the repository and installable via Internet -> Get Web Browser

The versions of the browsers as of 8-mar-2017 with their md5sums are:

chromium-56.0.2924.87+pepper_24.0.0.221 :e04ab8a7ffd000f2534dbd3e9add39b9

firefox-45.8.0esr :0fbab8e715e01e5c4171e27ba783ce6e

opera-stable_43.0.2442.1144_i386 :c7f11979cf02947bcdf6e427bb79c483

palemoon-27.1.2 :adf163e2d3ee43ecb04e8c3fa5f21966

seamonkey-2.46 :a7e8216ba4821129798b80a16d459b67

[Marv]

Delta downloaded and applied. md5sum of generated iso correct. Updated 17.02.23T install (savefile based) on the core 2 duo laptop so far to 17.03.1T. Update went normally, savefile checked after reboot (copy made and mounted to check) and is clean wrt the relevant system files as it was before. PM sent about possible savefile/savefolder clarification...

cheers,

[mavrothal]

There is a problem booting 17.03.1 with savefolders that have been previously upgraded.

The boot sequence will freeze early in its sequence.

Actually the boot process goes on in the background fine and the files update OK.
It would appear that the console output freezes at the init switch root step (but keyboard is live) and X never starts after the update has finished in the background.
Is a strange problem
I would first think the kernel. The problem first appear from 4.9.9 to 4.9.12. You may want to try 4.9.9 if you have it handy.
Also which was the woof commit for LxPupSc-17.02.22T ?

[Marv]

@mavrothal - I just replicated the freeze a few more times. I used a 17.01.26 savefile that had the above referenced system files in it and updated to 17.02.23T as that has the original rc.update. The kernels I used were the stock 17.02.23T kernel and the 'alternative' 4.4.45 kernel. In both cases the boot froze at the same line as previously. Removing the 'system' files from the save file gave a normal completed update and boot for both kernels.

@peebee - To clean a savefile I either boot from another pup on the computer or make a copy of the savefile I want to clean/check in the same boot directory as the original. Either way, it must not be the savefile currently in use by the system. Then, mount it (singleclick in LxPupSc), then open current folder in terminal (in Tools in PCmanFM) and run the cleaner script. I keep one-off ragtag stuff like that in /root/My-applications/bin as it's in the system path but doesn't muck up the main dirs. When I've had a look at the rest of the savefile I then unmount it and if I remember run e2fsck on it. The nice thing about making a copy is that you can rename it to incorporate the number you are updating to, replace the SFS files, initrd.gz and vmlinuz with the new ones, reboot and choose the new savefile and have the old one as a fallback.

[mavrothal]

@mavrothal - I just replicated the freeze a few more times. I used a 17.01.26 savefile that had the above referenced system files in it and updated to 17.02.23T as that has the original rc.update. The kernels I used were the stock 17.02.23T kernel and the 'alternative' 4.4.45 kernel. In both cases the boot froze at the same line as previously. Removing the 'system' files from the save file gave a normal completed update and boot for both kernels.

Does the 17.01.26 savefile updates OK with 17.02.21T and 17.02.22T??
It should be clear that what really "freezes" is the output to the console when the system shifts from the initrd to the layered newly constructed system. But the actual shift to the layered system and the update goes on fine in the background. Just give it a bit of time, hard shutdown, boot another puppy and check the save folder. Everything is updated.
On a fast check I did not see any issue tracing the output of init, rc.sysinit and rc.update. Did not check kernel output though. Hopefully over the WE.

Looking at woof, there is the deletion of functions4puppy4 (12 days ago - might be related) and the support for empty savefiles a in rc.update (3 weeks ago). In rc.sysinit is the firmware loading to compensate for the deletion of functions4puppy4 and the /mnt/home setup change (checked - does not appear to be the issue). In init there is a 3-weeks old change.
I think the "3 weeks ago" changes did not give any issues but have to verify that.
If we identify precisely the "break point", would easier to spot any woof culprits.

[peebee]

Also which was the woof commit for LxPupSc-17.02.22T ?

DISTRO_NAME='LxPup-Sc'
#version number of this distribution:
DISTRO_VERSION=17.02.22

BUILD_FROM_WOOF='testing;ceb7ffd;2017-02-10 01:12:08 +1000'

[mavrothal]

Also which was the woof commit for LxPupSc-17.02.22T ?

DISTRO_NAME='LxPup-Sc'
#version number of this distribution:
DISTRO_VERSION=17.02.22

BUILD_FROM_WOOF='testing;ceb7ffd;2017-02-10 01:12:08 +1000'

This was on Feb 9. There are several changes in kernel building after that.
Is the 4.4.45 kernel a new build (after Feb 9) or an older one? (just to make sure)

[peebee]

Is the 4.4.45 kernel a new build (after Feb 9) or an older one? (just to make sure)

4.4.45 has a date of 30-jan-2017 so older

the build.sh in kernel-kit has a date of 20-jan-2017

although kernel-kit had changes I don't think any of them affected the fundamentals of kernel building - they were just process and download changes....

[mavrothal]

Got it.
Is the deletion of /etc/rc.d/functions4puppy4 that is the culprit!
Is called from /bin/mount via /usr/local/pup_event/frontend_funcs(!). So mount spits and error and this freezes the console output.
Short term solution add back /etc/rc.d/functions4puppy4 (even an empty file will do!) till a proper fix is committed to woof.

[peebee]

Got it.
Is the deletion of /etc/rc.d/functions4puppy4 that is the culprit!
Is called from /bin/mount via /usr/local/pup_event/frontend_funcs . So mount spits and error and this freezes the console output.
Short term solution add back /etc/rc.d/functions4puppy4 (even an empty file will do!) till a proper fix is committed to woof.

Well done you!!

Now fixed with a new iso.

[Marv]

Great! Thank you mavrothal and peebee. ydrv downloaded and quickly tested. 17.01.27 savefile updated to both 17.02.23T and 17.03.1T, both when the 17.01.27 savefile had been previously updated (had the system files in it) and had not (no system files). All 4 updates proceded normally with the ydrv in place. Both of these updates of the previously updated 17.01.27 savefile were exactly those that failed previously.

[mavrothal]

till a proper fix is committed to woof.

It is now.
Should do for any old version and does not need the functions4puppy4 "add back" hack.

[peebee]

I've re-uploaded 17.03.1T - n.b. the new version will be the base for any interim deltas

The new md5 for the iso is f9a3f4003bfd3aa1b6cf3904551f6c7f

If you've downloaded (or made) the previous version, rename it to LxPupSc-17.03.1aT.iso and then apply the delta at:

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

then delete the 1a version - it won't be needed again.

The only changed file is the initrd.gz which now has mavrothal's init patch so should boot successfully with any savefolder / savefile upgrade.

[Billtoo]

I downloaded the new iso, md5sum matched, did a new install to the hard
drive:

System: Host: puppypc28856 Kernel: 4.10.1-lxpup-32-pae i686 (32 bit) Desktop: LXDE (Openbox 3.6.1)
Distro: LxPup-Sc 17.03.1
Machine: Device: desktop System: Compaq-Presario product: AU194AA-A2L CQ5123F serial: MXX9300M0F
Mobo: MSI model: Boston v: 1.0 BIOS: Phoenix v: 5.24 date: 06/19/2009
CPU: Dual core Pentium E5200 (-MCP-) speed/max: 1600/2500 MHz
Graphics: Card: NVIDIA GF108 [GeForce GT 430]
Display Server: X.org 1.19.1 drivers: nouveau (unloaded: modesetting,vesa)
tty size: 132x30 Advanced Data: N/A for root
Network: Card-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller driver: r8169
Card-2: D-Link System AirPlus G DWL-G122 Wireless Adapter(rev.C1) [Ralink RT2571W] driver: rt73usb
Drives: HDD Total Size: 508.1GB (11.1% used)
Weather: Conditions: 7 F (-14 C) - Partly Cloudy Time: March 4, 9:48 AM EST
Info: Processes: 171 Uptime: 1:31 Memory: 287.6/4035.3MB Client: Shell (bash) inxi: 2.3.8

I installed mkwallpaper-0.8-i686_s700.pet and
mkwallpaper-gui-2.3_32Bit.pet, also installed applications with PPM +
compiled a couple.

No problems so far.
Thanks.

[peebee]

Re-uploaded 10-mar-2017

Interim delta to LxPupSc-17.03.21T

Only change is:
Slackware Current updates of Fri Mar 10 05:41:05 UTC 2017

Firefox browsers have updates to ESR-47.8.0 and 52.0 however Firefox-52.0 has no sound (moved to pulseaudio) and other problems so 51.0.1 is still available.

[edited 12-mar-2017]

[Marv]

Running 17.03.21T for several days now on both the core 2 duo and the Pentium M laptops (4.4.45 kernel on the M). All good I'm using the 32 bit slimjet version 13.0.7.0 on SFS as my main browser. Other than the usual chrome toolbar/menu font issue I have no complaints with it and its wrapper script is much improved since the 13.0.3.0 version.

cheers,

[peebee]

LxPupSc-17.03.2T is a 32-bit pae woof-ce 'testing' branch build

LxPupSc-17.03.2T.iso {devx} - does not include kernel sources or headers {kernel 4.10.2-lxpup sources}
iso md5 = 8f77d283e345bbe7ab7e36ecd7466c31

Delta is available

- kernel 4.10.2 (alternative kernel 4.4.52 also available)
- Made from Slackware-14.2/current as of Fri Mar 10 05:41:05 UTC 2017
- BUILD_FROM_WOOF='testing;791a7b9;2017-03-11 09:09:41 +0200'
- web browser in adrv is light-48.0
- firmware is in fdrv
- alternative fall-back xorg is in ydrv (no need to install unless needed)

Woof-CE build repository is: http://smokey01.com/peebee/slackocurrent/

Chromium, Firefox, Opera, Palemoon and Seamonkey are in the repository and installable via Internet -> Get Web Browser

The versions of the browsers as of 08-mar-2017 with their md5sums are:

chromium-56.0.2924.87+pepper_24.0.0.221 :e04ab8a7ffd000f2534dbd3e9add39b9

firefox-45.8.0esr :0fbab8e715e01e5c4171e27ba783ce6e

opera-stable_43.0.2442.1144_i386 :c7f11979cf02947bcdf6e427bb79c483

palemoon-27.1.2 :adf163e2d3ee43ecb04e8c3fa5f21966

seamonkey-2.46 :a7e8216ba4821129798b80a16d459b67

[mistfire]

@Peebee

Can you help me how to upgrade Xorg completely? I heared that the lxpupsc has better touch support. Can you give me a complete Xorg package that you used on latest lxpupsc with touch support?

[peebee]

@Peebee

Can you help me how to upgrade Xorg completely? I heared that the lxpupsc has better touch support. Can you give me a complete Xorg package that you used on latest lxpupsc with touch support?

Look in LxPupSc's /root/.packages

Look in file DISTRO_PKGS_SPECS
the lines:
yes|xorg_base_new
yes|xserver_xorg

give details of xorg build

the file: woof-installed-packages
gives the versions of the components

the components are downloaded from:
z|http://www.slackware.org.uk/slackware/slackware-current
z|ftp://ftp.slackware.com/pub/slackware/slackware-current

All this is done by woof-ce