On Mon, Jun 22, 2009 at 01:42:40PM +0200, 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
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
On Wed, 09 Dec 2009, Josip Rodin wrote:
Jun 22 13:36:12 myhostname kernel: thinkpad_acpi: bluetooth_update_rfk:
forced rfkill state to 0
Jun 22 13:36:12 myhostname kernel: thinkpad_acpi: wan_update_rfk: forced
rfkill state to 0
OK, I think it's definitely something broken in the
On Fri, Jun 19, 2009 at 12:54:41PM +0200, Josip Rodin wrote:
I just booted into Linux again, it restored itself fine from hibernation,
but now I get a new symptom:
% cat /sys/devices/platform/thinkpad_acpi/wwan_enable
0
% sudo sh -c 'echo 1
On Tue, Jun 16, 2009 at 04:04:28PM -0700, Greg KH wrote:
On Tue, Jun 16, 2009 at 12:42:27AM +0200, Josip Rodin wrote:
On Tue, Jun 16, 2009 at 12:34:46AM +0200, Josip Rodin wrote:
I have an integrated wireless setup inside my Lenovo Thinkpad T400
which
normally works fine and
On Wed, 17 Jun 2009, Josip Rodin wrote:
So I thought - let me check that wwan_enable thing on 2.6.30:
% cat /sys/devices/platform/thinkpad_acpi/wwan_enable
0
The firmware will power down the internal WWAN module if that thing is set
to 0... so it will obviously not show up on the
