Re: [debian] Accerlerom. stop on movement, known issue / only for me?
On Mon, 2 Feb 2009 08:17:02 -0600, The Digital Pioneer digitalpion...@gmail.com wrote: Yeah, this is happening all across the board. Some bug in the kernel. If you just try flashing kernels, you'll probably come across one that doesn't have this sooner or later. I use mwester's kernel, and finally got rid of that bug. (I use SHR, too, it's not a Debian issue) I see, thanks for letting me know! :) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] Accerlerom. stop on movement, known issue / only for me?
Yeah, this is happening all across the board. Some bug in the kernel. If you just try flashing kernels, you'll probably come across one that doesn't have this sooner or later. I use mwester's kernel, and finally got rid of that bug. (I use SHR, too, it's not a Debian issue) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[debian] Accerlerom. stop on movement, known issue / only for me?
Hello, I remember there was a thread about accelerometers in Debian and I think they should not work correctly. I can't find it any more. So I recently played around with the accelerometers using Debian and found _some_ output from both /dev/input/event2 and event3. It seems not to be realistic what I receive from the hexdump, and when I move the FR the whole Output is stuck. This also happens when I use the python or perl script from the wiki. So I just wanted to check if this is the behavior caused by the accelerometers not working yet? Or are accelerometers in Debian fixed and this is only happening to me? Thanks and best regards, Daniel ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
