Switching to text console after suspend/resume gives only black screen
Hi all, I synced to the latest git (dc7fe476) to test suspend/resume to ram. Suspend and resume works like a charm with one drawback: switching to a text console after that does not work any more. The result is only a black screen. The console itself is responsive - just not displayed. Now the logs: Before a suspend/resume cycle - switching to the text console and back gives the following additional entries in Xorg.0.log: Synaptics DeviceOff called (II) Open ACPI successful (/var/run/acpid.socket) (II) <default pointer>: ps2EnableDataReporting: succeeded Synaptics DeviceOn called (--) Synaptics auto-dev sets device to /dev/input/event2 (**) Option "Device" "/dev/input/event2" (--) Synaptics touchpad found A suspend/resume cycle gives the following additional entries in Xorg.0.log: SetClientVersion: 0 9 SetGrabKeysState - disabled Synaptics DeviceOff called (II) Open ACPI successful (/var/run/acpid.socket) (EE) RADEONHD(0): RHDVGASave: VGA FB Offset (0x00000000) is out of range of the Cards Internal FB Address (0xD0000000) (II) <default pointer>: ps2EnableDataReporting: succeeded Synaptics DeviceOn called (--) Synaptics auto-dev sets device to /dev/input/event2 (**) Option "Device" "/dev/input/event2" (--) Synaptics touchpad found SetGrabKeysState - enabled After suspend/resume switching to the text console and back gives the following additional entries in Xorg.0.log Synaptics DeviceOff called (II) Open ACPI successful (/var/run/acpid.socket) (EE) RADEONHD(0): RHDVGASave: VGA FB Offset (0x00000000) is out of range of the Cards Internal FB Address (0xD0000000) (II) <default pointer>: ps2EnableDataReporting: succeeded Synaptics DeviceOn called (--) Synaptics auto-dev sets device to /dev/input/event2 (**) Option "Device" "/dev/input/event2" (--) Synaptics touchpad found attached ist the full Xorg.0.log keep up the good work Henry
I'm seeing problems switching to a text console as well, but it's not
related to suspend/resume -- it does it all the time. Anytime I
switch to a text console, my (ancient CRT) monitor goes into power
saving mode. I can blindly enter commands and I can switch back to
the X virtual terminal which works perfectly. The screen once again
goes off when X terminates.
Xorg.log with -logverbose 7 is attached. Please let me know if I can
provide any more information or help try something out.
Thanks for the amazing effort on this driver.
Robert
On Dec 12, 2007 1:07 AM, henry ritzlmayr
Hi all,
I synced to the latest git (dc7fe476) to test suspend/resume to ram.
Suspend and resume works like a charm with one drawback: switching to a text console after that does not work any more. The result is only a black screen. The console itself is responsive - just not displayed.
Now the logs:
Before a suspend/resume cycle - switching to the text console and back gives the following additional entries in Xorg.0.log:
Synaptics DeviceOff called (II) Open ACPI successful (/var/run/acpid.socket) (II) <default pointer>: ps2EnableDataReporting: succeeded Synaptics DeviceOn called (--) Synaptics auto-dev sets device to /dev/input/event2 (**) Option "Device" "/dev/input/event2" (--) Synaptics touchpad found
A suspend/resume cycle gives the following additional entries in Xorg.0.log:
SetClientVersion: 0 9 SetGrabKeysState - disabled Synaptics DeviceOff called (II) Open ACPI successful (/var/run/acpid.socket) (EE) RADEONHD(0): RHDVGASave: VGA FB Offset (0x00000000) is out of range of the Cards Internal FB Address (0xD0000000) (II) <default pointer>: ps2EnableDataReporting: succeeded Synaptics DeviceOn called (--) Synaptics auto-dev sets device to /dev/input/event2 (**) Option "Device" "/dev/input/event2" (--) Synaptics touchpad found SetGrabKeysState - enabled
After suspend/resume switching to the text console and back gives the following additional entries in Xorg.0.log
Synaptics DeviceOff called (II) Open ACPI successful (/var/run/acpid.socket) (EE) RADEONHD(0): RHDVGASave: VGA FB Offset (0x00000000) is out of range of the Cards Internal FB Address (0xD0000000) (II) <default pointer>: ps2EnableDataReporting: succeeded Synaptics DeviceOn called (--) Synaptics auto-dev sets device to /dev/input/event2 (**) Option "Device" "/dev/input/event2" (--) Synaptics touchpad found
attached ist the full Xorg.0.log
keep up the good work
Henry
Robert, Your problem should be fixed in the latest git commit. Thanks, Luc Verhaegen. SUSE/Novell X Driver Developer. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
Henry, Can you verify that this is still the case with the latest commit? Thanks, Luc Verhaegen. SUSE/Novell X Driver Developer. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
Am Samstag, den 15.12.2007, 02:27 +0100 schrieb Luc Verhaegen:
Henry,
Can you verify that this is still the case with the latest commit?
synced to the latest git (dcfd91c2) and I can verify that this is still the case. Also the same error message can be found in Xorg.0.log: (EE) RADEONHD(0): RHDVGASave: VGA FB Offset (0x00000000) is out of range of the Cards Internal FB Address (0xD0000000) cheers Henry -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
On Sun, Dec 16, 2007 at 11:00:26AM +0100, henry ritzlmayr wrote:
Am Samstag, den 15.12.2007, 02:27 +0100 schrieb Luc Verhaegen:
Henry,
Can you verify that this is still the case with the latest commit?
synced to the latest git (dcfd91c2) and I can verify that this is still the case.
Also the same error message can be found in Xorg.0.log:
(EE) RADEONHD(0): RHDVGASave: VGA FB Offset (0x00000000) is out of range of the Cards Internal FB Address (0xD0000000)
cheers Henry
Hrm... This does seem like behaviour that we cannot change immediately: When coming out of suspend/resume, there is probably no working mode, and we then enterVT into it and then set up X properly. So we save something that isn't really a working mode, and then restore that returning to VT. So there really is little we can do about this... Especially since we are just enabling/disabling the VGA emulation, never touching the other registers. So whatever we do, unless we do a full VGA store/restore as well, we cannot restore a vga text console. Then, if we do notice that we are coming out of a resume on entervt, and we decide not to store the current settings but keep old, already saved register content... What happens if there is a working mode on the console? What if the layout changed? This really is a tough nut to crack, and a serious minefield, and we probably will not fix it in the very forseeable future. Luc Verhaegen. SUSE/Novell X Driver Developer. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
Henry,
Have you tried switching to a console VT before suspending? I've been
using the tuxonice.net "hibernate" functionality with this driver
without difficulty, but I do have the SwitchToTextMode mode
configuration option enabled.
Robert
On Dec 16, 2007 4:00 AM, henry ritzlmayr
Am Samstag, den 15.12.2007, 02:27 +0100 schrieb Luc Verhaegen:
Henry,
Can you verify that this is still the case with the latest commit?
synced to the latest git (dcfd91c2) and I can verify that this is still the case.
Also the same error message can be found in Xorg.0.log:
(EE) RADEONHD(0): RHDVGASave: VGA FB Offset (0x00000000) is out of range of the Cards Internal FB Address (0xD0000000)
cheers Henry
-- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
-- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
Am Dienstag, den 18.12.2007, 22:07 -0600 schrieb Robert Tate:
Henry,
Have you tried switching to a console VT before suspending? I've been using the tuxonice.net "hibernate" functionality with this driver without difficulty, but I do have the SwitchToTextMode mode configuration option enabled.
Not yet - I will try it and post the result. Regarding tuxonice.net: Everything works flawlessly when I suspend to disk on FC7 - I only have this problem when suspending to ram - which I would prefer because it is much faster than saving 2Gig of ram to the disk, and I open/start my Z61p almost every day. thanks Henry
On Dec 16, 2007 4:00 AM, henry ritzlmayr
wrote: Am Samstag, den 15.12.2007, 02:27 +0100 schrieb Luc Verhaegen:
Henry,
Can you verify that this is still the case with the latest commit?
synced to the latest git (dcfd91c2) and I can verify that this is still the case.
Also the same error message can be found in Xorg.0.log:
(EE) RADEONHD(0): RHDVGASave: VGA FB Offset (0x00000000) is out of range of the Cards Internal FB Address (0xD0000000)
cheers Henry
-- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
-- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
On Wed, Dec 19, 2007 at 12:29:07PM +0100, henry ritzlmayr wrote:
Am Dienstag, den 18.12.2007, 22:07 -0600 schrieb Robert Tate:
Henry,
Have you tried switching to a console VT before suspending? I've been using the tuxonice.net "hibernate" functionality with this driver without difficulty, but I do have the SwitchToTextMode mode configuration option enabled.
Not yet - I will try it and post the result.
Regarding tuxonice.net: Everything works flawlessly when I suspend to disk on FC7 - I only have this problem when suspending to ram - which I would prefer because it is much faster than saving 2Gig of ram to the disk, and I open/start my Z61p almost every day.
thanks Henry
I explained why this happens in my previous mail, and i think that there is no other sane option but to close this issue. Luc Verhaegen. SUSE/Novell X Driver Developer. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
participants (4)
-
henry ritzlmayr
-
Luc Verhaegen
-
Robert Tate
-
Robert Tate