Fatdog64-811 Final [10 Sep 2020]

[fatdog]

EDIT:
Fatdog64 812 RC has been released. Forum thread here.

___________

Since we now have a dedicated subforum at our disposal, please do not post support questions in this thread, create a separate one instead. Comments, feedback, etc related to this specific release is still okay. Thank you.
___________

The Fatdog team is pleased to release Fatdog 811 Final.

This is a maintenance release with some new features. All Fatdog 810 users are recommended to upgrade to this release where possible as it contains important fixes.

If you still run earlier Fatdog series (700 or 600), we also recommend upgrading to this version where possible. In this case, you may want to read the notes/warnings noted in Fatdog64 802/801/800 thread.

As usual Fatdog64 does not upgrade from any older version. Using a new savefile/savedir is recommended.

=====

Changes from 810: 810 thread

Updates:

- Linux-5.4.60, low-latency, 1000Hz
- Microcode as of 2020.09.05
- mdview-2020.09
- devx: include lowdown, premake, qemu-4.2.0
- cloud-disk-4.0
- libSDL2-2.0.12 and its friends
- pigz-2.4
- tzdata-2020a
- pci-database-2020, usb-database-2020, out-database-2020
- iotop-c 1.1
- UExtract 4.3
- rox-filer 2020.08 (jun7 fork)
- MultiRename-1.9
- Avidemux 2.7.6
- mm_view 2020.09
- VLC 3.0.11
- avahi-0.8 (loses GUI discovery browser, which now requires gtk3)
- mtpaint-3.49.27
- PackIt-1.22
- sqlite 3.31.1
- bsdriver-3.24
- gptfdisk-1.0.5
- yad-gtk2-0.42.14
- exfat-utils-1.3.0
- bindfs-1.14.3
- adbfs-rootless-2020.03
- dislocker-2020.03
- btrfs-progs-5.4.1
- tigervnc-1.10.1
- libgnutls-3.6.12
- archivemount-0.8.12
- e3-2.82
- dnsmasq-2.80
- sct-1.5
- Screencaster 1.10 heavily improved and updated
- Samba Shares 2.2.0 heavily improved and updated
- Savefile-tool improved
- RAM layer operation fixes (including ability to clear whitouts automatically)
- usb-safe-remove does not remove SD Card reader (only ejects the card)
- wine-5.0.2 (package and SFS)
- Selected NVIDIA drivers SFS for 5.4.60 kernel

New Features:

- Documentation: Fatdog primer for seasoned Puppy users (also available in the ISO itself, new help icon on the desktop)
- New control panel applet: Keyboard Mouse Shortcuts, to list global shortcuts, e.g., what keys switch through the desktops, etc.
- Fatdog Wireless Antenna (GUI for rfkill and selection between multiple wifi cards)
- "ntfsnoperm" boot option - avoid problems dual-booting Windows
- support btrfs for savefile/savedir
- support compressed btrfs using "btrfscompress" boot option
- VLC youtube-player script updater ("update-vlc-playlist-luac.sh")
- (lxc-)rw-sandbox.sh supports running an OS image.
- (lxc-)rw-sandbox.sh supports using a directory for storage instead of an image file
- New universal installation method to USB stick (usb-boot)
- Seamonkey updater script (pulls seamonkey binary from official Seamonkey Project)
- "sudo" compatibility script

and numerous bug fixes, fine tunings, new and upgraded packages in the repository.

Downloads:

Get it from here: ibiblio.org, or from aarnet, uoc.gr, or nluug.nl.

The ISO builder is available on ibiblio.org or one of the mirrors above, get the builder dated 2020.09 and 811-pkglist.tar.xz.

DEXV, NLS, 32-bit compatibility, and kernel source SFS files can be downloaded using the "SFS Manager" applet located in Fatdog64 Control Panel's "System" tab.

=====

If you have any questions please check this pages first: http://distro.ibiblio.org/fatdog/web/faqs/faq.html. This page is also available offline, and you can view it by clicking this link file:///usr/share/doc/faqs/faq.html if you are currently running Fatdog. Or you can click the "question mark" icon on the desktop.

=====

Many thanks to all the contributors who supported us behind the scene with their feedback, bug reports, ideas, and fixes.

=====

[fatdog]

