Fatdog64-810 Final [17 Jan 2020]

Message

step · #141 Post by **step** » Sun 19 Jan 2020, 20:04

mavrothal wrote: Latter: Anther little thing (that may be mbp-specific) is that screen brightness is not "quite" remembered through reboots, but as soon as you press a brightness adjustment button starts to adjust from the last-set level. Maybe an addition to rc.platform could fix that

That is by design. The brightness level is a user-specific setting -- different users adjust brightness differently. Therefore the setting is stored in the user's home folder only after the user has pressed a brightness key.

mavrothal · #142 Post by **mavrothal** » Sun 19 Jan 2020, 21:00

step wrote:
mavrothal wrote: Latter: Anther little thing (that may be mbp-specific) is that screen brightness is not "quite" remembered through reboots, but as soon as you press a brightness adjustment button starts to adjust from the last-set level. Maybe an addition to rc.platform could fix that
That is by design. The brightness level is a user-specific setting -- different users adjust brightness differently. Therefore the setting is stored in the user's home folder only after the user has pressed a brightness key.

Maybe I miss something but if a user sets a level different than the default and indeed this is stored in $HOME, why is it ignored next time the said user logs in/boots up? Or is it assumed that a different person uses the computer with the same credentials?
Anyway, as I said minor annoyances.

SFR · #143 Post by **SFR** » Sun 19 Jan 2020, 21:33

@Mavrothal: the brightness is preserved only when you use the Control Panel -> Desktop -> Fatdog64 Laptop Screen Brightness applet, not the dedicated buttons/keys.

Greetings!

mavrothal · #144 Post by **mavrothal** » Mon 20 Jan 2020, 05:29

SFR wrote:@Mavrothal: the brightness is preserved only when you use the Control Panel -> Desktop -> Fatdog64 Laptop Screen Brightness applet, not the dedicated buttons/keys.

I'm afraid not.
The slider still shows the previous setting but the brightness is at 100%
I think the issue is because if you boot as root brightness_set.sh looks first at /etc/brightness.conf and so it ignores $HOME/.fatdog/brightness.conf
If the case, maybe this should be reversed and look in /etc/ only in the absence of the $HOME entry or maybe amend the scripts so when they are called by root also write the etc config file
Latter: Hmm, I can not see anywhere $HOME/.fatdog/brightness.conf

jamesbond · #145 Post by **jamesbond** » Mon 20 Jan 2020, 10:25

@LateAdopter: depending on how you install your own custom kernel, if the /etc/modules are created in your savefile/savedir, you can delete it from there so that the underlying /etc/modules from the basesfs will show up again. Run "aufs_reval" from terminal after you delete it from your savedir/savefolder.

@artsown: Another convert! Yay!

@mavrothal, thanks for the updated facetimehd module.

Booting from an ext4 USB stick with grub2 from with a not-yet-existing savefolder you don't

I cannot reproduce this on general PC. I checked rc.platform doesn't have code to touch PuppyPin (which is where the configuration on desktop icons are stored). So I really wonder who modifies PuppyPin on first boot ?

Brightness adjustment

The brightness adjustments, no matter how you do it - from the shortcut keys or from control panel is always stored in /etc/brightness.conf (if running as root).

But this setting is NOT restored when rebooting; until you finally make the brightness changes through using the control panel. When you do that, control panel creates an entry in $HOME/Startup/restore-brightness.sh which simply run "brightness-set restore" whenever X desktop is started. "brightness-set restore" will restore the brightness from /etc/brightness.conf (if you are root).

In other word, as soon as you make changes using control panel, the brightness level will be restored at boot - including if you change the brightness using keys, after that.

Well that's how it is supposed to work anyway, if it doesn't, then something else is wrong. Either $HOME/Startup/restore-brightness.sh is not created/not executed, or /etc/brightness.conf isn't created properly.

mavrothal · #146 Post by **mavrothal** » Mon 20 Jan 2020, 10:58

jamesbond wrote: Well that's how it is supposed to work anyway, if it doesn't, then something else is wrong. Either $HOME/Startup/restore-brightness.sh is not created/not executed, or /etc/brightness.conf isn't created properly.

/etc/brightness.conf has the correct setting but $HOME/Startup/restore-brightness.sh is not created. Which is the script that should create it?

jamesbond · #147 Post by **jamesbond** » Mon 20 Jan 2020, 11:06

