Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[HOWTO] Get DRI working with Radeon 9600/M10 (deprecated)
View unanswered posts
View posts from last 24 hours

Goto page 1, 2, 3, 4  Next  
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC
View previous topic :: View next topic  
Author Message
HighOnBonsai
Apprentice
Apprentice


Joined: 05 Jan 2004
Posts: 260

PostPosted: Thu Aug 18, 2005 11:37 am    Post subject: [HOWTO] Get DRI working with Radeon 9600/M10 (deprecated) Reply with quote

Note: This HOWTO is deprecated. The r300 drivers have been merged into the DRI project.

Have a look at this thread (and its newer replies!) for more updated information:
https://forums.gentoo.org/viewtopic-t-374745-highlight-r300.html

Since the r300 drivers are now included into modular X, check out this link too:
http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml

Thanks to the guys who gave me valuable feedback!

Christopher

Note: For the list of updates have a look at the end of this howto.

Introduction

I. What do we want to do?

The r300 project at sourceforge ( http://r300.sourceforge.net ) has mananged to provide open-source drivers for newer ATi Radeon. Especially the Radeon (Mobility) 9600 (M10) which is built into the Apple Powerbook ALU.

Although their has been support for 2D acceleration on this hardware for a long time, DRI (direct rendering) has not been supported until now. The r300 project provides drivers to get DRI activated on a basis of open-source drivers, which essentially means a drastic speed-up for most of the
OpenGL-based applications.

What we want to do is to get DRI working on a Apple Powerbook.

II. What can I expect?

You can expect a drastic speedup for most of the open-gl based applications (e.g. glxgears runs about 10-times faster - but who wants to watch rotating gears all the time? :-) ).

Tested programs:

  • TuxRacer: performance is ok; some problems with fonts in the menu (and with textures {sillian87})
  • Neverball: performance is good; reflection should be turned off - it does not work
  • OpenGL XScreensaver: performance depends on the screensaver (obviously); some screensavers produce 40% CPU usage, others 90%; run very stable
  • bzFlag: bad performance (a dia-show...)
  • gl117: too slow (silian87)
  • FooBillard works very nicely! (silian87)
  • Trigger gives an error whenn starting a race: r300SetupPixelShader: No valid fragment shader, exiting (silian87)
  • Cube gives an error (silian87)
  • Flightgear works, but it is TOO slow to be playable. (silian87)
  • Supertux with the opengl extension, work better than without, nice! (silian87)
  • CannonSmash has got flashing text on menu, but the game works without problems (silian87)
  • lincity-ng very slow with opengl, playable without opengl (but a bit slow). Game works. (silian87)


Please report programs you have tested!

III. What should I not expect?

The drivers a still very experimental:

  • do not expect them to be stable
  • do not expect them to be fast
  • do not expect them to implement every feature needed by some applications


Also the xorg composite extension is still not supported by this driver and will be deactivatet on start-up of X.

Please do also have a look at the project page of the r300 driver:

http://r300.sourceforge.net

Especially the paragraph:

Quote:
The source code on this website may damage your hardware.
It is *UNTESTED* and *BROKEN* !
Or, at least, some of it is.


Some words on this howto

This howto is essentially a compiled version of all the helpful howtos and documentation on this topic spread all of the web. Find the most important resource in the Appendix at the end of this howto.

0. Lets get started: Prerequisites

Before we get started, please check you have got the following software installed:


  • a Gentoo installation (ok, this is obvious :-) )
  • a >=2.6.11 kernel (I am using a 2.6.12 kernel)
  • the x.org x11 implementation (x11-base/xorg-x11-6.8.99.15) with the USE-flags "insecure-drivers" activated (this version of X is hard-masked!)
  • you need obviously the "~ppc" keyword in /etc/make.conf
  • CVS (we will need to fetch some sources)


You will also need some patience (compiling software takes some time!)

Note: Before you start you should consider to create a backup of your current X installation:

Code:
quickpkg xorg-x11


1. Compling the DRM kernel modules

Now we will the compile the DRM kernel modules. For this we use the "x11-drm" ebuild.

At first you need to make sure that you have DRM deactivated in your kernel and AGP support enabled. Your "<kernel-dir>/.config" should look like this:
Code:
...
CONFIG_AGP=m
CONFIG_AGP_UNINORTH=m
# CONFIG_DRM is not set
...


If your kernel config differs change it accordingly and reboot your machine with the new kernel.

Before we compile the "x11-drm" package we need to define what kernel modules we want. We can do this by adding the line

Code:
VIDEO_CARDS="radeon"


to our /etc/make.conf file.

Now emerge x11-drm:

Code:
# takes a minute or so
emerge -a x11-drm



2. Fetching the sources

What we need are the mesa-sources and DRM drivers (since 07/22/05 the mesa and the drm drivers of the r300 project have been accepted in the Mesa and DRM CVS trees - so we do not need to fetch the source from the r300-project). For this purpose lets create a directory:

Code:
mkdir -p /usr/src/r300


Now we need to fetch the up-to-date source trees. Let us start with Mesa:

Code:
cd /usr/src/r300
export CVSROOT=":pserver:anonymous@cvs.freedesktop.org:/cvs/mesa"
# This may take a while ("du -ms Mesa" gives me 41 MB)
cvs checkout Mesa


Now its time to fetch the DRM sources

Code:
 export CVSROOT=":pserver:anonymous@cvs.freedesktop.org:/cvs/dri"
# "du -ms drm" gives me 5 MB
cvs checkout drm


The DRM sources tree also contains the kernel drivers. I used the kernel drivers of the "x11-drm" package which have been working very fine so far.

3. Compiling the DRI drivers for X11

Now we are going to compile the DRI drivers for the X-server. At first change your working directory to the root of the Mesa source tree:

Code:
cd /usr/src/r300/Mesa


We now have to "make" the "linux-dri" target. But before we can do this we have to tweak the configuration. To do this lets changed to the "configs" subdir:

Code:
cd configs


This directory contains the target configurations for several platforms and operating systems. You may have recognized the "linux-dri-ppc" target. We
could use this, but we won't. We will use the "linux-dri" config file and adapt it. The linux-dri configuration file is a general purpose configuration common for all platforms. Fire up you favourite editor to edit the "linux-dri" file (which is hopefully vi... *flaming* :-) ):

Code:
# Back the old version!
cp linux-dri linux-dri.backup
${EDITOR} linux-dri


Move to the end of the file. You'll see a line, which looks like this:

Code:
DRI_DIRS = dri_client i810 i830 i915 mach64 mga r128 r200 r300 radeon s3v \
savage sis tdfx trident unichrome ffb


This are all the available DRI drivers which will be built. We only need two of the targets. So copy the line, comment out the original line and remove all targets "r300" (thats what we are talking about...)

(since recent changes "dri_client" is not needed anymore - thanks to gnomeza for pointing this out!).

Code:
#DRI_DIRS = i810 i830 i915 mach64 mga r128 r200 r300 radeon s3v \
#  savage sis tdfx trident unichrome ffb
DRI_DIRS = r300



Next we need to tell Mesa where the DRM drivers can be found. Do this by adding the line:

Code:
DRM_SOURCE_PATH = /usr/src/r300/drm


Since we are using a general purpose configuration file, we need to introduce some PPC-specific compiler-flags. We can do this by defining this flags with the "OPT_FLAGS" variable. The following flags worked fine for me:

Code:
OPT_FLAGS = -O2 -mcpu=7450 -mabi=altivec -maltivec -pipe


Save the changes and exit the editor - we are now ready to compile the DRI modules. To do so change your working directory to the root directory of the Mesa tree:

Code:
cd /usr/src/r300/Mesa


Lets compile the stuff:

Code:
# this may take some time (7 minutes and 30 secs on my powerbook 1.0 GHz)
make linux-dri


This produced some nifty libs:

Code:
ls /usr/src/r300/Mesa/lib


Can you see the "r300_dri.so" file? Yes? Great! Lets copy the "r300_dri" into the DRI driver directory of X:

Code:
cp /usr/src/r300/Mesa/lib/r300_dri.so /usr/X11R6/lib/modules/dri


4. Tell X to use the MesaGL library (the Gentoo-way)

Now we need to tell X to use the MesaGL library (have you seen the files in the lib-directory of Mesa?). We now create our own GL-implementation directory for the "eselect opengl"-command (formerly known as "opengl-update"):

Code:
mkdir -p /usr/lib/opengl/mesa-cvs


We need to create three symlinks. One to the aforementioned mesa libraries, one to the header files of mesa and one to the old extensions of the xorg-x11 implementation (thanks to electroarts):

Code:
ln -s /usr/src/r300/Mesa/lib /usr/lib/opengl/mesa-cvs/lib
ln -s /usr/src/r300/Mesa/include /usr/lib/opengl/mesa-cvs/include
ln -s /usr/lib/opengl/xorg-x11/extensions /usr/lib/opengl/mesa-cvs/extensions


Launch "eselect opengl list". You will recognize that we have a additional implementation now: "mesa-cvs". So lets activate our opengl implementation:

Code:
eselect opengl set mesa-cvs


If you still use opengl-update (which is deprecated and will likely be replaced in the foreseeable future) you can achieve the same as above with:

Code:
opengl-update mesa-cvs


5. Configuration

We need to configure two things: Loading the AGP modules on startup and tweaking the xorg.conf file.

To load the AGP modules on startup add the lines:

Code:
agpgart
uninorth-agp


To your /etc/modules.autoload.d/kernel-2.6 file.

Note: You should always load the AGP drivers before the radeon drivers! Otherwise AGP won't be available and DRI won't work!

Lets configure X now: Fire up again your editor and open the X configuration file: /etc/X11/xorg.conf

I can show you my "device"-section. You can adapt to your needs it if you want:

Code:
 ...
Section "Device"
        Identifier  "Card0"
        Driver          "radeon"
        VendorName  "ATI Technologies Inc"
        BoardName   "Unknown Board"

        Option "UseFBDev" "On"
        Option "AGPMode" "4"
        Option "EnablePageFlip" "true"

   # This two lines are needed to prevent fonts from being scrambled
        Option "XaaNoScanlineImageWriteRect"
        Option "XaaNoScanlineCPUToScreenColorExpandFill"

        Screen 0
EndSection
...


You may need to change the "identifier" to fit your configuration!

For the "scrambled fonts" issue have a look at:

http://www.mail-archive.com/dri-devel@lists.sourceforge.net/msg24410.html

Next you need to activate DRI in you X configuration by loading the modules "dri" and "drm"

Code:
Section "Module"
   ...
        Load    "drm"
        Load    "dri"
        ...
EndSection


And don't forget the famous "dri" section:

Code:
Section "dri"
        Mode 0666
EndSection


I also had some permission problems using udev. You should add your user to the "video" group if you experience a similar problem!

6. Testing

Now it time to test our configuration:

Code:
# Shut down your X-server
# remove all the loaded video modules (example:)
rmmod radeon
rmmod drm
# load the agp-modules
modprobe agpgart
modprobe uninorth-agp
# launch dmesg and lsmod to see if everything worked fine!
dmesg
lsmod
# start-up the X server again and have a look at /var/log/Xorg.0.log


Your Xorg.0.log should look like mine (the relevant parts):

Code:

