S15Pup - Discussion

[Wiz57]

Well, my testing did not go anywhere near as planned. I tried several times to boot the iso in my problem above,
each time resulted in the main puppy sfs file not being found??? After trying different boot parameters by booting
into my other 240413 iso, then rebooting, I don't know what happened, but now none of my frugals boot by the usual grub4dos menu.lst, give error when trying to load grub4dos that "grldr not found"...have tried reinstalling g4d, via
several methods, nothing is working. The last error I remember from one of the S15Pups was something about stray files mounted??? Not sure, may have to try a USB thumb drive and see if I can locate some sort of lock file on the internal HDD
in an obscure place. For now, the Acer is only booting Windows XP SP3 from internal HDD.
Wiz

[thinkpadfreak]

Hello.
I gave a try to the latest iso (s15pup32).

I was surprised that the touchpad did not work. Since an edge of the touchpad of my machine serves as click buttons, I could not even "click."
Later I found that the touchpad was disabled by default with a "new" type of mouse property.

This will confuse some notebook PC users. I wonder why such a change has been made.

Edit:
To be more precise
mouse property -> pointer property

[Wiz57]

Just a follow-up in regards to my old Acer Aspire One AOA150...I think it is getting close to end of the road! Now it not only lost the grldr to boot my Puppys,
but it seems to have lost the MBR, and the partitions (had 2 on the HDD, 1 hidden recovery, the regular in C:), so it appears the old HDD is starting to fail.
I don't use it much, only 1 gig RAM and the Intel Atom CPU, so it was already a tad slow...but it was handy for playing old Windows games and tweaking my
Puppys! I may try a full wipe and reformat of the HDD, but even booting with a USB thumb drive is sometimes not working. I've noticed the fan not spinning
up like it used to when powering it up. So, I may take her apart and inspect that...could be something simple like dust buildup, or it could be near fatal,
and it really isn't worth the cost to replace the fan. Just depends on how industrious I feel. For now, I'm using my Dell Latitude 3190 laptop, Win 11, and
even though it only has 4 gig RAM, it performs quite well for my needs...which are not computing intensive at the present time, LOL. I can't complain about
the Acer though, it has ran for 17 yrs now!

[Wiz57]

