Created attachment 16290 [details] xorg-log-crash.txt The following device does not work: Bluetake Bluetooth Presenter BTU-01 It creates a /dev/input/event** but then nothing else is configured. When trying to use the evdev driver and the xorg file, xorg crashes. Please make the device work out of the box after input device is created. See all the attached log files for more information. I use debian sid for testing and development.
Created attachment 16291 [details] xorg.conf
Created attachment 16292 [details] evtest-log.txt
Created attachment 16293 [details] data.bin
Created attachment 16294 [details] Bluetooth - Bluetake Presenter BTU-01.txt
Created attachment 16295 [details] bluetake.sh
I use debian sid, this should result in the latest released evdev driver. version 1:1.2.0-1 xserver-xorg-input-evdev I am willing to sent the device to a developer if he agrees to get it working.
looking at the evtest output, there's a number of buttons that aren't parsed properly (or known to the kernel). the second problem is that evdev 1.2 does a bit of automatic parsing, and - like in your case - it sometimes fails. It would be much easier to debug if you get the git version of evdev which is severely stripped down and slightly less prone to errors like this. as it is right now, I can't even fathom what exactly causes the crash.
I will test everything again with the latest git and report back, thank you for the message
I bought the same device which has some unique features: - uses bluetooth (not a seperate dongle) - includes laser pointer - fits into a pcmcia slot (always with you) - very affordable (15 Euro on Ebay) Since Jelle offered to send it to someone who can debug it, maybe it helps to show what it looks like: http://www.amazon.com/Bluetake-BTU-01-Bluetooth-Laser-Presenter/dp/B00138W7DG I am willing to send one to a developer as well if someone can get the buttons and mouse functionality to work.
The status just changed to: NEEDINFO What info is wanted: I now use the newest release of evdev: xserver-xorg-input-evdev_1.2.0-1_i386.deb I still got a non working device :-S Thanks in advance,
On Thu, Jun 12, 2008 at 01:33:12AM -0700, bugzilla-daemon@freedesktop.org wrote: > What info is wanted: > > I now use the newest release of evdev: > xserver-xorg-input-evdev_1.2.0-1_i386.deb please try xf86-input-evdev-1.99.4 which has been released recently. ftp://ftp.x.org/pub/individual/driver/xf86-input-evdev-1.99.4.tar.bz2 this codebase is much more straightforward and easier to debug if problems occur.
On Thu, Jun 12, 2008 at 10:45:04AM -0700, bugzilla-daemon@freedesktop.org wrote: > The status just changed to: NEEDINFO > > What info is wanted: > > I now use the newest release of evdev: > xserver-xorg-input-evdev_1.2.0-1_i386.deb > > I still got a non working device :-S As Peter said, right here: > please try xf86-input-evdev-1.99.4 which has been released recently. > > ftp://ftp.x.org/pub/individual/driver/xf86-input-evdev-1.99.4.tar.bz2 > > this codebase is much more straightforward and easier to debug if problems > occur. 1.99.4 is not 1.2.0 ...
Ok some updates; I am now using version 1.2.0 of evdev and run some new test, i still got the same bugs, i made new logs of them and attached them. xserver-xorg-input-evdev_1.2.0-1_i386.deb I hope somebody can fix the problem?
Created attachment 17504 [details] evtest-log-v1.2.0-1.txt
Created attachment 17505 [details] xorg-conf-v1.2.0-1.txt
Created attachment 17506 [details] xorg-crash-log-v1.2.0-1.txt
> --- Comment #13 from Jelle de Jong <jelledejong@powercraft.nl> 2008-07-03 14:26:31 PST --- > Ok some updates; I am now using version 1.2.0 of evdev and run some new test, i > still got the same bugs, i made new logs of them and attached them. you were running evdev 1.2 before already, we'd need you to run evdev 2.0 though to debug this issue. evdev 1.2 is essentially orphaned and I'd be surprised if there will be any patches to it in the future.
(In reply to comment #17) > > --- Comment #13 from Jelle de Jong <jelledejong@powercraft.nl> 2008-07-03 14:26:31 PST --- > > Ok some updates; I am now using version 1.2.0 of evdev and run some new test, i > > still got the same bugs, i made new logs of them and attached them. > > you were running evdev 1.2 before already, we'd need you to run evdev 2.0 > though to debug this issue. > > evdev 1.2 is essentially orphaned and I'd be surprised if there will be any > patches to it in the future. > My excuse, i overlooked the version, wanted to be the right one to much I guess. I will wait until the maintainer of debian sid decide to upgrade to evdev 2.0 or somebody else to provide a deb package.
> --- Comment #18 from Jelle de Jong <jelledejong@powercraft.nl> 2008-07-04 00:08:57 PST --- > My excuse, i overlooked the version, wanted to be the right one to much I > guess. I will wait until the maintainer of debian sid decide to upgrade to > evdev 2.0 or somebody else to provide a deb package. any updates? I guess by now sid uses evdev 2.0?
Created attachment 18912 [details] evdev 2.0.3 - debug report - bluetake presenter btu-01.txt
I did some new testings, xorg does not crashes any more but tells me it don't now how to use the device. So the device does not work yet. Please see the below attachement. http://bugs.freedesktop.org/attachment.cgi?id=18912
On Tue, Sep 16, 2008 at 01:01:00AM -0700, bugzilla-daemon@freedesktop.org wrote: > I did some new testings, xorg does not crashes any more but tells me it don't > now how to use the device. So the device does not work yet. Please see the > below attachement. All the keycodes your device report are above 255 (for some myserious reason, they even _start_ at 256), which X can't deal with right now due to a protocol limitation.
WONTFIX. We can't do anthing until we support keycodes > 255
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.