For the tests I've done, I've tried the last driver .i.e 280.26.
It failed.
So I use the old 275.33 and it works like a charm :) on
- XP Pro 32 bits SP3
- XP Pro 64 bits SP2
I can launch Crysis 2 and play the game :)
Have a look at http://www.youtube.com/watch?v=3SaYO0ERW44
Well I am a little limited with my graphic card (MSI GT 440 1GB for resolution and XP) but it is just enough for me
on a resolution like 1440x900 ou 1600x??? to play the
game.
Do not forget to adapt dsd to the requires ranges of your graphic card.
This is what I did for my card
-----------------------------------------------------------------------------------
root@mercury:~# lspci |grep VGA
01:00.0 VGA compatible controller: nVidia Corporation Device 0de0 (rev a1)
root@mercury:~# dmesg | grep 01:00.0 |grep mem
[ 3.124546] pci 0000:01:00.0: reg 10: [mem 0xfa000000-0xfaffffff]
[ 3.124565] pci 0000:01:00.0: reg 14: [mem 0xc0000000-0xcfffffff 64bit pref]
[ 3.124584] pci 0000:01:00.0: reg 1c: [mem 0xd0000000-0xd1ffffff 64bit pref]
[ 3.124609] pci 0000:01:00.0: reg 30: [mem 0xfb000000-0xfb07ffff pref]
[ 3.199436] vgaarb: device
added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
[ 3.199730] pci 0000:01:00.0: BAR 0: reserving [mem 0xfa000000-0xfaffffff flags 0x40200] (d=0, p=0)
[ 3.199732] pci 0000:01:00.0: BAR 1: reserving [mem 0xc0000000-0xcfffffff flags 0x14220c] (d=0, p=0)
[ 3.199735] pci 0000:01:00.0: BAR 3: reserving [mem 0xd0000000-0xd1ffffff flags 0x14220c] (d=0, p=0)
root@mercury:~# cat gfx_patch/dsdt.asl.patch
--- tools/firmware/hvmloader/acpi/dsdt.asl 2011-08-13 18:43:39.000000000 +0200
+++ tools/firmware/hvmloader/acpi/dsdt.asl 2011-08-13 18:58:25.000000000 +0200
@@ -173,15 +173,43 @@ DefinitionBlock ("DSDT.aml", "DSDT", 2,
0x00000000,
0x00020000)
+ /* reserve MMIO BARs of gfx for 1:1 mapping */
DWordMemory(
ResourceProducer, PosDecode, MinFixed, MaxFixed,
Cacheable,
ReadWrite,
0x00000000,
- 0xF0000000,
- 0xF4FFFFFF,
+ 0xFA000000,
+ 0xFAFFFFFF,
0x00000000,
- 0x05000000,
- ,, _Y01)
+ 0x01000000)
+
+ DWordMemory(
+ ResourceProducer, PosDecode, MinFixed, MaxFixed,
+ NonCacheable,
ReadWrite,
+ 0x00000000,
+ 0xC0000000,
+ 0xCFFFFFFF,
+ 0x00000000,
+ 0x10000000)
+
+
DWordMemory(
+ ResourceProducer, PosDecode, MinFixed, MaxFixed,
+ Cacheable, ReadWrite,
+ 0x00000000,
+ 0xD0000000,
+
0xD1FFFFFF,
+ 0x00000000,
+ 0x02000000)
+
+ DWordMemory(
+ ResourceProducer, PosDecode, MinFixed, MaxFixed,
+ Cacheable, ReadWrite,
+
0x00000000,
+ 0xFB000000,
+ 0xFB07FFFF,
+ 0x00000000,
+ 0x00080000,
+ ,, _Y01)
})
CreateDWordField(PRT0, \_SB.PCI0._CRS._Y01._MIN, MMIN)
De : komkon555 <komkon555@xxxxxxxxxx>
À : xen-devel@xxxxxxxxxxxxxxxxxxx
Envoyé le : Mardi 6 Septembre 2011 12h57
Objet : [Xen-devel] Re: Patches for VGA-Passthrough XEN 4.2 unstable
Hallo. I tested the new patches. The patched version of
xen-unstable let start/shutdown Windows XP
normally. But the current nvidia
driver is not yet functional: question-sign in device-manager windows.
This problem is very sadly, because it makes no sense to use gfx-passthrough
for nvidia cards.
Anyway thank you a lot for patches. I see some progress against
the old one.
P.S. Hardware as above.
--
View this message in context:
http://xen.1045712.n5.nabble.com/Patches-for-VGA-Passthrough-XEN-4-2-unstable-tp4406265p4774097.htmlSent from the Xen - Dev mailing list archive at Nabble.com.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxhttp://lists.xensource.com/xen-devel