Fatdog64-700/701 [April 22 2015] [CLOSED]
-
- Posts: 361
- Joined: Fri 27 May 2011, 17:21
- Location: Reading UK
SMPlayer
Hello terrapin231
I can tell you how I installed SMPlayer on fatdog700. It's quite easy using Ubuntu Trusty amd64.debs.
There are packages for Mplayer in the fatdog repo. You need to install one and check it's working first. I guess the statically linked one is safer, but I was using MPV so I haven't used either.
Download the latest amd64.debs from the SMPlayer developer's PPA on Launchpad Here:
https://launchpad.net/~rvm/+archive/ubu ... /+packages
You need: smplayer, smplayer-skins, smplayer-themes
also smtube, but I haven't tried that.
Put them in a temporary directory in a linux filesystem. Since my puppies are in FAT32, I make a directory under /root which will be inside the savefile.
Use the undeb script to extract the contents, then repack them using the command line in the FAQ.
Note: with most .debs it is necessary to rearrange and rename some of the directories before you repackage, because of the multiarch system that Ubuntu uses. But these are OK because they only have /usr/bin and /usr/share. I suggest you check before you repackage, though.
When I installed it, the only missing dependency was libQtScript.so.4. Rather than installing the full QT package, I downloaded the .txz and extracted just that file plus symlinks and put them in /usr/lib64.
Again you need to be in a linux filesystem, e.g. inside the savefile, because you can't extract a symlink in FAT32.
After you have installed the package you can check for missing dependencies by opening a terminal in /usr/bin and doing the following command:
It's Lima Delta Delta!
I find that using packages build by someone who knows what they are doing and has done sanity checks on the result, is more reliable than trying to do it myself.
I read that smtube works with VLC. If you find that SMPlayer/Mplayer were the cause of your playback problems, you could try that combination.
I can tell you how I installed SMPlayer on fatdog700. It's quite easy using Ubuntu Trusty amd64.debs.
There are packages for Mplayer in the fatdog repo. You need to install one and check it's working first. I guess the statically linked one is safer, but I was using MPV so I haven't used either.
Download the latest amd64.debs from the SMPlayer developer's PPA on Launchpad Here:
https://launchpad.net/~rvm/+archive/ubu ... /+packages
You need: smplayer, smplayer-skins, smplayer-themes
also smtube, but I haven't tried that.
Put them in a temporary directory in a linux filesystem. Since my puppies are in FAT32, I make a directory under /root which will be inside the savefile.
Use the undeb script to extract the contents, then repack them using the command line in the FAQ.
Note: with most .debs it is necessary to rearrange and rename some of the directories before you repackage, because of the multiarch system that Ubuntu uses. But these are OK because they only have /usr/bin and /usr/share. I suggest you check before you repackage, though.
When I installed it, the only missing dependency was libQtScript.so.4. Rather than installing the full QT package, I downloaded the .txz and extracted just that file plus symlinks and put them in /usr/lib64.
Again you need to be in a linux filesystem, e.g. inside the savefile, because you can't extract a symlink in FAT32.
After you have installed the package you can check for missing dependencies by opening a terminal in /usr/bin and doing the following command:
Code: Select all
ldd smplayer | grep not
I find that using packages build by someone who knows what they are doing and has done sanity checks on the result, is more reliable than trying to do it myself.
I read that smtube works with VLC. If you find that SMPlayer/Mplayer were the cause of your playback problems, you could try that combination.
Fatdog64-700 FINAL [Feb 22 2015]
I did a remaster of my Fatdog64-700 installation and burned the
remaster.iso to a dvd in Ubuntu-14-04 with brasero (or whatever the
default burner is called).
It's working well, can't get Google-Chrome to start but I downloaded
the latest Firefox and it's working fine.
All the other applications work fine too.
It runs at least 5 degrees C cooler from the remaster dvd than my SDHC card
installation.
On first reboot I created a new savefile on a local hard drive.
I like it
EDIT: I burned another copy of the remaster.iso to use on my Gateway desktop.
remaster.iso to a dvd in Ubuntu-14-04 with brasero (or whatever the
default burner is called).
It's working well, can't get Google-Chrome to start but I downloaded
the latest Firefox and it's working fine.
All the other applications work fine too.
It runs at least 5 degrees C cooler from the remaster dvd than my SDHC card
installation.
On first reboot I created a new savefile on a local hard drive.
I like it

