Fatdog64-810 Final [17 Jan 2020]

[peterw]

Just a note for anyone that gets affected to say that when booting Fatdog or Puppy on a Chrome book you may find that it can't because of a RAM memory problem. The answer is to add the comment "mem=1950m" to your boot manager as below.

menuentry "Fatdog-800 (sda1/fatdog-800)" {
set root=(hd0,1)
linux /fatdog-800/vmlinuz mem=1950m pmedia=atahd psubdir=fatdog-800
initrd /fatdog-800/initrd
}

That is for a grub2 boot manager and the same idea works with grub4dos:

title Fatdog64 (sda1/fatdog)
uuid 735cd2a0-7ef5-4981-bce4-c9c695a1c82f
kernel /fatdog/vmlinuz mem=1950m psubdir=fatdog pmedia=atahd pfix=fsck
initrd /fatdog/initrd

Apparently, after Puppy or Fatdog boots it will then use all the RAM you have and will not be limited to 1950 MB.

There is a UEFI full ROM version that you can get from Mrchromebox and I am not certain but I suspect that it will have cured the issue.

[peterw]

I am trying to help a member out over here. http://murga-linux.com/puppy/viewtopic. ... 7&start=30. And he has a Chrome book Acer R11 CYAN with a full UEFI ROM. His issue is with sound and it has a Maxim 98090 chip. This came up in Fatdog earlier with reports of burnt out speakers when jd7654 tried compiling his own and vtpup also tryinghttp://45.33.15.200/puppy/viewtopic.php ... 1b694b875e.

Now, I don't believe prell is too worried what flavour of Puppy/Fatdog he uses. In Bionic and other Puppies I see that "CONFIG_SND_SOC is not set" in the kernel which, I think gives the option to include the driver for that maxim 98090 and others. Through ignorance, I can't find the Dotconfig for Fatdog and don't know if that CONFIG setting is the same. Can someone please advise?

If it is not included, can someone point me in the right direction as to how to compile a driver for the kernel or do I have to recompile the whole kernel? And then do what?

Apart from trying to help, tasks such as these help increase my understanding which is not brilliant.

[SFR]

Minor glitch in the beta. When htop.desktop is dragged out to the desktop
and used, two terminals appear.

Thanks, fixed.
For the time being you can edit this line in /usr/share/applications/htop.desktop:

Code: Select all

Terminal=true

Just change it to false.
___________

I can't find the Dotconfig for Fatdog

Try:

Code: Select all

zgrep 'CONFIG_SND_SOC' /proc/config.gz

Greetings!

[peterw]

Thanks for that SFR. On my version of Fatdog I see "CONFIG_SND_SOC is not set" and so the option has not been set for that max 98090 chip.

I have since discovered that kernel 5.2 was a major upgrade for sound on Linux.
"Linux 5.2 includes Sound Open Firmware (SOF) project, which has been created to reduce firmware issues by providing an open source platform to create open source firmware for audio DSPs. The SOF project is backed by Intel and Google. This will enable users to have open source firmware, personalize it, and also use the power of the DSP processors in their sound cards in imaginative ways."
So in the future that should solve some problems.

[don570]

linux kernel news...

http://lkml.iu.edu/hypermail/linux/kern ... 04661.html

Last week, Linux kernel developer Greg Kroah-Hartman announced the 18th maintenance update (5.3.18 ) for the Linux 5.3 kernel series. This version has changed a total of 59 files, inserting 369 items / removing 329 items. In addition, developers point out that this will be the last maintenance update for the Linux 5.3 kernel series. As Linux Kernel 5.3 arrives in EoL, users are advised to update to Linux Kernel 5.4 in time to obtain comprehensive support and guarantee.
Greg Kroah-Hartman stated in the email announcement that after the support of Linux Kernel 5.3 expires, he will no longer receive maintenance updates for critical security issues or bugs, and interested friends can read the 5.3.y Git Tree .

Both ordinary Linux users and distribution vendors, once again, strongly recommend that you upgrade your OS to the latest Linux 5.4 kernel series. If this is not currently possible, please update to at least 5.3.18.

