Date: Fri, 11 Mar 2005 22:46:03 +0000
From: "J.A. Magallon" <jamagallon@able.es>
Subject: Re: AGP bogosities
To: Dave Jones <davej@redhat.com>
Cc: Paul Mackerras <paulus@samba.org>, torvalds@osdl.org,
       benh@kernel.crashing.org, linux-kernel@vger.kernel.org
References: <16944.62310.967444.786526@cargo.ozlabs.ibm.com>
	<1110579068l.8904l.0l@werewolf.able.es> <20050311221838.GG4185@redhat.com>
In-Reply-To: <20050311221838.GG4185@redhat.com> (from davej@redhat.com on
	Fri Mar 11 23:18:39 2005)
Message-Id: <1110581163l.5796l.0l@werewolf.able.es>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2946
Lines: 66


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

Thanks.

--
J.A. Magallon <jamagallon()able!es>     \               Software is like sex:
werewolf!able!es                         \         It's better when it's free
Mandrakelinux release 10.2 (Cooker) for i586
Linux 2.6.11-jam3 (gcc 3.4.3 (Mandrakelinux 10.2 3.4.3-6mdk)) #2


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/