public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Bearcat M. Sandor" <Linux@feline-soul.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Page timeout on Logetech cordless elite keyboard but mouse works
Date: Wed, 26 Jul 2006 01:40:09 -0600	[thread overview]
Message-ID: <200607260140.10216.Linux@feline-soul.com> (raw)
In-Reply-To: <1153898346.746.4.camel@localhost>

Marcel,

hidd --server is indeed running. 

At my start up i do:
modprobe hidp
/usr/bin/hidd --server
hid2hci -0
/usr/bin/hidd --connect 00:07:61:1d:29:32

That connects the mouse just fine. However the keyboard never wakes up.  Even 
removing and replacing a battery does nothing. A "/usr/bin/hidd --connect 
00:07:61:1B:50:9B" just gives me the time out error. (forget the MAC i 
entered below, i cut/paste the wrong one). Nothing appears in my syslogs when 
i do a hdd --connect.

Thanks for the help so far,

Bearcat

On Wednesday 26 July 2006 01:19 in an email titled "Re: [Bluez-users] Page 
timeout on Logetech cordless elite keyboard but mouse works" Marcel Holtmann 
wrote:
>Hi Bearcat,
>
>> I am running sourcemage gnu/linux. My kernel is 2.6.17 and blues-libs and
>> bluez-utils are versions 3.1. I have a Logitech cordless elite set
>> (keyboard and MX 900 mouse).
>>
>> The basis for my work on it so far is here:
>> http://www.bueche.ch/comp/mx900/mx900.html
>>
>> The logitech hub switches over to hci just fine and the mouse is
>> successfully connected via blue tooth. (Note, both mouse and kb work in
>> pure hid mode with no bluetooth). I need the bluetooth hub working as i
>> will be getting a headset this week, that i need to have operational
>>
>> However, i can not get the keyboard to connect. When i enter a "hidd
>> --connect 00:07:61:1d:29:32" i get "Can't get device information: Host is
>> down" from the terminal  and "Problem connecting with 00:07:61:1d:29:32:
>> Page Timeout" on a kdebluetooth tool tip.
>>
>> I have hit the connect button on the keyboard repeatedly and even taken
>> out a battery for a few seconds. I have verified that i am using the
>> correct MAC address via the printing on the bottom of the keyboard.
>>
>> I'll be happy to provide what ever config info you all need to help me
>> resolve this.
>
>make sure that "hidd --server" is running, because the keyboard will
>re-connect to you.
>
>Regards
>
>Marcel

-- 
Bearcat M. Sandor
Bearcat@feline-soul.com
ICQ: 6628727
MSN: bearcatsandor@hotmail.com
Yahoo: bearcatsandor
AIM: bearcatmsandor
Jabber: bearcatsandor@jabber.org

  reply	other threads:[~2006-07-26  7:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-26  6:27 [Bluez-users] Page timeout on Logetech cordless elite keyboard but mouse works Bearcat M. Sandor
2006-07-26  7:19 ` Marcel Holtmann
2006-07-26  7:40   ` Bearcat M. Sandor [this message]
2006-07-26  7:46     ` Marcel Holtmann
2006-07-26  8:11       ` Bearcat M. Sandor
  -- strict thread matches above, loose matches on Subject: below --
2006-07-25 18:40 Bearcat M. Sandor
2006-07-28 14:18 ` 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=200607260140.10216.Linux@feline-soul.com \
    --to=linux@feline-soul.com \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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