- <BurritoBazooka> Hey, a friend of mine (who has unfortunately gone to bed) installed Crunchbang on his Advent 7040. It has a bug where sometimes the left or right mouse buttons stop responding (most of the time while pressed, Crunchbang wouldn't respond to it being unpressed). He says that it did not happen on Windows XP. I didn't really know how to get more info from the bug, but demsg had this:
- <BurritoBazooka> atkbd.c: Use 'setkeycodes 66 <keycode>' to make it known.
- <BurritoBazooka> which appears to be related to the keyboard, not the mouse.
- <BurritoBazooka> anything I can tell him in the morning to get more info on the bug?
- <BurritoBazooka> dmesg*
- <BurritoBazooka> I've got no experience in Openbox or lightweight things like that so I couldn't help him much either >_>
- <BurritoBazooka> He used his laptop's internal touchpad, btw.
- <BurritoBazooka> I can tell him to come here tomorrow so that I don't have to be a proxy to him.
- <alazare619> sounds like his mouse and keyboard are ran on the same interface
- <alazare619> along with any softkeys as well
- <alazare619> and its quiet possibly faulting at the kernel level
- <alazare619> to check tho id recommend he try out xfce or gnome or kde to test tho
- <alazare619> or even just drop to terminal or shell login
- <BurritoBazooka> oh right..
- <alazare619> at terminal level just spam the clicks then fire up his gui
- <alazare619> and see if the moue responds
- <BurritoBazooka> alright. Would it work to try a USB mouse?
- <BurritoBazooka> It's quite frustrating when the trackpad derps out. And it may be handy to use a backup.
- <BurritoBazooka> I found one solution which is to install xserver-xorg-input-evdev from one of the Ubuntu PPAs. But I dunno if that would work on Crunchbang. It's not Ubuntu afterall.
- <BurritoBazooka> alazare619, here's a more informative dmesg output I think. The first one I pasted was a fragment from a google search I did on it. But I found the chat log.
- <BurritoBazooka> [ 2670.822366] atkbd.c: Use 'setkeycodes 66 <keycode>' to make it known.
- <BurritoBazooka> [ 2670.878025] atkbd.c: Unknown key released (translated set 2, code 0x66 on isa0060/serio0).
- <BurritoBazooka> [ 2670.878034] atkbd.c: Use 'setkeycodes 66 <keycode>' to make it known.
- <alazare619> he may try checking xorg.conf
- <alazare619> or config...
- <alazare619> pretty sure its .conf
- <alazare619> cant remember been dealing with windows all day
- <BurritoBazooka> alazare619, okay
- <BurritoBazooka> I'll write all that down :V
- <alazare619> it looks like its fauling id check xorg for sure tho and also see if there is a firmware available in the repo
- <alazare619> but first try a usb keyboard and mouse see if it doesnt solve it if it does its probably related to a firmware thats needed
- <alazare619> also that ppa will work if its available for lucid
- <BurritoBazooka> okay.
- 1. Get USB mouse
- 2. Check xorg.conf
- 3. Try xfce, or drop to terminal, spam clicks, see if mouse responds.
- 4. Try and find supported firmware in #! or deb repos
- 5. Try the PPA - xserver-xorg-input-evdev in ppa:xorg-edgers/ppa
Posted by Burrito on Fri 18th May 02:28 (modification of post by view diff)
download | new post
Submit a correction or amendment below (click here to make a fresh posting)
After submitting an amendment, you'll be able to view the differences between the old and new posts easily.