All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: cheapisp@sensewave.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: hi-res fb console with 2.6.0-testX ?
Date: Sun, 7 Sep 2003 22:58:04 +0100	[thread overview]
Message-ID: <20030907215803.GB28927@redhat.com> (raw)
In-Reply-To: <10539.80.202.106.246.1062964311.squirrel@to.server.sensewave.com>

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                       
 >                                    
 > both result in something resembling a Vesa 101 mode under 2.6.0-test4-mm3. 
 >                                    
 > (640x480, 60 Hz)                                                           
 >                                    
 > I'd expect 1280x1024 in 60 Hz, which is what I get with a 2.4 kernel.      

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

		Dave

-- 
 Dave Jones     http://www.codemonkey.org.uk

  reply	other threads:[~2003-09-07 21:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-07 19:51 hi-res fb console with 2.6.0-testX ? cheapisp
2003-09-07 21:58 ` Dave Jones [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-08 10:29 Petr Vandrovec
2003-09-08 20:57 ` Geert Uytterhoeven
2003-09-08 22:38   ` Petr Vandrovec
2003-09-09  8:54     ` Geert Uytterhoeven
2003-09-09  8:54       ` Geert Uytterhoeven

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=20030907215803.GB28927@redhat.com \
    --to=davej@redhat.com \
    --cc=cheapisp@sensewave.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.