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

  1. Intel 4600/ Nvidia GT 750M

    Thanks styrian. Will read that thread and ask there.
  2. Intel 4600/ Nvidia GT 750M

    I'm trying to get back into the scene with a new hack on a Dell XPS 15 9530. Graphics are almost identical to new MBP Retina (MacBookPro11,3) with Intel 4600 (Ven 8086 Device 0416) and Nvidia GT 750M (Ven 10DE Device 0FE4) Clover identifies Intel as primary graphics. I'm trying to install 10.9. When graphics initialize, no further output on LVDS, unless 2nd Monitor is plugged into HDMI, in which case you get a white screen on HDMI and a half white screen on LVDS. Its exactly like we saw with Mobility Radeons before we started patching per Mucha's technique. http://www.insanelymac.com/forum/topic/245308-mobility-radeon-10667-guide-for-qeci-testing-107/ Can the Clover Graphics Injector Menu fix this? And where might I find directions -- the wiki is blank. Any help would be appreciated -- I've been using 2 different MBP in recent years, but this is my first hack in a long time.
  3. [UEFIPatch] UEFI patching utility

    Thanks CodeRush! I missed /gan. Will try tonight. [EDIT] Victory! /gan works. There really is no excuse for my missing this, other than when I read the FAQ I thought I was dealing with a Phoenix BIOS (as every other Dell I've worked on) and missed the link. I also can confirm the stock Dell BIOS can be flashed over the patched BIOS in the usual way, which means updates can be installed, but repatching the BIOS will be necessary afterwards. On to install 10.9 on my mSATA. [EDIT] Reading the startup screen, I can confirm CodeRush's patch gets native power management on Dell XPS 15 9530. However, when graphics initialize, LVDS goes black unless something is plugged into HDMI. Which is exactly the video driver problem we saw on laptops before we started patching the driver. This problem I know how to fix: http://www.insanelymac.com/forum/topic/245308-mobility-radeon-10667-guide-for-qeci-testing-107/ [EDIT] PM'd Slice (who I knew from when we figured how to patch Mobility Radeons). He said my dev ids are not yet injected with Clover, although he will add them to the list. So plan is to disable QE in single user mode, install as VGA like we did with Mobility Radeons, then address the issue. Looks like I might be good with Enoch branch though, so will try that before anything else.
  4. [UEFIPatch] UEFI patching utility

    Thanks CodeRush. It's a signed AMI BIOSs, so looks like all 3 are going the same route. Chip looks soldered -- if it was a socket I might try that.
  5. [UEFIPatch] UEFI patching utility

    Hi CodeRush! Any chance this might be made to work on Dell XPS 15 9530? Attached file includes AIDA64 report, the latest BIOS, and the generated output. [EDIT] I have found I can write the rom file using /writeromfile (instead of the -writeromfile which used to work) I can then patch the resultant rom file using the tool successfully. Have not yet figured out how to flash the rom yet -- how did you repack it into the exe?. PMPatch 0.5.14 PowerManagement modules not found. PowerMgmtDxe/PowerManagement2.efi module at 00234BE8 patched. AMI nest modules not found. Phoenix nest modules not found. CpuPei module at 00759B40 not patched: Patch pattern not found. Output file generated. [EDIT] Its an AMI Aptio BIOS. Patched rom appears to be flashable using AFUWin64 v.3.05.02 I am going to review recovery procedure before I try it. If it works, will install Mavericks and have my 1st new hack in years. [EDIT] Both AFUWin64 and AFUDos won't flash mod files; they complain about secure flash They will flash the unpatched rom. [EDIT] Method is impossible for newer EFI BIOS. See p. 14 "a binary modified after signing will have an invalid signature" http://www.uefi.org/sites/default/files/resources/UEFI_Plugfest_2012Q1_v3_AMI.pdf 9530A01.EXE
  6. Dell E520 with 10.9 - Boot Panic Help

    Its been awhile , but maybe this helps: One issue with the E520 BIOS is you have no AHCI setting. You can either use ATA (slow) or RAID. Recollection is you have to add the device ID (Ven 8086 Dev 2822) to AHCIPortInjector. Another issue is you can install to other drives, but OS X could not find root device unless booted off a disk attached to the 1st SATA port (which is marked SATA0 on the motherboard).
  7. Dell E520 with 10.9 - Boot Panic Help

    I ran 10.5 and 10.6 on my E520 for years. It ran quite well. Install guide was here: http://www.insanelymac.com/forum/topic/192626-dell-e520-snow-leopard-1062-install-guide/ Recollection is it only installs on 1st HDD -- others panic. Another issue was Chameleon never loaded properly when installed normally. I had to load it from Linux partition with Grub. I turned my E520 into a private World of Warcraft server, so its not running OS X anymore. BTW, you can upgrade it to a Core2Quad Q6700 and 8GB -- I did. Those old processors are affordable on EBay.
  8. Mid 2010 MBP and x64 Windows 7

    Hi Guys! I am trying to install Windows 7 on a mid 2010 MBP and have observed: The 32 bit (x86) version installs nicely -- and one can easily install 3.0 Bootcamp, upgrading it to 3.1 and 3.2. Everything works BUT only 2.7 Gb of the 4.0 Gb of memory are useable (presumably due to the various devices utilizing a significant chunk of the 4GB potentially addressable). So what I want to do is use the 64 bit version of Windows 7 -- but Bootcamp won't install, saying its not supported on this Mac. Now you can get around this partially by using 7-Zip to decompress the exe, right clicking /Drivers/Apple/Bootcamp64.msi and using Windows troubleshooting to bypass the version checks.Unfortunately then you still don't have device drivers. I had hoped someone here had solved the same problem -- Insanelymac people have historically known more about Macs than Mac people. What I'm going to try next: Unzip all the separate device drivers in /Drivers/Apple/x64 and run them in troubleshooting mode. Do the same with the 3.1 and 3.2 updates If it fails, I may be stuck with 32 bit Windows utilizing only half the memory. Anyone else have ideas? Update -- That failed; no x64 Drivers in Bootcamp 3 I tried downloading "Bootcamp 4.0 drivers" from TPB -- they did not work either. So now I'm backing up the Snow Leopard System. I've been avoiding upgrading to Lion as too many reports of crashes with it on this system. But I'll do so temporarily just to attempt to download updated drivers from Apple. (The link in Bootcamp for Snow is broken.) Final Resolution: The bootcamp 4 drivers downloaded by Lion work -- one would think Apple would make them a little easier to download however. Reverting back to Snow was a pain as diskutil would not delete the hidden "Recovery HD" partition. (Found directions here: http://osxdaily.com/2011/06/30/deleting-the-mac-os-x-10-7-lion-recovery-hd-partition/ ) Hopefully this post will help someone else.
  9. mobility radeon HD 4330

    Well, it depends on your resolution. c0ke and I both used Dell 1545 to figure out how to mod the Radeon kexts. He eventually got his to worked. I did not. And to my knowledge noone else with 1600x900 resolution did either. Here is our thread: http://www.insanelymac.com/forum/index.php?showtopic=245308 However, I have been away from this a while, and am considering looking into it again, and if I figure anything out I might post again.
  10. Proposed Mobility Radeon DSDT Patch

    I would go back to modifying ati.c; I haven't been able to get this to work myself. Was hoping someone who new more than I do would contribute. And I don't want to give you misleading answers.
  11. Snow Leopard 1.6.7 Dell Inspiron 1545

    RadeonHD is wonderful, but it does not give you QE Some 1545 people have gotten their graphics fully functional (like c0ke) -- see the Hardware section -- but if you have the 1400x900 screen like me its still a work in progress. This is how I got my wifi functional: Locate IO8211Family.kext in /S/L/E Locate AppleAirPortBrcm4311.kext inside its plugins Open its info.plist. Under IONameMatch add: <string>pci14e4,4315</string> repair permissions and reboot
  12. I can now successfully inject dual-link property, link format, link type, engage video system including QE. See attached ioreg. Screen remains blurry, with the white lines, and PixelFormat remains a null value despite injection.
  13. I think I finally found the section of code that prevents dual link from working on hacks. Its in ATISupport ATIDigitalConnection::shouldUseDualLink(AtiDetailedTimingInformation*) +0 00006be4 55 pushl %ebp +1 00006be5 89e5 movl %esp,%ebp +3 00006be7 83ec18 subl $0x18,%esp +6 00006bea 895df8 movl %ebx,0xf8(%ebp) +9 00006bed 8975fc movl %esi,0xfc(%ebp) +12 00006bf0 8b5d08 movl 0x08(%ebp),%ebx +15 00006bf3 8b750c movl 0x0c(%ebp),%esi +18 00006bf6 8b4310 movl 0x10(%ebx),%eax +21 00006bf9 85c0 testl %eax,%eax +23 00006bfb 7430 je 0x00006c2d +25 00006bfd c744240438820200 movl $0x00028238,0x04(%esp) is-dual-link +33 00006c05 890424 movl %eax,(%esp) Now we can see if modifying it by hexediting the 7430 to 9090 will get rid of blurry screen on resolutions exceeding WXGA
  14. If you otool -vt ATISupport, you will see its in the code. Framebuffer won't load EDID properly unless its on MAC hardware -- or at least labeled as a MAC EDID. Theoretically, one could modify the code by inserting no-ops with hex editor. I tried modifying the EPROM on my LVDS screen, but unfortunately mine doesn't support writing to it.
  15. Method does not work. If you look at attached ioreg at VID@0, you will see LinkFormat, LinkType as 0 and PixelFormat null despite being injected as 30, 30, 20 and despite modified EDID injected at @0,LVDS,EDID Which means FB reads EDID from i2c, and fails to initialize these values. And we cannot trick it by inserting false EDID in EFI. Now back in the 8 bit days when I did assembly, we could just hexedit no-ops into the section dong referred to: "isAppleDisplay" What could work? 1)modifying the EDID on the EPROM on the LCD 2)disabling the isAppleDisplay section by hex editing it with the modern equivalent of no-ops 3)Disassembling the Framebuffer, disabling this section, then reassembling it Its been there both in correct values and default ones for a very long time. If it was that simple I would have my system fully functional. You forget, kizwan, that I was the one who suggested to bcc9 that this method could be used to enable LVDS, and so I've had a head start on all of you.