Xen devel - Oct 2004 - Domain 0 hardware problem with nForce2 AGP?

On a real kernel boot, I get:

  agpgart: Detected NVIDIA nForce2 chipset
  agpgart: Maximum main memory to use for agp memory: 816M
  agpgart: AGP aperture is 256M @ 0xc0000000

On a xen kernel boot, I get:

  agpgart: Detected an NVIDIA nForce/nForce2 chipset, but could not find the
secondary devices.

If I look at lspci listings, there are two entries missing in the Xen
kernel version:

  0000:00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev
a3)
  0000:00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev a2)

Now, I am asking, should this work? Do I have a snag in my configs? Or
if it shouldn''t work, should Xen be fixed or should the nForce AGP
driver be fixed? Or am I totally missing something?

-- Naked



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

We don''t support agpgart at the moment.

IIRC, the agpgart driver needs to write to some PCI config-space registers, 
which Xen currently disallows.  The output you''ve posted suggests it
also
needs to see some special bridges too.  Xen hides bridge devices from dom0 
because for all other purposes, it''s not necessary to reveal them.

It may not be too hard to get arggart working (although it''s unlikely
to
happen for 2.0).  If you (or anyone else) is interested in playing around 
with this, we''d provide support.  It seems likely that someone here
will get
round to implementing this eventually though...

Mark

On Monday 25 Oct 2004 01:14, Nuutti Kotivuori wrote:
> On a real kernel boot, I get:
>
>   agpgart: Detected NVIDIA nForce2 chipset
>   agpgart: Maximum main memory to use for agp memory: 816M
>   agpgart: AGP aperture is 256M @ 0xc0000000
>
> On a xen kernel boot, I get:
>
>   agpgart: Detected an NVIDIA nForce/nForce2 chipset, but could not find
> the secondary devices.
>
> If I look at lspci listings, there are two entries missing in the Xen
> kernel version:
>
>   0000:00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge
> (rev a3) 0000:00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev a2)
>
> Now, I am asking, should this work? Do I have a snag in my configs? Or
> if it shouldn''t work, should Xen be fixed or should the nForce AGP
> driver be fixed? Or am I totally missing something?
>
> -- Naked
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel

-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

There was a thread a month or two ago on this (largely with me trying to
get agpgart working here).  It still ends up instantly rebooting for me
when X tries to do any agpgart stuff.  I''ve got a radeon here, and the
agpgart
and drm modules seem happy, it just blows up when X tries to start.  You
may want to read over that and it might give you a few pointers on how to
potentially make progres.  I unfortunately don''t have a serial port on
my
thinkpad, so i haven''t made much progress since then.

				-- Gerald

On Mon, Oct 25, 2004 at 01:39:29AM +0100, Mark A. Williamson
wrote:
> We don''t support agpgart at the moment.
> 
> IIRC, the agpgart driver needs to write to some PCI config-space registers,
> which Xen currently disallows.  The output you''ve posted suggests
it also
> needs to see some special bridges too.  Xen hides bridge devices from dom0 
> because for all other purposes, it''s not necessary to reveal them.
> 
> It may not be too hard to get arggart working (although it''s
unlikely to
> happen for 2.0).  If you (or anyone else) is interested in playing around 
> with this, we''d provide support.  It seems likely that someone
here will get
> round to implementing this eventually though...
> 
> Mark
> 
> On Monday 25 Oct 2004 01:14, Nuutti Kotivuori wrote:
> > On a real kernel boot, I get:
> >
> >   agpgart: Detected NVIDIA nForce2 chipset
> >   agpgart: Maximum main memory to use for agp memory: 816M
> >   agpgart: AGP aperture is 256M @ 0xc0000000
> >
> > On a xen kernel boot, I get:
> >
> >   agpgart: Detected an NVIDIA nForce/nForce2 chipset, but could not
find
> > the secondary devices.
> >
> > If I look at lspci listings, there are two entries missing in the Xen
> > kernel version:
> >
> >   0000:00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI
Bridge
> > (rev a3) 0000:00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev
a2)
> >
> > Now, I am asking, should this work? Do I have a snag in my configs? Or
> > if it shouldn''t work, should Xen be fixed or should the
nForce AGP
> > driver be fixed? Or am I totally missing something?
> >
> > -- Naked
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: IT Product Guide on
ITManagersJournal
> > Use IT products in your business? Tell us what you think of them. Give
us
> > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out
more
> > http://productguide.itmanagersjournal.com/guidepromo.tmpl
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/xen-devel
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
> 

-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

> We don''t support agpgart at the moment.
> 
> IIRC, the agpgart driver needs to write to some PCI config-space registers,
> which Xen currently disallows.  The output you''ve posted suggests
it also
> needs to see some special bridges too.  Xen hides bridge devices from dom0 
> because for all other purposes, it''s not necessary to reveal them.
> 
> It may not be too hard to get arggart working (although it''s
unlikely to
> happen for 2.0).  If you (or anyone else) is interested in playing around 
> with this, we''d provide support.  It seems likely that someone
here will get
> round to implementing this eventually though...
Actually we''re quite forgiving about what can be written to the PCI
config space as there is often all kinds of device-specific stuff
hidden in there. But, yes, we do enough cooking of accesses that we''re
almost certainly messing up in this case.

 -- Keir


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

Mark A. Williamson wrote:
> We don''t support agpgart at the moment.
Ah. In that case, what is the agpgart patch under 2.6.8.1 patches? 
Because I saw that one, I thought that maybe agpgart should work
already.

-- Naked



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

> Mark A. Williamson wrote:
> > We don''t support agpgart at the moment.
> 
> Ah. In that case, what is the agpgart patch under 2.6.8.1 patches? 
> Because I saw that one, I thought that maybe agpgart should work
> already.
It''s a first stab at fixing all the obvious ''technical
bugs'' in
Linux agpgart support, but since we haven''t any of the relevant
hardware we haven''t been able to take it further. [The driver is
generally quite confused about the differences between phys and
bus addresses, which makes me suspect its never been used on
anything other than native x86.]

If you''ve a serial line console set up on your box then it
mightn''t be too hard to get going -- we''d be happy to help.


Ian


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

Ian Pratt wrote:
>> Mark A. Williamson wrote:
>>> We don''t support agpgart at the moment.
>>
>> Ah. In that case, what is the agpgart patch under 2.6.8.1 patches? 
>> Because I saw that one, I thought that maybe agpgart should work
>> already.
>
> It''s a first stab at fixing all the obvious ''technical
bugs'' in
> Linux agpgart support, but since we haven''t any of the relevant
> hardware we haven''t been able to take it further. [The driver is
> generally quite confused about the differences between phys and
> bus addresses, which makes me suspect its never been used on
> anything other than native x86.]
>
> If you''ve a serial line console set up on your box then it
> mightn''t be too hard to get going -- we''d be happy to
help.
I might take a stab at it later on, now I need to see if I can live
without agpgart for a while.

I don''t have a serial line setup handy right now, but I can probably
set it up later on.

-- Naked



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel