| View previous topic :: View next topic |
| Author |
Message |
Primozic
Apprentice
Joined: 11 Jun 2004
Posts: 186
Location: Dover, NH, USA
|
 Posted: Thu Jun 22, 2006 5:33 pm Post subject: |
 |
|
I've updated the ebuilds. Here are the changes:
- Added a CVS mesa-progs ebuild.
- Added a patch to Mesa that might fix some issues with 2.6.16 kernels.
- Moved the x11-drm patches to FILESDIR for easier maintenance.
I appreciate your feedback. Thanks for trying my ebuilds.
_________________
Interceptor: Intel Core 2 Duo 2.4GHz | AOpen i965GMt-LA Mini-ITX | 4GB PC2-5300 DDR2
Pursuit: AMD Geode NX 1500 1.0GHz | TYAN Tomcat K7M S2498AGNN FlexATX | 2GB PC2700 DDR |
|
| Back to top |
|
 |
DaiTengu
n00b
Joined: 21 Jul 2003
Posts: 21
Location: Appleton, WI
|
| Posted: Thu Jun 22, 2006 5:36 pm Post subject: |
|
|
| phuber wrote: | Hmm I had this too at one point.... I'm assuming you compile everything with the DRI useflag and have a correct xorg.conf?
make sure you have only one drm.ko and one radeon.ko
| Code: | $ find /lib/modules/`uname -r` -name "drm.ko"
/lib/modules/2.6.16-gentoo-r9/x11-drm/drm.ko
$ find /lib/modules/`uname -r` -name "radeon.ko"
/lib/modules/2.6.16-gentoo-r9/x11-drm/radeon.ko |
reboot after that to be sure you have the right modules loaded |
that's all OK ...
| Quote: | Also search for any WW and EE entries as well as for "r300" (there should be an entry saying it loaded r300_dri.so or something like that). Also, apart from the AIGLX-error-message, there should be another AIGLX message somewhere in the log.
Oh and look for something like this: "(II) RADEON(0): [dri] Found DRI library version 1.2.0 and kernel module version 1.25.0" too...
There could be some error in one of the messages listed above... |
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
I'm wondering if maybe there's something in my xorg.conf file I screwed up on ... I'll do some more digging to try and find out  |
|
| Back to top |
|
|
phuber
Tux's lil' helper
Joined: 19 Aug 2003
Posts: 106
Location: switzerland
|
| Posted: Thu Jun 22, 2006 5:38 pm Post subject: |
|
|
| Primozic wrote: | I've updated the ebuilds. Here are the changes:
- Added a CVS mesa-progs ebuild.
- Added a patch to Mesa that might fix some issues with 2.6.16 kernels.
- Moved the x11-drm patches to FILESDIR for easier maintenance.
I appreciate your feedback. Thanks for trying my ebuilds. |
cool, thanks...!
http://sturmartillerie.org/portage/ |
|
| Back to top |
|
|
Primozic
Apprentice
Joined: 11 Jun 2004
Posts: 186
Location: Dover, NH, USA
|
| Posted: Thu Jun 22, 2006 5:39 pm Post subject: |
|
|
| phuber wrote: | Oh and... I'm wondering wether or not quake3 is running on your systems... Here, neither q3 nor doom3 will start...  |
I just installed quake3-demo for testing purposes. It runs great on my end. 
I might try the doom3-demo out later.
_________________
Interceptor: Intel Core 2 Duo 2.4GHz | AOpen i965GMt-LA Mini-ITX | 4GB PC2-5300 DDR2
Pursuit: AMD Geode NX 1500 1.0GHz | TYAN Tomcat K7M S2498AGNN FlexATX | 2GB PC2700 DDR
Last edited by Primozic on Thu Jun 22, 2006 5:45 pm; edited 1 time in total |
|
| Back to top |
|
|
phuber
Tux's lil' helper
Joined: 19 Aug 2003
Posts: 106
Location: switzerland
|
| Posted: Thu Jun 22, 2006 5:41 pm Post subject: |
|
|
| DaiTengu wrote: |
I'm wondering if maybe there's something in my xorg.conf file I screwed up on ... I'll do some more digging to try and find out |
The config-instructions from the first page are still valid, have a look there first. |
|
| Back to top |
|
|
phuber
Tux's lil' helper
Joined: 19 Aug 2003
Posts: 106
Location: switzerland
|
| Posted: Thu Jun 22, 2006 5:49 pm Post subject: |
|
|
| Primozic wrote: | | phuber wrote: | | Oh and... I'm wondering wether or not quake3 is running on your systems... Here, neither q3 nor doom3 will start... |
I just installed quake3-demo for testing purposes. It runs great on my end.
I might try the doom3-demo out later. |
strange... demo works too, yet slow... |
|
| Back to top |
|
|
DaiTengu
n00b
Joined: 21 Jul 2003
Posts: 21
Location: Appleton, WI
|
| Posted: Thu Jun 22, 2006 6:09 pm Post subject: |
|
|
| phuber wrote: | | DaiTengu wrote: |
I'm wondering if maybe there's something in my xorg.conf file I screwed up on ... I'll do some more digging to try and find out |
The config-instructions from the first page are still valid, have a look there first. |
for some odd reason it's not loading r300_dri.so it goes right for libdri.so
 |
