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

Message

ozsouth · #1161 Post by **ozsouth** » Mon 24 Jun 2019, 08:42

Peebee - the 5.1.14 64 bit kernel works well with my kit. Do you have kernel sources for it?

peebee · #1162 Post by **peebee** » Mon 24 Jun 2019, 11:20

ozsouth wrote:Peebee - the 5.1.14 64 bit kernel works well with my kit. Do you have kernel sources for it?

Will shortly be:
http://www.smokey01.com/peebee/download ... xpup64.sfs

ff91b2c614fda614c3db23324fc93454

ozsouth · #1163 Post by **ozsouth** » Mon 24 Jun 2019, 12:43

Thanks Peebee - extra driver compiled, kernel in use.

peebee · #1164 Post by **peebee** » Tue 25 Jun 2019, 07:56

K5.1.15

peebee · #1165 Post by **peebee** » Fri 28 Jun 2019, 11:25

Interim to 19.06+2

see post #2

Slackware Current to Sun Jun 30 22:45:12 UTC 2019

Marv · #1166 Post by **Marv** » Fri 28 Jun 2019, 14:11

I'm up to date with with the 5.1.15 kernel on the current LxPupSc (not +1, I'll treat that as an 'experimental' as I do use lmsensors on the i5), LxPupSc64, and upupdd. Done both on the Fujitsu i5 based laptop and the Bay Trail desktop (intel J1900 CPU). All 3 current pups with that kernel are ok wrt systemic and normal use checks on both machines.

glxgears video FPS unchanged on all. I'm aware that there is no hardware 3D acceleration now in the chromium based Slimjet 23.0.6.0 but I don't see any content degradation or serious CPU overload on the little media content I do look at with Slimmie, certainly on the i5.

The i5 loads the intel ucode early with K5.1.15 and shows full mitigation exactly as it did with K5.1.14.

As of today, the Bay Trail box finds no updated ucode in the current CPIO microcode pkg so no ucode update there and mitigation is partial but on the other hand it has fewer vulns to start with.

Edit: Mitigation for the Bay Trail with this kernel is:

Code: Select all

l1tf:Not affected
mds:Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
meltdown:Mitigation: PTI
spec_store_bypass:Not affected
spectre_v1:Mitigation: __user pointer sanitization
spectre_v2:Mitigation: Full generic retpoline, STIBP: disabled, RSB filling

Thanks,

Marv · #1167 Post by **Marv** » Sat 29 Jun 2019, 00:46

Interim to 19.06+1 now installed to the Fujitsu S761, md5sums checked and fine

Code: Select all

System:    Host: puppypc4721 Kernel: 5.1.6-lxpup64 x86_64 (64 bit) Desktop: LXDE (Openbox 3.6.1)
           Distro: LxPup-Sc 19.06
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/max: 932/3200 MHz
Graphics:  Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller
           Display Server: X.org 1.20.5 drivers: intel (unloaded: modesetting,vesa) FAILED: fbdev
           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 (21.8% used)
Info:      Processes: 155 Uptime: 12 min Memory: 345.1/5794.4MB Client: Shell (bash) inxi: 2.3.8

Done both as a pristine Grub4Dos install, setup from scratch, and as an update of my 19.06 install with the 5.1.15 kernel. That is carried on a bone standard 256Mb EXT2 savefile, scrubbed and fsck.fat done prior to update. Basically all personal data is on an EXT2 data partition and symlinked back into multiple pups so the savefile stays quite slim.
Both installs were done in the sacrificial Experimental folder.

In both cases, boot, early loading of the intel microcode from a common folder per ozsouths directions, standard dmesg and system checks, video FPS, loading of the current Slimmie SFS went without a hitch. No CD/DVD/media checks yet.

On the intel hardware above, the glxgears FPS falls pretty much in line with earlier versions of LxPupSc and earlier 5.x.x kernels, as does the idle CPU use and idle memory use.

Indeed no lmsensors but ozsouths cpucurtemp32 with his sensors32 pet works well on this hardware, both in my 19.06 update (running his original version) and in the pristine install (running his v3). The link to it is: http://www.murga-linux.com/puppy/viewto ... 1130190063

Had to peek just now & check. Posting from the pristine install with rightclick, drives-on-desktop, bottom panel setup,
slimjet_lxsc_spot_23.0.6.0.sfs with external profile, SNS wifi setup, etc. I'll continue to use 19.06 +1 in the experimental box, probably switching to the 19.06 update with the 5.1.15 kernel for the look'n'feel and pre-setup printing though the fresh pristine has most of the function of that in not too much setup time.

Edit: installed lm_sensors-3.5.0-i586-1.txz to the pristine above. Made sure that symlinks were correct in /usr/lib and other files were present. log out, xwin restarts normally. WMrestart normal, reboot with save starts normally. PupSysInfo picks up temperatures under Devices>sensors normally. All seems ok at least on the intel i5 above.

ldd /usr/lib/xorg/modules/dri/nouveau_dri.so done before and after install. missing libsensors.so.5 before, nothing at all after.

Cheers,

peebee · #1168 Post by **peebee** » Mon 01 Jul 2019, 08:02

mesa problem has been fixed in Slackware Current

19.06+2 includes fix and lm_sensors

ydrv for nouveau no longer needed

peebee · #1169 Post by **peebee** » Thu 04 Jul 2019, 06:10

Kernel Release: 5.1.16-lxpup64
Build Date: Wed Jul 3 17:51:53 BST 2019
Build GCC: 9.1.0
OS Support: GNU/Linux
Architecture: x86_64
SMP Enabled: Yes

