Mac OS X Development Development and discussion on the latest hackintosh drivers and methods.
| ||Thread Tools||Display Modes|
Join Date: Oct 2009
12-21-2009, 05:35 PM
Efi strings are extremely vendor specific. And OS specific too (driver set + dsdt...)
For instance, when 10.6 came out, my fassl generated string for 9600m GT 512 GDDR3 under 10.5 had different behaviour, lost HDMI and QE or CI, can't remember which. Same string, different OS
I had to re-generate within 10.6 and dsdt fix for it external VGA and/or HDMI
geeting audio to work with on my ex-laptop was dead simple under 10.5, but I really had to go in dsdt to be able to get basic AUDIO support!!! It went to hell and back with this one!!
Helping others guys and gals with the same brand, model and specs, except 9600m GT 1GB GDDR2 had to generate their own string!
Exact same gfx card but on different vendor... very very slim chance to even work, let alone full potencial...
Absolutely the best thing that can be done is to manually patch the dsdt file to include/exclude/tweak whatever you'd like. Its not that hard actually, but quite intimidating at first.
If you change vendor ID in kexts, they will obviously not find the hardware, unless you change the hardware ID, which I think can only be done via dsdt. What in normally done is the opposite, edit kext to find non-apple-standard ID, or Enablers, like the older HDA enabler, which "morphed" these to translate to VoodooHDA what your system actually had, that could not be read correctly by OSx...
I think my facts are right here, confirmation welcome!
Join Date: Sep 2009
Location: Jersey City, NJ
12-21-2009, 06:07 PM
Reading this thread I involuntarily start to smell smoke....
MINI Cooper '02 | 1.6L | CVT | Moonroof | Red w/ White Stripes
Want the ALC268 mini 9 sound fix? Get it here http://dl.dropbox.com/u/2377323/Mini9SoundPatch.zip
Copyright © 2008-2016 MyDellMini.com.