From: Florian Ehrenthal <dizzinger@gmx.net>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Problems with Logitech Cordless Desktop NX for Bluetooth
Date: Mon, 1 Nov 2004 15:47:54 +0100 [thread overview]
Message-ID: <200411011547.55236.dizzinger@gmx.net> (raw)
Hi everyone,
i am using kernel 2.6.9 & bluez-utils/libs 2.10.
i do have some difficulties with my bluetooth keyboard. one really annoying
thing is, that i cannot control my bootloader (nor my bios) with my bluetooth
keyboard. the thing is, if i pair my keyboard using windows i am able to use
the kb during boot procedure. so there is probably something wrong with my
init-scripts? can anyone please point out what the issue might be?
second thing i noticed, those multimedia keys that are literally everywhere on
that keyboard don't seem to function, at least the majority doesn't (like 5
out of 32 work, the others don't seem to generate keycodes).
in a recent posting to that list i read something that this might be related
to boot-mode or something (if i got that right), but i am unsure if that
relates to my setup. hidd -show tells me that keyboard and mouse are in
boot-mode. what info do i need to provide to receive some help?
btw, why doesn't the keyboards win-key work, when the numpad is active, is
that related?
and there is one more thing that annoys me: there are certain words where
parts of the word get repeated. hmm, it's hard to explain that - it might
even be related to my bad typing style (which is not really 10-finger-typing,
it's more like 6-finger typing ;)
let me give you an example: if i type the word "hier" i usually get "hieier"
as output. i can reproduce the problem if i hit (and hold) the keys h, i and
e at the same time. now if i press the r key to complete the word, and
release the other buttons as well, i get "hieier" as a result.
if i remember correctly, this doesn't happen using windows, so i guess it must
be related to bluez somehow. i'd love to provide further info, to get that
solved. (well, maybe i will have to simply improve my typing style ;)
And theres another thing i wanted to express for quite some time now: Marcel,
thanks a lot for all the hard work you're putting into this. sometimes i have
the impression that you never actually sleep, as you replay to mailings on
that list usually only 5 minutes after they arrived - no difference if that
message arrived like 3 o'clock in the morning or 15:00 o'clock.
additionally i had the chance to attend one of your presentations this years
linux tag. that was one of the best i heard!
long story short: thanks!
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2004-11-01 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-01 14:47 Florian Ehrenthal [this message]
2004-11-01 15:39 ` [Bluez-users] Problems with Logitech Cordless Desktop NX for Bluetooth 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=200411011547.55236.dizzinger@gmx.net \
--to=dizzinger@gmx.net \
--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