Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/22/2019 in all areas

  1. If 'svnversion' are gone in newest os, I think switching all 'svnversion' to 'svn info | grep "Revision" | tr -cd [:digit:]' cmd is the best option.
    4 points
  2. No, everything stock standard in Catalina. If I run svnversion command in Cat terminal ---> get "command not found" (but svn info works so maybe work around) If I run svnversion command in High Sierra/Mojave terminal---> get correct Clover revision number (4968)
    3 points
  3. Tools to install Catalina to MBR HFS+ partition. Just make it easier now. How to finish the Catalina installation. 1. Use EasyMBR-Installer1015 to make USB Catalina Installer. 2. Boot to USB Catalina Installer, open Utilities -> Disk Utility, format as MBR HFS+. Install Catalina to blank MBR HFS+ "Target" partition. 3. Boot to USB Catalina Installer, open Utilities -> Terminal, run the script command: copytempdata 4. Boot to "Target" MBR HFS+ partition on single user mode (-s), run the script command: hfsupdatecache 5. Reboot to "Target" MBR HFS+ partition, setup user name and login, finish the installation.
    3 points
  4. I always check commit from several github kext everyday And make a new compiled kext if there is new change
    2 points
  5. I also noticed the missing revision number when making the Clover Package with the makepkg script in Catalina (Xcode 10.2.1). The build log throws the error below ... fusion71au@fusion71aus-Mac-Pro Clover % cd CloverPackage fusion71au@fusion71aus-Mac-Pro CloverPackage % ./makepkg ./makepkg: line 38: svnversion: command not found Strangely enough, when I build Clover with the Build_Clover.command in Catalina, the Clover revision number is generated OK. Also revision number ok with make iso...
    2 points
  6. 2 points
  7. All the mess erased! Guys please be more polished in your comments, as we always says, if you disagree with anyone use the PM box, (respectfully too) don't do this in public. Best regards to all
    2 points
  8. Hackintool v2.6.3 Released - Added Atheros BT device detection
    2 points
  9. Version 10.15.x

    6,975 downloads

    Patched OSInstaller.framework to allow macOS 10.15 installation on MBR HFS+ partition. Please read Readme-10.15.pdf first. How to finish the Catalina installation. 1. Use EasyMBR-Installer1015 to make USB Catalina Installer. 2. Boot to USB Catalina Installer, open Utilities -> Disk Utility, format as MBR HFS+. Install Catalina to blank MBR HFS+ "Target" partition. 3. Boot to USB Catalina Installer, open Utilities -> Terminal, run the script command: copytempdata 4. Boot to "Target" MBR HFS+ partition on single user mode (-s), run the script command: hfsupdatecache 5. Reboot to "Target" MBR HFS+ partition, setup user name and login, finish the installation. Also, you need to setup Clover as BooterConfig=0x28, CsrActiveConfig=0x67 ---------------------------------------------------------------------------------------------- List of known issues: 1. Some app-pkg-installers can't install to HFS+, but install to APFS fine. ---------------------------------------------------------------------------------------------- What is this patched OSInstaller doing? 1. Pass the MBR check, allow macOS 10.15 installation on MBR partition. 2. Pass the Firmware check, bypass the error of "An error occurred while verifying firmware". 3. Pass auto-convert to APFS , "ConvertToAPFS=false" is no longer worked with 10.15. 4. This MBR-Manual-Method will never convert to APFS, and will always install as HFS+ partition. 5. This MBR-Manual-Method works with both MBR HFS+ and GPT HFS+ partition (GPT+recovery). No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch. What's the difference between createinstallmedia method, MBR-Manual-Method, and MBR-Automatic-Method? As the following.... 1. createinstallmedia method, needs stage 1, stage 2 installation process, which is worked with GUID partition only, always convert to APFS format. 2. MBR-Manual-Method (same as 10.12), install via stage 2 manually, which is worked with both MBR HFS+ and GUID HFS+, will never convert the partition format. We can manually format as MBR HFS+ or GPT HFS+ on installation screen like as 10.12. We can manually select MBR HFS+ partition to install 10.13, 10.14, 10.15 on installation screen now. Needn't to update the MBR-Manual-Method files, it will still work on 10.13, 10.14, 10.15 future versions, I think so. It can be installed as Fresh installation on formated blank partition only, but can't be installed as update from previous version. 3. MBR-Automatic-Method (new for 10.13+), End of MBR and HFS+, there is no more MBR HFS+ patch available for 10.15 native OSInstaller. How to make 10.15 installer for MBR (MBR-Manual-Method)? Just use EasyMBR-Installer1015 to make installer, it works with both MBR and GPT. Read HowTo inside the dmg first, same as 10.12. Read HowTo Q/A Q4. How to patch to work with CPU SSE4.1 only for Mojave, Catalina? Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store? Read HowTo Q/A Q7. How to update 10.15.x combo-update to MBR and GPT with installScript directly? And, need a SMBIOS supported with /System/Library/CoreServices/PlatformSupport.plist. Q6. How to download the full installer app via swscan.apple.com, instead of App Store? A6. Some people download installer app from App Store, and get only 18 MB size, not the complete installer app (5.68 GB). You should boot to 10.12, or 10.13 to download it again from App Store, or use script Q6-DownloadFullApp/installScript_fullapp to download the full installer app via swscan.apple.com.
    1 point
  10. Do you want to quickly find your boot log, or ever wanted to know which version of bootloader is installed on your disk(s), had the need to dump your BIOS from OS X, just curious about your own system setup or been asked to provide your setup information to others when asking for assistance? DarwinDumper is a useful collection of readily available tools, and scripts wrapped in an application framework giving you a convenient method to quickly gather a system overview of your hack or Mac. And rest assured that enabling the privacy option will mask sensitive data like the IOPlatformSerialNumber, IOPlatformUUID, IOMACAddress(s), USB Serial Number(s), SystemSerialNumber, serial-number, fmm-mobileme-token-FMM, MLB and ROM efi vars and CustomUUID in the dumped files and report. Current Release Version: 3.1.1 The system dumps are saved to a folder or your choice, but defaulting to the same directory as the main application. You can choose to setup a symlink to make it simple to run DarwinDumper from the Terminal. There is an option to create an html report showing a complete overview of the dumps. This report will mostly just contain the text dumps as you'll find in the main dump directory, but for some dumps there is extra processing to try to present the information in a better way. For example, the Disk Partitions and Unique ID's dump will show a visual map of the disk layout, and the DMI Tables (SMBIOS) dump will show the data split by table type. Note: The html report does not contain all files from a complete dump so if seeking assistance for a problem and you wish to send someone a DarwinDump then you will want to send the complete dump directory and not just the .html report file. The following can be read and dumped by DarwinDumper: - ACPI tables. - Audio codec and further info. - Boot loaders and configuration files. - CPU info. - Device-properties. - Disk partition structure / info. - Disk sectors (hex). - DMI (SMBIOS). - EDID. - I/O Kit Registry. - EFI Memory Map. - EFI vars (some). - Kernel information - Kexts - (list of currently loaded kexts). - Memory. - NVRAM (both Apple specific and UEFI firmware variables). - SMC Keys. - LSPCI (PCI vendor & device codes) dumps. - Power (Sleep/Hibernate) settings. - RTC. - System Profiler. - System BIOS. - System Log(s). - Video BIOS. License: DarwinDumper is licensed under GNU General Public License, version 3.0 (GPLv3). Tools included: AnalyseVBIOS Copyright: Not Known. License: Not known Source: http://www.insanelymac.com/forum/topic/211294-information-on-vesa-modes-in-atinvidia-bios/ Alt Link: https://www.dropbox.com/s/dnp903x2z9pqf8k/AnalyseVBIOS.zip?dl=0 AppleIntelInfo Copyright: © 2012-2017 Pike R. Alpha. All rights reserved. License: Creative Commons Attribution-NonCommercial Source: https://github.com/Piker-Alpha/AppleIntelInfo atomdis Copyright: Michael Larabel @ Phoronix.com License: GPL Version 2 Source: http://www.phoronix.com/scan.php?page=article&item=amd_atombios_dumper bgrep Copyright 2009 Felix Domke <tmbinc@elitedvb.net>. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing official policies, either expressed or implied, of the copyright holder. Source: https://github.com/tmbinc/bgrep bdmesg Copyright 2010 by Islam M. Ahmed Zaid. All rights reserved. License: GPL Version 2 Source: http://forge.voodooprojects.org/p/chameleon/source/tree/HEAD/trunk/i386/util/bdmesg.c Alt Link: https://sourceforge.net/p/cloverefiboot/code/1905/tree/CloverPackage/utils/bdmesg/bdmesg.c cmosDumperForOsx Created by rafirafi, revised extensively by STLVNUB License: Information not available Source: https://www.dropbox.com/s/bg1q0yho6g7u3xn/cmosDumperForOsxV0.1.zip?dl=0 csrstat Created by Piker-Alpha Copyright: © 2015-2017) by Pike R. Alpha License: Information not available Source: https://github.com/Piker-Alpha/csrstat dmidecode Original nongnu.org License: GPL Version 2 Now updated and hosted by acidanthera Source: https://github.com/acidanthera/dmidecode dumpACPI Created by blackosx. Idea taken from PHPdev32's MacIASL. Source: https://bitbucket.org/blackosx/dumpacpi edid-decode Created by Adam Jackson, revised by Andy Vandijck License: Information not available Original Source: http://cgit.freedesktop.org/xorg/app/edid-decode Revised Source: https://www.dropbox.com/s/l0htffnqzs9e1vg/edid-decode.zip?dl=0 fdisk440 Apple Computer, Inc. License: APSL v2.0 Original Source: http://www.opensource.apple.com/source/diskdev_cmds/diskdev_cmds-491/fdisk.tproj/mbr.h Modified by Zef Source: http://forge.voodooprojects.org/p/chameleonApplications/source/tree/HEAD/trunk/fdisk.tproj Alternate Link: https://www.dropbox.com/s/odl9kp38j3flla5/fdisk440.zip?dl=0 FirmwareMemoryMap script Amit Singh (showbootermemorymap) Further development by bcc9 and dmazar License: Information not available flashrom http://flashrom.org/Flashrom License: GPL Version 2 Source: https://www.dropbox.com/s/gfmqx2t7lvofs1v/flashrom.zip?dl=0 getcodecid Copyright © 2012 AnV Software. All rights reserved. License: Information not available Source: https://github.com/Gengik84/getcodecid getdump Created by fassl?, modifications by Slice and AutumnRain? License: Information not available Source: https://sourceforge.net/projects/voodoohda/files/ gfxutil Copyright 2008 mcmatrix. All rights reserved. License: Information not available Historic detail can be found at forum.netkas.org Source: https://github.com/acidanthera/gfxutil iasl Copyright © 2000 – 2014 Intel Corporation. License: Information not available Source for v20200110: https://www.acpica.org/node/176 ioregwv Apple Computer, Inc. License: APSL v2.0 Original Source: https://opensource.apple.com/source/IOKitTools/IOKitTools-86/ Modified by blackosx Source: https://bitbucket.org/blackosx/ioregwv lzma Copyright © 2013 Igor Pavlov. License: GNU Lesser General Public License Source: http://www.7-zip.org/sdk.html This build by Slice at insanelymac.com: https://www.insanelymac.com/forum/topic/311786-updated-lzma-utility-v1514/ lzvn Copyright: © 2014 Apple Computer, Inc. All rights reserved. License: APSL Credit: Piker-Alpha, Andy Vandijck, MinusZwei. https://github.com/Piker-Alpha/LZVN MacGap2 Created by Tim Debo. All rights reserved. License: MIT Source: https://github.com/MacGapProject/MacGap2 Macpmem driver (Macpmem.kext) Copyright © 2007-2011 Volatile Systems. Copyright 2013-2014 Google Inc. All Rights Reserved. License: GPL Version 2 Source Code: https://github.com/google/rekall/tree/master/tools/osx/MacPmem]https://github.com/google/rekall/tree/master/tools/osx/MacPmem nvram Apple Computer, Inc. License: APSL v2.0 Modified by blackosx Source: https://bitbucket.org/blackosx/nvram oclinfo Copyright © 2009 cmf License: GPL Version 2 Source: http://www.insanelymac.com/forum/topic/170796-opencl-info/ pciutils driver (DirectHW.kext) DirectHW is Copyright © 2008-2010 coresystems GmbH License: GPL Version 2 Source: https://github.com/CloverHackyColor/directhw Kext: Pre-built (Signed) Kext pciutils lspci Copyright © 1997--2008 Martin Mares License: GPL Version 2 Source Code: https://git.kernel.org/pub/scm/utils/pciutils/pciutils.git RadeonDump Created by Dong Luo. Copyright 2008. All rights reserved. Modified by Andy Vandijck License: Information not available Source: http://www.insanelymac.com/forum/topic/282794-darwindumper/page__st__120?do=findComment&comment=1920068 Alt Link: https://www.dropbox.com/s/5drpckxlmaot732/RadeonPCI.zip?dl=0 radeon_bios_decode Created by Dong Luo. Copyright 2008. All rights reserved. License: Information not available Source: http://www.insanelymac.com/forum/topic/282794-darwindumper/page__st__120?do=findComment&comment=1920068 SMC_util_FansOnly Copyright © 2006 devnull License: GPL Version 2 Source: https://www.dropbox.com/s/ra9h6gbjj6yhgol/SMC_util_FansOnly.zip?dl=0 smcutil Copyright © 2006 devnull License: GPL Version 2 Source: https://www.dropbox.com/s/0dgvexijx4oewfr/smcutil.zip?dl=0 VoodooHDA.kext Created by fassl?, modifications by Slice and AutumnRain? License: https://sourceforge.net/p/voodoohda/code/HEAD/tree/tranc/License.h]https://sourceforge.net/p/voodoohda/code/HEAD/tree/tranc/License.h Source: https://sourceforge.net/p/voodoohda/code/HEAD/tree/]https://sourceforge.net/p/voodoohda/code/HEAD/tree/ x86info Written to succeed CPUID by Phil Karn (KA9Q). Contributed to by various people. OS X compatability by Slice License: GPL Version 2 Original Source: https://github.com/kernelslacker/x86info Revised Source: https://github.com/CloverHackyColor/x86info Running DarwinDumper from the command line: From Terminal, you can initiate DarwinDumper by running the following script directly. /DarwinDumper.app/Contents/Resources/public/bash/script.sh To help with this, the UI has a Symlink option which you can click to create a symbolic link which points to the above script. DarwinDumper can then be subsequently run from the command-line by loading a new Terminal window and typing darwindumper followed by return. $ darwindumper usage: [-a zip,lzma,none] [-d acpi,appleintelinfo,audio,biosSystem,biosVideo,codecid,cpuinfo,devprop,diskLoaderConfigs,bootLoaderBootSectors,diskPartitionInfo,dmi,edid,bootlogF,bootlogK,firmmemmap,memory,ioreg,kernelinfo,kexts,lspci,rcscripts,nvram,opencl,power,rtc,sip,smc,sysprof] [-h] [-l] [-o html,private] [-p 1,2,3,4,5,6,7,8] [-v] Example: $ darwindumper -l Will re-run the last dump used options. Credits (in alphabetical order): acidanthera team, Adam Jackson, Amit Singh, Andy Vandijck, Apple Inc., arsradu, bcc9, blackosx, cmf, DieBuche, dmazar, Dong Luo, droplets, ErmaC, Felix Domke, Google Inc., Intel Corporation, InsanelyDeepak, JrCs, Kabyl, Kynnder, Martin Mareš, mcmatrix, Michael Larabel, Mickey1979, phcoder, Phil Karn, Piker-Alpha, rafirafi, гык-sse2, Slice ,sonotone, STLVNUB, THe KiNG, Trauma, Volatile Systems, xsmile, !Xabbu. DarwinDumper was originally inspired as an open project by Trauma, it has remained an open project and please keep it an open project, so if you make any changes or additions to it then please share your work here. Please report any feedback, requests or bugs. Known issues: v3.1.0 1 - When SIP File Protection is enabled, dumping disk partition info of non-APFS containers and disks which are not APFS physical stores may fail when running from DarwinDumper via the graphical interface. However, it's been known to succeed when using DarwinDumper from the command line. Something to do with osascript. 2 - lzma archive option has been known to fail on macOS 10.15 when running dumps requiring root privileges. macOS Version support: - v2.9.9.2 is for older macOS versions - v3.0.4 requires OS X 10.9 and newer to run in the Finder, though it should work from the command line okay on older OS versions. - v3.1.0 was updated for newer macOS versions and has been tested on 10.13 and 10.15. DarwinDumper Download
    1 point
  11. So, I am officially crazy... I bought 26 Powermacs (G5) And I modded them ALL They are now ready for ATX and mATX Mainboards… But why 26? Did I mention I was crazy?! (And they were only sold together…) I modded G5 Cases before – They kind of became my passion. This time I wanted everything to be perfect: - Keep as much of the original design as possible - Cut as less as possible - Since it is impossible to find a G5 Case without dents and scratches, I wanted to paint them, freshly. I am done now and it is time to share my experiences: It was a rough 6 months from start to finish. The project kept me busy during all of the winter. I worked every weekend on it, till late. I need to apologize… …to my family for occupying their workshop, guest rooms and garages …to my friends for neglecting them during the last months …to the dogs and the cat for waking them up from their afternoon nap every now and then (because of the metalwork-noise). I hope to be able and show everybody that it was worth it - And that someone out there is appreciating the work, as well. Back me up, guys - Spread the love :-) I believe in Apples high quality and the unique design of Sir Jony Ive My mods include a preinstalled power supply (and even watercooling on some) Countless hours of work and high-quality components & tools were used Of course, you can come and have a look if you are near the South of Germany (or the North of Switzerland). Finished Builds: I do not have the money to equip all cases with CPU, RAM and SSDs right now. But it would be so much fun to do it, now that all the hard work is done. I will definitively equip machines later and build completely custom machines I already equipped two of the shown modded cases with complete hardware. One was for a music-studio. One for my brother. Threads for the finished build projects will be linked here later: Workstation & Gaming-Beast for my brother: - ATX- X99-Mainbaord - 8-Core Intel XEON E5-1660 v3 (Overclocked to 4 GHz - all-core) - 64GB ECC-RAM (Registered DIMMs) with dual Copper heatsinks & Heatpipes - 3x1TB SSD RAID5 - Two 1080Ti in SLI (two flexible SLI Bridges were later installed) Ryzentosh (For music production studio): o mATX Mainboard o Ryzen 1700X o biggest cooler on the market (BeQuiet! Dark Rock Pro) o 32GB RAM (ECC Unregistered DIMMs) with Aluminium heatsinks o 3x1TB SSD RAID5 A finished (painted) case from the outside. The Apple logo is gone after painting… For the better, I think! The rear of a finished build Preliminaries: All the planning that goes into modding one case actually affected 26 cases. It had to be perfect. That’s why I planned every step and every purchase of parts, meticulously. Then I applied every individual operation to all cases, one after another. This raised the quality of all cases. The metalwork (Filing, sanding, equalizing, gluing and painting) took a very long time. I don’t even know how many hours it took per case because I always did one individual operation to all cases (e.g. filing or cutting) and then started the next task. It probably took a couple of days per G5. Then I broke my shoulder in May 2017 (doing something stupid on an Austrian glacier). That made it harder to do the sanding for a couple of weeks. But even though it was painful, I couldn’t stop... The different case-types: The painting turned out very well. I chose the best 14 cases after painting and decided to finish modding them, completely. I will call these “Barebones” in the following. In the pyramid-pictures they are always on top, because they were finished last and taken to the workshop more often. The 14 best cases got equipped with a 600W PSU, front-panel, water-cooling (for the mATX Barebones), apple power-cables, etc… They are now proper Barebones. No more hard work needed to finish the build. Just missing a motherboard (and maybe hard drives) - and done. 12 other cases did not end up perfectly painted, but still good. Some orange peel here and there. Only 4 of them have stronger orange peel. I will call these 12 cases “Empty Ones” in the following. An “empty case” What to do with the “Empty Ones”? They are also clean and modded. Ready for ATX or mATX boards, empty PSU-Enclosure… One could make furniture or art out of them… One could finish the mod with a new front panel. Or one could paint them again in a different colour… I don’t know… Let’s start from the beginning: Delivery: first we sorted the cases from “good condition” to “scratched and scuffed” This sorting turned out to be useless, later as I ended up sanding, filling and painting all of them. I chose the best ones in the end. We disassembled everything and sorted the parts – plastics, aluminium, batteries, electronics, etc… then gave everything to recycling. I am an environmental engineer, so this was important to me. I gave away all parts that could possibly be reused - Like fans, RAM and graphics cards. There are no pictures of the disassembly, because it has been done by many people already and we were also too busy (it took a couple of days). We ended up making our own tools and screwdrivers for removing the processors and mainboards, because many screws are hard to reach. All parts that I wanted to keep were cleaned and kept separately. E.g. the fan grilles on the back, the rubber screws for the HDD Caddy or the DVD-drive stand-offs Planning & Conversion Then I made a plan for the easiest ATX conversion with the least cutting. Best thing to do: Cut an opening to the back - big enough for ATX boards I/O and reuse the original PCIe slots for graphics cards. This turned out to be just perfect. I tested different boards. E.g.: ASUS TUF X99 (ATX) and ASrock AB350M (mATX) Night shift – working with the Dremel First cut for the ATX Mainboard I/O. All the Internals are removed. Also, the fan grille with its many mini-screws. So that the plastic is not melting. Cut-out (before filing and sanding). Sharp edges. Straight cut of the long sides thanks to the big angle grinder. Shorter sides were done with the Dremel for precision towards the edges. Then the filing and sanding removed all sharp edges. I removed all the Motherboard standoffs from the inside, cleaned the surface with Isopropyl alcohol and glued the standoffs in the new places for ATX Boards using the 2K Aluminium Epoxy. This took a lot of measure to fit a mainboard in the right position for the PCIe-Slots. I bought test-boards that were placed in the empty case with a graphics card plugged in and then the screwholes werde marked on the stencils. I made two different stencils. One for ATX Boards and one for mATX Boards: Putting the standoff through the stencil and securing it with a screw Cleaning the surface before gluing. Both stencils with standoffs and fresh glue – right before placing it in the cases ATX stencil in the case – gluing down the standoffs. mATX stencil while gluing. It had to sit like this over night to make sure the glue is hard. Then, the stencil was taken out. There is no tray necessary under the mainboard. All stand-offs / threads are in the right position for standart mainboards, now. Now that all the disassembly, cutting and gluing was done it was time for some fresh paint. The painting: Before painting it was necessary to fill dents, file edges (there were chips, especially on the feet) and sand EVERYTHING to smoothen the surface and remove unwanted oils. Fill, file, sand, repeat… I used 2K Aluminium epoxy to fill dents The Epoxy is like a cold weld. Hard and sturdy. Dents before filling Dents after filling - before sanding More filling Filled and sanded case.   At first I did not want to paint them myself. So I bought the right 2K-Aluminium-paint (had to try different ones to find the perfect colour and shade) and handed four cases with the paint over to a professional paint shop (arm-industry - specialized on parts for tanks). They were happy to try this because they wanted to train their varnisher-apprentices on something that is more difficult than the usual tank-parts. The results were good, but It turned out that these cases are really hard to paint… I was not 100% happy with the result. They returned from the paint-shop with some varnish-runs on the bottom of the cases. They also missed some spots that were hard to reach. So, I changed my mind and decided to paint all the cases, myself (again...) What a fool I was. This took a week. First of all, I needed a cleanroom. So, I converted a shed in my parents’ garden. Shed / Cleanroom – Winter-time Thanks to my brothers’ help, the setup turned out really clean and airtight. Crucial for keeping it warm. To keep the shed warm, I used a big oven and additional electric heaters. My father even set up a big chimney, so that the smoke was led further away from the shed (as smoke=small particles that would leave marks on the fresh paint). I had a compressor on hand (with 30m hose) and used a spray-gun for coating the cases with Aluminium-paint. We used the spray-gun for car parts before. Paint-Shed from the inside Hanging case before spray-painting Usually two or three cases were sprayed at a time. All cases were sprayed at least two times with thin coats. After spray-painting it was time for drying The freshly sprayed cases were put in a sauna at roughly 80 degrees Celsius. That sped up the hardening and caked the varnish in. The fully varnished cases after drying. This is the result: The cases with the white bar on the back have the original Apple 2x2 Wifi / Bluetooth antennas in them (with two plugs) I installed a second 2x2 Antenna. Now they are 4x4. The (IPEX? MHF?) connectors are bigger than those I have seen before. They don’t fit the tiny connectors on laptop-wifi-cards. Maybe someone used the Apple Antennas with a PCIe Wifi-card before and can give me a tip or even post a link? The “Empty Ones”: This is what the 12 empty cases look like, that have some orange-peel skin: Basicaly the underside of ALL cases looks like this - because they were placed on their feet for drying or Spraying. You will never see this when the case is standing on its feet. An “empty-one” - ready for ATX boards. Empty PSU-Enclosure is installed. Fan-bracket is in place. Sometimes still with apple fans. A finished ”empty” mATX case You can see some orange-peel skin or varnish-runs on the “Empty Ones” I modded the 12 best-painted cases to create fully-modded Barebones: Time for re-assembly: Fan-Bracket: The Apple-fans were removed from the fan bracket. They were loud and needed re-wiring anyways. It is recommended to put more modern fans in there. I renewed the rubber-fixings where necessary. You do not need screws to put fans in. They are held in and decoupled by the rubber. Vibration is not passed on to the case. I put the PCIe slot brackets back in (they were also painted, of course) using the rubber-headed HDD screws from other cases. In case you want to add more HDDs you have the right screws at hand. The fan-bracket fits in its original position. That works fine for most Mainboards. If you have a Mainboard with very high VRM heatsinks or high I/O (e.g. with 6 stacked USB-Ports) you can either remove the fan bracket completely (I did that for my brothers build and just clamped some BeQuiet! Silent-Wings 2 - 92mm in) or move the bracket up a bit - by not inserting the hooks under the lip, but rather clamping the bracket above the lip (I did that for the Ryzentosh, it is also very stable). The bracket holds two 92mm x 25mm Fans My favourite: Noctua NF-B9 redux-1600 PWM - 92mm They look like the original ones and are very quiet. (I used them in two projects) Cheaper Arctic PWM Fans for testing Front-Panel: The Power-Buttons needed to be painted, as well. Over time they lost some of their thin chrome coating due to touching. The 2-K varnish is thicker and will be much more durable. Secured the power-buttons down using double-sided tape during varnishing To make them fit perfectly again, I needed to scrape of excess paint from the sides. The buttons would easily get stuck otherwise. The case without any front-panel board or power-button. Half of the G5s I bought were “late 2005” models. The front-panel-boards of all G5s have the same size and fit in all the cases. Only models before “late 2005” have a front panel connector-socket. So, I had 14 front-panels that could be used with BlackCH-Mods-cables, and 14 perfectly painted cases. That’s a match. Re-installing the power-button board with its securing ring. This took a long time because every button had to be re-adjusted to work nicely again. Also notice the rubber piece on the right-hand side. This is needed to support the front-panel board when plugging in the cable to the connector: Installation of the front-panel board. The housing of the front-panel board has also been painted. The custom-made front-panel cable by BlackCH Mods. They were not cheap but they work. I marked all the connectors on one of the cables to make them easier to identify. Audio works perfectly even though there is a proprietary sensing pin on apples board. I recommend to set the front-panel type to “AC’97” in the BIOS / UEFI instead of the default “HD Audio”. That way the front panel audio is basically ON all the time and you can choose other outputs from the task-bar. I used Realtek drivers for Windows in my last two builds. For a Hackintosh you would need to follow BlackCH Mods manual or ask the community about the best settings. Plugging in the mod-cable to the front-panel connector. Securing the plug with the black cap. It is pushed down even further than shown in the picture – so it clipped on to the board itself to give the connector more pressure and therefore stability. DVD / Blu-Ray drive: Eject the disc tray with a paper clip. Unclip the front-plate, so it does not get stuck in the auto-opening Apple-aperture Screw in the stand-off screws (I saved those) Standoffs installed Finally, slide the drive into the mounting-bracket and close the two little retention arms. Done. PSU (Power Supply Unit): I thought a long time about the perfect PSU. I really wanted to re-use the original PSU-housing, because of the clever placement in the case. It sits flush with the mainboard at the bottom and the original power- socket is a MUST to reuse for aesthetics and stability. The original Apple power-plug with Apple power-cable. How do you get a new PSU into the original Apple PSU? I did not want to crack open a standart ATX PSU and jerry-rig its sensible (and dangerous) electronics into the original PSU-housing. So, I looked for a server-PSU that would fit inside the original housing completely with own housing and fan. Safe and sound. Not an easy task setting those up, because server PSUs often have proprietary connectors. Also, I wanted 600 Watts of output power to drive any overclocked CPU with a powerful graphics card like the GTX 1080Ti. Soldering on the new -internal- power-cable to the original power-socket in the Apple PSU housing. Shrink-tube protects the soldered joints. The cable will be connected to the new PSU inside. As an extension. The input-filter is still connected to the socket. The Apple power-cord. I found the perfect PSU. A 600W PSU by Supermicro. Supermicro is a very known brand in the professional server market. So, I can trust those PSUs to constantly deliver real 600Watts. They are designed to run under full load for years. Hence, they can be really expensive. Many cheap PSUs just claim to be 600W but struggle to hold that power up for longer periods of time (or they degrade). This will not happen with a Supermicro PSU. The 600W PSU comes with a 80+ Platinum rating. That is one of the highest Energy efficiency ratings available. Higher than 80+ Gold, Silver or Bronze (which is kind of the standard right now) 80+ Platinum means 92-94% of the Input-power is delivered as output. Only 6-8% is transformed into heat. That was important to me in order to keep the PSU quiet. All PSUs before they were put in It has the 1U form factor. So, you could actually fit two of them in the housing. The 600W PSU plugged into the extension cord. Securing the PSU in place The 2005 Powermac Models have a bigger server power-plug (C19) suitable for higher power delivery of over 1000 Watts. Almost half of the cases have this kind of plug. They also have a bigger input filter. Soldering the extension on. Finished housing with server power jack (C19) on the outside and standart plug (C13) on the inside PSU inside the original Apple-Housing All the cables come out near the back of the case. I created bigger openings for the cables to feed through. All PSUs are prepared The PSUs and their connectors have been tested with a PSU-tester. These Server PSUs still have some proprietary connectors (and some cables, that are a bit shorter than usual), So, I bought different adapter-cables and extensions for the PSUs to make everything universal. PSU-Cables: - PCIe 8-Pin (2x) for graphics cards (over CPU 8-Pin adapter) - CPU (1x 8-Pin, 1x 4-Pin) – actually there is one more 8-Pin, but it is occupied by the PCIe-adapter. So, it is possible to do a dual-CPU setup with a small graphics-card, that does not need a dedicated power plug, as well. - Molex (2x) (6x over SATA-Adapter) - SATA (5x) (over Molex adapter), black sleeved - 24-Pin ATX (20 Pin is possible) + Extension (black) + Dual PSU connector - 12V Fan (4x over Molex Adapter), black sleeved Different types of cables and adapters (in an mATX Case) You can hide most cables behind the PSU-housing and under the mainboard, as the standoffs that hold the mainboard are quite high. That is the biggest benefit over using one of those tray-adapter-plates that would use up the space behind the mainboard. The cables in an ATX Case (not hidden / cable-managed) HDD-Caddy: The original Apple 2-Bay HDD-caddy was glued into its new place to be out of the way. Only necessary in the ATX-Cases to fit the bigger ATX Boards in. Using high-temperature silicone. Molex Power provided by adapter (if needed for 3,5” drives, most new 5400 rpm HDDs don’t even need Molex anymore) ATX Case with a bit of cable management and the HDD-caddy in place Finished ATX Barebones: Finished ATX case with all equipment and the server power-cord Finished ATX case with the Acrylic cover Different finished ATX Case with cover and cable management Watercooling (mATX Barebones): Now that the “Empty Ones” and the ATX Barebones were finished It was time to mod the mATX Cases. I added watercooling to the mATX-Barebones: Best place for the radiator is the front. Here it will blow the hot air directly out of the case. This is the 240mm radiator for the watercooling of all mATX cases To decouple the vibration of the loop from the case I used a foam seal on the front of the radiator and a thick silicone-seal on the sides and the top Gluing the radiator in with special high-temperature silicone. (This Silicone is usually used to attach the IHS to a CPU or to seal an exhaust pipe) – good for temperatures up to 329°C Radiator in Place. Thick silicone seal is decoupling the vibration of the water-pump that travels through the loop. The 240mm radiator fits right in between the PSU and the top-compartment. The mounting kits for this Cooler Master AiO support all modern processors and sockets (775, 1150, 1151, 1155, 1156, 1366, 2011, 2011-3, 2066, AM2, AM2+, AM3, AM3+, AM4, FM1, FM2, FM2+) Two 120mm high static pressure fans come with the watercooling loop. They blow out. You could of course turn the fans around to suck air in (positive pressure). Equipment: I saved the important bits and bought cables for all Barebones Every fully modded Barebone has its own new power-cable (half of them white apple cables, half of them black OEM server cables) All fully modded Barebones have the acrylic cover I kept HDD rubber-head screws, DVD-drive standoffs, Pump Mounting Kits in a little bag. Finished mATX Barebones with watercooling: Here are some pictures of the internal layout: Pictures of the outside can be seen in previous posts. Finished mATX Barebone Finished mATX Barebone with all equipment Finished mATX Barebone with all equipment Types of cases & Barebones: What I have right now: 12 fully modded Barebones: 6 - mATX - with watercooling 6 - ATX - (eATX boards should also fit) 12 “Empty Ones” - 8 prepared for ATX (3 of which have heavier orange-peel) - 3 prepared for mATX (1 of which has heavier orange-peel) The End: Thats it for now… What do you think? Was it worth it? What hardware would you put in? Please let me know… ;-) Yours, sincerely wise_rice
    1 point
  12. Ok, i will add resources files to AppleALC github then. I hope @vandroiy2012 can accept pull request. I have one pending pull request before
    1 point
  13. 1 point
  14. AirportBrcmFixup is a Lilu plugin, so EFI/CLOVER/Kexts/Other beside Lilu. https://github.com/acidanthera/AirportBrcmFixup/blob/master/README.md
    1 point
  15. I have a same issue too with latest 2.0.2 AirportBrcmFixup.kext haven't been fixed yet by source
    1 point
  16. First make git clone many github source into one directory, eg "ManualBuild" After that open your terminal and "cd ManualBuild" press enter, then type "find . -type d -depth 1 -exec git --git-dir={}/.git --work-tree=$PWD/{} pull origin master \;" and press enter,, automatic check now
    1 point
  17. Yes, you're right. All my kexts are up to date The first WEG 1.3.0 don't work on my config i7 9700K. The developer add new commit for 1.3.0, 5 days ago. With this new WEG 1.3.0, there is no more panic in my system. Take a look https://github.com/acidanthera/WhateverGreen/commit/e5e78bf07dff483fd4bc78d6355a65d08a8960ee
    1 point
  18. You don't need -lilubetaall as boot argument,, Lilu.kext and all plugin are compatible now with Catalina DP2. Just reCompiled all Lilu.kex and plugin
    1 point
  19. Yes that what I found when compiled it. Thanks for the detail.
    1 point
  20. New WEG in attachement If you want to compile by yourself: Download Lilu master from Acidanthera in Github Compile latest Lilu.debug (Xcode) Download Whatevergreen master from Acidanthera in Github Put Lilu.debug in your Whatevergreen folder Compile WEG (before edit scheme to release) in Xcode Sorry about my bad English 1.3.0 (RELEASE).zip
    1 point
  21. thank you Glasgood! this has been the only successful process i had in building my Hackintosh.. super comprehensive and easy to follow! cheers!
    1 point
  22. Can you post the compiled new WEG? Or you can compile yourself? If it's download-and-compile-done process I would be more happy do it myself. Update: It seems quite easy to compile those kexts. Here it is if anyone needs Lilu+WEG.zip
    1 point
  23. Works fine here on Sierra, Mojave and Catalina beta 2. Regards
    1 point
  24. All works fine. Thanks Do you know a solution for Clover Logo missing in Dark Mode
    1 point
  25. Just turned off VT-d on my own hack and updated guide, new BIOS screenshot uploaded. Cheers!
    1 point
  26. I just replaced line 38 in makepkg file (located in ~/src/edk2/Clover/CloverPackage folder) revision=$(svnversion -n | tr -d [:alpha:]) with revision=$(cat ../vers.txt) referring to vers.txt file in /Clover folder (like makeiso script does) and it works! The command svn info | grep Revision | tr -cd [:digit:] unfortunately returns no matches found... fusion71au@fusion71aus-Mac-Pro CloverPackage % svn info | grep Revision | tr -cd [:digit:] zsh: no matches found: [:digit:] @Matgen84, 1. Open the vers.txt file in your ~/src/edk2/Clover folder (after building Clover) and confirm it says the correct version eg 4968. 2. Replace ~/src/edk2/Clover/CloverPackage/makepkg file with attached: makepkg.zip 3. Open terminal and type cd ~/src/edk2/Clover/CloverPackage ./makepkg
    1 point
  27. If I still remember, macOS Catalina now uses ZSH by default. Try using Bash as your Terminal's Shell instead of ZSH, relaunch Terminal then rebuild Clover. Changing Your Default Shell From Terminal Open Terminal and enter the following command: $ chsh -s path Where path is one of shell paths listed in /etc/shells, such as /bin/zsh, /bin/bash, /bin/csh, /bin/dash, /bin/ksh, /bin/sh, or /bin/tcsh. #EDIT: Also consider doing this : cd ~/src/UDK2018 rm -rf Build make -C BaseTools/Source/C
    1 point
  28. Hi again revision number missing after compilation (Catalina Beta 2 / Xcode 11 Beta). Any idea, why
    1 point
  29. Basically now to get Catalina on HFS+ all must be done by copying manually from 2 Apfs installated partitions to a newly created Mbr HFS+ partition. BTW We have to: 1. Create installmedia USB 2. Use Clover 3. Install on Apfs CAT volume 4. Boot again on USB 5. Using terminal, type ditto /Volumes/CAT/ /Volumes/HFS/ ditto /Volumes/CAT\ - \Data/ /Volumes/HFS 6. Boot HFS in single user mode 7. Mount RW /sbin/mount - uw / 8. Recreate cache update_dyld_shared_cache - force kextcache - system-prelinked-kernel 9. Reboot in HFS and finish installation. 10. That's all... Or wait for the tool which CrayBirdy is working on to make all easy and errors proof... See Ya
    1 point
  30. Yeah Chrome + Silverlight works, confirmed thanks! I just prefer Firefox for privacy reasons and hope it gets fixed in the next update, as far as I know this is not specific to hackintoshes, it is a macOS issue with allowing the .dylib to be accessed for widevine
    1 point
  31. try chrome ... for me work netflix with google chrome ... install siverlight first ...
    1 point
  32. @Rodion2010, Could you please compile boot file with default path EFI\OC\OpenCore.efi instead of EFI\Boot\Bootx64.efi? I have Clover installed in more than one hard drive on my legacy desktop and unless I disabled/renamed all other instances of CLOVERX64.efi on all my hard drives (installed as EFI\BOOT\BOOTX64.efi), the CLOVER GUI would load instead of OC... This is mainly a problem if you want OC loading off a hard drive EFI instead of a USB EFI on a legacy BIOS system ---> boot file seems to load OC on USB EFI more reliably. The boot file (when installed to hard drive EFI) looks for \EFI\BOOT\BOOTX64.efi on all other hard drive EFIs, not just the one it is actually on. Also requesting if you can supply an OC boot file based on boot7 instead of boot6 (because on some legacy BIOS systems, boot7 significantly reduces boot time). Thanks Edit @RodionS has already compiled a number of different duet boot files for legacy BIOS systems in the Applelife forum - link post#176. His boot_BIOS_BlockIO solves the problem I described above
    1 point
  33. So far the issues did not reproduce for us, but we probably need to be trying harder. Thing is, Windows and Linux may store preferences somewhere, and after being configured with e.g. Apple vendor during boot or installation, some preferences may be irreversible. My opinion is that neither brightness slider, nor shutdown issues can appear when everything is off. In my opinion, disable everything you enabled (including custom ACPI, SMBIOS, device properties, absolutely everything), and try checking Windows and Linux. — If the bug persists, try loading from BIOS bypassing OpenCore (not Clover please, use BIOS). I believe it will remain here, if it disappears, upload full OC folder, we will try to reinspect. — If the bug disappears, find the offending preference. Ensure that you carefully and consistently test the configuration. Also it may be reasonable to retest with your and fresh Linux installation.
    1 point
  34. Yes, that's most reasonable. Having something like Acidanthera iMac15,1 (Automatic & SpoofVendor) is the recommended way to setup SMBIOS tables.
    1 point
  35. @Andres ZeroCross, you have Apple in your SMBIOS, thus you have SMC loaded. See: https://github.com/torvalds/linux/blob/9331b6740f86163908de69f4008e434fe0c27691/drivers/hwmon/applesmc.c#L1238-L1264 This is explicitly prohibited by docs. Rest: ACPI Quirks are documented in docs and given in samples. Those that are not implemented are to be written yourselves. Most likely you do not need them in the first place. And yes, it is just not for you if you cannot read, sorry about it.
    1 point
  36. Thanks @Matgen84, I'm going to try that... Cheers
    1 point
  37. You have install macOS Catalina Beta 1 ? I hope because its work only on Beta1 For Beta 2 its here ➜ Catalina Beta 2
    1 point
  38. Hackintool v2.6.2 Released - Added Bluetooth to Info->Misc
    1 point
  39. Hi @notiflux I appreciate and applaud your time and commitment developing the OpenCore Configurator, it looks good! but, I tried using your application attached here on your post but it randomly quits unexpectedly. Do you have an updated version ? I have just discovered your your latest version alpha18 . All good! thanks.
    1 point
  40. We have the Market Place for these kinds of posts. I guess you can use it to sell or buy things but please read these rules before posting anything in that section: 1. New rule, please read. 2. Important! How to use The Marketplace! Besides the upload feature is fixed now and you can post your picture in the first post if you like to update them.
    1 point
  41. SunKi's patches are now obsolete. It is more likely to use vit9696's patch, that disables behaviour of enabling ALPM where it is unneeded. Find --> 40600200 Replace --> 00000000 AppleAHCIPort <dict> <key>#MatchOS</key> <string>10.13.x</string> <key>Comment</key> <string>ALPM IO Error AppleAHCIPort</string> <key>Disabled</key> <false/> <key>Find</key> <data> QGACAA== </data> <key>Name</key> <string>AppleAHCIPort</string> <key>Replace</key> <data> AAAAAA== </data> </dict>
    1 point
  42. So you want to buy/sell/trade something here in The Marketplace? Great! Here are a few guidelines to follow... - Start the title of you thread with one of the following tags: [Deal] = You've found an amazing deal to share (We really like these!) [sell] = Something you're selling [buy] = Something you want to buy [Trade] = Something you want to trade [eBay] = Item for sale by author or found on eBay [Hire] = You want to hire someone to do some work (note: paid support is not in the spirit of the OSx86 project and will be removed) - Be very clear about what you're selling. This means including all the important information, pictures, etc. - If you're interested in buying something, PM the seller. Don't post "I want this!!!" in the thread. Just PM the seller. - After an item is sold, the seller must make a note of it in the actual thread with a big SOLD marking in the thread. PM a mod to have them add it to the thread title. - That's it! The OSx86 Project just provides this forum as a means for you to sell or get cool Mac stuff. We are not in charge of sales, and we can't ensure the safety of your purchase. If there is a problem with a sale, let us know and we'll see what we can do. If we catch you selling things without actually sending them (or buying without paying), disciplinary actions will be taken. We don't anticipate this happening, though, so just use common sense and you'll be fine! -Mashugly Last updated 02/08/06
    1 point
  43. Just to remind that this very wise guideline seems to have been forgotten by some people.
    1 point
×
×
  • Create New...