Any chance to get my Logitech Bluetooth hub working?

GeeZuZz · 07-21-2004, 11:55 AM

After searching the internet i have yet to find anyone telling that they got their Logitech bluetooth hub working...

I have a Logitech DiNovo keyboard/mouse pack, and the bluetooth reciever is also a bluetooth hub for use with other devices like cell phones and PDA's.

And thats the problem, i want to be able to use it to transfer files between my PC and phone and PDA. I'm running SuSE 9.1, and have installed all bluez- packages, and when I run kbluetoothd a grey icon appears in bottom corner, indicating that theres no connection. I don't think it have discovered my BT device.

Does someone know how to fix this?

GeeZuZz · 07-29-2004, 06:33 PM

So its not?

Not very surpricing actually...

twan · 08-22-2004, 05:54 PM

Hi,

Since kernel 2.6.4, bluetooth support has been updated, and it was reported that the dinovo worked perfect on a fedora core 1 setup, with kernel 2.6.4 or higher.

I also have the dinovo, yet, i have to check it, if it works. Stupid logitech for not releasing linux drivers for their flagship keyboard/mouse combo..

anyway

you should compile bluetooth support in your kernel, and it should work fine..

GeeZuZz · 08-22-2004, 05:57 PM

Keyboard works fine, since it doesn't need a driver (it works in BIOS too). The problem is to use the bluetooth hub as a "bluetooh dongle" to connect other devices.

dePOLL · 09-04-2004, 09:38 AM

I own the Logitech Elite Duo and also have problems using the hub under Linux. My kernel configuration:

Code:

Bluetooth subsystem support -> y
  L2CAP protocol support -> y
  SCO links support -> m
  RFCOMM protocol support -> y
    RFCOMM TTY support -> n
  BNEP protocol support -> m
    Multicast filter support -> n
    Protocol filter support -> n
  HIDP protocol support -> m

Bluetooth device drivers
  HCI USB driver -> m
  everything else -> n

I downloaded the latest bluez-libs & utils and compiled them. I can start hcid and sdpd without any error messages but hciconfig doesn't show any device neither does kdebluetooth :/

dePOLL · 09-04-2004, 10:53 AM

Alright, guys.. Actually it's pretty easy to get that thing running. The point is that the hub has 2 modes: In the first mode it just acts as an "adaptor" for your mouse and keyboard, in the second mode as a bluetooth hub with all its functionality. The advantage of the first mode is that you don't have to care about pairing PINs and all that stuff, the advantage of the second mode of course is the possibility to connect other devices than mouse and keyboard.

- To switch to the hub mode just run hid2hci. But keep in mind, that this will lead to a disconnection between your mouse and keyboard so you might want to consider plugging in a more conventional keyboard (you know.. with a wire and all that stuff

) for the time being.
- To check whether it really worked check the output of hciconfig. It should be something like

Code:

hci0:   Type: USB
        BD Address: 00:07:61:0D:EA:BC ACL MTU: 192:8  SCO MTU: 64:8
        UP RUNNING PSCAN ISCAN
        RX bytes:542215 acl:35751 sco:0 events:1219 errors:0
        TX bytes:12218 acl:418 sco:0 commands:308 errors:0

- Let's take a look what our host is capable of. Just run sdptool browse FF:FF:FF:00:00:00. If the mighty blue tooth considers you and your computer to be dignified enough there should be a lot of output. Assumed that you already have installed kdebluetooth.
- After those checks resulting in "Aaaaahhh"s and "Ooooohh"s let's do some real magic:
- Press the connect buttons of your mouse and keyboard.
- Hurry and run hcitool scan. Do it within 10 seconds or those devices will destroy themselves!
- As of nowhere 2 magic addresses will appear accompanied by two audacious device names. For instance:

Code:

        00:07:61:0B:94:95       Logitech Elite Keyboard
        00:07:61:17:4E:9B       Logitech MX900 Mouse

- If you are already crying because you just can't grasp the luck you have to use such a wonderful technology, hold on! It gets even better.
- Someday everybody wants to settle down and establish a family. For your computer and input devices this is today. For each (of the.. wait a second.. mouse.. keyboard.. for each of the two!) type in: hidd --connect the_address_from_above.
- Plug the USB and PS/2 cable of the hub into your computer and be awestruck! It works! Let's praise the mighty blue tooth!
- Start kbluetoothd and adore the blue icon in your systray

That's it for today. I'll have to try which pairing capabilities kde-bluetooth has, but anyhow adding

Code:

hid2hci
sdpd
hidd --connect 1
hidd --connect 2

to some startup file (i.e. /etc/rc.d/rc.sysinit) should suffice.

dePOLL · 09-04-2004, 05:28 PM

Umm.. I dunno how to connect mouse&keyboard automatically after a reboot. If I start hid2hci, hcid, sdpd and then hidd they get connected but I lose the hub-functionality. Otherwise I have to search for them first (hcidtool scan) and then add them manually...

Anybody able to help me out with this?

dePOLL · 09-05-2004, 04:38 AM

Quote:

hid2hci
sleep 1
hcid
sdpd
sleep 1
hidd --server

This works perfect as a startup script

Finally.

Bigiron.45 · 05-10-2006, 01:38 AM

I have the MX5000 desktop. None of the above works hid2hci tells me I am a stupid idiot for buying a packaged set... not really it just tells me that there are no devices in hci mode so I do a hid2hci -1 (switches things back) and it tells me there are no devices in hid mode so I really need some help here. AMD_64 running Suse 10.0 bone stock kernel.

thanks for any help you can give

gefunden · 08-11-2006, 04:23 AM

The cvs version of hid2hci now supports mx 5000, submitted the patch myself