Fatdog64-611 Final (Updated 12-14-2012)

A home for all kinds of Puppy related projects
Message
Author
User avatar
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#301 Post by smokey01 »

JustGreg in Control Panel under Desktop there is an Adjust Touch Pad tool (flSynclient) where you can turn your touch pad off. Have you tried this?

I don't have a 64bit Laptop so I can't test it but it works fine on my 32bit laptop under Dpup Exprimo.
Last edited by smokey01 on Sat 02 Feb 2013, 00:10, edited 1 time in total.

gcmartin

Re: Minor issues with pathing for utitities.

#302 Post by gcmartin »

rcrsn51 wrote:
gcmartin wrote:Seem that the current PPM version for SAMBA has the same problem.
Which Samba version are you talking about? The built-in version or Samba 3.6.5 from the repo?
I checked 3.6.5 and testparm worked OK.
Minor issues with pathing for utitities.
Please explain.
AS you know, I run Live media (DVD boot in this case expressing "media" at boot time.

@Kirk and all, nevermind. I have a update to that post.

For some reason for which I cannot explain, my post's problem has resolved. Here's what happen, but does NOT explain "why".
  1. I am running FATDOG from DVD on an 4GB X2 system.
  2. I downloaded a very large distro via browser, which only allows storage into the RAM based filesystem.
  3. A notification popped indicating "system running short of resources ..."
  4. I opened ROX and moved items from the RAM filesystem to permanent stores.
  5. while moving files, I opened a terminal to check which name was assigned for community share and found the problem with "testparm".
  6. I noted it, restarted the X desktop and posted the problem.
I remembered this 'testparm" problem from years ago and made an assumption. (that experience does NOT apply to this problem)
Note: This system has NOT been rebooted since its initial save session to Live media.

@Rcrsn51 thanks. I just reopened a terminal and the system now executes "testparm" as it should.

Sorry, but I still cannot find why that occurred.

Thanks for your help

JustGreg
Posts: 782
Joined: Tue 24 May 2005, 10:55
Location: Connecticut USA

#303 Post by JustGreg »

Thanks Smoke01. Yes the control panel applet works same with a 64 bit as 32 bit. It takes care of the problem. It does save the touch pad state so the touch pad is still off after a reboot. I just finished testing it.

That solves my problem, but, is there a way to use function key to do the same? This is more of an interest of mine rather that something that needs to be done. Thank you in advance for any help on the use of function keys.
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much

User avatar
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#304 Post by smokey01 »

JustGreg wrote:Thanks Smoke01. Yes the control panel applet works same with a 64 bit as 32 bit. It takes care of the problem. It does save the touch pad state so the touch pad is still off after a reboot. I just finished testing it.

That solves my problem, but, is there a way to use function key to do the same? This is more of an interest of mine rather that something that needs to be done. Thank you in advance for any help on the use of function keys.
Fn+F4 will toggle your touchpad on/off. It calls the following script:
/usr/bin/toggle-touchpad.

If you don't like the Fn-F4 key combination you can make your own with sven. Sven is in the taskbar, right click on it a choose preferences.

capicoso
Posts: 172
Joined: Fri 13 Jan 2012, 23:38
Location: Argentina

#305 Post by capicoso »

How can this be translated to spanish?
I'm surprised that nobody translated it already. I'd translate it if there are tools to do so? Like the scripts on other puppies. Or someone could point me in the right direction...

User avatar
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#306 Post by smokey01 »

This should get you started.

http://www.bkhome.org/blog/?viewDetailed=02676

http://bkhome.org/fossil/woof2.cgi/arti ... 512793a015

http://murga-linux.com/puppy/viewtopic.php?t=73440
capicoso wrote:How can this be translated to spanish?
I'm surprised that nobody translated it already. I'd translate it if there are tools to do so? Like the scripts on other puppies. Or someone could point me in the right direction...

User avatar
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#307 Post by smokey01 »

smokey01 wrote:This should get you started.

http://www.bkhome.org/blog/?viewDetailed=02676

http://bkhome.org/fossil/woof2.cgi/arti ... 512793a015

http://murga-linux.com/puppy/viewtopic.php?t=73440
capicoso wrote:How can this be translated to spanish?
I'm surprised that nobody translated it already. I'd translate it if there are tools to do so? Like the scripts on other puppies. Or someone could point me in the right direction...

capicoso
Posts: 172
Joined: Fri 13 Jan 2012, 23:38
Location: Argentina

#308 Post by capicoso »

smokey01 wrote:
smokey01 wrote:This should get you started.

http://www.bkhome.org/blog/?viewDetailed=02676

http://bkhome.org/fossil/woof2.cgi/arti ... 512793a015

http://murga-linux.com/puppy/viewtopic.php?t=73440
capicoso wrote:How can this be translated to spanish?
I'm surprised that nobody translated it already. I'd translate it if there are tools to do so? Like the scripts on other puppies. Or someone could point me in the right direction...
Thank you.
Both tools look good. Will try them.
I think i was talking about MoManager when i said "Like the scripts on other puppies", because i think i didn't see it installed on fatdog by default

User avatar
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#309 Post by smokey01 »

I think MoManager will work with Fatdog but I haven't tried it.

capicoso wrote:
Thank you.
Both tools look good. Will try them.
I think i was talking about MoManager when i said "Like the scripts on other puppies", because i think i didn't see it installed on fatdog by default

JustGreg
Posts: 782
Joined: Tue 24 May 2005, 10:55
Location: Connecticut USA

#310 Post by JustGreg »

Thanks Smoke01. I saw Sven before. Now I have a reason to use it.
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much

User avatar
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#311 Post by smokey01 »

JustGreg wrote:Thanks Smoke01. I saw Sven before. Now I have a reason to use it.
In case you weren't aware, Sven is all ready part of Fatdog.

Cheers.


User avatar
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#313 Post by smokey01 »

A few weeks back I brought myself a BluRay burner. I have just installed it to discover things don't work as expected. It won't read or write to BluRay disks. The burner is an LG BH14NS40. The disk I tried to burn is a Verbatim BD-RE

The BR disk I tried to watch was "Friends with Benefits" but it threw up an error about no keys or something.

I tried to burn with Pburn 3.7.11. I played around with the settings a bit but was still unsuccessful.

It will read and write DVD.

Any ideas? I am using FD-611, the Seamonkey version.

Cheers

to.scared.to.say
Posts: 4
Joined: Sun 03 Feb 2013, 20:40

#314 Post by to.scared.to.say »

The BR disk I tried to watch was "Friends with Benefits" but it threw up an error about no keys or something.
You need to install a key file in /root/.config/aacs named KEYDB.cfg and optionally a file named vuk. You can read about this here:

https://wiki.archlinux.org/index.php/BluRay

I've uploaded a pet to here:

http://www.mydrive.ch/

user name: fatdog@to.scared.to.say
password: fatdog

It's in the test folder. It contains the latest KEYDB.cfg I can find and the latest vuk collection I can put together.

After you install the keys you have to first mount the Bluray and then open VLC and select media, open-disk, and BluRay. If you still get an error then the BluRay is too new. The key file only supports up to MKB version 28.

Don't ask who I am. Not legal here to play Blurays you own without giving money to player/software makers who give money to politicians :)

User avatar
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#315 Post by smokey01 »

To.scared.to.say, check your pm.

Sage
Posts: 5536
Joined: Tue 04 Oct 2005, 08:34
Location: GB

#316 Post by Sage »

To, too, two, tutu.
Which?

rdog
Posts: 25
Joined: Mon 18 Oct 2010, 20:47
Location: Quesnel, BC, Canada

Error 16 booting FatDog64 611 from grub

#317 Post by rdog »

I decided to try Fatdog64-611-firefox.iso and Fatdog64-611-seamonkey.iso and I am getting the same error from both while attempting to boot from a frugal install using grub. Booting from the iso burned to a DVD+RW works fine. The downloaded ISO's md5sum to the correct values.

Let me explain...
# pwd
/mnt/sda2/fd64
# ls -la
total 207072
drwxr-xr-x 2 root root 4096 Feb 5 11:52 .
drwxr-xr-x 10 root root 4096 Feb 6 08:37 ..
-rw-r--r-- 1 root root 208261680 Dec 14 12:50 initrd
-rw-r--r-- 1 root root 3767056 Dec 14 12:50 vmlinuz

# cat /mnt/sda2/boot/grub/menu.lst
# GRUB configuration file '/boot/grub/menu.lst'.
#
# Start GRUB global section
default 0
#timeout 5
timeout 5
color light-gray/blue black/light-gray
# End GRUB global section
# Linux bootable partition config begins
title Puppy Linux 5.4.3 (hard disk hd0,1)
root (hd0,1)
kernel /puppy54/vmlinuz psubdir=puppy54
initrd /puppy54/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy Linux 5.4.3 pfix=ram (no pupsave file loaded, HD as hd0,1)
root (hd0,1)
kernel /puppy54/vmlinuz pfix=ram psubdir=puppy54
initrd /puppy54/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title FatDog64 version 611 (hard disk hd0,1)
rootnoverify (hd0,1)
kernel /fd64/vmlinuz
initrd /fd64/initrd
# Linux bootable partition config ends
# Linux bootable partition config begins
title FatDog64 Seamonkey 611 (hard disk hd0,1)
rootnoverify (hd0,1)
kernel /fd64Sea/vmlinuz
initrd /fd64Sea/initrd
# Linux bootable partition config ends

# grub --version
grub (GNU GRUB 0.97)

When booting and selecting either FatDog64 option I get the error:
Error 16: Inconsistent filesystem structure

I tried the root option and later changed it to rootnoverify with no change.

My puppy 5.4.3 boot works fine from grub. I'm not sure if I'm explaining this right :/

Thanks,
Rob

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#318 Post by rcrsn51 »

16 : Inconsistent filesystem structure
This error is returned by the filesystem code to denote an internal error caused by the sanity checks of the filesystem structure on disk not matching what it expects. This is usually caused by a corrupt filesystem or bugs in the code handling it in GRUB.
When the GRUB menu comes up, press the 'c' key.

Type each of the three commands from your Fatdog menu.

Which one throws the error message?

rdog
Posts: 25
Joined: Mon 18 Oct 2010, 20:47
Location: Quesnel, BC, Canada

#319 Post by rdog »

rcrsn51 wrote:
16 : Inconsistent filesystem structure
This error is returned by the filesystem code to denote an internal error caused by the sanity checks of the filesystem structure on disk not matching what it expects. This is usually caused by a corrupt filesystem or bugs in the code handling it in GRUB.
When the GRUB menu comes up, press the 'c' key.

Type each of the three commands from your Fatdog menu.

Which one throws the error message?
The step

initrd /fd64/initrd

is where the error message is returned.

rdog
Posts: 25
Joined: Mon 18 Oct 2010, 20:47
Location: Quesnel, BC, Canada

#320 Post by rdog »

rdog wrote:
rcrsn51 wrote:
16 : Inconsistent filesystem structure
This error is returned by the filesystem code to denote an internal error caused by the sanity checks of the filesystem structure on disk not matching what it expects. This is usually caused by a corrupt filesystem or bugs in the code handling it in GRUB.
When the GRUB menu comes up, press the 'c' key.

Type each of the three commands from your Fatdog menu.

Which one throws the error message?
The step

initrd /fd64/initrd

is where the error message is returned.
Sorry for the delay responding... I was off researching the issue and didn't expect such a speedy reply. I was wondering if there was a way to mount the initrd as a loop device and do a file system check on it LOL.

Thanks,
Rob

Post Reply