Jump to content

GMA X4500


  • Please log in to reply
1614 replies to this topic

#261
enzobelmont

enzobelmont

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 168 posts
Trauma! can you tell me how to use dsdt.aml file (sorry)

#262
coldequation

coldequation

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 118 posts
Edit: Summary so far & ANALYSIS OF BSD SOURCE:

Edit: Action items are highlighted with ===> ACTION:

Hi all:

Summary:
=======

Here's a quick summary to catch up all who don't want/need to read all the recent posts.

My goal was to see if the X3100 kexts could drive the 4500 (4-series) chips. I believe this to be important because with Apple moving to Nvidia, the majority of budget Windows laptops now use Intel 4-series chips. The net result is that the OSx86 world is moving steadily towards custom desktops. Philosophically, I have little problem with that as Apple makes excellent laptops (I have one), whereas their desktop offerings are not competitive for power users. But Apple's laptops remain pricey for many users, especially those outside the USA.

In my quick reading of the Intel chipset manuals, it seemed that the 4-series was basically compatible with earlier Intel chipsets and graphics cores. I suggested an experiment that Tienneke, Trauma, mindphazer, enzobelmont and others have tried. Basically we hexedited device ids into the AppleIntelGMAX3100 and AppleIntelGMAX3100FB kexts. We had a short term positive result in that the 4-series can now be used at native resolutions without resorting to grub-tricks, or special Chameleon VESA patches.

EDIT: However, the goal of a fully QE/CI supported 4-series has remained elusive. The basic problem is that the AppleIntelGMAX3100 is not getting loaded. The AppleIntelGMAX3100FB does load. Trauma has tried some further experiments with DSDT injection, but so far, that hasn't worked either.

Today, I examined the BSD changes (thanks Martin255) that added 4-series support to find evidence for or against my hunch. Since the Intel Linux drivers and BSD sources are similar, it's possible that even Apple's OS X (another Unix derivative) might follow suit. I've managed to examine all of the BSD changes that Martin pointed me to, as well as some others in the tree.

Note: I *did not* examine any fixes after the patch which enabled 4-series support. I do think that will have to be done, but since the fixes came from Intel, maybe not.

CAVEAT: I am not a graphics programmer. So could someone check my logic/conclusions below?

RESULTS:
======


