(old)Puppy Linux Discussion Forum

Anniekin wrote:Hey James,
Skype 4 seems to be working well, haven't seen any ads yet, unlike in the Windows version

Good to hear this!

The new fatdog comes with the new kernel no-xorg.conf by default, what do I do to enable opengl to play windoze games

is this enough to have as xorg.conf?
Section "Device"
Driver "radeon"
EndSection

or do i need to put more than that?

glxgears works with my current config (no-xorg) as well as glxinfo indicating rendering is on, yet Guild Wars complains about 3dx / direct x

Fatdog comes with full Xorg and Mesa OpenGL drivers (in other puppies usually called as "Xorg High" package). It provides native 3D facilities out of the box. Of course, if you need higher performance, you'll probably want the proprietary Catalyst driver.

But - I'm afraid windoze games are not supported properly in Fatdog. This is because Wine is 32-bit apps. Wine emulates DirectX using OpenGL, but being 32-bit apps it requires 32-bit OpenGL libraries - which are not in Fatdog and in all likelihood is not in the 32-bit libraries as well, sorry Your best bet is to run wine with Slacko, and install "Xorg High".

Also unrelated but PCM audio channel is not present on my new acer aspire 722, do i have to add some package?

Probably because your system is too new Anyway, run "Pdiag.sh" and upload the output to me, I'll see what I can do (no promises).

Window manager locks up alot on boot, not sure if it is because I plugged in a wireless mouse,

What do you mean by "window manager"? When does the lock-up happens? I have wireless keyboard and mouse plugged at all times and don't get the lockups ....

cheers!

Thanks James,

Pdiag info attached

I guess I need 'lib32-catalyst-utils'

What do I need to download and compile to get it?

I have a little experience compiling stuff from making pup4pentiums

pls advise,
thanks

Anniekin wrote:Thanks James,
Pdiag info attached

Your soundcard isn't detected
Either your card is too new; or your card need firmware. It's most likely the first one, unless you tell me that you can get other puppies to produce sound here.
Generally there isn't any solution to this other than waiting until alsa driver is updated (Fatdog already has the latest driver).

I guess I need 'lib32-catalyst-utils'
What do I need to download and compile to get it?
I have a little experience compiling stuff from making pup4pentiums

Probably not that one. You need the "catalyst-driver" or something like that; it's better if you get Slacko specific pets instead of the generic slackware packages. But beware: 32-bit packages will usually install to /usr/lib. In Fatdog, /usr/lib points to 64-bit packages, so a plain install will overwrite Fatdog's native library and your system will stop working. You need to install 32-bit packages to /lib32, /usr/lib32, and /usr/X11R7/lib32. You have to un-tar and copy the files over by hand.
If you do get it to work let me know

cheers!

ok,

I dont have to compile anything right?

I'm getting that fatdog is slacko based

but the (much improved interface) package manager does not have the option to select slacko repositories like other puppy derivatives

so I will just try with the official slacko packages from ibiblio

Anniekin wrote:ok,
I dont have to compile anything right?

I don't think so.

I'm getting that fatdog is slacko based

No, Fatdog itself isn't based no Slacko. But the 32-bit compatibility libraries which is required for wine to work *is* based on Slacko, that's why I keep referring to Slacko here

but the (much improved interface) package manager does not have the option to select slacko repositories like other puppy derivatives

Yes, because all those packages won't work, unless you install the 32-bit compatibility library. Even then not all of them will work --- some just won't.

so I will just try with the official slacko packages from ibiblio

That's the idea!

I know absolutely nothing but I've been told that FatDog 600 is T2 based
Now many others are too so FatDog is Kirk and JamesBond based.

thanks,

btw, i figured out the issue with the WM locking up on startup

I eventually quit the X server before it locked up

the cli shows Fatal IO Errors for the jwm_applets which seem to be the culprit

some of them say between 1000 to 2000 requests made, could have been overloading my computer

could be caused by volume applet as my system is missing PCM, but the errors are returning for each applet

Ah, JWM isn't well tested or supported because myself and kirk don't use it. the jwm_applets consist of a few applets, you can disable them one by one to see which one works.

Fatdog 600 final is here: http://murga-linux.com/puppy/viewtopic.php?t=79537

To us who don't really know English abbrev....

TBD means?

