From: Chuck Ebbert <cebbert@redhat.com>
To: Carlo Wood <carlo@alinoe.com>, Dave Airlie <airlied@gmail.com>,
Dave Jones <davej@redhat.com>,
linux-kernel@vger.kernel.org, eric@anholt.net
Subject: Re: [AGPGART] intel_agp: use table for device probe
Date: Mon, 18 Jun 2007 13:42:13 -0400 [thread overview]
Message-ID: <4676C3F5.5070501@redhat.com> (raw)
In-Reply-To: <20070618023726.GA7594@zhen-devel.sh.intel.com>
On 06/17/2007 10:37 PM, Wang Zhenyu wrote:
> On 2007.06.18 03:56:36 +0000, Carlo Wood wrote:
>> On Mon, Jun 18, 2007 at 10:57:38AM +1000, Dave Airlie wrote:
>>>> Right now, I'm at a loss to explain the corruption, so it's
>>>> difficult to suggest what to try.
>>> The thing is here, this is PCIE, so if there is a GPU plugged into the
>>> PCIE 16x slot in theory the main onboard graphics should disable, AGP
>>> code is used to control the GART for the onboard chip, in this case a
>>> plugged in card will not use AGP, I wonder have Intel tested with a
>>> pcie card in place...
>
> Agree. We seem to always enable AGP even IGD is disabled or not exists,
> other card should not depend on this module ever.
>
>> That is Chinese for me :/.
>> Do you want me to try something?
>
> Carlo, I've just built latest kernel git tree on a Dell 965G box and
> have a NV card plugged-in. It boots fine.
>
> Linux agpgart interface v0.102 (c) Dave Jones
> agpgart: Detected an Intel 965G Chipset.
> agpgart: AGP aperture is 256M @ 0x0
>
> I don't know why it hangs your machine when loading this module, it should
> just not bother anything. But from your last "modprobe: ..." line, it seems
> there's really badness somewhere, do you have serial console to see more
> in the message?
There are also these bug reports:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229913
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242101
next prev parent reply other threads:[~2007-06-18 17:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 8:02 DRI/AGP on AMD64 based machine Alex Bennee
2007-06-13 16:29 ` Dave Jones
2007-06-14 1:15 ` Carlo Wood
2007-06-14 1:17 ` Dave Airlie
2007-06-14 4:36 ` Carlo Wood
2007-06-14 4:40 ` Dave Airlie
2007-06-17 16:22 ` [AGPGART] intel_agp: use table for device probe Carlo Wood
2007-06-17 19:07 ` Dave Jones
2007-06-17 19:59 ` Carlo Wood
2007-06-17 20:49 ` Dave Jones
2007-06-17 21:13 ` Carlo Wood
2007-06-17 21:33 ` Dave Jones
2007-06-17 21:55 ` Carlo Wood
2007-06-17 22:19 ` Carlo Wood
2007-06-17 22:36 ` Carlo Wood
2007-06-17 22:49 ` Dave Jones
2007-06-18 0:06 ` Carlo Wood
2007-06-18 0:16 ` Dave Jones
2007-06-18 0:57 ` Dave Airlie
2007-06-18 1:56 ` Carlo Wood
2007-06-18 2:18 ` Dave Airlie
2007-06-18 17:37 ` Carlo Wood
2007-06-18 2:37 ` Wang Zhenyu
2007-06-18 17:42 ` Chuck Ebbert [this message]
2007-06-18 18:06 ` Dave Jones
2007-06-18 20:13 ` Carlo Wood
2007-06-18 19:58 ` Carlo Wood
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=4676C3F5.5070501@redhat.com \
--to=cebbert@redhat.com \
--cc=airlied@gmail.com \
--cc=carlo@alinoe.com \
--cc=davej@redhat.com \
--cc=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox