On Wed, Dec 09, 2009 at 01:49:42PM +0100, Josip Rodin wrote:
> > > > Then keep an eye on the logs, you want to check both the ones since
> > > > boot for the session where you notice WWAN is disabled, as well as the
> > > > ones since the boot _previous_ to that one, because something might
> > > > have caused thinkpad-acpi to tell the firmware to store in NVRAM that
> > > > WWAN should be disabled on the next power up...
>
> OK, I think it's definitely something broken in the driver, because under
> 2.6.31 and 2.6.32 it consistently screws things up through hibernation.
>
> If I just reboot the machine normally, I get the devices back in state 1,
> both in Linux and in Windows. Only when I hibernate in Linux does the driver
> seem to write the "let's-completely-disable-it" state into the hardware --
> even if it was explicitly *not* disabled in the Linux session that initiated
> the hibernation.
>
> The /sys/devices/platform/thinkpad_acpi/rfkill/rfkill?/persistent states
> are on (1) all the time, but it doesn't actually do what appears to be
> logical - keep the switch state that it had in the last session.
I've filed this in Bugzilla as Bug #14775.
--
2. That which causes joy or happiness.
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
ibm-acpi-devel mailing list
ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
