From: Alexey Fisher <bug-track@fisher-privat.net>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: [regression] agp/intel: Sandybridge doesn't require GMCH enabling
Date: Sun, 31 Oct 2010 11:29:18 +0100 [thread overview]
Message-ID: <1288520958.5299.4.camel@zwerg> (raw)
after commit e380f60b22eddec7825224b8d788572c82b63161
intel driver filed to load, so system fallback to vesa driver.
here is the interisting part of the dmesg:
[ 2.559921] agpgart-intel 0000:00:00.0: detected 32768K stolen memory
[ 2.559957] pci 0000:00:02.0: failed to enable the GTT: GMCH_CTRL=350
[ 2.559988] agpgart-intel 0000:00:00.0: error configuring host
chipset
[ 2.560069] agpgart-intel 0000:00:00.0: agp_backend_initialize()
failed
[ 2.560077] agpgart-intel: probe of 0000:00:00.0 failed with error
-22
[ 2.560252] [drm] Initialized drm 1.1.0 20060810
[ 2.560272] [drm:i915_init] *ERROR* drm/i915 can't work without
intel_agp module!
last working version 2.6.36-07538-gc584fe4
my hardware, Intel DG45ID board,
intel_stepping
Vendor: 0x8086, Device: 0x2e22, Revision: 0x03 (A3)
--
Regards,
Alexey
next reply other threads:[~2010-10-31 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 10:29 Alexey Fisher [this message]
2010-10-31 10:31 ` [regression] agp/intel: Sandybridge doesnt require GMCH enabling Chris Wilson
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=1288520958.5299.4.camel@zwerg \
--to=bug-track@fisher-privat.net \
--cc=intel-gfx@lists.freedesktop.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