From: Patrick <patbert@patbert.com>
To: Bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Using windows breaks bluetooth in linux? huh
Date: Wed, 17 Nov 2004 00:52:47 -0500 [thread overview]
Message-ID: <419AE72F.3030307@patbert.com> (raw)
I have an Apple BT keyboard and a D-Link usb BT adaptor.
I have had it up and running in linux now for quite some time without
any trouble. I reboot, turn the pc off, whatever, the bluetooth always
works.
But today I booted my pc into windows (half life 2 lol) and thanks to
service pack 2 I can now use my BT adaptor in windows so I fiddled
around and got the apple keyboard connected.
So now I reboot back into linux and I cannot for the life of me get
bluetooth working again! I have had the pc/keyboard off for an extended
period of time, unplugged and plugged the adaptor back in, nothing will
get this keyboard connected again!
Kawaii64 patrick # hidd --search
Searching ...
Connecting to device 00:0A:95:3A:63:E4
Can't create HID control channel: Permission denied
And while this is happening hcidump says:
Kawaii64 ~ # hcidump
HCIDump - HCI packet analyzer ver 1.9
device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
< HCI Command: Inquiry (0x01|0x0001) plen 5
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Inquiry Result (0x02) plen 15
> HCI Event: Inquiry Complete (0x01) plen 1
< HCI Command: Create Connection (0x01|0x0005) plen 13
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Link Key Request (0x17) plen 6
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
> HCI Event: Command Complete (0x0e) plen 10
> HCI Event: Connect Complete (0x03) plen 11
I used the same passkey in windows as I do in linux (0000). I honestly
cannot see how running BT while in windows would have any affect on its
functioning in linux, especially after everything has been off for a
long time in between.
The only reason I suspect there is a connection is that I had this crop
up in the past. For the longest time I stopped using the apple keyboard
because after I had it working in linux I rebooted into windows the same
day and then it never worked again in linux. I chalked it up to my
stupidty but here again it is happening.
Any idea what is going on here? Is this all unrelated? Thank you for any
insight.
Patrick
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users/listinfo/bluez-users
next reply other threads:[~2004-11-17 5:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 5:52 Patrick [this message]
2004-11-17 6:44 ` [Bluez-users] Using windows breaks bluetooth in linux? huh Marcel Holtmann
2004-11-17 15:09 ` Patrick
2004-11-17 15:21 ` Marcel Holtmann
2004-11-17 20:31 ` Patrick
2004-11-17 20:39 ` Marcel Holtmann
2004-11-18 3:05 ` Patrick
2004-11-18 7:13 ` Marcel Holtmann
2004-11-19 1:00 ` Patrick
2004-11-19 1:18 ` wim delvaux
2004-11-19 1:42 ` Marcel Holtmann
2004-11-19 1:40 ` 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=419AE72F.3030307@patbert.com \
--to=patbert@patbert.com \
--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