All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerome Brown <jerome@hub.net.nz>
To: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: AGP & Binary Nvidia Drivers
Date: Thu, 03 Mar 2005 15:35:55 +1300	[thread overview]
Message-ID: <4226780B.8070501@hub.net.nz> (raw)
In-Reply-To: <42264B1D.5000909@diku.dk>

Jacob Gorm Hansen wrote:
<snip>
> 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.

Well, I decided to start here. I removed the old driver and tried to
reinstall it, to be told that it requires MTRR to be enabled in the
kernel. (I must have accidently compiled against the wrong sources last
time). When I try to add this to with ARCH="xen" make menuconfig, the
option does not present itself. Is there a way to enable this in the
config, or would doing so be A Bad Thing (TM)? (I am also interested in
getting my soundcard going, and the ALSA sections are also not
displayed, but that is the next challenge!)

The good news is that I am writing this in X under a Xen kernel using
the opensource Nvidia Driver that is shipped with X.org - however it is
not as responsive, nor does the 3D work.

> 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.

What would be obvious? I know a little C, but that is about the strength
of it. I'm willing to have a look and play, but don't really know what I
am doing in the internals of code :)

> Good luck!

Thanks. I think I need it! :)

Thanks again for the help

-- 
Jerome Brown
Technology Architect
Hub.Net

P: +64  3 961-5116
M: +64 29 453 7663
F: +64  3 961-5129
E: jerome@hub.net.nz
W: http://www.hub.net.nz/
O: Level 4, 818 Colombo St, Christchurch, New Zealand
S: PO Box 1879, Christchurch, New Zealand


-------------------------------------------------------
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-03  2:35 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
2005-03-03  2:35     ` Jerome Brown [this message]
  -- 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=4226780B.8070501@hub.net.nz \
    --to=jerome@hub.net.nz \
    --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.