From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tempura San Subject: Re: i915 module does not find 82865G if configured as secondary Date: Sun, 09 Oct 2011 22:20:03 +0200 Message-ID: <4E9201F3.9030005@gmail.com> References: <4E906B64.2090702@gmail.com> <4E916AC1.1010104@gmail.com> <20111009101848.GA2947@phenom.ffwll.local> <4E91806D.8010000@gmail.com> <20111009124430.GB2947@phenom.ffwll.local> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Return-path: Received: from mail-bw0-f49.google.com (mail-bw0-f49.google.com [209.85.214.49]) by gabe.freedesktop.org (Postfix) with ESMTP id CDD7A9EC83 for ; Sun, 9 Oct 2011 13:20:05 -0700 (PDT) Received: by mail-bw0-f49.google.com with SMTP id t2so9228797bka.36 for ; Sun, 09 Oct 2011 13:20:05 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Chris Wilson Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org I've integrated your patches into the i915 driver I am using. If I just rebuild the module the result is the same as with Daniel's suggestion. As there is also a change in vgaarb.c - which is not a module - I need to do a full build and check again. If this is not fixing the behaviour either, is there a possibility to use a recent i915 driver with this kernel? Yours, Tempura On Sun, 09 Oct 2011 19:36:27 +0100, Chris Wilson wrote: > On Sun, 9 Oct 2011 14:44:30 +0200, Daniel Vetter wrote: >> On Sun, Oct 09, 2011 at 01:07:25PM +0200, Tempura San wrote: >>> Here is the output of lspci -nn: >>> >>> 00:00.0 Host bridge [0600]: Intel Corporation 82865G/PE/P DRAM >>> Controller/Host-Hub Interface [8086:2570] (rev 02) >>> 00:02.0 Display controller [0380]: Intel Corporation 82865G Integrated >>> Graphics Controller [8086:2572] (rev 02) >> The issue seems to be that the igd isn't a VGA pci class device anymore >> when used as secondary. The below (untested) patch should allow to still >> bind the i915 driver. Please test how far that gets us. > Note the old kernel, and probable lack of: > > commit 934f992c763ae1e5eefcce8af769c16444085df7 > Author: Chris Wilson > Date: Thu Jan 20 13:09:12 2011 +0000 > > drm/i915: Recognise non-VGA display devices > = > Starting with SandyBridge (though possible with earlier hacked BIOSes= ), > the BIOS may initialise the IGFX as secondary to a discrete GPU. Prio= r, > it would simply disable the integrated GPU. So we adjust our PCI class > mask to match any DISPLAY_CLASS device. > = > In such a configuration, the IGFX is not a primary VGA controller and > so should not take part in VGA arbitration, and the error return from > vga_client_register() is expected. > = > Signed-off-by: Chris Wilson > Cc: stable@kernel.org > > and > > commit 5fe49d86f9d01044abf687a8cd21edef636d58aa > Author: Chris Wilson > Date: Tue Feb 1 19:43:02 2011 +0000 > > drm/i915: Only bind to function 0 of the PCI device > = > Early chipsets (gen2/3) used function 1 as a placeholder for multi-he= ad. > We used to ignore these since they were not assigned to > PCI_CLASS_DISPLAY_VGA. However with 934f992c7 we attempt to bind to a= ll > Intel PCI_CLASS_DISPLAY devices (and functions) to work in multi-gpu > systems. This fails hard on gen2/3. > = > Reported-by: Ferenc W=C3=A1gner > Tested-by: Ferenc W=C3=A1gner > Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=3D28012 > Signed-off-by: Chris Wilson > Cc: stable@kernel.org > -Chris >