From: Mark Hounschell <dmarkh@cfl.rr.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: markh@compro.net, "Bruno Prémont" <bonbons@linux-vserver.org>,
"Intel Graphics Development" <intel-gfx@lists.freedesktop.org>,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] Intel graphics drm issue?
Date: Sun, 14 Oct 2012 07:39:21 -0400 [thread overview]
Message-ID: <507AA469.5070100@cfl.rr.com> (raw)
In-Reply-To: <CAKMK7uEw8D1r4hf_mE1q6kBwZzE+qmSeTui9adX4agj=5MDbWw@mail.gmail.com>
On 10/14/2012 07:26 AM, Daniel Vetter wrote:
> On Sun, Oct 14, 2012 at 12:20 PM, Mark Hounschell <dmarkh@cfl.rr.com> wrote:
>> Hi Daniel,
>>
>> cat /proc/cmdline
>> root=/dev/disk/by-id/ata-INTEL_SSDSC2CW060A3_CVCV205106EB060AGN-part4
>> video=1024x768 noresume splash=silent quiet apm=off nomodeset vga=normal
>> drm.debug=0xe
>>
>> dmesg is attached
>
>>From the dmesg:
>
> [ 1.833195] [drm:drm_pci_agp_init] *ERROR* Cannot initialize the
> agpgart module.
>
> Which is the root-cause preventing i915.ko from loading. Now with 3.7
> we /shouldn't/ all that agp crap any longer on snb/ivb, so I'm a bit
> confused why it still tries to initialize it. Can you maybe attach
> your .config?
>
Did you mean 3.6 above? I used 3.6.2? If I'm using the right kernel I will
apply the patch and try. Let me know.
> Also, we need to employ some dirty runtime tricks to no longer require
> agp on newer chips, since we still need to keep it around for
> backwards-compat with old userspace on old chips. Can you please check
> with the below diff whether this hack works?
>
> Thanks, Daniel
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
> index a7837e5..1152502 100644
> --- a/drivers/gpu/drm/i915/i915_drv.c
> +++ b/drivers/gpu/drm/i915/i915_drv.c
> @@ -842,6 +842,7 @@ i915_pci_probe(struct pci_dev *pdev, const struct
> pci_device_id *ent)
> if (intel_info->gen != 3) {
> driver.driver_features &=
> ~(DRIVER_USE_AGP | DRIVER_REQUIRE_AGP);
> + printk("dropping agp requirement\n");
> } else if (!intel_agp_enabled) {
> DRM_ERROR("drm/i915 can't work without intel_agp module!\n");
> return -ENODEV;
>
Doesn't this patch only add a printk? Is that what you want me to do?
Mark
next prev parent reply other threads:[~2012-10-14 11:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 12:54 Intel graphics drm issue? Mark Hounschell
2012-10-12 21:14 ` Bruno Prémont
2012-10-13 18:57 ` Mark Hounschell
2012-10-13 19:17 ` Mark Hounschell
2012-10-14 8:41 ` Bruno Prémont
2012-10-14 10:34 ` Mark Hounschell
2012-10-14 10:52 ` Mark Hounschell
2012-10-14 11:03 ` Bruno Prémont
2012-10-14 16:54 ` Mark Hounschell
2012-10-14 17:22 ` Bruno Prémont
2012-10-14 18:03 ` Mark Hounschell
2012-10-14 18:19 ` Bruno Prémont
2012-10-14 18:57 ` Mark Hounschell
2012-10-14 20:40 ` Bruno Prémont
2012-10-15 9:58 ` Mark Hounschell
2012-10-14 8:58 ` [Intel-gfx] " Daniel Vetter
2012-10-14 10:20 ` Mark Hounschell
2012-10-14 11:26 ` Daniel Vetter
2012-10-14 11:39 ` Mark Hounschell [this message]
2012-10-14 14:19 ` Mark Hounschell
2012-10-14 14:40 ` Daniel Vetter
2012-10-14 15:41 ` Mark Hounschell
2012-10-14 15:53 ` Daniel Vetter
2012-10-14 15:55 ` Bruno Prémont
2012-10-14 16:09 ` Mark Hounschell
2012-10-14 16:13 ` Mark Hounschell
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=507AA469.5070100@cfl.rr.com \
--to=dmarkh@cfl.rr.com \
--cc=bonbons@linux-vserver.org \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
/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