EDIT: I burned another copy of the remaster.iso to use on my Gateway desktop.
- Attachments
-
- gatewaydesktop.jpg
- (77.38 KiB) Downloaded 317 times
-
- remaster.jpg
- (112.92 KiB) Downloaded 443 times
Last edited by Billtoo on Sun 05 Apr 2015, 04:02, edited 1 time in total.
Jamesbond, thanks for uploading nvidia-uvm.ko that helped and I can now run some CUDA programs. However, something's still missing, but I'm not sure exactly what. On FD631 with the nvidia 340.69 legacy driver that I compiled I was able to run more a wider range of CUDA programs. I compared the driver package you uploaded with my 631 build and noticed that quite a few files are still missing from your build, although apparently they shouldn't affect CUDA. So, I will compile the nvidia driver on FD700 and see if I can figure out what additional files are necessary for full CUDA support. Can you please post the build configuration that you've used? So I can mirror the same directory structure of your package instead of using the nvidia default structure.
Who the hell removes Video files from the package in this day and age?step wrote: noticed that quite a few files are still missing from your build.
That would be as idiotic as removing the scroll wheel and click function from the mouse package.
How the hell can booting up from a DVD instead of a SDHC card make your computer run cooler?Billtoo wrote:It runs at least 5 degrees C cooler from the remaster dvd than my SDHC card installation.
That hands down has to be one of the dumbest things i've ever heard.

That would equate to a SDHC card consuming 60 watts of power instead of 200 milliamps.A DVD drive consumes 3x to 4x the amount of power more than a SDHC card just sitting idle and it's still less than 1 watt.
Don't be so ridiculous.

hay leatherface... ( You are a character in Texas Chainsaw... ) reading not a strong point. when I install the manufacturers video card drivers temp dropped for me as well. Not only would a spinning DVD move air the end where the GPU exushusts air is the same as a 3.0 USB port and with it plugged by a device the temp also goes up could be one 9r the other or both. Why do people feel the need to discourage first hand reports, whereas the person with out experience can't fathom just blurts out ignorance as fact.
Here is a possible answer.Ted Dog wrote:Why do people feel the need to discourage first hand reports, whereas the person with out experience can't fathom just blurts out ignorance as fact.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
@mavrothal - very true, unfortunately ...
@step - all the build recipes are located in /usr/src/pkgbuild/pkg (for your nvidia driver it will be /usr/src/pkgbuild/src/nvidia-driver-340.76-x86_64-1).
I built the nvidia driver in two steps:
1. Automated generic driver build - ie the libraries, control panels, etc everything except the kernel module. This is what you see from the recipe above.
2. Manual step: I extracted the driver again (sh NVIDIA-xxx.sh -x) and then went into NVIDIA*/kernel directory, and type "make module" (after making sure that kernel-source is loaded). The nvidia-uvm.ko is located in NVIDIA*/kernel/uvm.
Then I merge the output of these two steps into the package you see on ibiblio.
But this is unnecessarily complex. You could just boot to terminal (no X running), making sure that kernel-source is loaded, then just run "sh NVIDIA-xxx" and follow on-screen instructions. I think Billtoo did it that way too. I can't recall whether you need to disable nouveau first or not, in either case, there is a switch you can tell the installer to keep on going even if nouveau is installed ("sh NVIDIA-xxx --help" will show you the standard switches, "sh NVIDIA-xxx -A" will show you *all* switches).
The end result should be the same except that you can't package the result of direct install (you may be able to if you use sandbox but I won't confuse you further).
I can't recall the details but in 631 I may have included the 32-bit libraries. In 700 I definitely didn't, to save space. If this is the case, you may want to download the version of the driver that does come with 32-bit library, and do the installation with 32-bit compat SFS loaded.
@Billtoo - I will check why google-chrome can't start from the remaster.
EDIT: how did you install chrome? Did you use google-chrome SFS from the repo? Did you install from the menu? if you start it from the terminal, "google-chrome-spot", do you get any error message?
@step - all the build recipes are located in /usr/src/pkgbuild/pkg (for your nvidia driver it will be /usr/src/pkgbuild/src/nvidia-driver-340.76-x86_64-1).
I built the nvidia driver in two steps:
1. Automated generic driver build - ie the libraries, control panels, etc everything except the kernel module. This is what you see from the recipe above.
2. Manual step: I extracted the driver again (sh NVIDIA-xxx.sh -x) and then went into NVIDIA*/kernel directory, and type "make module" (after making sure that kernel-source is loaded). The nvidia-uvm.ko is located in NVIDIA*/kernel/uvm.
Then I merge the output of these two steps into the package you see on ibiblio.
But this is unnecessarily complex. You could just boot to terminal (no X running), making sure that kernel-source is loaded, then just run "sh NVIDIA-xxx" and follow on-screen instructions. I think Billtoo did it that way too. I can't recall whether you need to disable nouveau first or not, in either case, there is a switch you can tell the installer to keep on going even if nouveau is installed ("sh NVIDIA-xxx --help" will show you the standard switches, "sh NVIDIA-xxx -A" will show you *all* switches).
The end result should be the same except that you can't package the result of direct install (you may be able to if you use sandbox but I won't confuse you further).
I can't recall the details but in 631 I may have included the 32-bit libraries. In 700 I definitely didn't, to save space. If this is the case, you may want to download the version of the driver that does come with 32-bit library, and do the installation with 32-bit compat SFS loaded.
@Billtoo - I will check why google-chrome can't start from the remaster.
EDIT: how did you install chrome? Did you use google-chrome SFS from the repo? Did you install from the menu? if you start it from the terminal, "google-chrome-spot", do you get any error message?
Last edited by jamesbond on Sun 05 Apr 2015, 15:17, edited 1 time in total.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
You're being illogical Ted DoggyTed Dog wrote:hay leatherface... ( You are a character in Texas Chainsaw... ) reading not a strong point. when I install the manufacturers video card drivers temp dropped for me as well. Not only would a spinning DVD move air the end where the GPU exushusts air is the same as a 3.0 USB port and with it plugged by a device the temp also goes up could be one 9r the other or both. Why do people feel the need to discourage first hand reports, whereas the person with out experience can't fathom just blurts out ignorance as fact.
Installing the correct video drivers so your card runs at the correct frequency and voltage for a temp drop is not the same as just changing your external boot device.
What is being suggested is as silly as saying your computer runs cooler just changing from a USB stick to an older Floppy drive as the boot media.
Calling people trolls who call out bullshit and speak the truth is becoming tiresome.
This isn't the first time Billtoo has made crazy claims as in a conversation with Bindee he claimed he had perfect Nvidia v-sync even though he hadn't installed the pipeline fix but then went on to say he had sideways judder and posted a pic showing line tearing to contradict what he had said that showed he had v-sync tearing.
So can we all stop with the bullshit and the constant backing up of false hoods and lies just because someone as pavan would say Kisses Butt.
???
Still love you Ted Doggy.

