Fatdog64-810 Final [17 Jan 2020]

[rufwoof]

Thanks Fatdog team. 810 is working well for me (manual hdd frugal install, using grub4dos).

/usr/share/doc/fd-help/urxvt.md ... second to last line should read

Shift down-arrow will open a new tab

and not

Shift up-arrow will open a new tab

Similarly
Ctrl-left (or right) arrow to step between tabs
should read
Shift-left (or right) arrow to step between tabs

Code: Select all

Key	             Description

Shift+Down	New tab
Shift+Left	  Go to left tab
Shift+Right	Go to right tab
Ctrl+Left	    Move tab to the left
Ctrl+Right	 Move tab to the right
Ctrl+d	       Close tab

[stemsee]

Hydrogen doesn't work! Fatdog repo lacks libQt5XmlPatterns.so.5 but after trying packages from other distros without success I'm posting here.

[LateAdopter]

Hello jamesbond & kirk

DELETED

I would like to get VA-API working too, since VDPAU has been defunct for several years.

Can I request mesa-va-drivers 18.3.6 and libva-utils (vainfo) , please?

FD810 VA-API includes i965_drv_video.so but is missing nouveau_drv_video.so,
r600_drv_video.so and radeonsi_drv_video.so.

Thank you.

[step]

@stemsee, libQt5XmlPatterns.so.5 is included in qt-creator-qt5-4.7.2, which can be installed via package manager. It's huge (80+ MB), and you won't need all of it for sure. You could extract just the modules you need.

[jamesbond]

@stemsee, libQt5XmlPatterns.so.5 is included in qt-creator-qt5-4.7.2, which can be installed via package manager. It's huge (80+ MB), and you won't need all of it for sure. You could extract just the modules you need.

Or install the full qt5-5.11.1 SFS (using SFS manager). Or install the full qt5-5.11.1 package (from the repo). Or extract the file from the package. The qt5 libraries we include in the base is a "cut-down" version and does not include everything.

@LateAdopter: Thanks for the finding. I'll let kirk respond to that.

[don570]

There is a small change to Zigbert's pfilesearch ...
http://www.murga-linux.com/puppy/viewto ... 07#1044707
It works in fatdog64...
__________________________________

[kirk]

Looking at the major distributions FD810 is between Bionic and Buster. so I installed the mesa 18.3.6 package to make it like Buster.

I don't understand, 810 includes mesa 18.3.6.

[LateAdopter]

Hello kirk

I don't understand how I did it. I downloaded the ISO from nluug, checked the MD5, because I was confused by the fact that it appeared in two locations.
But when I extracted the initrd, I have ended up with the FD800 version.

I will delete my irrelevant comments and start again.

Sorry about that.

EDIT: - Oh no! I've gone down a snake again.

With the correct initrd and initrd-nano FD810 booted to a desktop once and allowed me to create a savefile. But it has failed to boot to the desktop again unless I have nomodeset.
I checked in /var/log/packages and it definitely lists the latest versions of mesa and xf86-video-amdgpu.
I deleted the savefile and it has still refused to boot again with amdgpu.

I think my installation of Bionicpup64 must have been beginners luck. I have used it for two weeks with its libreoffice SFS and my Vivaldi SFS loaded and it hasn't locked up at all.

EDIT 2 I confirm that, with amdgpu:

Fatdog 800 WILL NOT BOOT

Fatdog 810 WILL NOT BOOT

Fatdog 800 + mesa 18.3.6 + xf86-video-amdgpu 19.1 WILL BOOT

That's three out of three boots. GLXgears scores 12,500, so it's working properly.

[kirk]

Fatdog 800 + mesa 18.3.6 + xf86-video-amdgpu 19.1 WILL BOOT

That's three out of three boots. GLXgears scores 12,500, so it's working properly.

But that can't really work. The xf86-video-amdgpu-19.1.0-x86_64-1 package is compiled for 810's xorg-server and will not work with the one in 800/803. So what's probably happening is the xorg-server tries to load xf86-video-amdgpu and fails because it's not compiled for it, and then falls back to xf86-video-ati or maybe even the generic modesetting driver. So what you're essentially doing is removing the xf86-video-amdgpu package.

[stemsee]

has permissions for fixmenus changed?

Also for running Ardour 5.12 (available in repo) libaubio needs installing. This one works https://packages.slackonly.com/pub/pack ... slonly.txz

Also running qjackctl locks up the entire system.

[LateAdopter]

Fatdog 800 + mesa 18.3.6 + xf86-video-amdgpu 19.1 WILL BOOT

That's three out of three boots. GLXgears scores 12,500, so it's working properly.

But that can't really work. The xf86-video-amdgpu-19.1.0-x86_64-1 package is compiled for 810's xorg-server and will not work with the one in 800/803. So what's probably happening is the xorg-server tries to load xf86-video-amdgpu and fails because it's not compiled for it, and then falls back to xf86-video-ati or maybe even the generic modesetting driver. So what you're essentially doing is removing the xf86-video-amdgpu package.

Ha! Ha! After years of trying to make sense of the linux display driver tower of cards, I think I may be ahead of you. I've been off AMD for a few years but I'm up to speed now.

For xf86 it's only the ABI 24 that matters. I have attached the Xorg.0.log which you can see is for xserver 1.20.3 and does successfully initialise amdgpu.

