Jump to content

GMA X4500


Tienneke
 Share

368 posts in this topic

Recommended Posts

Hi didn't work for me maybe because i have a X4500MHD? It has the right device Id tho!

 

Dell Inspiron 1545

  • Processors: Intel Pentium Dual-Core T4200 - Working
  • Memory: 3 GB, dual channel DDR2 SDRAM @ 800 MHz - Working
  • Chipset: Intel GM45 Express Chipset. - Working MacBook Pro
  • Graphics Processor: integrated Intel GMA X4500MHD graphics - Installed Driver
  • LCD Display: 15.6" glossy widescreen with a 1366 × 768 and TrueLife - Completely Blank After Boot Loads Driver
  • Hard Drive: 160 GB - Partitione to 75GB for OS X
  • Optical Drive: 8X tray-load dual-layer DVD+/-RW drive - Working
  • Battery: 4-cell (37 Whr), 6-cell (56 Whr), or 9-cell (85 Whr) Lithium Ion battery. - Working & Displays
  • Camera: 1.3 MP webcam with optional facial recognition software - Working (no preview)
  • Wi-Fi Card: Dell Wireless 1397 802.11g half mini-card or Intel Wi-Fi Link 5100 802.11a/g/n half mini-card. - Working
  • Bluetooth: Dell Wireless Bluetooth Internal 365 (2.1 EDR). - Not Working

IATKOS V1.7 0 - OS X 10.5.8 Duel Boot Windows 7

 

PLEASE HELP IVE BEEN FOLLOWING THIS FORUM FOR MONTHS :-)

 

Thanks Dudes

 

Taz

Link to comment
Share on other sites

Hi didn't work for me maybe because i have a X4500MHD? It has the right device Id tho!

PLEASE HELP IVE BEEN FOLLOWING THIS FORUM FOR MONTHS :-)

 

Thanks Dudes

 

Taz

 

Hi Taz,

I personally have a 4500MHD too, so that shouldn't be the problem :(

What exactly does not work? Do you boot to a black/blue screen, do you get kernel panics, or does it just change absolutely nothing if you have the modded drivers?

Link to comment
Share on other sites

Hi Taz,

I personally have a 4500MHD too, so that shouldn't be the problem :(

What exactly does not work? Do you boot to a black/blue screen, do you get kernel panics, or does it just change absolutely nothing if you have the modded drivers?

 

does this work on 10.5.7?

what kind of version are you using...

Link to comment
Share on other sites

does this work on 10.5.7?

what kind of version are you using...

 

It works on 10.5.7, should work on 10.5.6 too (have used both of them before my laptop went down the crapper)

 

It seems to me that very often the 2A42AppleIntelGMAX3100.kext is not removed, causing the computer to boot to a blue screen due to hardware addressing issues.

Just removing the kext should allow you to boot to graphics mode with native resolution.

 

So before patching, you would have AppleIntelGMAX3100*.kext.

After patching, there should be 1 or 2 new kexts, starting with your device ID (2A42 for me). Those 2 kexts are 2A42AppleIntelGMAX3100.kext and 2A42AppleIntelGMAX3100FB.kext. Of those two, you only need the one ending in FB.kext, the other one will cause your pc to lock up at a blue/black screen.

Link to comment
Share on other sites

Hi Mac Peepz,

 

It boots to a black screen but an external monitor will work and displays as a second monitor - ie: just background is displayed.

 

If I try changing the resolution of my internal screen nothing happens. The picture tends to start turning things into lines and the mouse pointer appears as large pixely liney square.

 

The same thing happens with 10.5.7 and 10.5.8?

 

Thanks for the help guys,

 

Taz

Link to comment
Share on other sites

Hi Mac Peepz,

 

It boots to a black screen but an external monitor will work and displays as a second monitor - ie: just background is displayed.

 

If I try changing the resolution of my internal screen nothing happens. The picture tends to start turning things into lines and the mouse pointer appears as large pixely liney square.

 

The same thing happens with 10.5.7 and 10.5.8?

 

Thanks for the help guys,

 

Taz

 

Okay, it seems you'll need a natit in order to get image on your internal monitor. I can't make one atm, don't have access to a mac machine (and chances are I won't get access to one in near future. I'm planning on buying a mbp, getting tired of non-working hardware). I think trauma or coldequation could make one (just with the 'hasPanel' setting).

 

The cursor issue is atm unresolved. We don't yet know how to fix that. The only thing possible to get a cursor is changing the size in system preferences. (explained higher up)

Link to comment
Share on other sites

Okay, it seems you'll need a natit in order to get image on your internal monitor. I can't make one atm, don't have access to a mac machine (and chances are I won't get access to one in near future. I'm planning on buying a mbp, getting tired of non-working hardware). I think trauma or coldequation could make one (just with the 'hasPanel' setting).

 

The cursor issue is atm unresolved. We don't yet know how to fix that. The only thing possible to get a cursor is changing the size in system preferences. (explained higher up)

 

do you mean someone may meet The cursor issue but someone may not ?have you met such problem

Link to comment
Share on other sites

do you mean someone may meet The cursor issue but someone may not ?have you met such problem

 

Yes, we don't yet know what triggers the cursor issue. One thing we do know is that the issue is very common on lenovo thinkpads, especially the L500 with dual graphics.

Coldequation & OriginalMacNut are trying/have tried to find a fix, but up till now there hasn't been a right fix.

Link to comment
Share on other sites

Yes, we don't yet know what triggers the cursor issue. One thing we do know is that the issue is very common on lenovo thinkpads, especially the L500 with dual graphics.

Coldequation & OriginalMacNut are trying/have tried to find a fix, but up till now there hasn't been a right fix.

 

mine is the thinkpad x200....

Link to comment
Share on other sites

I got the screen resolution right. I have the cursor issue (Dell laditude E5500) and the screen is black on boot. Putting it to sleep will get the screen to come on again. I boot it up and after it finishes booting the screen turns off. Then I push Fn+F1 to put it to sleep then I wake it back up and it works

Link to comment
Share on other sites

Is there an option to restore after this if in case something something goes wrong?

 

 

 

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)

 

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

Link to comment
Share on other sites

Is there an option to restore after this if in case something something goes wrong?

 

Yes, If you just remove the patched kexts. The method is as follows:

 

at the boot loader prompt, boot in verbose mode (type -v -s at boot prompt)

when in single user mode, execute following commands:

fsck -fy
mount -uw /
rm -R /System/Library/Extensions/2A42*

 

If you have a different ID than 2A42, replace the last line with your device ID (and keep the * at the end of the line)

This should fix it if you get broken :D

Link to comment
Share on other sites

Thank you very much Tienneke!

 

Hope it will work!

 

I have a 0x2e22 ID :D, and it's on an Asus P5Q-VM MB!

Curently I have the 1280x1024@32 via boot plist!

 

 

Yes, If you just remove the patched kexts. The method is as follows:

 

at the boot loader prompt, boot in verbose mode (type -v -s at boot prompt)

when in single user mode, execute following commands:

fsck -fy
mount -uw /
rm -R /System/Library/Extensions/2A42*

 

If you have a different ID than 2A42, replace the last line with your device ID (and keep the * at the end of the line)

This should fix it if you get broken :D

Link to comment
Share on other sites

mine computer is lenovo thinkpad x200 , and the video card is Intel GMA X4500 , the id is 0x2A42, the mac edition is ideneb 10.5.7.

after using the patcher, i can't find the cursor. and the ci and qe is still not supported...

what should i do ?

Link to comment
Share on other sites

Yes, If you just remove the patched kexts. The method is as follows:

 

at the boot loader prompt, boot in verbose mode (type -v -s at boot prompt)

when in single user mode, execute following commands:

fsck -fy
mount -uw /
rm -R /System/Library/Extensions/2A42*

 

If you have a different ID than 2A42, replace the last line with your device ID (and keep the * at the end of the line)

This should fix it if you get broken ;)

 

 

Well, it did not work for me ;)

 

I got the blue-grey screen, no mouse and CAPS did not work either while in that blue-grey screen!

 

So I have used the commands that you provided (above), and now I'm back, THANKS AGAIN! ;)

(I have to mention that using my ID as 2e22 did not work but with 2E22, did; it was this CAPITAL leter E also important at the first run of the script for native resolution??)

 

Also, I think I have to add that I am still on iDeneb 1.3 - 10.5.5 (I am afraid to update since I did not find a working solution for that yet, and the install on my computer at home -i7- just crashed because the iDeneb 10.5.7 update Kit).

 

Any other ideas to this native resolution or even a point to a GOOD and WORKING path to update?!?

Thanks in advance to anyone that might bring some solutions!

Link to comment
Share on other sites

mine computer is lenovo thinkpad x200 , and the video card is Intel GMA X4500 , the id is 0x2A42, the mac edition is ideneb 10.5.7.

after using the patcher, i can't find the cursor. and the ci and qe is still not supported...

what should i do ?

 

I hate to be an ass, but read the thread. It's been said like 30 times, there is no fix for the cursor issue, the only thing you can do is: make the cursor larger, or remove the kexts (method I posted just a few posts ago). Other than that, I can't help you. Coldequation is working on it, though he's stuck debugging, if anyone has experience in doing two machine debugging, feel welcome to head over to the other thread.

 

Well, it did not work for me ;)

 