Needs firmware (e.g. in fdrv)

From Here

peebee · #1170 Post by **peebee** » Tue 09 Jul 2019, 11:36

Kernel Release: 5.2.0-lxpup64
Build Date: Tue Jul 9 10:15:51 BST 2019
Build GCC: 9.1.0
OS Support: GNU/Linux
Architecture: x86_64
SMP Enabled: Yes

Needs firmware (e.g. in fdrv)

From Here

Built with aufs 5.x-rcN until 5.2 appears

Marv · #1171 Post by **Marv** » Wed 10 Jul 2019, 01:30

Bumped my frugal Grub4Dos installs of the current LxPupSc, LxPupSc64, and upupdd from kernel 5.1.15 to Kernel Release: 5.2.0-lxpup64 on the Fujitsu S761 intel based laptop (2nd gen i5). Savefiles scrubbed and checked prior. System checks, early microcode loading and mitigation, video FPS, CPU % and mem use at idle all unchanged. No new dmesg failures or warnings to note.

Slimjet from SFS, Sylpheed, clipboard, geany, printing to brother 2170 laserjet all seem unchanged. Memory/SSD throughput unchanged.

I'll roll the dice and use one of the three as daily.

Thanks,

peebee · #1172 Post by **peebee** » Sun 14 Jul 2019, 08:23

Kernel Release: 5.2.1-lxpup64
Build Date: Sun Jul 14 07:35:24 BST 2019
Build GCC: 9.1.0
OS Support: GNU/Linux
Architecture: x86_64
SMP Enabled: Yes

Needs firmware (e.g. in fdrv)

From Here

Built with aufs 5.x-rcN until 5.2 appears

peebee · #1173 Post by **peebee** » Sun 14 Jul 2019, 10:49

14-jul-2019

Delta to 19.06+3

ISO md5 = 988f766ce6a1fed122376b09db550685 LxPupSc-19.06+3-uefi-T-k64.iso

Must be applied to: 7354341ccba39c08ece34cc2f953084e LxPupSc-19.06+0-uefi-T-k64.iso

Updates are cumulative - only the most recent needs to be applied.

ozsouth · #1174 Post by **ozsouth** » Sun 14 Jul 2019, 11:50

Peebee - did you see this http://murga-linux.com/puppy/viewtopic. ... 49#1032049
Applies to copies of ScPup64 & LxPup19.06 that I have, so I suspect others too.
Not startling, but explains why an ADDLIST item I added wasn't picked up in these, but was in Slacko64.

peebee · #1175 Post by **peebee** » Sun 14 Jul 2019, 20:21

ozsouth wrote:Peebee - did you see this http://murga-linux.com/puppy/viewtopic. ... 49#1032049
Applies to copies of ScPup64 & LxPup19.06 that I have, so I suspect others too.
Not startling, but explains why an ADDLIST item I added wasn't picked up in these, but was in Slacko64.

Thanks - I'd seen it but hadn't checked which versions of woof-ce were affected - the fix will apppear in future updates.....

davids45 · #1176 Post by **davids45** » Mon 15 Jul 2019, 01:29

G'day peebee,

Thanks for your continuing efforts with the various Pups.

I may be the only one affected as I use fairly old applications but in /usr/lib, you include a link for libpng12.so.0 to a libpng16.so.16.37.0, if I've got it right.

In each LxScPup lately, I have to replace this link with a link to point to an added libpng12.so.0.22.0 file (link in screenshot) to get Dukto, Xjigsaw and MasterPDFEditor to work.

I haven't found any included application to fail after making this new link.

Thanks again,

David S.

peebee · #1177 Post by **peebee** » Sat 20 Jul 2019, 08:52

davids45 wrote: in /usr/lib, you include a link for libpng12.so.0 to a libpng16.so.16.37.0,

Hi David

I've fixed the reason why that link was in the build - so the link will not appear in future builds. Thanks for raising.

Cheers
peebee

peebee · #1178 Post by **peebee** » Sun 21 Jul 2019, 12:55

Kernel Release: 5.2.2-lxpup64
Build Date: Sun Jul 21 10:13:21 BST 2019
Build GCC: 9.1.0
OS Support: GNU/Linux
Architecture: x86_64
SMP Enabled: Yes

Needs firmware (e.g. in fdrv)

From Here

Built with aufs 5.2

peebee · #1179 Post by **peebee** » Sun 21 Jul 2019, 12:59

21-jul-2019

Delta to 19.06+4

ISO md5 = 5d93f2d91578c03df775fb3705bf28c6 LxPupSc-19.06+4-uefi-T-k64.iso

Must be applied to: 7354341ccba39c08ece34cc2f953084e LxPupSc-19.06+0-uefi-T-k64.iso

Updates are cumulative - only the most recent needs to be applied.

Quite a lot of changes due to:
BUILD_FROM_WOOF='testing;36ae4e6f7;2019-07-16 09:25:58 +0800'

Needs initrd.gz updating as well as puppy_LxPupSc_19.06.sfs

peebee · #1180 Post by **peebee** » Sat 27 Jul 2019, 07:59

Kernel Release: 5.2.4-lxpup64
Build Date: Sun Jul 28 17:38:36 BST 2019
Build GCC: 9.1.0
OS Support: GNU/Linux
Architecture: x86_64
SMP Enabled: Yes

Needs firmware (e.g. in fdrv)

From Here

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

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

Wrong library file link?

Re: Wrong library file link?