LWN.net Logo

The first ATI r5xx/6xx X11 driver release

From:  Matthias Hopf <mhopf-AT-suse.de>
To:  xorg-announce-AT-lists.freedesktop.org, xorg-AT-lists.freedesktop.org
Subject:  [ANNOUNCE] xf86-video-radeonhd 1.0.0 - INITIAL RELEASE
Date:  Fri, 30 Nov 2007 02:18:06 +0100
Message-ID:  <20071130011806.GA7349@suse.de>
Archive-link:  Article, Thread

This is the first release of the xf86-video-radeonhd driver.

radeonhd is the X.org X11 driver for AMD GPG (ATI) r5xx/r6xx chipsets.
Main development is driven by Novell at the time of writing, in close
relationship to AMD which provides free documentation for the chipsets.

Note the wiki on http://wiki.x.org/wiki/radeonhd


Version 1.0.0 has

  - Full modesetting driver, capable of driving multiple monitors.
  - Support for VGA, DVI, DMS-59, and laptop panels.
  - Support for monitor hotplug detection, DDC, and dynamic reconfiguration.
  - Full RandR 1.2 compatibility.
  - AtomBIOS support for initialization, data tables, etc.
  - Early RandR 1.3 property support (subject to change).
  - Hardware cursor support.
  - No 2D & 3D acceleration, no XVideo yet. No TV, Component, and HDMI yet.



http://xorg.freedesktop.org/releases/individual/driver/xf...
MD5:  588e5fe6de45d217a658a3ce62e9254f  xf86-video-radeonhd-1.0.0.tar.gz
SHA1: d78cd3a5d0444916a5365ee5ad53dcd979411a3b  xf86-video-radeonhd-1.0.0.tar.gz

http://xorg.freedesktop.org/releases/individual/driver/xf...
MD5:  ea2832c84ec014bed55dcdd8baad06bc  xf86-video-radeonhd-1.0.0.tar.bz2
SHA1: 84092b5df1e4dbf7cd69006f3e545c293e80873c  xf86-video-radeonhd-1.0.0.tar.bz2



Matthias

-- 
Matthias Hopf <mhopf@suse.de>      __        __   __
Maxfeldstr. 5 / 90409 Nuernberg   (_   | |  (_   |__          mat@mshopf.de
Phone +49-911-74053-715           __)  |_|  __)  |__  R & D   www.mshopf.de

_______________________________________________
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


(Log in to post comments)

The first ATI r5xx/6xx X11 driver release

Posted Dec 1, 2007 17:21 UTC (Sat) by ajross (subscriber, #4563) [Link]

I'm confused.  How can you have DVI output working and yet not have HDMI support finished?
They're the same signal...  Are they talking about the HDMI audio device that some ATI cards
have?

The first ATI r5xx/6xx X11 driver release

Posted Dec 1, 2007 19:15 UTC (Sat) by Ross (subscriber, #4065) [Link]

I'm not really sure what they mean, but I think HDMI is a superset of DVI which adds DRM (HDCP
is mandatory, not optional like in DVI), and increases the maximum bandwidth (allowing more
bits per color channel).  Also the audio channels, as you say, and a different connector.

The first ATI r5xx/6xx X11 driver release

Posted Dec 1, 2007 20:19 UTC (Sat) by jwb (guest, #15467) [Link]

The funny thing about HDMI is that they "add bandwidth" by pure committee fiat.  They didn't
actually change anything about the cable, the connector, or the signalling that would actually
result in more capacity.  They did it again with the most recent revision of HDMI 1.3, which
increases the symbol rate from 165MHz to 340MHz by crossing out "165" and writing "340" over
it.

With that kind of process we should have 100-gigabit ethernet in no time ;)

Higher performance through revision of standards documents

Posted Dec 3, 2007 2:28 UTC (Mon) by tialaramex (subscriber, #21167) [Link]

That's essentially the process by which we got GigE on copper.

What's the difference between a Cat5 cable (suitable for 100baseT) and a Cat5e cable (suitable
for 1000baseT) ?

The Cat5e cable says "Cat5e" on it, which means it was tested to the newer standard. Did
anyone actually make cables that wouldn't have tested to the newer standard? Theory says
"Maybe". Practical experience says "Nope". They're just UTP cables, made from ordinary copper
wire. It's just not that hard when you're making thousands of kilometers of the stuff.

Obviously a process like that can't continue forever, 100 Gigabit Ethernet over Cat5 cable
isn't likely to work. But Ethernet and HDMI aren't by any means the only examples. USB 2.0
relies on the engineering choices made back in USB 1.0 to assure customers that their cables
will Just Work™ at the higher speed, and sure enough they do.

Higher performance through revision of standards documents

Posted Dec 3, 2007 3:06 UTC (Mon) by jwb (guest, #15467) [Link]

But the gigabit ethernet committee started with the requirement of achieving that speed on
existing installed wiring, so they invented a wholly new signalling scheme to do so.  They
didn't just overclock fast ethernet and call it a day.  Gigabit ethernet barely even resembles
fast ethernet at the electrical level.

Just for starters, gigabit ethernet requires four pairs while fast ethernet requires two.
Gigabit uses five signal levels while fast ethernet uses three.  An so forth.

First free driver?

Posted Dec 1, 2007 17:26 UTC (Sat) by arjan (subscriber, #36785) [Link]

I think LWN missummarized the announcement... it's the first release of this driver; it's of
course NOT the first driver for this hardware; one can argue it's the third (after the normal
ati and then the avivo drivers).

Dave Airlie and co have the same features... and more in the "other", full driver already
since some time, including various pieces of acceleration:

http://airlied.livejournal.com/53129.html

Plenty of work ahead

Posted Dec 1, 2007 18:44 UTC (Sat) by muwlgr (guest, #35359) [Link]

To compete even with Intel driver, in terms of overall usability.
And a little more work to get in line witn NVidia closed-source offer.
Too early to announce about its existence, I think :>

Plenty of work ahead

Posted Dec 1, 2007 23:51 UTC (Sat) by leoc (subscriber, #39773) [Link]

I don't know, it sounds about equally as capable as the open source intel driver for my X3100
based Thinkpad T61.  The 2D performance is terrible and running any OpenGL applications
immediately freezes the entire computer.

Plenty of work ahead

Posted Dec 2, 2007 0:24 UTC (Sun) by drag (subscriber, #31333) [Link]

What version of drivers are you using?

Mine is stable with acceptable 3D support and good 2D acceleration. It also suspends to ram
several times a day and this has worked better then my old Ibook.. with either OS X or Linux
on it.  Compiz-fusion works well also, the only major problem is that EXA support isn't fast
enough for large videos with 32bit graphics, so I run 16bit. Oh and OpenGL applications still
are ugly when running on compiz.. but their performance isn't affected in a noticable way.

That and it's xrandr support allows me to hotplug external monitors and configure X to use
them on the fly, which is a new experiance for with with open source drivers.

BTW, this is with Debian Unstable/testing on a Dell 1420n.

Plenty of work ahead

Posted Dec 2, 2007 0:31 UTC (Sun) by jwb (guest, #15467) [Link]

Whatever they shipped in Gutsy still can't render anything worth a damn with OpenGL.  Even
something pedestrian like Google Earth looks like junk on the GMA X3100.

I am fairly upset that I bought this Intel graphics chip 14 months ago on the strength of the
idea that a GPL driver would be a good thing.  In practice, the lack of public documentation
means that the GPL driver is held hostage to the whims of Keith Packard, and it seems that the
things Keith is interested in working on do not include correct output.

I give him props for the randr 1.2 stuff, but even that isn't particularly hot in practice.
With whatever version is in Ubuntu Gutsy, rotating my display locks up the hardware.

Plenty of work ahead

Posted Dec 2, 2007 2:55 UTC (Sun) by dberkholz (subscriber, #23346) [Link]

Sounds like you're held to the whims of Ubuntu, then, since you haven't tried the latest
driver to see whether your problems are fixed. Have you reported your problems on a bug?

Plenty of work ahead

Posted Dec 2, 2007 3:09 UTC (Sun) by jwb (guest, #15467) [Link]

True, to an extent, and bug reports are mostly ignored if you are not using the git head
revision of the driver, xorg, and mesa.  That's a common method that open source developers
use to pass the buck back to the bug reporter, but that's a subject for another post.

bug reports in open source projects

Posted Dec 3, 2007 10:49 UTC (Mon) by DonDiego (subscriber, #24141) [Link]

I really cannot speak for x.org, but given the low signal to noise ratio of bug reports in
general I must say I mostly ignore bug reports that are not against Subversion HEAD as well.
Spend some time tracing a bug report only to find out that it's fixed already when I have about
100 things on my ToDo list and only time for about 5?  Not to mention that 99 of those things
are more fun than validating bug reports?  No, I really cannot be bothered to throw away my
unpaid free time like that ...

Plenty of work ahead

Posted Dec 3, 2007 15:01 UTC (Mon) by alankila (subscriber, #47141) [Link]

Also remember that if you do not have the HEAD revision of the software compiled, then you
can't even test any fixes. So you not only do not know for sure whether the bug still exists,
you also can't tell whether its fixed by any changes made.

Actually it's possible

Posted Dec 3, 2007 15:48 UTC (Mon) by khim (subscriber, #9252) [Link]

Someone must do the following work:
1. Compile driver with some fixes just for you.
2. Package it for particular distribution - usually including distribution-specific patches
3. Send this binary to you and explain how to use it
4. Repeat the process starting from 1.
WAAAY to much work to do this for free. There are companies which will offer this level of support - but usually it's quite expensive. You should pay one way or another: either by buying expensive support contract or wasting sizable amount of time playing with HEAD drivers...

It's still better then situation in Windows world where you can only submit bugreport and hope that someone sometime will read it and you'll get your fix half-year later...

Plenty of work ahead

Posted Dec 3, 2007 15:35 UTC (Mon) by jond (subscriber, #37669) [Link]

Running HEAD seems to me to be a fair way for a developer to ensure that the reporter is
willing to invest at least a little bit of time towards diagnosing the problem and not just
fire-and-forget bug reporting, which is not really of use to anyone.

Plenty of work ahead

Posted Dec 3, 2007 18:08 UTC (Mon) by jwb (guest, #15467) [Link]

Building the tip of mesa and xorg is a major undertaking which is likely to break every
package on any given system.  Nevermind the minor fact that frequently the tip is in an
unbuildable or incompatible state.

For my own code, I follow the policy of taking a bug report seriously unless I have reason to
believe that it has been fixed in a newer revision.

I believe there was a long and thoughtful post on linux-kernel regarding this very issue
recently, where the author (a major kernel developer) concluded that it's counterproductive to
insist on testing with latest-test-rc-mm.

Plenty of work ahead

Posted Dec 3, 2007 19:57 UTC (Mon) by drag (subscriber, #31333) [Link]

Stable kernel interfaces be damned.

Both the X.org Intel drivers and DRI driver and libraries can be compiled out-of-tree and be
usable.

I've done that before when trying out different features that are only avialable via cvs.
(like texture/memory management features for the 915tex driver). Especially with the DRI
libraries. Using LD_PRELOAD tricks it's very possible to change between 3D driver versions
while running a single X session. 

There is almost no need to ever have to overwrite anything provided by your distribution. The
whole X server can be compiled seperately from distro-provided stuff if you like.  If the CVS
breaks everything then just go back to what is provided by your distribution. 

Worst case is that you have to compile a custom kernel to take advantage of some features
because of patches to DRM or AGPGART stuff. 

Soo... If you actually care about trying out patches and filing usefull bug reports then there
is nothing that is stopping you. Especially about 3D drivers.

Remember almost all of it, except for the DRM or AGP stuff, is userspace. Not much at all
depends in any way on the kernel (unlike your proprietary drivers) your using and you can use
different LD tricks and chroots to run any of it like any other application.


And remember now that X is now _modular_. The drivers themselves can be compiled seperately
from X. If your using a relatively recent version of X you can try out the latest 2D Intel
driver by just copying over the existing intel_drv.so file! If your worried about breakage
then just keep a backup to copy back.



This is a little out of date:
http://dri.freedesktop.org/wiki/NormalUserBuild

For example a most of the stuff has moved away from CVS to Git, but for the most part it still
applies. This tells you how to compile and run latest versions of Mesa libs, and DRI without
_EVER_EVEN_BECOMING_ROOT_.

Have you never had more then one version of a program or libraries installed on your computer
before?!


If your using Gutsy and the Intel stuff is crapping out on you then bitch to Ubuntu for
shipping something broken. On my Debian Unstable/Testing is is pretty stable, not perfect, but
it works well. A freind at work has a X3000 chipset and is using Fedora Core 8 and it runs
Compiz pretty well except for the 2D and 3D overlay problem/ugliness.

Plenty of work ahead

Posted Dec 3, 2007 19:26 UTC (Mon) by dvdeug (subscriber, #10998) [Link]

I've had the feeling with way too many projects that they're more willing to make cute new
features rather than actually fixing the bugs that are giving me trouble. File-and-forget bug
handling or making unreasonable demands on me just accentuate that feeling. Demanding that I
exchange a mostly-working program for a program that may not even compile or work remotely
correctly is absurd for anyone who actually has to use the program in question on the system
in question.

I see the reasoning behind it, but OSS already has a preception, often true, of not worrying
about the hard unfun stuff that users need. Stating that you're going to ignore bug reports
unless they follow a development version just stress that feeling. 

Plenty of work ahead

Posted Dec 4, 2007 17:05 UTC (Tue) by jsbarnes (guest, #4096) [Link]

Have you tried filing bugs for the issues you see in Gutsy?  We worked a 
lot with the Ubuntu team on the 2.2 driver release, fixing many Ubuntu 
reported problems in the process.  And we try to be responsive to bug 
reports in general (and I generally don't ask people to test newer 
versions unless I have reason to think the bug is fixed there and I want 
confirmation).

Plenty of work ahead

Posted Dec 2, 2007 2:59 UTC (Sun) by k8to (subscriber, #15413) [Link]

I can't really speak as to any hostage holding, but I can say that the intel 3d support has
not really impressed me, under Linux.  The performance under windows is notably better,
delivering framerates in 2-3 times better range, without video glitches, and while the
stability of Windows has its ups and downs, the Linux OpenGL experience with my GMA X3000
usually locks the machine solid.

The experience of this driver has actually driven me to use Windows again to get certain work
done after around ten years of Linux as my sole working platform.

I suspect there is simply not enough manpower in the arena of the video drivers on Linux.

Plenty of work ahead

Posted Dec 2, 2007 17:32 UTC (Sun) by mmarq (guest, #2332) [Link]

"" The experience of this driver has actually driven me to use Windows again to get certain
work
done after around ten years of Linux as my sole working platform.

I suspect there is simply not enough manpower in the arena of the video drivers on Linux. ""

Nevertheless i still use Linux... try the proprietary offerings... I've being "crying to the
winds" in this forum for more than half a decade!!...

In my opinion its not manpower its the *will* and a workable method and organization(
concentrated efforts, because reverse engineering would be still in the menu ) to obviate the
lack of a long in time stable API or ABI of the driver model.

Worst that can happen its the various distros driving different implementations as a marketing
differentiation point!... akin to our favorite "Bill" selling *rope*, openly and without
shame, at the entrances  of RH, Novell, Canonical... LF... headquarters ( rope for people to
hang themselfs )...  

( for crying out loud why isn't DKMS official tree code ?... or am i being out for too long
?!) 

If the *will* is there, than it only misses a good development method and organization for it
to take off good... because the hardware manufactores wont do it "really" for free for OSS( no
matter what they claim)... for them is just a matter of dumping development, maintenance and
support costs to the community.    

If the *will* is there and the method and organization, then 'we' can talk about Linux desktop
really taking off and spreading like wild fire, otherwise, we better talk about santa claus!

Plenty of work ahead

Posted Dec 3, 2007 18:34 UTC (Mon) by elanthis (guest, #6227) [Link]

"for crying out loud why isn't DKMS official tree code"

Because upstream kernel developers think that out-of-tree kernel code is disgusting and awful
and evil, and DKMS is unnecessary for in-tree code.

They don't mind the idea that, in order to use new hardware or use a newer driver, you need to
upgrade your entire fucking kernel, along with without user-space libraries and daemons and
tools occassionally get broken by those updates (hal, udev, and anything that uses the fluid
sysfs paths).

Not sure it's really worth it to whine about the kernel like that, though.  It's the same deal
for a Linux distribution as a whole.  Want a newer version of FooApp?  Upgrade your whole
fucking OS to the next release, and then you also get all those undesired changes to your
desktop and other apps along with all the new bugs and breakage you didn't have to put up with
before.

Linux (both the kernel and the family of OSes) has always been based on one of two models: the
"compile shit directly from version control on a daily basis" model and the "you get a fixed
set of software snapshots in your OS appliance" model.  If you dislike both of those models,
use a different OS.

Plenty of work ahead

Posted Dec 3, 2007 20:39 UTC (Mon) by drag (subscriber, #31333) [Link]

Plus DKMS isn't a big deal when it comes to open source drivers. 

The only thing that matters in terms of kernel would be things like DRM or AGPGART stuff. DRI
and Xorg XAA/EXA drivers have no dependancy on the kernel beyond that. 

It's fairly trivial to manage multiple versions of the Intel driver or have compiled a Mesa
tree and DRI stuff outside your distribution-provided stuff.

It's even possible to switch between multiple versions of DRI drivers within the same X
session. It just requires LD_LIBRARY_PATH tricks to point applications at a different path. 

for example:
export LD_LIBRARY_PATH=/path/to/xc/xc/exports/lib:$LD_LIBRARY_PATH
export LIBGL_DRIVERS_DIR=/path/to/Mesa/lib

It's not that hard at all.

With the 2D drivers you just copy over the *_drv.so file, and keep backups of the originals so
you can go back if it breaks something. 

Occasionally you'll run into kernel-level dependancies for a new texture memory management
change or something like that. But for the most part they can be compiled into modules.

Plenty of work ahead

Posted Dec 15, 2007 19:09 UTC (Sat) by anton (guest, #25547) [Link]

[...] intel 3d support has not really impressed me, under Linux. The performance under windows is notably better, delivering framerates in 2-3 times better range [...]
For various Radeon cards running the r300 driver I have seen about a factor of 2 slowdown on UT2004 compared to Windows.

Plenty of work ahead

Posted Dec 2, 2007 5:21 UTC (Sun) by leoc (subscriber, #39773) [Link]

My machine is running Fedora 7, and I manually installed the drivers from here a couple of weeks ago. I pulled the latest version (at the time) from their repository. When I bought this machine I followed the current conventional wisdom and went with an all-Intel model (intel video, intel audio, intel wireless, etc) because in theory everything would be supported by open source drivers. Unfortunately since it is such a new machine, the different bits are only just starting to get supported properly. I guess when I get a chance I will try redoing the install with a newer drop.

Plenty of work ahead

Posted Dec 2, 2007 17:04 UTC (Sun) by beoba (guest, #16942) [Link]

One of the primary tenets of open source is "release early, release often". Benefits include
more interest from potential developers and more bugfixes from early-adopter usage.

Plenty of work ahead

Posted Dec 2, 2007 17:47 UTC (Sun) by mmarq (guest, #2332) [Link]

"" One of the primary tenets of open source is "release early, release often". ""

Just an inconsequential 'cliche'. Nothing surpasses experience and the *will* to do it, and or
to do it right and good, even if its not often nor earlier.

Plenty of work ahead

Posted Dec 2, 2007 18:45 UTC (Sun) by dlang (✭ supporter ✭, #313) [Link]

you are correct that nothing replaces a will to work on a project, but the parent was
responding to the complaint that this wasn't a perfect driver yet, and I agree with him that
the principal of 'release early and release often' is appropriate. they have a driver that is
useable (but not finished) and they are releasing it so that people can find bugs in it and
tinker with it themselves.

Plenty of work ahead

Posted Dec 2, 2007 22:41 UTC (Sun) by mmarq (guest, #2332) [Link]

Absolutely correct... but it doesn't invalidate that we can get 3 or 4 projects doing the same
thing *early and often*, none gets to be *god enough* because of the waiting for input and the
lack of "will" for concentrated efforts... to the point that 3 different experiences gets to 3
different code repositorys with little chance of code intermingling... being the funny or
tragic fact that one is better at some features than the others, and vice versa, and the sum
of the three should had made a considerable better product while people are stucked with
buying $300 pieces for only using $100.    

Plenty of work ahead

Posted Dec 3, 2007 0:52 UTC (Mon) by dlang (✭ supporter ✭, #313) [Link]

but if they all wait until they are 'finished' to release anything the result is none of them
every show up, there's no chance for them to pickup features from each other, and no chance
for new developers to build off of what's been done instead of starting from scratch.

I agree that there needs to be a will to keep working, but in this case there's no indication
of any lack of will, so it seems like you are spouting discouragement when what needs to
happen in to encourage them to keep going (by pure praise, bug reports, beta testing, or
coding), not fussing that the driver they released doesn't have all the features yet.

The first ATI r5xx/6xx X11 driver release

Posted Dec 1, 2007 22:58 UTC (Sat) by louie (subscriber, #3285) [Link]

I would love a 'cranky editor reviews video cards' article :) I'd like to upgrade the video in
my current desktop box (very, very old card) but have had a hard time figuring out what (if
anything) will get me decent dual-head performance with a Free driver. (I don't care about 3D,
but I imagine others care about that too.)

Yes! A grumpy editor video card review please!

Posted Dec 2, 2007 2:07 UTC (Sun) by xuxa (guest, #29601) [Link]

I second that emotion!  I'd love to see a comparison of video cards that run well will free
software (no closed-source drivers)...

Me too.

Posted Dec 2, 2007 6:08 UTC (Sun) by undefined (guest, #40876) [Link]

i third that, though feel free to disregard my opinion as i'm not a subscriber (but i don't
block the non-flash ads and i try to post "polite, respectful, and informative" comments ;-).

on my desktop i'm running an ati 9250 because it (in order of personal importance):
1. is a foss driver
2. supports dual head (separate screens, not xinerama, as the monitors are different
resolutions and the secondary one always shows sysadmin stuff: ssh sessions, tail -f syslog,
gkrellm)
3. has at least one dvi port
3. supports accelerated 2D
4. supports Xv
5. supports accelerated 3D well (definitely not fast, but very reliable/stable)

the last motherboard i bought for my household (6 months ago) uses a K8M890 (openchrome)
because though it has its problems, it's at least foss and actively developed/supported (and
in a socket 939 miniatx form factor).  the motherboard has a PCIe x16 slot, but currently
there's nothing significantly better than the integrated K8M890 (where "significantly better"
== "foss, 2D accel, 3D accel, Xv, XvMC").

there's a lot of good stuff on the horizon (ati documentation release & follow-on radeonhd
driver, on-going nouveau development, rumors of discrete intel graphics, etc), but nothing
quite there yet (from the regular video driver coverage i'm reading over at phoronix).

in a year or two there will probably be mature foss drivers for all three vendors (intel,
amd/ati, nvidia), but for the immediate future we need a grumby editor's review!

Unpleasant task in sight.

Posted Dec 2, 2007 10:34 UTC (Sun) by xav (subscriber, #18536) [Link]

I'm afraid our grumpy editor will get veeery grumpy when he tries various graphics cards under
various graphic loads. In my experience, the r300 driver is the Free 3d driver that drives the
fastest cards (ATI x850), and:
- it's not the fastest driver around (fglrx and catalyst are way better on same hardware)
- it has a tendency to lock the machine solid under 3d load
- generally the 3d framework under linux isn't mature enough (try blender under compiz)

But it's the best thing we have right now.

Video cards

Posted Dec 2, 2007 14:41 UTC (Sun) by rfunk (subscriber, #4054) [Link]

Short answer: G450-G550 Matroxes are best for 2D and for multi-head.

Though for some weird reason my G450 didn't work in the latest 
Ubuntu.  :-(   (I only installed it because my ATI Radeon R100 stopped 
working due to a bug in the radeon driver!)  I ended up getting a used 
Radeon 9200, which works great.  Haven't tried to go dual with it yet 
though.

It seems to be easier to get working cards if you don't care about DVI 
output, since there seems to be a small window between when manufacturers 
started supporting DVI and when they stopped providing open specs.

Video cards

Posted Dec 2, 2007 17:03 UTC (Sun) by jwb (guest, #15467) [Link]

Luckily you can get a DVI daughtercard for the G400 series.  It's a bit sad that this is still
one of the best cards you can get for X.org.  Oh well.  At least you can play Quake on it.

Video cards

Posted Dec 3, 2007 16:50 UTC (Mon) by DG (subscriber, #16978) [Link]

I'll second the G550 - they're quite cheap on ebay, and seem very reliable.

Unfortunately they have no 3D capability, and are probably 5+ years old - hence I /think/ I'm
missing out on 'new' stuff. 

I've also not found a distro that will magically generate the appropriate xorg.conf file for
it, and have to revert to using my own each and every time.


David.

Video cards

Posted Dec 4, 2007 10:19 UTC (Tue) by zdzichu (subscriber, #17118) [Link]

Sorry, that is simply not true. G550 has 3D capability, I'm using it to play Quake 3 Arena.

Careful of the G550 and DVI

Posted Dec 5, 2007 8:48 UTC (Wed) by k8to (subscriber, #15413) [Link]

G550 is a solid piece of kit, and a modern version has a nice small IC, and is very power
efficient.  However, it cannot reliably drive 1600x1200 over DVI.  If your monitor has this
resolution, or larger, and is a digital device like an LCD, then yuou should look elsewhere if
you care about image quality.

Careful of the G550 and DVI

Posted Dec 5, 2007 8:49 UTC (Wed) by k8to (subscriber, #15413) [Link]

That is.. if you have this resolution or larger you'll be using VGA, and decoding in your
monitor back to pixels, resulting in a slightly offset (and degraded) image, most of the time.

Video cards

Posted Dec 5, 2007 21:01 UTC (Wed) by zooko (subscriber, #2589) [Link]

I just bought a new workstation, or more precisely a set of components that can be built into
a new workstation once my wife and I have an evening or two in which to do it.  I bought a
nice shiny new Radeon 9250.  Also a super high-performance new Athlon64 3800+ (2.4 GHz, 512 KB
L2) 65 nm Lima.  Hooray for trailing-edge technology!  Cheap, well-understood, and supported
by Free/Open Source Software.

The first ATI r5xx/6xx X11 driver release

Posted Dec 4, 2007 5:01 UTC (Tue) by Cato (subscriber, #7643) [Link]

I'd like this too - video cards are one of the hardest bits of hardware to choose, given the
various tradeoffs.  It would be good to have recommendations based on (1) best card with FOSS
driver and (2) best card overall, covering both low to mid end 2D/3D (enabling Compiz etc) and
maybe higher-end gaming as well.


The first ATI r5xx/6xx X11 driver release

Posted Dec 4, 2007 20:13 UTC (Tue) by oak (subscriber, #2786) [Link]

The problem with that is that the grumpy editor needs the video cards to 
do the testing. Unlike open source, they are not free...

The first ATI r5xx/6xx X11 driver release

Posted Dec 5, 2007 0:36 UTC (Wed) by louie (subscriber, #3285) [Link]

Yeah, though grumpy editor has Ways of Making People Talk, which hopefully he could use to
drastically narrow down the scope of cards he's looking at before buying, especially if he
limits it to free drivers, and cards available as standalone cards (which knocks out all the
intels, for example, AFAIK.)

The first ATI r5xx/6xx X11 driver release

Posted Dec 2, 2007 18:41 UTC (Sun) by drag (subscriber, #31333) [Link]

Hrm. 

So much hate towards the Intel drivers. In my experiance they've been adiquately fast, run
compiz acceptably well unless your running 3D apps on top of it, and have been stable. Xrandr
now allows hotplug, and yes there are a couple different ways to get DVI out on a Intel
onboard if you realy want it. (ie. by a motherboard with DVI out or purchase a ADD2 card and
add it to a existing0 motherboard)

Obviously if you need to a lot of 3D work and want to do gaming then Intel shouldn't be your
first choice. ATI's new proprietary drivers seem fine and Nvidia provides good performance.


If you realy want to know. Probably the biggest problem with Open Source drivers is the dual
driver nature of it. 

Currently, in Linux, with open source drivers, you have a minimum of 3 drivers running to
operate your video card at any one time.  

* You have the vga console or framebuffer stuff for the virtual console. This is from the
Linux kernel. 
* Then from X.org you have the xfree intel driver that provides acceleration for either XAA or
EXA framework. 
* Then on top of that you have the Mesa/DRI driver for opengl acceleration. 
(then the in kernel DRM driver to allow hardware access)

So essentially you have 3 different drivers from 3 different projects running one video card.
This is not a ideal situation.. in fact the whole architecture can be best described as just
very very bad. It's not so much designed, as just happenned over time.  

And not only that there has been a significant shift in how video cards are designed. There is
realy no such thing as a '2D' portion of the video card anymore. And not only that it's now
possible to use the 'GPU' as a more general purpose proccessor for running stuff other then
just 3D graphics. 

Now if you want to have your computer to have a entire proccessor that requires a significant
amount of proprietary middleware to run... then this is were things are headed. The GPU is
very powerfull stuff. For certain operations a modern video card can easily outpace a cluster
of Pentium machines running Linux. The way Nvidia and ATI have things setup right now is that
in order to utilize this power you have to program your software using their proprietary
tools. They have middleware that provides a abstraction for your application that in addition
to hiding the video card interfaces from you it provides a generic ISA that will work across
many of their video cards. 

This is the same thing that AMD and Intel do with their cpus, but it's done in hardware to
make the modern RISC-style proccessors they use appear as x86. 

So the way video cards and GPUs are going is that they are creating a new computer archecture,
a extension to x86, were they are refusing to disclose how to actually program for it. 

So this is why it's important to pay attention to projects like Gallium3D
http://www.tungstengraphics.com/wiki/index.php/Gallium3D

The way DRI is designed leads to very complex drivers. When combined with having to work side
by side with another driver or two that is made by other parties then it's obvious that it's
not going to lead to stable drivers. Now if all we used for acceleration was DRI.. have
everything purely OpenGL with no 'just 2d' exa or xaa then it has a much better chance of
working. 

But the goal of Gallium3D is a new driver achecture for Linux that is not only will provide
the features of Mesa/DRI it will make programming for modern hardware much more simplier. 

It is also suppose to not only provide acceleration for OpenGL it can provide acceleration for
all sorts of different APIs.. Glucose, OpenVR, DirectX, and support it for different window'ng
systems.. no-X framebuffer-style for embedded systems, Window, X windows/Linux/*BSD/etc

So you can get rid of the 2-3 driver nature of Linux graphics and go back to a single driver.
A single driver that is easier to deal with and supports multiple APIs, rather then _just_ EXA
or _just_ OpenGL.

That's the idea at least.

Just remember.. Those video cards are not just for graphics anymore. 

The first ATI r5xx/6xx X11 driver release

Posted Dec 2, 2007 19:04 UTC (Sun) by drag (subscriber, #31333) [Link]

Oh for links  to what I am talking about:

Here is Nvidia's CUDA:
http://developer.nvidia.com/object/cuda.html

> The CUDA Toolkit is a complete software development solution for programming CUDA-enabled
GPUs. The Toolkit includes standard FFT and BLAS libraries, a C-compiler for the NVIDIA GPU
and a runtime driver. The CUDA runtime driver is a separate standalone driver that
interoperates with OpenGL and Microsoft® DirectX® drivers from NVIDIA. CUDA technology is
currently supported on the Linux and Microsoft® Windows® XP operating systems.


ATI's effort is much more friendlier. It's CTM (close-to-metal) were they provide a assembler
programable interface for supported GPUs. It seems that they still had a software shim in
there to hide the video interfaces. 
http://en.wikipedia.org/wiki/Close_to_Metal

Arstechnica has some good articles on the subject:
http://arstechnica.com/news.ars/post/20070219-8878.html

AMD/ATI's Fusion is combining CPU/GPU cores into a single proccessor
http://arstechnica.com/news.ars/post/20061119-8250.html

Intel Larrebee seems to be taking the X86-style proccessor and extending into GPU-land.
http://arstechnica.com/news.ars/post/20070604-clearing-up...
http://arstechnica.com/news.ars/post/20070917-intel-picks...



The first ATI r5xx/6xx X11 driver release

Posted Dec 5, 2007 8:52 UTC (Wed) by k8to (subscriber, #15413) [Link]

The problem with the intel drivers aren't that the hardware isn't optimally fast for gaming.
The problem is that they seem many times slower than the hardware is capable of, and crash the
entire system as well.

Sure the hardware isn't a barnburner but if you don't care about the newest titles, that
doesn't matter, and it is a nice prospect for lowerall overall system thermal output, lower
noise, and lower power use.  But the drivers don't seem to work correctly.

Yes, if you don't push them, and stay in the desktop, things are fine.  It's the 3d that falls
over.

The first ATI r5xx/6xx X11 driver release

Posted Dec 5, 2007 13:57 UTC (Wed) by pheldens (guest, #19366) [Link]

Looking at the comments, it seems the r200 is still the best overall floss driver supported
chip.

I used it in the past but went for an r300 a year or so ago, and I can confirm it's alot
buggier in 3d and slowish in some 2D operations (mozilla, evince/epdf (popler) adobe flash,
gnash). On the positive side, it's a little faster in 3D and some applications, like
openarena, quake3 are rock solid.

Copyright © 2007, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds