Fatdog64-802/801/800 Final [21 May 2019]

[jake29]

Thanks for the reply James. The reason for my request was indeed related to compiling a newer version of Mesa.

I'm trying to resolve a crashing problem with a specific app and I'm comparing installed packages between Fatdog64-802 and Ubuntu 19.04 (where the app is stable). The app is the streaming client for a cloud platform, and it looks to be a video-related problem.

I have managed to update to the same version of libva and libva-intel-driver, but my problem persists.

Some remaining obvious differences are a newer version of Mesa, and the presence of 'intel-media-va-driver' (https://github.com/intel/media-driver).

A long-term question I've had regarding compiling - is there a way I can pause or break the progress made and resume later or after a reboot?

Thanks.

[rufwoof]

<Might I propose adding Terminus bold 32 console> ==> link?

https://sourceforge.net/projects/termin ... z/download Out of that complete set, dropping the ter-i28b.psf.gz into /lib/boot/consolefonts and it sits alongside big and bbig font that already exist. A 28 font size is nice for relatively common resolutions i.e. 768 (as in 1366x768) and a 28 bit height yields 768 / 28 = 27 lines, which is good for displaying 80x25 type content (BBS's etc), with a couple of extra lines for titles/panel (tmux). In Taiwan, millions still use BBS, often with 150,000 on at any one time. I guess it better facilitates posting things more anonymously.

<ccrypt> ==> It's 815KB. If it can be made smaller then I'll bring it in. Otherwise I'm sure there are similar others which is in the order of 50K or less (perhaps bcrypt?).

ccyrpt http://ccrypt.sourceforge.net/download/ ... .11.tar.gz (from http://ccrypt.sourceforge.net/#downloading)

When downloaded, extracted and

./configure
make CC=musl-gcc CFLAGS=-static

i.e. musl ... yields a 124K filesize.

Reading deeper and not only is ccrypt rather heavy, but also it doesn't salt i.e. gpg by comparison in effect concatenates a entered password with a random sequence to make otherwise simple/short passwords longer/more difficult to dictionary/brute-force attack. So another choice looks to be more appropriate.

A note about Fatdog's initrd. Fatdog is actually two operating system in one. Fatdog's initrd is actually its own independent CLI-only busybox-based mini operating system called "Bulldog Linux", with the proper Fatdog tacked on top of it. It is not an accident that the busybox in Fatdog's initrd is a complete busybox with almost all applets included; it is by design. In the proper Fatdog environment its only purpose is to setup Fatdog's layered filesystem and as a recovery console; but you can choose not to do that and run Bulldog by itself as a CLI operating system (run with basesfs=none and you'll see what I mean).

I do like "Bulldog Linux", with dropbear added on top and if you recompile the kernel with localyesconfig so that modules are built into the kernel (and also drop initrd into the kernel) - and that builds with only the modules your hardware uses - and I'm seeing 14MB type vmlinux (the only needed file to boot) filesize. And that's with wireless connecting also. (Ready to ssh into servers)

[SFR]

Hi all. I do not like to make a request like this, however I am having difficulty doing a pkgbuild of LLVM. I need v7.0.0 or newer to compile some other stuff. The laptop (and only machine I have) is locking up for hours during compiling.

Currently only v5.0.2 is available in Gslapt, which is quite dated - latest version is 8.0.1.

Yeah, building LLVM (or any substantial C++ app, for that matter) requires a lot of RAM, so if you have e.g. only ~4G, you need some swap as well.
Btw, in addition to normal file/partition-based swap, I'd also recommend using ZRAM swap (with a higher priority), which is faster and doesn't lock the system that much.

Code: Select all

# # Load the required kernel module:
# modprobe zram
#
# # Reserve the first free zram device:
# zramctl -f
/dev/zram0
# 
# # Create 2G zram device with zstandard compression (almost as fast as lz4 and almost as good as gzip):
# zramctl -s 2G -a zstd /dev/zram0
# 
# # Create swap in zram and activate it:
# mkswap /dev/zram0
# swapon /dev/zram0 -p 10
# 
# zramctl 
NAME       ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT
/dev/zram0 zstd            2G   4K   58B    4K       4 [SWAP]
#
# swapon
NAME              TYPE       SIZE USED PRIO
/dev/zram0        partition 2048M   0B   10
# 

To disable it:

Code: Select all

# swapoff /dev/zram0
# zramctl -r /dev/zram0

Note that the 2G figure refers to data before compression, so with zstd ratio being even ~5:1 (from my own experience), the actual amount of used RAM will be ~400M.

Also, you can modify the recipe, by adding '-j1' to make, which prolongs the compilation, but requires less RAM.

Anwyay, I just built it, so here you go: https://drive.google.com/open?id=1mfRvi ... PKfIdASMBx
MD5: 765eca3a5d569aa4f4170ec5f3005078 llvm-8.0.1-x86_64-1.txz

I downloaded the Fatdog64-802 .iso and burned it to a DVD using Burniso2cd. The DVD booted to a desktop without my intervention, but neither the mouse nor the keyboard worked. (Both are USB.)

When I chose the multisession boot option, it wouldn't boot at all.

Hard to tell, may be missing drivers and/or firmware.
But, on the other hand, the keyboard works for you in boot menu, correct?
Sometimes the same happens to me with a touchpad on another laptop, but it's really rare - perhaps it was a temporary glitch also in your case..?

<ccrypt> ==> It's 815KB. If it can be made smaller then I'll bring it in. Otherwise I'm sure there are similar others which is in the order of 50K or less (perhaps bcrypt?). Otherwise cryptsetup is already included in initrd, you can have a "secure vault" containing your keys, then open/mount it, start ssh, and close the vault again.

./configure
make CC=musl-gcc CFLAGS=-static

i.e. musl ... yields a 124K filesize.

Reading deeper and not only is ccrypt rather heavy, but also it doesn't salt i.e. gpg by comparison in effect concatenates a entered password with a random sequence to make otherwise simple/short passwords longer/more difficult to dictionary/brute-force attack. So another choice looks to be more appropriate.

Built against musl and UPX'ed it's 52K.
I also built bcrypt statically, but even UPX'ed it's 255K.
JB's idea to use some small LUKS container instead is kinda neat, actually, since cryptsetup is already there.

Greetings!

[rufwoof]

JB's idea to use some small LUKS container instead is kinda neat, actually, since cryptsetup is already there.

My upx'd ccrypt (musl) was around 57MB using --ultra-brute compression. Generally I use that ccrypt to lock down my dropbear private ssh key, so its encrypted and only briefly open for the duration of establishing a ssh connection.

Code: Select all

#!/bin/sh
cd /mnt/.ssh
/mnt/ccrypt -c db_id_rsa.cpt >db_id_rsa 
echo "#!/bin/sh" >/tmp/cleanup 
echo "sleep 20" >>/tmp/cleanup 
echo "rm /mnt/.ssh/db_id_rsa" >>/tmp/cleanup 
echo "rm /tmp/cleanup" >>/tmp/cleanuup 
chmod +x /tmp/cleanup 
/tmp/cleanup & 
chmod 0600 /mnt/.ssh/db_id_rsa 
cd /
ssh -i /mnt/.ssh/db_id_rsa user@ssh.server.host

Using a LUKS container and that requires a image file to serve as the holding container - which whilst you could set that image file to be just large enough to hold the ssh key(s), more generally you'd set that larger, perhaps 10K (possibly more). So the saving over installing/using ccrypt could be relatively small - 40K perhaps (or less), but with ccrypt installed that does open up encrypting other files relatively easily, perhaps your calendar/diary/journal ...etc. I also tried bcrypt and similarly saw larger binary size and upon reflection of my earlier comment about not being salted - for general use its probably ok as-is, enough to avoid open access to your ssh keys, diary ...etc.

Inclined to stick with my earlier suggestion of ccrypt being included, the upx suggestion knocking that down to sub 60K size is pretty good IMO. Absent that, and encryption options in Bulldog are pretty limited as-is (excepting the cryptsetup option).

Another method I use is my own pcrypt which when musl/upx'd is around 19K. That however works on a one-time-pad basis (that if truly random data is used is proven uncrackable), which in effect doubles up on the filesize of the file being encrypted and where you store the two halves physically separated. If I store my main private ssh key in pcrypt form, with one half on another ssh server that I access using a userid/password in order to scp that down and then decrypt the private ssh keyfile, then that does make it much more improbable that anyone finding the usb (with encrypted dropbear ssh private key) would be able to crack that private key. When using Bulldog that way however it makes sense to also have the full OpenSSH that supports sshfs, i.e. sshfs mount a ssh server that has the other half of all pcrypt keys for pcrypt encoded files being stored locally. But IIRC that does bloat Bulldog by around 2.5MB (sfs filesize 7.8MB fully extracted). Personally for me that's a small price.

[jake29]

Many thanks SFR, for the download and the compiling tips.

EDIT: I would appreciate anyone's thoughts on the below information and which dependencies are likely to play a role in the issue and require updating in Fatdog64-802. I personally suspect the issue is not video related, but hardware detection - the crash is triggered by cursor click.

Stable and latest Beta client for Linux frequently dropping / disconnecting video stream with error L:100. This problem is only occurring when free movement cursor is enabled. The client is 100% stable in 'cursor-locked' mode. Issue did not exist using the original (older) Shadow client in Fatdog64.

Additional context
Graphical corruption of cursor will sometimes occur seconds before the Client disconnects. The issue can be consistently reproduced by moving (travelling by clicking) around in Google Maps 'street view' mode.

Here is my 'problem' app: https://aur.archlinux.org/packages/shadow-beta

Dependencies:

Code: Select all

desktop-file-utils (desktop-file-utils-git)
freetype2 (freetype2-git, freetype2-v35, freetype2-infinality-remix, freetype2-old-hinting, freetype2-ttmetrics, freetype2-infinality, freetype2-ultimate5, freetype2-cleartype)
gcc7-libs
gconf (gconf-gtk2)
hicolor-icon-theme (hicolor-icon-theme-git)
json-c
libappindicator (libappindicator-gtk2)
libappindicator-gtk2 (libappindicator-gtk2-ubuntu)
libbsd (libbsd-git)
libcurl-compat
libcurl-gnutls
libdrm (libdrm-grate-git, libdrm-git, libdrm-amdgpu)
libnotify (libnotify-gtk2, libnotify-id-git, libnotify-id)
libsndio-61-compat
libuv (libuv-git)
libva (libva-git, intel-media-stack-bin, libva-headless)
libxss
libxtst
nss (nss-hg)
opus (opus-git)
qt5-base (qt5-base-git, qt5-base-headless)
qt5-svg (qt5-svg-git)
sdl (sdl-openglhq, sdl-nokbgrab, sdl-openglhq-nokbgrab, sdl-hg)
sdl2 (sdl2-ime-support, sdl2-rbp-bin, sdl2-nox, sdl2-hg, sdl2-hidpi-hg)
ttf-dejavu (ttf-dejavu-emojiless, ttf-dejavu-ib)

Installed in Ubuntu 19.04: (Where app is 100% stable)

Code: Select all

desktop-file-utils v0.23-4
libxft2 v2.3.2-2
gcc-8 v8.3.0-6
hicolor-icon-theme v0.17-2
json-c v012.1
libappindicator3-1 v12.10.1
libbsd0 v0.9.1-2
libcurl3-gnutls v7.64.0-2
libcurl4 v7.64.0-2
libdrm-common, libdrm-intel1, libdrm-radeon1, libdrm2 - all are v2.4.97-1
libnotify-bin, libnotify4 - both are v0.7.7
intel-media-va-driver v18.4.1
libva-drm2, libva-wayland2, libva-x11-2, libva2 - all are v2.4.0-1
libxss v1:1.2.3-1
libxtst6 v2:1.2.3-1
libnss-mdns v0.14.1-1
libnss3 v2:3.42-1
libopus v1.3-1
libqt5core5a, libqt5dbus5, libqt5designer5, libqt5gui5, libqt5help5, libqt5network5, libqt5printsupport5, libqt5sql5, libqt5svg5, libqt5test5, libqt5widgets5, libqt5xml5, python3-pyqt5 - all are v5.12.2
fonts-freefont-tff v20120503-9

EDIT2: ldd results.
Fatdog64-802: https://pastebin.com/raw/v0F1C00M
Ubuntu 19.04: https://pastebin.com/raw/rRuh4KWP

Missing in Fatdog64-802:

Code: Select all

libdatrie
liblz4
libselinux
libsystemd
libthai
libwayland-cursor
libwayland-egl
libwayland-client
com_err

libmount (installed but unused by app)
libxkbcommon (installed but unused by app)
libgssapi_krb5 (installed but unused by app)
libblkid (installed but unused by app)
libbsd (installed but unused by app)
liblzma (installed but unused by app)
libgcrypt (installed but unused by app)
libkrb5 (installed but unused by app)
libk5crypto (installed but unused by app)
krb5support (installed but unused by app)
libgpg-error (installed but unused by app)
libkeyutils (installed but unused by app)

Not used in Ubuntu: (Utilized in Fatdog64-802)

Code: Select all

libgthread
libssp

EDIT3: Fortunately my persistence has paid off. I learnt from support on discord, that 'the cursor is handled by a custom crafted SDL lib embedded with shadow client.' It turns out the env variable 'LD_PRELOAD' is correctly managed in Ubuntu by the client to use their own SDL lib, however the implementation does not work correctly in Fatdog64. By adding the env variable manually, I was able to force client to use the custom SDL lib and the difference is obvious. Client is now 100% stable in all modes where cursor is locked / client is in full-screen.

[Illutorium]

on Lubuntu: Doesn't had problem at savestate
on FatDog64: Does has problem with load savestate

[chiefengineer]

As long as I just read a lengthy cursor-handling problem thread, I thought I'd ask for any advice about this:

2 spanking new Lenovo laptops, same USB Fatdog 802 (cloned)

One of them (Intel) runs latest Firefox like a charm.
The other (AMD) boots half of Firefox, PAINTS HALF THE SCREEN
IN JAGGED BLACK, freezes the clicker (but not the cursor), and forces a hard reboot.

Both run Chrome and Seamonkey nicely, and everything else.
Have the latest GTK3 libraries, etc.

Seems like a graphics card issue...just thought I'd ask if I'm missing
something else obvious?

[dr. Dan]

@illutorium: Have you tried using the

Code: Select all

waitdev=

parameter in your grub configuration? Setting it to 3 or 5 (seconds) often solves that problem. See "My savefile is not loaded after reboot!" in the help files.

[step]

Seems like a graphics card issue...just thought I'd ask if I'm missing
something else obvious?

The Fatdog64 Live boot menu includes three entries that can help with video problems. Have you tried any of those?

[rufwoof]

Might be the same as what Step has highlighted ??? https://distro.ibiblio.org/fatdog/web/faqs/radeon.html

[Illutorium]

@illutorium: Have you tried using the

Code: Select all

waitdev=

parameter in your grub configuration? Setting it to 3 or 5 (seconds) often solves that problem. See "My savefile is not loaded after reboot!" in the help files.

Still doesn't helped.

[jake29]

@chiefengineer - A common (less than ideal) fix for Firefox GPU issues is to disable Hardware Acceleration in its settings. Also, perhaps this change (link) is related to your issue and older versions work fine?

[chiefengineer]

I commented out all three (one by one) sections in
/usr/share/X11/xorg.conf.d/20-radeon.conf
and X failed to strart in any iteration.

The "boot/radeon" selection also failed. The "really
bad graphics card problems" boot entry worked
after some screen mosaics, so I then installed GTK3 and
FF, and it worked as it should.

Unfortunately that boot option won't load my savefolder and the
boot menu is read-only.

As a side-note I also installed TOR's FF build separately which disables all kinds of extensions/plugins and ran it under a user I created. Same result...screen tearing
and freezing.

Edited one day later:
Created a new savefile under problematic radeon boot choice...firefox
worked nicely UNTIL reboot using savefile...couldn't even uncheck the default browser box before hard reboot required. On this machine FF is a close to a virus as I care to experience.

I zipped/copied/replaced the working X11 (from etc and usr/share) folders into my save folder and booted into it.

Things LOOKED almost normal! Then the clicker froze again where only
Firefox would shut, and nothing else was active.

I suspect Firefox is doing something (like freezing the system while trying to
upgrade which is unstoppable) and killing X...thus the clicker APPEARS to
not work when in fact it is clicking on appearances-only.

One of the ways FF used to fail was it would arrive visible with the screen behind
it black/gone.

I guess a try without acceleration might be next...I must confess if everything else works but
Firefox I really can't get mad over Radeon.

Edited: after creating second savefile under problematic screen driver boot choice FF 68 and below presented same freezes (not initially, only after savefile created and reboot). Curiously, without use of savefile on this machine clicker dies after being idle for just a few minutes...maybe related? Perhaps some sort of power module interrupt of something? FF (and not anything else) acts like a virus on this machine...abandoning efforts.

[ozsouth]

@chiefengineer - I had video & shutdown issues on a new AMD laptop (HP14-CM0009AU - AMD e2-9000e cpu radeon r2) with any kernel 4.19 - 5.1 inclusive. kernel 5.2 better but not perfect, & fatdog's 4.18.12 kernel fine. Suggest trying that or my 4.14 series before giving up.

[chiefengineer]

and if I didn't use a savefile...after a few minutes of
inactivity. Now, for the first time (on a happily stable
install) I enabled the screensaver.

It worked...and when it came back the clicker did not
work even though the mouse movement brought life back.
Also the top couple cm's of the screen was "torn off".

Deep dark kernel issue with X...but I am not rolling back
anything so far. I'm just compiling things for this machine
and cruising forward.

FYI

[ozsouth]

@chiefengineer - absolutely your choice. I wanted to point out for others benefit also that kernel 4.14 is a longterm supported one, until 2024, meaning it gets bugfixes & security updates till then. Future new drivers would need to be compiled for it.

[ICPUG]

Hello

It has been a long time since I have posted on the forums but I have still been an avid Puppy user in the meantime.

I have been using Lighthouse Puppy 503g for most of my work but, because of more and more web pages not being rendered by the Opera browser of that era (due to security protocol changes), I now have to use something more modern.

I have recently installed Fatdog64-802 (frugally on my hard drive) and it looks as if it could be what I am looking for. Admittedly, looking at the start of this thread where ‘Changes from version 701’ showed Wine mentioned, I thought Wine was built in to Fatdog – one of my needs. Subsequent investigations shows this is not the case. However, I see 3 different versions are available as an sfs or can be installed via gslapt. My first query concerns these different versions. I would instinctively choose the latest version (4.0) but wonder why the previous versions are still there. Are there any potential problems of Wine version 4 I need to be aware of?

I would like to try and emulate the appearance of Lighthouse 503g if I can and so I need something like the Pwidgets and, possibly, the Wbar. Having read the Fatdog FAQ I thought I would first try using the pwidgets-2.5.8-x86-64.pet in Fatdog. Following the FAQ, I right clicked the .pet file in Rox and selected ‘Convert to new package format’. Nothing happened!

Looking around I found in /user/bin ‘pet2txz’ and, without knowing how to use this program, I thought I would try it. I used a terminal and traversed to the directory of my pet file and gave the command:

pet2txv pwidgets-2.5.8-x86-64.pet

After first showing a checksum this resulted in the error message:
ERROR: Package extension .archive is not supported

Any thoughts on why I cannot convert the .pet file?

Of course, I am going to find some programs in Lighthouse that are not in Fatdog. Because I always use frugal installs, I used Isomaster in Lighthouse to extract the files from an .iso file. Is there anything in Fatdog to do this task?

Thanks for your help.

[step]

I think the three sfs versions for wine simply reflect what was the latest version at the time Fatdog64 800, 801 and 802 were released or thereabouts. Personally I use wine 4.0 and haven't had a single problem with it. But I'm not a heavy wine user. I think jake29 is using and earlier version, perhaps as early as wine 2.x, due to some issues with his graphics setup. Hopefully he'll notice your post and chime in.

If dir2txz didn't work for you, you can try breaking down the steps as follows:

unpack the pet into a directory using uextract.
Click the blue question mark icon (FAQ) on the desktop. When Fatdog Help opens scroll down then click the link labelled "How can I make a new package?". Go directly to step 3 and follow the instructions to repack the unpacked directory into a txz file, which you can then install with gslapt (GUI) or slapt-get (terminal).

If you prefer an sfs to a package, you can do that too. Instead of clicking the previous link, click the one immediately under it, labelled "How can I make a new SFS package?" and follow the directions.

In Fatdog you can open an iso file as a read-only folder just by clicking its icon in rox. It will be mounted. Click the icon again to unmount it and close the folder.

[dr. Dan]

wbar is available in the 700 contrib repository. It may not work in 802. https://distro.ibiblio.org/fatdog/contrib/packages/700/

Cairo-dock is available in the 720 contrib repository, and does work in 802. https://distro.ibiblio.org/fatdog/contrib/packages/720/

Dan

[ICPUG]

Thank you step and dr.Dan for the very helpful answers to all my questions. I shall now spend some time trying out the suggestions to add the extra Lighthouse Pup features to my Fatdog.

ICPUG