lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 15 Dec 2008 23:34:52 +0100
From:	"Robert M. Albrecht" <mail@...al.de>
To:	Philip Langdale <philipl@...rt.org>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Bug 10173 / Bluetooth on Toshiba & Compal laptops

Hi Phil,

anything I can do ? Providing some logs or granting ssh access to the 
machine to have a look ?

cu romal

www.romal.de
blog.romal.de


Am 15.12.2008 23:35 Uhr, schrieb Philip Langdale:
> On Mon, 15 Dec 2008 21:29:05 +0100, "Robert M. Albrecht"<mail@...al.de>
> wrote:
>> Hi,
>>
>> anyone working on toshiba_acpi or omnibook module ?
>>
>> toshiba_acpi:
>>
>>
> http://git.kernel.org/?p=linux/kernel/git/linville/wireless-next-2.6.git;a=commit;h=c41a40c58b623f97dd2e23aa3baab2cedb47d99f
>> The rfkill-switch does not work. The device is disabled when switched of,
>
>> but it gets not reenabled. But the bluetooth dongle is enabled after
>> booting.
>>
>> AFAIK this only works for Toshiba manufactured devices (toshiba_acpi),
> not
>> for Compal manufactured.
>
> The officially stated maintainer for toshiba_acpi seems to be out of
> contact,
> but I'm responsible for the rfkill patch. I can only say that the patch is
> designed
> to re-enable bluetooth when the hardware kill switch is de-asserted and
> that I tested
> this to work before the change was merged. If it doesn't work now, it's
> either:
>
> a) a regression introduced by one of the fixes for laptops with no
> bluetooth device. I
>     consider this unlikely.
>
> b) different behaviour in your model of toshiba vs. mine
>
> c) a difference in how you've got the kill switch configured in sysfs. Not
> sure if that's
>     even possible.
>
> As you might conclude, I suspect B.
>
> --phil
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