Logitech MX5000 blue tooth Keyboard and Mouse solved

Questions about hardware, drivers and peripherals
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
Kiwi-Hawk

Logitech MX5000 blue tooth Keyboard and Mouse solved

Post by Kiwi-Hawk »

Hi

I have a Logitech MX5000 Keyboard & Mouse thats dead in the water

on first boot the blue tooth icon show then despairs,..

From what I'm reading Blue tooth is all sorted and should run by default under Elyssa 5
I'm also seeing that the Logitech stuff can be a dog to get going

I want to use this system as a Media center and it would be much safer both for hardware and people not
to have cables across the lounge floor .

I have had no luck so far so any hep would be much appreciated ,.. thanks in advance
Edit:

Did a reboot and got mouse showing as an MX1000, tried to connect and got his error:

Couldn't display "obex://[00:07:61:98:c1:a2]/"

error: host down
Please select another viewer and try again


Cheers
Kiwi-Hawk
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Husse

Re: Logitech MX5000 blue tooth Keyboard and Mouse

Post by Husse »

This is what i found
Preferences > Bluetooth
Then go to the Services tab and make sure input service is checked. Then highlight it with a single click and select add on the bottom. Make the devices visible
I have no Bluetooth devices so I can't check this at all
Kiwi-Hawk

Re: Logitech MX5000 blue tooth Keyboard and Mouse

Post by Kiwi-Hawk »

Hi

I have done just that and it finds my phone and (at this point) has my Keyboard and as you say I highlight it
and select connect but he response is as in my first post:

Message is:
Couldn't display "obex://[00:07:61:98:ec:0c]/"

error: host down
Please select another viewer and try again


in dialog box and has an "OK" button thats all
I'm thinking that this [00:07:61:98:ec:0c] is the mac address of the device
the address from the last install in my first post was the mouse showing and not the keyboard

It's strange,.. I had a look at Mythbuntu and the blue tooth worked fine as it did with Ear-Media. Because it works with Myth
I'm thinking it would work with Mint as they'er both the same base OS as I understand it

Cheers
Kiwi-Hawk
Husse

Re: Logitech MX5000 blue tooth Keyboard and Mouse

Post by Husse »

I have limited time right now but I'll see if I find something
In the meantime google

Code: Select all

obex error: host down
Please select another viewer and try again
There may be an answer that suits you
Husse

Re: Logitech MX5000 blue tooth Keyboard and Mouse

Post by Husse »

I see you've found this
http://ubuntuforums.org/showthread.php?t=325455&page=4
Perhaps this is useful
http://ubuntuforums.org/archive/index.php/t-594624.html
That's about it - I found it while googling obex error: host down logitech keyboard
Kiwi-Hawk

Re: Logitech MX5000 blue tooth Keyboard and Mouse

Post by Kiwi-Hawk »

Hi

everything I'm reading is saying obex is for file transfer and that a mouse or keyboard does not support it.

if this is true then bluetooth is not defining the device well enough,.. this means to me that it's treating a mouse and keyboard the same
as a cellphone

I have no idea where I go from here,.. last time I followed a howto off Unbuntu it had me edit the xorg.conf to give full function to
mouse and it broke my X res si I don't wish to go there and have to reinstall again

Cheers
Kiwi-Hawk
Husse

Re: Logitech MX5000 blue tooth Keyboard and Mouse

Post by Husse »

I'm sorry I don't know either - it seems that it works generally as there are few questions about it
Husse

Re: Logitech MX5000 blue tooth Keyboard and Mouse

Post by Husse »

I hope I understand you right - you have solved this :)
electricuniverse

Re: Logitech MX5000 blue tooth Keyboard and Mouse

Post by electricuniverse »

Same problem here too with the laptop (acer ferrari-BTmouse).
Thanks anyway.
Kiwi-Hawk

Re: Logitech MX5000 blue tooth Keyboard and Mouse

Post by Kiwi-Hawk »

Husse wrote:I hope I understand you right - you have solved this :)
Yes I posted my config file well two of them in my xorg.conf help thread unfortunately this problem and the
xorg.conf problem seed to run into each other

http://www.linuxmint.com/forum/viewtopi ... 59&t=15203

I did however cheat LOL I copied the /etc/bluetooth directory and the executable bluetooth file from another distro (That I think maybe not right to name here not sure about rules etc and don't wish to start anything or upset anybody, I'm not a programmer and jus need it working, so did it the best way I know how) where it worked from the live CD right off. Used this thread as a walkthrough and guide as to what to look for and what to change. I guess you could call this the ole Kiwi no;8 wire fix,, may need to check New Zealand history if you not sure what I mean lol. buttom line Kiwi patch job

http://ubuntuforums.org/showthread.php? ... ech+MX5000

this is the bluetooth file if its a help:
# Defaults for bluez-utils

# This file supersedes /etc/default/bluez-pan. If
# that exists on your system, you should use this
# file instead and remove the old one. Until you
# do so, the contents of this file will be ignored.

