From: frank@inua.be
To: 9fans@9fans.net
Subject: [9fans] [frank@inua.be: Re: no frame buffer]
Date: Wed, 26 May 2010 18:32:26 +0200 [thread overview]
Message-ID: <20100526163226.GA20497@chiron.galaxy> (raw)
I don't see a follow-up on this topic... I hope someone still has an
idea.
----- Forwarded message from frank@inua.be -----
From: frank@inua.be
To: 9fans@9fans.net
Subject: Re: [9fans] no frame buffer
X-Virus-Scanned: Debian amavisd-new at mfilter3-v.gandi.net
Mail-Followup-To: 9fans@9fans.net
X-Virus-Scanned: clamav-milter 0.95.2 at lrelay02.edpnet.net
X-Virus-Status: Clean
X-BeenThere: 9fans@9fans.net
X-Mailman-Version: 2.1.10
Reply-To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.9fans.net>
List-Unsubscribe: <http://mail.9fans.net/options/9fans>,
<mailto:9fans-request@9fans.net?subject=unsubscribe>
List-Archive: <http://mail.9fans.net/private/9fans>
List-Post: <mailto:9fans@9fans.net>
List-Help: <mailto:9fans-request@9fans.net?subject=help>
List-Subscribe: <http://mail.9fans.net/listinfo/9fans>,
<mailto:9fans-request@9fans.net?subject=subscribe>
On Mon, May 24, 2010 at 12:00:14AM +0100, Ethan Grammatikidis wrote:
> Is it possible to limit the frame rate aux/vga sets? The reason I'm
> asking is:
No idea.
>> Whatever I use for monitor (vesa, vga) or vgasize, the
>> screen just turns black and the led of the monitor is blinking.
>
> I've had quite a lot of CRT monitors in the past. Many of them were
> detected as being more capable than they really were, so X would set the
> frame rate too high. A black screen with blinking led was a common
> symptom of that.
The same box with the same CRT runs X in 1280x1024x16 (didn't try
1600x1200).
Regarding Plan 9, I also tested it with:
- a plain old VGA monitor: just a blank screen
- a flat panel (vga connector): blank screen, "no signal"
Can it be that this is a driver issue?
I already tried to get more information using the -v and -V options of
aux/vga. With -m vesa, I always got the following, no matter what
resolution I asked:
main->snarf
vesa->snarf
vmf 100 vmdf 0 vf1 0 vbw 0
main->load
+vgactlw type vesa
-vgactlw type vesa
I also thought that I might get around it by using a specific
bios-string (-b option to aux/vga) but I don't know what I could
possibly use.
What can I do to debug this further?
Kind regards,
--
Frank Lenaerts ---------------------------------------- frank@inua.be
----- End forwarded message -----
--
Frank Lenaerts ---------------------------------------- frank@inua.be
next reply other threads:[~2010-05-26 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 16:32 frank [this message]
2010-05-27 0:00 ` erik quanstrom
2010-05-27 21:02 ` frank
2010-06-06 20:13 ` David du Colombier
2010-06-06 21:26 ` erik quanstrom
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=20100526163226.GA20497@chiron.galaxy \
--to=frank@inua.be \
--cc=9fans@9fans.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).