@icake's half-Chinese language packages for Fatdog64-811:
- fcitx Chinese input platform
- scim Chinese input platform
- yong Chinese input platform
and Chinese language packages for Fatdog64-811:
- Simplified Chinese
- Traditional Chinese

LINK

[fatdog]

A lot of websites will no longer accessible using wget (and perhaps curl, too).

This is because of two things:
a) Many of these websites uses LetsEncrypt SSL certificates, and, more importantly:
b) One of the key Certificate Authority for LetsEncrypt certificate has expired on 30 September 2021

If you try to access these websites using wget, you will get an error message stating that the certificate has expired.

To fix this, use Gslapt package manager and upgrade your "lfs-cacert" package to version 2021.10 or newer.

[fatdog]

reserved

[fatdog]

reserved

[fatdog]

Since we now have a dedicated subforum at our disposal, please do not post support questions in this thread, create a separate one instead. Comments, feedback, etc related to this specific release is still okay. Thank you.

[user1111]

sc.png (321.31 KiB) Viewed 6063 times

Multi-session style saving all working great here.

Tried chancing it and copied across my 810 save files and no issues so far.

Thanks Fatdog team

Code: Select all

# uname -a
Linux fatdog64-d37 5.4.60 #1 SMP PREEMPT Wed Aug 26 00:10:36 AEST 2020 x86_64 AMD E1-7010 APU with AMD Radeon R2 Graphics AuthenticAMD GNU/Linux

[Clarity]

@Rufwoof Multi-session ...+1

[Duprate]

Working perfectly, all browsers, libreoffice, gimp, wine and PortableApps platform. FatDog64 is the best! It is what all other Linux systems would like to be, only they are not! Thanks to the developers.

[user1111]

EDIT : Scratch the original text below.

In 810 I'd rebuilt the fd64.sfs (that I store outside of initrd) using lz4 high compression. Rebuilding 811's fd64.sfs the same and swap is now working as before

=============================

Seems like the Linux-5.4.60, low-latency, 1000Hz kernel is causing issues for me with regard to swap.

zcat /proc/config.gz | grep SWAP reveals the exact same setting between Fatdog 810 and the latest 811. However I boot using multi-session save, to ram, with a HDD based swap partition that I load as being encrypted.

/etc/rc.c/rc.local entries of

Code: Select all

/sbin/cryptsetup open --type plain --key-file /dev/urandom /dev/sda2 cswap
mkswap /dev/mapper/cswap 
swapon /dev/mapper/cswap
# My swap partition is 26GB, so I resize / to match that
mount -o remount,size=26G /aufs/pup_multi
mount -o remount,size=26G /aufs/pup_save
mount -o remount,size=26G /dev/shm
mount -o remount,size=26G /tmp

If I boot, cd to /root and run dd if=/dev/zero of=bigfile bs=1M count=4096 that exhausts available ram and initiates using swap, then under Fatdog 810 there were just marginal delays as swap started kicking in. Under 811 the delay is much more pronounced. Of the order of one tmux window showing htop, the other running that dd command and after starting the dd, switch to the htop window and it would 'lock up' for perhaps 5 seconds or so under 810 as swap starts kicking in, but is more like a 30 to 60 second lock up under 811. With swap being used the 811 system in general is a lot more sluggish than 810. Temporary booting 811 with the 810 kernel and kernel modules and swap works fine, the exact same as per a full Fatdog 810 boot.