...
(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 or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenByBusid: Searching for BusID pci:0000:00:10.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports pci:0000:00:10.0
(II) RADEON(0): [drm] loaded kernel module for "radeon" driver
(II) RADEON(0): [drm] DRM interface version 1.2
(II) RADEON(0): [drm] created "radeon" driver at busid "pci:0000:00:10.0"
(II) RADEON(0): [drm] added 8192 byte SAREA at 0xe100d000
(II) RADEON(0): [drm] mapped SAREA 0xe100d000 to 0x340b9000
(II) RADEON(0): [drm] framebuffer handle = 0xb8000000
(II) RADEON(0): [drm] added 1 reserved context for kernel
(II) RADEON(0): [agp] Mode 0x07000207 [AGP 0x106b/0x0034; Card 0x1002/0x4e50]
(II) RADEON(0): [agp] 8192 kB allocated with handle 0x00000001
(II) RADEON(0): [agp] ring handle = 0x00000000
(II) RADEON(0): [agp] Ring mapped at 0x340bb000
(II) RADEON(0): [agp] ring read ptr handle = 0x00101000
(II) RADEON(0): [agp] Ring read ptr mapped at 0x341bc000
(II) RADEON(0): [agp] vertex/indirect buffers handle = 0x00102000
(II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0x341bd000
(II) RADEON(0): [agp] GART texture map handle = 0x00302000
(II) RADEON(0): [agp] GART Texture map mapped at 0x343bd000
(II) RADEON(0): [drm] register handle = 0xb0000000
(II) RADEON(0): [dri] Visual configs initialized
(II) RADEON(0): Depth moves disabled by default
(II) RADEON(0): CP in BM mode
(II) RADEON(0): Using 8 MB GART aperture
(II) RADEON(0): Using 1 MB for the ring buffer
(II) RADEON(0): Using 2 MB for vertex/indirect buffers
(II) RADEON(0): Using 5 MB for GART textures
(II) RADEON(0): Memory manager initialized to (0,0) (1280,8191)
(II) RADEON(0): Reserved area from (0,854) to (1280,856)
(II) RADEON(0): Largest offscreen area available: 1280 x 7335
(II) RADEON(0): Will use back buffer at offset 0x119c000
(II) RADEON(0): Will use depth buffer at offset 0x15c8000
(II) RADEON(0): Will use 38912 kb for textures at offset 0x1a00000
(II) RADEON(0): Render acceleration unsupported on Radeon 9500/9700 and newer.
(II) RADEON(0): Render acceleration disabled
(**) RADEON(0): Option "XaaNoScanlineCPUToScreenColorExpandFill"
(**) RADEON(0): Option "XaaNoScanlineImageWriteRect"
(II) RADEON(0): Using XFree86 Acceleration Architecture (XAA)
   Screen to screen bit blits
   Solid filled rectangles
   8x8 mono pattern filled rectangles
   Solid Lines
   Offscreen Pixmaps
   Setting up tile and stipple cache:
      32 128x128 slots
      32 256x256 slots
      16 512x512 slots
(II) RADEON(0): Acceleration enabled
(==) RADEON(0): Backing store disabled
(==) RADEON(0): Silken mouse enabled
(II) RADEON(0): Using hardware cursor (scanline 856)
(II) RADEON(0): Largest offscreen area available: 1280 x 7331
(II) RADEON(0): No video input capabilities detected and no information is provided - disabling multimedia i2c
(II) RADEON(0): no multimedia table present, disabling Rage Theatre.
(II) RADEON(0): X context handle = 0x1
(II) RADEON(0): [drm] installed DRM signal handler
(II) RADEON(0): [DRI] installation complete
(II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers
(II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers
(II) RADEON(0): [drm] dma control initialized, using IRQ 48
(II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808
(II) RADEON(0): Direct rendering enabled
...


Now launch a shell in X and type

Code:
env LIBGL_DEBUG=verbose glxinfo


And look for the magic line

Code:
direct rendering = yes


If it says "no" have a look at the debugging output procduced by the "LIBGL_DEBUG=verbose" variable and post it here in the forums!

7. Updating the drivers
(Thanks to scoobydu for pointing out that this is missing)

In order to update the drivers you need to update the two CVS repositories. Before we update the Mesa repository we should make a copy of our own "linux-dri" file:

Code:
# lets backup our linux-dri file
cp /usr/src/r300/Mesa/configs/linux-dri /usr/src/r300/Mesa/configs/my-linux-dri


You should also update the old binaries in order to avoid problems if the new binaries are causing problems (thanks againg to scoobydu):

Code:
cp -r /usr/src/r300/Mesa/lib /usr/src/r300/Mesa/lib-backup


Now we can update the repository:

Code:
# change working directory to root of Mesa CVS
cd /usr/src/r300/Mesa
# lets update the CVS repository
cvs update -dP
# CVS will report some conflicts. Something like this:
#   Merging differences between 1.33 and 1.34 into linux-dri
#   rcsmerge: warning: conflicts during merge
#   cvs update: conflicts found in configs/linux-dri


You can remove the conflicts from the file manually or restore our copy of the modified linux-dri file:

Code:
mv /usr/src/r300/Mesa/configs/my-linux-dri /usr/src/r300/Mesa/configs/linux-dri


The same procedure with the drm repository:

Code:
cd /usr/src/r300/drm
cvs update -dP


Watch the CVS output to find out whether relevant files have been changed since the last update or not ('man cvs')! Now re-compile the sources:

Code:
cd /usr/src/r300/Mesa
# make will only re-compile the modified stuff!
make linux-dri


Now copy the r300_dri.so file into the X directory and update the environment:

Code:
cp lib/r300_dri.so /usr/X11R6/lib/modules/dri/
env-update


Now just follow the steps of "6. Testing"

Appendix: Resources

HOWTO DRI with ATi Open-Source Drivers - Gentoo Wiki
DRI Wiki - Building
R300 at SourceForge
HOWTO DRI with Unichrome (other GPU, similar problem)

Appendix: Updates

Update - 10/09/05

  • new order: building x11-drm now comes before building the drivers (thx electroarts)
  • now suggesting to create a symlink to the "extensions" directory of the xorg-x11 opengl implementation in the mesa-cvs opengl directory (thx electroarts)


Update - 08/30/05

  • updated the section 2: as "opengl-update" is deprecated now, we use "eselect" (thx gnomeza)


Update - 08/25/05


  • removed a typo (x11-base/xorg-x11-6.8.99.15 instead of xorg-x11.6.8.99.15 in section 0) (thx eisenack)


Update - 08/23/05


  • updated the list of tested programs (thx silian87)


Update - 08/22/05


  • updated the prerequisites (you need ~ppc keyword) (thx silian87)
  • removed a typo ("insecure-drivers")
  • "dri_client" is not needed anymore in the DRI_DIRS-variable (thx gnomeza)


Update - 08/21/05

  • now suggesting a backup before updating the drivers (thx scoobydu)
  • moved the updates to the end of the howto


Update - 08/20/05

  • added "6. Updating the drivers"


Update - 08/19/05

  • added the suggestion to make a backup of xorg-x11 (thx scoobydu)
  • added link to "HOWTO DRI with Unichrome"


Update - 08/18/05

  • removed some typos
  • did some formatting (thx scoobydu)
  • added a appendix with links to useful resources
  • changed the title

_________________
Are YOU high - on bonsai?


Last edited by HighOnBonsai on Wed Jan 11, 2006 8:22 pm; edited 21 times in total
Back to top
View user's profile Send private message
Miguel
Tux's lil' helper
Tux's lil' helper


Joined: 21 Aug 2002
Posts: 118

PostPosted: Thu Aug 18, 2005 1:34 pm    Post subject: Reply with quote

DRM X module? Or GLX?

EDIT: A question... Does the expernal VGA/DVI adapter works?
Back to top
View user's profile Send private message
gnomeza
Tux's lil' helper
Tux's lil' helper


Joined: 31 Dec 2003
Posts: 97

PostPosted: Thu Aug 18, 2005 7:18 pm    Post subject: Reply with quote

Nice work HighOnBonsai :)
There are a couple of typos in there as you said...

BBCode formatting link http://www.phpbb.com/phpBB/faq.php?mode=bbcode (for your convenience - when reformatting bulleted lists).
Back to top
View user's profile Send private message
HighOnBonsai
Apprentice
Apprentice


Joined: 05 Jan 2004
Posts: 260

PostPosted: Thu Aug 18, 2005 7:55 pm    Post subject: Reply with quote

Yeah, I know. Going to fix the typos tomorrow (today was a busy day... :-) )


Christopher
_________________
Are YOU high - on bonsai?
Back to top
View user's profile Send private message
Miguel
Tux's lil' helper
Tux's lil' helper


Joined: 21 Aug 2002
Posts: 118

PostPosted: Thu Aug 18, 2005 9:08 pm    Post subject: Reply with quote

HighOnBonsai

Does the external VGA adapter works?
Back to top
View user's profile Send private message
HighOnBonsai
Apprentice
Apprentice


Joined: 05 Jan 2004
Posts: 260

PostPosted: Thu Aug 18, 2005 9:41 pm    Post subject: Reply with quote

@Miguel: Oops... sorry, forgot to answer you! :oops: This may help you:

https://forums.gentoo.org/viewtopic-t-363427-highlight-powerbook+xinerama.html

Christopher
_________________
Are YOU high - on bonsai?
Back to top
View user's profile Send private message
Miguel
Tux's lil' helper
Tux's lil' helper


Joined: 21 Aug 2002
Posts: 118

PostPosted: Thu Aug 18, 2005 10:42 pm    Post subject: Reply with quote

Yes, but the thing is, I compiled modular X and it crashes if I have it plugged when I start it.
That's why. I know how to configure it... ;)

Oh and MergedFB works better, because Xinerama disables DRI.
Back to top
View user's profile Send private message
HighOnBonsai
Apprentice
Apprentice


Joined: 05 Jan 2004
Posts: 260

PostPosted: Fri Aug 19, 2005 7:13 am    Post subject: Reply with quote

Quote:
...I compiled modular X...


You mean 7.0.0?? Sorry, have never used external DVI connector under Linux... :-(


Christopher
_________________
Are YOU high - on bonsai?
Back to top
View user's profile Send private message
scoobydu
Veteran
Veteran


Joined: 16 Feb 2003
Posts: 1076
Location: 'Mind the Gap'

PostPosted: Fri Aug 19, 2005 9:29 am    Post subject: Reply with quote

Excellent work :)

Looks like I need to backup, then give this a try! Would be nice to get this on dual screens too!
_________________
Tyan Tiger K8W, 2xOpteron 240,Powerbook5,6 15" 1.5g, Macbook Black 2g, Mac Mini 1g, Ipod P60g.
| Linux - From a windows user perspective|
Back to top
View user's profile Send private message
HighOnBonsai
Apprentice
Apprentice


Joined: 05 Jan 2004
Posts: 260

PostPosted: Fri Aug 19, 2005 9:37 am    Post subject: Reply with quote

Quote:
Excellent work


Thanks! :-)

Quote:
Looks like I need to backup, then give this a try! Would be nice to get this on dual screens too!


Yes, you are right - a backup is a good idea! I should mention that in the howto.


Christopher
_________________
Are YOU high - on bonsai?
Back to top
View user's profile Send private message
scoobydu
Veteran
Veteran


Joined: 16 Feb 2003
Posts: 1076
Location: 'Mind the Gap'

PostPosted: Fri Aug 19, 2005 12:28 pm    Post subject: Reply with quote

I was thinking of a full stage4 backup ;) with -> https://forums.gentoo.org/viewtopic-t-312817-highlight-.html

xorg it packaged up too :)
_________________
Tyan Tiger K8W, 2xOpteron 240,Powerbook5,6 15" 1.5g, Macbook Black 2g, Mac Mini 1g, Ipod P60g.
| Linux - From a windows user perspective|
Back to top
View user's profile Send private message
scoobydu
Veteran
Veteran


