Fatdog64-600 alpha2

[Billtoo]

I booted the live dvd and had it create a save file and saved it to a
flash drive.
Next bootup from the dvd I tried to get the savefile on the flash
drive to load (tried several times with several different "fatdog
savefile=direct:usb" etc. but nothing worked, settings all lost.
Finally I copied the save file from the flash drive to the hard drive and
booted up the live dvd and used "fatdog savefile=direct:local"
I was given a choice of save file to load and it worked with my initial
settings correct.

I was able to install the devx and then install the proprietary Nvidia
driver, after removing the nouveau driver.

hardinfo couldn't create a report (permissions problem) so I compiled
the source and installed that.

Computer
Processor 8x Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
Memory 16394MB (369MB used)
Operating System Unknown distribution
User Name root (root)
Date/Time Mon 21 May 2012 08:16:54 PM EDT
Display
Resolution 1920x1080 pixels
OpenGL Renderer GeForce GTX 560 Ti/PCIe/SSE2
X11 Vendor The X.Org Foundation
Multimedia
Audio Adapter HDA-Intel - HDA Intel PCH
Audio Adapter HDA-Intel - HDA NVidia
Version
Kernel Linux 3.3.4 (x86_64)
Compiled #1 SMP Fri May 4 23:40:44 GMT 2012
C Library GNU C Library version 2.13 (stable)
Default C Compiler GNU C Compiler version 4.6.2 (GCC)
Distribution Unknown distribution

OpenGL
Vendor NVIDIA Corporation
Renderer GeForce GTX 560 Ti/PCIe/SSE2
Version 4.2.0 NVIDIA 295.53
Direct Rendering Yes

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

It took a while to get there but this is working well now.

[Jim1911]

I’ve discovered another incompatible program.

Installed wine-1.5.4-i486_v1.pet after first loading fd64-32bit-libs-3.sfs. Wine appears to be working well, and I’ve run some Windows programs under it.

However, the Wine installation somehow broke the Package Manager. When trying to execute it comes up with a message “Refreshing list of installed packages...

[jamesbond]

You mean Firefox binaries downloaded from mozilla site? Correct

All previous Fatdog uses Firefox compiled by kirk, not the official binaries. This is because standard official binaries require dependencies that are not included in Fatdog (mainly Dbus stuff).

Dbus is now included in Fatdog, but the official binaries now also require dbus-glib. Dbus glib is in the repo (refresh the package manager first). You also need to remove /usr/lib64/firefox (replace it with actual extract of firefox binary tarball). Firefox will launch. I didn't test further than that.

Knew that it had to be something simple, works great now, and it's at version 13.

Thanks,
Jim

Next release will fix this for you (libdbus_glib will be in the main sfs) so you don't need to go through this hoops again. Just download official firefox binaries and you're good to go.

[jamesbond]

I booted the live dvd and had it create a save file and saved it to a
flash drive.
Next bootup from the dvd I tried to get the savefile on the flash
drive to load (tried several times with several different "fatdog
savefile=direct:usb" etc. but nothing worked, settings all lost.

600 doesn't wait USB storage (flash drive etc) to be ready, because there is simply no reliable way of doing it (other than waiting and waiting and waiting ...). Thus you need to specify "waitdev=n" where "n" in the number of seconds to delay for the USB devices to settle and be ready. In my laptop, 3 seconds are enough. Yours may vary.

[jamesbond]

hardinfo couldn't create a report (permissions problem) so I compiled
the source and installed that.

Permission problem? When generating the report? I just run hardinfo (as multisession) and it seems to be working fine (it saves the report to /root)... Can you reproduce the issue?

[jamesbond]

jamesbond wrote

Do you mind sharing this for the rest of us?

Gladly

Thank you, will bookmark this post

[Billtoo]

hardinfo couldn't create a report (permissions problem) so I compiled
the source and installed that.

Permission problem? When generating the report? I just run hardinfo (as multisession) and it seems to be working fine (it saves the report to /root)... Can you reproduce the issue?

It was my mistake, sorry.I got the error because I had loaded the
wrong devx the first boot after copying the savefile from the flash
drive to the hard drive and using fatdog savefile=direct:local
With the proper devx loaded there is no error, I guess there would be
no error if no devx was loaded too.

I still can't get the savefile on the flash drive to load, I've tried
putting waitdev=15 before and after the savefile=direct:usb so I'm
doing something wrong.

[jamesbond]

It was my mistake, sorry.I got the error because I had loaded the
wrong devx the first boot after copying the savefile from the flash
drive to the hard drive and using fatdog savefile=direct:local
With the proper devx loaded there is no error, I guess there would be
no error if no devx was loaded too.

Yes, due to the new layering model, if you load the wrong devx, its library can hide Fatdog64 libraries and you'll get this problem. The SFS tool will allow you to load any SFS - so you need to exercise caution

I still can't get the savefile on the flash drive to load, I've tried
putting waitdev=15 before and after the savefile=direct:usb so I'm
doing something wrong.

Try this: savefile=direct:device:sdb1:/fd64save.ext4. Replace sdb1 with your flash drive; fd64save.ext4 with the name of your savefile. Put the waitdev parameter, try waitdev=5 (I think 15s is an extremely long delay). If this still doesn't work, use the "earlyshell" parameter. This will drop you to a shell in initramfs, you can check to see whether your flash drive is detected by running "blkid". When done, type "exit" to continue booting.

[Billtoo]

Try this: savefile=direct:device:sdb1:/fd64save.ext4. Replace sdb1 with your flash drive; fd64save.ext4 with the name of your savefile. Put the waitdev parameter, try waitdev=5 (I think 15s is an extremely long delay). If this still doesn't work, use the "earlyshell" parameter. This will drop you to a shell in initramfs, you can check to see whether your flash drive is detected by running "blkid". When done, type "exit" to continue booting.

This worked:

fatdog waitdev=5 savefile=direct:device:sdb1:/fd64save.ext4

Well it ought to be easy from now on since I have this written down in
my notebook

Thanks

[jamesbond]

This worked:

fatdog waitdev=5 savefile=direct:device:sdb1:/fd64save.ext4

Well it ought to be easy from now on since I have this written down in
my notebook

Thanks

You can try to reduce the waitdev (perhaps 3 seconds is enough?) You can also drop the filename (just use direct:device:sdb1) if the filename is fd64save.ext4.

BTW - notice for all multisession users --- SFS does not work at the moment and if you use it will disable you from saving future sessions.

This will be fixed in next release.

[jamesbond]

[quote="Jim1911"]I’ve discovered another incompatible program.

Installed wine-1.5.4-i486_v1.pet after first loading fd64-32bit-libs-3.sfs. Wine appears to be working well, and I’ve run some Windows programs under it.

However, the Wine installation somehow broke the Package Manager. When trying to execute it comes up with a message “Refreshing list of installed packages...

[irishrm]

kirk:
jamesbond:

I did a very careful re-install directly to USB.

During the install i was given the default option of moving the download file outside of the savefile.
I un-ticked that box and my downloads are appearing in spot as they should do.

I have downloaded some small and large downloads even a youtube video without any hiccup.

so far so good "upward and onwards"
irishrm.

[Jim1911]

You can try extract the wine.pet and change /usr/lib to /usr/lib64, then rebuild the pet then install. That *may* fix the problem for the time being.

I never compiled Wine myself, I always use green_dome's compilation - and the above is exactly how I did it (only that I turn it into SFS instead of another pet, and I also added wine-gecko).

Now on to 32-bit libs - which Puppy you all want to base the the 32-bit libs on? Racy? Wary? Slacko? For your info, the old 32-bit libs was based on Wary 5.0 (the reason being, it was compiled from T2 at about the same time Fatdog 500 - thus it has libraries of similar age). I'm open to suggestions. Or we can always be lazy and keep the existing 32-bit libs cheers!

I've found green_dome's wine pets to be very reliable and have been using mostly his development versions for years. The stable version usually is too far behind and I've found the development versions to be stable. It will be a good learning experience for me to try what you suggested.

As for 32-bit libs, I believe that Slacko would provide good results although the Wary based libs have given no problems with the programs I've tried.

Lazy, not you!

Thanks,
Jim

[Billtoo]

I tried to compile xfe-1.32.5 but get an error message, anything in
the config.log will baffle me I'm sure so is there an easy fix?

[kirk]

Bill,

It looks like you don't have the devx installed.

[Billtoo]

Bill,

It looks like you don't have the devx installed.

I do have the devx installed, I've successfully compiled xine-lib-1.2.1,fox-1.6.45,gogglesmm-0.12.6, and a couple of others already, no luck with xfe though.
Edit:also firefox-12 and xine-ui, vlc wouldn't play the movie dvd in the screenshot but xine-ui will, I admit to liking that movie

[Jim1911]

You can try extract the wine.pet and change /usr/lib to /usr/lib64, then rebuild the pet then install. That *may* fix the problem for the time being.

I never compiled Wine myself, I always use green_dome's compilation - and the above is exactly how I did it (only that I turn it into SFS instead of another pet, and I also added wine-gecko).

Now on to 32-bit libs - which Puppy you all want to base the the 32-bit libs on? Racy? Wary? Slacko? For your info, the old 32-bit libs was based on Wary 5.0 (the reason being, it was compiled from T2 at about the same time Fatdog 500 - thus it has libraries of similar age). I'm open to suggestions. Or we can always be lazy and keep the existing 32-bit libs cheers!

I've found green_dome's wine pets to be very reliable and have been using mostly his development versions for years. The stable version usually is too far behind and I've found the development versions to be stable. It will be a good learning experience for me to try what you suggested.

As for 32-bit libs, I believe that Slacko would provide good results although the Wary based libs have given no problems with the programs I've tried.

Lazy, not you!

Thanks,
Jim

Your suggestion to rebuild the Wine pet by changing /usr/lib to /usr/lib64 did not prevent Package Manager from breaking. It did work initially after the Wine installation, but after a reboot Package Manager is broken. However, nothing other than Package Manager appears to be broken and as you can see from the attached desktop, I have NVIDIA driver, xfe, Bibletime, and three Windows programs BibleAnalyzer, e-Sword, and theWord all running fine at the same time. I guess if I want to use Windows programs for the time being, I'll have to do without the Package Manager.

Thanks,
Jim

[jamesbond]

Bill,

It looks like you don't have the devx installed.

I do have the devx installed, I've successfully compiled xine-lib-1.2.1,fox-1.6.45,gogglesmm-0.12.6, and a couple of others already, no luck with xfe though.

Bill, please post the config.log of the failed configure phase of xfe. Btw xfe is already in the repo - you don't have to compile it unless you want to customise your own build, of course. You need FOX toolkit to build xfe (also already in repo).

Edit:also firefox-12 and xine-ui, vlc wouldn't play the movie dvd in the screenshot but xine-ui will, I admit to liking that movie

Can't test that because I don't have that movie, but all the movies I throw to VLC plays so far ...

[jamesbond]

Your suggestion to rebuild the Wine pet by changing /usr/lib to /usr/lib64 did not prevent Package Manager from breaking. It did work initially after the Wine installation, but after a reboot Package Manager is broken. However, nothing other than Package Manager appears to be broken and as you can see from the attached desktop, I have NVIDIA driver, xfe, Bibletime, and three Windows programs BibleAnalyzer, e-Sword, and theWord all running fine at the same time. I guess if I want to use Windows programs for the time being, I'll have to do without the Package Manager.

Thanks,
Jim

Try as I might, I could not make the package manager fail by installing the wine pet (even before renaming /usr/lib to /usr/lib64) - but then I'm running the latest build with all the fixes, so there may be a difference there.

Anyway, I'm uploading wine-1.5.4 SFS (courtesy of green_dome compile) to the repo now (not yet finished). You know it's finished when the accompanying md5sum.txt file is there too. You still need to use the old 32-bit libs, of course.

For the 32-bit libs, I remember in addition to standard Wary, I needed to add libSDL and other stuff. I haven't explorer 32-bit puppies so far, so which ones comes with the largest set of libraries? I want to avoid adding libs manually unless I really have to. Or may be they are all similar because all are based on Woof?

cheers!

[jamesbond]

Java JDK and JRE sfs uploaded (1.6 update 31).