From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Dave Jones <davej@redhat.com>
Cc: linux-kernel@vger.kernel.org, cheapisp@sensewave.com
Subject: Re: hi-res fb console with 2.6.0-testX ?
Date: Mon, 8 Sep 2003 12:29:49 +0200 [thread overview]
Message-ID: <C71CD161531@vcnet.vc.cvut.cz> (raw)
On 7 Sep 03 at 22:58, Dave Jones wrote:
> On Sun, Sep 07, 2003 at 09:51:51PM +0200, cheapisp@sensewave.com wrote:
> > The kernel command lines which work with vesafb and matroxfb in 2.4 do not
> > work for me in 2.6.0-testX.
> >
> > kernel (hd0,0)/bz-2.6.0-t4mm3 root=/dev/hdc2 video=matrox:vesa:0x11A
> > kernel (hd0,0)/bz-2.6.0-t4mm3 root=/dev/hdc2 vga=794
>
> vga= seems to have changed semantics. (Which is a polite way of saying
> "has regressed" IMO), this has been reported several times before, but
> it doesn't seem to be too high on peoples 'must fix' list.
>
> > Doing fbset "vesa11A" causes the monitor to lose the sync.
>
> last I looked, fbset needed updates for the changes in 2.6
video= changed sematic too. Now you have to do
video=matroxfb:...., not video=matrox:....
And /dev/fb* changed semantic too, so forget about using fbset on your
box.
And whole fb subsystem changed semantic, so do not build both
vesafb & matroxfb into the kernel - either one or another, or
you'll be definitely surprised what will happen (and I'm almost
sure that blank screen is not what you want).
Best regards,
Petr Vandrovec
next reply other threads:[~2003-09-08 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-08 10:29 Petr Vandrovec [this message]
2003-09-08 20:57 ` hi-res fb console with 2.6.0-testX ? Geert Uytterhoeven
2003-09-08 22:38 ` Petr Vandrovec
2003-09-09 8:54 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2003-09-07 19:51 cheapisp
2003-09-07 21:58 ` Dave Jones
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=C71CD161531@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=cheapisp@sensewave.com \
--cc=davej@redhat.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