mobile studio pro 16 ?

classic Classic list List threaded Threaded
23 messages Options
12
Reply | Threaded
Open this post in threaded view
|

mobile studio pro 16 ?

e.a.gebhart

Hello,

I have a mobile studio pro running Arch linux.

I have the xf86-input-wacom-git package installed
aur/xf86-input-wacom-git 0.33.0-1 [installed: 0.34.2-1] (2) (0.07)
    X.Org Wacom tablet driver (from git)

Linux kernel:
core/linux 4.8.13-1 (base) [installed]

Xorg Server 1.18.4-1

xsetwacom --list devices

-- sorry it's a different computer...

shows TOUCH, STYLUS, ERASER  with ids of 15, 16, and 17.

Touch works fine. But the pen doesn't work at all.

I've tried it krita and that doesn't work either. I would have expected
it to work in the OS.

I noticed on the device id doc that mobile studio pro 16 has it's
version numbers crossed out.  Should this device work ?

I've tried it with the old pen from my cintiq companion, and that
doesn't work either.

Does anyone have suggestions on how to get this working ?

Thanks,

Eric

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: mobile studio pro 16 ?

Aaron Armstrong Skomra
Hi Eric,

Support for MSP was added in kernel 4.10 so you'll need to install the
input-wacom kernel driver:

http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom

Let us know if you have any other questions.

Best,
Aaron

On Fri, Mar 17, 2017 at 10:45 AM,  <[hidden email]> wrote:

>
> Hello,
>
> I have a mobile studio pro running Arch linux.
>
> I have the xf86-input-wacom-git package installed
> aur/xf86-input-wacom-git 0.33.0-1 [installed: 0.34.2-1] (2) (0.07)
>     X.Org Wacom tablet driver (from git)
>
> Linux kernel:
> core/linux 4.8.13-1 (base) [installed]
>
> Xorg Server 1.18.4-1
>
> xsetwacom --list devices
>
> -- sorry it's a different computer...
>
> shows TOUCH, STYLUS, ERASER  with ids of 15, 16, and 17.
>
> Touch works fine. But the pen doesn't work at all.
>
> I've tried it krita and that doesn't work either. I would have expected
> it to work in the OS.
>
> I noticed on the device id doc that mobile studio pro 16 has it's
> version numbers crossed out.  Should this device work ?
>
> I've tried it with the old pen from my cintiq companion, and that
> doesn't work either.
>
> Does anyone have suggestions on how to get this working ?
>
> Thanks,
>
> Eric
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Linuxwacom-discuss mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: mobile studio pro 16 ?

e.a.gebhart

Hello Aaron,

Thanks for the help.  I thought that was what I was installing when
I installed the xf86-input-wacom-git package.

https://aur.archlinux.org/packages/xf86-input-wacom-git/

I've downloaded the tar ball from kernel downloads, but it has the same
name.  So I think I'm confused about which is the kernel driver, which
is the X11 driver and what it is that I've actually installed or not
installed.

Thanks,

Eric

Aaron Armstrong Skomra <[hidden email]> writes:

> Hi Eric,
>
> Support for MSP was added in kernel 4.10 so you'll need to install the
> input-wacom kernel driver:
>
> http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>
> Let us know if you have any other questions.
>
> Best,
> Aaron
>
> On Fri, Mar 17, 2017 at 10:45 AM,  <[hidden email]> wrote:
>>
>> Hello,
>>
>> I have a mobile studio pro running Arch linux.
>>
>> I have the xf86-input-wacom-git package installed
>> aur/xf86-input-wacom-git 0.33.0-1 [installed: 0.34.2-1] (2) (0.07)
>>     X.Org Wacom tablet driver (from git)
>>
>> Linux kernel:
>> core/linux 4.8.13-1 (base) [installed]
>>
>> Xorg Server 1.18.4-1
>>
>> xsetwacom --list devices
>>
>> -- sorry it's a different computer...
>>
>> shows TOUCH, STYLUS, ERASER  with ids of 15, 16, and 17.
>>
>> Touch works fine. But the pen doesn't work at all.
>>
>> I've tried it krita and that doesn't work either. I would have expected
>> it to work in the OS.
>>
>> I noticed on the device id doc that mobile studio pro 16 has it's
>> version numbers crossed out.  Should this device work ?
>>
>> I've tried it with the old pen from my cintiq companion, and that
>> doesn't work either.
>>
>> Does anyone have suggestions on how to get this working ?
>>
>> Thanks,
>>
>> Eric
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Linuxwacom-discuss mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: mobile studio pro 16 ?

e.a.gebhart

Ok, I followed the instruction for building the kernel modules and
installed them.

I also upgraded Xorg, and reinstalled the official xf86-input-wacom
package which installed 34.2-1 which matches the kernel modules I
downloaded.

The driver version in /sys/module/wacom/version is v2.00.

The pen/stylus still does not work.

Is there something I can look at or try that might help understand
this ?

Thanks,

Eric

[hidden email] writes:

> Hello Aaron,
>
> Thanks for the help.  I thought that was what I was installing when
> I installed the xf86-input-wacom-git package.
>
> https://aur.archlinux.org/packages/xf86-input-wacom-git/
>
> I've downloaded the tar ball from kernel downloads, but it has the same
> name.  So I think I'm confused about which is the kernel driver, which
> is the X11 driver and what it is that I've actually installed or not
> installed.
>
> Thanks,
>
> Eric
>
> Aaron Armstrong Skomra <[hidden email]> writes:
>
>> Hi Eric,
>>
>> Support for MSP was added in kernel 4.10 so you'll need to install the
>> input-wacom kernel driver:
>>
>> http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>>
>> Let us know if you have any other questions.
>>
>> Best,
>> Aaron
>>
>> On Fri, Mar 17, 2017 at 10:45 AM,  <[hidden email]> wrote:
>>>
>>> Hello,
>>>
>>> I have a mobile studio pro running Arch linux.
>>>
>>> I have the xf86-input-wacom-git package installed
>>> aur/xf86-input-wacom-git 0.33.0-1 [installed: 0.34.2-1] (2) (0.07)
>>>     X.Org Wacom tablet driver (from git)
>>>
>>> Linux kernel:
>>> core/linux 4.8.13-1 (base) [installed]
>>>
>>> Xorg Server 1.18.4-1
>>>
>>> xsetwacom --list devices
>>>
>>> -- sorry it's a different computer...
>>>
>>> shows TOUCH, STYLUS, ERASER  with ids of 15, 16, and 17.
>>>
>>> Touch works fine. But the pen doesn't work at all.
>>>
>>> I've tried it krita and that doesn't work either. I would have expected
>>> it to work in the OS.
>>>
>>> I noticed on the device id doc that mobile studio pro 16 has it's
>>> version numbers crossed out.  Should this device work ?
>>>
>>> I've tried it with the old pen from my cintiq companion, and that
>>> doesn't work either.
>>>
>>> Does anyone have suggestions on how to get this working ?
>>>
>>> Thanks,
>>>
>>> Eric
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Linuxwacom-discuss mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: mobile studio pro 16 ?

Aaron Armstrong Skomra
HI Eric,

If the driver version shows only "v2.00" you haven't installed the
kernel driver.

If you download the latest driver from
https://sourceforge.net/projects/linuxwacom/files/xf86-input-wacom/input-wacom/
and install it you should have a version suffix on v2.00. I realize it
is confusing how our input-wacom (kernel) driver is nested inside our
xf86 (X driver) folder.

When I download and install input-wacom-0.34.0.tar.bz2, load and
unload the driver with the commands from the link in my previous
message, and then issue the command 'modinfo wacom | grep version' ,
this is the output I see (granted I'm using a different distro and
kernel, but the version should be the same):

version:        v2.00-0.34.0
srcversion:     DFB3DEC94FA89060ACBD540
vermagic:       4.8.0-41-generic SMP mod_unload modversions

Best,
Aaron

On Fri, Mar 17, 2017 at 2:06 PM,  <[hidden email]> wrote:

>
> Ok, I followed the instruction for building the kernel modules and
> installed them.
>
> I also upgraded Xorg, and reinstalled the official xf86-input-wacom
> package which installed 34.2-1 which matches the kernel modules I
> downloaded.
>
> The driver version in /sys/module/wacom/version is v2.00.
>
> The pen/stylus still does not work.
>
> Is there something I can look at or try that might help understand
> this ?
>
> Thanks,
>
> Eric
>
> [hidden email] writes:
>
>> Hello Aaron,
>>
>> Thanks for the help.  I thought that was what I was installing when
>> I installed the xf86-input-wacom-git package.
>>
>> https://aur.archlinux.org/packages/xf86-input-wacom-git/
>>
>> I've downloaded the tar ball from kernel downloads, but it has the same
>> name.  So I think I'm confused about which is the kernel driver, which
>> is the X11 driver and what it is that I've actually installed or not
>> installed.
>>
>> Thanks,
>>
>> Eric
>>
>> Aaron Armstrong Skomra <[hidden email]> writes:
>>
>>> Hi Eric,
>>>
>>> Support for MSP was added in kernel 4.10 so you'll need to install the
>>> input-wacom kernel driver:
>>>
>>> http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>>>
>>> Let us know if you have any other questions.
>>>
>>> Best,
>>> Aaron
>>>
>>> On Fri, Mar 17, 2017 at 10:45 AM,  <[hidden email]> wrote:
>>>>
>>>> Hello,
>>>>
>>>> I have a mobile studio pro running Arch linux.
>>>>
>>>> I have the xf86-input-wacom-git package installed
>>>> aur/xf86-input-wacom-git 0.33.0-1 [installed: 0.34.2-1] (2) (0.07)
>>>>     X.Org Wacom tablet driver (from git)
>>>>
>>>> Linux kernel:
>>>> core/linux 4.8.13-1 (base) [installed]
>>>>
>>>> Xorg Server 1.18.4-1
>>>>
>>>> xsetwacom --list devices
>>>>
>>>> -- sorry it's a different computer...
>>>>
>>>> shows TOUCH, STYLUS, ERASER  with ids of 15, 16, and 17.
>>>>
>>>> Touch works fine. But the pen doesn't work at all.
>>>>
>>>> I've tried it krita and that doesn't work either. I would have expected
>>>> it to work in the OS.
>>>>
>>>> I noticed on the device id doc that mobile studio pro 16 has it's
>>>> version numbers crossed out.  Should this device work ?
>>>>
>>>> I've tried it with the old pen from my cintiq companion, and that
>>>> doesn't work either.
>>>>
>>>> Does anyone have suggestions on how to get this working ?
>>>>
>>>> Thanks,
>>>>
>>>> Eric
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>> _______________________________________________
>>>> Linuxwacom-discuss mailing list
>>>> [hidden email]
>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: mobile studio pro 16 ?

e.a.gebhart

Hi Aaron,

I see. Now I've just got to my kernel source in the right place. Either
I haven't found the right Arch doc or it's just not very easy..

I'm missing the config files for the kernel source and modules. Argh.



Aaron Armstrong Skomra <[hidden email]> writes:

> HI Eric,
>
> If the driver version shows only "v2.00" you haven't installed the
> kernel driver.
>
> If you download the latest driver from
> https://sourceforge.net/projects/linuxwacom/files/xf86-input-wacom/input-wacom/
> and install it you should have a version suffix on v2.00. I realize it
> is confusing how our input-wacom (kernel) driver is nested inside our
> xf86 (X driver) folder.
>
> When I download and install input-wacom-0.34.0.tar.bz2, load and
> unload the driver with the commands from the link in my previous
> message, and then issue the command 'modinfo wacom | grep version' ,
> this is the output I see (granted I'm using a different distro and
> kernel, but the version should be the same):
>
> version:        v2.00-0.34.0
> srcversion:     DFB3DEC94FA89060ACBD540
> vermagic:       4.8.0-41-generic SMP mod_unload modversions
>
> Best,
> Aaron
>
> On Fri, Mar 17, 2017 at 2:06 PM,  <[hidden email]> wrote:
>>
>> Ok, I followed the instruction for building the kernel modules and
>> installed them.
>>
>> I also upgraded Xorg, and reinstalled the official xf86-input-wacom
>> package which installed 34.2-1 which matches the kernel modules I
>> downloaded.
>>
>> The driver version in /sys/module/wacom/version is v2.00.
>>
>> The pen/stylus still does not work.
>>
>> Is there something I can look at or try that might help understand
>> this ?
>>
>> Thanks,
>>
>> Eric
>>
>> [hidden email] writes:
>>
>>> Hello Aaron,
>>>
>>> Thanks for the help.  I thought that was what I was installing when
>>> I installed the xf86-input-wacom-git package.
>>>
>>> https://aur.archlinux.org/packages/xf86-input-wacom-git/
>>>
>>> I've downloaded the tar ball from kernel downloads, but it has the same
>>> name.  So I think I'm confused about which is the kernel driver, which
>>> is the X11 driver and what it is that I've actually installed or not
>>> installed.
>>>
>>> Thanks,
>>>
>>> Eric
>>>
>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>
>>>> Hi Eric,
>>>>
>>>> Support for MSP was added in kernel 4.10 so you'll need to install the
>>>> input-wacom kernel driver:
>>>>
>>>> http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>>>>
>>>> Let us know if you have any other questions.
>>>>
>>>> Best,
>>>> Aaron
>>>>
>>>> On Fri, Mar 17, 2017 at 10:45 AM,  <[hidden email]> wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> I have a mobile studio pro running Arch linux.
>>>>>
>>>>> I have the xf86-input-wacom-git package installed
>>>>> aur/xf86-input-wacom-git 0.33.0-1 [installed: 0.34.2-1] (2) (0.07)
>>>>>     X.Org Wacom tablet driver (from git)
>>>>>
>>>>> Linux kernel:
>>>>> core/linux 4.8.13-1 (base) [installed]
>>>>>
>>>>> Xorg Server 1.18.4-1
>>>>>
>>>>> xsetwacom --list devices
>>>>>
>>>>> -- sorry it's a different computer...
>>>>>
>>>>> shows TOUCH, STYLUS, ERASER  with ids of 15, 16, and 17.
>>>>>
>>>>> Touch works fine. But the pen doesn't work at all.
>>>>>
>>>>> I've tried it krita and that doesn't work either. I would have expected
>>>>> it to work in the OS.
>>>>>
>>>>> I noticed on the device id doc that mobile studio pro 16 has it's
>>>>> version numbers crossed out.  Should this device work ?
>>>>>
>>>>> I've tried it with the old pen from my cintiq companion, and that
>>>>> doesn't work either.
>>>>>
>>>>> Does anyone have suggestions on how to get this working ?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Eric
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Check out the vibrant tech community on one of the world's most
>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>> _______________________________________________
>>>>> Linuxwacom-discuss mailing list
>>>>> [hidden email]
>>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: mobile studio pro 16 ?

e.a.gebhart

One thing leads to another. I decided to upgrade my install because 4.10
is current. I've done this many times before, but somehow I screwed
something up.

I started over from scratch, which isn't too bad from where I was. But
now I can't get Xorg working at all. The log looks good and it looks
like wacom input is going to work. But all I get is a black screen with
'startx xterm' or a simple xinitrc with xmonad.

Xmonad is working sort of. The only thing that works is shift-CMD-Q to
exit. There are no xmonad.errors.

Does anyone have a working xorg.conf for this machine ?  It seems like it
worked out of the box before.  'Xorg :0 -configure' crashes now. which
is what it seems that I did the last time.

The only errors I'm getting are unable to load module 'nouveau' and 'nv'
plus a few from wacom invalid types, which look ok, because it does find
the ones it needs.

the 'nv' driver no longer exists from what I can tell, and nouveau isn't
necessary for this video controller.

So, I'm just hoping someone here has an xorg.conf that works for this
machine. Suggestions welcome also.

Thanks,

Eric

[hidden email] writes:

> Hi Aaron,
>
> I see. Now I've just got to my kernel source in the right place. Either
> I haven't found the right Arch doc or it's just not very easy..
>
> I'm missing the config files for the kernel source and modules. Argh.
>
>
>
> Aaron Armstrong Skomra <[hidden email]> writes:
>
>> HI Eric,
>>
>> If the driver version shows only "v2.00" you haven't installed the
>> kernel driver.
>>
>> If you download the latest driver from
>> https://sourceforge.net/projects/linuxwacom/files/xf86-input-wacom/input-wacom/
>> and install it you should have a version suffix on v2.00. I realize it
>> is confusing how our input-wacom (kernel) driver is nested inside our
>> xf86 (X driver) folder.
>>
>> When I download and install input-wacom-0.34.0.tar.bz2, load and
>> unload the driver with the commands from the link in my previous
>> message, and then issue the command 'modinfo wacom | grep version' ,
>> this is the output I see (granted I'm using a different distro and
>> kernel, but the version should be the same):
>>
>> version:        v2.00-0.34.0
>> srcversion:     DFB3DEC94FA89060ACBD540
>> vermagic:       4.8.0-41-generic SMP mod_unload modversions
>>
>> Best,
>> Aaron
>>
>> On Fri, Mar 17, 2017 at 2:06 PM,  <[hidden email]> wrote:
>>>
>>> Ok, I followed the instruction for building the kernel modules and
>>> installed them.
>>>
>>> I also upgraded Xorg, and reinstalled the official xf86-input-wacom
>>> package which installed 34.2-1 which matches the kernel modules I
>>> downloaded.
>>>
>>> The driver version in /sys/module/wacom/version is v2.00.
>>>
>>> The pen/stylus still does not work.
>>>
>>> Is there something I can look at or try that might help understand
>>> this ?
>>>
>>> Thanks,
>>>
>>> Eric
>>>
>>> [hidden email] writes:
>>>
>>>> Hello Aaron,
>>>>
>>>> Thanks for the help.  I thought that was what I was installing when
>>>> I installed the xf86-input-wacom-git package.
>>>>
>>>> https://aur.archlinux.org/packages/xf86-input-wacom-git/
>>>>
>>>> I've downloaded the tar ball from kernel downloads, but it has the same
>>>> name.  So I think I'm confused about which is the kernel driver, which
>>>> is the X11 driver and what it is that I've actually installed or not
>>>> installed.
>>>>
>>>> Thanks,
>>>>
>>>> Eric
>>>>
>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>
>>>>> Hi Eric,
>>>>>
>>>>> Support for MSP was added in kernel 4.10 so you'll need to install the
>>>>> input-wacom kernel driver:
>>>>>
>>>>> http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>>>>>
>>>>> Let us know if you have any other questions.
>>>>>
>>>>> Best,
>>>>> Aaron
>>>>>
>>>>> On Fri, Mar 17, 2017 at 10:45 AM,  <[hidden email]> wrote:
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I have a mobile studio pro running Arch linux.
>>>>>>
>>>>>> I have the xf86-input-wacom-git package installed
>>>>>> aur/xf86-input-wacom-git 0.33.0-1 [installed: 0.34.2-1] (2) (0.07)
>>>>>>     X.Org Wacom tablet driver (from git)
>>>>>>
>>>>>> Linux kernel:
>>>>>> core/linux 4.8.13-1 (base) [installed]
>>>>>>
>>>>>> Xorg Server 1.18.4-1
>>>>>>
>>>>>> xsetwacom --list devices
>>>>>>
>>>>>> -- sorry it's a different computer...
>>>>>>
>>>>>> shows TOUCH, STYLUS, ERASER  with ids of 15, 16, and 17.
>>>>>>
>>>>>> Touch works fine. But the pen doesn't work at all.
>>>>>>
>>>>>> I've tried it krita and that doesn't work either. I would have expected
>>>>>> it to work in the OS.
>>>>>>
>>>>>> I noticed on the device id doc that mobile studio pro 16 has it's
>>>>>> version numbers crossed out.  Should this device work ?
>>>>>>
>>>>>> I've tried it with the old pen from my cintiq companion, and that
>>>>>> doesn't work either.
>>>>>>
>>>>>> Does anyone have suggestions on how to get this working ?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Eric
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>> _______________________________________________
>>>>>> Linuxwacom-discuss mailing list
>>>>>> [hidden email]
>>>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: mobile studio pro 16 ?

Jason Gerecke
Is there any particular reason you're using an xorg.conf file? That
should be completely unnecessary for most systems, and I didn't
require one when testing a MobileStudio Pro myself. (Note that I can
confirm that `Xorg :0 -configure` crashes, but it appears that's due
to a recently-introduced bug in the X server, not our driver. You
might consider filing a bug at https://bugzilla.freedesktop.org/ if
you rely on the option).

I'm not familiar with Xmonad, but if it is starting up then I'd
suspect a problem with either: a) incorrect xmonad config, b)
incorrect xinitrc config, or c) missing software.

As for "startx xterm", is that the literal command that you're
running? If you want to just start an xterm you'll need to provide the
full path (e.g. `startx /usr/bin/xterm`) or else startx will simply
pass "xterm" as a variable to your xinitrc script, where it will
(probably) be ignored. The pointer also won't be visible until its
moved over the xterm, so it may be advisable to use something like
`startx /usr/bin/xterm -maximized` to ensure the xterm takes up the
entire screen.

Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one  /
(That is to say, eight) to the two,     /
But you can’t take seven from three,    /
So you look at the sixty-fours....



On Wed, Mar 22, 2017 at 5:27 PM,  <[hidden email]> wrote:

>
> One thing leads to another. I decided to upgrade my install because 4.10
> is current. I've done this many times before, but somehow I screwed
> something up.
>
> I started over from scratch, which isn't too bad from where I was. But
> now I can't get Xorg working at all. The log looks good and it looks
> like wacom input is going to work. But all I get is a black screen with
> 'startx xterm' or a simple xinitrc with xmonad.
>
> Xmonad is working sort of. The only thing that works is shift-CMD-Q to
> exit. There are no xmonad.errors.
>
> Does anyone have a working xorg.conf for this machine ?  It seems like it
> worked out of the box before.  'Xorg :0 -configure' crashes now. which
> is what it seems that I did the last time.
>
> The only errors I'm getting are unable to load module 'nouveau' and 'nv'
> plus a few from wacom invalid types, which look ok, because it does find
> the ones it needs.
>
> the 'nv' driver no longer exists from what I can tell, and nouveau isn't
> necessary for this video controller.
>
> So, I'm just hoping someone here has an xorg.conf that works for this
> machine. Suggestions welcome also.
>
> Thanks,
>
> Eric
>
> [hidden email] writes:
>
>> Hi Aaron,
>>
>> I see. Now I've just got to my kernel source in the right place. Either
>> I haven't found the right Arch doc or it's just not very easy..
>>
>> I'm missing the config files for the kernel source and modules. Argh.
>>
>>
>>
>> Aaron Armstrong Skomra <[hidden email]> writes:
>>
>>> HI Eric,
>>>
>>> If the driver version shows only "v2.00" you haven't installed the
>>> kernel driver.
>>>
>>> If you download the latest driver from
>>> https://sourceforge.net/projects/linuxwacom/files/xf86-input-wacom/input-wacom/
>>> and install it you should have a version suffix on v2.00. I realize it
>>> is confusing how our input-wacom (kernel) driver is nested inside our
>>> xf86 (X driver) folder.
>>>
>>> When I download and install input-wacom-0.34.0.tar.bz2, load and
>>> unload the driver with the commands from the link in my previous
>>> message, and then issue the command 'modinfo wacom | grep version' ,
>>> this is the output I see (granted I'm using a different distro and
>>> kernel, but the version should be the same):
>>>
>>> version:        v2.00-0.34.0
>>> srcversion:     DFB3DEC94FA89060ACBD540
>>> vermagic:       4.8.0-41-generic SMP mod_unload modversions
>>>
>>> Best,
>>> Aaron
>>>
>>> On Fri, Mar 17, 2017 at 2:06 PM,  <[hidden email]> wrote:
>>>>
>>>> Ok, I followed the instruction for building the kernel modules and
>>>> installed them.
>>>>
>>>> I also upgraded Xorg, and reinstalled the official xf86-input-wacom
>>>> package which installed 34.2-1 which matches the kernel modules I
>>>> downloaded.
>>>>
>>>> The driver version in /sys/module/wacom/version is v2.00.
>>>>
>>>> The pen/stylus still does not work.
>>>>
>>>> Is there something I can look at or try that might help understand
>>>> this ?
>>>>
>>>> Thanks,
>>>>
>>>> Eric
>>>>
>>>> [hidden email] writes:
>>>>
>>>>> Hello Aaron,
>>>>>
>>>>> Thanks for the help.  I thought that was what I was installing when
>>>>> I installed the xf86-input-wacom-git package.
>>>>>
>>>>> https://aur.archlinux.org/packages/xf86-input-wacom-git/
>>>>>
>>>>> I've downloaded the tar ball from kernel downloads, but it has the same
>>>>> name.  So I think I'm confused about which is the kernel driver, which
>>>>> is the X11 driver and what it is that I've actually installed or not
>>>>> installed.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Eric
>>>>>
>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>
>>>>>> Hi Eric,
>>>>>>
>>>>>> Support for MSP was added in kernel 4.10 so you'll need to install the
>>>>>> input-wacom kernel driver:
>>>>>>
>>>>>> http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>>>>>>
>>>>>> Let us know if you have any other questions.
>>>>>>
>>>>>> Best,
>>>>>> Aaron
>>>>>>
>>>>>> On Fri, Mar 17, 2017 at 10:45 AM,  <[hidden email]> wrote:
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> I have a mobile studio pro running Arch linux.
>>>>>>>
>>>>>>> I have the xf86-input-wacom-git package installed
>>>>>>> aur/xf86-input-wacom-git 0.33.0-1 [installed: 0.34.2-1] (2) (0.07)
>>>>>>>     X.Org Wacom tablet driver (from git)
>>>>>>>
>>>>>>> Linux kernel:
>>>>>>> core/linux 4.8.13-1 (base) [installed]
>>>>>>>
>>>>>>> Xorg Server 1.18.4-1
>>>>>>>
>>>>>>> xsetwacom --list devices
>>>>>>>
>>>>>>> -- sorry it's a different computer...
>>>>>>>
>>>>>>> shows TOUCH, STYLUS, ERASER  with ids of 15, 16, and 17.
>>>>>>>
>>>>>>> Touch works fine. But the pen doesn't work at all.
>>>>>>>
>>>>>>> I've tried it krita and that doesn't work either. I would have expected
>>>>>>> it to work in the OS.
>>>>>>>
>>>>>>> I noticed on the device id doc that mobile studio pro 16 has it's
>>>>>>> version numbers crossed out.  Should this device work ?
>>>>>>>
>>>>>>> I've tried it with the old pen from my cintiq companion, and that
>>>>>>> doesn't work either.
>>>>>>>
>>>>>>> Does anyone have suggestions on how to get this working ?
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Eric
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>>> _______________________________________________
>>>>>>> Linuxwacom-discuss mailing list
>>>>>>> [hidden email]
>>>>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Linuxwacom-discuss mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: mobile studio pro 16 ?

e.a.gebhart

Using an xorg.conf file is the only way I know to change the behavior of
xorg. Given that the display is what is not showing I cannot think of
anything other than that the automatic configuration is not working.

This setup worked perfectly (no stylus) before upgrading the kernel to
4.10 and Xorg to 1.19.3. I thought about downgrading xorg but that is a huge pain.
Being on Arch I just did the usual pacman -Syy and pacman -Su. I thought
I had screwed something up, but now I'm seeing the same behavior on a
fresh install.

Xmonad does not have any errors. I can replace it with twm,
exec startxfce4 or exec xterm with the same effect. maximized xterm
makes no difference.

No matter what I do I get a black screen.  alt-ctrl-f1 brings me back to
the console. When running the xterm typing 'exit' return will
terminate the session.  with Xmonad shift-CMD-Q exits xmonad, etc.

running xfce does give a few errors one of which is:
Error opening /dev/dri/card0  permission denied

I get this from xfsettings and xfwm4
g_str_has_prefix: assertion 'prefix != NULL' failed

This makes me wonder if there is a conflict with the two video cards the
built in Intel and the nvidia.

thanks,

Eric

Jason Gerecke <[hidden email]> writes:

> Is there any particular reason you're using an xorg.conf file? That
> should be completely unnecessary for most systems, and I didn't
> require one when testing a MobileStudio Pro myself. (Note that I can
> confirm that `Xorg :0 -configure` crashes, but it appears that's due
> to a recently-introduced bug in the X server, not our driver. You
> might consider filing a bug at https://bugzilla.freedesktop.org/ if
> you rely on the option).
>
> I'm not familiar with Xmonad, but if it is starting up then I'd
> suspect a problem with either: a) incorrect xmonad config, b)
> incorrect xinitrc config, or c) missing software.
>
> As for "startx xterm", is that the literal command that you're
> running? If you want to just start an xterm you'll need to provide the
> full path (e.g. `startx /usr/bin/xterm`) or else startx will simply
> pass "xterm" as a variable to your xinitrc script, where it will
> (probably) be ignored. The pointer also won't be visible until its
> moved over the xterm, so it may be advisable to use something like
> `startx /usr/bin/xterm -maximized` to ensure the xterm takes up the
> entire screen.
>
> Jason
> ---
> Now instead of four in the eights place /
> you’ve got three, ‘Cause you added one  /
> (That is to say, eight) to the two,     /
> But you can’t take seven from three,    /
> So you look at the sixty-fours....
>
>
>
> On Wed, Mar 22, 2017 at 5:27 PM,  <[hidden email]> wrote:
>>
>> One thing leads to another. I decided to upgrade my install because 4.10
>> is current. I've done this many times before, but somehow I screwed
>> something up.
>>
>> I started over from scratch, which isn't too bad from where I was. But
>> now I can't get Xorg working at all. The log looks good and it looks
>> like wacom input is going to work. But all I get is a black screen with
>> 'startx xterm' or a simple xinitrc with xmonad.
>>
>> Xmonad is working sort of. The only thing that works is shift-CMD-Q to
>> exit. There are no xmonad.errors.
>>
>> Does anyone have a working xorg.conf for this machine ?  It seems like it
>> worked out of the box before.  'Xorg :0 -configure' crashes now. which
>> is what it seems that I did the last time.
>>
>> The only errors I'm getting are unable to load module 'nouveau' and 'nv'
>> plus a few from wacom invalid types, which look ok, because it does find
>> the ones it needs.
>>
>> the 'nv' driver no longer exists from what I can tell, and nouveau isn't
>> necessary for this video controller.
>>
>> So, I'm just hoping someone here has an xorg.conf that works for this
>> machine. Suggestions welcome also.
>>
>> Thanks,
>>
>> Eric
>>
>> [hidden email] writes:
>>
>>> Hi Aaron,
>>>
>>> I see. Now I've just got to my kernel source in the right place. Either
>>> I haven't found the right Arch doc or it's just not very easy..
>>>
>>> I'm missing the config files for the kernel source and modules. Argh.
>>>
>>>
>>>
>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>
>>>> HI Eric,
>>>>
>>>> If the driver version shows only "v2.00" you haven't installed the
>>>> kernel driver.
>>>>
>>>> If you download the latest driver from
>>>> https://sourceforge.net/projects/linuxwacom/files/xf86-input-wacom/input-wacom/
>>>> and install it you should have a version suffix on v2.00. I realize it
>>>> is confusing how our input-wacom (kernel) driver is nested inside our
>>>> xf86 (X driver) folder.
>>>>
>>>> When I download and install input-wacom-0.34.0.tar.bz2, load and
>>>> unload the driver with the commands from the link in my previous
>>>> message, and then issue the command 'modinfo wacom | grep version' ,
>>>> this is the output I see (granted I'm using a different distro and
>>>> kernel, but the version should be the same):
>>>>
>>>> version:        v2.00-0.34.0
>>>> srcversion:     DFB3DEC94FA89060ACBD540
>>>> vermagic:       4.8.0-41-generic SMP mod_unload modversions
>>>>
>>>> Best,
>>>> Aaron
>>>>
>>>> On Fri, Mar 17, 2017 at 2:06 PM,  <[hidden email]> wrote:
>>>>>
>>>>> Ok, I followed the instruction for building the kernel modules and
>>>>> installed them.
>>>>>
>>>>> I also upgraded Xorg, and reinstalled the official xf86-input-wacom
>>>>> package which installed 34.2-1 which matches the kernel modules I
>>>>> downloaded.
>>>>>
>>>>> The driver version in /sys/module/wacom/version is v2.00.
>>>>>
>>>>> The pen/stylus still does not work.
>>>>>
>>>>> Is there something I can look at or try that might help understand
>>>>> this ?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Eric
>>>>>
>>>>> [hidden email] writes:
>>>>>
>>>>>> Hello Aaron,
>>>>>>
>>>>>> Thanks for the help.  I thought that was what I was installing when
>>>>>> I installed the xf86-input-wacom-git package.
>>>>>>
>>>>>> https://aur.archlinux.org/packages/xf86-input-wacom-git/
>>>>>>
>>>>>> I've downloaded the tar ball from kernel downloads, but it has the same
>>>>>> name.  So I think I'm confused about which is the kernel driver, which
>>>>>> is the X11 driver and what it is that I've actually installed or not
>>>>>> installed.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Eric
>>>>>>
>>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>>
>>>>>>> Hi Eric,
>>>>>>>
>>>>>>> Support for MSP was added in kernel 4.10 so you'll need to install the
>>>>>>> input-wacom kernel driver:
>>>>>>>
>>>>>>> http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>>>>>>>
>>>>>>> Let us know if you have any other questions.
>>>>>>>
>>>>>>> Best,
>>>>>>> Aaron
>>>>>>>
>>>>>>> On Fri, Mar 17, 2017 at 10:45 AM,  <[hidden email]> wrote:
>>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> I have a mobile studio pro running Arch linux.
>>>>>>>>
>>>>>>>> I have the xf86-input-wacom-git package installed
>>>>>>>> aur/xf86-input-wacom-git 0.33.0-1 [installed: 0.34.2-1] (2) (0.07)
>>>>>>>>     X.Org Wacom tablet driver (from git)
>>>>>>>>
>>>>>>>> Linux kernel:
>>>>>>>> core/linux 4.8.13-1 (base) [installed]
>>>>>>>>
>>>>>>>> Xorg Server 1.18.4-1
>>>>>>>>
>>>>>>>> xsetwacom --list devices
>>>>>>>>
>>>>>>>> -- sorry it's a different computer...
>>>>>>>>
>>>>>>>> shows TOUCH, STYLUS, ERASER  with ids of 15, 16, and 17.
>>>>>>>>
>>>>>>>> Touch works fine. But the pen doesn't work at all.
>>>>>>>>
>>>>>>>> I've tried it krita and that doesn't work either. I would have expected
>>>>>>>> it to work in the OS.
>>>>>>>>
>>>>>>>> I noticed on the device id doc that mobile studio pro 16 has it's
>>>>>>>> version numbers crossed out.  Should this device work ?
>>>>>>>>
>>>>>>>> I've tried it with the old pen from my cintiq companion, and that
>>>>>>>> doesn't work either.
>>>>>>>>
>>>>>>>> Does anyone have suggestions on how to get this working ?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> Eric
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>>>> _______________________________________________
>>>>>>>> Linuxwacom-discuss mailing list
>>>>>>>> [hidden email]
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Linuxwacom-discuss mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: mobile studio pro 16 ?

