[Bug 2078422] Re: Upgrade to 24.04.1 is failing
On 07 Sept I encountered a similar issue going from 22.04.4 to 24.04.1. This is my work-around. The first `sudo apt dist-upgrade` seemed to complete but the kernel was still at 5.15.0-119. Third-party PPAs like docker were disabled. I then did a `sudo apt update` and received many of the following warnings. ``` # (appstreamcli:165135): GLib-GIO-CRITICAL **: 08:59:52.028: GFileInfo created without standard::is-hidden # (appstreamcli:165135): GLib-GIO-CRITICAL **: 08:59:52.028: file ../../../gio/gfileinfo.c: line 1632 (g_file_info_get_is_hidden): should not be reached ``` I did `sudo apt-get autoremove; sudo apt-get -s clean` I did a second `sudo apt dist-upgrade`, reboot, and the kernel updated to 6.8.0-41 but the GNOME desktop would not start, kicking out to a text terminal. I logged in and checked the apt logs but did not see anything obvious. I did a `journalctl /usr/bin/gnome-shell > /tmp/gs.log` and saw it exit with the following error: ``` Sep 07 19:12:45 linger gnome-shell[4539]: Xwayland terminated, exiting since it was mandatory Sep 07 19:12:45 linger gnome-shell[4539]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly @resource:///org/gnome/shell/ui/init.js:21:20 Sep 07 19:12:45 linger gnome-shell[4539]: Execution of main.js threw exception: Module resource:///org/gnome/shell/ui/init.js threw an exception Sep 07 19:15:20 linger gnome-shell[2911]: Gio.IOErrorEnum: GDBus.Error:org.freedesktop.DBus.Properties.Error.PropertyNotFound: Error return with empty body: Stack trace: _promisify/proto[asyncFunc]/https://bugs.launchpad.net/bugs/2078422 Title: Upgrade to 24.04.1 is failing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2078422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
Sorry - Kevin did a lot of work on the driver and then uploaded as an issue attachment. I just uploaded his tarball to http://www.dahetral.com/public-download. No one has reported anything negative about the new driver and it has been accepted to the linux kernel. Dave On 04/19/2013 11:26 AM, Richard Merren wrote: > When I upgraded my N5110 to the raring ringtail beta last week, the > touchpad was no longer recognized. I believe I had the 0.4 version > installed. I uninstalled and removed all of the existing DKMS entries > and installed the 1.3 version downloaded from http://www.dahetral.com > /public-download but the touchpad is still not recognized. > > Has anyone been successful on an N5110 with this kernel? Any > suggestions, or any tests I can perform to help resolve this? > > Some potentially helpful info: > > uname -a: > Linux rbmlaptop 3.8.0-17-generic #27-Ubuntu SMP Sun Apr 7 19:39:35 UTC 2013 > x86_64 x86_64 x86_64 GNU/Linux > > Some lines from dmesg: > [8.279185] psmouse serio1: alps: E6 report: 00 00 64 > [8.298297] psmouse serio1: alps: E7 report: 73 03 50 > [8.316631] psmouse serio1: alps: EC report: 73 02 02 > [8.319620] psmouse serio1: alps: ALPS: E7=73 03 50, EC=73 02 02 > [8.319626] psmouse serio1: alps: Unknown ALPS touchpad: E7=73 03 50, > EC=73 02 02 > > xinput: > ⎡ Virtual core pointerid=2[master pointer (3)] > ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer > (2)] > ⎜ ↳ PS/2 Generic Mouse id=12 [slave pointer > (2)] > ⎣ Virtual core keyboard id=3[master keyboard (2)] > ↳ Virtual core XTEST keyboard id=5[slave > keyboard (3)] > ↳ Power Buttonid=6[slave > keyboard (3)] > ↳ Video Bus id=7[slave > keyboard (3)] > ↳ Power Buttonid=8[slave > keyboard (3)] > ↳ Sleep Buttonid=9[slave > keyboard (3)] > ↳ Laptop_Integrated_Webcam_HD id=10 [slave > keyboard (3)] > ↳ AT Translated Set 2 keyboardid=11 [slave > keyboard (3)] > ↳ Dell WMI hotkeysid=13 [slave > keyboard (3)] > > dkms status: > psmouse, alps-1.3, 3.8.0-17-generic, x86_64: installed > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
Greetings - I have received a number of emails about running the our dlkms on a 3.5+ kernel. Kevin Cernekee made the required API changes and added it as an attachment to this issue. I have copied his tarball to my public area at: https://www.dahetral.com/public-download/psmouse-alps-1.3-alt.tbz/view Dave -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
@libondam-0 Response to comments 348, 349, 350: The easiest, and I mean *easiest*, way is to hack alps.c for the raw input from the touchpad and then "xinput setprop" to tune the X11 cooked input. For brand-new alps touchpads that don't adhere to any of the known protocols, this is not sufficient and one needs to reverse engineer the Windows driver behavior. Seth Forshee showed us the way and then Ben Garami figured out the the new extensions. I seriously doubt this will be the case for you. Use Virtualbox or Qemu to create a guest OS. I used Vista. Seth showed how to patch the I/O layer to dump the bytes going between the guest driver and the hardware. The catch is that the new alps drivers check the BIOS ACPI DSDT tables to make sure it's an ALPS hardware module; if not it drops into 3-byte PS2 mode. Therefore the virtual ACPI DSDT table must be updated to use the Hardware ID (HID) for the alps hardware model (taken from the real ACPI DSDT table.) If this sounds a little complicated, it is. Make sure you install the Alps driver into the guest OS! In the alps.sh from the 1.3 DLKM, there are some helper routines to get the real DSDT and patch the qemu acpi-dsdt.dsl table for the correct HID. There is another way to reverse engineer an ALPS touchpad, discovered by Kevin Cernekee but it's not totally reliable. It worked for him, and cleaned up the E6430 code a good deal. Email Kevin directly for how to do it. Dave -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
@libondom-0
My guess is this is another mutation of the ALPS touchpad. It clearly
is a new signature, which you added, which indicates new behavior: the
trackstick. There have been several new significant behaviors added to
the alps driver ("Rushmore" and "Dolphin").
The best I can recommend, not having this touchpad (and it's an n:m
mapping between Dell system and Alps touchpad), is to add code to the
driver to dump the trackstick changes and then try to reverse engineer
what the movement codes actually mean. See the
alps_process_packet_v1_v2 routine.
BTW, I experienced similar upheaval in the late 1980's as a customer to
a company called Newbridge. Its staff was turning over so quickly that
relative newbies were the sole support for some of their hardware and
just hacked it up to get it to work regardless of documentation or
compatibility. They released M$ drivers to support the new firmware but
Unix boxes (we were a SUN shop) were left hanging. Newbridge and SUN no
longer exist; I think this bodes poorly for ALPS.
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/606238
Title:
synaptic touchpad not recognized on dell latitude e6510 and others
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/606238/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
@matt I noticed that Kevin's patches were accepted for the next 3.7 kernel release. I also noticed that a fedora maintainer backported Kevin's patches to the next Fedora release. See https://bugzilla.redhat.com/show_bug.cgi?id=812111 I have not seen any activity by Ubuntu maintainers to backport the patches, so I doubt they will be integrated into the Ubuntu train any time soon. You can test it yourself by installing the psmouse-alps-1.3-alt.tbz attachment (see the "Bug Attachments" sidebar) ** Bug watch added: Red Hat Bugzilla #812111 https://bugzilla.redhat.com/show_bug.cgi?id=812111 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Quantal) Status: In Progress => Fix Committed ** Changed in: opensuse Assignee: (unassigned) => Dave Turvene (dturvene) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
Kevin - Responses inline On 02/18/2013 05:07 PM, Kevin Cernekee wrote: > Just so we're on the same page - the "input-next" tree [1] (input.git, > branch "next") is Dmitry's staging area for proposed input subsystem > changes to send to Linus for the next merge window - currently targeting > Linux 3.9. My patches 01-13 are in there now. This includes the code > refactoring + Rushmore support, but no Dolphin support. Good to know; I wondered how the roll-up works. > > This past weekend I submitted three more patches [2] to be applied on > top of input-next: > > 1) Remove unused argument to alps_enter_command_mode() - trivial cleanup > > 2) Dolphin V1 support, credited to Dave/florin. This is believed to be > in working order, and ready to merge. > > 3) Dolphin V2 support, consisting of my new init + detection sequence. > This was marked as WIP because the pressure readings at the edge of the > touchpad are still "off." I am hoping somebody with access to this > hardware can help figure out why. Maybe switching to the V2-native > report format (and writing a new decoder for it) would help, since that > is what the ALPS drivers seem to prefer. Great! I dump a lot of email lists, including linux-input, on my server and only periodically check them. I just saw your three-part submission. The code looks good. I'll post a new comment on the 606238 bug thread about my understanding of your progress - just to avoid confusion. > > > "It doesn't make sense to me for ALPS to create different touchpad layout > using the same signature; more likely is the laptop exposes an area of the > touchpad based on the available real estate." > > It appears that the driver can query the Dolphin V2 touchpads for their > specs, and adjust the operating parameters accordingly. > > Unfortunately I don't know much about how this works, or what range of > values we can expect to see in the wild. > > As for Rushmore, I can confirm that the touchpad dimensions and > trackstick/buttons differ between Dell E6230/E6430, even though the IDs > are the same. I haven't actually taken the laptops apart to see how > they contrast physically. Doing so might shed light on how ALPS manages > product variants. Good to know but I'm unclear how to proceed. Back when, I put in a sysfs debug interface that a user could run to capture the physical coordinates of the edges in order to tune the X edge properties. I could take your patches, add the debug and release a new dkms. > > > "Update ./Documentation/input/alps.txt with details on the new variants." > > That's a great idea, and it's something I've been neglecting. I'll update alps.txt tonight and submit to linux-input > > One other thing that might be worthwhile is to see how much (if any) of > the refactored V3 code can be used for the V4 touchpads. There are many > similarities between the two protocols. I agree there are a lot of similarities but some differences as well. For example, V3 uses byte 4 for x/y coordinates and byte 3 for buttons; V4 uses byte 3 for x/y coordinates and byte 4 for buttons. This could take a little bit of time to refactor. I'm backed up on several other projects so I need to move on. > > > [1] > http://git.kernel.org/?p=linux/kernel/git/dtor/input.git;a=shortlog;h=refs/heads/next > [2] http://www.spinics.net/lists/linux-input/msg24857.html > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
I'm just getting back to this. Here's my view of the bug progress based on the last several (okay, few) comments: 1) the psmouse-alps-1.3 dkms works well for MOST laptops, not those based on the mysterious "Dolphin V2" init sequence. 2) the subsequent psmouse-alps-1.3-alt dkms posted by Kevin has a minor change that works for "Dolphin V2" without impacting the existing logic. So is it safe to say that ALL existing ALPS touchpads are, more or less, working with Kevin's dkms? I think a lot of the problems with edge scrolling can be tuned using the "Synaptics Edges" property. It doesn't make sense to me for ALPS to create different touchpad layout using the same signature; more likely is the laptop exposes an area of the touchpad based on the available real estate. If this is a working dkms, then I would like to proceed by: 1) Documenting the logic in alps_identify surrounding the dolphin and rushmore variants (which were removed from the alps_model_info table because it doesn't contain enough information to uniquely identify the init sequences.) 2) Update ./Documentation/input/alps.txt with details on the new variants. 3) Clear out the debug info and submit a patchset to linux-input I would love to 1) rewrite a lot of the alps code and 2) document all the systems supported by the five protocol variants. For (1) Kevin's 14-part patchset cleaned up a lot of the code and I don't see spending a week or two refactoring and testing will improve the situation much. For (2) the current group does not KNOW which systems have the different touchpad variants (i.e. I just saw that the current software now runs on a Dell M4700, great news!) So, I want to freeze code changes, document the heck out of what everyone did and close this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
I need to work on several projects so will not have time to look at this again this week. I rebased our work on Kevin Cernekee's 14-part submission to linux-input. His patchset cleaned-up/refactored a lot of the messier code along with a more comprehensive init sequence for the Dell E6XXX series. Ben's V5 init sequence is no longer necessary. The new dlkm is at [1]. The one final step that needs to be taken is to reconcile florin9doi's init sequence for my Dell N5110 and a Fujitsu a512. The systems have the same E7/EC signatures but appear to have different init sequences. When I use the Fujitsu a512 init sequence, my system is stuck in PS/2 3-byte format and, apparently, the converse is true for the Fujitsu. I have re-added the alps_debug sysfs interface to toggle packet debug and switch between the new V5 (was V6) init sequences for the N5110 and a512. This can only be done by setting the alps_debug bit and rebuilding; I couldn't get it to work on-the-fly. We are almost to the point of a submitting a final patchset to resolve a LOT of ALPS touchpad bugs. [1]: http://dahetral.com/public-download -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
I reviewed Kevin Cernekee's touchpad code for Dell E6230, E6430, E6410 submitted as a patch set to the linux-input listserve. This is the main avenue for linux input driver patch submissions. It looks like it has the same functionality as Ben Garami's fix for the E6430 but is a lot cleaner: hardware init, interface protocol and overall driver cleanup. It sounds like several people have tested Kevin's patch and found it to work (with a couple questions posted.) @Emmanuel Thome: I can't tell from the thread whether your fixes for the 6230 are still necessary. It sounds like Kevin's patch with an X_BITS/Y_BITS tweak should be sufficient. My thinking is, I will: 1. install Kevin's patches on an Ubuntu 12.04 baseline. His patches are for 12.10 so it should be compatible. 2. investigate some clues Kevin sent me to better understand the hardware init sequences for the N5110 and try to incorporate them. 3. merge the mt and init fixes from florin9doi 4. release a new roll-up dlkm for testing I will discard the ACPI code, as it is not very useful. Apparently Linus was accurate when he stated "ACPI is a complete design disaster in every way." The documentation for the alps driver should be put in $KERNEL/Documentation/input/alps.txt I added some for the V5 and V6 protocols, but will need to update it for the new patches. If anyone wants to cross-reference system models and alps devices, that would be the place to do it. After a test period I will submit a patchset based on acceptance of Kevin's already submitted patchset for inclusion in upstream builds. I know the Fedora maintenance team expects to put this in their next major release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
** Changed in: linux (Ubuntu) Status: Fix Committed => In Progress ** Changed in: linux (Ubuntu Quantal) Assignee: (unassigned) => Dave Turvene (dturvene) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
@Masoud The alps driver does not support three-finger or four-finger gestures for any platforms. It would be nice but it took a better man than I, florin9doi, to figure out the two-finger gesture for our platform, and we do not have a 6430u to reverse-engineer. @florin9doi Based on your comments, in my next dkms I'll back out the ACPI lookup for hardware id (_HID) since it is not unique for the actual hardware behavior. The _HID is only as useful as ALPS wants it to be apparently. I'll also insert your really small v6 init sequence. How did you figure that out? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
@Kevin Cernekee
I have been asked to submit my patchset directly to the linux-input
newgroup. My patchset incorporates Ben's reverse-engineering for the
alps signature 0x73, 0x03, 0x0a and mine for 0x73, 0x03, 0x50. Your
patchset for 0x73, 0x03, 0x0a is very different, and has a lot of code
cleanup (which is a good thing.) Comments/Questions:
1) Where did you get the device names ("Dolphin", "Pinnacle", "Mercury",
etc.) and how did you figure out the protocols? Neither Ben nor I got
any kind of response from ALPS so we reverse engineered the protocol
under a virtual Windows environment. Did ALPS provide you information
on the devices?
2) All the existing EC responses are of the form 0x88, 0x07, 0xXX,
except for the signature 0x73, 0x03, 0x50, which has EC responses of
0x73, 0x01, {0x0d | 0x02}. Your patch #2 has the following assumption:
'It is presumed (hoped) that anything that isn't in the Pinnacle series
will not return "88 07 xx" or "88 08 xx".' This may break some existing
touchpad interfaces.
Any way you could provide your psmouse dkms as a tarball? Esp. because
there are a number of Fedora and Arch Linux users running my psmouse
dkms.
@all
Can people test Kevin's patch? If it works, then I'll layer the Dell
I15R, I17R, 13z on top of it and submit a patch to linux-input.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/606238
Title:
synaptic touchpad not recognized on dell latitude e6510 and others
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/606238/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
@David J
I just saw your #291 post. Your device looks similar to the Latitude 6430,
etc. that Ben reverse engineered. But it has a different command-mode response
(0x88 0x08 0x22). Maybe it still conforms to the V5 protocol. To test this,
add a new entry to alps_model_data and add a new command mode response check to
the alps_enter_command_mode routine.
Also, what is the DSDT entry for the device? If you're using my 1.2
driver, that hardware id string should be dumped. If you're using
something different, run these commands
sudo sh -c "cat /sys/firmware/acpi/tables/DSDT > DSDT.aml"
iasl -d DSDT.aml
and then in DSDT.dsl, search for 'Device (PS2)' or 'EisaId ("PNP0F13")'
and list the corresponding _HID value.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/606238
Title:
synaptic touchpad not recognized on dell latitude e6510 and others
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/606238/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
@Matt Yeah, I've received a couple "driver doesn't compile" emails recently for the newest kernels. See this issue on Arch Linux https://aur.archlinux.org/packages/psmouse-alps-driver with an appropriate work around. I don't plan on moving to a 3.5+ kernel in the near future and I have not heard ANYTHING about my patch submissions being accepted so I think submitting a patch with your 3 argument changes may be a little premature. My suggestion is to create a new issue on the Ubuntu launchpad for the three argument problem, document your work around and point to this and the Arch Linux bug report. BTW, I saw that Linux Journal picked Dell as the best Linux vendor. Ironic considering this thread! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
@florin9doi I added in your minimal init sequence but kept getting bare_ps2_packet notices. It didn't work for me. In my 1.2 tarball I called your init "alps_hw_init_v6_minimal". The original one works fine. @emmanuel-thome Nice cleanup! I started to merge but the effort looked to be too great, and I have no way to test them. @bgarami You were the one to figure out the whole ACPI interface. That was the major technical issue. You can rest on your laurels... @erno-iki Someone marked this as "Fixed Released" but never submitted a patch set. Subsequently I submitted a normalized patch set to Canonical, who SHOULD merge it and submit to the linux-input group. The correct status should be "Fix Committed" but I can't change the status. Sorry for the confusion. I don't think Canonical has done anything with it but I could be wrong. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
I added an ACPI interface to get the REAL alps hardware type. See version 1.2 at [1]. I hacked the driver to wrap the E6/E7/command mode selecton code inside a function that checks the ACPI PS2 hardware id against a table (which has only one entry right now, "DLL04B0" for my Dell N5110. If there is no ACPI access or no entry in the HID table, it calls the old "get_model" routine. It took me a while to figure out the ACPI language and API but it's actually fairly flexible. I had some problems with the API because it uses a lot of double pointers - which led to several kernel crashes. Anyways, this seems to be the way the Alps drivers do it - access the ACPI DSDT table to determine the init sequence, etc., which makes a lot of sense. Individual responses shortly [1]: http://www.dahetral.com/public-download -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
@Miguel and Adi I am almost certain your problems are caused by your X tuning and not the driver. Make sure you are using the ALPSPS/2 ALPS Glidepoint interface and not the default PS/2 Mouse. Try using xinput setprops to tune the "Synaptics Velocity Scaling", "Synaptics Move Speed", etc. If there are still issues, use psmouse-alps-dst-0.4 and enable DEBUG in alps.c. See the run_alps_debug shell function in alps.sh to set the sysfs alps_debug to a "deep debug" level which collects all V5 output from the driver and (on my system) dumps to syslog. It should show 6-byte packets that change linearly in the x/y planes. Please post the snippets of the log when the cursor jumps significantly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
I have attached the linux canonical patch file for the fixes by Malte for the E6530. This should be applied after patch 1 submitted in post 236 and patch 2 submitted in post 237. @Ubuntu Based on comments in the subsequent two weeks since I submitted the patches, it looks like there may be a new Alps touchpad protocol for the Dell E6230. This bug has been open for almost 2.5 years, with patches submitted. ** Patch added: "Alps touchpad fixes for Dell E6530 and formatting" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/606238/+attachment/3424714/+files/0003-alps.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
@ Markus and Nicolas Both of your E6230 systems have the same symptoms so I think it is systematic. My thoughts: Problem summary: The E6230 touchpad has the same signature and command-mode response as the E6430, so it is detected as a V4 protocol. The initialization sequence fails about halfway, putting the device in an unknown state. The psmouse driver completes initialization but the hardware is unresponsive. Reboot does not reset the touchpad because the driver is unresponsive. Power cycle resets the device. Workaround: The E6430 code fails on the E6230. If Ben's E6230 code is removed from alps.c your touchpad will default to the defacto 3-byte ps2 mode, which works but is limited. Possible Fix Paths: 1. Somehow the E6430 and E6230 must be identified differently (not just the E7 sequence and command mode response, which are identical) in order to differentiate the initialization paths. Then the E6230 must be reverse engineered to capture the desired init sequence and packet processing. 2. Ben Garami's initialization reverse engineering sequence is not complete. I know he did not spend a lot of time analyzing it. The init sequence must be captured for the E6230 and blended with the E6430 hw init. Does the Dell(Alps) touchpad driver for the E6430 say it supports the E6230? If so then Ben's sequence is not complete. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
@Nicolas D. Your alps touch pad on the E6230 is failing to complete the initialization sequence. It looks like it has the same signature as the alps touchpad on the E6430 and E6530 so the system thinks it's configured but it's not operational. Possible solutions: 1. Hardware failure and the touchpad needs to be physically replaced 2. This is a new alps model, different from the "new" one Ben Garami reverse-engineered a couple months ago for the E6430. I did the same steps for the N5110 for it's signature - very technical. 3. hack the alps dkms to glean more information about why it's failing. The fix for (1) is to take it to a Dell dealer. The fix for (2) is to re-trace Ben's steps to analyze the touchpad. He was mostly posting in a looong thread on the linux-input newsgroup under the title "New Alps protocol in the wild?", which can be googled. The eureka post is at: http://www.spinics.net/lists/linux- input/msg21993.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
@malte skoruppa Thanks for your efforts on this. Yes, I made mistake(s) converting the V5 init sequence, which you debugged and successfully fixed. I have added your changes to a new patch candidate at [1] Please test. If I hear nothing in a couple days I will resubmit the E6430/E6530 patch to ubuntu. To answer your questions: Q1) Yes, I think it is the same thrice PSMOUSE_CMD_RESET_WRAP sequence. This is the indicator to enter "command mode", where the touchpad can be configured. I have added this to the code. Ben and I have not figured out what is being configured when in command mode, just that it works. Q2) PSMOUSE_CMD_GETINFO returns a three-byte status code in the param field. It is important to determine the alps touchpad version for the so-called "E6" and "E7" code fragments . I could not figure out what the three-byte value indicates at other times. [1]: http://www.dahetral.com/public-download -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
I am submitting two patches for integration into the upstream Ubuntu and Linux source. I used the kernel canonical patch format and followed the kernel coding styles. First of two patches. ** Patch added: "Working Alps touchpad for Dell E6430 from Ben Garami" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/606238/+attachment/3413410/+files/0001-alps.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
Second of two patch files for alps support. ** Patch added: "Alps touchpad support for Dell N5110" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/606238/+attachment/3413411/+files/0002-alps.patch ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Dave Turvene (dturvene) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
There are two layers for input processing 1) The Alps driver which processes the raw input and feeds it to 2) X11, which handles cursor movement, scrolling, buttons using a large number of properties The GUI is one way to change the X11 properties. I traced where the properties are saved persistently and it seems like it's in a binary file at $HOME/.config/dconf/user. This must be read when X is starting up. For testing, I tuned my cursor movement using the following: echo "enable two-finger scrolling, disable edge scrolling" xinput set-prop $ID_TP "Synaptics Two-Finger Scrolling" 1 0 xinput set-prop $ID_TP "Synaptics Edge Scrolling" 0 0 0 xinput set-ptr-feedback $ID_TP 4 50 10 There is also a property for Synaptic touchpads named JumpyCursorThreshold. This is to reduce cursor jumping but applies to only Synaptic touchpads. Having said that cursor jumping and refocus could be the driver misinterpreting the raw data from the device. If you want to debug further use the psmouse-alps-dst-0.4 dlkm, which has a lot of debug. If the raw data dumped to syslog is linear then it's an X11 problem. If the raw data jumps then you probably have a mis-interpreted/new protocol. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
@Nicolas Dumoulin It looks like the driver is not detecting the alps touchpad. Look from the bottom up in the syslog (probably /varlog/syslog) for lines with "psmouse". If there are lines with "alps: E6" then the driver is installed correctly. What does the line with "alps: command_mode:" say? The E6230 may not be a supported alps model, at least there is no indication in the code it is. So the psmouse driver reverts to 3-byte ps2 mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
I just released a 1.0 version of the alps driver [1]. This is my candidate for linux patch submission for the alps driver supporting the new V5 and V6 protocols. The code mods in this release bring it into compliance with the patch submission requirements. I made no logic changes. I had to make some formatting changes to Ben Gamari's V5 protocol to pass the patch requirements - hopefully I didn't change the logic. In a couple days, I'll submit to Canonical rather than linux-input because I have only tested using Ubuntu 12.04 LTS. If you detect any problems with the 1.0 driver, please post here. [1]: http://www.dahetral.com/public-download -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
take ownership to merge upstream to linux-input -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
I integrated the multi-touch stuff from florin9doi and tested. See [1]. The alps.sh script contains example functions to install and build the psmouse dlkm. Nice job florin9doi! I really like mt - for me, much better than edge- scroll. But edge-scroll works okay after I increased the physical edge of the touchpad from 1340 to 1360. One still needs to modify the xinput "Synaptics Edges" property for personal preference if you want to use edge-scroll. For most properties, again see alps.sh In preparation to merge this into the upstream linux release, I cleaned up the code and removed a lot of crap and debug. I updated alps.txt from the linux source documentation to include the two new protocols: v5 from Ben Garami and v6 from our collective fixes. [1]: http://www.dahetral.com/public-download ** Changed in: linux (Ubuntu Precise) Assignee: (unassigned) => Dave Turvene (dturvene) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
On 09/21/2012 09:41 AM, Midhat wrote: > Hello Dave. I tested the new driver. It does not crash the kernel now > and the alps device shows up in `xinput list` , but the mouse pointer > does not move. I see activity in the syslog when I try to move the > pointer, but the pointer doesnt move at all. The buttons for left and > right click continue working. I'm not sure if it has any relation with > this driver. > > Thanks for all the work. If it helps, you can see my syslog at > http://dl.dropbox.com/u/7201872/syslog > @Midhat Make sure the driver is loaded and enabled. Look at the run_tp_check routine in the alps.sh script file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
I just released a 0.3 version of the alps driver [1]. So far I have no idea how to decode the multi-touch stuff. So I hacked an odd little code frag to discard all packets that are not single touch. The problem is there's a subtle transition from single to multi- touch that LOOKS like a wild single touch packet. That's why the cursor moves so dramatically. Shouldn't be happening now. @Richard & @medhat - I think this will stop your panics. I'm not sure what's going on but I'm pretty sure there was a crash waiting to happen. Thanks for testing and reporting. Please try again and report your progress. At the worst, it should drop to a standard ps2 mouse. I added an alps.sh script file that I actually use to build, test, run the driver. It should be self-descriptive. All functions work on my machine but use them with a grain-of-salt on yours. One function "run_tune_alps" sets up X for the touchpad speed and size. It will help for edge scrolling. But please adjust to your own preferences. [1]: http://www.dahetral.com/public-download -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
On 09/19/2012 05:21 PM, Richard Merren wrote:
> Still getting crashes/hang on boot with this driver on my N5110. No
> change from the 0.1 to the 0.2 version. Nothing for psmouse gets logged
> in the syslog at all. Following the steps within the build_alps
> function of the README file, all is well until I execute the "sudo
> modprobe -v psmouse". Then I am dropped out of X and see a stacktrace
> (which I can't really copy because I have no interactivity left...have
> to reboot at this point and then boot into an old kernel and do the
> remove command).
>
> Here is the DSDT info generated for the PS2 section:
>
> Device (PS2)
> {
> Name (_HID, EisaId ("DLL04B0"))
> Name (_CID, Package (0x03)
> {
> EisaId ("SYN0600"),
> EisaId ("SYN0002"),
> EisaId ("PNP0F13")
> })
> Name (CRS, ResourceTemplate ()
> {
> IRQNoFlags ()
> {12}
> })
> Method (_CRS, 0, NotSerialized)
> {
> Return (CRS)
> }
> }
>
> Are those the same codes you get, or is this a different device?
>
Richard -
Yes, "DLL04B0" is the same device. Several thoughts:
* Do you get ANY errors/warnings when building the psmouse.ko dlkm?
* What does "modprobe -v" report? It should be something like
"/lib/modules/3.2.0-30-generic/updates/dkms/psmouse.ko"
* What OS and ver are your running?
* Can you boot up into an Vista/Win7 or run a powerup diagnostic to
confirm it's not a hardware issue?
* Eyeball the crash stack trace and look for any paths through a
psmouse* or alps* function call. Each will have a hex offset. Email me
what you see.
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/606238
Title:
synaptic touchpad not recognized on dell latitude e6510 and others
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/606238/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
Vreixo - responses inline.
On 09/19/2012 09:25 AM, Vreixo Formoso wrote:
> I have been testing last Dave driver on my Inspiron 17R SE. First, I
> have change the line added by Dave on alps_model_data to
>
> { { 0x73, 0x03, 0x50 }, 0x02, ALPS_PROTO_V6, 0xc8, 0xc8, 0 },
>
> because the command mode resp for my touchpad is 0x02 and ALPS_DUALPOINT
> flag makes no sense as this touchpad has not trackstick.
Good to know. I'll drop the ALPS_DUALPOINT for the next driver rev.
>
> After loading the module, it seems the touchpad is detected:
>
> psmouse serio1: alps: E6 report: 00 00 64
> psmouse serio1: alps: E7 report: 73 03 50
> psmouse serio1: alps: alps_enter_command_mode: 73 02 02
> psmouse serio1: alps: ver=5, rsp=02
> psmouse serio1: alps: E6 report: 00 00 64
> psmouse serio1: alps: E7 report: 73 03 50
> psmouse serio1: alps: alps_enter_command_mode: 73 02 02
> psmouse serio1: alps: ver=5, rsp=02
> psmouse serio1: alps: ID 0: 00
> psmouse serio1: alps: 00 00 64: 00 00 64
> psmouse serio1: alps: ID 0: 00
> psmouse serio1: alps: 2-ID 0: c8
> psmouse serio1: alps: 73 03 50: 73 03 50
> psmouse serio1: alps: alps_enter_command_mode: 73 02 02
> psmouse serio1: alps: Addr ec
> psmouse serio1: alps: 0x0008=02
> psmouse serio1: alps: Match bf 1a 04: bf 01 50
> psmouse serio1: alps: Match 89 95 84: 78 79 7b
> psmouse serio1: alps: alps_enter_command_mode: 73 02 02
> psmouse serio1: alps: alps_init: keybit=159FD030
> input: PS/2 Mouse as /devices/platform/i8042/serio1/input/input18
> psmouse serio1: alps: alps_init: success
> input: AlpsPS/2 ALPS GlidePoint as
> /devices/platform/i8042/serio1/input/input19
For my init, "Match" indicates an expected response to the bytes before
the colon. Yours do not match. It may not be a problem.
>
> But it bothers me that both a PS/2 mouse and the AlpsPS/2 touchpad are
> detected. What is the reason for that? Any ideas?
The alps touchpad is an extension of the ps2 protocol. Linux uses a
tree structure to find devices.
>
> In any case, the touchpad does not work. However, when I touch the
> touchpad the events are received by the driver and logged:
>
> psmouse serio1: alps: d: c8 4c 3e 8 24 11 = 588 318 17
> psmouse serio1: alps: d: c8 4c 3e 8 24 11 = 588 318 17
>
> x, y and z values make sense according to how I press the touchpad, so the
> packet format seems similar. However, the mouse pointer doesn't move on the
> screen, and clicks in the touchpad buttons are not logged.
> I guess there is some trouble with the initialization sequence, maybe it is
> different for my touchpad.
>
> For completeness, I paste here the related X logs, if you have any idea
> about how to fix this I would be glad to test it. I would like to use
> the virtual machine stuff to reverse engineering the initialization
> sequence, but I have no time right now.
You're getting the 6-byte alps packets (standard ps2 is 3-bytes) so the
driver is working. I don't log button clicks. The X logs look good
also - consistent with what I see. Base on that the driver is working
and I suspect that something in the X linkage or X configuration is not
working.
Not to point out the obvious but: did you enable the mouse?
Do "xinput --list". For the ps2 and alps device ids, make sure "Device
Enabled" (prop 132) is set to "1" using "xinput list-props ". If
132 is set to "0" the device is disabled. You should be able to use
Fn-F3 to toggle 132.
I'll document how to reverse engineer the alps interface in the next
release. It's fairly time consuming.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/606238
Title:
synaptic touchpad not recognized on dell latitude e6510 and others
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/606238/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
On 09/18/2012 12:11 PM, Richard Merren wrote: > I downloaded Dave's patch in #144 and followed the install instructions > in #152. On reboot, my computer would freeze during boot with the > ubuntu logo and the row of dots. Attempts to boot into "recovery mode" > also did not complete, with freeze for a minute or so and then a > stacktrace/dump scrolling by. I was able to boot into a previous kernel > via GRUB with no problem, and this command successfully removed the > patch from the primary kernel: > > sudo dkms remove -m psmouse -v alps-dst-0.1 --all > > The "--all" was necessary because I was booted into a different kernel > than the one into which this was installed. > > I am on a Dell N5110 with Ubuntu 12.10 beta, x86_64, kernel 3.5.0-14. I > am happy to reproduce and upload any log files that may help. My laptop > is only a few months old, so it may be that Dell has decided to put a > different (and even more incompatible) version of the ALPS trackpad in. > If there is anything I can do to help test, please let me know. > Otherwise I will watch here to see if you post updates and try those > when they appear. Richard - Sorry for your problems. I just uploaded a more stable psmouse dklm. If that still crashes collect the last lines in /var/log/syslog with "psmouse" in the header. In the new README I added a script to pull the touchpad model number from the BIOS. Please run the script and send me the log. Dave -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
I fixed a couple panic situations, added a runtime debug flag and fixed (I think) edge-scrolling. Additionally I segmented the V6 operations from the other protocols so other laptops can uses this without a kernel panic. This driver should work for all known touchpads - it's the from the latest kernel and adds Ben Garami's code for the E6420 and mine for the N5110. All debug is enabled by default. See the README alps_debug script to disable it (which will make the system run a lot faster.) As previously, see the README for instructions. At the bottom of README, I pasted more shell scripts to install, build, run, control my alps touchpad. I spent a little time making the scripts generic but if one doesn't work for you, don't email me asking why. I tested virt and horz edge-scrolling with "good-enough" touchpad boundries when doing input_set_abs_params. I'm sure they can be tuned better. I have not looked at multi-touch yet. It looks to me like the driver alternately detects the location of each finger as a single input and updates the cursor position from that. I need to study the multi-touch controls a little more to figure out what is going on. Same steps as in post #152 except the it's now psmouse-alps-dst-0.2 [1]. [1]: http://www.dahetral.com/public-download -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
Good to see so many people testing this! Yes, it's a first cut and does not include multi-touch. The next rev of the DLKM will include: 1) more diagnostics to ascertain the ALPS model and behavior 2) support all recognized alps touchpads - including Ben Gamari's work on the E6430 (understanding that I can't test anything but the N5110), and 3) hopefully multi-touch. I set the Velocity Scaling to 40 and noticed the cursor jumps sometimes. I don't see any code in the psmouse driver area that explicitly supports edge-scroll so I think it's a generic X capability. However, I think I may have configured the Alps driver for the incorrect touchpad size - which would mean no edges. Dave -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
@quarara Explode the tarball: cd $HOME mkdir Stage tar -jxvf $HOME/Download/psmouse-alps-dst-0.1.tbz This will make a $HOME/Stage/README that should explain everything. It has a couple embedded scripts to build/install the DLKM. I forgot to document the DLKM source needs to be put under /usr/src: cd $HOME/Stage sudo cp -Rvup usr / BTW, you need sudo rights. Look in $HOME/Stage/README for the build_alps shell function to build/probe the driver. See man:dkms for more info. @richard-merren As far as I'm aware, my psmouse DLKM will work for Dell N5110 ONLY because it has a whacky control response code. For entering command mode it expects 0x73 0x01 where all the prior ALPS touchpad models expect 0x88 0x07 so it's hardcoded in the driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
I finally got the Alps touchpad working on a Dell N5110. Briefly, it's a new protocol to init the device and the 6-byte packets coming from it are a new format. I didn't spend much time trying to understand the init sequence, just stuck the qemu packet dump into a new (V6) init function. But it works; probably needs to be tightened up a little. I don't understand the thought process behind the different protocols. It seems like the NRE to keep writing test and production drivers would be unsustainable. I created a psmouse DLKM with a README at [1]. If there's anybody else with an N5110 who wants to try it out please post your results. [1]: http://www.dahetral.com/public-download -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
Discussion on the linux-input list. It looks like the ALPS protocol has been broken for a Dell E6230. I'm still having problems on my Dell Inspiron 15R N5110. --- snip --- On 08/16/2012 01:04 AM, Ben Gamari wrote: > Ben Gamari writes: > > snip >> Hopefully I'll find some more time in the next few days to figure out >> the last few bits (primarily how multitouch events work). I wouldn't be >> sad if someone finished the task for me, however. >> > Success! As it turns out, the process was actually not so bad. While I > wasted much of the night trying to reverse the protocol, I realized that > what I had come up with was nearly identical to the version 3 > documentation. Trying the version 3 protocol with the device, I found > that it was nearly immediately functional. It seems that while the > initialization procedure has changed, the position report format is > identical to previous generations. > > My tree[1] currently has a hacked brute-force initialization > implementation, although it would probably be nice to figure out what > this sequence actually means. Otherwise, it seems support for this device > is a solved problem. > > Feel free to give my tree a try. I'd be interested to know whether it > works for you. > > Cheers, > > - Ben > > [1] https://github.com/bgamari/linux/tree/alps Ben - I tried your fix on a Dell Inspiron 15R N5110 (I15R). It did not work. Things I noticed: 1) Consistent with prior observations, the touchpad E7 signature for it is: 0x73 0x03 0x50, different than yours on the E6230. 2) Your alps_hw_init_v5 sequence does not work for my I15R. I noticed that the sequence enters/exits command mode a couple times. Why not enter once, do the init and then exit? 3) When in command mode, the I15R accurately sets and retrieves registers (e.g. 0x0008 returns 0x00 0x08 0x02). When not in command mode, all register reads return -1. Oddly, the check in alps_enter_command_mode is 0x73 0x01 rather than 0x88 0x07. So I think either I'm doing something wrong or I'm dealing with YAAP (Yet Another ALPS Protocol). My question: how did you get the protocol trace? I think you said previously that the drive does some direct register I/O. I couldn't see anything beyond PS/2 commands running under Virtual Box. Dave -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
@bgamari I started tracking your progress for "New Alps protocol in the wild?" the linux-input list. The signature and command-mode id you report are the same as what I'm seeing on my Dell I15R N5110. Since your discussion seems to be more fruitful there, I'm going to respond there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
See #128 System: Dell I15R N5110, Ubuntu 12.04 I just can't give up on this freakin' bug. Running Linux it's unstable. I tried to reverse engineer using sforshee method (vbox running Vista) and all that is displayed is pure PS/2, no alps_command_mode stuff. So I hacked a small program based on the alps.c driver using serio_raw, then tested on my laptop. Here's what I see so far: * E6, E7 report definitely returns 0x73 0x03 0x50 (an unknown device) * enter command mode/exit command mode work BUT the "enter" return is NOT 0x88 0x07 which is being checked in the alps driver. It returns 0x73 0x01 0x0d. This would cause the device to never enter it's proprietary mode - which is what I'm seeing. * Using the V3 command indicator of PSMOUSE_CMD_RESET_WRAP, register reads return correctly: reg addr is in param[0] and param[1], value is in param[2]. reg8=2, reg6=1, others return 0. Using the V4 indicator of PSMOUSE_CMD_DISABLE results in bad register reads. I haven't coded a register write function yet. This step confirms that I'm in the proprietary command mode for the Alps device. My guess is the Alps device is either a new V3 instance or a totally new instance (V5?) I think the Dell Alps driver doesn't understand it either so it drops into pure PS/2, and probably has more elegant handling of the touchpad input when typing. I messed around with the syndaemon -i and -t arguments, which seemed change the behavior but not to my satisfaction. I need to work on other stuff for a little bit but will get back to this. I'll ping Dell on their newsgroups to see if I get any response. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
See my post in comment 126... I thought I was getting closer but it seems like a dead end. The ALPS touchpad on my Dell I15R N5110 has an E7 signature of 73 03 50. When I do a vbox capture it spits out pure PS/2 mouse commands and responses, nothing specific to the ALPS driver. I'm getting the exact behavior as this thread: https://patchwork.kernel.org/patch/1162831/ I'm running Windows Vista with the Alps 7.2.101.224 driver, which appears to be stable when I'm not doing a serio_raw capture. It is listed as a "Dell Touchpad" in the Device Manager One thing I need to research more is from this: dturvene@growler:539$ xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Logitech USB Mouseid=12 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS GlidePoint id=15 [slave pointer (2)] ⎜ ↳ PS/2 Mouseid=13 [slave pointer (2)] The ALPS driver is being used (I can see it's output in system logs) but all control is on the PS/2 Mouse id. For example: xinput "set-prop 13 132 0" disables the touchpad but "xinput set-prop 15 132 0" does nothing. Is the ALPS driver defaulting to a pure PS/2 mode and some secret command sequence gives it enhanced super powers? I messed around with the Vista control panel in serio="psmouse" mode and didn't see anything significant. The driver works fine, even with typing fast, which under Ubuntu causes the pointer to jump to the cursor location. In the Vista driver, there is very limited control of the mouse though (e.g. cannot disable tap-to-click) so maybe it's a very simple piece of hardware. Not much where the driver is install at c:\program files\delltpad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
@sforshee Oops, forgot to add the vbox log attachment. ** Attachment added: "vbox startup log using export VBOX_LOG="+dev_kbd.e.l.f"" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/606238/+attachment/3228772/+files/vbox.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
@sforshee System: Dell Inspiron 15R-5294BK running Ubuntu 12.04 LTS I was messing around in Virtualbox (4.1.18) for something else and had a chance to follow your touchpad reverse engineering notes. The API has been updated a little. However, I captured the attached exchange three times. I blew away the psmouse-alps.0.10 source from your home, and it appears you removed it, so I don't have a vehicle to test with. Attached is the vbox dump using bash> export VBOX_LOG="+dev_kbd.e.l.f". Since only one attachment per comment, I have pasted the entire local log here. So what's the next step? S ff R fa R aa R 00 S ff R fa R aa R 00 S f2 R fa R 00 S e8 R fa S ff R fa R aa R 00 S f2 R fa R 00 S e8 R fa S ff R fa R aa R 00 S f2 R fa R 00 S e8 R fa ** Attachment added: "vbox log using export VBOX_LOG="+dev_kbd.e.l.f"" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/606238/+attachment/3228769/+files/vbox.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
Dell I15R N5100 running Ubuntu 12.04 LTS. I've just marked 678103, 737051, 903236 as dups to this bug. Each has similar symptoms at root and seems to deal with the ALPS touchpad through the synaptics interface. Some solutions seem to revolve around the X setup but I couldn't make any work reliably. I put a fairly lengthy comment of my research at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/737051 I used the DKM driver at http://people.canonical.com/~sforshee/alps- touchpad/psmouse-alps-0.10/psmouse-alps-dkms_0.10_all.deb and added an E7 include of 0x73, 0x03, 0x50 to recognize my touchpad. Better but still getting spurious cursor movement and mouse refocus. I'm going to look at forshee touchpad reverse engineering doc for some clues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 678103] Re: Dell Inspiron N Series, Touchpad recognised as generic PS/2 mouse
*** This bug is a duplicate of bug 606238 *** https://bugs.launchpad.net/bugs/606238 ** This bug has been marked a duplicate of bug 606238 synaptic touchpad not recognized on dell latitude e6510 and others -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/678103 Title: Dell Inspiron N Series, Touchpad recognised as generic PS/2 mouse To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/678103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 737051] Re: [regression] Alps touchpad detected, but scrolling not working
*** This bug is a duplicate of bug 606238 *** https://bugs.launchpad.net/bugs/606238 ** This bug has been marked a duplicate of bug 606238 synaptic touchpad not recognized on dell latitude e6510 and others -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/737051 Title: [regression] Alps touchpad detected, but scrolling not working To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/737051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 773165] Re: Touchpad is recognized as PS/2 and ALPS simultaneously
*** This bug is a duplicate of bug 606238 *** https://bugs.launchpad.net/bugs/606238 ** This bug is no longer a duplicate of bug 737051 [regression] Alps touchpad detected, but scrolling not working ** This bug has been marked a duplicate of bug 606238 synaptic touchpad not recognized on dell latitude e6510 and others -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/773165 Title: Touchpad is recognized as PS/2 and ALPS simultaneously To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/773165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 903236] Re: Touchpad incorrectly detected as PS/2 mouse on Dell Inspiron 15R N5110
*** This bug is a duplicate of bug 606238 *** https://bugs.launchpad.net/bugs/606238 ** This bug has been marked a duplicate of bug 606238 synaptic touchpad not recognized on dell latitude e6510 and others -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/903236 Title: Touchpad incorrectly detected as PS/2 mouse on Dell Inspiron 15R N5110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/903236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 903236] Re: Touchpad incorrectly detected as PS/2 mouse on Dell Inspiron 15R N5110
Just came across this bug report... I'm having the same problem and diagnosed, adding a comment to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/737051 I've got the psmouse-alps-0.10 driver installed and put a couple printk's in so I know it's being hit. However, there are still spurious taps and mouse focus events being generated when I type. See my comment in 737051 for the steps I've tried. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/903236 Title: Touchpad incorrectly detected as PS/2 mouse on Dell Inspiron 15R N5110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/903236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 737051] Re: [regression] Alps touchpad detected, but scrolling not working
I installed the psmouse with ALPS support from #57 and it works better but is still buggy. I still get occasional spurious refocus actions even when typing and xinput watch-props says "Synaptics Off" is set. I'm using 12.04 LTS on a Dell I15R. Current issue: * syndaemon must be running in the background. I messed around with the -i times, while using xinput watch-props ID (the ALPS device id from xinput --list and it seems like it works. The higher the times, the longer "Synaptics Off" property is disabled after typing. However, I still seem to get spurious pointer refocus actions even when the "Synaptics Off" is set. * I tried to disable tap-to-click using xinput set-prop on various ALPS Tap properties. Another post said xinput set-prop 14 546 0 (set the prop id for "Synaptics Tap Time" to 0) will disable tap-to-click, but I saw no change. * I can disable the ALPS touchpad by doing xinput set-prop 12 132 0 (On the psmouse device id, set prop id for "Device Enabled" to 0) but this has no effect on the ALPS device. * I messed around with different values in /etc/modprobe.d/psmouse.conf for "options proto" but all were worse than the built driver. * I put some printk debug in the driver but it just confirmed what I was seeing. Tap-to-click and the buttons generate the same codes to the driver. alps_tap_mode defaults to enable tap, but when I set it to disable tap, the tap is still enabled. I sent a request to ALPS with a specific request for the tap disable sequence, but (as expected) no response. * I added known values to /etc/X11/xorg.conf.d/50-synaptics and verified they were set using xinput list-props 14, but that did not seem to affect anything. * I do Fn-F3 while monitoring the ALPS device (14) and it shows a bunch of changes with no visible result (e.g. "Device Enabled" toggles but does not enable/disable the touchpad. I monitor the psmouse device and see no changes. This is consistent with disabling the touch pad using xinput set-prop on the psmouse device. I'll continue to investigate because it bugs (no pun) me that I can't groom this to my liking. I suspect the control protocol to my version of the ALPS touchpad may be different than previous AND that 12.04 does not accurately recognize the ALPS touchpad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/737051 Title: [regression] Alps touchpad detected, but scrolling not working To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/737051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 678103] Re: Dell Inspiron N Series, Touchpad recognised as generic PS/2 mouse
Uggh. In my instructions "dkms add" should be changed to "dkms build". Also, to rebuild (e.g. add dbg statements), the simplest way is sudo dkms remove psmouse/alps-0.10 --all to remove package. "psmouse/alps-0.10" is an alternative to "-m psmouse -v alps-0.10" Dave -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/678103 Title: Dell Inspiron N Series, Touchpad recognised as generic PS/2 mouse To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/678103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 678103] Re: Dell Inspiron N Series, Touchpad recognised as generic PS/2 mouse
Well, after a day of testing I think something is still wrong, only less so. I still get occasional spurious focus changes. It only happens when I'm typing really fast. And then the focus changes to where I rested the cursor. Still, it happens a lot less frequently. @quarara: Yeah, it's a little detailed. Basically, I built a Dynamic Kernel Module for the psmouse driver, taking the source from http://people.canonical.com/~sforshee/alps-touchpad/psmouse-alps-0.10/psmouse-alps-dkms_0.10_all.deb It's the same patch sergiomb discusses. The step-by-step instructions are (taken from an askubuntu post), MUST USE sudo: * dpkg -i psmouse-alps-dkms_0.10_all.deb * cd /usr/src/psmouse-alps-0.10/src * edit alps.c, copy the line with the Vostros 1400 comment to the end of the array and change 0x73, 0x02 to 0x73, 0x03. This creates a new description for the I15R. BTW, DEBUG is defined so the driver will log to dmesg (/var/log/kern.log on my system) * dkms add -m psmouse -v alps-0.10, which builds the module. This is where I got the compile error and removed alps.c#136. * dkms install -m psmouse -v alps-0.10, which installs the new driver * rmmod psmouse && modprobe psmouse, which removes the old driver and loads the new one * dmesg for lines beginning with alps.c * xinput --list to see "PS/2 ALPS GlidePoint" * syndaemon -i 2.0 -K -R -t to change keystroke to touchpad delay. ALternatively use can use the Settings->Mouse and Touchpad->Touchpad screen, enabled by the ALPS driver, to mess around with this. * xev to test touchpad and buttons Complicated, and you need to be somewhat familiar with kernel drivers, but HTH. Dave -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/678103 Title: Dell Inspiron N Series, Touchpad recognised as generic PS/2 mouse To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/678103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 678103] Re: Dell Inspiron N Series, Touchpad recognised as generic PS/2 mouse
Oh, one thing I should add is that the module_param definition in alps.c:135 gives a compile error. I set alps_dump_packet=1 and commented out #135. I'm not familiar with linux 3 driver frameworks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/678103 Title: Dell Inspiron N Series, Touchpad recognised as generic PS/2 mouse To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/678103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 678103] Re: Dell Inspiron N Series, Touchpad recognised as generic PS/2 mouse
I just got a Dell Inspiron 15R, installed precise and updated. The current kernel is 3.2.0-24-generic-pae. The problem still exists, and was frustrating me. I fixed it (hopefully) by following the instructions on this thread to add the ALPS awareness in the psmouse driver: http://askubuntu.com/questions/104431/how-do-i-enable-multi-touch-on-a -dell-inspiron-n5110-with-an-alps-touchpad and then tuning the delay using sudo syndaemon -i 2 -k -t -R It appears to be working much cleaner. It's a tricky problem, and one that many people will like different solutions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/678103 Title: Dell Inspiron N Series, Touchpad recognised as generic PS/2 mouse To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/678103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 589043] Re: Evince does not use proper print margins
I had similiar symptoms and found this issue report. Using 10.04 and evince 2.30.3, the top margin is too big and the bottom is too small. CUPS is working fine and man:lpoptions -l shows the correct PageSize. Other programs (e.g. a2ps) print accurately. So either 1) evince is broken or 2) it is using config beyond CUPS. I found the $HOME/.gnome2/evince directory, which contains print-settings. This file has PPDNAME=A4. When I set evince print->page setup->paper size to "US Letter", it prints with correct margins. Once changed, the printer-settings file is updated with "US Letter". It's unclear why evince needs an additional printer control layer beyond CUPS, perhaps for portabiltiy. Setting issue to Invalid state ** Changed in: evince (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/589043 Title: Evince does not use proper print margins -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665603] Re: package emacs22 22.2-0ubuntu6.2 failed to install/upgrade:
Here is the /tmp/emacs22.* log file when trying to re-install emacs22:: emacs-install emacs22 install/a2ps: Handling install for emacsen flavor emacs22 cd: 35: can't cd to /usr/share/emacs/site-lisp/a2ps emacs-install: /usr/lib/emacsen-common/packages/install/a2ps emacs22 failed at /usr/lib/emacsen-common/emacs-install line 28, line 4. Seems similar to this issue https://bugs.launchpad.net/ubuntu/+source/emacs22/+bug/281766 There are package install/remove for emacsen a2ps but no package. I moved /usr/lib/emacsen-common/packages/install/a2ps and ../remove/a2ps and it looks like emacs is upgrading okay. My guess is the emacsen a2ps package was automatically removed on an upgrade but the packages scripts were not removed. -- package emacs22 22.2-0ubuntu6.2 failed to install/upgrade: https://bugs.launchpad.net/bugs/665603 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665603] Re: package emacs22 22.2-0ubuntu6.2 failed to install/upgrade:
-- package emacs22 22.2-0ubuntu6.2 failed to install/upgrade: https://bugs.launchpad.net/bugs/665603 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665603] [NEW] package emacs22 22.2-0ubuntu6.2 failed to install/upgrade:
Public bug reported: Binary package hint: emacs22 Upgrading from 9.04 to 9.10 via upgrade manager. I use emacs for almost everything and have a heavy .emacs file that loads a lot of libraries. I strongly suspect it's my .emacs. I'm currently running emacs 22.2.1 but not sure if that is pre- or post-upgrade. I will restart as 9.10 and try to do a manul upgrade of emacs. ProblemType: Package Architecture: i386 Date: Sat Oct 23 10:28:54 2010 DistroRelease: Ubuntu 9.10 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 NonfreeKernelModules: nvidia Package: emacs22 22.2-0ubuntu6.2 ProcVersionSignature: Ubuntu 2.6.28-19.66-generic SourcePackage: emacs22 Title: package emacs22 22.2-0ubuntu6.2 failed to install/upgrade: Uname: Linux 2.6.28-19-generic i686 ** Affects: emacs22 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 -- package emacs22 22.2-0ubuntu6.2 failed to install/upgrade: https://bugs.launchpad.net/bugs/665603 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 565810] Re: packages.medibuntu.org not available
DNS entry for 88.191.82.11 pings but times-out on livdvdread4/install- css.sh. I hardcoded name packages.medibuntu.org to 88.191.101.8 and install worked fine (surprisingly quick considering I'm in the U.S.) True, it's a temp fix but I frequently (40-50/year) hardcode /etc/hosts to override stale DNS entries. When the DNS servers are fully updated I remove the entry from /etc/hosts. -- packages.medibuntu.org not available https://bugs.launchpad.net/bugs/565810 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 301571] Re: GMenuSimpleEditor breaks buildout
datakid is correct, and the bug he/she references fixes the problem. The root fault: * buildout uses python modules from /usr/share/pyshared * In 8.10, for some reason, /usr/share/pyshared/GMenuSimpleEditor does not exist so the softlinks fail. As the referenced bug report states, a complete module exists in /usr/share/python-support/python-gmenu/GMenuSImpleEditor so link it into the pyshared area area sudo ln -s /usr/share/python-support/python-gmenu/GMenuSimpleEditor/ /usr/share/pyshared/ buildout runs to completion after that. On my system this seems to be an issue with 8.10 (Ibex) Ubuntu python installation changes OR with some dead soft links after 8.04->8.10 upgrade (which is more likely). I think another solution would be to reinstall python 2.4. -- GMenuSimpleEditor breaks buildout https://bugs.launchpad.net/bugs/301571 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 289986] Re: wireshark/tshark promiscuous capture on wireless interface locks up machine
Complete system lockup happens to me on a Dell M1530 with an Intel 3945 wireless card running 8.0.4 with a recently installed wireshark: > apt-cache policy wireshark wireshark: Installed: 1.0.0-1 Candidate: 1.0.0-1 Version table: *** 1.0.0-1 0 500 http://us.archive.ubuntu.com hardy/universe Packages 100 /var/lib/dpkg/status Don't know why the original bug report is at a higher level (wireshark 1.0.2-1) The root problem is in dumpcap. Running it without going into promisc mode works fine. -- wireshark/tshark promiscuous capture on wireless interface locks up machine https://bugs.launchpad.net/bugs/289986 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
