Re: [Dri-users] X hangs when starting glxgears on r350
radeon 9800 card still lockup with r300 driver. If you first run an X server with fglrx, then leave and launch xorg with r300 driver you shouldn't have any lockup. I am still looking at what fglrx does and i have a couple of guilty reg but so far after ten thousand reboot dump i haven't found the magic incantation. Help on this is more than welcome :) Jerome Glisse --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-users] X hangs when starting glxgears on r350
On Monday 25 July 2005 10:18, Jerome Glisse wrote: radeon 9800 card still lockup with r300 driver. If you first run an X server with fglrx, then leave and launch xorg with r300 driver you shouldn't have any lockup. I see. Will try that this evening. I am still looking at what fglrx does and i have a couple of guilty reg but so far after ten thousand reboot dump i haven't found the magic incantation. You beat me by far: I just did tens of reboots :) Help on this is more than welcome :) Sure. What could I do with my (very limited) knowledge of drm ?? Nicolas. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-users] X hangs when starting glxgears on r350
On 7/25/05, Bellido Nicolas [EMAIL PROTECTED] wrote: On Monday 25 July 2005 10:18, Jerome Glisse wrote: radeon 9800 card still lockup with r300 driver. If you first run an X server with fglrx, then leave and launch xorg with r300 driver you shouldn't have any lockup. I see. Will try that this evening. I am still looking at what fglrx does and i have a couple of guilty reg but so far after ten thousand reboot dump i haven't found the magic incantation. You beat me by far: I just did tens of reboots :) Help on this is more than welcome :) Sure. What could I do with my (very limited) knowledge of drm ?? First make sure you know how to dump reg, i use a tools from Vladimir: http://volodya-project.sourceforge.net/hw_script.php Then i will send you latter(when i access the computer on which they are) my script which use hw_script to dump reg. Basicly i dump all reg before starting anythings (after boot), then i start xserver with fglrx and i dump all reg, then i start x with r300 and i dump all reg. I have done this several time, running different apps each time thus i have some change in dump (maybe i am wrong doing so). Then i look at what reg are always the same in some fglrx dump and same in r300 dump (after fglrx) and different in r300 dump (r300 dump without previously run fglrx). With that i get a list of reg that fglrx always set in the same way (and that are preserved) and r300 doesn't. But some of them are status reg and finding which register(s) are needed to set a particular status is painfull and boring, you have to write in other regs hoping to no lock the card (which often lock) and now i am dealing with all this regs (as i already tested all non-status reg, and i think i haven't missed one, i hope :)) If anyone have a better procedure to track differences btw radeon/r300 2d driver from xorg and fglrx (2d driver) ? Jerome Glisse --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 3862] Seg. fault with r128 driver
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=3862 --- Additional Comments From [EMAIL PROTECTED] 2005-07-25 20:49 --- Created an attachment (id=3136) -- (https://bugs.freedesktop.org/attachment.cgi?id=3136action=view) Xorg conf. file -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 3862] Seg. fault with r128 driver
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=3862 --- Additional Comments From [EMAIL PROTECTED] 2005-07-25 20:51 --- Created an attachment (id=3137) -- (https://bugs.freedesktop.org/attachment.cgi?id=3137action=view) Xorg log file -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 3862] Seg. fault with r128 driver
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=3862 --- Additional Comments From [EMAIL PROTECTED] 2005-07-25 20:55 --- I've just seen a warning when inserting r128: PCI: Unable to reserve mem region #1:[EMAIL PROTECTED] for device :01:00.0 This seems uncritical warning, because the module keeps inserted and the whole X-system works ok with no error at launch time. But perhaps this concerns the reported bug on DRM-system. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-users] X hangs when starting glxgears on r350
On Monday 25 July 2005 11:33, Jerome Glisse wrote: If anyone have a better procedure to track differences btw radeon/r300 2d driver from xorg and fglrx (2d driver) ? I'm not used at all to work on x86 processors, nor am I with PCI or AGP, so what follows may be complete nonsense... Isn't it also important to know the exact stream of commands sent to the core ? I mean, as it is apparently known where the registers are, or what the commands to send to the gpu are, isn't it possible to put some watchpoints at specific locations, and see whet fglrx is doing ? Now, I'm not sure if x86 supports watchpoint on iomem... Nicolas --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-users] X hangs when starting glxgears on r350
On 7/25/05, Bellido Nicolas [EMAIL PROTECTED] wrote: On Monday 25 July 2005 11:33, Jerome Glisse wrote: If anyone have a better procedure to track differences btw radeon/r300 2d driver from xorg and fglrx (2d driver) ? I'm not used at all to work on x86 processors, nor am I with PCI or AGP, so what follows may be complete nonsense... Isn't it also important to know the exact stream of commands sent to the core ? I mean, as it is apparently known where the registers are, or what the commands to send to the gpu are, isn't it possible to put some watchpoints at specific locations, and see whet fglrx is doing ? Now, I'm not sure if x86 supports watchpoint on iomem... I don't think neither that you can put watchpoint or even capture what is written to the reg but this would help a lot as the key is there :) Anyone with more knowledge on this ? A modified X server ? Jerome Glisse --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-users] X hangs when starting glxgears on r350
On Mon, 25 Jul 2005 08:59:53 +0200 Bellido Nicolas [EMAIL PROTECTED] wrote: On Monday 25 July 2005 00:47, Roland Scheidegger wrote: Bellido Nicolas wrote: When the radeon module is loaded, i get in the kernel logs: Linux agpgart interface v0.101 (c) Dave Jones agpgart: Detected VIA KT880 chipset agpgart: AGP aperture is 128M @ 0xe000 [drm] Initialized drm 1.0.0 20040925 ACPI: PCI Interrupt :01:00.0[A] - GSI 16 (level, low) - IRQ 16 [drm] Initialized radeon 1.16.0 20050311 on minor 0: ATI Technologies Inc Radeon R350 [Radeon 9800 Pro] This is just a shot in the dark, have you built the drm module too? The r300 driver needs a new version too. I don't know what would happen if you don't build it however, but it certainly wouldn't work. That's the version string I have in radeon_drv.c: $ grep 20050311 linux-core/radeon_drv.h #define DRIVER_DATE 20050311 Checked out yesterday from drm cvs on freedesktop.org. In case it helps, i just insmoded the drm module with debug=1. Here are the last lines ok kmsg. [drm:drm_ioctl] pid=9684, cmd=0x6444, nr=0x44, dev 0xe200, auth=1 [drm:radeon_cp_idle] [drm:radeon_do_cp_idle] [drm:drm_ioctl] pid=9684, cmd=0xc0286429, nr=0x29, dev 0xe200, auth=1 [drm:radeon_freelist_get] done_age = 236 [drm:drm_ioctl] pid=9684, cmd=0xc010644d, nr=0x4d, dev 0xe200, auth=1 [drm:radeon_cp_indirect] indirect: idx=13 s=0 e=88 d=0 [drm:radeon_cp_dispatch_indirect] indirect: buf=13 s=0x0 e=0x58 [drm:drm_ioctl] pid=9684, cmd=0xc010644d, nr=0x4d, dev 0xe200, auth=1 [drm:radeon_cp_indirect] indirect: idx=13 s=88 e=104 d=1 [drm:radeon_cp_dispatch_indirect] indirect: buf=13 s=0x58 e=0x68 [drm:drm_ioctl] pid=9684, cmd=0x6444, nr=0x44, dev 0xe200, auth=1 [drm:radeon_cp_idle] [drm:radeon_do_cp_idle] [drm:drm_ioctl] pid=9684, cmd=0xc0286429, nr=0x29, dev 0xe200, auth=1 [drm:radeon_freelist_get] done_age = 237 [drm:drm_ioctl] pid=9684, cmd=0xc010644d, nr=0x4d, dev 0xe200, auth=1 [drm:radeon_cp_indirect] indirect: idx=14 s=0 e=176 d=0 [drm:radeon_cp_dispatch_indirect] indirect: buf=14 s=0x0 e=0xb0 [drm:drm_ioctl] pid=9684, cmd=0xc010644d, nr=0x4d, dev 0xe200, auth=1 [drm:radeon_cp_indirect] indirect: idx=14 s=176 e=192 d=1 [drm:radeon_cp_dispatch_indirect] indirect: buf=14 s=0xb0 e=0xc0 [drm:drm_ioctl] pid=9684, cmd=0x6444, nr=0x44, dev 0xe200, auth=1 [drm:radeon_cp_idle] [drm:radeon_do_cp_idle] [drm:drm_ioctl] pid=9684, cmd=0xc0286429, nr=0x29, dev 0xe200, auth=1 [drm:radeon_freelist_get] done_age = 238 [drm:drm_ioctl] pid=9684, cmd=0xc010644d, nr=0x4d, dev 0xe200, auth=1 [drm:radeon_cp_indirect] indirect: idx=15 s=0 e=124 d=0 [drm:radeon_cp_dispatch_indirect] indirect: buf=15 s=0x0 e=0x7c [drm:drm_ioctl] pid=9684, cmd=0xc010644d, nr=0x4d, dev 0xe200, auth=1 [drm:radeon_cp_indirect] indirect: idx=15 s=128 e=144 d=1 [drm:radeon_cp_dispatch_indirect] indirect: buf=15 s=0x80 e=0x90 [drm:drm_ioctl] pid=9684, cmd=0x6444, nr=0x44, dev 0xe200, auth=1 [drm:radeon_cp_idle] [drm:radeon_do_cp_idle] [drm:drm_ioctl] pid=9684, cmd=0xc0286429, nr=0x29, dev 0xe200, auth=1 [drm:radeon_freelist_get] done_age = 239 [drm:drm_ioctl] pid=9684, cmd=0xc010644d, nr=0x4d, dev 0xe200, auth=1 [drm:radeon_cp_indirect] indirect: idx=16 s=0 e=108 d=0 [drm:radeon_cp_dispatch_indirect] indirect: buf=16 s=0x0 e=0x6c [drm:drm_ioctl] pid=9684, cmd=0xc010644d, nr=0x4d, dev 0xe200, auth=1 [drm:radeon_cp_indirect] indirect: idx=16 s=112 e=128 d=1 [drm:radeon_cp_dispatch_indirect] indirect: buf=16 s=0x70 e=0x80 [drm:drm_ioctl] pid=9684, cmd=0x6444, nr=0x44, dev 0xe200, auth=1 [drm:radeon_cp_idle] [drm:radeon_do_cp_idle] [drm:drm_ioctl] pid=9733, cmd=0x4008642a, nr=0x2a, dev 0xe200, auth=1 [drm:drm_lock] 3 (pid 9733) requests lock (0x0001), flags = 0x [drm:drm_lock] 3 has lock [drm:drm_ioctl] pid=9733, cmd=0x40106450, nr=0x50, dev 0xe200, auth=1 [drm:radeon_cp_cmdbuf] RADEON_CMD_SCALARS2 [drm:radeon_cp_cmdbuf] *ERROR* bad cmd_type 0 at e08fa024 r300_do_cp_cmdbuf doesnt get called... -- Aapo Tahkola --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 3868] New: DRI drivers should export all supported fbconfigs
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=3868 Summary: DRI drivers should export all supported fbconfigs Product: Mesa Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Other AssignedTo: dri-devel@lists.sourceforge.net ReportedBy: [EMAIL PROTECTED] Each driver currently exports only the fbconfigs that match the current color bits. This is wrong. The driver should export *all* the fbconfigs that it can support and let the loader figure out which ones should actually be exposed to the application. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-users] X hangs when starting glxgears on r350
On Monday 25 July 2005 10:18, Jerome Glisse wrote: radeon 9800 card still lockup with r300 driver. If you first run an X server with fglrx, then leave and launch xorg with r300 driver you shouldn't have any lockup. A quick question: which version of X and fglrx are you using ? I've been struggling to get fglrx to work with Xorg CVS HEAD, without any success so far... Since X has moved to dlloader, while fglrx still is shipped as elf, this causes a lot of undefined symbols when X is starting. I tried to make a .so version of the fglrx_drv.o file, but now X complains about libfglrxdrm... Nicolas --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: X300SE PCI-E freezes
- Original Message - From: Alex Deucher [EMAIL PROTECTED] Date: Sunday, July 24, 2005 5:49 pm Subject: Re: X300SE PCI-E freezes On 7/24/05, Torbjörn Söderstedt [EMAIL PROTECTED] wrote: Hello, I tried the driver on my X300SE PCI-E card, but when I start the X server all I get is a black screen. To make the driver recognise my card at all, I added it to the pciids as a rv350 card (although it really should be rv370). Kernel and Xorg logs are attached. Because I don't have much kernel hacking experience, I don't really know where to start. I'm prepared to devote some time for this, so please tell me what I can do to help. PCIE is not currently working. So for the moment, PCIE cards will not work. What you can try is setting up the card with the fglrx driver and getting that working then use the radeon register dump scripts in r300 cvs to dump the PCIE config and then compare that to how the regs get set up in the open drm. I have had very little success with the fglrx driver. Last time I tried, it would lock up the system (even worse than r300) as soon as I tried to use opengl. This time it wouldn't activate dri at all, and glxgears gives me 25 fps!?! I'll get back to you if I ever get it to work. Regards Torbjörn Söderstedt --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-users] X hangs when starting glxgears on r350
On 7/25/05, Bellido Nicolas [EMAIL PROTECTED] wrote: On Monday 25 July 2005 10:18, Jerome Glisse wrote: radeon 9800 card still lockup with r300 driver. If you first run an X server with fglrx, then leave and launch xorg with r300 driver you shouldn't have any lockup. A quick question: which version of X and fglrx are you using ? I've been struggling to get fglrx to work with Xorg CVS HEAD, without any success so far... Since X has moved to dlloader, while fglrx still is shipped as elf, this causes a lot of undefined symbols when X is starting. I tried to make a .so version of the fglrx_drv.o file, but now X complains about libfglrxdrm... In fact, i use xfree86 (from debian testing) for fglrx, i don't think you could make lastest fglrx work with xorg head, have to wait for next ati release... Jerome Glisse --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-users] X hangs when starting glxgears on r350
Jerome Glisse wrote: On 7/25/05, Bellido Nicolas [EMAIL PROTECTED] wrote: On Monday 25 July 2005 10:18, Jerome Glisse wrote: radeon 9800 card still lockup with r300 driver. If you first run an X server with fglrx, then leave and launch xorg with r300 driver you shouldn't have any lockup. A quick question: which version of X and fglrx are you using ? I've been struggling to get fglrx to work with Xorg CVS HEAD, without any success so far... Since X has moved to dlloader, while fglrx still is shipped as elf, this causes a lot of undefined symbols when X is starting. I tried to make a .so version of the fglrx_drv.o file, but now X complains about libfglrxdrm... In fact, i use xfree86 (from debian testing) for fglrx, i don't think you could make lastest fglrx work with xorg head, have to wait for next ati release... Jerome Glisse I made xorg cvs work with fglrx but it doesn't work with DRI (it says DRM version is not what it expects). I don't remember the exact URL form where i got the instructions but i did something similar to this: http://lists.freedesktop.org/pipermail/xorg/2005-February/006049.html and this: http://www.mail-archive.com/dri-devel@lists.sourceforge.net/msg21846.html and i added this to my Section Module: # fglrx xorg cvs hack Loadfglrxdrm Loadxaa Loadramdac Loadfbdevhw Loadvgahw Loadvbe Loadi2c Loadint10 Loadfb Loadddc which solves the undefined symbol messages. -- Pedro Ramalhais --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
MSI RX9250-T128
Hey, I just installed the card mentioned in the subject line hoping to be able to get better performance with OpenCroquet than I could with my R128... I open it up and it crashes and locks the screen... Using a second computer to de-lock the console, I was able to recover this message from GDB: (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. 0x779844cf in _tnl_build_vertices () from /usr/lib/modules/dri/r200_dri.so (gdb) bt #0 0x779844cf in _tnl_build_vertices () from /usr/lib/modules/dri/r200_dri.so Error accessing memory address 0x77984450: No such process. (gdb) ( this is with xorg x11 on Gentoo, fully updated..., with the CVS DRI drivers...) The message from Squeak itself is: # [EMAIL PROTECTED] ~/Croquet0.3 $ squeak Segmentation fault 2036693844 OpenGLdrawIndexed:faces:vertices:normals:colors:texCoords: 2036693752 OpenGLdrawIndexedTriangles:vertices:normals:colors:texCoords: 2036687260 TMeshrenderPrimitive:alpha: 2036687168 TMeshrender: 2036686964 TFramerenderFrame:parent:root: 2036686084 [] in TFramerenderFrame:parent:root: 2036685816 OrderedCollectiondo: 2036685724 TFramerenderFrame:parent:root: 2036678492 TAvatarrenderFrame:parent:root: 2036678656 [] in TFramerenderFrame:parent:root: 2036678400 OrderedCollectiondo: 2036677812 TFramerenderFrame:parent:root: 2036678216 [] in TSpacerenderFrame:parent:root: 2036674284 BlockContexton:do: 2036674192 TSpacerenderFrame:parent:root: 2036673612 TSpacerenderSpace:port:depth:ghostFrame: 2036665708 TPortalrender:depth: 2036665456 [] in TSpacerenderSpace:port:depth:ghostFrame: 2036664348 SequenceableCollectiondo: 2036663232 TSpacerenderSpace:port:depth:ghostFrame: 2036664220 TSpacerenderSpace: 2036662932 TCamerarenderView: 2036662840 TeapotMorphglRenderOn: 2036662748 TeapotMorphrenderOn: 2036662656 TeapotMorphrender 2036662472 [] in TeapotMorphdrawOn: 2036662196 BlockContexton:do: 2036662288 [] in TeapotMorphdrawOn: 2036662104 BlockContextensure: 2036661892 [] in TeapotMorphdrawOn: 2036661984 [] in BlockContextnewProcess Aborted [EMAIL PROTECTED] ~/Croquet0.3 $ The other issue I'm having is this secondary PCI resource on the card... LSPCI outputs: WTF is this 5940 device :01:05.0 Class 0300: 1002:5960 (rev 01) Subsystem: 1462:9522 Flags: bus master, fast Back2Back, 66Mhz, medium devsel, latency 66, IRQ 18 Memory at e800 (32-bit, prefetchable) [size=128M] I/O ports at 2000 [size=256] Memory at e000 (32-bit, non-prefetchable) [size=64K] Capabilities: [58] AGP version 2.0 Capabilities: [50] Power Management version 2 :01:05.1 Class 0380: 1002:5940 (rev 01) Subsystem: 1462:9523 Flags: fast Back2Back, 66Mhz, medium devsel Memory at f000 (32-bit, prefetchable) [size=128M] Memory at e001 (32-bit, non-prefetchable) [size=64K] Capabilities: [50] Power Management version 2 ## Xorg.log outputs: (II) Module atimisc: vendor=X.Org Foundation compiled for 6.8.2, module version = 6.5.6 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 0.7 (WW) RADEON: No matching Device section for instance (BusID PCI:1:5:1) found (--) Chipset ATI Radeon 9200PRO 5960 (AGP) found (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0xffe0 - 0x (0x20) MX[B](B) [1] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [2] -1 0 0x000f - 0x000f (0x1) MX[B] [3] -1 0 0x000c - 0x000e (0x3) MX[B] [4] -1 0 0x - 0x0009 (0xa) MX[B] [5] -1 0 0xe0101000 - 0xe010107f (0x80) MX[B] [6] -1 0 0xe010 - 0xe0100fff (0x1000) MX[B] [7] -1 0 0xe040 - 0xe03f (0x0) MX[B]O [8] -1 0 0xe200 - 0xe1ff (0x0) MX[B]O [9] -1 0 0xe0102000 - 0xe0102fff (0x1000) MX[B](B) [10] -1 0 0xf800 - 0xf8ff (0x100) MX[B](B) [11] -1 0 0xe001 - 0xe001 (0x1) MX[B](B) ### There is also a Mach64 on the system but because there was a conflict with the R128 driver I used to have, 3D is disabled on that card for the time being... -- Friends don't let friends use GCC 3.4.4 GCC 3.3.6 produces code that's twice as fast on x86! --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[r300] undefined symbol: __driUtilCreateScreen
Hello, I am trying to get the r300 driver to work for my radeon 9600 on a 1GHz Powerbook G4. I am running Xorg 6.8.99.15 on a 2.6.11 kernel (Gentoo). I followed the instructions and checked out the r300_driver from the CVS as well as the latest Mesa CVS, compiled the whole thing and installed it. I get an error in glxinfo telling me that the r300_dri driver could not be loaded: == libGL: XF86DRIGetClientDriverName: 4.0.1 r300 (screen 0) libGL: OpenDriver: trying /usr/lib/modules/dri/r300_dri.so libGL error: dlopen /usr/lib/modules/dri/r300_dri.so failed (/usr/lib/modules/dri/r300_dri.so: undefined symbol: __driUtilCreateScreen) libGL error: unable to find driver: r300_dri.so name of display: :0.0 display: :0 screen: 0 direct rendering: No == Apparently, this function is declared in Mesa in src/mesa/drivers/dri/common/dri_util.c ... Obviously I am missing a library or using incompatible versions of Mesa, but I am not sure how to fix this. Am I doing some obvious mistake, or could someone point me to what could be wrong? Thanks, and keep up the good work with these free radeon drivers, they are enormously welcome! PS: I attached my Xorg log as well. -- Sébastien Cevey [EMAIL PROTECTED] | http://sirius.cine7.net/ | GPG: AEE9D6B9 Jabber: [EMAIL PROTECTED] | ICQ: 48895760 | MSN: [EMAIL PROTECTED] I feel like committing suicide but I have so many problems that wouldn't solve them all. Jason Biggs (Jerry Falk) [ Anything Else ] This is a pre-release version of the The X.Org Foundation X11. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the xorg product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the The X.Org Foundation monolithic tree CVS repository hosted at http://www.freedesktop.org/Software/xorg/ X Window System Version 6.8.99.15 Release Date: 16 July 2005 + cvs X Protocol Version 11, Revision 0, Release 6.8.99.15 Build Operating System: Linux 2.6.11.2-benh ppc [ELF] Current Operating System: Linux fawkes 2.6.11.2-benh #3 Sat May 28 19:27:04 CEST 2005 ppc Build Date: 25 July 2005 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Tue Jul 26 01:44:48 2005 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout X.org Configured (**) |--Screen Screen0 (0) (**) | |--Monitor LCD (**) | |--Device Card0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) FontPath set to /usr/share/fonts/misc/,/usr/share/fonts/TTF,/usr/share/fonts/Speedo/,/usr/share/fonts/Type1/,/usr/share/fonts/CID/,/usr/share/fonts/75dpi/,/usr/share/fonts/100dpi/,/usr/share/fonts/cyrillic/,/usr/share/fonts/artwiz:unscaled,/usr/share/fonts/ttf-bitstream-vera/ (**) RgbPath set to /usr/lib/X11/rgb (**) ModulePath set to /usr/lib/modules (II) Open APM successful (II) Module ABI versions: X.Org ANSI C Emulation: 0.2 X.Org Video Driver: 0.7 X.Org XInput driver : 0.4 X.Org Server Extension : 0.2 X.Org Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/lib/modules/fonts/libbitmap.so (II) Module bitmap: vendor=X.Org Foundation compiled for 6.8.99.15, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/lib/modules/libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 6.8.99.15, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.7 (++) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:0b:0: chip 106b,0034 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:10:0: chip 1002,4e50 card 1002,4e50 rev 00 class 03,00,00 hdr 00 (II) PCI: 10:0b:0: chip 106b,0035 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 10:13:0: chip 104c,ac56 card 1000, rev 00 class 06,07,00 hdr 02 (II) PCI: 10:17:0: chip 106b,003e card , rev 00 class ff,00,00 hdr 00 (II) PCI: 10:18:0: chip 106b,003f card , rev 00 class 0c,03,10 hdr 00 (II) PCI: 10:19:0: chip 106b,003f card , rev 00 class 0c,03,10 hdr 00 (II) PCI: 10:1a:0: chip 106b,003f card , rev 00 class 0c,03,10 hdr 00 (II) PCI: 10:1b:0: chip 1033,0035 card 1033,0035 rev 43 class 0c,03,10 hdr 80 (II) PCI: 10:1b:1: chip 1033,0035 card 1033,0035 rev 43 class 0c,03,10 hdr 00 (II) PCI: 10:1b:2: chip 1033,00e0 card 1033,00e0 rev 04 class 0c,03,20 hdr 00 (II) PCI: 24:0b:0: chip 106b,0036 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 24:0d:0: chip 106b,003b card , rev 00 class ff,00,00 hdr 00 (II)
Re: [r300] undefined symbol: __driUtilCreateScreen
begin Sebastien Cevey quotation of Tue, Jul 26, 2005 at 02:17:37AM +0200: Me again.. I get an error in glxinfo telling me that the r300_dri driver could not be loaded: Well I just saw the post saying that the r300 CVS is moved to the Mesa one, so I guess I tested a slightly outdated version. I tried the version in the Mesa CVS now (and renamed the __driCreateNewScreen_20050722 function to __driCreateNewScreen) and now the driver seems to be loaded! However, OpenGL does not seem to work: == $ glxinfo libGL: XF86DRIGetClientDriverName: 4.0.1 r300 (screen 0) libGL: OpenDriver: trying /usr/lib/modules/dri/r300_dri.so drmOpenByBusid: Searching for BusID pci::00:10.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 5, (OK) drmOpenByBusid: drmOpenMinor returns 5 drmOpenByBusid: drmGetBusid reports pci::00:10.0 Segmentation fault == glxgears segfaults too. I haven't had time to see if other people had already reported this problem, but I just wanted to post this follow-up before going to bed so people don't lose time on outdated problems... -- Sébastien Cevey [EMAIL PROTECTED] | http://sirius.cine7.net/ | GPG: AEE9D6B9 Jabber: [EMAIL PROTECTED] | ICQ: 48895760 | MSN: [EMAIL PROTECTED] http://support.microsoft.com/?kbid=265230 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [r300] undefined symbol: __driUtilCreateScreen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sebastien Cevey wrote: Well I just saw the post saying that the r300 CVS is moved to the Mesa one, so I guess I tested a slightly outdated version. I tried the version in the Mesa CVS now (and renamed the __driCreateNewScreen_20050722 function to __driCreateNewScreen) and now the driver seems to be loaded! However, OpenGL does not seem to work: So, that's like taking the Diesel fuel only sticker off your gas tank to make it work with regular gas. :) The name changed because the interface changed. Use *all* DRI drivers *and* libGL.so from Mesa CVS. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFC5Z/BX1gOwKyEAw8RApswAJ4vMZKcakYZv8rrmHUqORiArsTWXACfWeBv rVMUIPdwBtRE5p/QchAfxro= =qUkJ -END PGP SIGNATURE- --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
DRI_NEW_INTERFACE_ONLY
There are still some uses of this in the DRI tree... [EMAIL PROTECTED] mesa-cg]$ grep -r DRI_NEW_INTERFACE_ONLY * configs/freebsd-dri:DEFINES = -DDRI_NEW_INTERFACE_ONLY -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 configs/linux-solo: -DDRI_NEW_INTERFACE_ONLY -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DDRM_USE_MALLOC configs/linux-solo-ia64:DEFINES = -DDRI_NEW_INTERFACE_ONLY -D_POSIX_SOURCE -D_SVID_SOURCE -D_BSD_SOURCE -D_POSIX_C_SOURCE=199309L -D_GNU_SOURCE -DDRM_USE_MALLOC include/GL/internal/dri_interface.h:#ifndef DRI_NEW_INTERFACE_ONLY -- Jon Smirl [EMAIL PROTECTED] --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Left over in dri_interface.h
/** * \name Functions provided by the driver loader. */ /[EMAIL PROTECTED]/ extern __DRIscreen *__glXFindDRIScreen(__DRInativeDisplay *dpy, int scrn); -- Jon Smirl [EMAIL PROTECTED] --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