There was a study done that showed that people who thought wikipedia was accurate knowledge tended to have a low IQ and often believed that the Earth and everything was created in 7 days.mavrothal wrote:Here is a possible answer.Ted Dog wrote:Why do people feel the need to discourage first hand reports, whereas the person with out experience can't fathom just blurts out ignorance as fact.
Six out of 10 Wikipedia business entries contain factual errors
http://www.telegraph.co.uk/technology/w ... rrors.html
9 out of 10 health entries on Wikipedia are inaccurate, study finds
http://venturebeat.com/2014/05/28/nine- ... udy-finds/
And so on and so on..........
They say the only thing worse than a troll is someone who posts a wikipedia link.

Great. If you haven't already found it, there's a package in the repo called c720_700-022215. It has a different touch pad driver that works better overall, but right clicks with the button are disabled by default because it doesn't work well. To right click you'll have to two finger tap. The settings for the touch pad are in /root/Startup/touchpad.FD700 works on the Acer C720 Chromebook !
Edit: Also I should say that package includes other things for the c720 and should be used on a new savefile/folder.
Happy Easter!
oh man I feel bad, I got lost in a wikilink bunny trail last night reading up on that link. Did find out why I do not get why trolls troll. At least our troll is the common type according to the 2013 study. Which is someone is upset that someone else did not live up to expectations. Also explains why I hardly ever get troll on.... I give off low expectations
so underachieving protects you from the common troll. 


