From: frank@inua.be
To: 9fans@9fans.net
Subject: Re: [9fans] no frame buffer
Date: Mon, 24 May 2010 21:45:29 +0200 [thread overview]
Message-ID: <20100524194529.GA3742@chiron.galaxy> (raw)
In-Reply-To: <4B45AC2A-B400-41F7-B8A8-601E4017C452@fastmail.fm>
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
prev parent reply other threads:[~2010-05-24 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 22:55 frank
2010-05-23 0:01 ` erik quanstrom
2010-05-23 10:08 ` frank
2010-05-23 11:26 ` Richard Miller
2010-05-23 13:55 ` frank
2010-05-23 21:41 ` frank
2010-05-23 23:00 ` Ethan Grammatikidis
2010-05-24 19:45 ` frank [this message]
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=20100524194529.GA3742@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).