Experimental Free drivers for ATI cards

Message

DecayCell · Post by **DecayCell** » Tue Apr 26, 2005 9:26 pm

I've unmasked and emerged xorg-x11-6.8.99.3 today, since it contains an experimental driver for the Radeon 9800PRO card I have. However, I can't seem to get it to work. I've compiled all necessary kernel modules (agpgart, intel-agp, drm & radeon), but the X log indicates that it can't find the device file in /dev/dri/ (which is empty). I'm including the relevant part of the log, please help me!

Code: Select all

(WW) RADEON(0): Enabling DRM support

	*** Direct rendering support is highly experimental for Radeon 9500
	*** and newer cards. In fact, the only thing you could probably use
	***  it for is better 2d acceleration. The 3d mesa driver is not  
	*** provided in this tree. A very experimental (and incomplete)
	*** version is available from http://r300.sourceforge.net
	*** This message has been last modified on 12/12/04.

drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card1
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card2
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card3
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card4
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card5
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card6
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card7
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card8
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card9
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card10
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card11
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card12
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card13
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card14
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card1
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card2
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card3
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card4
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card5
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card6
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card7
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card8
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card9
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card10
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card11
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card12
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card13
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card14
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
(II) RADEON(0): [drm] drmOpen failed
(EE) RADEON(0): [dri] DRIScreenInit failed.  Disabling DRI.

JustinHoMi · Post by **JustinHoMi** » Wed Apr 27, 2005 2:15 am

I know this doesn't answer your question, but I'm just curious for my own use why you wouldn't use the current available drivers from ATI?

Desoto · Post by **Desoto** » Wed Apr 27, 2005 3:49 am

Well I'm curious for my own use because the currently available drivers aren't working correctly on my system. If I log out of Gnome and then try "startx" again I end up with just a black screen... its not enjoyable because it requires a hard reset. I've been scouring the forums and googling for a whole day trying to find the source of the issue.. I thought this thread might help but I don't know.

JustinHoMi · Post by **JustinHoMi** » Wed Apr 27, 2005 3:56 am

Desoto... make a different post with your config and maybe we can help you.

DecayCell · Post by **DecayCell** » Wed Apr 27, 2005 5:41 am

JustinHoMi wrote:I know this doesn't answer your question, but I'm just curious for my own use why you wouldn't use the current available drivers from ATI?

I use only Free software, and besides, the ATI drivers just suck.

d4rk74m4 · Post by **d4rk74m4** » Wed Apr 27, 2005 6:07 am

I'm almost certain that the actual 3D driver is not included in Xorg, but the changed needed to get it loaded and to utilise the DRM are.

The Mesa driver itself is available at http://r300.sf.net. You need to use the drm from that site, as the one built into the kernel does not provide the needed features for the experimental 3d driver.

DecayCell · Post by **DecayCell** » Wed Apr 27, 2005 6:57 am

d4rk74m4, I just tried that. First I'm trying to get the DRM to work, as I believe that right now it's failing before Mesa ever gets a chance to load. I got the latest DRM by following this guide, but for some strange reason dmesg reports that the CVS drm module dates just the same as the gentoo-sources one ("[drm] Initialized drm 1.0.0 20040925"); the latest x11-drm ebuild (20050104) won't even build on my system. I checked the CVS repository, and it seems that the only changes in the last few months were BSD-specific.
And of course, it still doesn't work, so any further advice would be appreciated.

d4rk74m4 · Post by **d4rk74m4** » Wed Apr 27, 2005 7:08 am

DecayCell wrote:d4rk74m4, I just tried that. First I'm trying to get the DRM to work, as I believe that right now it's failing before Mesa ever gets a chance to load. I got the latest DRM by following this guide, but for some strange reason dmesg reports that the CVS drm module dates just the same as the gentoo-sources one ("[drm] Initialized drm 1.0.0 20040925"); the latest x11-drm ebuild (20050104) won't even build on my system. I checked the CVS repository, and it seems that the only changes in the last few months were BSD-specific.
And of course, it still doesn't work, so any further advice would be appreciated.

The freedesktop.org drm also doesn't contain the needed support. The r300 driver is still rather incomplete, and not (in my opinion) yet ready for the main Mesa/drm trees yet.

Here's how I build it (from memory), if you want an explanation of the steps just ask, but for now I'm just going to spill the commands out:

For the drm:

Code: Select all

cvs -d:pserver:anonymous@cvs.sf.net:/cvsroot/r300 login
cvs -z3 -d:pserver:anonymous@cvs.sf.net:/cvsroot/r300 co r300_driver
cd r300_driver/drm
rm -rf shared
ln -s shared-core shared
cd linux-core
make radeon.o
cp *.ko /lib/modules/{kernel_version}/drivers/char/drm
modules-update

For the driver:

Code: Select all

cvs -d:pserver:anonymous@pdx.freedesktop.org:/cvs/mesa login
cvs -z3 -d:pserver:anonymous@pdx.freedesktop.org:/cvs/mesa co Mesa
mkdir Mesa/src/mesa/drivers/dri/r300
lndir /full/path/to/r300_driver/r300 /full/path/to/Mesa/src/mesa/drivers/dri/r300
cd Mesa
**EDIT** configs/linux-dri (or linux-dri-x86-64)
  add DRM_SOURCE_PATH=/full/path/to/r300_driver/drm above CONFIG_NAME
  edit DRI_DIRS to be "DRI_DIRS = dri_client r300"
**DONE EDIT**
make linux-dri-x86 (or linux-dri-x86-64)
cp Mesa/lib/r300_dri.so /usr/lib/modules/dri (or cp Mesa/lib64/r300_dri.so /usr/lib64/modules/dri)

Then, hopefully you should be able to modprobe drm and radeon, set xorg.conf driver to radeon, opengl-update xorg-x11 and have it all work.

My OpenGL renderer string with the driver working is

Code: Select all

OpenGL vendor string: Tungsten Graphics, Inc.
OpenGL renderer string: Mesa DRI R300 20040924 AGP 8x TCL
OpenGL version string: 1.3 Mesa 6.3

DecayCell · Post by **DecayCell** » Wed Apr 27, 2005 9:40 am

Thanks d4rk74m4, now I got it to work. However, upon running glxgears, X totally locks up, and requires a hard reboot. I know these drivers are experimental, but I suppose that something as simple as glxgears should work with them, and therefore something is wrong with my setup. Also, glxinfo claims that the AGP gives no speed multiplier (x1), could that have anything to do? Perhaps you could post the relevant section from your xorg.conf, please?

Thanks again for helping so far!

d4rk74m4 · Post by **d4rk74m4** » Wed Apr 27, 2005 1:18 pm

The lockup may be due to the agp problem. When I had the same issue, I didn't have lockups, but I did have artifacts over the screen.. Anyway.

Add

Code: Select all

Option "AGPMode" "8"

to the device section of your xorg.conf

Replace 8 with whatever agp mode you're running.

*edit* you asked for my xorg.conf, it's not very interesting:

Code: Select all

Section "Device"
    Identifier  "radeon"
    Driver      "radeon"
    Option      "AGPMode" "8"
EndSection

Good luck!

biitar · Post by **biitar** » Wed Apr 27, 2005 5:02 pm

Desoto wrote:Well I'm curious for my own use because the currently available drivers aren't working correctly on my system. If I log out of Gnome and then try "startx" again I end up with just a black screen... its not enjoyable because it requires a hard reset. I've been scouring the forums and googling for a whole day trying to find the source of the issue.. I thought this thread might help but I don't know.

I got a similare problem in all Xorg version 6.8.x ... tried diffrent ati drivers and diffrent xorg version over 6.8 ... all the time the same problem ... I even reconfigure my kernel ...

Of course I also get the computer to lock up if I jump to console and then back ... then X desktop appears but with distortion on the top and the whole computer freeze ...

DecayCell · Post by **DecayCell** » Thu Apr 28, 2005 8:21 am

Thanks, changed it. Well, it still locks up, so I guess that's why it's experimental...

By the way, about the other issue raised here: it's a bug in the ATI drivers, there's nothing you can do about it until ATI releases a new version with (hopefully) a fix.

d4rk74m4 · Post by **d4rk74m4** » Thu Apr 28, 2005 1:24 pm

DecayCell wrote:Thanks, changed it. Well, it still locks up, so I guess that's why it's experimental...

By the way, about the other issue raised here: it's a bug in the ATI drivers, there's nothing you can do about it until ATI releases a new version with (hopefully) a fix.

Are you able to give me some more info on your card, mobo etc?

Also, is it a "hard" lockup, ie. magic sysrq won't work, need reset button. Or are you able to still ssh into the machine and cleanly shutdown etc.

If you can, are you able to ssh into the machine and run

Code: Select all

RADEON_DEBUG=all glxgears &>log

and email me the log (darktama AT iinet DOT net DOT au), or pm it to me.

Thanks,
d4rk74m4

DecayCell · Post by **DecayCell** » Thu Apr 28, 2005 6:46 pm

It's a regular 128MB Radeon 9800PRO made by Hercules (it's in my desktop box).
I couldn't get the magic SysRq to work (which is strange by itself, I couldn't find it in the menu), but indeed I SSHed into the box after the lockup and it worked as usual, so I could at least reboot normally. Also, it seems to me that X is the only thing locking up...

Anyway, I'll e-mail you the log in a few minutes and continue to update this thread, in case it helps someone else.
Are you a DRI developer, by any chance?

Sir-Gentoo · Post by **Sir-Gentoo** » Tue May 17, 2005 7:50 am

So like i understand, with this dri300 drivers, you can get opensource 3d acceleration with the newest xorg server? would that be right and would they work better with composite and all of this stuff? and yes, i know that theire still not stable, but what time could that happen and they could replace the wrack ati drivers?

