Date: Mon, 13 Feb 2017 05:24:45 -0800 From: David Wolfskill <david@catwhisker.org> To: "Matthew D. Fuller" <fullermd@over-yonder.net>, Baptiste Daroussin <bapt@FreeBSD.org> Cc: x11@freebsd.org Subject: Re: X11 breaks for Intel after ports update from r433396 -> r433935? Message-ID: <20170213132445.GT1208@albert.catwhisker.org> In-Reply-To: <20170213125721.trufcakdjjpp2psq@ivaldir.etoilebsd.net> <20170213125626.GD83266@over-yonder.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--D5tFrmRBv7YOLFOK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 13, 2017 at 06:56:26AM -0600, Matthew D. Fuller wrote: > ... > 'k, so not the LLVM issue. I'd say the problem is around >=20 > > | [ 77486.077] (--) Using syscons driver with X support (version 2.0) > > | [ 77486.077] (--) using VT number 9 > > | > > | [ 77486.230] (EE) open /dev/dri/card0: No such file or directory > > | [ 77486.230] (WW) Falling back to old probe method for modesetting > > | [ 77486.230] (EE) open /dev/dri/card0: No such file or directory >=20 > where it just can't connect to the DRI stuff. Are you pre-loading the > KMS .ko? UPDATING suggests that may be called for now: >=20 > It is recommended to load the correct KMS driver (i915kms.ko or > radeonkms.ko) via rc.conf, i.e. kld_list=3D"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 driver is already > loaded and will fail if there is none. Ah; I hadn't noted that.... On Mon, Feb 13, 2017 at 01:57:22PM +0100, Baptiste Daroussin wrote: > ... > Are you on intel? if yes consider loading the i915kms by hand first >=20 > there seems to be a bug in latest intel ddx that makes it not load automa= gically > the kernel module, we are looking into it. >=20 > adding kld_list=3D"i915kms" in your rc.conf should do it the right things. >=20 > Note that is no now recommanded by various projects to use the modesetting > driver (which xorg tries to load automatically if the intel driver is not > installed) and that driver will expect you to load the kernel module your= self in > advance as well by design >=20 > Best regards, > Bapt OK; thanks (to both of you). I got i915kms.ko loaded (as well as iic.ko & iicbb.ko, apparently). Firing up xdm ... functions, which appears to be progress. I note that the xdm banner seems ... quite different: merely black & white, using larger characters than I had seen before. And my xdm start-up script has (for about 17 years) copied /usr/local/lib/X11/xdm/Xresources to a new temporary directory in /tmp, adjusted the size of the font, and changed the CLIENTHOST in the banner to "CLIENTHOST - `uname -v | sed -e 's| .*$||'`" -- which this xdm banner did not reflect. But when I try to login, I find the following in ~/.xsession-errors: | Protocol not supported by server | Error: Can't open display: :0 I'll try researching that later, I think. Peace, david --=20 David H. Wolfskill david@catwhisker.org How could one possibly "respect" a misogynist, racist, bullying con-man??!? See http://www.catwhisker.org/~david/publickey.gpg for my public key. --D5tFrmRBv7YOLFOK Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJYobOdXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XRTMH/jL2wfB8KU1dqE4NXWkVm2aa e9EjHPfkYFoFwxQtpk0hfs3r97h/u8o80XoB0QgxiRs1dsm4Ei6ph19vR/pUWLyC magJX1YK2Bep7N9yF0BP5J8SwnW3IsuVhk6g06z9nlnFU9nnxllwScGp1UfZN90c s8g+Ug0lafS6cWKSVoG9alvpdYhP5CVrI14Pvrp61QwLBXiF7Yy7bHj2uZ6I5zSt 5rSo9smycH34IO92lzozwTY54285SXLSrydU1s2fQHQ52VyFtXcEcIHA6NRaWvHN 7wbaS6t/n+xI5gCERFTK+vKBU/3yxhXBHs7M2PP/YYu6UKRhrOWJ83LXU1UJUXk= =W2BF -----END PGP SIGNATURE----- --D5tFrmRBv7YOLFOK--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170213132445.GT1208>