| View previous topic :: View next topic |
| Author |
Message |
djnauk
Apprentice
Joined: 11 Feb 2003
Posts: 183
Location: Caerphilly, Wales, UK
|
 Posted: Wed Mar 30, 2005 11:40 pm Post subject: |
 |
|
| sibov wrote: | | i ll try to patch my current kernel with the latest bluez patch set |
np. AFAIK, there's nothing new in the patches. It just updates what's there, so you should just be able to patch, clean, compile and reload (or reboot if the modules are built it). 
_________________
Jonathan Wright (Technical Director, JAB Web Solutions)
UK Hosting & Reseller Hosting from JAB Web Solutions |
|
| Back to top |
|
 |
basramm
n00b
Joined: 24 Nov 2002
Posts: 56
Location: Düsseldorf, Germany
|
| Posted: Sun Apr 24, 2005 1:06 pm Post subject: |
|
|
First I want to say: great howto, it helped me a lot and i am now happily using my Logitech diNovo.
But I still have a question. Is it possible to somehow read the keyboards battery status and maybe issue a warning if the power is getting low? I saw something alike on an Ibook with an Apple Wireless Keyboard. |
|
| Back to top |
|
|
sPOiDar
n00b
Joined: 05 May 2005
Posts: 3
Location: Melbourne, Oz
|
| Posted: Sun May 08, 2005 5:17 am Post subject: Re: Additional Tips N Tricks for DiNovo |
|
|
| xannor wrote: |
<snip>
With this code installed, everytime you plug in (or the system otherwise recognises) your adaptor it will run hid2hci so it is in hci mode.
I am still trying to come up with a solution to "not being able to use the adapter as a HID device once it is in HCI mode" (for bios and bootloader modes after reboot.) I think it could be done if we had a way to reset the device during shutdown, but I do not know how to do that. any takers? |
Firstly, very nice idea using udev to convert the device - I like it a lot, will try it out once I go home and steal a keyboard from one of the other boxen... as for converting back to HID on reboot, that should be very easy - just adding:
/etc/local.stop
| Code: | | /usr/sbin/hid2hci --tohid |
or, this might be a sensible change to the bluetooth init script:
/etc/init.d/bluetooth
| Code: | --- bluetooth 2005/05/08 05:05:25 1.1
+++ bluetooth 2005/05/08 05:07:39
@@ -96,6 +96,12 @@
ebegin "Shutting down Bluetooth"
+ if [ "${HID2HCI_ENABLE}" = "true" -a -x /usr/sbin/hid2hci ]; then
+ ebegin " Reverting hid2hci"
+ /usr/sbin/hid2hci -1 -q #be quiet
+ eend $?
+ fi
+
if [ "${PAND_ENABLE}" = "true" -a -x /usr/bin/pand ]; then
ebegin " Stopping pand"
start-stop-daemon --stop --quiet --exec /usr/bin/pand |
And you'd think that would be that... but I've just done a quick test via ssh and it seems that the '--tohid' option is not working for me... (I just get a message saying "No devices in HID mode", whereas it should output the device id). I'll test when actually at the box, but if anyone else has info on whether --tohid works that would be handy |
|
| Back to top |
|
|
julioromano
n00b
Joined: 19 Mar 2004
Posts: 43
Location: Italy
|
| Posted: Sun Jul 24, 2005 1:44 pm Post subject: |
|
|
Hi everybody, I bought yesterday a Dinovo Cordless Desktop for Notebooks (the wireless model without bluetooth).
I though the configuration scripts for xorg would be the same for having the media keys working, it seems I was wrong.
And for what I've checked it seems that pressing the media keys on the keyboard doesn't even generate an event for any of the /dev/input/event* devices.
Has anyone some suggestions?
Thanks and bye,
Marco
_________________
Nothing lasts forever, even a diamond. |
|
| Back to top |
|
|
tagwar
Tux's lil' helper
Joined: 11 Aug 2004
Posts: 147
Location: Karlsruhe
|
| Posted: Thu Jul 28, 2005 6:02 am Post subject: LCD |
|
|
Is there any progress with the LCD? I'm thinking about buying a DiNovo, but I wouldn't want to have something sitting on my desk that's so god damn proprietary that I cant get it to work... 
Guess I'll have to bug Logitech about that....?
Edit: Have started buggin them...
question: Will there be development on a driver from Logitechs side, or is it possible to get a specification of the protocoll used, so the community can create a driver themselves.
answer for now: Logitech is not going to develop a linux driver, cause all our customers use Windows or MacOS...
 so far... will report back if I get any news... the other way would be reverse engineering I think... anyone know how to, or if it is possible?
