Ticket #64 (closed defect: worksforme)

Opened 4 years ago

Last modified 3 years ago

wminput failure under centos / rhel 5.1

Reported by: cycon Owned by: dsmith
Priority: major Milestone:
Component: build system Version: 0.6.00
Keywords: Cc:

Description

I'm able to get cwiid 0.6.00 to compile without issue under Centos 5.1 (based of RHEL), so long as I used the flex patch included in this SRPM from rpmforge's Dag repository:

http://packages.sw.be/cwiid/

After building the software, installing the "uinput" module, and starting the bluetooth service, I can successfully connect to and run all functions under wmgui, as well as the wmdemo.py script for the Python module.

However, "wminput" from the command line simply doesn't work and produces no output.

For example, under fedora 9, after I run wminput, I get the request:

Put Wiimote in discoverable mode now (press 1+2)...

which is of course what I also see from the python module and in the graphical dialog box under wmgui.

Unfortunately, as wminput itself does not seem to function, I cannot therefore use the IR pointer facilities of the wiimote.

I'm happy to test any patches or SVN revisions, or help investigate further with a little direction.

Change History

follow-up: ↓ 2   Changed 4 years ago by dsmith

Are there any errors at all? Anything interesting in dmesg? Any diagnostics would be helpful.

in reply to: ↑ 1   Changed 4 years ago by cycon

Replying to dsmith:

Are there any errors at all? Anything interesting in dmesg? Any diagnostics would be helpful.

No, I'm sorry, no output whatsoever. It just hangs on the newline. Nothing in dmesg.

Is there a way to enable verbose debug messages, perhaps a macro in the source? There's nothing in the --help output.

  Changed 4 years ago by dsmith

Most of the errors should already be displayed.

Try this: When wminput starts up, it should create a new /dev/input/eventX file, where X is a number. See if it creates this file by comparing ls /dev/input before and after starting wminput. If a new event device file is created, try catting it to see if it's generating events - if cat /dev/input/eventX generates output (it'll be gibberish to human eyes), it is generating events, and I'd suspect an X configuration error: the wminput README has some notes on how to properly set up your xorg.conf. On the other hand, if a file isn't created, or it is, but nothing comes out of it, you've got a more interesting problem.

  Changed 4 years ago by cycon

I managed to build new RPMS, based off the Fedora 9 SRPM, and building Flex 2.5.33 (a requirement for the configure script) from Fedora 8 SRPM. wminput seems to work fine under this new build, so not sure it was a software bug after all (at least not with cwiid).

I've created a repository and released the RPMS and SRPMS here:

http://www.eyemagnet.com/repo/eyemagnet.repo

Please feel free to use at will.

Thanks again for the help.

  Changed 3 years ago by dsmith

  • status changed from new to closed
  • resolution set to worksforme
Note: See TracTickets for help on using tickets.