I *do* believe that we can make the X3100 work for the 4500 (4-series) chips, *if* we can control some addresses that are controlled by the kext. But to determine for sure, we will need help from anyone who has experience with video drivers (perhaps the XLabs guys, paulicat, netkas, Slice or others I don't know). I've tried to indicate what I consider to be *significant* problems, and *non-significant* issues.

===> ACTION: Can someone forward/send/PM this post to those guys?

DETAILS:
=======


Feel free to skip this part if you have no interest. I've tried to document my assumptions and conclusions, so others can verify or refute if they get a chance.

1. The defines:
+#define PCI_CHIP_IGD_E_G_BRIDGE 0x2E00
   +#define PCI_CHIP_G45_G_BRIDGE	0x2E20
   +#define PCI_CHIP_Q45_G_BRIDGE	0x2E10

It looks like subtracting 2 from the device id gets you the device id of the chipset "bridge". On both the MacBook X3100 and the HackBook X3100, there is a device in ioreg called MCHC ("acpi-path" = "IOACPIPlane:/_SB/PCI0/MCHC@0") that is registered against it. The BSD source defines new constants for the 4-series bridges, but I don't know how significant that is, because on my GMA950, I just have a device called "pci8086,27a0@0" and my display functions (albeit with artifacts).

CONCLUSION: *not significant* (although it might be nice to add the MCHC to one's DSDT, so the ioreg output looks "pretty.")

2. This lines:
#define IS_I965G(pI810) (DEVICE_ID(pI810->PciInfo) == PCI_CHIP_I965_G || 
	   DEVICE_ID(pI810->PciInfo) == PCI_CHIP_G35_G || DEVICE_ID(pI810->PciInfo) == PCI_CHIP_I965_Q || 
	   DEVICE_ID(pI810->PciInfo) == PCI_CHIP_I946_GZ || DEVICE_ID(pI810->PciInfo) == PCI_CHIP_I965_GM || 
	   DEVICE_ID(pI810->PciInfo) == PCI_CHIP_I965_GME || IS_IGD_GM(pI810) || IS_G4X(pI810))
CONCLUSION: *not significant* Code that uses IS_I965G (Desktop chipsets) considers the G4X series to be just a variant of the 965.

This is great! It means that for most purposes the 4-series (G4X) is compatible.

3. Seems that the differences between the various 4500 versions (with the notable exception of the laptop/mobile GMA 4500MHD) are pretty much ignored:

PCI_CHIP_IGD_GM/IS_IGD_GM (0x2a42) is the Cantiga with GMA 4500MHD graphics core
PCI_CHIP_IGD_E_G (0x2E02) is probably the G41/G43 chipset with GMA X4500 graphics core
PCI_CHIP_G45_G (0x2E22) is the G45 chipset with GMA X4500HD graphics core
PCI_CHIP_Q45_G (0x2E12) is the Q45 chipset with GMA 4500 graphics core

The line:
#define IS_G4X(pI810) (DEVICE_ID(pI810->PciInfo) == PCI_CHIP_IGD_E_G || 
	   DEVICE_ID(pI810->PciInfo) == PCI_CHIP_G45_G || 
	   DEVICE_ID(pI810->PciInfo) == PCI_CHIP_Q45_G)
CONCLUSION: *not significant* The Desktop GMA 4500, GMA X4500HD, and GMA X4500 or GMA X4500HD are treated effectively the same in the code. This means there should not be much variation between the desktop versions of the 4-series graphics core.

4. OK, to figure out the Laptop/Mobile GMA4500MHD we need to look at a previous commit to the one Martin sent. Looking at this: http://cgit.freedesk...3fbce21492a7c32

CONCLUSION: *not significant* the changes in adding IS_IGD_GM (GMA4500MHD) were very minor. This implies that a laptop with GMA4500MHD *could* work with very minor editing (device id hexediting of the laptop X3100 kexts), assuming Apple hasn't done anything weird in the X3100 kexts. This may also explain why people struggle getting desktop 3100s or 3500s to work. But see below:

4. This line:

+/* mark chipsets without overlay hw */
   +#define OVERLAY_NOEXIST(pI810) (IS_IGD_GM(pI810) || IS_G4X(pI810))
means that the GMA 4500 (Q45), X4500HD (G45), and X4500 (G41/G43) all do not have overlay hardware. More on that later:

5. This change:

/* chipsets require graphics mem for hardware status page */
   -#define HWS_NEED_GFX(pI810) (IS_G33CLASS(pI810) || IS_IGD_GM(pI810))
   +#define HWS_NEED_GFX(pI810) (IS_G33CLASS(pI810) || IS_IGD_GM(pI810) || IS_G4X(pI810))
   +/* chipsets require status page in non stolen memory */
   +#define HWS_NEED_NONSTOLEN(pI810) (IS_IGD_GM(pI810) || IS_G4X(pI810))
Means that hardware status (HWS) requires graphics memory. But all the Desktop GMA 3100 (G33/Q35/Q33) do the same. But we don't know what the mobile GMA X3100 (PCI_CHIP_I965_GM and PCI_CHIP_I965_GME) do.

CONCLUSION 1: *not significant* Desktop 3100 and 4-series act the same WRT to HWS (hardware status).

/* new chipsets need non-stolen status page */
	   if (HWS_NEED_GFX(pI830) && HWS_NEED_NONSTOLEN(pI830))
		   mmsize -= HWSTATUS_PAGE_SIZE;
CONCLUSION 2: Desktop 3100 and 4-series act the same WRT to mmsize. (Bad coding here: HWS_NEED_NONSTOLEN is a subset of HWS_NEED_GFX)

CONCLUSION 3: *significant* This could be an ISSUE.

===> ACTION: Can anyone confirm if Apple implemented only the X3100 mobile chips? If they implemented Desktop 3100 (on say the iMac), then we may be okay.

If Apple implemented only 3100 mobile, the implication is that laptop X3100 (PCI_CHIP_I965_GM || PCI_CHIP_I965_GME) *does not need a non-stolen* status page. To fix this, we may need to decrease the amount of memory for the driver by 4KB.

6. This change:

+/* chipsets require status page in non stolen memory */
   +#define HWS_NEED_NONSTOLEN(pI810) (IS_IGD_GM(pI810) || IS_G4X(pI810))
could be significant, since it is ONLY defined for the 4-series (mobile or desktop) but let's see:

+ if (HWS_NEED_NONSTOLEN(pI830))
   flags |= NEED_NON_STOLEN;
CONCLUSION: *significant* The BSD driver allocates a separate, fixed hardware status page of 4KB for the 4-series. But perhaps it will work with stolen memory?

7. OVERLAY_NOEXIST:

CONCLUSION: *significant* The 4-series (desktop & mobile) *do not* allocate any space in the kernel for overlay registers. It's possible that the driver will just fall back to not supporting overlay if we use the X3100 kexts to drive 4-series hardware.

8. These changes:

+#define INTEL_GMCH_GMS_STOLEN_96M (0xa << 4)
   +#define INTEL_GMCH_GMS_STOLEN_160M (0xb << 4)
   +#define INTEL_GMCH_GMS_STOLEN_224M (0xc << 4)
   +#define INTEL_GMCH_GMS_STOLEN_352M (0xd << 4)
are used to setup the The Graphics Translation Table (GTT). For the G33, 965 or older chipsets, the GTT is stolen from your memory, and may or not be larger than the aperture. But:

/* The stolen memory has the GTT at the top, and the 4KB popup below that.
	   * Everything else can be freely used by the graphics driver.
	   */
	  range = gtt_size + 4; // - I think this will be 8 KB ???
   
	  /* new 4 series hardware has separate GTT stolen with GFX stolen */
	  if (IS_G4X(pI830))
		  range = 0;
CONCLUSION: *significant* Your stolen memory's size is decreased by your GTT + 4 KB popup, whatever that is. But the 4-series has it's own stolen GTT, so its effective stolen memory size is not decreased by 8KB. Not sure how to fix this.

9. This change:

if (IS_I965G(pI830)) 
	   {
		   if (IS_IGD_GM(pI830) || IS_G4X(pI830)) {
				gttaddr = pI830->MMIOAddr + MB(2);
				pI830->GTTMapSize = MB(2);
			} else {
				gttaddr = pI830->MMIOAddr + KB(512);
				pI830->GTTMapSize = KB(512);
			}
	   }

CONCLUSION: *significant* It affects the address (location) and size of the GTT. The 4-series will be different from all previous Intel chips.

===> ACTION: Can we do anything with this?

10. This change:

/* Begin the long sequence of commands needed to set up the 3D
		* rendering pipe
		*/
   ...
	   if (IS_IGD_GM(pI830) || IS_G4X(pI830))
		   OUT_BATCH(NEW_PIPELINE_SELECT | PIPELINE_SELECT_3D);
	   else
		   OUT_BATCH(BRW_PIPELINE_SELECT | PIPELINE_SELECT_3D);

Affects the 3D pipeline.

+#define BRW_3D(Pipeline,Opcode,Subopcode) (CMD_3D | \
   + ((Pipeline) << 27) | \
   + ((Opcode) << 24) | \
   + ((Subopcode) << 16))
   
   +#define BRW_PIPELINE_SELECT BRW_3D(0, 1, 4)
   +#define NEW_PIPELINE_SELECT BRW_3D(1, 1, 4)

