Fatdog64-630 & 631 Final (May 12 2014)

[stemsee]

I was using FatDog64 631 and just beginning to appreciate it. I updated the kernel and added ralink firmware. Here is the repacked (not remastered)iso with devx included total @ 500mb
kernel is latest stable 3.15.1

https://drive.google.com/file/d/0B4GhZV ... edit?usp=1

[LateAdopter]

Thanks for the info

Does this mean that MKV , Avi and Mp4 would also use software decoding as that's the format i use the most ?

Thanks

MKV, AVI & MP4 are containers not codecs and don't have any connection with the graphics card.

Codecs are things like H.264 (MPEG4 part 10), XVID/DIVX (MPEG4 Part 2), MPEG2, VC1 etc.

These would be decoded in software with an ATI/AMD GPU using the Catalyst driver on linux, but hardware decoding would work on Windows and might work with the latest Radeon open source driver on linux.

[jamesbond]

For those who experience tearing problems, you can disable backing store by editing /etc/X11/xserverrc and edit the last line, so that it reads like this:

exec X "$@" -bs -nolisten tcp > /tmp/xerrs.$USER.log 2>&1

Sadly it made no difference to either , Still exactly the same.

Probably I didn't make it clear enough. Edit the file, adding that "-bs" option, and then you *need to restart* the X server. If the problem persists after restart, then yeah I have no further ideas. Some suggest about disabling compositing, that can be done too, but if disabling backing store doesn't fix it I doubt that disabling composition will make it work either ...

[lptpacct]

[quote="stemsee"]I was using FatDog64 631 and just beginning to appreciate it. I updated the kernel and added ralink firmware. Here is the repacked (not remastered)iso with devx included total @ 500mb
kernel is latest stable 3.15.1

Hi Stemsee, Want to give your 631 repack a spin, is there an md5? Thanks, lp

[stemsee]

here is the Md5 ... created with the iso ... i never use md5 ... so after I created the iso i changed its name, i don't know if that will affect the check! It was fatdog64.iso before.

https://drive.google.com/file/d/0B4GhZV ... edit?usp=1

[Yoni]

For those who experience tearing problems, you can disable backing store by editing /etc/X11/xserverrc and edit the last line, so that it reads like this:

exec X "$@" -bs -nolisten tcp > /tmp/xerrs.$USER.log 2>&1

Sadly it made no difference to either , Still exactly the same.

Probably I didn't make it clear enough. Edit the file, adding that "-bs" option, and then you *need to restart* the X server. If the problem persists after restart, then yeah I have no further ideas. Some suggest about disabling compositing, that can be done too, but if disabling backing store doesn't fix it I doubt that disabling composition will make it work either ...

Well i tried it Nvidia and nouveau drivers , fresh install , save and restart and it didn't work.

I've been going around and around in circles at google the last few days and about 70% results say the ripple is caused by compositing window manager.

I was thinking of buying a usb 3.0 hub

Does Fatdog detect them ok?

I would also like to know this as i still have USB 2.0

[Bindee]

Update 2013-06-17: this issue affects Adobe Flash Player videos, VLC and other media players, tearing can also be seen when scrolling pages in Mozilla Firefox.

Update 2013-09-24: Aaron Plattner says this issue cannot and won't be fixed, due to the Kepler architecture.

Kepler and earlier GPU architectures are dramatically different. Since, as I mentioned, the sync-to-vblank mechanism for Xv and VDPAU blit presentation queue are best-effort, small changes in timing anywhere in the system can cause tearing to appear or disappear. That's why I can't speculate as to why, on your particular system, one GPU behaves differently from another.

Aaron Plattner
NVIDIA Linux Graphics

https://devtalk.nvidia.com/default/topi ... g-desktop/

I all so have this problem with ripple and have been trying to find a resolution.

Don't know if the above 14 page thread has any information that means anything to anyone as i'm a newbie to all this.

[jamesbond]

My wife's laptop has USB3 port. It works when connecting USB2 devices to it. Never tried connecting USB3 devices.

Summary for that devtalk thread:

Two solutions for tearing:
1. Use a compositor (or a compositing window manager) with OpenGL backend.
2. Enable "ForceCompositionPipeline" metamodes.
Both relies on using the proprietary display driver.
Both relies that certain options are turned on the driver settings page.

The first option, in Fatdog, means that you need to run something like compton *with proper configuration*.
The second option, you need to open terminal and do this at every boot (once this is confirmed to work, you can put the correct command in $HOME/Startup: run "nvidia-settings --assign CurrentMetaMode="DFP-0: 1920x1200 { ForceCompositionPipeline = On }, CRT-0: 1920x1080 { ForceCompositionPipeline = On }"
(obviously replacing reference to DFP-0/CRT-0 to whatever the correct display port name on your computer, and change 1920x1080 to your correct resolution).

Note that none of the above is conclusive. It seems to solve problems for certain people, but not for all.

As for Aaron Plattner - somebody "interpreted" what he said as "nvidia took out the tear-free circuitry in Kepler (and all other newer cards) because it assumes that *everyone* will always use an OpenGL-based window manager."

EDIT: the compton compositor is attached. Please read here for more details on how to use it to enable vsync etc. Most importantly you must have use the GLX backend.
Basically you create the configuration file as indicated, and then run compton by opening terminal and type "compton -b".
Certain nvidia options may need to be turned on too - please read the full thread linked by Bindee, above this post.

Let me know if this helps. If yes, I will put a notice on the first page of this thread, and upload the pet to the package repository for others to use.

[Bindee]

The second option, you need to open terminal and do this at every boot (once this is confirmed to work, you can put the correct command in $HOME/Startup: run "nvidia-settings --assign CurrentMetaMode="DFP-0: 1920x1200 { ForceCompositionPipeline = On }, CRT-0: 1920x1080 { ForceCompositionPipeline = On }"
(obviously replacing reference to DFP-0/CRT-0 to whatever the correct display port name on your computer, and change 1920x1080 to your correct resolution).

Thankyou James for checking out the thread and making it into more sense.

I was going to have a another go at the above pipeline option as i think i got it wrong when i first tried it the other day and crashed X , but i just looked in $HOME/Startup and couldn't find a startup or run conf file to add any command too.

Just a couple of link files and a readme.txt that said something about symlinks

Bindee

[step]

When I click the firefox downloads folder button (green down arrow) three rox windows open instead of one. Is a fix available for this issue? TIA

[Bindee]

Pipeline works , everything is now tear free and perfect.

this is what i done.

In terminal type:

xrandr | grep " connect"

this will tell you the connection type and resolution you will need for the command.

I then went to $HOME/Startup folder and made a text file called run.sh

inside i put the following.

#!/bin/bash
nvidia-settings --assign CurrentMetaMode="DVI-I-1: 1920x1200 { ForceCompositionPipeline = On }"

Make sure you change the DVI-I-1 connection type and the 1920x1200 resolution to the same as was given in xrandr | grep " connect"

in my case it was "DVI-I-3: 1920x1080 {

then save and right click on run.sh and make it a executable file.

You will notice when you boot the desktop it will flash black and then come back again.

I can now play media with both software or hardware decoding without any tearing and youtube and firefox scrolling is ripple free.

[Pavan]

OMG , OMG , OMG

It only bloody works......

This should be added to Fatdog 7

Fatdog is now in sync the same as windows , it's beautiful.

Thanks James and Bindee for coming up with a fix , I've gone from the frustration to elation.

[jamesbond]

Glad that it work for you both. I'll definitely get it in for FD7.

[Fabio T]

I was using FatDog64 631 and just beginning to appreciate it. I updated the kernel and added ralink firmware. Here is the repacked (not remastered)iso with devx included total @ 500mb
kernel is latest stable 3.15.1

https://drive.google.com/file/d/0B4GhZV ... edit?usp=1

How I do to obtain Kernel-source.3.15.sfs?

THNX

[Yoni]

Wooooooohoooooooooooo

I can confirm Pipeline works , no more ripple.

hopefully TedDog and Billtoo can also confirm this and then it can be pretty much taken as a given that this is the Fix for Nvidia users without the need of messing about with Compton.

Shame Wilbert left before a fix was found , he will be kicking himself.

[stemsee]

@Fabio T

Here is the kernel sources sfs for 3.15.1

https://drive.google.com/file/d/0B4GhZV ... edit?usp=1

[Billtoo]

hopefully TedDog and Billtoo can also confirm this and then it can be pretty much taken as a given that this is the Fix for Nvidia users without the need of messing about with Compton.

I don't have a fatdog install for my pc with the nvidia card anymore
but I followed Bindee's instructions on my Quirky Tahr install and
created a run.sh with this in it as it is a dual monitor setup:

#!/bin/bash
nvidia-settings --assign CurrentMetaMode="DVI-I-1: 1920x1080 DVI-I-2: 1920x1080{ ForceCompositionPipeline = On }"

It works, no ripple lines etc.

I'm waiting for Fatdog64 version 7 to make another Fatdog install

[Fabio T]

@Fabio T

Here is the kernel sources sfs for 3.15.1

https://drive.google.com/file/d/0B4GhZV ... edit?usp=1

THANX VERY MUCH !!!

[grump]

I'd like to use Dropbox too. It works nicely for me in Precise.

[Bindee]

Doesn't Fatdog take donations ?

I looked on the homepage but couldn't see anything......