Subject: NetBSD-3 support for i915GM- hang on boot
To: None <tech-x11@netbsd.org>
From: Chris Billington <cbillington@emulti.net>
List: tech-x11
Date: 08/08/2006 16:54:19
I found a message from Michael Erikson in NetBSD Tech-X11 list dated last December with patches to NetBSD for 
enabling support for the Intel 915G/GM IGD.

I recently bought a new laptop that has one of these chipsets, and can report 
the following problem:

Model is a Uniwill E30I10 with WXGA 1280x768 display, http://www.uniwill.com/products/other/m30ei0/m30ei0_print.php

NetBSD3.0 GENERIC (before the patch): boots, Intel devices 0x2592/2792 not recognised, 
X11 can't have XV or hardware cursor (or read the VESA resolutions 
correctly). It always comes up with 1024x768 and not accelerated. There is no 
agpgart so the VESA driver has to be used. 

NetBSD-3 STABLE: (CVS 6 Aug 06) hangs on boot with Generic, Generic_Laptop and 
custom kernels. I updated the system using the procedure at
http://www.s-mackie.demon.co.uk/unix-notes/NetBSD-Updates.html 

The Intel chips (HB, IGD, IGD companion) are recognised, but the system hangs 
so early in boot there is little I can do to diagnose it.
I did try both with and without agp enabled, and with and without 
ACPI/PNPBIOS, with the same result.

From a remaining fragment of Dmesg with GENERIC_LAPTOP, the last line in the 
Dmesg is 
agp0: unknown memory configuration, disabling

So it looks like the 'stolen memory' code in agp_i810.c is failing to read the memory config and the agp is disabled.

I don't know if this is relevant, but in the source there is the comment that 
/* The 915G automatically initializes the 256k gatt on boot. */
Under the Intel Windows driver, however, the 915GM is shown as 192MB memory, 
so perhaps the above statement is not always true?
There is no way in the (AMI) Bios of this machine to set the AGP aperture size.

I would be very happy to help with solving this problem in NetBSD, though I am 
no programmer, as it does seem it could affect a number of laptops. 

Please let me know what logs or other info I can provde to help fix the problem.


regards
Chris Billington