From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Timothy Miller <miller@techsource.com>
Cc: benh@kernel.crashing.org, felix-kernel@fefe.de,
linux-kernel@vger.kernel.org
Subject: Re: radeonfb broken
Date: Fri, 16 Apr 2004 09:40:38 -0700 [thread overview]
Message-ID: <20040416094038.5ae1bc52.rddunlap@osdl.org> (raw)
In-Reply-To: <4080047E.9050804@techsource.com>
On Fri, 16 Apr 2004 12:06:22 -0400 Timothy Miller wrote:
|
| BTW, now that we're on the topic of Radeon, could someone tell me how to
| tell the kernel the default resolution to use when initializing the
| console?
|
| When using a CRT, it defaults to 640x480. When I use my Planar PQ191
| 19" 1280x1024 monitor, it defaults to 1024x768. I want it to default to
| 1280x1024. There's a tool, fbset or something like that, which I can
| use AFTER bootup, but trying to put that into init causes all sorts of
| conflicts. I need to be able to tell the kernel, either at compile time
| or on the boot command line.
See <Documentation/fb/modedb.txt> for a little help: <quote>
Valid mode specifiers (mode_option argument):
<xres>x<yres>[-<bpp>][@<refresh>]
<name>[-<bpp>][@<refresh>]
with <xres>, <yres>, <bpp> and <refresh> decimal numbers and <name> a string.
Things between square brackets are optional.
</quote>
I haven't done this, but I've seen emails using syntax like so:
(from /etc/lilo.conf:)
append="video=radeonfb:1024x768-32@100"
or:
append="video=radeonfb radeonfb.mode_option=1280x1024-32@60"
or:
append="video=radeonfb:1024x768-32@100"
Looking at the driver source code, I'd guess that the middle
one above is closest to correct.
ISTM that Documentation/kernel-parameters.txt needs a paragraph
about syntax for specifying parameters for built-in modules vs.
loadable modules....
| Moving off topic, my cries for help from the XFree86 people also seem to
| have gotten lost in the flow of hundreds of usenet messages. Try as I
| might, I cannot seem to get XFree86 to talk to my monitor at anything
| other than 60Hz. Even though LCD monitors have a persistent image,
| increasing the frame rate CAN reduce motion blur slightly.
--
~Randy
"We have met the enemy and he is us." -- Pogo (by Walt Kelly)
(Again. Sometimes I think ln -s /usr/src/linux/.config .signature)
next prev parent reply other threads:[~2004-04-16 16:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 20:25 Felix von Leitner
2004-04-15 21:13 ` Timothy Miller
2004-04-16 1:43 ` Benjamin Herrenschmidt
2004-04-16 15:58 ` Timothy Miller
2004-04-17 0:22 ` Benjamin Herrenschmidt
2004-04-19 14:18 ` Timothy Miller
2004-04-19 22:36 ` Benjamin Herrenschmidt
2004-04-16 16:06 ` Timothy Miller
2004-04-16 16:40 ` Randy.Dunlap [this message]
[not found] ` <20040415152507.3a0b014d.akpm@osdl.org>
2004-04-16 15:56 ` Timothy Miller
2004-04-16 20:34 ` James Simmons
2004-04-16 21:05 ` Timothy Miller
2004-04-19 2:18 ` David Eger
2004-04-16 1:46 ` Benjamin Herrenschmidt
2004-04-20 21:09 David Eger
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=20040416094038.5ae1bc52.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=felix-kernel@fefe.de \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.com \
/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®