Moderator: Forum moderators
First one of @ozsouth's I tried, huge-6.2.9-ubun64oz-ao-PRE.tar.bz2 worked with no hesitation whatsoever. Very fast booting. I had to run it through my zdrv_cp2deb script first and get the filesystem compatible but then it was good to go and everything seems to be working just fine. If anyone needs help with setting up this kernel for Jammy64pup let me know.
Cheers, J
That one of @ozsouths' works fine here also, as does his usrmerge 6.1.23. I'm currently running the 6.1.23 for no particular reason.
My pups: LxPupSc64 and Voidpup64 with LXDE ydrv and synaptics touchpad drivers, both using small savefiles for customizations. Ydrv based NoblePup64 and Fossapup64-small (both LXDE/PCManFM with no savefiles). No fdrvs throughout. 
I made an Anydesk (remote desktop access) .pet (see link) & an Xpat2 (card games) .pet - see attached. (For this usrmerge pup only). Use at own risk.
Anydesk 6.1.1 - https://www.mediafire.com/file/yfjet6q9 ... m.pet/file
xpat2.petWeird - when trying to browse to the following sites, I get 'unable to connect error'.
Different browsers (firefox, chrome, palemoon) & timezone settings make no difference.
Turning off firewall also has no effect. Is an issue in (at least) E1 & D3.
https://www.theaustralian.com.au
I had issues with the latter in the past, but timezone was the answer - not here.
I use this site to check to see if websites are experiencing difficulties, therefore not browser specific
https://www.isitdownrightnow.com/
@ozsouth No firefox here but here's a quick test on three chromium portables, Brave, Slimjet, and un-googled chromium tested in another jammypup64, a clean ydrv'd non-savefile install of the new Bookworm Pup64 (running beautifully except for a couple of multimedia hiccups), LxPupSc64, and F96-CE_4, all current versions of browsers and OS. Firewall on or off makes no difference. Run sequentially on the same Fujitsu S761 laptop. Results on your two sites are:
LxPupSc64: No problems at all connecting to either site in any of the three browsers.
F96-CE: No problems at all connecting to either site in any of the three browsers.
another jammypup64: Connection refused in all three.
Bookworm: Connection once in brave to https://www.heraldsun.com.au/, refused after that and in all other browsers. https://www.theaustralian.com.au/ refused in all three browsers.
Yep, Weirder.
Add: Incognito/private mode makes no difference in Brave or Slimjet and all connections are also fine in the current VoidPup64 as well, posting from that now.
My pups: LxPupSc64 and Voidpup64 with LXDE ydrv and synaptics touchpad drivers, both using small savefiles for customizations. Ydrv based NoblePup64 and Fossapup64-small (both LXDE/PCManFM with no savefiles). No fdrvs throughout.
Try to disable IPv6 (echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6). If a domain can be resolved to both IPv4 and IPv6 addresses, your OS supports both, but the web server listens only on the IPv4 address, the connection will be refused when your browser attempts IPv6. This can also happen if your ISP does weird stuff instead of providing customers with IPv6 support. And this won't happen 100%, because there's a race condition between the DNS lookups used to get the two addresses - if broken IPv6 support on either side (your ISP, your gateway) or the server side (a domain with an IPv6 address but a web server that only accepts IPv4 connections), the browser will probably try both in parallel and connect to the first address it resolves.
EDIT: I have IP6 connectivity here and from what I see, both domains time out when I'm trying to reach port 443 (HTTPS) over IPv4, and they don't resolve to IPv6 at all. The problem is not your Puppy.
@dimkr Thanks, I did have ipv6 disabled by kernel command line in LxPupSc64, VoidPup64, and F96-CE_4 but not in jammypup64 or Bookworm Pup64 so I played with that but indeed that wasn't it.
@ozsouth I think I've got it. In the 'older' pups the /etc/hosts file isn't set up by default to do ad blocking. In jammypup64 and Bookworm Pup64 it is and tags.news.com.au is in it. Pull that line out and have a go at those sites. No exhaustive tests but that seems to do it here.
My pups: LxPupSc64 and Voidpup64 with LXDE ydrv and synaptics touchpad drivers, both using small savefiles for customizations. Ydrv based NoblePup64 and Fossapup64-small (both LXDE/PCManFM with no savefiles). No fdrvs throughout.
Thanks guys! @Marv - I confirm the adblocker lines in /etc/hosts are the cause. I never used that in the past myself, so didn't think to look there. Great pickup!
Jammypup just zoomed into my top 2 Pups (with s15pup64).
Here's some more .pets, tested in version E1 (use at own risk):
Isomaster (for editing iso files - see attached below - menu entry in Utility)
Flashgames (projector & 6 games, in apps folder - menu entry in Fun) here: https://www.mediafire.com/file/yr1lf06l ... j.pet/file
Older scanner driver (xsane997) here (menu entry in Graphic): https://www.mediafire.com/file/xq7itdr9 ... j.pet/file
NOTES: May drive newer devices if official scanner software installed (my Brother HLL-2395DW needed .debs from their website).
I tried this version as ppm version (xsane999) had 25 dependency files & who knows if those had others.
isomaster-j.pet
Well, I think I'll have a look at this over the next few days. Guys, where are these "delta" files hiding? Original spec said page 1, post 2.....but all I can see are a bunch of terminal readouts and some stuff about libdvd and css....
I might as well try it in up-to-date, current format!
Mike. 
@mikewalsh The E1 iso in post 1 is the most recent version. At some point in the development deltas were dropped as being confusing. I've been running E1 albeit customized with PCManFM, my symlinks and JWM configuration, and synaptics drivers for touchpad in a ydrv for some time now and other than adjusting for my quirks and helping troubleshoot an ad-blocker issue for ozsouth I can't point to any issues. Have a go with E1.
OOTB it comes with an overlayfs only kernel but will run happily either with overlayfs or AUFS file systems with any of the 'usrmerge' recent kernels that support AUFS and ovelayfs (like @ozsouths' 6.1.23). Bear in mind that the savefile structure is different for the two FS.
I'm currently running it overlayfs as intended with peebees 6.3.0 kernel with the structure adjusted for usrmerge by @jrbs' script zdrv_cp2deb in the boot directory and punionfs=overlay in the boot stanza. jrb is running ozsouths 6.2.9, see here: viewtopic.php?p=87366#p87366.
FWIW, Bookworm Pup64 runs swimmingly with the same packaging. A couple of multimedia hiccups there that will get ironed out with the next release but it shows @radkys' polish. jammypup64 is more of a 'core' system, while Bookworm is quite full bodied. I like both for different reasons.
an inveterate tinker 
My pups: LxPupSc64 and Voidpup64 with LXDE ydrv and synaptics touchpad drivers, both using small savefiles for customizations. Ydrv based NoblePup64 and Fossapup64-small (both LXDE/PCManFM with no savefiles). No fdrvs throughout.
@Marv :-
'Kay, Marv.....thanks for the 'heads-up', AND the 'explainer' about the kernels. I'll take a look later on....
Mike.
@mikewalsh - I'm running E1 using my 6.1.23 usrmerge kernel (so that I had the sources & headers) with aufs, as I've (so far) not edited the initrd.gz to allow extra drvs & can use sfs_load. I did put punionfs=aufs in the boot stanza so I don't forget which I'm using. I also use a ydrv with my settings. Note your fdrv can't be from a non-usrmerge puppy & some .pets won't work.
For any who don't understand usrmerge, /bin /lib /lib32 /sbin are symlinks to /usr/bin /usr/lib /usr/lib32 /usr/sbin , respectively. This is the newer Debian/Ubuntu protocol, allowing package compatibilty going forward.
I went to change the password & got pam error 26. I discovered the file 'common-password' is missing from /etc/pam.d .
Attached below is one I found on the net. Must remove .fake.txt . Use at own risk.
I made a .pet for Masterpdf4 pdf editor. Use at own risk. See: https://www.mediafire.com/file/son4nnvt ... j.pet/file
I made a Libreoffice 6.4.7.2 us .pet - see: viewtopic.php?p=90146#p90146
By making .pets, I don't need to edit initrd.gz, so as to allow extra drvs. I can use ydrv for my settings, with adrv & bdrv for sources & devx under Overlayfs. If using Aufs, can still load sfs's as desired.
Small script to change your DNS at startup.
It uses
A free, sovereign and GDPR-compliant recursive DNS resolver with a strong focus on security to protect the citizens and organizations of the European Union.
Code: Select all
#!/bin/sh
echo "nameserver 193.110.81.0" > /etc/resolv.conf
echo "nameserver 185.253.5.0" >> /etc/resolv.conf
echo "nameserver 193.110.81.0
nameserver 185.253.5.0" > /etc/resolv.conf.head
nslookup google.com > /tmp/dnssetandcheck
DNSNEW=$(cat /tmp/dnssetandcheck)
gxmessage "$DNSNEW"
Copy the text to Geany and save it as a script and save it as SetDNS.sh.
Right click to allow it to be executable and finally put it in your directory
/root/Startup
One thing that I liked with FP95 was the CPU Frequency Scaling application, that allowed me to lower my cpu to powersave/on-demand
I was messing around with cpu scaling on-demand earlier and cannot remember if I actually set the parameters or if it has done this by itself.
The cpu goes down to 800Mhz when it is idle.
On FP95 there was a GUI available.
The location of the script
Anyone know what this application is named, so I can look it up in the PPM?
Jasper wrote: ↑Sat Jan 20, 2024 3:16 pmOne thing that I liked with FP95 was the CPU Frequency Scaling application, that allowed me to lower my cpu to powersave/on-demand
I was messing around with cpu scaling on-demand earlier and cannot remember if I actually set the parameters or if it has done this by itself.
The cpu goes down to 800Mhz when it is idle.
On FP95 there was a GUI available.
The location of the script
Anyone know what this application is named, so I can look it up in the PPM?
Hi Jasper, Nice to see someone running another jammy again. The application is wcpufreq. It's a script so easily modified. I haven't run another jammypup is a while so I had to look and see what I did there. Ah, I'm all intel and wcpufreq didn't do what I wanted there IIRC, so in /etc/init.d I set start_cpu_freq to non-executable and put a an executable script start_intel_pstate_schedutil in there with these contents:
Code: Select all
#!/bin/ash
modprobe cpufreq_powersave
for CPUNUM in `ls -1 /sys/devices/system/cpu/ | grep 'cpu[0-9]' | tr '\n' ' '`
do
echo schedutil >/sys/devices/system/cpu/$CPUNUM/cpufreq/scaling_governor
doneI have modified wcpufreq in the past but it's a moving target so the above was simpler for me.
My pups: LxPupSc64 and Voidpup64 with LXDE ydrv and synaptics touchpad drivers, both using small savefiles for customizations. Ydrv based NoblePup64 and Fossapup64-small (both LXDE/PCManFM with no savefiles). No fdrvs throughout.
I had to run jammy again to see exactly why I stopped using it. The stumbling block for me was getting LXDE to run cleanly, drives-on-desktop and all. My work when I stopped had a nice clean jwm desktop and all my workarounds to integrate PCManFM etc. Portables all work and it's fast as a scalded hog but the trash and some other workarounds aren't as good as the real thing, either in a pure ROX or in a good LXDE'd install. They are ok for me but not for other users I support.
My Bookworm 64 10.0.4.0 install has (thanks @peebee) LXDE running well so I've been using it as my 'modern millie' of late.
My pups: LxPupSc64 and Voidpup64 with LXDE ydrv and synaptics touchpad drivers, both using small savefiles for customizations. Ydrv based NoblePup64 and Fossapup64-small (both LXDE/PCManFM with no savefiles). No fdrvs throughout.
