Problems with ATI 9200SE and Suse 9.0
Hi, I tried to use the Suse driver for the ATI grafics adapter and the ATI driver. When I restart the X-Server the same happens he isn't able to show anything. A white light is flushing and then the screen is only black. Is here anybody that tried this drivers? And was successfull with them? Nimer
I have the exact same ATI graphics card (9200SE), and try as I might, I cannot get it to work. If ANYBODY has any help to contribute on this, I'd really appreciate it. I've tried the step by step HowTo: on LinuxGamer.net, and a couple found on other websites, each followed perfectly to the letter. My problem is that everything seems to install just fine. I manually install the drivers, run the config. However it just doesnt DO anything. I'd much rather prefer getting errors or bugs, at then I'd be able to see SOME kind of progress. I still see the Mesa drivers as the drivers used, when it should report ATI's drivers (which I have installed...numerous times), Gxlgears (run as a test) averages about 340fps. Nimer wrote:
I tried to use the Suse driver for the ATI grafics adapter and the ATI driver. When I restart the X-Server the same happens he isn't able to show anything. A white light is flushing and then the screen is only black.
On Thu, 19 Feb 2004 15:00:26 -0700 Ralph Jones <kestrel@dimensional.com> wrote:
My problem is that everything seems to install just fine. I manually install the drivers, run the config. However it just doesnt DO anything. I'd much rather prefer getting errors or bugs, at then I'd be able to see SOME kind of progress. I still see the Mesa drivers as the drivers used, when it should report ATI's drivers (which I have installed...numerous times), Gxlgears (run as a test) averages about 340fps.
Have you run switch2xf86_glx? Is the kernel module loaded (before the X server has started)? Cheers, Ingo -- "What're quantum mechanics?" "I don't know. People who repair quantums I suppose." --Rincewind, Terry Pratchett "Eric"
On 19.02.2004 23:10, Ingo Strauch wrote:
Have you run switch2xf86_glx?
This script doesn't exist any more in SuSE 9.0. If anybody knows, which mechanism decides about which libGL.so (MESA or vendor) is being loaded, please tell me! Regards, Oliver
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 19 February 2004 11:04, Nimer wrote:
Hi,
I tried to use the Suse driver for the ATI grafics adapter and the ATI driver. When I restart the X-Server the same happens he isn't able to show anything. A white light is flushing and then the screen is only black.
Is here anybody that tried this drivers? And was successfull with them?
Nimer
I'm curious. For those that have been having problems post the results of the following command please: rpm -qa | grep mesa And perhaps rpm -qa | grep mesasoft Curtis. :) - -- Spammers Beware: Tresspassers will be shot, survivors will be shot again! Warning: Individuals throwing objects at the crocodiles will be asked to retrieve them! If pro is the opposite of con, then the opposite of progress must be congress! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFANWtUN9r/ngHXpykRAt1cAJ0RBnEKw6hzUVdidON9Zb2Zy6rqzgCgpcjy qhGKLIoGFX9iwkzZ5pP4gU8= =ewQU -----END PGP SIGNATURE-----
On 19.02.2004 20:04, Nimer wrote: > Is here anybody that tried this drivers? And was successfull with > them? My experience was similar, but I managed to get my Radeon9600pro running with the original ATI drivers now. I think, one big drawback of the SuSE versions of this drivers is, that it doesn't supply the libGL.so. This helped me: http://www.linuxquestions.org/questions/history/122514 http://www.gmpf.de/ Notice that the following will *not* work if You have an nForce(2), VIA KT400/600 or SiS 648 chipset. You should read carefully what is written on http://www.gmpf.de/ in that case. I did the following: - installed the kernel source from SuSE (must match running kernel!); - installed the drivers from the ATI page with > rpm -i fglrx-glc22-4.3.0-3.7.0.i386.rpm - cd /usr/src/linux; make cloneconfig; make dep - cd /lib/modules/fglrx/build_mod; ./make.sh; cd..; ./make_install.sh - configured X with > sax2 -r -m 0=fglrx -b /usr/X11R6/lib/sax/profile/firegl - add the line Load "dri" to the "Module" section of /etc/X11/XF86Config - run fglrxconfig and answer the quesions; if in doubt, accept the default; specify you want to use the *external* agpgart module! (this is important) - load the agpgart module by adding the line /sbin/insmod agpgart to /etc/init.d/boot.local - mv /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.generated - copy relevant lines [1] from /etc/X11/XF86Config-4.generated to /etc/X11/XF86Config - do not run sax2 any more! - restart or do > init 3; rmmod fglrx; insmod agpgart; init 5 - check if glxinfo shows "direct rendering: Yes" - post the result of > glxinfo | grep "glx ve*" and > glxinfo | grep fbconfig to me or on this list or to satisfy my curiosity ;-) [1] relevant lines depend on the answers you have given in fglrxconfig, in my configuration: > # === disable/enable XAA/DRI === > Option "no_accel" "no" > Option "no_dri" "no" > # === misc DRI settings === > Option "mtrr" "off" # disable DRI mtrr mapper, driver has its own code for mtrr > # === FSAA Management === > Option "FSAAEnable" "no" > Option "FSAAScale" "1" > Option "FSAADisableGamma" "no" > Option "FSAACustomizeMSPos" "no" > # === Misc Options === > Option "UseFastTLS" "0" > Option "BlockSignalsOnLock" "on" > Option "UseInternalAGPGART" "no" ## THIS IS IMPORTANT !!! > Option "ForceGenericCPU" "no" in section "Device" That's what worked for me (Radeon 9600pro, Asus P4P800 w/ Intel 82865PE chipset). HTH! Regards, Oliver
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 20 February 2004 00:48, Oliver Baum wrote:
On 19.02.2004 20:04, Nimer wrote:
Is here anybody that tried this drivers? And was successfull with them?
My experience was similar, but I managed to get my Radeon9600pro running with the original ATI drivers now. I think, one big drawback of the SuSE versions of this drivers is, that it doesn't supply the libGL.so.
This helped me: http://www.linuxquestions.org/questions/history/122514 http://www.gmpf.de/
Notice that the following will *not* work if You have an nForce(2), VIA KT400/600 or SiS 648 chipset. You should read carefully what is written on http://www.gmpf.de/ in that case.
sax2 -r -m 0=fglrx -b /usr/X11R6/lib/sax/profile/firegl
- add the line Load "dri" to the "Module" section of /etc/X11/XF86Config - run fglrxconfig and answer the quesions; if in doubt, accept the default; specify you want to use the *external* agpgart module! (this is important) - load the agpgart module by adding the line /sbin/insmod agpgart to /etc/init.d/boot.local - mv /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.generated - copy relevant lines [1] from /etc/X11/XF86Config-4.generated to /etc/X11/XF86Config - do not run sax2 any more! - restart or do
init 3; rmmod fglrx; insmod agpgart; init 5
- check if glxinfo shows "direct rendering: Yes" - post the result of
glxinfo | grep "glx ve*"
and
glxinfo | grep fbconfig
to me or on this list or to satisfy my curiosity ;-)
[1] relevant lines depend on the answers you have given in fglrxconfig,
in my configuration:
# === disable/enable XAA/DRI === Option "no_accel" "no" Option "no_dri" "no" # === misc DRI settings === Option "mtrr" "off" # disable DRI mtrr mapper, driver has its own code for mtrr # === FSAA Management === Option "FSAAEnable" "no" Option "FSAAScale" "1" Option "FSAADisableGamma" "no" Option "FSAACustomizeMSPos" "no" # === Misc Options === Option "UseFastTLS" "0" Option "BlockSignalsOnLock" "on" Option "UseInternalAGPGART" "no" ## THIS IS IMPORTANT !!! Option "ForceGenericCPU" "no"
in section "Device"
That's what worked for me (Radeon 9600pro, Asus P4P800 w/ Intel 82865PE chipset).
HTH!
Regards,
Oliver
http://www2.ati.com/drivers/linux/readme0370.txt This section of the of the "readme0370.txt" is focused on RH 8, but the caveat is essentially true IMHO: "Remove the existing libGL installation and then install the new libGL with the ATI driver installation. For example: rpm -e --nodeps XFree86-Mesa-libGL-4.2.0-72 rpm -Uhv <ati_package_name>.rpm NOTES: (1) Ensure that no OpenGL program is running during installation (2) You need the "--nodeps" option because some screen savers, qt-3, and some parts of XFree86 might depend on the libGL presence. Installing the new libgl from the ATI package will restore the required libGL presence." - From what I have been able to gather, after battling with this for some time, is that the Mesa packages that provide "libGL.so" have a history of creating problems - namely that most programs will look to "libGL.so" to initialize 3D. Unfortunately if the drivers (which can be kludgy to say the least) don't establish a link in a proper way all programs will be naturally defaulted to MesaGLX - and this is completely software driven - hence the lack of true 3D HW accel. This is why I was curious about the output to: rpm -qa | grep mesa. my results are as follows: mesaglut-5.0.1-61 mesaglut-devel-5.0.1-61 mesa-5.0.1-61 However, it has been recommended to remove Mesa (specifically versions <= 4.x), Mesa 5.0 shouldn't be a problem - but I have noticed that it can still interfere. What worked for me is: Exit the gui, shift over to tty1, log in as root, then issue "init 3" or "telinit 3" rpm -Uhv fglrx-3.7.0-0.i586.rpm --replacepkgs rm /lib/modules/2.4.21-166-athlon/kernel/drivers/char/drm/fglrx.o rpm -Uhv km_fglrx-3.7.0-0.i586.rpm --replacepkgs NOTE: if you look at /usr/src/kernel-modules/fglrx and see that the old "fglrx.o" is still there try moving into that dir and then issuing "make -f Makefile.module clean", this will remove the old kernal driver modules. Now you want to go to /usr/src/kernel-modules/fglrx and issue (omit quotes) "make -f Makefile.module" "make -f Makefile.module install" then while still in init 3 issue "sax2 -r -m 0=fglrx -b /usr/X11R6/lib/sax/profile/firegl" Then open an edit (I use pico) pico /etc/X11/XF86Config add Load "dri" to Section "Module" Now, one can use fglrxconfig but that will point X to XF86Config-4 file rather than the XF89Config that is used presently - IMHO this adds unfavorably to the "kludge" factor. Then run ldconfig SuSEconfig You may reboot or do a startx/startx kdm I prefer to reboot simply because I've found that the card will initialize better and more cleanly. HTH, Curtis. - -- Spammers Beware: Tresspassers will be shot, survivors will be shot again! Warning: Individuals throwing objects at the crocodiles will be asked to retrieve them! If pro is the opposite of con, then the opposite of progress must be congress! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFANlUqN9r/ngHXpykRAv5cAJ4zF7zS4PNfJeOTgOZ8ec3kXKKbUgCg192q rkSxNBJSQKT9oeS3m+hdU3k= =QR3J -----END PGP SIGNATURE-----
participants (5)
-
Curtis Rey -
Ingo Strauch -
Nimer -
Oliver Baum -
Ralph Jones