openSuSE 10.2: Several graphics problems with ATI Radeon X1950 Prodriver

  • Thread starter Thread starter Eric
  • Start date Start date
E

Eric

Hi all,

i already checked several Linux NG's for this kind of problem but could
not find any working solutions. Also i tried a post within
alt.os.linux.suse without a reply. Maybe one of you knows this issues.

Fyi, i had a ATI Radeon 9800 Pro installed before without any problems.

Let me first explain the two problems i am facing

1) Sax2 does not recognize the graphics card and module, it starts in
Framebuffer mode which of course does not let me changes to the
graphics options for the ATI card, even if start with command 'sax2 -m
0=fglrx --sysconfig'

2) DRI module not loaded/working

I tried the manual installation of the kernel module from the sources,
which i downloaded from the ATI site and the packages provided
by SuSE. Also, i tried several xorg.conf versions including the default
configuration from SuSE installation and an aticonfig generated one.

Enclosed the system details:

Graphics: Sapphire ATI Radeon X1950 Pro (AGP)
CPU: AMD Athlon64 3000+ (2,4 GHz)
Chipset: NVIDIA nForce3

Linux:
localhost# uname -a
Linux localhost 2.6.18.8-0.1-default #1 SMP Fri Mar 2 13:51:59 UTC 2007
x86_64 x86_64 x86_64 GNU/Linux

localhost# rpm -qa | grep fglrx
x11-video-fglrx-8.28.8-2
ati-fglrx-kmp-default-8.28.8_2.6.16.21_0.8-2

localhost# lsmod | grep fgl
fglrx 639608 11

X-log extract:
<snip>
(II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0
(II) fglrx(0): detected X.org 7.1.-1.902
(==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
(**) fglrx(0): using built in AGPGART module: no
(**) fglrx(0): KernelModuleParm: "locked-userpages=0"
<snip>
(EE) fglrx(0): GART is not initialized, disabling DRI
(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): ********************************************* *
<snip>

localhost# fglrxinfo
Xlib: extension "XFree86-DRI" missing on display ":0.0".
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.1)


Did anyone of you experience these problems?
 
Eric said:
Hi all,

i already checked several Linux NG's for this kind of problem but could
not find any working solutions. Also i tried a post within
alt.os.linux.suse without a reply. Maybe one of you knows this issues.

Fyi, i had a ATI Radeon 9800 Pro installed before without any problems.

Let me first explain the two problems i am facing

1) Sax2 does not recognize the graphics card and module, it starts in
Framebuffer mode which of course does not let me changes to the
graphics options for the ATI card, even if start with command 'sax2 -m
0=fglrx --sysconfig'

2) DRI module not loaded/working

I tried the manual installation of the kernel module from the sources,
which i downloaded from the ATI site and the packages provided
by SuSE. Also, i tried several xorg.conf versions including the default
configuration from SuSE installation and an aticonfig generated one.

Enclosed the system details:

Graphics: Sapphire ATI Radeon X1950 Pro (AGP)
CPU: AMD Athlon64 3000+ (2,4 GHz)
Chipset: NVIDIA nForce3

Linux:
localhost# uname -a
Linux localhost 2.6.18.8-0.1-default #1 SMP Fri Mar 2 13:51:59 UTC 2007
x86_64 x86_64 x86_64 GNU/Linux

localhost# rpm -qa | grep fglrx
x11-video-fglrx-8.28.8-2
ati-fglrx-kmp-default-8.28.8_2.6.16.21_0.8-2

localhost# lsmod | grep fgl
fglrx 639608 11

