All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helmut Wieser <helmut.wieser@ieee.org>
To: xen-devel@lists.xensource.com
Subject: Re: VGA passthrough nVidia NVS 295
Date: Mon, 07 Jun 2010 10:46:57 +0200	[thread overview]
Message-ID: <4C0CB201.7060206@ieee.org> (raw)
In-Reply-To: <201006051738.01437.tobias.geiger@vido.info>

I second that, viridian = 1 doesn't make a difference neither in Windows 
XP x32 or Windows 7 x64.


On 05.06.2010 17:38, Tobias Geiger wrote:
> Hi,
>
> unfortunatly viridian=1 doesn't help with windows7 nvidia gfx passthrough;
> I have it enabled in both xen-cfgs - the one for win7 and the winxp one, so
> this one can be ruled out i think.
>
> Greetings
> Tobias
>
>
>
> Am Samstag 05 Juni 2010 15:17:06 schrieb Pasi Kärkkäinen:
>    
>> On Fri, Jun 04, 2010 at 04:27:38PM -0400, Konrad Rzeszutek Wilk wrote:
>>      
>>> On Thu, Jun 03, 2010 at 03:47:51PM +0200, Tobias Geiger wrote:
>>>        
>>>> Hi Helmut,
>>>>
>>>> i had the same experience with my setup regarding windows7.
>>>> The good news is, there are no such problems with winxp.
>>>>
>>>> Disabling the "Timeout Detection and Recovery (TDR)" Feature in the
>>>> win7 registry doesn't help for my nvlddmkm.sys BSOD, but if i interpret
>>>> the countless google hits regarding  "nvlddmkm.sys 0x00000116" (the
>>>> Error-Code that always appears in the win7 BSOD - is yours also always
>>>> the same?), it's hard to come to a solution:
>>>>          
>>> One thing that might be worth investigating is enabling the veridian
>>>        
>>                                                                 ^
>>
>> Just to correct the typo: viridian
>>
>> :)
>>
>> -- Pasi
>>
>>      
>>> option. I remember that on Windows 2008 and on, it fixed the watchdog
>>> BSOD, which might be what you are hitting (or not).
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>>        
>>      
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>    

      reply	other threads:[~2010-06-07  8:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-02 11:04 VGA passthrough nVidia NVS 295 Helmut Wieser
2010-06-03 13:47 ` Tobias Geiger
2010-06-04 13:07   ` Helmut Wieser
2010-06-04 14:09     ` Tobias Geiger
2010-06-04 14:17       ` Helmut Wieser
2010-06-07 10:08         ` Tobias Geiger
2010-06-07 11:07           ` Helmut Wieser
2010-06-04 20:27   ` Konrad Rzeszutek Wilk
2010-06-05 13:17     ` Pasi Kärkkäinen
2010-06-05 15:38       ` Tobias Geiger
2010-06-07  8:46         ` Helmut Wieser [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C0CB201.7060206@ieee.org \
    --to=helmut.wieser@ieee.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.