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

[peebee]

32-bit Slackware Current based Pup with LXDE desktop

Updated to 23.01+8 17-November-2024

details and downloads from here

previous discussion thread on murga-linux

...

Screenshot.png (249.76 KiB) Viewed 2807 times

[peebee]

reserved

[Marv]

Like LxPupSc64 20.06 +1, LxPupSc 20.06 +1 is running well on my i5 based all intel Fujitsu S761 laptop. The usual Frugal Grub4Dos install to SSD, an update to my 20.06 +0 install. All low level checks and video FPS good, lidsuspend ok, a couple of days now running it with the 5.8.5 kernel with no issues (haven't bumped either this or LxPupSc64 to the 5.8.7 kernel as yet). I am using a run-as-spot SFS of Slimjet 27.0.7.0 which while having the usual chromium cruft if run from terminal is functionally perfect. I use Cookie Autodelete and SlimJets' built in adblocker, A fair number of video clips run through it, no problems, and absolutely no 'AW SNAPS'.

Thanks,

Update 09 September: Kernels in both the 32b and 64b LxPups bumped to 5.8.7. No issues at all seen on the i5 based S761 laptop. All system level checks good and a couple of days run-time on each pup.

Update 14 September: Kernels up to 5.8.8 on both pups. Tests as above, Also as above; no issues in a day or two of normal use on each.

Update 20 September: Both pups above bumped to the 5.8.10 kernel. Same drill as above, same results -good tests, no issues-

[liogab11]

What live USB utility supports LxScPup (or is able to make a working live USB with it)?

I normally use YUMI, but all options for unsupported ISOs failed.

[tosim]

Here are two: Pentoy, and MultibootUSB.

[liogab11]

@tosim: I couldn't find any tools named "Pentoy". I tried MultiBootUSB, but it won't work.

[peebee]

What live USB utility supports LxScPup (or is able to make a working live USB with it)?

What kind of boot - UEFI or Bios?
If UEFI - is secure boot disabled?
How is the USB formatted?

If you are already running LxPup Bionic then you could try FrugalPup....
viewtopic.php?f=105&t=337

[mikeslr]

If you are already running LxPup Bionic then you could try FrugalPup....
viewtopic.php?f=105&t=337

Actually, AFAIK any recent Puppy can use Frugalpup.

About the only other way I know to create a Live USB Puppy from a Linux operating system is to install Unetbootin. Your Linux distro's package manager may provide a version. If not, it can be obtained here: https://unetbootin.github.io/

Unetbootin, however, doesn't 'understand' Puppy Linux. It writes boot arguments as if Puppy was on a CD/DVD. So you have to open the config file in a text-editor and manually change any reference to CD to read USB. At least, that's my recollection. Perhaps someone whose worked with Unetbootin recently can correct this or provide details; or better still, post a "How to".

Well, that was quick. Bigpup already did, http://murga-linux.com/puppy/viewtopic. ... 153#851153, especially, http://murga-linux.com/puppy/viewtopic. ... 870#861870

[liogab11]

EDIT: Unetbootin works, but it turns out I got the one that has a 64-bit kernel... watching it load on my 32-bit was like watching a Saint Bernard mate with a Chihuahua in heat...

I used ScPup and slapped the LXDE ydrv on it.

Thanks for the help!

=====

@peebee

What kind of boot - UEFI or Bios?
If UEFI - is secure boot disabled?
How is the USB formatted?

BIOS
FAT32

Will try Unetbootin and instructions next weekend, I guess...

[gudintac]

I download this file "LxPupSc-20.06+0-T-k64.iso"
from this url "http://www.smokey01.com/peebee/LxPupSc32-20.06.htm"
and get kernel error
my PC is 32bit and the ISO too

can some one help me

(sorry my english)

errordelgrub.jpg (64.25 KiB) Viewed 9187 times

[Wiz57]

Hello gudintac,
What you need is a pure 32 bit ScPup, as LxPupSc32 incorporates a 64 bit kernel.
I'm right now booted into ScPup32 20.01, but using the LXQT ydrv.sfs to give me
the LXQt desktop. More info here:
viewtopic.php?f=122&t=168

Try this one and see if it works for you!
Wiz

[peebee]

my PC is 32bit and the ISO too

LxPupSc32 iso does have a 64-bit kernel so will not run on a 32-bit processor I'm afraid.
You could change the kernel to 32-bit by replacing the vmlinuz and zdrv in a FRUGAL INSTALL - do NOT do a full install.
e.g. https://sourceforge.net/projects/lxpup/ ... 2/download

@Wiz57 suggestion of ScPup32 + ydrv is also a good route (again FRUGAL install).
download links: viewtopic.php?p=295#p295

[gudintac]

What you need is a pure 32 bit ScPup.
I'm right now booted into ScPup32 20.01, but using the LXQT ydrv.sfs

Try this one and see if it works for you!

vive.... VIVEEE!!!

it works
my 12 years old netbook is alive again and updated.

thank you.

[Marv]

The 5.9.14 kernel is swapped into all my LxPups, both 32b and 64b. It's a bump from 5.9.10 in all, on both the i5 based Fujitsu S761 laptop and on the Bay Trail based desktop. No issues whatsoever, full usual checks plus multimedia as I'm updating one of the farm laptops. Lots of fairly heavy use for the laptop as I also have been assembling a Fossapup64, with no adrv, your ydrv, geany and galculator added in. The portable 64b ungoogled-chromium, portable 32b and 64b LibreOffice and MasterPDFeditor shared by all. The Slimjet 28.0.3.0s are the only remaining SFS. That FFpup now has the balance I wanted and works a treat on both the lappies and the Bay Trail desktop. That leaves LxPupSc as my sole 32b pup. Inch by inch. Really nothing I can't do in the 64b ones now (except like the library structure). The farm laptop gets LxPupSC64 as prime, with LxPupSc set up as backup with a ramboot option for troubleshooting. Her older LxPupSc was still working well but the newest browser it would support is now woefully inadequate, alas. Once I deliver that laptop it has to just work for a fairly unsophisticated user so I have to carefully prune the menu and panel, set up the browsers minimally, get the goldarn canon printer working, and pick all the nits. Questions are harder to deal with in the time of Covid.

Cheers,

Update Dec 19, 2020: Farm laptop delivered as above, LxPupSc64 +2 and LxPupSc +2 both running the 5.9.14 kernel. I actually got all 3 pups on it (both the 64b and the two 32b slackware derivs) to print on their acursed canon MG-3670 printer. Holding my breath for a bit now... I'm happily running the 5.10.01 kernel in LxPupSc64 20.06 +2 on my laptops (Fujitsu S761s).

[mistfire]

Did you try hotplugging input devices while running Xorg? It seems that Xorg does not recognized a newly plugged input device unless Xorg was restarted. However AutoAddDevices was enabled on xorg.conf

[peebee]

Did you try hotplugging input devices while running Xorg? It seems that Xorg does not recognized a newly plugged input device unless Xorg was restarted. However AutoAddDevices was enabled on xorg.conf

Sorry @mistfire don't know what you mean - which device? plugged into which port?? Works OK for me with usb stick plugged into usb port.....
.

Screenshot.png (87.01 KiB) Viewed 5396 times

[mistfire]

Did you try hotplugging input devices while running Xorg? It seems that Xorg does not recognized a newly plugged input device unless Xorg was restarted. However AutoAddDevices was enabled on xorg.conf

Sorry @mistfire don't know what you mean - which device? plugged into which port?? Works OK for me with usb stick plugged into usb port.....
.

Screenshot.png

@peebee
Not USB storage, what I mean was hotplugging input peripherals such as USB Mouse, joysticks, or usb keyboards. I noticed that upon plugged those devices while Xorg is running it detected by udev, but it doesn't recognized by Xorg unless the Xorg was restarted.

[peebee]

@peebee
Not USB storage, what I mean was hotplugging input peripherals such as USB Mouse, joysticks, or usb keyboards. I noticed that upon plugged those devices while Xorg is running it detected by udev, but it doesn't recognized by Xorg unless the Xorg was restarted.

No - I don't "hotplug" such devices.
Is this an LxPupSc specific observation or does it also apply to other Pups - i.e. Woof-CE observation?

[mistfire]

@peebee this is LxPupSc specific observation as of now.

[mistfire]

@peebee

I finally found why Xorg hotplugging does not works. The problem was the eudev package from slackware current. It throws this error message

Code: Select all

name_to_handle_at on /dev: Function not implemented

The solution was rollback the eudev using the slackware 14.2 package

[peebee]

The problem was the eudev package from slackware current.

@mistfire
Can you tell me your system build date please - /etc/system_build_date

and which kernel you are using?

eudev was updated on 7/12/20 as part of the Plasma5 changes to Slackware Current...... the previous update was 28/10/2019

I wonder what the error message means? "name_to_handle_at on /dev: Function not implemented" - what Function????

[mistfire]

@peebee

I used the lxpupsc 20.06+3 build

Based on exploring the source code of Xorg and eudev, Xorg creates a netlink to eudev in order to listen on kernel events using the libudev

"name_to_handle_at on /dev: Function not implemented"

This error means that the function named "name_to_handle_at" on libudev might be missing or disabled upon compiling by slackware package maintainers this will stops the monitoring kernel events and the Xorg can no longer listen on udev socket for any changes on devices

[peebee]

Not USB storage, what I mean was hotplugging input peripherals such as USB Mouse, joysticks, or usb keyboards.

Hi @mistfire
I plugged in a usb keyboard and it was detected and immediately working as I would expect.....

Code: Select all

[  762.824962] usb 5-2: new low-speed USB device number 2 using uhci_hcd
[  763.014978] usb 5-2: New USB device found, idVendor=0e8f, idProduct=0021, bcdDevice= 2.10
[  763.014981] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  763.014984] usb 5-2: Product: AMP USB KB Pro
[  763.014986] usb 5-2: Manufacturer: AMP
[  763.032494] input: AMP AMP USB KB Pro as /devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2:1.0/0003:0E8F:0021.0005/input/input17
[  763.088474] hid-generic 0003:0E8F:0021.0005: input,hidraw4: USB HID v1.10 Keyboard [AMP AMP USB KB Pro] on usb-0000:00:1d.3-2/input0
[  763.110428] input: AMP AMP USB KB Pro Consumer Control as /devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2:1.1/0003:0E8F:0021.0006/input/input18
[  763.165037] input: AMP AMP USB KB Pro System Control as /devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2:1.1/0003:0E8F:0021.0006/input/input19
[  763.165108] hid-generic 0003:0E8F:0021.0006: input,hidraw5: USB HID v1.10 Device [AMP AMP USB KB Pro] on usb-0000:00:1d.3-2/input1

