This bug report was marked as Incomplete and has not had any updated
comments for quite some time. As a result this bug is being closed.
Please reopen if this is still an issue in the current Ubuntu release
http://www.ubuntu.com/getubuntu/download . Also, please be sure to
provide any requested in
The progress on this is breathtaking.
--
[Sony Corporation VGN-FW139E] suspend/resume failure
https://bugs.launchpad.net/bugs/360302
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.co
OK, so with the custom kernel I had other issues like dropped wifi
connections and no brightness control. Next, I compiled the new 2.6.32
kernel, and suspend still does not work with that, so I said F it and
went back to Jaunty, and now everything works. So, the bug fix is:
Reinstall Jaunty.
--
[
Compiled a custom kernel using KernelCheck and now suspend works like a
dream.
--
[Sony Corporation VGN-FW139E] suspend/resume failure
https://bugs.launchpad.net/bugs/360302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Suspend/resume worked perfect in Hardy and Intrepid as well, if that
helps.
--
[Sony Corporation VGN-FW139E] suspend/resume failure
https://bugs.launchpad.net/bugs/360302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
On a side note, hibernate works fine, just have to disable networking
and re-enable it to get wireless working. Just takes forever... Any
progress on the suspend/ resume fix?
Thanks!
--
[Sony Corporation VGN-FW139E] suspend/resume failure
https://bugs.launchpad.net/bugs/360302
You received this
still the same after updating to 2.6.31-15-generic-pae kernel, no
changes.
--
[Sony Corporation VGN-FW139E] suspend/resume failure
https://bugs.launchpad.net/bugs/360302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
Just went over the dmesg.txt, and there are no has matches, but there is
a magic number:
[0.955770] Magic number: 0:642:406
What to do with it though?
--
[Sony Corporation VGN-FW139E] suspend/resume failure
https://bugs.launchpad.net/bugs/360302
You received this bug notification because
On the above post I meant "there are no Hash Matches" no "there are no
has matches". yeesh.
--
[Sony Corporation VGN-FW139E] suspend/resume failure
https://bugs.launchpad.net/bugs/360302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Anything else I can do?
--
[Sony Corporation VGN-FW139E] suspend/resume failure
https://bugs.launchpad.net/bugs/360302
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
https://list
Well, that was fun. Ran a $sync; echo 1 > /sys/power/pm_trace; pm-
suspend from root terminal. On reboot, filesystem would not mount
because of the time difference (clock was reset to 1984) and errors in
the filesystem. Ran manual FSCK, and was able to reboot. Attached are
my dmesg.txt (from wh
OK, ran the pm-suspend after inserting no_console_suspend in the correct
place, and the first time got three lines for a split second that all
ended in "failed to resubmit", then they were gone and the computer
"suspended" AKA went into a coma like before. Second and third times
running pm_suspend
OK, answering the question in the "information gathering" area. NOW:
I believe this is a problem with suspend, as it never wakes up, just a black,
un-backlit screen.
It happens every single time without fail.
Suspend/ resume worked perfectly with Jaunty through most of the kernels(except
in t
I can personally confirm that this issue still exists on a fully updated
Karmic install, with _and_ without the FGLRX driver enabled.
Suspend/resume worked flawlessly for me in Jaunty. I'm in the process of
doing a clean reinstall from the Beta CD (had enabled some premature
PPA's which led to depe
Can you confirm this issue exists with the most recent Karmic Koala 9.10
Alpha release. ISO CD images are available at
http://cdimage.ubuntu.com/releases/karmic/ . If the issue remains with
Karmic it would be great to then also test the latest upstream mainline
kernel available. This will allow
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/25304368/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/25304371/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/25304373/Dependencies.txt
** A
16 matches
Mail list logo
