From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Damien Wyart <damien.wyart@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: VESA fb console in 2.6.15
Date: Wed, 23 Nov 2005 08:32:00 +0800 [thread overview]
Message-ID: <4383B880.80301@gmail.com> (raw)
In-Reply-To: <20051122162226.41305851.akpm@osdl.org>
Andrew Morton wrote:
> Damien Wyart <damien.wyart@gmail.com> wrote:
>>>> I've noticed in several versions of 2.6.15 that VESA fb console
>>>> seems completely broken : it draws screen in several very slow
>>>> steps, making the whole display almos unusable. And it crashes
>>>> *very* often, for example when switching to X. The computer is
>>>> complety locked, and doesn't even respond to SysRQ.
>>>> I use vga=0x31B as boot param.
>> * "Antonino A. Daplas" <adaplas@gmail.com> [051122 01:28]:
>>
>>> Try booting with:
>>> vga=0x31b video=vesafb:mtrr:3
>> Thanks, this works fine with this param and also without any video=
>> param. I had a default video=vesafb:mtrr:2 in my grub conf file because
>> of mtrr problems a few kernel versions earlier (had been discussed
>> extensively on this list). This setting doesn't work well in 2.6.15.
>>
>
> Does 2.6.15-rc? work OK without any special boot options? (We want it to..)
>
>From what I understand, before this, he needs video=vesafb:mtrr:2. (Because
his machine defaults to write-back mtrr instead of write-combining). Now it
works without any special boot options because I made vesafb default to
nomtrr because of problems like this and conflicts with X/DRI.
Tony
next prev parent reply other threads:[~2005-11-23 0:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 21:55 VESA fb console in 2.6.15 Damien Wyart
2005-11-22 0:28 ` Antonino A. Daplas
2005-11-22 17:17 ` Damien Wyart
2005-11-23 0:22 ` Andrew Morton
2005-11-23 0:32 ` Antonino A. Daplas [this message]
2005-11-23 7:36 ` Damien Wyart
2005-11-23 19:38 ` Bill Davidsen
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=4383B880.80301@gmail.com \
--to=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=damien.wyart@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.