[AstonX]

Hello
I am trying to boot LxPupsc32...i mean that is 32 bit
so i download iso from SF and theni try with qemu...

telling me that require 64bit cpu....
ok i switch to win7-64bit and try again ...but still same error...
Is there a version only for 32bit that is tested on 32bit machine?
tnx

[peebee]

LxPupSc32 has a 64-bit kernel in the .iso and therefore the default version will only run on 64-bit cpus.....

You can change the kernel to a 32-bit kernel by replacing the vmlinuz and zdrv renamed appropriately....
these can be obtained in various places - e.g.
https://sourceforge.net/projects/lxpup/ ... 2/download

[AstonX]

Thanks for reply.
Ok i put again iso on usb stick and boot directly
and worked ...but just for unknown reasons i cannot get proper resolution on my monitor
however system work very fast .

[Clarity]

Thanks for reply. ...

If you PC has the firmware to support VM AND you are using QEMU, you can tell QEMU to create a 64bit virtual PC and your distros will boot. This can be done even if you have booted a 32bit PUP distro.

HOW old is your PC (I am assuming you are using a 32bit PUP because your 64bit PC has issues...Y/N)?

Is there something wrong with @peebee's 64bit versions of LxPupSc?
Reason I am asking is "I have never had any issues, performance or otherwise" with his 64bit LxPup(s); so I am merely curious.

