Jump to content

9600m GT DDR3 (MXM)


tsalat
 Share

4 posts in this topic

Recommended Posts

Hi,

 

i would like to try the OSx on one older computer i have (its an DELL XPS one A2010) but iam facing one problem which i need to solve. The computer has an MXM slot but the default bios doesnt have any MXM structure, the card which was there had the VBIOS adjusted to the computer. One user injected the MXM structure inside the bios and now the card looks its working but the board is still refusing the new HW due to missing information inside the DSDT table. The GPU is working, the screen is working but in the moment i install the drivers the screen will become distorted. Its not a driver issue but missing MXM structure inside the DSDT table (or something like that). I dumped the DSDT table but i have no idea what i should add... can anyone help me with this? The GPU is a 9600m GT DDR3 / 512MB, the BIOS is AMI CORE8 (both files bellow). Any help would be appreciated.

 

 

xpsone.3d-sphere.com/Files/M-020006, with MXM structure 26.zip

xpsone.3d-sphere.com/Files/dsdt-ATI-24.zip

 

Tomas

Link to comment
Share on other sites

  • 3 weeks later...

Hi Guys,

 

with some luck i installed the OSx there,, enclosed the IORegistry report...http://xpsone.3d-sphere.com/Files/TomalfiMac.zip. However iam still suffering from fans getting full speed and GPU incompatibility. Can anyone suggest me how to solve the fans and the GPU? Tomas

 

EDIT: I installed Sierra 10.12.5 and using bootloader (Clover v2.4 rev 4063) 

Link to comment
Share on other sites

 

Hi,

 

no, you are wrong. DSDT is a part of sBIOS, if the description table is missing HW information such as MXM definition it will cause such kind of problems. The MXM structure inside the sBIOS is right, there is no way a vBIOS mod (from the link you posted) could solve this issue, however a sBIOS mod yes, specifically by editing the DSDT part of the single link architecture or by bypassing it by loading a custom one using Clover for example, at least for a test purpose is much more safer than flashing straight the sBIOS. Flashing the vBIOS is quite stupid, dont you think, breaking the checks which are comparing the mxm structure inside sBIOS - vBIOS and bypassing the performance levels is not a fix. Only way a vBIOS could solve this is to made a completely custom one from scratch for the "special" machine.

Link to comment
Share on other sites

  • 4 weeks later...
Well, did it smile.gif

In the first place, the XPS A2010 which is was modding has an MXM II slot but no entry about the MXM structure inside system BIOS. The reason why its not there is because they modified the video BIOS of the default ATI card to inject this while loading the vBIOS into the memory. Therefore there wasnt anything mentioned about the MXM interface in the DSDT as well, thats logicaly smile.png why it should be there in the first place smile.png

Hence, i had to modify all these to make it work. One user injected the MXM structure inside the system BIOS according to the MXM specification 2.1. Wasnt so hard i believe but you need to place there appropriated callbacks for the BIOS to load these, this is something which i cant explain more to be honest. The MXM structure consists from information like the interfaces to which the card can push the signal (internal LCD and so on), maximum power, maximum cooling capabilities and so on. Right after the MXM structure, EDID for the LCD can be add if the LCD doesnt have EDID pins to identify himself. Well, this was the part which add absolutely new feature to the system BIOS and the new card started to work with 3 major problems:
  • The performance was set to throttling
     
  • The picture was ok without the drivers but bad, and i mean really like distorted signal, after installing the drivers
     
  • The fans were all the time at full speed (system and CPU)
Now, the first two problems are a DSDT issue. Because no MXM structure was present before no was added to the description table. Problem is that the DSDT table has some length. IF you want to inject it back to the SBIOS it has to be the same size or smaller. I was lucky because the XPS has a on-board GPU as well. Well, i deleted it from the DSDT table to make room together with some OS entries. The on-board GPU is in this case never active, even with the default DSDT, and therefore no sense to keep it there. After making room i added the MXM structure according to the MXM specification, you can compare both *.dsl files which are attached to see the changes. The MXM structure has an buffer which is equal to the structure which was injected to the SBIOS. This solved the performance problem. To solve the LCD problem i added the _DDC method to the LCD and created an buffer with the EDID of the LCD. This solved the LCD problem.

Now, the fans were a bit more tricky. The DSDT doesnt have any Thermalzone and neither embedded controllers inside. Therefore the DSDT cant be the problem. The SBIOS could have some white list but no error at all. After some time i realized that the Fintek microchip which should control the fans is not used for that but instead Intel QST is controlling it. Well, dammit biggrin.png The Intel ME is not a part of the SBIOS but, i was lucky here, i found tools which could manipulate with the QST config. I looked on the status and realized that while changing the GPU the address of the fan changed and therefore the QST was in an emergency mod and set all fans to 100%. Well, dumped the settings, removed the GPU sensor and its done smile.png

i hope that this will help someone smile.png Tomas
 

dsdt.zip

dsdt-modified.zip

Link to comment
Share on other sites

 Share

×
×
  • Create New...