Date: Sat, 23 Jun 2012 15:08:40 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Thomas Zander <thomas.e.zander@googlemail.com> Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: KMS on Sandy bridge error device_attach Message-ID: <20120623120840.GT2337@deviant.kiev.zoral.com.ua> In-Reply-To: <CAFU734wegbSMoXo5kghRbS4P=qv1-RxFkPFu-OyWi74UZ_P=KA@mail.gmail.com> References: <CAFU734xpgn3HfS%2BjgaT_T9BLA0-P32wmHo9Pp74Mg4a4fh2TDw@mail.gmail.com> <20120622175128.GJ2337@deviant.kiev.zoral.com.ua> <CAFU734z97JcLRKXfuDaCWuy6V5exnHufS3QGfa_PyE9cTWFoOw@mail.gmail.com> <20120622183808.GK2337@deviant.kiev.zoral.com.ua> <CAFU734yfPtkN3yJRJUnRZLSeSO-fwaz-W=ZNyLDGD8qcZH_jDg@mail.gmail.com> <20120623085952.GO2337@deviant.kiev.zoral.com.ua> <CAFU734wegbSMoXo5kghRbS4P=qv1-RxFkPFu-OyWi74UZ_P=KA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On Sat, Jun 23, 2012 at 01:38:35PM +0200, Thomas Zander wrote:
> On Sat, Jun 23, 2012 at 10:59 AM, Konstantin Belousov
> <kostikbel@gmail.com> wrote:
> > Ok, but you did not tried to load i915kms, at least the dmesg you posted
> > lacks an indication.
>
> Actually, it did. i915kms was in loader.conf.
>
> dmesg, line 37f:
> Preloaded elf obj module "/boot/kernel/i915kms.ko" at 0xffffffff8113a820.
> Preloaded elf obj module "/boot/kernel/drm2.ko" at 0xffffffff8113ae88.
> ...
> dmesg, lines 482-489:
> vgapci0: <VGA-compatible display> port 0xf000-0xf03f mem
> 0xfb400000-0xfb7fffff,0xd0000000-0xdfffffff irq 16 at device 2.0 on
> pci0
> drmn0: <Intel SandyBridge (M)> on vgapci0
> vgapci0: attempting to allocate 1 MSI vectors (1 supported)
> msi: routing MSI IRQ 264 to local APIC 0 vector 59
> vgapci0: using IRQ 264 for MSI
> info: [drm] MSI enabled 1 message(s)
> error: [drm:pid0:drm_load] *ERROR* Card isn't AGP, or couldn't initialize AGP.
> device_attach: drmn0 attach returned 12
Do you have agp.ko loaded from loader.conf ? If not, what happens
if you add it there ?
The i915kms does have a dependency on agp, so it should have been
auto-loaded if not loaded explicitely. And agp should be probed at
least.
Loading i915kms from loader.conf is something I do not encourage
right now, since you loose VGA console somewhere during the kernel
startup.
>
> > Let me repeat: I need to see the lines related to the agp probe and
> > attachment, I believe that it will show us the next direction to
> > investigate.
>
> I did understand what you were after, but sorry, there is nothing more
> in the dmesg output. Do I need to perform additional steps besides
> verbose boot to obtain this data?
Hmm, I probably see an issue. Please try the patch below.
diff --git a/sys/dev/agp/agp_i810.c b/sys/dev/agp/agp_i810.c
index a181ad7..c0f592c 100644
--- a/sys/dev/agp/agp_i810.c
+++ b/sys/dev/agp/agp_i810.c
@@ -700,7 +700,7 @@ static const struct agp_i810_match {
.driver = &agp_i810_sb_driver
},
{
- .devid = 0x01088086,
+ .devid = 0x010a8086,
.name = "SandyBridge server IG",
.driver = &agp_i810_sb_driver
},
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (FreeBSD)
iEYEARECAAYFAk/lscgACgkQC3+MBN1Mb4jamACfSfjyvwJSnZhUXEABLLOMo88c
N10An2YojGmGweGrx7gCFytBFZs3I9zI
=0Oeq
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120623120840.GT2337>