Re: AGP bogosities

Martin Schlemmer
2005-03-11T23:26:56Z

[-- Attachment #1: Type: text/plain, Size: 3843 bytes --]

On Fri, 2005-03-11 at 23:17 +0000, J.A. Magallon wrote:
> On 03.12, Martin Schlemmer wrote:
> > On Fri, 2005-03-11 at 22:46 +0000, J.A. Magallon wrote:
> > > On 03.11, Dave Jones wrote:
> > > > On Fri, Mar 11, 2005 at 10:11:08PM +0000, J.A. Magallon wrote:
> > > > >
> > > > > On 03.11, Paul Mackerras wrote:
> > > > > > Linus,
> > > > > >
> > > > > ...
> > > > > >
> > > > > > Oh, and by the way, I have 3D working relatively well on my G5 with a
> > > > > > 64-bit kernel (and 32-bit X server and clients), which is why I care
> > > > > > about AGP 3.0 support. :)
> > > > > >
> > > > >
> > > > > I think it is not a G5 only problem. I have a x8 card, a x8 slot, but
> > > > > agpgart keeps saying this:
> > > > >
> > > > > Mar 11 23:00:28 werewolf dm: Display manager startup succeeded
> > > > > Mar 11 23:00:29 werewolf kernel: agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
> > > > > Mar 11 23:00:29 werewolf kernel: agpgart: reserved bits set in mode 0xa. Fixed.
> > > > > Mar 11 23:00:29 werewolf kernel: agpgart: X passes broken AGP2 flags (2) in AGP3 mode. Fixed.
> > > > > Mar 11 23:00:29 werewolf kernel: agpgart: Putting AGP V3 device at 0000:00:00.0 into 4x mode
> > > > > Mar 11 23:00:29 werewolf kernel: agpgart: Putting AGP V3 device at 0000:01:00.0 into 4x mode
> > > > > Mar 11 23:00:29 werewolf kernel: agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
> > > > > Mar 11 23:00:29 werewolf kernel: agpgart: reserved bits set in mode 0xa. Fixed.
> > > > > Mar 11 23:00:29 werewolf kernel: agpgart: X passes broken AGP2 flags (2) in AGP3 mode. Fixed.
> > > > > Mar 11 23:00:29 werewolf kernel: agpgart: Putting AGP V3 device at 0000:00:00.0 into 4x mode
> > > > > Mar 11 23:00:29 werewolf kernel: agpgart: Putting AGP V3 device at 0000:01:00.0 into 4x mode
> > > > >
> > > > > The nvidia driver (brand new 1.0-7167, now works with stock -mm) tells me
> > > > > it is in x8 mode, but i suspect it lies....
> > > > >
> > > > > Will try your patch right now.
> > > >
> > >
> > > Looks fine, now I got:
> > >
> > > agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
> > > agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
> > > agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
> > > agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
> > > agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
> > > agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
> > >
> > > werewolf:~> lspci
> > > 00:00.0 Host bridge: Intel Corporation 82875P/E7210 Memory Controller Hub (rev 02)
> > > 00:01.0 PCI bridge: Intel Corporation 82875P Processor to AGP Controller (rev 02)
> > > ...
> > > 01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)
> > >
> > > BTW, I had to patch the nVidia driver. It just tries up to x4 AGP...
> > >
> >
> > New and old one works fine with Paul's patch:
> >
> > --old--
> > agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
> > agpgart: X tried to set rate=x12. Setting to AGP3 x8 mode.
> > agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
> > agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
> > -------
> >
> > (ok, so old driver is a bit dodgy)
> >
> > --new--
> > agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
> > agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
> > agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
> > -------
> >
>
> Just curiosity, what says your /proc/driver/nvidia/agp/status ?
>

-----
# cat /proc/driver/nvidia/agp/status
Status: Enabled
Driver: AGPGART
AGP Rate: 8x
Fast Writes: Enabled
SBA: Enabled
-----

--
Martin Schlemmer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]