[SOLVED] Jumper EZBook 3 PRO - can't boot from USB most of common Linux distros
Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
@ibart / @mogio, have a look at this. The date is recent and this dev is the same guy I think that made the previous patch and here he is talking a lot about left-button click. Maybe this patch can fix the touchpad click problem? I think one problem may be that the touchpad maker being used is different between our notebooks and/or maybe I have the same touchpad but it's being treated different due to my different BIOS version? How can we identify if our touchpads are exactly the same ones or different?
Hans de Goede - Nov. 22, 2017, 11:57 a.m.
According to the Win8 Precision Touchpad spec, inside the HID_UP_BUTTON
usage-page usage 1 is for a clickpad getting clicked, 2 for an external
left button and 3 for an external right button. Since Linux uses
BTN_LEFT for a clickpad being clicked we end up mapping both usage 1
and 2 to BTN_LEFT and if a single report contains both then we ended
up always reporting the value of both in a single SYN, e.g. :
BTN_LEFT 1, BTN_LEFT 0, SYN. This happens for example with Hantick
HTT5288 i2c mt touchpads.
This commit fixes this by not immediately reporting left button when we
parse the report, but instead storing or-ing together the values and
reporting the result from mt_sync_frame() when we've a complete frame.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
---
Changes in v2:
-Rewrite of v1 of "HID: multitouch: Fix BTN_LEFT 0-1-0-1 events on Novatek
mt touchpad" to kill two birds with one stone
Changes in v3:
-Delay reporting for all buttons not just for BTN_LEFT
Changes in v4:
-Back to combining only the value for BTN_LEFT, the other issues are fixed
with the new "HID: multitouch: Only look at non touch fields in first
packet of a frame" patch
---
drivers/hid/hid-multitouch.c | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
Patch
Yeah, Hans de Goede is very kind. I mailed him, he replied but his patches don't solve the problem at all.
Latest drm-intel-next 4.15 hasn't the touchpad working at all. Not clicks nor movements.
I've been using Manjaro 17.06 XFCE w/updated kernel 4.14.3-1. After weeks of use and dozens of sleep/wake and power on/off cycles my touchpad has not failed (yet!). It doesn't mean the problem is 100% fixed but at least it seems to be happening less often. So far... it seems that way. Time will tell. Again, my BIOS is "Jumper EZbook/P313R, BIOS JUMPER10x.P8.WP313R.NHNAUHN02 08/07/2017"
Install instructions are above in this thread and also on the TT forum here: https://techtablets.com/forum/topic/...v4/#post-75176
Last edited by bbaker6212; 12-20-2017 at 10:58 AM.
I've been using Manjaro 17.06 XFCE w/updated kernel 4.14.3-1. After weeks of use and dozens of sleep/wake and power on/off cycles my touchpad has not failed (yet!). It doesn't mean the problem is 100% fixed but at least it seems to be happening less often. So far... it seems that way. Time will tell. Again, my BIOS is "Jumper EZbook/P313R, BIOS JUMPER10x.P8.WP313R.NHNAUHN02 08/07/2017"
Install instructions are above in this thread and also on the TT forum here: https://techtablets.com/forum/topic/...v4/#post-75176
Thanks, I'll try the ubuntu mainline 4.14.3. But I don't think it is going to work.
Thanks, I'll try the ubuntu mainline 4.14.3. But I don't think it is going to work.
Btw... I don't want Manjero.
I'm starting to wonder if the 09/30 BIOS version has problems that the 08/07 BIOS does not.
See if you can contact Jumper and find out if it's possible to reflash the BIOS.
I cannot think of anything else that could be causing such difference in functioning...
oh... maybe it could be a difference in touchpad versions or a difference in the firmware files shipped with Arch/Manjaro and Ubuntu.
How can we display the firmware files in use?
if I run "cat /proc/bus/input/devices" I see this. Is it the same on yours?...
FYI, anyone hitting a problem of no touch-pad mouse clicks working on Ubuntu (and perhaps other distro's) there is a patch for it until kernel 4.16 comes out: https://bugs.launchpad.net/ubuntu/+s...44/comments/81
Btw guys; a list of commands to identify your touchpad and config info - which may help to debug it if you continue to have problems report it on the Launchpad bug linked above:
Hi everyone, I tried to use isorespin. I've use Linux for years but I'm not great with the terminal. When I go to get the packages (sudo apt -y install*bc curl losetup ip isoinfo mkdosfs mksquashfs rsync*
* * * * sudo apt -y install unsquashfs unzip wget xargs xorriso) the terminal can't find them, even when I update the repository. Any help would be great
Hi all. Late post, for future reference:
I have same laptop and same problem. After lots of work, indeed grub was the cause.
But I went another way to solve the problem.
systemd boot loader works perfectly. I found that Arch and old versions of Manjaro use systemd.
So I've downloaded the image of the last version of manjaro that used systemd (17.0). The boot and installation did run smoothly =)
After installed, I've update to latest version of Manjaro (but keeping systemd boot loader, reject anything grub-related).
By the way, Manjaro w xfce in this laptop runs nice and sweet
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.