d4rk74m4 · Post by **d4rk74m4** » Tue May 17, 2005 1:46 pm

Sir-Gentoo wrote:So like i understand, with this dri300 drivers, you can get opensource 3d acceleration with the newest xorg server? would that be right and would they work better with composite and all of this stuff? and yes, i know that theire still not stable, but what time could that happen and they could replace the wrack ati drivers?

Yes, you can get 3d acceleration. Quake3 and simple things should work (see http://r300.sf.net for known issues, etc). Composite on it's own should work (I haven't tested this) but it will not be fast with xcompmgr as there is no RENDER acceleration yet. As for when r300_dri will be stable, that all depends on when people have time to implement things and fix bugs etc.

Also DecayCell, did you get my email ages ago? It bounced the first time and I can't remember if I resent it.

Debentoo_Gao · Post by **Debentoo_Gao** » Wed May 18, 2005 6:54 am

What's wrong with my r300 driver from r300.sf.net:

Code: Select all

inheart debentoogao # modprobe radeon
FATAL: Error inserting radeon (/lib/modules/2.6.12-rc4-nitro1/kernel/drivers/char/drm/radeon.ko): Unknown symbol in module, or unknown parameter (see dmesg)

Code: Select all

[drm] Initialized drm 1.0.0 20040925
radeon: Unknown symbol i2c_bit_add_bus
radeon: Unknown symbol i2c_bit_del_bus
radeon: Unknown symbol i2c_bit_add_bus
radeon: Unknown symbol i2c_bit_del_bus
radeon: Unknown symbol i2c_bit_add_bus
radeon: Unknown symbol i2c_bit_del_bus

It's the ATI Radeon 9600XT Card. Please help me,thanks a lot

Debentoo_Gao · Post by **Debentoo_Gao** » Wed May 18, 2005 8:55 am

Debentoo_Gao wrote:What's wrong with my r300 driver from r300.sf.net:

Code: Select all

inheart debentoogao # modprobe radeon
FATAL: Error inserting radeon (/lib/modules/2.6.12-rc4-nitro1/kernel/drivers/char/drm/radeon.ko): Unknown symbol in module, or unknown parameter (see dmesg)

Code: Select all

[drm] Initialized drm 1.0.0 20040925
radeon: Unknown symbol i2c_bit_add_bus
radeon: Unknown symbol i2c_bit_del_bus
radeon: Unknown symbol i2c_bit_add_bus
radeon: Unknown symbol i2c_bit_del_bus
radeon: Unknown symbol i2c_bit_add_bus
radeon: Unknown symbol i2c_bit_del_bus

It's the ATI Radeon 9600XT Card. Please help me,thanks a lot

FIXED!!!
I lost some I2C options in Kernels before. It's OK now

infirit · Post by **infirit** » Fri Jul 01, 2005 7:15 pm

Thanks for the little howto

Now if only they would support render acceleration...

Anyhow it is working great for xscreensaver and playing video with mplayer

infirit · Post by **infirit** » Tue Jul 12, 2005 12:05 pm

Well I have been experimenting with this driver and i have to say i'm impressed! The games I tried are chromium bse (+/- 50fps) and cube (+/- 40fps). Both run without visible artifact and smooooth

niskel · Post by **niskel** » Tue Jul 12, 2005 2:11 pm

Can anybody compare these driver's performance against the ati-drivers. The idea of open source drivers is exciting and I would love to try them out before long if it is worth making the switch from the closed source ones.

dapsaille · Post by **dapsaille** » Fri Jul 15, 2005 5:38 pm

well .. i'm really interested about this project .. but before try i need to do some others things and of course backup my system:p

yes .. from now i won't use anymore root for doing all my stuff :p

.. If someone have informations about this opensource driver , we are here :p

DAMNED .. it's too late for backup time .. my right hand have writed some awfull commands in terminal .. like cvs and others ... oh my goddd it's full of stars .. dhu .?. not stars but lovely commands with gcc and other exotic words ... rhaaaa

NOTA= This is my DPOM ... (delirious post of the month)

infirit · Post by **infirit** » Thu Jul 21, 2005 9:29 pm

r300 drm and Mesa has just been merged into the main cvs on freedesktop.org.

Kanniball · Post by **Kanniball** » Wed Jul 27, 2005 6:56 pm

infirit wrote:r300 drm and Mesa has just been merged into the main cvs on freedesktop.org.

Well can anybody tell me what I need to emerge in order to try these drivers???

Thanks a lot!

infirit · Post by **infirit** » Wed Jul 27, 2005 7:22 pm

Kanniball wrote:
infirit wrote:r300 drm and Mesa has just been merged into the main cvs on freedesktop.org.
Well can anybody tell me what I need to emerge in order to try these drivers???

Thanks a lot!

Well, you don't

You will have to build it from cvs. Instructions can be found here.