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

[peebee]

Interim delta +9 to LxPupSc-17.12+9T-k64.iso

- kernel 4.14.10

- Slackware Current Fri Dec 29 23:09:14 UTC 2017

[peebee]

LxPupSc-18.01T-k64 is a 32-bit woof-ce 'testing' branch build with a 64-bit kernel (therefore only compatible with 64-bit capable processors)

LxPupSc-18.01T-k64.iso {devx} - (devx does not include kernel sources or headers) {kernel 4.14.10-lxpup64 sources}
iso md5 = 07b4f43b6bb7551360ddb5953e88a73e

Delta from 17.12T is available

- kernel 4.14.10 64-bit (alternative 32-bit kernels 3.16.x 4.4.x & 4.9.x also available - all need firmware in the fdrv)
- Made from Slackware-Current as of Fri Dec 29 23:09:14 UTC 2017
- BUILD_FROM_WOOF='testing;6ea03c27;2017-12-31 21:32:24 +0800'
- 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)

**N.B. the 64-bit kernel means that any kernel drivers have to be built in a true 64-bit system - slacko64 with the LxPupSc kernel and it's own devx is suggested but use the kernel sources above

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

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

The versions of the browsers as of 28-dec-2017 with their md5sums are:
chromium_63.0.3239.108+pepper_28.0.0.126 RUN-AS-SPOT :a58a24daf43937360f2e166918654cbc
firefox-52.5.3esr :c4c2b10ff61e03216c48043ba406db5e
palemoon-27.6.2 :f9294cfb49756fd38e01dafea323118e
seamonkey-2.49.1 :699e87b4036359bfbd396fd837b33b30

firefox-57, iron, slimjet, vivaldi and min are also available

[Marv]

Updated 17.12 +8T to 18.01T on the i5 based Fujitsu S761 laptop (I'm up to 4 of them now). Used the delta, md5sums ok, uneventful boot, quickcheck of systems, SFS browser, video, etc. seem fine, CPU at idle 0 to 1%. en keyboard on this one & I've been using the lxde volume control instead of retrovol in the tray for a bit. It calls alsamixer and does what I need. Brightness and volume keys both working OOTB on these laptops, up arrow function is normal and PrtSc calls screenshot as it should. Obviously I'm in red and orange mode at the moment I'll check a pristine later today.

# inxi -bw
System: Host: puppypc1355 Kernel: 4.14.10-lxpup64 x86_64 (64 bit)
Desktop: LXDE (Openbox 3.6.1) Distro: LxPup-Sc 18.01
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: 67.0 Wh 100.0% condition: 67.0/67.0 Wh (100%)
CPU: Dual core Intel Core i5-2520M (-HT-MCP-) speed: 2501 MHz (max)
Graphics: Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller
Display Server: X.org 1.19.6 drivers: intel (unloaded: modesetting,vesa)
tty size: 80x24 Advanced Data: N/A for root
Network: Card-1: Intel 82579LM Gigabit Network Connection (Lewisville)
driver: e1000e
Card-2: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express)
driver: ath9k
Drives: HDD Total Size: 120.0GB (11.8% used)
Weather: Conditions: -7 F (-22 C) - Clear Time: January 1, 11:30 AM CST
Info: Processes: 128 Uptime: 10 min Memory: 187.3/5802.7MB
Client: Shell (bash) inxi: 2.3.8

Thanks,

[peebee]

Interim delta +1 to LxPupSc-18.01+1T-32pae.iso

- kernel 4.14.12 32-bit pae

- Slackware Current Wed Jan 3 05:45:43 UTC 2018 including dhcpcd-7.0.0

This interim delta sees a return to a 32-bit pae kernel....

The reason: my desktop pc kernel panics on boot with the 64-bit build of 4.14.11 (but my laptop doesn't!) - one of the changes from 4.14.10 to 4.14.11 must be responsible.....

The original reason to move to the 64-bit kernel was a system crash on some laptops when a dvd was inserted - this problem seems to have "gone away" with this new 32-bit build (@Marv and anybody else - grateful for your testing).

Just for a bit of extra spice , the kernel config for the new 32-bit-pae kernel is based on BK's pyro32-0.6.1 32-bit build so testing reports are welcomed. It's also compiled with gcc-7 and is a bit smaller than previous kernels.

Slackware Current updates include:
:dhcpcd:
:e2fsprogs:
:nano:

Firefox-57.0.4 "This release contains security fixes and improvements, in particular a mitigation for a speculative execution side-channel attack ("Spectre")." is also available.

[Marv]

18.01 updated to 18.01 1T on my i5 based S761 laptop using the delta. md5sums all ok. Kaiser patches toggled and firstresults reported in the 'Slowdown' thread. Certainly OK on the i5. Kernel config has intel_pstate governor disabled which is good, schedutil governor not enabled, personally I like it but have found monitoring temps on the i5s I can pretty much just run performance when plugged in anyway. Sound, connection, video, suspend, all seem ok with one change wrt CD autoplay noted (checked because of the kernel change). Autoplay ie. starting the media handler automatically on disc insertion is no longer working. Swapping kernels.. It's not that. On a closer look the change I see occurred between 17.12.8 and 18.01 (I didn't run 17.12.9) and seems like a puppy eventmanager change. See the screenshots below. I haven't done much beyond a swap of /usr/sbin/eventmanager and that brings back the tickbox but not the function for me. A front_end change? Try autoplaying and see if it's just me. Only matters for my 'users' I'm housebreaking the newest S761 rescue and will continue to use 1T there and on my main laptop.

