linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rutger Hendriks <Loial@home.nl>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Correction
Date: Sat, 3 Dec 2005 13:21:14 +0100	[thread overview]
Message-ID: <200512031321.23435.Loial@home.nl> (raw)
In-Reply-To: <200511301046.25700.mgorbach@yahoo.com>

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

On Wednesday 30 November 2005 16:46, Michael Gorbach wrote:
> Sorry about a typo ... When i wrote "mouse" i meant keyboard. My dinovo
> keybord is stuck in f-lock mode after I run hid2hci. Actually ... the
> f-keys seem to be working in console mode (outside of x). Inside x, it xev
> shows a kepress of the event "f12" but nothing seems to happen. Weird isnt
> it? Is it a problem with x keybindings?
By stuck, do you mean the F-lock light on the receiver does not respond? 
because it doesn't respond here either, it burns continuously, but I can 
still switch between F1-F12 and F-lock mode by pressing the F-lock key. 
Unfortunately only Undo (F5) and My Comp (F9) work when in F-lock mode, but 
that is another problem.

xev should recognise the F1-F12 keypresses and applications should respond.

> Also ... is there no way to put the 
> device out of hci mode when the system shuts off so that I can have access
> to GRUB and my BIOS? The windows drivers seem to be OK doing this ...

I'm experiencing no problems in GRUB or the BIOS when I reboot my machine. It 
just takes a second for the first keypress to get processed it seems, after 
that no delays or problems.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2005-12-03 12:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-30 15:46 [Bluez-users] Correction Michael Gorbach
2005-11-30 17:26 ` Marcel Holtmann
2005-12-03 12:21 ` Rutger Hendriks [this message]

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=200512031321.23435.Loial@home.nl \
    --to=loial@home.nl \
    --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;
as well as URLs for NNTP newsgroup(s).