Fatdog64-710 Final [4 Dec 2016]

[L18L]

@anyone - I'm trying to enable the AMDGPU driver, but it's not working. Xorg log attached. My Graphics Card (Radeon 7770 - Southern Island) is supported but requires some changes.

You might try boot with kernel option

Code: Select all

drm_kms_helper.edid_firmware=edid/1929x1080.bin

or 1280x1024
or 1024x768

Hope this helper will also help you

[jake29]

@anyone - I'm trying to enable the AMDGPU driver, but it's not working. Xorg log attached. My Graphics Card (Radeon 7770 - Southern Island) is supported but requires some changes.

You might try boot with kernel option

Code: Select all

drm_kms_helper.edid_firmware=edid/1929x1080.bin

or 1280x1024
or 1024x768

Thanks for the suggestion, but still not working.

I've become less concerned about this since doing more reading on the topic. The open-source driver combined with newer versions of Mesa now appears just as capable, and is in some cases superior.

http://www.phoronix.com/scan.php?page=article&item=amdgpu-new-1710&num=1

I've tried to compile Mesa 17.1.3 myself, however it's also meant needing to compile dependencies.

[L18L]

About language

Fatdog has already several translations to en_GB
(English as it is spoken in Great Britain)
see: /usr/share/locale/en_GB/LC_MESSAGES.

Thus it was time to use our translation tool for English, too.

Note, it is never necessary to translate each msg in en
only the ones which differ from the msg in the sources
and
it is never necessary to translate each msg in en_GB
only the ones which differ from en translation.

Another note, default GNU tools create po files for English
with "translations" 100% identic to original msg.
MoManager does not have this behaviour.
Saves just the necessary minimum
that is when translation is different from original.

As the screeny suggest, developers now can use MoManager
to create the pot file, check all messages by ID,
search for terms, test a pseudo translation...



EDIT
______________________________________________

New momanager should be available via gslapt 24 hours later

[L18L]

attached:

fatdog-xorgwizard.sh

i18n'ed
tested in X and terminal

/etc/X11/app-defaults/Xmessage needs an entry of

Code: Select all

*international: true

Without this non-ASCII is garbage.

[jake29]

As I mention in a previous post above, video hardware acceleration support in Linux has been improving at an increasing pace in recent months. Mesa 17.2 is expected to release mid-August 2017.

Mesa 17.2 is coming in as one of the largest updates ever to Mesa 3D, at least in terms of code delta.

http://www.phoronix.com/scan.php?page=n ... -Code-Size

In tests, Linux Kernel 4.12 is being used however I cannot establish if it's a requirement to see the benefits of this new version of Mesa.

If there is a planned new build of Fatdog64, I would like to see this area updated. Currently compiling new versions of Mesa appears to require quite a number of other packages be upgraded first.

[Yoliano]

I have read all the pages of posts in 01micko's thread on the development of Pmcputemp, but have found nothing that relates to this bug. I suspect that thread is "cold" now, as the last post was in June 2016. So have decided to post the problem here.

I am a fan of Fd64 and think it is the greatest! I have been running Fd64-710 for about 3 months now. Previously, 702, 630, 600, etc. My sincere thanks and congratulations to Jamesbond, Kirk, et al. Initially, Pmcputemp behaved perfectly, present in the tray at boot and remaining there until shutdown. But about three weeks ago, it started disappearing from the tray. It always appears at boot, but now it disappears from the tray at irregular intervals. Sometimes a couple of minutes after boot, other times after half an hour, or more. I can get it back by going to: >usr>bin> and clicking on pmcputemp. It then reappears in the tray, but soon disappears again. I have used Gslapt to uninstall, then reinstall the app., but no change, the problem persists.

I updated the google-chrome browser recently and if my memory serves me correctly, this problem emerged soon after. So that event could possibly have something to do with this change of behaviour.

I realize that this is a minor issue, but if anyone has experienced this same problem, or can otherwise give advice, I will welcome their kind assistance.

[smokey01]

@Yoliano I also had trouble running the pmcputemp.sh script in /etc/xdg/Startup.
Try placing a symlink in /etc/xdg/Startup pointing at the /usr/bin/pmcputemp binary. It works here without problems on Fatdog64-710.

[Yoliano]

Hi "Smokey", thanks for your quick response. Haven't had time yet to test your suggestion. As soon as I have done so, I will post the results for you.

Hasta pronto!

[prehistoric]

@smokey01

Tried your temperature app hack, and got it to come up and display a temperature. The number even changed, but afterward the monitor disappeared. No idea what is going on.
BTW: I hid the pmcputemp shell script in a subdirectory, in case that was causing the crash, and just used the link to the binary. Nope.

[smokey01]

@smokey01

Tried your temperature app hack, and got it to come up and display a temperature. The number even changed, but afterward the monitor disappeared. No idea what is going on.
BTW: I hid the pmcputemp shell script in a subdirectory, in case that was causing the crash, and just used the link to the binary. Nope.

How very odd. I know at least one other person that's symlinking to the binary and it's working. It is working on my other machine as well. The other machine is Intel and this one is AMD.

[borzeh]

hi
I'am using fatdog as my every day distro about a year.
but recently , (as I learn more about Linux) I'm facing with problems with compile and MAKE packages.

