Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by SwithDrawn

  1. SwithDrawn

    iMacPro SMBIOS and new horizens

    I switched over from MacPro6,1 to iMacPro1,1 on my 10.13.4 build and it is working great so far. I got the black screen issue but removing NvidiaGraphicsFixup/Lilu solved it -- it's nice these are no longer needed! I didn't have to futz with PlatformSupport.plist either, it worked OOTB (possibly due to the beta build). Just had to remote in to get around the black screen and remove those kexts. Also lost my USB2 ports. Updating USBInjectAll to the latest fixed that. I'm not noticing any video lag (156 drivers) it actually SEEMS snappier as far as UI animation. Geekbench results were all a little lower than before, though. Most importantly... unlock with Apple Watch works now! Not sure if due to the new smbios itself, or something to do with my wifi/bt card which seems to work more consistently on this smbios.
  2. Updated from the App Store without any issue and running WebDriver-387. All looks good - not seeing that preview/quicklook bug either. Has anyone else noticed slightly improved FPS when using HiDPI scaling? Metal score went up a bit (226444 to 228104) from 10.13.3. Premiere Pro UI feels faster while running my 3840x2160 display @ 2560 x 1440 HiDPI.
  3. SwithDrawn

    [Pre-Release] MacOS High Sierra 10.13.2

    OpenGL: 57.29 fps CPU: 1348cb I've never run Cinebench so I have no reference for comparison. However Geekbench results are similar to 10.13.0 with CUDA dropping slightly. My stats are here: https://browser.geekbench.com/user/143656
  4. SwithDrawn

    [Pre-Release] MacOS High Sierra 10.13.2

    Build 17C85a (beta 6) working well. I started with a working 13.2.1 and had to boot with -liluoff to avoid kernel panic once the install process began, but once it installed simply updating Lilu to 1.2.1 fixed the KP. Used chris1111's Nvidia Payload Packager on WebDriver-378., have not run benchmarks but the 1080 Ti seems to be just fine.,,
  5. Thanks to everyone here for the shares -- finally got my old X9DR3-F upgraded from Sierra. I'm using x.di's config minus the included ssdt (got a kp related to P-States). I also had to use SunKi's fix for ICH10 in order to get passed the "still waiting for root device" with garbled screen & stop sign. I was able to boot High Sierra from a usb drive but got this error with SATA. Everything working great so far.
  6. Working with my EVGA 1080 Ti Founders Edition It's also serving as a 'helper' card for my Rx 480 (waiting on a new monitor to arrive -- the 1080 doesn't have DVI so I can't switch over completely). Tested an export in Adobe Premiere with CUDA and it seemed to go well. Used AGDPfix with Mac Pro 6,1. I'm having trouble getting the nvda_drv=1 setting to stick though, it looks like I have to manually enable it on every boot. Clover boot options in the config don't work -- it just loads the Apple driver. Is anyone else having that issue?
  7. SwithDrawn

    NVIDIA - new beta Pascal drivers

    So... does anyone want to buy the two Rx 480s I just purchased? LOL. Anxiously awaiting stability reports from the beta drivers!
  8. SwithDrawn

    AMD Polaris IDs on Sierra / High Sierra

    Good find, but what was your Luxmark score before the change? 14k is about consistent with one of my 480 8GB cards on Luxball. I added AMDBaffinGraphicsAccelerator to AppleMGPUPowerControl but didn't see any difference. Actually went down by 100, lol.
  9. SwithDrawn

    AMD Polaris IDs on Sierra / High Sierra

    I have the Asus Rx 480 Dual-Fan 8GBs (I believe they are non reference). With regards to flashing, here's the original post (though it looks like you've already seen it lol). His instructions are a little vague, I used ATIFlash to back up the original bios, modified it like in his video and reflashed. That prevented the card from posting. Obviously do this at your own risk. It wasn't clear to me why he was using a downloaded BIOS instead of the original extracted one, which worked fine for me -- probably less of a big deal if you have a reference card. I wasn't able to boot into Windows without a helper card until I installed the Crimson drivers, which cleared Error 43 in the Device Manager. After that, it booted up on the 480s just like OSX (no Windows loading/logo but video turns on when the login screen appears).
  10. SwithDrawn

    AMD Polaris IDs on Sierra / High Sierra

    A huge thanks to everyone working on this -- was able to get my two Asus Dual-Fan RX480 8G's working on 10.12.3! 1) Started with a single 480 and Nvidia GT710 as a helper card (I have a Matrox IGPU so it's no good). For some reason the clover injection methods weren't working for me, I ended up editing info.plist in AMDRadeonX4100.kext, changing 0x67FF1002 to 0x67DF1002. That gave me acceleration on the 480, and I applied the CU patch to unlock all 36 compute units. I still needed the GT710 to boot. I tried putting in the second 480 but wasn't able to get a boot even with the GT710 helper card -- the setup only worked with a single 480 + helper card. 2) I modified the 480's vbios so I wouldn't need the GT710 (thanks to Rhys216's method). This worked fine, I hoped this would allow me to insert the second 480 without needing to mod its bios but this wasn't the case. I couldn't get OS X to boot up with the unmodded 480 alongside the modded 480 even with the GT710 helper card still in the case. 3) I modded the second 480's vbios and presto - both cards working in OS X and I don't need the GT710. Edit: for those interested in using the modded bios 480's in Windows, I had to use Crimson 16.9.1 as recent drivers check the bios signature and I got Error 43 in the Device Manager. 4) With just the two 480's and no post/bios/bootloader showing up, I have two config.plist files - one specifies the MacOS disk as default and the other selects the Windows disk. I switch them out depending on which OS I want to boot up. I used this guide to mount the clover EFI partition in Windows. My Luxmark scores about doubled from the single 480. That being said, even on just one 480 Adobe Premiere is very unstable with OpenCL but I can use Metal API for rendering and it seems solid. My test scene with Metal API trounced the same scene on Windows with OpenCL, and they were both way better than my previous setup (two R9 280s). Edit: I've found that removing the extra CU patch (so CUs go from 36 to 16) improves my OpenCL stability in Premiere.
  11. Strange issues with 346.03.05f02 on 10.11.3 (346.03.05f01 works perfectly). I get black screen instead of login screen. When I connect via remote desktop, suddenly the display becomes active (weird!). Yes, it's using the web driver. I have a GTX 980 with the display on the DVI connector. Once logged in after activating the screen via remote desktop, the UI hangs every couple of seconds and makes it unusable. I downgraded to 346.03.05f01 and it's fine again.
  12. For what it's worth, I was never able to get a USB installer for Yosemite to boot on my Supermicro X9DR3-F, always getting stuck at bluetooth controller or a black screen no matter what flags are used. I have to install the OS from my Macbook to an SSD in a USB dock, install Clover or Chameleon, and then put the SSD in my hack. At this point I can usually remote desktop in to install the nVidia web driver and then it's good to go. Welcome to the Supermicro server board world of hurt
  13. On 10.11.1, most of the time, I don't have working internet or USB3 (both the NIC and usb3 are PCIe cards). Occasionally, about every 4th or 5th boot, they will work. Even when it's not working, the NIC is detected under System Profiler and shows up as "Connected" under the Preferences, but I can't ping any addresses, even my router. I have tried flushing the cache. Same goes for the USB3 - hardware shows up but is not functional. I've had this problem going from Mavericks to Yosemite but fixed it by installing old versions of the following kexts: AppleACPIPlatform.kext (version 2.0) IOACPIFamily.kext (version 1.4) IOPCIFamily.kext (version 2.8) IOUSBFamily.kext (version 675.4.0) I have not been able to upgrade past 10.10.3 with these kexts due to dependencies changing, etc. I was hoping a clean 10.11.1 would just fix everything (naive, I know). The situation is the same with both Clover and Chameleon installations, and I've tried several smbios's (3,1 and 5,1, iMac14,2). I have one other PCIe card - my 980 GTX, which works 100 percent of the time. My mobo (see signature) is a server board so I'm sure this problem is due to some strangeness related to how PCIe is set up on my board. I just don't know where to look or what to do to fix the problem. I thought about adding the cards to my DSDT but since they are always detected I'm not sure that would make a difference? I can also use IORegistryExplorer but don't really know what I'm looking for. Any guidance or suggestions are appreciated!
  14. Does your adapter connect instantly on boot, or does it take 1-2 minutes to show as connected/get an IP? Can you ping your router? I have a similar issue with a Marvell 88E8053 pcie card after installing Yosemite (a clean install with chameleon). It takes 1-2 minutes for the Ethernet Adapter to connect on startup (in 10.9.2 this is instant). After that, it shows connected, but there's no internet access. I can ping my router but not websites. This card should be natively supported and works fine in 10.9.2. I have EthernetBuiltIn=Yes in my boot.plist and even tried injecting the device properties. I've also tried deleting the connection in the preferences window and deleting the NetworkInterfaces.plist in the /Library/Preferences/SystemConfiguration/ folder. I've also tried copying IONetworkingFamily.kext from 10.9.2 with the same result. I don't know what's changed other than IONetworkingFamily since Mavericks that would be causing this.
  15. Just wanted to say that creating a UUID via uuidgen as described in the linked thread and putting it into org.chameleon.Boot.plist as the SystemID string solved this problem for me on 10.9.1, Chameleon 2.2 r2281.
  16. SwithDrawn


    It's just sending - I have no problems downloading, even a large queue of files over FTP. What's strange to me is that if I I'm on another local box, remote connect to my the i350, and then pull files off of the i350 box, it will work fine. But if I try to drag files in Finder while on the i350 to another local machine, it will fail.
  17. SwithDrawn


    Thanks so much for your work. It's working nicely except for some uploading issues... I'm running 4.1.2 but am having trouble uploading files through FTP and also on my local network (AFP). For FTP, I can transfer one or two files, but with a large amount queued in Filezilla (set to do multiple transfers at once), it hangs fairly quickly and a reboot is required. For AFP, I can remotely connect to the machine and pull the file FROM my hackintosh, but not the other way around - Finder hangs and a reboot is required. I would love to get it working because it seems very close to being fully functional- just let me know what you need for diagnostic purposes and I can provide it. Running a supermicro X9DR3F with i350 chipset, Lion 10.7.4.
  18. [solved - see post 8] Update 6.1.10: Original Post -------------------------------- I've installed Snow Leopard (10.6.2) on my eight core xeon system. As with Leopard, everything went pretty smoothly. It works 100 percent, except for the fact that unless I repair permissions immediately after booting, a multi-language shutdown screen will appear invariably after 5-10 minutes. The Event Log shows nothing useful. However, the repair permissions always repairs the same file, IOATAFamily.kext/Contents/PlugIns/AppleIntelPIIXATA.kext: Has anyone ran into this? It's somewhat annoying to have to spend four minutes each boot repairing permissions, and sometimes it crashes before the repair finishes and I have to start over. My system is as follows: Dual Quad Zeon E5405 Harpertown Procs (8 Cores) Intel 5000X Northbridge and ESB2 Southbridge EVGA Geforce 9800GTX 8GB Buffered ECC Ram Creative Audigy 2 ZS 10.6.2 with Chameleon.
  19. This has been solved for those interested - it turns out to be related to the graphics card. I had suspected hardware because (for a time) similar symptoms were appearing in Windows as well. The 9800GTX died recently (artifacting, freezes in both Win and OSX). It was replaced with a GTX260. Problem solved - no more having to repair permissions on each boot. I have NO IDEA why repairing permissions would have fixed a hardware incongruity with the video card.
  20. SwithDrawn

    Snow Leopard Graphics Update 1.0

    Going from 10.6.3 to 10.6.4 with the Graphics Update improved FPS scores in Open GL Extension Viewer by ~20 fps for each test. However, there was a noticeable slowdown in the responsiveness of Finder, playback of video in VLC, as well as viewport interaction in Maya (2011 Hotfix2). I reverted to 10.6.3 and everything is back to normal. I run a Geforce 9800GTX 512. This update appears to fix the Flicker of Death that plagues some users of 10.6.4 and Adobe/Autodesk products (see: http://www.youtube.com/watch?v=Uoo-B3PeyBc).
  21. I'm bringing this back from the dead because I still have this problem: Kernel panics 5-10 minutes after each boot unless I run a disk permissions repair. Sometimes it panics while the permissions repair is in progress (always at 70%). The system will lock and the harddrive audibly stops accessing - sometimes it panics, sometimes it recovers. The panics are either pmap_flush_tlbs() timeout: "cpu(s) failing to respond to interrupts" as described above OR "Spinlock acquisition timed out". The panics are not related to anything in the permissions repair log. For awhile the log was empty, it repaired no files but it would still panic. I've done multiple clean installs using multiple harddrives. I've also tried using both 32 and 64 bit modes for Snow Leopard. I read a thread about the spinlock timeout problem. It seems setting a boot-arg that effectively sets the timeout to a really high number might solve this. The boot-arg is slto_us=0xffffffff. I put this in my com.apple.boot.plist under Kernel Flags but that caused a panic while booting - I'm not sure if this is the correct way to set this boot-arg. Any ideas?? Current thought is it might be AHCI or motherboard related... I will test this next. I'm on 10.6.3 with Chameleon, using EvOreboot, myHack's IOATAFamily.kext, IONetworkingFamily.kext, and NullCPUPOwerManagement.kext. System: Dual Quad Zeon E5405 Harpertown Procs (8 Cores) Intel 5000X Northbridge and ESB2 Southbridge EVGA Geforce 9800GTX 8GB Buffered ECC Ram Creative Audigy 2 ZS
  22. SwithDrawn

    Dell Studio 15: Help Please

    If you want a script to run on startup for number 3, just copy it into TextEdit and save it as something like myscript.command. Chmod the file and make sure it runs in terminal. You can then open preferences, go to Accounts, click on your account and go to "Login Items" and drag the script into the window, now it will run on startup. However, because it's sudo you'll still have to enter a password. At least it's less typing
  23. I got the log. Wow, I didn't know booting verbosely would enable outputting logs after boot. Learn something new everyday... Here's the log: Second crash log, very similar message: All googling suggests faulty hardware, which I doubt in my case because of the fact that a permissions repair somehow solves everything.
  24. You were right, they weren't linked correctly. I copied the files from the installation dvd and repair permissions doesn't complain about it anymore. HOWEVER, the freezing problem still remains, I guess those files had nothing to do with it. I noticed it always freezes at 70 percent. It's definitely doing something.
  25. This issue is getting worse. It doesn't make it through the permissions repairs about half of the time now. What's curious is that if you run the repair again, after it's finished, it repairs the same files with the same messages - "should be lrwxr-xr-x , they are -rwxr-xr-x". I've tried manually chmoding these files at startup instead of running the repair, it makes no difference - no matter what, it always corrects those particular permissions. I think just the *act* of running the repair is, for some reason, averting the crashes. Are there different levels of verbosity for permissions repair? Is it doing something here behind the scenes that's fixing everything?