Page 1 of 2

puppy 4.3beta2/3 Ati Catalyst 9.9 graficsdriver

Posted: Sat 12 Sep 2009, 13:58
by MU
I compiled the kernelmodule and repackaged the Catalyst 9.8 pet, that was introduced here:

http://www.murga-linux.com/puppy/viewtopic.php?t=45594
Update: upgraded it to 9.9.

You also can read there more info about that driver.

You can download the updated pet from:
http://dotpups.de/puppy4/dotpups/XServe ... 3beta3.pet


I also compiled 9.3 after applying some patches from:
http://bugs.gentoo.org/show_bug.cgi?id=266819
The driver then works with accellerated 2D, for example videos run fullscreen.
But running the Control Center or antinspect (so programs accessing OpenGL), the computer completely freezes.
It seems, that this problem is not fixable - if you depend on 9.3, you need a puplet with an older Kernel, like Puppy 4.3 beta1, see:
http://www.murga-linux.com/puppy/viewtopic.php?t=45601
BROKEN 9.3:
http://dotpups.de/puppy4/dotpups/XServe ... 3beta3.pet

Note:
to use 2 monitors, have a look at this small utility, I did not add it yet to the driver pets:
http://www.murga-linux.com/puppy/viewtopic.php?t=41625

Mark

Posted: Sat 12 Sep 2009, 17:17
by panzerpuppy
Catalyst 9.9 is out with a bunch of OpenGL rendering fixes:

- Rendering bugfixes for various Open-source 3D game engines
- Unigine Tropics works correctly
- OpenGL updates, fixes and improvements
- Crossfire support in the AMDCCCLE properties
- Randr 1.2 fixes

This driver is much better than previous version. Although the release notes don't say much, this version contains fixes for many of the rendering problems of the previous release.

Posted: Sun 13 Sep 2009, 01:44
by panzerpuppy
Only for Xorg 7.4 and later :(

Posted: Sun 13 Sep 2009, 18:02
by MU
updated from 9.8 to 9.9.
Installed fine in Puppy 4.3beta3 :)
Mark

Posted: Sun 13 Sep 2009, 18:13
by exProphecy
Nice nice I shall soon try this on with Pup4.3beta2 on my Radeon Mobility x700..

By the way, why is it only ATI .pets are being made for the new kernels? Racism I presume? hehe just kiddin'

Posted: Sun 13 Sep 2009, 18:17
by MU
By the way, why is it only ATI .pets are being made for the new kernels? Racism I presume? hehe just kiddin'
I do have a Nvidia 7050 in this computer, but need to remove the external Ati, to be able, to use it.
The Ati is not so stable, as I added a passive cooler, and two fans attached with some wire on it.

In addition, I had to look up again, how I had built the Nvidia pets.
I will do it, once the final version of 4.3 is out, but until then, it is too much work.

The Ati pets are built quickly, as I use the existing ones as templates, and basically just update the files in the older pets to create a new one.
Mark

Posted: Sun 13 Sep 2009, 18:52
by panzerpuppy
MU wrote:Installed fine in Puppy 4.3beta3
Weird,cause the official ATI installer displays a warning: for X.Org 7.4 and later.

Nice to see it working with X.Org 7.3 as well :)

P.S. Where can I download the kernel source .SFS for Puppy 4.3?

Posted: Sun 13 Sep 2009, 21:52
by panzerpuppy
Does this Catalyst PET package work at all if you've already installed the Xserver-1.6.3-Mesa-7.5.1-xf86-Radeon upgrade package ?

Posted: Mon 14 Sep 2009, 04:36
by MU
panzerpuppy wrote:Does this Catalyst PET package work at all if you've already installed the Xserver-1.6.3-Mesa-7.5.1-xf86-Radeon upgrade package ?
no, you need a fresh install.
I had to build another pet for the upggraded xorg, but did not try, if xserver 1.6.3 is already supported.

The kernelsource:
http://puppylinux.com/sources/kernel-2.6.30.5/

http://puppyisos.org/isos/Puppylinux-of ... el-source/

User: puppy
Password: linux

Mark

Posted: Mon 14 Sep 2009, 08:28
by exProphecy
In addition, I had to look up again, how I had built the Nvidia pets.
I will do it, once the final version of 4.3 is out, but until then, it is too much work.
OooOO yay! How sweet of you! My main laptop uses Nvidia GeForce G 105M so that would be a useful .pet. What is the most recent .pet for nvidia drivers anyways? And what kernel is it for?

Posted: Tue 20 Oct 2009, 02:56
by Flash
Rats, antinspect says this after I installed the 9.9 .pet:
antinspect: error while loading shared libraries: libGLU.so.1: cannot open shared object file: No such file or directory
-hit a key to exit-
Puppy version is 4.3.1, run from a multisession DVD.
Motherboard is a Gigabyte GA-MA69GM-S2H, which has the AMD 690G graphics chip. I'm pretty sure that chip uses the Catalyst driver. It's working pretty well with Xvesa, but when I try to use the full resolution of the display the edge of the desktop is off the screen, hiding some icons.

Posted: Tue 20 Oct 2009, 22:12
by MU
Flash,
after installing the Pet you MUST exit X and type:
xorgwizard

This will extract the catalyst drivers, some libs like libGLU.so.1, and update xorg.conf.

Mark

Posted: Wed 21 Oct 2009, 01:28
by Flash
Thanks, Mark. I thought I did that last night but I could have been a little sloppy about the order. :oops:

Funny thing, the .pet I stored last night on my USB flash drive would not install. I had to install it from a fresh download. After it was installed I went to Menu --> Exit to prompt, entered xorgwizard, and chose to use the ATI drivers. This time at least it correctly detected the maximum resolution of my LCD (1440 x 900). But the desktop is still too big for the screen. :(

When I ran antinspect, it dropped me back to the prompt, where I re-ran xorgwizard. After I got the desktop back, I ran xvidtune from the command line (The dialog window froze when I chose Xorg video wizard from the Setup menu) and got this:
# xvidtune
Vendor: Monitor Vendor, Model: Monitor Model
Num hsync: 1, Num vsync: 1
hsync range 0: 30.00 - 83.00
vsync range 0: 50.00 - 72.00
Video are not settable on this chip
#
I think the AMD 690 chip was designed during the transition from ATI to AMD, and they did a slap-dab job of it because it was meant to be a placeholder until they could get something better on the market. The reason I bought this motherboard is that it was the only way I could find to put audio through a HDMI cable in Windows 2000. I didn't want to have to "upgrade" to Windows XP in addition to everything else.

Ah, well. The search for perfection continues.

Posted: Wed 21 Oct 2009, 22:40
by MU
flash,
you had to zip and attach
/var/log/Xorg.0.log

This file is extremely important whenever things work unexpected in Xorg.
It gives info about detected chipsets, and potential problems.

If antinspect crashes, this indicates, that the "fglrx.ko" kernelmodule was not loaded. I that case, the catalyst drivers often crash, when you try to run an application, that uses OpenGL.

You can check that by typing:
modprobe fglrx
If you get an error here, your card is not supported.
The log can give us more detailed infos, so please attach it.

Mark

Posted: Thu 22 Oct 2009, 01:53
by Flash
# modprobe fglrx
FATAL: Module fglrx not found.
#
:(

Oh well. Anyway, everything seems to work fine with Xvesa now. I just thought I'd try your Catalyst .pet to see if it would be better somehow.

Posted: Thu 22 Oct 2009, 02:36
by MU
# modprobe fglrx
FATAL: Module fglrx not found.
This just should happen in two cases:
1.) you use a Puppy with a different kernel.
To test that, type:
uname -r
This should return:
2.6.30.5

2.) Not enough diskspace
The pet installs a huge archive:
/usr/local/graficsdrivers/atilatest.tgz
Do you have that? It is around 30MB.

If yes:
3.) when you run xorgwizard and choose the Ati driver, that archive is extracted.
This creates (beside others) the file:
/lib/modules/2.6.30.5/kernel/drivers/char/drm/fglrx.ko
Do you have that?

If not, then something went wrong with extraction.
Maybe not enough free diskspace?
What do you get please by typing:
df -m

If you DO have that file, then it was not properly registered to the kernel. In that case, please type:
depmod -a
and exit X and run xorgwizard again.

Please let me know your results, so that I can fix it in the pet, if it contains any error.
Mark

Posted: Thu 22 Oct 2009, 03:00
by Flash
Just for fun I went ahead and installed the .pet again, but before I could post Xorg.0.log my system froze so solid the only way I could get it to work again was a hard reboot.

So I did it again. :lol:

Yes, I have the file /usr/local/graficsdrivers/atilatest.tgz

Yes, I have the file /lib/modules/2.6.30.5/kernel/drivers/char/drm/fglrx.ko
# uname -r
2.6.30.5
#
# df -m
Filesystem 1M-blocks Used Available Use% Mounted on
tmpfs 1599 115 1485 8% /initrd/pup_rw
tmpfs 1599 7 1593 1% /initrd/pup_ro1
tmpfs 103 102 1 100% /initrd/mnt/tmpfs
/dev/loop0 102 102 0 100% /initrd/pup_ro2
unionfs 1599 115 1485 8% /
#
I ran depmod -a then reran xorgwizard, with this result:
# modprobe fglrx
FATAL: Error inserting fglrx (/lib/modules/2.6.30.5/kernel/drivers/char/drm/fglrx.ko): Cannot allocate memory
#

Posted: Thu 22 Oct 2009, 03:19
by MU
ok, I see:
your log tells me:
(--) PCI:*(1:5:0) ATI Technologies Inc ATI Radeon Xpress 1200 Series rev 0,
The 1200 is not supported by driver 9.9, only by 9.3.
But as explained in the first message, the 9.3 works erratic with Kernel 2.6.30.5.
You might get a correct resolution, but the driver will crash with 3D applications.

An alternative for that chip might be the free Xorg drivers:
http://www.murga-linux.com/puppy/viewtopic.php?t=46266

But I don't know, if the 1200 has 3D support with those free drivers.
If you want to try those, do it ONLY with a new savefile, as they overwrite Puppys existing xorg with an incompatible version.
That free driver pet is only intended for those cases, where everything else fails.

Mark

Posted: Thu 22 Oct 2009, 03:26
by MU
oh yes, and if you want to use xorg again with the vesa driver, just run xorgwizard, and choose "xorgwizard - force vesa".

This will extract working opengl drivers.
You then have no accellerated 3D, but at least such applications should no longer crash (they just run slow then).

Without this, you would run a mix of catalyst and free Xorg libraries.

Mark

Posted: Thu 22 Oct 2009, 03:28
by Flash
Okay, Mark. Thanks for all your trouble. :)

Since I'm running Puppy from a multisession DVD I'll just shut down without saving. Next time I boot, I'll be back to Xvesa.

I'll give the free Xorg drivers a try next.