Cheers,

edited once to add governor information. And again to note that swapping the 4.14.11 32b kernel into LxPupSc 17.12.+8T the autoplay function works correctly in that 17.12 +8T as it did with the stock 4.14.9 64b kernel.

[peebee]

On a closer look the change I see occurred between 17.12.8 and 18.01 (I didn't run 17.12.9) and seems like a puppy eventmanager change.
A front_end change?

Thanks @Marv - 18.01 did have a new woof-ce base and there have been changes to /usr/local/pup_event/pup_event_frontend_d ....
https://github.com/puppylinux-woof-CE/w ... 27ed39dad4

Might be worth trying the 17.12 version? (later - done - see next post)
Cheers
PeeBee

[peebee]

Yes - this ydrv (false .gz) reverts /usr/local/pup_event

and when the "Auto-launch" option is selected

auto-play functionality is restored

I've put a comment onto Github....

[mistfire]

@peebee can I get your 4.14.11 32-bit kernel source code?

P.S: Can you take a look on slitaz? It uses lxde too. But the pcmanfm can detect mounted disk images. It has search file function. Also can browse and access ftp and smb (if im not wrong).

Can you figure how to make this pcmanfm functions work on lxpupsc?

[Marv]

Yes - this ydrv (false .gz) reverts /usr/local/pup_event

and when the "Auto-launch" option is selected

auto-play functionality is restored

I've put a comment onto Github....

You're faster than me.. or just awake. I just did the same swap.
Thanks,

[peebee]

@peebee can I get your 4.14.11 32-bit kernel source code?

P.S: Can you take a look on slitaz? It uses lxde too. But the pcmanfm can detect mounted disk images. It has search file function. Also can browse and access ftp and smb (if im not wrong).

Can you figure how to make this pcmanfm functions work on lxpupsc?

Hi @mistfire

4.14.12 is already available....if you mean by "source code" the .config then this is in the .iso/zdrv in /etc/modules....

Unless I'm misunderstanding, all the pcmanfm functions you mention are active in LxPupSc....I use them all the time particularly sftp and smb!!!???

Cheers
peebee

[peebee]

Interim delta +2 to LxPupSc-18.01+2T-32pae.iso

BUILD_FROM_WOOF='testing;3ff35ec2;2018-01-07 23:21:18 +0800'

incorporates a raft of changes to woof-ce's pup-event handling by wdlkmpx on github

[Marv]

+2 delta downloaded, applied, and tested on the Fujitsu S761 above, both as pristine frugal and update of stripped +1 savefile. md5sums correct, clean boots on both, autoplay of CD and DVD works correctly both on pristine with default settings and on my update. USB3 flashdrive shows up correctly on PCmanFM when hotplugged. Nice to see the 4.14.12 kernel. Maybe a few more eyeballs have seen the kpti patches.. I'll use LxPupSc +2 on the i5 as daily and push the 4.14.12 kernel to Artful and LxArtful. Current versions of those three pups are now installed on the i5 and core 2 duo laptops and the Bay Trail desktop with the 4.14.11 kernel with no issues. Samba not being used at this time. Posting from Light in the pristine install.

Thanks,

[peebee]

Interim delta +3 to LxPupSc-18.01+3T-32pae.iso

- kernel 4.14.13 32-bit pae

- BUILD_FROM_WOOF='testing;358697d4;2018-01-10 22:32:18 +0800'

- Slackware Current Tue Jan 9 00:54:19 UTC 2018

with @Marv have been investigating enabling PAGE_TABLE_ISOLATION in 32-bit kernels but so far have not found how to.....

[mistfire]

@peebee I tried to compile the kernel with CONFIG_PAGE_TABLE_ISOLATION=y parameter but that parameter was missing or got deleted when start compiling the kernel

[peebee]

@peebee I tried to compile the kernel with CONFIG_PAGE_TABLE_ISOLATION=y parameter but that parameter was missing or got deleted when start compiling the kernel

Indeed - same experience here - suspect this config option is only applicable to 64-bit???

Found at: https://www.debian.org/security/2018/dsa-4078

This specific attack has been named Meltdown and is addressed in the Linux kernel for the Intel x86-64 architecture by a patch set named Kernel Page Table Isolation, enforcing a near complete separation of the kernel and userspace address maps and preventing the attack.

[mistfire]

@peebee so it means that 32-bit linux are vulnerable to meltdown attack?

[peebee]

Back to 64-bit kernel with thanks to @Marv and to FatDog64 and @jamesbond

Interim delta +4 to LxPupSc-18.01+4T-k64.iso

- kernel 4.14.13 64-bit with CONFIG_PAGE_TABLE_ISOLATION=y

[Marv]

Got it. Delta applied, md5sum correct, installed to Fujitsu S761 laptop (2nd gen i5). Both pristine and update of scrubbed +2T savefile done and checked for kpti patches and ucode loading capability. OK on all counts. Pristine checked through timezone setup, SNS connection and firewall setup, sound, video resolution, savefile creation, and reboot. OK on all counts. I'll check CD, DVD, and other hardware later. Also swap into my Artful, LxArtful, and XFCEXenial pups. Looks good!

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: Select all

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/viewto ... 149#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.

[peebee]

CAUTION: only try this in a new frugal install!!

Updated 22-jan2018

For anybody who would like to try @gyro's new initrd approach based on overlayfs instead of aufs ......

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: Select all

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.

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".

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".

Please report any test results on @gyro's thread.

[Sailor Enceladus]

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.