FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora User

 
 
LinkBack Thread Tools
 
Old 03-29-2008, 08:06 PM
Mike
 
Default Where's the bluetooth jargon demystifier?

Mike <mike.cloaked <at> gmail.com> writes:

> So there is something not right with bluetooth -
>
> Maybe someone else on this list can help out here?
>

I think that bluetooth is badly broken.

It certainly used to work - however I can reset everything and get an
association with the BT mouse but once I disconnect it won't re-associate.

I see a bz report at https://bugzilla.redhat.com/show_bug.cgi?id=439248

I don't know what broke it - maybe it is in the kernel? Maybe it is
in one of the desktop libraries. I think this probably needs a bugilla report
with some log files - and see if the bug triage team can sort it out?

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 03-29-2008, 08:11 PM
Mike
 
Default Where's the bluetooth jargon demystifier?

Mike <mike.cloaked <at> gmail.com> writes:

> I think that bluetooth is badly broken.

In /var/log/messages I see

Mar 29 20:56:31 lapmike2 hcid[1934]: Default passkey agent (:1.14,
/org/kde/kbluetooth_1234) registered
Mar 29 20:56:31 lapmike2 hcid[1934]: Default authorization agent (:1.14,
/org/kde/kbluetooth_auth_1234) registered
Mar 29 20:56:37 lapmike2 kernel: hci_acldata_packet: hci0 ACL packet for
unknown connection handle 46
Mar 29 20:57:11 lapmike2 kernel:last message repeated 192 times
Mar 29 20:57:11 lapmike2 kernel: Bluetooth: HIDP (Human Interface Emulation)
ver 1.2
Mar 29 20:57:20 lapmike2 kernel: hci_acldata_packet: hci0 ACL packet for
unknown connection handle 46
Mar 29 20:57:24 lapmike2 kernel:last message repeated 9 times
Mar 29 20:57:24 lapmike2 input[1944]: Hangup or error on HIDP control socket
Mar 29 20:57:25 lapmike2 kernel: hci_acldata_packet: hci0 ACL packet for
unknown connection handle 46
Mar 29 20:57:38 lapmike2 kernel:last message repeated 289 times
Mar 29 20:57:38 lapmike2 input[1944]: Hangup or error on HIDP control socket
Mar 29 20:57:40 lapmike2 kernel: hci_acldata_packet: hci0 ACL packet for
unknown connection handle 46
Mar 29 20:57:48 lapmike2 kernel:last message repeated 32 times
Mar 29 20:57:48 lapmike2 input[1944]: Hangup or error on HIDP control socket
Mar 29 20:57:58 lapmike2 kernel: hci_acldata_packet: hci0 ACL packet for
unknown connection handle 46
Mar 29 20:57:59 lapmike2 input[1944]: Hangup or error on HIDP control socket
Mar 29 20:58:18 lapmike2 kernel: hci_acldata_packet: hci0 ACL packet for
unknown connection handle 46
Mar 29 20:58:58 lapmike2 kernel: hci_acldata_packet: hci0 ACL packet for
unknown connection handle 46
Mar 29 20:59:02 lapmike2 input[1944]: Hangup or error on HIDP control socket
Mar 29 20:59:10 lapmike2 input[1944]: Hangup or error on HIDP control socket
Mar 29 21:00:18 lapmike2 kernel: hci_acldata_packet: hci0 ACL packet for
unknown connection handle 46
Mar 29 21:01:28 lapmike2 kernel:last message repeated 3 times

Maybe others are also seeing errors from the kernel and/or hcid concerned
with bluetooth?


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 03-29-2008, 09:02 PM
Jim
 
Default Where's the bluetooth jargon demystifier?

Mike wrote:

Mike <mike.cloaked <at> gmail.com> writes:


So there is something not right with bluetooth -


Maybe someone else on this list can help out here?




I think that bluetooth is badly broken.

It certainly used to work - however I can reset everything and get an
association with the BT mouse but once I disconnect it won't re-associate.

I see a bz report at https://bugzilla.redhat.com/show_bug.cgi?id=439248

I don't know what broke it - maybe it is in the kernel? Maybe it is
in one of the desktop libraries. I think this probably needs a bugilla report
with some log files - and see if the bug triage team can sort it out?


I do know that there was a problem with bluetooth working with cups,
something about bluez-utils, I sent a bug in , Bug 435081 and supposedly
they sent it upstream to be incorporated into the RPM to be released,
but to this point bluetooth and cups still don't work together.

You'll probably see the fix in FC 9.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 04-04-2008, 11:45 PM
Bill Davidsen
 
Default Where's the bluetooth jargon demystifier?

James Pifer wrote:

I go to the official bluez-utils web site and their documentation page
basically says "You don't want to look at our docs, they suck.".

I go to the official bluetooth web site and their documentation either
tells me why I ought to be making bluetooth devices or talks about
radio spectrum and communications layers.

Where is the web page that explains to a human what the gibberish
in the hcid.conf man page actually means?

All I'm trying to do is arrange for my bluetooth keyboard (which definitely
works with manual poking and prodding) to work automatically once
my fedora 8 system has booted. Seems like it ought to be a simple task :-).

