From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mta01.eonet.ne.jp ([203.140.81.46]) by ur; Sun Jun 19 01:58:22 EDT 2016
Received: from vaioL.jitaku.localdomain (182-164-101-240f1.osk3.eonet.ne.jp [182.164.101.240])
	by mailmsa11.mozu.eo.k-opti.ad.jp  with ESMTP id u5J5wHSN028728
	for <9front@9front.org>; Sun, 19 Jun 2016 14:58:17 +0900
To: 9front@9front.org
Subject:  Re: [9front] strange behaviour of igfx and vesa
Date: Sun, 19 Jun 2016 14:58:16 +0900
From: kokamoto@hera.eonet.ne.jp
Message-ID: <9c67231286fc5f89d13515ff239f7bd1@vaioL.jitaku.localdomain>
In-Reply-To: <644ef2b1069fabf217cddbfd75b14cae@felloff.net>
References: <644ef2b1069fabf217cddbfd75b14cae@felloff.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: app-oriented lifecycle CMS controller 

>you can dump the register contents with aux/vga and compare
>native igfx vs vesa + igfx.

After checking the differences between the two, I can now
say those do not explain the blank screen.   One is the
difference of resolutions, one is the difference between
started from VGA or started from 1024x768 etc.

Kenji