_______________________________________

[don570]

There is more recent version of FLTK
FLTK-1.3.5 [released 3rd March 2019]
https://www.fltk.org/articles.php?L825
____________________________________

[rufwoof]

linux kernel news...

http://lkml.iu.edu/hypermail/linux/kern ... 04661.html

Last week, Linux kernel developer Greg Kroah-Hartman announced the 18th maintenance update (5.3.18 ) for the Linux 5.3 kernel series. This version has changed a total of 59 files, inserting 369 items / removing 329 items. In addition, developers point out that this will be the last maintenance update for the Linux 5.3 kernel series. As Linux Kernel 5.3 arrives in EoL, users are advised to update to Linux Kernel 5.4 in time to obtain comprehensive support and guarantee.
Greg Kroah-Hartman stated in the email announcement that after the support of Linux Kernel 5.3 expires, he will no longer receive maintenance updates for critical security issues or bugs, and interested friends can read the 5.3.y Git Tree .

Both ordinary Linux users and distribution vendors, once again, strongly recommend that you upgrade your OS to the latest Linux 5.4 kernel series. If this is not currently possible, please update to at least 5.3.18.

_______________________________________

Thanks

https://www.kernel.org/category/releases.html
For my cutdown Fatdog's Bulldog, I'm tracking 4.14 which as the above link indicates has a projected EOL of 2024. I tend to recompile that for each point release and .160 so far has been working very well for me. Around a 40 minute build time for my bespoke kernel .config on my 2 core laptop.

[don570]

stable kernels - They list 5.3.18 as EOL
https://www.kernel.org/
_______________________________

[Atle]

Downloaded the iso to a Windows 10 infected Samsung laptop.

Extracted the iso in Win10 and ran LICK. Followed the instructions and it all came out very nice in less than 5 minutes including the reboot.

This "first time user" app never came up and that is ok with me as i just need to change the keyboard to my locale and enable the "tap to click".

It looks perfectly good to me this far. Just works...

ADDED

Installed Firefox and sound did not work, despite it works on the system(VLC etc).It works in the other browsers like Firefox 52, etc.

so the latest version of Firefox does not produce sound then on this hardware

https://www.cnet.com/products/samsung-a ... 00-gb-hdd/

[jamesbond]

@Atle:
1. Quick-setup no longer runs automatically. You must launch it by clicking at the desktop icon, or from control panel.

2. Firefox: How do you install it, and how do you launch it?
Unlike earlier Fatdogs, where "apulse" is installed in the system path, the 810 beta (and forward) have apulse installed in a private location (just like the rest of Puppies), and you will need to use "apulse firefox-spot" (or "apulse firefox") to launch it with sound.

If you download Firefox using the latest Firefox downloader from 810beta, this should already been taken care of; but if you use older copies of firefox downloaded on older Fatdogs (or if you download manually), the firefox.desktop file needs to be updated to account for this.

Reason for the change: the "apulse" library doesn't always play well with other software. I have a (closed) software that just locks up when apulse is there. So the need for the compromise: apulse is still built-in, but you need to prefix the program with "apulse" when launching it to make it work.

@don570: thanks, fltk-1.3.5 is now in the repo and will be in the basesfs on next release.

@peterw: we have other kernels that CONFIG_SND_SOC enabled. You may want to try that (anything newer than 4.19.24 should have it, I think).

Happy New Year everyone.

We aimed to make the 810 final release before New Year, but all of us got busy in between. So the next release will be on next year - hopefully not too far off.

[s243a]

I forget. How do I set the time off the internet?

[jamesbond]

I forget. How do I set the time off the internet?

If you want to sync once:

Code: Select all

ntpd -nqp pool.ntp.org

If you want to sync continously

Code: Select all

ntpd -p pool.ntp.org

"ntpd" is a busybox applet; if your busybox doesn't have it then you're SOL. (There are other, "full" version of ntp client but I haven't used those as the one from busybox is already excellent).

[s243a]

I forget. How do I set the time off the internet?

If you want to sync once:

Code: Select all

ntpd -nqp pool.ntp.org

If you want to sync continously

Code: Select all

ntpd -p pool.ntp.org

"ntpd" is a busybox applet; if your busybox doesn't have it then you're SOL. (There are other, "full" version of ntp client but I haven't used those as the one from busybox is already excellent).

Thankyou. BTW, if the time is off it breaks ssl. This means that your install chrome browser script won't work if the time is wrong. Perhaps the download chrome script could be modified so that if the download fails, it does a one-time sync of the clock and tries again.

This however, won't stop the annoying errors that seamonkey gives about invalid ssl certificates. Maybe the first time the browser runs a pop-up could be created where the user can choose to either set the time or sync it from the internet.

[s243a]

Has anyone tried to port PupMenu-6.2.1 to fatdog64. The menu's don't seem to automatically update when I make a change.

Note: I tested this with virtual-box. I'll test it for a few more applications to verify the issue.

[s243a]

@Atle:
1. Quick-setup no longer runs automatically. You must launch it by clicking at the desktop icon, or from control panel.

Is this intentional? It would explain the time issue that I note in my previous post. If intentional, I will note that it will make fatdog64 less user-friendly...at least for new users.

[jamesbond]

Has anyone tried to port PupMenu-6.2.1 to fatdog64. The menu's don't seem to automatically update when I make a change.

Yeah, you need to restart the desktop to see the menu changes.

This is a known problem with lxqt-panel (its menu refresh is inconsistent) but we have come up with a Fatdog-only workaround (a patch to lxqt-panel). The workaround is to touch a certain "special" file as a command for lxqt-panel to refresh its menus. Since radky built the app for Puppy, he probably doesn't know about this workaround.

@Atle:
1. Quick-setup no longer runs automatically. You must launch it by clicking at the desktop icon, or from control panel.

Is this intentional?

Yes it is intentional.

It would explain the time issue that I note in my previous post.

Sorry, I don't get it. What does the running/not-running "Quick-Setup" has to do with your system time being wrong?

If intentional, I will note that it will make fatdog64 less user-friendly...at least for new users.

There are always pros and cons. The "Quick-setup" was formerly known as "firstrun-wizard". The former behavious of this "initial-setup" prompt is like this: it runs __EXACTLY ONCE__ when you boot with a savefile/savedir for the very first time. Unlike Puppy, this "initial-setup" prompt does __NOT__ run when you boot __without__ savefile/savedir (this was by choice).

Once the "initial-setup" has been run, it will self-destruct and will __NEVER__ run again if you use the same savefile/savedir. There is no way to trigger it again, even if you happen to know its filename and run it from terminal (it will just quit).

I have received feedback that sometimes people miss this initial setup dialog, accidentally press "Quit" with the hope of running it later, etc. And they can't. Even though all the "setup items" in the initial setup are actually part of the Control Panel's applets; the feedback I have received is that it is good to have a "wizard" that runs through the most-often configuration items.

With this in mind, I removed the "self-destruct" mechanism and the script can be run multiple times, as needed. The downside of being able to be run multiple times, of course, means it will also run at every single __boot__, if it still being used as a "firstrun-wizard". Hence, I removed the "first-run functionality", renamed it as "quick-setup", and have it as a prominent entry in the desktop where people can choose to run it whenever they like it. Once people are satisfied, they can freely choose to delete the icon from the desktop. The quick-setup will still be accessible from the Control Panel.

You may say it is less friendly not to be prompted at boot; I would say that it is less friendly to be prompted and having to answer a prompt when I don't need or want to setup anything (on a throwaway session-less boot, for example); or being prompted at inappropriate time and can't recall the prompt again once it has been dismissed. Having the Quick-Setup icon prominently displayed on desktop that can be used multiple time is a compromise.

[s243a]

Has anyone tried to port PupMenu-6.2.1 to fatdog64. The menu's don't seem to automatically update when I make a change.

Yeah, you need to restart the desktop to see the menu changes.

This is a known problem with lxqt-panel (its menu refresh is inconsistent) but we have come up with a Fatdog-only workaround (a patch to lxqt-panel). The workaround is to touch a certain "special" file as a command for lxqt-panel to refresh its menus. Since radky built the app for Puppy, he probably doesn't know about this workaround.

I hope that radky will include this workaround in the next release

@Atle:
1. Quick-setup no longer runs automatically. You must launch it by clicking at the desktop icon, or from control panel.

Is this intentional?

Yes it is intentional.

cool.

It would explain the time issue that I note in my previous post.

Sorry, I don't get it. What does the running/not-running "Quick-Setup" has to do with your system time being wrong?

The first run wizard gives you the opportunity to set the time correctly. If one doesn't do this then the scripts to download and install a browser might not work and also the browsers won't work properly for https sites. You'll get false (and scary) warnings about invalid certificates.

If intentional, I will note that it will make fatdog64 less user-friendly...at least for new users.

There are always pros and cons. The "Quick-setup" was formerly known as "firstrun-wizard". The former behavious of this "initial-setup" prompt is like this: it runs __EXACTLY ONCE__ when you boot with a savefile/savedir for the very first time. Unlike Puppy, this "initial-setup" prompt does __NOT__ run when you boot __without__ savefile/savedir (this was by choice).

Once the "initial-setup" has been run, it will self-destruct and will __NEVER__ run again if you use the same savefile/savedir. There is no way to trigger it again, even if you happen to know its filename and run it from terminal (it will just quit).

I have received feedback that sometimes people miss this initial setup dialog, accidentally press "Quit" with the hope of running it later, etc. And they can't. Even though all the "setup items" in the initial setup are actually part of the Control Panel's applets; the feedback I have received is that it is good to have a "wizard" that runs through the most-often configuration items.

With this in mind, I removed the "self-destruct" mechanism and the script can be run multiple times, as needed. The downside of being able to be run multiple times, of course, means it will also run at every single __boot__, if it still being used as a "firstrun-wizard". Hence, I removed the "first-run functionality", renamed it as "quick-setup", and have it as a prominent entry in the desktop where people can choose to run it whenever they like it. Once people are satisfied, they can freely choose to delete the icon from the desktop. The quick-setup will still be accessible from the Control Panel.

You may say it is less friendly not to be prompted at boot; I would say that it is less friendly to be prompted and having to answer a prompt when I don't need or want to setup anything (on a throwaway session-less boot, for example); or being prompted at inappropriate time and can't recall the prompt again once it has been dismissed. Having the Quick-Setup icon prominently displayed on desktop that can be used multiple time is a compromise.

I agree that you should be able to run this script again (...or alternatively do similar things in other programs) via menu options or in the control panel. I'm just suggesting that if someone doesn't know that the correct time is required for ssl to work than fatdog64 might not work for them and they might not know why.

At least with the download/install browser scripts we could ask people to either set the time (or sync with a time server) if the download fails. For the browser, I'm not sure what the best approach is. People might complain if one automatically connects to a time server but without doing this I don't know how one would know that the time is wrong.

[s243a]

On another note, It would be nice if the ISO had some kind of file in it (maybe a readme) that simply give the version of fatdog64. I have an old cd I forgot to label and don't feel like booting it up at the moment. I'm guessing that it was the previous version of fatdog64, so I'll write that on the DVD.

Also, I notice that on puppy pmount tells you how much free space is available on the drive. Is there a similar utility on fatdog64? The fatdog version of pmount doesn't seem to do this.

[SFR]

Also, I notice that on puppy pmount tells you how much free space is available on the drive. Is there a similar utility on fatdog64? The fatdog version of pmount doesn't seem to do this.

Yes, right click any drive icon -> Disk Usage.
I've also been using the attached script for years, it shows free space in the tooltip of each mounted drive.

Greetings!

[step]

Adding to jamesbond's answer about setting time from the internet, you can also enable the time update service from Control Panel > System > Manage Servers and Services, scroll down to the ntpd service lines and enable (or run once) one of the two services.