Jason Gerecke
I just gave Arch a whirl to see if a recent update broke something,
but even after rebooting from a fresh `pacman -Syu` I don't see any
problems on the MobileStudio Pro 16. Its using GDM by default, but
even when I switch to multi-user.target and run `startx
/usr/bin/xfce4-terminal` (I don't have the vanilla xterm installed)
manually I don't see any problems. No xorg.conf file either...

Notable package versions (though if you upgraded, they should be identical...):

 * core/linux 4.10.4-1
 * extra/xorg-server 1.19.3-1
 * extra/xf86-video-fbdev 0.4.4-6
 * extra/xf86-video-intel 1:2.99.917+767+g7e9e92c8-1
 * (No nouveau, nv, or nvidia graphics)
 * extra/mesa 17.0.1-2

If you've got an Xorg.0.log, go ahead and attach it for me to review...

Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one  /
(That is to say, eight) to the two,     /
But you can’t take seven from three,    /
So you look at the sixty-fours....



On Thu, Mar 23, 2017 at 11:47 AM,  <[hidden email]> wrote:

>
> Using an xorg.conf file is the only way I know to change the behavior of
> xorg. Given that the display is what is not showing I cannot think of
> anything other than that the automatic configuration is not working.
>
> This setup worked perfectly (no stylus) before upgrading the kernel to
> 4.10 and Xorg to 1.19.3. I thought about downgrading xorg but that is a huge pain.
> Being on Arch I just did the usual pacman -Syy and pacman -Su. I thought
> I had screwed something up, but now I'm seeing the same behavior on a
> fresh install.
>
> Xmonad does not have any errors. I can replace it with twm,
> exec startxfce4 or exec xterm with the same effect. maximized xterm
> makes no difference.
>
> No matter what I do I get a black screen.  alt-ctrl-f1 brings me back to
> the console. When running the xterm typing 'exit' return will
> terminate the session.  with Xmonad shift-CMD-Q exits xmonad, etc.
>
> running xfce does give a few errors one of which is:
> Error opening /dev/dri/card0  permission denied
>
> I get this from xfsettings and xfwm4
> g_str_has_prefix: assertion 'prefix != NULL' failed
>
> This makes me wonder if there is a conflict with the two video cards the
> built in Intel and the nvidia.
>
> thanks,
>
> Eric
>
> Jason Gerecke <[hidden email]> writes:
>
>> Is there any particular reason you're using an xorg.conf file? That
>> should be completely unnecessary for most systems, and I didn't
>> require one when testing a MobileStudio Pro myself. (Note that I can
>> confirm that `Xorg :0 -configure` crashes, but it appears that's due
>> to a recently-introduced bug in the X server, not our driver. You
>> might consider filing a bug at https://bugzilla.freedesktop.org/ if
>> you rely on the option).
>>
>> I'm not familiar with Xmonad, but if it is starting up then I'd
>> suspect a problem with either: a) incorrect xmonad config, b)
>> incorrect xinitrc config, or c) missing software.
>>
>> As for "startx xterm", is that the literal command that you're
>> running? If you want to just start an xterm you'll need to provide the
>> full path (e.g. `startx /usr/bin/xterm`) or else startx will simply
>> pass "xterm" as a variable to your xinitrc script, where it will
>> (probably) be ignored. The pointer also won't be visible until its
>> moved over the xterm, so it may be advisable to use something like
>> `startx /usr/bin/xterm -maximized` to ensure the xterm takes up the
>> entire screen.
>>
>> Jason
>> ---
>> Now instead of four in the eights place /
>> you’ve got three, ‘Cause you added one  /
>> (That is to say, eight) to the two,     /
>> But you can’t take seven from three,    /
>> So you look at the sixty-fours....
>>
>>
>>
>> On Wed, Mar 22, 2017 at 5:27 PM,  <[hidden email]> wrote:
>>>
>>> One thing leads to another. I decided to upgrade my install because 4.10
>>> is current. I've done this many times before, but somehow I screwed
>>> something up.
>>>
>>> I started over from scratch, which isn't too bad from where I was. But
>>> now I can't get Xorg working at all. The log looks good and it looks
>>> like wacom input is going to work. But all I get is a black screen with
>>> 'startx xterm' or a simple xinitrc with xmonad.
>>>
>>> Xmonad is working sort of. The only thing that works is shift-CMD-Q to
>>> exit. There are no xmonad.errors.
>>>
>>> Does anyone have a working xorg.conf for this machine ?  It seems like it
>>> worked out of the box before.  'Xorg :0 -configure' crashes now. which
>>> is what it seems that I did the last time.
>>>
>>> The only errors I'm getting are unable to load module 'nouveau' and 'nv'
>>> plus a few from wacom invalid types, which look ok, because it does find
>>> the ones it needs.
>>>
>>> the 'nv' driver no longer exists from what I can tell, and nouveau isn't
>>> necessary for this video controller.
>>>
>>> So, I'm just hoping someone here has an xorg.conf that works for this
>>> machine. Suggestions welcome also.
>>>
>>> Thanks,
>>>
>>> Eric
>>>
>>> [hidden email] writes:
>>>
>>>> Hi Aaron,
>>>>
>>>> I see. Now I've just got to my kernel source in the right place. Either
>>>> I haven't found the right Arch doc or it's just not very easy..
>>>>
>>>> I'm missing the config files for the kernel source and modules. Argh.
>>>>
>>>>
>>>>
>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>
>>>>> HI Eric,
>>>>>
>>>>> If the driver version shows only "v2.00" you haven't installed the
>>>>> kernel driver.
>>>>>
>>>>> If you download the latest driver from
>>>>> https://sourceforge.net/projects/linuxwacom/files/xf86-input-wacom/input-wacom/
>>>>> and install it you should have a version suffix on v2.00. I realize it
>>>>> is confusing how our input-wacom (kernel) driver is nested inside our
>>>>> xf86 (X driver) folder.
>>>>>
>>>>> When I download and install input-wacom-0.34.0.tar.bz2, load and
>>>>> unload the driver with the commands from the link in my previous
>>>>> message, and then issue the command 'modinfo wacom | grep version' ,
>>>>> this is the output I see (granted I'm using a different distro and
>>>>> kernel, but the version should be the same):
>>>>>
>>>>> version:        v2.00-0.34.0
>>>>> srcversion:     DFB3DEC94FA89060ACBD540
>>>>> vermagic:       4.8.0-41-generic SMP mod_unload modversions
>>>>>
>>>>> Best,
>>>>> Aaron
>>>>>
>>>>> On Fri, Mar 17, 2017 at 2:06 PM,  <[hidden email]> wrote:
>>>>>>
>>>>>> Ok, I followed the instruction for building the kernel modules and
>>>>>> installed them.
>>>>>>
>>>>>> I also upgraded Xorg, and reinstalled the official xf86-input-wacom
>>>>>> package which installed 34.2-1 which matches the kernel modules I
>>>>>> downloaded.
>>>>>>
>>>>>> The driver version in /sys/module/wacom/version is v2.00.
>>>>>>
>>>>>> The pen/stylus still does not work.
>>>>>>
>>>>>> Is there something I can look at or try that might help understand
>>>>>> this ?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Eric
>>>>>>
>>>>>> [hidden email] writes:
>>>>>>
>>>>>>> Hello Aaron,
>>>>>>>
>>>>>>> Thanks for the help.  I thought that was what I was installing when
>>>>>>> I installed the xf86-input-wacom-git package.
>>>>>>>
>>>>>>> https://aur.archlinux.org/packages/xf86-input-wacom-git/
>>>>>>>
>>>>>>> I've downloaded the tar ball from kernel downloads, but it has the same
>>>>>>> name.  So I think I'm confused about which is the kernel driver, which
>>>>>>> is the X11 driver and what it is that I've actually installed or not
>>>>>>> installed.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Eric
>>>>>>>
>>>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>>>
>>>>>>>> Hi Eric,
>>>>>>>>
>>>>>>>> Support for MSP was added in kernel 4.10 so you'll need to install the
>>>>>>>> input-wacom kernel driver:
>>>>>>>>
>>>>>>>> http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>>>>>>>>
>>>>>>>> Let us know if you have any other questions.
>>>>>>>>
>>>>>>>> Best,
>>>>>>>> Aaron
>>>>>>>>
>>>>>>>> On Fri, Mar 17, 2017 at 10:45 AM,  <[hidden email]> wrote:
>>>>>>>>>
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> I have a mobile studio pro running Arch linux.
>>>>>>>>>
>>>>>>>>> I have the xf86-input-wacom-git package installed
>>>>>>>>> aur/xf86-input-wacom-git 0.33.0-1 [installed: 0.34.2-1] (2) (0.07)
>>>>>>>>>     X.Org Wacom tablet driver (from git)
>>>>>>>>>
>>>>>>>>> Linux kernel:
>>>>>>>>> core/linux 4.8.13-1 (base) [installed]
>>>>>>>>>
>>>>>>>>> Xorg Server 1.18.4-1
>>>>>>>>>
>>>>>>>>> xsetwacom --list devices
>>>>>>>>>
>>>>>>>>> -- sorry it's a different computer...
>>>>>>>>>
>>>>>>>>> shows TOUCH, STYLUS, ERASER  with ids of 15, 16, and 17.
>>>>>>>>>
>>>>>>>>> Touch works fine. But the pen doesn't work at all.
>>>>>>>>>
>>>>>>>>> I've tried it krita and that doesn't work either. I would have expected
>>>>>>>>> it to work in the OS.
>>>>>>>>>
>>>>>>>>> I noticed on the device id doc that mobile studio pro 16 has it's
>>>>>>>>> version numbers crossed out.  Should this device work ?
>>>>>>>>>
>>>>>>>>> I've tried it with the old pen from my cintiq companion, and that
>>>>>>>>> doesn't work either.
>>>>>>>>>
>>>>>>>>> Does anyone have suggestions on how to get this working ?
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> Eric
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>>>>> _______________________________________________
>>>>>>>>> Linuxwacom-discuss mailing list
>>>>>>>>> [hidden email]
>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Linuxwacom-discuss mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: mobile studio pro 16 ?

e.a.gebhart

I'm wondering if I shouldn't start over with a fresh install again. But
maybe this will reveal something.  Here is my log.

[  2768.163]
X.Org X Server 1.19.3
Release Date: 2017-03-15
[  2768.166] X Protocol Version 11, Revision 0
[  2768.168] Build Operating System: Linux 4.9.11-1-ARCH x86_64
[  2768.169] Current Operating System: Linux egalite 4.10.4-1-ARCH #1 SMP PREEMPT Sat Mar 18 19:39:18 CET 2017 x86_64
[  2768.169] Kernel command line: initrd=\initramfs-linux.img root=PARTUUID=773da99e-8124-4e01-9ccd-4a95061d3359 rw
[  2768.172] Build Date: 16 March 2017  02:47:54PM
[  2768.173]
[  2768.174] Current version of pixman: 0.34.0
[  2768.176] Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[  2768.176] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  2768.182] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Mar 23 14:50:43 2017
[  2768.184] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  2768.184] (==) No Layout section.  Using the first Screen section.
[  2768.184] (==) No screen section available. Using defaults.
[  2768.184] (**) |-->Screen "Default Screen Section" (0)
[  2768.184] (**) |   |-->Monitor "<default monitor>"
[  2768.184] (==) No monitor specified for screen "Default Screen Section".
        Using a default monitor configuration.
[  2768.184] (**) Option "IgnoreABI"
[  2768.184] (**) Ignoring ABI Version
[  2768.184] (==) Automatically adding devices
[  2768.184] (==) Automatically enabling devices
[  2768.184] (==) Automatically adding GPU devices
[  2768.184] (==) Automatically binding GPU devices
[  2768.184] (==) Max clients allowed: 256, resource mask: 0x1fffff
[  2768.184] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[  2768.184] Entry deleted from font path.
[  2768.184] (==) FontPath set to:
        /usr/share/fonts/misc/,
        /usr/share/fonts/TTF/,
        /usr/share/fonts/OTF/,
        /usr/share/fonts/100dpi/,
        /usr/share/fonts/75dpi/
[  2768.184] (==) ModulePath set to "/usr/lib/xorg/modules"
[  2768.184] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[  2768.184] (II) Loader magic: 0x822d60
[  2768.184] (II) Module ABI versions:
[  2768.184] X.Org ANSI C Emulation: 0.4
[  2768.184] X.Org Video Driver: 23.0
[  2768.184] X.Org XInput driver : 24.1
[  2768.184] X.Org Server Extension : 10.0
[  2768.185] (--) using VT number 2

[  2768.185] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[  2768.186] (II) xfree86: Adding drm device (/dev/dri/card0)
[  2768.191] (II) xfree86: Adding drm device (/dev/dri/card1)
[  2768.192] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules"
[  2768.192] (**) OutputClass "nvidia" setting /dev/dri/card1 as PrimaryGPU
[  2768.193] (--) PCI: (0:0:2:0) 8086:1927:1b0a:01cf rev 10, Mem @ 0xa2000000/16777216, 0xb0000000/268435456, I/O @ 0x00004000/64, BIOS @ 0x????????/131072
[  2768.193] (--) PCI:*(0:1:0:0) 10de:13b1:1b0a:01cf rev 162, Mem @ 0xa3000000/16777216, 0x90000000/268435456, 0xa0000000/33554432, I/O @ 0x00003000/128
[  2768.193] (II) Open ACPI successful (/var/run/acpid.socket)
[  2768.193] (II) LoadModule: "glx"
[  2768.193] (II) Loading /usr/lib/nvidia/xorg/libglx.so
[  2768.197] (II) Module glx: vendor="NVIDIA Corporation"
[  2768.197] compiled for 4.0.2, module version = 1.0.0
[  2768.197] Module class: X.Org Server Extension
[  2768.197] (II) NVIDIA GLX Module  378.13  Tue Feb  7 18:25:34 PST 2017
[  2768.197] (II) Applying OutputClass "nvidia" to /dev/dri/card1
[  2768.197] loading driver: nvidia
[  2768.197] (II) Applying OutputClass "intel" to /dev/dri/card0
[  2768.197] loading driver: modesetting
[  2768.197] (==) Matched nvidia as autoconfigured driver 0
[  2768.197] (==) Matched nouveau as autoconfigured driver 1
[  2768.197] (==) Matched nv as autoconfigured driver 2
[  2768.197] (==) Matched modesetting as autoconfigured driver 3
[  2768.197] (==) Matched intel as autoconfigured driver 4
[  2768.197] (==) Matched nouveau as autoconfigured driver 5
[  2768.197] (==) Matched nv as autoconfigured driver 6
[  2768.197] (==) Matched modesetting as autoconfigured driver 7
[  2768.197] (==) Matched fbdev as autoconfigured driver 8
[  2768.197] (==) Matched vesa as autoconfigured driver 9
[  2768.197] (==) Assigned the driver to the xf86ConfigLayout
[  2768.197] (II) LoadModule: "nvidia"
[  2768.198] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[  2768.198] (II) Module nvidia: vendor="NVIDIA Corporation"
[  2768.198] compiled for 4.0.2, module version = 1.0.0
[  2768.198] Module class: X.Org Video Driver
[  2768.198] (II) LoadModule: "nouveau"
[  2768.198] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[  2768.198] (II) Module nouveau: vendor="X.Org Foundation"
[  2768.198] compiled for 1.19.2, module version = 1.0.14
[  2768.198] Module class: X.Org Video Driver
[  2768.198] ABI class: X.Org Video Driver, version 23.0
[  2768.198] (II) LoadModule: "nv"
[  2768.198] (II) Loading /usr/lib/xorg/modules/drivers/nv_drv.so
[  2768.198] (II) Module nv: vendor="X.Org Foundation"
[  2768.198] compiled for 1.19.3, module version = 2.1.20
[  2768.198] Module class: X.Org Video Driver
[  2768.198] ABI class: X.Org Video Driver, version 23.0
[  2768.198] (II) LoadModule: "modesetting"
[  2768.199] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  2768.199] (II) Module modesetting: vendor="X.Org Foundation"
[  2768.199] compiled for 1.19.3, module version = 1.19.3
[  2768.199] Module class: X.Org Video Driver
[  2768.199] ABI class: X.Org Video Driver, version 23.0
[  2768.199] (II) LoadModule: "intel"
[  2768.199] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[  2768.199] (II) Module intel: vendor="X.Org Foundation"
[  2768.199] compiled for 1.19.3, module version = 2.99.917
[  2768.199] Module class: X.Org Video Driver
[  2768.199] ABI class: X.Org Video Driver, version 23.0
[  2768.199] (II) LoadModule: "fbdev"
[  2768.199] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[  2768.199] (II) Module fbdev: vendor="X.Org Foundation"
[  2768.199] compiled for 1.19.0, module version = 0.4.4
[  2768.199] Module class: X.Org Video Driver
[  2768.199] ABI class: X.Org Video Driver, version 23.0
[  2768.199] (II) LoadModule: "vesa"
[  2768.199] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[  2768.199] (II) Module vesa: vendor="X.Org Foundation"
[  2768.199] compiled for 1.19.0, module version = 2.3.4
[  2768.199] Module class: X.Org Video Driver
[  2768.199] ABI class: X.Org Video Driver, version 23.0
[  2768.199] (II) NVIDIA dlloader X Driver  378.13  Tue Feb  7 18:01:51 PST 2017
[  2768.199] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[  2768.199] (II) NOUVEAU driver
[  2768.199] (II) NOUVEAU driver for NVIDIA chipset families :
[  2768.199] RIVA TNT        (NV04)
[  2768.199] RIVA TNT2       (NV05)
[  2768.199] GeForce 256     (NV10)
[  2768.199] GeForce 2       (NV11, NV15)
[  2768.199] GeForce 4MX     (NV17, NV18)
[  2768.200] GeForce 3       (NV20)
[  2768.200] GeForce 4Ti     (NV25, NV28)
[  2768.200] GeForce FX      (NV3x)
[  2768.200] GeForce 6       (NV4x)
[  2768.200] GeForce 7       (G7x)
[  2768.200] GeForce 8       (G8x)
[  2768.200] GeForce GTX 200 (NVA0)
[  2768.200] GeForce GTX 400 (NVC0)
[  2768.200] (II) NOUVEAU driver
[  2768.200] (II) NOUVEAU driver for NVIDIA chipset families :
[  2768.200] RIVA TNT        (NV04)
[  2768.200] RIVA TNT2       (NV05)
[  2768.200] GeForce 256     (NV10)
[  2768.200] GeForce 2       (NV11, NV15)
[  2768.200] GeForce 4MX     (NV17, NV18)
[  2768.200] GeForce 3       (NV20)
[  2768.200] GeForce 4Ti     (NV25, NV28)
[  2768.200] GeForce FX      (NV3x)
[  2768.200] GeForce 6       (NV4x)
[  2768.200] GeForce 7       (G7x)
[  2768.200] GeForce 8       (G8x)
[  2768.200] GeForce GTX 200 (NVA0)
[  2768.200] GeForce GTX 400 (NVC0)
[  2768.200] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[  2768.200] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
        i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
        915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
        Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
        GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[  2768.200] (II) intel: Driver for Intel(R) HD Graphics
[  2768.200] (II) intel: Driver for Intel(R) Iris(TM) Graphics
[  2768.200] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics
[  2768.200] (II) FBDEV: driver for framebuffer: fbdev
[  2768.200] (II) VESA: driver for VESA chipsets: vesa
[  2768.223] (II) Loading sub module "fb"
[  2768.223] (II) LoadModule: "fb"
[  2768.223] (II) Loading /usr/lib/xorg/modules/libfb.so
[  2768.223] (II) Module fb: vendor="X.Org Foundation"
[  2768.223] compiled for 1.19.3, module version = 1.0.0
[  2768.223] ABI class: X.Org ANSI C Emulation, version 0.4
[  2768.223] (II) Loading sub module "wfb"
[  2768.223] (II) LoadModule: "wfb"
[  2768.223] (II) Loading /usr/lib/xorg/modules/libwfb.so
[  2768.223] (II) Module wfb: vendor="X.Org Foundation"
[  2768.223] compiled for 1.19.3, module version = 1.0.0
[  2768.223] ABI class: X.Org ANSI C Emulation, version 0.4
[  2768.223] (II) Loading sub module "ramdac"
[  2768.223] (II) LoadModule: "ramdac"
[  2768.223] (II) Module "ramdac" already built-in
[  2768.224] (WW) Falling back to old probe method for modesetting
[  2768.241] (WW) Falling back to old probe method for fbdev
[  2768.241] (II) Loading sub module "fbdevhw"
[  2768.241] (II) LoadModule: "fbdevhw"
[  2768.241] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[  2768.241] (II) Module fbdevhw: vendor="X.Org Foundation"
[  2768.241] compiled for 1.19.3, module version = 0.0.2
[  2768.241] ABI class: X.Org Video Driver, version 23.0
[  2768.241] (WW) Falling back to old probe method for vesa
[  2768.258] (II) modeset(G0): using drv /dev/dri/card0
[  2768.258] (II) NVIDIA(0): Creating default Display subsection in Screen section
        "Default Screen Section" for depth/fbbpp 24/32
