Leopard Laptops with NON-working GMA X3100

olykwon · December 26, 2009

http://www.mediafire.com/?lndq35kgzuy

Here are my outputs from Everest Ultimate and DXDiag for anyone who could assist me with my problem plzzzzzz =[[[[[ also how do i get my dsdt?

olykwon · December 27, 2009

I ran dsdt patcher and here is the session folder in a zip archive if anyone could possibly take a look at it my max resolution for this computer is 1680x1050 im pretty sure.... in my other post someone explained the fiixes i might need

http://www.insanelymac.com/forum/index.php...p;#entry1369671

http://www.mediafire.com/?efbygnn3nyo

olykwon · December 27, 2009

ALSO is this the info i need?

----------------------------------------------------

Monitor

Windows description...... Generic PnP Monitor

Manufacturer............. Microsoft

Plug and Play ID......... MS_9004

Serial number............ 9

Manufacture date......... 2002, ISO week 0

Filter driver............ monitor

-------------------------

EDID revision............ 1.3

Input signal type........ Digital

Color bit depth.......... Undefined

Display type............. RGB color

Screen size.............. Undefined or variable

Power management......... Active off/sleep

Extension blocs.......... None

-------------------------

DDC/CI................... n/a

Color characteristics

Default color space...... sRGB

Display gamma............ 3.55

Red chromaticity......... Rx 0.625 - Ry 0.340

Green chromaticity....... Gx 0.285 - Gy 0.605

Blue chromaticity........ Bx 0.148 - By 0.063

White point (default).... Wx 0.281 - Wy 0.309

Additional descriptors... None

Timing characteristics

Horizontal scan range.... 0-217kHz

Vertical scan range...... 0-60Hz

Video bandwidth.......... 120MHz

CVT standard............. Not supported

GTF standard............. Supported

Additional descriptors... None

Preferred timing......... Yes

Native/preferred timing.. 1680x1050p at 60Hz

Modeline............... "1680x1050" 119.000 1680 1728 1760 1824 1050 1053 1059 1080 +hsync +vsync

Standard timings supported

Report information

Date generated........... 12/27/2009

Software revision........ 2.43.0.822

Operating system......... 6.1.7600.2

Raw data

00,FF,FF,FF,FF,FF,FF,00,36,7F,04,90,09,00,00,00,00,0C,01,03,80,00,00,FF,2F,00,00

,A0,57,49,9B,26,

10,48,4F,00,00,00,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,7C,2E,90,90,60

,1A,1E,40,30,20,

36,00,00,00,00,00,00,1E,00,00,00,FD,00,00,3C,00,D9,0C,00,00,00,00,00,00,00,00,00

,00,00,00,00,00,

00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

,00,00,00,00,DA

------------

and using dump edid i got

---------------

DumpEDID v1.01

Web site: http://www.nirsoft.net

*****************************************************************

Registry Key : DISPLAY\MS_9004\4&df930bc&0&UID67568640

Manufacture Week : 0 / 2002

ManufacturerID : 32566 (0x7F36)

ProductID : 36868 (0x9004)

Serial Number (Numeric) : 9 (0x00000009)

EDID Version : 1.3

Display Gamma : 3.55

Maximum Resolution : 0 X 0

Support Standby Mode : No

Support Suspend Mode : No

Support Low-Power Mode : Yes

Support Default GTF : Yes

Digital : Yes

Supported Display Modes :

*****************************************************************

CharredPC · December 27, 2009

Raw data
00,FF,FF,FF,FF,FF,FF,00,36,7F,04,90,09,00,00,00,00,0C,01,03,80,00,00,FF,2F,00,00

,A0,57,49,9B,26,

10,48,4F,00,00,00,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,7C,2E,90,90,60

,1A,1E,40,30,20,

36,00,00,00,00,00,00,1E,00,00,00,FD,00,00,3C,00,D9,0C,00,00,00,00,00,00,00,00,00

,00,00,00,00,00,

00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

,00,00,00,00,DA

That's your EDID. Now use the directions in my post here to make a display override.

ariethekid · December 27, 2009

Hey guys i got my laptop finally working right with the x3100. For a while I had to make custom resolutions to make it work but I no longer have to. Although I don't have res change. I modified Natit to work on my system.

Here were my symptoms:

I could only see resolutions with a vertical resolution of 1024. Anything else lower would show colored lines on the screen. Anything higher would crash the computer. I can get my native resolution of 1400x1050 now finally with the native vanilla kexts. Although there is no 64 natit, I'm running other kexts that are 32bit only. (Tablet Driver, Lid sleep kext, etc.) My computer (T4220 Fujitsu Tablet) Doesn't like DSDT for some reason. I cannot get a DSDT with the DSDT patcher. I had to get the aml file from a bios update and use Phoenix BIOS editor to get the DSDT tables out from there. Maybe thats why its not working. Anyway, I can't get DSDT to work. I guess if I used an EFI string I could avoid the Natit.kext but I don't really want to mess with that now. Thats just an alternative for people who don't want to use 32 bit SL.

For people who get a stretched out view of the left half of the screen use this Natit with the 10.6.2 x3100 kexts. It should work for you. it did for me. This does not fix the other issues with Dells and such...This is just a patch for duallink graphics for high res laptop screens. Enjoy.

Natit.kext.zip

olykwon · December 28, 2009

thanks arie and charred im running 1280x800 using the patched fb and appleintelfb and the natit arie posted, and with the resolution fix from charred (swtchresx EDID override) now is there a way to fix the EDID issue WITHOUT switchrez? and also im having MANY troubles editing the dual link fix into my DSDT i get a compilation error i posted mine so could anyone take a look at it for me please, im going to go ahead and write up a guide on how to get 10.6.2 running on the hp touchsmar iq5xx series. im on the iq504 reporting no artifacts or tearing and although its not my max resolution 1280x800 takes up the entire screen PERFECTLY and QE/CI is working! im SO HAPPY!

ariethekid · December 28, 2009

thanks arie and charred im running 1280x800 using the patched fb and appleintelfb and the natit arie posted, and with the resolution fix from charred (swtchresx EDID override) now is there a way to fix the EDID issue WITHOUT switchrez? and also im having MANY troubles editing the dual link fix into my DSDT i get a compilation error i posted mine so could anyone take a look at it for me please, im going to go ahead and write up a guide on how to get 10.6.2 running on the hp touchsmar iq5xx series. im on the iq504 reporting no artifacts or tearing and although its not my max resolution 1280x800 takes up the entire screen PERFECTLY and QE/CI is working! im SO HAPPY!

The Natit I posted incorporates the Dual Link Fix. I will look at your DSDT and see whats wrong with it.

olykwon · December 28, 2009

The Natit I posted incorporates the Dual Link Fix. I will look at your DSDT and see whats wrong with it.

Thanks i figured you might also be able to make use of my EDID hopefully do you know if switchresX has to be used for the issue? ALSO even though my correct display resolutions ARE selectable selecting anything higher than 1280x800 results in either distorition or the vertical and horizontal lines and my system not responding

EDID: 00ffffff ffffff00 367f0490 09000000 000c0103 800000ff 2f0000a0 57499b26 10484f00 00000101 01010101 01010101 01010101 01017c2e 9090601a 1e403020 36000000 0000001e 000000fd 00003c00 d90c0000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 000000da

ariethekid · December 28, 2009

Thanks i figured you might also be able to make use of my EDID hopefully do you know if switchresX has to be used for the issue? ALSO even though my correct display resolutions ARE selectable selecting anything higher than 1280x800 results in either distorition or the vertical and horizontal lines and my system not responding

EDID: 00ffffff ffffff00 367f0490 09000000 000c0103 800000ff 2f0000a0 57499b26 10484f00 00000101 01010101 01010101 01010101 01017c2e 9090601a 1e403020 36000000 0000001e 000000fd 00003c00 d90c0000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 000000da

Did you create a resolution 1680x1050? Have you tried displaying 1680x1050 on your screen? Also backup your video drivers and go back to vanilla ones. Im assuming you have 10.6.2 so update to 1.6.6 x3100 drivers and get into switchresX and try that. Just get a resolution that will work then add your 1680x1050 resolution in switchresX. Morelikely its disabled so go in there and re-enable it. It should be in the list already. I don't need the EDID, it just does a display override. You may need the EDID for resolution changing however. I haven't figured that out yet.

Thanks i figured you might also be able to make use of my EDID hopefully do you know if switchresX has to be used for the issue? ALSO even though my correct display resolutions ARE selectable selecting anything higher than 1280x800 results in either distorition or the vertical and horizontal lines and my system not responding

EDID: 00ffffff ffffff00 367f0490 09000000 000c0103 800000ff 2f0000a0 57499b26 10484f00 00000101 01010101 01010101 01010101 01017c2e 9090601a 1e403020 36000000 0000001e 000000fd 00003c00 d90c0000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 000000da

BTW, I looked at your DSDT file. I cleaned up some errors and it should be good. The two remarks that show up when i compiled them looked very minor and irrelevant to your problem. but you never know. What did you want added to the DSDT again? I didn't modify it other than clean out bugs.

olykwon · December 28, 2009

oh for my DSDT i just need a way to fix the brightness and also the dual link fix thing

razzzor · December 29, 2009

Hi! All pages of the given forum are very interesting, but i can`t solved my problem with video.

I'm running iDeneb v.1.5.1 10.5.7 on my Sony VAIO VGN-NR31E with GM960/965 x3100

Device id: 0x2a02

Revision id: 0x000c

I installed Errandwolfe's *and Slashack`s kext, but i cant change resolution on 1280*800. Only 1024*768, 1280*1024, 1280*960 etc...

How I can solve this problem whith DSDT? )

olykwon · December 29, 2009

i for the most part only needed the modified natit kext that includes the dual link fix and stock 10.6.2 kexts from Hazaard. try downloading the 10.6.0 + 6.1,6.2 updates you can find it in the usual places then try using the fixes, natit and EDID injection(with switch res X) and you SHOULD be somewhat good to go im able to get 1600x1000 but not my native 1650x1080 if you need the display override file to modify the values ill post mine, i dont think this is the BEST fix but it is ALOT better than trying to figure out that confusing as hell DSDT file. someones looking at mine now trying to inject the brightness and dual link fix so i can kick NATIT to the curb XD does anyone know if i can remove switchrezX after i do the EDID fix with it because it expires and im not looking forward to reinstalling the OS when it doess =[[[

Zprood · January 1, 2010

guys, i am using the intel Graphics x3100 on snow leopard 10.6.2 ,and i can open QE&CI ,also i use natit and correct some errors in the dsdt by the hack ,such as add the Device (PEGP) and another Device is GFX0 is not added, like:

 Name (_ADR, 0x00010000)
			Device (GFX)
			{
				Name (_ADR, Zero)
				Method (_DSM, 4, NotSerialized)
				{
					Store (Package (0x54)
						{
							"device_type", 
							Buffer (0x08)
							{
								"display"
							}, 

							"model", 
							Buffer (0x0D)
							{
								"X3100"
							}, 

							"built-in", 
							Buffer (One)
							{
								0x01
							}, 

							"AAPL,backlightRestore", 
							Buffer (0x04)
							{
								0x01, 0x00, 0x00, 0x00
							}, 

							"AAPL,DisplayConfig", 
							Buffer (0x20)
							{
								/* 0000 */	0x13, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 
								/* 0008 */	0x21, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
								/* 0010 */	0x41, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
								/* 0018 */	0x81, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
							}, 

							"AAPL,HasLid", 
							Buffer (0x04)
							{
								0x01, 0x00, 0x00, 0x00
							}, 

							"AAPL,HasPanel", 
							Buffer (0x04)
							{
								0x01, 0x00, 0x00, 0x00
							}, 

							"AAPL,NumDisplays", 
							Buffer (0x04)
							{
								0x04, 0x00, 0x00, 0x00
							}, 

							"AAPL,NumFramebuffers", 
							Buffer (0x04)
							{
								0x02, 0x00, 0x00, 0x00
							}, 

							"AAPL,SelfRefreshSupported", 
							Buffer (0x04)
							{
								0x01, 0x00, 0x00, 0x00
							}, 

							"AAPL,aux-power-connected", 
							Buffer (0x04)
							{
								0x01, 0x00, 0x00, 0x00
							}, 

							"AAPL,backlight-control", 
							Buffer (0x04)
							{
								0x01, 0x00, 0x00, 0x00
							}, 

							"AAPL00,blackscreen-preferences", 
							Buffer (0x04)
							{
								0x00, 0x00, 0x00, 0x08
							}, 

							"AAPL01,BacklightIntensity", 
							Unicode ("d"), 
							"AAPL01,blackscreen-preferences", 
							Buffer (0x04)
							{
								0x00, 0x00, 0x00, 0x08
							}, 

							"AAPL01,BootDisplay", 
							Buffer (0x04)
							{
								0x01, 0x00, 0x00, 0x00
							}, 

							"AAPL01,CurrentDisplay", 
							Buffer (0x04)
							{
								0x00, 0x00, 0x00, 0x00
							}, 

							"AAPL01,DataJustify", 
							Buffer (0x04)
							{
								0x01, 0x00, 0x00, 0x00
							}, 

							"AAPL01,Depth", 
							Unicode (" "), 
							"AAPL01,Dither", 
							Buffer (0x04)
							{
								0x00, 0x00, 0x00, 0x00
							}, 

							"AAPL01,DualLink", 
							Buffer (0x04)
							{
								0x01, 0x00, 0x00, 0x00
							}, 

							"AAPL01,EDID", 
							Buffer (0x80)
							{
								/* 0000 */	0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 
								/* 0008 */	0x06, 0x10, 0x5F, 0x9C, 0x00, 0x00, 0x00, 0x00, 
								/* 0010 */	0x08, 0x10, 0x01, 0x03, 0x80, 0x1D, 0x12, 0x78, 
								/* 0018 */	0x0A, 0x2F, 0x30, 0x97, 0x58, 0x53, 0x8B, 0x29, 
								/* 0020 */	0x25, 0x50, 0x54, 0x00, 0x00, 0x00, 0x01, 0x01, 
								/* 0028 */	0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 
								/* 0030 */	0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0xBC, 0x1B, 
								/* 0038 */	0x00, 0xA0, 0x50, 0x20, 0x17, 0x30, 0x30, 0x20, 
								/* 0040 */	0x36, 0x00, 0x1E, 0xB3, 0x10, 0x00, 0x00, 0x18, 
								/* 0048 */	0x00, 0x00, 0x00, 0x0F, 0x00, 0x06, 0x10, 0x20, 
								/* 0050 */	0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
								/* 0058 */	0x0A, 0x20, 0x00, 0x00, 0x00, 0xFE, 0x00, 0x4C, 
								/* 0060 */	0x54, 0x31, 0x33, 0x33, 0x57, 0x58, 0x31, 0x2D, 
								/* 0068 */	0x00, 0x43, 0x41, 0x31, 0x00, 0x00, 0x00, 0xFE, 
								/* 0070 */	0x00, 0x43, 0x6F, 0x6C, 0x6F, 0x72, 0x20, 0x4C, 
								/* 0078 */	0x43, 0x44, 0x0A, 0x20, 0x20, 0x20, 0x00, 0xC2
							}, 

							"AAPL01,Height", 
							Buffer (0x04)
							{
								0x20, 0x03, 0x00, 0x00
							}, 

							"AAPL01,Interlace", 
							Buffer (0x04)
							{
								0x00, 0x00, 0x00, 0x00
							}, 

							"AAPL01,Inverter", 
							Buffer (0x04)
							{
								0x00, 0x00, 0x00, 0x00
							}, 

							"AAPL01,InverterCurrent", 
							Buffer (0x04)
							{
								0x00, 0x00, 0x00, 0x00
							}, 

							"AAPL01,InverterFrequency", 
							Buffer (0x04)
							{
								0x08, 0x52, 0x00, 0x00
							}, 

							"AAPL01,IODisplayMode", 
							Buffer (0x04)
							{
								0x00, 0x10, 0x00, 0x80
							}, 

							"AAPL01,LinkFormat", 
							Buffer (0x04)
							{
								0x00, 0x00, 0x00, 0x00
							}, 

							"AAPL01,LinkType", 
							Buffer (0x04)
							{
								0x00, 0x00, 0x00, 0x00
							}, 

							"AAPL01,Pipe", 
							Buffer (0x04)
							{
								0x01, 0x00, 0x00, 0x00
							}, 

							"AAPL01,PixelFormat", 
							Buffer (0x04)
							{
								0x00, 0x00, 0x00, 0x00
							}, 

							"AAPL01,Refresh", 
							Unicode (";"), 
							"AAPL01,Stretched", 
							Buffer (0x04)
							{
								0x00, 0x00, 0x00, 0x00
							}, 

							"AAPL01,T0", 
							Buffer (0x04)
							{
								0x00, 0x00, 0x00, 0x00
							}, 

							"AAPL01,T1", 
							Buffer (0x04)
							{
								0x01, 0x00, 0x00, 0x00
							}, 

							"AAPL01,T2", 
							Buffer (0x04)
							{
								0xC8, 0x00, 0x00, 0x00
							}, 

							"AAPL01,T3", 
							Buffer (0x04)
							{
								0xC8, 0x00, 0x00, 0x00
							}, 

							"AAPL01,T4", 
							Buffer (0x04)
							{
								0x01, 0x00, 0x00, 0x00
							}, 

							"AAPL01,T5", 
							Buffer (0x04)
							{
								0x00, 0x00, 0x00, 0x00
							}, 

							"AAPL01,T6", 
							Buffer (0x04)
							{
								0x90, 0x01, 0x00, 0x00
							}, 

							"AAPL01,Width", 
							Buffer (0x04)
							{
								0x00, 0x05, 0x00, 0x00
							}
						}, Local0)
					DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
					Return (Local0)
				}
			}

but when i start the computer ,i see the warning in the kernel.log

Kernel.log

natit info

Graphics info

here is my dsdt DSDT.dsl.zip

thank for your help.......

CharredPC · January 1, 2010

tmacyunn:

So, you've put the entire video section of a Macbook into your DSDT, plus are injecting the same values using Natit? ...may I ask why? Are you also using an alternate AppleIntelX3100FB? Also, that DSDT edit may very well be making no difference at all, if your actual video device is at 0x00020000, like mine and others I've seen. X3100-based Macbooks are a bit different; the display devices are attached to 0x00010000.

My X3100 works great in 10.6.2, using stock drivers, without Natit or any DSDT adjustment (besides the duallink line for my 1440x900 LCD, and the Override to keep the EDID found). What problems were you having that made you try this combination?

i for the most part only needed the modified natit kext that includes the dual link fix and stock 10.6.2 kexts from Hazaard. try downloading the 10.6.0 + 6.1,6.2 updates you can find it in the usual places then try using the fixes, natit and EDID injection(with switch res X) and you SHOULD be somewhat good to go im able to get 1600x1000 but not my native 1650x1080 if you need the display override file to modify the values ill post mine, i dont think this is the BEST fix but it is ALOT better than trying to figure out that confusing as hell DSDT file. someones looking at mine now trying to inject the brightness and dual link fix so i can kick NATIT to the curb XD does anyone know if i can remove switchrezX after i do the EDID fix with it because it expires and im not looking forward to reinstalling the OS when it doess =[[[

If the other fellow can't do it, just post your DSDT and I'll add the duallink fix. You don't actually need SwitchResX at all, it's simply a useful tool for helping setting up a Display Override. You can get rid of it anytime you like, it's the Display Override you created doing the work, not SwitchResX. If you're worried, you can even backup the override.

Good luck on the brightness. You won't get OSX's brightness control, but maybe something specific to your laptop can enable some hotkeys to adjust things manually, like mine.

Zprood · January 2, 2010

tmacyunn:

So, you've put the entire video section of a Macbook into your DSDT, plus are injecting the same values using Natit? ...may I ask why? Are you also using an alternate AppleIntelX3100FB? Also, that DSDT edit may very well be making no difference at all, if your actual video device is at 0x00020000, like mine and others I've seen. X3100-based Macbooks are a bit different; the display devices are attached to 0x00010000.

My X3100 works great in 10.6.2, using stock drivers, without Natit or any DSDT adjustment (besides the duallink line for my 1440x900 LCD, and the Override to keep the EDID found). What problems were you having that made you try this combination?

If the other fellow can't do it, just post your DSDT and I'll add the duallink fix. You don't actually need SwitchResX at all, it's simply a useful tool for helping setting up a Display Override. You can get rid of it anytime you like, it's the Display Override you created doing the work, not SwitchResX. If you're worried, you can even backup the override.

Good luck on the brightness. You won't get OSX's brightness control, but maybe something specific to your laptop can enable some hotkeys to adjust things manually, like mine.

So ,maybe i do something wrong in the dsdt,because when i install snow leopard 10A432 on my laptop ,after it finished ,i reboot and it goes black screen.also i try to reboot again by force sometimes. it log in system formally.But if i shut down my laptop restart it .guess what ?black screen again. so , i add the natit.kext (i do not add some values) and alternate AppleIntelX3100FB version 5.1.8 size 86kb ,it performs very well.And now i have upgraded 10.6.2, do something about dsdt to solve sleep problem and so on.Yes ,i can control the brightness and the sound with my hotkeys.my x3100 has some Devices,like Device PEGP(0x00010000) ,GFX0(0x00020000) ,The display resolution is 1280x800.i appreciate your reply.i post some information about my x3100.thank in advance.

dsdt.dsl.zip

this is the Kernel log:

an  2 12:52:08 localhost kernel[0]: BSD root: disk0s8, major 14, minor 7
Jan  2 12:52:08 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete
Jan  2 12:52:15 localhost kernel[0]: Waiting for DSMOS...
Jan  2 12:52:15 localhost kernel[0]: systemShutdown false
Jan  2 12:52:19 zheng-yuns-MacBook-Pro kernel[0]: Warning - kext com.apple.driver.AppleIntelGMAX3100FB has immediate dependencies on both com.apple.kernel* and com.apple.kpi.* components; use only one style.
Jan  2 12:52:19 zheng-yuns-MacBook-Pro kernel[0]: Previous Shutdown Cause: 0
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: wl0: Broadcom BCM4315 802.11 Wireless Controller
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: 5.10.91.19
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: AppleUSBEthernet 0x23bc9000 init
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: AppleUSBEthernet: - Version number 2.1.0, Input buffers 64, Output buffers 64
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Alkor: Starting.
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Chosen model GMA X3100
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Alkor: Setting AAPL01,DataJustify=<data not shown>
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Alkor: Setting AAPL01,Depth=<data not shown>
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Alkor: Setting AAPL,NumDisplays=<data not shown>
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Alkor: Setting built-in=<data not shown>
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Alkor: Setting AAPL01,Pipe=<data not shown>
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Alkor: Setting AAPL,HasPanel=<data not shown>
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Alkor: Setting AAPL,SelfRefreshSupported=<data not shown>
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Alkor: Setting AAPL,NumFramebuffers=<data not shown>
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Alkor: Starting.
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Chosen model GMA X3100
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Alkor: Setting AAPL01,DataJustify=<data not shown>
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Alkor: Setting AAPL01,Depth=<data not shown>
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Alkor: Setting AAPL,NumDisplays=<data not shown>
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Alkor: Setting built-in=<data not shown>
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Alkor: Setting AAPL01,Pipe=<data not shown>
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Alkor: Setting AAPL,HasPanel=<data not shown>
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Alkor: Setting AAPL,SelfRefreshSupported=<data not shown>
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Alkor: Setting AAPL,NumFramebuffers=<data not shown>
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: commands[11] = 0
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Set Timeout Starting
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Set Timeout to loop Failed 0
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Set Timeout to loop Ending
Jan  2 12:52:20 zheng-yuns-MacBook-Pro kernel[0]: Click Timer Starting

CharredPC · January 3, 2010

So ,maybe i do something wrong in the dsdt,because when i install snow leopard 10A432 on my laptop ,after it finished ,i reboot and it goes black screen.also i try to reboot again by force sometimes. it log in system formally.But if i shut down my laptop restart it .guess what ?black screen again. so , i add the natit.kext (i do not add some values) and alternate AppleIntelX3100FB version 5.1.8 size 86kb ,it performs very well.And now i have upgraded 10.6.2, do something about dsdt to solve sleep problem and so on.Yes ,i can control the brightness and the sound with my hotkeys.my x3100 has some Devices,like Device PEGP(0x00010000) ,GFX0(0x00020000) ,The display resolution is 1280x800.i appreciate your reply.i post some information about my x3100.thank in advance.

This sounds like you DON'T need the DSDT / dual link fix (if your maximum resolution is truly 1280x800). As far as I know, that issue only affects WSXGA+ and higher LCD's. If you did need it, then the only thing to add to your DSDT is the following, placed directly under the GFX0 (0x00020000) line:

Method (_DSM, 4, NotSerialized)
				{
					Store (Package ()
						   {
							"AAPL01,DualLink",
							Buffer (0x04)
							{
								0x01, 0x00, 0x00, 0x00
							}
					   }, Local0)
					DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
					Return (Local0)
				}

As you describe it, the problem sounds more like poor EDID detection, same as my laptop. Yes, for some reason the alternate drivers are better at picking up the EDID (or maybe just have better defaults if the EDID isn't found). You can probably just do what I do, though, and use stock drivers with a Display Override. I explain how to create one a page or two back in this thread. Then when your EDID isn't picked up, the Override supplies it, so you never get a black screen.

Zprood · January 3, 2010

This sounds like you DON'T need the DSDT / dual link fix (if your maximum resolution is truly 1280x800). As far as I know, that issue only affects WSXGA+ and higher LCD's. If you did need it, then the only thing to add to your DSDT is the following, placed directly under the GFX0 (0x00020000) line:
Method (_DSM, 4, NotSerialized)
				{
					Store (Package ()
						   {
							"AAPL01,DualLink",
							Buffer (0x04)
							{
								0x01, 0x00, 0x00, 0x00
							}
					   }, Local0)
					DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
					Return (Local0)
				}
As you describe it, the problem sounds more like poor EDID detection, same as my laptop. Yes, for some reason the alternate drivers are better at picking up the EDID (or maybe just have better defaults if the EDID isn't found). You can probably just do what I do, though, and use stock drivers with a Display Override. I explain how to create one a page or two back in this thread. Then when your EDID isn't picked up, the Override supplies it, so you never get a black screen.

Thank you! But,i add this code to dsdt.and remove the Natit,x3100fb (version 5.18),replace the original x3100fb.After comipling and replacing dsdt.aml ,i reboot ,the black screen comes again.My Graphic maximum resolution is 1280x800,also i try to get the EDID in the windows,but i only get few information .can`t use your EDID method. It is so bad.i do not know why adding the Natit and replacing x311fb can make a difference.

bozon42 · January 4, 2010

Hello all, in my post 742 I described my problems with Hazard's distro and with X3100.

Main problems:

no 64bit mode

in 32bit mode no sleep/wake, no reboot, no shutdown possible, no QE/CI

In http://www.insanelymac.com/forum/index.php...7396&st=500

you see my steps of installation.

1.

Can I somehow force the system to us dsdt fixes? I so how?

2.

Can somebody have a look at my dsdt?

(so far not created and posted).

Thanks and regards.

bozon42

CharredPC · January 4, 2010

Hello all, in my post 742 I described my problems with Hazard's distro and with X3100.

Main problems:

no 64bit mode

in 32bit mode no sleep/wake, no reboot, no shutdown possible, no QE/CI

In http://www.insanelymac.com/forum/index.php...7396&st=500

you see my steps of installation.

1.

Can I somehow force the system to us dsdt fixes? I so how?

2.

Can somebody have a look at my dsdt?

(so far not created and posted).

Thanks and regards.

bozon42

Sorry, it has to be said... problem #1 is you're using a distro, not retail. This makes it much harder to troubleshoot, because now no one has any idea what drivers are on your system, which ones are original, what's been modified...

Secondly, your signature suggests that you're talking about your Acer Extensa 5220 with SL 10.6.1 on it. The 10.6.2 update contained X3100 64-bit drivers, so you won't have any success there until you update. I'm not sure how well the update works for a hacked distro- you'll have to do some research on that one.

Thirdly, if you're running the cobbled ethernet driver that requires promiscuous mode, you'll never have sleep. You have to choose one or the other. Running that driver completely kills sleep, though there's probably other things stopping it as well.

Your 5220 should be nearly the same thing as my Extensa 5620. I run retail 10.5.8 and 10.6.2 with less than five extra kext files. You really don't need all those extra patches and fixes. I'd be happy to look at your DSDT once you have a specific problem to fix in it. Right now, I doubt anyone would know where to start.

bozon42 · January 5, 2010

Hello CharredPC,

thanks for reply.

I have tried Hazard's distro with 10.6.1 and 10.6.2 updates at one step.

Maybe I should try only with 10.6.1 (or even with the base 10.6 only) and see how my system behaves during upgrades.

Maybe I should take into account netkas' remark about 10.6.2 update.

If all this fail I will try guid install with original SL DVD (though I have never tried it and not sure how to create 4system in guid - win7,leo, snowleo and ubuntu) - there are some pages I have found on the net.

Concerning similarity between 5220 and 5620 - I think the big difference is that AFIAK my 5220 has only one Core - and I am not sure whether this can be a problem for Snow Leo installation.

non-working Sleep is not a problem - only reboot and shutdown annoy me.

Regards,

bozon42

Zprood · January 7, 2010

This sounds like you DON'T need the DSDT / dual link fix (if your maximum resolution is truly 1280x800). As far as I know, that issue only affects WSXGA+ and higher LCD's. If you did need it, then the only thing to add to your DSDT is the following, placed directly under the GFX0 (0x00020000) line:
Method (_DSM, 4, NotSerialized)
				{
					Store (Package ()
						   {
							"AAPL01,DualLink",
							Buffer (0x04)
							{
								0x01, 0x00, 0x00, 0x00
							}
					   }, Local0)
					DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
					Return (Local0)
				}
As you describe it, the problem sounds more like poor EDID detection, same as my laptop. Yes, for some reason the alternate drivers are better at picking up the EDID (or maybe just have better defaults if the EDID isn't found). You can probably just do what I do, though, and use stock drivers with a Display Override. I explain how to create one a page or two back in this thread. Then when your EDID isn't picked up, the Override supplies it, so you never get a black screen.

Hi man .i succeed .Thank you so much .i follow the method what you posted .Also, i install the software EDID view,but it can`t give any information about the EDID ,and i have the other tool named Monitor EDID. It works great.i add the information ,replace and reboot.Everything works perfect. So,i can use the kexts originally. But i have a question about the default-resolution you have set in the file "DisplayProductID-717".Because,when i log in system after replaced and reboot ,the resolution is 1440x900.

CharredPC · January 7, 2010

I have my default resolution set as 1440x900, because that's my highest available (WSXGA+ LCD). You can change that or even get rid of the default resolution if you like, the only required info is the EDID. Glad this worked for you!

Hi man .i succeed .Thank you so much .i follow the method what you posted .Also, i install the software EDID view,but it can`t give any information about the EDID ,and i have the other tool named Monitor EDID. It works great.i add the information ,replace and reboot.Everything works perfect. So,i can use the kexts originally. But i have a question about the default-resolution you have set in the file "DisplayProductID-717".Because,when i log in system after replaced and reboot ,the resolution is 1440x900.

Zprood · January 8, 2010

I have my default resolution set as 1440x900, because that's my highest available (WSXGA+ LCD). You can change that or even get rid of the default resolution if you like, the only required info is the EDID. Glad this worked for you!

Thanks.i also use it to solve the same problem on leo 10.5.8 ,i think this is the best way to solve the black screen.Anyway. i go other website to search no good result, like projectosx infinitemac .But i can see someone correct dsdt the issue can be solved.like Slice etc.So you do a great job.And this morning i notice that when i log in the system ,the wallpaper is changed default,the display color setting does not show color description Adobe RGB (1998) etc.it seems can not save the info .

CharredPC · January 8, 2010

And this morning i notice that when i log in the system ,the wallpaper is changed default,the display color setting does not show color description Adobe RGB (1998) etc.it seems can not save the info .

What you're describing might be the difference between your EDID being detected or not. If it's detected, you use one display profile. When it's not, it falls back on the Display Override, which is a different display profile. Basically, OSX sees it as two separate screens. So you have to set your wallpaper / color settings in each case. If you set them both the same, you won't even notice the difference when your Override is used or not. Both are saved fine for me, just separately.

Zprood · January 8, 2010

What you're describing might be the difference between your EDID being detected or not. If it's detected, you use one display profile. When it's not, it falls back on the Display Override, which is a different display profile. Basically, OSX sees it as two separate screens. So you have to set your wallpaper / color settings in each case. If you set them both the same, you won't even notice the difference when your Override is used or not. Both are saved fine for me, just separately.

Thanks, I delete some info in the file of DisplayProductID-717.So when i restore them ,it is clear,my Graghics works fine.OSX can detect my screen.Nice~

Leopard Laptops with NON-working GMA X3100

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites