On Tue, May 9, 2017 at 11:43 AM, Sampsa Riikonen wrote:
> I am a bit confused that the name is not "Intel" and/or "nouveau"..
> and "modesetting" is a kernel module that finds display modes, right?
>
> (Q2) Am I doing something wrong here?
No. You are using a distribution
Hi,
Thanks for your advice..! I have a few follow-up questions (tagged
below Q1, Q2 and Q3). Any help highly/extremely appreciated.
Regarding to "reverse prime", etc. I have read the following page:
https://nouveau.freedesktop.org/wiki/Optimus/
So, if we want a single "macro" xscreen that
Would be nice if you could "bisect" those, i.e. which one matters? Or
do they both have to be there to have the desired effect?
On Mon, May 8, 2017 at 11:52 PM, Karl Schmidt wrote:
> I was getting a glicthy checkerboard mess at the cursor in some programs
> (konsol+) with
> #
Some additional data:
- putting LIBGL_ALWAYS_SOFTWARE=1 in /etc/environment makes indeed the
system work (for my current usage, the slowness is acceptable in exchange
of stabillity)
- I still get lock-up using mesa from git (17.2~git1705081930.25d2 from
this repository
Since notification side has been changed to always notify kernel listeners
using _LID returning value. Now listeners needn't invoke acpi_lid_open(),
it should use a spec suggested control method lid device usage model:
register lid notification and use the notified value instead, which is the
only