Jonathan Gray <[email protected]> wrote:
> On Mon, May 30, 2016 at 02:41:59PM +0200, Walter Alejandro Iglesias wrote:
> > Stefan Sperling <[email protected]> wrote:
> >
> > > On Sun, May 29, 2016 at 09:19:58PM +0200, Mark Kettenis wrote:
> > > > And I can't reproduce this on my x220. So either this issue depends on
> > > > specific BIOS revisions, or the description of how to reproduce the
> > > > problem
> > > > is incomplete.
> > >
> > > I've been seeing it on my x201 for a while.
> > >
> > > Isn't this the same issue as was discussed in the "ACPI thinkpad
> > > brightness
> > > regression" thread back in Feburary? It seems this was never resolved.
> > > http://marc.info/?t=145501244400002&r=1&w=2
> >
> > I've found out that setting UXA acceleration in xorg.conf solves not
> > only this issue but the one about cwm menu fonts corruption I reported
> > on May 21th. So, am I wrong assuming it's not an acpi issue but a intel
> > driver one? (Sorry if I can't be more useful, my knowledge is poor).
> >
> > But, using UXA it appears a new issue. When I exit X, I end with a
> > black empty screen and I must change manually to tty1. X shows the
> > error below:
> >
> > -------------------------------------------------------------------
> > X.Org X Server 1.18.3
> > Release Date: 2016-04-04
> > X Protocol Version 11, Revision 0
> > Build Operating System: OpenBSD 6.0 amd64
> > Current Operating System: OpenBSD mamuca.local 6.0 GENERIC.MP#2142 amd64
> > Build Date: 30 May 2016 12:02:37AM
> >
> > Current version of pixman: 0.32.8
> > Before reporting problems, check http://wiki.x.org
> > to make sure that you have the latest version.
> > Markers: (--) probed, (**) from config file, (==) default setting,
> > (++) from command line, (!!) notice, (II) informational,
> > (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> > (==) Log file: "/var/log/Xorg.0.log", Time: Mon May 30 14:22:58 2016
> > (==) Using config file: "/etc/X11/xorg.conf"
> > (II) AIGLX: Suspending AIGLX clients for VT switch
> > xinit: connection to X server lost
> >
> > waiting for X server to shut down
> > X:/usr/X11R6/lib/modules/drivers/intel_drv.so: undefined symbol
> > 'intel_sync_close'
> > lazy binding failed!
> > (EE) Segmentation fault at address 0x0
> > (EE)
> > Fatal server error:
> > (EE) Caught signal 11 (Segmentation fault). Server aborting
> > (EE)
> > (EE)
> > Please consult the The X.Org Foundation support
> > at http://wiki.x.org
> > for help.
> > (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional
> > information.
> > (EE)
> > (EE) Bus error at address 0x1b427e38efd4
> > (EE)
> > FatalError re-entered, aborting
> > (EE) Caught signal 10 (Bus error). Server aborting
> > (EE)
> > ---------------------------------------------------------------
> >
> > (I've upgraded today to latest snapshot)
>
> Here's a diff that might help, compile tested only:
>
> Index: src/uxa/intel_driver.c
> ===================================================================
> RCS file: /cvs/xenocara/driver/xf86-video-intel/src/uxa/intel_driver.c,v
> retrieving revision 1.2
> diff -u -p -r1.2 intel_driver.c
> --- src/uxa/intel_driver.c 12 Apr 2015 19:42:07 -0000 1.2
> +++ src/uxa/intel_driver.c 30 May 2016 13:08:02 -0000
> @@ -1188,7 +1188,9 @@ static Bool I830CloseScreen(CLOSE_SCREEN
> intel->dri3 = DRI_NONE;
> }
>
> +#if HAVE_DRI3
> intel_sync_close(screen);
> +#endif
>
> xf86GARTCloseScreen(scrn->scrnIndex);
>
YES!
It took me a while because it's my first time compiling cvs xenocara. I
can confirm that at least at my end Jonathan's diff solves the intel UXA
issue I mentioned in my last message.
Using UXA, changing to ttys from X is flawless, it doesn't affect the
screen brightness at all.
Now, my question is, may I expect this diff be applied in default
xenocara build?
Walter
