public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Sunnan <sunnan@handgranat.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] apple wireless mouse on apple ibook (g4, builtin usb)
Date: Sat, 14 Feb 2004 12:06:52 +0100	[thread overview]
Message-ID: <402E014C.807@handgranat.org> (raw)
In-Reply-To: <1076720052.18588.147.camel@pegasus>

[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]

Marcel Holtmann wrote:
> is the script executable? Do you restarted hcid?

slowstorm/home/sunnan% pin-helper.sh
PIN:0000
slowstorm/home/sunnan% ps aux|grep hcid
root      1668  0.0  0.2  1708  628 ?        S    Feb13   0:00 hcid: 
processing events
root      3763  0.0  0.1  1724  456 pts/3    S    11:51   0:00 hcidump 
-w thirddata
sunnan    3957  0.0  0.2  1656  528 pts/5    R    11:57   0:00 grep hcid
slowstorm/home/sunnan%

And yeah, I've restarted it, both from the /etc/init.d/ scripts and also 
rebooted.

> We really need a full binary hcidump to see what is going on.

I've sent several to the list but I'm unsure of how large they are 
supposed to get before I C-c. I'm attaching one larger now (still only 4 
k... they just don't get very large.). (Are my attachment's getting 
through? Maybe they are stripped somewhere.)

There's been some progress since the last mail. I've run "hcitool scan" 
a couple of times, and _one_ of the times it showed:
slowstorm/home/sunnan% hcitool scan
Scanning ...
         00:0A:95:01:5F:57       sunnan???s mouse

Argh! Why did I give it a name with an apostrophe! Oh, Mac OS, thou 
tempted me to many strange filenames, some even including spaces!
(Note the hexadecimal device number is different from my local device, 
which is 00:0D:93:04:19:15.)

All the other times it just exited after writing "Scanning ...". I've 
been unable to find it again.

As usual, bthid is just quitting after a while without saying so in 
/var/log/daemon.log.

[-- Attachment #2: thirddata --]
[-- Type: application/octet-stream, Size: 2447 bytes --]

  reply	other threads:[~2004-02-14 11:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 17:22 [Bluez-users] apple wireless mouse on apple ibook (g4, builtin usb) Sunnan
2004-02-13 17:51 ` Marcel Holtmann
2004-02-13 18:59   ` Sunnan
2004-02-13 19:56     ` Marcel Holtmann
2004-02-13 20:48       ` Sunnan
2004-02-13 21:50         ` Marcel Holtmann
2004-02-13 22:02           ` Sunnan
2004-02-13 22:29             ` Marcel Holtmann
2004-02-13 22:54               ` Sunnan
2004-02-13 23:21                 ` Marcel Holtmann
     [not found]                   ` <402D5EB0.3090601@handgranat.org>
2004-02-14  0:54                     ` Marcel Holtmann
2004-02-14 11:06                       ` Sunnan [this message]
2004-02-15 23:43                         ` Sunnan
2004-02-15 23:59                           ` Marcel Holtmann
2004-02-13 22:59               ` one more thing (was Re: [Bluez-users] apple wireless mouse on apple ibook (g4, builtin usb)) Sunnan
2004-02-13 23:22                 ` Marcel Holtmann
2004-02-13 22:13           ` [Bluez-users] apple wireless mouse on apple ibook (g4, builtin usb) Ramon A Reveron
2004-02-13 22:15             ` 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=402E014C.807@handgranat.org \
    --to=sunnan@handgranat.org \
    --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