Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
HOWTO: Radeon 9500 (and newer) with DRI [Part I]
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4 ... 38, 39, 40  Next  
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
infirit
l33t
l33t


Joined: 11 Jan 2003
Posts: 764
Location: Hoofddorp / The Netherlands

PostPosted: Tue Oct 18, 2005 9:53 pm    Post subject: Reply with quote

mariux2 wrote:
But more importantly :) Does this really improve the desktop experience?
A lot of opengl operations get accelerated.
mariux2 wrote:
Does the desktop feel more snappy? Can we now use composition? Will this work on my 9700 Mobility?
No unfortunately at this moment no composit or render accelleration. This will work on all R3X0 chips the 9700 is one of them.

mariux2 wrote:
This uses the Open Source 'radeon' driver, correct?

This IS the opensource radeon driver. Support for older pre 9500 cards was already in mesa. Then a project started to reverse engineer the r300 driver (website) which got meged in mesa cvs recently.
_________________
EASY TO INSTALL = Difficult to install, but instruction manual has pictures.
Join the adopt an unanswered post initiative today
Back to top
View user's profile Send private message
lroland
n00b
n00b


Joined: 28 Aug 2005
Posts: 32
Location: Copenhagen, Denmark

PostPosted: Wed Oct 19, 2005 9:02 am    Post subject: Reply with quote

mariux2 wrote:

Does the desktop feel more snappy? Can we now use composition? Will this work on my 9700 Mobility?


If you have a Xserver installed which uses exa then you should be able to get a really snappy desktop, but AFAIK exa is only in xorg-server.
Back to top
View user's profile Send private message
infirit
l33t
l33t


Joined: 11 Jan 2003
Posts: 764
Location: Hoofddorp / The Netherlands

PostPosted: Wed Oct 19, 2005 9:33 am    Post subject: Reply with quote

lroland wrote:
mariux2 wrote:

Does the desktop feel more snappy? Can we now use composition? Will this work on my 9700 Mobility?


If you have a Xserver installed which uses exa then you should be able to get a really snappy desktop, but AFAIK exa is only in xorg-server.
True if the driver supports it, the radeon driver still uses xaa unfortunately...
_________________
EASY TO INSTALL = Difficult to install, but instruction manual has pictures.
Join the adopt an unanswered post initiative today
Back to top
View user's profile Send private message
RobNyc
Tux's lil' helper
Tux's lil' helper


Joined: 11 Oct 2005
Posts: 101
Location: NYC

PostPosted: Sat Oct 22, 2005 3:31 pm    Post subject: Reply with quote

I have a radeon pro 9200 256ddr
_________________
Thank You
Back to top
View user's profile Send private message
Iluminatus
Tux's lil' helper
Tux's lil' helper


Joined: 13 Nov 2004
Posts: 93
Location: Maia/Portugal

PostPosted: Sat Oct 22, 2005 3:55 pm    Post subject: Little script, to help deploy DRI libraries! Reply with quote

It needs a lot of rework i'm steel learning to make scripts.
This is my first, i'll try during this weekend to make the script in english.
The script is intended to install mesa libraries after the step "make linux-dri"
Every advice would be apreciated.

Code:

#!/bin/sh
#
# Script para substituir As libs da MESA, iniciacao ao scripting...
#
# Baseado no script de inatalação de drivers dri, créditos devidos a:
#   Frank Worsley   <franco@nettaxi.com>
#   Alan Hourihane  <alanh@fairlite.demon.co.uk>
#   Felix Kuehling  <fxkuehl@gmx.de>
#
#    Pedro Maia     <pedrom.maia@netcabo.pt>
#
#   ALPHA VERSION
############################################################################################################
#            Variáveis
############################################################################################################
MESASRC="/home/pedro_maia/Mesa"

###########################################################################################################
LIB="/usr/lib/"
DRI="/usr/lib/modules/dri/"
OPENGL_DIR="/usr/lib/opengl"
MESAGL="${OPENGL_DIR}/mesa-cvs"
MESAGL_LIB="${MESAGL}/lib/"
KERNEL_VER=`uname -r`
KERNEL_LIB_DIR="/lib/modules/$KERNEL_VER"

LIBMESA="${MESASRC}/lib"
INCLUDEMESA="${MESASRC}/include"

HERE=`pwd`
LOGFILE="${HERE}/Mesa_DRI.log"

ARG="$1"

############################################################################################################
#            Verificações
############################################################################################################
# verificar se o utilizador é o Root (admin)
if [ `whoami` != "root" ] && [ `whoami` != "ROOT" ]; then
   echo -e "\033[31m Se não é o utilizador root não pode instalar as driver's DRI."
   exit 1;
fi

