public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Peddemors <michael@wizard.ca>
To: linux-kernel@vger.kernel.org
Subject: Framebuffer detection problems, 2.4.9
Date: 09 Oct 2001 16:38:15 -0700	[thread overview]
Message-ID: <1002670696.4112.285.camel@mistress> (raw)

I seldom dive into the graphical end of things myself, but this one has
had me stumped for the last week and a half..

I have a working ThinClient setup, that loads it's kernel via tftpd and
mknbi, with the 'vga=ask' option..
On one machine, with a Cirrus Logic card, (Cirrus Framebuffer support
compiled in) things work fine, but on all my other boxes with VESA
complaint cards, I cannot get it to use the VESA framebuffer, or
seemingly to detect the VESA devices with this kernel, although we can
on detect and pass modes using LILO on similar kernels.

I have of course read as many how-to's as possible, and the svga.txt
file seems to indicate that if I use the vga=ask option, and then run
scan it should show all VESA modes as well, (It does detect it as a VESA
VGA card), but the /fb/vesafb.txt seems to indicate that it won't show
the modes..

I see that in video.S CONFIG_VIDEO_VESA is harddefined, but I cannot
quite understand why I cannot enter a VESA mode that works..
I tried 313, 0313, and the decimal equivs 787 and 0787 but it keeps
returning that as an invalid mode..  This occurs on several machines,
all with recent video cards, that are VESA compliant, and listed as
compatible.. the motherboards all use recent BIOS's but still no joy..

I will accept help here, or can someone point me to a good mailing list
to work this out?

-- 
"Catch the Magic of Linux..."
--------------------------------------------------------
Michael Peddemors - Senior Consultant
LinuxAdministration - Internet Services
NetworkServices - Programming - Security
Wizard IT Services http://www.wizard.ca
Linux Support Specialist - http://www.linuxmagic.com
--------------------------------------------------------
(604)589-0037 Beautiful British Columbia, Canada


             reply	other threads:[~2001-10-09 23:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-09 23:38 Michael Peddemors [this message]
2001-10-10  0:24 ` Framebuffer detection problems, 2.4.9 Steven Walter
     [not found]   ` <1002675326.4200.297.camel@mistress>
2001-10-10  0:54     ` Steven Walter

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=1002670696.4112.285.camel@mistress \
    --to=michael@wizard.ca \
    --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