Jump to content

GMA X4500


aldo77
 Share

1,615 posts in this topic

Recommended Posts

Well, it may be interesting for yours my dear frends!!!

 

I am on my way to a new method of getting it working.

Try now with DSDTSE. Click Extract DSDT. Choose DSDT Hacks -> Method DTGP, Copy method to your decompiled DSDT, then select Hacks -> Intel GMA950 Desktop Hack (rename GMA950 to X3100)or X3100 Laptop Hack (if you have a laptop). copy method to your DSDT. do everything according to instructions given in hacks!!!

 

patch kxts with your dev-id's.

have fun! if you have enough magic and fortuna then you get all thesse accelerations (CI/QE/GL)!

 

i'll probe it myself and give you results later...

Link to comment
Share on other sites

In my opinion, X3100 kexts will never accomplish QE/CI. It's like trying to get driver for card A to work with card B, two VERY different cards. It just won't cut it. There's more of a chance with the new IntelHD kexts, however i still don't think the QE/CI Engine is implemented in these kexts.

Link to comment
Share on other sites

Well, it may be interesting for yours my dear frends!!!

 

I am on my way to a new method of getting it working.

Try now with DSDTSE. Click Extract DSDT. Choose DSDT Hacks -> Method DTGP, Copy method to your decompiled DSDT, then select Hacks -> Intel GMA950 Desktop Hack (rename GMA950 to X3100)or X3100 Laptop Hack (if you have a laptop). copy method to your DSDT. do everything according to instructions given in hacks!!!

 

patch kxts with your dev-id's.

have fun! if you have enough magic and fortuna then you get all thesse accelerations (CI/QE/GL)!

 

i'll probe it myself and give you results later...

 

Thanks man. Good luck! Hope it works...

Link to comment
Share on other sites

Well, what we need is to set device id of GFX0 device in our DSDT to one of the GMA950 or X3100.

I don't know how to do that and would be grateful if someone helps ))

 

all i need is to know the name of "device id" string and "where" the device id is stored!

for example we have :

"device_type",

Buffer (0x08)

{

"display"

},

 

"model",

Buffer (0x07)

{

"X3100"

},

 

"built-in",

Buffer (One)

{

0x01

}

we have to add something like this:

"$id????",

Buffer (0x??)

{

"0x2A02"

},

Link to comment
Share on other sites

Trying to hack GMA950 kexts.

i think its simpler to implement cause its PCI and compatible with all other chips (its i915 if it means anything for you), kexts load normal without blue screens…

 

P.S.: I did not have any success with X3100 kexts in 32-bit mode with or without DSDT patch.

(always blue screens and hangs, very slow framebuffer in console - its like symbol by symbol typing)

Link to comment
Share on other sites

I have success loading both ApleIntegratedFB and GMA950 kexts without errors

no acceleration yet, now i will try patching dsdt

 

notice, both kexts are loaded! I didnt hex edition!

 

EDIT: efi string did nothing

Link to comment
Share on other sites

I have success loading both ApleIntegratedFB and GMA950 kexts without errors

no acceleration yet, now i will try patching dsdt

 

notice, both kexts are loaded! I didnt hex edition!

 

EDIT: efi string did nothing

 

are you getting native resolution?

Link to comment
Share on other sites

are you getting native resolution?

hmm…no.

i'll try hex edition of course.

 

also framebuffer is slow if i set custom res. in boot plist

dsdt compiles with warnings and i cannot inject efi strings via boot plist nor via dsdt

 

I need help people, may be one more experimentator to play with GMA950 kexts!!

 

UPDATE:

Bingo! I set the ball rolling ;]

What i've done is Hex-edited AppleIntelIntegratedFramebuffer.kext and AppleIntelGMA950.kext.

replaced 86808225 by 8680322E. both kexts loaded OK in 32 bit mode, no native resolution, no accelerations,

 

BUT

i got this:

Intel GMA 900:

 

Модель набора микросхем: GMA 900

Тип: GPU

Шина: Встроенный

VRAM-память (всего): 64 МБ совместно используемой памяти системы

Производитель: Intel (0x8086)

ID устройства: 0x2e32

Ревизия: 0x0003

Информация Kernel Extension: Не загружено Kext

which means system profiler says i have GMA 900 chip!!!

and "No kext loaded" in the end (((

I also don't see AppleIIFB and GMA950 kexts in SystemProfiler anymore. what happened?

it looks like it injects card info but unloads kexts

Link to comment
Share on other sites

Thats because the kexts can not work with the x4500 card. I don't know why before the release of the new macbooks everyone had agreed it was impossible to get the QE/CI enabled on the x4500 with X3100/GMA950 kexts and now all of a sudden you think it's possible again. It isn't. Your best shot is the new IntelHD kexts

Link to comment
Share on other sites

Thats because the kexts can not work with the x4500 card. I don't know why before the release of the new macbooks everyone had agreed it was impossible to get the QE/CI enabled on the x4500 with X3100/GMA950 kexts and now all of a sudden you think it's possible again. It isn't. Your best shot is the new IntelHD kexts

The new ideas born new opportunities, so you can not be sure.

Link to comment
Share on other sites

hmm…no.

i'll try hex edition of course.

 

also framebuffer is slow if i set custom res. in boot plist

dsdt compiles with warnings and i cannot inject efi strings via boot plist nor via dsdt

 

I need help people, may be one more experimentator to play with GMA950 kexts!!

 

UPDATE:

Bingo! I set the ball rolling ;]

What i've done is Hex-edited AppleIntelIntegratedFramebuffer.kext and AppleIntelGMA950.kext.

replaced 86808225 by 8680322E. both kexts loaded OK in 32 bit mode, no native resolution, no accelerations,

 

BUT

i got this:

 

which means system profiler says i have GMA 900 chip!!!

and "No kext loaded" in the end (((

I also don't see AppleIIFB and GMA950 kexts in SystemProfiler anymore. what happened?

it looks like it injects card info but unloads kexts

X-user if you have system profiler seeing a gma 950 you should have a look at the intel GMA945 by Andy Vandijck thread in New Releases and Up Dates.He has a gma graphics enabler for chameleon maybe this could work with your patched kexts

Link to comment
Share on other sites

The new ideas born new opportunities, so you can not be sure.

 

I agree with the new ideas thing, however the hardware is too different. I'd love to be corrected here, but the kext for GMA950 or the one for X3100 simply were not made for the X4500, the hardware on the X4500 includes new hardware features. Here's an example. the X4500 in windows is a DX10 card. Good Luck trying to get DX10 working on a X3100 with the X4500 drivers. It simply will not work.

Link to comment
Share on other sites

I agree with the new ideas thing, however the hardware is too different. I'd love to be corrected here, but the kext for GMA950 or the one for X3100 simply were not made for the X4500, the hardware on the X4500 includes new hardware features. Here's an example. the X4500 in windows is a DX10 card. Good Luck trying to get DX10 working on a X3100 with the X4500 drivers. It simply will not work.

 

If you followed the topic, you need to know that there are so many issues with the IntelHD driver.

Link to comment
Share on other sites

Oh, i've been following this topic since the beginning. I was shortly after it was created. I'm well aware of the fact the new drivers haven't proven very...successful. However, and as I've said like 3 times now, too many hardware differences to make x3100/gma950 kexts work with x4500 (for QE/CI)

Link to comment
Share on other sites

huh, i've gone through forums and found this interesting thread : http://www.insanelymac.com/forum/index.php?showtopic=168014

Man here says that we can trick device-ids via DSDT without patching kexts.

This maybe interesting! Hope you see and test it.

 

Since we hexedit kexts we do blind edition, cause we don't actually know what is it for, its hardcoded,

so this method could help a lot

 

 

UPDATE: Successfully changed device id from 2e32 to 2a02 using this DSDT method )))

hope it works for you too!!!

both X3100 kexts load successfully

Link to comment
Share on other sites

huh, i've gone through forums and found this interesting thread : http://www.insanelymac.com/forum/index.php?showtopic=168014

Man here says that we can trick device-ids via DSDT without patching kexts.

This maybe interesting! Hope you see and test it.

 

Since we hexedit kexts we do blind edition, cause we don't actually know what is it for, its hardcoded,

so this method could help a lot

 

 

UPDATE: Successfully changed device id from 2e32 to 2a02 using this DSDT method )))

hope it works for you too!!!

both X3100 kexts load successfully

 

 

What about faking the Intel HD device ID on DSDT? This may lead us to sth....

Link to comment
Share on other sites

What about faking the Intel HD device ID on DSDT? This may lead us to sth....

 

I have intel hd from core i3 330m and blank screen upon boot with integratedfb kext in S/L/E...not to sure where to go from here. The only thing I can see that might be different is the revision, mine is 02, not sure what the MBP is...also the appleintelhdintegratedfb.kext is likely trying to find the nvidia card, which could be preventing the showing of the login screen. At the blank screen, I can change volume levels and that works, but nothing else shows....any insight would be great!

Link to comment
Share on other sites

 Share

×
×
  • Create New...