Re: N10 graphics controller

Sean Healy <jalopeura@...> wrote:
> On 10/22/2011 06:26 PM, luroh wrote:
> > Sean Healy wrote:
>>> 00:02.0 VGA compatible controller [0300]: Intel Corporation N10 
> > > Family
>>> Integrated Graphics Controller [8086:a011]
> 
> The one on my old laptop (which works fine) is:

This should be supported already, so something's going wrong. Quite 
possibly it's the regression tracked in #8001 if it only started failing 
more or less recently.

>> Looking at the commit history, support for this device was added by
>> brecht in r40319, but I am unable to find any evidence of it ever
>> being tested or working under Haiku. You may want to file a bug in
>> Trac.

Agreed. I can't really tell, for lack of hardware, either.

> 00:02.0 VGA compatible controller [0300]: Intel Corporation N10 Family 
> Integrated Graphics Controller [8086:a011]
> 00:02.1 Display controller [0380]: Intel Corporation N10 Family 
> Integrated Graphics Controller [8086:a012]
> 
> I don't know if the second controller is part of the problem or not.

Not really, only the first one is relevant.

> By checking the boot log, I was able to see that near the end of the 
> log, 'intel_extreme: uninit()' and 'intel_extreme: close()' are 
> called. 
> I would expect functions with those names to be called during 
> shutdown, 
> not at the end of startup. So either these two function calls are 
> part 
> of the problem, and I need guidance on what to look for next, or else 
> someone with a different sense for function naming wrote the driver 
> API 
> (and I still need guidance on what to look for next).

Yes, these are called during shutdown of the driver. So for some reason 
the driver isn't used any longer, i.e. due to the accelerant using it 
failed to initialize properly and getting shutdown as well.

> I used the built-in log viewer to find this information. Is there any 
> way to copy the in-memory buffer that holds the boot log onto a file? 
> Can I dd it from a device? If so, which device and from what offset?

What do you mean exactly? The built-in log viewer as in the "syslog" 
command of KDL? There's a way you can store that to a FAT formated USB 
stick from the bootloader. Otherwise just copy the syslog file as 
mentioned by Adrien.

Regards
Michael