I have given up on BT for the moment. Under Windows there's a utility
which shows the mouse, the keyboard, the printer, and all the nearby
cell phones. Under Linux there's an icon which you can click (using a
PS2 mouse) which does nada. And after downloading all the bluez stuff
without reading the documentation (there is none on using the software,
as you note), no amount of clicking, typing, or swearing made anything
happen.




I've had similar experiences. I'm actually running OpenSuse 10.3 on my
laptop now. I'm running gnome but I have to run kbluetooth to get the
mouse to work. Couldn't get gnome to see it at all. Even with
kbluetooth, the mouse quits after a certain amount of inactivity.
Haven't figured out how much though. When this happens I have to
manually make kbluetooth reconnect. Very frustrating.


People wou use a GUI instead of the command line... ;-)
Since I actually stumbled over what looks like the answer, see the "-t"
option of the hidd command.


Now if I could get the --search command to *find* anything I would be
happy. But changing the timeout may solve your problems. And yes, dmesg
seems to show HID initializing, hidd runs fine, just doesn't see
anything. Like a keyboard, mouse, printer, and two cell phone sitting on
top of the &^%&^%&^ case! Bah!



Same mouse and same laptop running Vista I never had these issues. It
was found easily and never disconnected.


No way in hell...


--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 04-04-2008, 11:54 PM
Bill Davidsen
 
Default Where's the bluetooth jargon demystifier?

Tom Horsley wrote:

On Sat, 29 Mar 2008 11:03:28 +0000 (UTC)
Mike <mike.cloaked@gmail.com> wrote:


I also realised I had not used my BT mouse on my F8 laptop, and am in the
same boat as you guys!


As near as I can tell, the theory is that hidd is obsolete and the
new InputService does the job. I accidentally stumbled across a
wiki page that gave an example of some dbus gibberish used to
feed the input service various info: http://wiki.bluez.org/wiki/Input
(I've rarely seen such dense gibberish :-).

My impression is also that the gnome-bluetooth stuff is supposed to
know how to talk to this thing, but the gui for bluetooth preferences
is barely less cryptic than the wiki page.

By using the gnome utility in combination with manually running
hidd --search and taking the back off the keyboard to get to the
button I need to push to make it connect, I finally got the input
service to record some files in the /var/lib/bluetooth tree, but
even with the files there, I still don't get the keyboard automatically
reconnected on a reboot - I still need to run hidd --search and
push the button.

Did you run the --connect command after finding the device? (I assume
so, but BT is magic)



It works much better with the logitech dongle that simply make it look
like a USB keyboard, but unfortunately X or the linux USB layer
or something doesn't recognize the mouse protocol, so the touchpad
will only work with the bluetooth adapter.

So right now my choices are: No mouse, or no auto connection.




--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 04-04-2008, 11:56 PM
Bill Davidsen
 
Default Where's the bluetooth jargon demystifier?

Mike wrote:

Mike <mike.cloaked <at> gmail.com> writes:


So some reading will now be needed!



I went back to my start point :

As root did
hidd --server --search

clicked reset and it paired up with the Logitech BT mouse.

After rebooting it was not connected!

So I had to do as root
hidd --connect BT-MAC-Address
and then it connected...


Did that result in a file in /var/lib/bluetooth?

So there is something not right with bluetooth -


Maybe someone else on this list can help out here?







--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 04-05-2008, 12:00 AM
Tom Horsley
 
Default Where's the bluetooth jargon demystifier?

On Fri, 04 Apr 2008 19:54:59 -0400
Bill Davidsen <davidsen@tmr.com> wrote:

> Did you run the --connect command after finding the device? (I assume
> so, but BT is magic)

When I was playing with bluetooth, I never once got --connect to
work, the only thing that ever caused the keyboard to appear
was doing a --search, then (before the search timed out) taking
the back off the keyboard and pressing the connect button.

I have since gotten everything working with the USB dongle, and
it functions perfectly. I never have to push any buttons on the
keyboard or dongle (even if I reboot or move the dongle to a
different computer), the USB interface lets the keyboard work
in the BIOS screen and in grub, etc.

I have abandoned bluetooth till I happen to get something that
only works in bluetooth mode and I am forced to try again :-).

Here's the tale of my keyboard:

http://home.att.net/~Tom.Horsley/mini.html

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 04-07-2008, 05:07 PM
Bill Davidsen
 
Default Where's the bluetooth jargon demystifier?

Tom Horsley wrote:

On Fri, 04 Apr 2008 19:54:59 -0400
Bill Davidsen <davidsen@tmr.com> wrote:

Did you run the --connect command after finding the device? (I assume
so, but BT is magic)


When I was playing with bluetooth, I never once got --connect to
work, the only thing that ever caused the keyboard to appear
was doing a --search, then (before the search timed out) taking
the back off the keyboard and pressing the connect button.

I have since gotten everything working with the USB dongle, and
it functions perfectly. I never have to push any buttons on the
keyboard or dongle (even if I reboot or move the dongle to a
different computer), the USB interface lets the keyboard work
in the BIOS screen and in grub, etc.

I have abandoned bluetooth till I happen to get something that
only works in bluetooth mode and I am forced to try again :-).

Here's the tale of my keyboard:

http://home.att.net/~Tom.Horsley/mini.html

Thank you for documenting, I would love to have BT speakers and printing
working, the current setup really rots.


--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 

Thread Tools




All times are GMT. The time now is 03:56 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org