Fatdog64-600 alpha2
I have just replaced all blkid with disktype, so let's see how this works. In my machine disktype is faster than blkid; blkid is faster than busybox blkid.Jim1911 wrote:This code executed in about 2 min and includes much more information.
I just did this on savefile=none (that's the equivalent of pfix=ram), I don't get any error. Could be some of your libraries are overwritten by earlier pet install; and/or the /usr/lib get hosed again as per irishrm case.On another matter, xfe, installed with the Package Manager, give an error:
- # xfe
xfe: error while loading shared libraries: libGL.so.1: wrong ELF class: ELFCLASS32
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
That explains, I may overlooked that part. I assume you just click the .DEB? (you don't, by any change, do undeb manually and copy the files over?)LateAdopter wrote:I didn't use a .pet, I installed using opera_11.64.1403_amd64.deb downloaded via the Opera website.
The reason is that things like web browsers and display drivers are updated every few weeks and it is not reasonable to expect Puppy developers to provide new .pets so often.
I don't mind a bit of manual fixing, if necessary. In this case I would just move the Opera folder to /usr/lib64 and reinstate the symbolic link.
I did that in the past for previous Fatdogs, haven't done this myself on 600. Once I've done it I can document the steps and share it with you (or even better, make a script out of it).If anyone can give me step by step instructions on how to install the ATI driver in fd6 using the .run file from AMD, I would be pleased to have a go.
I would prefer that or, even better, a script rather than a .pet so that I can install whichever version is currently the least buggy.
You are referring to Opera right? I don't use Opera so I can't comment. You can still probably use 32-bit libs from 521. I plan to build a new 32-bit library from latest Puppy (Racy, Slacko, Wary? not sure yet) - but that will take a while.I know the 12.1 package required 32 bit libraries in order to install on a 64bit system. I don't know whether that is still true for 12.4
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Re: BibleTime version 2.9.1
Bibletime 2.9.1 is now the in the repo. I'm using old clucene and sword from 521 - repackaged for 600.Jim1911 wrote:Kirk prepared version 2.8.1 for Fatdog64-521 and it's in your repository along with the dependencies. I think the dependencies may be OK, just Bibletime needs update. Other than Kirk's version, the later versions available are 32 bit, 01micko prepared 2.9.1 for Slacko, pemasu and jerimah also have version 2.9.1 for their distributions. I have copies of all of these.
cheers!
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Fatdog64-600 alpha2
I want to use the fatdog64 installer to prepare and install fatdog to
an 8gb flash drive.
I did all the steps but chose to install the bootloader to the
partition of the flash drive and that wouldn't boot, I wasn't sure
installing it to the MBR meant the MBR of the internal hard drive or
the flash drive so I chickened out on that option.
Will the installer put the bootloader on the MBR of the flash drive
and not disturb the internal hard drive?
an 8gb flash drive.
I did all the steps but chose to install the bootloader to the
partition of the flash drive and that wouldn't boot, I wasn't sure
installing it to the MBR meant the MBR of the internal hard drive or
the flash drive so I chickened out on that option.
Will the installer put the bootloader on the MBR of the flash drive
and not disturb the internal hard drive?
Re: Fatdog64-600 alpha2
It would put the MBR to the flash drive. It should not disturb the harddisk at all. That being said, this is new code - I'd say backup your harddisk mbr first ...Billtoo wrote:I want to use the fatdog64 installer to prepare and install fatdog to
an 8gb flash drive.
I did all the steps but chose to install the bootloader to the
partition of the flash drive and that wouldn't boot, I wasn't sure
installing it to the MBR meant the MBR of the internal hard drive or
the flash drive so I chickened out on that option.
Will the installer put the bootloader on the MBR of the flash drive
and not disturb the internal hard drive?
The MBR that got installed is the MBR that comes with syslinux, it's pretty generic (should also boot a regular harddisk, unless you previously have wee.mbr or grub4dos bootlace.com installed there instead ...)
I need to say though my experience with booting from flash is very shaky; my laptops all boot with no problem. Standard partitioned mode (where the flashdrive has partition table) has more success than "superfloppy" mode. I can't however get my desktop to boot from my flash drive, whatever method I have tried ...
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
-
- Posts: 361
- Joined: Fri 27 May 2011, 17:21
- Location: Reading UK
Hello jamesbond
That's right, I just download the .deb to a folder on my hard disk. Click on it and click to confirm that I want to install.I assume you just click the .DEB? (you don't, by any change, do undeb manually and copy the files over?)
I know the 12.1 package required 32 bit libraries in order to install on a 64bit system. I don't know whether that is still true for 12.4
I was referring to installing from the Catalyst 12.1 .run file. There were various discussions in the forums about this, at the time. But I don't know whether it was a temporary bug or a permanent feature of the installer.You are referring to Opera right? I don't use Opera so I can't comment. You can still probably use 32-bit libs from 521. I plan to build a new 32-bit library from latest Puppy (Racy, Slacko, Wary? not sure yet) - but that will take a while.
Manually installed NVIDIA-Linux-x86_64-295.53.run. Be sure and remove or disable the "nouveau" driver, load FDdevx which has all other necessary files. and reboot before going to a prompt and executingsebus wrote:Did you use Nvidia driver or some .pet?Jim1911 wrote:Although, xorgwizard does not work, I was able to remove the "nouveau" driver and install the latest NIVIDIA driver.
sebus
Code: Select all
sh NVIDIA-Linux-x86_64-295.53.run
Re: BibleTime version 2.9.1
WOW! That was quick!jamesbond wrote:Bibletime 2.9.1 is now the in the repo. I'm using old clucene and sword from 521 - repackaged for 600.Jim1911 wrote:Kirk prepared version 2.8.1 for Fatdog64-521 and it's in your repository along with the dependencies. I think the dependencies may be OK, just Bibletime needs update. Other than Kirk's version, the later versions available are 32 bit, 01micko prepared 2.9.1 for Slacko, pemasu and jerimah also have version 2.9.1 for their distributions. I have copies of all of these.
cheers!
Thank you,
Jim
jamesbond wrote:I have just replaced all blkid with disktype, so let's see how this works. In my machine disktype is faster than blkid; blkid is faster than busybox blkid. Great, that will be about 4 times faster, although, "busybox bikid" would be blazing fast on my hardware, amazing that there is that much difference in hardware.Jim1911 wrote:This code executed in about 2 min and includes much more information.
I just did this on savefile=none (that's the equivalent of pfix=ram), I don't get any error. Could be some of your libraries are overwritten by earlier pet install; and/or the /usr/lib get hosed again as per irishrm case. It must have been caused by Bibletime 2.8.1 because other than radky's pup snap, hp driver's, and NVIDIA driver it's a pristine installation.On another matter, xfe, installed with the Package Manager, give an error:
- # xfe
xfe: error while loading shared libraries: libGL.so.1: wrong ELF class: ELFCLASS32
Re: Fatdog64-600 alpha2
The fatdog64 installer to flash drive didn't go well,the installerjamesbond wrote: I need to say though my experience with booting from flash is very shaky; my laptops all boot with no problem. Standard partitioned mode (where the flashdrive has partition table) has more success than "superfloppy" mode. I can't however get my desktop to boot from my flash drive, whatever method I have tried ...
said it was going to write to the master boot record on the flash
drive but my Ubuntu install on the hard drive wouldn't boot anymore so it's
history.
I now have a fatdog install on the hard drive with lots of room for other
stuff
Sat 19 May 2012 Operating System: Fatdog64-600 Linux 3.3.4
oem: ATI ATOMBIOS product: RS880M 01.00
X Server: Xorg Driver: radeon
X.Org version: 1.11.4
dimensions: 1920x1080 pixels (211x158 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RS880
OpenGL version string: 2.1 Mesa 8.0.2
AMD Athlon(tm) II Neo K125 Processor
Core 0: 1700 MHz
Network controller Broadcom Corporation BCM43225 802.11b/g/n (rev 01)
This is running on an Acer Aspire netbook hooked up to 23.6" monitor
via hdmi cable.
The screen resolution is correct on the big monitor but wrong on the
netbook screen.
Sound is still coming from the speakers on the netbook instead of the
builtin speakers in the monitor.
If I'm playing a video in vlc and go full screen it only goes to about
1/4 the size that it should on the big monitor but if I play a movie dvd and
go full screen it displays on the entire screen of the big monitor.
That's enough for now.
- Attachments
-
- screenshot.jpg
- (21.6 KiB) Downloaded 901 times
Bibletime 2.9.1
Fresh installation with a new fd64save.4fs on an ext4 partition. Bibletime 2.9.1 works great with a minor problem. Bibletime.desktop in /usr/local/share/applications needs to be copied to /usr/share/applications in order for it to show up in menu.
I confirmed that Bibletime installation breaks xfe since I installed programs in this order using new save file.
1. Nvidia 295.53 driver
2. xfe
3. Bibletime 2.9.1
After installing Bibletime, xfe gives this error:
Thanks,
Jim
I confirmed that Bibletime installation breaks xfe since I installed programs in this order using new save file.
1. Nvidia 295.53 driver
2. xfe
3. Bibletime 2.9.1
After installing Bibletime, xfe gives this error:
- # xfe
xfe: error while loading shared libraries: libGL.so.1: wrong ELF class: ELFCLASS32
#
Thanks,
Jim
Problems with save file
Using a fresh installation, I created a new save file named fd64save-1.4fs. Upon reboot it booted fine, however, on the next reboot, it wanted to create a new save file. Next I copied the fd64save-1.4fs to fd64save.4fs and rebooted. I was not given the opportunity to choose which save file to boot. Apparently, the only name recognized was fd64save.4fs placed in /mnt/home. It won't recognize /fatdog/fd64save.4fs.
I prefer to be able to personalize the save file with a unique name and place it in a subdirectory and be able to choose the save file to be booted.
Cheers,
Jim
I prefer to be able to personalize the save file with a unique name and place it in a subdirectory and be able to choose the save file to be booted.
Cheers,
Jim
Wine
Wine works!
Loaded fd64-32bit-libs.sfs and fd64-32bit-libs-3sfs and then installed Wine 1.5.4
Next I installed the Windows e-Sword program which is running great, so some 32 bit Windows programs will run in Fatdog64-600.
Cheers,
Jim
Loaded fd64-32bit-libs.sfs and fd64-32bit-libs-3sfs and then installed Wine 1.5.4
Next I installed the Windows e-Sword program which is running great, so some 32 bit Windows programs will run in Fatdog64-600.
Cheers,
Jim
- Attachments
-
- image-1.jpg
- e-Sword running under Wine in Fatdog64-600
- (42.26 KiB) Downloaded 709 times
What are the Grub4Dos Menu.lst arguments for Fatdog64-600
Hi Jim1911, or whoever can help,
Jim, you mentioned that you got Grub4Dos to recognize Fatdog64-600. I assume you hand-edited its Menu.lst as running Grub4Dos misses Fatdog. I guess it only looks for intrid.gz files.
I checked the FAQ, tried the suggestion (seems to be Grub, not Grub4dos) and some variants, but so far the proper arguments escape me.
My Fatdog files are in a folder named "fatdog" --without the quotes. It is on the second partition of a sata drive, which all other puppies have recognized as sda2. Grub4dos and its Menu.lst are located on a second sata drive, which puppies have recognized as sdb.
Thanks in advance.
mikesLr
Jim, you mentioned that you got Grub4Dos to recognize Fatdog64-600. I assume you hand-edited its Menu.lst as running Grub4Dos misses Fatdog. I guess it only looks for intrid.gz files.
I checked the FAQ, tried the suggestion (seems to be Grub, not Grub4dos) and some variants, but so far the proper arguments escape me.
My Fatdog files are in a folder named "fatdog" --without the quotes. It is on the second partition of a sata drive, which all other puppies have recognized as sda2. Grub4dos and its Menu.lst are located on a second sata drive, which puppies have recognized as sdb.
Thanks in advance.
mikesLr
Re: What are the Grub4Dos Menu.lst arguments for Fatdog64-600
My menu.lst entry:mikeslr wrote:Hi Jim1911, or whoever can help,
Jim, you mentioned that you got Grub4Dos to recognize Fatdog64-600. I assume you hand-edited its Menu.lst as running Grub4Dos misses Fatdog. I guess it only looks for intrid.gz files.
I checked the FAQ, tried the suggestion (seems to be Grub, not Grub4dos) and some variants, but so far the proper arguments escape me.
My Fatdog files are in a folder named "fatdog" --without the quotes. It is on the second partition of a sata drive, which all other puppies have recognized as sda2. Grub4dos and its Menu.lst are located on a second sata drive, which puppies have recognized as sdb.
Thanks in advance.
mikesLr
Code: Select all
title Fatdog64-600A2(sdb2/fatdog)
find --set-root --ignore-floppies --ignore-cd /fatdog/initrd
kernel /fatdog/vmlinuz pmedia=atahd pdev1=sdb2 psubdir=fatdog
initrd /fatdog/initrd
Accept the default names and location for your save file and expect it to take about 10 min to create it. It can't seem to find it otherwise.
Hope this helps,
Jim
Online with Fatdog64-600 : Thanks Jim1911
Hi and thanks again Jim1911,
I don't know which makes me seem dumber: (a) that I couldn't figure it out, or (b) that my first guess was correct but I forgot to delete the ".gz" from the fourth line of fatdog's listing in Menu.lst, and then tried other stuff. (':oops:')(':lol:').
Well, to quote a line from a pretty good movie, The Best Exotic Marigold Hotel, "Everything's all right in the end. And if it isn't alright, it's not the end."
mikesLr
P.S. After writing this post using Seamonkey, I thought I'd see if Opera64-11.10, which I have on and run from a folder from sda2 --which will be /mnt/home-- would work. It does. Using "program folders" might solve the conflicts mentioned in this thread. I'll download the latest 64-bit from Opera and see how that goes.
I don't know which makes me seem dumber: (a) that I couldn't figure it out, or (b) that my first guess was correct but I forgot to delete the ".gz" from the fourth line of fatdog's listing in Menu.lst, and then tried other stuff. (':oops:')(':lol:').
Well, to quote a line from a pretty good movie, The Best Exotic Marigold Hotel, "Everything's all right in the end. And if it isn't alright, it's not the end."
mikesLr
P.S. After writing this post using Seamonkey, I thought I'd see if Opera64-11.10, which I have on and run from a folder from sda2 --which will be /mnt/home-- would work. It does. Using "program folders" might solve the conflicts mentioned in this thread. I'll download the latest 64-bit from Opera and see how that goes.
Last edited by mikeslr on Sat 19 May 2012, 23:52, edited 1 time in total.
LibreOffice error
LibreOffice gives this error when trying to load. Ideas?
Jim
- # libreoffice3.5
/opt/libreoffice3.5/program/../ure-link/bin/javaldx: /usr/lib64/libxml2.so.2: no version information available (required by /opt/libreoffice3.5/ure/bin/../lib/libjvmfwk.so.3)
#
Jim
After we go to the latest 3.3.x kernel we will make pet packages for ATI and Nvidia. The Nvidia installer usually works, but the ATI installer is too stupid and takes some tweaking.I was referring to installing from the Catalyst 12.1 .run file. There were various discussions in the forums about this, at the time. But I don't know whether it was a temporary bug or a permanent feature of the installer.
You may need to use the Multiple sound card wizard to fix that.Sound is still coming from the speakers on the netbook instead of the
builtin speakers in the monitor.
Haven't tried anything like that, you might want to give Zarfy a try, It's Display Properties under the setup menu.The screen resolution is correct on the big monitor but wrong on the
netbook screen.
That means you've installed a 32bit libGL. Maybe you got the wrong Nvidia package?# xfe
xfe: error while loading shared libraries: libGL.so.1: wrong ELF class: ELFCLASS32
#
I prefer to be able to personalize the save file with a unique name and place it in a subdirectory and be able to choose the save file to be booted.
You do that in grub now. See http://distro.ibiblio.org/pub/linux/dis ... tions.html About 3/4 of the way down that page you'll see some examples that cover this.
That's all changed now see http://distro.ibiblio.org/pub/linux/dis ... tions.htmlkernel /fatdog/vmlinuz pmedia=atahd pdev1=sdb2 psubdir=fatdog