[Solved] Bluetooth service restart required after (re)boot

.:B:. · 2011-07-14 13:57:47

I got a new laptop yesterday and set up my bluetooth keyboard and mouse with it. Strangely enough both devices do not get any connection whatsoever, unless I restart the bluetooth service through rc.local (which, annoyingly enough, will also get me a QWERTY layout instead of AZERTY in the login manager, but that's less of a problem).

I was wondering if there's a fix for this? Google isn't really helping... Since I had this issue with my previous laptop as well, it looks likes something more systematic. Bluetooth configuration was done from scratch (and through blueman, for what it's worth). Since a restart of the bluetooth service gets both devices connected, I'd guess the configuration an sich is correct (once it's up, it stays up).

Last edited by .:B:. (2011-07-15 16:34:38)

Inxsible · 2011-07-14 14:30:54

I do not use bluetooth, but according to this thread,

https://bbs.archlinux.org/viewtopic.php?id=120715

zenlord wrote:

/etc/bluetooth/main.conf: InitiallyPowered = false

Maybe setting that to true will start up your bluetooth at all times.

.:B:. · 2011-07-14 17:29:33

Thanks. Turns out it's already set to "true" by default though :-/

It seems the connection 'survives' between reboots but a cold boot means I need to restart the bluetooth service before the devices can connect.

Inxsible · 2011-07-14 18:10:25

and obviously you already have the bluetooth daemon in the DAEMONS array ....

.:B:. · 2011-07-14 19:29:15

Yeah .

I can only really test whether changing those InitallyPowered values works on cold boots, so I'll report back tomorrow.

Inxsible · 2011-07-14 19:33:17

That's all I got. Sorry couldn't be of more help Stijn.

.:B:. · 2011-07-14 21:53:12

No problems, you've been really helpful (I hadn't thought about the config files in /etc/bluetooth at first).

ngoonee · 2011-07-15 01:42:41

What's the order like in your DAEMONS array? Maybe something else is needed before bluetooth starts up. You could put it right at the end and see if it helps (mine is almost the last one).

Alternatively, perhaps your hardware simply takes a bit longer to initialize? Behaving differently on reboots and cold boots indicate more of a hardware issue (to me).

.:B:. · 2011-07-15 14:33:38

This is how my rc.conf looks:

$ grep ^DAEMONS /etc/rc.conf
DAEMONS=(hwclock syslog-ng @net-profiles @crond @hal @openntpd @cpufreq @bluetooth @acpid @alsa @cupsd)

Maybe the backgrounding isn't such a brilliant idea (I don't know). I doubt the hardware needs more time, it usually does take a few seconds to connect devices, but I can keep jamming on my keyboard or torturing my mouse for half a minute in the login screen, and no response whatsoever.

Edit: I checked the wiki, apparently bluetooth should be started after dbus, so I'm de-backgrounding the hal service to see what that is going to do (and taking out hwclock while I'm at it, since rc.conf tells me that kind of conflicts with openntpd ).

I'll report back .

Last edited by .:B:. (2011-07-15 14:53:08)

.:B:. · 2011-07-15 16:34:22

Well certainly feels fixed now. Thanks guys, and onto the next issue .

Arch Linux

#1 2011-07-14 13:57:47

[Solved] Bluetooth service restart required after (re)boot

#2 2011-07-14 14:30:54

Re: [Solved] Bluetooth service restart required after (re)boot

#3 2011-07-14 17:29:33

Re: [Solved] Bluetooth service restart required after (re)boot

#4 2011-07-14 18:10:25

Re: [Solved] Bluetooth service restart required after (re)boot

#5 2011-07-14 19:29:15

Re: [Solved] Bluetooth service restart required after (re)boot

#6 2011-07-14 19:33:17

Re: [Solved] Bluetooth service restart required after (re)boot

#7 2011-07-14 21:53:12

Re: [Solved] Bluetooth service restart required after (re)boot

#8 2011-07-15 01:42:41

Re: [Solved] Bluetooth service restart required after (re)boot

#9 2011-07-15 14:33:38

Re: [Solved] Bluetooth service restart required after (re)boot

#10 2011-07-15 16:34:22

Re: [Solved] Bluetooth service restart required after (re)boot

Board footer