Forcing Bluetooth on at start-up.

Well it sort of works… on start-up,


It flashes on and off once, and then once I log in as myself, it turns on… so I need to tweak something, somewhere… ::slight_smile:

You’ve lost me ???

Is it honestly that difficult to understand? It toggles itself on and off for a split second at the Ubuntu splash screen, with the script and when I log it, it turns itself automatically on… I don’t understand how the concept is hard to understand? ???

OK, I’ll elaborate :slight_smile:

a) how does your picture of the Ubuntu loading screen help anyone understand that ?
b) so it’s fixed and doesn’t require “tweaking” ?

If it’s working … why does it need “tweaking” ? ← THIS is the bit you haven’t explained

So YES, I’d say it needs some explaining :o

Δεν καταλαβαίνω

Ok, I’ll help you “understand” :wink:

It needs tweaking as I want it to come on and stay on AT the Ubuntu splash screen. Like I said, it comes on for a brief second whilst AT the UBUNTU SPLASH SCREEN. Still with me? Ok, good.

In order for it to stay on, it (the script you wrote which now resides in rc.local) needs “some tweaking”, which help enable me to get the desired result I’m looking for.

This way I can use bluetooth devices at start to control the laptop, coughAppleMagicMousecough. I’m picking such devices up on Tuesday, next week.

Surely that wasn’t TOO complicated to understand?

But that’s an impossibility … how are you to use Bluetooth until the drivers and service are loaded and the “pairing” negotiated, Bluetooth requires that “authenticated” connections are negotiated … this can only occur in software, and I doubt will EVER be part of a system BIOS

What you’re expecting would be analogous to a wireless connection being negotiated BEFORE Network Manager is loaded … I would have thought you’d understand that ?

Let me know if you need this explaining … Smart Alec :wink:

Oh god, you don’t get me…

When the devices have already been paired, they’d automatically connect to the laptop, so the authentication would already be there. As it would have been setup whilst the machine was running. Like you would normally. The “cool” bit kicks in, AFTER you’ve negotiated the connections. So when you restart, the laptop already knows what authenticates what.

The drivers are loaded whilst the the Ubuntu splash screen, otherwise it wouldn’t come on.

So yes, smart alec I am… :stuck_out_tongue:

Wireless is a whole different story, but we already know that. So let’s not go down there.

I’ll give you the benefit of the doubt that you’re not thinking this through …

Wireless is NOT a whole other question … as with Network Manger, a Bluetooth device CANNOT be “paired” until the software that authenticates the “pairing” is loaded … the devices themselves do NOT do the pairing, as they have no way of remembering a “pairing” … in EXACTLY the same way a wireless device cant authenticate with the router UNTIL Network Manager is loaded, then Network Manager loads the saved profile for the connection.

the flashing of the light you are seeing early in the boot process is the bluetooth device being initialised, and the drivers loaded … then it has to wait for the bluetooth service to be started for the “pairing”/authentication/connection to take place.

Bluetooth is just a wireless protocol like any other, and requires software management of the connections.

Thanks for calling me “God” by the way … but a little over the top, and not necessary :wink:

If you’ve already ordered the hardware, it probably makes more sense to try sort this when it arrives … it may even turn out that the bluetooth light only comes on when something connects or there may be a delay … point is we have no way of knowing ATM ???

Links for future reference:

From the look of those pages, maybe we need to work out why /etc/init.d/bluetooth doesn’t appear to be starting bluetooth properly (or at all).


Bear in mind it’s never going to be available for things as early as the GRUB menu … but we may (with luck) be able to get it to kick it before the login screen … worst case scenario, enable auto login, granted not ideal, but an option.