From: Sebastian <bastisoft@arcor.de>
To: buildroot@busybox.net
Subject: [Buildroot] Xorg configuration for XGI chip
Date: Wed, 24 Mar 2010 13:46:00 +0100 [thread overview]
Message-ID: <4BAA0988.9050708@arcor.de> (raw)
In-Reply-To: <4BA8E694.3080809@terawatt.fr>
Hello,
> I tried with latest snapshot. I still have problems to launch a X server.
> With vesa and fbdev X drivers, it's OK, I can launch X server but only
> with depth 8, and resolution 800x600 for vesa and 600x480 for fbdev
> (framebuffer limit?). The problem is that I need depth 16 and 1024x600
> resolution.
You could check if the video BIOS allows higher resolutions for the
framebuffer. But you probably won't get widescreen this way.
About the compiling and loading issues, I have no idea.
> With SIS driver built in Buildroot, everything seems ok, no errors, but
> I only get a black screen. I tried a lot of options of the driver which
> seems to be useful but with no results.
Newer versions of the Xorg server won't display the black-and-white
pattern anymore, but instead a black screen. Try to run some application
from the same console device and watch the screen, like in:
# Xorg &
# DISPLAY=:0.0 xclock &
maybe the server is up and running, but you don't think it is?
> I don't know how to resolve this problem. I need a working displaying in
> 1024x600x16 mode but this chip doesn't seems to be very used with Linux.
I had some fun with SiS chipsets (SiS 315) myself, so I'm avoiding it.
Probably it isn't an option for you...
> So if somebody has the begin of an idea to solve this, I accept everything.
Try to post a full Xorg.0.log using the SiS driver, as it seems to be
the best working one for now.
I do not know if the driver supports full modesetting (i.e. widescreen
resolutions not offered by the video BIOS).
Best regards,
Sebastian
next prev parent reply other threads:[~2010-03-24 12:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 16:32 [Buildroot] Xorg configuration for XGI chip Damien Borie
2010-03-19 16:48 ` Paulius Zaleckas
2010-03-23 16:04 ` Damien Borie
2010-03-24 12:46 ` Sebastian [this message]
2010-03-24 15:19 ` Damien Borie
2010-03-24 15:55 ` Sebastian
2010-03-25 14:21 ` Damien Borie
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=4BAA0988.9050708@arcor.de \
--to=bastisoft@arcor.de \
--cc=buildroot@busybox.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 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.