Fatdog64-700 beta1

Message

Billtoo · #141 Post by **Billtoo** » Wed 01 Oct 2014, 14:51

I spent some time today in Windows 8.1 on a pc with an ati video card, Radeon
HD 8570, catalyst control center 14.9.
The tearing clip (in windows) had the same jiggle,tremble,shiver,etc as my mac mini in
fatdog with the intel HD 4000 chip.

The same 1080p fullsceen music video at youtube plays well in both windows 8.1
running google chrome and fatdog running firefox 32.03

I can't see any difference in the video playback quality between
windows 8.1 and fatdog64 beta 1.

The end. (hopefully)

Billtoo · #142 Post by **Billtoo** » Wed 01 Oct 2014, 18:13

I made an sfs file of Deadbeef.0.6.2

I tested it in Fatdog64 beta 1 only, also I should have included x86_64
in the name but forgot.

EDIT: Tested and works in Fatdog64 701 beta, doesn't work in Fatdog64 631

After loading the sfs restart x and the menu entry will appear in
the multimedia section of the fatdog menu.

The md5sum is: c19f81bc4ff6617c750a00434193e158 deadbeef-0.6.2.sfs

The download link is: Removed

Pavan · #143 Post by **Pavan** » Wed 01 Oct 2014, 22:54

Billtoo wrote:The end. (hopefully)

Maybe for you if your happy with the fact that there must be something seriously wrong with your setup.There should be no jiggle,tremble,shiver,etc on that clip at all with correct Vsync , it should be as smooth as a puck sliding back and forth across ice.

As previously stated it is the lowest of the lowest sync test you can run as it's only 2 colors and is of a standard basic frame rate.There is nothing special about it that's any different from sideways movement in any other clip , it's just 2 colors to make it easier to see if there is a problem.

jiggle,tremble,shiver,etc is a problem

Teddog and the rest of us can't be wrong as it's perfect in windows but not in Fatdog unless in my case i run a Nvidia card with the pipe line fix then it matches windows for actual smooth constant sideways scroll without any jiggle,tremble,shiver.

We can't all be wrong and you are right.

If you are happy with media playing incorrectly then no one in the future should ask you for your opinion and you shouldn't give it.Sorry if that sounds rude but being happy with something that is incorrect doesn't help anyone fix it.

Sadly Bindee understood what correct media playback should look like and helped us to fix it before but that doesn't look like it is going to happen now as it seem more important to post pretty desktop pics and pretend everything is fine when really it isn't

Sorry but it seems to be true.

When a project becomes more about waxing the ego of the developers and pretending anything that is incorrect is perfectly acceptable than it is set sail for fail.

James C · #144 Post by **James C** » Wed 01 Oct 2014, 23:34

What's the odds that all these Linux graphics guru's joined this forum in June 2014? What a coincidence.

Billtoo · #145 Post by **Billtoo** » Thu 02 Oct 2014, 01:56

I made an sfs of audacity-2.0.6 sound editor.

After loading the sfs in Fatdog64 701 beta it still needed wxWidgets to run so I opened the Gslapt Package Manager in the Fatdog64 Control Panel,updated it,searched for wxwidgets,installed wxwidgets.

After loading the sfs restart x and a menu entry will appear in the multimedia section of the fatdog menu.

The md5sum is: a7c396bc882d0350729dee0a4b657a82 audacity-2.0.6-x86_64.sfs

The download link is:Removed

Wilbert · #146 Post by **Wilbert** » Thu 02 Oct 2014, 04:54

James C wrote:What's the odds that all these Linux graphics guru's joined this forum in June 2014? What a coincidence.

What's the odds that all these embarrassing cringe-worthy brown noses joined this forum in March/April 2009? What a coincidence.

gcmartin · #147 Post by **gcmartin** » Thu 02 Oct 2014, 06:45

Hello all.

I am NOT a video specialist. In my past, I have come to realize that some configurations perform better than others. Further, I know NOTHING of tweaking options of a video card and NOTHING of tweaking a video player's config.

So I offer this:

A little while ago, thru the collaboration with others, a document giving some simple steps in using KVM on a 64bit PUP. It has been tested by members in and out of this PUP's community in the past before this FATDOG version. I found out several things; in summary, some things actually perform better in a KVM VM guest, than natively.

Would any of this thread's users test that document for accuracy for this version of FATDOG, and report ANY issues found? (Your investment in time, start to finish, should be around 5 minutes including reading the steps. After which any distro you subsequent use/test requires the single screen Launch (seconds) to boot a Guest's ISO ... even with persistence should you choose.)

I just found that the video performs without a problem. I only did the simplest of testing.

If others report the same findings, this "may" give something to go on.

P.S. I already know developer's

"apple to oranges" views, but, this provide one view of how we can overcome this issue, if others find the same as I.

Here to help

Yoni · #148 Post by **Yoni** » Thu 02 Oct 2014, 07:10

Is this for running a Vitual Machine inside a Linux shell or for running a Virtual Machine in Windows?

The concept of a virtual OS running faster is making my head hurt.

neerajkolte · #149 Post by **neerajkolte** » Thu 02 Oct 2014, 08:04

Hi Yoni,

This is for running virtual machine inside Fatdog.

I have been using this method on 630 and 631.
I am yet to use it on 700.

The process uses KVM-Qemu.

I have ran Ubuntu, Mint, Windows7 on it in my Fatdog.

I actively use it to test out different puppies too.

Give it a try and see for yourself.

Thanks.

- Neeraj.

jamesbond · #150 Post by **jamesbond** » Thu 02 Oct 2014, 08:52

Anyone who is into running qemu VM in Fatdog is welcome to check qemu-vm-manager in the repo.

Also, get bash-4.2-x86-64-1.txz from the repo. Test using: http://murga-linux.com/puppy/viewtopic. ... 675#801675.

prehistoric · #151 Post by **prehistoric** » Thu 02 Oct 2014, 14:47

Believe we have another problem with bash version numbers in these posts. Consider this result for bash 4.2-x86_64-1:

Code: Select all