With RadeonSI and later there seems to be an implied dependency between mesa and the xserver. This probably doesn't apply to i965 or Radeon that don't use libglamoregl.
It looks like mesa needs to have been built against an xserver version that is equal too or later than the version to be used. So it should be possible to update or backport mesa without recompiling the xserver. But, if you update the xserver, then mesa needs to be recompiled.

Looking at the dates of the packages mesa 18.3.6 was built after the xserver FD800 and before the xserver in FD810. According to my hypothesis that means that it will work with FD800 but not with FD810.

[SFR]

has permissions for fixmenus changed?

It's been like this for a while now.
We use fatdog-jwm-xdgmenu.sh script (which in turn uses jwm-xdgmenu binary) instead.
But it makes sense only if you use JWM. Otherwise LxQt-Panel is capable of refreshing the menu on its own.
If you use JWM indeed, after installing a package you need to run 'Menu -> Window Manager -> Restart JWM' to refresh the menu.

Also for running Ardour 5.12 (available in repo) libaubio needs installing. This one works https://packages.slackonly.com/pub/pack ... slonly.txz

aubio-0.4.7-x86_64.txz is also in the repo.

Also running qjackctl locks up the entire system.

Yep, it does that for some reason, but we're not alone: http://linux-audio.4202.n7.nabble.com/q ... 04541.html
I just rebuilt it with the suggested '--disable-xunique' option and it doesn't freeze anymore.
I'll let James know about it.
___________

There is a small change to Zigbert's pfilesearch ...
http://www.murga-linux.com/puppy/viewto ... 07#1044707
It works in fatdog64...

Thanks, it's in.

Greetings!

[kirk]

For xf86 it's only the ABI 24 that matters. I have attached the Xorg.0.log which you can see is for xserver 1.20.3 and does successfully initialise amdgpu

Yes, if there's not much change in the xorg-server then it can work. Forgot the xorg-server hasn't had a major update in the past year. We'll recompile mesa for final and you can see if that helps. Thanks.

[artsown]

I ran into a puzzling situation when trying to remaster a hard drive frugal
installation. I had added firefox and a old version of thunderbird without
being concerned with removing anything I'm not interested in. So the initrd
size was expected to increase by maybe 200 to 300 mb.

My remasters are being done using the humongous initrd. Instead of /tmp
I aim the result at a very large ext3 partition (/mnt/home).

While booting the remaster I got a error message saying there was
insufficient ram. But I have 4gb ... so what gives? After doing the remaster
again and getting the same error message, I removed seamonkey and
libreoffice. No error message when booting and the remaster works
perfectly.

So color me puzzled

Art

[rufwoof]

I ran into a puzzling situation when trying to remaster a hard drive frugal
installation. I had added firefox and a old version of thunderbird without
being concerned with removing anything I'm not interested in. So the initrd
size was expected to increase by maybe 200 to 300 mb.

My remasters are being done using the humongous initrd. Instead of /tmp
I aim the result at a very large ext3 partition (/mnt/home).

While booting the remaster I got a error message saying there was
insufficient ram. But I have 4gb ... so what gives? After doing the remaster
again and getting the same error message, I removed seamonkey and
libreoffice. No error message when booting and the remaster works
perfectly.

So color me puzzled

Art

Are you loading/running all in ram?

https://www.lightofdawn.org/blog/?viewDetailed=00128

If the uncompressed size is getting on for 2GB (IIRC the standard uncompressed size is around 1.2GB), but you expand that by 300MB of compressed, perhaps 900MB of uncompressed (2.1GB) alongside 700MB of compressed (rounding combined 3GB total), then after graphics and the main system also take their slice I would have thought that would 'fit', but in your case apparently not.

Not using humongous and not loading into ram would be the solution (or at least worth giving a try to see if that loads/runs OK).

[artsown]

rufwoof, thanks much for the quick response and link to james's tutorial.
Since my results aren't totally unreasonable, I doubt that I'll fiddle with
the issue any longer. I just hope that other users will be alerted to be
careful because of this discussion. It sure took me by surprise!

EDIT: Well, I did eventually "fiddle", and I'm now using a method that
allows me to use the standard humongous initrd. I have firefox (199 meg)
and thunderbird (64 meg) extracted folders on the home partition instead
of in /opt. The only package removed from fatdog is seamonkey. Added to
fatdog are qpdfview, gtk+3, my traytemp, and some smaller items.

I share the firefox and tbird folders with a few puppies on the same partition.

The remastered fatdog is not only quick to boot, it runs beautifully fast
using a save folder that's relatively small in size.

Art

[jamesbond]

For xf86 it's only the ABI 24 that matters. I have attached the Xorg.0.log which you can see is for xserver 1.20.3 and does successfully initialise amdgpu

Yes, if there's not much change in the xorg-server then it can work. Forgot the xorg-server hasn't had a major update in the past year. We'll recompile mesa for final and you can see if that helps. Thanks.

To follow up kirk: we've recompiled mesa and pushed to the package repo. You can try that now if you want to test it, or otherwise you can wait until final.

[LateAdopter]

Hello jamesbond

Yes that build of mesa works with Fatdog 800 AND Fatdog 810.

I have booted three times and run glxgears each time. Everything looks normal.

Thanks.

[artsown]

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

Art

[stemsee]

thanks @SFR

qjackctl updated through gslapt ... all good!

stemsee