Greetings -
I have a Logitech mouse and keyboard that use bluetooth (dinovo). I
have enabled bluetooth on this Fedora 8 system and both work well with
two problems.
(1) When I lock the system and return later the mouse no longer works.
I have to open a terminal window and issue an hidd --connect command.
(2) When I log out, both the mouse and keyboard stop working. I have to
connect a USB mouse and USB keyboard to enter the authentication
information. Once logged in the bluetooth devices usually work,
although I sometimes have to issue an hidd --connect command to enable
the keyboard.
Any suggestions on resolving these issues would be appreciated.
Thank you,
Brad
On Fri, 30 Nov 2007, Dave Young wrote:
> > This particular warning means, that someone (usually indeed hid2hci)
> > passed usage through hiddev that was out of bounds, with respect to
> > the device's report descriptor.
> Is this behaviour the normal one? IMHO, userspace program should not
> cause kernel warnings like this no mater what input from users.
It has been on my todo list to convert that WARN_ON() to something that
won't scare users that much, especially the stacktrace shouldn't certainly
be there. I will do it.
--
Jiri Kosina
On Nov 30, 2007 4:43 AM, Jiri Kosina <[email protected]> wrote:
> On Thu, 29 Nov 2007, Marcel Holtmann wrote:
>
> > > >Nov 28 18:53:39 pico kernel: WARNING: at drivers/hid/hid-core.c:784
> [ ... ]
>
> > > Does bluetooth input devices have something to do with usbhid? I don't
> > > know, perhaps this is another problem in kernel.
> > in case you have a HID proxy dongle the usbhid driver can be involved. And
> > since this is hiddev, then it will be caused by the hid2hci program.
>
> Absolutely.
>
> This particular warning means, that someone (usually indeed hid2hci)
> passed usage through hiddev that was out of bounds, with respect to the
> device's report descriptor.
Is this behaviour the normal one? IMHO, userspace program should not
cause kernel warnings like this no mater what input from users.
>
> This usually means that hid2hci has chosen the wrong method to switch the
> modes. Unfortunately, it's not easy to implement always the switching
> properly, if we don't know the vendor-specific packet that has to be sent.
>
> --
> Jiri Kosina
>
On Thu, 29 Nov 2007, Marcel Holtmann wrote:
> > >Nov 28 18:53:39 pico kernel: WARNING: at drivers/hid/hid-core.c:784
[ ... ]
> > Does bluetooth input devices have something to do with usbhid? I don't
> > know, perhaps this is another problem in kernel.
> in case you have a HID proxy dongle the usbhid driver can be involved. And
> since this is hiddev, then it will be caused by the hid2hci program.
Absolutely.
This particular warning means, that someone (usually indeed hid2hci)
passed usage through hiddev that was out of bounds, with respect to the
device's report descriptor.
This usually means that hid2hci has chosen the wrong method to switch the
modes. Unfortunately, it's not easy to implement always the switching
properly, if we don't know the vendor-specific packet that has to be sent.
--
Jiri Kosina
Hi Dave,
>> apparently does manage bluetooth devices using bluetooth-input-
>> service.
>> I still have the problem of the devices disappearing if idle for too
>> long such as when i lock the desktop or log out for a long period.
>> Sometimes I can re-enable the devices, but sometimes I cannot.
>> This is
>> frustrating.
>>
>> I see a the following several times in the system log if i restart
>> bluetooth:
>> Nov 28 18:53:39 pico kernel: WARNING: at drivers/hid/hid-core.c:784
>> implement() (Tainted: P )
>> Nov 28 18:53:39 pico kernel:
>> Nov 28 18:53:39 pico kernel: Call Trace:
>> Nov 28 18:53:39 pico kernel: [<ffffffff811d8549>] hid_output_report
>> +0x1c5/0x232
>> Nov 28 18:53:39 pico kernel: [<ffffffff811ddaf1>] hid_submit_ctrl
>> +0x60/0x24b
>> Nov 28 18:53:39 pico kernel: [<ffffffff811dde45>]
>> usbhid_submit_report
>> +0x169/0x19e
>> Nov 28 18:53:39 pico kernel: [<ffffffff811e030b>] hiddev_ioctl
>> +0x368/0x919
>> Nov 28 18:53:39 pico kernel: [<ffffffff810f54c5>] inode_has_perm
>> +0x65/0x72
>> Nov 28 18:53:39 pico kernel: [<ffffffff81120c17>] __up_read
>> +0x19/0x7f
>> Nov 28 18:53:39 pico kernel: [<ffffffff8125eecc>] do_page_fault
>> +0x490/0x7e4
>> Nov 28 18:53:39 pico kernel: [<ffffffff810a7399>] do_ioctl+0x55/0x6b
>> Nov 28 18:53:39 pico kernel: [<ffffffff810a75f2>] vfs_ioctl
>> +0x243/0x25c
>> Nov 28 18:53:39 pico kernel: [<ffffffff810a7664>] sys_ioctl
>> +0x59/0x79
>> Nov 28 18:53:39 pico kernel: [<ffffffff8100bd45>] tracesys+0xd5/0xda
>>
>
> Does bluetooth input devices have something to do with usbhid? I don't
> know, perhaps this is another problem in kernel.
in case you have a HID proxy dongle the usbhid driver can be involved.
And since this is hiddev, then it will be caused by the hid2hci program.
Regards
Marcel
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
On Nov 29, 2007 11:03 AM, Brad Smith <[email protected]> wrote:
>
> Thank you for the reply Marvel. I use the gnome bluetooth client which
Marcel
> apparently does manage bluetooth devices using bluetooth-input-service.
> I still have the problem of the devices disappearing if idle for too
> long such as when i lock the desktop or log out for a long period.
> Sometimes I can re-enable the devices, but sometimes I cannot. This is
> frustrating.
>
> I see a the following several times in the system log if i restart
> bluetooth:
> Nov 28 18:53:39 pico kernel: WARNING: at drivers/hid/hid-core.c:784
> implement() (Tainted: P )
> Nov 28 18:53:39 pico kernel:
> Nov 28 18:53:39 pico kernel: Call Trace:
> Nov 28 18:53:39 pico kernel: [<ffffffff811d8549>] hid_output_report
> +0x1c5/0x232
> Nov 28 18:53:39 pico kernel: [<ffffffff811ddaf1>] hid_submit_ctrl
> +0x60/0x24b
> Nov 28 18:53:39 pico kernel: [<ffffffff811dde45>] usbhid_submit_report
> +0x169/0x19e
> Nov 28 18:53:39 pico kernel: [<ffffffff811e030b>] hiddev_ioctl
> +0x368/0x919
> Nov 28 18:53:39 pico kernel: [<ffffffff810f54c5>] inode_has_perm
> +0x65/0x72
> Nov 28 18:53:39 pico kernel: [<ffffffff81120c17>] __up_read+0x19/0x7f
> Nov 28 18:53:39 pico kernel: [<ffffffff8125eecc>] do_page_fault
> +0x490/0x7e4
> Nov 28 18:53:39 pico kernel: [<ffffffff810a7399>] do_ioctl+0x55/0x6b
> Nov 28 18:53:39 pico kernel: [<ffffffff810a75f2>] vfs_ioctl+0x243/0x25c
> Nov 28 18:53:39 pico kernel: [<ffffffff810a7664>] sys_ioctl+0x59/0x79
> Nov 28 18:53:39 pico kernel: [<ffffffff8100bd45>] tracesys+0xd5/0xda
>
Does bluetooth input devices have something to do with usbhid? I don't
know, perhaps this is another problem in kernel.
Please dont mind to add lkml as cc.
Regards
dave
> Brad
>
>
>
> On Mon, 2007-11-26 at 06:49 +0100, Marcel Holtmann wrote:
> > Hi Brad,
> >
> > > I have a Logitech mouse and keyboard that use bluetooth (dinovo). I
> > > have enabled bluetooth on this Fedora 8 system and both work well with
> > > two problems.
> > >
> > > (1) When I lock the system and return later the mouse no longer works.
> > > I have to open a terminal window and issue an hidd --connect command.
> > >
> > > (2) When I log out, both the mouse and keyboard stop working. I have to
> > > connect a USB mouse and USB keyboard to enter the authentication
> > > information. Once logged in the bluetooth devices usually work,
> > > although I sometimes have to issue an hidd --connect command to enable
> > > the keyboard.
> > >
> > > Any suggestions on resolving these issues would be appreciated.
> >
> > not using hidd and using bluetoothd-input-service instead is one thing.
> > For input devices to re-connect you have to have a daemon running that
> > handles this. The input service is the best way to achieve this. Check
> > the BlueZ wiki for details.
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell. From the desktop to the data center, Linux is going
> mainstream. Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
> _______________________________________________
> Bluez-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
>
Thank you for the reply Marvel. I use the gnome bluetooth client which
apparently does manage bluetooth devices using bluetooth-input-service.
I still have the problem of the devices disappearing if idle for too
long such as when i lock the desktop or log out for a long period.
Sometimes I can re-enable the devices, but sometimes I cannot. This is
frustrating.
I see a the following several times in the system log if i restart
bluetooth:
Nov 28 18:53:39 pico kernel: WARNING: at drivers/hid/hid-core.c:784
implement() (Tainted: P )
Nov 28 18:53:39 pico kernel:
Nov 28 18:53:39 pico kernel: Call Trace:
Nov 28 18:53:39 pico kernel: [<ffffffff811d8549>] hid_output_report
+0x1c5/0x232
Nov 28 18:53:39 pico kernel: [<ffffffff811ddaf1>] hid_submit_ctrl
+0x60/0x24b
Nov 28 18:53:39 pico kernel: [<ffffffff811dde45>] usbhid_submit_report
+0x169/0x19e
Nov 28 18:53:39 pico kernel: [<ffffffff811e030b>] hiddev_ioctl
+0x368/0x919
Nov 28 18:53:39 pico kernel: [<ffffffff810f54c5>] inode_has_perm
+0x65/0x72
Nov 28 18:53:39 pico kernel: [<ffffffff81120c17>] __up_read+0x19/0x7f
Nov 28 18:53:39 pico kernel: [<ffffffff8125eecc>] do_page_fault
+0x490/0x7e4
Nov 28 18:53:39 pico kernel: [<ffffffff810a7399>] do_ioctl+0x55/0x6b
Nov 28 18:53:39 pico kernel: [<ffffffff810a75f2>] vfs_ioctl+0x243/0x25c
Nov 28 18:53:39 pico kernel: [<ffffffff810a7664>] sys_ioctl+0x59/0x79
Nov 28 18:53:39 pico kernel: [<ffffffff8100bd45>] tracesys+0xd5/0xda
Brad
On Mon, 2007-11-26 at 06:49 +0100, Marcel Holtmann wrote:
> Hi Brad,
>
> > I have a Logitech mouse and keyboard that use bluetooth (dinovo). I
> > have enabled bluetooth on this Fedora 8 system and both work well with
> > two problems.
> >
> > (1) When I lock the system and return later the mouse no longer works.
> > I have to open a terminal window and issue an hidd --connect command.
> >
> > (2) When I log out, both the mouse and keyboard stop working. I have to
> > connect a USB mouse and USB keyboard to enter the authentication
> > information. Once logged in the bluetooth devices usually work,
> > although I sometimes have to issue an hidd --connect command to enable
> > the keyboard.
> >
> > Any suggestions on resolving these issues would be appreciated.
>
> not using hidd and using bluetoothd-input-service instead is one thing.
> For input devices to re-connect you have to have a daemon running that
> handles this. The input service is the best way to achieve this. Check
> the BlueZ wiki for details.
Hi Brad,
> I have a Logitech mouse and keyboard that use bluetooth (dinovo). I
> have enabled bluetooth on this Fedora 8 system and both work well with
> two problems.
>
> (1) When I lock the system and return later the mouse no longer works.
> I have to open a terminal window and issue an hidd --connect command.
>
> (2) When I log out, both the mouse and keyboard stop working. I have to
> connect a USB mouse and USB keyboard to enter the authentication
> information. Once logged in the bluetooth devices usually work,
> although I sometimes have to issue an hidd --connect command to enable
> the keyboard.
>
> Any suggestions on resolving these issues would be appreciated.
not using hidd and using bluetoothd-input-service instead is one thing.
For input devices to re-connect you have to have a daemon running that
handles this. The input service is the best way to achieve this. Check
the BlueZ wiki for details.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBMQ0KDQpMZSBTdW4s
IDkgRGVjIDIwMDcgMTc6NDU6NDAgKzAxMDAsDQpGYWJyaWNlIE3DqW5hcmQgPG1lbmFyZC5mYWJy
aWNlQG9yYW5nZS5mcj4gYSDDqWNyaXQgOg0KDQoNCj4gU3VyZSEgSGVyZSBpdCBpcy4NCg0KSGkg
RmFicmljZSwgdGhhbmtzIGEgbG90ICENCg0KSSB3aWxsIHRlc3QgaXQgYXMgc29vbiBhcyBwb3Nz
aWJsZSA7KQ0KDQpBbnkgY29tbWVudHMgZnJvbSB0aGUgYmx1ZXogdGVhbSBhYm91dCB0aGUgaGlk
MmhjaSBwYXRjaCA/Pw0KDQpCZXN0IHJlZ2FyZHMuDQoNCkRpZGllciBMaW5rDQoNCi0gLS0gDQpE
aWRpZXIgTGluayA8ZGlkaWVyQGZhbWlsbGUtbGluay5mcj4NCkphYmJlciA6IGRpZGllcl9saW5r
QGphYmJlci5mcg0KTVNOIDogemFuZmliQGhvdG1haWwuZnINClNJUCA6IFphbmZpYkBla2lnYS5u
ZXQNCg0KQ2zDqSBHUEcgOiA3NUJBQzlFRQ0KLS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0N
ClZlcnNpb246IEdudVBHIHYxLjQuNyAoR05VL0xpbnV4KQ0KDQppRDhEQlFGSFhUTEFreVB3aW5X
NnllNFJBZzlzQUo5cnROK3gwSU84bXJFRkpMS3BQQk1nR2dTSlhnQ2RIMTl3DQpwTnp1bG8yWEx1
OHlZU3l1ak00M01oTT0NCj1vb1ZoDQotLS0tLUVORCBQR1AgU0lHTkFUVVJFLS0tLS0NCi0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0KU0YuTmV0IGVtYWlsIGlzIHNwb25zb3JlZCBieToKQ2hlY2sgb3V0IHRoZSBu
ZXcgU291cmNlRm9yZ2UubmV0IE1hcmtldHBsYWNlLgpJdCdzIHRoZSBiZXN0IHBsYWNlIHRvIGJ1
eSBvciBzZWxsIHNlcnZpY2VzIGZvcgpqdXN0IGFib3V0IGFueXRoaW5nIE9wZW4gU291cmNlLgpo
dHRwOi8vc291cmNlZm9yZ2UubmV0L3NlcnZpY2VzL2J1eS9pbmRleC5waHAKX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KQmx1ZXotdXNlcnMgbWFpbGluZyBs
aXN0CkJsdWV6LXVzZXJzQGxpc3RzLnNvdXJjZWZvcmdlLm5ldApodHRwczovL2xpc3RzLnNvdXJj
ZWZvcmdlLm5ldC9saXN0cy9saXN0aW5mby9ibHVlei11c2Vycwo=
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBMQ0KDQpMZSBTYXQs
IDggRGVjIDIwMDcgMTE6MjU6MDMgKzAxMDAsDQpGYWJyaWNlIE3DqW5hcmQgPG1lbmFyZC5mYWJy
aWNlQG9yYW5nZS5mcj4gYSDDqWNyaXQgOg0KDQo+IE9uIFNhdHVyZGF5IDA4IERlY2VtYmVyIDIw
MDcgMDA6NDI6MzkgRGlkaWVyIExpbmsgd3JvdGU6DQo+ID4gSGkgYWxsLA0KPiA+DQo+ID4gSnVz
dCBmb3IgYWRkIHNvbWV0aGluZyBvbiB0aGlzIGJ1ZyByZXBvcnQsIEkndmUgdGhlIHNhbWUgaGFy
ZHdhcmUNCj4gPiAoTG9naXRlY2ggZGlub3ZvIGtleWJvYXJkK21vdXNlKSwgY29ubmVjdGVkIHdp
dGggYmx1ZXRvb3RoDQo+ID4gaGNpZC9ibHVldG9vdGhkLXNlcnZpY2UtaW5wdXQNCj4gPg0KPiA+
IEZpcnN0IG9mIGFsbCwgdGhpcyB3b3JrIHZlcnkgd2VsbCBhdCBmaXJzdCBydW4gYW5kIGFsbCB0
aGUgdGltZSBJDQo+ID4gaW50ZXJhY3Qgd2l0aCBrZXlib2FyZCBhbmQgbW91c2UsIHZlcnkgZ29v
ZCBqb2Igb2YgdGhlIGJsdWV6IHN0YWNrDQo+ID4gZGV2ZWxvcHBlcnMgIQ0KPiA+DQo+ID4gQnV0
LCBsaWtlIEJyYWQsIGFmdGVyIGFuIGFtb3VudCBvZiBpbmFjdGl2aXR5IChhYm91dCAyMCBtaW51
dGVzDQo+ID4gSSB0aGluayAuLi4pIHRoZSBkZXZpY2VzIGdvIHRvIHNsZWVwIG1vZGUgYW5kIG5l
dmVyIHJlY29ubmVjdC4gSQ0KPiA+IG5lZWQgdG8gcmVzdGFydCB0aGUgYmx1ZXRvb3RoIHNlcnZp
Y2UgYXQgYWxsLCB3aXRoIGFub3RoZXIgdXNiDQo+ID4ga2V5Ym9hcmQuIE15IGtlcm5lbCBsb2cg
Y29udGFpbiB0aGUgc2FtZSB3YXJuaW5ncyBhcyBCcmFkIGVhY2ggdGltZQ0KPiA+IHRoZSBzZXJ2
aWNlIGlzIHJlc3RhcnRlZC4NCg0KSGkgRmFicmljZSwNCg0KPiANCj4gSSBoYWQgYSBzaW1pbGFy
IHByb2JsZW0sIHNlZSBteSBwb3N0IGZvciBhIHBvc3NpYmxlIHNvbHV0aW9uIChpdA0KPiB3b3Jr
cyBmb3IgbWUpOg0KPiBodHRwOi8vYXJ0aWNsZS5nbWFuZS5vcmcvZ21hbmUubGludXguYmx1ZXou
dXNlci8xMjk4OC9tYXRjaD1kaW5vdm8NCg0KVGhhbmtzIGZvciB0aGlzIGxpbmssIEkndmUgbWlz
c2VkIHlvdXIgbWVzc2FnZSBhbmQgSSdtIG5vdCBhbG9uZQ0KYmVjYXVzZSBub2JvZHkgZnJvbSBi
bHVleiBkZXZlbG9wZXJzIGhhdmUgY29tbWVudGVkIHlvdSBwb3N0IC4uLiA6KA0KDQpJIGtub3cg
Ymx1ZXogaXMgYSBsb3Qgb2Ygd29yayBmb3IgTWFyY2VsIGFuZCBvdGhlcnMgYnV0IEkgdGhpbmsg
dGhpcw0KaXNzdWUgaXMgaW1wb3J0YW50IGZvciBhbGwgZGlub3ZvIHVzZXJzLCBhbmQgbWF5YmUg
b3RoZXJzIGtleWJvYXJkIHNldA0KZnJvbSBMb2dpdGVjaCA/DQoNCkFzIERhdmUgWW91bmcgcG9p
bnRlZCBiZWZvcmUsIEkgdGhpbmsgdGhpcyB3YXJuaW5nIChhbmQgdGhlIG9vcHNlIEkNCnBvc3Rl
ZCkgbmVlZCB0byBiZSBmaXhlZCBmb3IgaW1wcm92ZSBrZXJuZWwgc3RhYmlsaXR5Lg0KDQpGaW5h
bGx5LCBGYWJyaWNlLCB5b3VyIHBhdGNoZXMgYXJlbid0IGFjY2Vzc2libGUgd2l0aCB0aGUgc291
cmNlZm9yZ2UNCmFuZCBnbWFuZSBhcmNoaXZlcyBvZiB0aGUgbGlzdCwgY2FuIHlvdSByZXNlbmQg
b3IgcHV0IGl0IG9uIHBhc3RlYmluIG9yDQpvdGhlciB3ZWIgbG9jYXRpb24gcGxlYXNlID8/DQoN
ClRoYW5rcyBhIGxvdCBmb3IgdGhlIGdvb2Qgd29yayBhbmQgYmVzdCByZWdhcmRzLg0KDQpEaWRp
ZXIgTGluaw0KDQpwczogdGhlIGxhc3QgLW1oMSBwYXRjaCBmb3Iga2VybmVsIDIuNi4yMyBkb2Vz
bid0IHNvbHZlIHRoZQ0Kc2xlZXAvcmVjb25uZWN0IGlzc3VlLg0KDQotIC0tIA0KRGlkaWVyIExp
bmsgPGRpZGllckBmYW1pbGxlLWxpbmsuZnI+DQpKYWJiZXIgOiBkaWRpZXJfbGlua0BqYWJiZXIu
ZnINCk1TTiA6IHphbmZpYkBob3RtYWlsLmZyDQpTSVAgOiBaYW5maWJAZWtpZ2EubmV0DQoNCkNs
w6kgR1BHIDogNzVCQUM5RUUNCi0tLS0tQkVHSU4gUEdQIFNJR05BVFVSRS0tLS0tDQpWZXJzaW9u
OiBHbnVQRyB2MS40LjcgKEdOVS9MaW51eCkNCg0KaUQ4REJRRkhXcFRIa3lQd2luVzZ5ZTRSQXBX
a0FKOUtORWdDdFJCUU1uTHpSZkRRRUtQRG1Jbk5MQUNmYlBkMQ0KQUdpcUdxZVZVNzRseHhCdHNV
VXFSOFU9DQo9V0hOWQ0KLS0tLS1FTkQgUEdQIFNJR05BVFVSRS0tLS0tDQotLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tClNGLk5ldCBlbWFpbCBpcyBzcG9uc29yZWQgYnk6CkNoZWNrIG91dCB0aGUgbmV3IFNvdXJj
ZUZvcmdlLm5ldCBNYXJrZXRwbGFjZS4KSXQncyB0aGUgYmVzdCBwbGFjZSB0byBidXkgb3Igc2Vs
bCBzZXJ2aWNlcyBmb3IKanVzdCBhYm91dCBhbnl0aGluZyBPcGVuIFNvdXJjZS4KaHR0cDovL3Nv
dXJjZWZvcmdlLm5ldC9zZXJ2aWNlcy9idXkvaW5kZXgucGhwCl9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fCkJsdWV6LXVzZXJzIG1haWxpbmcgbGlzdApCbHVl
ei11c2Vyc0BsaXN0cy5zb3VyY2Vmb3JnZS5uZXQKaHR0cHM6Ly9saXN0cy5zb3VyY2Vmb3JnZS5u
ZXQvbGlzdHMvbGlzdGluZm8vYmx1ZXotdXNlcnMK
On Saturday 08 December 2007 00:42:39 Didier Link wrote:
> Hi all,
>
> Just for add something on this bug report, I've the same hardware
> (Logitech dinovo keyboard+mouse), connected with bluetooth
> hcid/bluetoothd-service-input
>
> First of all, this work very well at first run and all the time I
> interact with keyboard and mouse, very good job of the bluez stack
> developpers !
>
> But, like Brad, after an amount of inactivity (about 20 minutes
> I think ...) the devices go to sleep mode and never reconnect. I need to
> restart the bluetooth service at all, with another usb keyboard. My
> kernel log contain the same warnings as Brad each time the service is
> restarted.
I had a similar problem, see my post for a possible solution (it works for =
me):
http://article.gmane.org/gmane.linux.bluez.user/12988/match=3Ddinovo
Regards,
Fabrice M=E9nard
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users