Puppy Gamers Unite!

[steve_s]

Well, I seem to have come full circle on this...I installed it myself, didn't like that, installed somethings that didn't work, then finally came back to the pet file that had been made for this radeon driver, a la kirk:
http://www.murga-linux.com/puppy/viewtopic.php?t=29727&sid=a811aae7860077c40261fecd0a2361f3

(thanks to kirk for creating this one...)

Edit: since then, i've discovered the correct driver for my kernel, also due to kirk's diligence, and installed it.

Edit: also, when I run

Code: Select all

fireglcontrolpanel

which is the same as clicking on the ATI Control in the menu, I get this error:

Code: Select all

fireglcontrolpanel: xcb_io.c:357: _XReply: Assertion `!dpy->xcb->reply_data' failed.

But I still don't have any 3d elements at this point. Everything looks good, but I can't really get the games going without the 3d (except REALLY slow) .

So, how can I get that set up?

[Pizzasgood]

Shot in the dark: do you have 'DRI' enabled in the xorg.conf file? Should be a line for it in the modules section.

If so, check the log at /var/log/Xorg.0.log to see if there are any errors.

[steve_s]

Shot in the dark: do you have 'DRI' enabled in the xorg.conf file? Should be a line for it in the modules section.

If so, check the log at /var/log/Xorg.0.log to see if there are any errors.

Nice catch, Pizzasgood, you may be onto something.

DRI is enabled.

however, I checked the log file and saw this...you know this stuff better than me, is this the error you are talking about and, if so, what can be done about it?

Code: Select all

drmOpenByBusid: drmGetBusid reports PCI:1:0:0
(EE) AIGLX error: dlopen of /usr/lib/dri/fglrx_dri.so failed (/usr/lib/dri/fglrx_dri.so: undefined symbol: __glXFindDRIScreen)
(EE) AIGLX: reverting to software rendering
(II) Loading local sub module "GLcore"
(II) LoadModule: "GLcore"
(II) Loading /usr/lib/xorg/modules/extensions//libGLcore.so
(II) Module GLcore: vendor="X.Org Foundation"
	compiled for 7.2.0, module version = 1.0.0
	ABI class: X.Org Server Extension, version 0.3
(II) GLX: Initialized MESA-PROXY GL provider for screen 0
(WW) <default pointer>: No Device specified, looking for one...
(II) <default pointer>: Setting Device option to "/dev/input/mice"
(--) <default pointer>: Device: "/dev/input/mice"

[steve_s]

All right, what about switching to the Linux radeon driver? Can someone tell me how to give that a try?

The reason why is that I saw this at this site:

Code: Select all

Unfortunately, the version 8.41.7 of fglrx for 10.3 is not recommended by AMD for any non-HD cards, and is known to be broken on AGP 4th and 5th generation radeons (ie. the AGP x700, x1300, x1600, etc.) 

Before using the drivers below, try running your 3D application using open source drivers: radeon.

...so, switch to the Radeon driver? If so, how? If not, what do you recomend?

Edit: well, just realized they are talking about AGP cards, and mine is a PCI express card, so not the same.

Still would love help figuring out what that error message is all about and how to fix it?

[steve_s]

I know that it is poor form to answer myself, but I am impatient to figure this out, so I'll just keep muddling along. If anyone feels that they can tell me what I should do to fix this, I would LOVE the input.

Okay, I google the error code (just copied it and searched directly).

Came across this site that had exactly the same problem on an Ubuntu install with only a slightly different card. They recomended disabling aiglx.

This siteexplains how to disable aiglx. In fact, it even mentioned that disabling aiglx is helpful in resolving the exact issue that I seem to have.

I'm going to do that tonight and post back.

[steve_s]

Ahhh! I need help with this crazy thing!!! Anyone?!!

I changed and made aiglx disabled. That seemed to take care of the error.

But, as far as I can tell, STILL NO 3D!!!! The 3dd checker gui says DRI is active "and that everything should go fast!" but the little ants in there balls don't move fast at all...games show up but crawl along...

Are there other ways to check? Is there a switch that I can click that says "3d on?"? Any other ideas on what I can try? I'm starting to have exhausted all leads...

The only other search item I've seen is that there is a library that ati-fglrx folder uses that it shouldn't be using, BUT I DON'T HAVE THAT FOLDER...

booger-snot...I don't know where to from here/what else to try...

[MU]

please zip and attach the files:
/var/log/Xorg.0.log
/etc/X11/xorg.conf

Mark

[steve_s]

please zip and attach the files:
/var/log/Xorg.0.log
/etc/X11/xorg.conf

Mark

You got it...

[MU]

the log indicates, that the driver was made for Puppy 4.

(EE) AIGLX error: dlopen of /usr/lib/dri/fglrx_dri.so failed (/usr/lib/dri/fglrx_dri.so: undefined symbol: __glXFindDRIScreen)

(II) Module glx: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0

Puppy3/Muppy008x has Xorg 7.1.

So you might have to use this pet posted by our russian friends:
http://forum.puppyrus.org/index.php/topic,307.0.html
http://puppyrus.org/pub/other/video-dri ... -8.493.pet

Mark

[steve_s]

All right...downloaded the pet file, clicked on it and installed it. Used aticonfig from command to set up xorg. (should I use xorgwizard instead?)

Still get the error with DRI...attaching the log...ALL kindsa new error messages there, mostly fglrx, not sure what to do with it...

[MU]

(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *

(WW) fglrx(0): ********************************************* *

you might have to reboot, as the old fglrx module still will be loaded.
To load the new one, you had to type something like
rmmod fglrx

To check if it is loaded you can type:
lsmod
This should show a line with "fglrx".

As it might depend on other modules, I am not sure, that "rmmod fglrx" is sufficient, so a reboot will be best.
If it still does not work, please again attach the log.
Mark

[steve_s]

I reboot all the time, but I didn't have a line for fglrx...I rebooted, lsmod now shows fglrx.

But still no DRI...

Attaching the log anyway...

Edit: from the log, what does this mean?

Code: Select all

(EE) AIGLX: Screen 0 is not DRI capable

Should I disable AIGLX as I mentioned in one of my previous posts (I would have to start all over with that since the driver is a different one than before, right?)?

And still seem to have the fglrx error listed in the log... (end edit)

[steve_s]

Okay, I've got it to where I have no errors, but everything is still moving slowly.

I run the 3dcc thing, it says, DRI is enabled (the log says that too) but it's output is 22.6 FDS, which is under 30, which is slow.

I am attaching the log, again. Please advise what I can do to get this thing moving faster...

Oh, to get rid of the error, I reinstalled Xorg 7.2, then the driver for that and this kernel, then fixed that library issue, then disabled AIGLX.

Help!!!

[MU]

ok, the log looks correct now.
So the basic setup works correct.
The only thing I could imagine is, that there is an issue with your version of:

/usr/X11R7/lib/libGL.so.1.2

To check this, please type in a console:
fglrxinfo
Or if that is not included, and you run Muppy:
/usr/X11R71/bin/fglrxinfo

I get this for the free Xorg driver:

# /usr/X11R71/bin/fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: Tungsten Graphics, Inc.
OpenGL renderer string: Mesa DRI R200 20060602 AGP 2x x86/MMX/SSE TCL
OpenGL version string: 1.3 Mesa 6.5.2

Important is to get:
OpenGL version string: 1.3

If you get 1.2, and something about "indirect", then your libGL.so is wrong.
Please post, what result you get.

Before we make any further experiments, please backup your pup_save.2fs (msy_save.2fs) now, that the fglrx driver is loaded correctly!!
Mark

[steve_s]

Code: Select all

display: :0.0  screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.4 (1.5 Mesa 6.5.2)

Segmentation fault

...so it looks like you got it.

How do I fix that?

[MU]

this is a bit difficult, as I am not sure, what libGL.so you have.
Assuming you made this:
1.) installed xorg
2.) installed a ATI.pet

Then you should have the libGL from ATI.
This should work.
What pet did you install?
One quick thing you could try:
Replace your one (backup first) with the ones attached in this thread:
http://www.murga-linux.com/puppy/viewtopic.php?t=28031
Then try fglrxinfo again.

I think it is not required to restart X.
Also look in /tmp/xerrs.txt, if you find a hint, why indirect opengl is used, that file has several warnings and hints.

Maybe it is because you deactivated AIGLX?

Mark

[steve_s]

this is a bit difficult, as I am not sure, what libGL.so you have.
Assuming you made this:
1.) installed xorg
2.) installed a ATI.pet

Then you should have the libGL from ATI.
This should work.
What pet did you install?
One quick thing you could try:
Replace your one (backup first) with the ones attached in this thread:
http://www.murga-linux.com/puppy/viewtopic.php?t=28031
Then try fglrxinfo again.

I think it is not required to restart X.
Also look in /tmp/xerrs.txt, if you find a hint, why indirect opengl is used, that file has several warnings and hints.

Maybe it is because you deactivated AIGLX?

Mark

Here are the steps I took:

1. I installed xorg_BASIC-7.2.pet and xorg_DRI_MODULES-7.2.pet
2. I installed ATI_driver-8.40.4.pet
3. After looking at that thread you provided, MU, I used the libGL that wasn't the "Mesa" one. (should I use the other one? Couldn't understand with the edit/reposting in that thread which was the better one to use). This is, however, the first time I've replaced that library in that location, so it probably had been overwritten.

4. Rebooted, just to be sure.

Here is fglrxinfo, again:

Code: Select all

display: :0.0  screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.4 (1.5 Mesa 6.5.2)

Segmentation fault

I am attaching xerrs.log, even as I begin looking through it myself. (strange errors in that one!)

think I should reactivate aiglx?

[MU]

(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
(II) Module already built-in
(II) Module already built-in

now this I don't understand (the other messages you can ignore).

According to your last /var/log/Xorg.0.log, there was no error with fglrx.
Can you please look up, if it now lists errors again?

At moment, I have no idea, what else could be wrong.
Usually the libGL.so from your ATI_driver-8.40.4.pet should work fine, as it was made for the fglrx driver.

So lets look at the log again. If we don't find a hint in it, I would be clueless

Please re-activate AIGLX, too, to see, if that fixes something.

Mark

[steve_s]

MU: if I haven't said it before: thanks for taking the time to look at this stuff...what a pain.


No obvious errors in the log prior to initializing aiglx.

Reinitialized aiglx (enabling it).

Rebooted.

Instant aiglx errors in the log. Attaching.

lsmod shows fglrx listed. rmmod fglrx shows fglrx already in use.

[MU]

ok, so this:

(EE) AIGLX error: dlopen of /usr/lib/dri/fglrx_dri.so failed (/usr/lib/dri/fglrx_dri.so: undefined symbol: __glXFindDRIScreen)

seems to be the result of ativating AIGLX.
So it really must be deactivated.

You might attach the log again after deactivating AIGLX and rebooting, though I fear, that now I am out of ideas
I'm really sorry...

Mark