All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Rik van Riel <riel@redhat.com>
Cc: Jerome Brown <jerome@hub.net.nz>,
	xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: AGP & Binary Nvidia Drivers
Date: Wed, 02 Mar 2005 15:24:13 -0800	[thread overview]
Message-ID: <42264B1D.5000909@diku.dk> (raw)
In-Reply-To: <Pine.LNX.4.61.0503020105510.1691@chimarrao.boston.redhat.com>

Rik van Riel wrote:
> On Wed, 2 Mar 2005, Jerome Brown wrote:
> 
> 
>>Any ideas as to where to look and/or what more information you would
>>like would be greatly appreciated.
> 
> 
> Yeah, the Nvidia people will probably need to create a
> special version of their driver that knows that virt
> to phys conversion inside Xen virtual hosts is different.
> 

Actually, for the Radeon driver all the important stuff seemed to have 
nice abstractions in the open source part of the driver, and I was able 
to get that running.

A few things that might help you when debugging:

a) before you run X, log in via SSH. Run it from there with just 'X' 
instead of via gdm or startx, and inspect its output and log files. Also 
have a look to see if any errors are reported by 'dmesg'.

b) If the driver loads a kernel module, check dmesg before and after the 
module is loaded (again, better to load it yourself by hand), and see if 
anything appears to be wrong.

Remember that you need to recompile the open source parts of the nvidia 
driver with the headers from the xenlinux kernel, or nothing will work, 
but also remember to keep the old non-Xen version around. Then you can 
boot normal linux, load the module and start X, and note down all the 
relevant parts of the logs, so that you can compare against them when 
trying to run things in Xen. Hopefully the difference between the logs 
should give a hint about what stuff goes wrong.

Finally, look in the open source part of the module for stuff like 
virt_to_phys*, remap_pfn*, etc., to see if there is anything obvious there.

There is a previous thread on the list about the Radeon, wherein Ian 
gives a lot of good clues about how to solve this problem.

Good luck!

Jacob


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-03-02 23:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02  4:19 AGP & Binary Nvidia Drivers Jerome Brown
2005-03-02  6:06 ` Rik van Riel
2005-03-02 23:24   ` Jacob Gorm Hansen [this message]
2005-03-03  2:35     ` Jerome Brown
  -- strict thread matches above, loose matches on Subject: below --
2005-03-02  8:00 Ian Pratt
2005-03-03  9:31 Ian Pratt
2005-03-03 12:24 ` Nuutti Kotivuori
2005-03-06 20:04 ` Jerome Brown

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=42264B1D.5000909@diku.dk \
    --to=jacobg@diku.dk \
    --cc=jerome@hub.net.nz \
    --cc=riel@redhat.com \
    --cc=xen-devel@lists.sourceforge.net \
    /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.