You are not logged in.
Pages: 1
I was anxiously awaiting kernel 3.1 so that I could have a play around with a Wiimote on my PC. Now that I'm all upgraded I'm not able to actually pair with it. Has anyone else managed to get their wiimote working with the kernel drivers?
I can't find any post-3.1 info on the subject except for: https://wiki.archlinux.org/index.php/XWiimote
Offline
I've discovered that there is a bluez 4.96-2 PKGBUILD available which has the "--enable-wiimote" flag enabled. I've built and installed this version but am still having no luck with the supposed new easy-to-pair wiimote support.
Has anyone else managed to make it work?
Offline
I am having the same problem. Has anyone gotten this to work. The default gnome bluetooth setup wizard fails immediately after selecting the device and clicking next, and bluez-simple-agent fails as well saying i put in the wrong pin. Im going to try it with blueman now.
Dell XPS M1330 : Core 2 Duo, 4GB RAM, 32-bit, GNOME 3
Offline
I got it to work with blueman-applet
to set it up you need to put the wiimote in discovery mode" press1+2
then in blueman-applet choose the wiimote it should be Nintendo RVL-blablabla and click "setup..."
from there choose proceed without pairing, make sure it is still discoverable and you then you should be able to connect to input service. from there it should work.
Dell XPS M1330 : Core 2 Duo, 4GB RAM, 32-bit, GNOME 3
Offline
asjimene, are you using Bluez with wiimote support enabled (ie. 4.96-2)?
If the wiimote isn't paired then auto-connect isn't possible and we're not using the new Bluez feature at all.
Offline
no I'm using the 4.96-1 from the normal repos
and i see what you mean about the autoconnect,
Where did you get the newer version of BlueZ?
Dell XPS M1330 : Core 2 Duo, 4GB RAM, 32-bit, GNOME 3
Offline
http://projects.archlinux.org/svntogit/ … ages/bluez
Same version (4.96) but with the --enable-wiimote option enabled.
Offline
Ok so I downloaded the PKGBUILD and the other 2 files on that page, It wouldn't build because http://www.kernel.org/pub/linux/bluetooth/ doesn't contain anything
so I went online and found the correct package bluez-4.96 here: http://mirror.anl.gov/pub/linux/bluetooth/ ,copied it into the folder with the PKGBUILD
changed the PKGBUILD so it didn't look for the file online anymore and successfully built the package and installed it.
From there I rebooted my computer and tried to pair the WiiMote with my computer through the GNOME bluetooth applet, with automatic PIN and it actually worked.
Then to test it I put my computer to sleep and waited till the wiimote turned off then brought my computer back from sleep, pressed a button on the wiimote and it automatically connected! success!
update: Tested to see if it would still reconnect after a full shutdown and it did.
Last edited by asjimene (2011-12-19 23:40:50)
Dell XPS M1330 : Core 2 Duo, 4GB RAM, 32-bit, GNOME 3
Offline
My guess is the problem must be with bluez-simple-agent. It mustn't know how to handle the auto-pin.
Thanks for your feedback.
Offline
My guess is the problem must be with bluez-simple-agent. It mustn't know how to handle the auto-pin.
Thanks for your feedback.
Sounds possible, I tried to set up mine with bluez-simple-agent, and it wouldn't even run. Just to check, you do have "hid-wiimote" in your modules, in your rc.conf right? That's the only other thing I can think of that would cause it not to pair.
EDIT: bluez was updated on the 20th with wiimote support, so using the PKGBUILD is unnecessary, just pacman -Syu. The gnome bluetooth wizard does find and pair with my wiimote with the new bluez. Now if someone could just tell me how to change the default button mappings.
Last edited by asjimene (2011-12-21 18:20:55)
Dell XPS M1330 : Core 2 Duo, 4GB RAM, 32-bit, GNOME 3
Offline
My guess is the problem must be with bluez-simple-agent. It mustn't know how to handle the auto-pin.
Thanks for your feedback.
No. You can use whatever agent you want. Either the bluez-simple-agent, the gnome-bluetooth applet or blueman. They all work the same way. The important thing is, that you use bluez with the wiimote plugin. This plugin automatically selects the right PIN for the wiimote regardless of the agent you use.
The most recent bluez version in archlinux includes the wiimote plugin so you do not need to compile it on your own.
Sounds possible, I tried to set up mine with bluez-simple-agent, and it wouldn't even run. Just to check, you do have "hid-wiimote" in your modules, in your rc.conf right? That's the only other thing I can think of that would cause it not to pair
hid-wiimote in kernel modules is not needed to pair the wiimote. If hid-wiimote is not loaded, the wiimote will be detected as generic bluetooth HID device. It will be paired/connected but will not be usable as there is no protocol driver available.
The hid-wiimote kernel module provides this protocol parser and hence provides the input event-files for wiimotes.
EDIT: bluez was updated on the 20th with wiimote support, so using the PKGBUILD is unnecessary, just pacman -Syu. The gnome bluetooth wizard does find and pair with my wiimote with the new bluez. Now if someone could just tell me how to change the default button mappings.
The driver is still under development. There won't be any way to change the default mappings (this wouldn't make sense). Instead, the X-server is supposed to ignore wiimotes and you should use separate applications which provide different mouse- or keyboard-emulations to the x-server.
I am working on these apps but it will take some time.
Regards
David
Offline
greatant wrote:My guess is the problem must be with bluez-simple-agent. It mustn't know how to handle the auto-pin.
Thanks for your feedback.
No. You can use whatever agent you want. Either the bluez-simple-agent, the gnome-bluetooth applet or blueman. They all work the same way. The important thing is, that you use bluez with the wiimote plugin. This plugin automatically selects the right PIN for the wiimote regardless of the agent you use.
The most recent bluez version in archlinux includes the wiimote plugin so you do not need to compile it on your own.asjimene wrote:Sounds possible, I tried to set up mine with bluez-simple-agent, and it wouldn't even run. Just to check, you do have "hid-wiimote" in your modules, in your rc.conf right? That's the only other thing I can think of that would cause it not to pair
hid-wiimote in kernel modules is not needed to pair the wiimote. If hid-wiimote is not loaded, the wiimote will be detected as generic bluetooth HID device. It will be paired/connected but will not be usable as there is no protocol driver available.
The hid-wiimote kernel module provides this protocol parser and hence provides the input event-files for wiimotes.asjimene wrote:EDIT: bluez was updated on the 20th with wiimote support, so using the PKGBUILD is unnecessary, just pacman -Syu. The gnome bluetooth wizard does find and pair with my wiimote with the new bluez. Now if someone could just tell me how to change the default button mappings.
The driver is still under development. There won't be any way to change the default mappings (this wouldn't make sense). Instead, the X-server is supposed to ignore wiimotes and you should use separate applications which provide different mouse- or keyboard-emulations to the x-server.
I am working on these apps but it will take some time.Regards
David
Awesome! thanks for all the info.
Dell XPS M1330 : Core 2 Duo, 4GB RAM, 32-bit, GNOME 3
Offline
I also updated the wiki page:
http://wiki.archlinux.org/index.php/XWiimote
Please always try with the "red-sync button" behind the battery-cover instead of using the 1+2 buttons. Otherwise auto-reconnect may not work reliably.
Offline
I still can't get it to work.
My bluetoothd has the wiimote plugin built-in, but I'm still asked for a PIN when I try to connect with simple-agent
simple-agent hci0 $WIIMOTE
RequestPinCode (/org/bluez/24893/hci0/dev_00_1F_C5_1B_3A_B1)
Enter PIN Code:
Creating device failed: org.bluez.Error.AuthenticationRejected: Authentication Rejected
Even if I succeed in pairing, how can I access the data? Is there a /dev associated with the wiimote? /dev/hid0 or /dev/wiimote?
Thanks.
Offline
I still can't get it to work.
My bluetoothd has the wiimote plugin built-in, but I'm still asked for a PIN when I try to connect with simple-agent
simple-agent hci0 $WIIMOTE
RequestPinCode (/org/bluez/24893/hci0/dev_00_1F_C5_1B_3A_B1)
Enter PIN Code:
Creating device failed: org.bluez.Error.AuthenticationRejected: Authentication Rejected
Do you have an original Wii Remote from Nintendo or some 3rd Party Wii Remote by some other vendor?
Please also see https://github.com/dvdhrm/xwiimote/issues/3 for some more detailed information.
Even if I succeed in pairing, how can I access the data? Is there a /dev associated with the wiimote? /dev/hid0 or /dev/wiimote?
Thanks.
Yes, there are several devices in /dev/input/ associated with the Wii Remote. If you are a developer, you may want to have a look at http://github.com/dvdhrm/xwiimote
If you just want to use the Wii Remote, then you have to wait as the User-Space tools are still under development. Or you simply use cwiid in the meantime.
Regards
David
Offline
Thanks for the pointers, I'll have a look into them. I'd like to develop a small shell script that waits polling regularly until I press 1+2 on the mote, and then automatically connects so that I can use it as a remote in mplayer (or other sotfware).
By the way my wiimote is an official Nintendo one.
See you.
Offline
Pages: 1