From owner-freebsd-x11@freebsd.org Fri Mar 24 15:23:51 2017 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1215CD1B2B0 for ; Fri, 24 Mar 2017 15:23:51 +0000 (UTC) (envelope-from info@microlinux.fr) Received: from smtp.nfrance.com (smtp-4.nfrance.com [80.247.229.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CDC27FBF; Fri, 24 Mar 2017 15:23:50 +0000 (UTC) (envelope-from info@microlinux.fr) Received: from alphamule.microlinux.lan (nikikovacs.pck.nerim.net [62.212.104.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.nfrance.com (Postfix) with ESMTPSA id E052412B0ED; Fri, 24 Mar 2017 16:23:40 +0100 (CET) Reply-To: info@microlinux.fr Subject: Re: Can't configure Intel video card: hard freeze or fallback to VESA References: <20170323144435.GB87700@rancor.immure.com> <4a94ed70-fa86-79e1-c036-4f5f9bdd8187@feinen.com> To: Stephan Feinen , cem@freebsd.org, Bob Willcox Cc: x11-list freebsd From: Nicolas Kovacs Organization: Microlinux Message-ID: <6a455e9a-780e-030c-db12-52c60e66e847@microlinux.fr> Date: Fri, 24 Mar 2017 16:23:39 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: <4a94ed70-fa86-79e1-c036-4f5f9bdd8187@feinen.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.78 on 80.247.229.46 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Mar 2017 15:23:51 -0000 Le 23/03/2017 à 18:05, Stephan Feinen a écrit : > I had a similar problem last week. After an update, the intel driver stopped > working and xorg used the vesa driver instead. > > I then found out that the i915kms wasn't loaded automatically anymore. > All how-to articles warned "do not add the module to loader.conf, because a failure > may render your system inoperable. Instead add the module to /etc/rc.conf". > > I tested the module with kldload and it worked, so I added the module to rc.conf > ("kld_list="i915kms") and everything was fine. After two long days of experimenting, it seems like I finally found the solution. There are two distinct Intel drivers in /boot/kernel: i915 and i915.kms. Loading i915kms on that machine (at any time) leads to an instant system freeze. The plain i915 driver loads fine, on the other hand. X starts perfectly, even without the slightest configuration stub. Thanks everybody for your help. Cheers from the rainy South of France, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info@microlinux.fr Tél. : 04 66 63 10 32