Jump to content
InsanelyMac Forum


  • Content count

  • Joined

  • Last visited

About McLGF

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
  • Location
    New York
  1. I never had any luck with ATY_Init, despite heavily patching.
  2. Silly question: You are using the dual-architectured (i386 + x86_64) ATY_Init right?
  3. Welcome to the club! I pretty much ran out of all possible combinations and permutations (along with wall space to run my head into...) myself, with the same result as yours: either a blank screen, or a greenish looking screen (with QE/CI) with lots of "noise". I have worked on a different solution for the past couple of weeks, one which involves only DSDT patching. I am helping a fellow member here with an ATI Personality Generator (http://www.insanelymac.com/forum/index.php?showtopic=270527&view=findpost&p=1782048). I believe there are quite a few combinations of connectors, encoders, and transmitters that we don't even know about yet. I've been trying to find official documentation (from Apple or one of the major vendors of supported video cards) on the structure of a framebuffer personality, but alas I have yet to find anything useful. Let me know if you come across something interesting. Let's work together, I am determined to make this darn thing work...it's become "personal" now...
  4. I took the liberty to add to OP mcbyte's code and implemented your suggestions. Here is version 0.2. PS To OP: Feel free to merge, discard, modify, etc. ati_personality.0.2.htm
  5. No. I've been at it for almost four months now, and just a few nights ago I made some progress by achieving QE/CI on partially working outputs (actually HDMI and VGA are working properly, just LVDS is not).
  6. iAtkos L2 not installing :(

    I compiled Chameleon from SVN and installed on USB, the same where my Lion installation is. There are several guides available, like this one. I was able to go through a successful install by adding these boot/kernel flags: arch=x86_64 cpus=1 GraphicsEnabler=N npci=0x2000 pciRoot=0 UsbBusFix=Y Once you go through a successful install, you will most likely have a non working keyboard/touchpad. Have a USB keyboard and mouse ready and follow these instructions: http://iatkos.blogspot.com/2011/12/how-to-install-iatkos-l2-1072-on-hp.html from the section named "Get ready to install additional kexts to fix remaining functionality". Good luck.
  7. Hey there. If you're still working on this, I would like to offer my help. I've been trying to make things work myself, so who knows, perhaps this would be a good opportunity to discover things I have not yet. Let me know.
  8. - Download and install XCode (3.2.x or 4.2.x depending on which OSX version you're running). - Pull down Chameleon source code as follows: - Fire up a Terminal window - Type mkdir chamsrc (or whatever name you prefer to name it) - Type cd chamsrc - Type svn co http://forge.voodooprojects.org/svn/chameleon - this will pull the latest from trunk. If you have a specific version in mind, simply add the version number between co and http . i.e. svn co 1700 http://forge...etc. - Type cd chameleon/trunk/i386/libsaio - Edit ati.c with your editor of choice (you could use XCode's). - Search for string "9553" and you should come up with a section where 9553's are grouped together (I believe latest trunk has two or three definitions). - If your line does not exist already, add it and save the file. - Type cd .. twice and then pwd to make sure you are inside the "trunk" directory (Look at your prompt line, it will show which directory you are in). - Type make clean to prep working folders using during compile. - Type make to start compiling the bootloader, and wait until it's finished. The next steps assume your current configuration has the loader installed in the MBR and the boot file in your OSX installation's root. If you have a different configuration (i.e. dedicated EFI partition), these steps will not work and you will have to refer to other guides you can find on the Internet (Google is your friend...). Also, if you don't want to type "sudo" every time, just type sudo -s once. This will have you rooted. Personally, I root on a "once and only if needed" basis. - Type diskutil list and take note of the identifier assigned to your OSX installation partition (normally it is disk0s2 and that is what I used for these instructions. If yours is different you must make sure you replace when typing the commands below). - Type cd sym/i386 and do a ls . You should have a bunch of boot files with different names, a "modules" folder, etc. - Type sudo ./fdisk440 -f boot0 -u -y /dev/rdisk X << careful here, the X in rdiskX must be replaced to match the X in the diskXsZ part you noted from diskutil. - Type sudo dd if=boot1h of=/dev/rdisk X s Z << again, X and Z from your diskXsZ you noted from diskutil. Normally you would type rdisk0s2 here... You can make a copy of your current boot file, just in case. If you don't want to you can skip the next command. - Type sudo cp /boot /boot.old - Type sudo cp boot / - Type sudo ./fdisk440 -e /dev/disk X << Need I say what N should be, again? - Ignore any messages about the MBR and standalone folders... - Type f 2 - Type write and again ignore any messages about exclusive access. If asked to reboot to complete changes then answer y. - Type exit to return to your bash prompt. - You may optionally copy the entire "modules" folder in /Extra. I don't use it (yet). - Make sure you have your GraphicsEnabler=Y setting in your boot.plist file and reboot OSX. - If you don't KP and the system comes back up, there's a chance or two you may have QE/CI. I hope you do, and I hope this helps.
  9. Hey there, not sure if you're referring to any particular set of steps from that post, or the whole thing is just unclear to you. I filtered some noise out of crazybirdy's post hoping for improved clarity. Basically we can hope to achieve full graphics potential, assuming that the OSX version you are running on is SL(6.6; 6.7; 6.8;) or Lion(7.0; 7.1; 7.2), under two different conditions: 1. Screen resolutions up to 1366x768 2. Screen resolutions higher than 1366x768 1. Achieving full graphics potential with screen resolutions up to 1366x768 Go to /System/Library/Extensions and look for ATI4600Controller.kext and ATIRadeonX2000.kext For each component, descend into its ./Contents folder (either by double clicking in a Finder window or by cd'ing from a bash Terminal). Edit the Info.plist file (again for each of the aforementioned libraries). I prefer using TextWrangler because it unrestricts permissions automatically, allowing for in-place editing, but your editor of choice will work just fine. If using Terminal the good old "sudo nano libraryname" works beautifully. In the file, locate the IOPCIMatch key and add your card in the 0xDeviceIDVendorID format (i.e. 0x95531002). Save. I personally prefer to repair permissions manually as opposed to use any kext installation tools. Open Terminal: sudo chmod -R 755 /System/Library/Extensions/ATI4600Controller.kext sudo chown -R root:wheel /System/Library/Extensions/ATI4600Controller.kext Repeat the two directives above for ATIRadeonX2000.kext. sudo touch /System/Libraries/Extensions/ [*]At this point you need to choose whether you want to use the graphics detection features of your bootloader (Chameleon, Chimera, PCEFI, etc.), or seek the support of a dedicated kext, such as ATY_Init.kext. If opting for the bootloader then edit the org.chameleon.boot.plist file (or com.apple.boot.plist depending on what your bootloader recognizes) and add GraphicsEnabler=Y as shown in crazybirdy's post. If your bootloader is Chameleon and you are fairly confident the Peregrine framebuffer supports your card, then download one of the Chameleon installers crazybirdy posted, install, restart, and hopefully enjoy full resolution and QE/CI. Please note that Peregrine is no longer supported starting with Lion (7.0+), not sure about SL6.8. If your choice is instead that of using ATY_Init.kext, then edit your bootloader config file (org.cham.... or apple.boot...), set GraphicsEnabler=N and save. Download the ATY_Init package from the set crazybirdy posted, that matches your card device id. Copy ATY_Init.kext to /System/Library/Extensions and repair the permissions as shown earlier in this section (or use your kext installer of choice if that's what you're most comfortable with). Restart the system and hopefully enjoy full resolution and QE/CI when it comes back on. 2. Achieving full graphics potential with screen resolutions higher than 1366x768 To be continued...perhaps with new instructions once I get mine working...
  10. Hello everyone, first post here but I've been following for a while. I pretty much tried everything that this guide and bcc9's one suggest but I came to the conclusion that it is impossible to get LVDS working on the Mobility Radeon HD (M92) that came with my system, a three year old HP DV7t-2000. Tried on SL10.6.6, SL10.6.7, SL10.6.8, Li10.7.1, and Li10.7.2 I took card info from Windows (several tools used), Ubuntu (compiled RadeonHD driver and Xorg's info), and OSX(using all the tools indicated in these guides). I got my desktop with a 4670 (94801002) working in about 20 minutes. But I'm now on my third month, and countless sleepless nights, trying to get my 4500 Series (95531002:3629103C) working and getting nowhere. 4600 kext is patched in both 32 and 64-bit modes, using the offsets from the ati-personality.pl script (w/x and w/o x switch), for all three personalities (Shrike, Flicker and Gliff), and contains my card ID in Info.plist. So does the ATIRadeon2000 extension. Chameleon 2.1 Bootloader is recompiled with my card info in Ati.c, using 1732 right from trunk. GraphicsEnabler is set to "Y" of course. The result is KP immediately after the loader reports "Device in SLOT---1" and immediately before the loginwindow should come up. One strange thing I noticed is that the detection code in the bootloader says my subsystem id is 3624 instead of 3629, yet all tools I've tried, no matter which OS they were running, all reported 3629 as the subsystem. I doubt that could be of much relevance, but I wanted to mention it. I truly hope some DV7t-2000 user can prove me wrong, but as it stands QE/CI on LVDS is unattainable on these machines. Saving for a real MacBook...at least I can go to sleep at night rather than banging my head on the wall. PS: Forgot to mention QE/CI works fine with external monitor hooked up to VGA or DMI, as long as I use the AtiConfig=AtiRadeonFrameBuffer switch, but still LVDS remains either blank or green-ish-garbled-up... PS 2: BTW I have been a programmer for 22 years...