# Verificar se o Xserver está a correr
ps -C X > /dev/null
if [ $? == 0 ]; then
   echo -e "\033[31m Aviso: O SEU SERVIDOR X, PARECE ESTAR A CORRER!!"
   echo "        E necessário sair do ambiente gráfico, para que o"
   echo "        script faça a actualização correcta dos drivers."
   exit 1
fi
#Coloca a cor normal
echo -e -n "\033[0m"   #???

#Script apenas compativel com kernel 2.6
# Kernel version and module filename extension
KERNEL_MAJOR=${KERNEL_VER%%.*}
KERNEL_TAIL=${KERNEL_VER#*.}
KERNEL_MINOR=${KERNEL_TAIL%%.*}
KERNEL_PATCH=${KERNEL_TAIL#.*}

if [ $KERNEL_MAJOR -eq 2 -a $KERNEL_MINOR -le 4 ]; then
   echo -e "\033[31m ERRO: Este script não suporta kernel's de versão inferior a 2.6!"
   #Coloca a cor normal
   echo -e -n "\033[0m"
   exit 1
else
   echo "Versão do Kernel       : ${KERNEL_VER}"
   echo "Directoria dos Modulos : ${KERNEL_LIB_DIR}"
fi

############################################################################################################
#            Verificar configuração/ Directorias
############################################################################################################
check_cfg () {
   #verifica a existência de mesa-cvs
   ls -d ${OPENGL_DIR}/mesa-cvs > /dev/null
   if [ $? -ne 0 ] ; then
      mkdir -p ${MESAGL}
   fi
   #verifica a existência de mesa-cvs/libs
   ls -d  ${MESAGL_LIB} > /dev/null
   if [ $? -ne 0 ] ; then
      mkdir -p ${MESAGL_LIB}
   fi
   #verifica a existência de mesa-cvs/include
   #FIXME, outras possiblidades
   ls -f ${MESAGL}/include > /dev/null
   if [ $? -ne 0 ] ; then
      ln -s ${INCLUDEMESA} ${MESAGL}/include
   fi
}

############################################################################################################
#            Verifca Suporte DRM
############################################################################################################
check_drm () {
#  verificar a existência do modulo DRM PRINCIPAL
ls ${KERNEL_LIB_DIR}/kernel/drivers/char/drm/drm.ko > /dev/null
if [ $? -eq 0 ] ; then
   echo -e "\033[33m Suporte DRM (modulo) activo!"
else
   dmesg |grep drm > /dev/null
   if [$? -ne 0]; then
      echo -e "\033[31m Aviso: Não tem suporte DRM activo no KERNEL!!"
   else
      echo -e "\033[33m Suporte DRM (builtin) activo!"
   fi
fi
echo -e -n "\033[0m"
#  verificar a existência do modulo DRM RADEON
ls ${KERNEL_LIB_DIR}/kernel/drivers/char/drm/radeon.ko > /dev/null
if [ $? -eq 0 ] ; then
   echo -e "\033[33m Suporte DRM para a placa Radeon (modulo) activa"
else
   dmesg |grep radeon > /dev/null
   if [$? -ne 0]; then
           echo -e "\033[31m Aviso: Não tem suporte DRM para a placa Radeon activo no KERNEL!!"
   else
      echo -e "\033[33m Suporte DRM para a placa Radeon (builtin) activo!"
   fi
fi
#Coloca a cor normal
echo -e -n "\033[0m"
}

############################################################################################################
#            Mover os ficheiros
############################################################################################################
move_files() {
   ERRO="0"
   OPERACAO="actualizacão"
   echo " Os ficheiros LibGLU.so*, libGLw.so*, libglut.so * vao para:"
   echo "  ${LIB}"
   #  mover biblioteca
   if [ "${ARG}" == "backup" ] || [ "${ARG}" == "BACKUP" ]; then
      cd ${LIB}
      ls -1 libGLU.s* | while read FILE
      do
         mv ${LIB}/$FILE ${LIB}/old_dri-$FILE >& $LOGFILE
      done
   fi
   mv ${LIBMESA}/libGLU.s* ${LIB} >& $LOGFILE
   if [ $? -eq 0 ] ; then
      echo " Os ficheiros LibGLU.so foram colocados com sucesso!"
   else
      ERR0="1"
      echo -e "\033[31m ERRO: Os ficheiros LibGLU.so não foram colocados!"
      echo -e -n "\033[0m"
   fi
   #  mover biblioteca
   if [ "${ARG}" == "backup" ] || [ "${ARG}" == "BACKUP" ]; then
      cd ${LIB}
      ls -1 libGLw.s* | while read FILE
      do
         mv ${LIB}/$FILE ${LIB}/old_dri-$FILE   >& $LOGFILE
      done
   fi
   mv ${LIBMESA}/libGLw.s* ${LIB} >& $LOGFILE
   if [ $? -eq 0 ] ; then
      echo " Os ficheiros LibGLw.so foram colocados com sucesso!"
   else
      ERR0="1"
      echo -e "\033[31m ERRO: Os ficheiros LibGLw.so não foram colocados!"
      echo -e -n "\033[0m"
   fi
   #  mover biblioteca glut (muito usada)
   if [ "${ARG}" == "backup" ] || [ "${ARG}" == "BACKUP" ]; then
      cd ${LIB}
      ls -1 libglut.s* | while read FILE
      do
         mv ${LIB}/$FILE ${LIB}/old_dri-$FILE >& $LOGFILE
      done
   fi
   mv ${LIBMESA}/libglut.s* ${LIB} >& $LOGFILE
   if [ $? -eq 0 ]; then
      echo " Os ficheiros Libglut.so foram colocados com sucesso!"
   else
      ERR0="1"
      echo -e "\033[31m ERRO: Os ficheiros Libglut.so não foram colocados!"
      echo -e -n "\033[0m"
   fi
   echo " Os ficheiros LibGL.so*,vao para:"
   echo "   ${MESAGL_LIB}"
   #  mover a biblioteca wrapper de funções OpenGL, (extensoes suportadas e afins)
   if [ "${ARG}" == "backup" ] || [ "${ARG}" == "BACKUP" ]; then
      cd  ${MESAGL_LIB}
      ls -1 libGL.s* | while read FILE
      do
         mv  ${MESAGL_LIB}/$FILE  ${MESAGL_LIB}/old_dri-$FILE >& $LOGFILE
      done
   fi
   mv ${LIBMESA}/libGL.s*  ${MESAGL_LIB} >& $LOGFILE
   if [ $? -eq 0 ] ; then
      echo " Os ficheiros LibGL.so foram colocados com sucesso!"
   else
      ERR0="1"
      echo -e "\033[31m ERRO: Os ficheiros LibGL.so não foram colocados!"
      echo -e -n "\033[0m"
   fi
   echo " Os ficheiros r300_dri.so, radeon_dri.so vao para:"
   echo "  ${DRI}"
   # mover as bibliotecas responsáveis pelo DRI (Direct Rendering Interface)
   if [ "${ARG}" == "backup" ] || [ "${ARG}" == "BACKUP" ]; then
      cd ${LIBMESA}  #get rest of dri files
      ls -1 *dri.so | while read FILE
      do
         mv ${DRI}/$FILE ${DRI}/old_dri-$FILE >& $LOGFILE
      done
   fi
   mv ${LIBMESA}/*dri.so ${DRI} >& $LOGFILE
   if [ $? -eq 0 ] ; then
      echo " Os ficheiros DRI foram colocados com sucesso!"
   else
      ERR0="1"
      echo -e "\033[31m ERRO: Os ficheiros DRI não foram colocados!"
      echo -e -n "\033[0m"
   fi
}

############################################################################################################
#            Recuperar os ultimos ficheiros DRI
############################################################################################################
restore_files () {
   OPERACAO="restauro"
   ERRO="0"
   echo " Os ficheiros de restauro LibGLU.so*, libGLw.so*, libglut.so * estao em:"
   echo "  ${LIB}"
   #  mover biblioteca
   cd ${LIB}
   ls -1 libGLU.s* | while read FILE
   do
      mv ${LIB}/old_dri-$FILE ${LIB}/$FILE >& $LOGFILE
      if [ $? -eq 0 ] ; then
         echo " Os ficheiros LibGLU.so, LibGLw.so e Libglut.so foram restaurados com sucesso!"
      else
         ERR0="1"
         echo -e "\033[31m ERRO: Os ficheiros LibGLU.so, LibGLw.so e Libglut.so não foram restaurados!"
         echo -e -n "\033[0m"
      fi
   done
   ls -1 libGLw.s* | while read FILE
   do
      mv ${LIB}/old_dri-$FILE ${LIB}/$FILE >& $LOGFILE
      if [ $? -eq 0 ] ; then
         echo " Os ficheiros LibGLU.so, LibGLw.so e Libglut.so foram restaurados com sucesso!"
      else
         ERR0="1"
         echo -e "\033[31m ERRO: Os ficheiros LibGLU.so, LibGLw.so e Libglut.so não foram restaurados!"
         echo -e -n "\033[0m"
      fi
   done
   ls -1 libglut.s* | while read FILE
   do
      mv ${LIB}/old_dri-$FILE ${LIB}/$FILE >& $LOGFILE
      if [ $? -eq 0 ] ; then
         echo " Os ficheiros LibGLU.so, LibGLw.so e Libglut.so foram restaurados com sucesso!"
      else
         ERR0="1"
         echo -e "\033[31m ERRO: Os ficheiros LibGLU.so, LibGLw.so e Libglut.so não foram restaurados!"
         echo -e -n "\033[0m"
      fi
   done
   echo " Os ficheiros de restauro LibGL.so*,estao em:"
   echo "   ${MESAGL_LIB}"
   #  mover a biblioteca wrapper de funções OpenGL, (extensoes suportadas e afins)
   cd  ${MESAGL_LIB}
   ls -1 libGL.s* | while read FILE
   do
      mv  ${MESAGL_LIB}/old_dri-$FILE  ${MESAGL_LIB}/$FILE >& $LOGFILE
      if [ $? -eq 0 ] ; then
         echo "Os ficheiros LibGL.so foram restaurados com sucesso!"
      else
         ERR0="1"
         echo -e "\033[31m ERRO: Os ficheiros LibGL.so não foram restaurados!"
         echo -e -n "\033[0m"
      fi
   done
   echo " Os ficheiros de restauro r300_dri.so, radeon_dri.so estao em:"
   echo "  ${DRI}"
   # mover as bibliotecas responsáveis pelo DRI (Direct Rendering Interface)
   #FIXME, need to generate correct list...
   cd ${DRI}  #get rest of dri files
   ls -1 *dri.so | while read FILE
   do
      mv ${DRI}/old_dri-$FILE ${DRI}/$FILE >& $LOGFILE
      if [ $? -eq 0 ] ; then
         echo "Os ficheiros DRI foram restaurados com sucesso!"
      else
         ERR0="1"
         echo -e "\033[31m ERRO: Os ficheiros DRI não foram restaurados!"
         echo -e -n "\033[0m"
      fi
   done
}

############################################################################################################
#            Fim -> Sucesso!!
############################################################################################################
msg_final () {
   if [ "$ERRO" != "1" ]; then
      echo " SUCESSO: A operação de ${OPERACAO}, dos ficheiros DRI, foi bem sucedida!!"
   else
      echo " ERRO: A operação de ${OPERACAO}, dos ficheiros DRI, não foi bem sucedida!!"
   fi
}

############################################################################################################
#            PSEUDONIMO MAIN()
############################################################################################################
check_cfg

if [ "${ARG}" == "restore" ] || [ "${ARG}" == "RESTORE" ]; then
   restore_files
   msg_final
   exit 0
else   #backup or not here we go..
   check_drm
   move_files
   if [ "ERR" == "0" ]; then
      whereis eselect > /dev/null
      if [ $? -eq 0 ]; then
         eselect opengl set mesa-cvs  #opengl Update
      else
         opengl-update mesa-cvs
      fi
   fi
   msg_final
   exit 0
fi


More to come....
Back to top
View user's profile Send private message
lroland
n00b
n00b


Joined: 28 Aug 2005
Posts: 32
Location: Copenhagen, Denmark

PostPosted: Sun Oct 23, 2005 9:32 pm    Post subject: Reply with quote

lroland wrote:
mariux2 wrote:

Does the desktop feel more snappy? Can we now use composition? Will this work on my 9700 Mobility?


If you have a Xserver installed which uses exa then you should be able to get a really snappy desktop, but AFAIK exa is only in xorg-server.


Just installed xorg-server 7.0 RC1 and it greatly simplifies the process of getting DRI/3D working :D (using xorg-server 7.0rc1 with kernel 2.6.14rc5 makes everything work out of the box, no cvs drm/mesa needed 8) ) - however EXA is only accelrated for core operations on R300, so no render accell just yet :cry: -
Back to top
View user's profile Send private message
withoutclass
n00b
n00b


Joined: 12 Oct 2005
Posts: 50

PostPosted: Mon Oct 24, 2005 5:07 am    Post subject: Reply with quote

i followed the instructions, and now i get this :(

Code:

drm: Unknown symbol agp_bind_memory
drm: Unknown symbol agp_enable
drm: Unknown symbol agp_find_bridge
drm: Unknown symbol agp_backend_acquire
drm: Unknown symbol agp_free_memory
drm: Unknown symbol agp_allocate_memory
drm: Unknown symbol agp_unbind_memory
drm: Unknown symbol agp_copy_info
drm: Unknown symbol agp_backend_release
radeon: Unknown symbol drm_open
radeon: Unknown symbol drm_fasync
radeon: Unknown symbol drm_poll
radeon: Unknown symbol drm_get_resource_len
radeon: Unknown symbol drm_core_get_reg_ofs
radeon: Unknown symbol drm_irq_uninstall
radeon: Unknown symbol drm_get_dev
radeon: Unknown symbol drm_ioctl
radeon: Unknown symbol drm_exit
radeon: Unknown symbol drm_debug
radeon: Unknown symbol drm_core_get_map_ofs
radeon: Unknown symbol drm_init
radeon: Unknown symbol drm_addmap
radeon: Unknown symbol drm_get_resource_start
radeon: Unknown symbol drm_vbl_send_signals
radeon: Unknown symbol drm_cleanup_pci
radeon: Unknown symbol drm_ati_pcigart_init
radeon: Unknown symbol drm_mmap
radeon: Unknown symbol drm_order
radeon: Unknown symbol drm_ati_pcigart_cleanup
radeon: Unknown symbol drm_core_reclaim_buffers
radeon: Unknown symbol drm_release


i have no idea what happened, and i actually performed the whole process twice too
Back to top
View user's profile Send private message
infirit
l33t
l33t


Joined: 11 Jan 2003
Posts: 764
Location: Hoofddorp / The Netherlands

PostPosted: Mon Oct 24, 2005 5:12 am    Post subject: Reply with quote

These errors are because of missing libdrm... Did you install these
Quote:
Code:
echo x11-libs/libdrm >> /etc/portage/package.unmask
echo 'x11-libs/libdrm ~*' >> /etc/portage/package.keywords
echo x11-misc/util-macros >> /etc/portage/package.unmask
echo 'x11-misc/util-macros ~*' >> /etc/portage/package.keywords
emerge -v --oneshot --nodeps util-macros libdrm

_________________
EASY TO INSTALL = Difficult to install, but instruction manual has pictures.
Join the adopt an unanswered post initiative today
Back to top
View user's profile Send private message
withoutclass
n00b
n00b


Joined: 12 Oct 2005
Posts: 50

PostPosted: Mon Oct 24, 2005 1:15 pm    Post subject: Reply with quote

infirit wrote:
These errors are because of missing libdrm... Did you install these
Quote:
Code:
echo x11-libs/libdrm >> /etc/portage/package.unmask
echo 'x11-libs/libdrm ~*' >> /etc/portage/package.keywords
echo x11-misc/util-macros >> /etc/portage/package.unmask
echo 'x11-misc/util-macros ~*' >> /etc/portage/package.keywords
emerge -v --oneshot --nodeps util-macros libdrm


yes, i followed the guide exactly.
Back to top
View user's profile Send private message
withoutclass
n00b
n00b


Joined: 12 Oct 2005
Posts: 50

PostPosted: Tue Oct 25, 2005 1:17 am    Post subject: Reply with quote

I am going through the whole guide again, and I'm noticing that this time around, when i get to cvs checkout Mesa, it seems to be getting many more things than the first time I did it, hopefully it works this time around

EDIT:

i do not get direct rendering.

Code:

modprobe radeon
WARNING: Error inserting drm (/lib/modules/2.6.13-gentoo-r3/kernel/drivers/char/drm/drm.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting radeon (/lib/modules/2.6.13-gentoo-r3/kernel/drivers/char/drm/radeon.ko): Unknown symbol in module, or unknown parameter (see dmesg)


EDIT2: I guess id rather keep editing this one instead of pissing people off

just curious, i got it working after noticing the post about making sure the right chipset module was activated

but i get this now, just wondering if its a big deal:

Code:

 glxinfo | grep -i "direct rendering"
*********************************WARN_ONCE*********************************
File r300_state.c function r300Enable line 456
TODO - double side stencil !
***************************************************************************
No ctx->FragmentProgram._Current!!
direct rendering: Yes


any ideas?
Back to top
View user's profile Send private message
infirit
l33t
l33t


Joined: 11 Jan 2003
Posts: 764
Location: Hoofddorp / The Netherlands

PostPosted: Tue Oct 25, 2005 4:43 am    Post subject: Reply with quote

withoutclass wrote:
but i get this now, just wondering if its a big deal:

Code:

 glxinfo | grep -i "direct rendering"
*********************************WARN_ONCE*********************************
File r300_state.c function r300Enable line 456
TODO - double side stencil !
***************************************************************************
No ctx->FragmentProgram._Current!!
direct rendering: Yes


any ideas?

They are reminders for the devs so you can ignore those. WHen playing a game like cube or quake a few of these will be in the log.
_________________
EASY TO INSTALL = Difficult to install, but instruction manual has pictures.
Join the adopt an unanswered post initiative today
Back to top
View user's profile Send private message
withoutclass
n00b
n00b


Joined: 12 Oct 2005
Posts: 50

PostPosted: Tue Oct 25, 2005 4:57 am    Post subject: Reply with quote

infirit wrote:
withoutclass wrote:
but i get this now, just wondering if its a big deal:

Code:

 glxinfo | grep -i "direct rendering"
*********************************WARN_ONCE*********************************
File r300_state.c function r300Enable line 456
TODO - double side stencil !
***************************************************************************
No ctx->FragmentProgram._Current!!
direct rendering: Yes


any ideas?

They are reminders for the devs so you can ignore those. WHen playing a game like cube or quake a few of these will be in the log.


ok thanks, now i get to try and figure out the error i get when attempting to emerge point2play
Back to top
View user's profile Send private message
fuoco
Guru
Guru


Joined: 23 May 2004
Posts: 386
Location: Israel

PostPosted: Tue Oct 25, 2005 11:06 pm    Post subject: Reply with quote

Does r300 work with radeon 9550 series too ? (those found in new ibooks)

How would it be to get this to work on modular X ? I suppose the idea is to just get 'newer' or cvs versions of certain components, and maybe even possible to easily make ebuilds for those components and put them in the overlay for easy install with the rest of the modular X components ?
Back to top
View user's profile Send private message
lroland
n00b
n00b


Joined: 28 Aug 2005
Posts: 32
Location: Copenhagen, Denmark

PostPosted: Wed Oct 26, 2005 8:58 am    Post subject: Reply with quote

fuoco wrote:
Does r300 work with radeon 9550 series too ? (those found in new ibooks)

How would it be to get this to work on modular X ? I suppose the idea is to just get 'newer' or cvs versions of certain components, and maybe even possible to easily make ebuilds for those components and put them in the overlay for easy install with the rest of the modular X components ?


It should work with that card also - if you install the latest modular xorg package and a kernel never than 2.6.13 then it should all work right out of the box (i.e. you do not even need to folow my guidelines with compiling drm/mesa from cvs). I haveit running just fine here.
Back to top
View user's profile Send private message
fuoco
Guru
Guru


Joined: 23 May 2004
Posts: 386
Location: Israel

PostPosted: Wed Oct 26, 2005 9:30 am    Post subject: Reply with quote

lroland wrote:
fuoco wrote:
Does r300 work with radeon 9550 series too ? (those found in new ibooks)

How would it be to get this to work on modular X ? I suppose the idea is to just get 'newer' or cvs versions of certain components, and maybe even possible to easily make ebuilds for those components and put them in the overlay for easy install with the rest of the modular X components ?


It should work with that card also - if you install the latest modular xorg package and a kernel never than 2.6.13 then it should all work right out of the box (i.e. you do not even need to folow my guidelines with compiling drm/mesa from cvs). I haveit running just fine here.


Thanks. But with that configuration I don't get direct rendering:
Code:
$ glxinfo |grep "direct rendering"
direct rendering: No

in xorg.conf:
Code:
Section "Device"
        Identifier      "Card0"
        Driver  "radeon"
        Option  "AccelMethod"   "exa"
EndSection

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

Section "DRI"
        Group 0
        Mode 0666
EndSection


in Xorg.0.log I find:
Code:
(WW) ****INVALID IO ALLOCATION**** b: 0xf0000400 e: 0xf00004ff correcting^G
(EE) end of block range 0xefffffff < begin 0xf0000000

(WW) RADEON(0): Video BIOS not detected in PCI space!
(WW) RADEON(0): Attempting to read Video BIOS from legacy ISA space!
(WW) RADEON(0): Unrecognized BIOS signature, BIOS data will not be used


And then:
Code:
(WW) RADEON(0): Enabling DRM support

        *** Direct rendering support is highly experimental for Radeon 9500
        *** and newer cards. The 3d mesa driver is not provided in this tree.
        *** A very experimental (and incomplete) version is available from Mesa CVS.
        *** Additional information can be found on http://r300.sourceforge.net
        *** This message has been last modified on 2005-08-07.

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
which goes on for a few thousand lines until:

Code:
(II) RADEON(0): [drm] drmOpen failed
(EE) RADEON(0): [dri] DRIScreenInit failed.  Disabling DRI.
Back to top
View user's profile Send private message
lroland
n00b
n00b


Joined: 28 Aug 2005
Posts: 32
Location: Copenhagen, Denmark

PostPosted: Wed Oct 26, 2005 9:42 am    Post subject: Reply with quote

Well I did nothing special, I installed the latest modular xorg, kernel 2.6.14rc5 with drm and radeon modules - then I fired up X and get the following in the logs (which indikate that DRI is working (also I can play games so there is no doubt :D )):

Code:

(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 11
(II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808
(II) RADEON(0): Direct rendering enabled


Note that I did the modular xorg installation on a clean machine (i.e. I wiped out my prior Gentoo installation and installed from scratch (using jackass)). Also note that glxgears need to be installed from spyderous overlay or directly from source.


Last edited by lroland on Wed Oct 26, 2005 9:50 am; edited 2 times in total
Back to top
View user's profile Send private message
fuoco
Guru
Guru


Joined: 23 May 2004
Posts: 386
Location: Israel

PostPosted: Wed Oct 26, 2005 9:45 am    Post subject: Reply with quote

I have kernel-2.6.14-rc5 too. I made a clean install with modular X too, and I used glx-utils ebuild from gentopia which provides glxinfo/glxgears...
Back to top
View user's profile Send private message
Iluminatus
Tux's lil' helper
Tux's lil' helper


Joined: 13 Nov 2004
Posts: 93
Location: Maia/Portugal

PostPosted: Wed Oct 26, 2005 11:06 pm    Post subject: Reply with quote

Please verify if your Board PCI ID is registered in file radeon_screen.c
If it's not you'll have to add it manually!

lspci |grep ATI

now you can see the PCI ID

lspci -n |grep 0300

with this you check again PCI ID, and get Chip ID it's after 1002:XXXX

then check if your PCI ID match!

make the patch!

Example patch:
Code:

--- xc/extras/Mesa/src/mesa/drivers/dri/r300/radeon_screen.c   2005-10-19 21:02:06.000000000 +0200
+++ radeon_screen.c   2005-10-20 10:32:56.000000000 +0200
@@ -201,6 +201,7 @@
 #define PCI_CHIP_R300_AF      0x4146
 #define PCI_CHIP_R300_AG      0x4147
 #define PCI_CHIP_RV350_AP               0x4150
+#define PCI_CHIP_RV350_AQ               0x4151
 #define PCI_CHIP_RV350_AR               0x4152
 #define PCI_CHIP_RV350_AS               0x4153
 #define PCI_CHIP_RV350_NJ      0x4E4A
@@ -384,6 +385,7 @@
    case PCI_CHIP_R300_AF:
    case PCI_CHIP_R300_AG:
    case PCI_CHIP_RV350_AP:
+        case PCI_CHIP_RV350_AQ:
    case PCI_CHIP_RV350_AR:
    case PCI_CHIP_RV350_AS:
    case PCI_CHIP_RV350_NJ:



By the way a few hours ago, Aapo Tahkola implemented a patch that gives support to GL_ARB_texture_cube_map, also had done a little cleanup/bug fixes. Even so s3t textures are still a little broken so don't expect clear textures (only crisp textures at least if you are from objects (in games like ET, RTCW), if you are near the object s3tc work well (Bahh, known bug!!))
Back to top
View user's profile Send private message
fuoco
Guru
Guru


Joined: 23 May 2004
Posts: 386
Location: Israel

PostPosted: Wed Oct 26, 2005 11:13 pm    Post subject: Reply with quote

Iluminatus wrote:
Please verify if your Board PCI ID is registered in file radeon_screen.c
If it's not you'll have to add it manually!

lspci |grep ATI

now you can see the PCI ID

lspci -n |grep 0300

with this you check again PCI ID, and get Chip ID it's after 1002:XXXX

then check if your PCI ID match!

make the patch!

Example patch:
Code:

--- xc/extras/Mesa/src/mesa/drivers/dri/r300/radeon_screen.c   2005-10-19 21:02:06.000000000 +0200
+++ radeon_screen.c   2005-10-20 10:32:56.000000000 +0200
@@ -201,6 +201,7 @@
 #define PCI_CHIP_R300_AF      0x4146
 #define PCI_CHIP_R300_AG      0x4147
 #define PCI_CHIP_RV350_AP               0x4150
+#define PCI_CHIP_RV350_AQ               0x4151
 #define PCI_CHIP_RV350_AR               0x4152
 #define PCI_CHIP_RV350_AS               0x4153
 #define PCI_CHIP_RV350_NJ      0x4E4A
@@ -384,6 +385,7 @@
    case PCI_CHIP_R300_AF:
    case PCI_CHIP_R300_AG:
    case PCI_CHIP_RV350_AP:
+        case PCI_CHIP_RV350_AQ:
    case PCI_CHIP_RV350_AR:
    case PCI_CHIP_RV350_AS:
    case PCI_CHIP_RV350_NJ:



By the way a few hours ago, Aapo Tahkola implemented a patch that gives support to GL_ARB_texture_cube_map, also had done a little cleanup/bug fixes. Even so s3t textures are still a little broken so don't expect clear textures (only crisp textures at least if you are from objects (in games like ET, RTCW), if you are near the object s3tc work well (Bahh, known bug!!))


Thanks !

# lspci |grep -i ati
0000:00:10.0 VGA compatible controller: ATI Technologies Inc M11 NV [FireGL Mobility T2e] (rev 80)
# lspci -n|grep 0300
0000:00:10.0 Class 0300: 1002:4e56 (rev 80)

so it means my pci ID is "4e56" ? that's what I need to add to radeon_screen.c ? So it means I need to get mesa/dri source and manually compile, or maybe I can add the patch to the ebuild of it ?
Back to top
View user's profile Send private message
Iluminatus
Tux's lil' helper
Tux's lil' helper


Joined: 13 Nov 2004
Posts: 93
Location: Maia/Portugal

PostPosted: Wed Oct 26, 2005 11:43 pm    Post subject: Reply with quote

The best way to install r300, is to use all sources from CVS, although Xorg RC1, is recent enought, but you need mesa 6.4 , and drm also.

But the best way is to install mesa and drm from cvs!!, Check front page.

In your case the patch becomes a little weard because i don't know the mobilty family can be included here (SPEC name from pciids.sf.net).
Never seen no FireGL mobility working with r300, please then give some feedback!!

for a quick test you probably could do something like this

Code:

--- radeon_screen.c~   2005-10-27 01:39:42.000000000 +0100
+++ radeon_screen.c   2005-10-27 01:38:21.000000000 +0100
@@ -210,6 +210,7 @@
 #define PCI_CHIP_RV350_NP               0x4E50
 #define PCI_CHIP_RV350_NQ               0x4E51         /* Saphire 9600 256MB card */
 #define PCI_CHIP_RV350_NT               0x4E54
+#define PCI_CHIP_M11_NV         0x4E56         /*FireGl Mobility , i don't know if it's compatible, PCII from pciids.sf.net*/
 #define PCI_CHIP_RV350_NQ_2             0x4E71         /* Saphire 9600 256MB card - Second Head */
 #define PCI_CHIP_R300_ND      0x4E44
 #define PCI_CHIP_R300_NE      0x4E45
@@ -394,6 +395,7 @@
    case PCI_CHIP_RV350_NJ:
    case PCI_CHIP_RV350_NP:
    case PCI_CHIP_RV350_NT:
+   case PCI_CHIP_M11_NV:
    case PCI_CHIP_RV350_NQ:
 /*   case PCI_CHIP_RV350_NQ:  -- Should we have the second head in here too? */
    case PCI_CHIP_RV370_5460:
Back to top
View user's profile Send private message
fuoco
Guru
Guru


Joined: 23 May 2004
Posts: 386
Location: Israel

PostPosted: Thu Oct 27, 2005 7:59 am    Post subject: Reply with quote

I suppose the part that I need is the kernel module because I don't get anything under /dev/dri/
I will try to get a newer drm then and compile the 'radeon' kernel module.
Back to top
View user's profile Send private message
lroland
n00b
n00b


Joined: 28 Aug 2005
Posts: 32
Location: Copenhagen, Denmark

PostPosted: Thu Oct 27, 2005 8:18 am    Post subject: Reply with quote

fuoco wrote:
I suppose the part that I need is the kernel module because I don't get anything under /dev/dri/
I will try to get a newer drm then and compile the 'radeon' kernel module.


jJst did the same here and although I had DRI working with RC1 it does seam to work better with CVS. I will upgrade the guide for modular X as sson as I get the time.
Back to top
View user's profile Send private message
fuoco
Guru
Guru


Joined: 23 May 2004
Posts: 386
Location: Israel

PostPosted: Thu Oct 27, 2005 8:21 am    Post subject: Reply with quote

lroland wrote:
fuoco wrote:
I suppose the part that I need is the kernel module because I don't get anything under /dev/dri/
I will try to get a newer drm then and compile the 'radeon' kernel module.


jJst did the same here and although I had DRI working with RC1 it does seam to work better with CVS. I will upgrade the guide for modular X as sson as I get the time.


What did you do ? build the kernel module ? what did you do yo compile just the kernel module ?
Back to top
View user's profile Send private message
Iluminatus
Tux's lil' helper
Tux's lil' helper


Joined: 13 Nov 2004
Posts: 93
Location: Maia/Portugal

PostPosted: Thu Oct 27, 2005 12:07 pm    Post subject: Reply with quote

By the way,

i don't know if it's better or not, but can you chage
Quote:

mkdir /usr/src/r300
cd /usr/src/r300
export CVSROOT=":pserver:anonymous@cvs.freedesktop.org:/cvs/dri"
cvs checkout drm
cd drm
rm -rf shared
ln -s shared-core shared
cd linux-core
make radeon.o
cp *.ko /lib/modules/{kernel_version}/kernel/drivers/char/drm
modules-update


to

Quote:

mkdir /usr/src/r300
cd /usr/src/r300
export CVSROOT=":pserver:anonymous@cvs.freedesktop.org:/cvs/dri"
cvs checkout drm
cd drm
rm -rf shared
ln -s shared-core shared
cd linux-core
DRM_MODULES="radeon" make
cp *.ko /lib/modules/{kernel_version}/kernel/drivers/char/drm
modules-update


It's just how is written dri wiki. :(


About the dri part (fuoco), it's strange try to load drm, and radeon module before going to X. Does dmesg show anything strange.

Any sort fo errors in Xorg.log
Back to top
View user's profile Send private message
lroland
n00b
n00b


Joined: 28 Aug 2005
Posts: 32
Location: Copenhagen, Denmark

PostPosted: Thu Oct 27, 2005 12:24 pm    Post subject: Reply with quote

fuoco wrote:
What did you do ? build the kernel module ? what did you do yo compile just the kernel module ?

Updated the guide to include pointers on installation with xorg-server.
Back to top
View user's profile Send private message
Display posts from previous:   
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Unsupported Software All times are GMT
Goto page Previous  1, 2, 3, 4 ... 38, 39, 40  Next
Page 3 of 40

 
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