Jump to content

Anachronaut

Members
  • Content Count

    40
  • Joined

  • Last visited

Everything posted by Anachronaut

  1. If you are going to mess around with trying to create a working Hackintosh, you’re really going to want some form of backup so that you can revert to it when your changes or tweaks don’t work right. You could use Time Machine, Carbon Copy Cloner, SuperDuper! or any number of other GUI programs that run in Mac OS (and then to restore your whole disk you may need to reinstall your boot loader), but there is another alternative in Clonezilla that works very well. This is a tutorial to show how to use Clonezilla Live to make a basic disk clone for backup, or to restore your machine from a perviously created backup. Clonezilla is a very capable program with many options and uses. This tutorial is only intended to show its use in its most basic form for new users. If you want to explore other uses for Clonezilla, you will need to do research and exploration yourself, as for me, this is all I need. Why use Clonezilla Live instead of another backup program? 1. Clonezilla Live is FREE and OPEN SOURCE. 2. Clonezilla Live is outside of your current operating system and can make a bootable clone of nearly any current boot disk from a current OS and boot loader. For more details, see the Clonezilla website: http://www.clonezilla.org 3. Clonezilla Live is fast. Well, relatively speaking I guess, at least for most disks. It only clones the used data portion of the disk, saving time. Connecting my computer to a refurbished Western Digital Caviar Blue 250GB drive in an old-and-really-cheap USB 2.0 case, a clone of my startup drive with about 60GB of data took about 21 minutes. Connecting to a 250 GB SSD in a modern USB3 SuperSpeed Case, the same clone took 4 minutes (running at near 20 GB/min speed). 4. Clonezilla Live creates a bare metal backup. What that means is that if everything goes sideways, you could buy new hardware matching your current specs, properly set up the BIOS, then use Clonezilla to restore the information and boot sectors to a new drive and you would be back in business. [i have not tried this with a new disk, but have reloaded my system several times form backup with perfect results.] 5. Unlike some commercial cloning programs that run within the Mac OS (or others), there is no need to reinstall the boot loader after the clone is made. The disk is ready to use right after being made. What are the disadvantages to using Clonezilla Live? 1. Finding the correct version and creating a usable USB stick, CD, or DVD can be difficult and intimidating for those with a less technical background. 2. The user interface, while very usable, is a bit of an antique. It looks and acts like it belongs in ye olde computer museum. This further adds to the difficulty and intimidation factor for new and less technically skilled users. 3. Clonezilla cannot do incremental backups. It only does whole disk copies. 4. Clonezilla can be very picky about cloning to a drive the is not equal to or greater in size than the source disk – even down to the last sector block. Hopefully this tutorial will help some of you get started with this very useful program. The Setup You need a disk for your backup. The Clonezilla instructions say “the destination partition must be equal or larger than the source one.” So technically, you want a disk equal in size to the one you are Cloning (or a partition of equal size, but this tutorial is ONLY about the BASICS, so we will just use the whole disk). Now, it is true that the program only copies the data portion of the disk, so it is possible that this will work with two different size disks, but this is not supported by the Clonezilla documentation (unless you use Expert Mode, but this tutorial is ONLY for BASICS, remember). Having said that, I used a 1 TB disk for backup and restored the clone to a 250 GB drive with no problems, but this may not always work. For the purposes of this tutorial, I will stick to just a 250 GB internal SSD startup disk, and an external 250 GB hard disk backup for simplicity. Download Clonezilla As stated above, getting the correct version can be intimidating for new users. Almost all modern hardware that is being used for a Hackintosh will use the Ubuntu based version that can be downloaded from the link below. Be sure to download the ISO file. The download options should look like this before pressing the down load button (you want the version labeled amd64 even if you have an Intel processor). Clonezilla Download Take the ISO image out of your downloads folder and place it on the desktop before continuing to the next step. Create a bootable USB flash drive from the ISO file While you COULD use a CD or DVD for this purpose, why would you go for such old technology when a USB flash drive with work better and faster. Before I start: I am using the brackets [ ] to denote something to be replaced in a command. You do not type the brackets, only the item described inside the brackets. If you still don’t understand any part, look at the completed example at the end of this section. 1. Insert your USB Flash Drive. Since the ISO file is only about 200 MB, you won’t need a very large drive. I don’t think it even matters what the current file system is on the drive for this because it will all be erased in this process (I have done this with both GUID and FAT32 systems). 2. Open Terminal (in the finder, use the Go menu and choose Utilities, there you will find Terminal.app) 3. Type diskutil list to get a list of connected drives. Note the identifier for your drive (disk1 in my example) 4. Unmount your USB drive with the following command. diskutil unmountDisk /dev/[your disk identifier] 5. Copy the ISO image to your USB drive with the following command. Note that you should start typing until “if=“ and then drag the ISO image from the desktop to the insertion point to get its path before continuing to type the rest of the command. sudo dd if=[drag your ISO image from the desktop to here to get its path] of=/dev/r[your disk identifier] bs=1m When you press enter your will be prompted for your password. Enter it and press return. Be patient as it will take a bit of time with no indication that anything is happening other than the fact that the $ prompt has not reappeared yet. dd is a direct sector disk copy utility if= specifies the source disk or image of= specifies the destination disk or image /dev/ means device r before the disk identifier apparently speeds up the process bs=1m specifies the size of block to read at one time (if this is not working you can try bs=1M) See sources How to Copy and ISO to a USB Drive from Mac OS X with dd and Disk Management From the Command-Line, Part 1 for more information. When finished it will give a message about what was copied. Also, a warning should appear on your desktop indicating that the disk is not readable by your computer: This is another indication that you followed the steps correctly – IMPORTANT! Click on the Ignore button to dismiss the warning. 5. IMPORTANT! After dismissing the warning, go back to the terminal. Enter the command diskutil list again. You should see your USB drive with something like “FDisk_partition_scheme.” 6. Eject your USB drive by issuing the command diskutil eject /dev/[your disk identifier] You should get a message that the disk was ejected. Remove the USB drive at this time, and use something to write Clonezilla on its case so you know what it is. Here is the text of the entire process on my computer for reference: Last login: Sun Oct 11 09:06:17 on console Anachronauts-Computer:~ anachronaut$ diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *250.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_HFS El Capitan 249.2 GB disk0s2 /dev/disk1 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *7.9 GB disk1 1: EFI EFI 209.7 MB disk1s1 2: Apple_HFS Clonezilla 7.6 GB disk1s2 Anachronauts-Computer:~ anachronaut$ diskutil unmountDisk /dev/disk1 Unmount of all volumes on disk1 was successful Anachronauts-Computer:~ anachronaut$ sudo dd if=/Users/anachronaut/Desktop/clonezilla-live-20150805-vivid-amd64.iso of=/dev/rdisk1 bs=1m Password: 191+0 records in 191+0 records out 200278016 bytes transferred in 6.947753 secs (28826301 bytes/sec) Anachronauts-Computer:~ anachronaut$ diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *250.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_HFS El Capitan 249.2 GB disk0s2 /dev/disk1 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *7.9 GB disk1 1: 0xEF 7.5 MB disk1s2 Anachronauts-Computer:~ anachronaut$ diskutil eject /dev/disk1 Disk /dev/disk1 ejected Anachronauts-Computer:~ anachronaut$ The following seems like a lot of steps, but it all goes quite quickly once you get the idea. Boot from your Clonezilla Live USB drive to clone your startup disk 1. Shut down your computer 2. Insert your Clonezilla Live USB drive into an active USB port. Clonezilla does seem to use USB3 speeds, so this may be a good option. (Although this is probably only relevant to your backup drive, not the USB stick). 3. Attach your backup disk to another USB port (USB3 if available) if your are using an external backup drive (highly recommended). 4. Power up your computer while holding down the key for choosing boot options. Since I am using an ASUS board this is f8, but this varies by manufacturer, so check your manual if you are not sure. 5. Choose to boot from your Clonezilla USB drive. It should be the one with the smaller capacity. Don’t worry if you have an older USB backup drive that does not show up at this point, we can get it to show later. You will see some text, and then Clonezilla will start. Here is what my boot options list looked like: For all of the following Clonezilla screens, it is usually easiest to use the arrow keys and the enter key to select your options. Ignore the part in the onscreen Clonezilla instructions about using the space key. Most of the time, if you don't know, just stick with the default options. 6. Choose screen resolution 7. Choose language 8. Choose keymap Some text will fly by here and then… 9. Choose Start Clonezilla 10. Choose device to device clone 11. Choose Beginner Mode 12. Choose disk_to_local_disk 13. Choose source disk. Notice in the above image, that my 250 GB external disk does not show here. If the target disk doesn’t appear, as like the image here, choose cancel (use the mouse). Turn the external drive off, and then back on again (or disconnect and reconnect if no external power) and then follow the onscreen instructions to restart Clonezilla. It should appear in the list the next time. 14. Here is the source disk chooser after restarting Clonezilla and getting back to this point. Notice that both 250 GB disks now appear. I will choose the M.2 drive for the source, and the WD drive for the target from here. 15. Choose target disk. This will be erased so be sure you have the right one. 16. Choose to skip repair. 17. Press Enter to continue. 18. Enter y and then y again to confirm erasure of your disk. This is your last chance to back out if you did not choose the correct target disk, so double check you are correct. 19. Watch the progress, or go do something else for a while. 20. Press enter to continue again. 21. IMPORTANT! Choose to Poweroff. Once the computer has shut down, remove the Clonezilla USB drive and your external backup drive before starting your computer again. You should now have a nearly identical, bootable clone to your startup disk. To restore a system, just reverse the choices with the Source and Target disks. One final note: Despite appearances, Clonezilla is still in active development. When I first downloaded and used Clonezilla Live, the file name was clonezilla-live-20150805-vivid-amd64.iso, when writing this tutorial, I downloaded the latest version which is clonezilla-live-20151012-wily-amd64.iso. Notice that the date of issue is conveniently coded in the name, the latest version being issued on October 12, 2015.
  2. Well now, Security Update 2016-002 broke my NVIDIA web drivers again, this time version 346.03.15f03 in El Capitan 10.11.6 build 15G1108. I tried using the NVIDIA Webdriver Updater App, but it did not successfully solve the problem. I think I used the app correctly, as I checked the modify after installation thing. Perhaps I put the wrong number in it – I could not find good documentation on this. The app just stopped responding, displaying a spinning beach ball. Although the driver was installed, it would not activate after the restart due to a wrong build error. Onto solution 2 until NVIDIA comes out with a new version for this build: I just manually edited the info.plist in the NVDAStartupWeb.kext to look for the new build, then installed the kext using my favorite kext installer program. This got it to mostly work, it is now showing Apple driver as selected at startup, but is in fact using the NVIDIA driver. Hopefully NVIDIA will issue an update in the next few days for this.
  3. I am considering building a very low budget system for testing purposes. The tests will be on different hardware, OS's, utilities, etc., so the processor will not be taxed at all. About the most difficult thing the processor will need to do well in this build is to post and respond to forum topics. Is it possible to use the integrated HD 530 graphics on the Skylake Pentium G4500? If so, then the information is difficult for me to find and/or interpret. This chip has been used in a successful build by Frank Nitty: http://www.insanelymac.com/forum/topic/311747-guide-how-to-install-el-capitan-on-asus-z170m-plus-with-clover-using-pentium-g4500/ But Frank Nitty "cheated" on this one using a great NVIDIA graphics card instead of the integrated graphics. Also, he used Clover FakeCPUID for an Ivy Bridge CPU, which may not work if I want to use the HD 530. The Clover Wiki ( https://clover-wiki.zetam.org/Configuration/KernelAndKextPatches#kernelandkextpatches_fakecpuid) lists codes for other FakeCPUID's, but there are currently none for a Skylake chip. From my limited understanding, using a FakeCPUID of a Skylake chip with HD 530 graphics would seem to give the best chance for success. Also, El Capitan 10.11.4 and later have native support for HD 530. Pike R Alpha related in his blog that this may be possible: https://pikeralpha.wordpress.com/2016/03/25/os-x-10-11-4-build-15e65-and-skylake-graphics-support/ Unfortunately, he discusses things that are quite outside of my knowledge base so it is difficult for me to interpret what he is saying or how to proceed. Any help or suggestions would be appreciated. An example build would be even better if one already exists as I have not been able to find one.
  4. My new Skylake build is mostly working. When I choose shutdown from my OS X 10.11.6 installation, everything goes well and the computer shuts off; no drives, fans, or lights appear to be active. However, if I press any key on the keyboard, or remove or attach any USB device, the computer will boot from the BIOS as if I pressed the power button. I have disabled "Power on by Keyboard" and "Power on by Mouse" in the BIOS (version F4 – the latest for this board) so this is confusing. Also, when I used Clonezilla to backup my hard disk, the computer shuts down properly from the Linux OS that it uses and required the power button to boot. I am running the latest version of Clover for my boot loader. I would like to fix this if possible, as the computer will boot at the slightest movement, touch to keyboard, etc. the way it is now.
  5. Absolutely, it should work perfectly if the clone was successful.
  6. Refresh your screen and read additional info— I updated/edited the post.
  7. Not a problem if the new drive is as large (same sector count) or larger than the drive you currently have. The model only matters for sizing, and restoring from the backup. For the initial clone, you can use any drive that is the same size or larger. It is even possible that two drives from different "manufacturers" have the same sector count because they contain the same chips internally. In that case, a clone would work in both directions. You could try buying the updated model of the drive you currently have. It may still have the same sector count as companies tend to stay the same on these things with SSD's.
  8. That is why with my new Hackintosh I just bought two identical drives right from the start. If you have extra money lying around (???!!), you could buy two new SSD's, clone to the new drive, swap it into your current computer in place of the other SSD, and then use the second one you bought for a backup. Note that if the new drive has a larger capacity than the old drive, you may want to resize the main partition after you make the clone, otherwise you will be limited to using only as much space as the smaller original drive.
  9. That is correct. Not just the same size SSD, but the same make and model — the actual sector count needs to be identical to clone easily in both directions.. This is important, as Clonezilla (with basic use) cannot clone from a larger disk to a smaller disk, even if the data on it would fit. If sectors are blocked due to damage, it may not work correctly when trying to restore. That being said, I have not had a problem restoring from my SSD clone, probably because with over-provisioning there are always the correct number of sectors unless the SSD is way overused.. It is possible to do a correct clone from a larger disk to a smaller disk by resizing the main partition and then cloning each partition separately, including the EFI partition. This is a bit sketchy and may not always work but I have done it successfully on occasion. I really like the simplicity of Clonezilla and continue to use it. Oops, one more note to add. When I first used this with SSD's it was easy to identify the internal drive to be cloned because it was an M.2 drive and it said that right on the screen. With my newest Hackintosh, I am using 2 identical SATA SSD's, one internal and one external. It does not say "internal" or "external" in Clonezilla, all you get is sda, sdb, sdc, etc. So what I did to make absolutely sure was to start Clonezilla with only the internal drive and copied down the serial number. Then I restarted Clonezilla (easy to do from the given options onscreen), and I could easily identify the internal and external drives by their serial numbers.
  10. Confirmed WebDriver 346.03.15b01 is working on my system after security update 2016-001 for 10.11.6 broke my NVIDIA web driver. For anyone who doesn't know, there is a download link for the installer for this on the first post in this thread. I have temporarily disabled the automatic update feature of my NVIDIA updater control panel until a new version of the web driver is available for this build.
  11. Clover is a great boot loader, however, some people are still having problems. I think a lot of this has to do with the design of the systems. Many have extra backup internal hard drives or partitions with legacy boot loaders or previous Clover systems. While this may have been fine in the past, with Clover and the newer OS X's, this does not work on many motherboards. Often it happens that Clover and El Capitan (or Yosemite) will install and seem to work fine, but then degenerate to an unusable state. I chased this problem for quite a while before I found the solution (see Source #1 below). Look at the boot options list in your BIOS. If you see entries that are not physical drives, it is likely that you are encountering some form of this problem. First, remove all of the extra boot entries. 0. You COULD try to reflash the BIOS and you MAY be done. This worked on my 6 series board, but not on my current 9 series. If it works for you, skip to the second section on preventing the problem from happening again. If this does not work, or if you really don't want to have to flash the BIOS, then continue. 1. Disconnect all drives except one with only one instance of Clover. If you only have a partitioned drive with ANY backups on the partitions, it is probably best to boot with only the Clover Install USB stick and no other drives attached. 2. Boot your system and press the right arrow key when the Clover boot loader appears. 2b. If you cannot get to Clover, reset your CMOS and try again, this time going into the BIOS and selecting your physical drive for boot override. DO NOT touch any other entries at this point as it may lock the BIOS and you will need to reset the CMOS and start over again. It SHOULD work, so keep trying – I don't know another way. 3. Use the right and left arrow keys to select the Clover UEFI Shell and hit enter. The following screen should appear, and either let it time out, or press a key: 4. At the Shell> prompt type bcfg boot dump the results should look something like this: 5. You need to remove any entry that is not a physical hard drive. As far as I know, if it is a real physical disk, it will list as DevPath - HD. The code to remove an entry looks like this: bcfg boot rm XX where XX is the Option number. In this example, I remove Option 02 with bcfg boot rm 02 If you have a LOT of bogus entries, it is best to do just a few, and then type the command bcfg boot dump again before repeating the process. When I first did this on my ASUS H97 board, I had at least 10 entries to clear so it took several iterations of this process. 6. When your have removed all entries that are not physical hard drives, type exit and press the return key. This will get you back to the main Clover screen. At this point, I would choose restart from the Clover choices and enter the BIOS to check if your work was successful. Second, rethink your system design and backup scheme to prevent this from happening again. • Design your system so that there is only one disk (an SSD if you like speed) that has an EFI partition that contains the Clover boot loader. Of course in OS X, all (I think) formatted drives will have an EFI partition, but you do not want two EFI partitions that contain ANY boot loader – that includes Clover, Chameleon, Chimera or whatever. • On some boards, it may help to set the boot options for all devices to UEFI Only (didn't make a difference on my board, but did speed up boot time). • Currently, I have a 250 GB M.2 SSD as my boot disk, and the others are just for data. For backups I use EXTERNAL DISKS, so that I don't reencounter the same problems. The external drives are connected only when I need to backup. [i am working on a GUIDE for Clonezilla.] External USB 2.0 or USB 3.0 drive enclosures are quite reasonably priced at the moment, so I encourage you to do this as well. I think you could use Time Machine for data backup, but I have no experience with this. • Currently I am only running Mac OS X 10.11 El Capitan. It would be great to hear about successful system designs in the same way I am discussing here from others who are also running Windows, Linux or other versions of Mac OS X Source #1 - Thanks to trioset
  12. This behavior is apparently due to a bug in the bios, as it reportedly also affects Linux machines. The Windows drive contains its own boot loader on the boot partition of the drive from the install of Windows. This is probably why it still adds entries after reconnecting the drives. From my understanding, the solution is to remove the boot loader from the Windows drive, and just let Clover handle everything. I have no idea how to do this and still keep the Windows drive bootable. If you try something like this and are successful, please post your method so others can benefit. Apparently, you need to have only one installed boot loader (Clover) for all of your operating system drives.
  13. Could this be a problem with the install? 1024x1280 is the resolution that my system defaults to when the Nvidia Web Driver is not installed or is not up to date for the current OS version.
  14. I don't know much about using this with a non uefi motherboard. It is likely that this method will not work without a uefi bios. I would try reflashing the bios and see if that does the trick. Make sure to make note of any particular bios settings before the reflash.
  15. Anachronaut

    El Capitan - Problems with sleep

    Well, that didn't last long. Sleep is now back to not working, with the same symptoms as before. Console messages again show the problem (shortened to remove many duplicates of "Attempt to set push wake topics without dark wake enabled"): 11/4/15 11:26:41.519 AM apsd[76]: Attempt to set push wake topics without dark wake enabled: () 11/4/15 11:26:41.785 AM apsd[76]: Peer [pid=422] requested push wake but lacks APSPushWakeEntitlement I really think this has something to do with the way dark wake is used and/or provisioned in the software. Also, as stated in other threads on this forum, I think the implementation of USB and putting USB items to rest during sleep is part of the problem.
  16. Anachronaut

    El Capitan - Problems with sleep

    Question: "sleep is working" means what? How many days without reset? Sleep is working means that I can leave the computer and it goes into lower power mode – no fans, hard drives, screen display, and the "sleep" light on my case blinks. This always has worked this way, the change is that now it properly wakes up after sleep. Previously, the screen would stay black except for the mouse pointer which would not move after sleep (sometimes just after longer sleep periods, recently after any sleep). To get it out of the "black screen" state required a hard reset. I no longer get Console messages like "Attempt to set push wake topics without dark wake enabled," so something is definitely different. I had previously set Darkwake=8 in my Clover config.plist, but it did not make any difference after having tried no darkwake flag, darkwake=0 and darkwake=1. In fact, before changing to iMac 14,2, it seemed that the darkwake boot flag was not accepted by the system at all. After the change it does seem to be working properly with the previously set darkwake=8. I don't plan to mess with it at the moment unless something changes. Here is what the terminal says: anachronauts-iMac:~ anachronautscomputer$ sysctl -a | grep -iE "dark|wake" kern.waketime: { sec = 1446477693, usec = 502 } Mon Nov 2 09:21:33 2015 kern.wakereason: XHC kern.hibernatewakenotification: 0 kern.bootargs: dart=0 darkwake=8 nvda_drv=1 net.link.generic.system.rxpoll_wakeups_lowat: 10 net.link.generic.system.rxpoll_wakeups_hiwat: 100 debug.darkwake: 8 anachronauts-iMac:~ anachronautscomputer$ I just changed to iMac 14,2 yesterday after finally getting my digital audio outputs to work (steep learning curve, but I managed to figure it out with Toleda's help). Honestly, from past experience, this state will work forever, for as many days as I keep the computer on. The challenge seems to be after system or program updates and/or multiple restarts. Also, I want to make sure that my DVR program records properly after a period of sleep, and that I can wake it up when needed to watch the program. Previously, the DVR program would record properly, but I would not be able to wake the computer without a hard reset. If I wanted a complete recording and happened to get back in the middle of it, I would have to wait until the recording was finished before I reset the computer to watch it. (Normally I would just restart the computer and then restart the recording, missing a few minutes of the program which was no big deal.)
  17. Anachronaut

    El Capitan - Problems with sleep

    Changed to SMBIOS 14,2 and now sleep is working [for now only? I will continue to monitor]. Also, my system starts up much better and more consistently since the change. AppleIntelCPUPowerManagement.kext is not loading, but apparently this is not a problem (see Xnu CPU Power Management | Pike's Universum link below). AppleSMBusController.kext is loading, but AppleLPC.kext is not loading. Both of these are supposed to be necessary, so I may need an SSDT to get AppleLPC.kext to load and run properly. Xnu CPU Power Management is active, as shown by the terminal: Anachronauts-iMac:~ anachronautscomputer$ sysctl machdep.xcpm.mode machdep.xcpm.mode: 1 Really, I don't know why sleep is working well now and was not before the change. It is true that the iMac 14,2 hardware specs are much closer to mine, so maybe something changed that I am unaware of (perhaps this Xnu CPU Power Management stuff, I didn't check before). Also, Pike R. Alpha seems to be a great source of knowledge, but he has not posted about power management in a while. For now if sleep continues to work, I may just put this issue to rest (bad joke intended) for while until more definitive El Capitan power management posts appear, as it is an active area of current research in the Hackintosh community. Reference Link (Please note that this is OLD, most of the information is written about Mavericks. While useful for some background, I think I may wait until more is available about El Capitan power management): Xnu CPU Power Management | Pike's Universum This may also be of some use, but I don't have the time for it right now: http://www.insanelymac.com/forum/topic/304369-how-to-check-your-states-–-using-aicpminfo-msrdumper-or-appleintelinfo/ For what it's worth, this problem may not be limited to hacks – see this discussion: https://discussions.apple.com/thread/6610693?start=75&tstart=0
  18. Anachronaut

    El Capitan: Realtek ALC AppleHDA Audio

    Update: Rebuilt system and kexts caches on my startup disk with KCPM Utility Pro, restarted and now all is working, including the digital S/PDIF outputs! Hopefully it stays stable. Thanks Toleda! Note: I also tried to "Repair Permissions on Entire Disk" with this utility, but it never finished [3+ hours], so perhaps something changed in 10.11.1.
  19. Anachronaut

    El Capitan: Realtek ALC AppleHDA Audio

    I started over, but seem to have the same result. I checked the info.plist from the AppleHDA.kext that is now in S/L/E and it seems to show the correct edits (see attachment). I attached a new IOReg file as well. Anachronaut’s iMac.ioreg.zip Info.plist.zip
  20. Anachronaut

    El Capitan: Realtek ALC AppleHDA Audio

    Here you go... Anthony’s iMac.ioreg.zip Info.plist.zip Platforms.xml.plist.zip
  21. Anachronaut

    El Capitan: Realtek ALC AppleHDA Audio

    Sorry for the long delay in responding, but work and life got in the way. I could not get this to work. For sake of simplicity, I removed all the Clover kexts to modify from the config.plist, and the realtek_HDA.kext from the Clover 10.11 folder. Then I went back to the original AppleHDA.kext, and ran audio_realtekALC-110_v1.0h.command (see attached alc_110_Terminal.txt) After restart, analog audio was working, digital out was not. I applied the fixes to Item 0 on Platforms.xml, and Item 3 on HDAHardwareConfigDriver/info.plist, as it appears this is what was needed from the instruction in your post. After installation and restart, none of the onboard audio choices show at all. This is what was happening with the Clover configuration, but I decided that this would be easier to diagnose, fix and re-apply after updates using just a modified AppleHDA.kext. I still am able to use my external USB audio driver, but I want to try to fix the internal one so I don't need to use it. Here are my current audio choices: It appears that modified AppleHDA.kext is loading: I have attached my modified AppleHDA.kext. Did I make an incorrect edit somewhere, or is there some other problem with the kext or my procedure? AppleHDA.kext.zip alc_110_Terminal.txt
  22. Anachronaut

    Clover with Mac skylake CPU support?

    True in the open market, but H170 or something like that is coming soon. It wouldn't be out of the question for Apple to make a deal to get these chipsets (iMac = MILLIONS of computers) before they are released to the general public. Maybe not custom chips, but normal production chipsets before they are available to us.
  23. Anachronaut

    El Capitan: Realtek ALC AppleHDA Audio

    Thanks for the quick reply. Requested files attached. Platforms.plist.zip Info.plist.zip
  24. Anachronaut

    El Capitan - Problems with sleep

    Nope. Check out the list of loaded kexts in the text file, generated from a kextstat -l terminal command. No AppleIntelCPUPowerMgt or AppleLPC to be found. Even more interesting, is that the extensions are in the S/L/E folder. Something must be preventing them from loading. I also found this extension that may play a part, and is also not loading according to kextstat: I think you are on to something here. Let me know what you find. I would love to do this without a custom DSDT or SSDT, since I don't currently have any of that (and really don't know anything about them other than the letters). Would a change in system definition get them to load. Currently, mine is a MacPro 3,1 (but the terminal insists it is an iMac – see attached text file). extensions.txt
  25. Anachronaut

    El Capitan: Realtek ALC AppleHDA Audio

    Audio through my analog ports is working after audio_cloverALC-110.command, but I am struggling to customize the install to get the S/PDIF output working. I really prefer to use the digital outputs for sound quality, so I bought this small addition to go with my board: http://www.amazon.com/gp/product/B0035J9Z7W?psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s00 It connects the S/PDIF header from the board to ports on the back of the case. It definitely has power, as the laser for the optical output is working. I have tried both the optical and coaxial S/PDIF outputs from the attached board. Seeing that neither was working, I tried to follow the instructions here: https://github.com/toleda/audio_ALC_guides/blob/master/Customization%20-%20Realtek%20ALC%20AppleHDA_v2%20%5BGuide%5D.pdf The relevant section says: 7. Substitute SPDIF-2 Wire Output: Replaces SPDIFOut Optical with motherboard SPDIF 2 wire SPDIF audio output device Credit: intamara: Lion HDMI Audio - Part 2a: DSDT Edits/Discrete - AMD/Nvidia - Page 29, Post 289 A. Edit Platforms.xml/zml 1. Open Item/PathMapID 2. Open the current SPDIFOut (last item) 3. Edit this path map as follows: 4. Current: ⁃ Item 0/NodeID/Number/30 ⁃ Item 1/NodeID/Number/6 5. New: ⁃ Item 0/NodeID/Number/17 ⁃ Item 1/NodeID/Number/16 B. Edit HDAHardwareConfigDriver/info.plist or realtekALC/Info.plist 1. Open Item/CodecID 2. Verify CodecID/LayoutID 3. Edit ConfigData (1150 only, edit each entry, 21 to 01) ⁃ Find: 21171cf0 21171d00 21171e00 21171f40 ⁃ Replace: 21171ca0 21171d01 21171e43 21171f99 ⁃ Find: 21e71c90 21e71d61 21e71e4b 21e71f01 ⁃ Replace: 21e71cf0 21e71d00 21e71e00 21e71f40 C. Save, install and restart It appears that I can edit Platforms.zml as described, but I can't find the same items in the Platforms.xml to edit. Also, the structure of the HDAHardwareConfigDriver/info.plist seems to be different than is described, and I cannot figure out how to achieve the edits listed. I must say that I am a bit confused about the item numbers, as everything in the plists is an item. According to the guide, Realtek 887 is item 1. Specs for the motherboard say Realtek 887, and so did the audio_cloverALC-110.command install script. DPCIManager lists the audio codec as Realtek 888B, but apparently this is the same as 887. ASUS H97M-PLUS — BIOS v2404, i3-4370, ASUS GeForce GTX 750 Ti STRIX Had to do some workarounds to attach files as some formats are not allowed for posts on this board. Hopefully this will be enough information for someone with more knowledge to assist me. One last thought. In the tools listed for inflating and deflating the zlib files here: https://github.com/toleda/audio_ALCInjection/blob/master/zlib_terminal.zip The instructions for the perl script leave a .xml file that Xcode reads as xml. To get it to read as a plist, I just appended .plist to the file, which worked great. Then I thought, why not just add this when inflating the .xml. This also worked. Here are the commands: Last login: Sat Oct 24 16:41:19 on ttys000 Anachronauts-iMac:~ anachronaut$ cd /Users/anachronaut/Desktop/New\ Folder Anachronauts-iMac:New Folder anachronaut$ perl zlib.pl inflate Platforms.xml.zlib>Platforms.xml.plist Anachronauts-iMac:New Folder anachronaut$ perl zlib.pl inflate Platforms.zml.zlib>Platforms.zml.plist Anachronauts-iMac:New Folder anachronaut$ I extracted the AppleHDA.kext from the El Capitan installer. It was only in one place, and seems to be complete. It is working on my computer after the audio_CloverALC110.command script. Clover_config_plist.txt DPCIManager_Misc_Boot_Log.txt DPCIManager_Status.tiff info_plist.tiff Platforms_xml.tiff Platforms_zml.tiff System_Report_Audio1.tiff System_Report_Audio2.tiff Anachronaut’s iMac IOReg.tiff platforms_xml_plist.txt Platforms_zml_plist.txt AppleHDAHardwareConfigDriver_Info.txt Audio Clover 110 audio script.txt
×