Joined: 16 Feb 2003
Posts: 1076
Location: 'Mind the Gap'

PostPosted: Fri Aug 19, 2005 6:09 pm    Post subject: Reply with quote

Working nicely ;) 222fps -> 1800fps 8)

Thx.

Couple of typo's fyi, with spaces around the = and 'quote' around the flags;

Quote:

DRI_DIRS=dri_client r300
DRM_SOURCE_PATH=/usr/src/r300/drm

OPT_FLAGS='-O2 -mcpu=7450 -mabi=altivec -maltivec -pipe'


So I guess for updates we update cvs and recopy modules ... ?
_________________
Tyan Tiger K8W, 2xOpteron 240,Powerbook5,6 15" 1.5g, Macbook Black 2g, Mac Mini 1g, Ipod P60g.
| Linux - From a windows user perspective|
Back to top
View user's profile Send private message
HighOnBonsai
Apprentice
Apprentice


Joined: 05 Jan 2004
Posts: 260

PostPosted: Sat Aug 20, 2005 11:03 am    Post subject: Reply with quote

Quote:
Working nicely 222fps -> 1800fps


Great!

Quote:
Couple of typo's fyi, with spaces around the = and 'quote' around the flags;


Its Makefile-syntax => should work without quotes and with spaces around the '='! But thank you anyway! :-)

Yeah, for updates just update the cvs repository, recompile and copy the r300_dri.so module.


Christopher
_________________
Are YOU high - on bonsai?
Back to top
View user's profile Send private message
scoobydu
Veteran
Veteran


Joined: 16 Feb 2003
Posts: 1076
Location: 'Mind the Gap'

PostPosted: Sun Aug 21, 2005 1:07 pm    Post subject: Reply with quote

Looking good!

I just did a backup of the previous module, incase the new one caused problems ...

Quote:

cp /usr/X11R6/lib/modules/dri/r300_dri.so /usr/X11R6/lib/modules/dri/r300_dri.so.backup


Interesting ... though for the syntax only worked with the spaces removed, wierd :)

Would be nice to have a x11-base/x11-dri ebuild ;)
_________________
Tyan Tiger K8W, 2xOpteron 240,Powerbook5,6 15" 1.5g, Macbook Black 2g, Mac Mini 1g, Ipod P60g.
| Linux - From a windows user perspective|
Back to top
View user's profile Send private message
HighOnBonsai
Apprentice
Apprentice


Joined: 05 Jan 2004
Posts: 260

PostPosted: Sun Aug 21, 2005 2:21 pm    Post subject: Reply with quote

Quote:
I just did a backup of the previous module, incase the new one caused problems ...


