I first want to thank you for putting so much effort into this.
Last week I was sick of not being able to have graphics on i5-460M, so I switched my laptop to one with a i5-2410m.
This particular CPU has the intel HD 3000 graphics chip, with hw id 116.
After a week of trial and error (Snow Leopard worked fine, but Lion didn't want to show graphics), I have a full resolution, QE/CI enabled laptop, thanks to this 8.1 mbp SMBIOS with the SMboardproduct ID correctly set).
My laptop only has a VGA output, and of course the internal display.
My Lion install would keep hanging every once in a while, especially after trying to save a document. That is when I found this thread, and went on trying to fix the errors.
[codebox]adr: 173356818-09-11 18:01:29,000 kernel: stampWait: Overflowed checking for stamp 0x1191 on Main ring: called from waiting for blt buffer (3D blt)
18-09-11 18:01:29,000 kernel: timestamp = 0x1171
18-09-11 18:01:29,000 kernel: **** Debug info for apparent hang in Main graphics engine ****
18-09-11 18:01:29,000 kernel: ring head = 0x028028bc, wrap count = 0x14
18-09-11 18:01:29,000 kernel: ring tail = 0x00003da8 ring control = 0x00003401 enabled, auto report disabled, not waiting, semaphore is waiting, length = 0x004 4KB pages
18-09-11 18:01:29,000 kernel: timestamps = 0x1173
18-09-11 18:01:29,000 kernel: Semaphore register values:
18-09-11 18:01:29,000 kernel: VRSYNC: (0x12044) = 0x1174
18-09-11 18:01:29,000 kernel: BRSYNC: (0x22040) = 0x0
18-09-11 18:01:29,000 kernel: RVSYNC: (0x 2040) = 0x0
18-09-11 18:01:29,000 kernel: BVSYNC: (0x22044) = 0x0
18-09-11 18:01:29,000 kernel: RBSYNC: (0x 2044) = 0x0
18-09-11 18:01:29,000 kernel: VBSYNC: (0x12040) = 0x0
18-09-11 18:01:29,000 kernel: trying to clear semaphore wait on Main ring
18-09-11 18:01:29,000 kernel: After attempt to clear semaphore wait = 0x00003001 no longer waiting
18-09-11 18:01:29,000 kernel: kIPEHR: 0x2000000
18-09-11 18:01:29,000 kernel: kINSTDONE: 0xfffffffb
18-09-11 18:01:29,000 kernel: kINSTDONE_1: 0x3bffffec
I looked in the IORegExplorer at the Framebuffer Display and it showed 00080000 at the IODisplayConnectFlags. I figured my primary output is an HDMI connector.
I first tried bcc9's modifications, but they did not resolve anything (I was expecting that). So I edited the HDMI port as the first connector, and left 2 DP's after that. Still no solution to the ring-stuck error.
Since then I removed ALL connectors, except for the HDMI one, so now my hex file looks like this:
[codebox]0000000: 0102 0100 1007 0000 1007 0000 ............
000000c: 0406 0000 0008 0000 0600 0000 ........0...
0000018: 0000 0000 0000 0000 0000 0000 ............
0000024: 0000 0000 0000 0000 0000 0000 ............
0000030: 0000 0000 0000 0000 0000 0000 ............
and STILL I get the ring-stalling errors.
Can someone identify what I am doing wrong?
I thought it was suspicious when I looked at the SystemInfo page, and my display showed spdisplays_display (built in) as its default screen. Is this correct? I do not use any device-property EFI strings. I currently run the latest 10.7.2 beta.
Thanks in advance! And please keep up the good work!