public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Patrick W. Healy" <phealy@phealy.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Re: diNovo/MX900 problem with hidd
Date: Sat, 09 Jul 2005 15:25:01 -0500	[thread overview]
Message-ID: <42D0329D.7090500@phealy.com> (raw)
In-Reply-To: <42CFD081.90800@phealy.com>

Hmm. Noticed this on boot:
hci_usb: Unknown symbol hci_free_dev
hci_usb: Unknown symbol hci_alloc_dev
hci_usb: Unknown symbol hci_unregister_dev
hci_usb: Unknown symbol hci_register_dev
hci_usb: Unknown symbol hci_free_dev
hci_usb: Unknown symbol hci_alloc_dev
hci_usb: Unknown symbol hci_unregister_dev
hci_usb: Unknown symbol hci_register_dev

Interesting, anyone?

Patrick W. Healy wrote:

> You know, one thing I just realized I forgot to mention...
>
> When I do get it to pair (which I apparently can't right now), hidd 
> --show lists it as a "boot mode device" even though 
> /var/log/daemon.log shows it as a Logitech MX900.
>
> I have tried it with auth/encrypt on, although I don't think they're 
> on as of the hciconfig -a I just sent.
>
> -- 
> Patrick Healy
>
> Dick wrote:
>
>> Patrick W. Healy <phealy <at> phealy.com> writes:    
>>
>>> Greetings, everyone. I'm having some issues with getting my 
>>> bluetooth    keyboard and mouse to work, and they're getting rather 
>>> frustrating.    Perhaps someone can help me.     I have a Logitech 
>>> diNovo media desktop and the matching MX900 mouse,    which I am 
>>> attempting to pair with the internal bluetooth on my Dell    
>>> Inspiron 8500. I can get them to pair successfully, and even move 
>>> and    type, but the mouse movement is extremely jerky and useless, 
>>> while the    keyboard types erratically and quite often repeats 
>>> keystrokes.     I'm using a 2.6.12 kernel and the latest bluez in 
>>> debian unstable (hcid    2.15) along with all the bluetooth modules 
>>> compiled and ready.     I also usually receive a message saying 
>>> "Can't create HID control    channel: Invalid exchange", along with 
>>> input output errors and errors    about the file descriptor being in 
>>> a bad state. Sometimes the pin auth    system comes up, sometimes it 
>>> doesn't.     Any help? I'd be happy to provide any additional 
>>> information needed.     
>>
>>   I've got a Logitech dinovo and it works like a charm on my Dell 
>> Latitude D800,   I've had some bad experience with an external 
>> sitecom dongle (laggy mouse)     You should enable auth and encrypt 
>> in hcid.conf, or enable it manually with   hciconfig hci0 auth 
>> encrypt     If your keyboard / mouse are already associated you 
>> should move the mouse   around for a while to reconnect and keep 
>> pressing enter on the keyboard until   it connects. If that failes 
>> you should press the connect buttons and start   scanning with hidd 
>> --search. I'm using kbluepin as pin helper, so I must have a  running 
>> X server for the association. Your error messages might be related 
>> to  that (a failing pin helper).   
>> I'm really happy with my dinovo and bluez, it's way better than the  
>> apple/widcomm/microsoft bluetooth stacks and I hope this helps.
>> greetings, Dick
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by the 'Do More With Dual!' webinar 
>> happening
>> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
>> core and dual graphics technology at this free one hour event hosted 
>> by HP, AMD, and NVIDIA.  To register visit 
>> http://www.hp.com/go/dualwebinar
>> _______________________________________________
>> Bluez-users mailing list
>> Bluez-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bluez-users
>>  
>>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the 'Do More With Dual!' webinar 
> happening
> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
> core and dual graphics technology at this free one hour event hosted 
> by HP, AMD, and NVIDIA.  To register visit 
> http://www.hp.com/go/dualwebinar
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users




-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP, 
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-07-09 20:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-08 23:38 [Bluez-users] diNovo/MX900 problem with hidd Patrick W. Healy
2005-07-09  7:49 ` Marcel Holtmann
2005-07-09  9:48 ` [Bluez-users] " Dick
2005-07-09 13:26   ` Patrick W. Healy
2005-07-09 20:25     ` Patrick W. Healy [this message]
2005-07-09 20:30       ` Marcel Holtmann
2005-07-09 22:22         ` Patrick W. Healy
2005-07-10  8:00           ` Marcel Holtmann
2005-07-10 14:07             ` Patrick W. Healy
2005-07-11 17:21               ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42D0329D.7090500@phealy.com \
    --to=phealy@phealy.com \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox