Jump to content
InsanelyMac Forum

bdv

Donators
  • Content count

    69
  • Joined

  • Last visited

About bdv

  • Rank
    InsanelyMac Protégé

Contact Methods

  • Website URL
    http://

Profile Information

  • Gender
    Male
  • Location
    France, Near Bordeaux
  • Interests
    Italian motorcycles riding and fixing, computers, cats, pre-print design.
  1. Hello I am installing 10.11.6 on an Asus H70M-Plus (see config1 in my signature). Everything is fine (sound not installed, will come later) except an ethernet problem in relation to sleep/wake: I use MausiEthernet kext for the I219v, works fine till the first sleep/wake: the IP is not renewed after wake. If I do a "ifconfig en0 down" followed by "ifconfig en0 up" the interface gets its IP back and networks is fine till the next sleep/wake. I tried with older kext revision (2.1.0), same problem. Tried loading kext from /S/L/E or EFI/.../kexts/10.11 or /others: same problem. Tried Clover ACPI settings to fix lan: same result, tried with or without WakeOnLan in bios or/and System preference panel: same result Sleep/wake works OK for USB and graphics, only ethernet is problematic. I think that it is a powermanagement problem wthat could be cured with a proper dsdt edit, but cannot figure what to do. I am currently using the debug version of MausiEthernet kext, I upload several files to help diagnose problem, feel free to ask for more info if needed. Thanks in advance for any suggestion. Folder with relevant files H170M-Plus Files.zip EDIT: As I suspected, nothing to do with MausiEthernet kext, it was a DSDT error in Method(_PRW). Once fixed, no more problem after wake. Sound fixed also with voodoohda, everything is fine, thread marked as solved. BTW, Great job with this network kext !
  2. Furthermore, the American Constitution does not apply to the *World Wide* Web, last time I check. That said, freedom of speech is a great principle; live and let live too. One can promote different view of hackintoshing without spending so much time and effort pointing fingers at Tony**** : just forget that clown and move on.
  3. I am trying to install Mavericks (10.9.4 installer) on a brand new Asus Z87-Pro (V Edition) using Clover UEFI Clover boots, load kexts (FakeSMC), patch kernel and reboots just after patching kernel. Mobo: Asus Z87-Pro, latest bios (2103) Proc: Core i5-4590 Graphic: GTX650 (with UEFI VBios GOP), runs OK on other UEFI Asus mobo Ram: 2x8GB Crucial 1600 (run ok on other mobo) Clover : r3193, UEFI mode, also tried with legacy mode : same instant reboot Bios settings: as usual for Asus (I installed Z77, Z87M, Z87-WS, X79-WS, P8B-WS, P8C-WS, etc) AHCI, No Memory Remap, no VT-d, IGPU deactivated, CSM disabled and "Other OS" (for UEFI boot). The only new setting for this board is MSR 0x02 Lock : disabled or enabled. Set as disabled (default), also tried Enabled just in case : same instant reboot. Clover settings: KernelPM + AsusCPUPM (tried also disabled) With this release of Clover, I think that Haswell instant reboot bug should be cured by KernelPM ? I also tried with a Yosemite Installer, even with myHack/Chameleon and legacy bios settings Tried combination of npci=0x2000 or 0x3000, -xcpm (normally only for IvyBridge), samme reboot. Any idea? Solved by downgrading bios to 1802 release, it boots directly to the installer with the same settings.
  4. Perhaps this post should go in Power Management section, but as it seem related to a graphic card issue, I choose this place. Please feel free to move it elsewhere. I recently replaced the Asus GTX650 graphic card on my main rig (see signature) with a Sapphire R9 280x Tri-X 3GB (UEFI bios switched on). I use UEFI Clover (2999, same problem with older revisions)). I have 2 monitors, but the problem is the same with only one on every port I tried (DVI-I, DVI-D, HDMI) With the old card (GTX650), all was fine including speedstep and sleep under 10.9.4 and 10.9.5. No problem at all. I Use MacPro6,1 smbios and kernelPM, with a custom SSDT, booting with -xcpm. I could let it sleep and wake on his own or provoke sleep using power button or the apple menu, it all worked OK including PowerNap. Hibernation is disabled (hibernatemode 0 and autopoweroff 0). Since I replace the graphic card, sleep is broken: I can let it sleep on its own or provoke it but cannot wake it up. If I try waking it by keyboard, mouse or powerbutton, I hear fans starting, DVDdrive powering then all stop 2 or 3 seconds later, going back to sleep. It then loop every ten seconds, trying to wake for several seconds then sleeping, and so on. I cannot wake it up and must reboot it. The monitor stays black with "no signal". From the log: Any idea, things to check or try?
  5. Hi. I am trying to switch my running rig from chameleon to uefi clover. I ran into a problem: clover does not seem to "see" my drive as uefi OS to boot it. I successfully install legacy clover, but could not boot this rig using uefi clover (same dsdt, settings etc that worked with legacy clover). The rig: Asus P9X79-WS, Xeon E5-1650, 16 GB ECC ram, Asus GTX650 1024 MB with GOP VBios, Crucial MX500 SSD 250GB. OSX 10.9.5 This rig worked fine under 10.9.4 + chameleon, 10.9.5 + chameleon and works fine with 10.9.5 and legacy clover. Asus bios does not identify the SSD as UEFI drive, only legacy (I think that this is the real problem). SSD was partitioned under osx as GPT, it has EFI and Recovery HD partitions. EDIT: Solved. I made a backup of the disk and make a clean GPT partition with disk Utility. Restore backup, reinstall UEFI Clover on EFI partition and it boots in UEFI mode, disk is seen as UEFI in Asus "bios". I do not know what was wrong with the original GPT partition, anyway, it is fixed.
  6. I am actually using a Barts Pro Sapphire HD6850 1GB (Vendor: 1002, Device: 6739) on this rig running osx 10.9.2 (genuine graphic kexts) and using GraphicsEnabler=yes. I do not have any DSDT edit for the graphic card. Graphic card is identified as Radeon HD6850 with the correct framebuffer (Duckweed) and number of ports (4). It drives 2 monitors, a 27"Viewsonic @2560x1440 via DP and 26" IIyama @1920x1200 via DVI, performance seems fine The only defect is the vram total size incorrectly reported as: VRAM,totalMB 0x16800400 Is it only cosmetic or should I do something to get a correct value?
  7. Xeon E5-1650v2 @ 3,5GHz (turbo 3.9 GHz) and Asus GTX650 - OSX 10.9.2 CPU (6 cores/12 threads): 960 1 core: 138 OpenGL: 60.64 with GTX650 79.93 with Sapphire HD6850
  8. bdv

    [UEFIPatch] UEFI patching utility

    On the same subject, I put together a Xeon E5-1650v2 (6/12 cores Ivy Bridge) on an Asus P9X79 WS with latest genuine Bios (4601) and can confirm that there is no lock. I installed the 4601 bios from asus website with EZflash, made a backup with afudos and PMPatch could not find any trace of a lock in this backup bios. Just installed 10.9.2 with MyHack, removed NullCPUPM and Voilà: it boots ok.
  9. Hi Just bought an inateck BT 4.0 dongle, based on CSR8510 A10 chip with 8891 firmware. Works OOB with osx 10.8.5.
  10. I just installed 10.9 on an Asus P8B-WS with latest patched bios + Xeon E3-1230 and Asus GTX650. The mobo was running with 10.8.5 prior upgrade. With this mobo, I can run OSX only with a patched AppleACPIPlatform: if I use the vanilla one, I got a KP at boot when switching to graphic mode. Tried with a Sapphire HD6850, an Asus GTS250 or GTX275, same symptoms. Tried with GraphicsEnabler yes/no, with DSDT edit fot graphic card or no, same problem. Fresh system installed with MyHack or Pandora, same thing. I use a custom DSDT + SSDT that worked OK with 10.6.8 and 10.7. This problem firts appeared when upgrading from 10.7 to 10.8 Once I replace the vanilla AppleACPIPlatform.kext with the "X58" patched by Ermac I can boot. Is the patch related to MCHC (DRam Controller) device? On my P8B-WS MCHC device-id is 8086,108 which does not appear in the Info.plist for AppleSMCPDRC plugin of IOPlatformPluginFamily As the DRAM Controller of the Xeon E3 is different from the Core one (for the ECC support), could be related. Any idea to fully support this motherboard without having to use the patched kext (which is really a 10.6.8 kext with modified Info.plist if I recall correctly)? I can run test if needeed, this rig is a testbed.
  11. I think you mix two separate things: 816M indeed fixed the sound problem but you have to patch audio anyway. I is needed because the audio chip is not supported by Apple kext as they used unobtainium hardware in their line of products. The chip used for Quo board is an alternative hardware commonly used by mobo manufacturers, but as it is unsupported OOB by OSX, you have to add support by patching kext or adding an other kext. For the same reason you could have to add non-Apple kexts to support new hardware that you install on a genuine Mac (printer, TB enclosure with specialized hardware, etc) No big deal, and not a problem AFAIC.
  12. Honestly I gave the rig to SWMBO after installation. I tested it and audio seemed to work fine, without pops, hiss or any problems but I did not tested it for long. No complaints so far but she does not use it a lot for audio. I'll ask and report if any problem arise.
  13. In a nutshell, you have to run a script named PatchALC892.sh in the 108 folder (to patch 10.8.x osx audio), in the PatchALC892 folder at the root of your system disk. /PatchALC892/108/PatchALC892.sh First copy the PatchALC892 folder to the root of your drive (same level than /System, /Users, /Volumes,) Under Terminal as root user, go to the script folder: your host$: sudo -s bash-3.2# bash-3.2# cd /PatchALC892/108 bash-3.2# then run the script: bash-3.2# ./PatchALC892.sh You can use line completion and just type ./Pat then use tab key to complete the name of the script, then return or enter. Using ./ indicates that the file is in the current folder, standard unix shell: . = current folder .. = parent folder / = root of the drive
  14. As far as I remember I just use the patch for osx 10.8 I believe I got the needed files in this post http://www.insanelymac.com/forum/topic/285920-new-os-x-compatible-motherboard-quo/page-13?do=findComment&comment=1937448
  15. My bad, Don't know how I wrote 839, it is 816M... Post edited.
×