Re: Vmwgfx: lack of 3D acceleration
Please provide the full Xorg.0.log file. Here it is (in the meantime I recompiled drm 2.4.18, but non vmwgfx 3D again) Marco Xorg.0.log Description: Binary data -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Vmwgfx: lack of 3D acceleration
Hallo, I'trying to use the vmwgfx driver to anable 3D accellarion on vmware player, but xorg still use swrast driver. I'm using kernel 2.6.33-rc7-00213-g0706f50 self comiled with vmwgfx driver enabled. I'm using mesa_7_7_branch because is the only one vmwgfx works in xorg (master still doesn't work in xorg) and xorg 1.7.99.3 dated 20100121. It seems that drm recognize 3D capabilities, but Xorg doesn't This is what I get from dmesg: [4.470260] [drm] Initialized drm 1.1.0 20060810 [4.470304] initcall drm_core_init+0x0/0x100 [drm] returned 0 after 220 usecs [4.488209] [drm:drm_init], [4.488231] [drm:drm_get_dev], [4.488253] [drm:drm_get_minor], [4.489182] [drm:drm_get_minor], new minor assigned 64 [4.489204] [drm:drm_get_minor], [4.489372] [drm:drm_get_minor], new minor assigned 0 [4.490037] [drm] Capabilities: [4.491037] [drm] Rect copy. [4.491059] [drm] Cursor. [4.491080] [drm] Cursor bypass. [4.491102] [drm] Cursor bypass 2. [4.491124] [drm] 8bit emulation. [4.491146] [drm] Alpha cursor. [4.491167] [drm] 3D. [4.491189] [drm] Extended Fifo. [4.491211] [drm] Multimon. [4.491233] [drm] Pitchlock. [4.491254] [drm] Display Topology. [4.491276] [drm] VRAM at 0xf000 size is 131072 kiB [4.491298] [drm] MMIO at 0xe800 size is 2048 kiB [4.491320] [drm] global init. [4.495033] [drm] width 640 [4.495055] [drm] height 480 [4.495076] [drm] bpp 32 [4.496038] [drm] Fifo max 0x0020 min 0x1000 cap 0x007f [4.498031] [drm:vmw_fb_init], width 2560 [4.498053] [drm:vmw_fb_init], height 1600 [4.498075] [drm:vmw_fb_init], width 2048 [4.498097] [drm:vmw_fb_init], height 1600 [4.498118] [drm:vmw_fb_init], bpp32 [4.498140] [drm:vmw_fb_init], depth 24 [4.498162] [drm:vmw_fb_init], bpl8192 [4.498184] [drm:vmw_fb_init], r mask 00ff [4.498205] [drm:vmw_fb_init], g mask ff00 [4.498227] [drm:vmw_fb_init], b mask 00ff [4.498247] [drm:vmw_fb_init], fb_offset 0x [4.498266] [drm:vmw_fb_init], fb_pitch 8192 [4.498288] [drm:vmw_fb_init], fb_size 12800 kiB [4.524038] [drm] Have 3D [4.524059] [drm] Initialized vmwgfx 1.0.0 20100209 for :00:0f.0 on minor 0 [ 24.434211] [drm:drm_stub_open], [ 24.434390] [drm:drm_open_helper], pid = 2335, minor = 0 [ 24.435062] [drm] Master create. [ 24.435242] [drm] Master set. [ 24.436399] [drm:drm_setup], What Xorg says is this: II) vmwgfx(0): Using exact sizes for initial modes II) vmwgfx(0): Output LVDS1 using initial mode 800x600 II) vmwgfx(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated. ==) vmwgfx(0): DPI set to (96, 96) II) vmwgfx(0): 2D Acceleration is disabled II) vmwgfx(0): Fallback debugging is enabled II) vmwgfx(0): 3D Acceleration is disabled ==) vmwgfx(0): Backing store disabled ==) vmwgfx(0): Silken mouse enabled II) vmwgfx(0): RandR 1.2 enabled, ignore the following RandR disabled message. ==) vmwgfx(0): DPMS enabled II) vmwgfx(0): Damage tracking initialized II) vmwgfx(0): Setting screen physical size to 211 x 158 This is what glxinfo says: name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_hyperpipe, GLX_SGIX_swap_barrier, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_MESA_copy_sub_buffer, GLX_INTEL_swap_event client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory, GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap GLX version: 1.4 GLX extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer OpenGL vendor string: Mesa Project OpenGL renderer string: Software Rasterizer OpenGL version string: 2.1 Mesa 7.7.1-DEVEL OpenGL shading language version string: 1.20 It seems to use swrast. I would expect it to use vmwgfx_dri. Bye Marco -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel
Re: glxgears crash with latest mesa swrast module
I forgot to mention I enabled dri2 in xserver, and yes I always do a clean rebuild. But after latest commit: author George Sapountzis [EMAIL PROTECTED] Fri, 12 Sep 2008 09:43:10 + (12:43 +0300) commit d3dc95e26a0da2b89e7a3cdf5bacbfc66ed17c95 all is fine now and glkxgears doesn't segfault anymore. Thanks Marco - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: glxgears crash with latest mesa swrast module
I don't see how that change could be related to a SwapBuffers crash Sorry I was misunderstod: that is latest commit I have. Last mesa sources I had was from 20/08/2008, and glxgears was running fine, then I upgraded till the commit of Fri Sep 5 08:06:59 2008 -0600 and glxgears now crashes. Bye - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
glxgears crash with latest mesa swrast module
I tried latest git from mesa master (latest commit is): commit 11d694b1bb0cb384d802d7e0e252cf5119febb98 Author: Brian Paul [EMAIL PROTECTED] Date: Fri Sep 5 08:06:59 2008 -0600 mesa: replace MALLOC w/ CALLOC to fix memory error in glPushClientAttrib() Glxgears crash as soon as it starts. This is gdb trace: [EMAIL PROTECTED]:~$ gdb glxgears GNU gdb 6.6-debian Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i486-linux-gnu... Using host libthread_db library /lib/libthread_db.so.1. (gdb) run Starting program: /usr/bin/glxgears [Thread debugging using libthread_db enabled] [New process 11011] [New Thread -1211914576 (LWP 11011)] libGL: OpenDriver: trying /usr/lib/dri/swrast_dri.so Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1211914576 (LWP 11011)] 0x47206769 in ?? () (gdb) bt #0 0x47206769 in ?? () #1 0xb7f09deb in glXSwapBuffers (dpy=0x804c008, drawable=35651586) at glxcmds.c:859 #2 0x0804a69b in main (argc=1, argv=0xbfc857b4) at glxgears.c:338 (gdb) Bye Marco - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Another question about DRI2 direct rendering
I tried the latest drm,mesa e xorg from git to test the new DRI2 direct rendering and possibly AIGLX. I also pull the latest intel batchbuffer branch to have DRI2 enabled. These are my logs: 1) It seems (from Xorg.log) that direct rendering is enabled with DRI2; 2) The output of glxinfo keeps saying the direct rendering is not enabled; 3) The performance of glxgears resamble the ones achieved with dri (stable version), a little bit less fluid; 4) Compiz refuses to start saying: Root visual is not a double buffered GL visual; Am I missing something? Where did I go wrong? Bye and keep up your great work. Marco (WW) Failed to open protocol names file /etc/X11/xserver/protocol.txt This is a pre-release version of the X server from The X.Org Foundation. 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 X.Org Foundation git repository. See http://wiki.x.org/wiki/GitPage for git access instructions. X.Org X Server 1.5.99.1 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux (xorg-server 2:1.4.1~git20080331-0.1) Current Operating System: Linux deneb 2.6.25-rc6-git3-port #1 SMP PREEMPT Wed Mar 19 09:52:36 UTC 2008 i686 Build Date: 01 April 2008 11:21:43AM 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: Wed Apr 2 20:34:56 2008 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Monitor Generico (**) | |--Device Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (**) |--Input Device Generic Keyboard (**) |--Input Device Configured Mouse (**) |--Input Device Synaptics Touchpad (**) Option AIGLX true (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (WW) `fonts.dir' not found (or not valid) in /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType. Entry deleted from font path. (Run 'mkfontdir' on /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType). (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi (==) ModulePath set to /usr/lib/xorg/modules (**) Extension Composite is enabled (II) Open ACPI successful (/var/run/acpid.socket) (II) Loader magic: 0x81cb4c0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 4.0 X.Org XInput driver : 2.0 X.Org Server Extension : 1.0 X.Org Font Renderer : 0.5 (II) Loader running on linux (++) using VT number 7 (--) PCI:*([EMAIL PROTECTED]:2:0) unknown vendor (0x8086) unknown chipset (0x27a2) rev 3, Mem @ 0xd030/0, 0xc000/0, 0xd040/0, I/O @ 0x5088/0 (--) PCI: ([EMAIL PROTECTED]:2:1) unknown vendor (0x8086) unknown chipset (0x27a6) rev 3, Mem @ 0xd038/0 (II) System resource ranges: [0] -1 0 0x - 0x (0x1) MX[B] [1] -1 0 0x000f - 0x000f (0x1) MX[B] [2] -1 0 0x000c - 0x000e (0x3) MX[B] [3] -1 0 0x - 0x0009 (0xa) MX[B] [4] -1 0 0x - 0x (0x1) IX[B] [5] -1 0 0x - 0x (0x1) IX[B] (II) LoadModule: extmod (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.5.99.1, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 1.0 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: dbe (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so (II) Module dbe: vendor=X.Org Foundation compiled for 1.5.99.1, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 1.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: glx (II) Loading /usr/lib/xorg/modules/extensions//libglx.so (II) Module glx: vendor=X.Org Foundation compiled for 1.5.99.1, module version = 1.0.0 ABI
[Dri-devel] FYI: savage vast_speed_improvement
Just checked out mesa/dri cvs and build the whole tree. And glxgears got from prior 400 to 490 fps on my t23 (1,1 ghz p3 mobile, supersavage). thats nearly 25 % faster ! good work --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] freedesktop cvs /tmp no space
it seems the freedesktop cvs machine is running out of space on /tmp : [EMAIL PROTECTED] mesa]# ./up.bat Logging in to :pserver:[EMAIL PROTECTED]:2401/cvs/mesa CVS password: can't create temporary directory /tmp/cvs-serv27957 No space left on device same on dri trunk. No problems with my /tmp ... so. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Fw: Re: [Dri-devel] savage-2-0-0 test notes
Begin forwarded message: Date: Fri, 27 Feb 2004 11:59:22 -0600 From: Steve Holland [EMAIL PROTECTED] To: Felix Khling [EMAIL PROTECTED] Subject: Re: [Dri-devel] savage-2-0-0 test notes I tested it with a fresh copy from the trunk (effective tuesday), and have the same problems. Here are some PNG's of the results from drawpix: 16 bit display, drawing to back buffer: http://69.5.151.193/~sdh4/drawpix16bit.png drawing to front buffer: http://69.5.151.193/~sdh4/drawpix16bitfrontbuffer.png 24 bit display drawing to back buffer: http://69.5.151.193/~sdh4/drawpix24bit.png (24 bit display drawing to front buffer was similar to 16-front buffer) I also noticed problems when switching video modes on a 24 bit display. For example, running tuxracer would get the display parameters wrong, leading to an incomprehensible display (even after quitting). Thanks, Steve The code i'm running is also about 2-3 days old. I've got the same Hardware (T23 - supersavage IX/SDR). What he means with corruption occurs when changing the display mode on-the-fly. Then the screen is corrupted. Switching back to the old resolution normalizes the screen again. This won't happen when starting initialy with the new setting. So setting XF86Config to a new res and restart X everything is fine. Acceleration stuff : -only works in 16 bpp (2d/3d) -in 24bpp there is no 2d nor any 3d accelleration. -2D accell worked with tims driver on 24bpp. Tuxracer is still fine. But blender didn't change. The screen is clean but all fonts are corrupted. It seems to me that the fonts in blender are also gl, but that's just an assumption. Besides that you did a _GREAT_ work, and the driver speeded up in the last 2-3 Months as gar as i can see. With savage-2-0-0 i had about 270 fps in the beginning of working dri-support for my chip. Than it got from 325 to 378. And with the last code in the savage branch it reached 408. That stayed with the HEAD Branch since then. regards marco --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] savage success report
hi. just checked out the most recent savage_2.0.0 branch. enabled dri and working ;) xv working, consoles scrambled. chromium looking good, tuxracer is somehow a bit choppy and not playable, but accelerated. all gl screensavers work. ;) on t23 , supersavage IX/SDR marco --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] supersavage IX / SDR - cvs
Hello. drm loads cleanly, finds card, inits. driver recognizes drm cleanly. xvideo is broken, no 2d acceleration at all. Speed is equal to vesa driver. glplanet exits with invalid texture size. glxgears locks up X (sometime). In any case there is nothing to see in 3d ;) After trying 3d stuff and restarting X, X is unusable. Even after warm boot of the machine X is not usable. When starting the login manager it takes about 3 minutes to get the picture completed. A shutdown/turnoff/restart solves the problem. regards marco --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] kernel 2.6.1 - supersavage
ok, changed the code and recompiled the source. Now the drm module recognizes the card and inits it. /dev/dri/card0 is present even though not accessable by any user besides root. (flags are ok and i also have a proper DRI Section in config...) glxinfo reports dri is enabled. no gl stuff works. glxgears shows nothing. in X log : this is the card : (II) SAVAGE(0): VESA VBE OEM Vendor: S3 Incorporated. (II) SAVAGE(0): VESA VBE OEM Product: VBE 2.0 (II) SAVAGE(0): VESA VBE OEM Product Rev: Rev 1.0 (--) SAVAGE(0): Chip: id 8c2e, SuperSavage/PM64IXC_SDR (--) SAVAGE(0): Engine: SuperSavage (--) SAVAGE(0): mapping MMIO @ 0xc010 with size 0x8 (II) SAVAGE(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x (--) S3:support device 15. (--) S3:tv size 0x0. this is drm stuff : (--) SAVAGE(0): mapping framebuffer @ 0xe800 with size 0x100 (==) SAVAGE(0): Write-combining range (0xe800,0x100) (II) SAVAGE(0): Splitting WC range: base: 0xe400, size: 0x500 (==) SAVAGE(0): Write-combining range (0xe800,0x100) (==) SAVAGE(0): Write-combining range (0xe400,0x500) (II) SAVAGE(0): map aperture:0x41301000 (--) SAVAGE(0): SavageMatchBiosMode:chose mode 13e at 75Hz. (II) SavageSetVESAMode:mode=0x13e,refresh=75HZ (II) SAVAGE(0): [drm] bpp: 32 depth: 24 (II) SAVAGE(0): [drm] Sarea 2200+872: 3072 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenByBusid: Searching for BusID pci::01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenByBusid: drmOpenMinor returns 7 drmOpenByBusid: drmGetBusid reports pci::01:00.0 (II) SAVAGE(0): [drm] DRM interface version 1.1 (II) SAVAGE(0): [drm] created savage driver at busid pci::01:00.0 (II) SAVAGE(0): [drm] added 8192 byte SAREA at 0xe08d9000 (II) SAVAGE(0): [drm] mapped SAREA 0xe08d9000 to 0x46301000 (II) SAVAGE(0): [drm] framebuffer handle = 0xe800 (II) SAVAGE(0): [drm] added 1 reserved context for kernel (II) SAVAGE(0): [agp] Mode 0x1f000217 [AGP 0x8086/0x3575; Card 0x5333/0x8c2e] (II) SAVAGE(0): [agp] 16384 kB allocated with handle 0x0001 (II) SAVAGE(0): [agp] agpTextures microcode handle = 0xd000 (II) SAVAGE(0): [agp] agpTextures mapped at 0x (II) SAVAGE(0): [drm] aperture handle = 0xe400 (II) SAVAGE(0): [drm] Status handle = 0xe08f4000 (II) SAVAGE(0): [agp] Status page mapped at 0x46303000 (II) SAVAGE(0): [dri] visual configs initialized (**) SAVAGE(0): DRI is enabled (II) SAVAGE(0): virtualX:1400,virtualY:1050 (II) SAVAGE(0): bpp:32,tiledwidthBytes:5632,tiledBufferSize:5947392 (II) SAVAGE(0): bpp:32,widthBytes:5632,BufferSize:5914624 (II) SAVAGE(0): videoRambytes:0x0100 (II) SAVAGE(0): textureSize:0xffce3000 (II) SAVAGE(0): textureSize:0x (II) SAVAGE(0): textureOffset:0x00fdf000 (II) SAVAGE(0): depthOffset:0x00a33000,depthPicth:5632 (II) SAVAGE(0): backOffset:0x00487000,backPicth:5632 (EE) SAVAGE(0): Memory manager initialization to (0,0) (1408,-1) failed (==) SAVAGE(0): Backing store disabled (**) Option dpms (**) SAVAGE(0): DPMS enabled (II) SAVAGE(0): X context handle = 0x0001 (II) SAVAGE(0): [drm] installed DRM signal handler (II) SAVAGE(0): [DRI] installation complete (II) SAVAGE(0): [junkers]pSAVAGEDRIServer: [LOTS OF STUFF DELETED] (II) SAVAGE(0): [junkers] BCIcmdBuf:map:0x0001 (II) SAVAGE(0): [junkers] status:handle:0xe08f4000 (II) SAVAGE(0): [junkers] status:offset:0x (II) SAVAGE(0): [junkers] status:size:0x2000 (II) SAVAGE(0): [junkers] status:map:0x (II) SAVAGE(0): [junkers] sarea_priv_offset:0x0898 (II) SAVAGE(0): Direct rendering enabled (--) SAVAGEInitMC: There is no enough memory! (**) SAVAGE(0): XvMC is not enabled (WW) SAVAGE(0): Option ForceInit is not used (==) RandR enabled -- snip. see the not enough memory error... Hope this helps... ;) regards Marco --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] supersavage-kernel 2.6.1
Hi. I managed to get everything compiled cleanly. Hardware is t23/ S3 Supersavage / 1400x1050 Kernel Module loads cleanly. but xfree writes in log : snip II) SAVAGE(0): map aperture:0x41301000 (--) SAVAGE(0): SavageMatchBiosMode:chose mode 13e at 75Hz. (II) SavageSetVESAMode:mode=0x13e,refresh=75HZ (EE) SAVAGE(0): DRI isn't enabled (II) SAVAGE(0): Using 998 lines for offscreen memory. (II) SAVAGE(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles [DELETED] (==) SAVAGE(0): Backing store disabled (**) Option dpms (**) SAVAGE(0): DPMS enabled (EE) SAVAGE(0): Direct rendering disabled (WW) SAVAGE(0): Option ForceInit is not used (==) RandR enabled snip-- Also the consoles on ctrl+alt+Fx are not useable any more. I tried the Forceinit option , but doesn't recognizes it any more. I'm so close ;) Help would be appreciated. regards Marco --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] same radeon7500 lockup (as 2 weeks ago)
since 1 week i get the same lookup using the lastest tcl-0-0-branch on my radeon7500 ddr 64m. the lockup seems the one that someone (maybe keithp) fixes 3 weeks ago. -- BOFH excuse #442: Trojan horse ran out of hay ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Radeon7500 lockups with Q3A
On Mon, Mar 04, 2002 at 09:41:38AM -0800, Ian Romanick wrote: On Mon, Mar 04, 2002 at 03:28:48AM +0100, Andreas Stenglein wrote: I have this lockups with quake3arena, too. I found a temporary (and slow) workaround: disable the use of OpenGL-extensions in the q3a-setup-menu. Its strange, as I can remember that some people reported they were using XFree 4.1.0 with the Radeon7500, I wonder, didnt they play quake3? It's interesting that you mention this. I had a similar issue a long (5 or 6 months or more) time ago. It was with an older version of Q3A (1.17 perhaps), and the problem went away when I moved to 1.27g. nope. q3a 1.31 with the *same* problems in rendering and the *same* machine lockup ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