Better updating the whole lib-directory... :-)

Quote:
Interesting ... though for the syntax only worked with the spaces removed, wierd


Did you set the variables in the "linux-dri" file or did you do that in the shell, just before executing make?


Christopher
_________________
Are YOU high - on bonsai?
Back to top
View user's profile Send private message
scoobydu
Veteran
Veteran


Joined: 16 Feb 2003
Posts: 1076
Location: 'Mind the Gap'

PostPosted: Sun Aug 21, 2005 2:24 pm    Post subject: Reply with quote

In the shell :)

edit: xterm.
_________________
Tyan Tiger K8W, 2xOpteron 240,Powerbook5,6 15" 1.5g, Macbook Black 2g, Mac Mini 1g, Ipod P60g.
| Linux - From a windows user perspective|


Last edited by scoobydu on Sun Aug 21, 2005 3:08 pm; edited 2 times in total
Back to top
View user's profile Send private message
HighOnBonsai
Apprentice
Apprentice


Joined: 05 Jan 2004
Posts: 260

PostPosted: Sun Aug 21, 2005 2:35 pm    Post subject: Reply with quote

Thats why it is not working (it depends on what shell you are using). Setting the variables in the file works with Makefile-syntax :-D


Christopher
_________________
Are YOU high - on bonsai?
Back to top
View user's profile Send private message
gringo
Advocate
Advocate


Joined: 27 Apr 2003
Posts: 3793

PostPosted: Mon Aug 22, 2005 9:46 am    Post subject: Reply with quote

tons of thanx for this ! :D

I had not much time this weekend, but from what i saw, it looks like something has changed in the cvs recently, is that posssible ?
I was following your steps and when i try to compile the linux-dri ( or linux-dri-ppc) taget, it says libdrm is not present ... i didnt got this one week ago and did more or less the same you have written down. Any tip ? I also dont see any libdrm dir in the mesa root, and i think it was there the last time i tried.

As said, had not much time and will have look again tomorrow ;)

TIA
EDIT -> maybe some mod could made this sticky as i think many people will be interested in at least trying this !
Back to top
View user's profile Send private message
gnomeza
Tux's lil' helper
Tux's lil' helper


Joined: 31 Dec 2003
Posts: 97

PostPosted: Mon Aug 22, 2005 1:15 pm    Post subject: Reply with quote

Quote:
I was following your steps and when i try to compile the linux-dri ( or linux-dri-ppc) taget, it says libdrm is not present ...


Yes, this is a recent change in Mesa CVS (there have been a few major changes).

You now need to have libdrm installed and registered with pkg-config. Mesa uses pkg-config to find out where the headers are when building. Which is why you will get output from the build like this:
Code:

gcc -c -I. -I../../../include -I../../../include/GL/internal -I../../../src/mesa/main -I../../../src/mesa/glapi -I../../../src/mesa/drivers/dri/common `pkg-config --cflags libdrm` -I  ...blah blah blah...