|
| Back to top |
|
|
phuber
Tux's lil' helper
Joined: 19 Aug 2003
Posts: 106
Location: switzerland
|
| Posted: Thu Jun 22, 2006 6:14 pm Post subject: |
|
|
the files should be in /usr/lib/dri
| Code: | $ l /usr/lib/dri
1541420 -rwxr-xr-x 1 root root 2486440 22. Jun 19:47 r200_dri.so
1541412 -rwxr-xr-x 1 root root 2385484 22. Jun 19:47 r300_dri.so
1541413 -rwxr-xr-x 1 root root 2450928 22. Jun 19:47 radeon_dri.so
$ equery b r300_dri.so
[ Searching for file(s) r300_dri.so in *... ]
media-libs/mesa-9999 (/usr/lib/dri/r300_dri.so) |
Xorg.0.log should contain this:
| Code: | (II) AIGLX: Loaded and initialized /usr/lib/dri/r300_dri.so
(II) GLX: Initialized DRI GL provider for screen 0 |
-----------------------------
About my quake/doom problem: I had this message:
| Code: | | libGL warning: 3D driver claims to not support visual 0x4b |
It disappeared after removing the "Composite" extension from xorg.conf
But quake/doom still claim they can't initialize OpenGL
At least the quake3 demo now seems to run at an acceptable speed... :-\ |
|
| Back to top |
|
|
Primozic
Apprentice
Joined: 11 Jun 2004
Posts: 186
Location: Dover, NH, USA
|
| Posted: Thu Jun 22, 2006 6:36 pm Post subject: |
|
|
DOOM3 retail initializes and runs here, although it is unplayable due to a very low number of frames per second and many graphical artifacts.
Here's my xorg.conf is case anyone is interested:
http://sturmartillerie.org/portage/xorg.conf
_________________
Interceptor: Intel Core 2 Duo 2.4GHz | AOpen i965GMt-LA Mini-ITX | 4GB PC2-5300 DDR2
Pursuit: AMD Geode NX 1500 1.0GHz | TYAN Tomcat K7M S2498AGNN FlexATX | 2GB PC2700 DDR |
|
| Back to top |
|
|
phuber
Tux's lil' helper
Joined: 19 Aug 2003
Posts: 106
Location: switzerland
|
| Posted: Thu Jun 22, 2006 6:47 pm Post subject: |
|
|
I emerged quake3-9999 from svn which didn't change anything. Then tried again with USE=-sdl because the actual errors are sdl-related. Maybe reemerging sdl may help...
I'm now trying with your Module section -- is there a reason it looks like this? mine looks somewhat different... |
|
| Back to top |
|
|
Primozic
Apprentice
Joined: 11 Jun 2004
Posts: 186
Location: Dover, NH, USA
|
| Posted: Thu Jun 22, 2006 6:53 pm Post subject: |
|
|
| phuber wrote: | | I'm now trying with your Module section -- is there a reason it looks like this? mine looks somewhat different... |
No particular reason, it's just barebones. I use Openbox, so I don't need anything fancy.
_________________
Interceptor: Intel Core 2 Duo 2.4GHz | AOpen i965GMt-LA Mini-ITX | 4GB PC2-5300 DDR2
Pursuit: AMD Geode NX 1500 1.0GHz | TYAN Tomcat K7M S2498AGNN FlexATX | 2GB PC2700 DDR |
|
| Back to top |
|
|
DaiTengu
n00b
Joined: 21 Jul 2003
Posts: 21
Location: Appleton, WI
|
| Posted: Thu Jun 22, 2006 7:08 pm Post subject: |
|
|
Feh, Direct rendering is still off.
here's my Xorg.0.log:
EDIT: hang on, finding a place to post it, it's too long for the forums
EDIT EDIT: http://war-ensemble.com/tengu/xorg |
|
| Back to top |
|
|
Primozic
Apprentice
Joined: 11 Jun 2004
Posts: 186
Location: Dover, NH, USA
|
| Posted: Thu Jun 22, 2006 7:36 pm Post subject: |
|
|
Hmm. Try something like this as root:
| Code: | | echo -e 'R300_FORCE_R300="1"' >> /etc/env.d/00local |
After that, logout of both X and your tty session, then login and start X again.
_________________
Interceptor: Intel Core 2 Duo 2.4GHz | AOpen i965GMt-LA Mini-ITX | 4GB PC2-5300 DDR2
Pursuit: AMD Geode NX 1500 1.0GHz | TYAN Tomcat K7M S2498AGNN FlexATX | 2GB PC2700 DDR |
|
| Back to top |
|
|
DaiTengu
n00b
Joined: 21 Jul 2003
Posts: 21
Location: Appleton, WI
|
| Posted: Thu Jun 22, 2006 7:45 pm Post subject: |
|
|
| Primozic wrote: | Hmm. Try something like this as root:
| Code: | | echo -e 'R300_FORCE_R300="1"' >> /etc/env.d/00local |
After that, logout of both X and your tty session, then login and start X again. |
yeah, I did that. it's now loading the r300_dri.so module, but direct rendering is still off
my xorg.0.log: http://war-ensemble.com/tengu/xorg/Xorg.0.log |
|
| Back to top |
|
|
Primozic
Apprentice
Joined: 11 Jun 2004
Posts: 186
Location: Dover, NH, USA
|
| Posted: Thu Jun 22, 2006 8:22 pm Post subject: |
|
|
I don't know man, I don't see any problems. Your X log looks very similar to mine:
http://sturmartillerie.org/portage/Xorg.0.log
Maybe it's a permission problem? Try logging in to X as root and see if you get direct rendering.
_________________
Interceptor: Intel Core 2 Duo 2.4GHz | AOpen i965GMt-LA Mini-ITX | 4GB PC2-5300 DDR2
Pursuit: AMD Geode NX 1500 1.0GHz | TYAN Tomcat K7M S2498AGNN FlexATX | 2GB PC2700 DDR |
|
| Back to top |
|
|
phuber
Tux's lil' helper
Joined: 19 Aug 2003
Posts: 106
Location: switzerland
|
| Posted: Thu Jun 22, 2006 9:51 pm Post subject: |
|
|
| Code: | | (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found |
Try to get rid of that -- apart from the above message, the log looks exactly like mine... |
|
| Back to top |
|
|
phuber
Tux's lil' helper
Joined: 19 Aug 2003
Posts: 106
Location: switzerland
|
| Posted: Thu Jun 22, 2006 10:09 pm Post subject: |
|
|
| This is only getting stranger... q3demo ran fine. After reemerging my sdl packages (because q3retail was complaining about some sdl things), q3retail still does not work and q3demo suddenly has an almost not responding mouse... wondering what I've broken now... |
|
| Back to top |
|
|
phuber
Tux's lil' helper
Joined: 19 Aug 2003
Posts: 106
Location: switzerland
|
| Posted: Fri Jun 23, 2006 6:25 am Post subject: |
|
|
was trying to reemerge mesa-9999 which worked yesterday but now... *confused*
| Code: | cd drivers/dri ; make
make[4]: Entering directory `/var/tmp/portage/mesa-9999/work/Mesa/src/mesa/drivers/dri'
mkdir /var/tmp/portage/mesa-9999/image//usr/lib
echo r200 r300 radeon
r200 r300 radeon
r200
make[5]: Entering directory `/var/tmp/portage/mesa-9999/work/Mesa/src/mesa/drivers/dri/r200'
install r200_dri.so /var/tmp/portage/mesa-9999/image//usr/lib
make[5]: Leaving directory `/var/tmp/portage/mesa-9999/work/Mesa/src/mesa/drivers/dri/r200'
r300
make[5]: Entering directory `/var/tmp/portage/mesa-9999/work/Mesa/src/mesa/drivers/dri/r300'
install r300_dri.so /var/tmp/portage/mesa-9999/image//usr/lib
make[5]: Leaving directory `/var/tmp/portage/mesa-9999/work/Mesa/src/mesa/drivers/dri/r300'
radeon
make[5]: Entering directory `/var/tmp/portage/mesa-9999/work/Mesa/src/mesa/drivers/dri/radeon'
install radeon_dri.so /var/tmp/portage/mesa-9999/image//usr/lib
make[5]: Leaving directory `/var/tmp/portage/mesa-9999/work/Mesa/src/mesa/drivers/dri/radeon'
make[4]: Leaving directory `/var/tmp/portage/mesa-9999/work/Mesa/src/mesa/drivers/dri'
make[3]: Leaving directory `/var/tmp/portage/mesa-9999/work/Mesa/src/mesa'
install -d /usr/local/include/GL
ACCESS DENIED mkdir: /usr/local/include/GL
install: kann Verzeichnis â/usr/local/include/GLâ nicht anlegen: Keine Berechtigung
make[2]: *** [install] Error 1
make[2]: Leaving directory `/var/tmp/portage/mesa-9999/work/Mesa/src/mesa'
make[1]: *** [install] Error 1
make[1]: Leaving directory `/var/tmp/portage/mesa-9999/work/Mesa/src'
make: *** [install] Error 1
!!! ERROR: media-libs/mesa-9999 failed.
Call stack:
ebuild.sh, line 1539: Called dyn_install
ebuild.sh, line 1013: Called src_install
mesa-9999.ebuild, line 228: Called die
!!! Installation failed
!!! If you need support, post the topmost build error, and the call stack if relevant.
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/var/log/sandbox/sandbox-media-libs_-_mesa-9999-18014.log"
mkdir: /usr/local/include/GL
--------------------------------------------------------------------------------
!!! This ebuild is from an overlay: '/home/phuber/Subversion/mesa-cvs' |
|
|
| Back to top |
|
|
sefi
n00b
Joined: 23 Jun 2006
Posts: 14
|
| Posted: Fri Jun 23, 2006 7:19 am Post subject: |
|
|
Hi Primozic,
thank you for your ebuilds. They worked on an i386 system for me. But unfortunately I got problems on my amd64 system.
sandbox complains about the makefile trying to unlink libdrm.pc while compiling libdrm-9999.
| Quote: |
ACCESS DENIED unlink: /usr/lib64/pkgconfig/libdrm.pc
/bin/install: cannot remove `/usr/lib64/pkgconfig/libdrm.pc': Permission denied
|
As I am not familiar with the autotools (and this makefile certainly is generated by those) I would be glad if someone with more experience could delve into that and see what is wrong.
Cheers,
Philipp |
|
| Back to top |
|
|
DaiTengu
n00b
Joined: 21 Jul 2003
Posts: 21
Location: Appleton, WI
|
| Posted: Fri Jun 23, 2006 9:59 am Post subject: |
|
|
| phuber wrote: | | Code: | | (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found |
Try to get rid of that -- apart from the above message, the log looks exactly like mine... |
That's for the second monitor, my card has a Digital Video Out which isn't used.
I'm completely stumped. I have no freaking clue as to what to do |
|
| Back to top |
|
|
tchak
Tux's lil' helper
Joined: 19 Aug 2003
Posts: 124
Location: France/Russia
|
| Posted: Fri Jun 23, 2006 1:04 pm Post subject: |
|
|
| sefi wrote: | Hi Primozic,
thank you for your ebuilds. They worked on an i386 system for me. But unfortunately I got problems on my amd64 system.
sandbox complains about the makefile trying to unlink libdrm.pc while compiling libdrm-9999.
| Quote: |
ACCESS DENIED unlink: /usr/lib64/pkgconfig/libdrm.pc
/bin/install: cannot remove `/usr/lib64/pkgconfig/libdrm.pc': Permission denied
|
As I am not familiar with the autotools (and this makefile certainly is generated by those) I would be glad if someone with more experience could delve into that and see what is wrong.
Cheers,
Philipp |
Same error here. A workaround is to emerge libdrm with FEATURES="-sandbox".
Primozic :
As for my errors, I steel have some artifacts. You are right with EXA their is looooots more, but even without EXA I have some. Even without DRI I steel have artifacts...
Am I alone in this situation?
_________________
maybe this world is another planet's hell...
Athlon64 | ATI Mobility Radeon 9700 | Netgear (Prism54) + ASUS (USB2 ZD1211) |
|
| Back to top |
|
|
Primozic
Apprentice
Joined: 11 Jun 2004
Posts: 186
Location: Dover, NH, USA
|
| Posted: Fri Jun 23, 2006 1:43 pm Post subject: |
|
|
| phuber wrote: | | was trying to reemerge mesa-9999 which worked yesterday but now... *confused* |
Hmm, strange. I get the same thing. It looks like they changed a Makefile and it messed up the ebuild. I'll see what I can do, but I'm not good with this sort of thing.
_________________
Interceptor: Intel Core 2 Duo 2.4GHz | AOpen i965GMt-LA Mini-ITX | 4GB PC2-5300 DDR2
Pursuit: AMD Geode NX 1500 1.0GHz | TYAN Tomcat K7M S2498AGNN FlexATX | 2GB PC2700 DDR |
|
| Back to top |
|
|
Primozic
Apprentice
Joined: 11 Jun 2004
Posts: 186
Location: Dover, NH, USA
|
| Posted: Fri Jun 23, 2006 3:25 pm Post subject: |
|
|
Mesa has been fixed in the latest tarball. It looks like the Mesa developers are moving away from using the installmesa script, but the ebuild doesn't like it, so I ended up adding a patch.
I'll look into the AMD64 libdrm issue later.
_________________
Interceptor: Intel Core 2 Duo 2.4GHz | AOpen i965GMt-LA Mini-ITX | 4GB PC2-5300 DDR2
Pursuit: AMD Geode NX 1500 1.0GHz | TYAN Tomcat K7M S2498AGNN FlexATX | 2GB PC2700 DDR |
|
| Back to top |
|
|
Primozic
Apprentice
Joined: 11 Jun 2004
Posts: 186
Location: Dover, NH, USA
|
| Posted: Fri Jun 23, 2006 4:48 pm Post subject: |
|
|
Updated the libdrm ebuild in the latest tarball. This may fix the AMD64 sandbox issue. Please test. I can't, since I don't have an AMD64 box.
EDIT: Ugh, these CVS changes are killing me!
| Code: | todd@geode ~ $ LIBGL_DEBUG=all glxinfo
libGL error: dlopen /usr/X11R6/lib/modules/dri/r300_dri.so failed (/usr/X11R6/lib/modules/dri/r300_dri.so: cannot open shared object file: No such file or directory)
libGL error: unable to find driver: r300_dri.so |
Working on another fix...
Fixed with a patch that changes the default install directories.
_________________
Interceptor: Intel Core 2 Duo 2.4GHz | AOpen i965GMt-LA Mini-ITX | 4GB PC2-5300 DDR2
Pursuit: AMD Geode NX 1500 1.0GHz | TYAN Tomcat K7M S2498AGNN FlexATX | 2GB PC2700 DDR |
|
| Back to top |
|
|
sefi
n00b
Joined: 23 Jun 2006
Posts: 14
|
| Posted: Fri Jun 23, 2006 9:09 pm Post subject: |
|
|
Hi Primozic,
thank you, the new ebuilds worked for me. A problem followed though. I didn't get direct rendering to work at first glance. A quick search via google gave me the hint to export R300_FORCE_R300 before starting X. So I did export R300_FORCE_300=1 and gladly that enabled direct rendering for me.
Now there is only one problem remaining which is unfortunalety due to the fact that I have a Radeon 9800 SE which has 8 pixel pipelines but 4 of them should be disabled (which classified it to be an SE version). If all 8 are enabled (which seems to be the default with mesa), I get funky rectangles which are ordered in a chess pattern that have very regular artifacts in them (the same happened when I tried to enable all 8 pixel pipelines in Windows).
So does anyone know how to set the driver to use my graphic card as an SE version properly? |
|
| Back to top |
|
|
|
Unsupported Software
