mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: tapiov@welho.com
To: linux-kernel@vger.kernel.org
Cc: tapiov@welho.com
Subject: 2.6.0-test7 : S3 Virge (DX) driver, framebuffer
Date: Wed, 15 Oct 2003 14:42:01 +0300	[thread overview]
Message-ID: <1066218121.3f8d32897f51b@webmail.welho.com> (raw)


Hello,

I have an older PC, dating back to 1997, which has a graphic chip integrated on
the mother board. The chip is (based on) S3 Virge DX2. I have been using a
2.4.22 kernel from Slackware 9.1 distribution, which has been able to use the
framebuffer  modes (especially mode vga=773) successfully. 
So I tried compiling the 2.6.0-test7 kernel and followed the advice given in the
Framebuffer-HOWTO from TLDP (http://www.tldp.org/HOWTO/Framebuffer-HOWTO-5.html)
as good as I was able to. I could not find all the items from the xconfig menus
mentioned in that article  (namely the "advanced low level drivers) so I assumed
that the article was probably a bit outdated. I successfully turned on all
framebuffer related switches, fonts and mode selection support. Then compiled
and installed the new kernel. 

Now I found out that I wasn't able to use vga=773 anymore; only some
lower-resolution modes were available at the lilo prompt. From the mentioned
article I also read about a patch used earlier for S3 drivers, due to S3 chips
non-compatibility with VESA 2.0 (them being 1.2 only?).

Does such a patch exist still for 2.6.0? Or how could I get back to using better
resolution?

My apologizes, if this mail is completely off-topic. Please, let me know (email
me directly) if you have a better source of information than this forum.

Thanks,

Tapio Valli



                 reply	other threads:[~2003-10-15 11:42 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=1066218121.3f8d32897f51b@webmail.welho.com \
    --to=tapiov@welho.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

all inboxes | Powered by JetHome®