Fatdog64-710 beta [28 August 2016] [CLOSED]

[drunkjedi]

Check out the FAQ (the Help icon on desktop) - just type 'extrasfs' into the search field and you'll find the details.

Thanks SFR I found my answer for my both questions in Boot options faq after I posted my question.
http://distro.ibiblio.org/fatdog/web/fa ... tions.html

I initially thought being new options the faq wouldn't be updated yet.
I was wrong.
Good job Fatdog team.

Also I find the boot options to load extra sfs very interesting, I can choose which to load in RAM and which not.
Awesome.

Looks like I am migrating from 700 to 710 now.

Thanks mate.

[Gordie]

Has anyone got Google-Chrome to work on 710 Beta? It worked well on Alpha but I can't seem to get it to work on Beta.
Can use it from root desktop but when choosing another user of my making it does not load.

Am gonna wipe and reinstall again tonight and see otherwise am not sure what course of action to take

[prehistoric]

@Gordie, I'm posting this from FD710b using Google Chrome installed via the update option in the control center.

I'm a little confused about how you are trying to run this. I just did a download to check that I am running it as user spot, not root.

Are you trying to create yet another user besides spot?

[SFR]

Has anyone got Google-Chrome to work on 710 Beta? It worked well on Alpha but I can't seem to get it to work on Beta.
Can use it from root desktop but when choosing another user of my making it does not load.

Are you trying to create yet another user besides spot?

If that's the case, try to launch it from terminal using:

Code: Select all

google-chrome-stable

Greetings!

[Wognath]

James and Kirk, congratulations and thanks for FD710b. It looks really good and boots right up on my quirky VIA-nano netbook.

I have been using FD70? for so long that I'm reluctant to start over with a new save folder. I'd like to suggest a guide or script to import old save folder to new FD, when you have time.

I have ignored your warnings and reused my old save folder several times in the 700 series. This time, when the old save folder is loaded I get "xinit: connection to X server lost ". xorgwizard finds correct resolution, but X won't start-- same message.

I tried the old save folder minus /etc with the same result. I tried making a new 710 save folder, then merging in items from old folder. /root minus .* is ok, but /usr breaks it. Still tinkering...

[belham2]

James, Kirk, SFR, et al, thank you very much.

Installed on dual screen:

Processor : 2x AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
Memory : 1783MB (564MB used)
Machine Type : Physical machine
Operating System : Fatdog64 [710]
User Name :
Date/Time : Tue Aug 30 20:29:14 2016
-Display-
Resolution : 2560x1024 pixels
OpenGL Renderer : Gallium 0.4 on AMD RS780 (DRM 2.43.0, LLVM 3.7.0)
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : HDA-Intel - HDA ATI SB
Audio Adapter : HDA-Intel - HDA ATI HDMI
-Input Devices-
HDA ATI HDMI HDMI/DP,pcm : 3=
HDA ATI SB Rear Mic
HDA ATI SB Front Mic
HDA ATI SB Line
HDA ATI SB Line Out Front
HDA ATI SB Line Out Surround
HDA ATI SB Line Out CLFE
HDA ATI SB Line Out Side



Took my FD64-710a install, deleted the vmlinuz and initrd, copied over the new vmlinuz & initrd from the beta, and initially could not get any of the upgrades to appear. Then, remembering I'd read to delete the old save file, extracted what I needed out of the old, saved it, then deleted it, and finally everything was great. Thank you for all your hard work. Fatdog is still one of the only 64bit pup/pup-related distros that I can plug into any of my machines, and it will grab both wired and wireless, especially on a notorious broadcom b43 mini wireless netbook that stumps nearly all other puppies & forces me to add (or compile) + blacklist firmware to get wireless to work.




Final note, once again stuck SFR's firewall tray icon in etc/xdg/autostart...not sure why this little gem of a visual sight firewall script isn't included in the FD64 beta version (mentioned it in the alpha version some months ago).

Otherwise, nice job overall. Thanks. Only thing I can find is that a few times I saw some funny popup boxes with unreadable characters (for example, put ctrl+c something into glipper-lite, then open abiword, and ctrl+v it, and then try to save that abiword document). The popup box has a few times now given me garbled lettering on the options within it. Figure it must be something on my end, not yours, but still, thought I'd mention it.

[Gordie]

Has anyone got Google-Chrome to work on 710 Beta? It worked well on Alpha but I can't seem to get it to work on Beta.
Can use it from root desktop but when choosing another user of my making it does not load.

Are you trying to create yet another user besides spot?