THERE'S STILL LIFE IN THIS OLD ACER ASPIRE ONE AOA150! I'm rebuilding contents of the HDD from scratch, had a few things on other media, but it is back up and running. Cleaned the fan a bit, best I could without a total teardown (didn't have time on Mother's Day), but I'm back online with it now, running ScPup32 20.06 with the kernel and zdrv swap I'd done one time! Woo Hoo! Even got Windows XP SP3 running again (WinXP Pro this time, didn't want "Home" edition for a change).
Wiz

[ozsouth]

@Wiz57 - do you have the devx for 240413 or 240420?

[Wiz57]

@Wiz57 - do you have the devx for 240413 or 240420?

I don't think so, best I can tell it is the devx for the latest release. If needed, I may just
rename the devx to match, and see if that works. Not sure what the changes are...I'm
also running on an older kernel and zdrv at the moment, using kernel 4.14.173 from an
older ArchPup32, lol...when this old Acer went haywire I lost all the downloaded stuff I'd
saved over the years, but at least I was able to get it back to usability.
Which reminds me...the discussion about DistroWatch needing new Puppy, and the various
postings about the strengths and positives of Puppy all neglect its biggest selling point...
THE SMALLER DOWNLOAD SIZE FOR A FULL OPERATING SYSTEM! I'm on a metered internet
connection, and I don't have the data cap to allow downloading multiple 1-2 gigabyte installation
media typical of other distributions...for less than 1 gig download, I have 4 Pups at my disposal!
Now that's what I call a strength...I know, most probably have "unlimited highspeed internet"
but for those who don't, Puppy is a tremendous asset to have available!
Wiz

[ozsouth]

Thanks anyway Wiz57. Does ANYONE have the devx for s15pup64 240413 or 240420?

[ozsouth]

In May I made a remaster (ovrly-6) based on 240323. Worked well. May & June versions had several issues, fixed in 240612 version by peebee (thanks!).
I've since noticed that my Dell Inspiron touchpad doesn't work in May & June versions, unless I rmmod hid_multitouch , then modprobe hid_multitouch. Even if I do that, if I later restart X, I need to repeat it. I had to put a script to do it in /root/Startup.

[peebee]

In May I made a remaster (ovrly-6) based on 240323. Worked well. May & June versions had several issues, fixed in 240612 version by peebee (thanks!).
I've since noticed that my Dell Inspiron touchpad doesn't work in May & June versions, unless I rmmod hid_multitouch , then modprobe hid_multitouch. Even if I do that, if I later restart X, I need to repeat it. I had to put a script to do it in /root/Startup.

Kernel related? Are you able to try a kernel from an earlier version? 240505 & 240518 iso's are still available from SourceForge.

[ozsouth]

@peebee - I tried default kernel as well as 2 of mine in 240612. Also tried default fdrv as well as mine. Also ran default 240505 - same. Also tried a 10 sec delay in /etc/init.d - no good. Also tried initrd.gz from 240323 with correct DISTRO_SPECS inserted - no joy. Could just be my Dell though.

My script /root/Startup/unreloadhidm (need to make executable - takes up to 10 seconds after desktop up to activate):

Code: Select all

#!/bin/sh
M=$( lsmod | grep hid_multitouch )
[ -n "$M" ] && rmmod hid_multitouch && sleep 0.5 && modprobe hid_multitouch

[simfann]

Hello, I'm new to "S15Pup64" since yesterday. I'm coming from "FossaPup64", which still works quite fine for me since more than 6 months. Now I'm searching for a more modern version of puppy and started two weeks ago with "F96-CE". But I was much disappointed about it, because I found no solution for running "xwin", that means display (screen), and at the same time WIFI. (I have posted these problems under forum "F96-CE".) "Starting yesterday with "S15Pup64" all works fine until now. Congratulation for this nice puppy! I had a little problem with installing KeePassXC, but I've found an AppImage of it and now my most important programs at the moment "Firefox", KeePassXC" and "Double Commander" are working perfectly under "S15Pup64". Configuring of two screens and audio also made no problems. I think, I will transfer in the next time all programs from "FossaPup64" to "S15Pup64".

[version2013]

@peebee thanks for your responses.
YOur command opens desktop themes. Dont remember the Window Manager doing that before. Seem to remember a different window where the ability to manipulate ICONs and TRAY elements along with desktop selections were present via the Window Manager.

"Could be my memory."

My understanding (I could be wrong) is that "Window Manager Settings" button used to launch "JWMdesk"
Currently the "Desk Manager" is "Ptheme"

Once "JWMdesk" is installed, pressing that button will then ask if you want to manage jwm desktop with "JWMdesk"

References:
viewtopic.php?p=32268#p32268
http://www.smokey01.com/radky/PupMates.html

[ozsouth]

For some reason, I've never succeded in compiling ffplay in Slackware derivatives. I made an ffplay v6.1.2 in fossapup64, with libs pointing to /usr/lib64 & it runs in s15pup64-22.12-240717, which has ffmpeg 6.1.1 (as do 240612 & later), so required av libs match. Pet below installs binary, plus SDL2.0 lib & launch script vidplay. Use at own risk.

Once installed, find /usr/local/bin/vidplay in ROX-Filer filemanager & drag to desktop. Then drop a media file on that icon to play it. Plays most video file types & mp3 & ogg files. Closes on completion.
Useful keys when playing media:- q=quit ; p=pause/resume ; left arrow=back 10 sec ; right arrow=fwd 10 sec.

LATER: Runs ok in 240919.

[yolhurt]

I have an issue with the latest version of S15Pup64 (S15Pup64-22.12-240907) on my Thinkpad X230 laptop.

After closing the lid, instead of going to suspend, the laptop just freezes and has to be restarted. This didn't happen on any previous version of S15Pup64 that I've tried.

[yolhurt]

I have an issue with the latest version of S15Pup64 (S15Pup64-22.12-240907) on my Thinkpad X230 laptop.

After closing the lid, instead of going to suspend, the laptop just freezes and has to be restarted. This didn't happen on any previous version of S15Pup64.

I forgot that I haven't actually updated to the latest release of S15Pup64 for a while, so I'm not sure in which version this issue began. When I posted my previous comment I hadn't noticed there was a new release today, but I've just tested it and the same issue occurs (and also in the August release that's still on the Sourceforge releases page).

[ozsouth]

@yolhurt - Would you please run the following terminal command (to see what your wakeup options are): cat /proc/acpi/wakeup
I had laptops that wouldn't wake on lid lift & willams2 pointed out a tweakable fix. I also made a different fix for mikewalsh.

[yolhurt]

Hi ozsouth. This is what that command gives me:

Code: Select all

Device	S-state	  Status   Sysfs node
LID	  S4	*enabled   platform:PNP0C0D:00
SLPB	  S3	*enabled   platform:PNP0C0E:00
IGBE	  S4	*disabled
EXP3	  S4	*disabled
XHCI	  S3	*enabled   pci:0000:00:14.0
EHC1	  S3	*enabled   pci:0000:00:1d.0
EHC2	  S3	*enabled   pci:0000:00:1a.0
HDEF	  S4	*disabled  pci:0000:00:1b.0 

Until updating to the penultimate release I haven't had this issue before using S15Pup64 on this laptop. I remember I had a similar issue with another Thinkpad laptop running Slacko 5.6.

[ozsouth]

@yolhurt - your lid is going into hibernate state. A try at own risk option - the .pet linked below won't totally fix it, but lid-lift then mouse movement (or a key press, say shift) is better than a lockup. See: https://forum.puppylinux.com/viewtopic. ... 47#p127947

[yolhurt]

@yolhurt - your lid is going into hibernate state. A try at own risk option - the .pet linked below won't totally fix it, but lid-lift then mouse movement (or a key press, say shift) is better than a lockup. See: https://forum.puppylinux.com/viewtopic. ... 47#p127947

I tried the .pet, but unfortunately it didn't make any difference.

After testing various previous releases (found on Internet Archive), the last version on which this issue doesn't occur is actually the S15Pup64-22.12-240223 release (didn't think it was so long since I updated ).

So something changed in the following release (S15Pup64-22.12-240309) that makes closing the lid freeze my laptop.

Any idea what it could be?

[ozsouth]

@yolhurt - could be a kernel issue, but I would try substituting the /etc/acpi/actions/suspend.sh from your last working puppy. Without having a copy of those puppies, it's hard to assess. I will look into it. If you open a terminal & maximise it, then run: dmesg | grep err , do you see any error messages?
You can stop lid suspend totally by editing /etc/acpi/acpi.conf & deleting the # to left of DISABLE_SUSPEND='yes' , then restarting X.

[yolhurt]

@ozsouth , cheers for your help. I didn't get any error messages with "dmesg | grep err". The /etc/acpi/actions/suspend.sh was the same on the last working puppy, as was the acpi_poweroff.sh file. I think I'll just disable the lid suspend for now, but hope there might be a possible fix for this.

[ozsouth]

@yolhurt - that's probably best. There is a lesser suspend - freeze (normal suspend is mem). Most PCs have it. Everything is in low power, screen goes blank, but fan might run very occasionally. Must tap power button to resume. Mem is recommended for most users.
To see if you have freeze, run in a terminal: cat /sys/power/state
If so, could try the following in a terminal, at own risk: echo freeze > /sys/power/state
You can run it from /etc/acpi/actions , by replacing mem in the suspend.sh script, but I'd test it from terminal first.

[yolhurt]

@yolhurt - that's probably best. There is a lesser suspend - freeze (normal suspend is mem). Most PCs have it. Everything is in low power, screen goes blank, but fan might run very occasionally. Must tap power button to resume. Mem is recommended for most users.
To see if you have freeze, run in a terminal: cat /sys/power/state
If so, could try the following in a terminal, at own risk: echo freeze > /sys/power/state
You can run it from /etc/acpi/actions , by replacing mem in the suspend.sh script, but I'd test it from terminal first.

I tried that from a terminal, and it does go into low power, but after tapping the power button to resume, the screen comes back on and the laptop just freezes again.

Could that possibly be a clue to what's happening?

[ozsouth]

@yolhurt - I'm out of ideas, other than to disable suspend. I will download 240223 later & look through it. I'm now running 240919 without issue. Did you do a fresh install, without using any previous savefile/folder?

LATER: - I made a combo pup - 240919 with puppy sfs from 240223. Would tell us if you have a kernel problem or a puppy update one.

[yolhurt]

@ozsouth, thanks a lot for your help with this, appreciate it. I've just tested your combo pup but still get the freeze when reopening the laptop lid. All the previous S15Pup64s I've tested have been with a fresh install, no save folder, and the issue is only present from S15Pup64-22.12-240309 onwards. This is on a Thinkpad laptop, I currently have nothing else to test it on. I think I'll go back to S15Pup64-22.12-240223 for now and see if anything changes in future releases.

[ozsouth]

@yolhurt - ok, this seems like a kernel or firmware issue. There were big changes after 240420 (ffmpeg issues). You could try a recent s15pup64 with the kernel & firmware from 240223. All you need to swap is fdrv, zdrv, vmlinuz. It may be that combo will work for you. Otherwise sticking to what works or disabling suspend is best.

[yolhurt]

@ozsouth That has worked, nice one! I've installed the latest S15Pup64 with the fdrv, zdrv, vmlinuz from the 240223 release and now no more problems with suspend.

[amethyst]

Abiword - inserting symbols does not work for me. No symbols are showing for none of the fonts and it's not working. Is there a fix?

[ozsouth]

@amethyst - the debian one I used in fossa-mid works (slowly) for me in s15pup64-240717 (in /usr/bin). Attached below.

[amethyst]

@amethyst - the debian one I used in fossa-mid works (slowly) for me in s15pup64-240717 (in /usr/bin). Attached below.

Thanks. I'll try some other executables from other Puppys also to see if it is a bit faster. I know that Fossa9.6's abw executable also worked with your stripped-down versions of Fossa 9.5.