similar to: VRAM

I am using Ubuntu Hardy, using the latest release of wine from the wine repos. I have an nVidia 7600GT with 256MB of video memory. One windows game i installed, Medal of Honor Allied Assault, has a simple config utility that sets game settings based on your hardware. This utility is detecting only 64MB of video memory. I tried setting it using wine regedit, HKCU>Software>Wine>Direct3d

Does Wine use past the first 64MB on any video card? This question applies to all wine versions. I have heard it stated before that wine only uses the first 64MB on your video card either in direct3d or opengl modes. Is this true? If it is true is there a registry entry that can be added to make wine use past the first 64MB on your video card? I apprecaite your help in this matter?

Ubuntu Lucid 10.04 WINE 1.2.3 WINEtricks 20111115 I followed all the instructions in the AppDB, and I was able to install DCUO using the EXE downloaded from their site (http://launch.soe.com/installer/DCUO_setup.exe). I'm not using Steam. Another exception is that I'm using Adobe Flash 11 instead of 10. Launchpad comes up after a little wait. Before downloading the game components, it

It's that time again. I'm stuck with a bunch of older Powermac G4's that I either need to repurpose or give the heave ho. I've not tried CentOS on Mac hardware before. Would the following config be suitable for a (somewhat slow) workstation? PowerMac G4 400mhz 256mb RAM 40gig ATA disk Some sort of dual-head ATI video setup with 64mb VRAM (I've forgotten which cards they

I've heard that sometimes Wine will detect a gpu as having less Vram than it really does, I know this can be fixed by entering a specific registry key, but before I mess around with the registry I want to know if Wine is detecting it well or not. Is there any way I can do this? As in see how much VRAM Wine thinks I have?

On 19 June 2015 at 21:51, Martin Peres <martin.peres at free.fr> wrote: > On 19/06/2015 13:02, Alexandre Courbot wrote: >> >> New revision of this patchset that prevents VRAM objects from being >> allocated on VRAM-less systems like Tegra. This is required for Mesa >> to work on such systems. >> >> Changes since v2: >> - Use vram_size to detect

Hello list, Having a bit of an issue with virt-manager and virsh on Fedora 19/20. I've created several virtual guest machines, one of them is Windows. I've selected QXL and everything is working normally. The only part that's giving me trouble is that I'm unable to set the QXL VRAM higher than 64mb. This would be very useful for performance reasons. I've edited the XML

On Mon, Oct 27, 2014 at 6:34 AM, Alexandre Courbot <acourbot at nvidia.com> wrote: > GK20A does not have dedicated VRAM, therefore allocating in VRAM can be > sub-optimal and sometimes even harmful. Set its VRAM domain to > NOUVEAU_BO_GART so all objects are allocated in system memory. > > Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> > --- >

Some newer chips have trouble coming up, and we get bad MMIO reads from them, like 0xbadf100. This ends up translating into crazy amounts of VRAM, which destroys all sorts of other logic down the line. Instead, fail device init. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> Cc: stable at kernel.org --- drm/nouveau/nvkm/subdev/fb/ramgf100.c | 6 ++++++ 1 file changed, 6 insertions(+)

Hello all, I am pretty new to this and have wine 1.1.22. I am trying to run the Lord of the Rings Battle for Middle Earth 2, and it works, but most of the units display as white (makes it very difficult to play....) On the appdp, one person said "To avoid white characters in the game set the parameter "UseGLSL" in the wine registry to value "disabled". So the game

12:08 < curro_> shining: hmm, it seems, darktama didn't quite finish the additional reloc checking he started to code 12:11 < curro_> shining: that would have solved your problem, poke him when he's back from vacations :) 12:16 < shining> curro_: hmm I really dont get it, it looks like domain can have both set, and flags can also have both set 12:16 < shining> I

VRAM MM and GEM VRAM are only used with each other. This patch set moves VRAM MM into GEM VRAM source files and cleans up the helper's public interface. Thomas Zimmermann (4): drm/vram: Move VRAM memory manager to GEM VRAM implementation drm/vram: Have VRAM MM call GEM VRAM functions directly drm/vram: Unexport internal functions of VRAM MM drm/vram: Unconditonally set BO call-back

Hi, I have a fedora27 system with a win10 guest trying to use photoshop 2015. I've adjusted the vram parameter for the guest to 512M with QXL, but photoshop still reports "3D features and some filters require 512MB vRAM and photoshop has detected less than that on your system." What is the proper way to adjust the vram value to provide at least 512MB vram? I've included my xml

VRAM MM and GEM VRAM are only used with each other. This patch set moves VRAM MM into GEM VRAM source files and cleans up the helper's public interface. Version 2 of the patch set doesn't contain functional changes. I'm reposting due to the rebasing onto the debugfs patches. v2: * updated for debugfs support * fixed typos in comments Thomas Zimmermann (4): drm/vram: Move VRAM

Hello list, I am experiencing sound problems with Soul Reaver 2, follows the initial log after starting the game. $wine sr2.exe fixme:system:SystemParametersInfoW Unimplemented action: 59 (SPI_SETSTICKYKEYS) fixme:d3d:IWineD3DDeviceImpl_GetAvailableTextureMem (0x17a890) : stub, simulating 64MB for now, returning 64MB left fixme:d3d:IWineD3DDeviceImpl_ValidateDevice (0x17a890) : stub loading

Wine List, Just looking for ideas, here's my system configuration: Gentoo Linux 2.4.24 ALSA built as modules Creative Labs X-Fi 1.18 Driver with a few modifications per http://gentoo-wiki.com/HARDWARE_Creative_Labs_X-Fi Game I'm trying to get sound working on is WoW 2.4 winecfg shows no OSS or ALSA mixers, and none show up in the game either. Now I know, the first thing you're

There's a short window between module load and fbcon initalization when it's possible for vgacon to write to VGA RAM. Nouveau uses this memory for different purposes, so if we are unlucky, it causes mysterious memory corruptions. For me, booting with nv_printk debug levels set to 5 was enough to trigger it. It manifested as long stream of: "trapped write at ... on channel 0x0001fea0

This series is to allow NVIDIA chips with shared memory to operate more efficiently (and to operate at all once we disable VRAM from the kernel driver) by allowing nouveau_screen to specify a domain to use for objects originally allocated into VRAM. If the domain is not overridden, the default NOUVEAU_BO_VRAM is used. A NV_VRAM_DOMAIN() macro is then introduced to be used in place of

New revision of this patchset that prevents VRAM objects from being allocated on VRAM-less systems like Tegra. This is required for Mesa to work on such systems. Changes since v2: - Use vram_size to detect systems without VRAM and set the correct domain instead of expecting each chip to set its domain explicitly. Alexandre Courbot (2): nouveau: support for custom VRAM domains nvc0: use

On Friday 17 November 2017 18:41:17 Ilia Mirkin wrote: > On Fri, Nov 17, 2017 at 12:33 PM, Ondrej Zary > > <linux at rainbow-software.org> wrote: > > @@ -483,8 +483,8 @@ > > nouveau 0000:02:00.0: disp: 0860: 00000000 -> 00000500 > > nouveau 0000:02:00.0: disp: 0864: 00000000 > > nouveau 0000:02:00.0: disp: 0868: 00000000 -> 04000500 >