Fatdog64-700 beta2 [Closed]

[Pelo]

FatDog would'nt be a Puppy Linux ? it' looks like Porteus, with new apps in the menu (Shotcut, screencast) Puppy packages can't be used, Fatdog saves too.
As Porteus FatsDog does not load the last save at start. But saves exist
Never with Porteus i succeeded retrieving my passed sessions
Sorry messieurs. I first noticed my remarks, now i go and translate what is said inside this english spoken topic).
Install goes very well,

shutdown is a problem :
FatDog does not want to exit without saving.
When I save it does not load my save fd64save-premierpas.ext4 at boot.

7 pages, i will look at it avec a good but light breakfast. (croissants)
"This pet has worked on Lucid 5.2.8.6, Slacko 5.3.3, Precise 5.6, and Precise 5.7" Surprise. So pets from Puppy will run on Fatdog !?

[yerc1]

Kirk and James, take care brothers. Family should always come first. I wish them a fast recovery.
Thanks for all your work.

+1

After a bit more time with Fatdog64-700b on my chromebook, i found that my wireless and touchpad issues were a result of my non-familiarity with Fatdog and its tools, wpa_gui and flSynclient (Control Panel, Desktop, Adjust Touchpad).

A few adjustments within the tools and wireless is now working (with occasional disconnect/reconnect). I'm happy with touchpad too.

With Fatdog, the chromebook is no longer a browser-only device.
Thanks for a great linux distribution.

Take care

[neerajkolte]

@Pelo did you put your savefile on usb drive, If yes please add waitdev=5 boot option. Fatdog is configured to boot fast but Sometimes usb devices take time to load while booting. This was the case for me while I was trying FD630rc2. Now I use Savefolder that too on HDD.
More info about fatdog boot option can be found at file:///usr/share/doc/faqs/boot-options.html inside your fatdog system.

Thanks.

- Neeraj.

[neerajkolte]

"This pet has worked on Lucid 5.2.8.6, Slacko 5.3.3, Precise 5.6, and Precise 5.7" Surprise. So pets from Puppy will run on Fatdog !?

Some pets which contain simple scripts or some compiled for 64bit like slacko64 or lighthouse64 do work on Fatdog but others need to be made for Fatdog specifically. I suspect the printer driver that @rek769 asks might be one of them that need to be compiled for FD.
It's a hit or miss case. I do use thred-get, pup-advert-blocker and many more puppy tools in my FD. Just try them.

Search what you want in Fatdog Package Manager in FD631 or Gslapt in FD700. If not found, ask here.

Thanks.

- Neeraj

[L18L]

Note: Do not use Puppy pet packages in Fatdog64, Puppy's 32bit packages won't work.

[JustGreg]

rek769,

There is a known problem with printing in the 700 beta versions. The beta version is for testing and should not be used for day to day operations. It maybe better to use the stable 630 version of fatdog64. The 630 version is what I use for my normal day to day stuff. I do know the printing works as expected. The 630 version uses Puppy packages.

The printing problem should be eliminated in the final release of 700.

I hope this helps.

[jangelelcangry]

oops! Wrong page.

[vvvora]

Sometimes if the printer disappears, I try

# service cups restart

and that seems to get my printer loaded into cups properly once again.

I hope that helps!

[step]

I don't know if this is could be an issue - or point to an issue - or nothing, but I'm reporting it to the devs anyway. While running fatdog-split-initrd.sh I got a couple of depmod warnings, see the second half of the output capture below. I'm about to use the split-out initrd in a few minutes. I'll post again if I get stuck.

Code: Select all

# fatdog-split-initrd.sh /aufs/devbase/puppy-fd64-700b2/initrd /aufs/devbase/tmp
511427 blocks
Parallel unsquashfs: Using 2 processors
3560 inodes (4040 blocks) to write

[=============================================================-] 4040/4040 100%

created 3481 files
created 666 directories
created 79 symlinks
created 0 devices
created 0 fifos
Parallel unsquashfs: Using 2 processors
19480 inodes (22885 blocks) to write

[===========================================================/] 22885/22885 100%

created 16691 files
created 1871 directories
created 2441 symlinks
created 0 devices
created 0 fifos
Parallel mksquashfs: Using 2 processors
Creating 4.0 filesystem on /aufs/devbase/tmp/fd64.sfs, block size 131072.
[===========================================================\] 24405/24405 100%

Exportable Squashfs 4.0 filesystem, xz compressed, data block size 131072
	compressed data, compressed metadata, compressed fragments, compressed xattrs
	duplicates are removed
Filesystem size 260619.20 Kbytes (254.51 Mbytes)
	31.89% of uncompressed filesystem size (817358.95 Kbytes)
Inode table size 199422 bytes (194.75 Kbytes)
	23.21% of uncompressed inode table size (859304 bytes)
Directory table size 230254 bytes (224.86 Kbytes)
	40.79% of uncompressed directory table size (564495 bytes)
Number of duplicate files found 562
Number of inodes 25219
Number of files 20172
Number of fragments 2086
Number of symbolic links  2520
Number of device nodes 0
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 2527
Number of ids (unique uids + gids) 13
Number of uids 7
	root (0)
	spot (502)
	unknown (493)
	unknown (1001)
	unknown (501)
	webuser (504)
	lp (9)
Number of gids 11
	root (0)
	users (500)
	lp (111)
	spot (502)
	tty (3)
	ftp (1000)
	bin (2)
	vboxusers (1001)
	guest (501)
	webgroup (504)
	lpadmin (112)
depmod: WARNING: could not open /tmp/module-iUAcD1P6/lib/modules/3.17.1/modules.order: No such file or directory
depmod: WARNING: could not open /tmp/module-iUAcD1P6/lib/modules/3.17.1/modules.builtin: No such file or directory
Parallel mksquashfs: Using 2 processors
Creating 4.0 filesystem on /tmp/initrd-IVC9Sku2/kernel-modules.sfs, block size 131072.
[=================================================================|] 14/14 100%

Exportable Squashfs 4.0 filesystem, xz compressed, data block size 131072
	compressed data, compressed metadata, compressed fragments, compressed xattrs
	duplicates are removed
Filesystem size 57.60 Kbytes (0.06 Mbytes)
	25.66% of uncompressed filesystem size (224.50 Kbytes)
Inode table size 282 bytes (0.28 Kbytes)
	36.62% of uncompressed inode table size (770 bytes)
Directory table size 338 bytes (0.33 Kbytes)
	63.53% of uncompressed directory table size (532 bytes)
Number of duplicate files found 1
Number of inodes 24
Number of files 15
Number of fragments 2
Number of symbolic links  0
Number of device nodes 0
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 9
Number of ids (unique uids + gids) 1
Number of uids 1
	root (0)
Number of gids 1
	root (0)

[smokey01]

Recently I discovered that the slideshow function in peasydisc-3.0 would not work. Part of the reason was the missing peasydisc-extras package with 64bit binaries.

The other reason was dvdauthor required re-compiling. Thanks to Catdude's investigatory work and compiling prowess, this has now been fixed. It also bumps the version up to 0.7.1.

To make rcrsn51 great package work in Fatdog64-700b2 you need to add the following three packages:
http://smokey01.com/fd700/packages/dvda ... 6_64-1.txz
http://smokey01.com/fd700/packages/libn ... 6_64-1.txz
http://smokey01.com/fd700/packages/peas ... 6_64-1.txz
This is the skinny way to do it.

If you don't care about space simply add:
http://smokey01.com/fd700/packages/netp ... 6_64-1.txz and the dvdauthor package.
I don't think the netpbm-advanced-10.64.1-x86_64-1.txz in the repo has the netpbm library included.

Enjoy

[rcrsn51]

There is a known problem with printing in the 700 beta versions.

????????

Since 2012, the forum has contained a section devoted to printing in Fatdog. IIRC, there is a link to it in the Fatdog FAQS.

[JustGreg]

Excuse me, rcrsn51, I said it was only the beta versions of Fatdog64 700 that had the problem with printing. Both official version 700 beta (1 and 2) are missing the files ghostscript and ps2pdf. This was discussed here (http://www.murga-linux.com/puppy/viewto ... 4&start=30), which is page 3 of the Fatdog64 700 beta 1 version thread. The two files (ghostscript and ps2pdf) are needed for printing.

This is why peasy print pet does not work correctly. This is why I said

The 630 version is what I use for my normal day to day stuff. I do know the printing works as expected. The 630 version uses Puppy packages.

The printing problem should be eliminated in the final release of 700.

Yes, there is information on how to print on Fatdog64. Printing works well in Fatdog64 version 630. I am sure the final released 700 version will have the problem corrected.

[rcrsn51]

I am sure the final released 700 version will have the problem corrected.

The absence of Ghostscript was a decision by the Fatdog team. Many printer drivers will work without it if CUPS is built to use Poppler tools instead.

Since ps2pdf is a component of Ghostscript, programs like PeasyPrint will break. This situation was known in advance and the assumption was that users would install Ghostscript from the repo if they needed it.

However, the recent requests for help with printing are different. They are of the variety "is there a 64-bit version of my printer driver?" or "how do I install a PET in FD700?".

Those problems can be dealt with now, independent of the Ghostscript issue.

[step]

I have updated exiftool-fd64 to version 9.76-1 here http://murga-linux.com/puppy/viewtopic. ... 845#801845

• exiftool 9.76 packaged for FD64 700. Exiftool needs perl, which is included in the FD64 700 devx SFS. If you use fotoxx this package is needed to enable menu entry Info>View Info, which displays jpeg comments. Package now includes ROXapp and ROX right-click menu entry for jpeg files.

[step]

In beta 2 (and beta 1) starting X11vnc server from system menu entry Network>X11VNC Server invariably fails, that is, after about 20 seconds an x11vnc Properties dialog pops up with error message:

The x11vnc program failed to start!

Maybe there is another VNC server
already listening on port 5900?

You will need to start over after
you make sure x11vnc can start.

Typing 'x11vnc' in a Terminal starts the server without problem. So does 'x11vnc-gui'. So maybe x11vnc-gui could replace the current menu entry?

It would be nice if x11vnc-gui used option -usepw instead of its own cleartext password file. By default usepw saves a weakly crypted password in ~/.vnc/passwd.

[JustGreg]

The CUPS program does not work correctly with Fatdog64 700 beta versions (see comments on page 8 of this thread).

The issue can be resolved by using Gslapt (either with menu entry in setup or in the control panel system utilities). The two (2) programs needed are ghostscript-9.10-x86_64-1.txz and ghostscript-std-fonts-8.11-noarch-1.txz. Both are in the standard ibibilio.org repository (http://ibiblio.org/fatdog/packages/700).

One needs to ensure the Gslapt is looking at the correct repository. One uses the preferences entry in the edit menu. When the preferences window is opened, click on the sources tab to view the which repositories are been used. Make sure the ibibilio fatdog 700 package one is selected. After closing the preferences window, click on the update button to ensure the latest list of packages is available. Search on the word "ghostscript" and the two needed packages will be shown. Select them and right-click on each. The pop up menu will appear. Select "install" option for each of them. To complete the installation of the packages, click on the execute button (should no longer be "grayed out"). Gslapt will download and install them.

The speed of downloads from ibibilio is dependent on time of day and can be slow. After Gslapt has completed its operations, a popup window will show the operations have been completed.

With the correct print driver for the printer you are using installed, CUPS should allow you to select the printer and print from applications as needed.

I hope this helps,

[vvvora]

Solution:

(Leave it to me to post a question only to figure it out minutes later...)

# cdrecord -scanbus dev=ATAPI

that seems to work for me.

Thanks again!

Hello,

I was wondering if anyone else has tried

# cdrecord -scanbus

and seen it fail.

The cdrecord in FD64 on my system doesn't work the way it used to. Is there a page that would help explain the correct usage of cdrecord in the FD64 environment?

Thanks again,

VVV

[JustGreg]

Thanks, vvora, for the problem and solution. Yes this happens

(Leave it to me to post a question only to figure it out minutes later...)

to a lot of us.

In my case, it is usually longer than minutes. Often, the process of writing out the problem provides the ideas to solve it

[vvvora]

Another question, probably with an obvious answer.

I've tried to play an audio cd from my computer, and this isn't working. Audio CDs seem to show up as blank discs.

Is there a player that I can install? I was going to install mplayer from gslapt, but then it said that it needed a library that doesn't exist.

Thanks again,

VVV

[JustGreg]

Yes, vvora, if you just click on the cd disk icon, fatdog64 version 700 beta2 tries to mount it as a normal data disk. The result is an empty directory because it is an audio.

To play (i.e. listen) the audio tracks, one can use VLC media player to select and play the disk. VLC media player is under the Multimedia tab of the Menu (lower left hand corner). Once VLC is up and running, one clicks on the Media entry on the tool bar. This will show options, select "Open Disc". This will show the Selection Window. Just select the "Audio CD" button and click on "Play". After a few moments(about six seconds in my case), the audio should be heard.

If you want to "rip" the audio tracks, then one can use "Peasy Disc optical disc tools" under the Multimedia tab of the Menu. Select audio tab of the window and fill in the options.

There is an information section in ibiblio.org repository. The main page is here:http://distro.ibiblio.org/fatdog/web/. You can find a lot about using fatdog64 under the documentation section.
There is a reference to an excellent beginner's guide written by smoke01. It covers most of the normal operations.

I hope this helps.