Jump to content
InsanelyMac Forum

Kill.Javascript

Members
  • Content count

    9
  • Joined

  • Last visited

About Kill.Javascript

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Male
  • Location
    TrialandError
  • Interests
    Music, photography, wordplay, art, graphic design, travel
  1. Kill.Javascript

    [UEFIPatch] UEFI patching utility

    A Different View -- for Perspective. As a subscriber to this thread for well over a year, as well as someone who has tried to do some BIOS patching with CodeRush's old and more recent tools, I would like to add the following: Generally, strident comments or posts should be taken with a grain of salt. The reason? The vast majority of DIY'ers who are trying these tools DO NOT have the coding know-how or knowledge of low-level programming to do it themselves. Thus, they (myself included) are often at their wit's end as far as achieving predictable & successful results. Also, with respect to the overwhelming majority of technical software utilities, the instructional writing is so opaque and insider-oriented that it is confounding and frustrating to the average user. I've edited technical manuals for over 20 years in a variety of industries, and the writing in the computer world is by far the most nightmarish I have ever had to deal with. Knowing how to code, knowing how & why processes and procedures work -- and attempting to clearly and concisely explain it to others -- are mutually exclusive skills. Personally, I've had to start from SCRATCH too many projects to count after wading through reams of computer-speak written by people for whom it might actually make perfect sense, but is utterly painful for the rest of us. For me, most of the zillions of software reference manuals -- by every publisher -- aren't worth the paper they're printed on. Not saying that CodeRush's READ MEs fall into this category; I haven't looked at them for awhile. I am only trying to give a possible, legitimate, context for the frustration that user, or other users, expressed when trying these highly technical fixes. I know I've felt that myself in my experience building, testing, troubleshooting and maintaining h@ckint0shes over the past few years. Workable fixes are very hard to come by. Most people seeking answers do follow forum protocol, and I would think that even those who don't, who fly off the handle due to frustration, are genuinely appreciative of the selfless work done by developers like CodeRush. If they didn't think it was worth trying and spending lots of time, effort and patience on, they wouldn't bother to download and give feedback at all. Actually, I would consider that kind of feedback more useful than dozens of "Thanks a lot!" or "I have the same problem too!" posts. So, rather than consider it an insult, I would just chalk it up to feedback. I guess it's ultimately up to board admins to determine when someone is crossing the line, which I don't feel that guy did. Yes it was negative, but not without context. I liken it to being a musician. You can do tons of preparation and even turn in a good performance that measures up to your own high standards, but there will always be someone in the audience who says, "Pfff, he's not that good. What a waste of my time..." I wouldn't quit being a musician in that case. Nor would I kick the guy out of the venue for good. I would take it as a call for me to work even harder, to find something in my playing that might not be there, and add it to my repertoire. Maybe I'd get him on board next time. Anyway, Peace all, thanks for the thread & Happy New Year!
  2. Kill.Javascript

    [UEFIPatch] UEFI patching utility

    well, i hope i'm not breaking any written or unwritten forum protocols here, but check out myHack home page (vous avez lu google, non?): http://myhack.sojugarden.com/guide/ as I indicated above, it's not perfect but I've got three OS X.9.4 builds running fine that I installed with it. again, you'll have to do the mach_kernel patching after creating the USB installer, and then again on your OS X hard drive after installing (provided you get that far).
  3. Kill.Javascript

    [UEFIPatch] UEFI patching utility

    double-check the md5 hash to make sure the patch actually succeeded. the md5 (terminal command: md5) for the vanilla mach_kernel is different than the one for the patched one. if the patched one is the same, re-do your patch operation. again, make sure you follow the proper directories (just drag and drop the file onto the Terminal window, as well as the patched file location. and use the sudo command. also, make sure you keep a backup of the original. if you've done everything properly and it STILL doesn't work, then you might want to consider re-authoring your USB stick with another installer strategy. I've used myHack lately on a few installs and for the most part it's been fine.
  4. Kill.Javascript

    [UEFIPatch] UEFI patching utility

    Yes, you'll use the Terminal (likely as "sudo") to run the script (which you can just copy and paste). Make sure your directory paths are correct when you issue the Terminal commands. Here's a rundown of how this guy did it. Not all of it applies to you, but you'll be able to pick up some tips: http://www.thev.net/PaulLiu/nuc-hackintosh.html
  5. Kill.Javascript

    [UEFIPatch] UEFI patching utility

    Anyone ever try to patch a SUPERMICRO board BIOS? I just built a mini-itx rig using a Supermicro X10LSV board. The stock BIOS is version 1.00, with a build date of 09/09/2013. Everything is running fine but the rig won't be ready for prime time until I get sleep working. Right now it's not waking up. I'm using stock AICPM.
  6. Kill.Javascript

    [UEFIPatch] UEFI patching utility

    Greetings, Coderush: I tried to re-flash my bios (recall that I successfully upgraded it from 0904 to 1006 using FTK/DOS) using your patched bios, but was unsuccessful. Rather than giving you an entire screen dump, here are the lines that seemed to reflect the reason why it failed: ====== FPT Operation Passed Copying module data from BIOS region backup to bios.bin DOS/4GW Protected Mode Run-time Version 1.97 Copyright © etc... ASUS BIOS file signature not found in input file Error occured during copy phase. Exiting. Thank you for using FTK. Have a nice day. C:\> ====== Do you think the reason this happened is that, after I upgraded the BIOS from 0904 to 1006; the new BIOS is not able to be flashed in the same way? Meaning, is the ASUS tool required? Just curious... Thanks anyway, friend.
  7. Kill.Javascript

    [UEFIPatch] UEFI patching utility

    howdy: wish i could join the "thanks, it worked!" party. but i can't even seem to get the PMPatch executable to work. I tried versions 0.5.10 and 0.5.11 for OSX, and both gave me the same error in terminal: "Illegal instruction: 4" i thought maybe you had left out the need to run as sudo in the instructions, so i tried that. no more illegal instruction errors, but I got nothing else. just a return back to the prompt and no readouts indicating that anything was happening. and of course no modified bios on my desktop. the PMPatch executable is executable, so i don't understand the illegal instruction error. not a permissions issue either. for the record, i am trying to patch the bios for my asus p8h77-i. the version asus recommends for the cpu i'm using (i3-3240) is 1006. it's a .cap file. i tried changing the extension to .rom, .ROM but nothing worked...PMPatch couldn't get to first base. any suggestions? BTW, I was able to successfully flash my bios using FTK and DOS as in your other tutorial. but even with the BIOS upgrade, sleep doesn't work, even with the usual patch to AICPM.kext. (attaching vanilla BIOS from Asus in case you might have the time to patch it. if so, many thanks) P8H77-I-ASUS-1006_(FROM ASUS).zip
  8. Kill.Javascript

    Geforce GT 610 - OOB in 10.8.2?

    I had a difficult time with my latest ITX build, using an ASUS P8H77-I mainboard and i3-3240 CPU. Was able to get onboard HD2500 graphics to work using the ig-platform-id=11 injection (shows up as HD4000 with 768MB), but no matter what else I tried, and believe me I tried everything I've been able to find, I could NEVER get QE/CI to work. Just impossible with the setup. And yes, it was DVI-D, not VGA. So since I hadn't budgeted for a graphics card, I went cheapo and got the GeForce GT 610 (Gigabyte). It appeared to work OOB, although had pretty lame Cinebench scores, but the more I broke it in, the more the "NVDA(GL) channel exception error" freezes came up. They happened at weird intervals -- during screensaver mode; when browsing a folder of jpgs, looking at websites with minimal graphics, etc. Removing AGPM.kext was of no benefit, and I found you have to leave the other NV* kexts in S/L/E as well. The GPU PWM temps are fine in HW Monitor, so I've been stumped. I did add the "nvda_drv=1" string back into the boot.plist (it had automatically been erased for some reason when I switched between Chameleon Wizard and manual plist editing in TextWrangler); see if it makes any difference. I also modded AGPM.kext by adding the GT 610's Vendor and Device IDs, since they weren't included in the iMac12,2 SMBIOS. That's about all I can muster. If I get any more freezes, I'll return this card and get a GT 620 or something. I've had good luck in the past with the GTX-550Ti, but can't seem to find any locally right now, plus I think I'll have problems fitting that inside this small Raidmax rig. ================= UPDATE: 24 HOURS LATER Well, it's a done deal...I'm returning the GT 610. Why? ---> NVDA(OpenGL): Channel exception errors (and resulting system freezes) no matter what. I've tried the AGPM doctoring, I've tried different SMBIOSes, I've fiddled with all the extensions and the kernel flags. Nothing works. Another F-U to the whole idea of Hackintosh building. Recommendations: • Don't buy the Asus P8H77-I board for a Mini-ITX build. It works okay as a NAS server, but if you want a GUI on it, forget it. • Don't buy an Intel i3-3240 CPU. The price might seem good, but the HD2500 on-chip graphics is a pit of trouble and time expenditure. • Avoid the Nvidia GeForce GT 610. Even at $40, it's a waste of $$.
×