for example , to install vim plugins, sometimes need compile them , but always I have some dependency missings in process of make.
also to install Emacs , same thing occurred . (and many other packages that is not in fatdog Repositories)
I have tried to get missing dependencies from anywhere (even slackware 14.2 Repositories) . but at the end, near always some conflicts or other problems occurred.

{ I am try use debian , its repositories have all dependencies , seems everything work, but I don't like migration to another distro because of some problems . until today, fatdog is far more than everything I need in pc and I don't like to loose it)

is I do something wrong?
is fatdog core is limit and not for compiling?
or even all because of slackware core?

thank you

[WillM]

Hi borzeh,
There are plugin managers for Vim. Pathogen and Vundle are probably the two most widely used. What plugin do you need?

[borzeh]

Hi borzeh,
There are plugin managers for Vim. Pathogen and Vundle are probably the two most widely used. What plugin do you need?

Hi and thank you very much for your reply

some plugins like (vimproc)
i see many plugins need compile just like vimproc.

To install vimproc

Code: Select all

vimproc uses a pathogen compatible structure, so it can be managed with pathogen, however you must remember to compile after cloning the repo.

git clone https://github.com/Shougo/vimproc.vim.git ~/.vim/bundle/vimproc.vim
cd ~/.vim/bundle/vimproc.vim
make

-----

also my problem not exactly for editors and their plugins, but, trying to compile or install every package that is not in fatdog repositories.

Is it true that minimal distros like fatdog isnt good options to Compile packages?

[WillM]

vimproc installed for me. Do you have the fd64-devx-710.sfs loaded? That is if you are using Fatdog64-710, if you are using an older version of Fatdog load the devx.sfs for that version. It has all the files for compiling.

[borzeh]

vimproc installed for me. Do you have the fd64-devx-710.sfs loaded? That is if you are using Fatdog64-710, if you are using an older version of Fatdog load the devx.sfs for that version. It has all the files for compiling.

YES!
Thank you very much WillM.

// and sorry for off topic

now i'm trying make all packages i need them and have totally successful
with "checkinstall" which gives txz file at last
is there any location to upload them (permanent) and let others use them?

thanks WillM i am very happy

[Yoliano]

@smokey01

Following your suggestion, I made a Relative Symlink in /etc/xdg/Startup pointing to /usr/bin/pmcputemp, (the binary file with gearwheel icon). Then I made various tests, as follows:

1 - Rebooted 710. Temp. Icon present in tray. Completed 2 Hr. working session on PC. Temp. Icon remained present until shutdown. All OK.

2 - Made 2 more tests, as in 1. But Temp Icon disappeared from tray before end of session, in each case. Failure.

3 - Downloaded new ISO Image file of 710, from Ibiblio. Installed it on a new, unused USB3.1 16 GB Kingston Memory Stick, (genuine, bought from K. official online store). All in accordance with Jamesbond's instructiojns. Booted it Without Savefile option. 710 OS came up all good. Made minimal configuration, installing Pmcputemp from Gslapt. Went to /aufs/devsave/ and changed name of original Savefile. Closed session and made new Savedirectory. Rebooted 710 from same memstick. All good. Temp. Icon present in tray. Made 1.5 Hr. work session, including emailing and other tasks. But the Temp Icon disappeared from tray somewhere in the middle of the session! Failure. Note: Google-Chrome Browser NOT installed yet.

4 - Made relative symlink in /etc/xdg/Startup, as described above. Rebooted again and all good, with Temp. Icon in tray. Left PC running, without making operations, for 1 Hr. But Temp. Icon disappeared during that time. Failure.

So, it looks like there is some corruption going on somewhere. Maybe it originates in my hardware. It is difficult to understand how the Temp. Icon can survive for a while and then disappear. It is very weird behaviour. Also, I note that I cannot now restore the Icon to the tray by clicking on the binary file, as I could before. Things seem to be getting worse.

My ability to analise the intestines of my PC are minimal. So if you, or anyone else have some useful thoughts on this subject, I shall be very pleased to receive them. Many thanks for your interest and help.

[smokey01]

@Yoliano try deleting the /root/.config/pmcputemp directory. It should regenerate a new directory on the fly.

The contents of my /root/.config/pmcputemp/pmcputemprc are:
/sys/devices/pci0000:00/0000:00:02.0/0000:01:00.0/hwmon/hwmon0/temp1_input

Do you have something similar?

It's a bit of a mystery as it works for some but not others.

[step]

is there any location to upload them (permanent) and let others use them?

If you follow the link "+packages' in my signature you'll find the thread for user-user-contributed Fatdog packages, and you could share yours there.

[Terry H]

2 days ago I did some updates via gslapt, which i hadn't done for quite a while. When I log in now using openbox I no longer have the lxqt-panels being displayed. When I attempt to execute lxqt-panel from a termnal I get an error:
"error while loading shared libraries: /usr/lib64/libglapi.so.0: file too short."

Checking /usr/lib64, there is no libglapi.so.0. So it appears that something that I updated stopped the panels I had from running.

Any assistance greatly appreciated.




Edit: fixed typo.

[don570]

Checking /usr/lib64, there is no libglapi.so/0

Did you make spelling error?

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



I would boot up , putting 'savefile=none' in menu.lst file
and copy over an undamaged file
libglapi.so.0

http://distro.ibiblio.org/fatdog/web/fa ... efile.html

____________________________________________