Those .debs should already contain a complete kernel with the driver
builtin, no separate modules required.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1372609
Title:
Touchpad detecte
Hm, I probably made a mistake there. Can you instead test the following
packages?
https://drive.google.com/file/d/0Bz7ZZcjnECHLR2EwTVdYd0VWdGc/view?usp=sharing
I've rewritten the fix for your laptop based on comments on the linux-input
mailing list, so I am interested in
1. Does it work at all f
Given my very limited upload speed, that's actually a good idea.
Chris, can you try putting
https://drive.google.com/file/d/0Bz7ZZcjnECHLMHp0V2h1OGtmWXc/view?usp=sharing
into /lib/modules/3.17.0-focaltech-fix/kernel/drivers/input/mouse/ and
reload the psmouse kernel module (or reboot)? That module
No, I think that's not how that byte works - once it is 0xff, it stays
like that until the finger is lifted from the touchpad.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1372609
Title:
Hey, thanks for the information. So, you get that value even without
large contact area? I never managed to get something like that during
normal usage, but maybe other devices have different thresholds. In that
case I'd just drop that part of the code, it is not important enough
that it should sta
Chris: There is no documentation yet. The packets are 6 bytes long, and
I think the lower four bit of the first byte identify the type of the
packet. If you can read some C, then
https://github.com/mgottschlag/linux/blob/focaltech4/drivers/input/mouse/focaltech.c#L229
is the best source available.
I pushed the two patches to my focaltech4 branch:
https://github.com/mgottschlag/linux/tree/focaltech4
@Chris: The issue 1) sounds really hard to debug. One possibility might
be that, like above, you enable i8042 debug output display and have a
life view of dmesg in a window on your screen. If you
Hey, to Chris or anyone else who has the same problem: Can you test the
following kernel and see whether it solves the problem?
https://drive.google.com/file/d/0Bz7ZZcjnECHLeUI5Tnk4VXNoMGM/view?usp=sharing
What it does is it skips some of the initialization code which was
skipped in Hans de Goede
I noticed that the problem was the same as redhat bug 1110011 again
because I managed to break the previous fix for these models, I didn't
get around writing a fix for it yet though. I'll probably have a test
kernel at some point today though.
--
You received this bug notification because you are
Okay, that's what I get here, although of course my system configuration
will be different:
[17.976] (II) config/udev: Adding input device FocalTechPS/2 FocalTech
FocalTech Touchpad (/dev/input/event4)
[17.976] (**) FocalTechPS/2 FocalTech FocalTech Touchpad: Applying
InputClass "evdev t
At someone whose touchpad does not work, with the error "Failed to
enable mouse on isa0060/serio1": Can you boot the following kernel, with
the kernel commandline parameter i8042.debug=1 and send me once more
your dmesg?
https://drive.google.com/file/d/0Bz7ZZcjnECHLc1VMSl9PRnhNdW8/view?usp=sharing
Note though that the fact that the kernel is able to identify the
touchpad does not mean that the driver is enabled.
CONFIG_MOUSE_PS2_FOCALTECH simply switches between the "real driver" and
some legacy code specific to the touchpad. The latter is required
because otherwise the touchpad does not wor
Marcel, have you enabled the touchpad driver in .config? Rerun make
menuconfig and make sure that CONFIG_MOUSE_PS2_FOCALTECH is set. I
cannot think of any other reason yet, as your dmesg does not contain any
error.
I received a bug report though where apparently the touchpad didn't work
together w
@Stephan: Yes, that's totally unrelated, better open a new bug.
@Tom: Just to check that the problem is the same as with the other
models where the touchpad is not working: Can you post a complete dmesg
here?
And to all who have a touchpad where the touchpad does not work and
dmesg shows lines li
Yeah, opening a new bug might be a good idea. Also, I'll try to find
some time next week, then I'll create a patch which generates some more
debugging output, to get some information about the issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
I have to admit I totally forgit this bug and the patch. The linux-input
maintainers probably forgot the patch as well, and I didn't push the
patch for inclusion yet because I thought there still was a regression
for Owen, and I didn't have the time to debug that. I 100% want to avoid
any regressio
@Owen:
Did the touchpad work before you installed the driver (with reduced features)?
Does the touchpad work if you add i8042.noloop=1 psmouse.proto=bare to the
kernel command line?
Can you post your complete dmesg, and the first couple of lines from ./init
/dev/serio_raw0?
--
You received this
Duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1372609 (same
touchpad), try the patches/debs in the comments from that bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs
I'll ask the person to test with a different kernel, but so far the
symptoms looked different to the reports here.
Am 10.11.2014 17:15 schrieb "Pilot6" <1372...@bugs.launchpad.net>:
> The suspend problem is a general 3.18 but. It works for everyone else. So
> no need to be so focused on that probl
No, it probably won't. I have not had much time, and on the red hat bug
tracker there is one case where the patch breaks suspend.
I do not know how to proceed or how to debug the issue, maybe adding a
quirk which disables the driver would be an option. I'll see whether I find
some more time next
I don't have much time and before I do any backporting, I want to get
the driver into a state where it will be merged into mainline linux.
There is one problem report where the touchpad is broken after
suspend/resume which needs to be fixed first, that's why I was asking
here in the first place.
h
Which part of suspend/resume is broken? Only the touchpad, or the whole
system? I am on Ubuntu 14.04 and did not have any problems with
suspend/resume so far.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
I've uploaded debs of the kernel with the new version of the driver here:
https://drive.google.com/file/d/0Bz7ZZcjnECHLX21ES1JPMnFyNVk/view?usp=sharing
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
Okay, thanks, can you also send me the first couple of lines printed by
the program? ("status:")
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1388160
Title:
[ASUS X200MA] Touchpad scro
This is basically the same touchpad as in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1372609.
Can you maybe:
- Run the program in comment #32 of that bug? I am specifically looking for
the maximum and minimum coordinates reported by the touchpad, e.g. in the
output which occurs when y
There is a second version of the driver which improves compatibility with other
Asus laptops here:
https://github.com/mgottschlag/linux/tree/focaltech2
As to the the firmware_id issue, these three patches are relevant:
http://www.spinics.net/lists/linux-input/msg33508.html
I don't think packagin
I've written a multitouch-capable driver which seems to work well at
least on the UX303LN. The code is available under the following URL (in
the focaltech branch):
https://github.com/mgottschlag/linux/tree/focaltech
Before I send anything for review, can people with affected devices
maybe test th
>
> $ sudo ./init /sys/bus/serio/devices/serio1/
> Could not open /sys/bus/serio/devices/serio1/. Check that the program is
> run
> with the required privileges and that the file exists.
> open: Is a directory
>
> What file does the program want as its argument?
>
> On 2
... that went quicker than expected. The link above now contains a
mostly complete parser for the packet stream that (afaics) gives the
correct finger position for up to 5 fingers, as well as information
about touchpad clicks.
--
You received this bug notification because you are a member of Kern
I am in the process of reverse engineering the protocol. I have executed
the Windows 8.1 driver in a VM and have written a short program which
puts the touchpad into the proprietary mode. The code can be found here:
https://github.com/mgottschlag/focaltech-tools
If anybody wants to join me, befor
30 matches
Mail list logo