CONCLUSION: *significant* For 3D graphics, the 4-series use a new pipeline (pipeline 1) while the older cards (including the X3100) use pipeline 0.

Final thoughts:
==========


Given that the ATI drivers seem to use different pipelines, memory sizes, registers, etc, and IOKit being very object-oriented, we may be able to trick the 3100 drivers by pretending to be a different 3100, albeit with different GTT location, overlays, pipelines etc. Or maybe not. But,

Edit: We need to know what's in the X3100 MacBook (and any Apple desktop 3100). So...

===> ACTION: Anyone who knows the EFI Utils, getting strings from EFI, etc. We need to know what (if any) specific keys and values exist for the X3100.

Edit: The ball's in the community's court now.

==coldequation==

-u

#263
nomi81

nomi81

    InsanelyMac Protégé

  • Members
  • Pip
  • 44 posts
  • Gender:Male
  • Location:Saudi Arabia
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.

#264
deathanarchist2

deathanarchist2

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 114 posts
I have a GMA x4500 mhd is there anything i can do to help and does that post mean im more likely to be supported in the near future?
edit it works for dection of card but i have major artifacts

#265
Tienneke

Tienneke

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 206 posts
  • Gender:Male
  • Location:Mechelen (Belgium)

I have a GMA x4500 mhd is there anything i can do to help and does that post mean im more likely to be supported in the near future?
edit it works for dection of card but i have major artifacts


Did you use the custom DSDT.aml that trauma made for me? Try the previous version maybe, cause with this version I have the same problem, with the previous version it works better for me (then again, that DSDT was made for my hardware, so it would be strange if it wouldn't give some kind of problem on your pc..)

Do you get to your desktop in normal boot, and do you have qe/ci?

#266
WinSucks_4ever

WinSucks_4ever

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 212 posts
  • Gender:Male
  • Location:Manchester, UK
Hi guys I have a question!
Is there anyway to force the translucid menubar in Leopard without QE/CI
Please a tweak or something

#267
Trauma!

Trauma!

    Took too much...

  • Members
  • PipPipPipPipPipPipPip
  • 964 posts
  • Gender:Male
  • Location:France
Coldequation,

Thanks for this analisys ! What i can tell is Apple has only used X3100 in Macbook3,1. See attached documents about MacBook and is X3100 :

- DSDT injections to match original MacBook3,1 IOreg.
- MacBook3,1 IOreg save.
- MacBook3,1 DSDT and SSDT Dumps.
- The script to quickly patch X3100 driver to X4500MHD ID's.
- A set of patched drivers, for testing purpose.
- A Natit to works with 950 / X3100 and hopefully X4500.

My thought, if the framebuffer runs fine without injection we may not need to use injection at all.



#268
coldequation

coldequation

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 118 posts
Critical question is whether the framebuffer is loading. <= Title

Bonjour Trauma, Comment a va?

Thanks for the thanks :) and thanks for the files you posted. I will take a look.

I believe the critical question is to determine whether the framebuffer is loading.

Tienneve, enzobelmont: is there any way you can ssh into your box and tell? Also, did either of you find out whether AppleIntegratedFrameBuffer is interfering with the AppleGMAX3100FB loading? Earlier, I suggested deleting/moving it to see if it makes a difference.

My analysis leads me to believe that we should first concentrate on the GMA4500MHD, as it is the most compatible with the X3100.

Also, if would be good if someone could find an EFI strings dump from a real X3100 Mac, and turn it into a plist for us to study. We could then see if there is a key to alter the pipeline, overlay, and memory regions. We may end up finally hexediting those into the kext if there is no way from the AAPL/EFI keys.

Back later,
-u

Coldequation,