I got the blue-grey screen, no mouse and CAPS did not work either while in that blue-grey screen!

 

So I have used the commands that you provided (above), and now I'm back, THANKS AGAIN! ;)

(I have to mention that using my ID as 2e22 did not work but with 2E22, did; it was this CAPITAL leter E also important at the first run of the script for native resolution??)

 

Also, I think I have to add that I am still on iDeneb 1.3 - 10.5.5 (I am afraid to update since I did not find a working solution for that yet, and the install on my computer at home -i7- just crashed because the iDeneb 10.5.7 update Kit).

 

Any other ideas to this native resolution or even a point to a GOOD and WORKING path to update?!?

Thanks in advance to anyone that might bring some solutions!

 

Glad to hear it didn't work :P Well, actually, glad you understood my explanation ;)

 

The capital E is not important in the patching process, since the script capitalizes your device ID before it does the patching ;)

I don't know if it works on 10.5.5, I didn't try that, so can't confirm wether it should work or not.

 

The update progress is indeed not as easy as just pushing update, I had to do a lot of manual console work to update, and I can believe that that's not the easiest way to do it.

I can't point you straight to a good solution, but using the forum search you should be able to find what you need ;) Or there might be someone here that can help you with that, hopefully ;) (but maybe send that information in PM's, so this thread stays reserved for X4500 talk?)

Link to comment
Share on other sites

Hey all, just to say I tried this, and absolutely nothing. System boots like normal, as if i've changed nothing, so Neither good nor bad.. But what else can I do? Followed exactly dev ID was 2a42, as many others. and nada.

 

EDIT: I deleted one of the .kext files for the x3100 and it now detects and I have the option to change resolutions. Only downside now being, that he bottom edge of my screen repeats, that is, the screen stops and the bottom cm basically repeats (like repeating wallpaper) but the mose cant get there. Is this a resolution detection issue?? I have the options for like 1280x768 instead of 800.

Link to comment
Share on other sites

Works for me. But sad to say that watching any kind of video leaves me with disappointment, without full support it is just not worth it imo. But great work hopefully we will receive a miracle soon. I am done till that miracle happens, back to windows for the time being.

Link to comment
Share on other sites

Again thanks for the great work, it's great seeing this setup nice and.... crisp!

 

BUt I have tried the boot command;

 

-v "Graphics Mode"="1280x800x32@60Hz" also and still got nada, in terms of proper resolution, its still at 768, leaving that extra bar at the bottom of the screen that repeats stuff from the top (like repeating wallpaper). Any suggestions if anyone else has seen this?

Link to comment
Share on other sites

I am in a Sony Vaio VGN-NW125J and the patch worked, but not 100%. I get way better reslotion than what I had before, but I don't have the 1600x900, I only have what appear to be "non wide screen" resolutions, so I get crisp image, but it does not use 100% of the screen, I have a black line of about one inch on the right side, the black line does not affect the view area since its like if that inch was turned off.

 

Is there a setting somewhere or a way to add the 1600x900 to the options?? or do I have to live with the screen not using my whole screen??

Link to comment
Share on other sites

I am in a Sony Vaio VGN-NW125J and the patch worked, but not 100%. I get way better reslotion than what I had before, but I don't have the 1600x900, I only have what appear to be "non wide screen" resolutions, so I get crisp image, but it does not use 100% of the screen, I have a black line of about one inch on the right side, the black line does not affect the view area since its like if that inch was turned off.

 

Is there a setting somewhere or a way to add the 1600x900 to the options?? or do I have to live with the screen not using my whole screen??

 

I think you'll have to live with that resolution :s for now. You could try the alternate method with chameleon 2, but I can't help with that one (didn't use it.. Only used the framebuffer method I posted, since I find it more straightforward, and it works (for me))

Link to comment
Share on other sites

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

 

Same thing here. Same Device ID (gma 4500mhd - inspiron 1545). After applying the patch instead of login screen, the screen turns black.

Also tried to modify the kext manually replacing the Device ID.

I found somewhere a GMAX4500.pkg also not working.

 

What does "This only applies to people previously running kernel extensions provided by me in the other thread." (original Thread) Do I need other kext - which post, i can`t find it?,

im running Iatkos v7.

Link to comment
Share on other sites

What does "This only applies to people previously running kernel extensions provided by me in the other thread." (original Thread) Do I need other kext - which post, i can`t find it?

 

There is another thread in the Hardware>Graphics Cards>Intel which was actually the start of this project. The kext that he is refering to is one that was patched by him before it was distributed. It actually gives the identical result to using the script to copy/modify the kexts. You can't use both kexts because it would mean that the system would try to load 2 identical kexts for the same thing.

 

iPoco

Link to comment
Share on other sites

 Share

×
×
  • Create New...