On Fri, Jun 19, 2009 at 11:13:03AM +0200, Josip Rodin wrote:
> On Fri, Jun 19, 2009 at 12:35:05AM +0200, Josip Rodin wrote:
> > > > In the meantime I've rebooted as well as hibernated the laptop a few
> > > > more
> > > > times, and I can't seem to establish a clear pattern by which
> > > > wwan_
On Wed, Jun 17, 2009 at 10:42:05PM -0300, Henrique de Moraes Holschuh wrote:
> > > > So it looks like the remaining problem is that something somewhere seems
> > > > to have set that option in a way that disabled the hardware, but nothing
> > > > tells the user that there is a problem. Can this be
On Fri, Jun 19, 2009 at 12:35:05AM +0200, Josip Rodin wrote:
> > But please _do_ open a bug about it on bugzilla.kernel.org, just in case I
> > have to send the fix after -rc1.
>
> Yet another bugzilla to register to, sigh...
It's #13600.
> > > In the meantime I've rebooted as well as hibernated
On Fri, Jun 19, 2009 at 12:35:05AM +0200, Josip Rodin wrote:
> > > In the meantime I've rebooted as well as hibernated the laptop a few more
> > > times, and I can't seem to establish a clear pattern by which wwan_enable
> > > gets set or unset, because it unset itself at least twice since, without
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 > /sys/devices/platform/thinkpad_
