From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mta01.eonet.ne.jp ([203.140.81.46]) by ur; Sat Jul  9 02:28:05 EDT 2016
Received: from vaioL.jitaku.localdomain (101-141-37-76f1.osk3.eonet.ne.jp [101.141.37.76])
	by mailmsa11.mozu.eo.k-opti.ad.jp  with ESMTP id u696Rw6R023800
	for <9front@9front.org>; Sat, 9 Jul 2016 15:27:59 +0900
To: 9front@9front.org
Subject:  Re: [9front] core-i3 and vesa mode
Date: Sat, 9 Jul 2016 15:27:58 +0900
From: kokamoto@hera.eonet.ne.jp
Message-ID: <a8f8a4f9ded39ccbae0352b6b348e2ff@vaioL.jitaku.localdomain>
In-Reply-To: <adbd1412b31f101687ac2e2ac75aa814@titan.jitaku.localdomain>
References: <218cc5ab77df81bd55ea5f71540952e6@felloff.net>
	<adbd1412b31f101687ac2e2ac75aa814@titan.jitaku.localdomain>
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: patented distributed out-scaling-based app 

Sorry, I was wrong!

As the system stalled after started messages of:
post...

init: starting /bin/rc, I made easy decision.

Now I'm searching /sys/src/cmd/aux/vga/igfx.c, and found
this system is not reliable, which means stalls verious source
position at individual running.  The most long traveled of the system is as follows:
(in snarf() function, and made 0152 belong to TypeIVB)
-----from here------
	for(x=0; x<igfx->npipe; x++)
		snarfpipe(igfx, x);

print("OK snarfpipe()\n");
print("Number of elements of edid = %d\n", nelem(vga->edid));


	for(x=0; x<nelem(vga->edid); x++){
		Modelist *l;

		switch(x){
		case PortVGA:

print("OK, snarfing edid for PortVGA\n");

			vga->edid[x] = snarfgmedid(igfx, 2, 0x50); <=======HERE

print("OK, snarfed edid for PortVGA\n");

			break;
		case PortLCD:
------to here------.

The system never runs ahead and system stalls at the line maked arrow above.

Kenji