Yves-Alexis Perez | 10 Oct 2009 23:53
Picon
Favicon

Re: bluetooth off state not remembered accross reboots?

On sam, 2009-10-10 at 13:49 -0300, Henrique de Moraes Holschuh wrote:
> On Sat, 10 Oct 2009, Yves-Alexis Perez wrote:
> > since some time (I guess 2.6.29 or 2.6.30 kernel), it seems that the
> > bluetooth ???off??? state isn't remembered on my T61. I usually turn
> 
> The driver can remember state, yes. It *might* not work though. And it can
> be overriden by userspace.
> 
> Do note that when thinkpad-acpi switches bluetoot off, it *disappears* from
> the bus (so, lsusb won't find it, etc).
> 
> If bluetooth is still present in the bus, but the bluetooth interface is
> down, then your problem is not related directly or indirectly to
> thinkpad-acpi.

In fact, I check with the bluetooth LED state.
> 
> Now, if the bluetooth state persistence used to work on your thinkpad and it
> doesn't work anymore, then the problem is likely in userspace.

In fact, I watched the LED accross the boot, and it lights on when the
following is displayed:

[   19.441103] Bluetooth: Core ver 2.15
[   19.451982] Bluetooth: HCI device and connection manager initialized
[   19.456402] Bluetooth: HCI socket layer initialized
[   19.497216] Bluetooth: Generic Bluetooth USB driver ver 0.5

So I guess thinkpad-acpi correctly tries to keep bluetooth off, but the
bluetooth module re-enables it for some reason.
(Continue reading)

Henrique de Moraes Holschuh | 11 Oct 2009 14:39
Picon
Favicon

Re: bluetooth off state not remembered accross reboots?

On Sat, 10 Oct 2009, Yves-Alexis Perez wrote:
> On sam, 2009-10-10 at 13:49 -0300, Henrique de Moraes Holschuh wrote:
> > Do note that when thinkpad-acpi switches bluetoot off, it *disappears* from
> > the bus (so, lsusb won't find it, etc).

It appears I was not clear enough... when thinkpad-acpi disables bluetooth,
for all intents and purposes, your computer *ceases to have bluetooth
hardware* as far as the rest of the Linux kernel knows.

So, the bluetooth core is not able to "reenable" bluetooth.

> > If bluetooth is still present in the bus, but the bluetooth interface is
> > down, then your problem is not related directly or indirectly to
> > thinkpad-acpi.
> 
> In fact, I check with the bluetooth LED state.

Do it with lsusb (run it as root), instead.

> > Now, if the bluetooth state persistence used to work on your thinkpad and it
> > doesn't work anymore, then the problem is likely in userspace.
> 
> In fact, I watched the LED accross the boot, and it lights on when the
> following is displayed:
> 
> [   19.441103] Bluetooth: Core ver 2.15
> [   19.451982] Bluetooth: HCI device and connection manager initialized
> [   19.456402] Bluetooth: HCI socket layer initialized
> [   19.497216] Bluetooth: Generic Bluetooth USB driver ver 0.5

(Continue reading)

Yves-Alexis Perez | 11 Oct 2009 14:44
Picon
Favicon

Re: bluetooth off state not remembered accross reboots?

On dim, 2009-10-11 at 09:39 -0300, Henrique de Moraes Holschuh wrote:
> On Sat, 10 Oct 2009, Yves-Alexis Perez wrote:
> > On sam, 2009-10-10 at 13:49 -0300, Henrique de Moraes Holschuh wrote:
> > > Do note that when thinkpad-acpi switches bluetoot off, it *disappears* from
> > > the bus (so, lsusb won't find it, etc).
> 
> It appears I was not clear enough... when thinkpad-acpi disables bluetooth,
> for all intents and purposes, your computer *ceases to have bluetooth
> hardware* as far as the rest of the Linux kernel knows.
> 
> So, the bluetooth core is not able to "reenable" bluetooth.

HMh, ok.
> 
> > > If bluetooth is still present in the bus, but the bluetooth interface is
> > > down, then your problem is not related directly or indirectly to
> > > thinkpad-acpi.
> > 
> > In fact, I check with the bluetooth LED state.
> 
> Do it with lsusb (run it as root), instead.

Attached are both lsusb with on and off.
> 
> > > Now, if the bluetooth state persistence used to work on your thinkpad and it
> > > doesn't work anymore, then the problem is likely in userspace.
> > 
> > In fact, I watched the LED accross the boot, and it lights on when the
> > following is displayed:
> > 
(Continue reading)


Gmane