* [Bluez-users] yet another Barton Keyboard problem
@ 2004-06-28 16:43 Soenke von Stamm
2004-06-28 17:01 ` Marcel Holtmann
0 siblings, 1 reply; 2+ messages in thread
From: Soenke von Stamm @ 2004-06-28 16:43 UTC (permalink / raw)
To: bluez-users
Hi!
I'm new to the list but I've read about another guy's problem with this k=
b in=20
the archive. My problem might be a little different as I assume my shiny=20
lilly Barton is jast broken.
I have purchased it just a few days back, plugged it into the next comput=
er=20
(the originally supplied dongle that is) and wondered a bit why I couldn'=
t=20
access the BIOS. I had jus read in c't that this should work... (and it w=
orks=20
with my Logitech Cordless Desktop via USB)
Further on under Linux (debian sid, 2.6.[67]-mh1/custom) after some troub=
le I=20
was able to attach the mouse which then also ran in hidproxy mode, but th=
e kb=20
still refuses every connection attempt. On one machine I was able to see =
it=20
via=20
~$ hcitool inq
Inquiring ...
00:04:61:81:75:B2 clock offset: 0x0597 class: 0x002580
00:04:61:81:74:2B clock offset: 0x5658 class: 0x002540
(kb is the second one)
but my home machine doesn't even give me that:
~$ hcitool inq
Inquiring ...
~$
Funny anough, the kde environment (kbluetoothd and bluetooth:/) returns=20
adresses and names. The mouse works fine now.
Connection attempts mostly look like this:
bibo:~# hcitool cc --role=3Dm 00:04:61:81:74:2B
Can't create connection: Connection timed out
bibo:~# hcitool cc --role=3Ds 00:04:61:81:74:2B
Can't create connection: Connection timed out
but sometimes I also get that error 53...
As I've read the other thread I've tried each and every option described =
there=20
but nothing helps.
Now I'm wondering if I should just return the whole package because of th=
e=20
non-operational hidproxy mode. Or I could bite the bullet and try with a=20
win98se install only for testing my hardware :-(
any advice?
tia,
S=F6nke
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Bluez-users] yet another Barton Keyboard problem
2004-06-28 16:43 [Bluez-users] yet another Barton Keyboard problem Soenke von Stamm
@ 2004-06-28 17:01 ` Marcel Holtmann
0 siblings, 0 replies; 2+ messages in thread
From: Marcel Holtmann @ 2004-06-28 17:01 UTC (permalink / raw)
To: Soenke von Stamm; +Cc: BlueZ Mailing List
Hi Soenke,
> I'm new to the list but I've read about another guy's problem with this kb in
> the archive. My problem might be a little different as I assume my shiny
> lilly Barton is jast broken.
>
> I have purchased it just a few days back, plugged it into the next computer
> (the originally supplied dongle that is) and wondered a bit why I couldn't
> access the BIOS. I had jus read in c't that this should work... (and it works
> with my Logitech Cordless Desktop via USB)
>
> Further on under Linux (debian sid, 2.6.[67]-mh1/custom) after some trouble I
> was able to attach the mouse which then also ran in hidproxy mode, but the kb
> still refuses every connection attempt. On one machine I was able to see it
> via
<snip>
> As I've read the other thread I've tried each and every option described there
> but nothing helps.
>
> Now I'm wondering if I should just return the whole package because of the
> non-operational hidproxy mode. Or I could bite the bullet and try with a
> win98se install only for testing my hardware :-(
this is easy to answer, but it seems that actually nobodoy knows it. The
original HID proxy software needs the link key of the keyboard. At the
moment the Linux HID code don't asks for a PIN code when connectiong a
keyboard the first time. I worked on it, but I ran into troubles with
some non CSR chips. Once you connected your keyboard you only have to
request an authentication with "hcitool auth ..." and everything should
work afterwards.
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-06-28 17:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-06-28 16:43 [Bluez-users] yet another Barton Keyboard problem Soenke von Stamm
2004-06-28 17:01 ` Marcel Holtmann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox