From owner-svn-ports-head@freebsd.org Thu Apr 20 17:08:38 2017 Return-Path: Delivered-To: svn-ports-head@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 92DE3D4879B; Thu, 20 Apr 2017 17:08:38 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6B1F1218; Thu, 20 Apr 2017 17:08:38 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id 94E1774C8; Thu, 20 Apr 2017 17:08:37 +0000 (UTC) Date: Thu, 20 Apr 2017 17:08:37 +0000 From: Alexey Dokuchaev To: Matthew Rezny Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r433902 - head Message-ID: <20170420170837.GA10533@FreeBSD.org> References: <201702111903.v1BJ3sMj021042@repo.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201702111903.v1BJ3sMj021042@repo.freebsd.org> User-Agent: Mutt/1.7.1 (2016-10-04) X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 17:08:38 -0000 On Sat, Feb 11, 2017 at 07:03:54PM +0000, Matthew Rezny wrote: > New Revision: 433902 > URL: https://svnweb.freebsd.org/changeset/ports/433902 > > Log: > Add UPDATING entry for Xorg server 1.18.4 > > Modified: head/UPDATING > ... > +20170211: > + AFFECTS: users of x11-server/xorg-server > + AUTHOR: rezny@FreeBSD.org > + > + Xorg server has been updated to 1.18.4 and autodetection has changed. I've just had a chance to upgrade X.org/Mesa ports on my fresh -CURRENT laptop, and noticed that X.org server indeed won't startup unless I load radeonkms.ko module by hand. I understand that this entry specifically talks about it, but would like to clarify a few things if you don't mind: > + The order in which drivers are now attempted is: > + 1) vendor/model specific driver according to PCI IDs > + 2) generic modesetting driver which requires a drm driver with KMS > + 3) scfb, the generic framebuffer driver > + 4) vesa (only if arch is x86) Can you recall what was the previous order? > + This should minimize the need for xorg.conf files. Didn't have one for a quite a few years now, didn't know it was still needed. ;-) > + i.e. kld_list="i915kms.ko", to ensure correct functionality. Although > + the vendor drivers may attempt to load the correct drm driver, which > + does not always work, the modesetting driver assumes the required KMS Any ideas why it does not work now with AMD A8 APU (Aruba, NI)? I don't mind loading it by hand or via kld_list, but still want to know what had broken automatic loading in my case (as it worked fine before). > + driver is already loaded and will fail if there is none. The modesetting > + driver is now recommended as an alternative to the Intel driver; the > + performance is comparable and stability is better with modesetting. The > + ATI driver continues to offer better performance than modesetting. Can you elaborate a bit on the last sentense (my context is solely AMD/ATI, I don't own or care about Intel hardware). Thanks, ./danfe