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
