Updated version

Over the last few weeks there's been a lot of advances in getting X4500 support in osX86. At the moment only framebuffer works, which means getting native resolution, no QE or CI yet, but hey, it's already great to have native resolution.

Coldequation has modded a patcher script provided by Trauma, with wich you can patch the stock AppleIntelGMAX3100.kext's to give support for X4500 graphics cards.

All you need atm is your device ID (you can find it in system profiler (/Applications/Utilities/System Profiler or about this mac --> more info) under graphics section. The device ID starts with 0x and then 4 numbers, probably 0x2A42 (for X4500MHD)

Once you know your device ID, download the script attached to this post, then follow these steps:

1. Start a terminal
2. type sudo -s and enter your user password
3. drag the script from the location you downloaded it from to the terminal
4. at the end of the line, add following options: -rf *your device ID* (it should look something like /Users/username/Downloads/patchX4500.bash -rf 2A42
5. Press enter. The command will give you some output for feedback.
6. Once you executed the script, repair permissions using disk utility (in Applications/Utilities, click on your primary harddrive, and on the first aid tab click on repair permissions.) This might take a while, but will make sure that your driver can be loaded.
7. Reboot and (hopefully) enjoy native resolution

Make sure you have the vanilla version of the kernel extensions (being AppleIntelGMAX3100.kext and AppleIntelGMAX3100FB.kext in /System/Library/Extensions). This only applies to people previously running kernel extensions provided by me in the other thread.

Please post your results in this thread, be it good results or bad results, we'll try to help you . In your post please include hardware info (both laptop type/brand and video card device ID) and software info (osX version and distro)

If you don't get response here, you can (most of the time) find me or other guys willing to help you on the IRC channel #GMA_X4500 at irc.voodooprojects.org

I'll update this thread every time a (more or less) stable breakthrough has been made, and everytime a new patcher script comes out.
known issues

• Cursor vanishes
  --> workaround: change the cursor size in system preferences -- mouse (till it's really huge, not so handy, but at least it works )
• vertical stripes
  --> No workaround yet, looking into it atm

Last update: July 15, 2009 at 23:17 CET: New patcher script

it worked for me!

saludos

I hope you get QE/CI - that will open up a lot of boards for use...

keep up the good work,

Patrick

it works for me too. Toshiba Satellite L300-1F4 with Intel GMA 4500.

Good work, thx!  

It's maybe interesting for everybody who got it working to write down the hardware they use in their post, so other people using the same hardware can find the procedure and if it works or not

I've got a Toshiba L300-19F (Model PSLB8E-01200DBT) and it's working (as said before, no qe/ci, but I get native resolution without having to use a complex hack, and can switch resolution.

Hello there,

I've tried the kexts with latitude e6400 but i've faced all the time same problem of blue screen before my desktop comes to alive.

i've tested it with 10.5.6 and 10.5.7 but with no luck.

We really need of some help here from all OSX 86 gurus....

Please listen to the public.

Very interesting..

I was involved with getting the GMA950 driver hack to work a few years ago using the same hack method that you guys are describing. Can I ask what does system profiler report?

Does it report as a X3100 type Graphics card? if so has anyone tried EFI strings to get QE/CI working?

Just a thought??

We tried using a custom DSDT to get the same effect.. System profiler did report X3100 before trauma made me a custom DSDT, now it reports X4500.. But we're stuck, any help of people knowing more is welcome! Look at the originating thread I posted in my first post, at page 11 there is an analysis of what seems possible to do..

If you get a blue screen and nothing else, remove the AppleIntelGMAX3100.kext, we're still looking for a way to be able to use the AppleIngelGMAX3100.kext properly

would you mind helping us a little over at the original thread? We're stuck at the moment..

Awesome! Thanks a whole lot dude!
(no qe/ci yet but hey, it works a f**king charm)

Unfortunately this isn't working for me. I have a new SX2800 system. Specs here:
http://www.gateway.com/systems/product/529...1.php?tab=specs

After reboot, I do see the two AppleIntel files mentioned in the right directory but when I go to system preferences -> Displays, it still only shows me the single option of 1024 x 768

I'm new to MACs and any help you can provide would be appreciated

Thanks

Have you used correct device id?
The desktop version is different from mobile version.
Please read post #1 carefully.

i'm find solution from my GMA X3500 Card!

Can' get it to work... I'm sure I'm getting the right Device Number, and is the same as yours, and Im sure it's mobile 'cause I'm on a Notebook (Dell inspiron 1545), and still I can't get it to work.

The System Profiler tells me that no kext were loaded to the Graphics... Any ideas?

PS.: I already tried to boot on -x...

[UPDATE]
I booted on -x and done the same thing, now my screen is black and I can't get past the login screen...

[UPDATE 2X]
Got it to 1024x768 by deleting via command Line (-s) the 2A42AppleIntelGMAX3100 | AppleIntelGMAX3100 | AppleIntelGMAX3100FB

This is specifically for GMA X4500, don't think this method works for X3500.. Can't help you straight away (although, if you look for your device ID and follow this tutorial, it might be possible to get it working.. Though I don't know about it.. Otherwise, look in the forums, it's got a search function, we all had to do it.. I know there's a mass of information to go through, but there's no other way..)

thx advance

I did the whole tutorial:
-terminal...sudo -s...run the bash script with -vrf 2a42 options (my hardware id is 2a42)
-after that i repair the permissions
-then reboot the mashine (Toshiba Satellite L300-19J, the most hardwares works fine, except the graphic card and the wifi (intel 5100 agn), the wifi hasn't 3rd party support)
-after the reboot, I don't have native resolution, so don't wokr the patch correctly

The mashine is Toshiba Satellite L300-19J, I installed iAtkos v7 10.5.7.

P.S.: I'm a beginner in this OSX thing.

I have a Toshiba L350-20G and the patch fails too, for some reason the device ID is not injected into the kext at all, it's just left with >8086<.
When using pre-patched kext's I get the native resolution, but with white horizontal lines every other pixel, making the display hard to read.
I did notice that without the patch System Info shows that I have a Inbuilt Display attached, however when using the patched kext's it shows no display attached.

I've removed OS X for now, needed the extra space, but will install it again later today.

If you want me to provide and further details just ask.

Haven't had the problem with the script. Technically the end result of the script and the pre-patched kexts should be identical. 8086 is actually the Vendor (Intel) so it should stay as this. It is OK that it says it does not have a display attached. Going by others results it does not affect anything (at the moment ).

Interesting though about the lines. I also get them but when you connect to an external display the lines are not there on external display (they stay on the built-in). At the moment I'm trying with tienneke to address the no cursor issue which seems to be only affecting Lenovo users. Anyways hope to find a solution for this too. Its kind of hard to use with no mouse and white lines everywhere

iPoco

What I mean is that 8086 is all that is left, no device ID is patched in at all.
I'm using iAtkos 10.5.7, I have replaced all the GMA* kext's with ones from the 10.5.7 combo update.
Another thing I have noted is that with stock kext's I am stuck with 1024x768 but the X3100 kext get's loaded.

The no cursor issue may be related to the white lines problem.
Could it be that the kexts are setting the external display as primary and the internal as a mirror display?
Is their a way of turning off the external display, I don't have the option in BIOS, mine is setup as a dual display in bios.
If I use the display switch button on the laptop the internal display switches off, and just wont cycle back to it, I don't have a external monitor to test.

The script does not patch the extisting files. It copies them and then patches the copied kexts. Once you have run the script you will notice in your extensions folder that there are two new kexts (or if you used -r only one):

-2a42AppleIntelGMAX3100FB.kext
-2a42AppleIntelGMAX3100.kext (This one is removed with -r)

So it is normal that there are no changes to the original AppleIntelGMAX3100*.kext files.

The no cursor issue seems to be unrelated to the white lines problem as some people such as chopped experience the no cursor issue but have no white lines on the display.

iPoco

Yes I know.
The patch does not change the device id in the 2a42*.kext's it literally removes it.

I'll re-install OS X tomorrow and I'll post up the kexts as they are AFTER i run the patch script.

You're talking about the Info.plist file in the AppleIntelGMAX3100FB.kext I believe, it works with a match, and as such indeed is only left with 8086..

It actually matches with every device of class 0x03 and made by 8086 (the mask is 0x03000000&0xff000000, which results in 0x30, same method for the PCIMatch).

So that's normal (if it's that you talk about)..

Or do you mean it doesn't actually hexedit your files?

Try using the patcher script in the top of the thread, I updated it. This one should work perfectly

The new patch works fine, and I did mean the info.plist.
I still get the vertical lines, I'm thinking it maybe caused by not having the non FB kext loaded.
I've tried all the fix's that people used with laptops and the GMA950 holding on blue screens, but none worked

[edit]
oops

I've just noticed something. You say you have horizontal lines like --- not | ?

Slightly different then me then because mine are | (vertical). I'm not sure that the lines are caused by not having the other driver loaded because that wouldn't explain how other people without that file would have no problems. I've thought about this too. Maybe it is the problem. We will have to wait and see!

iPoco

Sorry, meant vertical, I should not post on forums when half asleep, the lines go |

Are you sure you have the non FB module loaded?
E.G. if you type in terminal you see both X3100FB and X3100 in the list?

I'm not sure he meant it was loaded:



iPoco

Sorry, My bad, moesn't read messages when falling asleep :$

Tried the new one just out of interest and still lines :s I'll be on IRC if you have any ideas.

iPoco

You should correct your instructions as Step 4 contradicts itself:

at the end of the line, add following options: -rf *your device ID* (it should look something like /Users/username/Downloads/patchX4500.bash -vrf 2A42

You say to type -rf but in the example you have -vrf

I typed without the 'v' and now I boot and get a black screen.

So lucky,Its work for me,But another problem come,the cursor disappeared,So ,what to do next?

I've noticed that when using the 2A42...FB.kext I get

in the system log, it does not appear when not using it.
Maybe this has something to do with the vertical lines?

Actually the v shouldn't be there.. If you get black screen, try booting into safe mode, and see if it works.. If it works there, then remove /System/Library/Extensions/*your device ID*AppleIntelGMAX3100.kext

Are you refering to this:


It could be related for all I know. Or it could just be because it can't detect what type of display we are using so it thinks it can't use it. If someone who has no lines on there screen can look for that in there system.log it would be appreciated.

iPoco

Tienneke said...

"Actually the v shouldn't be there.. If you get black screen, try booting into safe mode, and see if it works.. If it works there, then remove /System/Library/Extensions/*your device ID*AppleIntelGMAX3100.kext"


perhaps an edit to you instructions is in order, as it does include the "v":


"at the end of the line, add following options: -rf *your device ID* (it should look something like /Users/username/Downloads/patchX4500.bash -vrf 2A42"

BTW, great work; getting there.

I have an Asus P5Q-EM; the device id is

00:02.0 VGA compatible controller [0300]: Intel Corporation Eaglelake Integrated Graphics Controller [8086:2e22] (rev 03)

And...

then I noticed this:

00:02.1 Display controller [0380]: Intel Corporation Eaglelake HECI Controller [8086:2e23] (rev 03)

I'm thinking this is probably the HDMI side of the on-board?

I've yet to play with this enough to know if the mac side even sees the HDMI, but that would be Sweet!

jp

Edited the instructions without the -v. I spoke to Trauma about the display message and he doesn't seem to know.

iPoco

Okay, here's my process and results so far:

HW: Asus P5Q-EM with x4500 integrated on-board

Comes up fine in 1024x768; no adjustments available.

System Profiler reports:

Display:

Type: Display
Bus: Built-In
VRAM (Total): 64 MB of Shared System Memory
Vendor: Intel (0x8086)
Device ID: 0x2e22
Revision ID: 0x0003
Kernel Extension Info: No Kext Loaded
Displays:
Display:
Resolution: 1024 x 768
Depth: 32-Bit Color
Core Image: Software
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Not Supported

Results:

I first ran the script by itself, free of any additional arguements (I had previously put the lspci.txt at root)

Script ran fine; found the ID, created the kext, and gave me the "This is not a tested (stock 10.5.7) AppleIntelGMAX3100 version, but it might work anyway." I am running an iDeneb-based vanilla kernel install, updated to 10.5.7

Repaired permissions, rebooted, got the nice blue screen, followed by a blank dead screen, and my monitor giving me the "out of range" comment

Said "hmmm...."; deleted the kext and boot back into the stock driver.

DL's the 10.5.7 combo update, used Pacifist to replace the stock apple driver. Rebooted (for grins), ran the script again; same error message (so is the script seeing the "stock" apple driver correctly?)

booted into superuser, moved the stock apple driver out to a folder at root (to make sure somehow it and the modified kexts were separated), and rebooted again with -f.

Same result; dead black screen.

Any ideas or suggestions appreciated; I am curious about the error message coming out of the script after re-installing the known 10.5.7 kexts from the combo update...

THis would be really nice to get working, as the accepted graphics workaround for the P5Q family has been a pci card...and those nvidias are about as quiet as a 747 coming in low over your house...

thanks!

UPDATE: THe chipset I'm using is a G45, and so the graphics unit is really an X4500HD...could it be that this is significantly different enough from the X3100 driver set that it isn't getting it done?

HW Brand new Gateway SX2800 running Intel® G45/G43 Express Chipset
SW ideneb 10.5.5

Guys

I tried doing this but my PC boots into a blue screen and remains there. I tried safe mode by doing F8 and -x but it still comes back to the blue screen.

Tienneke suggested deleting AppleIntelGMAX3100.kext. How do I do that? Can I do it coming to the command prompt after hitting F8? Some details would help

Boot into single user mode. Where you entered -v instead enter -s. Then you can enter:

/sbin/fsck -fy
/sbin/mount -uw /
rm -R /System/Library/Extensions/<name of kext here>
rm /System/Library/Extensions.mkext

Boot with -f the next startup.


iPoco

It did not work. Here's what I did

1) After F8, I booted with -s
2) Then entered all four commands below (the last two commands gave me no output)
3) Typed 'reboot'
4) After F8, I booted with -f

Since it did not work, I ran through this one more time and both 'rm' commands returned file not found since I had already deleted them. This time, after reboot I used the -F string and still getting the blue screen

Are there any additional files I have to delete?

I've had problems with removing files via -s in the past. You can look through what files are in the extensions folder by using

The only files that this installed were (unless using -r):
-2a42AppleIntelGMAX3100FB.kext
-2a42AppleIntelGMAX3100.kext

Without them you should be back to where your system was before you installed the patch. The -f flag used to rebuild the kext cache you can try without it.

iPoco

I saw that AppleIntelGMAX3100FB.kext was still in the folder so I deleted it and get the same blue screen whether I boot with -f or not

I still see the following files with '3100' in their file name in the Extensions directory. Should I delete them as well?
AppleIntelGMA3100GA.plgin
AppleIntelGMA3100GLDriver.bundle
AppleIntelGMA3100VADriver.bundle

The .plugin and .bundle items in the /Extensions folder are loaded by their kext. So in this case AppleIntelGMAX3100.kext. I thought of one other file that you may not have removed: 2a42AppleIntelGMAX3100.kext. If this kext is in the folder it will try to load the .plugin and .bundle which are not yet working. If this doesn't work you can try do a wildcard move BUT ONLY after you have tried removing the other file and boot with -f:


iPoco

Yes, it is possible.. I'll give you step by step instructions:

• mount -uw
• cd /System/Library/Extensions
• mv *your device ID*AppleIntelGMAX3100.kext /
• reboot

You might notice I put mv instead of rm (move instead of delete), just so you could very easily try if you need the kext again. The script doesn't touch the standard AppleIntelGMAX3100, so there's no need moving that away.

What device ID do you have? (if you boot into graphics mode do the following: apple icon (top left corner of your screen) --> about this mac --> more info --> Graphics, look at the right column, there'll be a line stating your device ID..)



That's an issue that we have not been able to pinpoint yet. It appears consistently on laptops with 2 graphics cards (lenovo T500, got an integrated GMA X4500 and a dedicated radeon), and on some other pc's too.. We can't yet help you, the best solution is making your cursor bigger (in system preferences). There'll be a point where the cursor reappears (it'll be quite big)




Thank you It's really a community effort, a great community.

The two devices are most probably the graphics controller and the graphics memory controller, that has a different device ID (got that from coldequation).. If you want to know more about that, you can read all about it in the linux device docs for X4500 (coldequation gave me the infos, but really was not so interested that I would read through it )



Well, great we fount somebody with X4500HD.. Up till now we only tested on X4500MHD, the mobile version. It can be interesting if you would want to do more testing, but the testing is best to happen in the non-genius bar thread ( http://www.insanelymac.com/forum/index.php?showtopic=129744 ). It seems that our method might not work directly for X4500HD, but maybe with a little fiddling? (I'm mostly over optimistic )

I also have the cursor problem.
Mine is X200 tablet, 4500MHD (1280x800 screen) running iATKOS v7 with stock graphic driver (display only 1024x768). I ran the script and the resolution is ok now. However there is no mouse cursor on the screen.

Yup well known. Seems to be common to all Lenovos. Hey tienneke/coldequation I found something interesting today. Sometimes when I move my mouse it flickers on and I can see the cursor (still buried by lines) and then its gone the next second. Also something interesting is that on some startups I get garbage for a mouse. A little rectagle around 5cm below the real location and then other startups I'm lucky enough to get two rectangles. One 5cm below the mouse and the other where the cursor actually is. I've even once had a one pixel mouse in white.

On a note of another problem sometimes when I startup my screen really green. Then if I change resolutions it goes away. I'm sure I wrote this somewhere else before but just posting it again

I fixed the mouse (sorta) by downloading mighty mouse and magnifying the mouse.

As pointed out by chopped you can get the mouse to show by editing the size inside of System Preferences.

iPoco