X11 breaks for Intel after ports update from r433396 -> r433935?

[David Wolfskill]

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
> 
> > | [ 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
> 
> 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:
> 
>     It is recommended to load the correct KMS driver (i915kms.ko or
>     radeonkms.ko) via rc.conf, 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 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
> 
> there seems to be a bug in latest intel ddx that makes it not load automagically
> the kernel module, we are looking into it.
> 
> adding kld_list="i915kms" in your rc.conf should do it the right things.
> 
> 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 yourself in
> advance as well by design
> 
> 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
-- 
David H. Wolfskill				david at 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 603 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20170213/3c9fe9d1/attachment.sig>