Helped need with GMX3100 Driver on Lenovo IdeaPad U110 and Snow Leopard 10.6.2

pp611 · January 12, 2010

I installed the Snow Leopard's DVD prepared by Hazard onto Lenovo Ideapad U110. It's getting very close. I can boot with the default VGA driver but could not load any GMX 3100 driver. Sound card works fine. Wired

network worked with an Apple USB Ethernet Adapter and once connected to the machine, OSX automatically detected it and asked if to install the driver. However I could not graphic card driver work, which is really necessary to run the display in 1366x768 resolution, otherwise everything is stretched a bit in the 1024x768 resolution. Here is the situation.

Boot in 64-bit mode with AppleIntelGMAX3100.kext and verbose mode. I can see the color wheel spinning and can even move the mouse over the black backround with system log text. This looks it getting very close.
Boot in 32-bit mode always getting into a blue screen and hang, with or without AppleIntelGMAX3100.kext.

What is the difference of AppleIntelGMAX3100FB.kext AppleIntelGMAX3100.kext? I noticed that AppleIntelGMAX3100FB.kext and and Natis.kext only support 32-bit mode.

The Lenovo U110 comes with a GMX3100 card with Device ID: 0x2a02 Revision ID: 0x0003.

Please please help. It's getting so close....

anselmoso · January 12, 2010

I installed the Snow Leopard's DVD prepared by Hazard onto Lenovo Ideapad U110. It's getting very close. I can boot with the default VGA driver but could not load any GMX 3100 driver. Sound card works fine. Wired
network worked with an Apple USB Ethernet Adapter and once connected to the machine, OSX automatically detected it and asked if to install the driver. However I could not graphic card driver work, which is really necessary to run the display in 1366x768 resolution, otherwise everything is stretched a bit in the 1024x768 resolution. Here is the situation.

Boot in 64-bit mode with AppleIntelGMAX3100.kext and verbose mode. I can see the color wheel spinning and can even move the mouse over the black backround with system log text. This looks it getting very close.

Boot in 32-bit mode always getting into a blue screen and hang, with or without AppleIntelGMAX3100.kext.

What is the difference of AppleIntelGMAX3100FB.kext AppleIntelGMAX3100.kext? I noticed that AppleIntelGMAX3100FB.kext and and Natis.kext only support 32-bit mode.

The Lenovo U110 comes with a GMX3100 card with Device ID: 0x2a02 Revision ID: 0x0003.

Please please help. It's getting so close....

My experiences are the following:

- you only need the AppleIntelGMAX3100FB.kext, the other one isn't necessary

- there are several AppleIntelGMAX3100FB.kexts by several people you can try out in this (sub-)forum, one should probably work

- You can try booting with the "arch=i386 -x -f -v" flag, that often helps getting the driver working, afterwards you can boot normal with "arch=i386 -f -v" flags

- The safest way to get native resolution working is by using a patched grub in my experience. Cause with these patches 3100 kexts I often had instabilities while using OSX, applications crashing and stuff...when playing youtube videos for example or using Skype. To use this method you'll have to install Linux and OSX parallel on your notebook, for example a simple Ubuntu 9.10 installation with 4GIG partition on the first partition and OSX on the 2nd. Then you'll have to install a patched grub into your Ubuntu installation which then will set your resolution at boot time. Then you don't need any patched kexts for graphics in OSX and the system runs very stable in my experience.

The only thing I still can't get working is sleep mode on my Inspiron 1545.

Here's a howto for the patched grub method

http://deviato.wordpress.com/2009/09/03/ho...l-with-leopard/

And the previous howto

http://deviato.wordpress.com/2009/07/24/ho...-inspiron-1545/

Works with Snow Leopard, I'm using this method myself.

CharredPC · January 12, 2010

Back up a second here.

After installing SL, everything worked, but you're just in the wrong resolution? ...why does everyone jump on "I need new drivers!!!" as a first option?

First thing to do, if you haven't already, is to update to 10.6.2. That update gives you X3100 64-bit drivers. Secondly, check and see if QE is enabled without changing out any kexts. If so, YOUR ORIGINAL STOCK DRIVERS ARE WORKING FINE. Do NOT touch them. The reason for the 1024x768 resolution is a common EDID / display data issue. My X3100 has the same thing (same exact device id as yours), and it's fixable. I use all stock drivers and just add in a Display Override. A how-to is available a couple pages back in the stickied X3100 thread.

Once OSX understands what display you're using, all available resolutions will show up. Sometimes different (older) drivers can pick up the EDID better than others, but it's just a hacky cob-job mishmash you'll have to redo after each update, instead of an actual solution.

pp611 · January 13, 2010

Back up a second here.

After installing SL, everything worked, but you're just in the wrong resolution? ...why does everyone jump on "I need new drivers!!!" as a first option?

First thing to do, if you haven't already, is to update to 10.6.2. That update gives you X3100 64-bit drivers. Secondly, check and see if QE is enabled without changing out any kexts. If so, YOUR ORIGINAL STOCK DRIVERS ARE WORKING FINE. Do NOT touch them. The reason for the 1024x768 resolution is a common EDID / display data issue. My X3100 has the same thing (same exact device id as yours), and it's fixable. I use all stock drivers and just add in a Display Override. A how-to is available a couple pages back in the stickied X3100 thread.

Once OSX understands what display you're using, all available resolutions will show up. Sometimes different (older) drivers can pick up the EDID better than others, but it's just a hacky cob-job mishmash you'll have to redo after each update, instead of an actual solution.

When I actually got display (64-bit mode, with AppleIntelGMAX3100.kext removed) work the System Profile shows no kext loaded for the graphic driver. So the stock driver was not working.

The system has already been updated to 10.6.2. As I mentioned it looks like AppleIntelGMAX3100.kext was loaded in the 64-bit mode but the system won't hang with black background and a color spinning wheel which can move along with mouse movement.

In 32-bit mode system seems have AppleIntelGMAX3100FB.kext loaded but hangs with a blue screen.

Noticed that AppleIntelGMAX3100.kext is for 64-bit and AppleIntelGMAX3100FB.kext for 32-bit. Is that the only difference? How to do Display Override?

I am on a trip now and try your method and anselmoso's method over the weekend.

pp611 · January 17, 2010

Same results after several tries over the weekend.

CharredPC: I've read several of your posts and would like to ask several more questions. In one post you mentioned to try a different FB and Natis would solve the problem, would this work for 10.6? Any working FB and Native driver set you can point to?

I tried to follow the override method in your other post but was not sure what to do. I used SiwtchResX and exported an EDID but don't know what to add to the file DisplayProductID-717 (got the same file name as yours). The exported EDID file looks like: (I changed the default resolution to 1366x768 before exporting)

DDC block report generated by SwitchResX version 4.0.3 for display
Unknown Monitor


-----------------------------------------------------
------------------- RAW DATA ------------------------
-----------------------------------------------------
     0  1  2  3  4  5  6  7  8  9  A  B  C  D  E  F
-----------------------------------------------------
0  | 00 FF FF FF FF FF FF 00 00 00 17 07 00 00 00 00
1  | 0A 0A 01 01 0C 1E 17 BE E8 2D C9 A0 57 47 98 27
2  | 12 48 4C 00 00 00 01 01 01 01 01 01 01 01 01 01
3  | 01 01 01 01 01 01 00 00 00 FE 00 53 52 58 46 61
4  | 6B 65 45 44 49 44 0A 20 01 01 01 01 01 01 01 01
5  | 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
6  | 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
7  | 01 01 01 01 01 01 01 01 01 01 01 01 01 01 00 5A

-----------------------------------------------------
<  00FFFFFF FFFFFF00 00001707 00000000 0A0A0101 0C1E17BE E82DC9A0 57479827 12484C00 00000101 01010101 01010101 01010101 01010000 00FE0053 52584661 6B654544 49440A20 01010101 01010101 01010101 01010101 01010101 01010101 01010101 01010101 01010101 01010101 01010101 01010101 01010101 0101005A	> 

-----------------------------------------------------
Valid EDID block: checksum passed

-----------------------------------------------------
------------------- MAIN EDID BLOCK -----------------
-----------------------------------------------------

EDID Version........1.1
Manufacturer........@@@
Product Code........5895 (1707) (0717) 
Serial Number.......00000000

Manufactured........Week 10 of year 2000
Max H Size..........30 cm
Max V Size..........23 cm
Gamma...............2.90

Display Supported Features:
---------------------------
Power Management: Active off	Power Management: Suspend	Power Management: Standby

Display type:
------------- 
RGB color display
Display is non continuous frequency
Default color space is not sRGB standard


Input signal & sync:
-------------------- 
Analog input with: 	0.700V / 0.300V
Separate Sync
Composite Sync


Color info:
----------- 
Red x = 0.625  Green x = 0.280  Blue x = 0.155  White x = 0.283
Red y = 0.342  Green y = 0.595  Blue y = 0.070  White y = 0.298

Established Timings:
-------------------- 

Manufacturer Reserved Timings:
------------------------------ 

Standard Timing Identification:
------------------------------- 

Monitor Description blocks:
--------------------------- 
Descriptor #0 - ASCII data:
		SRXFakeEDID

Descriptor #1 - Empty descriptor

Descriptor #2 - Empty descriptor

Descriptor #3 - Empty descriptor

I could not figure out where to add the EDID stuff in PlistEditor Pro. Any more detailed instructions around? I also attached these two files here in case if you would like to take a try.

I must admit I am really new to this stuff and all these DSDT stuffs are really beyond my comprehension.

Also the DisplayProductID file....

The DisplayProdutID file....

U110_EDID.txt

DisplayProductID_717.txt

CharredPC · January 18, 2010

I can't really recommend a FB / Natit version for 10.6.x, as I stopped using anything other than stock kexts even before installing Snow. Sorry! I don't consider that a real fix, just a temporary hack.

If you read that post, you'd have noticed I said boot to windows... there is no EDID reported for you in OSX (and therefore SwitchResX), so there's no way to get it there. From your own post:

Descriptor #0 - ASCII data:
SRXFakeEDID

You'll need your actual EDID to do any good. Once you get it, you open the 717 Display Override with Plist Editor Pro, edit the data value for IODisplayEDID, and paste your EDID there. You'll know it's working when you have all available resolutions listed, and not need SwitchResX anymore.

I'm not sure why the X3100 driver isn't loading for you; your hardware id and even version are the exact same as mine. Perhaps it's because you're using a a hacked distro instead of a retail DVD... did you select an "X3100" option? That may have overwritten the stock drivers, though I would think that updating to 10.6.2 should have put them back. I leave all stock kexts, "needed" or not, and use no Natit.

You might want to verify that you do in fact have all stock 10.6.2 X3100 kexts installed properly. Generally speaking, if you get a working, movable mouse icon but nothing else, this means the framebuffer is working, and the video drivers aren't. Anything unusual in the console from when it hangs this way? Anything saying why the X3100 kext isn't loaded during normal startup?

On a side note... with your cpu / chipset / video, any reason why you didn't just install retail?

pp611 · January 18, 2010

I did not install any Windows on the laptop (the HD is only 120G). Anyway to get the EDID through Linux? Probably I can run a Live CD version of Ubuntu.

The driver I am using were copied from a MBP running on 10.6.2, therefore I believe are the stock drivers.

Since I am really new to OSx86. I don't know if I can directly install the retail version. Does it need Chameleon or any other bootloader?

CharredPC · January 18, 2010

I did not install any Windows on the laptop (the HD is only 120G). Anyway to get the EDID through Linux? Probably I can run a Live CD version of Ubuntu.

The driver I am using were copied from a MBP running on 10.6.2, therefore I believe are the stock drivers.

Since I am really new to OSx86. I don't know if I can directly install the retail version. Does it need Chameleon or any other bootloader?

I haven't done it myself, but you should be able to use get-edid or read-edid in Ubuntu, though you may have to install some packages first. There seems to be some tutorials on Google for it.

If the drivers were all copied from a SL MBP, they should be fine, as long as you copied them all (including AppleIntelFramebuffer, and all AppleIntelGMA* kexts) and aren't adding anything extra in.

Easiest way is using a boot cd or a bootable usb key to get the retail DVD to load, then adding Chameleon (or whichever bootloader you like) once OSX is installed. There's lots of tutorials and apps (BootCD Maker, Empire EFI, etc) if you look around for booting retail.

pp611 · January 19, 2010

Somehow Lenovo U110 could not boot with an USB key. That's why I was trying the distros.

I copied all AppleIntel*.kext from a 10.6.2 MBP. At one time when I was experimenting different drivers I got kext validation problem but not now since I switched all to the stock 10.6.2 drivers. Also occasionally I saw in the kernel.log messages like "Alkor: Starting" then "Chosen model GMA X3100" but could not remember under what driver combination. I assume now AppleIntelGMAX3100.kext, AppleIntelGMAX3100FB.kext and AppleIntelFrameBuffer.kext were all loaded as there is no error or warning from log file regarding kext's but it just could not display properly. If I remove AppleIntelGMAX3100.kext and AppleIntelGMAX3100FB.kext I got a 1024x768 display working.

I'll try Ubuntu to get EDID later.

Also I noticed a post in which it suggest do something like

perl -pi -e "s|\x86\x80\x02\x2A|\x86\x80\x12\x2A|g" /System/Library/Extensions/AppleIntelGMAX3100FB.kext/AppleIntelGMAX3100FB

perl -pi -e "s|\x86\x80\x02\x2A|\x86\x80\x12\x2A|g" /System/Library/Extensions/AppleIntelGMAX3100.kext/Contents/MacOS/AppleIntelGMAX3100

perl -pi -e "s|028086|128086|g" /System/Library/Extensions/AppleIntelGMAX3100FB.kext/Info.plist

perl -pi -e "s|028086|128086|g" /System/Library/Extensions/AppleIntelGMAX3100.kext/Contents/Info.plist

Something I might try but need to figure what all these numbers mean first. Any suggestions?

CharredPC · January 19, 2010

Somehow Lenovo U110 could not boot with an USB key. That's why I was trying the distros.

Well, then you could always use a boot cd.

I copied all AppleIntel*.kext from a 10.6.2 MBP. At one time when I was experimenting different drivers I got kext validation problem but not now since I switched all to the stock 10.6.2 drivers. Also occasionally I saw in the kernel.log messages like "Alkor: Starting" then "Chosen model GMA X3100" but could not remember under what driver combination. I assume now AppleIntelGMAX3100.kext, AppleIntelGMAX3100FB.kext and AppleIntelFrameBuffer.kext were all loaded as there is no error or warning from log file regarding kext's but it just could not display properly. If I remove AppleIntelGMAX3100.kext and AppleIntelGMAX3100FB.kext I got a 1024x768 display working.

Simple explanation: The Alkor and Chosen model messages are from having Natit.kext installed. The kext validation problem is from not having permissions set correctly. I'm not sure what you mean by "not display properly," but if the drivers get loaded, they likely work fine. They just don't know how to correctly display, hence needing the Display Override EDID fix. Delete enough of the X3100 kexts, and of course you're defaulted back to generic non-accelerated 1024x768. But that's a step backwards, not forwards.

I'll try Ubuntu to get EDID later.

Very likely this will solve everything. Your drivers aren't the problem; the display detection is.

Also I noticed a post in which it suggest do something like

perl -pi -e "s|\x86\x80\x02\x2A|\x86\x80\x12\x2A|g" /System/Library/Extensions/AppleIntelGMAX3100FB.kext/AppleIntelGMAX3100FB

perl -pi -e "s|\x86\x80\x02\x2A|\x86\x80\x12\x2A|g" /System/Library/Extensions/AppleIntelGMAX3100.kext/Contents/MacOS/AppleIntelGMAX3100

perl -pi -e "s|028086|128086|g" /System/Library/Extensions/AppleIntelGMAX3100FB.kext/Info.plist

perl -pi -e "s|028086|128086|g" /System/Library/Extensions/AppleIntelGMAX3100.kext/Contents/Info.plist

Something I might try but need to figure what all these numbers mean first. Any suggestions?

This has nothing to do with your situation. What those lines do is edit the X3100 drivers to replace the hardware ID's. Your hardware ID's are fine. Your drivers are fine. The display detection is what needs fixing.

How about trying this: You say with stock drivers loaded, the display is 'messed up.' So enable Screen Sharing (System preferences -> Sharing -> click Screen Sharing, enable and set password under Computer Settings). Then put all drivers back to complete stock with no extras, and boot up. Now if the screen isn't usable (if it's just blue, or black) you should be able to remote in using another Mac or TightVNC. Once in, I bet it will show QE is enabled.

If it doesn't actually completely boot but just hangs so you can't remote in, there should be something in the Console log about it.

pp611 · January 19, 2010

When I said ""not display properly" I meant it was either gray screen or in text mode if booted with "-v", and no error or warning messages in kernel.log or system.log ("grep 3100 *.log" did not show any messages).

I had screen sharing enabled. I could use vncviewer when the machine was booted with the generic VGA display. However if the machines was booted with the X3100 drivers VNC viewer was either not able to connect or get connected with a black screen. Not sure if it has anything to do with using the Apple USB ethernet adapter rather than the built-in. In both case I can telnet onto the machine fine.

CharredPC · January 19, 2010

When I said ""not display properly" I meant it was either gray screen or in text mode if booted with "-v", and no error or warning messages in kernel.log or system.log ("grep 3100 *.log" did not show any messages).

I had screen sharing enabled. I could use vncviewer when the machine was booted with the generic VGA display. However if the machines was booted with the X3100 drivers VNC viewer was either not able to connect or get connected with a black screen. Not sure if it has anything to do with using the Apple USB ethernet adapter rather than the built-in. In both case I can telnet onto the machine fine.

You don't want to grep for anything, you'd want to look at the actual whole log. The X3100 kexts likely load fine, and the errors will be due to something else. By the sounds of it, you might have an "unusable display" error. What that happens, OSX boots enough that telnet functions, but since it has no display device, you can't see anything or even VNC in. This could be fixed by injecting the EDID.

pp611 · January 26, 2010

On business trip until today and did not get chance to try.

Finally I got the EDID information out after installed Windows XP on the machine (EDIDViewer seems not working on Windows 7, and Ubuntu's get-edid does not work on my machine when running live Ubuntu CD.

With the injected EDID the system goes just a little bit further, when booted with -v option, it can get out the tty mode and into a gray screen. And it stops there.

I used CharredPC's DisplayProductID-717 file and changed the EDID hex string, the resolution, and left the frequency at 60 (EDID shows 65.46). I do'nt know what dspc part is and left it unchanged. Then the file was copied back into the /System/Library/Displays/Overrides/DisplayVendorID-756e6b6e/ folder.

It is so close now. Is the dspc part a problem?

Here is the EDID info I got from EDIDViewer

 </P> <P>Vendor/Product Identification:</P> <P> Monitor Name :  
Monitor Serial Number :  
Manufacturer Name :  MS_
Product Id :  412:00:00 AM
Serial Number :  3
Week Of Manufacture :  0
Year Of Manufacture :  2002
EDIDVersion :  V1.3
Number Of Extension Flag :  0</P> <P>Display parameters:</P> <P> Video Input Definition :  Digital Signal
DFP1X Compatible Interface :  False
Max Horizontal Image Size :  2550 mm
Max Vertical Image Size :  2550 mm
Max Display Size :  142 Inches</P> <P>Power Management and Features:</P> <P> Standby :  Not Supported
Suspend :  Not Supported
ActiveOff :  Supported
Video Input :  1
sRGB Default ColorSpace :  True
Default GTF :  Supported
Prefered Timing Mode :  True</P> <P>Gamma/Color and Etablished Timings:</P> <P> Display Gamma :  3.55
Red :  x = 0.625 - y = 0.34
Green :  x = 0.285 - y = 0.605
Blue :  x = 0.148 - y = 0.062
White :  x = 0.281 - y = 0.309</P> <P> Etablished Timings :  </P> <P> Display Type :  RGB Color Display</P> <P>Standard Timing:</P> <P>
Preferred Detailed Timing:</P> <P> Pixel Clock :  65.46 Mhz</P> <P> Horizontal Active :  1366 pixels
Horizontal Blanking :  112 pixels
Horizontal Sync Offset :  64 pixels
Horizontal Sync Pulse Width :  106 pixels
Horizontal Border :  0 pixels
Horizontal Size :  0 mm</P> <P> Vertical Active :  768 lines
Vertical Blanking :  4 lines
Vertical Sync Offset :  1 lines
Vertical Sync Pulse Width :  6 lines
Vertical Border :  0 lines
Vertical Size :  0 mm</P> <P> Input Type :  Digital Separate
Interlaced :  False
VerticalPolarity :  False
HorizontalPolarity :  False</P> <P>Monitor Range Limit:</P> <P> Maximum Vertical Frequency :  57 Hz
Minimum Vertical Frequency :  0 Hz
Maximum Horizontal Frequency :  1 KHz
Minimum Horizontal Frequency :  0 KHz
Maximum Pixel Clock :  70 MHz</P> <P>Stereo Display:</P> <P> Stereo Display :  Normal display (no stereo)</P> <P>RAW Data:</P> <P>0x00  00 FF FF FF FF FF FF 00 36 7F 4C 00 03 00 00 00 .ÿÿÿÿÿÿ.6L.....
0x10  00 0C 01 03 80 FF FF FF 2F 00 00 A0 57 49 9B 26 ....?ÿÿÿ/.. WI?&
0x20  10 48 4F 00 00 00 01 01 01 01 01 01 01 01 01 01 .HO.............
0x30  01 01 01 01 01 01 92 19 56 70 50 00 04 30 40 6A <A href="mailto:......?.VpP..0@j">......?.VpP..0@j</A>
0x40  16 00 00 00 00 00 00 18 00 00 00 FD 00 00 39 00 ...........ý..9.
0x50  01 07 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0x60  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0x70  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 83 ...............?</P> <P>

CharredPC · January 26, 2010

Check the latest instructions in the Overrides / Scrambled screen thread I created a few days ago. The dspc part isn't needed, nor is the default resolution.

pp611 · January 27, 2010

Thanks much for the reply. I did the stuff again after reading the instructions in your post. Still the same gray screen.

However I believe the Override file was picked up properly. Here is a portion of the ioreg -l result

 </P> <P>	| |   | | +-o display0  <class IODisplayConnect, id 0x1000002fa, registered, matched, active, busy 0 (897 ms), retain 5>
| |   | |   +-o AppleDisplay  <class AppleDisplay, id 0x1000002fc, registered, matched, active, busy 0 (1 ms), retain 11>
| |   | |		 "IOProviderClass" = "IODisplayConnect"
| |   | |		 "IOClass" = "AppleDisplay"
| |   | |		 "IODisplayParameters" = {"pscn"={"min"=0,"max"=10000,"value"=0},"rgsc"={"min"=0,"max"=65536,"value"=65536},"bklt"={"min"=0,"max"=494,"value"=494},"bgsc"={"min"=0,"ma$
| |   | |		 "DisplayVendorID" = 1970170734
| |   | |		 "IODisplayConnectFlags" = <00080000>
| |   | |		 "DisplayProductID" = 1815
| |   | |		 "IODisplayPrefsKey" = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/VGA@2/AppleIntelFramebuffer/display0/AppleDisplay-756e6b6e-717"
| +-o IODisplayWrangler  <class IODisplayWrangler, id 0x1000002ab, registered, matched, active, busy 0 (3 ms), retain 6>
| |	 "IOClass" = "IODisplayWrangler"
</P> <P>

My IODisplayPrefsKey was just AppleDisplay-756e6b6e-717 rather than AppleBacklightDisplay-756e6b6e-717. Would this be the problem?

Also the /var/log/windowserver.log file had the following lines:

</P> <P>Jan 27 19:59:38  [54] Server is starting up
Jan 27 19:59:43  [54] CGXMappedDisplayStart: Display0 : no display alias property
Jan 27 19:59:43  [54] CGXPerformInitialDisplayConfiguration
Jan 27 19:59:43  [54]   Display 0x5b81c5c0: MappedDisplay Unit 0; Vendor 0x756e6b6e Model 0x717 S/N 0; online enabled (0,0)[1024 x 768], Rotation 0, base addr 0x106000000
Jan 27 19:59:43  [54] AGCAttach: Couldn't find any matches
Jan 27 19:59:44  [54] Display 0x5b81c5c0: MappedDisplay Unit 0; ColorProfile "Internal LCD Forced EDID"
Jan 27 20:58:04  [54] kCGErrorIllegalArgument: CGXSetWindowListTags: Operation on a window 0x6 not owned by caller loginwindow
Jan 27 20:58:05  [54] dict count after removing entry for window 0x9 is 0
Jan 27 20:58:05  [54] CGXRestartSessionWorkspace: session workspace exited for session 256 ( on console )
Jan 27 20:58:06  [54] loginwindow connection closed; closing server.
Jan 27 20:59:24  [58] Server is starting up</P> <P>

The lines for 19:50:XX was for a boot with both AppleIntelGMAX3100.kext and AppleIntelGMAX3100FB.kext removed. After I put these two drivers back (kext rebuilt), there is only the line of "Server is starting up". No error messages were found in the log file regarding loading the X3100 drivers.

CharredPC · January 28, 2010

My IODisplayPrefsKey was just AppleDisplay-756e6b6e-717 rather than AppleBacklightDisplay-756e6b6e-717. Would this be the problem?

Mine only shows up as "AppleBacklightDisplay" because I have added the PNLF device to my DSDT. It shouldn't make a difference here.

The lines for 19:50:XX was for a boot with both AppleIntelGMAX3100.kext and AppleIntelGMAX3100FB.kext removed. After I put these two drivers back (kext rebuilt), there is only the line of "Server is starting up". No error messages were found in the log file regarding loading the X3100 drivers.

Removing some of the X3100 drivers will, surprisingly enough, cause errors. All drivers should be left there, none should be removed.

When you added the EDID, you cleaned up the code from what you posted, right? According to your post, your EDID should be: 00FFFFFFFFFFFF00367F4C0003000000000C010380FFFFFF2F0000A057499B260101010101019219

567050000430406A1600000000000018000000FD00003900010700000000000000000000000000000

000000000000000000000000000000000000000000000000000000000000083

Can you normally remote in using VNC? It just doesn't work when it stops on the gray screen?

pp611 · January 29, 2010

body { background: #FFFFFF; margin: 0px; padding: 4px; font-family: Verdana, arial, sans-serif; font-size: 10pt; } The EDID in your post was the one I added. I'll double check when I get home tonight.

The current behaviors go like this. Without the EDID override

The system would hang at the tty mode.
VNC client would hang when connecting to the Snow Leopard machine. Telnet works however

With the EDID override

The system would hang at a bright gray screen (after the Apple logo is gone when booted without -v option)
VNC client returns immediately with the error of not being able to connect. Telnet also works.

VNC client works fine when X3100 driver are not loaded.

CharredPC · January 29, 2010

If you post your override file, I will have a look at it. It sounds like it almost works...

pp611 · January 29, 2010

Here are the content of the Override file

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>DisplayProductID</key>
<integer>1815</integer>
<key>DisplayProductName</key>
<string>Internal LCD Forced EDID</string>
<key>DisplayVendorID</key>
<integer>1970170734</integer>
<key>IODisplayEDID</key>
<data>
AP///////wA2f0wAAwAAAAAMAQOA////LwAAoFdJmyYQSE8AAAABAQEBAQEBAQEBAQEB
AQEBkhlWcFAABDBAahYAAAAAAAAYAAAA/QAAOQABBwAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIM=
</data>
</dict>
</plist>

And the raw EDID data

0x00	 00 FF FF FF FF FF FF 00 36 7F 4C 00 03 00 00 00	.ˇˇˇˇˇˇ.6L.....
0x10	 00 0C 01 03 80 FF FF FF 2F 00 00 A0 57 49 9B 26	....?ˇˇˇ/..†WI?&
0x20	 10 48 4F 00 00 00 01 01 01 01 01 01 01 01 01 01	.HO.............
0x30	 01 01 01 01 01 01 92 19 56 70 50 00 04 30 40 6A	......?.VpP..0@j
0x40	 16 00 00 00 00 00 00 18 00 00 00 FD 00 00 39 00	...........˝..9.
0x50	 01 07 00 00 00 00 00 00 00 00 00 00 00 00 00 00	................
0x60	 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00	................
0x70	 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 83	...............?

You are right. I think it is really close...

pp611 · February 3, 2010

Hi, CharredPC, any hope for this machine? Waiting for your insight....

Helped need with GMX3100 Driver on Lenovo IdeaPad U110 and Snow Leopard 10.6.2

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