Fatdog64-630 & 631 Final (May 12 2014)

[Puppus Dogfellow]

fatdog64-630 mirrored.

[Sage]

Sorry guys cannot connect via my onboard RTL8201CL, (which also masquerader as a SiS190?), nor will any of my bog std. wifi sticks (150 nor 300) connect via wlan. Added to which, this is the weirdest set of network utilities* ever espied - where did they come from? Hopefully, not Frisbee which is an eternal curse on connectivity. Already wasted oodles of time. Any road up, they don't work!
630Final is a serious retrograde step from earlier RCs - and on the same range of AMD and i hardware. Shame, just as I was beginning to like it. None of the majors have this issue - strongest recommendation has to be Mint.

*even caused a whole machine crash on one occasion trying to scan wlan.

[prehistoric]

Tried nvidia 331.38-3.12.9.pet, but got no video at all under xwindows. Took a couple of tries to get to the point I could uninstall pet using Fatdog package manager. I'm back to the frame buffer driver.

This is probably a legacy nvidia video device, or at least older, are there any drivers which can be used with 630?

[Billtoo]

Installed to a 16gb usb 3.0 flash drive.

video-info-glx 1.5.3 Mon 17 Feb 2014 on Fatdog64 630 Linux 3.12.9 x86_64
0.0 VGA compatible controller: nVidia Corporation GF114 [GeForce GTX 560 Ti] (rev a1)
oem: NVIDIA
product: GF110 Board - 12630002 Chip Rev
X Server: Xorg Driver: nvidia
X.Org version: 1.15.0
dimensions: 1920x1080 pixels (602x343 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 560 Ti/PCIe/SSE2
OpenGL core profile version string: 4.4.0 NVIDIA 334.16

Network controller Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe

The latest beta of the proprietary nvidia driver compiled okay.

[Billtoo]

If anyone wants it I found newer source code for gtktetris and made a pet of it, this
keeps track of your high scores.
After installing the pet restart x to update the menu.
Works for me.

[jamesbond]

Tried nvidia 331.38-3.12.9.pet, but got no video at all under xwindows. Took a couple of tries to get to the point I could uninstall pet using Fatdog package manager. I'm back to the frame buffer driver.

Sorry to hear this one doesn't work. You can uninstall from command line simply by typing:
"silent_petget package-name uninstall"
or if you forgot the package name
"silent_petget /root/.packages/pacge-name (use tab completion to fill-in the package name) uninstall".

This is probably a legacy nvidia video device, or at least older, are there any drivers which can be used with 630?

There is also a nvidia legacy driver 304.119 in the repo, also for kernel 3.12.9...

[Ted Dog]

I downloaded the nv driver hopefully It will work for me.. Ive been playing with older fatdogs with Nvidia to boot minimac.. I got it to work awhile back but its not been successful. The mac may have been updated and not boot same. Cant recall the admin pass to bless my efforts.

[Sage]

Welcome to Bulldog Linux

CLI ???

[jamesbond]

Welcome to Bulldog Linux

CLI ???

From Fatdog's FAQ: http://distro.ibiblio.org/fatdog/web/fa ... tions.html:

basesfs=none
This instructs Fatdog64 not to use any basesfs at at all. Booting with no basesfs will run a console-only minimal system based on busybox (bulldog).

If you've got this prompt when you're not using "basesfs=none", it means that the Fatdog64 somehow fails to find your (externally located) fd64-630.sfs and thus fallback to running everything from initrd; hopefully to be able to recover and boot the full Fatdog.

[Sage]

Yes, got all those messages plus asking for login, thanks jb.
Maybe my oversight - borrowed stick of mem for another machine and substituted 512. Perhaps that's not enough for FD? Can't swap back again today.
For the record, what would be the P/W? And what should be the desktop GUI start command? xwin or startx? Tried the latter - no go.

[neerajkolte]

Hi I am new to Linux.
Just few days ago I installed FD64-630 RC2 on my 1gb usb which was just laying around.
And now I am using FD64 Final.
I installed it in Win7 through an app yumi2.0 I found on pendrivelinux site.

I have 2 questions
1. My system takes almost 45sec to boot is this normal.
I am using

Processor : 4x Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz
Memory : 6010MB (394MB used)
Machine Type : Physical machine
Operating System : Fatdog64 [ba31d2d557]
User Name : root (root)
Date/Time : Tue Feb 18 15:50:58 2014
-Display-
Resolution : 1920x1080 pixels
OpenGL Renderer : Mesa DRI Intel(R) Ivybridge Desktop
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : HDA-Intel - HDA Intel PCH


2. Could anyone tell me how to enable the panel shown at right side in image1 posted by Billtoo. I couldn't find it.

[smokey01]

2. Could anyone tell me how to enable the panel shown at right side in image1 posted by Billtoo. I couldn't find it.

Download these two pets then click on them to install them.
http://www.smokey01.com/software/Fatdog ... x86_64.pet
http://www.smokey01.com/software/Fatdog ... x86_64.pet

[smokey01]

Has anyone managed to get Teamviewer9 working in Fatdog-630?

Thanks

[neerajkolte]

Download these two pets then click on them to install them.

Installed and got it working.
Thanks smokey01.

[DC]

Hi kirk,

Quote:

Has anybody tried to get Pipelight working in any puppies?
First I've heard of it. I'll take a look.

Depends on Wine, so I'm not sure what the point would be. Maybe a Windows browser running under Wine can't run Silverlight?

pipelight comes with its own version of a patched wine browser plugin. It does not need normal wine. Just needs ia32-libs and pipelight

As previously mentioned it runs fine in Mint 16 - 32bit and 64bit using Firefox or Opera. But I would still like to get it running under Fatdog as puppy linux is my preferred distro and Fatdog has been my main desktop for the last 2/3 years.

thanks

dc

p.s. works for Netflix

[jamesbond]

Yes, got all those messages plus asking for login, thanks jb.
Maybe my oversight - borrowed stick of mem for another machine and substituted 512. Perhaps that's not enough for FD? Can't swap back again today.

512MB used to be enough for Fatdog, but thanks recent inclusion of inittmpfs patch, it is no longer enough (min 1GB is now required) unless one can use the magic incantation on kernel command line. The magic words are "rootfstype=ramfs". Mind you, though, running Fatdog on 512MB machine is quite limiting ...

For the record, what would be the P/W?

None. Just press Enter. In the future, this may change to the regular puppy password you already know

And what should be the desktop GUI start command? xwin or startx? Tried the latter - no go.

There is no GUI command. If you find yourself in "bulldog", you're basically running from initrd; you only have busybox commands at your disposal. No GUI, no X, no graphical desktop. At one time I was interested to put some lightweight GUI on it (that's why I have been watching "Puppy In-House development thread" and got very excited the Iguleder built x86-64 version of Xfbdev; but it is still just a plan for now).

1. My system takes almost 45sec to boot is this normal.

Tell me which part seems to take the longest - my guess is the bootloader portion (syslinux/grub), that is, before you see the words "decompressing kernel".

If it is, then you can use a small initrd. There are official and unofficial ways to create small initrd (use fatdog-split-initrd command); if you want the smallest and fastest you need to use the official way; otherwise you can use the unofficial way as below:
- after you boot, find your initrd using Rox, and then (double-)click to open it.
- move fd64-630.sfs to the root of your boot disk
- repack initrd
- in your bootloader command line, add these magic incantations: "waitdev=5 basesfs=local"

Otherwise tell us where is the time the system spent the most during booting.

[jamesbond]

I downloaded the nv driver hopefully It will work for me.. Ive been playing with older fatdogs with Nvidia to boot minimac.. I got it to work awhile back but its not been successful. The mac may have been updated and not boot same. Cant recall the admin pass to bless my efforts.

There are quite a few of older nvidia legacy drivers; I only built the latest "legacy" driver. Very old cards require drivers from older legacy drivers (195 branch or perhaps even 76 branch... (note: branch versions may be wrong, I just recall from memory, I don't bother to google, but you can check the details on nvidia website to get the exact details).

[Ted Dog]

Mine is same series as Billtoos so non legacy... any chance we could get that dup removal program fslint compiled for 64bit. It should work better since it does stuff in parallel..

[jamesbond]

any chance we could get that dup removal program fslint compiled for 64bit. It should work better since it does stuff in parallel..

C'mon Ted, I know you build stuff yourself too Okay, where's the source URL?

[Ted Dog]

lol did not get dev yet... its big and do not wish to use my data plan on the stuff that may not make it successfully from that supper slow download site..
Ive been using my phone to download stuff, its the fastest internet here in the deep wilderness of near nowhere internet.
Also cant figure out steps to make 64bit pets... I just make a multisession save session and change the name to whatever package name. But that makes a bunch of cruft not good to share..