Saw this
If FD finds it useful, could it be made available in FD REPO or somewhere as an installable to gain feedback?
I know this was considered in the past because it offers a more universal solution for client access to the desktop from ANY LAN PC or smartDevice, but, is it appropriate to ask FD to reconsider @GoingNUTs solution of XRDP as an remote access to FD?JamesBond wrote:Yes, known problem. I was considering the remove these items from the menu (alternative GUI exists), but I left it just in case. Perhaps I should remove them altogether. Will think about it.SSH/SSL VNC Viewer & X11 VNC Server
Both won't work if devx is not loaded (lack of Tcl/Tk).
If FD finds it useful, could it be made available in FD REPO or somewhere as an installable to gain feedback?
Jamesbond, what alternative GUI exists for X11vnc server in FD-700? I always start the server from the system menu and wouldn't know how to start it otherwise...JamesBond wrote:Yes, known problem. I was considering the remove these items from the menu (alternative GUI exists), but I left it just in case. Perhaps I should remove them altogether. Will think about it.SSH/SSL VNC Viewer & X11 VNC Server
Both won't work if devx is not loaded (lack of Tcl/Tk).
Performance is the essence.
This is NOT an attack post and certainly is NOT a demand of any sort. Please regard this post as mere information and does NOT need/desire support/contrast. The mere facts that I show to a prior reference is not pointing any fingers and is merely a instance of the multitude (hundreds in fact) of similar comments that have been made across the forum in the past.
This statement hints at size!
impact performance, AND, that path-length thru the code is what translates to performance, such that "shorter is faster". Thus, Size is NOT, and never was, a measure of superiority!
So, this is information that I think needs stating, again, so that members understand that size has ABSOLUTELY 'little-to-nothing' to do with performance.
When I boot my PC (and since I rarely boot my main PCs) I am most concerned not about its ISO size, rather, about its performance to carry out the tasks it offers me to do useful things, out-of-the-box (OOTB).
This distro and all other 64bit distro, work with the same hardware consideration. I would hope that in 64bit distros, all of the developers are considering benefit versus size as the primary presentation to its community of expected users. If your benefit is small, that's OK. If your benefit is large, that's OK. But, I hope most of us, as users, understand that its the benefit we are looking for, rather than sizes. Performance is seen once the distro hits the desktop. (And everyone of us wants instantaneous performance every-time we touch our PCs, although, in reality, everything takes time executing the instructions necessary for our touching needs.)
Again, this is NOT an attack and it is certainly is NOT a demand. I see FD700 as facilitating this along with the other 64bit distros we are now seeing in this community.
FYI
This statement hints at size!
I want to begin by merely sharing some facts that we are all aware of:...libraries. In 700 I definitely didn't, to save space. If this...
- In 2005, Puppy's beginning, this community of users ONLY had 32bit PCs (some still had 16bit)
- Today's community users have vastly different PCs with many-most have "enormous RAM/HDD sizes" than what we had in 2005.
- In 2006, the PC spec changed and 64bit PC became cost-effective to the Public
2007 to date, excepting for some ARM/TI/ATOM/others technology, all PCs from Intel/AMD are 64bit. - Years later, we got FATDOG to take advantage of the bus changes to benefit PC performance (Thank you @Kirk)
- The smallest PC from vendors was 1GB with larger HDDs than meager 32bit PC not to mention that excepting Netbooks, all 64bit PCs have DVD recording.
- USB sticks costs have reduced and in some stores, the smallest USB sold today is 4GB @$5(ca).
- For most in the community, we have seen our download speeds, both from the servers as well as thru our network, change dramatically.
- The landfills today and 2ndhand shops everywhere are filling with 64bit PCs being the greater majority.
impact performance, AND, that path-length thru the code is what translates to performance, such that "shorter is faster". Thus, Size is NOT, and never was, a measure of superiority!
So, this is information that I think needs stating, again, so that members understand that size has ABSOLUTELY 'little-to-nothing' to do with performance.
When I boot my PC (and since I rarely boot my main PCs) I am most concerned not about its ISO size, rather, about its performance to carry out the tasks it offers me to do useful things, out-of-the-box (OOTB).
This distro and all other 64bit distro, work with the same hardware consideration. I would hope that in 64bit distros, all of the developers are considering benefit versus size as the primary presentation to its community of expected users. If your benefit is small, that's OK. If your benefit is large, that's OK. But, I hope most of us, as users, understand that its the benefit we are looking for, rather than sizes. Performance is seen once the distro hits the desktop. (And everyone of us wants instantaneous performance every-time we touch our PCs, although, in reality, everything takes time executing the instructions necessary for our touching needs.)
Again, this is NOT an attack and it is certainly is NOT a demand. I see FD700 as facilitating this along with the other 64bit distros we are now seeing in this community.
FYI
Well said gcmartin but i'm sure you will just be called a troll.
I'm surprised John Murga allows this project to continue as it completely breaks the Puppy Linux concept of KISS ( Keep it simple stupid ) as 99% of the problems seem to be with what James and Kirk have left out or removed.
Fatdog should heave been based on a tried and tested platform such as Debian and made fully compatible with standard off the shelf install packages.
If there was then a problem we could all piss off too google or the Debian forum for real support instead of bollocking about with a hacked up packages for the sake of a few megabytes of ram.
Fatdog may be considered free by some but it's not free for the amount of time it wastes out of your life that you will never get back again , so in that aspect it's very expensive and something which James and Kirk seem to have no consideration for because they seem to have this twisted concept that we should be grateful for their time creating a project that wastes our time.
People need to stop sucking up and sugar coating things and being blatantly honest as you shouldn't have to apologize for pointing things out.
A project is in a bad place when you have to worry about the Ego's of the dev.
I'm surprised John Murga allows this project to continue as it completely breaks the Puppy Linux concept of KISS ( Keep it simple stupid ) as 99% of the problems seem to be with what James and Kirk have left out or removed.
Fatdog should heave been based on a tried and tested platform such as Debian and made fully compatible with standard off the shelf install packages.

