public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Damian Kolkowski <damian@kolkowski.no-ip.org>
Cc: Kronos <kronos@kronoz.cjb.net>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Sergio Vergata <vergata@stud.fbi.fh-darmstadt.de>
Subject: Re: Radeonfb problem
Date: Wed, 18 Feb 2004 09:22:12 +1100	[thread overview]
Message-ID: <1077056532.1076.27.camel@gaston> (raw)
In-Reply-To: <20040217215738.ALLYOURBASEAREBELONGTOUS.B9706@kolkowski.no-ip.org>

On Wed, 2004-02-18 at 08:57, Damian Kolkowski wrote:
> * Kronos <kronos@kronoz.cjb.net> [2004-02-17 22:51]:
> > > 2.6.3-rc4 with new radeonfb looks better, but in lilo.con append for radeonfb
> > > wont work.
> > 
> > What do you mean? What are passing to the kernel?
> 
> For example:
> 
> append = "video=radeon:1024x768-32@100" works for 2.4.x
> append = "video=radeonfb:1024x768-32@100 works for 2.6.x
> 
> but for new radeonfb _radeonfb_ in append won't work, my screean start with
> small res on 36 Hz ;-) So I need to use fbset.
> 
> Besides don't use 2.6.x even on desktop, that was only a test with new
> radeonfb from Ben H.

Ugh ? Send me a dmesg log at boot please without any command
line. radeonfb should set your display to the native panel size
by default

Ben.



  reply	other threads:[~2004-02-17 22:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-17 19:08 Radeonfb problem Sergio Vergata
2004-02-17 20:36 ` Kronos
2004-02-17 21:11   ` Damian Kolkowski
2004-02-17 21:34     ` Kronos
2004-02-17 21:57       ` Damian Kolkowski
2004-02-17 22:22         ` Benjamin Herrenschmidt [this message]
2004-02-18  0:02           ` Sergio Vergata
2004-02-18  0:11             ` Benjamin Herrenschmidt
2004-02-18 10:26           ` Damian Kolkowski
2004-02-18 11:01             ` Benjamin Herrenschmidt
2004-02-18 10:33           ` Damian Kolkowski
2004-02-19 23:21           ` Joshua Kwan

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=1077056532.1076.27.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=damian@kolkowski.no-ip.org \
    --cc=kronos@kronoz.cjb.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vergata@stud.fbi.fh-darmstadt.de \
    /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