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@gmai...> 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
> 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
Loading i915kms from loader.conf is something I do not encourage
right now, since you loose VGA console somewhere during the kernel
> > 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.