> Though somehow comment 86 indicates this is not a fix in all cases.
I have the same hardware (Asus Eee PC 1000H) and can't reproduce the issue stated in comment #86 with 2.6.31-16.51~pre2 (no other issues turning wireless on/off with this kernel as well).
> the patch was delayed because -15 was already uploaded to proposed
> for verification.
There is something strange in the changelog <https:/ /launchpad. net/ubuntu/ karmic/ +source/ linux/+ changelog> claiming two identical entries for 2.6.31-15.49: the first dated 2009-10-28 and the second 2009-11-10. The patch was checked in upstream on 2009-10-22: <http:// git.kernel. org/?p= linux/kernel/ git/stable/ linux-2. 6.31.y. git;a=commitdif f;h=b5a56fc94bc c0910870391da87 78ba1c6d41bd3d>. Does it mean, the first -15 was uploaded to proposed 5 days before the official timestamp in the changelog? And what about the second one?
> Though somehow comment 86 indicates this is not a fix in all cases.
I have the same hardware (Asus Eee PC 1000H) and can't reproduce the issue stated in comment #86 with 2.6.31-16.51~pre2 (no other issues turning wireless on/off with this kernel as well).