mavrothal wrote:/etc/brightness.conf has the correct setting but $HOME/Startup/restore-brightness.sh is not created. Which is the script that should create it?

That should be /usr/bin/fatdog-brightness.sh line 108.

mavrothal · #148 Post by **mavrothal** » Mon 20 Jan 2020, 11:33

jamesbond wrote:
mavrothal wrote:/etc/brightness.conf has the correct setting but $HOME/Startup/restore-brightness.sh is not created. Which is the script that should create it?
That should be /usr/bin/fatdog-brightness.sh line 108.

wow, 2 problems at once
Apparently copying from the first stick to the second I copied the FD800 files instead of the 810

, hence the missing desktop icon and brightness issue.
(To my desperate defence

) maybe FT version should be more obvious

jamesbond · #149 Post by **jamesbond** » Mon 20 Jan 2020, 14:29

LOL

So all is good now?

The ISO now includes "VERSION" info. That should help

recobayu · #150 Post by **recobayu** » Tue 21 Jan 2020, 03:10

I am very like the rox filer's behavior in this fatdog.
We can search file by typing the name keyword directly.
Is it possible to make this rox filer in puppy linux?

I look at https://github.com/jun7/rox-filer and try to compile it my self. But it still different with rox filer in fatdog. It also show Running as user 'root' in the top of window below toolbar. My png folder also show black.
How to compile it so it is equal to this fatdog?
Thank you.

jamesbond · #151 Post by **jamesbond** » Tue 21 Jan 2020, 03:47

recobayu wrote:I am very like the rox filer's behavior in this fatdog.
We can search file by typing the name keyword directly.
Is it possible to make this rox filer in puppy linux?

That's really up to Woof-CE guys.

I look at https://github.com/jun7/rox-filer and try to compile it my self. But it still different with rox filer in fatdog. It also show Running as user 'root' in the top of

Right-click ROX windows, choose "Option", then on then look at the very bottom - there is an option settings to "Hide message running as root".

How to compile it so it is equal to this fatdog?
Thank you.

If you're running Fatdog, load devx and check /usr/src/pkgbuild/source/rox-filer-jun7-2020.01-x86_64-1.tar.gz and read this (scroll to the bottom, read method 5, using pkgbuild).

If you don't run Fatdog then download this and then read this.

mavrothal · #152 Post by **mavrothal** » Tue 21 Jan 2020, 10:11

jamesbond wrote: So all is good now?

Pretty much! I'm afraid FD becomes too mature for this forum

However, I manage to get in trouble with the quick-setup icon that in another machine installation did not want to go away!

I interupted the process in the middle and finished the setup through the individual apps and the icon is still there (I actually manually delete it after few reboots).
I guess it stays there till it runs fully and successfully but maybe add an explicit remove from desktop or something option if its "canceled"

artsown · #153 Post by **artsown** » Tue 21 Jan 2020, 12:28

The Rox pinboard has a "Single-click to open" option that's checked by
default that can cause problems for users with certain disabilities. They
often double (or multiple) click, resulting in multiple activation of
applications.

I found that unchecking that option works very well to prevent multiple
instances of applications when clicking their desktop icons. In fact, I
haven't yet been able to get multiple instances.

To get at the setting, I right click on the text under any desktop icon,
then select Rox-filer Options, then pinboard. then pinboard behavior.

Art

mavrothal · #154 Post by **mavrothal** » Tue 21 Jan 2020, 13:57

Looking at the FD800 thread I gathered that Skype does not play well with FatDog. Any chance that you'll take another crack at it with 810?

Later: Tried a slackware version from here and it pretty much works (using a Gtk3 SFS I had made for FD800). No complains about root and audio video are good too. Menus and panel integration may need some work but in general pretty functional (sorry sage)
Later-later: Just installing Gtk3 (and the pulled dependencies) with the FD810 package manager is sufficient for the above skype package.

Sage · #155 Post by **Sage** » Tue 21 Jan 2020, 14:07

Skype does not play well with FatDog

- that's the good news! They sold out to Redmond several years ago. Why not try some of the others like Ekiga & co. Puppy used to have a selection of IP video phone applications. There was an expert on this Forum back then - will need a lot of patience to SEARCH, though.
Later: I didn't say it doesn't work! The further you get from Redmond the safer you'll be...

LateAdopter · #156 Post by **LateAdopter** » Fri 24 Jan 2020, 13:40

LateAdopter wrote:
SFR wrote:Anyway, there's k5.4.7 in the repo, so maybe you could give it a try.
Hello SFR
I think 5.4.3 is as far as AUFS gets so far. I did try the Fatdog 5.4.7, also a 5.4.7 and 5.4.12 that I built, on 810 beta. None of them would boot, and there was no previous-messages from the failed boot. So I guess the layered filesystem was broken.

There is an aufs5.4.3 branch and it doesn't have a + at the end. My 5.4.3 kernel built with that branch boots OK.

Next time I build a kernel I can delete the /etc/modules directory and see what happens.

I have built a 5.4.14 kernel using the current aufs5.4 branch. It boots my Athlon 3000G OK with Fatdog 810 and Bionicpup64

There is a commit in the 5.4.14 changelog that is specific to Raven2.

I also applied the patches that add current and voltage reporting to k10temp. That is working too.

LateAdopter · #157 Post by **LateAdopter** » Sat 25 Jan 2020, 12:23

hello jamesbond & kirk
Is there something unusual about the way cpufreq and the ondemand governor are conigured in Fatdog 810?

The ondemand governor is very keen to jump to P0, more like the performance governor. The up_threshold is still the default 95, but it doesn't behave like that. I'm using the same kernel as I use with Bionicpup64 where the ondemand governor behaves normally.

don570 · #158 Post by **don570** » Sat 25 Jan 2020, 20:16

gpg files can be opened by uextract
http://www.murga-linux.com/puppy/viewto ... 57#1048548

don570 wrote:
Code: Select all
tar czvpf - file1.txt file2.pdf file3.jpg | gpg --symmetric --cipher-algo aes256 -o myarchive.tar.gz.gpg
Just FYI: when you right-click a .gpg file, UExtract doesn't show up (ROX recognizes it as generic application/octet-stream), but it's possible to decrypt it from CLI (uextract file.gpg).

stefan21 · #159 Post by **stefan21** » Sun 26 Jan 2020, 15:42

From: http://www.murga-linux.com/puppy/viewtopic.php?t=117923

jamesbond,

thank you for taking your time an jumping in.

Here's what I found out so far:

- changing in FD system menu under Fatdog64 local to (at least) German, seems to break the Fatdog64 standard sound device gui. Only bluetooth shows up. Changing back to locals US make every device visuable again.

- choosing the default sound device before changing the locals seems to work.

- No luck with FF ESR releases and sound. Sound is working with FF latest release.

It seems I'm having issues with my setup in general, but I'm not quite sure about this. I'm using a 14 GB USB-stick with two partitions. First partition is formatted as ext4 an holds puppy. This is the boot partition configured with an mbr on the stick and syslinux in /boot. The second partition is formatted as f2fs and also as f2fs luks-encrypted. Puppy is configured to use this partition as save directory. The boot command is

append rootfstype=ramfs savefile=direct:uuid:myuuid:/fd64save:dmcrypt waitdev=5

In the past I had no problems with this configuration. It was running stable I had no issues. With upgrading to FD 810 I changed also the USB-stick. The old one was about 3 years old. Maybe the new one is some kind of lossy. I'll try another one form the same manufactorer and report.

OR do you recommend another setup in general? I.e. second partition formatted with another filesystem? Or/and using another luks file-system?

Thank's for any recommendation.

regards,
stefan

SFR · #160 Post by **SFR** » Mon 27 Jan 2020, 09:47

stefan21 wrote:- changing in FD system menu under Fatdog64 local to (at least) German, seems to break the Fatdog64 standard sound device gui. Only bluetooth shows up. Changing back to locals US make every device visuable again.

Confirmed, thanks. To fix this, open /usr/bin/fatdog-default-soundcard.sh and modify line 28 from:

Code: Select all

SOUNDCARDS=$(aplay -l | awk '$1~/card/ { print """ $0 "" " """ $0 """ }')

to:

Code: Select all

SOUNDCARDS=$(LANG=C aplay -l | awk '$1~/card/ { print """ $0 "" " """ $0 """ }')

EDIT: alternatively download and install fatdog-hotfixes package (see 2nd post for details).

Greetings!

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Fatdog64-810 Final [17 Jan 2020]

A Rox-filer pinboard option

gpg files can be opened by uextract

http://www.murga-linux.com/puppy/viewtopic.php?t=117923