Puppy Gamers Unite!

Message

#31 Post by MU » Sun 13 Jul 2008, 01:47

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 · #32 Post by **steve_s** » Sun 13 Jul 2008, 20:27

MU wrote: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?

#33 Post by MU » Sun 13 Jul 2008, 23:46

(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 · #34 Post by **steve_s** » Mon 14 Jul 2008, 00:46

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.

#35 Post by MU » Mon 14 Jul 2008, 00:52

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

steve_s · #36 Post by **steve_s** » Mon 14 Jul 2008, 13:34

MU wrote: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

Ok, attaching a zipped file with /etc/X11/xorg.conf, /tmp/xerrs.log and /var/log/Xorg.0.log

I'm also checking around the "local computer place" as I have some friends here that might be able to give some other ideas...just trying to track down the best one. Tough to find other knowledgable sources in this category since you've already been so thorough, MU, but I'll follow any lead at this point...

steve_s · #37 Post by **steve_s** » Mon 14 Jul 2008, 15:28

Anyone please chime in, but especially MU and tombh. And of course, anyone that has gotten one of these @#$%@% x1600 ATI cards to work with Puppy.

The reason I mention tombh is because I saw this threadand am wondering if there is anything in that initial explanation that he did that can help me get my card going. I'm not using aiglx and am using the proprietary driver but tom edits a line that I had never heard about and I wonder if that would help me...suggestions?

...just about in full out experimental mode with this card at this point...

Edit: and Ubuntu install uses a different ATI downloaded driver (why do they use that one?) for this card...may have to experiment.

#38 Post by MU » Mon 14 Jul 2008, 15:43

the thing that myself I would try now:

1.)
Exit X, and run
aticonfig

This is a utility from ati, to create a new xorg.conf
Then
xwin

to start X.

no success?

2.) download the development-addon (Muppy 0083):
ftp://ks301128.kimsufi.com/Muppy0083/EN ... nt_083.sfs

Place it in "/" of the drive, where your msy_save.2fs is stored.
Add it in the bootmanager, and reboot.

Then download the installer from ati.com, and run it.

When I created dotpups for older versions of the driver, I had to run the installer several times, because I had overseen several things it created, when I made the dotpups.

Maybe there is missing something small but evident in the ATI_driver-8.40.4.pet.
Mark

steve_s · #39 Post by **steve_s** » Mon 14 Jul 2008, 16:30

MU: see my edit of my last post...is it the driver itself?! Just don't know why that Ubuntu wiki uses that driver.run file...

#40 Post by MU » Mon 14 Jul 2008, 16:46

driver 8.25.18 is outdated.
I think it is a optional driver for Ubuntu, as it supports older cards, too.
The last driver supporting Radeon 7000 to 9250 was version 8.28.8, I also packaged such a driver for Puppy (not recommended for new cards).

I think, it is not good for you, also these old drivers were quite unstable.
I experienced many crashes with 8.28.8, so use Puppys free xorg-drivers instead.

I'd suggest to install the current with the installer from ati.com.

Mark

steve_s · #41 Post by **steve_s** » Tue 15 Jul 2008, 00:08

All right, Mark (and anyone else reading).

I downloaded and settup the development sfs.

I ran the ati .run driver from their site, very current.

I disabled aiglx.

I changed the library in /usr/X11R7/lib to the libGL with the Mesa distinction from the other thread that you did/mentioned.

I rmmod fglrx.

lsmod shows fglrx.

Oh, I rebooted in between each of these steps.

And now I got the DRI won't enable error in my Xorg.0.log! What @#$@?

Attached it again...early in the thread I show that I got rid of that error, but didn't say how and for the life of me can't remember.

Any idea how to get DRI to enable?

steve_s · #42 Post by **steve_s** » Tue 15 Jul 2008, 23:36

MU (and anyone else):

Is this significant? Why aren't the radeon and dri modules listed in lsmod? They should be right? I'm attaching it zipped...

I had run rmmod radeon and rmmod dri and it says neither one exists.

#43 Post by MU » Wed 16 Jul 2008, 04:16

