Attention Fedora Core 3 Radeon users

[Mike A. Harris]

Does DRI actually work on Radeon for _anyone_ out there without 
crashing either immediately, or within some timeframe?

There are oodles of DRI related radeon bugs, and I'm just trying 
to get an idea if it actually works for anyone at all, so we can 
decide the best approach to resolving the issues reported so far.

Thanks in advance.



-- 
Mike A. Harris        ftp://people.redhat.com/mharris
OS Systems Engineer   -   X11 Developer   -   Red Hat

[Rui Miguel Silva Seabra]

On Wed, 2004-12-08 at 12:14 -0500, Mike A. Harris wrote:
>  Does DRI actually work on Radeon for _anyone_ out there without 
>  crashing either immediately, or within some timeframe? 
Hi Mike,

 It seems to work here (I've an updated system), is that timeframe
usually short? For how long, more or less?

From rom lspci:
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon IGP
330M/340M/350M

From rom glxinfo:
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes

[rms@roque ~]$ glxgears
1717 frames in 5.0 seconds = 343.400 FPS
1782 frames in 5.0 seconds = 356.400 FPS

So, it seems to work, although far from perfect.

>  There are oodles of DRI related radeon bugs, and I'm just trying
>
>  to get an idea if it actually works for anyone at all, so we can 
>  decide the best approach to resolving the issues reported so far. 
It works for me but I'm not a frequent user, some bzflag mostly but on
other machine with a better supported card (01:00.0 VGA compatible
controller: ATI Technologies Inc Radeon RV200 QW [Radeon 7500]).

On the Radeon IGP, bzflag has very weird colours on the text parts
(messaging, info, etc...).

Regards, Rui

[Rui Miguel Silva Seabra]

On Wed, 2004-12-08 at 17:42 +0000, Rui Miguel Seabra wrote:
>  On Wed, 2004-12-08 at 12:14 -0500, Mike A. Harris wrote:
>  > Does DRI actually work on Radeon for _anyone_ out there without 
>  > crashing either immediately, or within some timeframe? 
BTW, does recovering from ACPI state S3 failing (likely due to the
radeon IGP) count?

Rui

[James Kosin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Mike A. Harris wrote:

|Does DRI actually work on Radeon for _anyone_ out there without
|crashing either immediately, or within some timeframe?
|
|There are oodles of DRI related radeon bugs, and I'm just trying
|to get an idea if it actually works for anyone at all, so we can
|decide the best approach to resolving the issues reported so far.
|
|Thanks in advance.
|
|
|
Hmmm.....

I forgot about that.  I'll have to try that before starting X again,
and see if that does the trick.
My setup gets loaded and the graphics appear on the screen to start
the login; only the whole system is FROZEN by then.
I'm running an ATI Radeon VIVO 64MB card.

Thanks,
James Kosin
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>  
> iD8DBQFBt0TlkNLDmnu1kSkRAvuUAJ0b6giqUunXcuPyoMqm9TMvZiDA+wCeLuvB
> y/ldFc4LdrNGrX9bqojFGlI=
> =fUZT
> -----END PGP SIGNATURE-----

[Robert]

Mike A. Harris wrote:
>  Does DRI actually work on Radeon for _anyone_ out there without 
>  crashing either immediately, or within some timeframe?
>  
>  There are oodles of DRI related radeon bugs, and I'm just trying 
>  to get an idea if it actually works for anyone at all, so we can 
>  decide the best approach to resolving the issues reported so far.
>  
>  Thanks in advance.
>  
>  
>   
There have been a few times that I've had to quit back to runlevel 3 to 
clear some goofy hung-up situation. I can't remember that NOT being 
because of the sound stuff getting tangled up.
It generally works swell. I sometimes watch a movie on DVD using xine, 
switching desktops to read email during boring parts of the movie.



[root@mavis ~]# grep -A 10 -B 10 dri /etc/X11/xorg.conf
EndSection

Section "Module"
         Load  "dbe"
         Load  "extmod"
         Load  "fbdevhw"
         Load  "glx"
         Load  "record"
         Load  "freetype"
         Load  "type1"
         Load  "dri"
EndSection

Section "InputDevice"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#       Option  "Xleds"         "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
#       Option  "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
[root@mavis ~]#

[root@mavis ~]# lspci
00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) 
(rev c1)
00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1)
00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:05.0 Multimedia audio controller: nVidia Corporation nForce 
MultiMedia audio[Via VT82C686B] (rev a2)
00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 
Audio Controler (MCP) (rev a1)
00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3)
00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
00:0d.0 FireWire (IEEE 1394): nVidia Corporation nForce2 FireWire (IEEE 
1394) Controller (rev a3)
00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
01:06.0 PCI bridge: Digital Equipment Corporation DECchip 21152 (rev 03)
01:07.0 SCSI storage controller: Adaptec AHA-2940/2940W / AIC-7871
02:04.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] 
(rev 05)
02:05.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] 
(rev 05)
03:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 If 
[Radeon9000] (rev 01)
03:00.1 Display controller: ATI Technologies Inc Radeon RV250 [Radeon 
9000] (Secondary) (rev 01)
[root@mavis ~]#
[root@mavis ~]# rpm -qa | grep xorg
xorg-x11-sdk-6.8.1-12
fonts-xorg-ISO8859-15-75dpi-6.8.1-1
fonts-xorg-syriac-6.8.1-1
xorg-x11-Mesa-libGLU-6.8.1-12
xorg-x11-deprecated-libs-devel-6.8.1-12
fonts-xorg-ISO8859-9-100dpi-6.8.1-1
xorg-x11-libs-6.8.1-12
xorg-x11-xauth-6.8.1-12
xorg-x11-deprecated-libs-6.8.1-12
fonts-xorg-truetype-6.8.1-1
xorg-x11-Xdmx-6.8.1-12
xorg-x11-Mesa-libGL-6.8.1-12
xorg-x11-font-utils-6.8.1-12
fonts-xorg-75dpi-6.8.1-1
xorg-x11-Xnest-6.8.1-12
fonts-xorg-ISO8859-15-100dpi-6.8.1-1
fonts-xorg-100dpi-6.8.1-1
xorg-x11-tools-6.8.1-12
xorg-x11-doc-6.8.1-12
xorg-x11-devel-6.8.1-12
fonts-xorg-ISO8859-14-75dpi-6.8.1-1
xorg-x11-xfs-6.8.1-12
[root@mavis ~]# rpm -qa | grep xorg
xorg-x11-sdk-6.8.1-12
fonts-xorg-ISO8859-15-75dpi-6.8.1-1
fonts-xorg-syriac-6.8.1-1
xorg-x11-Mesa-libGLU-6.8.1-12
xorg-x11-deprecated-libs-devel-6.8.1-12
fonts-xorg-ISO8859-9-100dpi-6.8.1-1
xorg-x11-libs-6.8.1-12
xorg-x11-xauth-6.8.1-12
xorg-x11-deprecated-libs-6.8.1-12
fonts-xorg-truetype-6.8.1-1
xorg-x11-Xdmx-6.8.1-12
xorg-x11-Mesa-libGL-6.8.1-12
xorg-x11-font-utils-6.8.1-12
fonts-xorg-75dpi-6.8.1-1
xorg-x11-Xnest-6.8.1-12
fonts-xorg-ISO8859-15-100dpi-6.8.1-1
fonts-xorg-100dpi-6.8.1-1
xorg-x11-tools-6.8.1-12
xorg-x11-doc-6.8.1-12
xorg-x11-devel-6.8.1-12
fonts-xorg-ISO8859-14-75dpi-6.8.1-1
xorg-x11-xfs-6.8.1-12
xorg-x11-xdm-6.8.1-12
fonts-xorg-ISO8859-2-100dpi-6.8.1-1
fonts-xorg-base-6.8.1-1
xorg-x11-Xvfb-6.8.1-12
fonts-xorg-ISO8859-9-75dpi-6.8.1-1
fonts-xorg-cyrillic-6.8.1-1
fonts-xorg-ISO8859-14-100dpi-6.8.1-1
xorg-x11-6.8.1-12
xorg-x11-twm-6.8.1-12
fonts-xorg-ISO8859-2-75dpi-6.8.1-1
[root@mavis ~]#

[rj@mavis ~]$ glxgears
5164 frames in 5.0 seconds = 1032.800 FPS
6095 frames in 5.0 seconds = 1219.000 FPS
6097 frames in 5.0 seconds = 1219.400 FPS
6067 frames in 5.0 seconds = 1213.400 FPS
[rj@mavis ~]$


You can have dinner tonight, confident that despite a few bugs, y'all 
did a bunchastuff right!

[Markku Kolkka]

Mike A. Harris kirjoitti viestissään (lähetysaika keskiviikko, 8. 
joulukuuta 2004 19:14):
>  Does DRI actually work on Radeon for _anyone_ out there
>  without crashing either immediately, or within some timeframe? 
Yes, I haven't seen any crashes with my Sapphire Radeon 9000.
(01:00.0 VGA compatible controller: ATI Technologies Inc Radeon 
RV250 If [Radeon9000] (rev 01))

[Schlaegel]

Mike A. Harris wrote:

> Does DRI actually work on Radeon for _anyone_ out there without 
> crashing either immediately, or within some timeframe?
>   
>  
I have a Radeon 9100 IGP.
glxinfo:

>  OpenGL renderer string: Mesa DRI R200 20030328 AGP 4x x86/MMX/SSE2
> NO-TCL 
The ATI binary drivers do not support this chipset, so I am very happy
that FC3 does.
I can run all of the GL xscreensaver hacks with no problems.
I can run bzflag with no problem.

