Please try to fix this before the release if you can. I can cofirm that
the bug is still present in current feisty. When resuming from
hibernation, it crashes when switching to graphics mode (num-lock
doesn't react any more). See also #79286 for logs.
However, the solution mentioned above works:
In my system the question is yes.
(Sony Vaio, VGN FS285M, Nvidia Go 6200)
--
Pedro Martínez Juliá
\ [EMAIL PROTECTED]
)| WebLog: http://www.pedromj.com/blog
/ Página web: http://www.pedromj.com
GoogleTalk: [EMAIL PROTECTED]
Socio HispaLinux #311
Usuario Linux #275438 -
I am still running 6.10. I will upgrade to 7.04 when the final release is
out.
On 3/19/07, Pedro Martínez Juliá [EMAIL PROTECTED] wrote:
In my system the question is yes.
(Sony Vaio, VGN FS285M, Nvidia Go 6200)
--
Pedro Martínez Juliá
\ [EMAIL PROTECTED]
)| WebLog:
If you get a chance to test this, we may be able to fix it before Feisty
gets released. The DesktopCD (LiveCD) should be enough to confirm
whether it is happening with a suspend to ram and without needing a full
installation to test.
--
Suspend and Hibernate solution for nvidia binary drivers
ok I will download the latest tonight. I will go ahead and do a complete
install so I can test it with the latest nvidia drivers.
On 3/19/07, Paul Sladen [EMAIL PROTECTED] wrote:
If you get a chance to test this, we may be able to fix it before Feisty
gets released. The DesktopCD (LiveCD)
I'm unable to get suspend/hibernate working in latest feisty with binary
drivers. Works perfectly with free drivers. What kind of information
would be useful to help resolve this? (I'm still using a Compaq R3000
type laptop with a geforce go 440)
Thanks,
Aaron
--
Suspend and Hibernate solution
Okay, it's been a year since there was first opened. Could either of
you with this issue test Feisty, and if we still have the issue I'll try
to revisit it.
** Changed in: acpi-support (Ubuntu)
Assignee: Paul Sladen = (unassigned)
--
Suspend and Hibernate solution for nvidia binary
I can confirm for a nVidia 6600GT chipset, I have to set
SAVE_VBE_STATE=false (or uncomment the default, which is true).
When I've later accessed the Monitor Display section in KDE's
System Settings, it printed VESA BIOS Extensions not detected. to
the console. So probably a fix would be to use