X-log extract:
<snip>
(II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0
(II) fglrx(0): detected X.org 7.1.-1.902
(==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
(**) fglrx(0): using built in AGPGART module: no
(**) fglrx(0): KernelModuleParm: "locked-userpages=0"
<snip>
(EE) fglrx(0): GART is not initialized, disabling DRI
(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): ********************************************* *
<snip>

localhost# fglrxinfo
Xlib: extension "XFree86-DRI" missing on display ":0.0".
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.1)


Did anyone of you experience these problems?
Click to expand...

Eric,

Support for the X1950 Pro was not added to fglrx until the 8.32 driver. The
ATI Linux driver is now at version 8.34.8. The driver included with Suse
10.2 is significantly out-dated at 8.28.

Please download the latest ATI driver from the ATI/AMD website and follow
the included directions. Easiest way is to just run the installer from
within your X that is now using a standard VESA driver.

I bet you'll have much better results :)

Tony
 
Tony said:
Eric,

Support for the X1950 Pro was not added to fglrx until the 8.32 driver. The
ATI Linux driver is now at version 8.34.8. The driver included with Suse
10.2 is significantly out-dated at 8.28.

Please download the latest ATI driver from the ATI/AMD website and follow
the included directions. Easiest way is to just run the installer from
within your X that is now using a standard VESA driver.

I bet you'll have much better results :)

Tony
Click to expand...

Thanks a lot Tony,

i installed the driver by running the install binary, since the package
did not work.

it solved the DRI problem, but now i have other problems.

1) Sax2 issue still exists (starts in framebuffer mode) and wont come
back while getting the X window (came back before).

2) Switching to Command Line Mode (Ctrl+Alt+F2) is possible but
switching back to X mode (Ctrl+Alt+F7) ends up in a black screen

localhost# fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: Radeon X1950 Series
OpenGL version string: 2.0.6334 (8.34.8)

Eric
 
Eric said:
Thanks a lot Tony,

i installed the driver by running the install binary, since the package
did not work.

it solved the DRI problem, but now i have other problems.

1) Sax2 issue still exists (starts in framebuffer mode) and wont come
back while getting the X window (came back before).

2) Switching to Command Line Mode (Ctrl+Alt+F2) is possible but
switching back to X mode (Ctrl+Alt+F7) ends up in a black screen

localhost# fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: Radeon X1950 Series
OpenGL version string: 2.0.6334 (8.34.8)

Eric
Click to expand...

What do you mean "the package did not work"? Download
"ati-driver-installer-8.34.8-x86.x86_64.run", start up X using a standard
VESA driver, make sure "ati-driver-installer-8.34.8-x86.x86_64.run" has
execute permissions, so chmod +x it, execute it and follow the GUI wizard :)

Once you're done with the driver install, exit X. Then use the fglrx command
line utility (can't remember the filename) to modify your xorg.conf to the
point where X loads using fglrx with proper 3D acceleration. From that point
on all modifications to xorg.conf should be by hand. Do not try to use sax
to change your X config to use the fglrx driver; that will not work well. I
can email you my _working_ xorg.conf from Suse 10.1 with an X1900XTX and the
same driver you're trying to get working... if you want to use it/compare
it.

Again, sax2 is designed to be used with the Suse 10.x bundled
drivers/packages. Use the graphical sax from within X once you get it
working with fglrx. I'm not in front of a suse box to verify, but I think
sax2 uses a different xorg.conf when it starts up.

Tony
 
Hi Tony,

Thanks a lot for your support.
What do you mean "the package did not work"? Download
"ati-driver-installer-8.34.8-x86.x86_64.run", start up X using a standard
VESA driver, make sure "ati-driver-installer-8.34.8-x86.x86_64.run" has
execute permissions, so chmod +x it, execute it and follow the GUI wizard :)

Once you're done with the driver install, exit X. Then use the fglrx command
line utility (can't remember the filename) to modify your xorg.conf to the
point where X loads using fglrx with proper 3D acceleration. From that point
on all modifications to xorg.conf should be by hand. Do not try to use sax
to change your X config to use the fglrx driver; that will not work well. I
can email you my _working_ xorg.conf from Suse 10.1 with an X1900XTX and the
same driver you're trying to get working... if you want to use it/compare
it.
Click to expand...

That's exactly what i did. I meant with the package, the provided rpm
from the ATI side. So i went the way with the binary installation as you
described.
Again, sax2 is designed to be used with the Suse 10.x bundled
drivers/packages. Use the graphical sax from within X once you get it
working with fglrx. I'm not in front of a suse box to verify, but I think
sax2 uses a different xorg.conf when it starts up.
Click to expand...

Well, the 3D is now working, however as i said i now face the 2 problems
mentioned above. One of them is related to Sax which i wont use as you
recommended. It would be very great to be able to compare my xorg.conf
with yours.

Thanks and cheers,
Eric
 
Back
Top