public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Lindner <mailinglists@xgm.de>
To: linux-kernel@vger.kernel.org
Subject: Problem with framebuffer resolution setting
Date: Wed, 21 Jan 2004 15:01:40 +0100	[thread overview]
Message-ID: <200401211501.40794.mailinglists@xgm.de> (raw)

Hello,
sorry for bothering you with this (probably) rather simple question. but I've 
already asked two newsgroups, none had the answer.
I just try to compile kernel 2.6.1. Everything works perfect, except the
framebuffer support (I want to higher resolution for the console).
I've support for frame buffer devices (FB) and nVidia Riva support
(FB_RIVA) as well as Video mode selection support (VIDEO_SELECT) and
Framebuffer Console support (FRAMEBUFFER_CONSOLE) enabled. All of them are 
compiled into the kernel, not as a module. I've a Riva TNT2
I tried some modes from $KERNEL-SOURCES/Documentation/fb/vesafb.txt like
vga=0x317, vga=0x318 to append to to the kernel command line.
I've tried it with setting vga=0x317 in lilo.conf and also with vga=ask and 
entering 317 directly.
The monitor switches to another resolution upon boot for a very short time
and displays a message, but to short to read. Than it switches back to the
default resolution.
Trying fbset on the console to set the resolution results in a blank screen.
What is wrong? fb support with 2.4 and vga=773 worked perfect.
Thx,
Florian

This is the output of fbset -i

mode "640x480-60"
    # D: 25.176 MHz, H: 31.469 kHz, V: 59.942 Hz
    geometry 640 480 640 480 8
    timings 39721 40 24 32 11 96 2
    accel true
    rgba 8/0,8/0,8/0,0/0
endmode

Frame buffer device information:
    Name        : nVidiaRIVA-VTNT2
    Address     : 0xd4000000
    Size        : 33554432
    Type        : PACKED PIXELS
    Visual      : PSEUDOCOLOR
    XPanStep    : 1
    YPanStep    : 1
    YWrapStep   : 0
    LineLength  : 640
    MMIO Address: 0xd6000000
    MMIO Size   : 16777216
    Accelerator : Unknown (28)


                 reply	other threads:[~2004-01-21 13:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200401211501.40794.mailinglists@xgm.de \
    --to=mailinglists@xgm.de \
    --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