TBD - Acronyms - The Free Dictionary
acronyms.thefreedictionary.com/TBD
Acronym, Definition.
TBD, To Be Determined.
TBD, To Be Defined.
TBD, To Be Decided.
TBD, To Be Done.
TBD, To Be Developed.
TBD, To Be Discussed ...

Nooby's suggestion.

TBD, To Be Downloaded and booted now !

I have followed your suggestions and packaged the slacko ati drivers renaming all etc and lib dirs to 32

I have uploaded at:

http://dimensions-web.com/downloads/amd ... -s_600.sfs

however it is not working

I have followed your suggestions and packaged the slacko ati drivers renaming all etc and lib dirs to 32

I doubt that's going to work. Besides getting all the 32bit slacko ati stuff in the right placed you'll need a 64bit fglrx kernel module. You could possibly get that out of the Fatdog64 ATI pet package if it's the same version as the slacko version. That's going to take a lot of luck.

so... no gaming on fatdog?

I've enjoyed the speed of Fatdog64 drive mounter so much that I failed to notice that all linux partitions are recognized as ext3.

Yes, thanks, that's guess_fstype bug again. I see Barry has fixed it in Woof, I'm going to steal that for Fatdog hehehe
EDIT: it's also busybox problem, so I have patched busybox to recognise ext4 correctly.

For those of you who have trouble running some 32-bit stuff (especially Skype), here's a neat trick I discovered today.

I wanted to run Skype on my distro and it's 64-bit only, with 32-bit compatibility only in the kernel (e.g no 32-bit libraries) - this is a great solution. I had a weird issue - I couldn't run any graphical application and I solved it too.

In my testing I ran a Slackware 13.37-based, x86_64 distro against Slacko 5.3.4's beta.

Step 1: extract a main SFS of a 32-bit Puppy. Copy your .Xauthority file inside, so graphical applications can connect to your X server. Step 2: install your stuff, in my case it's just Skype. Step 2: bind its virtual file systems and /dev to your running distro's ones, so it can access your hardware and kernel information. Step 3: chroot! pwd is used to make sure chroot worked (the output will be"/") Now you can do whatever you want inside that 32-bit Puppy, as if you were running it! The fun part is that all 32-bit stuff run in a sandbox so they cannot pollute your system (e.g /lib and /usr/lib) - you don't have to install anything.

The whole thing can be wrapped in a script, by the way, so executing Skype is transparent.

EDIT: amazing. Wrote a script which automates this and now I can issue "skype" as if Skype was natively installed.

Iguleder :

Thanks Iggy for that.

There was a post last week about 32 and 64 bit questions.

I will point them here to your reply when I come across it again.

Cheers...and look after yourself mate....Chris.

Iguleder where do I find this .Xauthority file?

It's not in any SFS files I have checked

cp ~/.Xauthority squashfs-root/root

Any chance of a copy of the script you referred to.

Thanks

Since nobody answered ...

smokey01, .Xauthority file is a file that is created/needed when X server is run with security enabled. Almost all puppies don't do this, so you won't find this file and you can simply ignore it. Fatdog only uses the security mode when you enable the use of graphical login manager.

Anniekin, I managed to get DirectX running in Fatdog64 with nvidia. The trick is to get the correct 32-bit libraries. I installed 32-bit nvidia (using the x86 driver bundle) in sandbox, get all those files and move them under /lib32 - and voila it works! With this, I managed to get wine (and older version no less! 1.3.25) to start and run Freelancer from Fatdog64
Note: only the userland libglx stuff are needed. Do not install 32-bit xorg or kernel modules - these must come from 64-bit driver.
I haven't tested radeon or intel graphics - but the principle is the same.

I have to run networkwizard and do auto-dhcp on eth0
everytime I boot up

I tried
rm -f /var/run/dhcpcd-eth0.pid
dhcpcd -h aalo -d eth0

from terminal

Seems like it connects but nothing happens when I try
to reach internet


Maybe I've missed some step that network wizard does?

Does it do some configuration of eth0? ifconfig?

I strongly believe we need a sub-forum designated to Fatdog64.
Having just this topic makes it hard to find specific information.
It would be nice to be able to have separate topics for specific issues, such as bug reports, questions, requests for improvements, etc.
Can you please make it happen?