linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Carlo E. Prelz" <fluido@fluido.as>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: how to activate X with famebuffer
Date: Tue, 28 Sep 2004 08:54:32 +0200	[thread overview]
Message-ID: <20040928065431.GA9604@epio.fluido.as> (raw)
In-Reply-To: <4EE0CBA31942E547B99B3D4BFAB34811107FFD@mail.esn.co.in>

	Subject: RE: [Linux-fbdev-devel] how to activate X with famebuffer
	Date: mar, set 28, 2004 at 11:11:37 +0530

Quoting Mukund JB. (mukundjb@esntechnologies.co.in):

> > > I get the error message saying :-
> > > (EE) Screen(s) found, but none have a usable configuration.
> > 
> > <cut>
> > 
> > > Section "Screen"
> > > 	Identifier "Screen0"
> > > 	Device "Linux Frame Buffer"
> > > 	Monitor "COMPAQ S510"
> > > 	DefaultDepth 8
> > > 	Subsection "Display"
> > > 		Depth 8
> > > 	#	Modes "1024x768"
> > > 	EndSubSection
> > > EndSection
> > 
> > Why did you comment out the "modes" line??
> I am defining the mode in the lilo.conf file.

Your error message tells you that the "screen" section is
unusable. So, you are supposed to experiment with modifications on
that section until the error message changes - that is, until your
screen section becomes usable. Focus on the immediate block. When your
screen section is OK. either X will work, or you will have a new error
message pointing to new tests and experiments.

X must be told at what resolution to work, and all framebuffer drivers
but the simple VESA one can change resolution on the fly, so you can
very well have X in one resolution and text mode in one (or more)
other resolutions. 

Carlo

-- 
  *         Se la Strada e la sua Virtu' non fossero state messe da parte,
* K * Carlo E. Prelz - fluido@fluido.as             che bisogno ci sarebbe
  *               di parlare tanto di amore e di rettitudine? (Chuang-Tzu)


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php

  reply	other threads:[~2004-09-28  6:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28  5:41 how to activate X with famebuffer Mukund JB.
2004-09-28  6:54 ` Carlo E. Prelz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-09-28 11:27 Mukund JB.
2004-09-28 21:33 ` Antonino A. Daplas
2004-09-27 13:36 Mukund JB.
2004-09-27 18:11 ` Carlo E. Prelz
2004-09-27  9:28 Mukund JB.
2004-09-27 11:20 ` Geert Uytterhoeven
2004-09-27  5:15 Mukund JB.
2004-09-27  5:48 ` Carlo E. Prelz

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=20040928065431.GA9604@epio.fluido.as \
    --to=fluido@fluido.as \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).