Second Edit: I got another answer from someone at Logitech somewhere "up the ladder"...
| Quote: | Leider handelt es sich hierbei um Firmeninterne Technologien, die nicht öffentlich zur Verfügung gestellt werden.
Auch ist dies nicht geplant. Die Grund ist folgender:
Eine Entwicklung solcher Treiber für Linux oder eine Unterstützung anderer Entwickler wäre nicht das Problem. Problematisch wäre die Technische Unterstützung, wenn bei den Usern Schwierigkeiten auftreten. Linux zu supporten ist sehr aufwendig (jede Distribution ist im Prinzip ein eigenes Betriebssystem). Daher wird dieses Betriebssystem von unserer Seite wohl auf absehbarer Zeit nicht unterstützt.
Ich bedauere Ihnen keine günstigere Aussage machen zu können. |
for those who don't speak german, it says that the technology used in DiNovo is "internal" and won't be made public. Second sentence says that helping developers create a driver or create one themselves wouldn't be a problem, but Logitech is not going to support linux in any way, because there are so many different distris out there and every single one of them is like a different OS.... Is it only me, or does the second sentence not fit with the first?
Sorry, but I realy dont like this answer.. so, as long as noone has reverse engineered the needed information and built a driver themselves, i'm not going to buy a dinovo.. I might repeat myself, but I'm not going to have proprietary stuff sitting on my desk, that doesnt work with my system.
Greets
Tom |
|
| Back to top |
|
|
Diavolo
Apprentice
Joined: 09 Jan 2005
Posts: 151
|
| Posted: Sat Aug 13, 2005 7:31 pm Post subject: |
|
|
Thank you for that HowTo - it helped me to install my new diNovo Set.
I have managed to set all special keys, only the first key on the left side (the one with the moon) does not work.
Here is my "inet" entry:
key <I63> { [ XF86Sleep ] };
key <I02> { [ XF86HomePage ] };
key <I6C> { [ XF86Mail ] };
key <I07> { [ Undo ] };
key <K67> { [ XF86MyComputer ] };
key <I22> { [ XF86AudioPlay, XF86AudioPause ] };
key <I24> { [ XF86AudioStop ] };
key <I10> { [ XF86AudioPrev ] };
key <I17> { [ XF86Search ] };
key <I19> { [ XF86AudioNext ] };
key <I30> { [ XF86AudioRaiseVolume ] };
key <I2E> { [ XF86AudioLowerVolume ] };
key <I20> { [ XF86AudioMute ] };
key <XFER> { [ XF86AudioMedia ] };
key <I6A> { [ XF86Back ] };
key <I69> { [ XF86Forward ] };
key <FK17> { [ XF86Search ] };
Another thing: What are the entries Undo, XF86MyComputer, XF86Back and XF86Forward? I don't have such keys on my keyboard.
How can I add functionality to the F-Keys when F1-F12 are not active. On Windows they are set up with different actions. Is there a possibility to activate the "F-Key" as default?
And does anyone know how to adjust the mouse buttons on my MX900?
Thank you! |
|
| Back to top |
|
|
javac16
Tux's lil' helper
Joined: 10 Aug 2003
Posts: 111
|
| Posted: Fri Sep 02, 2005 2:38 am Post subject: |
|
|
| sibov wrote: | | djnauk wrote: | | sibov wrote: | Hi djnauk,
i am running on 2.6.11-nitro2, but the bluetooth stuff is working fine in hidd2hci mode. |
Yeah, the problems we were having is that the bluetooth modules weren't running mode discovery on the items, and therefore the keyboard was only running in boot mode. Running hidd will tell you how the keyboard/mouse/mediapad are running. If they all say boot mode, then you will need to get the latest patch (at least 2.6.11-mh2) from www.bluez.org and patch it against the kernel: cd /usr/src/linux && patch -p1 -i patch_file. |
u are right,
hidd --show
00:07:61:19:6B:27 HID Boot Device [046d:b001] connected [boot-protocol]
00:07:61:18:7C:0C HID Boot Device [046d:b303] connected [boot-protocol]
i ll try to patch my current kernel with the latest bluez patch set
thanx |
I recently purchased the dinovo desktop and have the keyboard and mouse "basically" working but am having the same problem as above. No media keys work and I seem to be stuck in this "boot" mode. I looked at the bluez website but they only had a 2.6.13 patch. I am currently running 2.6.12-gentoo-r9, so I am guessing that patch may not apply. I am also assuming that this should include the patch that everyone here installed and had success with. Any other ideas of where I could look for a bad setting?
| Code: | # hidd
00:07:61:24:2E:0F HID Boot Device [046d:b3e1] connected [boot-protocol]
00:07:61:24:0B:EC HID Boot Device [046d:b303] connected [boot-protocol]
00:07:61:23:CE:A7 HID Boot Device [046d:b001] connected [boot-protocol]
|
Thanks!
(Edited to add hidd result) |
|
| Back to top |
|
|
javac16
Tux's lil' helper
Joined: 10 Aug 2003
Posts: 111
|
| Posted: Fri Sep 02, 2005 4:42 am Post subject: |
|
|
If I click on the connect button on the media pad and run hcitool I get the following:
| Code: | etc # hcitool scan
Scanning ...
00:07:61:24:2E:0F Logitech Mediapad
|
However I can't seem to actually get this to connect, with
| Code: | | hictool cc 00:07:61:24:2E:0F |
I get no response back, but the media pad does not connect - button presses do nothing except bring up "No Network" in the LCD.
It is definitely driving me crazy that I can't set up the media buttons but everyone here seems to be having success... |
|
| Back to top |
|
|
Meeuw
Tux's lil' helper
Joined: 08 Nov 2002
Posts: 77
Location: NL - Oostzaan
|
| Posted: Sat Sep 03, 2005 8:39 am Post subject: |
|
|
| javac16 wrote: | However I can't seem to actually get this to connect, with
| Code: | | hictool cc 00:07:61:24:2E:0F |
|
No, don't do that
try:
1) hit the connect button on your mediapad
2) hidd --search
if this doesn't work remove the link key from /var/lib/bluetooth/*/linkkeys
you could also try removing the batteries en try to reconnect.
you should enable auth and encrypt to enchance security and configure a proper pinhelper in hcid.conf:
...
security user;
...
pin_helper /usr/bin/bluepin;
...
auth enable;
encrypt enable;
...
BTW I'm using a hacked bluepinstub:
| Code: | #!/bin/bash
if [ "${1}" == "out" ] ; then
case ${2} in
"00:07:61:24:XX:XX") # replace with your mouse address
echo "PIN:0000"
exit
;;
"00:07:61:24:XX:XX") # replace with your keyboard address
PIN="${RANDOM}"
echo "PIN:${PIN}"
wall "PIN:${PIN}" &>/dev/null
flite "$(echo -n "pin. "
i=1
while [ $i -le $(echo ${PIN}|wc -m) ] ; do
echo -n "$(echo ${PIN}|cut -c${i}) "
i=$(($i + 1))
done)" -o /dev/stdout|aplay &
echo "${1} Pairing ${2} with pin: ${PIN}" > /dev/console exit
;;
esac
fi
bluepin ${*} |
This code shouts the pin over all your consoles (wall) and out of your speakers using flite, quite effective |
|
| Back to top |
|
|
javac16
Tux's lil' helper
Joined: 10 Aug 2003
Posts: 111
|
| Posted: Sat Sep 03, 2005 7:23 pm Post subject: |
|
|
I tried a number of things based on your suggestions (thank you for them). Should I be running hidd --search as root or a user? I seem to get the same response either way, but I was curious.
I did remove the link key from /var/lib/bluetooth/<device address>/linkkeys
After removing the lines from this file, moving the mouse results in a prompt for the pin. I don't know what it is but have tried "0000" and "" and "1234" with no success.
With auth enabled I get the following when trying to connect the media pad (press connect and then type the search command):
| Code: |
$ hidd --search
Searching ...
Connecting to device 00:07:61:24:2E:0F
Can't get device information: Function not implemented
|
A box does pop up prompting me for a bin...but I honestly have no idea what the pin is for the mouse, media pad or keyboard.
With auth disabled I get this, with no prompt.
| Code: |
tim@morpheus ~ Searching ...
Connecting to device 00:07:61:24:2E:0F
HID create error 13 (Permission denied)
|
When I use your script for the pin (/usr/bin/bluepinstub) with my mods to addresses (note: there isn't one for the media pad?)
| Code: |
"00:07:61:23:CE:A7") # replace with your mouse address
echo "PIN:0000"
exit
;;
"00:07:61:24:0B:EC") # replace with your keyboard address
|
Initially the keyboard was attached but still in "boot mode" like before:
| Code: |
morpheus bin # hidd
00:07:61:24:0B:EC HID Boot Device [046d:b303] connected [boot-protocol]
|
When I pushed connect on the keyboard and then did an hidd --search I got:
| Code: | morpheus bin # hidd --search
Searching ...
Connecting to device 00:07:61:24:0B:EC
Can't get device information: Invalid exchange
|
and a prompt did show up, which I thought was odd...
Anytime I move my mouse right now I get a prompt...so confused...  |
|
| Back to top |
|
|
javac16
Tux's lil' helper
Joined: 10 Aug 2003
Posts: 111
|
| Posted: Sat Sep 03, 2005 7:39 pm Post subject: |
|
|
Played around a little more. It seems "0000" is working for the mouse now, when I actually push connect and then do a hidd --search. It didn't work when I just entered it after doing some mouse movement.
I also realized that when I tried to connect the media pad that a prompt shows up on the LCD, so I could put in the same pin on both places and get it connected.
I then followed that pattern for the keyboard. I entered a pin into the prompt and then typed it on the keyboard. Now I am back to where I started.
| Code: |
# hidd
00:07:61:24:0B:EC HID Boot Device [046d:b303] connected [boot-protocol]
00:07:61:24:2E:0F HID Boot Device [046d:b3e1] connected [boot-protocol]
00:07:61:23:CE:A7 HID Boot Device [046d:b001] connected [boot-protocol]
|
I did all the above as root. |
|
| Back to top |
|
|
Loial
n00b
Joined: 24 Mar 2003
Posts: 29
|
| Posted: Fri Sep 09, 2005 12:14 pm Post subject: hope this helps |
|
|
I found that editing /etc/conf.d/bluetooth and /etc/bluetooth/hcid.conf was about all that was needed to get the keyboard and mouse working in full mode, i.e. not in bootprotocol mode
I'm not sure exactly what I changed in those files, but here they are:
| Code: | # cat /etc/conf.d/bluetooth
# Bluetooth configuraton file
# Start of hcid (allowed values are "true" and "false")
HCID_ENABLE=true
# Config file for hcid
HCID_CONFIG="/etc/bluetooth/hcid.conf"
# Start sdpd (allowed values are "true" and "false")
SDPD_ENABLE=true
# Start hidd (allowed values are "true" and "false")
#HIDD_ENABLE=false
HIDD_ENABLE=true
# Arguments to hidd
HIDD_OPTIONS=""
# Run hid2hci (allowed values are "true" and "false")
#HID2HCI_ENABLE=false
HID2HCI_ENABLE=true
# Bind rfcomm devices (allowed values are "true" and "false")
RFCOMM_ENABLE=true
# Config file for rfcomm
RFCOMM_CONFIG="/etc/bluetooth/rfcomm.conf"
# Start dund (allowed values are "true" and "false")
#DUND_ENABLE=false
DUND_ENABLE=true
# Arguments to dund
DUND_OPTIONS="--listen --persist"
# Start pand (allowed values are "true" and "false")
#PAND_ENABLE=false
PAND_ENABLE=true
# Arguments to pand
PAND_OPTIONS="--listen --role NAP" |
and
| Code: | # cat /etc/bluetooth/hcid.conf
#
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.7 2004/12/13 14:16:03 holtmann Exp $
#
# HCId options
options {
# Automatically initialize new devices
autoinit yes;
# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security user;
# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;
# PIN helper
#pin_helper /usr/bin/bluepin;
#pin_helper /usr/bin/kbluepin;
pin_helper /usr/lib/kdebluetooth/kbluepin;
# D-Bus PIN helper
#dbus_pin_helper;
}
# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "Loial BlueZ";
# Local device class
class 0x3e0100;
# Default packet type
#pkt_type DH1,DM1,HV1;
# Inquiry and Page scan
iscan enable; pscan enable;
# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept,master;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
# Authentication and Encryption (Security Mode 3)
#auth enable;
auth disable;
#encrypt enable;
}
|
Oh and don't forget /etc/bluetooth/pin. You should set it to something nice and use that whenever your pc asks you. (Should be only once)
now a simple | Code: | | rc-update add bluetooth default |
and upon reboot all should be well
there is no need to keep doing stuff like hcitool cc <address> because your keyboard and mediapad should already be connected. IIRC the hcitool cc command is not intended to be used like that. |
|
| Back to top |
|
|
javac16
Tux's lil' helper
Joined: 10 Aug 2003
Posts: 111
|
| Posted: Fri Sep 09, 2005 8:00 pm Post subject: |
|
|
I did have some differences from you in my configs so I changed them...
auth to disabled and lm accept,master (I didn't have the master).
This still didn't work for me. I still come up in boot mode only. I am currently using 2.6.9-r10 (gentoo-sources). Is this what you are using? I am also using 2.19 of bluez-utils.
Thanks for the suggestions. |
|
| Back to top |
|
|
Loial
n00b
Joined: 24 Mar 2003
Posts: 29
|
| Posted: Fri Sep 09, 2005 9:23 pm Post subject: |
|
|
the master isn't needed, it can be used to allow other machines to make network connections to your pc over bluetooth...I wanted to play with this, but it does nothing for your keyboard/mouse
i'm using 2.6.12-gentoo-r10, the latest stable for x86. I did apply the bluetooth patch from http://www.bluez.org/patches.html But 2.6.9 should work just fine, I've used it successfully also. That was also with the patch from bluez.org. Unfortunately on bluez.org the older 2.6 patches are hidden. Just edit the URL for the latest 2.6 patch and make it 2.6.12-mh3 or whatever you want
I'm using bluez-utils-2.19 and bluez-libs-2.19.
I'm not sure what can fix it. Maybe you have not compiled your kernel with the right config. Here is part of my config:
| Code: | # grep -i bt .config
CONFIG_BT=m
CONFIG_BT_L2CAP=m
CONFIG_BT_SCO=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
# CONFIG_BT_BNEP_MC_FILTER is not set
# CONFIG_BT_BNEP_PROTO_FILTER is not set
CONFIG_BT_HIDP=m
CONFIG_BT_HCIUSB=m
CONFIG_BT_HCIUSB_SCO=y
CONFIG_BT_HCIUART=m
# CONFIG_BT_HCIUART_H4 is not set
# CONFIG_BT_HCIUART_BCSP is not set
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIVHCI=m
CONFIG_VIDEO_BT848=m
CONFIG_VIDEO_BTCX=m
# CONFIG_SND_BT87X is not set
# CONFIG_USB_KBTAB is not set
|
I autoload usbhid upon boot (add usbhid to /etc/modules.autoload, which points to /etc/modules.autoload.d/kernel-2.6 )
Please tell me if this changed anything for you. |
|
| Back to top |
|
|
javac16
Tux's lil' helper
Joined: 10 Aug 2003
Posts: 111
|
| Posted: Fri Sep 09, 2005 9:35 pm Post subject: |
|
|
| What a horrible mis-type by myself - I meant I am using 2.6.12-r10 (I was thinking 2.6.9 because that is what the tutorial states to use), I haven't applied the patch on bluez yet, so I will try that when I get home later tonight. I will also check my config (which I am 98% sure is correct -- I've definitely read it over enough times) and see if autoloading the one module helps. I will report back after trying these things out. Thanks again! |
|
| Back to top |
|
|
javac16
Tux's lil' helper
Joined: 10 Aug 2003
Posts: 111
|
| Posted: Sat Sep 10, 2005 1:18 am Post subject: |
|
|
Loial --THANK YOU!
I found the patches on the bluez website by changing the url like you suggested and was able to get the mh3 patch for 2.6.12. Once I recompiled the kernel and what not I am up and running!
| Code: |
00:07:61:24:2E:0F Logitech Bluetooth Mediapad [046d:b3e1] connected
00:07:61:24:0B:EC Logitech Bluetooth Keyboard [046d:b303] connected
00:07:61:23:CE:A7 Logitech Bluetooth Mouse [046d:b001] connected
|
Thanks again, you really helped me out. |
|
| Back to top |
|
|
trevorj
n00b
Joined: 13 May 2003
Posts: 68
|
| Posted: Sat Oct 22, 2005 4:08 am Post subject: |
|
|
I just got a Logitech DiNovo Media Desktop Laser. Difference is you get a bluetooth MX1000 laser mouse, a usb 2.0 usb bluetooth dongle, and the mouse charger is used only for well... charging
It works fine in HID mode, but it's a new dongle not yet recognized by bluez, so I couldn't turn it into an HCI device. I had to hack hid2hci as well as the kernel's hci_usb driver to include the new dongle's id.
This is ONLY for the Logitech DiNovo Media Desktop Laser !
I'll have to send a post with the patch to the bluez mailing list.. It's just a couple one-liners though.
| Code: | # Kernel patch
--- drivers/bluetooth/hci_usb.orig 2005-10-21 23:37:25.000000000 -0400
+++ drivers/bluetooth/hci_usb.c 2005-10-21 22:11:02.000000000 -0400
@@ -119,6 +119,9 @@
/* Kensington Bluetooth USB adapter */
{ USB_DEVICE(0x047d, 0x105d), .driver_info = HCI_RESET },
+ /* Logitech DiNovo Media Desktop Laser Transceiver for Bluetooth 2.0 */
+ { USB_DEVICE(0x046d, 0xc709), .driver_info = HCI_RESET },
+
/* ISSC Bluetooth Adapter v3.1 */
{ USB_DEVICE(0x1131, 0x1001), .driver_info = HCI_RESET }, |
| Code: | # bluez-utils patch against CVS ( Oct 21 '05 )
--- tools/hid2hci.c.orig 2005-10-21 23:40:20.000000000 -0400
+++ tools/hid2hci.c 2005-10-21 23:52:49.000000000 -0400
@@ -226,6 +226,7 @@
{ HCI, 0x046d, 0xc703, switch_logitech },
{ HCI, 0x046d, 0xc704, switch_logitech },
{ HCI, 0x046d, 0xc705, switch_logitech },
+ { HCI, 0x046d, 0x0b02, switch_logitech },
{ -1 }
}; |
_________________
\\ trevorj |
|
| Back to top |
|
|
mgorbach
n00b
Joined: 03 Aug 2005
Posts: 51
|
| Posted: Tue Nov 29, 2005 3:12 am Post subject: |
|
|
Can someone help me out? When i enable bluetooth on my dinovo ... the fn keys dont work anymore!
I cant toggle the f-lock?
What can i do to fix this? |
|
| Back to top |
|
|
chojin
n00b
Joined: 26 Jun 2005
Posts: 42
|
| Posted: Sat Jan 07, 2006 11:53 am Post subject: |
|
|
| trevorj wrote: | I just got a Logitech DiNovo Media Desktop Laser. Difference is you get a bluetooth MX1000 laser mouse, a usb 2.0 usb bluetooth dongle, and the mouse charger is used only for well... charging
It works fine in HID mode, but it's a new dongle not yet recognized by bluez, so I couldn't turn it into an HCI device. I had to hack hid2hci as well as the kernel's hci_usb driver to include the new dongle's id.
This is ONLY for the Logitech DiNovo Media Desktop Laser !
I'll have to send a post with the patch to the bluez mailing list.. It's just a couple one-liners though.
| Code: | # Kernel patch
--- drivers/bluetooth/hci_usb.orig 2005-10-21 23:37:25.000000000 -0400
+++ drivers/bluetooth/hci_usb.c 2005-10-21 22:11:02.000000000 -0400
@@ -119,6 +119,9 @@
/* Kensington Bluetooth USB adapter */
{ USB_DEVICE(0x047d, 0x105d), .driver_info = HCI_RESET },
+ /* Logitech DiNovo Media Desktop Laser Transceiver for Bluetooth 2.0 */
+ { USB_DEVICE(0x046d, 0xc709), .driver_info = HCI_RESET },
+
/* ISSC Bluetooth Adapter v3.1 */
{ USB_DEVICE(0x1131, 0x1001), .driver_info = HCI_RESET }, |
| Code: | # bluez-utils patch against CVS ( Oct 21 '05 )
--- tools/hid2hci.c.orig 2005-10-21 23:40:20.000000000 -0400
+++ tools/hid2hci.c 2005-10-21 23:52:49.000000000 -0400
@@ -226,6 +226,7 @@
{ HCI, 0x046d, 0xc703, switch_logitech },
{ HCI, 0x046d, 0xc704, switch_logitech },
{ HCI, 0x046d, 0xc705, switch_logitech },
+ { HCI, 0x046d, 0x0b02, switch_logitech },
{ -1 }
}; |
|
I also recently bought a diNovo Media Desktop Laser with the laser mouse, the mini USB bluetooth receiver and the charging-only cradle.
I applied the patches to both the kernel and the bluez-utils package (using a portage overlay). Now i do get a result with hid2hci. But thats everything:
| Code: | # hid2hci
Switching device 046d:0b02 to HCI mode was successful |
So this looks good, but I thought it to be strange that I didn't notice the keyboard or mouse reconnecting.. so I checked if the hci device really came up, but it seems that it didn't:
| Code: | # udevinfo -ap /sys/class/bluetooth/hci0
couldn't get the class device
# hcitool inq
Inquiring ...
Inquiry failed.: No such device
# hcitool scan
Device is not available: No such device
# hcitool dev
Devices:
|
This is what I get with lsusb
| Code: | # lsusb
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 008: ID 046d:c70c Logitech, Inc.
Bus 002 Device 007: ID 046d:c70b Logitech, Inc.
Bus 002 Device 006: ID 046d:0b02 Logitech, Inc.
Bus 002 Device 002: ID ffa1:0201
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
|
I also don't find the device 0x046d, 0xc709 mentioned in the kernel patch.. maybe my version has another id? How can I find this id? is it one of the above (lsusb output) ?
some more info:
| Code: | # cat /proc/bus/usb/devices
T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 3
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.14-gentoo-r5-mh2 ohci_hcd
S: Product=OHCI Host Controller
S: SerialNumber=0000:00:02.1
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 3
B: Alloc= 6/900 us ( 1%), #Int= 4, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.14-gentoo-r5-mh2 ohci_hcd
S: Product=OHCI Host Controller
S: SerialNumber=0000:00:02.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 4
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=ffa1 ProdID=0201 Rev= 1.10
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms
T: Bus=02 Lev=02 Prnt=02 Port=03 Cnt=01 Dev#= 6 Spd=12 MxCh= 3
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=046d ProdID=0b02 Rev=40.00
S: Manufacturer=Logitech
S: Product=Logitech BT Mini-Receiver
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms
T: Bus=02 Lev=03 Prnt=06 Port=01 Cnt=01 Dev#= 7 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=046d ProdID=c70b Rev=40.00
S: Manufacturer=Logitech
S: Product=Logitech BT Mini-Receiver
S: SerialNumber=00076141F580
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 98mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms
T: Bus=02 Lev=03 Prnt=06 Port=02 Cnt=02 Dev#= 8 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=046d ProdID=c70c Rev=40.00
S: Manufacturer=Logitech
S: Product=Logitech BT Mini-Receiver
S: SerialNumber=00076141F580
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 98mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=5ms
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.14-gentoo-r5-mh2 ehci_hcd
S: Product=EHCI Host Controller
S: SerialNumber=0000:00:02.2
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms
|
Anyone has an idea why this isn't working? |
|
| Back to top |
|
|
davez
n00b
Joined: 21 Mar 2004
Posts: 28
Location: Switzerland
|
| Posted: Thu Jan 19, 2006 3:04 pm Post subject: |
|
|
I received a diNovo Laser as a replacement for a defective diNovo "Standard" yesterday... Now I have excactly the same problem like chojin I patched kernel + bluez-utils as described from trevorj.. But the USB dongle just doesn't get recognized by hcitool and co.
Are there any solutions? |
|
| Back to top |
|
|
sibov
Tux's lil' helper
Joined: 09 Feb 2004
Posts: 147
Location: Germany
|
| Posted: Thu Jan 26, 2006 11:48 pm Post subject: |
|
|
I'm currently on kernel 2.6.15-gentoo-r1 but the good old
patch-2.6.14-mh2.gz seems to fail on that kernel source.
Does anybody have a clue what's going on 
My Dinovo devices are currently only in boot-protocol mode 
Regards,
SiboV
_________________
Gentoo 2.6.17-gentoo-r5 with dmraid Raid0 Dualboot
AMD64 X2 3800+, 4x512MB DDR PC3200Pro Corsair Geforce EN6600GT silencer @ 256MB
4x250GB SATAII Samsung SP120, Asus A8N Premium, Plextor PX712SA DVDRW
Logitech Dinovo, SB Audigy4 |
|
| Back to top |
|
|
javac16
Tux's lil' helper
Joined: 10 Aug 2003
Posts: 111
|
| Posted: Mon Feb 13, 2006 3:08 pm Post subject: |
|
|
| I haven't upgreaded to 2.6.15 yet, but I noticed today that bluez.org has put a patch up on their site for the 2.6.15 kernel. Are you using that patch? |
|
| Back to top |
|
|
sibov
Tux's lil' helper
Joined: 09 Feb 2004
Posts: 147
Location: Germany
|
| Posted: Tue Feb 14, 2006 10:51 am Post subject: |
|
|
 thx i'll try it out.