# start bluetooth on boot?
# compatibility note: If this variable is not found bluetooth will
# start
# BLUETOOTH_ENABLED=1

# This setting will switch HID devices (e.g mouse/keyboad) to HCI mode, that is
# you will have bluetooth functionality from your dongle instead of only HID.
# Note that not every bluetooth dongle is capable of switching back to HID
# mode, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355497
HID2HCI_ENABLED=1

############ HIDD
#
# HID daemon
HIDD_ENABLED=1
HIDD_OPTIONS="--master --server"
# to make hidd always use a particular interface, use something
# like this, substituting the bdaddr of the interface:
# HIDD_OPTIONS="-i AA:BB:CC:DD:EE:FF --server"
#
# remove '--master' if you're having trouble working with Ericsson
# T630 phones with hidd operational at the same time.

############ COMPATIBILITY WITH OLD BLUEZ-PAN
# Compatibility: if old PAN config exists, use it
# rather than this file.
if test -f /etc/default/bluez-pan; then
. /etc/default/bluez-pan
return
fi
############

############ DUND
#
# Run dund -- this allows ppp logins. 1 for enabled, 0 for disabled.
DUND_ENABLED=0

# Arguments to dund: defaults to acting as a server
DUND_OPTIONS="--listen --persist"

# Run dund --help to see the full array of options.
# Here are some examples:
#
# Connect to any nearby host offering access
# DUND_OPTIONS="--search"
#
# Connect to host 00:11:22:33:44:55
# DUND_OPTIONS="--connect 00:11:22:33:44:55"
#
# Listen on channel 3
# DUND_OPTIONS="--listen --channel 3"

# Special consideration is needed for certain devices. Microsoft
# users see the --msdun option. Ericsson P800 users will need to
# listen on channel 3 and also run 'sdptool add --channel=3 SP'

############ PAND
#
# Run pand -- ethernet: creates new network interfaces bnep<N>
# that can be configured in /etc/network/interfaces
# set to 1 for enabled, 0 for disabled
PAND_ENABLED=0

# Arguments to pand
# Read the PAN howto for ways to set this up
# http://bluez.sourceforge.net/contrib/HOWTO-PAN
# in later versions of pand it used to execute /etc/bluetooth/pan/dev-up
# automatically, now you will need to use the --devup/--devdown options. See
# the pand manpage for more informations
PAND_OPTIONS=""

# example pand lines
#
# Act as the controller of an ad-hoc network
# PAND_OPTIONS="--listen --role GN"
#
# Act as a network access point: routes to other networks
# PAND_OPTIONS="--listen --role NAP"
#
# Act as a client of an ad-hoc controller with number 00:11:22:33:44:55
# PAND_OPTIONS="--role PANU --connect 00:11:22:33:44:55"
#
# Connect to any nearby network controller (access point or ad-hoc)
# PAND_OPTIONS="--role PANU --search"

############ SDPTOOL
# this variable controls the options passed to sdptool on boot, useful if you
# need to setup sdpd on boot.
# options are ;-separated, i.e. for every ; an sdptool instance will be
# launched
#
# examples:
# SDPTOOL_OPTIONS="add --channel=3 SP" # ericsson P800 serial profile
# SDPTOOL_OPTIONS="add --channel=8 OPUSH ; add --channel=9 FTRN" # motorola
and my xorg.conf:
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Emulate3Buttons" "false"
Option "Buttons" "7"
Option "ButtonMapping" "1 2 3 6 7"
Option "ZAxisMapping" "4 5"
EndSection

Section "Device"
Identifier "Configured Video Device"
Driver "nvidia"
Option "NoLogo" "True"
EndSection

Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
Defaultdepth 24
EndSection

Section "ServerLayout"
Identifier "Default Layout"
screen "Default Screen"
EndSection
Section "Module"
Load "glx"
EndSection
and my hcid.conf file
Tha I forgot to put in yesterday
#
# HCI daemon configuration file.
#

# 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;

# Default PIN code for incoming connections
passkey "1234";
}

# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "%h-%d";

# Local device class
class 0x000100;

# Default packet type
#pkt_type DH1,DM1,HV1;

# Inquiry and Page scan
iscan enable; pscan enable;
discovto 0;

# 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;

# 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;
}
device <Mac-address> {
name "Logitech MX5000 Keyboard";
auth enable;
encrypt enable;
}
device <Mac_address> {
name "Logitech MX1000 mouse"
}
Don't know if they help others with Blutooth MX5000 or not
Sorry for double post I should have put this here anyway

Cheers
Kiwi-Hwak
Kiwi-Hawk

Re: Logitech MX5000 blue tooth Keyboard and Mouse

Post by Kiwi-Hawk »

Hi

If it the general rule for your Forum to do so I think we can mark this solved

Cheers
Kiwi-Hawk

PS I thank everybody that gave time and energy to helping me with this
Locked

Return to “Hardware Support”