On Wed, 24 Jun 2009, Noèl Köthe wrote:

> Thanks alot for this hint. Yes, it fixes the problem.
>
> After booting 2.6.30:
>
> $ cat /proc/acpi/ibm/wan
> status: disabled
> commands: enable, disable
>
> So the fix for this bug is to get the same behaviour like before to have
> it enabled after booting. The machine has a kill switch to disable it.

so what happend since. how does 2.6.32 behave?
does upstream know of aboves, if not please notify bugzilla.kernel.org
and let us know the bug nr.

thanks



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Am Samstag, den 13.02.2010, 12:13 +0100 schrieb maximilian attems:

> > After booting 2.6.30:
> >
> > $ cat /proc/acpi/ibm/wan
> > status: disabled
> > commands: enable, disable
> >
> > So the fix for this bug is to get the same behaviour like before to have
> > it enabled after booting. The machine has a kill switch to disable it.
>
> so what happend since. how does 2.6.32 behave?
> does upstream know of aboves, if not please notify bugzilla.kernel.org
> and let us know the bug nr.

2.6.32 enables the 3G device and its available in networkmanager
(squeeze) without manual steps.


--
Noèl Köthe <noel debian.org>
Debian GNU/Linux, www.debian.org