Ubuntu
bluez package

Logitech Bluetooth dongle does not work on startup

Asked by Deon Korb

Hi,

I own a Logitech diNovo Laser Bluetooth keyboard and mouse. I got it to work in Bluetooth mode perfectly, but it does not work at start up.

I had to edit the /etc/udev/rules.d/97-bluetooth-dih2hci rules to

The dongle has two modes:
1. HID mode (default, allows the set to be used as a normal keyboard and mouse pre boot)
2. Bluetooth mode (appears as a Bluetooth adapter and pairs to the keyboard and mouse)

As I understood, once the dongle is in Bluetooth mode, in should stay there. This does not seem to be the case. Everything keeps working after a restart, but after a shut down and start up it doesn't. Bluetooth does not appear and only the mouse works.

The work around is to remove the dongle, press the connect button and re-insert the dongle whilst still pressing the connect button. Ubuntu picks up the dongle and reconnects to the previously paired keyboard and mouse.

This does not help the adoption of Ubuntu in my household.

Is there a way to make Ubuntu remember that my dongle must be a Bluetooth adapter, so that it all work at start up as was the case before shut down?

Your help will be much appreciated.

Regards,
Deon

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu bluez Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Deon Korb (deon-korb) said : 		#1

The bug I linked seems related.

As stated above, everything works fine after a reconnect.

All I want is that it works in Bluetooth mode on start up prior to login (as the keyboard is required for login)

Thanks,
Deon

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#2

Can you give the output of:

lsb_release -a; uname -a; lsmod

Thanks

Revision history for this message
Deon Korb (deon-korb) said : 		#3

As requested:

Output of lsb_release -a; uname -a; lsmod is as follows (this was run after I reinserted the dongle with the connect button)

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.1 LTS
Release: 12.04
Codename: precise
Linux Desktop 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux
Module Size Used by
nls_utf8 12493 1
isofs 39553 1
hidp 22165 2
btusb 17912 6
vesafb 13516 1
rfcomm 38139 12
parport_pc 32114 0
bnep 17830 2
ppdev 12849 0
bluetooth 158438 32 hidp,btusb,rfcomm,bnep
snd_hda_codec_hdmi 31775 4
snd_seq_midi 13132 0
snd_rawmidi 25424 1 snd_seq_midi
nvidia 10971098 50
snd_seq_midi_event 14475 1 snd_seq_midi
snd_seq 51567 2 snd_seq_midi,snd_seq_midi_event
snd_hda_codec_idt 60251 1
snd_hda_intel 32765 5
snd_hda_codec 109562 3 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel
snd_hwdep 13276 1 snd_hda_codec
joydev 17393 0
psmouse 86421 0
serio_raw 13027 0
snd_pcm 80845 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_timer 28931 2 snd_seq,snd_pcm
snd_seq_device 14172 3 snd_seq_midi,snd_rawmidi,snd_seq
mac_hid 13077 0
snd 62064 20 snd_hda_codec_hdmi,snd_rawmidi,snd_seq,snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer,snd_seq_device
mei 36570 0
soundcore 14635 1 snd
snd_page_alloc 14108 2 snd_hda_intel,snd_pcm
lp 17455 0
parport 40930 3 parport_pc,ppdev,lp
usbhid 41906 0
hid 77367 2 hidp,usbhid
firewire_ohci 40172 0
firewire_core 56906 1 firewire_ohci
crc_itu_t 12627 1 firewire_core
floppy 60310 0
e1000e 140005 0
pata_marvell 12763 0

This is the output before (with the keyboard in a non working state):

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.1 LTS
Release: 12.04
Codename: precise
Linux Desktop 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux
Module Size Used by
vesafb 13516 1
snd_hda_codec_hdmi 31775 4
rfcomm 38139 0
bnep 17830 2
bluetooth 158438 10 rfcomm,bnep
parport_pc 32114 0
ppdev 12849 0
snd_hda_codec_idt 60251 1
snd_hda_intel 32765 5
snd_hda_codec 109562 3 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel
snd_hwdep 13276 1 snd_hda_codec
nvidia 10971098 30
snd_pcm 80845 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_seq_midi 13132 0
snd_rawmidi 25424 1 snd_seq_midi
snd_seq_midi_event 14475 1 snd_seq_midi
snd_seq 51567 2 snd_seq_midi,snd_seq_midi_event
snd_timer 28931 2 snd_pcm,snd_seq
psmouse 86421 0
serio_raw 13027 0
snd_seq_device 14172 3 snd_seq_midi,snd_rawmidi,snd_seq
joydev 17393 0
snd 62064 20 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
mac_hid 13077 0
soundcore 14635 1 snd
snd_page_alloc 14108 2 snd_hda_intel,snd_pcm
lp 17455 0
mei 36570 0
parport 40930 3 parport_pc,ppdev,lp
usbhid 41906 0
hid 77367 1 usbhid
firewire_ohci 40172 0
firewire_core 56906 1 firewire_ohci
e1000e 140005 0
floppy 60310 0
crc_itu_t 12627 1 firewire_core
pata_marvell 12763 0

Hope this helps. Let me know what else I can do.

Thanks for the speedy response.

Cheers,
Deon

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#4

Run:

gksudo gedit /etc/rc.local

above the 'exit 0' line add:

modprobe -r btusb
sleep 2
modprobe btusb

Save the new file, reboot to test

Revision history for this message
Deon Korb (deon-korb) said : 		#5

Hi,

I did this and it seemed to work after a restart.

I then tested it after a shut down and it does not work again.

I gather from the code that on start up, the script disables the Bluetooth USB adapter and re-enables it after 2 seconds.

What is different after a shut down?

Revision history for this message
Launchpad Janitor (janitor) said : 		#6

This question was expired because it remained in the 'Open' state without activity for the last 15 days.