Re: [Dri-devel] PCIGART Radeon AIW support
On Mon, 2002-10-21 at 21:07, Kees Cook wrote: > On Mon, Oct 21, 2002 at 07:53:13PM +0200, Michel Dänzer wrote: > > FWIW, I have an AGP 7000 running with PCI GART right now. It has locked > > Which binaries need to be replaced? radeon_drv.o (the 2D driver) and radeon.o (the DRM). > I built the dri tree from CVS, but X11 is still being weird. According > to the log, Direct Rendering is enabled, but glxinfo still says "SGI". > I have NO idea what's going on. > > $ grep Direct /var/log/XFree86.0.log > (II) RADEON(0): Direct rendering enabled > $ glxinfo > name of display: :0.0 > display: :0 screen: 0 > direct rendering: No > server glx vendor string: SGI Running glxinfo with LIBGL_DEBUG=verbose might give more info. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast --- This sf.net emial is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ad.doubleclick.net/clk;4699841;7576301;v? http://www.sun.com/javavote ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] PCIGART Radeon AIW support
>It might be related to the bus mastering issues. > >The reason that PCIGART support was not enabled on x86 was due to >lockups that happened with AGP cards. What we need is either to fix the >bug with using PCIGART on AGP cards or we need a way to have AGP cards >fail to load the DRI when the AGPGART kernel module is not loaded (i.e., >workaround the problem so that we can enable PCIGART for PCI cards). >It's on my TODO list but I haven't gotten to it yet. If someone beats >me to it, that would be great! On PPC, some people like me regulary use PCIGART on AGP cards, mostly because we still have some stability problems with AGP, it seems to work fine. Ben. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] PCIGART Radeon AIW support
On Mon, Oct 21, 2002 at 07:53:13PM +0200, Michel Dänzer wrote: > FWIW, I have an AGP 7000 running with PCI GART right now. It has locked Which binaries need to be replaced? I built the dri tree from CVS, but X11 is still being weird. According to the log, Direct Rendering is enabled, but glxinfo still says "SGI". I have NO idea what's going on. $ grep Direct /var/log/XFree86.0.log (II) RADEON(0): Direct rendering enabled $ glxinfo name of display: :0.0 display: :0 screen: 0 direct rendering: No server glx vendor string: SGI -- Kees Cook@outflux.net --- This sf.net emial is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ad.doubleclick.net/clk;4699841;7576298;k? http://www.sun.com/javavote ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] PCIGART Radeon AIW support
On Fri, Oct 18, 2002 at 02:28:33PM +0200, Michel Dänzer wrote: > > The PCI radeon seems to work fairly well actually: > [...] > Great news! Kevin, do you think we can enable PCI GART everywhere now, > or what were the problems you were seeing? (Is it possible that they > were related to bus mastering getting disabled?) I just got a Radeon 7000 PCI... so it seems like I need to do the same stuff to get mine working. However, I don't know how to compile it. :) Or rather, I don't know which branch of what I need to grab. I'm trying to stay as close to RedHat 7.3's versions of things, and I'd rather not recompile the entire XFree server. Is it possible to get the PCI GART working without that? -- Kees Cook@outflux.net --- This sf.net email is sponsored by: Access Your PC Securely with GoToMyPC. Try Free Now https://www.gotomypc.com/s/OSND/DD ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] PCIGART Radeon AIW support
On Don, 2002-10-17 at 21:07, James Fung wrote: > > The PCI radeon seems to work fairly well actually: > > OpenGL vendor string: Tungsten Graphics, Inc. > OpenGL renderer string: Mesa DRI Radeon 20020611 AGP 1x x86/MMX/3DNow! TCL > OpenGL version string: 1.2 Mesa 4.0.4 > > glxgears gives 1000 frames in 5.0 seconds = 200.000 FPS > > I've tried going through the Mesa demos and they seem to run OK, however > I've only ever seen them run on the Radeon so far so I don't really know > what I'm supposed to see. [...] > All in all, however, its been stable so far, and its nice to have it > working with DRI. Great news! Kevin, do you think we can enable PCI GART everywhere now, or what were the problems you were seeing? (Is it possible that they were related to bus mastering getting disabled?) -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] PCIGART Radeon AIW support
James Fung wrote: Thanks. The PCI radeon seems to work fairly well actually: OpenGL vendor string: Tungsten Graphics, Inc. OpenGL renderer string: Mesa DRI Radeon 20020611 AGP 1x x86/MMX/3DNow! TCL OpenGL version string: 1.2 Mesa 4.0.4 glxgears gives 1000 frames in 5.0 seconds = 200.000 FPS I've tried going through the Mesa demos and they seem to run OK, however I've only ever seen them run on the Radeon so far so I don't really know what I'm supposed to see. I also tried tuxracer - the ice patches seem to flicker (especially at the edges of the ice patches where the textures seem to flicker in and out), and there seems to be a similarly odd flicker/flash on the gloss.c mesa demo. These are known issues with the radeon driver. They're not really bugs as the behaviour is within GL spec, but we'd all rather it didn't happen. --- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm When did sourceforge start doing this? Keith --- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] PCIGART Radeon AIW support
Thanks. The PCI radeon seems to work fairly well actually: OpenGL vendor string: Tungsten Graphics, Inc. OpenGL renderer string: Mesa DRI Radeon 20020611 AGP 1x x86/MMX/3DNow! TCL OpenGL version string: 1.2 Mesa 4.0.4 glxgears gives 1000 frames in 5.0 seconds = 200.000 FPS I've tried going through the Mesa demos and they seem to run OK, however I've only ever seen them run on the Radeon so far so I don't really know what I'm supposed to see. I also tried tuxracer - the ice patches seem to flicker (especially at the edges of the ice patches where the textures seem to flicker in and out), and there seems to be a similarly odd flicker/flash on the gloss.c mesa demo. Additionally, I'm having some problems calling glTexSubImage2D(). It keeps saying OpenGL: Invalid value, but the same code works on a matrox and in software rendering. Also, a similar call to glTexImage2D() with the same texture and pixel formats succeeds. I'm still looking into this. All in all, however, its been stable so far, and its nice to have it working with DRI. -James On 17 Oct 2002, Michel Dänzer wrote: > On Mit, 2002-10-16 at 23:14, James Fung wrote: > > > > I'm using an All-In-Wonder Radeon card, and its the PCI version (not AGP). > > > > I complied the drm radeon.o module, and I editting the radeon_cp.c file to > > say #define PCIGART (presumably to try using the PCI GART). > > You need to do the same in > programs/Xserver/hw/xfree86/drivers/ati/radeon_dri.c . Let us know if it > works. > > > -- > Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer > XFree86 and DRI project member / CS student, Free Software enthusiast > > --- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] PCIGART Radeon AIW support
On Mit, 2002-10-16 at 23:14, James Fung wrote: > > I'm using an All-In-Wonder Radeon card, and its the PCI version (not AGP). > > I complied the drm radeon.o module, and I editting the radeon_cp.c file to > say #define PCIGART (presumably to try using the PCI GART). You need to do the same in programs/Xserver/hw/xfree86/drivers/ati/radeon_dri.c . Let us know if it works. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast --- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] PCIGART Radeon AIW support
Hi. I'm using an All-In-Wonder Radeon card, and its the PCI version (not AGP). I complied the drm radeon.o module, and I editting the radeon_cp.c file to say #define PCIGART (presumably to try using the PCI GART). If I just insmod radeon.o and not agpgart.o, then I get: (II) RADEON(0): [drm] created "radeon" driver at busid "PCI:0:9:0" (II) RADEON(0): [drm] added 8192 byte SAREA at 0xf088d000 (II) RADEON(0): [drm] mapped SAREA 0xf088d000 to 0x40014000 (II) RADEON(0): [drm] framebuffer handle = 0xe000 (II) RADEON(0): [drm] added 1 reserved context for kernel (EE) RADEON(0): [agp] AGP not available (EE) RADEON(0): [drm] failed to remove DRM signal handler (II) RADEON(0): [drm] removed 1 reserved context for kernel (II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xf088d000 at 0x40014000 and glxinfo uses Mesa Indirect. I tried to insmod both agpgart.o and radeon.o, then startx. Then, all I see is a bunch of green lines whipping by on the screen. I'm pretty sure its not a resolution/sync problem. The computer still runs, but I only see the green lines. CTRL-ALT-BKSPC doesn't return to the console properly. The xfree86.0.log looks ok: (II) RADEON(0): [drm] created "radeon" driver at busid "PCI:0:9:0" (II) RADEON(0): [drm] added 8192 byte SAREA at 0xf08a3000 (II) RADEON(0): [drm] mapped SAREA 0xf08a3000 to 0x40014000 (II) RADEON(0): [drm] framebuffer handle = 0xe000 (II) RADEON(0): [drm] added 1 reserved context for kernel (II) RADEON(0): [agp] Mode 0x1f000201 [AGP 0x1106/0x0305; Card 0x1002/0x5144] (II) RADEON(0): [agp] 8192 kB allocated with handle 0xf28a7000 (II) RADEON(0): [agp] ring handle = 0xe600 (II) RADEON(0): [agp] Ring mapped at 0x42207000 (II) RADEON(0): [agp] ring read ptr handle = 0xe6101000 (II) RADEON(0): [agp] Ring read ptr mapped at 0x40016000 (II) RADEON(0): [agp] vertex/indirect buffers handle = 0xe6102000 (II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0x42308000 (II) RADEON(0): [agp] AGP texture map handle = 0xe6302000 (II) RADEON(0): [agp] AGP Texture map mapped at 0x42508000 (II) RADEON(0): [drm] register handle = 0xdf00 (II) RADEON(0): [dri] Visual configs initialized (II) RADEON(0): CP in BM mode (II) RADEON(0): Using 8 MB AGP aperture (II) RADEON(0): Using 1 MB for the ring buffer (II) RADEON(0): Using 2 MB for vertex/indirect buffers (II) RADEON(0): Using 5 MB for AGP textures (II) RADEON(0): Memory manager initialized to (0,0) (1024,8191) (II) RADEON(0): Largest offscreen area available: 1024 x 7423 (II) RADEON(0): Will use back buffer at offset 0x90 (II) RADEON(0): Will use depth buffer at offset 0xc0 (II) RADEON(0): Will use 17408 kb for textures at offset 0xf0 (==) RADEON(0): Backing store disabled (==) RADEON(0): Silken mouse enabled Fatal server error: Caught signal 11. Server aborting (presumably the ctrl-alt-backspace causes the sig11) the only warnings I get are further up: (--) RADEON(0): Chipset: "ATI Radeon QD (AGP)" (ChipID = 0x5144) (--) RADEON(0): Linear framebuffer at 0xe000 (--) RADEON(0): MMIO registers at 0xdf00 (--) RADEON(0): BIOS at 0x000c (WW) System lacks support for changing MTRRs and something to do with xaa: (II) Loading sub module "xaa" (II) LoadModule: "xaa" (II) Loading /usr/X11R6/lib/modules/libxaa.a (II) Module xaa: vendor="The XFree86 Project" compiled for 4.2.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.5 (WW) module minor version (0) is less than the required minor version (1) (II) UnloadModule: "xaa" (II) Unloading /usr/X11R6/lib/modules/libxaa.a (II) Loading sub module "xaa" (II) LoadModule: "xaa" (II) Loading /usr/X11R6/lib/modules/libxaa.a (II) Module xaa: vendor="The XFree86 Project" compiled for 4.2.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.5 Is there anything else I need to do to get the PCI GART working? Any ideas would be appreciated. Thanks very much. -James --- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
