From: Sergey V. O. <ser...@cl...> - 2003-11-16 01:36:23
|
Hi all I just took the R200 snapshot and trying to run in on Radeon R250 Lf (Mobility). First, I encountered the problem with ABI version (6 vs 7) but after taking XFree86 executable from some well-known place (mentioned in FAQ) XFree finally took off (first question - would it be possible to include this binary into R200 snapshots - it is necessary anyway). Now I am trying to run glxinfo - and it says there is no DRI. What could this be? I even tried to say explicitly LD_PRELOAD=... (pointing to libGL.so.1.2 shipped with the snapshot). Still no direct rendering. What could this be? XFree86.0.log says I _do_ have dri enabled. (funny enough, the main reason to try DRI snapshots was broken dynamic access to GL in Fedora's libGL - no way to play Half-Life:). -- Sergey |
From: Sergey V. O. <ser...@cl...> - 2003-11-16 01:59:52
|
Well, in my previous mail I was citing the wrong XFree86.0.log. The right one shows that DRI is actually disabled. And dmesg gives me this: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held [drm:radeon_unlock] *ERROR* Process 5985 using kernel context 0 Googling around shows that I am not the only one with the problem of that kind. Is it curable? Is current R200 driver binary snapshot broken? -- Sergey |
From: Sergey V. O. <ser...@cl...> - 2003-11-18 09:26:24
|
> > Well, in my previous mail I was citing the wrong XFree86.0.log. The > > right one shows that DRI is actually disabled. And dmesg gives me this: > > > > [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held > > [drm:radeon_unlock] *ERROR* Process 5985 using kernel context 0 > > This is usually a symptom, not a cause. Look at the server log. OK. Here it is. % grep -i agp /var/log/XFree86.0.log | tail -9 (--) Chipset ATI Radeon Mobility 9000 (M9) Lf (AGP) found (**) RADEON(0): Option "AGPMode" "4" (--) RADEON(0): Chipset: "ATI Radeon Mobility 9000 (M9) Lf (AGP)" (ChipID = 0x4c66) (II) RADEON(0): AGP card detected (**) RADEON(0): Using AGP 4x mode (II) RADEON(0): AGP Fast Write disabled by default (WW) RADEON(0): [agp] AGP not available (EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI. (II) RADEON(0): [agp] You may want to make sure the agpgart kernel module So, first thing I found - X driver does not autoload agpgart on startup. While the "original" Fedora does (I use standard Fedora kernel, no tweaks, just FYI). This is the probem #1. OK, not a big problem - I loaded agpgart manually and started X again. Now XFree.0.log says "Direct rendering enabled". But still glxinfo is not happy: % LD_LIBRARY_PATH=/usr/X11R6/lib/tls/libGL.so.1.2 glxinfo |grep direct direct rendering: No OpenGL renderer string: Mesa GLX Indirect I explicitly pointed to the libGL.so shipped with dri snapshots (just in case it uses the old library for some reason...) -- Sergey |
From: Michel <mi...@da...> - 2003-11-19 00:44:24
|
On Tue, 2003-11-18 at 10:26, Sergey V. Oudaltsov wrote: >=20 > (WW) RADEON(0): [agp] AGP not available > (EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI. > (II) RADEON(0): [agp] You may want to make sure the agpgart kernel > module >=20 > So, first thing I found - X driver does not autoload agpgart on startup. Stock drivers never have. You may want to help with the kernel patches floating around for this? > % LD_LIBRARY_PATH=3D/usr/X11R6/lib/tls/libGL.so.1.2 glxinfo |grep direct > direct rendering: No Does it give more information with LIBGL_DEBUG=3Dverbose ? --=20 Earthling Michel D=C3=A4nzer | Debian (powerpc), X and DRI develop= er Software libre enthusiast | http://svcs.affero.net/rm.php?r=3Ddaenzer |
From: Sergey V. O. <ser...@cl...> - 2003-11-19 00:57:44
|
> Stock drivers never have. You may want to help with the kernel patches > floating around for this? Well, I don't really know. I am not a big kernel expert. I just say what I see: when I run "standard" Fedora X driver - agpgart is loaded without my intervention. With dri snapshots - I have to load it myself. That's just it. > Does it give more information with LIBGL_DEBUG=verbose ? Tried a couple of hours ago: # LIBGL_DEBUG=verbose glxinfo | head libGL error: XF86DRIQueryDirectRenderingCapable returned false name of display: :0.0 display: :0 screen: 0 direct rendering: No Does this make any sense? -- Sergey |
From: F. <jrf...@tu...> - 2003-11-19 13:23:35
|
On Wed, Nov 19, 2003 at 12:57:25AM +0000, Sergey V. Oudaltsov wrote: > > > Stock drivers never have. You may want to help with the kernel patches > > floating around for this? > Well, I don't really know. I am not a big kernel expert. I just say what > I see: when I run "standard" Fedora X driver - agpgart is loaded without > my intervention. With dri snapshots - I have to load it myself. That's > just it. That's very odd. AFAIK, unless agpgart is statically linked in the kernel (i.e., not a module), you _always_ need a line in /etc/modules.conf as: pre-install r200 modprobe -k agpgart Otherwise agpgart won't be loaded. The only explanation for a different behavior is if Fedora's kernel includes some patch to do this automagiclly... José Fonseca |
From: Sergey V. O. <ser...@cl...> - 2003-11-19 14:02:55
|
> pre-install r200 modprobe -k agpgart Just one question. Should it be "r200" or "radeon"? Thanks for the config line, I'll try it. Sergey |
From: F. <jrf...@tu...> - 2003-11-19 15:08:08
|
On Wed, Nov 19, 2003 at 02:02:50PM +0000, Sergey V. Oudaltsov wrote: > > pre-install r200 modprobe -k agpgart > Just one question. Should it be "r200" or "radeon"? It should be "radeon" actually. My bad... Jose Fonseca |
From: Sergey V. O. <ser...@cl...> - 2003-11-19 15:25:52
|
> It should be "radeon" actually. My bad... I knew! I knew! :) Well, anyway - this does not explain why libGL cannot find dri while xfree86.0.log says it is there... Sergey |
From: F. <jrf...@tu...> - 2003-11-19 15:40:24
|
On Wed, Nov 19, 2003 at 03:25:49PM +0000, Sergey V. Oudaltsov wrote: > > It should be "radeon" actually. My bad... > I knew! I knew! :) > > Well, anyway - this does not explain why libGL cannot find dri while > xfree86.0.log says it is there... > > Sergey It must be the TLS thingy. Do ldd /usr/bin/X11/glxinfo It should point to the right one. If it points to */tls/libGl.* then rename that "tls" into something else, until it uses the right one. If you want to experiment with environent vars, you can do that with the above command too: LD_LIBRARY_PATH=... ldd /usr/bin/X11/glxinfo But from what I could understand, for with directory in the search path, ld.so will first try to check for a 'tls' subdir for the library, and I don't think there is a way to prevent that with environment vars... Probably in the long run, the install.sh script should install a tls/liGL too, or at least rename the existing one... Jose Fonseca |
From: Sergey V. O. <ser...@cl...> - 2003-11-19 15:48:28
|
# ldd /usr/bin/X11/glxinfo ... libGL.so.1 => /usr/X11R6/lib/tls/libGL.so.1 (0x00541000) ... And this symlink points to the library (libGL.so.1.2) shipped with the binary snapshot (well, the install.sh script had some problem - but I fixed it manually). > LD_LIBRARY_PATH=... ldd /usr/bin/X11/glxinfo I did it. See my previous posts:) $ LD_LIBRARY_PATH=/home/svu/dripkg/GL/libGL.so.1.2 glxinfo | grep irect direct rendering: No OpenGL renderer string: Mesa GLX Indirect That's it. -- Sergey |
From: Sergey V. O. <ser...@cl...> - 2003-11-20 23:06:27
|
Yess! I found! Strace is the girl's best friend! r200_dri.so is linked against libexpat.so.1 - while Fedora only provides libexpat.so.0. That is why libGL.so cannot load r200_dri.so - and reports missing DR! At the moment, I just symlinked libexpat.so.0 to libexpat.so.1 - and got my DRI working. Yahooo! -- Sergey |
From: Felix <fx...@gm...> - 2003-11-21 14:52:44
|
On Thu, 20 Nov 2003 23:06:23 +0000 "Sergey V. Oudaltsov" <ser...@cl...> wrote: > Yess! I found! Strace is the girl's best friend! > > r200_dri.so is linked against libexpat.so.1 - while Fedora only provides > libexpat.so.0. That is why libGL.so cannot load r200_dri.so - and > reports missing DR! At the moment, I just symlinked libexpat.so.0 to > libexpat.so.1 - and got my DRI working. Yahooo! That's strange. You should have seen a dlopen-error in the output of # LIBGL_DEBUG=verbose glxinfo The error message you got would indicate that something else was wrong at that time: libGL error: XF86DRIQueryDirectRenderingCapable returned false José, many people are having this libexpat problem. What's the recommended method to add some sort of trouble-shooting entry in the Wiki? The TroubleShooting template seems to be tailored for application-specific problems. We could use it though to make one page InstallationProblems to cover typical installation problems. > > -- > Sergey Regards, Felix ------------ __\|/__ ___ ___ ------------------------- Felix ___\_e -_/___/ __\___/ __\_____ You can do anything, Kühling (_____\Ä/____/ /_____/ /________) just not everything fx...@gm... \___/ \___/ U at the same time. |
From: F. <jrf...@tu...> - 2003-11-21 15:09:56
|
Felix, On Fri, Nov 21, 2003 at 03:51:40PM +0100, Felix Kühling wrote: > > José, many people are having this libexpat problem. What's the > recommended method to add some sort of trouble-shooting entry in the > Wiki? The TroubleShooting template seems to be tailored for > application-specific problems. We could use it though to make one page > InstallationProblems to cover typical installation problems. This is something that only happens with the binary snapshots - when the DRI drivers are packaged by a distribution or built from source these sort of problems won't happen - so I also agree think these should be kept seperate in a single Wiki page, e.g., SnapshotsCaveats (or even in a subsection of a more general InstallationProblems page if you like), and mentioned in the Download page. This makes even more sense as these sort of problems are very localized in time (basically they appear when compatability is being broken upstream on one of the driver dependencies, or locally in our CVS), so it doesn't make sense to have an individual page for each problem as they'll disapear eventually. Jose Fonseca |
From: Ian R. <id...@us...> - 2003-11-17 18:52:48
|
Sergey V. Oudaltsov wrote: > I just took the R200 snapshot and trying to run in on Radeon R250 Lf > (Mobility). First, I encountered the problem with ABI version (6 vs 7) > but after taking XFree86 executable from some well-known place > (mentioned in FAQ) XFree finally took off (first question - would it be > possible to include this binary into R200 snapshots - it is necessary > anyway). > > Now I am trying to run glxinfo - and it says there is no DRI. What could > this be? I even tried to say explicitly LD_PRELOAD=... (pointing to > libGL.so.1.2 shipped with the snapshot). Still no direct rendering. What > could this be? XFree86.0.log says I _do_ have dri enabled. > > (funny enough, the main reason to try DRI snapshots was broken dynamic > access to GL in Fedora's libGL - no way to play Half-Life:). I don't remember the exact details, but I believe Fedora has separate TLS enabled libraries. You may be picking that up instead of the new non-TLS libGL. Could you be more specific what you mean by "problem with ABI version"? |