From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: LKML List <linux-kernel@vger.kernel.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: Yet more display troubles with 2.6.15-rc5-mm2
Date: Wed, 14 Dec 2005 09:22:28 +0800 [thread overview]
Message-ID: <439F73D4.9060304@gmail.com> (raw)
In-Reply-To: <9a8748490512131319o408a368eqfed225abebaff4d@mail.gmail.com>
Jesper Juhl wrote:
> On 12/13/05, Antonino A. Daplas <adaplas@gmail.com> wrote:
>> Jesper Juhl wrote:
>>> On 12/12/05, Antonino A. Daplas <adaplas@gmail.com> wrote:
>>>> Jesper Juhl wrote:
>>>>
>>> I'm already using the vesa driver. It seems to be the only Open Source
>>> driver that'll work with this card, so i don't have any other to try.
>>>
>> I just tried with Xorg vesa and vgacon, and everything seems to work okay.
>> Now I'm not sure what changes in linux causes the vgacon state restore
>> to fail (VGA state restoration is almost the entire responsibility
>> of X, BTW), but maybe you can use vbetool to get and set the vga mode,
>> just to test?
>>
> Ok, I'm not familiar with that tool and my distribution doesn't
> include it, but if it will be useful to you for me to test with it
> I'll get and install it. What exactely would you like me to do/try
> with it?
The vbetool is capable of getting/setting or saving/restoring the current
state of the hardware. You can run vbetool vbestate save before going
to X and then run vbetool vbestate restore after switching back to console.
Tony
next prev parent reply other threads:[~2005-12-14 1:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-11 21:06 Yet more display troubles with 2.6.15-rc5-mm2 Jesper Juhl
2005-12-12 0:03 ` Antonino A. Daplas
2005-12-12 18:31 ` Jesper Juhl
2005-12-13 0:38 ` Antonino A. Daplas
2005-12-13 21:16 ` Jesper Juhl
2005-12-13 9:41 ` Antonino A. Daplas
2005-12-13 21:19 ` Jesper Juhl
2005-12-14 1:22 ` Antonino A. Daplas [this message]
2005-12-20 18:00 ` Jesper Juhl
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=439F73D4.9060304@gmail.com \
--to=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.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