It works fine in Ubuntu 9.10. FINALLY!!
** Changed in: cwiid (Ubuntu)
Status: Incomplete => Fix Released
--
nintendo wiimote not working
https://bugs.launchpad.net/bugs/291051
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
Is this bug still reproducible on Karmic?
** Changed in: cwiid (Ubuntu)
Status: Fix Committed => Incomplete
--
nintendo wiimote not working
https://bugs.launchpad.net/bugs/291051
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: bluez-utils
Status: New => Fix Committed
** Changed in: cwiid (Ubuntu)
Status: Incomplete => Fix Committed
--
nintendo wiimote not working
https://bugs.launchpad.net/bugs/291051
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
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
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
I tried Jaunty beta CD, same problem and solution, hcitool works.
--
nintendo wiimote not working
https://bugs.launchpad.net/bugs/291051
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
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 blue
** Description changed:
- There was a time, two or three ubuntu releases back, in which I could connect
to the wiimote on ubuntu.
- The last update makes this to lswm:
+ In hardy, cwiid worked; I could connect to the wiimote on ubuntu. In
+ Intrepid, this fails.
- $$ lswm
- lswm: error while l
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.
--
nintendo wiimote not working
https://bugs.launchpad.net/bugs/291051
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
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->conne
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 De
@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
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.
--
nintendo wiimote not working
https://bugs.launchpad.ne
@justin Can you grab a Jaunty beta CD and test this with your systems?
OK
--
nintendo wiimote not working
https://bugs.launchpad.net/bugs/291051
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
@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?
--
nintendo wiimote not working
h
"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 a
@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 an
Marked Incomplete until description is resolved
** Changed in: cwiid (Ubuntu)
Status: New => Incomplete
--
nintendo wiimote not working
https://bugs.launchpad.net/bugs/291051
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
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
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...-)!
--
nintendo wiimote not working
https://bugs.launchpad.net/b
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 :-)
--
nintendo wiimote not working
https://bugs.launchpad.net/bugs/291051
You received this bug not
@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 pe
...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 pressin
Sorry for asking dumb questions - but how do I find out my Wiimote's
MAC?
--
nintendo wiimote not working
https://bugs.launchpad.net/bugs/291051
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
** Changed in: cwiid (Ubuntu)
Sourcepackagename: None => cwiid
--
nintendo wiimote not working
https://bugs.launchpad.net/bugs/291051
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
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,
I will report this to other interested people in other bugs.
--
nintendo wiimote not working
https://bugs.launchpad.net/bugs/291051
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
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 " 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 bu
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 " I get a connection
as usual. I don't have a single clue what's happening but I believe
something in the wmgui/wminput
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 l
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.
mattyc...@mattycoze-laptop:~$ lspci
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory
Controller Hub (rev 0c)
0
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(detec
** Also affects: bluez-utils
Importance: Undecided
Status: New
--
nintendo wiimote not working
https://bugs.launchpad.net/bugs/291051
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
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.
--
nintendo wiimote not working
https://bugs.launchpad.net/bugs/291051
Y
Wiiuse gives this problem:
./wiiuse-example
wiiuse v0.12 loaded.
By: Michael Laforest
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.
In
In another machine I have with ubuntu 7.10, it works well(same usb
bluetooth dongle), lswm and wmgui works.
--
nintendo wiimote not working
https://bugs.launchpad.net/bugs/291051
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
36 matches
Mail list logo
