From owner-freebsd-stable@FreeBSD.ORG Sat Jun 23 11:38:39 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D5AE210657A7 for ; Sat, 23 Jun 2012 11:38:39 +0000 (UTC) (envelope-from thomas.e.zander@googlemail.com) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by mx1.freebsd.org (Postfix) with ESMTP id 4B50A8FC14 for ; Sat, 23 Jun 2012 11:38:39 +0000 (UTC) Received: by wibhn6 with SMTP id hn6so1177216wib.13 for ; Sat, 23 Jun 2012 04:38:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Zx9Rw9TTqxdS9MDtSmFQXZ+pqpf5IyxdbEMUnHHuX8w=; b=Vx3k1SHeKgcE5t5wmIbkuwoHOmN7VjjesM+xteDtb7S3Z/XQbqwOGSKk1MDXEgFAT1 yvKUYYUVdej4plqZupK2q3D9rY6DamYyL71B98ILPVPdyTbBKFb5NUJJhhk4zVb13Vmb 8HyjJPpW9oRSAJIn6mTM+MT9CXTx78xQ4Xxg3TtFD1cUKuXEwJEe9HFmFbAQ7b6VxvYs Z0KZDB133+EOKuEjrtyTdAVXUuFXwBPJDWs7Kt87Roc1YOw2rruG5Bq8qS+GK3CZIf3M Cfp0NnULy89zO7GOA3RPVhJTODa3VOtfUTVGfI9ILW08+1wyxGNtQEm7HQsPavVHXf1z KNSw== MIME-Version: 1.0 Received: by 10.216.228.29 with SMTP id e29mr3027318weq.153.1340451516004; Sat, 23 Jun 2012 04:38:36 -0700 (PDT) Received: by 10.223.155.72 with HTTP; Sat, 23 Jun 2012 04:38:35 -0700 (PDT) In-Reply-To: <20120623085952.GO2337@deviant.kiev.zoral.com.ua> References: <20120622175128.GJ2337@deviant.kiev.zoral.com.ua> <20120622183808.GK2337@deviant.kiev.zoral.com.ua> <20120623085952.GO2337@deviant.kiev.zoral.com.ua> Date: Sat, 23 Jun 2012 13:38:35 +0200 Message-ID: From: Thomas Zander To: Konstantin Belousov Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable Subject: Re: KMS on Sandy bridge error device_attach X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jun 2012 11:38:39 -0000 On Sat, Jun 23, 2012 at 10:59 AM, Konstantin Belousov 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: port 0xf000-0xf03f mem 0xfb400000-0xfb7fffff,0xd0000000-0xdfffffff irq 16 at device 2.0 on pci0 drmn0: 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 > 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? Best regards Riggs