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 Net-burst

  • Rank
    InsanelyMac Protégé
  • Birthday 01/18/1986

Profile Information

  • Gender
  1. [UEFIPatch] UEFI patching utility

    Ok, my BIOS flashed ok. But now I'm facing another problem, which is out of scope of this thread. I replaced WiFi combo-board to new one and my ASM1061 SATA stopped working. Only in OSX. Talk about esoteric problems
  2. [UEFIPatch] UEFI patching utility

    @CodeRush, thanks. Will check it later tonight. Replaced 2kb, checked file in UEFITool. Looks like all is OK. Fortunately, I have dual bios, so I think I can revert even if something will go FUBAR PS. Z77 is old platform, so I think all will work. At least I hope so.
  3. [UEFIPatch] UEFI patching utility

    @CodeRush, I'm losing sleep and half of USB ports with it, unfortunately. One USB2 hub, to be more precise. It somehow messes up my IRQ allocation. At least I think so. Furthermore, I'm still getting rollback to old NVRAM mode in bootlog. Looks like ROG series have something different about them. How much bytes is header do I need to replace? 11? As I understand, I need to copy set number of bytes starting from first one into modified file. Am I correct? Nothing else? PS. Looking at file differences, it looks like several different modules were either replaced or moved. For example, after PMPatch, I get few different bits. However, after AMIBCP I'm getting a lot of chunks.
  4. [UEFIPatch] UEFI patching utility

    Hello. I'm trying to disable BIOS and NVRAM lock on my Z77 motherboard. I used AMIBCP to disable SMI and BIOS lock in image file, but program produced CAP file with different firs bits, than original. UEFITool shows that I'm opening not capsule file, but rather BIOS file. I'm attaching both files here. Can someone please look at them? PS. I have Asus Maximus V Extreme motherboard with 1903 BIOS. I can only flash with Flashback because of lock. MAXIMUS-V-EXTREME-ASUS-1903.rar MAXIMUS-V-EXTREME-ASUS-1903-SMI-unlock.rar
  5. [UEFIPatch] UEFI patching utility

    @CodeRush, thanks. I thought that it is locked because of some messages on forums. Also OSX on boot writes something about inability to write to NVRAM. Also, some users stated that older version of bios did not have NVRAM lock (older versions don't have SMI lock enabled in BCP, if that matters). So, new Clover eliminates any need to unlock NVRAM? PS. I'm already following that topic. But still waiting to some iMessages clarification, because I use it quite heavily
  6. [UEFIPatch] UEFI patching utility

    Hi, CodeRush. Can you please help me? I'm trying to remove NVRAM lock on Z77 Asus Maximus V Extreme board. I found info about using AMIBCP to remove lock, but it produces image without capsule header. I think I read somewhere that UBF don't do any checks, so I'm little afraid to flash this image. So, what's best way to remove NVRAM lock for Asus boards? If its complicated like using disassembler, then can you please help me with producing image with lock removed: https://mega.co.nz/#!rk12BapQ!kCXx-HpGXsljtPCQZnlgTK6EGimu2rtUuKqPEy2H-6g ? Thanks in advance.
  7. Looks like I nailed root of the problem: Asus combo board. Its bluetooth part, to be more precise. Maybe someone can check with wifi only card. Somehow E1000e driver conflicts with bluetooth device. I don't know what kind conflict it is, but it looks like its IRQ related because one if IRQs of NIC changed to 03 from 02. Just disabling bluetooth controller in BIOS helped, you don't need to physically remove card.
  8. What extensions do you mean exactly? On first look I dont have any broken system extensions. Only problem is IvyBridge CPU under MacPro3,1 SMBIOS. Under Macmini6,2 everything is normal. At least I think so. Maybe I'm missing something.
  9. Yes, I did update it. I installed OSX after about 2 weeks later than windows. My network card just disappeared after sleep on windows 8 and Asus site recommended updating fw of network card, so I did it. EDIT: So, looks like we don't have any ideas how to fix this . It's a pity.
  10. I don't code for OSX, so I don't know such specifics. If I knew C, I would already be half way to find reason of sleep breakage. Yes, I can unload it without problems. Without kext, system sleeps fine. Also, system sleeped fine when I deleted network service from network preferences panel. But not always. I need more time to understand why. Also, I tried revision 20 and last one. Both exhibited this behavior. Also, here's some more logs. All logs from now on will be with proper IRQ assignment to HPET device. Log name represents what was done in that time span. PS. Also, one side note: visually all devices shut down on sleep attempt, but LAN continues to work. I see leds that represent uplink and data transfer. On successful sleep they both go down. BootInactive.txt Inactive-Active-ReAdd.txt RemoveService.txt
  11. Some more research: On kext v 2.1.7 or 2.0.0 (I dont remember what exact version I used) I had some pause (around 5-7 seconds, I think) between pressing sleep button and actually going to sleep. Latest version dont exhibit this behavior, but continues to fail going into sleep with 2 IRQs on GLAN device. Debug log don't have anything after pressing sleep... Attached to post are several debug logs, taken after boot. To me they are completely identical. IRQBoot.txt - HPET have 4 not overlapping IRQs, GLAN have 2 (one is overlapping). IRQ2Boot.txt - HPET have 2 IRQs (happens around once per 3-4 week, don't know why), GLAN have 2 (one is overlapping). NormalBoot.txt - HPET have 4 overlapping IRQs, GLAN have 1 not overlapping. Also, main IRQ of GLAN device is not constant, but always exclusive to GLAN. I'll test some more. EDIT 1: Scratch first part. Looks like delays caused by something else, not kext version. It well may be traffic from torrent client. I need to do more testing. EDIT 2: Found similar bug report with this driver, but on Linux: https://bugzilla.ker...ug.cgi?id=36132 EDIT 3: Forgot to mention: my tests are on OSX 10.8.2 and 10.8.3. IRQBoot.txt IRQ2Boot.txt NormalBoot.txt
  12. hnak, I came across very esoteric problem with your kext and sleep. Monitor turns off, same as HDDs, mouse and keyboard, but fans continue to spin and computer wont react to any input. Even power button. In other words hangs in transition to sleep. This is same as THe KiNG's problem, I think. I have Asus Maximus V Extreme motherboard with Intel 82579V ethernet. Asus Maximus V series of motherboards have problem with mid-motherboard usb ports. Thing is, HPET device hijacks exclusively IRQs for one of USB hubs. We can easily fix this with DSDT edit, but not in this case. If you reassign IRQs, you lose sleep. After around 50 reboots with different IRQ assignments, I tried to install OSX from scratch, just in case my current install was faulty by itself. Sleep worked flawlessly on fresh (only FakeSMC kext) system. So, I began to install required kexts one by one and sleep broke on AppleIntelE1000e. And I think I have some ideas why this is happening. Here comes some research: With HPET patch. GLAN device gets IRQ 20 and 03 ("IOInterruptSpecifiers" = (<1400000007000000>,<0300000000000100>)) - sleep breaks. I think this is because IRQ 20 (<1400000007000000>) is also used by one of USB2.0 hubs. Or because GLAN usually have only one IRQ. Whithout HPET patch. GLAN device gets ONLY IRQ 03 ("IOInterruptSpecifiers" = (<0300000000000100>)) - sleep works. This is because HPET already hijacked IRQ 20 exclusively, so GLAN and USB hub cant claim it for themselves. Also IRQ 03 is exclusive to GLAN, so I think that problem is somewhere in the driver, that dont like IRQ sharing with other device. Or driver expects only one IRQ. In either case LAN and HPET is working. The only thing that's breaking - is sleep. I'll try to do some IRQ shuffling when I'll get home later. I think I have one free IRQ to reassing LAN controller onto. Also I need to look how IRQs are assigned without your kext, because I forgot to look at it