All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michel Dänzer <daenzer@relog.ch>
To: John Grimes <jpgrimes@johngrimes.dyndns.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Xfree86 version 4.01
Date: Tue, 25 Jul 2000 10:56:25 +0200	[thread overview]
Message-ID: <397D5639.97BCD510@relog.ch> (raw)
In-Reply-To: Pine.LNX.4.21.0007241055570.1920-100000@johngrimes.dyndns.org


John Grimes wrote:

> > > For some reason I can not get any other mode to work (i.e.
> > > 640x480,1024x768, 800x600).  If any would fail I would expect it to be
> > > 1280x1024 not the smaller modes.  I have no modelines defined, just
> > > letting XF86 decided which modes to use.  Any ideas why the defaults
> > > don't work?
> >
> > Look at the log. There should be a reason for every rejected mode.
>
> There aren't any rejected modes.

How exactly do they not work then?

> I think the suggestion taht I use fbset to create modelines is right on.

Try it, but I think if that was the problem your modes would get rejected. Do
you use Option "UseFBDev"?


> > > First how do I find out the bus address of my internal video?  It
> > > doesn't show up in /proc/pci although it is in /proc/fb.  This is on a
> > > highly upgraded powercenter.
> >
> > If it's not in /proc/pci, the server probably doesn't bother about it
> > either, so you shouldn't have to care.
>
> ahh, i think i see now.  By defining a fb device the fbdev driver will
> figure it wou,

Yes. If the internal video isn't the default framebuffer device (where the
initial console comes up on), you'll have to add

	Option	"fbdev" "/dev/fb1"

in its Device Section though.

> unlike the r128 driver which wanted a bus id.

Actually, the bus ID is needed there because the higher level PCI code of the
X server will deactivate the chip otherwise. :)

(it can't determine the connection between the PCI and framebuffer devices
automatically)


> how do I do fbset -x to see the modelines on the second monitor?

There's an fbset option to select the framebuffer device, the second monitor
is probably /dev/fb1 .


Michel


--
UNIX is like Sex:
If you don't know it, you don't miss it. But if you know it, you'll need it.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-07-25  8:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0007240938040.11526-100000@dyn-133-196.gordon.edu>
2000-07-24 14:12 ` Xfree86 version 4.01 John Grimes
2000-07-24 14:20   ` Michael Schmitz
2000-07-24 14:41     ` John Grimes
2000-07-24 14:43       ` Michael Schmitz
2000-07-24 14:38   ` Michel Dänzer
2000-07-24 15:00     ` John Grimes
2000-07-25  8:56       ` Michel Dänzer [this message]
2000-07-25 13:10         ` John Grimes
2000-07-25 13:41           ` Michel Dänzer
2000-07-25 14:02             ` John Grimes
2000-07-25 14:02               ` Michel Dänzer
2000-07-25 14:44             ` Benjamin Herrenschmidt
2000-07-25 15:01               ` Michael Schmitz
2000-07-25 15:38                 ` John Grimes
2000-07-25 17:28                   ` Michael Schmitz
2000-07-25 15:23 tjw4

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=397D5639.97BCD510@relog.ch \
    --to=daenzer@relog.ch \
    --cc=daenzerm@student.ethz.ch \
    --cc=jpgrimes@johngrimes.dyndns.org \
    --cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.