When I run neverball the in the high texture mode the text disappears,
but there still is never any crash.

[Satish Balay]

On Wed, 8 Dec 2004, Mike A. Harris wrote:

01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 Lf [Radeon Mobility
9000 M9] (rev 02)

Don't use DRI much (however its always enabled). Recently I tred
BZFlag - it crashed on me once. Don't remember all the details - I
might have tried init3; init 5 - at which point glxgears was extremely
slow.

Satish

[Bruno Wolff III]

On Wed, Dec 08, 2004 at 12:14:32 -0500,
  "Mike A. Harris" <mharris(a)redhat.com&gt; wrote:
>  Does DRI actually work on Radeon for _anyone_ out there without 
>  crashing either immediately, or within some timeframe?
>  
>  There are oodles of DRI related radeon bugs, and I'm just trying 
>  to get an idea if it actually works for anyone at all, so we can 
>  decide the best approach to resolving the issues reported so far. 
I can play NWN using a 9200 and FC2. I eventually (on the order of an
hour) get lock ups. Usually restarting X will fix the problem, but
not always. (In the not always case, I get a normal desktop when I
log back in, but NWN crashes immediately when I try to start it
back up.)

This isn't a big deal for solo play, but really messes up team play.
So I would like to see this fixed and would be willing to try some
stuff out to help isolate problems.

[Summer Brooks]

On Wed, 8 Dec 2004, Mike A. Harris wrote:

>  Does DRI actually work on Radeon for _anyone_ out there without
>  crashing either immediately, or within some timeframe?
>
>  There are oodles of DRI related radeon bugs, and I'm just trying
>  to get an idea if it actually works for anyone at all, so we can
>  decide the best approach to resolving the issues reported so far.
>
>  Thanks in advance. 
Are you only interested in Radeon DRI bugs, or any particular
Radeon (and nVidia) bugs?

I ran into what seems to be an FC3 AGP "issue"...   I say AGP issue,
only because that's the one thing the nVidia GeForce 440 MX and the
Radeon 9200SE I tried that locked up my system have in common.

So far, the Radeon 9200SE PCI card I'm trying has not as yet locked
up my desktop, but it did lock up my Viewsonic VX900-2 LCD monitor
when switching from text mode during the boot sequence to graphical
login, just like the other two cards did, so I still don't know what's
causing that.

Frozen power buttons cannot be good for the monitor, so if it's not
an AGP/LCD issue, I'm stumped as to what it may be.

I've also reinstalled the sharutils and metamail rpms (had to use
the RH9 ones, because the src rpms I found barfed spectacularly).
So I'm currently running FC3, with exmh just like I like it, and
so far, so good.

-------------------------------------------------------------------------
Summer Brooks, WildHorse.com Staff      I will choose a Path that's clear
brooksj at wildhorse dot com		I will choose Free Will

[Paul R. Ganci]

Mike A. Harris wrote:

> Does DRI actually work on Radeon for _anyone_ out there without 
> crashing either immediately, or within some timeframe?
>  
It is a mixed bag on my systems. On a system with an ASUS K7V 
motherboard with 768MB RAM, VIA VT8371 chipset and a Radeon 8500LE video 
adapter:

ganci@mcduff> glxgears
7667 frames in 5.0 seconds = 1533.400 FPS
7569 frames in 5.0 seconds = 1513.800 FPS
8524 frames in 5.0 seconds = 1704.800 FPS

However on a system with a Shuttle AI61 mainboard with 512MB RAM, AMD 
751 & 756 chipsets and a Radeon 8500LE video adapter the system will 
lock up immediately if DRI is on and I start X. Requires a hard reset.

-- 
Paul (ganci(a)nurdog.com)

[Jakub Jelinek]

On Wed, Dec 08, 2004 at 12:14:32PM -0500, Mike A. Harris wrote:
>  Does DRI actually work on Radeon for _anyone_ out there without 
>  crashing either immediately, or within some timeframe?
>  
>  There are oodles of DRI related radeon bugs, and I'm just trying 
>  to get an idea if it actually works for anyone at all, so we can 
>  decide the best approach to resolving the issues reported so far. 
Works just fine here.
glxgears:
6595 frames in 5.0 seconds = 1319.000 FPS
6595 frames in 5.0 seconds = 1319.000 FPS
6585 frames in 5.0 seconds = 1317.000 FPS
tuxracer, bzflag both work fast and without any issues.

01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV200 QW [Radeon 7500]
(prog-if 00 [VGA])
        Subsystem: C.P. Technology Co. Ltd RV200 QW [Radeon 7500 Evil Master Multi Display
Edition]
on x86-64.

	Jakub

[Jeff Epler]

I'm using
	OpenGL renderer string: Mesa DRI R200 20030328 AGP 4x x86/MMX+/SSE2 TCL
	01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 Lf
		[Radeon Mobility 9000 M9] (rev 01)
It's an hp pavilion zt3000-series notebook.

OpenGL apps work, but there are occasional problems with images in other
applications (eg firefox) being corrupted while an opengl application (with
vertex arrays and display lists, no textures) is running.

Jeff

[Bruno Wolff III]

On Wed, Dec 08, 2004 at 12:14:32 -0500,
  "Mike A. Harris" <mharris(a)redhat.com&gt; wrote:
>  Does DRI actually work on Radeon for _anyone_ out there without 
>  crashing either immediately, or within some timeframe?
>  
>  There are oodles of DRI related radeon bugs, and I'm just trying 
>  to get an idea if it actually works for anyone at all, so we can 
>  decide the best approach to resolving the issues reported so far. 
Are you guys going to put out xorg 6.8.2 for FC3? I don't think the
development rpms are going to work on FC3 because glibc is different.
However, there are supposed to be some radeon driver changes and
I would like to see if it fixes the problems I have been having
running programs that use 3d.

[Mike A. Harris]

On Sun, 13 Feb 2005, Bruno Wolff III wrote:

>   "Mike A. Harris" <mharris(a)redhat.com&gt; wrote:
> > Does DRI actually work on Radeon for _anyone_ out there without 
> > crashing either immediately, or within some timeframe?
> > 
> > There are oodles of DRI related radeon bugs, and I'm just trying 
> > to get an idea if it actually works for anyone at all, so we can 
> > decide the best approach to resolving the issues reported so far.
>
> Are you guys going to put out xorg 6.8.2 for FC3? 
Yes.  For those who haven't followed development discussions, 
etc. too closely, we've planned all along to keep FC3 updated 
with 6.8.x updates as they are all intended to be stable bugfix 
updates with no new features.

Having said that, people will now be wondering "when".  There is 
no specific date or time determined yet, however I am going to 
build rpms for FC3 and push them to "testing" first sometime 
soon, and after a week or two push them to "updates" if no major 
catastrophic problems (relative to my own viewpoint of course 
<grin>) are reported.  ;o)

People wanting to test 6.8.2 with official RHAT rpms, should add 
FC3 "testing" to their yum configuration, and just keep checking 
until it is available.  Should be really soon, but I wont provide 
any specific date because I don't want to be tied to any specific 
date.
</blatant honesty>

;o)

Summary:  Yes, soon.


P.S.  I am not subscribed to fedora-list, so wont see anyone's 
replies.



-- 
Mike A. Harris, Systems Engineer - X11 Development team, Red Hat Canada, Ltd.

IT executives rate Red Hat #1 for value:  http://www.redhat.com/promo/vendor