[Marv]

Build of 01-Apr-2021 up and running on the Fujitsu S761. Hardware, procedure, and tests as outlined for LxPupSc64. Clean boot, good tests, and savefile scrub and update from 20.06 +2 went well. A sticking point for me at the moment is that neither 32b Slimjet 29.0.0.0 or a 32b SlimJet 28.0.3.0 run-as-spot SFS will run under 21.04.0 while they both ran correctly under 20.06 +2. They both start ok in 21.04 but give aw-snaps on all pages on this hardware. I haven't run either from terminal or done any chasing as yet. U-light works correctly so it's a crumium thing. Checksum is fine on the downloaded iso.

Thanks,

[peebee]

neither 32b Slimjet 29.0.0.0 or a 32b SlimJet 28.0.3.0 run-as-spot SFS will run under 21.04.0

Hi @Marv
This is caused by the update of glibc to version 2.33...........
Its got something to do with preparations for the 2038 clock changes (I think I read....)
https://lwn.net/Articles/664800/

What you need to do is add switches:
--disable-seccomp-filter-sandbox -test-type
to the exec line

This is of course not as secure as running without this bodge but hopefully a chromium patch will eventually appear to sort things - however 32-bit is not high priority for the chromium devs so may take some time..... but AlienBob is on the case batting for 32-bit Slackware..... https://groups.google.com/a/chromium.or ... wWwdXmCcgY

It affects all 32-bit chromium derivatives.... all my 32-bit chromium based browser sfs have the bodge.... https://sourceforge.net/projects/lxpup/ ... /browsers/

Cheers
peebee

[Marv]

neither 32b Slimjet 29.0.0.0 or a 32b SlimJet 28.0.3.0 run-as-spot SFS will run under 21.04.0

Hi @Marv
What you need to do is add switches:
--disable-seccomp-filter-sandbox -test-type
to the exec line

Thanks peebee, bodge applied and the SlimJet 29.0.0.0 SFS rewrapped. Running fine now. I pretty much run 64b pups now, primarily LxPupSc64 and my ydrive driven highly minimized 64b fossapup with no save file or folder. SSD/memory throughput and the availability of ungoogled-chromium the main reasons. LxPupSc32 is onboard all the computers though with a normal and a pfix=ram boot available as the neverfail/recovery OS.

Thanks and cheers,