[  2768.258] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[  2768.258] (==) NVIDIA(0): RGB weight 888
[  2768.258] (==) NVIDIA(0): Default visual is TrueColor
[  2768.258] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[  2768.258] (II) Applying OutputClass "nvidia" options to /dev/dri/card1
[  2768.258] (**) NVIDIA(0): Option "DPI" "96 x 96"
[  2768.258] (**) NVIDIA(0): Option "AllowEmptyInitialConfiguration"
[  2768.258] (**) NVIDIA(0): Enabling 2D acceleration
[  2768.460] (II) NVIDIA(0): NVIDIA GPU Quadro M1000M (GM107GL-A) at PCI:1:0:0 (GPU-0)
[  2768.460] (--) NVIDIA(0): Memory: 4194304 kBytes
[  2768.460] (--) NVIDIA(0): VideoBIOS: 82.07.9b.00.cc
[  2768.460] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[  2768.460] (II) NVIDIA(0): Validated MetaModes:
[  2768.460] (II) NVIDIA(0):     "NULL"
[  2768.460] (II) NVIDIA(0): Virtual screen size determined to be 640 x 480
[  2768.460] (**) NVIDIA(0): DPI set to (96, 96); computed from "DPI" X config option
[  2768.460] (==) modeset(G0): Depth 24, (==) framebuffer bpp 32
[  2768.460] (==) modeset(G0): RGB weight 888
[  2768.460] (==) modeset(G0): Default visual is TrueColor
[  2768.460] (II) Loading sub module "glamoregl"
[  2768.460] (II) LoadModule: "glamoregl"
[  2768.460] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[  2768.460] (II) Module glamoregl: vendor="X.Org Foundation"
[  2768.460] compiled for 1.19.3, module version = 1.0.0
[  2768.460] ABI class: X.Org ANSI C Emulation, version 0.4
[  2768.460] (II) glamor: OpenGL accelerated X.org driver based.
[  2768.470] (II) glamor: EGL version 1.4 (DRI2):
[  2768.473] (II) modeset(G0): glamor initialized
[  2768.474] (II) modeset(G0): Output eDP-1-1 has no monitor section
[  2768.476] (II) modeset(G0): Output DP-1-1 has no monitor section
[  2768.478] (II) modeset(G0): Output DP-1-2 has no monitor section
[  2768.479] (II) modeset(G0): EDID for output eDP-1-1
[  2768.479] (II) modeset(G0): Manufacturer: WAC  Model: 1053  Serial#: 803
[  2768.479] (II) modeset(G0): Year: 2016  Week: 47
[  2768.479] (II) modeset(G0): EDID Version: 1.4
[  2768.479] (II) modeset(G0): Digital Display Input
[  2768.479] (II) modeset(G0): 8 bits per channel
[  2768.479] (II) modeset(G0): Digital interface is DisplayPort
[  2768.479] (II) modeset(G0): Max Image Size [cm]: horiz.: 35  vert.: 19
[  2768.479] (II) modeset(G0): Gamma: 2.20
[  2768.479] (II) modeset(G0): No DPMS capabilities specified
[  2768.479] (II) modeset(G0): Supported color encodings: RGB 4:4:4
[  2768.479] (II) modeset(G0): First detailed timing is preferred mode
[  2768.479] (II) modeset(G0): Preferred mode is native pixel format and refresh rate
[  2768.479] (II) modeset(G0): redX: 0.640 redY: 0.330   greenX: 0.300 greenY: 0.600
[  2768.479] (II) modeset(G0): blueX: 0.150 blueY: 0.060   whiteX: 0.313 whiteY: 0.329
[  2768.479] (II) modeset(G0): Supported established timings:
[  2768.479] (II) modeset(G0): 640x480@60Hz
[  2768.479] (II) modeset(G0): 800x600@60Hz
[  2768.479] (II) modeset(G0): 1024x768@60Hz
[  2768.479] (II) modeset(G0): Manufacturer's mask: 0
[  2768.479] (II) modeset(G0): Supported standard timings:
[  2768.479] (II) modeset(G0): #0: hsize: 1920  vsize 1080  refresh: 60  vid: 49361
[  2768.479] (II) modeset(G0): #1: hsize: 1680  vsize 1050  refresh: 60  vid: 179
[  2768.479] (II) modeset(G0): #2: hsize: 1600  vsize 900  refresh: 60  vid: 49321
[  2768.479] (II) modeset(G0): #3: hsize: 1440  vsize 900  refresh: 60  vid: 149
[  2768.479] (II) modeset(G0): #4: hsize: 1400  vsize 1050  refresh: 60  vid: 16528
[  2768.479] (II) modeset(G0): #5: hsize: 1280  vsize 1024  refresh: 60  vid: 32897
[  2768.479] (II) modeset(G0): #6: hsize: 1280  vsize 960  refresh: 60  vid: 16513
[  2768.479] (II) modeset(G0): #7: hsize: 1280  vsize 720  refresh: 60  vid: 49281
[  2768.479] (II) modeset(G0): Supported detailed timing:
[  2768.479] (II) modeset(G0): clock: 533.2 MHz   Image Size:  346 x 194 mm
[  2768.479] (II) modeset(G0): h_active: 3840  h_sync: 3888  h_sync_end 3920 h_blank_end 4000 h_border: 0
[  2768.479] (II) modeset(G0): v_active: 2160  v_sync: 2163  v_sync_end 2168 v_blanking: 2222 v_border: 0
[  2768.479] (II) modeset(G0): Monitor name: MStudioPro 16
[  2768.479] (II) modeset(G0): Serial No: 6KH0054000803
[  2768.479] (II) modeset(G0): Ranges: V min: 59 V max: 61 Hz, H min: 31 H max: 135 kHz, PixClock max 605 MHz
[  2768.479] (II) modeset(G0): Supported detailed timing:
[  2768.479] (II) modeset(G0): clock: 594.0 MHz   Image Size:  346 x 194 mm
[  2768.479] (II) modeset(G0): h_active: 3840  h_sync: 4016  h_sync_end 4104 h_blank_end 4400 h_border: 0
[  2768.479] (II) modeset(G0): v_active: 2160  v_sync: 2168  v_sync_end 2178 v_blanking: 2250 v_border: 0
[  2768.479] (II) modeset(G0): Number of EDID sections to follow: 1
[  2768.479] (II) modeset(G0): EDID (in hex):
[  2768.479] (II) modeset(G0): 00ffffffffffff005c23531023030000
[  2768.479] (II) modeset(G0): 2f1a0104a523137802ee95a3544c9926
[  2768.479] (II) modeset(G0): 0f5054210800d1c0b300a9c095009040
[  2768.479] (II) modeset(G0): 8180814081c04dd000a0f0703e803020
[  2768.479] (II) modeset(G0): 35005ac21000001a000000fc004d5374
[  2768.479] (II) modeset(G0): 7564696f50726f203136000000ff0036
[  2768.479] (II) modeset(G0): 4b4830303534303030383033000000fd
[  2768.479] (II) modeset(G0): 003b3d1f873c000a20202020202001e8
[  2768.479] (II) modeset(G0): 020312f0230907078301000065030c00
[  2768.479] (II) modeset(G0): 100008e80030f2705a80b0588a005ac2
[  2768.479] (II) modeset(G0): 1000001e000000000000000000000000
[  2768.479] (II) modeset(G0): 00000000000000000000000000000000
[  2768.479] (II) modeset(G0): 00000000000000000000000000000000
[  2768.479] (II) modeset(G0): 00000000000000000000000000000000
[  2768.479] (II) modeset(G0): 00000000000000000000000000000000
[  2768.479] (II) modeset(G0): 0000000000000000000000000000007f
[  2768.479] (II) modeset(G0): Printing probed modes for output eDP-1-1
[  2768.479] (II) modeset(G0): Modeline "3840x2160"x60.0  533.25  3840 3888 3920 4000  2160 2163 2168 2222 +hsync -vsync (133.3 kHz eP)
[  2768.479] (II) modeset(G0): Modeline "3840x2160"x60.0  594.00  3840 4016 4104 4400  2160 2168 2178 2250 +hsync +vsync (135.0 kHz e)
[  2768.479] (II) modeset(G0): Modeline "2048x1536"x60.0  266.95  2048 2200 2424 2800  1536 1537 1540 1589 -hsync +vsync (95.3 kHz d)
[  2768.479] (II) modeset(G0): Modeline "1920x1440"x60.0  234.00  1920 2048 2256 2600  1440 1441 1444 1500 -hsync +vsync (90.0 kHz d)
[  2768.479] (II) modeset(G0): Modeline "1856x1392"x60.0  218.30  1856 1952 2176 2528  1392 1393 1396 1439 -hsync +vsync (86.4 kHz d)
[  2768.479] (II) modeset(G0): Modeline "1792x1344"x60.0  204.80  1792 1920 2120 2448  1344 1345 1348 1394 -hsync +vsync (83.7 kHz d)
[  2768.479] (II) modeset(G0): Modeline "1920x1080"x60.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 -hsync -vsync (67.5 kHz e)
[  2768.479] (II) modeset(G0): Modeline "1600x1200"x60.0  162.00  1600 1664 1856 2160  1200 1201 1204 1250 +hsync +vsync (75.0 kHz d)
[  2768.479] (II) modeset(G0): Modeline "1680x1050"x60.0  146.25  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
[  2768.479] (II) modeset(G0): Modeline "1400x1050"x60.0  122.00  1400 1488 1640 1880  1050 1052 1064 1082 +hsync +vsync (64.9 kHz d)
[  2768.479] (II) modeset(G0): Modeline "1400x1050"x60.0  121.75  1400 1488 1632 1864  1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[  2768.479] (II) modeset(G0): Modeline "1600x900"x60.0  108.00  1600 1624 1704 1800  900 901 904 1000 +hsync +vsync (60.0 kHz e)
[  2768.479] (II) modeset(G0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[  2768.479] (II) modeset(G0): Modeline "1440x900"x59.9  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz e)
[  2768.479] (II) modeset(G0): Modeline "1280x960"x60.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
[  2768.479] (II) modeset(G0): Modeline "1280x720"x60.0   74.25  1280 1390 1430 1650  720 725 730 750 +hsync +vsync (45.0 kHz e)
[  2768.479] (II) modeset(G0): Modeline "1280x720"x59.9   74.18  1280 1390 1430 1650  720 725 730 750 +hsync +vsync (45.0 kHz e)
[  2768.479] (II) modeset(G0): Modeline "1024x768"x60.0  133.47  1024 1100 1212 1400  768 768 770 794 doublescan -hsync +vsync (95.3 kHz d)
[  2768.479] (II) modeset(G0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[  2768.479] (II) modeset(G0): Modeline "960x720"x60.0  117.00  960 1024 1128 1300  720 720 722 750 doublescan -hsync +vsync (90.0 kHz d)
[  2768.479] (II) modeset(G0): Modeline "928x696"x60.1  109.15  928 976 1088 1264  696 696 698 719 doublescan -hsync +vsync (86.4 kHz d)
[  2768.479] (II) modeset(G0): Modeline "896x672"x60.0  102.40  896 960 1060 1224  672 672 674 697 doublescan -hsync +vsync (83.7 kHz d)
[  2768.479] (II) modeset(G0): Modeline "800x600"x60.0   81.00  800 832 928 1080  600 600 602 625 doublescan +hsync +vsync (75.0 kHz d)
[  2768.479] (II) modeset(G0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[  2768.479] (II) modeset(G0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz d)
[  2768.479] (II) modeset(G0): Modeline "700x525"x60.0   61.00  700 744 820 940  525 526 532 541 doublescan +hsync +vsync (64.9 kHz d)
[  2768.479] (II) modeset(G0): Modeline "640x512"x60.0   54.00  640 664 720 844  512 512 514 533 doublescan +hsync +vsync (64.0 kHz d)
[  2768.479] (II) modeset(G0): Modeline "640x480"x60.0   54.00  640 688 744 900  480 480 482 500 doublescan +hsync +vsync (60.0 kHz d)
[  2768.479] (II) modeset(G0): Modeline "640x480"x60.0   25.20  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[  2768.479] (II) modeset(G0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[  2768.479] (II) modeset(G0): Modeline "512x384"x60.0   32.50  512 524 592 672  384 385 388 403 doublescan -hsync -vsync (48.4 kHz d)
[  2768.479] (II) modeset(G0): Modeline "400x300"x60.3   20.00  400 420 484 528  300 300 302 314 doublescan +hsync +vsync (37.9 kHz d)
[  2768.479] (II) modeset(G0): Modeline "400x300"x56.3   18.00  400 412 448 512  300 300 301 312 doublescan +hsync +vsync (35.2 kHz d)
[  2768.479] (II) modeset(G0): Modeline "320x240"x60.1   12.59  320 328 376 400  240 245 246 262 doublescan -hsync -vsync (31.5 kHz d)
[  2768.481] (II) modeset(G0): EDID for output DP-1-1
[  2768.483] (II) modeset(G0): EDID for output DP-1-2
[  2768.483] (==) modeset(G0): Using gamma correction (1.0, 1.0, 1.0)
[  2768.483] (==) modeset(G0): DPI set to (96, 96)
[  2768.483] (II) Loading sub module "fb"
[  2768.483] (II) LoadModule: "fb"
[  2768.483] (II) Loading /usr/lib/xorg/modules/libfb.so
[  2768.483] (II) Module fb: vendor="X.Org Foundation"
[  2768.483] compiled for 1.19.3, module version = 1.0.0
[  2768.483] ABI class: X.Org ANSI C Emulation, version 0.4
[  2768.483] (II) UnloadModule: "nouveau"
[  2768.483] (II) Unloading nouveau
[  2768.483] (II) UnloadModule: "nv"
[  2768.483] (II) Unloading nv
[  2768.483] (II) UnloadModule: "intel"
[  2768.483] (II) Unloading intel
[  2768.483] (II) UnloadModule: "fbdev"
[  2768.483] (II) Unloading fbdev
[  2768.483] (II) UnloadSubModule: "fbdevhw"
[  2768.483] (II) Unloading fbdevhw
[  2768.483] (II) UnloadModule: "vesa"
[  2768.483] (II) Unloading vesa
[  2768.483] (--) Depth 24 pixmap format is 32 bpp
[  2768.539] (==) modeset(G0): Backing store enabled
[  2768.539] (==) modeset(G0): Silken mouse enabled
[  2768.539] (II) modeset(G0): RandR 1.2 enabled, ignore the following RandR disabled message.
[  2768.539] (==) modeset(G0): DPMS enabled
[  2768.539] (II) modeset(G0): [DRI2] Setup complete
[  2768.539] (II) modeset(G0): [DRI2]   DRI driver: i965
[  2768.539] (II) modeset(G0): [DRI2]   VDPAU driver: i965
[  2768.539] (II) NVIDIA: Using 12288.00 MB of virtual memory for indirect memory
[  2768.539] (II) NVIDIA:     access.
[  2768.558] (II) NVIDIA(0): Built-in logo is bigger than the screen.
[  2768.558] (II) NVIDIA(0): Setting mode "NULL"
[  2768.562] (==) NVIDIA(0): Disabling shared memory pixmaps
[  2768.562] (==) NVIDIA(0): Backing store enabled
[  2768.562] (==) NVIDIA(0): Silken mouse enabled
[  2768.562] (==) NVIDIA(0): DPMS enabled
[  2768.562] (WW) NVIDIA(0): Option "PrimaryGPU" is not used
[  2768.562] (II) Loading sub module "dri2"
[  2768.562] (II) LoadModule: "dri2"
[  2768.562] (II) Module "dri2" already built-in
[  2768.562] (II) NVIDIA(0): [DRI2] Setup complete
[  2768.562] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[  2768.562] (--) RandR disabled
[  2768.564] (II) Initializing extension GLX
[  2768.564] (II) Indirect GLX disabled.
[  2768.836] (II) modeset(G0): Damage tracking initialized
[  2768.915] (II) config/udev: Adding input device Power Button (/dev/input/event6)
[  2768.915] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[  2768.915] (II) LoadModule: "libinput"
[  2768.915] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[  2768.915] (II) Module libinput: vendor="X.Org Foundation"
[  2768.915] compiled for 1.19.2, module version = 0.25.0
[  2768.915] Module class: X.Org XInput Driver
[  2768.915] ABI class: X.Org XInput driver, version 24.1
[  2768.915] (II) Using input driver 'libinput' for 'Power Button'
[  2768.915] (**) Power Button: always reports core events
[  2768.916] (**) Option "Device" "/dev/input/event6"
[  2768.916] (**) Option "_source" "server/udev"
[  2768.916] (II) input device 'Power Button', /dev/input/event6 is tagged by udev as: Keyboard
[  2768.916] (II) input device 'Power Button', /dev/input/event6 is a keyboard
[  2768.936] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event6"
[  2768.936] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[  2768.937] (II) input device 'Power Button', /dev/input/event6 is tagged by udev as: Keyboard
[  2768.937] (II) input device 'Power Button', /dev/input/event6 is a keyboard
[  2768.937] (II) config/udev: Adding input device Video Bus (/dev/input/event10)
[  2768.937] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[  2768.937] (II) Using input driver 'libinput' for 'Video Bus'
[  2768.937] (**) Video Bus: always reports core events
[  2768.937] (**) Option "Device" "/dev/input/event10"
[  2768.937] (**) Option "_source" "server/udev"
[  2768.937] (II) input device 'Video Bus', /dev/input/event10 is tagged by udev as: Keyboard
[  2768.937] (II) input device 'Video Bus', /dev/input/event10 is a keyboard
[  2768.956] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10/event10"
[  2768.956] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[  2768.957] (II) input device 'Video Bus', /dev/input/event10 is tagged by udev as: Keyboard
[  2768.957] (II) input device 'Video Bus', /dev/input/event10 is a keyboard
[  2768.957] (II) config/udev: Adding input device Video Bus (/dev/input/event11)
[  2768.957] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[  2768.957] (II) Using input driver 'libinput' for 'Video Bus'
[  2768.957] (**) Video Bus: always reports core events
[  2768.957] (**) Option "Device" "/dev/input/event11"
[  2768.957] (**) Option "_source" "server/udev"
[  2768.957] (II) input device 'Video Bus', /dev/input/event11 is tagged by udev as: Keyboard
[  2768.957] (II) input device 'Video Bus', /dev/input/event11 is a keyboard
[  2768.976] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:38/LNXVIDEO:01/input/input11/event11"
[  2768.976] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
[  2768.977] (II) input device 'Video Bus', /dev/input/event11 is tagged by udev as: Keyboard
[  2768.977] (II) input device 'Video Bus', /dev/input/event11 is a keyboard
[  2768.978] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[  2768.978] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[  2768.978] (II) Using input driver 'libinput' for 'Power Button'
[  2768.978] (**) Power Button: always reports core events
[  2768.978] (**) Option "Device" "/dev/input/event3"
[  2768.978] (**) Option "_source" "server/udev"
[  2768.979] (II) input device 'Power Button', /dev/input/event3 is tagged by udev as: Keyboard
[  2768.979] (II) input device 'Power Button', /dev/input/event3 is a keyboard
[  2768.996] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3/event3"
[  2768.996] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 9)
[  2768.998] (II) input device 'Power Button', /dev/input/event3 is tagged by udev as: Keyboard
[  2768.998] (II) input device 'Power Button', /dev/input/event3 is a keyboard
[  2768.998] (II) config/udev: Adding input device Lid Switch (/dev/input/event5)
[  2768.998] (II) No input driver specified, ignoring this device.
[  2768.998] (II) This device may have been added with another device file.
[  2768.999] (II) config/udev: Adding input device Sleep Button (/dev/input/event1)
[  2768.999] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[  2768.999] (II) Using input driver 'libinput' for 'Sleep Button'
[  2768.999] (**) Sleep Button: always reports core events
[  2768.999] (**) Option "Device" "/dev/input/event1"
[  2768.999] (**) Option "_source" "server/udev"
[  2769.000] (II) input device 'Sleep Button', /dev/input/event1 is tagged by udev as: Keyboard
[  2769.000] (II) input device 'Sleep Button', /dev/input/event1 is a keyboard
[  2769.026] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1/event1"
[  2769.026] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 10)
[  2769.028] (II) input device 'Sleep Button', /dev/input/event1 is tagged by udev as: Keyboard
[  2769.028] (II) input device 'Sleep Button', /dev/input/event1 is a keyboard
[  2769.029] (II) config/udev: Adding input device USB Camera (/dev/input/event17)
[  2769.029] (**) USB Camera: Applying InputClass "libinput keyboard catchall"
[  2769.029] (II) Using input driver 'libinput' for 'USB Camera'
[  2769.030] (**) USB Camera: always reports core events
[  2769.030] (**) Option "Device" "/dev/input/event17"
[  2769.030] (**) Option "_source" "server/udev"
[  2769.030] (II) input device 'USB Camera', /dev/input/event17 is tagged by udev as: Keyboard
[  2769.030] (II) input device 'USB Camera', /dev/input/event17 is a keyboard
[  2769.076] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input17/event17"
[  2769.076] (II) XINPUT: Adding extended input device "USB Camera" (type: KEYBOARD, id 11)
[  2769.078] (II) input device 'USB Camera', /dev/input/event17 is tagged by udev as: Keyboard
[  2769.078] (II) input device 'USB Camera', /dev/input/event17 is a keyboard
[  2769.080] (II) config/udev: Adding input device Wacom MobileStudio Pro 16 Pen (/dev/input/event19)
[  2769.080] (**) Wacom MobileStudio Pro 16 Pen: Applying InputClass "libinput tablet catchall"
[  2769.080] (**) Wacom MobileStudio Pro 16 Pen: Applying InputClass "Wacom USB tablet class"
[  2769.080] (**) Wacom MobileStudio Pro 16 Pen: Applying InputClass "Wacom tablet class"
[  2769.080] (II) LoadModule: "wacom"
[  2769.080] (II) Loading /usr/lib/xorg/modules/input/wacom_drv.so
[  2769.081] (II) Module wacom: vendor="X.Org Foundation"
[  2769.081] compiled for 1.19.2, module version = 0.34.2
[  2769.081] Module class: X.Org XInput Driver
[  2769.081] ABI class: X.Org XInput driver, version 24.1
[  2769.081] (II) wacom: Driver for Wacom graphics tablets: PenPartner, Graphire,
        Graphire2 4x5, Graphire2 5x7, Graphire3 4x5, Graphire3 6x8,
        Graphire4 4x5, Graphire4 6x8, BambooFun 4x5, BambooFun 6x8,
        Bamboo1 Medium, Graphire4 6x8 BlueTooth, CTL-460, CTH-461, CTL-660,
        CTL-461/S, Bamboo Touch, CTH-460/K, CTH-461/S, CTH-661/S1, CTH-461/L,
        CTH-661/L, Intuos 4x5, Intuos 6x8, Intuos 9x12, Intuos 12x12,
        Intuos 12x18, PTU600, PL400, PL500, PL600, PL600SX, PL550, PL800,
        PL700, PL510, PL710, DTI520, DTF720, DTF720a, DTF521, DTU1931,
        DTU2231, DTU1631, Intuos2 4x5, Intuos2 6x8, Intuos2 9x12,
        Intuos2 12x12, Intuos2 12x18, Intuos2 6x8 , Volito, PenStation,
        Volito2 4x5, Volito2 2x3, PenPartner2, Bamboo, Bamboo1, Bamboo1 4x6,
        Bamboo1 5x8, Intuos3 4x5, Intuos3 6x8, Intuos3 9x12, Intuos3 12x12,
        Intuos3 12x19, Intuos3 6x11, Intuos3 4x6, Intuos4 4x6, Intuos4 6x9,
        Intuos4 8x13, Intuos4 12x19, Intuos4 WL USB Endpoint,
        Intuos4 WL Bluetooth Endpoint, Intuos5 touch S, Intuos5 touch M,
        Intuos5 touch L, Intuos5 S, Intuos5 M, Intuos Pro S, Intuos Pro M,
        Intuos Pro L, Cintiq 21UX, Cintiq 20WSX, Cintiq 12WX, Cintiq 21UX2,
        Cintiq 24HD, Cintiq 22HD, Cintiq 24HD touch (EMR digitizer),
        Cintiq 13HD, DTK2241, DTH2242, Cintiq 22HDT, TabletPC 0x90,
        TabletPC 0x93, TabletPC 0x97, TabletPC 0x9A, CapPlus  0x9F,
        TabletPC 0xE2, TabletPC 0xE3, TabletPC 0xE5, TabletPC 0xE6,
        TabletPC 0xEC, TabletPC 0xED, TabletPC 0xEF, TabletPC 0x100,
        TabletPC 0x101, TabletPC 0x10D, TabletPC 0x116, TabletPC 0x12C,
        TabletPC 0x4001, TabletPC 0x4004, TabletPC 0x5000, TabletPC 0x5002,
        usb:172f:0024, usb:172f:0025, usb:172f:0026, usb:172f:0027,
        usb:172f:0028, usb:172f:0030, usb:172f:0031, usb:172f:0032,
        usb:172f:0033, usb:172f:0034, usb:172f:0035, usb:172f:0036,
        usb:172f:0037, usb:172f:0038, usb:172f:0039, usb:172f:0051,
        usb:172f:0052, usb:172f:0053, usb:172f:0054, usb:172f:0055,
        usb:172f:0056, usb:172f:0057, usb:172f:0058, usb:172f:0500,
        usb:172f:0501, usb:172f:0502, usb:172f:0503, usb:1b96:0001,
        usb:17ef:6004
[  2769.083] (II) Using input driver 'wacom' for 'Wacom MobileStudio Pro 16 Pen'
[  2769.083] (**) Wacom MobileStudio Pro 16 Pen: always reports core events
[  2769.083] (**) Option "Device" "/dev/input/event19"
[  2769.140] (II) Wacom MobileStudio Pro 16 Pen: type not specified, assuming 'stylus'.
[  2769.140] (II) Wacom MobileStudio Pro 16 Pen: other types will be automatically added.
[  2769.140] (--) Wacom MobileStudio Pro 16 Pen stylus: using pressure threshold of 873 for button 1
[  2769.140] (--) Wacom MobileStudio Pro 16 Pen stylus: maxX=69520 maxY=39280 maxZ=8191 resX=200000 resY=200000  tilt=enabled
[  2769.140] (II) Wacom MobileStudio Pro 16 Pen stylus: hotplugging dependent devices.
[  2769.140] (EE) Wacom MobileStudio Pro 16 Pen stylus: Invalid type 'touch' for this device.
[  2769.140] (EE) Wacom MobileStudio Pro 16 Pen stylus: Invalid type 'pad' for this device.
[  2769.140] (II) Wacom MobileStudio Pro 16 Pen stylus: hotplugging completed.
[  2769.176] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.1/1-6.1:1.0/0003:056A:034E.000D/input/input21/event19"
[  2769.176] (II) XINPUT: Adding extended input device "Wacom MobileStudio Pro 16 Pen stylus" (type: STYLUS, id 12)
[  2769.177] (**) Wacom MobileStudio Pro 16 Pen stylus: (accel) keeping acceleration scheme 1
[  2769.177] (**) Wacom MobileStudio Pro 16 Pen stylus: (accel) acceleration profile 0
[  2769.177] (**) Wacom MobileStudio Pro 16 Pen stylus: (accel) acceleration factor: 2.000
[  2769.177] (**) Wacom MobileStudio Pro 16 Pen stylus: (accel) acceleration threshold: 4
[  2769.235] (II) config/udev: Adding input device Wacom MobileStudio Pro 16 Pen (/dev/input/mouse2)
[  2769.235] (II) No input driver specified, ignoring this device.
[  2769.235] (II) This device may have been added with another device file.
[  2769.236] (II) config/udev: Adding input device Wacom MobileStudio Pro 16 Pad (/dev/input/event20)
[  2769.237] (**) Wacom MobileStudio Pro 16 Pad: Applying InputClass "libinput tablet catchall"
[  2769.237] (**) Wacom MobileStudio Pro 16 Pad: Applying InputClass "Wacom USB tablet class"
[  2769.237] (**) Wacom MobileStudio Pro 16 Pad: Applying InputClass "Wacom tablet class"
[  2769.237] (II) Using input driver 'wacom' for 'Wacom MobileStudio Pro 16 Pad'
[  2769.237] (**) Wacom MobileStudio Pro 16 Pad: always reports core events
[  2769.237] (**) Option "Device" "/dev/input/event20"
[  2769.237] (EE) Wacom MobileStudio Pro 16 Pad: Invalid type 'stylus' for this device.
[  2769.237] (EE) Wacom MobileStudio Pro 16 Pad: Invalid type 'eraser' for this device.
[  2769.237] (EE) Wacom MobileStudio Pro 16 Pad: Invalid type 'cursor' for this device.
[  2769.237] (EE) Wacom MobileStudio Pro 16 Pad: Invalid type 'touch' for this device.
[  2769.237] (II) Wacom MobileStudio Pro 16 Pad: type not specified, assuming 'pad'.
[  2769.237] (II) Wacom MobileStudio Pro 16 Pad: other types will be automatically added.
[  2769.237] (II) Wacom MobileStudio Pro 16 Pad pad: hotplugging dependent devices.
[  2769.237] (EE) Wacom MobileStudio Pro 16 Pad pad: Invalid type 'stylus' for this device.
[  2769.237] (EE) Wacom MobileStudio Pro 16 Pad pad: Invalid type 'eraser' for this device.
[  2769.237] (EE) Wacom MobileStudio Pro 16 Pad pad: Invalid type 'cursor' for this device.
[  2769.237] (EE) Wacom MobileStudio Pro 16 Pad pad: Invalid type 'touch' for this device.
[  2769.237] (II) Wacom MobileStudio Pro 16 Pad pad: hotplugging completed.
[  2769.280] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.1/1-6.1:1.0/0003:056A:034E.000D/input/input23/event20"
[  2769.280] (II) XINPUT: Adding extended input device "Wacom MobileStudio Pro 16 Pad pad" (type: PAD, id 13)
[  2769.280] (**) Wacom MobileStudio Pro 16 Pad pad: (accel) keeping acceleration scheme 1
[  2769.281] (**) Wacom MobileStudio Pro 16 Pad pad: (accel) acceleration profile 0
[  2769.281] (**) Wacom MobileStudio Pro 16 Pad pad: (accel) acceleration factor: 2.000
[  2769.281] (**) Wacom MobileStudio Pro 16 Pad pad: (accel) acceleration threshold: 4
[  2769.282] (II) config/udev: Adding input device Wacom MobileStudio Pro 16 Pad (/dev/input/js0)
[  2769.282] (II) No input driver specified, ignoring this device.
[  2769.282] (II) This device may have been added with another device file.
[  2769.284] (II) config/udev: Adding input device Wacom MobileStudio Pro 16 Touch Finger (/dev/input/event18)
[  2769.284] (**) Wacom MobileStudio Pro 16 Touch Finger: Applying InputClass "libinput touchscreen catchall"
[  2769.284] (**) Wacom MobileStudio Pro 16 Touch Finger: Applying InputClass "Wacom USB touchscreen class"
[  2769.284] (**) Wacom MobileStudio Pro 16 Touch Finger: Applying InputClass "Wacom touchscreen class"
[  2769.284] (II) Using input driver 'wacom' for 'Wacom MobileStudio Pro 16 Touch Finger'
[  2769.284] (**) Wacom MobileStudio Pro 16 Touch Finger: always reports core events
[  2769.284] (**) Option "Device" "/dev/input/event18"
[  2769.340] (EE) Wacom MobileStudio Pro 16 Touch Finger: Invalid type 'stylus' for this device.
[  2769.340] (EE) Wacom MobileStudio Pro 16 Touch Finger: Invalid type 'eraser' for this device.
[  2769.340] (EE) Wacom MobileStudio Pro 16 Touch Finger: Invalid type 'cursor' for this device.
[  2769.340] (II) Wacom MobileStudio Pro 16 Touch Finger: type not specified, assuming 'touch'.
[  2769.340] (II) Wacom MobileStudio Pro 16 Touch Finger: other types will be automatically added.
[  2769.340] (--) Wacom MobileStudio Pro 16 Touch Finger touch: maxX=13824 maxY=7776 maxZ=0 resX=40000 resY=40000
[  2769.340] (II) Wacom MobileStudio Pro 16 Touch Finger touch: hotplugging dependent devices.
[  2769.340] (EE) Wacom MobileStudio Pro 16 Touch Finger touch: Invalid type 'stylus' for this device.
[  2769.340] (EE) Wacom MobileStudio Pro 16 Touch Finger touch: Invalid type 'eraser' for this device.
[  2769.340] (EE) Wacom MobileStudio Pro 16 Touch Finger touch: Invalid type 'cursor' for this device.
[  2769.340] (EE) Wacom MobileStudio Pro 16 Touch Finger touch: Invalid type 'pad' for this device.
[  2769.340] (II) Wacom MobileStudio Pro 16 Touch Finger touch: hotplugging completed.
[  2769.376] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.3/1-6.3:1.0/0003:056A:034B.000E/input/input25/event18"
[  2769.376] (II) XINPUT: Adding extended input device "Wacom MobileStudio Pro 16 Touch Finger touch" (type: TOUCH, id 14)
[  2769.377] (**) Wacom MobileStudio Pro 16 Touch Finger touch: (accel) keeping acceleration scheme 1
[  2769.377] (**) Wacom MobileStudio Pro 16 Touch Finger touch: (accel) acceleration profile 0
[  2769.377] (**) Wacom MobileStudio Pro 16 Touch Finger touch: (accel) acceleration factor: 2.000
[  2769.377] (**) Wacom MobileStudio Pro 16 Touch Finger touch: (accel) acceleration threshold: 4
[  2769.435] (II) config/udev: Adding input device Wacom MobileStudio Pro 16 Touch Finger (/dev/input/mouse1)
[  2769.435] (II) No input driver specified, ignoring this device.
[  2769.435] (II) This device may have been added with another device file.
[  2769.436] (II) config/udev: Adding input device Intel RealSense 3D Camera R200 (/dev/input/event8)
[  2769.436] (**) Intel RealSense 3D Camera R200: Applying InputClass "libinput keyboard catchall"
[  2769.436] (II) Using input driver 'libinput' for 'Intel RealSense 3D Camera R200'
[  2769.436] (**) Intel RealSense 3D Camera R200: always reports core events
[  2769.436] (**) Option "Device" "/dev/input/event8"
[  2769.436] (**) Option "_source" "server/udev"
[  2769.437] (II) input device 'Intel RealSense 3D Camera R200', /dev/input/event8 is tagged by udev as: Keyboard
[  2769.437] (II) input device 'Intel RealSense 3D Camera R200', /dev/input/event8 is a keyboard
[  2769.480] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4:1.2/input/input8/event8"
[  2769.480] (II) XINPUT: Adding extended input device "Intel RealSense 3D Camera R200" (type: KEYBOARD, id 15)
[  2769.481] (II) input device 'Intel RealSense 3D Camera R200', /dev/input/event8 is tagged by udev as: Keyboard
[  2769.481] (II) input device 'Intel RealSense 3D Camera R200', /dev/input/event8 is a keyboard
[  2769.483] (II) config/udev: Adding input device Intel RealSense 3D Camera R200 (/dev/input/event9)
[  2769.483] (**) Intel RealSense 3D Camera R200: Applying InputClass "libinput keyboard catchall"
[  2769.483] (II) Using input driver 'libinput' for 'Intel RealSense 3D Camera R200'
[  2769.483] (**) Intel RealSense 3D Camera R200: always reports core events
[  2769.483] (**) Option "Device" "/dev/input/event9"
[  2769.483] (**) Option "_source" "server/udev"
[  2769.484] (II) input device 'Intel RealSense 3D Camera R200', /dev/input/event9 is tagged by udev as: Keyboard
[  2769.484] (II) input device 'Intel RealSense 3D Camera R200', /dev/input/event9 is a keyboard
[  2769.530] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4:1.4/input/input9/event9"
[  2769.530] (II) XINPUT: Adding extended input device "Intel RealSense 3D Camera R200" (type: KEYBOARD, id 16)
[  2769.531] (II) input device 'Intel RealSense 3D Camera R200', /dev/input/event9 is tagged by udev as: Keyboard
[  2769.531] (II) input device 'Intel RealSense 3D Camera R200', /dev/input/event9 is a keyboard
[  2769.534] (II) config/udev: Adding input device Lenovo ThinkPad Compact USB Keyboard with TrackPoint (/dev/input/event0)
[  2769.534] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: Applying InputClass "libinput keyboard catchall"
[  2769.534] (II) Using input driver 'libinput' for 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint'
[  2769.534] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: always reports core events
[  2769.534] (**) Option "Device" "/dev/input/event0"
[  2769.534] (**) Option "_source" "server/udev"
[  2769.535] (II) input device 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint', /dev/input/event0 is tagged by udev as: Keyboard
[  2769.535] (II) input device 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint', /dev/input/event0 is a keyboard
[  2769.560] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/0000:03:00.0/usb3/3-2/3-2:1.0/0003:17EF:6047.0001/input/input0/event0"
[  2769.560] (II) XINPUT: Adding extended input device "Lenovo ThinkPad Compact USB Keyboard with TrackPoint" (type: KEYBOARD, id 17)
[  2769.562] (II) input device 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint', /dev/input/event0 is tagged by udev as: Keyboard
[  2769.562] (II) input device 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint', /dev/input/event0 is a keyboard
[  2769.564] (II) config/udev: Adding input device Lenovo ThinkPad Compact USB Keyboard with TrackPoint (/dev/input/event4)
[  2769.564] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: Applying InputClass "libinput pointer catchall"
[  2769.564] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: Applying InputClass "libinput keyboard catchall"
[  2769.564] (II) Using input driver 'libinput' for 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint'
[  2769.564] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: always reports core events
[  2769.564] (**) Option "Device" "/dev/input/event4"
[  2769.564] (**) Option "_source" "server/udev"
[  2769.565] (II) input device 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint', /dev/input/event4 is tagged by udev as: Keyboard Mouse Pointingstick
[  2769.565] (II) input device 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint', /dev/input/event4 is a pointer caps
[  2769.565] (II) input device 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint', /dev/input/event4 is a keyboard
[  2769.590] (II) libinput: Lenovo ThinkPad Compact USB Keyboard with TrackPoint: needs a virtual subdevice
[  2769.590] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/0000:03:00.0/usb3/3-2/3-2:1.1/0003:17EF:6047.0002/input/input4/event4"
[  2769.590] (II) XINPUT: Adding extended input device "Lenovo ThinkPad Compact USB Keyboard with TrackPoint" (type: MOUSE, id 18)
[  2769.591] (**) Option "AccelerationScheme" "none"
[  2769.591] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: (accel) selected scheme none/0
[  2769.591] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: (accel) acceleration factor: 2.000
[  2769.591] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: (accel) acceleration threshold: 4
[  2769.592] (II) input device 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint', /dev/input/event4 is tagged by udev as: Keyboard Mouse Pointingstick
[  2769.592] (II) input device 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint', /dev/input/event4 is a pointer caps
[  2769.592] (II) input device 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint', /dev/input/event4 is a keyboard
[  2769.594] (II) config/udev: Adding input device Lenovo ThinkPad Compact USB Keyboard with TrackPoint (/dev/input/mouse0)
[  2769.594] (II) No input driver specified, ignoring this device.
[  2769.594] (II) This device may have been added with another device file.
[  2769.595] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event12)
[  2769.595] (II) No input driver specified, ignoring this device.
[  2769.595] (II) This device may have been added with another device file.
[  2769.595] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event13)
[  2769.595] (II) No input driver specified, ignoring this device.
[  2769.595] (II) This device may have been added with another device file.
[  2769.596] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event14)
[  2769.596] (II) No input driver specified, ignoring this device.
[  2769.596] (II) This device may have been added with another device file.
[  2769.597] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event15)
[  2769.597] (II) No input driver specified, ignoring this device.
[  2769.597] (II) This device may have been added with another device file.
[  2769.597] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event16)
[  2769.598] (II) No input driver specified, ignoring this device.
[  2769.598] (II) This device may have been added with another device file.
[  2769.598] (II) config/udev: Adding input device Intel HID events (/dev/input/event2)
[  2769.598] (**) Intel HID events: Applying InputClass "libinput keyboard catchall"
[  2769.598] (II) Using input driver 'libinput' for 'Intel HID events'
[  2769.598] (**) Intel HID events: always reports core events
[  2769.598] (**) Option "Device" "/dev/input/event2"
[  2769.598] (**) Option "_source" "server/udev"
[  2769.599] (II) input device 'Intel HID events', /dev/input/event2 is tagged by udev as: Keyboard
[  2769.599] (II) input device 'Intel HID events', /dev/input/event2 is a keyboard
[  2769.620] (**) Option "config_info" "udev:/sys/devices/platform/INT33D5:00/input/input2/event2"
[  2769.620] (II) XINPUT: Adding extended input device "Intel HID events" (type: KEYBOARD, id 19)
[  2769.621] (II) input device 'Intel HID events', /dev/input/event2 is tagged by udev as: Keyboard
[  2769.621] (II) input device 'Intel HID events', /dev/input/event2 is a keyboard
[  2769.622] (II) config/udev: Adding input device PC Speaker (/dev/input/event7)
[  2769.622] (II) No input driver specified, ignoring this device.
[  2769.622] (II) This device may have been added with another device file.
[  2769.629] (**) Wacom MobileStudio Pro 16 Pen eraser: Applying InputClass "libinput tablet catchall"
[  2769.629] (**) Wacom MobileStudio Pro 16 Pen eraser: Applying InputClass "Wacom USB tablet class"
[  2769.629] (**) Wacom MobileStudio Pro 16 Pen eraser: Applying InputClass "Wacom tablet class"
[  2769.629] (II) Using input driver 'wacom' for 'Wacom MobileStudio Pro 16 Pen eraser'
[  2769.629] (**) Wacom MobileStudio Pro 16 Pen eraser: always reports core events
[  2769.629] (**) Option "Device" "/dev/input/event19"
[  2769.629] (**) Option "Type" "eraser"
[  2769.630] (--) Wacom MobileStudio Pro 16 Pen eraser: maxX=69520 maxY=39280 maxZ=8191 resX=200000 resY=200000  tilt=enabled
[  2769.650] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.1/1-6.1:1.0/0003:056A:034E.000D/input/input21/event19"
[  2769.650] (II) XINPUT: Adding extended input device "Wacom MobileStudio Pro 16 Pen eraser" (type: ERASER, id 20)
[  2769.650] (**) Wacom MobileStudio Pro 16 Pen eraser: (accel) keeping acceleration scheme 1
[  2769.650] (**) Wacom MobileStudio Pro 16 Pen eraser: (accel) acceleration profile 0
[  2769.650] (**) Wacom MobileStudio Pro 16 Pen eraser: (accel) acceleration factor: 2.000
[  2769.650] (**) Wacom MobileStudio Pro 16 Pen eraser: (accel) acceleration threshold: 4
[  2769.650] (**) Wacom MobileStudio Pro 16 Pen cursor: Applying InputClass "libinput tablet catchall"
[  2769.651] (**) Wacom MobileStudio Pro 16 Pen cursor: Applying InputClass "Wacom USB tablet class"
[  2769.651] (**) Wacom MobileStudio Pro 16 Pen cursor: Applying InputClass "Wacom tablet class"
[  2769.651] (II) Using input driver 'wacom' for 'Wacom MobileStudio Pro 16 Pen cursor'
[  2769.651] (**) Wacom MobileStudio Pro 16 Pen cursor: always reports core events
[  2769.651] (**) Option "Device" "/dev/input/event19"
[  2769.651] (**) Option "Type" "cursor"
[  2769.670] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.1/1-6.1:1.0/0003:056A:034E.000D/input/input21/event19"
[  2769.670] (II) XINPUT: Adding extended input device "Wacom MobileStudio Pro 16 Pen cursor" (type: CURSOR, id 21)
[  2769.670] (**) Wacom MobileStudio Pro 16 Pen cursor: (accel) keeping acceleration scheme 1
[  2769.670] (**) Wacom MobileStudio Pro 16 Pen cursor: (accel) acceleration profile 0
[  2769.670] (**) Wacom MobileStudio Pro 16 Pen cursor: (accel) acceleration factor: 2.000
[  2769.670] (**) Wacom MobileStudio Pro 16 Pen cursor: (accel) acceleration threshold: 4
[  2769.671] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: Applying InputClass "libinput pointer catchall"
[  2769.671] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: Applying InputClass "libinput keyboard catchall"
[  2769.671] (II) Using input driver 'libinput' for 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint'
[  2769.671] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: always reports core events
[  2769.671] (**) Option "Device" "/dev/input/event4"
[  2769.671] (**) Option "_source" "_driver/libinput"
[  2769.671] (II) libinput: Lenovo ThinkPad Compact USB Keyboard with TrackPoint: is a virtual subdevice
[  2769.671] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/0000:03:00.0/usb3/3-2/3-2:1.1/0003:17EF:6047.0002/input/input4/event4"
[  2769.671] (II) XINPUT: Adding extended input device "Lenovo ThinkPad Compact USB Keyboard with TrackPoint" (type: KEYBOARD, id 22)
[  2775.560] (II) UnloadModule: "libinput"
[  2775.560] (II) UnloadModule: "wacom"
[  2775.560] (II) UnloadModule: "wacom"
[  2775.561] (II) UnloadModule: "libinput"
[  2775.561] (II) UnloadModule: "libinput"
[  2775.561] (II) UnloadModule: "libinput"
[  2775.561] (II) UnloadModule: "libinput"
[  2775.561] (II) UnloadModule: "libinput"
[  2775.561] (II) UnloadModule: "wacom"
[  2775.561] (II) UnloadModule: "wacom"
[  2775.561] (II) UnloadModule: "wacom"
[  2775.561] (II) UnloadModule: "libinput"
[  2775.561] (II) UnloadModule: "libinput"
[  2775.561] (II) UnloadModule: "libinput"
[  2775.561] (II) UnloadModule: "libinput"
[  2775.561] (II) UnloadModule: "libinput"
[  2775.561] (II) UnloadModule: "libinput"
[  2775.591] (II) NVIDIA(GPU-0): Deleting GPU-0
[  2775.916] (II) Server terminated successfully (0). Closing log file.


Jason Gerecke <[hidden email]> writes:

> I just gave Arch a whirl to see if a recent update broke something,
> but even after rebooting from a fresh `pacman -Syu` I don't see any
> problems on the MobileStudio Pro 16. Its using GDM by default, but
> even when I switch to multi-user.target and run `startx
> /usr/bin/xfce4-terminal` (I don't have the vanilla xterm installed)
> manually I don't see any problems. No xorg.conf file either...
>
> Notable package versions (though if you upgraded, they should be identical...):
>
>  * core/linux 4.10.4-1
>  * extra/xorg-server 1.19.3-1
>  * extra/xf86-video-fbdev 0.4.4-6
>  * extra/xf86-video-intel 1:2.99.917+767+g7e9e92c8-1
>  * (No nouveau, nv, or nvidia graphics)
>  * extra/mesa 17.0.1-2
>
> If you've got an Xorg.0.log, go ahead and attach it for me to review...
>
> Jason
> ---
> Now instead of four in the eights place /
> you’ve got three, ‘Cause you added one  /
> (That is to say, eight) to the two,     /
> But you can’t take seven from three,    /
> So you look at the sixty-fours....
>
>
>
> On Thu, Mar 23, 2017 at 11:47 AM,  <[hidden email]> wrote:
>>
>> Using an xorg.conf file is the only way I know to change the behavior of
>> xorg. Given that the display is what is not showing I cannot think of
>> anything other than that the automatic configuration is not working.
>>
>> This setup worked perfectly (no stylus) before upgrading the kernel to
>> 4.10 and Xorg to 1.19.3. I thought about downgrading xorg but that is a huge pain.
>> Being on Arch I just did the usual pacman -Syy and pacman -Su. I thought
>> I had screwed something up, but now I'm seeing the same behavior on a
>> fresh install.
>>
>> Xmonad does not have any errors. I can replace it with twm,
>> exec startxfce4 or exec xterm with the same effect. maximized xterm
>> makes no difference.
>>
>> No matter what I do I get a black screen.  alt-ctrl-f1 brings me back to
>> the console. When running the xterm typing 'exit' return will
>> terminate the session.  with Xmonad shift-CMD-Q exits xmonad, etc.
>>
>> running xfce does give a few errors one of which is:
>> Error opening /dev/dri/card0  permission denied
>>
>> I get this from xfsettings and xfwm4
>> g_str_has_prefix: assertion 'prefix != NULL' failed
>>
>> This makes me wonder if there is a conflict with the two video cards the
>> built in Intel and the nvidia.
>>
>> thanks,
>>
>> Eric
>>
>> Jason Gerecke <[hidden email]> writes:
>>
>>> Is there any particular reason you're using an xorg.conf file? That
>>> should be completely unnecessary for most systems, and I didn't
>>> require one when testing a MobileStudio Pro myself. (Note that I can
>>> confirm that `Xorg :0 -configure` crashes, but it appears that's due
>>> to a recently-introduced bug in the X server, not our driver. You
>>> might consider filing a bug at https://bugzilla.freedesktop.org/ if
>>> you rely on the option).
>>>
>>> I'm not familiar with Xmonad, but if it is starting up then I'd
>>> suspect a problem with either: a) incorrect xmonad config, b)
>>> incorrect xinitrc config, or c) missing software.
>>>
>>> As for "startx xterm", is that the literal command that you're
>>> running? If you want to just start an xterm you'll need to provide the
>>> full path (e.g. `startx /usr/bin/xterm`) or else startx will simply
>>> pass "xterm" as a variable to your xinitrc script, where it will
>>> (probably) be ignored. The pointer also won't be visible until its
>>> moved over the xterm, so it may be advisable to use something like
>>> `startx /usr/bin/xterm -maximized` to ensure the xterm takes up the
>>> entire screen.
>>>
>>> Jason
>>> ---
>>> Now instead of four in the eights place /
>>> you’ve got three, ‘Cause you added one  /
>>> (That is to say, eight) to the two,     /
>>> But you can’t take seven from three,    /
>>> So you look at the sixty-fours....
>>>
>>>
>>>
>>> On Wed, Mar 22, 2017 at 5:27 PM,  <[hidden email]> wrote:
>>>>
>>>> One thing leads to another. I decided to upgrade my install because 4.10
>>>> is current. I've done this many times before, but somehow I screwed
>>>> something up.
>>>>
>>>> I started over from scratch, which isn't too bad from where I was. But
>>>> now I can't get Xorg working at all. The log looks good and it looks
>>>> like wacom input is going to work. But all I get is a black screen with
>>>> 'startx xterm' or a simple xinitrc with xmonad.
>>>>
>>>> Xmonad is working sort of. The only thing that works is shift-CMD-Q to
>>>> exit. There are no xmonad.errors.
>>>>
>>>> Does anyone have a working xorg.conf for this machine ?  It seems like it
>>>> worked out of the box before.  'Xorg :0 -configure' crashes now. which
>>>> is what it seems that I did the last time.
>>>>
>>>> The only errors I'm getting are unable to load module 'nouveau' and 'nv'
>>>> plus a few from wacom invalid types, which look ok, because it does find
>>>> the ones it needs.
>>>>
>>>> the 'nv' driver no longer exists from what I can tell, and nouveau isn't
>>>> necessary for this video controller.
>>>>
>>>> So, I'm just hoping someone here has an xorg.conf that works for this
>>>> machine. Suggestions welcome also.
>>>>
>>>> Thanks,
>>>>
>>>> Eric
>>>>
>>>> [hidden email] writes:
>>>>
>>>>> Hi Aaron,
>>>>>
>>>>> I see. Now I've just got to my kernel source in the right place. Either
>>>>> I haven't found the right Arch doc or it's just not very easy..
>>>>>
>>>>> I'm missing the config files for the kernel source and modules. Argh.
>>>>>
>>>>>
>>>>>
>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>
>>>>>> HI Eric,
>>>>>>
>>>>>> If the driver version shows only "v2.00" you haven't installed the
>>>>>> kernel driver.
>>>>>>
>>>>>> If you download the latest driver from
>>>>>> https://sourceforge.net/projects/linuxwacom/files/xf86-input-wacom/input-wacom/
>>>>>> and install it you should have a version suffix on v2.00. I realize it
>>>>>> is confusing how our input-wacom (kernel) driver is nested inside our
>>>>>> xf86 (X driver) folder.
>>>>>>
>>>>>> When I download and install input-wacom-0.34.0.tar.bz2, load and
>>>>>> unload the driver with the commands from the link in my previous
>>>>>> message, and then issue the command 'modinfo wacom | grep version' ,
>>>>>> this is the output I see (granted I'm using a different distro and
>>>>>> kernel, but the version should be the same):
>>>>>>
>>>>>> version:        v2.00-0.34.0
>>>>>> srcversion:     DFB3DEC94FA89060ACBD540
>>>>>> vermagic:       4.8.0-41-generic SMP mod_unload modversions
>>>>>>
>>>>>> Best,
>>>>>> Aaron
>>>>>>
>>>>>> On Fri, Mar 17, 2017 at 2:06 PM,  <[hidden email]> wrote:
>>>>>>>
>>>>>>> Ok, I followed the instruction for building the kernel modules and
>>>>>>> installed them.
>>>>>>>
>>>>>>> I also upgraded Xorg, and reinstalled the official xf86-input-wacom
>>>>>>> package which installed 34.2-1 which matches the kernel modules I
>>>>>>> downloaded.
>>>>>>>
>>>>>>> The driver version in /sys/module/wacom/version is v2.00.
>>>>>>>
>>>>>>> The pen/stylus still does not work.
>>>>>>>
>>>>>>> Is there something I can look at or try that might help understand
>>>>>>> this ?
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Eric
>>>>>>>
>>>>>>> [hidden email] writes:
>>>>>>>
>>>>>>>> Hello Aaron,
>>>>>>>>
>>>>>>>> Thanks for the help.  I thought that was what I was installing when
>>>>>>>> I installed the xf86-input-wacom-git package.
>>>>>>>>
>>>>>>>> https://aur.archlinux.org/packages/xf86-input-wacom-git/
>>>>>>>>
>>>>>>>> I've downloaded the tar ball from kernel downloads, but it has the same
>>>>>>>> name.  So I think I'm confused about which is the kernel driver, which
>>>>>>>> is the X11 driver and what it is that I've actually installed or not
>>>>>>>> installed.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> Eric
>>>>>>>>
>>>>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>>>>
>>>>>>>>> Hi Eric,
>>>>>>>>>
>>>>>>>>> Support for MSP was added in kernel 4.10 so you'll need to install the
>>>>>>>>> input-wacom kernel driver:
>>>>>>>>>
>>>>>>>>> http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>>>>>>>>>
>>>>>>>>> Let us know if you have any other questions.
>>>>>>>>>
>>>>>>>>> Best,
>>>>>>>>> Aaron
>>>>>>>>>
>>>>>>>>> On Fri, Mar 17, 2017 at 10:45 AM,  <[hidden email]> wrote:
>>>>>>>>>>
>>>>>>>>>> Hello,
>>>>>>>>>>
>>>>>>>>>> I have a mobile studio pro running Arch linux.
>>>>>>>>>>
>>>>>>>>>> I have the xf86-input-wacom-git package installed
>>>>>>>>>> aur/xf86-input-wacom-git 0.33.0-1 [installed: 0.34.2-1] (2) (0.07)
>>>>>>>>>>     X.Org Wacom tablet driver (from git)
>>>>>>>>>>
>>>>>>>>>> Linux kernel:
>>>>>>>>>> core/linux 4.8.13-1 (base) [installed]
>>>>>>>>>>
>>>>>>>>>> Xorg Server 1.18.4-1
>>>>>>>>>>
>>>>>>>>>> xsetwacom --list devices
>>>>>>>>>>
>>>>>>>>>> -- sorry it's a different computer...
>>>>>>>>>>
>>>>>>>>>> shows TOUCH, STYLUS, ERASER  with ids of 15, 16, and 17.
>>>>>>>>>>
>>>>>>>>>> Touch works fine. But the pen doesn't work at all.
>>>>>>>>>>
>>>>>>>>>> I've tried it krita and that doesn't work either. I would have expected
>>>>>>>>>> it to work in the OS.
>>>>>>>>>>
>>>>>>>>>> I noticed on the device id doc that mobile studio pro 16 has it's
>>>>>>>>>> version numbers crossed out.  Should this device work ?
>>>>>>>>>>
>>>>>>>>>> I've tried it with the old pen from my cintiq companion, and that
>>>>>>>>>> doesn't work either.
>>>>>>>>>>
>>>>>>>>>> Does anyone have suggestions on how to get this working ?
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>>
>>>>>>>>>> Eric
>>>>>>>>>>
>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Linuxwacom-discuss mailing list
>>>>>>>>>> [hidden email]
>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>> _______________________________________________
>>>> Linuxwacom-discuss mailing list
>>>> [hidden email]
>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: mobile studio pro 16 ?

Jason Gerecke
Thanks for the log. It looks pretty similar to what I see on my system,
except for the presence of a few more video drivers (though only
'nvidia' ends up getting used) and your system's obvious lack of
systemd-logind. I tried installing the nvidia package to see if maybe it
was the source of the problem, but it still seems to work fine.

I do notice that your system uses slightly different monitor timings
than mine, but if the timings were wrong I'd expect the display to go to
sleep (and turn off the backlight) rather than just render nothing.

Finally, I also see that the X server is getting a DPI value of 96 from
somewhere. On my system it says that it can't find the screen's DPI and
so it falls back to 75. While the DPI itself isn't going to change
anything, it might indicate the presence of X configuration files that
are modifying its behavior in ways not captured by the log. Do you have
any files under /etc/X11/xorg.conf.d or have you edited any files under
/usr/share/X11/xorg.conf.d?

Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one /
(That is to say, eight) to the two, /
But you can’t take seven from three, /
So you look at the sixty-fours....

On 03/29/2017 06:47 AM, [hidden email] wrote:
>
> I'm wondering if I shouldn't start over with a fresh install again. But
> maybe this will reveal something.  Here is my log.
>
[snip]

>
> Jason Gerecke <[hidden email]> writes:
>
>> I just gave Arch a whirl to see if a recent update broke something,
>> but even after rebooting from a fresh `pacman -Syu` I don't see any
>> problems on the MobileStudio Pro 16. Its using GDM by default, but
>> even when I switch to multi-user.target and run `startx
>> /usr/bin/xfce4-terminal` (I don't have the vanilla xterm installed)
>> manually I don't see any problems. No xorg.conf file either...
>>
>> Notable package versions (though if you upgraded, they should be identical...):
>>
>>  * core/linux 4.10.4-1
>>  * extra/xorg-server 1.19.3-1
>>  * extra/xf86-video-fbdev 0.4.4-6
>>  * extra/xf86-video-intel 1:2.99.917+767+g7e9e92c8-1
>>  * (No nouveau, nv, or nvidia graphics)
>>  * extra/mesa 17.0.1-2
>>
>> If you've got an Xorg.0.log, go ahead and attach it for me to review...
>>
>> Jason
>> ---
>> Now instead of four in the eights place /
>> you’ve got three, ‘Cause you added one  /
>> (That is to say, eight) to the two,     /
>> But you can’t take seven from three,    /
>> So you look at the sixty-fours....
>>
>>
>>
>> On Thu, Mar 23, 2017 at 11:47 AM,  <[hidden email]> wrote:
>>>
>>> Using an xorg.conf file is the only way I know to change the behavior of
>>> xorg. Given that the display is what is not showing I cannot think of
>>> anything other than that the automatic configuration is not working.
>>>
>>> This setup worked perfectly (no stylus) before upgrading the kernel to
>>> 4.10 and Xorg to 1.19.3. I thought about downgrading xorg but that is a huge pain.
>>> Being on Arch I just did the usual pacman -Syy and pacman -Su. I thought
>>> I had screwed something up, but now I'm seeing the same behavior on a
>>> fresh install.
>>>
>>> Xmonad does not have any errors. I can replace it with twm,
>>> exec startxfce4 or exec xterm with the same effect. maximized xterm
>>> makes no difference.
>>>
>>> No matter what I do I get a black screen.  alt-ctrl-f1 brings me back to
>>> the console. When running the xterm typing 'exit' return will
>>> terminate the session.  with Xmonad shift-CMD-Q exits xmonad, etc.
>>>
>>> running xfce does give a few errors one of which is:
>>> Error opening /dev/dri/card0  permission denied
>>>
>>> I get this from xfsettings and xfwm4
>>> g_str_has_prefix: assertion 'prefix != NULL' failed
>>>
>>> This makes me wonder if there is a conflict with the two video cards the
>>> built in Intel and the nvidia.
>>>
>>> thanks,
>>>
>>> Eric
>>>
>>> Jason Gerecke <[hidden email]> writes:
>>>
>>>> Is there any particular reason you're using an xorg.conf file? That
>>>> should be completely unnecessary for most systems, and I didn't
>>>> require one when testing a MobileStudio Pro myself. (Note that I can
>>>> confirm that `Xorg :0 -configure` crashes, but it appears that's due
>>>> to a recently-introduced bug in the X server, not our driver. You
>>>> might consider filing a bug at https://bugzilla.freedesktop.org/ if
>>>> you rely on the option).
>>>>
>>>> I'm not familiar with Xmonad, but if it is starting up then I'd
>>>> suspect a problem with either: a) incorrect xmonad config, b)
>>>> incorrect xinitrc config, or c) missing software.
>>>>
>>>> As for "startx xterm", is that the literal command that you're
>>>> running? If you want to just start an xterm you'll need to provide the
>>>> full path (e.g. `startx /usr/bin/xterm`) or else startx will simply
>>>> pass "xterm" as a variable to your xinitrc script, where it will
>>>> (probably) be ignored. The pointer also won't be visible until its
>>>> moved over the xterm, so it may be advisable to use something like
>>>> `startx /usr/bin/xterm -maximized` to ensure the xterm takes up the
>>>> entire screen.
>>>>
>>>> Jason
>>>> ---
>>>> Now instead of four in the eights place /
>>>> you’ve got three, ‘Cause you added one  /
>>>> (That is to say, eight) to the two,     /
>>>> But you can’t take seven from three,    /
>>>> So you look at the sixty-fours....
>>>>
>>>>
>>>>
>>>> On Wed, Mar 22, 2017 at 5:27 PM,  <[hidden email]> wrote:
>>>>>
>>>>> One thing leads to another. I decided to upgrade my install because 4.10
>>>>> is current. I've done this many times before, but somehow I screwed
>>>>> something up.
>>>>>
>>>>> I started over from scratch, which isn't too bad from where I was. But
>>>>> now I can't get Xorg working at all. The log looks good and it looks
>>>>> like wacom input is going to work. But all I get is a black screen with
>>>>> 'startx xterm' or a simple xinitrc with xmonad.
>>>>>
>>>>> Xmonad is working sort of. The only thing that works is shift-CMD-Q to
>>>>> exit. There are no xmonad.errors.
>>>>>
>>>>> Does anyone have a working xorg.conf for this machine ?  It seems like it
>>>>> worked out of the box before.  'Xorg :0 -configure' crashes now. which
>>>>> is what it seems that I did the last time.
>>>>>
>>>>> The only errors I'm getting are unable to load module 'nouveau' and 'nv'
>>>>> plus a few from wacom invalid types, which look ok, because it does find
>>>>> the ones it needs.
>>>>>
>>>>> the 'nv' driver no longer exists from what I can tell, and nouveau isn't
>>>>> necessary for this video controller.
>>>>>
>>>>> So, I'm just hoping someone here has an xorg.conf that works for this
>>>>> machine. Suggestions welcome also.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Eric
>>>>>
>>>>> [hidden email] writes:
>>>>>
>>>>>> Hi Aaron,
>>>>>>
>>>>>> I see. Now I've just got to my kernel source in the right place. Either
>>>>>> I haven't found the right Arch doc or it's just not very easy..
>>>>>>
>>>>>> I'm missing the config files for the kernel source and modules. Argh.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>>
>>>>>>> HI Eric,
>>>>>>>
>>>>>>> If the driver version shows only "v2.00" you haven't installed the
>>>>>>> kernel driver.
>>>>>>>
>>>>>>> If you download the latest driver from
>>>>>>> https://sourceforge.net/projects/linuxwacom/files/xf86-input-wacom/input-wacom/
>>>>>>> and install it you should have a version suffix on v2.00. I realize it
>>>>>>> is confusing how our input-wacom (kernel) driver is nested inside our
>>>>>>> xf86 (X driver) folder.
>>>>>>>
>>>>>>> When I download and install input-wacom-0.34.0.tar.bz2, load and
>>>>>>> unload the driver with the commands from the link in my previous
>>>>>>> message, and then issue the command 'modinfo wacom | grep version' ,
>>>>>>> this is the output I see (granted I'm using a different distro and
>>>>>>> kernel, but the version should be the same):
>>>>>>>
>>>>>>> version:        v2.00-0.34.0
>>>>>>> srcversion:     DFB3DEC94FA89060ACBD540
>>>>>>> vermagic:       4.8.0-41-generic SMP mod_unload modversions
>>>>>>>
>>>>>>> Best,
>>>>>>> Aaron
>>>>>>>
>>>>>>> On Fri, Mar 17, 2017 at 2:06 PM,  <[hidden email]> wrote:
>>>>>>>>
>>>>>>>> Ok, I followed the instruction for building the kernel modules and
>>>>>>>> installed them.
>>>>>>>>
>>>>>>>> I also upgraded Xorg, and reinstalled the official xf86-input-wacom
>>>>>>>> package which installed 34.2-1 which matches the kernel modules I
>>>>>>>> downloaded.
>>>>>>>>
>>>>>>>> The driver version in /sys/module/wacom/version is v2.00.
>>>>>>>>
>>>>>>>> The pen/stylus still does not work.
>>>>>>>>
>>>>>>>> Is there something I can look at or try that might help understand
>>>>>>>> this ?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> Eric
>>>>>>>>
>>>>>>>> [hidden email] writes:
>>>>>>>>
>>>>>>>>> Hello Aaron,
>>>>>>>>>
>>>>>>>>> Thanks for the help.  I thought that was what I was installing when
>>>>>>>>> I installed the xf86-input-wacom-git package.
>>>>>>>>>
>>>>>>>>> https://aur.archlinux.org/packages/xf86-input-wacom-git/
>>>>>>>>>
>>>>>>>>> I've downloaded the tar ball from kernel downloads, but it has the same
>>>>>>>>> name.  So I think I'm confused about which is the kernel driver, which
>>>>>>>>> is the X11 driver and what it is that I've actually installed or not
>>>>>>>>> installed.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> Eric
>>>>>>>>>
>>>>>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>>>>>
>>>>>>>>>> Hi Eric,
>>>>>>>>>>
>>>>>>>>>> Support for MSP was added in kernel 4.10 so you'll need to install the
>>>>>>>>>> input-wacom kernel driver:
>>>>>>>>>>
>>>>>>>>>> http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>>>>>>>>>>
>>>>>>>>>> Let us know if you have any other questions.
>>>>>>>>>>
>>>>>>>>>> Best,
>>>>>>>>>> Aaron
>>>>>>>>>>
>>>>>>>>>> On Fri, Mar 17, 2017 at 10:45 AM,  <[hidden email]> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hello,
>>>>>>>>>>>
>>>>>>>>>>> I have a mobile studio pro running Arch linux.
>>>>>>>>>>>
>>>>>>>>>>> I have the xf86-input-wacom-git package installed
>>>>>>>>>>> aur/xf86-input-wacom-git 0.33.0-1 [installed: 0.34.2-1] (2) (0.07)
>>>>>>>>>>>     X.Org Wacom tablet driver (from git)
>>>>>>>>>>>
>>>>>>>>>>> Linux kernel:
>>>>>>>>>>> core/linux 4.8.13-1 (base) [installed]
>>>>>>>>>>>
>>>>>>>>>>> Xorg Server 1.18.4-1
>>>>>>>>>>>
>>>>>>>>>>> xsetwacom --list devices
>>>>>>>>>>>
>>>>>>>>>>> -- sorry it's a different computer...
>>>>>>>>>>>
>>>>>>>>>>> shows TOUCH, STYLUS, ERASER  with ids of 15, 16, and 17.
>>>>>>>>>>>
>>>>>>>>>>> Touch works fine. But the pen doesn't work at all.
>>>>>>>>>>>
>>>>>>>>>>> I've tried it krita and that doesn't work either. I would have expected
>>>>>>>>>>> it to work in the OS.
>>>>>>>>>>>
>>>>>>>>>>> I noticed on the device id doc that mobile studio pro 16 has it's
>>>>>>>>>>> version numbers crossed out.  Should this device work ?
>>>>>>>>>>>
>>>>>>>>>>> I've tried it with the old pen from my cintiq companion, and that
>>>>>>>>>>> doesn't work either.
>>>>>>>>>>>
>>>>>>>>>>> Does anyone have suggestions on how to get this working ?
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>>
>>>>>>>>>>> Eric
>>>>>>>>>>>
>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>>>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> Linuxwacom-discuss mailing list
>>>>>>>>>>> [hidden email]
>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Check out the vibrant tech community on one of the world's most
>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>> _______________________________________________
>>>>> Linuxwacom-discuss mailing list
>>>>> [hidden email]
>>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: mobile studio pro 16 ?

e.a.gebhart

Yes, I had added Option "DPI" "96 x 96" to the 10-nvidia conf file
during that run. But I have done it both ways with no changes.

At one point I tried using the nvidia generated xorg.conf.  That results
in what appears to be about 10 pixels being lit up in a row in the upper
left corner of the screen. But I removed that conf file.

Thanks for looking at this.

Eric


Jason Gerecke <[hidden email]> writes:

> Thanks for the log. It looks pretty similar to what I see on my system,
> except for the presence of a few more video drivers (though only
> 'nvidia' ends up getting used) and your system's obvious lack of
> systemd-logind. I tried installing the nvidia package to see if maybe it
> was the source of the problem, but it still seems to work fine.
>
> I do notice that your system uses slightly different monitor timings
> than mine, but if the timings were wrong I'd expect the display to go to
> sleep (and turn off the backlight) rather than just render nothing.
>
> Finally, I also see that the X server is getting a DPI value of 96 from
> somewhere. On my system it says that it can't find the screen's DPI and
> so it falls back to 75. While the DPI itself isn't going to change
> anything, it might indicate the presence of X configuration files that
> are modifying its behavior in ways not captured by the log. Do you have
> any files under /etc/X11/xorg.conf.d or have you edited any files under
> /usr/share/X11/xorg.conf.d?
>
> Jason
> ---
> Now instead of four in the eights place /
> you’ve got three, ‘Cause you added one /
> (That is to say, eight) to the two, /
> But you can’t take seven from three, /
> So you look at the sixty-fours....
>
> On 03/29/2017 06:47 AM, [hidden email] wrote:
>>
>> I'm wondering if I shouldn't start over with a fresh install again. But
>> maybe this will reveal something.  Here is my log.
>>
> [snip]
>>
>> Jason Gerecke <[hidden email]> writes:
>>
>>> I just gave Arch a whirl to see if a recent update broke something,
>>> but even after rebooting from a fresh `pacman -Syu` I don't see any
>>> problems on the MobileStudio Pro 16. Its using GDM by default, but
>>> even when I switch to multi-user.target and run `startx
>>> /usr/bin/xfce4-terminal` (I don't have the vanilla xterm installed)
>>> manually I don't see any problems. No xorg.conf file either...
>>>
>>> Notable package versions (though if you upgraded, they should be identical...):
>>>
>>>  * core/linux 4.10.4-1
>>>  * extra/xorg-server 1.19.3-1
>>>  * extra/xf86-video-fbdev 0.4.4-6
>>>  * extra/xf86-video-intel 1:2.99.917+767+g7e9e92c8-1
>>>  * (No nouveau, nv, or nvidia graphics)
>>>  * extra/mesa 17.0.1-2
>>>
>>> If you've got an Xorg.0.log, go ahead and attach it for me to review...
>>>
>>> Jason
>>> ---
>>> Now instead of four in the eights place /
>>> you’ve got three, ‘Cause you added one  /
>>> (That is to say, eight) to the two,     /
>>> But you can’t take seven from three,    /
>>> So you look at the sixty-fours....
>>>
>>>
>>>
>>> On Thu, Mar 23, 2017 at 11:47 AM,  <[hidden email]> wrote:
>>>>
>>>> Using an xorg.conf file is the only way I know to change the behavior of
>>>> xorg. Given that the display is what is not showing I cannot think of
>>>> anything other than that the automatic configuration is not working.
>>>>
>>>> This setup worked perfectly (no stylus) before upgrading the kernel to
>>>> 4.10 and Xorg to 1.19.3. I thought about downgrading xorg but that is a huge pain.
>>>> Being on Arch I just did the usual pacman -Syy and pacman -Su. I thought
>>>> I had screwed something up, but now I'm seeing the same behavior on a
>>>> fresh install.
>>>>
>>>> Xmonad does not have any errors. I can replace it with twm,
>>>> exec startxfce4 or exec xterm with the same effect. maximized xterm
>>>> makes no difference.
>>>>
>>>> No matter what I do I get a black screen.  alt-ctrl-f1 brings me back to
>>>> the console. When running the xterm typing 'exit' return will
>>>> terminate the session.  with Xmonad shift-CMD-Q exits xmonad, etc.
>>>>
>>>> running xfce does give a few errors one of which is:
>>>> Error opening /dev/dri/card0  permission denied
>>>>
>>>> I get this from xfsettings and xfwm4
>>>> g_str_has_prefix: assertion 'prefix != NULL' failed
>>>>
>>>> This makes me wonder if there is a conflict with the two video cards the
>>>> built in Intel and the nvidia.
>>>>
>>>> thanks,
>>>>
>>>> Eric
>>>>
>>>> Jason Gerecke <[hidden email]> writes:
>>>>
>>>>> Is there any particular reason you're using an xorg.conf file? That
>>>>> should be completely unnecessary for most systems, and I didn't
>>>>> require one when testing a MobileStudio Pro myself. (Note that I can
>>>>> confirm that `Xorg :0 -configure` crashes, but it appears that's due
>>>>> to a recently-introduced bug in the X server, not our driver. You
>>>>> might consider filing a bug at https://bugzilla.freedesktop.org/ if
>>>>> you rely on the option).
>>>>>
>>>>> I'm not familiar with Xmonad, but if it is starting up then I'd
>>>>> suspect a problem with either: a) incorrect xmonad config, b)
>>>>> incorrect xinitrc config, or c) missing software.
>>>>>
>>>>> As for "startx xterm", is that the literal command that you're
>>>>> running? If you want to just start an xterm you'll need to provide the
>>>>> full path (e.g. `startx /usr/bin/xterm`) or else startx will simply
>>>>> pass "xterm" as a variable to your xinitrc script, where it will
>>>>> (probably) be ignored. The pointer also won't be visible until its
>>>>> moved over the xterm, so it may be advisable to use something like
>>>>> `startx /usr/bin/xterm -maximized` to ensure the xterm takes up the
>>>>> entire screen.
>>>>>
>>>>> Jason
>>>>> ---
>>>>> Now instead of four in the eights place /
>>>>> you’ve got three, ‘Cause you added one  /
>>>>> (That is to say, eight) to the two,     /
>>>>> But you can’t take seven from three,    /
>>>>> So you look at the sixty-fours....
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Mar 22, 2017 at 5:27 PM,  <[hidden email]> wrote:
>>>>>>
>>>>>> One thing leads to another. I decided to upgrade my install because 4.10
>>>>>> is current. I've done this many times before, but somehow I screwed
>>>>>> something up.
>>>>>>
>>>>>> I started over from scratch, which isn't too bad from where I was. But
>>>>>> now I can't get Xorg working at all. The log looks good and it looks
>>>>>> like wacom input is going to work. But all I get is a black screen with
>>>>>> 'startx xterm' or a simple xinitrc with xmonad.
>>>>>>
>>>>>> Xmonad is working sort of. The only thing that works is shift-CMD-Q to
>>>>>> exit. There are no xmonad.errors.
>>>>>>
>>>>>> Does anyone have a working xorg.conf for this machine ?  It seems like it
>>>>>> worked out of the box before.  'Xorg :0 -configure' crashes now. which
>>>>>> is what it seems that I did the last time.
>>>>>>
>>>>>> The only errors I'm getting are unable to load module 'nouveau' and 'nv'
>>>>>> plus a few from wacom invalid types, which look ok, because it does find
>>>>>> the ones it needs.
>>>>>>
>>>>>> the 'nv' driver no longer exists from what I can tell, and nouveau isn't
>>>>>> necessary for this video controller.
>>>>>>
>>>>>> So, I'm just hoping someone here has an xorg.conf that works for this
>>>>>> machine. Suggestions welcome also.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Eric
>>>>>>
>>>>>> [hidden email] writes:
>>>>>>
>>>>>>> Hi Aaron,
>>>>>>>
>>>>>>> I see. Now I've just got to my kernel source in the right place. Either
>>>>>>> I haven't found the right Arch doc or it's just not very easy..
>>>>>>>
>>>>>>> I'm missing the config files for the kernel source and modules. Argh.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>>>
>>>>>>>> HI Eric,
>>>>>>>>
>>>>>>>> If the driver version shows only "v2.00" you haven't installed the
>>>>>>>> kernel driver.
>>>>>>>>
>>>>>>>> If you download the latest driver from
>>>>>>>> https://sourceforge.net/projects/linuxwacom/files/xf86-input-wacom/input-wacom/
>>>>>>>> and install it you should have a version suffix on v2.00. I realize it
>>>>>>>> is confusing how our input-wacom (kernel) driver is nested inside our
>>>>>>>> xf86 (X driver) folder.
>>>>>>>>
>>>>>>>> When I download and install input-wacom-0.34.0.tar.bz2, load and
>>>>>>>> unload the driver with the commands from the link in my previous
>>>>>>>> message, and then issue the command 'modinfo wacom | grep version' ,
>>>>>>>> this is the output I see (granted I'm using a different distro and
>>>>>>>> kernel, but the version should be the same):
>>>>>>>>
>>>>>>>> version:        v2.00-0.34.0
>>>>>>>> srcversion:     DFB3DEC94FA89060ACBD540
>>>>>>>> vermagic:       4.8.0-41-generic SMP mod_unload modversions
>>>>>>>>
>>>>>>>> Best,
>>>>>>>> Aaron
>>>>>>>>
>>>>>>>> On Fri, Mar 17, 2017 at 2:06 PM,  <[hidden email]> wrote:
>>>>>>>>>
>>>>>>>>> Ok, I followed the instruction for building the kernel modules and
>>>>>>>>> installed them.
>>>>>>>>>
>>>>>>>>> I also upgraded Xorg, and reinstalled the official xf86-input-wacom
>>>>>>>>> package which installed 34.2-1 which matches the kernel modules I
>>>>>>>>> downloaded.
>>>>>>>>>
>>>>>>>>> The driver version in /sys/module/wacom/version is v2.00.
>>>>>>>>>
>>>>>>>>> The pen/stylus still does not work.
>>>>>>>>>
>>>>>>>>> Is there something I can look at or try that might help understand
>>>>>>>>> this ?
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> Eric
>>>>>>>>>
>>>>>>>>> [hidden email] writes:
>>>>>>>>>
>>>>>>>>>> Hello Aaron,
>>>>>>>>>>
>>>>>>>>>> Thanks for the help.  I thought that was what I was installing when
>>>>>>>>>> I installed the xf86-input-wacom-git package.
>>>>>>>>>>
>>>>>>>>>> https://aur.archlinux.org/packages/xf86-input-wacom-git/
>>>>>>>>>>
>>>>>>>>>> I've downloaded the tar ball from kernel downloads, but it has the same
>>>>>>>>>> name.  So I think I'm confused about which is the kernel driver, which
>>>>>>>>>> is the X11 driver and what it is that I've actually installed or not
>>>>>>>>>> installed.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>>
>>>>>>>>>> Eric
>>>>>>>>>>
>>>>>>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>>>>>>
>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>
>>>>>>>>>>> Support for MSP was added in kernel 4.10 so you'll need to install the
>>>>>>>>>>> input-wacom kernel driver:
>>>>>>>>>>>
>>>>>>>>>>> http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>>>>>>>>>>>
>>>>>>>>>>> Let us know if you have any other questions.
>>>>>>>>>>>
>>>>>>>>>>> Best,
>>>>>>>>>>> Aaron
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Mar 17, 2017 at 10:45 AM,  <[hidden email]> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hello,
>>>>>>>>>>>>
>>>>>>>>>>>> I have a mobile studio pro running Arch linux.
>>>>>>>>>>>>
>>>>>>>>>>>> I have the xf86-input-wacom-git package installed
>>>>>>>>>>>> aur/xf86-input-wacom-git 0.33.0-1 [installed: 0.34.2-1] (2) (0.07)
>>>>>>>>>>>>     X.Org Wacom tablet driver (from git)
>>>>>>>>>>>>
>>>>>>>>>>>> Linux kernel:
>>>>>>>>>>>> core/linux 4.8.13-1 (base) [installed]
>>>>>>>>>>>>
>>>>>>>>>>>> Xorg Server 1.18.4-1
>>>>>>>>>>>>
>>>>>>>>>>>> xsetwacom --list devices
>>>>>>>>>>>>
>>>>>>>>>>>> -- sorry it's a different computer...
>>>>>>>>>>>>
>>>>>>>>>>>> shows TOUCH, STYLUS, ERASER  with ids of 15, 16, and 17.
>>>>>>>>>>>>
>>>>>>>>>>>> Touch works fine. But the pen doesn't work at all.
>>>>>>>>>>>>
>>>>>>>>>>>> I've tried it krita and that doesn't work either. I would have expected
>>>>>>>>>>>> it to work in the OS.
>>>>>>>>>>>>
>>>>>>>>>>>> I noticed on the device id doc that mobile studio pro 16 has it's
>>>>>>>>>>>> version numbers crossed out.  Should this device work ?
>>>>>>>>>>>>
>>>>>>>>>>>> I've tried it with the old pen from my cintiq companion, and that
>>>>>>>>>>>> doesn't work either.
>>>>>>>>>>>>
>>>>>>>>>>>> Does anyone have suggestions on how to get this working ?
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>
>>>>>>>>>>>> Eric
>>>>>>>>>>>>
>>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>>>>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> Linuxwacom-discuss mailing list
>>>>>>>>>>>> [hidden email]
>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>> _______________________________________________
>>>>>> Linuxwacom-discuss mailing list
>>>>>> [hidden email]
>>>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: mobile studio pro 16 ?

Jason Gerecke
Huh, that's an interesting observation. Lets try removing the nVidia
graphics drivers (`pacman -Rs nvidia nvidia-utils`) and see if the
open-source drivers work differently. If there's no change, figure out
what package installed the legacy nv driver (`pacman -Qo
/usr/lib/xorg/modules/drivers/nv_drv.so` should give its name) and
remove it too. If that *still* doesn't work, remove the
xf86-video-nouveau package as well (which should hopefully have X try to
use the Intel drivers).

Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one /
(That is to say, eight) to the two, /
But you can’t take seven from three, /
So you look at the sixty-fours....

On 03/29/2017 04:00 PM, [hidden email] wrote:

>
> Yes, I had added Option "DPI" "96 x 96" to the 10-nvidia conf file
> during that run. But I have done it both ways with no changes.
>
> At one point I tried using the nvidia generated xorg.conf.  That results
> in what appears to be about 10 pixels being lit up in a row in the upper
> left corner of the screen. But I removed that conf file.
>
> Thanks for looking at this.
>
> Eric
>
>
> Jason Gerecke <[hidden email]> writes:
>
>> Thanks for the log. It looks pretty similar to what I see on my system,
>> except for the presence of a few more video drivers (though only
>> 'nvidia' ends up getting used) and your system's obvious lack of
>> systemd-logind. I tried installing the nvidia package to see if maybe it
>> was the source of the problem, but it still seems to work fine.
>>
>> I do notice that your system uses slightly different monitor timings
>> than mine, but if the timings were wrong I'd expect the display to go to
>> sleep (and turn off the backlight) rather than just render nothing.
>>
>> Finally, I also see that the X server is getting a DPI value of 96 from
>> somewhere. On my system it says that it can't find the screen's DPI and
>> so it falls back to 75. While the DPI itself isn't going to change
>> anything, it might indicate the presence of X configuration files that
>> are modifying its behavior in ways not captured by the log. Do you have
>> any files under /etc/X11/xorg.conf.d or have you edited any files under
>> /usr/share/X11/xorg.conf.d?
>>
>> Jason
>> ---
>> Now instead of four in the eights place /
>> you’ve got three, ‘Cause you added one /
>> (That is to say, eight) to the two, /
>> But you can’t take seven from three, /
>> So you look at the sixty-fours....
>>
>> On 03/29/2017 06:47 AM, [hidden email] wrote:
>>>
>>> I'm wondering if I shouldn't start over with a fresh install again. But
>>> maybe this will reveal something.  Here is my log.
>>>
>> [snip]
>>>
>>> Jason Gerecke <[hidden email]> writes:
>>>
>>>> I just gave Arch a whirl to see if a recent update broke something,
>>>> but even after rebooting from a fresh `pacman -Syu` I don't see any
>>>> problems on the MobileStudio Pro 16. Its using GDM by default, but
>>>> even when I switch to multi-user.target and run `startx
>>>> /usr/bin/xfce4-terminal` (I don't have the vanilla xterm installed)
>>>> manually I don't see any problems. No xorg.conf file either...
>>>>
>>>> Notable package versions (though if you upgraded, they should be identical...):
>>>>
>>>>  * core/linux 4.10.4-1
>>>>  * extra/xorg-server 1.19.3-1
>>>>  * extra/xf86-video-fbdev 0.4.4-6
>>>>  * extra/xf86-video-intel 1:2.99.917+767+g7e9e92c8-1
>>>>  * (No nouveau, nv, or nvidia graphics)
>>>>  * extra/mesa 17.0.1-2
>>>>
>>>> If you've got an Xorg.0.log, go ahead and attach it for me to review...
>>>>
>>>> Jason
>>>> ---
>>>> Now instead of four in the eights place /
>>>> you’ve got three, ‘Cause you added one  /
>>>> (That is to say, eight) to the two,     /
>>>> But you can’t take seven from three,    /
>>>> So you look at the sixty-fours....
>>>>
>>>>
>>>>
>>>> On Thu, Mar 23, 2017 at 11:47 AM,  <[hidden email]> wrote:
>>>>>
>>>>> Using an xorg.conf file is the only way I know to change the behavior of
>>>>> xorg. Given that the display is what is not showing I cannot think of
>>>>> anything other than that the automatic configuration is not working.
>>>>>
>>>>> This setup worked perfectly (no stylus) before upgrading the kernel to
>>>>> 4.10 and Xorg to 1.19.3. I thought about downgrading xorg but that is a huge pain.
>>>>> Being on Arch I just did the usual pacman -Syy and pacman -Su. I thought
>>>>> I had screwed something up, but now I'm seeing the same behavior on a
>>>>> fresh install.
>>>>>
>>>>> Xmonad does not have any errors. I can replace it with twm,
>>>>> exec startxfce4 or exec xterm with the same effect. maximized xterm
>>>>> makes no difference.
>>>>>
>>>>> No matter what I do I get a black screen.  alt-ctrl-f1 brings me back to
>>>>> the console. When running the xterm typing 'exit' return will
>>>>> terminate the session.  with Xmonad shift-CMD-Q exits xmonad, etc.
>>>>>
>>>>> running xfce does give a few errors one of which is:
>>>>> Error opening /dev/dri/card0  permission denied
>>>>>
>>>>> I get this from xfsettings and xfwm4
>>>>> g_str_has_prefix: assertion 'prefix != NULL' failed
>>>>>
>>>>> This makes me wonder if there is a conflict with the two video cards the
>>>>> built in Intel and the nvidia.
>>>>>
>>>>> thanks,
>>>>>
>>>>> Eric
>>>>>
>>>>> Jason Gerecke <[hidden email]> writes:
>>>>>
>>>>>> Is there any particular reason you're using an xorg.conf file? That
>>>>>> should be completely unnecessary for most systems, and I didn't
>>>>>> require one when testing a MobileStudio Pro myself. (Note that I can
>>>>>> confirm that `Xorg :0 -configure` crashes, but it appears that's due
>>>>>> to a recently-introduced bug in the X server, not our driver. You
>>>>>> might consider filing a bug at https://bugzilla.freedesktop.org/ if
>>>>>> you rely on the option).
>>>>>>
>>>>>> I'm not familiar with Xmonad, but if it is starting up then I'd
>>>>>> suspect a problem with either: a) incorrect xmonad config, b)
>>>>>> incorrect xinitrc config, or c) missing software.
>>>>>>
>>>>>> As for "startx xterm", is that the literal command that you're
>>>>>> running? If you want to just start an xterm you'll need to provide the
>>>>>> full path (e.g. `startx /usr/bin/xterm`) or else startx will simply
>>>>>> pass "xterm" as a variable to your xinitrc script, where it will
>>>>>> (probably) be ignored. The pointer also won't be visible until its
>>>>>> moved over the xterm, so it may be advisable to use something like
>>>>>> `startx /usr/bin/xterm -maximized` to ensure the xterm takes up the
>>>>>> entire screen.
>>>>>>
>>>>>> Jason
>>>>>> ---
>>>>>> Now instead of four in the eights place /
>>>>>> you’ve got three, ‘Cause you added one  /
>>>>>> (That is to say, eight) to the two,     /
>>>>>> But you can’t take seven from three,    /
>>>>>> So you look at the sixty-fours....
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 22, 2017 at 5:27 PM,  <[hidden email]> wrote:
>>>>>>>
>>>>>>> One thing leads to another. I decided to upgrade my install because 4.10
>>>>>>> is current. I've done this many times before, but somehow I screwed
>>>>>>> something up.
>>>>>>>
>>>>>>> I started over from scratch, which isn't too bad from where I was. But
>>>>>>> now I can't get Xorg working at all. The log looks good and it looks
>>>>>>> like wacom input is going to work. But all I get is a black screen with
>>>>>>> 'startx xterm' or a simple xinitrc with xmonad.
>>>>>>>
>>>>>>> Xmonad is working sort of. The only thing that works is shift-CMD-Q to
>>>>>>> exit. There are no xmonad.errors.
>>>>>>>
>>>>>>> Does anyone have a working xorg.conf for this machine ?  It seems like it
>>>>>>> worked out of the box before.  'Xorg :0 -configure' crashes now. which
>>>>>>> is what it seems that I did the last time.
>>>>>>>
>>>>>>> The only errors I'm getting are unable to load module 'nouveau' and 'nv'
>>>>>>> plus a few from wacom invalid types, which look ok, because it does find
>>>>>>> the ones it needs.
>>>>>>>
>>>>>>> the 'nv' driver no longer exists from what I can tell, and nouveau isn't
>>>>>>> necessary for this video controller.
>>>>>>>
>>>>>>> So, I'm just hoping someone here has an xorg.conf that works for this
>>>>>>> machine. Suggestions welcome also.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Eric
>>>>>>>
>>>>>>> [hidden email] writes:
>>>>>>>
>>>>>>>> Hi Aaron,
>>>>>>>>
>>>>>>>> I see. Now I've just got to my kernel source in the right place. Either
>>>>>>>> I haven't found the right Arch doc or it's just not very easy..
>>>>>>>>
>>>>>>>> I'm missing the config files for the kernel source and modules. Argh.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>>>>
>>>>>>>>> HI Eric,
>>>>>>>>>
>>>>>>>>> If the driver version shows only "v2.00" you haven't installed the
>>>>>>>>> kernel driver.
>>>>>>>>>
>>>>>>>>> If you download the latest driver from
>>>>>>>>> https://sourceforge.net/projects/linuxwacom/files/xf86-input-wacom/input-wacom/
>>>>>>>>> and install it you should have a version suffix on v2.00. I realize it
>>>>>>>>> is confusing how our input-wacom (kernel) driver is nested inside our
>>>>>>>>> xf86 (X driver) folder.
>>>>>>>>>
>>>>>>>>> When I download and install input-wacom-0.34.0.tar.bz2, load and
>>>>>>>>> unload the driver with the commands from the link in my previous
>>>>>>>>> message, and then issue the command 'modinfo wacom | grep version' ,
>>>>>>>>> this is the output I see (granted I'm using a different distro and
>>>>>>>>> kernel, but the version should be the same):
>>>>>>>>>
>>>>>>>>> version:        v2.00-0.34.0
>>>>>>>>> srcversion:     DFB3DEC94FA89060ACBD540
>>>>>>>>> vermagic:       4.8.0-41-generic SMP mod_unload modversions
>>>>>>>>>
>>>>>>>>> Best,
>>>>>>>>> Aaron
>>>>>>>>>
>>>>>>>>> On Fri, Mar 17, 2017 at 2:06 PM,  <[hidden email]> wrote:
>>>>>>>>>>
>>>>>>>>>> Ok, I followed the instruction for building the kernel modules and
>>>>>>>>>> installed them.
>>>>>>>>>>
>>>>>>>>>> I also upgraded Xorg, and reinstalled the official xf86-input-wacom
>>>>>>>>>> package which installed 34.2-1 which matches the kernel modules I
>>>>>>>>>> downloaded.
>>>>>>>>>>
>>>>>>>>>> The driver version in /sys/module/wacom/version is v2.00.
>>>>>>>>>>
>>>>>>>>>> The pen/stylus still does not work.
>>>>>>>>>>
>>>>>>>>>> Is there something I can look at or try that might help understand
>>>>>>>>>> this ?
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>>
>>>>>>>>>> Eric
>>>>>>>>>>
>>>>>>>>>> [hidden email] writes:
>>>>>>>>>>
>>>>>>>>>>> Hello Aaron,
>>>>>>>>>>>
>>>>>>>>>>> Thanks for the help.  I thought that was what I was installing when
>>>>>>>>>>> I installed the xf86-input-wacom-git package.
>>>>>>>>>>>
>>>>>>>>>>> https://aur.archlinux.org/packages/xf86-input-wacom-git/
>>>>>>>>>>>
>>>>>>>>>>> I've downloaded the tar ball from kernel downloads, but it has the same
>>>>>>>>>>> name.  So I think I'm confused about which is the kernel driver, which
>>>>>>>>>>> is the X11 driver and what it is that I've actually installed or not
>>>>>>>>>>> installed.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>>
>>>>>>>>>>> Eric
>>>>>>>>>>>
>>>>>>>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>>>>>>>
>>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>>
>>>>>>>>>>>> Support for MSP was added in kernel 4.10 so you'll need to install the
>>>>>>>>>>>> input-wacom kernel driver:
>>>>>>>>>>>>
>>>>>>>>>>>> http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>>>>>>>>>>>>
>>>>>>>>>>>> Let us know if you have any other questions.
>>>>>>>>>>>>
>>>>>>>>>>>> Best,
>>>>>>>>>>>> Aaron
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Mar 17, 2017 at 10:45 AM,  <[hidden email]> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hello,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I have a mobile studio pro running Arch linux.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I have the xf86-input-wacom-git package installed
>>>>>>>>>>>>> aur/xf86-input-wacom-git 0.33.0-1 [installed: 0.34.2-1] (2) (0.07)
>>>>>>>>>>>>>     X.Org Wacom tablet driver (from git)
>>>>>>>>>>>>>
>>>>>>>>>>>>> Linux kernel:
>>>>>>>>>>>>> core/linux 4.8.13-1 (base) [installed]
>>>>>>>>>>>>>
>>>>>>>>>>>>> Xorg Server 1.18.4-1
>>>>>>>>>>>>>
>>>>>>>>>>>>> xsetwacom --list devices
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- sorry it's a different computer...
>>>>>>>>>>>>>
>>>>>>>>>>>>> shows TOUCH, STYLUS, ERASER  with ids of 15, 16, and 17.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Touch works fine. But the pen doesn't work at all.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I've tried it krita and that doesn't work either. I would have expected
>>>>>>>>>>>>> it to work in the OS.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I noticed on the device id doc that mobile studio pro 16 has it's
>>>>>>>>>>>>> version numbers crossed out.  Should this device work ?
>>>>>>>>>>>>>
>>>>>>>>>>>>> I've tried it with the old pen from my cintiq companion, and that
>>>>>>>>>>>>> doesn't work either.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Does anyone have suggestions on how to get this working ?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Eric
>>>>>>>>>>>>>
>>>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>>>>>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> Linuxwacom-discuss mailing list
>>>>>>>>>>>>> [hidden email]
>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>>> _______________________________________________
>>>>>>> Linuxwacom-discuss mailing list
>>>>>>> [hidden email]
>>>>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: mobile studio pro 16 ?

Jason Gerecke
Oh, another quick question while I'm thinking about it:

Do you have the 'libglvnd' package installed, or are you using another
package to provide libgl?

On 03/29/2017 04:15 PM, Jason Gerecke wrote:

> Huh, that's an interesting observation. Lets try removing the nVidia
> graphics drivers (`pacman -Rs nvidia nvidia-utils`) and see if the
> open-source drivers work differently. If there's no change, figure out
> what package installed the legacy nv driver (`pacman -Qo
> /usr/lib/xorg/modules/drivers/nv_drv.so` should give its name) and
> remove it too. If that *still* doesn't work, remove the
> xf86-video-nouveau package as well (which should hopefully have X try to
> use the Intel drivers).
>
> Jason
> ---
> Now instead of four in the eights place /
> you’ve got three, ‘Cause you added one /
> (That is to say, eight) to the two, /
> But you can’t take seven from three, /
> So you look at the sixty-fours....
>
> On 03/29/2017 04:00 PM, [hidden email] wrote:
>>
>> Yes, I had added Option "DPI" "96 x 96" to the 10-nvidia conf file
>> during that run. But I have done it both ways with no changes.
>>
>> At one point I tried using the nvidia generated xorg.conf.  That results
>> in what appears to be about 10 pixels being lit up in a row in the upper
>> left corner of the screen. But I removed that conf file.
>>
>> Thanks for looking at this.
>>
>> Eric
>>
>>
>> Jason Gerecke <[hidden email]> writes:
>>
>>> Thanks for the log. It looks pretty similar to what I see on my system,
>>> except for the presence of a few more video drivers (though only
>>> 'nvidia' ends up getting used) and your system's obvious lack of
>>> systemd-logind. I tried installing the nvidia package to see if maybe it
>>> was the source of the problem, but it still seems to work fine.
>>>
>>> I do notice that your system uses slightly different monitor timings
>>> than mine, but if the timings were wrong I'd expect the display to go to
>>> sleep (and turn off the backlight) rather than just render nothing.
>>>
>>> Finally, I also see that the X server is getting a DPI value of 96 from
>>> somewhere. On my system it says that it can't find the screen's DPI and
>>> so it falls back to 75. While the DPI itself isn't going to change
>>> anything, it might indicate the presence of X configuration files that
>>> are modifying its behavior in ways not captured by the log. Do you have
>>> any files under /etc/X11/xorg.conf.d or have you edited any files under
>>> /usr/share/X11/xorg.conf.d?
>>>
>>> Jason
>>> ---
>>> Now instead of four in the eights place /
>>> you’ve got three, ‘Cause you added one /
>>> (That is to say, eight) to the two, /
>>> But you can’t take seven from three, /
>>> So you look at the sixty-fours....
>>>
>>> On 03/29/2017 06:47 AM, [hidden email] wrote:
>>>>
>>>> I'm wondering if I shouldn't start over with a fresh install again. But
>>>> maybe this will reveal something.  Here is my log.
>>>>
>>> [snip]
>>>>
>>>> Jason Gerecke <[hidden email]> writes:
>>>>
>>>>> I just gave Arch a whirl to see if a recent update broke something,
>>>>> but even after rebooting from a fresh `pacman -Syu` I don't see any
>>>>> problems on the MobileStudio Pro 16. Its using GDM by default, but
>>>>> even when I switch to multi-user.target and run `startx
>>>>> /usr/bin/xfce4-terminal` (I don't have the vanilla xterm installed)
>>>>> manually I don't see any problems. No xorg.conf file either...
>>>>>
>>>>> Notable package versions (though if you upgraded, they should be identical...):
>>>>>
>>>>>  * core/linux 4.10.4-1
>>>>>  * extra/xorg-server 1.19.3-1
>>>>>  * extra/xf86-video-fbdev 0.4.4-6
>>>>>  * extra/xf86-video-intel 1:2.99.917+767+g7e9e92c8-1
>>>>>  * (No nouveau, nv, or nvidia graphics)
>>>>>  * extra/mesa 17.0.1-2
>>>>>
>>>>> If you've got an Xorg.0.log, go ahead and attach it for me to review...
>>>>>
>>>>> Jason
>>>>> ---
>>>>> Now instead of four in the eights place /
>>>>> you’ve got three, ‘Cause you added one  /
>>>>> (That is to say, eight) to the two,     /
>>>>> But you can’t take seven from three,    /
>>>>> So you look at the sixty-fours....
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Mar 23, 2017 at 11:47 AM,  <[hidden email]> wrote:
>>>>>>
>>>>>> Using an xorg.conf file is the only way I know to change the behavior of
>>>>>> xorg. Given that the display is what is not showing I cannot think of
>>>>>> anything other than that the automatic configuration is not working.
>>>>>>
>>>>>> This setup worked perfectly (no stylus) before upgrading the kernel to
>>>>>> 4.10 and Xorg to 1.19.3. I thought about downgrading xorg but that is a huge pain.
>>>>>> Being on Arch I just did the usual pacman -Syy and pacman -Su. I thought
>>>>>> I had screwed something up, but now I'm seeing the same behavior on a
>>>>>> fresh install.
>>>>>>
>>>>>> Xmonad does not have any errors. I can replace it with twm,
>>>>>> exec startxfce4 or exec xterm with the same effect. maximized xterm
>>>>>> makes no difference.
>>>>>>
>>>>>> No matter what I do I get a black screen.  alt-ctrl-f1 brings me back to
>>>>>> the console. When running the xterm typing 'exit' return will
>>>>>> terminate the session.  with Xmonad shift-CMD-Q exits xmonad, etc.
>>>>>>
>>>>>> running xfce does give a few errors one of which is:
>>>>>> Error opening /dev/dri/card0  permission denied
>>>>>>
>>>>>> I get this from xfsettings and xfwm4
>>>>>> g_str_has_prefix: assertion 'prefix != NULL' failed
>>>>>>
>>>>>> This makes me wonder if there is a conflict with the two video cards the
>>>>>> built in Intel and the nvidia.
>>>>>>
>>>>>> thanks,
>>>>>>
>>>>>> Eric
>>>>>>
>>>>>> Jason Gerecke <[hidden email]> writes:
>>>>>>
>>>>>>> Is there any particular reason you're using an xorg.conf file? That
>>>>>>> should be completely unnecessary for most systems, and I didn't
>>>>>>> require one when testing a MobileStudio Pro myself. (Note that I can
>>>>>>> confirm that `Xorg :0 -configure` crashes, but it appears that's due
>>>>>>> to a recently-introduced bug in the X server, not our driver. You
>>>>>>> might consider filing a bug at https://bugzilla.freedesktop.org/ if
>>>>>>> you rely on the option).
>>>>>>>
>>>>>>> I'm not familiar with Xmonad, but if it is starting up then I'd
>>>>>>> suspect a problem with either: a) incorrect xmonad config, b)
>>>>>>> incorrect xinitrc config, or c) missing software.
>>>>>>>
>>>>>>> As for "startx xterm", is that the literal command that you're
>>>>>>> running? If you want to just start an xterm you'll need to provide the
>>>>>>> full path (e.g. `startx /usr/bin/xterm`) or else startx will simply
>>>>>>> pass "xterm" as a variable to your xinitrc script, where it will
>>>>>>> (probably) be ignored. The pointer also won't be visible until its
>>>>>>> moved over the xterm, so it may be advisable to use something like
>>>>>>> `startx /usr/bin/xterm -maximized` to ensure the xterm takes up the
>>>>>>> entire screen.
>>>>>>>
>>>>>>> Jason
>>>>>>> ---
>>>>>>> Now instead of four in the eights place /
>>>>>>> you’ve got three, ‘Cause you added one  /
>>>>>>> (That is to say, eight) to the two,     /
>>>>>>> But you can’t take seven from three,    /
>>>>>>> So you look at the sixty-fours....
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Mar 22, 2017 at 5:27 PM,  <[hidden email]> wrote:
>>>>>>>>
>>>>>>>> One thing leads to another. I decided to upgrade my install because 4.10
>>>>>>>> is current. I've done this many times before, but somehow I screwed
>>>>>>>> something up.
>>>>>>>>
>>>>>>>> I started over from scratch, which isn't too bad from where I was. But
>>>>>>>> now I can't get Xorg working at all. The log looks good and it looks
>>>>>>>> like wacom input is going to work. But all I get is a black screen with
>>>>>>>> 'startx xterm' or a simple xinitrc with xmonad.
>>>>>>>>
>>>>>>>> Xmonad is working sort of. The only thing that works is shift-CMD-Q to
>>>>>>>> exit. There are no xmonad.errors.
>>>>>>>>
>>>>>>>> Does anyone have a working xorg.conf for this machine ?  It seems like it
>>>>>>>> worked out of the box before.  'Xorg :0 -configure' crashes now. which
>>>>>>>> is what it seems that I did the last time.
>>>>>>>>
>>>>>>>> The only errors I'm getting are unable to load module 'nouveau' and 'nv'
>>>>>>>> plus a few from wacom invalid types, which look ok, because it does find
>>>>>>>> the ones it needs.
>>>>>>>>
>>>>>>>> the 'nv' driver no longer exists from what I can tell, and nouveau isn't
>>>>>>>> necessary for this video controller.
>>>>>>>>
>>>>>>>> So, I'm just hoping someone here has an xorg.conf that works for this
>>>>>>>> machine. Suggestions welcome also.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> Eric
>>>>>>>>
>>>>>>>> [hidden email] writes:
>>>>>>>>
>>>>>>>>> Hi Aaron,
>>>>>>>>>
>>>>>>>>> I see. Now I've just got to my kernel source in the right place. Either
>>>>>>>>> I haven't found the right Arch doc or it's just not very easy..
>>>>>>>>>
>>>>>>>>> I'm missing the config files for the kernel source and modules. Argh.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>>>>>
>>>>>>>>>> HI Eric,
>>>>>>>>>>
>>>>>>>>>> If the driver version shows only "v2.00" you haven't installed the
>>>>>>>>>> kernel driver.
>>>>>>>>>>
>>>>>>>>>> If you download the latest driver from
>>>>>>>>>> https://sourceforge.net/projects/linuxwacom/files/xf86-input-wacom/input-wacom/
>>>>>>>>>> and install it you should have a version suffix on v2.00. I realize it
>>>>>>>>>> is confusing how our input-wacom (kernel) driver is nested inside our
>>>>>>>>>> xf86 (X driver) folder.
>>>>>>>>>>
>>>>>>>>>> When I download and install input-wacom-0.34.0.tar.bz2, load and
>>>>>>>>>> unload the driver with the commands from the link in my previous
>>>>>>>>>> message, and then issue the command 'modinfo wacom | grep version' ,
>>>>>>>>>> this is the output I see (granted I'm using a different distro and
>>>>>>>>>> kernel, but the version should be the same):
>>>>>>>>>>
>>>>>>>>>> version:        v2.00-0.34.0
>>>>>>>>>> srcversion:     DFB3DEC94FA89060ACBD540
>>>>>>>>>> vermagic:       4.8.0-41-generic SMP mod_unload modversions
>>>>>>>>>>
>>>>>>>>>> Best,
>>>>>>>>>> Aaron
>>>>>>>>>>
>>>>>>>>>> On Fri, Mar 17, 2017 at 2:06 PM,  <[hidden email]> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Ok, I followed the instruction for building the kernel modules and
>>>>>>>>>>> installed them.
>>>>>>>>>>>
>>>>>>>>>>> I also upgraded Xorg, and reinstalled the official xf86-input-wacom
>>>>>>>>>>> package which installed 34.2-1 which matches the kernel modules I
>>>>>>>>>>> downloaded.
>>>>>>>>>>>
>>>>>>>>>>> The driver version in /sys/module/wacom/version is v2.00.
>>>>>>>>>>>
>>>>>>>>>>> The pen/stylus still does not work.
>>>>>>>>>>>
>>>>>>>>>>> Is there something I can look at or try that might help understand
>>>>>>>>>>> this ?
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>>
>>>>>>>>>>> Eric
>>>>>>>>>>>
>>>>>>>>>>> [hidden email] writes:
>>>>>>>>>>>
>>>>>>>>>>>> Hello Aaron,
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks for the help.  I thought that was what I was installing when
>>>>>>>>>>>> I installed the xf86-input-wacom-git package.
>>>>>>>>>>>>
>>>>>>>>>>>> https://aur.archlinux.org/packages/xf86-input-wacom-git/
>>>>>>>>>>>>
>>>>>>>>>>>> I've downloaded the tar ball from kernel downloads, but it has the same
>>>>>>>>>>>> name.  So I think I'm confused about which is the kernel driver, which
>>>>>>>>>>>> is the X11 driver and what it is that I've actually installed or not
>>>>>>>>>>>> installed.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>
>>>>>>>>>>>> Eric
>>>>>>>>>>>>
>>>>>>>>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Support for MSP was added in kernel 4.10 so you'll need to install the
>>>>>>>>>>>>> input-wacom kernel driver:
>>>>>>>>>>>>>
>>>>>>>>>>>>> http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>>>>>>>>>>>>>
>>>>>>>>>>>>> Let us know if you have any other questions.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Best,
>>>>>>>>>>>>> Aaron
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Mar 17, 2017 at 10:45 AM,  <[hidden email]> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hello,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have a mobile studio pro running Arch linux.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have the xf86-input-wacom-git package installed
>>>>>>>>>>>>>> aur/xf86-input-wacom-git 0.33.0-1 [installed: 0.34.2-1] (2) (0.07)
>>>>>>>>>>>>>>     X.Org Wacom tablet driver (from git)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Linux kernel:
>>>>>>>>>>>>>> core/linux 4.8.13-1 (base) [installed]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Xorg Server 1.18.4-1
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> xsetwacom --list devices
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> -- sorry it's a different computer...
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> shows TOUCH, STYLUS, ERASER  with ids of 15, 16, and 17.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Touch works fine. But the pen doesn't work at all.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I've tried it krita and that doesn't work either. I would have expected
>>>>>>>>>>>>>> it to work in the OS.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I noticed on the device id doc that mobile studio pro 16 has it's
>>>>>>>>>>>>>> version numbers crossed out.  Should this device work ?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I've tried it with the old pen from my cintiq companion, and that
>>>>>>>>>>>>>> doesn't work either.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Does anyone have suggestions on how to get this working ?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Eric
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>>>>>>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> Linuxwacom-discuss mailing list
>>>>>>>>>>>>>> [hidden email]
>>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>>>> _______________________________________________
>>>>>>>> Linuxwacom-discuss mailing list
>>>>>>>> [hidden email]
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: mobile studio pro 16 ?

e.a.gebhart
In reply to this post by Jason Gerecke

The display does seem to go to sleep. the backlight is on for a second
or two but then it goes black.

I also deleted the DPI line, with no real changes to report other than
the default 75 x 75 is now being used.

Eric

Jason Gerecke <[hidden email]> writes:

> Thanks for the log. It looks pretty similar to what I see on my system,
> except for the presence of a few more video drivers (though only
> 'nvidia' ends up getting used) and your system's obvious lack of
> systemd-logind. I tried installing the nvidia package to see if maybe it
> was the source of the problem, but it still seems to work fine.
>
> I do notice that your system uses slightly different monitor timings
> than mine, but if the timings were wrong I'd expect the display to go to
> sleep (and turn off the backlight) rather than just render nothing.
>
> Finally, I also see that the X server is getting a DPI value of 96 from
> somewhere. On my system it says that it can't find the screen's DPI and
> so it falls back to 75. While the DPI itself isn't going to change
> anything, it might indicate the presence of X configuration files that
> are modifying its behavior in ways not captured by the log. Do you have
> any files under /etc/X11/xorg.conf.d or have you edited any files under
> /usr/share/X11/xorg.conf.d?
>
> Jason
> ---
> Now instead of four in the eights place /
> you’ve got three, ‘Cause you added one /
> (That is to say, eight) to the two, /
> But you can’t take seven from three, /
> So you look at the sixty-fours....
>
> On 03/29/2017 06:47 AM, [hidden email] wrote:
>>
>> I'm wondering if I shouldn't start over with a fresh install again. But
>> maybe this will reveal something.  Here is my log.
>>
> [snip]
>>
>> Jason Gerecke <[hidden email]> writes:
>>
>>> I just gave Arch a whirl to see if a recent update broke something,
>>> but even after rebooting from a fresh `pacman -Syu` I don't see any
>>> problems on the MobileStudio Pro 16. Its using GDM by default, but
>>> even when I switch to multi-user.target and run `startx
>>> /usr/bin/xfce4-terminal` (I don't have the vanilla xterm installed)
>>> manually I don't see any problems. No xorg.conf file either...
>>>
>>> Notable package versions (though if you upgraded, they should be identical...):
>>>
>>>  * core/linux 4.10.4-1
>>>  * extra/xorg-server 1.19.3-1
>>>  * extra/xf86-video-fbdev 0.4.4-6
>>>  * extra/xf86-video-intel 1:2.99.917+767+g7e9e92c8-1
>>>  * (No nouveau, nv, or nvidia graphics)
>>>  * extra/mesa 17.0.1-2
>>>
>>> If you've got an Xorg.0.log, go ahead and attach it for me to review...
>>>
>>> Jason
>>> ---
>>> Now instead of four in the eights place /
>>> you’ve got three, ‘Cause you added one  /
>>> (That is to say, eight) to the two,     /
>>> But you can’t take seven from three,    /
>>> So you look at the sixty-fours....
>>>
>>>
>>>
>>> On Thu, Mar 23, 2017 at 11:47 AM,  <[hidden email]> wrote:
>>>>
>>>> Using an xorg.conf file is the only way I know to change the behavior of
>>>> xorg. Given that the display is what is not showing I cannot think of
>>>> anything other than that the automatic configuration is not working.
>>>>
>>>> This setup worked perfectly (no stylus) before upgrading the kernel to
>>>> 4.10 and Xorg to 1.19.3. I thought about downgrading xorg but that is a huge pain.
>>>> Being on Arch I just did the usual pacman -Syy and pacman -Su. I thought
>>>> I had screwed something up, but now I'm seeing the same behavior on a
>>>> fresh install.
>>>>
>>>> Xmonad does not have any errors. I can replace it with twm,
>>>> exec startxfce4 or exec xterm with the same effect. maximized xterm
>>>> makes no difference.
>>>>
>>>> No matter what I do I get a black screen.  alt-ctrl-f1 brings me back to
>>>> the console. When running the xterm typing 'exit' return will
>>>> terminate the session.  with Xmonad shift-CMD-Q exits xmonad, etc.
>>>>
>>>> running xfce does give a few errors one of which is:
>>>> Error opening /dev/dri/card0  permission denied
>>>>
>>>> I get this from xfsettings and xfwm4
>>>> g_str_has_prefix: assertion 'prefix != NULL' failed
>>>>
>>>> This makes me wonder if there is a conflict with the two video cards the
>>>> built in Intel and the nvidia.
>>>>
>>>> thanks,
>>>>
>>>> Eric
>>>>
>>>> Jason Gerecke <[hidden email]> writes:
>>>>
>>>>> Is there any particular reason you're using an xorg.conf file? That
>>>>> should be completely unnecessary for most systems, and I didn't
>>>>> require one when testing a MobileStudio Pro myself. (Note that I can
>>>>> confirm that `Xorg :0 -configure` crashes, but it appears that's due
>>>>> to a recently-introduced bug in the X server, not our driver. You
>>>>> might consider filing a bug at https://bugzilla.freedesktop.org/ if
>>>>> you rely on the option).
>>>>>
>>>>> I'm not familiar with Xmonad, but if it is starting up then I'd
>>>>> suspect a problem with either: a) incorrect xmonad config, b)
>>>>> incorrect xinitrc config, or c) missing software.
>>>>>
>>>>> As for "startx xterm", is that the literal command that you're
>>>>> running? If you want to just start an xterm you'll need to provide the
>>>>> full path (e.g. `startx /usr/bin/xterm`) or else startx will simply
>>>>> pass "xterm" as a variable to your xinitrc script, where it will
>>>>> (probably) be ignored. The pointer also won't be visible until its
>>>>> moved over the xterm, so it may be advisable to use something like
>>>>> `startx /usr/bin/xterm -maximized` to ensure the xterm takes up the
>>>>> entire screen.
>>>>>
>>>>> Jason
>>>>> ---
>>>>> Now instead of four in the eights place /
>>>>> you’ve got three, ‘Cause you added one  /
>>>>> (That is to say, eight) to the two,     /
>>>>> But you can’t take seven from three,    /
>>>>> So you look at the sixty-fours....
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Mar 22, 2017 at 5:27 PM,  <[hidden email]> wrote:
>>>>>>
>>>>>> One thing leads to another. I decided to upgrade my install because 4.10
>>>>>> is current. I've done this many times before, but somehow I screwed
>>>>>> something up.
>>>>>>
>>>>>> I started over from scratch, which isn't too bad from where I was. But
>>>>>> now I can't get Xorg working at all. The log looks good and it looks
>>>>>> like wacom input is going to work. But all I get is a black screen with
>>>>>> 'startx xterm' or a simple xinitrc with xmonad.
>>>>>>
>>>>>> Xmonad is working sort of. The only thing that works is shift-CMD-Q to
>>>>>> exit. There are no xmonad.errors.
>>>>>>
>>>>>> Does anyone have a working xorg.conf for this machine ?  It seems like it
>>>>>> worked out of the box before.  'Xorg :0 -configure' crashes now. which
>>>>>> is what it seems that I did the last time.
>>>>>>
>>>>>> The only errors I'm getting are unable to load module 'nouveau' and 'nv'
>>>>>> plus a few from wacom invalid types, which look ok, because it does find
>>>>>> the ones it needs.
>>>>>>
>>>>>> the 'nv' driver no longer exists from what I can tell, and nouveau isn't
>>>>>> necessary for this video controller.
>>>>>>
>>>>>> So, I'm just hoping someone here has an xorg.conf that works for this
>>>>>> machine. Suggestions welcome also.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Eric
>>>>>>
>>>>>> [hidden email] writes:
>>>>>>
>>>>>>> Hi Aaron,
>>>>>>>
>>>>>>> I see. Now I've just got to my kernel source in the right place. Either
>>>>>>> I haven't found the right Arch doc or it's just not very easy..
>>>>>>>
>>>>>>> I'm missing the config files for the kernel source and modules. Argh.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>>>
>>>>>>>> HI Eric,
>>>>>>>>
>>>>>>>> If the driver version shows only "v2.00" you haven't installed the
>>>>>>>> kernel driver.
>>>>>>>>
>>>>>>>> If you download the latest driver from
>>>>>>>> https://sourceforge.net/projects/linuxwacom/files/xf86-input-wacom/input-wacom/
>>>>>>>> and install it you should have a version suffix on v2.00. I realize it
>>>>>>>> is confusing how our input-wacom (kernel) driver is nested inside our
>>>>>>>> xf86 (X driver) folder.
>>>>>>>>
>>>>>>>> When I download and install input-wacom-0.34.0.tar.bz2, load and
>>>>>>>> unload the driver with the commands from the link in my previous
>>>>>>>> message, and then issue the command 'modinfo wacom | grep version' ,
>>>>>>>> this is the output I see (granted I'm using a different distro and
>>>>>>>> kernel, but the version should be the same):
>>>>>>>>
>>>>>>>> version:        v2.00-0.34.0
>>>>>>>> srcversion:     DFB3DEC94FA89060ACBD540
>>>>>>>> vermagic:       4.8.0-41-generic SMP mod_unload modversions
>>>>>>>>
>>>>>>>> Best,
>>>>>>>> Aaron
>>>>>>>>
>>>>>>>> On Fri, Mar 17, 2017 at 2:06 PM,  <[hidden email]> wrote:
>>>>>>>>>
>>>>>>>>> Ok, I followed the instruction for building the kernel modules and
>>>>>>>>> installed them.
>>>>>>>>>
>>>>>>>>> I also upgraded Xorg, and reinstalled the official xf86-input-wacom
>>>>>>>>> package which installed 34.2-1 which matches the kernel modules I
>>>>>>>>> downloaded.
>>>>>>>>>
>>>>>>>>> The driver version in /sys/module/wacom/version is v2.00.
>>>>>>>>>
>>>>>>>>> The pen/stylus still does not work.
>>>>>>>>>
>>>>>>>>> Is there something I can look at or try that might help understand
>>>>>>>>> this ?
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> Eric
>>>>>>>>>
>>>>>>>>> [hidden email] writes:
>>>>>>>>>
>>>>>>>>>> Hello Aaron,
>>>>>>>>>>
>>>>>>>>>> Thanks for the help.  I thought that was what I was installing when
>>>>>>>>>> I installed the xf86-input-wacom-git package.
>>>>>>>>>>
>>>>>>>>>> https://aur.archlinux.org/packages/xf86-input-wacom-git/
>>>>>>>>>>
>>>>>>>>>> I've downloaded the tar ball from kernel downloads, but it has the same
>>>>>>>>>> name.  So I think I'm confused about which is the kernel driver, which
>>>>>>>>>> is the X11 driver and what it is that I've actually installed or not
>>>>>>>>>> installed.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>>
>>>>>>>>>> Eric
>>>>>>>>>>
>>>>>>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>>>>>>
>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>
>>>>>>>>>>> Support for MSP was added in kernel 4.10 so you'll need to install the
>>>>>>>>>>> input-wacom kernel driver:
>>>>>>>>>>>
>>>>>>>>>>> http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>>>>>>>>>>>
>>>>>>>>>>> Let us know if you have any other questions.
>>>>>>>>>>>
>>>>>>>>>>> Best,
>>>>>>>>>>> Aaron
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Mar 17, 2017 at 10:45 AM,  <[hidden email]> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hello,
>>>>>>>>>>>>
>>>>>>>>>>>> I have a mobile studio pro running Arch linux.
>>>>>>>>>>>>
>>>>>>>>>>>> I have the xf86-input-wacom-git package installed
>>>>>>>>>>>> aur/xf86-input-wacom-git 0.33.0-1 [installed: 0.34.2-1] (2) (0.07)
>>>>>>>>>>>>     X.Org Wacom tablet driver (from git)
>>>>>>>>>>>>
>>>>>>>>>>>> Linux kernel:
>>>>>>>>>>>> core/linux 4.8.13-1 (base) [installed]
>>>>>>>>>>>>
>>>>>>>>>>>> Xorg Server 1.18.4-1
>>>>>>>>>>>>
>>>>>>>>>>>> xsetwacom --list devices
>>>>>>>>>>>>
>>>>>>>>>>>> -- sorry it's a different computer...
>>>>>>>>>>>>
>>>>>>>>>>>> shows TOUCH, STYLUS, ERASER  with ids of 15, 16, and 17.
>>>>>>>>>>>>
>>>>>>>>>>>> Touch works fine. But the pen doesn't work at all.
>>>>>>>>>>>>
>>>>>>>>>>>> I've tried it krita and that doesn't work either. I would have expected
>>>>>>>>>>>> it to work in the OS.
>>>>>>>>>>>>
>>>>>>>>>>>> I noticed on the device id doc that mobile studio pro 16 has it's
>>>>>>>>>>>> version numbers crossed out.  Should this device work ?
>>>>>>>>>>>>
>>>>>>>>>>>> I've tried it with the old pen from my cintiq companion, and that
>>>>>>>>>>>> doesn't work either.
>>>>>>>>>>>>
>>>>>>>>>>>> Does anyone have suggestions on how to get this working ?
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>
>>>>>>>>>>>> Eric
>>>>>>>>>>>>
>>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>>>>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> Linuxwacom-discuss mailing list
>>>>>>>>>>>> [hidden email]
>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>> _______________________________________________
>>>>>> Linuxwacom-discuss mailing list
>>>>>> [hidden email]
>>>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: mobile studio pro 16 ?

e.a.gebhart
In reply to this post by Jason Gerecke

I have libglvnd.

I deinstalled nvidia and nvidia utils.
When I run xinitrc with an exec xterm -maximized
I get a terminal.

Doing a startxfce4 also works. Next I'll have to refresh my xmonad
and try that.

I'm pretty sure I tried running without the nvidia packages after you
said it should work without them, but maybe I had something else wrong
at the time.

It's weird that those drivers are causing a problem, they should be
unloaded.

The stylus is working too, which is what started me on this path.

Thank you for your help!  I had tried so many things I think I just
needed someone else to talk some sense with me. It's really hard to
do these things without others for feedback and critical thinking.

I can't say how many times I've found a bug just by describing the
problem to someone.

Thank you. I'm very appreciative.

Eric


Jason Gerecke <[hidden email]> writes:

> Oh, another quick question while I'm thinking about it:
>
> Do you have the 'libglvnd' package installed, or are you using another
> package to provide libgl?
>
> On 03/29/2017 04:15 PM, Jason Gerecke wrote:
>> Huh, that's an interesting observation. Lets try removing the nVidia
>> graphics drivers (`pacman -Rs nvidia nvidia-utils`) and see if the
>> open-source drivers work differently. If there's no change, figure out
>> what package installed the legacy nv driver (`pacman -Qo
>> /usr/lib/xorg/modules/drivers/nv_drv.so` should give its name) and
>> remove it too. If that *still* doesn't work, remove the
>> xf86-video-nouveau package as well (which should hopefully have X try to
>> use the Intel drivers).
>>
>> Jason
>> ---
>> Now instead of four in the eights place /
>> you’ve got three, ‘Cause you added one /
>> (That is to say, eight) to the two, /
>> But you can’t take seven from three, /
>> So you look at the sixty-fours....
>>
>> On 03/29/2017 04:00 PM, [hidden email] wrote:
>>>
>>> Yes, I had added Option "DPI" "96 x 96" to the 10-nvidia conf file
>>> during that run. But I have done it both ways with no changes.
>>>
>>> At one point I tried using the nvidia generated xorg.conf.  That results
>>> in what appears to be about 10 pixels being lit up in a row in the upper
>>> left corner of the screen. But I removed that conf file.
>>>
>>> Thanks for looking at this.
>>>
>>> Eric
>>>
>>>
>>> Jason Gerecke <[hidden email]> writes:
>>>
>>>> Thanks for the log. It looks pretty similar to what I see on my system,
>>>> except for the presence of a few more video drivers (though only
>>>> 'nvidia' ends up getting used) and your system's obvious lack of
>>>> systemd-logind. I tried installing the nvidia package to see if maybe it
>>>> was the source of the problem, but it still seems to work fine.
>>>>
>>>> I do notice that your system uses slightly different monitor timings
>>>> than mine, but if the timings were wrong I'd expect the display to go to
>>>> sleep (and turn off the backlight) rather than just render nothing.
>>>>
>>>> Finally, I also see that the X server is getting a DPI value of 96 from
>>>> somewhere. On my system it says that it can't find the screen's DPI and
>>>> so it falls back to 75. While the DPI itself isn't going to change
>>>> anything, it might indicate the presence of X configuration files that
>>>> are modifying its behavior in ways not captured by the log. Do you have
>>>> any files under /etc/X11/xorg.conf.d or have you edited any files under
>>>> /usr/share/X11/xorg.conf.d?
>>>>
>>>> Jason
>>>> ---
>>>> Now instead of four in the eights place /
>>>> you’ve got three, ‘Cause you added one /
>>>> (That is to say, eight) to the two, /
>>>> But you can’t take seven from three, /
>>>> So you look at the sixty-fours....
>>>>
>>>> On 03/29/2017 06:47 AM, [hidden email] wrote:
>>>>>
>>>>> I'm wondering if I shouldn't start over with a fresh install again. But
>>>>> maybe this will reveal something.  Here is my log.
>>>>>
>>>> [snip]
>>>>>
>>>>> Jason Gerecke <[hidden email]> writes:
>>>>>
>>>>>> I just gave Arch a whirl to see if a recent update broke something,
>>>>>> but even after rebooting from a fresh `pacman -Syu` I don't see any
>>>>>> problems on the MobileStudio Pro 16. Its using GDM by default, but
>>>>>> even when I switch to multi-user.target and run `startx
>>>>>> /usr/bin/xfce4-terminal` (I don't have the vanilla xterm installed)
>>>>>> manually I don't see any problems. No xorg.conf file either...
>>>>>>
>>>>>> Notable package versions (though if you upgraded, they should be identical...):
>>>>>>
>>>>>>  * core/linux 4.10.4-1
>>>>>>  * extra/xorg-server 1.19.3-1
>>>>>>  * extra/xf86-video-fbdev 0.4.4-6
>>>>>>  * extra/xf86-video-intel 1:2.99.917+767+g7e9e92c8-1
>>>>>>  * (No nouveau, nv, or nvidia graphics)
>>>>>>  * extra/mesa 17.0.1-2
>>>>>>
>>>>>> If you've got an Xorg.0.log, go ahead and attach it for me to review...
>>>>>>
>>>>>> Jason
>>>>>> ---
>>>>>> Now instead of four in the eights place /
>>>>>> you’ve got three, ‘Cause you added one  /
>>>>>> (That is to say, eight) to the two,     /
>>>>>> But you can’t take seven from three,    /
>>>>>> So you look at the sixty-fours....
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Mar 23, 2017 at 11:47 AM,  <[hidden email]> wrote:
>>>>>>>
>>>>>>> Using an xorg.conf file is the only way I know to change the behavior of
>>>>>>> xorg. Given that the display is what is not showing I cannot think of
>>>>>>> anything other than that the automatic configuration is not working.
>>>>>>>
>>>>>>> This setup worked perfectly (no stylus) before upgrading the kernel to
>>>>>>> 4.10 and Xorg to 1.19.3. I thought about downgrading xorg but that is a huge pain.
>>>>>>> Being on Arch I just did the usual pacman -Syy and pacman -Su. I thought
>>>>>>> I had screwed something up, but now I'm seeing the same behavior on a
>>>>>>> fresh install.
>>>>>>>
>>>>>>> Xmonad does not have any errors. I can replace it with twm,
>>>>>>> exec startxfce4 or exec xterm with the same effect. maximized xterm
>>>>>>> makes no difference.
>>>>>>>
>>>>>>> No matter what I do I get a black screen.  alt-ctrl-f1 brings me back to
>>>>>>> the console. When running the xterm typing 'exit' return will
>>>>>>> terminate the session.  with Xmonad shift-CMD-Q exits xmonad, etc.
>>>>>>>
>>>>>>> running xfce does give a few errors one of which is:
>>>>>>> Error opening /dev/dri/card0  permission denied
>>>>>>>
>>>>>>> I get this from xfsettings and xfwm4
>>>>>>> g_str_has_prefix: assertion 'prefix != NULL' failed
>>>>>>>
>>>>>>> This makes me wonder if there is a conflict with the two video cards the
>>>>>>> built in Intel and the nvidia.
>>>>>>>
>>>>>>> thanks,
>>>>>>>
>>>>>>> Eric
>>>>>>>
>>>>>>> Jason Gerecke <[hidden email]> writes:
>>>>>>>
>>>>>>>> Is there any particular reason you're using an xorg.conf file? That
>>>>>>>> should be completely unnecessary for most systems, and I didn't
>>>>>>>> require one when testing a MobileStudio Pro myself. (Note that I can
>>>>>>>> confirm that `Xorg :0 -configure` crashes, but it appears that's due
>>>>>>>> to a recently-introduced bug in the X server, not our driver. You
>>>>>>>> might consider filing a bug at https://bugzilla.freedesktop.org/ if
>>>>>>>> you rely on the option).
>>>>>>>>
>>>>>>>> I'm not familiar with Xmonad, but if it is starting up then I'd
>>>>>>>> suspect a problem with either: a) incorrect xmonad config, b)
>>>>>>>> incorrect xinitrc config, or c) missing software.
>>>>>>>>
>>>>>>>> As for "startx xterm", is that the literal command that you're
>>>>>>>> running? If you want to just start an xterm you'll need to provide the
>>>>>>>> full path (e.g. `startx /usr/bin/xterm`) or else startx will simply
>>>>>>>> pass "xterm" as a variable to your xinitrc script, where it will
>>>>>>>> (probably) be ignored. The pointer also won't be visible until its
>>>>>>>> moved over the xterm, so it may be advisable to use something like
>>>>>>>> `startx /usr/bin/xterm -maximized` to ensure the xterm takes up the
>>>>>>>> entire screen.
>>>>>>>>
>>>>>>>> Jason
>>>>>>>> ---
>>>>>>>> Now instead of four in the eights place /
>>>>>>>> you’ve got three, ‘Cause you added one  /
>>>>>>>> (That is to say, eight) to the two,     /
>>>>>>>> But you can’t take seven from three,    /
>>>>>>>> So you look at the sixty-fours....
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Mar 22, 2017 at 5:27 PM,  <[hidden email]> wrote:
>>>>>>>>>
>>>>>>>>> One thing leads to another. I decided to upgrade my install because 4.10
>>>>>>>>> is current. I've done this many times before, but somehow I screwed
>>>>>>>>> something up.
>>>>>>>>>
>>>>>>>>> I started over from scratch, which isn't too bad from where I was. But
>>>>>>>>> now I can't get Xorg working at all. The log looks good and it looks
>>>>>>>>> like wacom input is going to work. But all I get is a black screen with
>>>>>>>>> 'startx xterm' or a simple xinitrc with xmonad.
>>>>>>>>>
>>>>>>>>> Xmonad is working sort of. The only thing that works is shift-CMD-Q to
>>>>>>>>> exit. There are no xmonad.errors.
>>>>>>>>>
>>>>>>>>> Does anyone have a working xorg.conf for this machine ?  It seems like it
>>>>>>>>> worked out of the box before.  'Xorg :0 -configure' crashes now. which
>>>>>>>>> is what it seems that I did the last time.
>>>>>>>>>
>>>>>>>>> The only errors I'm getting are unable to load module 'nouveau' and 'nv'
>>>>>>>>> plus a few from wacom invalid types, which look ok, because it does find
>>>>>>>>> the ones it needs.
>>>>>>>>>
>>>>>>>>> the 'nv' driver no longer exists from what I can tell, and nouveau isn't
>>>>>>>>> necessary for this video controller.
>>>>>>>>>
>>>>>>>>> So, I'm just hoping someone here has an xorg.conf that works for this
>>>>>>>>> machine. Suggestions welcome also.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> Eric
>>>>>>>>>
>>>>>>>>> [hidden email] writes:
>>>>>>>>>
>>>>>>>>>> Hi Aaron,
>>>>>>>>>>
>>>>>>>>>> I see. Now I've just got to my kernel source in the right place. Either
>>>>>>>>>> I haven't found the right Arch doc or it's just not very easy..
>>>>>>>>>>
>>>>>>>>>> I'm missing the config files for the kernel source and modules. Argh.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>>>>>>
>>>>>>>>>>> HI Eric,
>>>>>>>>>>>
>>>>>>>>>>> If the driver version shows only "v2.00" you haven't installed the
>>>>>>>>>>> kernel driver.
>>>>>>>>>>>
>>>>>>>>>>> If you download the latest driver from
>>>>>>>>>>> https://sourceforge.net/projects/linuxwacom/files/xf86-input-wacom/input-wacom/
>>>>>>>>>>> and install it you should have a version suffix on v2.00. I realize it
>>>>>>>>>>> is confusing how our input-wacom (kernel) driver is nested inside our
>>>>>>>>>>> xf86 (X driver) folder.
>>>>>>>>>>>
>>>>>>>>>>> When I download and install input-wacom-0.34.0.tar.bz2, load and
>>>>>>>>>>> unload the driver with the commands from the link in my previous
>>>>>>>>>>> message, and then issue the command 'modinfo wacom | grep version' ,
>>>>>>>>>>> this is the output I see (granted I'm using a different distro and
>>>>>>>>>>> kernel, but the version should be the same):
>>>>>>>>>>>
>>>>>>>>>>> version:        v2.00-0.34.0
>>>>>>>>>>> srcversion:     DFB3DEC94FA89060ACBD540
>>>>>>>>>>> vermagic:       4.8.0-41-generic SMP mod_unload modversions
>>>>>>>>>>>
>>>>>>>>>>> Best,
>>>>>>>>>>> Aaron
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Mar 17, 2017 at 2:06 PM,  <[hidden email]> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Ok, I followed the instruction for building the kernel modules and
>>>>>>>>>>>> installed them.
>>>>>>>>>>>>
>>>>>>>>>>>> I also upgraded Xorg, and reinstalled the official xf86-input-wacom
>>>>>>>>>>>> package which installed 34.2-1 which matches the kernel modules I
>>>>>>>>>>>> downloaded.
>>>>>>>>>>>>
>>>>>>>>>>>> The driver version in /sys/module/wacom/version is v2.00.
>>>>>>>>>>>>
>>>>>>>>>>>> The pen/stylus still does not work.
>>>>>>>>>>>>
>>>>>>>>>>>> Is there something I can look at or try that might help understand
>>>>>>>>>>>> this ?
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>
>>>>>>>>>>>> Eric
>>>>>>>>>>>>
>>>>>>>>>>>> [hidden email] writes:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hello Aaron,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks for the help.  I thought that was what I was installing when
>>>>>>>>>>>>> I installed the xf86-input-wacom-git package.
>>>>>>>>>>>>>
>>>>>>>>>>>>> https://aur.archlinux.org/packages/xf86-input-wacom-git/
>>>>>>>>>>>>>
>>>>>>>>>>>>> I've downloaded the tar ball from kernel downloads, but it has the same
>>>>>>>>>>>>> name.  So I think I'm confused about which is the kernel driver, which
>>>>>>>>>>>>> is the X11 driver and what it is that I've actually installed or not
>>>>>>>>>>>>> installed.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Eric
>>>>>>>>>>>>>
>>>>>>>>>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Support for MSP was added in kernel 4.10 so you'll need to install the
>>>>>>>>>>>>>> input-wacom kernel driver:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Let us know if you have any other questions.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Best,
>>>>>>>>>>>>>> Aaron
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Mar 17, 2017 at 10:45 AM,  <[hidden email]> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hello,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have a mobile studio pro running Arch linux.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have the xf86-input-wacom-git package installed
>>>>>>>>>>>>>>> aur/xf86-input-wacom-git 0.33.0-1 [installed: 0.34.2-1] (2) (0.07)
>>>>>>>>>>>>>>>     X.Org Wacom tablet driver (from git)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Linux kernel:
>>>>>>>>>>>>>>> core/linux 4.8.13-1 (base) [installed]
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Xorg Server 1.18.4-1
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> xsetwacom --list devices
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> -- sorry it's a different computer...
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> shows TOUCH, STYLUS, ERASER  with ids of 15, 16, and 17.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Touch works fine. But the pen doesn't work at all.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I've tried it krita and that doesn't work either. I would have expected
>>>>>>>>>>>>>>> it to work in the OS.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I noticed on the device id doc that mobile studio pro 16 has it's
>>>>>>>>>>>>>>> version numbers crossed out.  Should this device work ?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I've tried it with the old pen from my cintiq companion, and that
>>>>>>>>>>>>>>> doesn't work either.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Does anyone have suggestions on how to get this working ?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Eric
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>>>>>>>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>> Linuxwacom-discuss mailing list
>>>>>>>>>>>>>>> [hidden email]
>>>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>>>>> _______________________________________________
>>>>>>>>> Linuxwacom-discuss mailing list
>>>>>>>>> [hidden email]
>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: mobile studio pro 16 ?

Jason Gerecke
Glad to hear that it's showing signs of life again :)

I still wonder why the nVidia driver isn't working properly though. The
backlight turning off (as mentioned in your other message) is definitely
a bit suspicious. Would you mind posting your Xorg.0.log again for
comparison to the broken one? It'd be interesting to see if the current
driver also detects/uses the "extra" modeline.

Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one /
(That is to say, eight) to the two, /
But you can’t take seven from three, /
So you look at the sixty-fours....

On 03/29/2017 05:04 PM, [hidden email] wrote:

>
> I have libglvnd.
>
> I deinstalled nvidia and nvidia utils.
> When I run xinitrc with an exec xterm -maximized
> I get a terminal.
>
> Doing a startxfce4 also works. Next I'll have to refresh my xmonad
> and try that.
>
> I'm pretty sure I tried running without the nvidia packages after you
> said it should work without them, but maybe I had something else wrong
> at the time.
>
> It's weird that those drivers are causing a problem, they should be
> unloaded.
>
> The stylus is working too, which is what started me on this path.
>
> Thank you for your help!  I had tried so many things I think I just
> needed someone else to talk some sense with me. It's really hard to
> do these things without others for feedback and critical thinking.
>
> I can't say how many times I've found a bug just by describing the
> problem to someone.
>
> Thank you. I'm very appreciative.
>
> Eric
>
>
> Jason Gerecke <[hidden email]> writes:
>
>> Oh, another quick question while I'm thinking about it:
>>
>> Do you have the 'libglvnd' package installed, or are you using another
>> package to provide libgl?
>>
>> On 03/29/2017 04:15 PM, Jason Gerecke wrote:
>>> Huh, that's an interesting observation. Lets try removing the nVidia
>>> graphics drivers (`pacman -Rs nvidia nvidia-utils`) and see if the
>>> open-source drivers work differently. If there's no change, figure out
>>> what package installed the legacy nv driver (`pacman -Qo
>>> /usr/lib/xorg/modules/drivers/nv_drv.so` should give its name) and
>>> remove it too. If that *still* doesn't work, remove the
>>> xf86-video-nouveau package as well (which should hopefully have X try to
>>> use the Intel drivers).
>>>
>>> Jason
>>> ---
>>> Now instead of four in the eights place /
>>> you’ve got three, ‘Cause you added one /
>>> (That is to say, eight) to the two, /
>>> But you can’t take seven from three, /
>>> So you look at the sixty-fours....
>>>
>>> On 03/29/2017 04:00 PM, [hidden email] wrote:
>>>>
>>>> Yes, I had added Option "DPI" "96 x 96" to the 10-nvidia conf file
>>>> during that run. But I have done it both ways with no changes.
>>>>
>>>> At one point I tried using the nvidia generated xorg.conf.  That results
>>>> in what appears to be about 10 pixels being lit up in a row in the upper
>>>> left corner of the screen. But I removed that conf file.
>>>>
>>>> Thanks for looking at this.
>>>>
>>>> Eric
>>>>
>>>>
>>>> Jason Gerecke <[hidden email]> writes:
>>>>
>>>>> Thanks for the log. It looks pretty similar to what I see on my system,
>>>>> except for the presence of a few more video drivers (though only
>>>>> 'nvidia' ends up getting used) and your system's obvious lack of
>>>>> systemd-logind. I tried installing the nvidia package to see if maybe it
>>>>> was the source of the problem, but it still seems to work fine.
>>>>>
>>>>> I do notice that your system uses slightly different monitor timings
>>>>> than mine, but if the timings were wrong I'd expect the display to go to
>>>>> sleep (and turn off the backlight) rather than just render nothing.
>>>>>
>>>>> Finally, I also see that the X server is getting a DPI value of 96 from
>>>>> somewhere. On my system it says that it can't find the screen's DPI and
>>>>> so it falls back to 75. While the DPI itself isn't going to change
>>>>> anything, it might indicate the presence of X configuration files that
>>>>> are modifying its behavior in ways not captured by the log. Do you have
>>>>> any files under /etc/X11/xorg.conf.d or have you edited any files under
>>>>> /usr/share/X11/xorg.conf.d?
>>>>>
>>>>> Jason
>>>>> ---
>>>>> Now instead of four in the eights place /
>>>>> you’ve got three, ‘Cause you added one /
>>>>> (That is to say, eight) to the two, /
>>>>> But you can’t take seven from three, /
>>>>> So you look at the sixty-fours....
>>>>>
>>>>> On 03/29/2017 06:47 AM, [hidden email] wrote:
>>>>>>
>>>>>> I'm wondering if I shouldn't start over with a fresh install again. But
>>>>>> maybe this will reveal something.  Here is my log.
>>>>>>
>>>>> [snip]
>>>>>>
>>>>>> Jason Gerecke <[hidden email]> writes:
>>>>>>
>>>>>>> I just gave Arch a whirl to see if a recent update broke something,
>>>>>>> but even after rebooting from a fresh `pacman -Syu` I don't see any
>>>>>>> problems on the MobileStudio Pro 16. Its using GDM by default, but
>>>>>>> even when I switch to multi-user.target and run `startx
>>>>>>> /usr/bin/xfce4-terminal` (I don't have the vanilla xterm installed)
>>>>>>> manually I don't see any problems. No xorg.conf file either...
>>>>>>>
>>>>>>> Notable package versions (though if you upgraded, they should be identical...):
>>>>>>>
>>>>>>>  * core/linux 4.10.4-1
>>>>>>>  * extra/xorg-server 1.19.3-1
>>>>>>>  * extra/xf86-video-fbdev 0.4.4-6
>>>>>>>  * extra/xf86-video-intel 1:2.99.917+767+g7e9e92c8-1
>>>>>>>  * (No nouveau, nv, or nvidia graphics)
>>>>>>>  * extra/mesa 17.0.1-2
>>>>>>>
>>>>>>> If you've got an Xorg.0.log, go ahead and attach it for me to review...
>>>>>>>
>>>>>>> Jason
>>>>>>> ---
>>>>>>> Now instead of four in the eights place /
>>>>>>> you’ve got three, ‘Cause you added one  /
>>>>>>> (That is to say, eight) to the two,     /
>>>>>>> But you can’t take seven from three,    /
>>>>>>> So you look at the sixty-fours....
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Mar 23, 2017 at 11:47 AM,  <[hidden email]> wrote:
>>>>>>>>
>>>>>>>> Using an xorg.conf file is the only way I know to change the behavior of
>>>>>>>> xorg. Given that the display is what is not showing I cannot think of
>>>>>>>> anything other than that the automatic configuration is not working.
>>>>>>>>
>>>>>>>> This setup worked perfectly (no stylus) before upgrading the kernel to
>>>>>>>> 4.10 and Xorg to 1.19.3. I thought about downgrading xorg but that is a huge pain.
>>>>>>>> Being on Arch I just did the usual pacman -Syy and pacman -Su. I thought
>>>>>>>> I had screwed something up, but now I'm seeing the same behavior on a
>>>>>>>> fresh install.
>>>>>>>>
>>>>>>>> Xmonad does not have any errors. I can replace it with twm,
>>>>>>>> exec startxfce4 or exec xterm with the same effect. maximized xterm
>>>>>>>> makes no difference.
>>>>>>>>
>>>>>>>> No matter what I do I get a black screen.  alt-ctrl-f1 brings me back to
>>>>>>>> the console. When running the xterm typing 'exit' return will
>>>>>>>> terminate the session.  with Xmonad shift-CMD-Q exits xmonad, etc.
>>>>>>>>
>>>>>>>> running xfce does give a few errors one of which is:
>>>>>>>> Error opening /dev/dri/card0  permission denied
>>>>>>>>
>>>>>>>> I get this from xfsettings and xfwm4
>>>>>>>> g_str_has_prefix: assertion 'prefix != NULL' failed
>>>>>>>>
>>>>>>>> This makes me wonder if there is a conflict with the two video cards the
>>>>>>>> built in Intel and the nvidia.
>>>>>>>>
>>>>>>>> thanks,
>>>>>>>>
>>>>>>>> Eric
>>>>>>>>
>>>>>>>> Jason Gerecke <[hidden email]> writes:
>>>>>>>>
>>>>>>>>> Is there any particular reason you're using an xorg.conf file? That
>>>>>>>>> should be completely unnecessary for most systems, and I didn't
>>>>>>>>> require one when testing a MobileStudio Pro myself. (Note that I can
>>>>>>>>> confirm that `Xorg :0 -configure` crashes, but it appears that's due
>>>>>>>>> to a recently-introduced bug in the X server, not our driver. You
>>>>>>>>> might consider filing a bug at https://bugzilla.freedesktop.org/ if
>>>>>>>>> you rely on the option).
>>>>>>>>>
>>>>>>>>> I'm not familiar with Xmonad, but if it is starting up then I'd
>>>>>>>>> suspect a problem with either: a) incorrect xmonad config, b)
>>>>>>>>> incorrect xinitrc config, or c) missing software.
>>>>>>>>>
>>>>>>>>> As for "startx xterm", is that the literal command that you're
>>>>>>>>> running? If you want to just start an xterm you'll need to provide the
>>>>>>>>> full path (e.g. `startx /usr/bin/xterm`) or else startx will simply
>>>>>>>>> pass "xterm" as a variable to your xinitrc script, where it will
>>>>>>>>> (probably) be ignored. The pointer also won't be visible until its
>>>>>>>>> moved over the xterm, so it may be advisable to use something like
>>>>>>>>> `startx /usr/bin/xterm -maximized` to ensure the xterm takes up the
>>>>>>>>> entire screen.
>>>>>>>>>
>>>>>>>>> Jason
>>>>>>>>> ---
>>>>>>>>> Now instead of four in the eights place /
>>>>>>>>> you’ve got three, ‘Cause you added one  /
>>>>>>>>> (That is to say, eight) to the two,     /
>>>>>>>>> But you can’t take seven from three,    /
>>>>>>>>> So you look at the sixty-fours....
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Mar 22, 2017 at 5:27 PM,  <[hidden email]> wrote:
>>>>>>>>>>
>>>>>>>>>> One thing leads to another. I decided to upgrade my install because 4.10
>>>>>>>>>> is current. I've done this many times before, but somehow I screwed
>>>>>>>>>> something up.
>>>>>>>>>>
>>>>>>>>>> I started over from scratch, which isn't too bad from where I was. But
>>>>>>>>>> now I can't get Xorg working at all. The log looks good and it looks
>>>>>>>>>> like wacom input is going to work. But all I get is a black screen with
>>>>>>>>>> 'startx xterm' or a simple xinitrc with xmonad.
>>>>>>>>>>
>>>>>>>>>> Xmonad is working sort of. The only thing that works is shift-CMD-Q to
>>>>>>>>>> exit. There are no xmonad.errors.
>>>>>>>>>>
>>>>>>>>>> Does anyone have a working xorg.conf for this machine ?  It seems like it
>>>>>>>>>> worked out of the box before.  'Xorg :0 -configure' crashes now. which
>>>>>>>>>> is what it seems that I did the last time.
>>>>>>>>>>
>>>>>>>>>> The only errors I'm getting are unable to load module 'nouveau' and 'nv'
>>>>>>>>>> plus a few from wacom invalid types, which look ok, because it does find
>>>>>>>>>> the ones it needs.
>>>>>>>>>>
>>>>>>>>>> the 'nv' driver no longer exists from what I can tell, and nouveau isn't
>>>>>>>>>> necessary for this video controller.
>>>>>>>>>>
>>>>>>>>>> So, I'm just hoping someone here has an xorg.conf that works for this
>>>>>>>>>> machine. Suggestions welcome also.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>>
>>>>>>>>>> Eric
>>>>>>>>>>
>>>>>>>>>> [hidden email] writes:
>>>>>>>>>>
>>>>>>>>>>> Hi Aaron,
>>>>>>>>>>>
>>>>>>>>>>> I see. Now I've just got to my kernel source in the right place. Either
>>>>>>>>>>> I haven't found the right Arch doc or it's just not very easy..
>>>>>>>>>>>
>>>>>>>>>>> I'm missing the config files for the kernel source and modules. Argh.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>>>>>>>
>>>>>>>>>>>> HI Eric,
>>>>>>>>>>>>
>>>>>>>>>>>> If the driver version shows only "v2.00" you haven't installed the
>>>>>>>>>>>> kernel driver.
>>>>>>>>>>>>
>>>>>>>>>>>> If you download the latest driver from
>>>>>>>>>>>> https://sourceforge.net/projects/linuxwacom/files/xf86-input-wacom/input-wacom/
>>>>>>>>>>>> and install it you should have a version suffix on v2.00. I realize it
>>>>>>>>>>>> is confusing how our input-wacom (kernel) driver is nested inside our
>>>>>>>>>>>> xf86 (X driver) folder.
>>>>>>>>>>>>
>>>>>>>>>>>> When I download and install input-wacom-0.34.0.tar.bz2, load and
>>>>>>>>>>>> unload the driver with the commands from the link in my previous
>>>>>>>>>>>> message, and then issue the command 'modinfo wacom | grep version' ,
>>>>>>>>>>>> this is the output I see (granted I'm using a different distro and
>>>>>>>>>>>> kernel, but the version should be the same):
>>>>>>>>>>>>
>>>>>>>>>>>> version:        v2.00-0.34.0
>>>>>>>>>>>> srcversion:     DFB3DEC94FA89060ACBD540
>>>>>>>>>>>> vermagic:       4.8.0-41-generic SMP mod_unload modversions
>>>>>>>>>>>>
>>>>>>>>>>>> Best,
>>>>>>>>>>>> Aaron
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Mar 17, 2017 at 2:06 PM,  <[hidden email]> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Ok, I followed the instruction for building the kernel modules and
>>>>>>>>>>>>> installed them.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I also upgraded Xorg, and reinstalled the official xf86-input-wacom
>>>>>>>>>>>>> package which installed 34.2-1 which matches the kernel modules I
>>>>>>>>>>>>> downloaded.
>>>>>>>>>>>>>
>>>>>>>>>>>>> The driver version in /sys/module/wacom/version is v2.00.
>>>>>>>>>>>>>
>>>>>>>>>>>>> The pen/stylus still does not work.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Is there something I can look at or try that might help understand
>>>>>>>>>>>>> this ?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Eric
>>>>>>>>>>>>>
>>>>>>>>>>>>> [hidden email] writes:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hello Aaron,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks for the help.  I thought that was what I was installing when
>>>>>>>>>>>>>> I installed the xf86-input-wacom-git package.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> https://aur.archlinux.org/packages/xf86-input-wacom-git/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I've downloaded the tar ball from kernel downloads, but it has the same
>>>>>>>>>>>>>> name.  So I think I'm confused about which is the kernel driver, which
>>>>>>>>>>>>>> is the X11 driver and what it is that I've actually installed or not
>>>>>>>>>>>>>> installed.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Eric
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Support for MSP was added in kernel 4.10 so you'll need to install the
>>>>>>>>>>>>>>> input-wacom kernel driver:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Let us know if you have any other questions.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Best,
>>>>>>>>>>>>>>> Aaron
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Fri, Mar 17, 2017 at 10:45 AM,  <[hidden email]> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hello,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have a mobile studio pro running Arch linux.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have the xf86-input-wacom-git package installed
>>>>>>>>>>>>>>>> aur/xf86-input-wacom-git 0.33.0-1 [installed: 0.34.2-1] (2) (0.07)
>>>>>>>>>>>>>>>>     X.Org Wacom tablet driver (from git)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Linux kernel:
>>>>>>>>>>>>>>>> core/linux 4.8.13-1 (base) [installed]
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Xorg Server 1.18.4-1
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> xsetwacom --list devices
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> -- sorry it's a different computer...
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> shows TOUCH, STYLUS, ERASER  with ids of 15, 16, and 17.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Touch works fine. But the pen doesn't work at all.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I've tried it krita and that doesn't work either. I would have expected
>>>>>>>>>>>>>>>> it to work in the OS.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I noticed on the device id doc that mobile studio pro 16 has it's
>>>>>>>>>>>>>>>> version numbers crossed out.  Should this device work ?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I've tried it with the old pen from my cintiq companion, and that
>>>>>>>>>>>>>>>> doesn't work either.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Does anyone have suggestions on how to get this working ?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Eric
>>>>>>>>>>>>>>>>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: mobile studio pro 16 ?

e.a.gebhart

Unless I missed something it looks like it's using the intel video.
I should probably remove the nouveau driver. It's not doing anything.

[539692.498]
X.Org X Server 1.19.3
Release Date: 2017-03-15
[539692.500] X Protocol Version 11, Revision 0
[539692.501] Build Operating System: Linux 4.9.11-1-ARCH x86_64
[539692.501] Current Operating System: Linux egalite 4.10.4-1-ARCH #1 SMP PREEMPT Sat Mar 18 19:39:18 CET 2017 x86_64
[539692.501] Kernel command line: initrd=\initramfs-linux.img root=PARTUUID=773da99e-8124-4e01-9ccd-4a95061d3359 rw
[539692.503] Build Date: 16 March 2017  02:47:54PM
[539692.504]
[539692.504] Current version of pixman: 0.34.0
[539692.506] Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[539692.506] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[539692.508] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 29 19:59:28 2017
[539692.509] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[539692.509] (==) No Layout section.  Using the first Screen section.
[539692.509] (==) No screen section available. Using defaults.
[539692.509] (**) |-->Screen "Default Screen Section" (0)
[539692.509] (**) |   |-->Monitor "<default monitor>"
[539692.509] (==) No monitor specified for screen "Default Screen Section".
        Using a default monitor configuration.
[539692.509] (==) Automatically adding devices
[539692.509] (==) Automatically enabling devices
[539692.509] (==) Automatically adding GPU devices
[539692.509] (==) Automatically binding GPU devices
[539692.509] (==) Max clients allowed: 256, resource mask: 0x1fffff
[539692.509] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[539692.509] Entry deleted from font path.
[539692.509] (==) FontPath set to:
        /usr/share/fonts/misc/,
        /usr/share/fonts/TTF/,
        /usr/share/fonts/OTF/,
        /usr/share/fonts/100dpi/,
        /usr/share/fonts/75dpi/
[539692.509] (==) ModulePath set to "/usr/lib/xorg/modules"
[539692.509] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[539692.509] (II) Loader magic: 0x822d60
[539692.509] (II) Module ABI versions:
[539692.509] X.Org ANSI C Emulation: 0.4
[539692.509] X.Org Video Driver: 23.0
[539692.509] X.Org XInput driver : 24.1
[539692.509] X.Org Server Extension : 10.0
[539692.510] (--) using VT number 2

[539692.510] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[539692.510] (II) xfree86: Adding drm device (/dev/dri/card0)
[539692.526] (II) xfree86: Adding drm device (/dev/dri/card1)
[539692.527] (--) PCI:*(0:0:2:0) 8086:1927:1b0a:01cf rev 10, Mem @ 0xa2000000/16777216, 0xb0000000/268435456, I/O @ 0x00004000/64, BIOS @ 0x????????/131072
[539692.528] (--) PCI: (0:1:0:0) 10de:13b1:1b0a:01cf rev 162, Mem @ 0xa3000000/16777216, 0x90000000/268435456, 0xa0000000/33554432, I/O @ 0x00003000/128
[539692.528] (II) Open ACPI successful (/var/run/acpid.socket)
[539692.528] (II) LoadModule: "glx"
[539692.528] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[539692.528] (II) Module glx: vendor="X.Org Foundation"
[539692.528] compiled for 1.19.3, module version = 1.0.0
[539692.528] ABI class: X.Org Server Extension, version 10.0
[539692.528] (==) Matched intel as autoconfigured driver 0
[539692.528] (==) Matched nouveau as autoconfigured driver 1
[539692.528] (==) Matched nv as autoconfigured driver 2
[539692.528] (==) Matched intel as autoconfigured driver 3
[539692.528] (==) Matched modesetting as autoconfigured driver 4
[539692.528] (==) Matched fbdev as autoconfigured driver 5
[539692.528] (==) Matched vesa as autoconfigured driver 6
[539692.529] (==) Assigned the driver to the xf86ConfigLayout
[539692.529] (II) LoadModule: "intel"
[539692.529] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[539692.529] (II) Module intel: vendor="X.Org Foundation"
[539692.529] compiled for 1.19.3, module version = 2.99.917
[539692.529] Module class: X.Org Video Driver
[539692.529] ABI class: X.Org Video Driver, version 23.0
[539692.529] (II) LoadModule: "nouveau"
[539692.529] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[539692.529] (II) Module nouveau: vendor="X.Org Foundation"
[539692.529] compiled for 1.19.2, module version = 1.0.14
[539692.529] Module class: X.Org Video Driver
[539692.529] ABI class: X.Org Video Driver, version 23.0
[539692.529] (II) LoadModule: "nv"
[539692.529] (II) Loading /usr/lib/xorg/modules/drivers/nv_drv.so
[539692.529] (II) Module nv: vendor="X.Org Foundation"
[539692.529] compiled for 1.19.3, module version = 2.1.20
[539692.529] Module class: X.Org Video Driver
[539692.529] ABI class: X.Org Video Driver, version 23.0
[539692.529] (II) LoadModule: "modesetting"
[539692.529] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[539692.529] (II) Module modesetting: vendor="X.Org Foundation"
[539692.529] compiled for 1.19.3, module version = 1.19.3
[539692.529] Module class: X.Org Video Driver
[539692.529] ABI class: X.Org Video Driver, version 23.0
[539692.529] (II) LoadModule: "fbdev"
[539692.529] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[539692.529] (II) Module fbdev: vendor="X.Org Foundation"
[539692.529] compiled for 1.19.0, module version = 0.4.4
[539692.529] Module class: X.Org Video Driver
[539692.529] ABI class: X.Org Video Driver, version 23.0
[539692.529] (II) LoadModule: "vesa"
[539692.530] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[539692.530] (II) Module vesa: vendor="X.Org Foundation"
[539692.530] compiled for 1.19.0, module version = 2.3.4
[539692.530] Module class: X.Org Video Driver
[539692.530] ABI class: X.Org Video Driver, version 23.0
[539692.530] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
        i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
        915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
        Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
        GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[539692.530] (II) intel: Driver for Intel(R) HD Graphics
[539692.530] (II) intel: Driver for Intel(R) Iris(TM) Graphics
[539692.530] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics
[539692.530] (II) NOUVEAU driver
[539692.530] (II) NOUVEAU driver for NVIDIA chipset families :
[539692.530] RIVA TNT        (NV04)
[539692.530] RIVA TNT2       (NV05)
[539692.530] GeForce 256     (NV10)
[539692.530] GeForce 2       (NV11, NV15)
[539692.530] GeForce 4MX     (NV17, NV18)
[539692.530] GeForce 3       (NV20)
[539692.530] GeForce 4Ti     (NV25, NV28)
[539692.530] GeForce FX      (NV3x)
[539692.530] GeForce 6       (NV4x)
[539692.530] GeForce 7       (G7x)
[539692.530] GeForce 8       (G8x)
[539692.530] GeForce GTX 200 (NVA0)
[539692.530] GeForce GTX 400 (NVC0)
[539692.530] (II) NOUVEAU driver
[539692.530] (II) NOUVEAU driver for NVIDIA chipset families :
[539692.530] RIVA TNT        (NV04)
[539692.530] RIVA TNT2       (NV05)
[539692.530] GeForce 256     (NV10)
[539692.530] GeForce 2       (NV11, NV15)
[539692.530] GeForce 4MX     (NV17, NV18)
[539692.530] GeForce 3       (NV20)
[539692.530] GeForce 4Ti     (NV25, NV28)
[539692.530] GeForce FX      (NV3x)
[539692.530] GeForce 6       (NV4x)
[539692.530] GeForce 7       (G7x)
[539692.530] GeForce 8       (G8x)
[539692.530] GeForce GTX 200 (NVA0)
[539692.530] GeForce GTX 400 (NVC0)
[539692.530] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[539692.530] (II) FBDEV: driver for framebuffer: fbdev
[539692.530] (II) VESA: driver for VESA chipsets: vesa
[539692.580] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20161121
[539692.580] (II) intel(0): SNA compiled from 2.99.917-767-g7e9e92c8
[539692.581] (WW) Falling back to old probe method for modesetting
[539692.581] (WW) Falling back to old probe method for fbdev
[539692.581] (II) Loading sub module "fbdevhw"
[539692.581] (II) LoadModule: "fbdevhw"
[539692.581] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[539692.581] (II) Module fbdevhw: vendor="X.Org Foundation"
[539692.581] compiled for 1.19.3, module version = 0.0.2
[539692.581] ABI class: X.Org Video Driver, version 23.0
[539692.581] (WW) Falling back to old probe method for vesa
[539692.581] (EE) [drm] Failed to open DRM device for (null): -22
[539692.581] (EE) [drm] Failed to open DRM device for (null): -22
[539692.581] (--) intel(0): Integrated Graphics Chipset: Intel(R) Iris Graphics 550
[539692.581] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx, avx2; using a maximum of 2 threads
[539692.581] (II) intel(0): Creating default Display subsection in Screen section
        "Default Screen Section" for depth/fbbpp 24/32
[539692.581] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[539692.581] (==) intel(0): RGB weight 888
[539692.581] (==) intel(0): Default visual is TrueColor
[539692.582] (II) intel(0): Output eDP1 has no monitor section
[539692.582] (**) intel(0): Found backlight control interface intel_backlight (type 'raw') for output eDP1
[539692.582] (II) intel(0): Enabled output eDP1
[539692.582] (II) intel(0): Output DP1 has no monitor section
[539692.582] (II) intel(0): Enabled output DP1
[539692.582] (II) intel(0): Output DP2 has no monitor section
[539692.582] (II) intel(0): Enabled output DP2
[539692.582] (--) intel(0): Using a maximum size of 256x256 for hardware cursors
[539692.582] (II) intel(0): Output VIRTUAL1 has no monitor section
[539692.582] (II) intel(0): Enabled output VIRTUAL1
[539692.582] (--) intel(0): Output eDP1 using initial mode 3840x2160 on pipe 0
[539692.582] (==) intel(0): TearFree disabled
[539692.582] (==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
[539692.582] (==) intel(0): DPI set to (96, 96)
[539692.582] (II) Loading sub module "dri3"
[539692.582] (II) LoadModule: "dri3"
[539692.582] (II) Module "dri3" already built-in
[539692.582] (II) Loading sub module "dri2"
[539692.582] (II) LoadModule: "dri2"
[539692.582] (II) Module "dri2" already built-in
[539692.582] (II) Loading sub module "present"
[539692.582] (II) LoadModule: "present"
[539692.582] (II) Module "present" already built-in
[539692.582] (II) UnloadModule: "fbdev"
[539692.582] (II) Unloading fbdev
[539692.582] (II) UnloadSubModule: "fbdevhw"
[539692.582] (II) Unloading fbdevhw
[539692.582] (II) UnloadModule: "vesa"
[539692.582] (II) Unloading vesa
[539692.582] (==) Depth 24 pixmap format is 32 bpp
[539692.583] (II) intel(0): SNA initialized with Skylake (gen9) backend
[539692.583] (==) intel(0): Backing store enabled
[539692.583] (==) intel(0): Silken mouse enabled
[539692.583] (II) intel(0): HW Cursor enabled
[539692.583] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[539692.583] (==) intel(0): DPMS enabled
[539692.583] (==) intel(0): Display hotplug detection enabled
[539692.583] (II) intel(0): [DRI2] Setup complete
[539692.583] (II) intel(0): [DRI2]   DRI driver: i965
[539692.583] (II) intel(0): [DRI2]   VDPAU driver: va_gl
[539692.583] (II) intel(0): direct rendering: DRI2 DRI3 enabled
[539692.583] (II) intel(0): hardware support for Present enabled
[539692.583] (--) RandR disabled
[539692.592] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[539692.592] (II) AIGLX: enabled GLX_ARB_create_context
[539692.592] (II) AIGLX: enabled GLX_ARB_create_context_profile
[539692.592] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[539692.592] (II) AIGLX: enabled GLX_INTEL_swap_event
[539692.592] (II) AIGLX: enabled GLX_SGI_swap_control
[539692.592] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[539692.592] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[539692.592] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[539692.592] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[539692.592] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[539692.592] (II) AIGLX: Loaded and initialized i965
[539692.592] (II) GLX: Initialized DRI2 GL provider for screen 0
[539692.599] (II) intel(0): switch to mode 3840x2160@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
[539692.609] (II) intel(0): Setting screen physical size to 1016 x 571
[539692.658] (II) config/udev: Adding input device Power Button (/dev/input/event6)
[539692.658] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[539692.658] (II) LoadModule: "libinput"
[539692.658] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[539692.658] (II) Module libinput: vendor="X.Org Foundation"
[539692.658] compiled for 1.19.2, module version = 0.25.0
[539692.658] Module class: X.Org XInput Driver
[539692.658] ABI class: X.Org XInput driver, version 24.1
[539692.658] (II) Using input driver 'libinput' for 'Power Button'
[539692.658] (**) Power Button: always reports core events
[539692.658] (**) Option "Device" "/dev/input/event6"
[539692.658] (**) Option "_source" "server/udev"
[539692.659] (II) input device 'Power Button', /dev/input/event6 is tagged by udev as: Keyboard
[539692.659] (II) input device 'Power Button', /dev/input/event6 is a keyboard
[539692.682] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event6"
[539692.683] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[539692.683] (II) input device 'Power Button', /dev/input/event6 is tagged by udev as: Keyboard
[539692.683] (II) input device 'Power Button', /dev/input/event6 is a keyboard
[539692.683] (II) config/udev: Adding input device Video Bus (/dev/input/event10)
[539692.683] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[539692.683] (II) Using input driver 'libinput' for 'Video Bus'
[539692.683] (**) Video Bus: always reports core events
[539692.683] (**) Option "Device" "/dev/input/event10"
[539692.683] (**) Option "_source" "server/udev"
[539692.683] (II) input device 'Video Bus', /dev/input/event10 is tagged by udev as: Keyboard
[539692.683] (II) input device 'Video Bus', /dev/input/event10 is a keyboard
[539692.702] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10/event10"
[539692.702] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[539692.703] (II) input device 'Video Bus', /dev/input/event10 is tagged by udev as: Keyboard
[539692.703] (II) input device 'Video Bus', /dev/input/event10 is a keyboard
[539692.703] (II) config/udev: Adding input device Video Bus (/dev/input/event11)
[539692.703] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[539692.704] (II) Using input driver 'libinput' for 'Video Bus'
[539692.704] (**) Video Bus: always reports core events
[539692.704] (**) Option "Device" "/dev/input/event11"
[539692.704] (**) Option "_source" "server/udev"
[539692.704] (II) input device 'Video Bus', /dev/input/event11 is tagged by udev as: Keyboard
[539692.704] (II) input device 'Video Bus', /dev/input/event11 is a keyboard
[539692.723] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:38/LNXVIDEO:01/input/input11/event11"
[539692.723] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
[539692.724] (II) input device 'Video Bus', /dev/input/event11 is tagged by udev as: Keyboard
[539692.724] (II) input device 'Video Bus', /dev/input/event11 is a keyboard
[539692.725] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[539692.725] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[539692.725] (II) Using input driver 'libinput' for 'Power Button'
[539692.725] (**) Power Button: always reports core events
[539692.725] (**) Option "Device" "/dev/input/event3"
[539692.725] (**) Option "_source" "server/udev"
[539692.726] (II) input device 'Power Button', /dev/input/event3 is tagged by udev as: Keyboard
[539692.726] (II) input device 'Power Button', /dev/input/event3 is a keyboard
[539692.753] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3/event3"
[539692.753] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 9)
[539692.754] (II) input device 'Power Button', /dev/input/event3 is tagged by udev as: Keyboard
[539692.754] (II) input device 'Power Button', /dev/input/event3 is a keyboard
[539692.755] (II) config/udev: Adding input device Lid Switch (/dev/input/event5)
[539692.755] (II) No input driver specified, ignoring this device.
[539692.755] (II) This device may have been added with another device file.
[539692.756] (II) config/udev: Adding input device Sleep Button (/dev/input/event1)
[539692.756] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[539692.756] (II) Using input driver 'libinput' for 'Sleep Button'
[539692.756] (**) Sleep Button: always reports core events
[539692.756] (**) Option "Device" "/dev/input/event1"
[539692.756] (**) Option "_source" "server/udev"
[539692.757] (II) input device 'Sleep Button', /dev/input/event1 is tagged by udev as: Keyboard
[539692.757] (II) input device 'Sleep Button', /dev/input/event1 is a keyboard
[539692.783] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1/event1"
[539692.783] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 10)
[539692.784] (II) input device 'Sleep Button', /dev/input/event1 is tagged by udev as: Keyboard
[539692.784] (II) input device 'Sleep Button', /dev/input/event1 is a keyboard
[539692.786] (II) config/udev: Adding input device USB Camera (/dev/input/event17)
[539692.786] (**) USB Camera: Applying InputClass "libinput keyboard catchall"
[539692.786] (II) Using input driver 'libinput' for 'USB Camera'
[539692.786] (**) USB Camera: always reports core events
[539692.786] (**) Option "Device" "/dev/input/event17"
[539692.787] (**) Option "_source" "server/udev"
[539692.788] (II) input device 'USB Camera', /dev/input/event17 is tagged by udev as: Keyboard
[539692.788] (II) input device 'USB Camera', /dev/input/event17 is a keyboard
[539692.843] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input17/event17"
[539692.843] (II) XINPUT: Adding extended input device "USB Camera" (type: KEYBOARD, id 11)
[539692.844] (II) input device 'USB Camera', /dev/input/event17 is tagged by udev as: Keyboard
[539692.844] (II) input device 'USB Camera', /dev/input/event17 is a keyboard
[539692.846] (II) config/udev: Adding input device Wacom MobileStudio Pro 16 Pen (/dev/input/event19)
[539692.846] (**) Wacom MobileStudio Pro 16 Pen: Applying InputClass "libinput tablet catchall"
[539692.846] (**) Wacom MobileStudio Pro 16 Pen: Applying InputClass "Wacom USB tablet class"
[539692.846] (**) Wacom MobileStudio Pro 16 Pen: Applying InputClass "Wacom tablet class"
[539692.846] (II) LoadModule: "wacom"
[539692.847] (II) Loading /usr/lib/xorg/modules/input/wacom_drv.so
[539692.847] (II) Module wacom: vendor="X.Org Foundation"
[539692.847] compiled for 1.19.2, module version = 0.34.2
[539692.847] Module class: X.Org XInput Driver
[539692.847] ABI class: X.Org XInput driver, version 24.1
[539692.847] (II) wacom: Driver for Wacom graphics tablets: PenPartner, Graphire,
        Graphire2 4x5, Graphire2 5x7, Graphire3 4x5, Graphire3 6x8,
        Graphire4 4x5, Graphire4 6x8, BambooFun 4x5, BambooFun 6x8,
        Bamboo1 Medium, Graphire4 6x8 BlueTooth, CTL-460, CTH-461, CTL-660,
        CTL-461/S, Bamboo Touch, CTH-460/K, CTH-461/S, CTH-661/S1, CTH-461/L,
        CTH-661/L, Intuos 4x5, Intuos 6x8, Intuos 9x12, Intuos 12x12,
        Intuos 12x18, PTU600, PL400, PL500, PL600, PL600SX, PL550, PL800,
        PL700, PL510, PL710, DTI520, DTF720, DTF720a, DTF521, DTU1931,
        DTU2231, DTU1631, Intuos2 4x5, Intuos2 6x8, Intuos2 9x12,
        Intuos2 12x12, Intuos2 12x18, Intuos2 6x8 , Volito, PenStation,
        Volito2 4x5, Volito2 2x3, PenPartner2, Bamboo, Bamboo1, Bamboo1 4x6,
        Bamboo1 5x8, Intuos3 4x5, Intuos3 6x8, Intuos3 9x12, Intuos3 12x12,
        Intuos3 12x19, Intuos3 6x11, Intuos3 4x6, Intuos4 4x6, Intuos4 6x9,
        Intuos4 8x13, Intuos4 12x19, Intuos4 WL USB Endpoint,
        Intuos4 WL Bluetooth Endpoint, Intuos5 touch S, Intuos5 touch M,
        Intuos5 touch L, Intuos5 S, Intuos5 M, Intuos Pro S, Intuos Pro M,
        Intuos Pro L, Cintiq 21UX, Cintiq 20WSX, Cintiq 12WX, Cintiq 21UX2,
        Cintiq 24HD, Cintiq 22HD, Cintiq 24HD touch (EMR digitizer),
        Cintiq 13HD, DTK2241, DTH2242, Cintiq 22HDT, TabletPC 0x90,
        TabletPC 0x93, TabletPC 0x97, TabletPC 0x9A, CapPlus  0x9F,
        TabletPC 0xE2, TabletPC 0xE3, TabletPC 0xE5, TabletPC 0xE6,
        TabletPC 0xEC, TabletPC 0xED, TabletPC 0xEF, TabletPC 0x100,
        TabletPC 0x101, TabletPC 0x10D, TabletPC 0x116, TabletPC 0x12C,
        TabletPC 0x4001, TabletPC 0x4004, TabletPC 0x5000, TabletPC 0x5002,
        usb:172f:0024, usb:172f:0025, usb:172f:0026, usb:172f:0027,
        usb:172f:0028, usb:172f:0030, usb:172f:0031, usb:172f:0032,
        usb:172f:0033, usb:172f:0034, usb:172f:0035, usb:172f:0036,
        usb:172f:0037, usb:172f:0038, usb:172f:0039, usb:172f:0051,
        usb:172f:0052, usb:172f:0053, usb:172f:0054, usb:172f:0055,
        usb:172f:0056, usb:172f:0057, usb:172f:0058, usb:172f:0500,
        usb:172f:0501, usb:172f:0502, usb:172f:0503, usb:1b96:0001,
        usb:17ef:6004
[539692.850] (II) Using input driver 'wacom' for 'Wacom MobileStudio Pro 16 Pen'
[539692.850] (**) Wacom MobileStudio Pro 16 Pen: always reports core events
[539692.850] (**) Option "Device" "/dev/input/event19"
[539692.906] (II) Wacom MobileStudio Pro 16 Pen: type not specified, assuming 'stylus'.
[539692.906] (II) Wacom MobileStudio Pro 16 Pen: other types will be automatically added.
[539692.906] (--) Wacom MobileStudio Pro 16 Pen stylus: using pressure threshold of 873 for button 1
[539692.906] (--) Wacom MobileStudio Pro 16 Pen stylus: maxX=69520 maxY=39280 maxZ=8191 resX=200000 resY=200000  tilt=enabled
[539692.906] (II) Wacom MobileStudio Pro 16 Pen stylus: hotplugging dependent devices.
[539692.906] (EE) Wacom MobileStudio Pro 16 Pen stylus: Invalid type 'touch' for this device.
[539692.906] (EE) Wacom MobileStudio Pro 16 Pen stylus: Invalid type 'pad' for this device.
[539692.906] (II) Wacom MobileStudio Pro 16 Pen stylus: hotplugging completed.
[539692.953] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.1/1-6.1:1.0/0003:056A:034E.000D/input/input21/event19"
[539692.953] (II) XINPUT: Adding extended input device "Wacom MobileStudio Pro 16 Pen stylus" (type: STYLUS, id 12)
[539692.953] (**) Wacom MobileStudio Pro 16 Pen stylus: (accel) keeping acceleration scheme 1
[539692.953] (**) Wacom MobileStudio Pro 16 Pen stylus: (accel) acceleration profile 0
[539692.954] (**) Wacom MobileStudio Pro 16 Pen stylus: (accel) acceleration factor: 2.000
[539692.954] (**) Wacom MobileStudio Pro 16 Pen stylus: (accel) acceleration threshold: 4
[539693.011] (II) config/udev: Adding input device Wacom MobileStudio Pro 16 Pen (/dev/input/mouse2)
[539693.011] (II) No input driver specified, ignoring this device.
[539693.011] (II) This device may have been added with another device file.
[539693.013] (II) config/udev: Adding input device Wacom MobileStudio Pro 16 Pad (/dev/input/event20)
[539693.013] (**) Wacom MobileStudio Pro 16 Pad: Applying InputClass "libinput tablet catchall"
[539693.013] (**) Wacom MobileStudio Pro 16 Pad: Applying InputClass "Wacom USB tablet class"
[539693.013] (**) Wacom MobileStudio Pro 16 Pad: Applying InputClass "Wacom tablet class"
[539693.013] (II) Using input driver 'wacom' for 'Wacom MobileStudio Pro 16 Pad'
[539693.013] (**) Wacom MobileStudio Pro 16 Pad: always reports core events
[539693.013] (**) Option "Device" "/dev/input/event20"
[539693.013] (EE) Wacom MobileStudio Pro 16 Pad: Invalid type 'stylus' for this device.
[539693.013] (EE) Wacom MobileStudio Pro 16 Pad: Invalid type 'eraser' for this device.
[539693.013] (EE) Wacom MobileStudio Pro 16 Pad: Invalid type 'cursor' for this device.
[539693.013] (EE) Wacom MobileStudio Pro 16 Pad: Invalid type 'touch' for this device.
[539693.013] (II) Wacom MobileStudio Pro 16 Pad: type not specified, assuming 'pad'.
[539693.013] (II) Wacom MobileStudio Pro 16 Pad: other types will be automatically added.
[539693.013] (II) Wacom MobileStudio Pro 16 Pad pad: hotplugging dependent devices.
[539693.014] (EE) Wacom MobileStudio Pro 16 Pad pad: Invalid type 'stylus' for this device.
[539693.014] (EE) Wacom MobileStudio Pro 16 Pad pad: Invalid type 'eraser' for this device.
[539693.014] (EE) Wacom MobileStudio Pro 16 Pad pad: Invalid type 'cursor' for this device.
[539693.014] (EE) Wacom MobileStudio Pro 16 Pad pad: Invalid type 'touch' for this device.
[539693.014] (II) Wacom MobileStudio Pro 16 Pad pad: hotplugging completed.
[539693.072] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.1/1-6.1:1.0/0003:056A:034E.000D/input/input23/event20"
[539693.073] (II) XINPUT: Adding extended input device "Wacom MobileStudio Pro 16 Pad pad" (type: PAD, id 13)
[539693.073] (**) Wacom MobileStudio Pro 16 Pad pad: (accel) keeping acceleration scheme 1
[539693.074] (**) Wacom MobileStudio Pro 16 Pad pad: (accel) acceleration profile 0
[539693.074] (**) Wacom MobileStudio Pro 16 Pad pad: (accel) acceleration factor: 2.000
[539693.074] (**) Wacom MobileStudio Pro 16 Pad pad: (accel) acceleration threshold: 4
[539693.075] (II) config/udev: Adding input device Wacom MobileStudio Pro 16 Pad (/dev/input/js0)
[539693.075] (II) No input driver specified, ignoring this device.
[539693.075] (II) This device may have been added with another device file.
[539693.077] (II) config/udev: Adding input device Wacom MobileStudio Pro 16 Touch Finger (/dev/input/event18)
[539693.077] (**) Wacom MobileStudio Pro 16 Touch Finger: Applying InputClass "libinput touchscreen catchall"
[539693.077] (**) Wacom MobileStudio Pro 16 Touch Finger: Applying InputClass "Wacom USB touchscreen class"
[539693.077] (**) Wacom MobileStudio Pro 16 Touch Finger: Applying InputClass "Wacom touchscreen class"
[539693.077] (II) Using input driver 'wacom' for 'Wacom MobileStudio Pro 16 Touch Finger'
[539693.077] (**) Wacom MobileStudio Pro 16 Touch Finger: always reports core events
[539693.077] (**) Option "Device" "/dev/input/event18"
[539693.133] (EE) Wacom MobileStudio Pro 16 Touch Finger: Invalid type 'stylus' for this device.
[539693.133] (EE) Wacom MobileStudio Pro 16 Touch Finger: Invalid type 'eraser' for this device.
[539693.133] (EE) Wacom MobileStudio Pro 16 Touch Finger: Invalid type 'cursor' for this device.
[539693.133] (II) Wacom MobileStudio Pro 16 Touch Finger: type not specified, assuming 'touch'.
[539693.133] (II) Wacom MobileStudio Pro 16 Touch Finger: other types will be automatically added.
[539693.133] (--) Wacom MobileStudio Pro 16 Touch Finger touch: maxX=13824 maxY=7776 maxZ=0 resX=40000 resY=40000
[539693.133] (II) Wacom MobileStudio Pro 16 Touch Finger touch: hotplugging dependent devices.
[539693.133] (EE) Wacom MobileStudio Pro 16 Touch Finger touch: Invalid type 'stylus' for this device.
[539693.133] (EE) Wacom MobileStudio Pro 16 Touch Finger touch: Invalid type 'eraser' for this device.
[539693.133] (EE) Wacom MobileStudio Pro 16 Touch Finger touch: Invalid type 'cursor' for this device.
[539693.133] (EE) Wacom MobileStudio Pro 16 Touch Finger touch: Invalid type 'pad' for this device.
[539693.133] (II) Wacom MobileStudio Pro 16 Touch Finger touch: hotplugging completed.
[539693.179] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.3/1-6.3:1.0/0003:056A:034B.000E/input/input25/event18"
[539693.179] (II) XINPUT: Adding extended input device "Wacom MobileStudio Pro 16 Touch Finger touch" (type: TOUCH, id 14)
[539693.180] (**) Wacom MobileStudio Pro 16 Touch Finger touch: (accel) keeping acceleration scheme 1
[539693.180] (**) Wacom MobileStudio Pro 16 Touch Finger touch: (accel) acceleration profile 0
[539693.180] (**) Wacom MobileStudio Pro 16 Touch Finger touch: (accel) acceleration factor: 2.000
[539693.180] (**) Wacom MobileStudio Pro 16 Touch Finger touch: (accel) acceleration threshold: 4
[539693.238] (II) config/udev: Adding input device Wacom MobileStudio Pro 16 Touch Finger (/dev/input/mouse1)
[539693.238] (II) No input driver specified, ignoring this device.
[539693.238] (II) This device may have been added with another device file.
[539693.239] (II) config/udev: Adding input device Intel RealSense 3D Camera R200 (/dev/input/event8)
[539693.239] (**) Intel RealSense 3D Camera R200: Applying InputClass "libinput keyboard catchall"
[539693.239] (II) Using input driver 'libinput' for 'Intel RealSense 3D Camera R200'
[539693.239] (**) Intel RealSense 3D Camera R200: always reports core events
[539693.239] (**) Option "Device" "/dev/input/event8"
[539693.239] (**) Option "_source" "server/udev"
[539693.241] (II) input device 'Intel RealSense 3D Camera R200', /dev/input/event8 is tagged by udev as: Keyboard
[539693.241] (II) input device 'Intel RealSense 3D Camera R200', /dev/input/event8 is a keyboard
[539693.283] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4:1.2/input/input8/event8"
[539693.283] (II) XINPUT: Adding extended input device "Intel RealSense 3D Camera R200" (type: KEYBOARD, id 15)
[539693.284] (II) input device 'Intel RealSense 3D Camera R200', /dev/input/event8 is tagged by udev as: Keyboard
[539693.285] (II) input device 'Intel RealSense 3D Camera R200', /dev/input/event8 is a keyboard
[539693.286] (II) config/udev: Adding input device Intel RealSense 3D Camera R200 (/dev/input/event9)
[539693.286] (**) Intel RealSense 3D Camera R200: Applying InputClass "libinput keyboard catchall"
[539693.286] (II) Using input driver 'libinput' for 'Intel RealSense 3D Camera R200'
[539693.286] (**) Intel RealSense 3D Camera R200: always reports core events
[539693.286] (**) Option "Device" "/dev/input/event9"
[539693.286] (**) Option "_source" "server/udev"
[539693.287] (II) input device 'Intel RealSense 3D Camera R200', /dev/input/event9 is tagged by udev as: Keyboard
[539693.287] (II) input device 'Intel RealSense 3D Camera R200', /dev/input/event9 is a keyboard
[539693.332] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4:1.4/input/input9/event9"
[539693.333] (II) XINPUT: Adding extended input device "Intel RealSense 3D Camera R200" (type: KEYBOARD, id 16)
[539693.334] (II) input device 'Intel RealSense 3D Camera R200', /dev/input/event9 is tagged by udev as: Keyboard
[539693.334] (II) input device 'Intel RealSense 3D Camera R200', /dev/input/event9 is a keyboard
[539693.337] (II) config/udev: Adding input device Lenovo ThinkPad Compact USB Keyboard with TrackPoint (/dev/input/event0)
[539693.337] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: Applying InputClass "libinput keyboard catchall"
[539693.337] (II) Using input driver 'libinput' for 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint'
[539693.337] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: always reports core events
[539693.337] (**) Option "Device" "/dev/input/event0"
[539693.337] (**) Option "_source" "server/udev"
[539693.338] (II) input device 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint', /dev/input/event0 is tagged by udev as: Keyboard
[539693.338] (II) input device 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint', /dev/input/event0 is a keyboard
[539693.363] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/0000:03:00.0/usb3/3-2/3-2:1.0/0003:17EF:6047.0001/input/input0/event0"
[539693.363] (II) XINPUT: Adding extended input device "Lenovo ThinkPad Compact USB Keyboard with TrackPoint" (type: KEYBOARD, id 17)
[539693.365] (II) input device 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint', /dev/input/event0 is tagged by udev as: Keyboard
[539693.365] (II) input device 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint', /dev/input/event0 is a keyboard
[539693.367] (II) config/udev: Adding input device Lenovo ThinkPad Compact USB Keyboard with TrackPoint (/dev/input/event4)
[539693.367] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: Applying InputClass "libinput pointer catchall"
[539693.367] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: Applying InputClass "libinput keyboard catchall"
[539693.367] (II) Using input driver 'libinput' for 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint'
[539693.367] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: always reports core events
[539693.367] (**) Option "Device" "/dev/input/event4"
[539693.367] (**) Option "_source" "server/udev"
[539693.368] (II) input device 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint', /dev/input/event4 is tagged by udev as: Keyboard Mouse Pointingstick
[539693.369] (II) input device 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint', /dev/input/event4 is a pointer caps
[539693.369] (II) input device 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint', /dev/input/event4 is a keyboard
[539693.426] (II) libinput: Lenovo ThinkPad Compact USB Keyboard with TrackPoint: needs a virtual subdevice
[539693.426] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/0000:03:00.0/usb3/3-2/3-2:1.1/0003:17EF:6047.0002/input/input4/event4"
[539693.426] (II) XINPUT: Adding extended input device "Lenovo ThinkPad Compact USB Keyboard with TrackPoint" (type: MOUSE, id 18)
[539693.427] (**) Option "AccelerationScheme" "none"
[539693.427] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: (accel) selected scheme none/0
[539693.427] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: (accel) acceleration factor: 2.000
[539693.427] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: (accel) acceleration threshold: 4
[539693.429] (II) input device 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint', /dev/input/event4 is tagged by udev as: Keyboard Mouse Pointingstick
[539693.429] (II) input device 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint', /dev/input/event4 is a pointer caps
[539693.429] (II) input device 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint', /dev/input/event4 is a keyboard
[539693.430] (II) config/udev: Adding input device Lenovo ThinkPad Compact USB Keyboard with TrackPoint (/dev/input/mouse0)
[539693.430] (II) No input driver specified, ignoring this device.
[539693.431] (II) This device may have been added with another device file.
[539693.432] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event12)
[539693.432] (II) No input driver specified, ignoring this device.
[539693.432] (II) This device may have been added with another device file.
[539693.433] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event13)
[539693.433] (II) No input driver specified, ignoring this device.
[539693.433] (II) This device may have been added with another device file.
[539693.433] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event14)
[539693.433] (II) No input driver specified, ignoring this device.
[539693.433] (II) This device may have been added with another device file.
[539693.434] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event15)
[539693.434] (II) No input driver specified, ignoring this device.
[539693.434] (II) This device may have been added with another device file.
[539693.435] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event16)
[539693.435] (II) No input driver specified, ignoring this device.
[539693.435] (II) This device may have been added with another device file.
[539693.436] (II) config/udev: Adding input device Intel HID events (/dev/input/event2)
[539693.436] (**) Intel HID events: Applying InputClass "libinput keyboard catchall"
[539693.436] (II) Using input driver 'libinput' for 'Intel HID events'
[539693.436] (**) Intel HID events: always reports core events
[539693.436] (**) Option "Device" "/dev/input/event2"
[539693.436] (**) Option "_source" "server/udev"
[539693.437] (II) input device 'Intel HID events', /dev/input/event2 is tagged by udev as: Keyboard
[539693.437] (II) input device 'Intel HID events', /dev/input/event2 is a keyboard
[539693.456] (**) Option "config_info" "udev:/sys/devices/platform/INT33D5:00/input/input2/event2"
[539693.456] (II) XINPUT: Adding extended input device "Intel HID events" (type: KEYBOARD, id 19)
[539693.458] (II) input device 'Intel HID events', /dev/input/event2 is tagged by udev as: Keyboard
[539693.458] (II) input device 'Intel HID events', /dev/input/event2 is a keyboard
[539693.459] (II) config/udev: Adding input device PC Speaker (/dev/input/event7)
[539693.459] (II) No input driver specified, ignoring this device.
[539693.459] (II) This device may have been added with another device file.
[539693.493] (**) Wacom MobileStudio Pro 16 Pen eraser: Applying InputClass "libinput tablet catchall"
[539693.493] (**) Wacom MobileStudio Pro 16 Pen eraser: Applying InputClass "Wacom USB tablet class"
[539693.493] (**) Wacom MobileStudio Pro 16 Pen eraser: Applying InputClass "Wacom tablet class"
[539693.493] (II) Using input driver 'wacom' for 'Wacom MobileStudio Pro 16 Pen eraser'
[539693.493] (**) Wacom MobileStudio Pro 16 Pen eraser: always reports core events
[539693.493] (**) Option "Device" "/dev/input/event19"
[539693.493] (**) Option "Type" "eraser"
[539693.494] (--) Wacom MobileStudio Pro 16 Pen eraser: maxX=69520 maxY=39280 maxZ=8191 resX=200000 resY=200000  tilt=enabled
[539693.509] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.1/1-6.1:1.0/0003:056A:034E.000D/input/input21/event19"
[539693.509] (II) XINPUT: Adding extended input device "Wacom MobileStudio Pro 16 Pen eraser" (type: ERASER, id 20)
[539693.510] (**) Wacom MobileStudio Pro 16 Pen eraser: (accel) keeping acceleration scheme 1
[539693.510] (**) Wacom MobileStudio Pro 16 Pen eraser: (accel) acceleration profile 0
[539693.510] (**) Wacom MobileStudio Pro 16 Pen eraser: (accel) acceleration factor: 2.000
[539693.510] (**) Wacom MobileStudio Pro 16 Pen eraser: (accel) acceleration threshold: 4
[539693.510] (**) Wacom MobileStudio Pro 16 Pen cursor: Applying InputClass "libinput tablet catchall"
[539693.510] (**) Wacom MobileStudio Pro 16 Pen cursor: Applying InputClass "Wacom USB tablet class"
[539693.510] (**) Wacom MobileStudio Pro 16 Pen cursor: Applying InputClass "Wacom tablet class"
[539693.510] (II) Using input driver 'wacom' for 'Wacom MobileStudio Pro 16 Pen cursor'
[539693.510] (**) Wacom MobileStudio Pro 16 Pen cursor: always reports core events
[539693.510] (**) Option "Device" "/dev/input/event19"
[539693.511] (**) Option "Type" "cursor"
[539693.529] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.1/1-6.1:1.0/0003:056A:034E.000D/input/input21/event19"
[539693.529] (II) XINPUT: Adding extended input device "Wacom MobileStudio Pro 16 Pen cursor" (type: CURSOR, id 21)
[539693.530] (**) Wacom MobileStudio Pro 16 Pen cursor: (accel) keeping acceleration scheme 1
[539693.530] (**) Wacom MobileStudio Pro 16 Pen cursor: (accel) acceleration profile 0
[539693.530] (**) Wacom MobileStudio Pro 16 Pen cursor: (accel) acceleration factor: 2.000
[539693.530] (**) Wacom MobileStudio Pro 16 Pen cursor: (accel) acceleration threshold: 4
[539693.530] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: Applying InputClass "libinput pointer catchall"
[539693.530] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: Applying InputClass "libinput keyboard catchall"
[539693.530] (II) Using input driver 'libinput' for 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint'
[539693.530] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: always reports core events
[539693.530] (**) Option "Device" "/dev/input/event4"
[539693.531] (**) Option "_source" "_driver/libinput"
[539693.531] (II) libinput: Lenovo ThinkPad Compact USB Keyboard with TrackPoint: is a virtual subdevice
[539693.531] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/0000:03:00.0/usb3/3-2/3-2:1.1/0003:17EF:6047.0002/input/input4/event4"
[539693.531] (II) XINPUT: Adding extended input device "Lenovo ThinkPad Compact USB Keyboard with TrackPoint" (type: KEYBOARD, id 22)
[539693.628] (II) intel(0): EDID vendor "WAC", prod id 4179
[539693.628] (II) intel(0): Using EDID range info for horizontal sync
[539693.628] (II) intel(0): Using EDID range info for vertical refresh
[539693.628] (II) intel(0): Printing DDC gathered Modelines:
[539693.628] (II) intel(0): Modeline "3840x2160"x0.0  533.25  3840 3888 3920 4000  2160 2163 2168 2222 +hsync -vsync (133.3 kHz eP)
[539693.628] (II) intel(0): Modeline "3840x2160"x0.0  594.00  3840 4016 4104 4400  2160 2168 2178 2250 +hsync +vsync (135.0 kHz e)
[539693.628] (II) intel(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[539693.628] (II) intel(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[539693.628] (II) intel(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[539693.628] (II) intel(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248 2576  1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[539693.628] (II) intel(0): Modeline "1680x1050"x0.0  146.25  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
[539693.628] (II) intel(0): Modeline "1600x900"x60.0  119.00  1600 1696 1864 2128  900 901 904 932 -hsync +vsync (55.9 kHz e)
[539693.628] (II) intel(0): Modeline "1440x900"x0.0  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz e)
[539693.628] (II) intel(0): Modeline "1400x1050"x0.0  121.75  1400 1488 1632 1864  1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[539693.628] (II) intel(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[539693.628] (II) intel(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
[539693.628] (II) intel(0): Modeline "1280x720"x60.0   74.48  1280 1336 1472 1664  720 721 724 746 -hsync +vsync (44.8 kHz e)


Jason Gerecke <[hidden email]> writes:

> Glad to hear that it's showing signs of life again :)
>
> I still wonder why the nVidia driver isn't working properly though. The
> backlight turning off (as mentioned in your other message) is definitely
> a bit suspicious. Would you mind posting your Xorg.0.log again for
> comparison to the broken one? It'd be interesting to see if the current
> driver also detects/uses the "extra" modeline.
>
> Jason
> ---
> Now instead of four in the eights place /
> you’ve got three, ‘Cause you added one /
> (That is to say, eight) to the two, /
> But you can’t take seven from three, /
> So you look at the sixty-fours....
>
> On 03/29/2017 05:04 PM, [hidden email] wrote:
>>
>> I have libglvnd.
>>
>> I deinstalled nvidia and nvidia utils.
>> When I run xinitrc with an exec xterm -maximized
>> I get a terminal.
>>
>> Doing a startxfce4 also works. Next I'll have to refresh my xmonad
>> and try that.
>>
>> I'm pretty sure I tried running without the nvidia packages after you
>> said it should work without them, but maybe I had something else wrong
>> at the time.
>>
>> It's weird that those drivers are causing a problem, they should be
>> unloaded.
>>
>> The stylus is working too, which is what started me on this path.
>>
>> Thank you for your help!  I had tried so many things I think I just
>> needed someone else to talk some sense with me. It's really hard to
>> do these things without others for feedback and critical thinking.
>>
>> I can't say how many times I've found a bug just by describing the
>> problem to someone.
>>
>> Thank you. I'm very appreciative.
>>
>> Eric
>>
>>
>> Jason Gerecke <[hidden email]> writes:
>>
>>> Oh, another quick question while I'm thinking about it:
>>>
>>> Do you have the 'libglvnd' package installed, or are you using another
>>> package to provide libgl?
>>>
>>> On 03/29/2017 04:15 PM, Jason Gerecke wrote:
>>>> Huh, that's an interesting observation. Lets try removing the nVidia
>>>> graphics drivers (`pacman -Rs nvidia nvidia-utils`) and see if the
>>>> open-source drivers work differently. If there's no change, figure out
>>>> what package installed the legacy nv driver (`pacman -Qo
>>>> /usr/lib/xorg/modules/drivers/nv_drv.so` should give its name) and
>>>> remove it too. If that *still* doesn't work, remove the
>>>> xf86-video-nouveau package as well (which should hopefully have X try to
>>>> use the Intel drivers).
>>>>
>>>> Jason
>>>> ---
>>>> Now instead of four in the eights place /
>>>> you’ve got three, ‘Cause you added one /
>>>> (That is to say, eight) to the two, /
>>>> But you can’t take seven from three, /
>>>> So you look at the sixty-fours....
>>>>
>>>> On 03/29/2017 04:00 PM, [hidden email] wrote:
>>>>>
>>>>> Yes, I had added Option "DPI" "96 x 96" to the 10-nvidia conf file
>>>>> during that run. But I have done it both ways with no changes.
>>>>>
>>>>> At one point I tried using the nvidia generated xorg.conf.  That results
>>>>> in what appears to be about 10 pixels being lit up in a row in the upper
>>>>> left corner of the screen. But I removed that conf file.
>>>>>
>>>>> Thanks for looking at this.
>>>>>
>>>>> Eric
>>>>>
>>>>>
>>>>> Jason Gerecke <[hidden email]> writes:
>>>>>
>>>>>> Thanks for the log. It looks pretty similar to what I see on my system,
>>>>>> except for the presence of a few more video drivers (though only
>>>>>> 'nvidia' ends up getting used) and your system's obvious lack of
>>>>>> systemd-logind. I tried installing the nvidia package to see if maybe it
>>>>>> was the source of the problem, but it still seems to work fine.
>>>>>>
>>>>>> I do notice that your system uses slightly different monitor timings
>>>>>> than mine, but if the timings were wrong I'd expect the display to go to
>>>>>> sleep (and turn off the backlight) rather than just render nothing.
>>>>>>
>>>>>> Finally, I also see that the X server is getting a DPI value of 96 from
>>>>>> somewhere. On my system it says that it can't find the screen's DPI and
>>>>>> so it falls back to 75. While the DPI itself isn't going to change
>>>>>> anything, it might indicate the presence of X configuration files that
>>>>>> are modifying its behavior in ways not captured by the log. Do you have
>>>>>> any files under /etc/X11/xorg.conf.d or have you edited any files under
>>>>>> /usr/share/X11/xorg.conf.d?
>>>>>>
>>>>>> Jason
>>>>>> ---
>>>>>> Now instead of four in the eights place /
>>>>>> you’ve got three, ‘Cause you added one /
>>>>>> (That is to say, eight) to the two, /
>>>>>> But you can’t take seven from three, /
>>>>>> So you look at the sixty-fours....
>>>>>>
>>>>>> On 03/29/2017 06:47 AM, [hidden email] wrote:
>>>>>>>
>>>>>>> I'm wondering if I shouldn't start over with a fresh install again. But
>>>>>>> maybe this will reveal something.  Here is my log.
>>>>>>>
>>>>>> [snip]
>>>>>>>
>>>>>>> Jason Gerecke <[hidden email]> writes:
>>>>>>>
>>>>>>>> I just gave Arch a whirl to see if a recent update broke something,
>>>>>>>> but even after rebooting from a fresh `pacman -Syu` I don't see any
>>>>>>>> problems on the MobileStudio Pro 16. Its using GDM by default, but
>>>>>>>> even when I switch to multi-user.target and run `startx
>>>>>>>> /usr/bin/xfce4-terminal` (I don't have the vanilla xterm installed)
>>>>>>>> manually I don't see any problems. No xorg.conf file either...
>>>>>>>>
>>>>>>>> Notable package versions (though if you upgraded, they should be identical...):
>>>>>>>>
>>>>>>>>  * core/linux 4.10.4-1
>>>>>>>>  * extra/xorg-server 1.19.3-1
>>>>>>>>  * extra/xf86-video-fbdev 0.4.4-6
>>>>>>>>  * extra/xf86-video-intel 1:2.99.917+767+g7e9e92c8-1
>>>>>>>>  * (No nouveau, nv, or nvidia graphics)
>>>>>>>>  * extra/mesa 17.0.1-2
>>>>>>>>
>>>>>>>> If you've got an Xorg.0.log, go ahead and attach it for me to review...
>>>>>>>>
>>>>>>>> Jason
>>>>>>>> ---
>>>>>>>> Now instead of four in the eights place /
>>>>>>>> you’ve got three, ‘Cause you added one  /
>>>>>>>> (That is to say, eight) to the two,     /
>>>>>>>> But you can’t take seven from three,    /
>>>>>>>> So you look at the sixty-fours....
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Mar 23, 2017 at 11:47 AM,  <[hidden email]> wrote:
>>>>>>>>>
>>>>>>>>> Using an xorg.conf file is the only way I know to change the behavior of
>>>>>>>>> xorg. Given that the display is what is not showing I cannot think of
>>>>>>>>> anything other than that the automatic configuration is not working.
>>>>>>>>>
>>>>>>>>> This setup worked perfectly (no stylus) before upgrading the kernel to
>>>>>>>>> 4.10 and Xorg to 1.19.3. I thought about downgrading xorg but that is a huge pain.
>>>>>>>>> Being on Arch I just did the usual pacman -Syy and pacman -Su. I thought
>>>>>>>>> I had screwed something up, but now I'm seeing the same behavior on a
>>>>>>>>> fresh install.
>>>>>>>>>
>>>>>>>>> Xmonad does not have any errors. I can replace it with twm,
>>>>>>>>> exec startxfce4 or exec xterm with the same effect. maximized xterm
>>>>>>>>> makes no difference.
>>>>>>>>>
>>>>>>>>> No matter what I do I get a black screen.  alt-ctrl-f1 brings me back to
>>>>>>>>> the console. When running the xterm typing 'exit' return will
>>>>>>>>> terminate the session.  with Xmonad shift-CMD-Q exits xmonad, etc.
>>>>>>>>>
>>>>>>>>> running xfce does give a few errors one of which is:
>>>>>>>>> Error opening /dev/dri/card0  permission denied
>>>>>>>>>
>>>>>>>>> I get this from xfsettings and xfwm4
>>>>>>>>> g_str_has_prefix: assertion 'prefix != NULL' failed
>>>>>>>>>
>>>>>>>>> This makes me wonder if there is a conflict with the two video cards the
>>>>>>>>> built in Intel and the nvidia.
>>>>>>>>>
>>>>>>>>> thanks,
>>>>>>>>>
>>>>>>>>> Eric
>>>>>>>>>
>>>>>>>>> Jason Gerecke <[hidden email]> writes:
>>>>>>>>>
>>>>>>>>>> Is there any particular reason you're using an xorg.conf file? That
>>>>>>>>>> should be completely unnecessary for most systems, and I didn't
>>>>>>>>>> require one when testing a MobileStudio Pro myself. (Note that I can
>>>>>>>>>> confirm that `Xorg :0 -configure` crashes, but it appears that's due
>>>>>>>>>> to a recently-introduced bug in the X server, not our driver. You
>>>>>>>>>> might consider filing a bug at https://bugzilla.freedesktop.org/ if
>>>>>>>>>> you rely on the option).
>>>>>>>>>>
>>>>>>>>>> I'm not familiar with Xmonad, but if it is starting up then I'd
>>>>>>>>>> suspect a problem with either: a) incorrect xmonad config, b)
>>>>>>>>>> incorrect xinitrc config, or c) missing software.
>>>>>>>>>>
>>>>>>>>>> As for "startx xterm", is that the literal command that you're
>>>>>>>>>> running? If you want to just start an xterm you'll need to provide the
>>>>>>>>>> full path (e.g. `startx /usr/bin/xterm`) or else startx will simply
>>>>>>>>>> pass "xterm" as a variable to your xinitrc script, where it will
>>>>>>>>>> (probably) be ignored. The pointer also won't be visible until its
>>>>>>>>>> moved over the xterm, so it may be advisable to use something like
>>>>>>>>>> `startx /usr/bin/xterm -maximized` to ensure the xterm takes up the
>>>>>>>>>> entire screen.
>>>>>>>>>>
>>>>>>>>>> Jason
>>>>>>>>>> ---
>>>>>>>>>> Now instead of four in the eights place /
>>>>>>>>>> you’ve got three, ‘Cause you added one  /
>>>>>>>>>> (That is to say, eight) to the two,     /
>>>>>>>>>> But you can’t take seven from three,    /
>>>>>>>>>> So you look at the sixty-fours....
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Mar 22, 2017 at 5:27 PM,  <[hidden email]> wrote:
>>>>>>>>>>>
>>>>>>>>>>> One thing leads to another. I decided to upgrade my install because 4.10
>>>>>>>>>>> is current. I've done this many times before, but somehow I screwed
>>>>>>>>>>> something up.
>>>>>>>>>>>
>>>>>>>>>>> I started over from scratch, which isn't too bad from where I was. But
>>>>>>>>>>> now I can't get Xorg working at all. The log looks good and it looks
>>>>>>>>>>> like wacom input is going to work. But all I get is a black screen with
>>>>>>>>>>> 'startx xterm' or a simple xinitrc with xmonad.
>>>>>>>>>>>
>>>>>>>>>>> Xmonad is working sort of. The only thing that works is shift-CMD-Q to
>>>>>>>>>>> exit. There are no xmonad.errors.
>>>>>>>>>>>
>>>>>>>>>>> Does anyone have a working xorg.conf for this machine ?  It seems like it
>>>>>>>>>>> worked out of the box before.  'Xorg :0 -configure' crashes now. which
>>>>>>>>>>> is what it seems that I did the last time.
>>>>>>>>>>>
>>>>>>>>>>> The only errors I'm getting are unable to load module 'nouveau' and 'nv'
>>>>>>>>>>> plus a few from wacom invalid types, which look ok, because it does find
>>>>>>>>>>> the ones it needs.
>>>>>>>>>>>
>>>>>>>>>>> the 'nv' driver no longer exists from what I can tell, and nouveau isn't
>>>>>>>>>>> necessary for this video controller.
>>>>>>>>>>>
>>>>>>>>>>> So, I'm just hoping someone here has an xorg.conf that works for this
>>>>>>>>>>> machine. Suggestions welcome also.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>>
>>>>>>>>>>> Eric
>>>>>>>>>>>
>>>>>>>>>>> [hidden email] writes:
>>>>>>>>>>>
>>>>>>>>>>>> Hi Aaron,
>>>>>>>>>>>>
>>>>>>>>>>>> I see. Now I've just got to my kernel source in the right place. Either
>>>>>>>>>>>> I haven't found the right Arch doc or it's just not very easy..
>>>>>>>>>>>>
>>>>>>>>>>>> I'm missing the config files for the kernel source and modules. Argh.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>>>>>>>>
>>>>>>>>>>>>> HI Eric,
>>>>>>>>>>>>>
>>>>>>>>>>>>> If the driver version shows only "v2.00" you haven't installed the
>>>>>>>>>>>>> kernel driver.
>>>>>>>>>>>>>
>>>>>>>>>>>>> If you download the latest driver from
>>>>>>>>>>>>> https://sourceforge.net/projects/linuxwacom/files/xf86-input-wacom/input-wacom/
>>>>>>>>>>>>> and install it you should have a version suffix on v2.00. I realize it
>>>>>>>>>>>>> is confusing how our input-wacom (kernel) driver is nested inside our
>>>>>>>>>>>>> xf86 (X driver) folder.
>>>>>>>>>>>>>
>>>>>>>>>>>>> When I download and install input-wacom-0.34.0.tar.bz2, load and
>>>>>>>>>>>>> unload the driver with the commands from the link in my previous
>>>>>>>>>>>>> message, and then issue the command 'modinfo wacom | grep version' ,
>>>>>>>>>>>>> this is the output I see (granted I'm using a different distro and
>>>>>>>>>>>>> kernel, but the version should be the same):
>>>>>>>>>>>>>
>>>>>>>>>>>>> version:        v2.00-0.34.0
>>>>>>>>>>>>> srcversion:     DFB3DEC94FA89060ACBD540
>>>>>>>>>>>>> vermagic:       4.8.0-41-generic SMP mod_unload modversions
>>>>>>>>>>>>>
>>>>>>>>>>>>> Best,
>>>>>>>>>>>>> Aaron
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Mar 17, 2017 at 2:06 PM,  <[hidden email]> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Ok, I followed the instruction for building the kernel modules and
>>>>>>>>>>>>>> installed them.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I also upgraded Xorg, and reinstalled the official xf86-input-wacom
>>>>>>>>>>>>>> package which installed 34.2-1 which matches the kernel modules I
>>>>>>>>>>>>>> downloaded.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The driver version in /sys/module/wacom/version is v2.00.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The pen/stylus still does not work.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Is there something I can look at or try that might help understand
>>>>>>>>>>>>>> this ?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Eric
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [hidden email] writes:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hello Aaron,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks for the help.  I thought that was what I was installing when
>>>>>>>>>>>>>>> I installed the xf86-input-wacom-git package.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> https://aur.archlinux.org/packages/xf86-input-wacom-git/
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I've downloaded the tar ball from kernel downloads, but it has the same
>>>>>>>>>>>>>>> name.  So I think I'm confused about which is the kernel driver, which
>>>>>>>>>>>>>>> is the X11 driver and what it is that I've actually installed or not
>>>>>>>>>>>>>>> installed.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Eric
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Aaron Armstrong Skomra <[hidden email]> writes:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Support for MSP was added in kernel 4.10 so you'll need to install the
>>>>>>>>>>>>>>>> input-wacom kernel driver:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Let us know if you have any other questions.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Best,
>>>>>>>>>>>>>>>> Aaron
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Fri, Mar 17, 2017 at 10:45 AM,  <[hidden email]> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hello,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I have a mobile studio pro running Arch linux.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I have the xf86-input-wacom-git package installed
>>>>>>>>>>>>>>>>> aur/xf86-input-wacom-git 0.33.0-1 [installed: 0.34.2-1] (2) (0.07)
>>>>>>>>>>>>>>>>>     X.Org Wacom tablet driver (from git)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Linux kernel:
>>>>>>>>>>>>>>>>> core/linux 4.8.13-1 (base) [installed]
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Xorg Server 1.18.4-1
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> xsetwacom --list devices
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> -- sorry it's a different computer...
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> shows TOUCH, STYLUS, ERASER  with ids of 15, 16, and 17.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Touch works fine. But the pen doesn't work at all.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I've tried it krita and that doesn't work either. I would have expected
>>>>>>>>>>>>>>>>> it to work in the OS.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I noticed on the device id doc that mobile studio pro 16 has it's
>>>>>>>>>>>>>>>>> version numbers crossed out.  Should this device work ?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I've tried it with the old pen from my cintiq companion, and that
>>>>>>>>>>>>>>>>> doesn't work either.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Does anyone have suggestions on how to get this working ?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Eric
>>>>>>>>>>>>>>>>>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: mobile studio pro 16 ?

Jason Gerecke
Good news and bad news...

Bad news first:

Looks like the "extra" modeline is still present and being used, so its
probably just a red herring. It also doesn't look like an issue with the
the system "simply" turning off the backlight since I don't see any
nVidia options that would explain that. No luck finding any "Optimus"
settings in UEFI setup that might have gotten toggled to a bad setting
either. I'm running out of ideas of where the bug might be hiding.

Good news:

I've somehow managed to reproduce the issue on my own system. I'm not
entirely sure what's changed and why the nvidia driver no longer lights
up the screen, but I get the same behavior -- running a bare xterm from
xinit causes the screen to go dark, but the xterm still responds to
input (e.g. I can type 'exit' and return back to my VT). Hopefully now
that I've got the system behaving like this I can figure out what's
going on.

Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one /
(That is to say, eight) to the two, /
But you can’t take seven from three, /
So you look at the sixty-fours....

On 03/30/2017 10:31 AM, [hidden email] wrote:

>
> Unless I missed something it looks like it's using the intel video.
> I should probably remove the nouveau driver. It's not doing anything.
>
> [snip]
>
> Jason Gerecke <[hidden email]> writes:
>
>> Glad to hear that it's showing signs of life again :)
>>
>> I still wonder why the nVidia driver isn't working properly though. The
>> backlight turning off (as mentioned in your other message) is definitely
>> a bit suspicious. Would you mind posting your Xorg.0.log again for
>> comparison to the broken one? It'd be interesting to see if the current
>> driver also detects/uses the "extra" modeline.
>>
>> Jason
>> ---
>> Now instead of four in the eights place /
>> you’ve got three, ‘Cause you added one /
>> (That is to say, eight) to the two, /
>> But you can’t take seven from three, /
>> So you look at the sixty-fours....
>>
>> On 03/29/2017 05:04 PM, [hidden email] wrote:
>>>
>>> I have libglvnd.
>>>
>>> I deinstalled nvidia and nvidia utils.
>>> When I run xinitrc with an exec xterm -maximized
>>> I get a terminal.
>>>
>>> Doing a startxfce4 also works. Next I'll have to refresh my xmonad
>>> and try that.
>>>
>>> I'm pretty sure I tried running without the nvidia packages after you
>>> said it should work without them, but maybe I had something else wrong
>>> at the time.
>>>
>>> It's weird that those drivers are causing a problem, they should be
>>> unloaded.
>>>
>>> The stylus is working too, which is what started me on this path.
>>>
>>> Thank you for your help!  I had tried so many things I think I just
>>> needed someone else to talk some sense with me. It's really hard to
>>> do these things without others for feedback and critical thinking.
>>>
>>> I can't say how many times I've found a bug just by describing the
>>> problem to someone.
>>>
>>> Thank you. I'm very appreciative.
>>>
>>> Eric
>>>
>>>
>>> Jason Gerecke <[hidden email]> writes:
>>>
>>>> Oh, another quick question while I'm thinking about it:
>>>>
>>>> Do you have the 'libglvnd' package installed, or are you using another
>>>> package to provide libgl?
>>>>
>>>> On 03/29/2017 04:15 PM, Jason Gerecke wrote:
>>>>> Huh, that's an interesting observation. Lets try removing the nVidia
>>>>> graphics drivers (`pacman -Rs nvidia nvidia-utils`) and see if the
>>>>> open-source drivers work differently. If there's no change, figure out
>>>>> what package installed the legacy nv driver (`pacman -Qo
>>>>> /usr/lib/xorg/modules/drivers/nv_drv.so` should give its name) and
>>>>> remove it too. If that *still* doesn't work, remove the
>>>>> xf86-video-nouveau package as well (which should hopefully have X try to
>>>>> use the Intel drivers).
>>>>>
>>>>> Jason
>>>>> ---
>>>>> Now instead of four in the eights place /
>>>>> you’ve got three, ‘Cause you added one /
>>>>> (That is to say, eight) to the two, /
>>>>> But you can’t take seven from three, /
>>>>> So you look at the sixty-fours....
>>>>>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
12