Looks to me that the newer lower latency kernel tuned for better audio quality has a impact upon swap usage, at least for me. Also whilst playing a long (1 hour) video in VLC the other day whilst also copying across large files from one partition to another (data backup, many many GB's), I did notice VLC was jerky at times, perhaps no better or worse than under 810.

In short, the choice of 811 default kernel might be good for the audio purists but for the more general/broad users there may be performance issues in running under that kernel.

[TerryH]

Since recently manually installing FatDog 811 to a MicroSD Card via a USB Card reader, I have been having significant freezes using the included semonkey browser. I then created a new Firefox ESR portable installation using fredX181's script, which is stored in /mnt/home. I have continued to get continual freezes in firefox also. This is the same card I had FD-810 running from and have replaced the 810 files.

I decided to try the 5.4.60-std kernel instead of the included low latency version. I edited the initrd and swapped in the kernel-modules.sfs and replaced the vmlinuz. So far after a couple of hours usage, seamonkey and firefox are running well at present without issue.

[baldronicus]

Hi. Thank you to all involved in making Fatdog64-811 available. It is very nice.

It works without the need for special parameters on a laptop (AMD A4-9125 based) that has a bit of a history of video issues.

I also tried copying (dd) the usb-boot-mbr.img to an 8GB USB drive, as per the Fatdog Help-
"How to install Fatdog64 to a flash drive that works for both BIOS and UEFI machines" link.

It works nicely. It booted well in "UEFI only" mode, in CSM- "Legacy and UEFI" mode, and on an older laptop that has either a legacy BIOS, or one that is locked in CSM mode (it seems that EFI/UEFI has been with us longer than I had realised).

As indicated in the help topic, GParted was able to work it's magic on the partitions on the USB drive.

After some experimentation, following yet another "Homer" moment, the USB drive was also used to boot some Puppies, both 64 and 32 bit, on some 64 bit and 32 bit hardware.

Again, very nice. Thanks again.

[Duprate]

FatDog64-811, installed and working very well on BIOS and UEFI machines:

Desktop, Intel Pentium CPU G3260 @ 3.30GHz, RAM 8Gb, HDD disk, 64bit.

NUC, Intel Celeron CPU N3060 @ 1.60 GHz, 2Gb RAM, SSD disk, 64bits.

[blackgatonegro]

Update to 811 from the previous version, so far it works fine. Fatdog has now become my main puppy as wary and racy are dead.

[user1111]

Yesterday I 'upgraded' my old Acer desktop from Fatdog 7 to 811. Complete rebuild. All working well (that's it in the middle/vnc)

xscreenshot-20201005T125616.jpg (103.88 KiB) Viewed 2513 times

Only hit one snag, when running vnc server I must have typed in my password into the 'additional options' as it wouldn't start/work until I found that string in the vnc server invocation parameters.

Other than that, fine. 22 core 67GB RAM, 30GB swap

[step]

Other than that, fine. 22 core 67GB RAM, 30GB swap

Liquid nitrogen cooling, I suppose .

[user1111]

Looks to me like the default iwconfig installed in Fatdog 811 is the v30 version - that is in beta

Experimental version of Wireless Tools (at your own risk) :

https://www.hpl.hp.com/personal/Jean_To ... tml#latest

Was that intentional? Or perhaps the build scripts picking up on the non-stable/release version?

Seems to be fine/OK, but perhaps a potential for a future release of Fatdog to pick up a unstable source code version.

https://distro.ibiblio.org/fatdog/sourc ... 4-1.tar.gz

[m1k3]

Other than that, fine. 22 core 67GB RAM, 30GB swap

Wow! What do you even do with a machine that jacked up?

[user1111]

Other than that, fine. 22 core 67GB RAM, 30GB swap

Wow! What do you even do with a machine that jacked up?

I guess the same as what the average user with perhaps a 500MB puppy sfs on a standard laptop with 8GB RAM and 1TB disk might do Mike

[m1k3]

Good answer

[step]

Looks to me like the default iwconfig installed in Fatdog 811 is the v30 version - that is in beta

Experimental version of Wireless Tools (at your own risk) :

https://www.hpl.hp.com/personal/Jean_To ... tml#latest

Was that intentional? Or perhaps the build scripts picking up on the non-stable/release version?

Seems to be fine/OK, but perhaps a potential for a future release of Fatdog to pick up a unstable source code version.

https://distro.ibiblio.org/fatdog/sourc ... 4-1.tar.gz

Intentional. Fatdog-800 (28 February 2019) was the first release to use this version (30.pre9).

[user1111]

On two different CPU's (both AMD), pmcputemp doesn't work for me.

In gslapt there are two versions, if I remove the active one (-1 version) and replace it with the 'older' version, in both cases adding a symbolic link to /usr/bin/pmcputemp in ~/Startup has the temperature tray icon correctly displayed.

[don570]

mtpaint is still being supported by wjaguar

Version 3.49.33
https://github.com/wjaguar/mtPaint
_____________________________________________

I was able to launch KRITA and gmic plugins at same time

Instructions at viewtopic.php?p=10579#p10579

[wiak]

mtpaint is still being supported by wjaguar

Yes of particular importance:

3.50 2020-??-??
* GTK+3 support - "./configure gtk3"

[don570]

3.50 2020-??-??
* GTK+3 support - "./configure gtk3"

wjaguar uses the version number 3.50 as a future goal to obtain.

version 3.49 is the current version that he has been on for many years

[don570]

AZpainter 215 SFS works in Fatdog

https://sourceforge.net/projects/puppys ... /packages/

_____________________________________________

[don570]

I was able to get KRITA 5 alpha appimage (called Krita NEXT) to work in fatdog dog
but because I was using older krita 4 version I had to use clear the older files (resources are
different between krita 4 and 5)

So I used pfind to find all folders with krita in name. There were two.
I left the /root/.config/kritarc file alone.
I was able to get my script to work....
viewtopic.php?f=103&t=2202

Krita 5 has some useful improvements i.e. smear brushes

[wiak]

wjaguar uses the version number 3.50 as a future goal to obtain.

version 3.49 is the current version that he has been on for many years

Currently using mtPaint 3.51 in WeeDogLinux_Arch64 (as provided by rolling Arch repos) - Copyright (C) 2004-2021 The Authors. Seems to actually be version 3.50.05 and compiled to use GTK3.

[jakel]

Hello all, I'd like to report a GPU compatibility issue - with RTX 30XX cards. With default setup, I am unable to set the resolution to 1920x1080. It would also be great if someone could compile a proprietary Nvidia driver that is compatible with the latest build of fatdog64. I have tried myself - using James' guide - unsuccessfully.

EDIT: I've managed to create an SFS of the latest driver compatible with Kernel 5.4.60, and confirm that it works with my card.

Download: nvidia-glx-460.56-k5.4.60-64.sfs

[jakel]

I recently got a new laptop (HP ENVY x360 13-ay0008na) which has a USB-C port that supports DisplayPort™ 1.4. My external monitor does not work when connected to the laptop via a HDMI adaptor, and neither zarfy and lxrandr detect it.

According to phoronix.com a USB Type-C DisplayPort Alternate Mode driver arrived with the Linux 4.19 kernel.

I'm going to guess a custom kernel with support enabled is required in this case?

EDIT: After further investigation I see that the usb-c display driver (typec_displayport.ko) is already included with kernel 5.4.60. I booted into Ubuntu 21.04 and found that usb-c to hdmi works perfectly. Comparing Fatdog's drivers with Ubuntu, I notice some missing files: hd3ss3220.ko and stusb160x.ko and the folder: tcpm entirely.

Below are the files and folders as found in Ubuntu.

Code: Select all

ubuntu@ubuntu:/lib/modules/5.11.0-16-generic/kernel/drivers/usb/typec$ ls

altmodes (folder)
mux (folder)
tcpm (folder)
Ucsi (folder)
hd3ss3220.ko  
stusb160x.ko   
tps6598x.ko  
typec.ko  


ubuntu@ubuntu:/lib/modules/5.11.0-16-generic/kernel/drivers/usb/typec/altmodes/
typec_displayport.ko  typec_nvidia.ko

ubuntu@ubuntu:/lib/modules/5.11.0-16-generic/kernel/drivers/usb/typec/mux/
intel_pmc_mux.ko  pi3usb30532.ko

ubuntu@ubuntu:/lib/modules/5.11.0-16-generic/kernel/drivers/usb/typec/tcpm/
fusb302.ko  tcpci_maxim.ko   tcpci_rt1711h.ko
tcpci.ko tcpci_mt6360.ko  tcpm.ko

ubuntu@ubuntu:/lib/modules/5.11.0-16-generic/kernel/drivers/usb/typec/ucsi/
typec_ucsi.ko  ucsi_acpi.ko  ucsi_ccg.ko

Edit2: I've attempted to compile my own version of the 5.11 kernel for fatdog64 and have had some success with this issue. External monitor is now working, however it is still not identified in zarfy and lxrandr. Here is the .config I used when compiling the kernel, and output of lsmod when external monitor is displaying.

---------------------------------------------------------------------------

I'm unsure which of the following flags was specifically required:

Code: Select all

CONFIG_TYPEC=m
CONFIG_TYPEC_TCPM=m
CONFIG_TYPEC_UCSI=m
CONFIG_UCSI_CCG=m
CONFIG_UCSI_ACPI=m
CONFIG_TYPEC_HD3SS3220=m
CONFIG_TYPEC_TPS6598X=m
CONFIG_TYPEC_STUSB160X=m

Hopefully this helps enable usbc-displayport functionality in future fatdog kernels. Thanks.