_________________
Gentoo 2.6.17-gentoo-r5 with dmraid Raid0 Dualboot
AMD64 X2 3800+, 4x512MB DDR PC3200Pro Corsair Geforce EN6600GT silencer @ 256MB
4x250GB SATAII Samsung SP120, Asus A8N Premium, Plextor PX712SA DVDRW
Logitech Dinovo, SB Audigy4 |
|
| Back to top |
|
|
javac16
Tux's lil' helper
Joined: 10 Aug 2003
Posts: 111
|
| Posted: Tue Feb 14, 2006 2:07 pm Post subject: |
|
|
| I'm really interested to know if it works out, so post your results if you get a chance. Whether the dinovo works or not on the new kernel is the only thing keeping me from upgrading (that and I haven't had the time). |
|
| Back to top |
|
|
sibov
Tux's lil' helper
Joined: 09 Feb 2004
Posts: 147
Location: Germany
|
| Posted: Wed Feb 15, 2006 9:07 pm Post subject: |
|
|
| javac16 wrote: | | I'm really interested to know if it works out, so post your results if you get a chance. Whether the dinovo works or not on the new kernel is the only thing keeping me from upgrading (that and I haven't had the time). |
Hi javac16,
today i tried the latest bluez kernel patch (3 or more times).
Every time the bootprocess is going to make the hid2hci command i get a kernel panic.
I think i'll have to wait for a second release of the bluez patch.
Kind regards,
Sibov
_________________
Gentoo 2.6.17-gentoo-r5 with dmraid Raid0 Dualboot
AMD64 X2 3800+, 4x512MB DDR PC3200Pro Corsair Geforce EN6600GT silencer @ 256MB
4x250GB SATAII Samsung SP120, Asus A8N Premium, Plextor PX712SA DVDRW
Logitech Dinovo, SB Audigy4 |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Documentation, Tips & Tricks
