Fatdog64-900 Alpha and Fatdog64-814 [04 July 2023]

[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 are still okay. Thank you.
___________

Fatdog64-900 Alpha released on 4 July 2023.
Fatdog64-814 Final released on 4 July 2023.

The Fatdog team is pleased to announce the simultaneous release of Fatdog 900 Alpha and Fatdog 814 Final.

The long awaited Fatdog64-900 Alpha is the focus of this release. It is the next generation Fatdog64, a new foundation based on LFS 11.3. Everything is new: compiler (gcc 12.2.0), glibc (2.37) and almost everything else is updated.

The GTK3 graphical toolkit is now built into the base system, along with GTK2 for older applications and Qt5, which have been Fatdog's primary UI toolkits so far. Many old GTK2 applications are updated to their GTK3 counterpart, offering new features. A new default theme is applied (Adwaita) to both GTK2 and GTK3 so that all GTK applications look similar regardless of their toolkit version. Even the Qt5 Adwaita theme is included for consistency, if needed. To complete its fresh new look, Fatdog64 features the first desktop background update in the last nine years (since Fatdog64 700).

Despite all these new changes, Fatdog64 continues its tradition of "if it ain't broken, don't fix it". Its internal architecture remains the same. Existing users and power users should feel right at home with the new series.

Don't let the 'alpha' label scare you. As it's always the case with the Fatdog developers' "eat-own-dog-food" philosophy, the team has been using 900 Alpha for months (two months in this case), fixing any major bugs that were found. That doesn't meant that this release is be completely bug-free either -- that's why we call it an 'alpha' release.

However, if you are not the adventurous kind, we also release Fatdog64-814 Final at the same time. Fatdog64-814 Final is the swansong of the 800 series. It contains very minor changes since 813 release along with some bug fixes. This is the last version of Fatdog64 800 series that we have used internally, before we finally moved over to 900 Alpha. There will be no further 800 releases after 814, and we will __NOT__ be fixing any more bugs for it, unless these bugs can also be reproduced in the 900 series. It features the same kernel (5.19.17) as the 900 Alpha release.

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

Fatdog64-900 Alpha changelist from 813: 813 announcement

Updates:

• Full system rebuild with major package updates.

• Linux Kernel 5.19.17 (same as Final 814 release)

• gcc 12.2.0

• glibc 2.37

• eudev 3.2.11

• Glib-2.74.5

• GTK+ 2.24.33

• GTK+ 3.24.36

• Qt 5.15.8

• Xorg-21.1.8

• Mesa-22.3.7

• xf86-video-amdgpu-23.0.0

• xf86-video-ati-19.1.0

• xf86-video-intel-2023.02

• ALSA 1.2.8

• libinput 1.22.1

• libgcrypt 1.10.1

• VLC-3.0.18

• ffmpeg 5.1.2

• CUPS 2.4.2

• LibreOffice 7.5.2.2

• OpenSSL 3.0.8

• LxQt Panel Qt5 1.3.0

• Seamonkey 2.53.15

• Bluez 5.66

• Wine 8.6 supporting 32-bit and 64-bit Windows applications

• SMB Browser 2.2.2

• Various system tools updates

• Hundreds of other package upgrades, some GTK2 apps replaced with GTK3 version

New Features:

• xscreenshot now supports copying to clipboard. Press Ctrl-Print to activate

• dconf gsettings backend to enable application settings persistence in evince, etc

• touchegg - convert multi-touch gesture to actions

• All changes listed in 814 as well

Known Issues:

• Suspend/resume does not always work with certain machines.

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

Fatdog64-814 Final changelist from 813: 813 announcement

Updates:

• Linux-5.19.17, low-latency, 1000Hz, dynamic preemption

• Microcode as of 2022.10.09

• tzdata 2022.e

• iptables 1.8.8 with nftables support

• Bluetooth Manager fixes

• vlc-3.0.18

• rox-jun7 2022.12

• apfs-fuse 2023.03

• pfilesearch 2.3

• UExtract 4.11

• Avidemux 2.8.1

• mdview 2023.04

• yad_gtk2 0.42.78

• SMB Browser 2.2.2

New Features:

• fzf is now built-in

• geany-themes is now built-in

• Apply LFS 11.3 patch to recognise ext4 filesystems created by newer e2fsprogs

• Add DJVU thumbnailer for ROX

• fatdog-drive-mounter.sh: support UDF labels, add support to mount by label

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

Please do not post support questions in this thread. Instead create a separate thread for your support question. This thread is for comments, feedback, etc related to this specific release.

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

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.

Downloads:

Get the Fatdog64-900 Alpha ISO from here: ibiblio.org, or from uoc.gr, or nluug.nl.

The ISO and corresponding devx, nls and 32-bit compatibility library are located in the same location above. Kernel sources can be downloaded using the "SFS Manager" applet located in Fatdog64 Control Panel's "System" tab.

The ISO builder is not available now. It will be released with Fatdog64-900 Final.

----

Get the Fatdog64-814 Final ISO from here: ibiblio.org, or from uoc.gr, or nluug.nl.

The corresponding devx, nls and 32-bit compatibility library, and the kernel source SFS can be can be downloaded using the "SFS Manager" applet located in Fatdog64 Control Panel's "System" tab.

There is no ISO builder for the 814 release. Please use ISO builder for 813 release and update the package list manually as needed.

=====

If you need to boot on a machine with Secure Boot enabled, please make sure you read this first this: http://distro.ibiblio.org/fatdog/web/fa ... -boot.html.

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 on Fatdog64 by visiting file:///usr/share/doc/faqs/faq.html or clicking the "question mark" icon on the desktop.

=====

[fatdog]

A quick clarification. Before the Alpha is released, there are links circulating that points to "900tip" from which one can download Fatdog64's ISO, and somehow this was interpreted as an "alpha release".

This is incorrect. "900tip" is not alpha release. The official alpha release is located in the links given in the first post.

The 900tip is a an "internal test build" for the internal Fatdog team. It is built differently from the official releases (alpha, beta, or final). It is updated often, and sometimes can be (very) buggy (or even break completely).

Of course, nothing stops you from using the 900tip version, but if you do, please be prepared to encounter bugs. And if you do encounter bugs, please don't report is as "alpha bugs" unless you can also reproduce the bug in the actual, official alpha release. And finally, before reporting the bug, it is a good idea to check if a new ISO has been cut on the 900tip (look at the "last modified date"), because if you can find a newer build, the likelihood is that your bug has already been fixed.

[fatdog]

Updates:
=======
1. Kernel 6.1.39 is now available for testing: http://distro.ibiblio.org/fatdog/kernels/900/
How to test kernels without installing it: http://distro.ibiblio.org/fatdog/web/fa ... ernel.html
WIth the kernel, you don't need to specify 'coldplug' to boot NVME drives.
If this kernel is good, it will be used in beta.

2. PulseAudio SFS is now available for testing: http://distro.ibiblio.org/fatdog/sfs/900/ (or from SFS Manager).
Load the SFS, and start the service ("service pulseaudio start" from terminal).
Then from Control Panel, Launch Fatdog Set Default Soundcard and choose "ALSA -> PulseAudio bridge").
Pavucontrol and pasystray available to manage PulseAudio.
You can stop PulseAudio anytime by running "service pulseaudio stop" from terminal (don't forget to configure the default soundcard back to one of the hardware devices).

[fatdog]

Reserved.

[fatdog]

Reserved.

[don570]

Fatdog 900

Blender 3.6 LTS worked well and fspy appimage

My wacom tablet worked with GIMP
SAMBA server worked
Bluetooth - cheap USB adaptor CRS
It could see my Sony stereo but not make connection.

-checked my ptmtimer pet and baconrecorder pet

Good work!! Thanks.
____________________________________

[jamesbond]

Thanks @don570 for testing.

[stemsee]

As of today files listed in my SFS Manager

sfsm.png (32.15 KiB) Viewed 2074 times

[don570]

Wishlist-

Right click on mounted disk (such as /mnt/sda2) and right click menu shows
pFind can do a search for file.
_________________________________

[step]

As of today files listed in my SFS Manager
sfsm.png

As of today we have added all and only those four SFS packages to the SFS repo. We will be slowly adding more as we move forward with development.

[don570]

I noticed that libuchardet is needed for media player 'mpv'
but it's not listed in the meta file

Code: Select all

PACKAGE REQUIRED:  alsa-lib,ffmpeg,libass,libjpeg-turbo,libdvdread,libdvdnav,lcms2,libarchive,librubberband,luajit,mujs

Wondering if this is important??
In EASY OS libuchardet isn't needed for media player 'mpv'
___________________________________________

[jamesbond]

I noticed that libuchardet is needed for media player 'mpv'
but it's not listed in the meta file

Fixed, thanks.

Wondering if this is important??
In EASY OS libuchardet isn't needed for media player 'mpv'

It's used to guess the codepage of the subtitle if you don't specify it.

[proebler]

I am trying out Fatdog64-900 Alpha on my Acer C720 (ex)chromebook.
I have got the special keys working with the 'proven' c720_720-120417-x86_64-1.txz plugins.
But I seem to have a temperature problem as reported by the System Profiler.
The thermal_zone1 is showing values > 90.00°C .
I don't know what thermal_zone1 is , but a temperature > 90.00°C makes me feel hot as well.

Perhaps jamesbond or anyone else with an Acer C720 would be so kind and try to verify what I see and hopefully suggest a remedy.
I attach a part hardinfo_report taken , it shows the sensors, kernel modules and the memory usage information.

regards proebler

[don570]

It may just be badly written code that displays the temperature inaccurately.
What I would do is play a video file or go to youtube.com and play a video and observe the temperature.
If the temperature remains the same (90) then it's a case of badly written code.
_______________________________________________________

[jamesbond]

I don't have C720, but don570 is probably right. If parts of your C720 is really running at 90degree, you can probably feel it with your hand. Can you please run "sensors" on terminal and see what have you got?

[proebler]

@jamesbond & @don570, thank you both for your response.

These are the values with a youtube video running in Seamonkey:
# sensors
coretemp-isa-0000
Adapter: ISA adapter
Package id 0: +43.0°C (high = +100.0°C, crit = +100.0°C)
Core 0: +42.0°C (high = +100.0°C, crit = +100.0°C)
Core 1: +41.0°C (high = +100.0°C, crit = +100.0°C)

So they are ok.
The temperatures are < 40 C when doing light tasks.
It is just that thermal_zone1 from System Profiler/Information which goes to > 90 C , irrespective of what I do.

The processor on my Acer C720 is a Celeron 2955U, for which Tjunction(max) is given as 100 C , the processor has internal thermal control mechanisms.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Intel gives information about their processors:
Thermal Monitoring Technologies

Thermal Monitoring Technologies protect the processor package and the system from thermal failure through several thermal management features. An on-die Digital Thermal Sensor (DTS) detects the core's temperature, and the thermal management features reduce package power consumption and thereby temperature when required in order to remain within normal operating limits.
...................................................
TJUNCTION

Junction Temperature is the maximum temperature allowed at the processor die.

What is Tjunction max temperature?
Tjunction max is the maximum thermal junction temperature that a processor will allow prior to using internal thermal control mechanisms to reduce power and limit temperature. Activation of the processor's thermal control system may cause performance loss as the processor typically reduces frequency and power to prevent overheating. The maximum junction temperature limit varies per product and usually is between 100°C-105°C. Consult the product specification page [ark.intel.com] (ark.intel.com) to determine the details for specific processor models. The goal for a system builder or a do-it-yourself (DIY) end user is to design a platform configuration that keeps the processor under the Tjunction max threshold during heavy workloads to maximize performance of the system.

The benefit to a user is that many third-party utilities can monitor the digital thermal sensor (DTS) on the processor die to see how close the system is approaching the Tjunction max temperature without any destructive testing. .....
.....................................................
Could my processor get damaged from overheating?

It's unlikely that a processor would get damaged from overheating, due to the operational safeguards in place. Processors have two modes of thermal protection, throttling and automatic shutdown. When a core exceeds the set throttle temperature, it will reduce power to maintain a safe temperature level. The throttle temperature can vary by processor and BIOS settings. If the processor is unable to maintain a safe operating temperature through throttling actions, it will automatically shut down to prevent permanent damage.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Apologies to jamesbond for assuming that you have an Acer C720, (a mix up with kirk?)
Thank you for providing Fatdog64. It is 'cool' and i don't feel hot anymore .
regards proebler

[Neo_78]

Thanks for your effort @jamesbond and team!

Have the bug fixes that were developed for 813 in order to correct the Chrome update problem and the remastering process been incorporated into version 814?

Or do these fixes still have to be installed manually in 814?

Thanks for your feedback!

[jamesbond]

Apologies to jamesbond for assuming that you have an Acer C720, (a mix up with kirk?)
Thank you for providing Fatdog64. It is 'cool' and i don't feel hot anymore .

You're much welcome. No apologies needed, it's easy to get things mixed up like this You're right it was Kirk who had the C720.

Thanks for your effort @jamesbond and team!

You're welcome.

Have the bug fixes that were developed for 813 in order to correct the Chrome update problem and the remastering process been incorporated into version 814?

Or do these fixes still have to be installed manually in 814?

Why don't you download 814 and check it for yourself, and report?

[step]

It may just be badly written code that displays the temperature inaccurately.
What I would do is play a video file or go to youtube.com and play a video and observe the temperature.
If the temperature remains the same (90) then it's a case of badly written code.
_______________________________________________________

One more data point about possible thermal issues. Yesterday my laptop was engaged in heavy computation, and all cores were nearly 100% maxed. I checked their temperature with htop and got readings of 190 degrees Celsius! I immediately powered off my computer. It was hot but certainly not 190 degrees.

[don570]

Linux is typically months behind Windows in kernel development.
Laptops especially, but if the processor manufacturer cares about its reputation,
it will submit a kernel patch eventually.
______________________________________

[don570]

Fatdog64-900 Alpha

Report-

When I downloaded and tried to install
https://distro.ibiblio.org/fatdog/packa ... i686-1.txz

I was warned that it didn't install. A failure.

I was able to get WINE to work using an old SFS file of wine 4.0 and used it successfully
to launch ...
https://www.fosshub.com/mp3DirectCut.html
_______________________________________

[step]

@don570, thank you for reporting. We'll fix it. Meanwhile, you can download an equivalent wine SFS from Fatdog64 Control Panel > System > SFS Manager.

Update: strange, I can download and install the wine txz package. The md5 checksum is 85a76a8ff37fb93efad5c80f78108e0f . Does it match the file you downloaded? Do you have sufficient free RAM for installer's temporary files?

[don570]

I didn't create a folder save file. It was a fresh frugal install. Maybe that is the problem.
I have a 8 gigbyte machine.
I'll download it again (MD5sum 85a76a8ff37fb93efad5c80f78108e0f)
and compare with and without save file.

_____________________________________________

[fatdog]

@don570, it could happen when you're downloading at the same time the repository is updated with new packages. In that case, stop gslapt, delete everything in /var/slapt-get ("rm /var/slapt-get/.*" and "rm /var/slapt-get/*") then try again after a few minutes.

[fatdog]

Updates: Kernel 6.1.39 and PulseAudio SFS.
See third post: viewtopic.php?p=93227#p93227

[Duprate]

Hello! I don't know if I should opine about the kernel....
The fact is that, for me, kernel 5.19.17 and 6.1.39, on startup give the error "kernel panic" and crash. However, for years I use FatDog64 only in Overlayfs mode and compile the Kernel as Monolithic (without modules and firmware). I'm already using 6.1.39 which I compiled on the 19th of July 2023. So my obtained results are probably not of interest to any of the AUFS users.
But, I would also like to know what the result of using the new kernel is with other users.......

[don570]

I spent some time trying to get WINE to work.

I was able to use the wine4 SFS package
wine-4.0-i686-1.sfs and any 32bit compatibility package
https://distro.ibiblio.org/fatdog/sfs/8 ... 64_811.sfs

I simply installed them using control panel . Drive C was set up and I could launch the window's notepad.
I downloaded and launched mp3DC236.exe as well

__________________________________________

However when I used wine 8.6 slack package or SFS file in repository
I had some trouble.
For example I installed wine-8.6-i686-1.txz
I ran

Code: Select all

./wine64 notepad

and because I had CD'd into bin folder ---> it could set up wine folders in /root and launch notepad.
however

Code: Select all

./wine notepad

didn't work.

Also when I dragged mp3DC236.exe into bin folder

Code: Select all

./wine64 mp3DC236.exe

it didn't work ---> vulkan error

Code: Select all

./wine64 ./mp3DC236.exe

gave ld-linux.so.2 missing
________________________________
So I need help

[jamesbond]

Hello! I don't know if I should opine about the kernel....
The fact is that, for me, kernel 5.19.17 and 6.1.39, on startup give the error "kernel panic" and crash. However, for years I use FatDog64 only in Overlayfs mode and compile the Kernel as Monolithic (without modules and firmware). I'm already using 6.1.39 which I compiled on the 19th of July 2023. So my obtained results are probably not of interest to any of the AUFS users.
But, I would also like to know what the result of using the new kernel is with other users.......

Hi Duprate, I'm not sure I understand you. When you said you experienced crash, in what situation did it happen? If it happens you're using your own custom kernel with your own custom config, and your own custom initrd to use overlayfs when it happens ... I'm afraid you're right, it's probably irrelevant to others, as the configuration is very specific to you and it will not be reproducible by others.

[jamesbond]

However when I used wine 8.6 slack package or SFS file in repository
I had some trouble.
For example I installed wine-8.6-i686-1.txz

I assume with this one, you will use the 32-bit package from the 900? Not from 811?

Also when I dragged mp3DC236.exe into bin folder

Code: Select all

./wine64 mp3DC236.exe

it didn't work ---> vulkan error

This is because libvulkan isn't installed. You can install it from the repo, but in the future builds I will include this as part of the base.

Code: Select all

./wine64 ./mp3DC236.exe

gave ld-linux.so.2 missing

ld-linux.so.2 comes from the 32-bit SFS, so this one is really odd, it is as if the 32-bit SFS is not loaded. Can you try again with 32-bit SFS from 900?

[step]

With libvulkan installed, I tested the wine SFS with the following commands:
load the wine-8.6-i686 SFS first, then

Code: Select all

# rm -r /tmp/w64 /tmp/w32
# mkdir /tmp/w64 /tmp/w32
# WINEPREFIX=/tmp/w64/ wine64 notepad
(notepad started)
# WINEPREFIX=/tmp/w32/ wine   notepad
(notepad started)
# WINEPREFIX=/tmp/w64/ wine   notepad
wine: WINEARCH set to win32 but '/tmp/w64' is a 64-bit installation.
# WINEPREFIX=/tmp/w32/ wine64 notepad
wine: '/tmp/w32' is a 32-bit installation, it cannot support 64-bit applications.

Wine's two error messages about 64-bit / 32-bit installation are to be expected. They say that wine does not support crossing the bitness of WINEARCH vs WINEPREFIX.

Then I unloaded the SFS and installed the wine-8.6-i386 TXZ package to repeated the same commands with the same results: the two notepads ran OK, and crossing bitness is not supported.