All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-tools@lists.xensource.com, xen-devel@lists.xensource.com,
	Onkar Mahajan <kern.devel@gmail.com>,
	xen-users@lists.xensource.com,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Video driver update
Date: Fri, 18 Jun 2010 06:35:51 +0200	[thread overview]
Message-ID: <4C1AF7A7.7000409@ts.fujitsu.com> (raw)
In-Reply-To: <4C1A2F48.1070404@goop.org>

On 06/17/2010 04:20 PM, Jeremy Fitzhardinge wrote:
> On 06/17/2010 02:20 PM, Konrad Rzeszutek Wilk wrote:
>> On Thu, Jun 17, 2010 at 05:02:41PM +0530, Onkar Mahajan wrote:
>>
>>> Hi,
>>>
>>> When I boot into the dom0 kernel. The system is not able to find the
>>> NVIDIA video driver.Normally , when I update the non-pvops kernel
>>> I switch the virtual console and install the
>>> video driver and reboot , then the video driver module gets installed.
>>> But I am not able to do similar thing in the case of pvops kernel.
>>> How can I keep this video driver installed across the kernel updates.
>>> Note that this driver is a proprietary driver from NVIDIA.
>>>
>>> (NVIDIA-Linux-x86_64-195.36.
>>> 31-pkg2.run)
>>>
>> I would think this would not work.. but you never know. Did you run the
>> package? Did it install/compile the modules? Did it change your Xorg
>> file? Did you crank up the verbosity of the kernel and Xen to see what
>> is happening.
>>
>> Please do look at the PVOPS Wiki (just google for it) for how to set
>> those verbosity functions.
>>
>
> As far as I know, the nvidia installer explicitly tests for Xen and does
> nothing/fails if present.

This can be handled by setting the shell variable

IGNORE_XEN_PRESENCE=1

before starting the installer.


Juergen

-- 
Juergen Gross                 Principal Developer Operating Systems
TSP ES&S SWE OS6                       Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

  reply	other threads:[~2010-06-18  4:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17 11:32 Video driver update Onkar Mahajan
2010-06-17 12:36 ` Maarten Vanraes
2010-06-17 13:20 ` Konrad Rzeszutek Wilk
2010-06-17 14:20   ` Jeremy Fitzhardinge
2010-06-18  4:35     ` Juergen Gross [this message]
2010-06-18 14:37       ` [Xen-devel] " Konrad Rzeszutek Wilk

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=4C1AF7A7.7000409@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --cc=jeremy@goop.org \
    --cc=kern.devel@gmail.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-tools@lists.xensource.com \
    --cc=xen-users@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.