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
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
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
--
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
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
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
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
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
@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?
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
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
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
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
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
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
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
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
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
@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
@ 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
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
@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
@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
@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
@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
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:
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,
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
@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
** 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
@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
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
@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
@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
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
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
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
*** 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,
*** 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
*** 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,
*** 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,
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
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
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.
@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
@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
** 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
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:
@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
@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
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
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
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:
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
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
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
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
@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
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 bgamari.f...@gmail.com writes:
snip
Hopefully I'll find some more
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
@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
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
62 matches
Mail list logo
