From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 24 May 2010 21:45:29 +0200 From: frank@inua.be To: 9fans@9fans.net Message-ID: <20100524194529.GA3742@chiron.galaxy> References: <20100522225553.GA17342@chiron.galaxy> <20100523214139.GA25735@chiron.galaxy> <4B45AC2A-B400-41F7-B8A8-601E4017C452@fastmail.fm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B45AC2A-B400-41F7-B8A8-601E4017C452@fastmail.fm> Subject: Re: [9fans] no frame buffer Topicbox-Message-UUID: 29b611c6-ead6-11e9-9d60-3106f5b1d025 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