# bash --version
GNU bash, version 4.2.45(2)-release (x86_64-unknown-linux-gnu)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
# curl --insecure https://shellshocker.net/shellshock_test.sh | bash 
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  2009  100  2009    0     0   3519      0 --:--:-- --:--:-- --:--:--  3524
CVE-2014-6271 (original shellshock): VULNERABLE
CVE-2014-6278 (Florian's patch): VULNERABLE
CVE-2014-7169 (taviso bug): VULNERABLE
CVE-2014-//// (exploit 3 on http://shellshocker.net/): not vulnerable
bash: line 44:  2490 Segmentation fault      bash -c 'true <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF' 2> /dev/null
CVE-2014-7186 (redir_stack bug): VULNERABLE
CVE-2014-7187 (nested loops off by one): not vulnerable

versus this for bash 4.2-x86_64-4

Code: Select all

# bash --version
GNU bash, version 4.2.51(2)-release (x86_64-unknown-linux-gnu)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
# curl --insecure https://shellshocker.net/shellshock_test.sh | bash 
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  2009  100  2009    0     0   5105      0 --:--:-- --:--:-- --:--:--  5111
CVE-2014-6271 (original shellshock): not vulnerable
bash: shellshocker: command not found
CVE-2014-6278 (Florian's patch): not vulnerable
CVE-2014-7169 (taviso bug): not vulnerable
CVE-2014-//// (exploit 3 on http://shellshocker.net/): not vulnerable
CVE-2014-7186 (redir_stack bug): not vulnerable
CVE-2014-7187 (nested loops off by one): not vulnerable
#

This should also apply to backported fixes for Fatdog 630-631.

jamesbond · #152 Post by **jamesbond** » Thu 02 Oct 2014, 15:05

"-1" and "-4" are build numbers. The bash version is the same (4.2) but more recent builds will have a higher build number (in theory). Thus bash-4.2-x86_64-4 is newer than bash-4.2-x86_64-1 (or -2, or -3). So when installing always look for the latest build.

I don't include the patchlevel (51 for build 4) in the package name for the simple reason that the original package was called "bash-4.2" (that is build 1, which is at patchlevel 45 from LFS 7.5).

And yes, I think JustGreg and others have confirmed in 630/631 thread that the the latest build will work there too.

Gobbi · #153 Post by **Gobbi** » Thu 02 Oct 2014, 15:42

jamesbond wrote:Anyone who is into running qemu VM in Fatdog is welcome to check qemu-vm-manager in the repo.
].

As it can be seen , I'm running qemu 2.1 already but qemu-vm-manager refuse to install due to some error...

jamesbond · #154 Post by **jamesbond** » Thu 02 Oct 2014, 15:59

@Gobbi - yeah, wrong dependency naming - the qemu in the repo is named "qemu-arm-x86_64". I'll just remove the dependency, anyone using that would know they'll need qemu anyway. For now, just download the package from ibiblio, then right-click with Rox and choose "Install package". That should do it. There is no menu, just run from terminal "qemu-vm-manager" as it is still in experimental stage.

EDIT: Please bear in mind that this is meant for very simple uses only. If you need powerful interface that can do everything you should probably attempt to build libvirt

Gobbi · #155 Post by **Gobbi** » Thu 02 Oct 2014, 16:22

jamesbond wrote:There is no menu, just run from terminal "qemu-vm-manager" as it is still in experimental stage.

I installed the downloaded package but running it from the terminal does not work for me...

Later I took a look in /usr/bin and saw that the executable is called qemu-vm-manager.sh so running that into terminal did work .

jamesbond · #156 Post by **jamesbond** » Thu 02 Oct 2014, 16:59

Gobbi wrote:I installed the downloaded package but running it from the terminal does not work for me...

You will need to "right-click" and then "install package" first ... the package needs to be installed. The bin works, but you will need to have the script library for it to work. I may change this later, for now that's how it works. EDIT: Version 1.1 uploaded.

step · #157 Post by **step** » Thu 02 Oct 2014, 21:07

I'm stuck trying to build R 3.1.1 cran.r-project.org in a sandbox. I can't get past the simplest step involving gfortran, for instance

Code: Select all

sandbox# (cd src/extra/blas ; gfortran     -c blas.f -o blas.o)
f951: internal compiler error: Illegal instruction
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
sandbox#

gfortran always spits out that illegal instruction error.
Can anyone help me fixing this?
The rw-sandbox imports 4 sfs files; fd64 (extracted from initrd), fd64-devx_700b1, kernel-modules and tmpfs.
Though I doubt this issue is sandbox specific. If i try the same command outside the sandbox I get exactly the same error message.
This is my hardware

Code: Select all

# lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                2
On-line CPU(s) list:   0,1
Thread(s) per core:    1
Core(s) per socket:    2
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 15
Model name:            Intel(R) Core(TM)2 Duo CPU     T7700  @ 2.40GHz
Stepping:              10
CPU MHz:               2401.000
CPU max MHz:           2401.0000
CPU min MHz:           800.0000
BogoMIPS:              4789.22
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              4096K
NUMA node0 CPU(s):     0,1

edit 1: I worked-around this issue by compiling with gfortran 4.9 (FD devx.sfs includes gfortran 4.8.2). Now I'm stuck on g++ header issues...

gcmartin · #158 Post by **gcmartin** » Thu 02 Oct 2014, 22:29

Hi @Gobbi, I'm a little late, but, you may want to try this GUI. It has a little more PUPPY mileage in user testing as it was design by a Puppy author who felt a simple screen would help KVM comfort and it does work. The tool @JamesBond mentions works to provide the same.

Again, that GUI, shown below, to ease use is at ===> A QEMU Laucher

Oh, another item many will find interesting. Notice YOUR INTERNET PERFORMANCE!

This should ease your burden.

step · #159 Post by **step** » Fri 03 Oct 2014, 09:12

@gcmartin, @Gobbi,

gcmartin wrote:... you may want to try this GUI...

QEMU Control Center pet repackaged for FD700 here: https://www.dropbox.com/s/5h5f9a6utfem5 ... T.txz?dl=0

Gobbi · #160 Post by **Gobbi** » Fri 03 Oct 2014, 09:42

Thank's gcmartin and step for your advices !
I already used Qemu Control Center 0.6 with qemu packages in FD700 ... It' comfortable but I'm also trying to learn the terminal way because I want to give more features to the guest ( sound , screen resolution...) .
qemu-vm-manager package from the repo has the advantage to remember different virtual machines created by the user : the approach that VBox has... If developed , I think this package will be also very useful ...

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum