Fatdog64 702 Final [7 Feb 2016] [CLOSED]

[april]

One of the most frustrating puppy distros I have come across.

I still cannot connect to the net via the dialler and my optus mobile modem
Just will not work


I want to open the savefile
Its name is "fd64save.ext4"
I click on it expecting it to open and it does not
I want to copy some sane files out of it.


I want to post an observation on release 701 ....
I can't . Its bloody closed???
This presumption of authority by the developers is staggering. Leave the bloody thing open for comments . Don't assume everyone will update or even wants to.

[puttingau]

HI, just started with fatdog 64 on a macbook pro, which I'm not very familiar with either.
I was expecting to see the files in the mac, as I can in a pc when puppy is booted, however, I have sda1, which is a small drive containing just efi stuff, another sda3, which seems to contain apple recovery stuff, and sda2, which seems to be the main drive, containing nothing at all.
I know there is local data on the mac, is it possible to see and access it, with fatdog?
thanks

[step]

Can you please open a terminal, run the following commands, and copy and paste all output in your reply? Thank you.
uname -a
lsblk -paf

[puttingau]

sorry for the delay, step, have been otherwise occupied...
# lsblk -paf
NAME FSTYPE LABEL UUID MOUNTPOINT
/dev/sda
|-/dev/sda1 vfat EFI 70D6-1701
|-/dev/sda2 hfsplus Macintosh HD
49627bb3-bd3a-36e1-aa50-d3f1c7977e56
`-/dev/sda3 hfsplus Recovery HD 5bf12c55-0ef4-36ed-a14c-a76e528aefce
/dev/sdb
`-/dev/sdb1 vfat BEEB-335D /aufs/devs
/dev/nbd0
/dev/nbd1
/dev/nbd2
/dev/nbd3
/dev/nbd4
/dev/nbd5
/dev/nbd6
/dev/nbd7
/dev/nbd8
/dev/nbd9
/dev/loop0 squashfs /aufs/kern
/dev/loop1 squashfs /aufs/pup_
/dev/loop2 ext4 c1f840cf-7077-4a3e-9cb9-c0adf600f713 /aufs/pup_
/dev/loop3
/dev/loop4
/dev/loop5
/dev/loop6
/dev/loop7
/dev/loop8
/dev/loop9
/dev/nbd10
/dev/nbd11
/dev/nbd12
/dev/nbd13
/dev/nbd14
/dev/nbd15
/dev/loop10
/dev/loop11
/dev/loop12
/dev/loop13
/dev/loop14
/dev/loop15

# uname -a
Linux fatdog64-255 3.18.7 #1 SMP Mon Nov 16 01:58:11 WIB 2015 x86_64 GNU/Linux

Thanks for your help

[step]

@puttingau,

it appears your issue concerns the hfs+ file system. Earlier in this thread user mavrothal reported an empty folder issue with a similar setup. User jamesbond, one of the Fatdog64 developers, traced that issue back to a kernel problem. If your issue is the same, your best bet is to change the kernel and retry.

However, before you attempt to do so, ensure that you're experiencing the same kind of issue as mavrothal's, and consider your other options (more below).

The thread involves the following posts. Read and try to adapt mavrothal's command line results to your case. Are you getting similar output? If so, you're probably in the same camp. The fourth post includes links to other forums where the kernel issue is discussed. Perhaps you can find newer solutions there, since jamesbond's posting is about eight months old by now.

http://www.murga-linux.com/puppy/viewtopic.php?p=883852#883852
http://www.murga-linux.com/puppy/viewtopic.php?p=883855#883855
http://www.murga-linux.com/puppy/viewtopic.php?p=883884#883884
http://www.murga-linux.com/puppy/viewtopic.php?p=883962#883962

Changing the kernel
It appears your current kernel version is 3.18.7, so you want to try either 4.3.3 or 4.4.3 from the kernels/700 folder. The procedure is explained here
http://distro.ibiblio.org/fatdog/web/faqs/kernel.html

Your other options
Fatdog64-710 is just around the corner. If you aren't too invested in version 702 already, I suggest you should switch. That will give you a newer kernel right away, and much more attention to your support requests, as the Fatdog64 devs are spread thin so they need to prioritize the support threads. Click on the 710 link in my forum signature to go to the Fatdog64-710 beta link. A release candidate is due out very soon.

[Insomniacno1]

Hi, I have tried to boot Fatdog64 702 from USB(with MicroUSB connector) on an ODYS Wintab 8 that has 32bit UEFI bios and is preinstalled with Windows 8.1 with Bing. The tablet has an 8" screen, 1GB Ram, 16GB SSD, 64bit Intel Atom Baytrail Z3735E Quad core cpu at 1.33Ghz, intel HD video.

I use Ted Dog's uefi.zip contents on my usb stick to make UEFI compatible, and it works.
http://murga-linux.com/puppy/viewtopic.php?t=97141

The problem is not getting to the boot menu, the problem is that after starting to boot Fatdog64 I get to black screen and then it hangs there. No indication on why this happens.

On my laptop I have a fork of Xubuntu 14.04 LTS and I have ISO master installed, I like to know if there is a possibility of editing the Fatdog64.iso so that I can get it to save a log file to my USB stick so I can figure out why it do not continue to desktop?

I tried other distro's like Tahrpup and slacko, all ubuntu versions since 14.04 and up + flavours and some debian based that should work with touchscreen - 32bit and 64bit - with same result, though 32bit tahrpup and slacko showed everything up to "loading kernel modules" and then black screen.

The boot parameter of Fatdog64 do not have quiet splash, so I cannot remove that to see what is going on. But a log file would be nice:)

JBJ

EDIT: I finally got slacko 32bit booting to the desktop - have a bit trouble with the touchscreen though. You can follow the thread here:
http://www.murga-linux.com/puppy/viewtopic.php?t=108295

[chapchap70]

Just to let someone know, I installed PHP 5.5 (forgot the exact version) on 702 from the package manager and when I tried to run it, it barked about not having a dependency. Does anyone else have the same experience?

I'll have to get more specific info later when I get home if needed.

There is a Hiawatha pet I contributed onto the FatDog contributors thread;
http://murga-linux.com/puppy/viewtopic. ... &start=133

I might try to make a Hiawatha, PHP7, MYSQL package. If you are able to try the Hiawatha package I made, let me know how it works.

[april]

Someone has closed this so maybe interest in it has waned.

I could never get it to connect to the net through my Realtek adaptors but I persevered and worked out the different way of connecting being used .

I went to the Control panel and network and network wizard and found this time my adaptor had been recognised ? I configured it and put in the password and was able to get a connection finally and use it now .

No doubt it was just this fuzzy brain behind it.

Now maybe I can go a bit further and delve into 64bit technology ,compiling and trying stuff.

[step]

I think CLOSED doesn't means that "interest has waned" but rather it reflects the reality that the devs don't have enough bandwidth to support more than one Fatdog64 at the time, so they choose to support the latest version (710 now). Active users of version 702 may still read this thread, share and help fellow users as they can. I'm glad you persevered, and got around your network connectivity issues. If you do pursue compiling, load the FD-702 devx.sfs and you're good to go. I think that learning to use the FD build scripts will be time well-spent. Start reading in /usr/src/pkgbuild <- you need to load the devx.sfs to get this directory.