Thanks for this analisys ! What i can tell is Apple has only used X3100 in Macbook3,1. See attached documents about MacBook and is X3100 :

- DSDT injections to match original MacBook3,1 IOreg.
- MacBook3,1 IOreg save.
- MacBook3,1 DSDT and SSDT Dumps.
- The script to quickly patch X3100 driver to X4500MHD ID's.
- A set of patched drivers, for testing purpose.
- A Natit to works with 950 / X3100 and hopefully X4500.

My thought, if the framebuffer runs fine without injection we may not need to use injection at all.



#269
WinSucks_4ever

WinSucks_4ever

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 212 posts
  • Gender:Male
  • Location:Manchester, UK
Coldequation,

Thanks for this analisys ! What i can tell is Apple has only used X3100 in Macbook3,1. See attached documents about MacBook and is X3100 :

- DSDT injections to match original MacBook3,1 IOreg.
- MacBook3,1 IOreg save.
- MacBook3,1 DSDT and SSDT Dumps.
- The script to quickly patch X3100 driver to X4500MHD ID's.
- A set of patched drivers, for testing purpose.
- A Natit to works with 950 / X3100 and hopefully X4500.

My thought, if the framebuffer runs fine without injection we may not need to use injection at all.

Attached File Archive.zip ( 840.82K ) Number of downloads: 9

Tell me if that works!
I m affraid to test because If my system breaks I need to install Mac OS X againt!

how do I do to delete a kext using -s command
and /sbin........

I want to delete natit.kext

please guys I need the anwsore today!!!!!!!!

#270
coldequation

coldequation

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 118 posts
Your enthusiasm is noted but, <== TITLE

Rubenmarques,

Your enthusiasm is noted, but until we get some detailed and repeatable instructions, I would suggest waiting.

And that advice is to all who consider themselves noobs. I'm not being pejorative as we were all noobs once. But right now, we need to have some volunteers who can do some basic stuff: research, testing, idea generation, provide moral support :) , and communicate with the Elder Gods of the OSX86 universe. So if any noob-oriented questions are ignored, trust that we are focusing down on the problem.

Check back every few days. I'm sure if something works, you'll see a title of "WORKING!!!" or "HEAVENS HAVE OPENED!!!!!!" :D

P.S. don't take this in a bad way. We all have only so much bandwidth.

Thanks,
-u

how do I do to delete a kext using -s command
and /sbin........
I want to delete natit.kext


Type -s when you boot the machine. That puts you into single-user mode and does not run the desktop.

At that point, it gives you two commands to type to check and mount the filesystem. I don't remember them from memory, but the first is fsck, and the second is a mount command, mounting the / directory.

IIRC, you should be root at that point, so you can:
cd /System/Library/Extensions
rm -rf natit.kext

be careful with the rm command! One way to check that you don't delete anything else is when you start to type nat, hit the TAB key and the shell will complete the filename for you. Also, remember that filenames are case-sensitive, so make sure which it is, natit.kext or Natit.kext.

You can use the ls command to check, before removing with rm; ls lists the files in the directory.

Once you have removed natit, then reboot with the -f option to get rid of your kext cache (it reloads all of them).

#271
WinSucks_4ever

WinSucks_4ever

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 212 posts
  • Gender:Male
  • Location:Manchester, UK

Your enthusiasm is noted but, <== TITLE

Rubenmarques,

Your enthusiasm is noted, but until we get some detailed and repeatable instructions, I would suggest waiting.

And that advice is to all who consider themselves noobs. I'm not being pejorative as we were all noobs once. But right now, we need to have some volunteers who can do some basic stuff: research, testing, idea generation, provide moral support :) , and communicate with the Elder Gods of the OSX86 universe. So if any noob-oriented questions are ignored, trust that we are focusing down on the problem.

Check back every few days. I'm sure if something works, you'll see a title of "WORKING!!!" or "HEAVENS HAVE OPENED!!!!!!" :D

