@ssz: re: pWidgets-2.5.8-486 Dangerous old program - not updated since 2015! Has nasty hidden dependencies in /usr/local/pwidgets/install/.dependencies which because pWidgets does not understand the lib structure of modern UPups means that its pinstall merrily overwrites those essential system depen...

gyro wrote:A place to start with the "mmc module issue" would be to recompile the kernel with a modified 'DOTconfig':

64-bit kernel 5.7.2 has the suggested config changes:
http://murga-linux.com/puppy/viewtopic. ... 96#1060596

Kernel Release: 5.7.2-lxpup64
Build Date: Thu Jun 11 11:38:25 BST 2020

Needs firmware (e.g. in fdrv)

From Here

installing pWidgets-2.5.8-486 in UpupEF totally "destroys the entire program"... Hi ssz. Please explain exactly what happens? What program? What is totally destroyed and how? Where do you get pWidgets from? Have you looked inside pWidgest (rh click - pextract) to see what is being loaded ...

New release:

https://github.com/intel/Intel-Linux-Pr ... e-20200609

gyro wrote:If it is a "module" issue, it can be fixed with a recompiled kernel,

Do you know what kernel config is needed?
Thanks

For my WIFI problem I tried changing to the 5.7.1 64bit kernel. Hi @bigpup Googling shows lots of problems with Realtek 8822be ..... One suggestion seen is that the rtw88 driver is the one to use - this is in 5.7.1 https://www.reddit.com/r/linux/comments/cvbqem/realtek_rtl8822be_under_linux/ https:...

07-June-2020 - updates to Qt-5.15.0

09-June-2020

Now:

chromium_83.0.4103.97+pepper_32.0.0.387

Kernel Release: 5.7.1-lxpup64
Build Date: Sun Jun 7 17:56:03 BST 2020

Needs firmware (e.g. in fdrv)

From Here

Need the kernel driver. r8822be.ko The kernel configs for 4.14.160 as shipped have: # CONFIG_RTL8XXXU is not set whereas Porteus kernel has: CONFIG_RTL8XXXU=m CONFIG_RTL8XXXU_UNTESTED=y CONFIG_RTW88=m CONFIG_RTW88_CORE=m CONFIG_RTW88_PCI=m CONFIG_RTW88_8822BE=y CONFIG_RTW88_8822CE=y # CONFIG_RTW88_...

@mash
@bigpup

are either / both of you booting directly from ssd??

Many thanks for all the testing - seems like we're narrowing it down to something that changed in woof-ce between: 2019-12-01 19:44:38 +1000 & 2019-12-06 22:02:47 +1000 There were many woof-ce commits in this time period: https://github.com/puppylinux-woof-CE/woof-CE/commits/testing?after=4a32f8...

06-Jun-2020

+4 update available - both Ubuntu and Woof-CE updates. See post #1

@mash & @bigpup Please try a hybrid install - all the components from 20.01+6 but renamed: rename 20.01 19.09 *.sfs and: replace the initrd.gz with that from 19.09+0 if that install boots with no kernel panic, please swap the initrd.gz for that from 19.09+7: http://www.smokey01.com/peebee/downlo...

LTS 32-bit-pae kernel 5.4.44 ...... Built using the Porteus configs so for test only No firmware - needs separate fdrv Builds surprisingly small, so wondering what's missing?? Available from: https://sourceforge.net/projects/lxpup/files/Other/huge-kernels/ Tests on a range of hardware - age and powe...

Thanks for the tests......... https://github.com/puppylinux-woof-CE/woof-CE/commits/testing/initrd-progs shows the changes to initrd in recent times....... ScPup = BUILD_FROM_WOOF='testing;291ac8276;2020-05-02 04:38:20 +1000' so all commits should be included as at 2 May..... I can't see anything th...

Can somebody with "the problem" please try 32-bit kernel 5.4.37 from Porteus: http://www.smokey01.com/peebee/downloads/test/porteus-k5.4.37-scpup32.sfs - open the sfs and copy the 2 files to the ScPup32 frugal install folder. Reboot. My HP550 laptop does boot ScPup32 with k4.14.160 however...

These are the systems we should be considering: ScPup32 System built on: Sat May 2 16:50:32 BST 2020 3ae78a543f5ba2fdb9a1bb7c2098d77d ScPup-20.01+6-T.iso BUILD_FROM_WOOF='testing;291ac8276;2020-05-02 04:38:20 +1000' kernel 4.14.160 32bit-pae ==================== ScPup64 System built on: Sat May 2 09...

Thank you for reports. I obviously do not have these problems on the hardware I have available to test..... Can people: 1. try an alternative kernel: https://sourceforge.net/projects/lxpup/files/Other/huge-kernels/ 2. post output from System -> Pup-SysInfo -> Sys-Specs -> Base Report 3. try booting ...