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.
Testing latest -bk would be useful.
It has Paul's patch, and a few others.
Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
