Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The latest Ubuntu didn't work with it either. Same exact problem. I'll download Knoppix during the middle of the night tonight and try it tomorrow. I'll post my findings then.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
If Ubuntu failed to work it I am learning towards the USB controller and USB controller module to be the issue. Does this machine have front and rear USB ports. If so try the oppisite one. Reason I mention this is the boot seems to be loading ehci-hcd modules which is 2.0 USB ports. The Bluettoth appears to be being plugged into a 1.0 to 1.1 version USB port using the ohci-hcd module.
Brian, the USB ports on the front are CLEARLY labeled as USB 2.0 ports. I've tried those and the ones in the back. I haven't tried each and every single port, but I'm pretty sure they're all USB 2.0. You can even look up the specs for yourself, HP m7248n. Here's a link: http://review.zdnet.com/desktops/hp-...06.html?tag=ut
I've been a little lazy and haven't tried Knoppix yet, but I do have it. Is it possible to force the ehci drivers to be used and not the ohci? Maybe delete the ohci dirvers?
Regards,
Brandon
Last edited by MyHeartPumpsFreon; 12-09-2007 at 08:16 PM.
F*CK ME RUNNING I GOT IT!!! I had to add 'blacklist pegasus' to the blacklist file. I issuued the 'hcitool scan' and the summab*tch worked! Now, let's just get it connected and I'm good. Problem solved.
F*CK ME RUNNING I GOT IT!!! I had to add 'blacklist pegasus' to the blacklist file. I issuued the 'hcitool scan' and the summab*tch worked! Now, let's just get it connected and I'm good. Problem solved.
Ok, another problem... there always is. I have a wiimote, which I purchased so I could do mouse emulation. (Forgive me, I thought it would be cool. I thought I'd do it in Windoze, but you can't when you don't have an authentic copy. Go figure) When I try to connect to the controller, the connection is refused. Not sure why? I tried connecting to my phone, I had to enter a pass key on both the computer and the phone. Now I am able to browse the contents of the phone. Is it possible that I can create some config file (maybe one already exists?) that says it doesn't need a passkey or it automatically gives a passkey to the controller and I have to enter the same one on the computer?
Thanks,
Brandon
edit: Glad you can appreicate my tenacity. I know I cussed a lot, but I thought it could be tolerated. It appears as though it will. This problem lingered for MONTHS. Across two computers and two bluetooth devices. I forgot about it, and I rehashed the problem recently. You can see why I had the sudden burst of joy once it worked.
Last edited by MyHeartPumpsFreon; 12-09-2007 at 08:57 PM.
I don't know if this will be of any help. Using the rfcomm connect 0 xx:xx:xx:xx:xx:xx <-mac address x <-- connection type (Should look like this: rfcomm connect 0 xx:xx:xx:xx:xx:xx x). I could connect to my mobile without requiring a password using any of the following numbers:
x=
1 = DUN (Dial Up Networking)
2 = Recieve Object
3 = Connection refused (might work with your wiimote)
4 = Serial
5 = Audio
6 = Exchange Data
7-9 The same as 3
Hope this helps you to further troubleshoot connecting to your wiimote.
The zero before the MAC address, is that the channel it's supposed to connect on? If so, I tried changing it and just not using it entirely, neither worked.
I'll try researching this further unless you have any other suggestions.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.