I have an Dell Inspiron 8500 which an ALPS dualpoint device. This thing has the touchpad and one of the eraser nub pointing sticks. there are also 2 sets of buttons. With 2.6.11-gentoo-r4 the stick doesn't work anymore. The buttons don't respond either. If I boot to windows first, the stick will work, but the buttons for the stick still don't respond. ALPS Touchpad (Dualpoint) detected input: AlpsPS/2 ALPS TouchPad on isa0060/serio1 The kernel does properly detect this device though.
*** This bug has been marked as a duplicate of 84657 ***
Re-opening as per comment 37 in bug #84657
> Bug 85932 was made a duplicate of this bug. It's the trackpoint not working on > my dell inspiron 8500 with an alps dualpoint device. This is still not fixed in > 2.6.12. It's also intermittent (was before too) if i reboot a few times, > sometimes the trackpoint will initialize, other times it will not. Perhaps my > bug should be re-opened standalone since it doesn't seem to be the same problem. I also have an 8500, I saw this in the past but on the 2.6.12 kernel the only time the stick dies for me is after a suspend/resume cycle. What's the exact kernel version that you are using?
I'm using 2.6.12-gentoo-r4. Just built it today. I haven't ever actually got suspend/resume to work ever, so I wouldn't know if that's where it's breaking :). If you have, would you be willing to e-mail me any scripts you have?
(In reply to comment #4) > I'm using 2.6.12-gentoo-r4. Just built it today. Could you attach your kernel config so I can try your exact kernel/config, and check to see if there is any in /proc/bus/input/devices between when it works and when it doesn't. Might as well also do a cat on /dev/input/mouse0 or mouse1 (which ever one it is on your system) when it isn't working and try to fiddle with the mouse to check that it is indeed the kernel doing it. > I haven't ever actually got suspend/resume to work ever, so I wouldn't know if > that's where it's breaking :). > > If you have, would you be willing to e-mail me any scripts you have? lets keep this bug on alps, I should post some documentation on what I'm doing on my system sometime. :-)
(In reply to comment #5) > (In reply to comment #4) > > I'm using 2.6.12-gentoo-r4. Just built it today. > > Could you attach your kernel config so I can try your exact kernel/config, and > check to see if there is any in /proc/bus/input/devices between when it works *any difference in* > and when it doesn't. Might as well also do a cat on /dev/input/mouse0 or mouse1 > (which ever one it is on your system) when it isn't working and try to fiddle > with the mouse to check that it is indeed the kernel doing it.
Try this patch on for size: http://dev.gentoo.org/~marineam/files/alps-dell8500-dualpoint.patch it fixes the resume issue for mine, maybe it'll fix your's as well. If that still doesn't work, open up drivers/input/mouse/alps.c and change #undef DEBUG to #define DEBUG and post the alps.c: dmesg lines that pop up.
Hrm, that might not actually fix anything at all... there's something else funky going on here.
This hasn't occured in a few weeks. I haven't rebooted my laptop very often though. I am 100% sure that there were at least 1 or 2 boots since going to 2.6.12-gentoo-r4 that my alps pointing stick did not work (but the touchpad did). But it hasn't happened in quite some time. I probably won't have time to test this more thoroughly for a few weeks though, but when I do, I'll see what I can find.
It's just one of those magical things I think, with acpi resume (the only way I have seen a similar issue on recent kernels) I managed to make things work differently by just adding some printk statements here and there. I didn't get far enough to see where the timing was being weird though. hopefully I'll get back to this one soon.
If this bug is still present in 2.6.13 and you have some time to give us some more info, then please reopen this bug.
I was able to reproduce this problem one more time after my last post. However, i did something stupid and had to reboot before I could gather any more information and since then it hasn't occurred again. I'm thinking I agree with Micheal that it's some kind of horrible timing thing that causes it to happen.
