nintendo wiimote not working

In another machine I have with ubuntu 7.10, it works well(same usb bluetooth dongle), lswm and wmgui works.

Wiiuse gives this problem:

./wiiuse-example
wiiuse v0.12 loaded.
  By: Michael Laforest <thepara[at]gmail{dot}com>
  http://wiiuse.net http://wiiuse.sf.net
[INFO] Found 2 bluetooth device(s).
[INFO] Found wiimote (00:19:1D:B7:D9:ED) [id 1].
connect() output sock: Connection timed out
Failed to connect to any wiimote.

Installing libbluetooth from hardy debs:
https://launchpad.net/ubuntu/hardy/i386/libbluetooth2/3.24-1

makes lswm and wmgui to start. Like wiiuse, it just doesn't connect.

Does anybody has ANYTHING to add about the possible justification of this problem?

A lot of people is having problems too with 8.10:
http://www.ubuntu-forum.org/showthread.php?p=6164424

This bug report is completely muted.

I had previous versions of lswm, wmgui... in /usr/ocal/... that explains the problem:
lswm: error while loading shared libraries: libbluetooth.so.2: cannot open shared object file: No such file or directory

I removed every /usr/local program, now the only problem is connecting the wiimote(detection works fine):

Pairing wih Nintendo RVL-CNT-01 failed

More details on bug 284982

Bump. Same problem here, I also wanted to try and connect the Wii remote; have been experiencing the same issue with other bluetooth devices such as mobile phones.

mattycoze@mattycoze-laptop:~$ lspci
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 0c)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 6 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation GeForce 8400M GS (rev a1)
02:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 01)
07:09.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
07:09.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
07:09.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 12)
07:09.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)
07:09.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff)

I have the same problem. In Hardy I could connect just fine.

Using this USB dongle (worked fine in Hardy)
Bus 001 Device 004: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter

I get the same "pairing failed" message through the bluez utils and hidd times out. hcitool and lswm find the hardware address but I can't connect whatsoever. WMgui says "unable to connect". Is there anyone working on this? I don't understand why it worked perfectly in Hardy and now nothing goes. Did something in the bluetooth stack change?

I just played around with it a little more and I found that when I first start wminput or wmgui and start the polling and THEN simultaneously in the terminal run "sudo hcitool cc <mac of wiimote>" I get a connection as usual. I don't have a single clue what's happening but I believe something in the wmgui/wminput code isn't authorizing with the Wiimote correctly so you have to force hcitool to do it for you.

At least this way I can get my Wiimote to connect via bluetooth on a 2.6.27-11-generic Kernel with the btusb module.

I found a workaround that does the trick for me. You start wminput or wmgui polling for the wiimote and while it's scanning run "sudo hcitool cc <MAC of Wiimote>" in a terminal it finds the Wiimote correctly, pairs and uses it. That's at least how I get it to run at the moment. I don't know exactly what's wrong but I believe something with the auth/connection in wminput/wmgui must be wrong or at least something with the way they use the backend/stack.

MARKUS, you are a genius!!

Your hcitool cc MAC trick works for me!!!

If only someone that knows could understand what is happening and fix it.

I had been mad about this bug a lot of time. You wring it a window, light over this bug. This is very important, before your trick, it could be anything, now I think it will be easily handled.

I will report this to other interested people in other bugs.

Sorry for asking dumb questions - but how do I find out my Wiimote's MAC?

...I installed lswm from terminal, it gave me "00:21:BD:10:AA:A5" - So then I started wmgui, pasted "sudo hcitool cc 00:21:BD:10:AA:A5" (without quotes) to the terminal, pressed 1+2 on my Wiimote, wmgui started connecting to Wiimote, I ran the above mentioned code from the terminal (by just pressing enter), and... wmgui said it couldn't connect to Wiimote (which it had done before without the terminal code)... - I really want to get this working: http://www.uweschmidt.org/wiimote-whiteboard - help appreciated...

@Matthias: I feel your pain. But I can not understand exactly what you have done. You told things worked, then not. Could you explain it more detailed? Imagine that I'm in the other side of the world and can't look at your computer as you do(e.g the "above code" is ambiguous, it could be another person posted code, your own...) :-)

The moment you press enter when "sudo hcitool cc 00:21:BD:10:AA:A5" is in the terminal is important.

In my own experience, I have to press 1+2 after pressing "connect" on wmgui, and at the same time press enter in the terminal( I have different terminals in different windows). Given that I need to do this to tree wiimotes at once is a little nasty. For this to work I need to open wmgui with the MAC as a terminal argument.

I can make any wii program with the Markus trick. Once it connects, it will last. You will make the whiteboard to work, although not as elegant as it should until someone solves the bluez bug.

upss, sorry for the errors:

I omited "work" in "I can make any wii program" work...
and the "when" in "you press enter when" needs to be removed

I have to improve the voice recognition software :-)

Never mind, I got it working (whiteboard_0.3.4.2-0ubuntu1_i386.deb did the job for me without following the above instructions) - thanks for your help, Jose - and please let me know how you got speech recognition to work on Ubuntu...-)!

I cannot duplicate this in Intrepid on my machine. From reading the reports there seems to be some confusion -- Intrepid featured a major version bump to Bluez, so /usr/local/ binaries reasonably would have been affected.

Can the original reporter amend the bug description to reflect the current problem? It looks like a hardware problem rather than anything specific to cwiid, but if I misunderstand, updating the description is a perfect action to take in fixing this.

Marked Incomplete until description is resolved

@Justin: It's not a hardware problem. I have three different wiimotes, no one works out of the box. They work in another machine with the last ubuntu version before intrepid. Exactly the same hardware. The same computer, the same bluez dongle, with Intrepid stoping to work when updated. I go to another machine, and they work fine.

And I'm not the only person that has this problem, a lot of people have it too, like Markus, you can look at other bluez bug reports they have exactly the same problem. Indeed, using the Markus trick makes the wiimote to connect and work fine. The trick is to do "sudo hcitool cc 00:19:1D:B7:D7:10" exactly at the same time it tries to connect.

When I say wmgui I say every program that connects with the wiimote. I use the tree wiimotes at the same time without problems with the trick.

https://bugs.launchpad.net/ubuntu/+source/bluez-utils/+bug/284982

In fact I have a new acer aspire one that I installed from scratch, and... it doesn't work ... unless I use the hcitool trick again.

Let's see:
Three machines:
One with ubuntu intrepid and ubuntu Hardy heron(works out of the box), in intrepid it doesn't work(multiple boot machine).Same USB dongle.
Acer aspire 5610, it worked in Hardy,updated,in intrepid it doesn't work
Acer aspire one with intrepid doesn't work.

They all work well with the trick. I have tested two different USB dongles, they don't work without the trick, work with it.

"you can look at other bluez bug reports they have exactly the same problem."

Precisely. I'm trying to determine whether this report applies to cwiid or bluez. There's some work going on right now to fix some Intrepid bluetooth regressions on a number of modules. Can you grab a Jaunty beta CD and test this with your systems?

@Justing. Please ask for any information I could give you. I don't know what "description" you need.

Is
"Wiimote fails to connect in intrepid, unless you do hcitool cc MAC at the same time you try to connect"
a valid description or you need logs and other data?

@justin Can you grab a Jaunty beta CD and test this with your systems?

OK

Well, for example, does lswm still produce an error asking for libbluetooth.2.so?

Also, can you provide the results of lsusb , in particular, the lines for your bluetooth devices?

Ideally, steps to reproduce the error are what I'm after.

@Justin:does lswm still produce an error asking for libbluetooth.2.so?

No, I had the problems I told you with bluethooth, so I tried to fix it downloading and compiling some packages,once installing-removing bluez packages didn't work, that located in /usr/local/ but I forgot to remove then. When I removed them, I got the initial error: Only problems connecting.

The asking for libbluetooth.2.so only happened in the computer I tried to fix it, Acer aspire 5610, when updating from Hardy, and being frustrated because it worked before(it was the first machine to upgrade), I tried every solution people posted in the forums without success.

lsusb
Bus 003 Device 006: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 056a:0013 Wacom Co., Ltd Graphire 3 4x5
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 0603:00f2 Novatek Microelectronics Corp.
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 1395:3554 Sennheiser Communications
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Steps to reproduce the error:

Detect mac address:
lswm
Put Wiimotes in discoverable mode now (press 1+2)...
00:19:1D:B7:D7:10

Try to connect to wiimote: For example using wmgui

wmgui 00:19:1D:B7:D7:10
(wmgui doesn't connect to wiimote), "No conection" message is displayed.

If you do File->connect

Put Wiimote in discoverable mode...

Press OK , pressing 1+2on wiimote

You Wait,wait, 20 seconds or so... Message is displayed "Unable to connect"

In the terminal a message has appeared "Socket connect error (control channel)"

If you do "hcitool cc MAC" when pressing OK, in a different terminal window, it connects.

If instead of wmgui 00:19:1D:B7:D7:10, I put wmgui without the MAC, it works too with the hcitool trick when pressing OK.

At this point, I think its related to the specific hardware you have. There's an Intrepid Stable Release Update out for this specific device as of like today.

For more info, see https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/268502?comments=all (150+ comments!)

You suggested other bluetooth "dongles" also did this. If you can, share the lsusb lines for them in case they're not currently known to be broken.

I tried Jaunty beta CD, same problem and solution, hcitool works.

Looks like the driver fix may not be in the archives yet, but the kernel team is definitely moving on this. I'm reluctant to recommend this, but sfbader publishes the proposed fix in the above thread near the end. Installing the package may cause catastrophic failure, so it might be wisest to wait for a kernel to be published in intrepid-proposed or even intrepid-updates.

lsusb with the other dongle:

Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 004: ID 1395:3554 Sennheiser Communications
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 0603:00f2 Novatek Microelectronics Corp.
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 056a:0013 Wacom Co., Ltd Graphire 3 4x5
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

So it's seems it has the same base circuit although externally seems a very different dongle. How much time could it take to be solved?

Could you give me information of valid IC dongles and sellers trademark? so I could buy someone that works. I don't want to risk stability on my working machine.

Is this bug still reproducible on Karmic?

It works fine in Ubuntu 9.10. FINALLY!!