If there was then a problem we could all piss off too google or the Debian forum for real support instead of bollocking about with a hacked up packages for the sake of a few megabytes of ram.
Fatdog may be considered free by some but it's not free for the amount of time it wastes out of your life that you will never get back again , so in that aspect it's very expensive and something which James and Kirk seem to have no consideration for because they seem to have this twisted concept that we should be grateful for their time creating a project that wastes our time.
People need to stop sucking up and sugar coating things and being blatantly honest as you shouldn't have to apologize for pointing things out.
A project is in a bad place when you have to worry about the Ego's of the dev.
To gcmartin,
Bustle and waffle is not industry, but with nearly 50 golden years in the IT industry and as the principal history lecturer on this Forum - surely you can publish a distro which is perfection in your own eyes (just tweak the work of any other Forum member(s) and share the credit).
Get usefully active, but circumnavigate the circles. Don't tell the developers what to do - show them (and all of us) what you can do.
Bustle and waffle is not industry, but with nearly 50 golden years in the IT industry and as the principal history lecturer on this Forum - surely you can publish a distro which is perfection in your own eyes (just tweak the work of any other Forum member(s) and share the credit).
Get usefully active, but circumnavigate the circles. Don't tell the developers what to do - show them (and all of us) what you can do.
gcmartin,
Size of the distro is something we keep in mind for a couple reasons. Boot speed goes down the bigger we make the iso, while that may matter little in your use case, for others it's a bigger deal, usually folks with laptops or booting from USB. And making suspend work is not always easy or even possible depending on the hardware and kernel combination. The other significant reason is that we load the whole OS into RAM. Again, if you have lots of RAM, no problem. But if you don't then the ram we use to store the OS is now not available to run programs. All that said Fatdog64 will continue to grow in size, every package we update is almost always larger in the end and we want things to work. But we do have to watch the Fatdog's weight
Size of the distro is something we keep in mind for a couple reasons. Boot speed goes down the bigger we make the iso, while that may matter little in your use case, for others it's a bigger deal, usually folks with laptops or booting from USB. And making suspend work is not always easy or even possible depending on the hardware and kernel combination. The other significant reason is that we load the whole OS into RAM. Again, if you have lots of RAM, no problem. But if you don't then the ram we use to store the OS is now not available to run programs. All that said Fatdog64 will continue to grow in size, every package we update is almost always larger in the end and we want things to work. But we do have to watch the Fatdog's weight

I've updated the c720 package. It's now called c720_700-04515. The xf86-input-cmt developer fixed the right click problem. Working pretty nice now.FD700 works on the Acer C720 Chromebook !
Great. If you haven't already found it, there's a package in the repo called c720_700-022215. It has a different touch pad driver that works better overall, but right clicks with the button are disabled by default because it doesn't work well. To right click you'll have to two finger tap. The settings for the touch pad are in /root/Startup/touchpad.
Edit: Also I should say that package includes other things for the c720 and should be used on a new savefile/folder.