P.S. don't take this in a bad way. We all have only so much bandwidth.

Thanks,
-u



Type -s when you boot the machine. That puts you into single-user mode and does not run the desktop.

At that point, it gives you two commands to type to check and mount the filesystem. I don't remember them from memory, but the first is fsck, and the second is a mount command, mounting the / directory.

IIRC, you should be root at that point, so you can:
cd /System/Library/Extensions
rm -rf natit.kext

be careful with the rm command! One way to check that you don't delete anything else is when you start to type nat, hit the TAB key and the shell will complete the filename for you. Also, remember that filenames are case-sensitive, so make sure which it is, natit.kext or Natit.kext.

You can use the ls command to check, before removing with rm; ls lists the files in the directory.

Once you have removed natit, then reboot with the -f option to get rid of your kext cache (it reloads all of them).



#272
Trauma!

Trauma!

    Took too much...

  • Members
  • PipPipPipPipPipPipPip
  • 964 posts
  • Gender:Male
  • Location:France
Here you are coldequation :D

a va bien merci !

Exctrated from the ioreg i've posted earlier.




Cheers.

And please people stop spamming the thread with inappropriate questions ! We are looking for a solution to make X4500MHD works fully.... be sure you'll know it when it will work fine. :)

@ rubenmarques : If you don't know how to use this forum... please clean your mistakes at least :)

@ Tienneke : Try to add that inside natit plist in the "Unknow" dictionary (<dict>)

<key>revision-id</key>
	<data>
	AwAAAA==
	</data>


#273
ADN

ADN

    InsanelyMac Protégé

  • Members
  • Pip
  • 5 posts

Mount your file system in read/write then :

sudo rm -R /System/Library/Extensions/2A42AppleIntelGMAX3100.kext
sudo reboot

Use -f for first boot.

Should be enough.

If not :

sudo rm -R /System/Library/Extensions/2A42AppleIntelGMAX3100FB.kext
sudo rm -R /System/Library/Extensions/Natit.kext
sudo reboot

Did you see natit outputs during the boot ?


Hi,

I try all case but its not work. Maybe I will reinstall and test your driver :).

Thanks

#274
enzobelmont

enzobelmont

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 168 posts

Tienneve, enzobelmont: is there any way you can ssh into your box and tell? Also, did either of you find out whether AppleIntegratedFrameBuffer is interfering with the AppleGMAX3100FBloading? Earlier, I suggested deleting/moving it to see if it makes a difference.

-u


i've deleted2A42AppleGMAX3100FB and my system do not load the GUI...

#275
Trauma!

Trauma!

    Took too much...

  • Members
  • PipPipPipPipPipPipPip
  • 964 posts
  • Gender:Male
  • Location:France
PLEASE DO NOT INSTALL THIS EXCEPT IF YOU DO KNOW WHAT YOU DO !!!! PLEASE

THERE IS 99% THIS WILL MESS UP YOUR DISPLAY.

All others a welcome to test it freely of course :) :D :)

Maybe i can create an IRC channel so we can discuss live about GMA X4500 debugging ?

#276
coldequation

coldequation

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 118 posts
Je vous remercie de l'avoir trouv.

I'm taking a look and will post an analysis later.

-u

Here you are coldequation :D

a va bien merci !

Exctrated from the ioreg i've posted earlier.




Cheers.

And please people stop spamming the thread with inappropriate questions ! We are looking for a solution to make X4500MHD works fully.... be sure you'll know it when it will work fine. :)

@ rubenmarques : If you don't know how to use this forum... please clean your mistakes at least :)

@ Tienneke : Try to add that inside natit plist in the "Unknow" dictionary (<dict>)

<key>revision-id</key>
	 <data>
	 AwAAAA==
	 </data>



#277
coldequation

coldequation

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 118 posts
IRC is a good idea. I won't be able to take part today (4th of July festivities-- after days of rain it is beautifully sunny right now!)

Some quick ideas off the top of my head:
AAPL,DisplayConfig - what is in here? What is known is that it needs to be set for mirror mode to work...
AAPL01,EDID - may need to be set, since it will be different for each laptop.
AAPL01,Pipe - wohoo! Could enable us to set an alternate pipe for the 4-series!
AAPL01,T0 - AAPL01,T6 - what are these???
IODeviceMemory - gives us access to memory addresses and size, I think
IOFBMemorySize - what is its relation to stolen memory?

As far as the remaining issues, Linux does detection of them (using code Intel authored, but similar code could be present in OSX).

So for an X3100:

(II) intel(0): Integrated Graphics Chipset: Intel® 965GM
(--) intel(0): Chipset: "965GM"
(--) intel(0): Linear framebuffer at 0xE0000000
(--) intel(0): IO registers at addr 0xF8100000
(II) intel(0): 2 display pipes available.
(==) intel(0): Using XAA for acceleration
(II) intel(0): detected 512 kB GTT.
(II) intel(0): detected 7676 kB stolen memory.
(==) intel(0): video overlay key set to 0x83e

Perhaps we can use Linux on a X3100, and get the addresses and settings we need from the machine. Then in OSX *on the same machine*, look into the X3100 ioregistryexplorer and see if we can find map the addresses and sizes to where they are in OSX. Then we can see if we can adjust for differences on the 4-series and test on a 4-series.

Does that sound stupid? You may argue that the sizes will be determined at kext load, but the BSD code #defines many of the sizes, depending on the chipset. Which helps us!

Off to enjoy the day,
-u

PLEASE DO NOT INSTALL THIS EXCEPT IF YOU DO KNOW WHAT YOU DO !!!! PLEASE

THERE IS 99% THIS WILL MESS UP YOUR DISPLAY.

All others a welcome to test it freely of course :( :) :D

Maybe i can create an IRC channel so we can discuss live about GMA X4500 debugging ?



#278
deathanarchist2

deathanarchist2

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 114 posts
Im just wondering since i have one why is the 4500 mhd more comp with osx then any of the other chipsets if i had to assume Id say it is closer to either the 950 or 3100 correct? or is it just normaly detected and i was wondering is there a way i can replace my boot file without being able to boot into osx my pcefi 10 seems to be conflicting with the patched dsdt and pcefi10 requires that you have dsdt in the root so i cant sudo rm /dsdt.aml

#279
Tienneke

Tienneke

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 206 posts
  • Gender:Male
  • Location:Mechelen (Belgium)

Je vous remercie de l'avoir trouv.

I'm taking a look and will post an analysis later.

-u


I'll try later this evening, just back from work..

Btw, could you explain why you add a certain string, or what it should do? I like to understand what a change does :D

On which IRC channel can we meet? And on which IRC server?

#280
Tienneke

Tienneke

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 206 posts
  • Gender:Male
  • Location:Mechelen (Belgium)

Im just wondering since i have one why is the 4500 mhd more comp with osx then any of the other chipsets if i had to assume Id say it is closer to either the 950 or 3100 correct? or is it just normaly detected and i was wondering is there a way i can replace my boot file without being able to boot into osx my pcefi 10 seems to be conflicting with the patched dsdt and pcefi10 requires that you have dsdt in the root so i cant sudo rm /dsdt.aml


To remove your patched dsdt you should boot using the install dvd, mount your drive through the console, and then remove the dsdt.. Once again, that patched DSDT was made specially for my pc, DON'T TRY IT ON YOURS, as it'll give you problems for sure.. (I think I already posted that before.. Pls try to read the thread completely, and as said above, only try the experimental stuff if you know your way around the terminal and like getting your hands dirty.. For easier stuff, head over to the tutorial at genius bar, there I have explained in an easy matter how to get to native resolution (the only thing working now) in a very easy and straightforward way..





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy