Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About coldequation

  • Rank
    InsanelyMac Geek
  1. [SOLVED] Help Needed Getting pin configs from working VoodooHDA

    To those who wondered: getdump does produce the info needed, but not the way I need it, so I wrote a script to massage the output the way I needed it to be.
  2. Hi-- I'm trying to switch back from VoodooHDA to AppleHDA following the guide here: http://www.infinitemac.com/f57/guide-how-t...da-to-sl-t3981/ and here: http://www.projectosx.com/forum/index.php?...65&hl=codec. I had a working AppleHDA under Leopard, but it didn't have a working mike, and the mute didn't work. VoodooHDA fixes both those issues, but stutters playing some mp3s (and yes I have a late dev version, which fixes stuttering after sleep). So I'd like to hand-craft something that has the best of both. The problem: I don't do Windows anymore, so I can't get the pinconfig data from Vista/XP. Is it possible to somehow get the pin configurations from my working VoodooHDA?? Thanks! BTW-- I'm running retail SL on a Gateway laptop.
  3. I had a strange result yesterday while removing older Windows code, and enabling Windows 2006 for Darwin. I was editing my DSDT to take out parts that were specific for older parts of Windows (Win 2001). I also enabled for Darwin, anything that was specific to Windows 2006. When I rebooted, everything seemed pretty much the same, except I no longer had the brightness controls, which are mapped to the Fn-up, and fn-down arrows. So I plan to analyze what changed, and then see if I can make them come back. Might be a clue to that brightness keys issue which bedevils many laptop users: for some it works, others, nothing works.
  4. Which means your DSST has stuck to a particular style consistently. I've seen DSDTs that don't, so caution is needed in trying to enable Windows-specific DSDT code. Still, I was wrong about the code being "defect-based", and you were more correct in your thinking. According to the ACPI spec: Still, one woman's feature is another woman's defect. So a DSDT writer will have to do other things if the OS doesn't support the feature-- a classic workaround as the vendors march down the path to the latest hardware and OS.
  5. Let me know if there's anyway I can help. Your goal is very noble. BTW, there is one thing in your guide that I disagree with. It's in the section where you discuss the fix to override operating system checks. In many cases, vendors put checks in there to enable specific hacks for a particular OS version. By enabling all, you make it difficult to predict which hacks/fixes/or even enhancements are applied. It may end up depending on the order of if statements that test for a particular OS. So where as you put it as "onsider Darwin to be capable of all Win-specific features," what if the DSDT code is really there to work around differences in how the OS handles certain things-- in other words "consider Darwin to be capable of all Win-specific *defects*??
  6. silencers, This is indeed a wonderful DSDT guide. Really the best one out there. It's lacking one thing, however; an explanation of some of the fixes. I've documented some of the fixes elsewhere (don't want to diss insanely by posting where) and I've tried to indicate what the relevant devices, and methods are so that folks who have different hardware can try to create a similar fix. For example, I have a machine that's quite similar to your Tpad, since it uses ICH7 and Core 2 Duo. I'ts also by default very compatible with a MacBook. However, I don't have a GPCT method anywhere, so suggesting pasting the Native ACHI fix above the GPCT method doesn't tell me what context to put it in. I find that if you can possibly correlate things to the ICH7 datasheet, the ACPI 4.0 spec, or implementers guide, then demystifying DSDT becomes easier for all. But please don't take the above as a criticism-- you've done a wonderful job!
  7. How I got Silverlight 3 working

    If you DON'T want to install netkas's kext, try this: 1. First get rid of any old Silverlight installations by opening up a terminal and: rm -rf /Library/Internet\ Plug-Ins/Silverlight.plugin rm -rf /Library/Receipts/Silverlight*.pkg rm -rf ~/Library/Application\ Support/Microsoft/Silverlight rm -rf /Library/Application\ Support/Microsoft/Silverlight/ 2. Next open up the Silverlight.dmg with Pacifist 3. Click on the Contents of Silverlight 3.0.pkg. The Install icon in Pacifist should now be active (un greyed-out). 4. Click Install, give your password and you should be all set. Pacifist apparently doesn't do the run-time check.
  8. GMA X4500

    Jasim-- my instructions were faulty. It turns out that lavender.t distributed only the binary file in his zip file. So you need to: 1. open terminal 2. sudo -s 3. cd /System/Library/Extensions 4. cp -R AppleIntelGMAX3100FB.kext AppleIntelGMAX3100FB.kext.orig 5. mv <path-to>/AppleIntelGMAX3100FB.soft-cursor AppleIntelGMAX3100FB.kext/AppleIntelGMAX3100FB 6. <path-to>/patch4500 -rf 2A42 7. reboot with -f We have two reports in Tienneke's genius bar thread (topic is GMA 4500 under Genius Bar) that this does fix the cursor problem by giving you a software, not hardware cursor. We have one report that it does not work. We are trying to find out why it works for some and not all. Stay tuned, and stay patient -u
  9. SOLVED: X3100 mouse artifact in full resolutions

    lav, Nice work! I've tried to apply your technique to 10.5.6 (AppleIntelGMAX3100FB with no luck. I don't have IDA Pro, so I was using otx and otool. Would you be able to look into 10.5.6 and 10.5.7? If you could share some more details on how you found the location where "getAttribute() method returns FALSE for kIOHardwareCursorAttribute" then I could probably do the same for 10.5.6/10.5.7/10.5.8. Also, I'm curious why you didn't just distribute the zipped kext, with the Info.plist and version.plist. By just distributing the binary, won't there be an issue with using a different (say 10.5.6) version of the Info.plist and version.plist? Or would it just work with any Info.plist and version.plist? -u lav, BTW, I have posted your results to a thread that's trying to get the Intel 4500 working using the 3100 kexts. Lenovo users have a disappearing mouse problem. Two 4500 users have tried your hacked 3100FB kext and it's solved their disappearing cursor problem. I too am a developer. I've been working on hacking the X3100 (not the FB) kext to work on Intel's 4500MHD set of chips. I'm stymied in disassembling the X3100 kext because I don't have tools like IDA Pro. If you have some time, I'd like to know if you can join forces with me on tackling this. I've posted my analysis of the changes made to the BSD drivers to support Intel's 4-series (which were pretty small) here: http://www.insanelymac.com/forum/index.php...t&p=1191941 So far we have a patched X3100FB kext (patched to use the dev ids of the 4500) loading which gives 4500 users native resolution for the first time. Unfortunately, the X3100 kext does not load and dumps its SVG registers, failing on an invalid instruction. I believe that it can't find the Graphics Translation Table. My theory is that we'd basically need to know where to patch the kext to set the following: 1. The address (location) and size of the GTT (Graphics Tranlation Table) 2. The graphics pipeline. For 3D graphics, the 4-series use a new pipeline (pipeline 1) while the older cards (including the X3100) use pipeline 0. 3. The address of the hardware status page which affects the location of the shared memory used by the 4500 versus the 3100. The 4500 BSD driver allocates a separate, fixed hardware status page of 4KB for the 4-series. 4. 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. Let me know if you'd like to help. As an aside, all new budget hardware is using Intel's 4500 MHD series. -u
  10. GMA X4500

    Thanks. I contacted lavender.t yesterday by PM but he hasn't replied. The offsets are different with the 10.5.6 and 10.5.7 kexts, so I'd need his help to fix this. Actually if we could draft him into the 4500 work, that would be great, as he has IDA Pro and disassembly experience (both of which I don't have ) I'll post a message in his thread and see if he replies there.
  11. GMA X4500

    Great. Two reports that it works. Now we need to find out why it doesn't work for mormegil. Can all three of you do the following and post back: 1. open terminal 2. cd /System/Library/Extensions/AppleIntelGMAX3100FB.kext/ 3. grep "AppleIntelGMAX3100FB " Info.plist ** Note the quotes and the trailing space, they are needed. On my 10.5.6 machine, I see: <string>AppleIntelGMAX3100FB</string> lavender.t's hacked kext is a version (I presume 10.5.5 or earlier). Now that we know it works, I'll see if there's a way to use patch4500 to patch whatever kext you have installed. If I can't do that, I'll concentrate on 10.5.7. Tienneke: Once we figure out what mormegil's issue is, can you update the topic? I also think you'll want to highlight macgeek's iWork fixes. If possible, I will try to get that into patch4500 as well. -u
  12. GMA X4500

    You're right. I hadn't opened the zip file. Why did lavender.t do that?? To use the binary then, you need to have a matching Info.plist, or the CFBundleGetInfoString and IOSourceVersion will be mismatched if you copy into your existing kext directory. I guess I'll have to look into editing a 10.5.7 version myself. Sigh.
  13. GMA X4500

    No, you don't want to do that. Then the plist etc may be incorrect. Here's what you want to do: 1. open terminal 2. sudo -s <then enter password> 3. cd /System/Library/Extensions 4. mv AppleIntelGMAX3100FB.kext AppleIntelGMAX3100FB.kext.orig 5. mv <path-to>/AppleIntelGMAX3100FB.soft-cursor AppleIntelGMAX3100FB.kext 6. chown -R 0:0 AppleIntelGMAX3100FB.kext 7. chmod -R 755 AppleIntelGMAX3100FB.kext 8. <path-to>/patch4500 -rf 2A42 9. Reboot with -f (and -v if you feel like it) -u
  14. GMA X4500

    Deleted "vanilla AppleIntelGMAX3100FB binary from the kext" from what kext? I presume not from AppleIntelGMAX3100FB.soft-cursor?
  15. GMA X4500

    twister-- my bad. You actually need to rerun patch4500, to patch lavender.t's hacked kext. Since the 2A42*3100.kext is being deleted anyway, no need to worry about whether a will work with it... macgeek-- you need to rerun patch4500. See my revised instructions above...