If that's the case, try to launch it from terminal using:

Code: Select all

google-chrome-stable

Greetings!

Yes, another user of my making. It works for root but not for users I made. This is a change from 710 alpha that I noticed

[Gordie]

google-chrome-stable

Yup, that fixed it. Thanks so much

[kirk]

Gordie,

You'll want to edit /usr/share/applications/google-chrome.desktop and change:

Exec=google-chrome-spot %U

to

Exec=google-chrome-stable %U

Of course you'll have to do that as the root user.

[mcewanw]

Hi,

I've never tried any FatDog but thought I'd give this one a spin. I want to test some of my programs on it.

I am trying to make a frugal install to my /dev/sda5 ext2 partion into subdir /puppy-fatdog. Unfortunately, I'm missing something. Originally I just copied the vmlinuz and large initrd into there, since that's all I could see as likely relevant in the FatDog 710 iso (I've double-checked and there is no base sfs in there). However, on booting, the system couldn't find the 'base' sfs.

I thus went back to the download site and downloaded a further sfs (32bit-fd64_710b.sfs) from there (previously I presumed this additional sfs was likely for adding 32bit functionality only, since file name start with 32bit). Anyway, though that sfs is recognised I still can't get boot beyond bulldog login prompt. I imagine 32bit-fd64_710b.sfs is indeed NOT the required base sfs, so the question is, where is the correct one?

I couldn't find any installation ReadMe, but I presume the answer to my question is somewhere in this thread (or maybe the alpha thread?). Had I used FatDog before, I guess it is easy, but since I haven't, could someone kindly advise me what I am doing wrong. I have rightly or wrongly presumed that I don't also need the devx file simply to boot the system - or do I need to download that too?

My current menu.lst as is follows. I basically just copied this from a post I stumbled across so I'd be grateful if you could let me know if any of the parameters below are also wrong or irrelevant:

Code: Select all

title FatDog64 710b (sda5/puppy-fatdog)
root (hd0,4)
  kernel /puppy-fatdog/vmlinuz   basesfs=device:sda5:/puppy-fatdog/32bit-fd64_710b.sfs savefile=direct:device:sda5:/puppy-fatdog/fd64save-abc.ext2 psubdir=puppy-fatdog pmedia=atahd
  initrd /puppy-fatdog/initrd

Thanks, William

[SFR]

Final note, once again stuck SFR's firewall tray icon in etc/xdg/autostart...not sure why this little gem of a visual sight firewall script isn't included in the FD64 beta version (mentioned it in the alpha version some months ago).

It's there, in /etc/xdg/Startup, but it's disabled by default.
Enable it either using 'chmod +x' or 'Control panel -> Desktop -> Manage desktop startup programs'.
___________

I just copied the vmlinuz and large initrd into there

Code: Select all

kernel /puppy-fatdog/vmlinuz   basesfs=device:sda5:/puppy-fatdog/32bit-fd64_710b.sfs savefile=direct:device:sda5:/puppy-fatdog/fd64save-abc.ext2 psubdir=puppy-fatdog pmedia=atahd

Since you're using the default, "humongous initrd" (check it out in FAQ), the base SFS is inside of it, so you don't need the 'basesfs=...' bit.
Actually you don't need also pmedia nor psubdir - they're not suppoted in Fatdog.
Try this:

Code: Select all

kernel /puppy-fatdog/vmlinuz savefile=direct:device:sda5:/puppy-fatdog/fd64save-abc.ext2
initrd /puppy-fatdog/initrd

Btw, yes, 32bit-fd64_710b.sfs is indeed 32bit compatibility SFS.

Greetings!

[smokey01]

@mcewanw
This works for me. My drive is sdc1 and my grub files are on the same drive hence (hd0,0).

title FatDog 710b
rootnoverify (hd0,0)
kernel /fd710b/vmlinuz savefile=direct:device:sdc1:fd710b/fd64save dofsck waitdev=1
initrd /fd710b/initrd

[mcewanw]

Thanks SFR and smokey01. Successfully booted into Fatdog64-710b and posting from it right now. It certainly looks and feels like a tradition Puppy - I hadn't expected that degree of lookalike compatibility.

William

[mcewanw]

I tried my weX AV+screencast program in FatDog64 by first converting the pet to FatDog package via rightclick menu. I didn't bother installing scrox (64bit version) for these initial tests since need libgiblib.so.1 for that. Instead just used weX with Fixed Region (setting appropriate coordinates in weX config GUI.

Worked fine with the FatDog included ffmpeg version, except for one thing... FatDog, unlike other systems I've tested seems to have threads enabled correctly in its kernel. Result is that ffmpeg starts a child process as well as parent on my machine, so trying to stop the recording process with simple kill -TERM fails to work. I thus need to change kill to pkill -TERM -P to kill the child process instead (in weX function stoprec) - that seems to work fine, but I need to test it more since probably need to do the same in pause functions (pauserec and unpauserec) - i.e. all kill commands in these functions changed to pkill -<signal_type> -P.

There hasn't been any feedback on weX since I released it nor many downloads so it may not be worth my bother uploading a new version. Spring is finally here in this part of the world and I'm busy in the garden (!) but I'll see how much time I can find for further testing and consider a second release. I think most are just using Simple Screen Recorder now though, so not sure if worth more work really.

FatDog working well for me so far by the way.

William

[mcewanw]

I have now uploaded a second version of weX, which seems to stop the recording correctly in FatDog64-710beta per my post above (note that for woof-ce Puppy Linux or Debian/UbuntuDogs the original weX version is still needed):

http://www.murga-linux.com/puppy/viewtopic.php?t=107905

I haven't tested it much at all so hopefully I didn't make any coding error prior to packaging it.

Remember, for Area/Window region mode to work you need scrox 64bit version installed, and that will need giblib1 as a dependency.

If anyone tests weX and wants to give me any feedback, please do so on the above weX thread.

William

EDIT: Just noticed the mhwaveedit setup you have in FatDog doesn't seem to recognise mp3 tracks even after I installed lame encoder. In XenialDog, if you click mhwaveedit icon in weX the audio track instantly appears for editing (when recorded as x264 video with mp3 audio track in mkv container).

[Sage]

Getting repetitive bad d/l or bad burns. Is there something inherent? any other d/l sites?
Many ".EDD: ERROR 1000 reading sector 149947/15069/150789/151765/13679/14567/73390.....etc."
But it keeps running, running...... , just never gets to boot up!
Update:
A fourth d/l and lost count of re-burns resulted in a working copy. Looks good! Any chance of putting .iso on a mirror? smokey?!

[ryukisai]

Hi guys! I'm new here. Alban from France. I've been using Puppy Linux and then Fatdog for about 4 years. I'm a fan of the load in ram approach, and the preincluded features, which let you work on any computer in just seconds. So a huge thanks to the devs!

I have a technical question. My wish is to :

• -Make a USB flash drive that can boot both on UEFI and legacy BIOS systems,
  -But still use the rest of my flash drive's capacity as a regular USB disk, working both on Linux and Windows (lets say FAT32) and without the need for admin rights.

I installed Fatdog on a 64GB drive following the dd isohybrid method described here:
ftp://distro.ibiblio.org/fatdog/web/faq ... drive.html
It allowed me to reach my first goal. The drive boots on UEFI and BIOS without troubles.

Then I also used the fix-usb.sh included in Fatdog. It effectively created a third partition called sdb3, that i could format to FAT32.
However, when plugging the drive in windows, the only partition seen is the sdb2 10 MB FAT16 partition containing GRUB and EFI drivers.

I tried to change drive letters in windows disk manager. Even if i assign a drive letter to the 50+ GB FAT32 partition, it will only link to the 10 MB FAT16.

I think it has to do with the overlapping first 2 partitions messing with msdos partition table (sdb1 ranges from 0 to 610303, and sdb2 from 116 to 20595).

I tried to manually regenerate a partition table with fdisk before dding the iso, with no luck.
Does anyone know about a workaround about this? I will investigate any idea! Thanks in advance guys!

[Sage]

Why not use one USB fob per OS - the smaller ones are cheap or even cheaper (I was given one recently just for looking at a car in a show!). It's possible to slip at least four on your house key ring. It's always a bad idea to mix M$doze with anything - in another four years you'll probably forget it ever existed?

[smokey01]

@sage here are a couple more links.
http://ftp.nluug.nl/ftp/pub/os/Linux/di ... o/710beta/
http://mirror.aarnet.edu.au/pub/fatdog/iso/710beta/

[anikin]

...
...
There have been about 230 commits since the alpha release. So there's been a bit going on...
...
Updates/additions:
...
rox-filer-jun7-08192016 (https://github.com/jun7/rox-filer)
...

Can you guys, please enlighten me on the nuances of this particular variant vs the original rox-filer sources? And will it be too much to ask you to share the build (./config) script? I'm eager to compile rox-filer myself and I want the best variant. Thank you in advance.