that is ok.
fglrx is loaded, so drm and radeon were unloaded before.

radeon + drm = free driver
fglrx = propriatary driver from Ati

but fglrx is unused...
Mark

steve_s · #44 Post by **steve_s** » Fri 18 Jul 2008, 13:49

Still here, still trying to get it to work. I think it is just 'cause I'm so cheap and won't go out and buy an Invidia card...maybe my frugality will lead to an answer and a good gaming system.

Here is a site for the DRI users guide that I have been going through. Anyone (MU) see anything that I might have missed? I've checked out bus mastering and a few other options...

What about using the Generic drivers rather than the ATI driver? Do I have any chance at that working? How can I give that a shot now that I've done all this with ATI driver?

Also, noticed Envy here at this site, but also this thread in Puppy forums talking about how they couldn't get it to go. I encountered similar problems messing with it last night, but wondered if anyone has had luck with Envy on Puppy.

As always, any input on this is appreciated...

Attached is the latest Xorg.0.log and /etc/X11/xorg.conf...there is the DRI error on Xorg log, so maybe someone else can figure out how I can fix that...

#45 Post by MU » Fri 18 Jul 2008, 13:56

What about using the Generic drivers rather than the ATI driver? Do I have any chance at that working? How can I give that a shot now that I've done all this with ATI driver?

create a second savefile.
msy_save-DUMMY.sfs

It can be an empty textfile.
If you reboot, you get a menu, to choose one of the two savefiles, or boot to Ram.
Choose Ram here.
When Puppy started, shut down again, now you are offered to create a valid savefile.
Use a unique name here like "test2".
On reboot, you now can choose your old one, or this new one for testing.
Mark

steve_s · #46 Post by **steve_s** » Fri 18 Jul 2008, 14:47

MU wrote: On reboot, you now can choose your old one, or this new one for testing.
Mark

...man, you're like superman or Puppy Ninja or something...great advice.

Would the process then simply be activation of the correct modules, using radeon and drm and blacklisting fgrlx? Or is there a more extensive process? Know any good thread on that?

#47 Post by MU » Fri 18 Jul 2008, 14:53

both savefiles are 100% independent.

So the new one starts without fglrx.
it should use in xorg.conf

load "dri"
load "glx"
driver "ati"

by default, these are the settings for the free Xorgdriver.

Supported cards then have 3D accelleration enabled (immedeatly in "Muppy-Standard/Live" , or when you added addons.sfs in the bootmanager, if you use the Mini).

Mark

steve_s · #48 Post by **steve_s** » Fri 18 Jul 2008, 15:09

MU wrote:both savefiles are 100% independent.

So the new one starts without fglrx.
it should use in xorg.conf

load "dri"
load "glx"
driver "ati"

by default, these are the settings for the free Xorgdriver.

Supported cards then have 3D accelleration enabled (immedeatly in "Muppy-Standard/Live" , or when you added addons.sfs in the bootmanager, if you use the Mini).

Mark

Hmmm...so basically it should work right away or not at all. Gotcha.

Ok, I'll try it tonight, hopefully, and post back.

steve_s · #49 Post by **steve_s** » Sun 20 Jul 2008, 17:51

All right, the radeon/drm modules are in lsmod.

Oh, I created the "test" install without a hitch and we are now using the generic drivers they are at least a little quicker (now at about 24 fps rather than 22).

I have no errors in Xorg.0.log since I disabled aiglx.

Still no DRI, though.

I have attached a zip file with xorg.conf, Xorg.0.log and xerrs.log just for fun.

Please help get DRI activated!

#50 Post by MU » Sun 20 Jul 2008, 18:07

the xorg.conf is wrong.

Delete (line 26):

Code: Select all

    Load 	   "drm"
    Load 	   "radeon"

Instead, replace (line 133):

Code: Select all

	Driver      "vesa" #card0driver

with:

Code: Select all

	Driver      "ati" #card0driver

or with:

Code: Select all

	Driver      "radeon" #card0driver

It should not matter, if you use ati or radeon.
Mark

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Puppy Gamers Unite!