(old)Puppy Linux Discussion Forum

Posted: **Tue 24 Jul 2012, 18:28**

Green_dome's latest wine-1.5.9-i486_v1.pet works fine without any modifications in using new frugal installation of Fatdog64-601.

Posted: **Tue 24 Jul 2012, 22:59**

[Edit] Go here for GTK-mpscan v1.1.

Posted: **Tue 24 Jul 2012, 23:13**

Jim1911 wrote:Green_dome's latest wine-1.5.9-i486_v1.pet works fine without any modifications in using new frugal installation of Fatdog64-601.

Jim do you have a link please.

Posted: **Wed 25 Jul 2012, 03:54**

smokey01 wrote:
Jim1911 wrote:Green_dome's latest wine-1.5.9-i486_v1.pet works fine without any modifications in using new frugal installation of Fatdog64-601.
Jim do you have a link please.

Latest Wine

Posted: **Wed 25 Jul 2012, 13:15**

Is there a Pet or SFS available for Skype 4.0.0.8?

Ta

Posted: **Wed 25 Jul 2012, 14:49**

smokey01 wrote:Is there a Pet or SFS available for Skype 4.0.0.8?

Ta

This one for LHP64 may work.

Posted: **Wed 25 Jul 2012, 20:31**

Jim1911 wrote:
smokey01 wrote:Is there a Pet or SFS available for Skype 4.0.0.8?

Ta
This one for LHP64 may work.

Thanks but no.

Posted: **Thu 26 Jul 2012, 10:27**

jamesbond I just tried to build VirtualBox with your script and it failed.

Any idea what might be wrong? This is the error from the command prompt:

# VirtualBox
VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/opt/VirtualBox/VirtualBox.so",) failed: libGL.so.1: wrong ELF class: ELFCLASS32
#

Your script:

#!/bin/ash
if ! which make || ! which gcc; then
Xdialog --infobox "Install devx first." 0 0 10000
exit
fi

Xdialog --no-buttons --infobox "Downloading, please wait ..." 0 0 1000000 &
PID=$!

cd /tmp
TMPFILE=$(mktemp)
wget -O $TMPFILE http://dlc.sun.com/virtualbox/LATEST.TXT
VERSION=$(cat $TMPFILE)
wget -O $TMPFILE http://dlc.sun.com/virtualbox/$VERSION/
FILE=$(sed -n '/amd64\.run/ {s/^.*"$V.*_amd64.run$".*$/\1/;p}' $TMPFILE)
rm $TMPFILE
wget http://dlc.sun.com/virtualbox/$VERSION/$FILE
chmod +x $FILE
kill $PID

Xdialog --no-buttons --infobox "Installing, please wait ..." 0 0 1000000 &
PID=$!
./$FILE
kill $PID

Xdialog --infobox "Done. The file is stored in /tmp/$FILE in case you want to keep it." 0 0 10000

Thanks

Edit: I have just installed VirtualBox before installing the Nvidia driver and it worked fine. It appears Nvidia installs a driver file and a couple of symlinks which causes VirtualBox some grief. Rather wierd. See screeny for files. The numbering of the libGL files has the same number as the Nvidia driver.

Posted: **Thu 26 Jul 2012, 10:33**

Another problem.

# mpg321
mpg321: error while loading shared libraries: libao.so.2: cannot open shared object file: No such file or directory

Sorry..

Posted: **Thu 26 Jul 2012, 12:04**

So since wpa_gui is afaict the only software provided at gui level for using wifi, this amounts to saying the end user has to configure wpa_supplicant.conf before using wifi is possible? Unclear why the usual Puppy gui utils for wifi are not present, eg SNS, or have I failed to locate them?

Posted: **Thu 26 Jul 2012, 12:56**

smokey01,

Re: virtualbox - do you install nvidia driver using the available pet, or do you use getnvidia? I haven't tested getnvidia yet but I suspect that it also pulls 32-bit driver and that overwrites the 64-bit libGL.so.1. The fact that you did manage to install virtualbox before installing the driver seems to confirm this.

Re: mpg321, yes, we need to recompile mpg321. For the time being, just symlink libao.so.4 to libao.so.2 in /usr/lib64

Code: Select all

ln -s /usr/lib64/libao.so.4 /usr/lib64/libao.so.2

gnomic, you have the choice of using either wpa_gui or network-wizard.

Posted: **Thu 26 Jul 2012, 21:21**

jamesbond wrote:smokey01,

Re: virtualbox - do you install nvidia driver using the available pet, or do you use getnvidia? I haven't tested getnvidia yet but I suspect that it also pulls 32-bit driver and that overwrites the 64-bit libGL.so.1. The fact that you did manage to install virtualbox before installing the driver seems to confirm this.

Re: mpg321, yes, we need to recompile mpg321. For the time being, just symlink libao.so.4 to libao.so.2 in /usr/lib64
Code: Select all
ln -s /usr/lib64/libao.so.4 /usr/lib64/libao.so.2

I generally download the 64 bit nVidia driver directly from the site.

NVIDIA-Linux-x86_64-295.59.run

jamesbond wrote:The fact that you did manage to install virtualbox before installing the driver seems to confirm this.

I agree but I'm not sure how this is happening.

Posted: **Thu 26 Jul 2012, 21:32**

In another Fatdog-600 frugal install video is working fine but VirtualBox won't work.

See attached screenies.

Mmm, a bit strange.

Posted: **Fri 27 Jul 2012, 02:12**

smokey01 wrote:I generally download the 64 bit nVidia driver directly from the site.

NVIDIA-Linux-x86_64-295.59.run

If you install the driver directly from source, it is imperative that you do not install the 32-bit compatibility library. The screenshot above (from a clean install, I suppose?) only confirms my suspicion - libGL.so.1 is now a 32-bit library instead of 64-bit.

Posted: **Fri 27 Jul 2012, 10:26**

jamesbond wrote:
smokey01 wrote:I generally download the 64 bit nVidia driver directly from the site.

NVIDIA-Linux-x86_64-295.59.run
If you install the driver directly from source, it is imperative that you do not install the 32-bit compatibility library. The screenshot above (from a clean install, I suppose?) only confirms my suspicion - libGL.so.1 is now a 32-bit library instead of 64-bit.

I'm not sure how you prevent 32-bit compatibility. When I run the script like:

sh NVIDIA-Linux-x86_64-295.59.run

The screen is quite messy and it's hard to follow the prompts. Previous attempts with 32-bit, not problems at all.

Anyway, I installed the nvidia-295.59-601.pet from the Fatdog Package Manager and it installed all the correct drivers. Then I installed VirtualBox that worked properly too.

What special things did you do to make the the pet?

Thanks

Posted: **Fri 27 Jul 2012, 15:12**

smokey01 wrote:I'm not sure how you prevent 32-bit compatibility.

Choose no when asked whether you'd to install 32-bit libraries.

When I run the script like:

sh NVIDIA-Linux-x86_64-295.59.run

The screen is quite messy and it's hard to follow the prompts.

Yes, very messy. Same here too.

Previous attempts with 32-bit, not problems at all.

Because there aren't multiple libraries involved.

What special things did you do to make the the pet?

Nothing, I already informed you how I did it: http://www.murga-linux.com/puppy/viewto ... &start=450.

cheers!

Posted: **Fri 27 Jul 2012, 19:04**

I run many different puppies and other distros on my laptop, but FD601 just hangs - it finds and identifies the vmlinuz file, but just hangs on initrd. I downloaded Fatdog64-601-Firefox.iso from the Greek mirror and checked the md5sum (OK).
I have tried all sorts of parameters like waitdev and various pci parms but nothing happens and there are no error messages. Has anyone else encountered this?
I think it' could be a kernel problem but I have never had any kernel issues with this machine.
Through Grub I run Windows 7, Lighthouse64, Mint 11, Mint Debian, Macpup 528v2, Saluki 021, Racy puppy, which covers many kernels.
I have set up and run with no problems FD600 on my regular 64 bit desktop..
I'm stumped on this one. Any suggestions?

My laptop is Acer Aspire 5810tz-4775 and Hardinfo gives:
Processor: 2x Genuine Intel(R) CPU U4100 @ 1.30GHz
Memory: 3987MB Resolution: 1366x768 pixels
OpenGL Renderer: Mesa DRI Mobile Intel® GM45 Express Chipset
SCSI Disks: ATA Hitachi HTS54505 MATSHITA DVD-RAM UJ862AS

I use grub to boot everything, and my preferred method for adding a new distro is:
- download the .iso, check md5sum
- open the iso and copy the required files to a directory.
- Add an entry for the new distro to menu.lst
- reboot and test

My existing menu.lst entry for FD601 is:
title Fat Dog 601 (on /dev/sda5 - ext4)
root (hd0,4)
kernel /FatDog601/vmlinuz waitdev=3 pci=nocrs loglevel=7
initrd /FatDog601/initrd

sda5 is an extended partition formatted to ext4, and the two files in /FatDog601 are vmlinuz and initrd.

Posted: **Fri 27 Jul 2012, 20:51**

jamesbond wrote:
What special things did you do to make the the pet?
Nothing, I already informed you how I did it: http://www.murga-linux.com/puppy/viewto ... &start=450.
cheers!

So you did, but I couldn't find it, Sorry.

Thanks again.

Posted: **Fri 27 Jul 2012, 20:53**

Barburo wrote:but FD601 just hangs - it finds and identifies the vmlinuz file, but just hangs on initrd..

This sounds like the same behaviour I get when trying to boot FD600 off a flash drive - it's a BIOS issue. My solution is to use the small-initrd version from here.

I don't know if there is a small-initrd release for 601.

Posted: **Sat 28 Jul 2012, 05:27**

I have JWM working fairly well on Fatdog 601, I like using xcompmgr (for shadowing). The last JWM snapshot that works with it for me is 523. I had to compile it myself.

I have also modified the /usr/bin/jwm_menu_create, first I removed the corner tags (line #353 and #359) and then corrected one line about #391 for the pager styles foreground (This fixes the color tag error).

Reads.

Code: Select all

<Foreground>'${PAGERG}'</Foreground>

Should be.

Code: Select all

<Foreground>'${PAGERFG}'</Foreground>

This fixes the errors listed with “jwm -p

(old)Puppy Linux Discussion Forum

Fatdog64-600 Final and 601 (July 2012)

wine-1.5.9-i486_v1.pet

Re: wine-1.5.9-i486_v1.pet

Re: wine-1.5.9-i486_v1.pet

wpa_gui

xcompmgr & JWM