[Bug 444187] Re: [Micro-Star International MSI Notebook PR200] suspend/resume failure

2010-05-07 Thread mrbyu
Is that so? OK, they'll never fix it :) now i can clearly see that They just simply can not or do not want to resolve the problem. Doesn't matter now anyway because my little PR200X is broken... maybe I'll have a better luck with my next machine. I really love Ubuntu and all the developers but

[Bug 444187] Re: [Micro-Star International MSI Notebook PR200] suspend/resume failure

2009-10-12 Thread mrbyu
Anyway (offtopic - sry), what are your experiences about the battery time in Ubuntu? When I bought this notebook 2 years ago, the battery time was great, it lasted for almost 6 hours on Windows XP (with the original 6 cells battery), this was one of the best things about this machine. When I

[Bug 444187] Re: [Micro-Star International MSI Notebook PR200] suspend/resume failure

2009-10-10 Thread mrbyu
I always update my kernel to the latest, which I get from this page: http://kernel.ubuntu.com/~kernel-ppa/mainline/ But now I can't install the newest kernels (2.6.32-rc1, 2.6.31-rc3), because the package installer has a problem about an invalid package file descriptor or something like that...

[Bug 215033] Re: Resuming from suspend fails

2009-09-25 Thread mrbyu
** Description changed: -- Resuming from suspend fails https://bugs.launchpad.net/bugs/215033 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 436513] [NEW] suspend/resume still doesn't work on MSI PR200

2009-09-25 Thread mrbyu
Assignee: mrbyu (mrbyu) Status: New ** Tags: msi pr200 resume suspend ** Description changed: - When I try to resume my MSI PR200X notebook from suspend, it simply shuts down. Sometimes after this power-off the machine turns on itself, but nothing happens (I can only see a lighting

[Bug 215033] Re: Resuming from suspend fails

2009-06-10 Thread mrbyu
I keep updating the kernel and now I'm using Jaunty with 2.6.30 final but this annoying bug is still present, no matter how many times I update the kernel... looks like the Ubuntu developers has forgotten this bug and they do not make any effort to fix it... it couldn't be that hard to find an