From: Frank <hugelmopf-S0/GAf8tV78@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: vbetool on pure AMD64 system
Date: Wed, 9 Nov 2005 23:42:39 +0100 [thread overview]
Message-ID: <200511092342.40477.hugelmopf@web.de> (raw)
Hey guys,
due to your work in new kernels, my AMD64-laptop now resumes after an ACPI S3
suspend (I can type commands and they get executed) :-). Thanks a lot.
But the LCD stays black. So I read about the various options to reinitialize
the VGA, which were:
1. kernel boot options: acpi=s3_sleep, acpi=s3_mode, pci=routeirq. I tried
each one of them, LCD still stays black.
2. Using the vbetool to save/restore the state of the VGA.
Here is the problem: I didn't find an AMD64 version of vbetool (using Debian
testing AMD64), so I forced the i386 package and manually met its 32bit
dependencies. It does run, and the "vgastate off" option does disable the
LCD. But saving and restoring the state, I get the following error:
# vbetool vbestate save > /tmp/save
Can't get video state buffer size (vm86 failure)
Get video state buffer size failed
Can't save video state (vm86 failure)
Save video state failed
So I guess, there is some reason, that this program does not work on 64bit
machines. Is there a workaround or any other idea, how I can get my display
back alive?
Thanks,
Frank
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
next reply other threads:[~2005-11-09 22:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 22:42 Frank [this message]
[not found] ` <200511092342.40477.hugelmopf-S0/GAf8tV78@public.gmane.org>
2005-11-10 16:07 ` vbetool on pure AMD64 system Matthew Garrett
2005-11-11 10:33 ` Pavel Machek
[not found] ` <20051111103315.GB27805-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-11-14 17:02 ` Phillip Susi
[not found] ` <4378C318.9090105-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2005-11-14 21:48 ` Alan Cox
[not found] ` <1132004907.16148.32.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-11-14 22:29 ` Carl-Daniel Hailfinger
2005-11-12 11:02 ` Erik Slagter
[not found] ` <1131793377.5267.6.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-11-12 12:09 ` Frank
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200511092342.40477.hugelmopf@web.de \
--to=hugelmopf-s0/gaf8tv78@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox