Hi,
i’ve bought a lenovo yoga 300-11IBY with a touchscreen.
i installed opensuse tumbleweed but unfortunately the touchscreen is not recognized.
i tried differend linux distros like Kubuntu, ubuntu and here the touchscreen is recognized out-of-the-box. Can anybody help me to get my touchscreen working in tumbleweed?.
Bertos
Apparently there were also issues on Ubuntu until 15.10 was released. You mentioned that you tried it out on Kubuntu. How did that work? From what I have gathered, the touchscreen works fine on Unity and Gnome, but in KDE it works like a touchpad rather than touchscreen. I also gather that the touchscreen for your unit only works well with kernel 4.2.x. I believe Tumbleweed uses ver 4.0.x, but do not hold me to that. Hopefully someone who has more information will pick up my slack. I will update you if I find any new information.
Regards,
tstor
Am 10.02.2016 um 17:56 schrieb tstor:
>
> that the touchscreen for your unit only works well with kernel 4.2.x. I
> believe Tumbleweed uses ver 4.0.x,
according to software.opensuse.org tumbleweed should be at kernel 4.4
@Bertos: can you show the output of “uname -a”?
–
PC: oS 13.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.14 | GTX 760
Yoga 2 Pro: oS 42.1 | x86_64 | i7-4500U@1.80GHz | 8GB | KDE 5.16
HTPC: oS 42.1 x86_64 | Celeron@1.8GHz | 2GB | Gnome 3.16 | HD 2500
Sorry about that, I was having trouble finding an outright answer from any authoritative source. I am not sure what the problem could be with the touch screen then. I will do some more reading on the issue at hand, but most of my information regarding the screen has come from the following page:
Post #9:
Tried the 32 bit Lubuntu 15.10 version with legacy mode. Could run it from the usb drive but once installed there came an error that no bootable disk was detected. Switched to UEFI mode and installed the 64bit Lubuntu 15.10 version and works great. Touchscreen works out of the box. Button on the side of the notebook to rotate screen by 180° does not work. Installed xbindkeys added it to the startup applications and created .xbindkeyscr file in home folder with following content:
*“xrandr --output eDP1 --rotate inverted; xinput set-prop ‘ATML1000:00 03EB:8C3C’ ‘Coordinate Transformation Matrix’ -1 0 1 0 -1 1 0 0 1”
Control + Next
“xrandr --output eDP1 --rotate normal; xinput set-prop ‘ATML1000:00 03EB:8C3C’ ‘Coordinate Transformation Matrix’ 1 0 0 0 1 0 0 0 1”
Control + Prior
*
This rotates the screen as well as the touch input. The original button did somehow not work therefore I used control+next and control+prior as shortcuts.
Installed onboard as touchscreen keyboard. Works fine. The only problem I still have is that onboard’s emulation of middle and right click does not work.
Post #10:
+1 solved: with kernel 4.2. and higher the touch screen works fine…
Hi, and thank you all for your replies.
From what I have gathered, the touchscreen works fine on Unity and Gnome, but in KDE it works like a touchpad rather than touchscreen
Well, i would be glad if i would get any reaction when i touch the screen. i agree, with ubuntu the function of the touchscreen was more like a touchpad or a mouse than the touch abilities known from windows. But with ubuntu (and kubuntu) the touchscreen was recognized and gives me a reaction when touching. With tumbleweed there is nothing at all.
I will update you if I find any new information
thanks.
@Bertos: can you show the output of “uname -a”?
Of course:
Linux linux-7uav 4.4.0-3-default #1 SMP PREEMPT Thu Jan 28 08:15:06 UTC 2016 (9f68b90) x86_64 x86_64 x86_64 GNU/Linux
Bertos
Am 10.02.2016 um 22:06 schrieb Bertos:
> Code:
> --------------------
> Linux linux-7uav 4.4.0-3-default #1 SMP PREEMPT Thu Jan 28 08:15:06 UTC 2016 (9f68b90) x86_64 x86_64 x86_64 GNU/Linux
> --------------------
ok so it is confirmed that your kernel is new enough (>=4.2), so that
seems not to be the problem. In order to see if your touchscreen is
really not recognized (disclaimer I do not have the same modell and the
same touchscreen), I would check with xinput and lsusb what you have.
lsusb
xinput list
If it is recognized in xinput we have to find out why it is not enabled
(if xinput is not installed, the package has the same name in order to
install it).
For example on my model it reports
martinh@yoga:~> lsusb
Bus 003 Device 002: ID 8087:8000 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 5986:0535 Acer, Inc
Bus 001 Device 005: ID 04f3:016f Elan Microelectronics Corp.
Bus 001 Device 004: ID 2047:0855 Texas Instruments
Bus 001 Device 003: ID 8087:07dc Intel Corp.
Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
martinh@yoga:~> xinput list
⎡ Virtual core pointer id=2 [master pointer
(3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer
(2)]
⎜ ↳ PixArt USB Optical Mouse id=9 [slave pointer
(2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=14 [slave pointer
(2)]
⎜ ↳ ELAN Touchscreen id=10 [slave pointer
(2)]
⎣ Virtual core keyboard id=3 [master keyboard
(2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard
(3)]
↳ Power Button id=6 [slave keyboard
(3)]
↳ Video Bus id=7 [slave keyboard
(3)]
↳ Power Button id=8 [slave keyboard
(3)]
↳ Lenovo EasyCamera id=11 [slave keyboard
(3)]
↳ Ideapad extra buttons id=12 [slave keyboard
(3)]
↳ AT Translated Set 2 keyboard id=13 [slave keyboard
(3)]
The ELAN is the touchscreen. I can enable/disable it with
xinput --disable "ELAN Touchscreen"
xinput --enable "ELAN Touchscreen"
–
PC: oS 13.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.14 | GTX 760
Yoga 2 Pro: oS 42.1 | x86_64 | i7-4500U@1.80GHz | 8GB | KDE 5.16
HTPC: oS 42.1 x86_64 | Celeron@1.8GHz | 2GB | Gnome 3.16 | HD 2500
yoga300@linux-7uav:~> lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 004: ID 8087:07dc Intel Corp.
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 5986:0673 Acer, Inc
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
yoga300@linux-7uav:~> xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ Sleep Button id=9 [slave keyboard (3)]
↳ Lenovo EasyCamera id=10 [slave keyboard (3)]
↳ Ideapad extra buttons id=11 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]
yoga300@linux-7uav:~>
As far as i understand, the touchscreen is not recognized at all (no ELAN device)?
Bertos
I have to say that I hoped to see anything which could be identified as
the touch screen and can only guess that kernel 4.4 in contrast to 4.2
does not see the device.
Myself I would look for a 4.2 kernel here
https://software.opensuse.org/package/kernel-default
and install it in addition to your standard 4.4 one to see if the device
works when you boot with it, I would also grab a 4.5rc kernel and see
how that behaves.
No further idea so far.
–
PC: oS 13.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.14 | GTX 760
Yoga 2 Pro: oS 42.1 | x86_64 | i7-4500U@1.80GHz | 8GB | KDE 5.16
HTPC: oS 42.1 x86_64 | Celeron@1.8GHz | 2GB | Gnome 3.16 | HD 2500
Thank you, i will try your suggestions.
Bertos
Am 11.02.2016 um 06:46 schrieb Bertos:
>
> Thank you, i will try your suggestions.
I should have added that you should just grab the corresponding rpm for
the additional kernels you install for testing and not add the
repositories to avoid side effects.
If you just add an additional kernel (or several) for testing worst
thing which can happen is that it does not work for you and you can
easily boot with your original one by selecting it at startup in grub.
Removing it then is also no problem.
The system as such is not really affected by changing the kernel (that
means the software you have is not modified, if you have something which
needs an additional kernel module like virtual box or something else
just break it while installing, it is temporarily only broken when
booting with the testing kernel not with the original one.
Intention is simply to see if 4.2 or 4.5 really sees the device in
contrast to your 4.4 you have now.
–
PC: oS 13.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.14 | GTX 760
Yoga 2 Pro: oS 42.1 | x86_64 | i7-4500U@1.80GHz | 8GB | KDE 5.16
HTPC: oS 42.1 x86_64 | Celeron@1.8GHz | 2GB | Gnome 3.16 | HD 2500
thank you again.
first i tried something different. as mentioned, with ubuntu the touchscreen gave me a reaction. so i tried the live version of ubuntu 15.10 again and as expected the touchscreen worked. i compared the output of
lsusb
xinput list
ubuntu-gnome@ubuntu-gnome:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 005: ID 8087:07dc Intel Corp.
Bus 001 Device 004: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 003: ID 5986:0673 Acer, Inc
Bus 001 Device 002: ID 0951:16a5 Kingston Technology
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The ‘Kingston Technology’ entry is the live usb stick.
ubuntu-gnome@ubuntu-gnome:~$ xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ ATML1000:00 03EB:8C3C id=12 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=14 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ Sleep Button id=9 [slave keyboard (3)]
↳ Lenovo EasyCamera id=10 [slave keyboard (3)]
↳ Ideapad extra buttons id=11 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]
This ubuntu output shows compared to the tumbleweed output the additional entry
‘ATML1000:00 03EB:8C3C’
This seems to be the touchscreen.
Does this observation give any additional value?
Bertos
Am 11.02.2016 um 13:56 schrieb Bertos:
> ATML1000:00 03EB:8C3C
you could at least use that on your openSUSE to check if anything
happened with that device or simply nothing at all
journalctl -l | grep -i atml1000 | less
to give an indication if your tumbleweed kernel did at all identify that
it is there or not
if that then helps further is a bit unclear
that we cannot see it on the ubuntu output with lsusb just says that it
is not an usb device (my touchscreen is one), maybe it is serial or
something else
–
PC: oS 13.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.14 | GTX 760
Yoga 2 Pro: oS 42.1 | x86_64 | i7-4500U@1.80GHz | 8GB | KDE 5.16
HTPC: oS 42.1 x86_64 | Celeron@1.8GHz | 2GB | Gnome 3.16 | HD 2500