Package libdrm was not found in the pkg-config search path.
Perhaps you should add the directory containing `libdrm.pc'
to the PKG_CONFIG_PATH environment variable

No package 'libdrm' found
In file included from glxclient.h:82,
                 from clientattrib.c:38:
../../../include/GL/internal/dri_interface.h:42:21: xf86drm.h: No such file or directory
../../../include/GL/internal/dri_interface.h:43:17: drm.h: No such file or directory


libdrm ebuilds are hardmasked so you'll need to build from cvs (I don't have time to check how right now).

The second change I've found in CVS is that in the configs, "dri-client" is no longer included in the DRI_DIRS line.


ciao
Mark
_________________
http://markferry.net
Back to top
View user's profile Send private message
silian87
Advocate
Advocate


Joined: 06 Oct 2003
Posts: 2318
Location: Treviso, Italy

PostPosted: Mon Aug 22, 2005 1:33 pm    Post subject: Reply with quote

2 questions:
1) Does this driver support the powerbook sleep? I use a lot this functions, so I need it
2) I'll be able to use the DVI port as I do now?

Thk :)
_________________
Musica che ascolto: http://www.last.fm/user/silian87/

Silian87 FAQs: http://marentax.homelinux.org/~silian87/silian87-faq.txt

GTalk: silian87@gmail.com
Back to top
View user's profile Send private message
scoobydu
Veteran
Veteran


Joined: 16 Feb 2003
Posts: 1076
Location: 'Mind the Gap'

PostPosted: Mon Aug 22, 2005 1:41 pm    Post subject: Reply with quote

silian87 wrote:
2 questions:
1) Does this driver support the powerbook sleep? I use a lot this functions, so I need it
2) I'll be able to use the DVI port as I do now?

Thk :)


1) Seems to for me, no problems here ... sleep to mem that is not suspend2 (disk - which I have yet to get working)
2) Not tried, but had intended to get the dvi port going with my cinema display .. give me the details and I can try it.
_________________
Tyan Tiger K8W, 2xOpteron 240,Powerbook5,6 15" 1.5g, Macbook Black 2g, Mac Mini 1g, Ipod P60g.
| Linux - From a windows user perspective|


Last edited by scoobydu on Mon Aug 22, 2005 2:40 pm; edited 1 time in total
Back to top
View user's profile Send private message
silian87
Advocate
Advocate


Joined: 06 Oct 2003
Posts: 2318
Location: Treviso, Italy

PostPosted: Mon Aug 22, 2005 1:47 pm    Post subject: Reply with quote

Ok if sleep works I'll tell you if second screen works too :D
wait :D
_________________
Musica che ascolto: http://www.last.fm/user/silian87/

Silian87 FAQs: http://marentax.homelinux.org/~silian87/silian87-faq.txt

GTalk: silian87@gmail.com
Back to top
View user's profile Send private message
silian87
Advocate
Advocate


Joined: 06 Oct 2003
Posts: 2318
Location: Treviso, Italy

PostPosted: Mon Aug 22, 2005 3:36 pm    Post subject: Reply with quote

Another hints... x11-drm should be emerged with ~ppc :wink:
_________________
Musica che ascolto: http://www.last.fm/user/silian87/

Silian87 FAQs: http://marentax.homelinux.org/~silian87/silian87-faq.txt

GTalk: silian87@gmail.com
Back to top
View user's profile Send private message
gnomeza
Tux's lil' helper
Tux's lil' helper


Joined: 31 Dec 2003
Posts: 97

PostPosted: Mon Aug 22, 2005 5:02 pm    Post subject: Reply with quote

libdrm is hardmasked since it's part of the new modularized X11.

You can still emerge libdrm anyway by doing:
Code:

echo x11-libs/libdrm >> /etc/package.unmask
echo x11-misc/util-macros >> /etc/package.unmask
emerge libdrm


Mesa CVS builds cleanly again.
I'll see how far I get with the rest tonight ...
Back to top
View user's profile Send private message
HighOnBonsai
Apprentice
Apprentice


Joined: 05 Jan 2004
Posts: 260

PostPosted: Mon Aug 22, 2005 7:23 pm    Post subject: Reply with quote

Haven't had this problem with libdrm so far - "equery" says that libdrm belongs to x11-drm and pkgconfig also works with the x11-package. Maybe I should put section three (DRM) before section 2 (DRI) just to be sure...


Christopher
_________________
Are YOU high - on bonsai?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC All times are GMT
Goto page 1, 2, 3, 4  Next
Page 1 of 4

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum