Jump to content


  • Content Count

  • Joined

  • Last visited

About Quattro74

  • Rank
    InsanelyMac Protégé
  1. I had to back port the 10.11 release drivers in order to get my 390x to work on Yos without the tearing/black screens described here.
  2. Quattro74

    El Capitan 10.11 & R9 290X * 2

    Just did the backport for my powercolor devil 390x works great, used terminal from within the installer. cp -R will preserve the symbilic links, I rm -R'd everything that I replaced after backing them up then did the copy. No patched framebuffer. Using exmoor as that is the only personality I saw in the .plist.
  3. Have you tried copying the pre-built executables? Once I had the right programming env on my 10.9.2 install I was able to just run the sbsign tool after copying it and any .lib files it needs over to the /use/bin and /use/lib directories, respectively. If it is still giving you an error about 10.10 then maybe it won't work on your Mavericks version. Don't try to run the installer and compile your own. Much too hard. It might still fail due to needing some other .libs though. Good luck.
  4. Hey guys, Sorry I've been away from the forum for a bit. If you get an Ubuntu install going you could try and sign the Mac os x binaries from its sbsigntool install. Worth a try I guess, not sure it will work :-) I am running 10.9.2 on rev2 sp2, and it was a struggle to find the correct versions of programming tools that would allow me to run the sbsign on Mac, that is the biggest challenge. I had to download the correct tools from apple's dev site.
  5. Stereo, my tutorial is linked to off of the first post and also back one page, Its really more of an outline and not step by step. The most important thing to get working is the sbsign tool. You will need to read the thread and not the install or readme. You don't need to compile anything you can just copy the pre-compiled binary and .lib files to /use/bin and /use/lib, respectively. You will have to make sure to have the proper programing invironment set up on your Mac before you'll be able to get it to run. Once you can run the sbsigntool from the command line without error you should be fine. Then just continue with my instructions as best you can. :-)
  6. Actually, yes. IF you are willing to try the workaround posted 3 posts above this question.
  7. Wm, You still have no way to access the uefi and install the certificates to your db? If not you won't be able to get to clover regardless where it is installed. That is your main issue. Get the certificates into the db and you can do what you want. Having a working Ubuntu means you can get a working shim-signed and get that to boot OK from where-ever but you can't get past it w/o the clover certs being added.
  8. Hi again WM, If you can boot now off of USB in secure mode it is a secure USB key right? Then maybe all you need is a way to get a secured clover on a USB stick? Sounds to me like you'd have to do this anyway just to create the proper OS X insall USB key. So yeah once that is created installing OS X is the easy part. You may need another computer to help troubleshoot the USB key creation.
  9. WM, Your best bet is to follow the instructions on Surface Pro OSX, android and Windows triple boot thread to get OSX installed and working correctly, which means dis-ableing secure boot for now. When all of those other things are working to your satisfaction then come back here to lock it down. EDIT: or in your case one of the Surface Pro 3 OSX threads ; )
  10. Surface2OSX HD 4400 i5 4300U 8GB 512GB "Look Ma no Dongle" ok.. I'd never actually say something like that to Mom, she worries... Anyhow I had never planned to buy a usb wifi dongle after reading some of the horror stories of getting one to work and still getting app store etc to function properly. Also, I planned on using my iPhone and tether wifi etc. if needed and also use the built in VPN. Also, I was always bothered that we had a perfectly good built in wifi-bluetooth and couldn't really use them, unless you wanted the bluetooth to be always on. Since there is only the one USB port on the Surface Pro it sure would be useful to free it up for other devices. Well I'm sure I'm not the first to do this but its pretty easy to share the built in USB wifi via a Virtual Machine. I used Ubuntu 14.04 and Parallels as my solution since Parallels creates the necessary link that you can configure in the Mac OS Network settings. Ubuntu has the driver for our USB wifi buillt into the kernel, plus the updated firmware addon somewhere, which makes it very stable. Also, Parallels VMs have direct control of anything USB if you give it to them, and you can limit the amount of memory and cpus allocated to the VM in the settings so that the host OS can still function solidly. First you have to download a VM, I went to osboxes.org and grabbed a 64bit ubuntu 14.04 that is designed for VMware. Once I opened it with parallels I was asked to convert it over to the parallels format. Then just use the newly created VM. In the Parallels control center for the new VM make sure there is a network setup, go into its hardware settings and add one if its not already there, you will need to do this before starting up the new VM. Once its created make sure the checkbox for 'connected' is checked and you can use the virtuio or the Intel 'Nic type'. Under Parallels> preferences >Advanced click on Network: 'Change Settings' Under the Host-Only Tab check all the boxes and take note of the start and end addresses and subnet. Under Shared tab deselect all checkboxes. Back to Parallels>Preferences select the Devices menu and see if Bluetooth and Wireless Lan Composite Device is listed, If not see if you can add it and then sellect 'connect it to the active virtual machine'. If it doesn't allow you to do this now It might need to be done after the first VM connection. Now boot up the VM and as its connecting see if you can add the Marvel USB under USB or if the previous step was already successful you should see the Bluetooth and Wireless Lan device listed and connecting under the devices icon on the VM window border. The next part differs with different Ubuntus but basically its time to find the wifi network settings and connect to you wifi router. You may have to deselect and select the USB wifi device connection every now and again but once it connects it is usually pretty stable and will connect immediately whenever its needed and you fire up the VM. you should be able to test the connection within the VM by starting up Firefox to see that you now have internet access from Ubuntu. Also, as an added bonus if you haven't installed the avastar-fw.kext into mac os you may notice that each time you exit the VM and wait a few secs that you will have Bluetooth functioning from within Mac os. So you can basically use this procedure as a virtual 'switch' to turn on BT whenever you'd like and you don't have to leave it on all the time. You may have to install the avastar-fw.kext at least once to provide the 'infrastructure' for this to work tho. Then just delete the kext and run kext utility. Now go into Network settings in Ubuntu and find the 'wired' internet connection, write down the ip address make sure its on and then go into its 'Options' button. Under IPv4 settings tab>Method>select 'Shared to other computers' then save. Open terminal in Ubuntu VM and type ifconfig and the prompt. It should show you the same ip address as in the step above as eth0. Now run the same command at the Mac Terminal. You should see a vnic1 and vnic0, which are the two virtual links that parallels set up for you in the above network setup steps. Notice that one of them will have an IP on the same subnet as the IP from the previous step, in my case it is one number above. Restart VM. Now under Mac's network settings find the Parallels Host-Only virtual link, select under Configure IPv4 as Manually. Then for IP address use the same IP as the one for the vnic1 or vnic0 that was on the same subnet as the ubuntu wired connection, from the above step. For subnet mask: For Router use the original IP from the Ubuntu wired connection. Then go into advanced and add under dns servers and then Save. Then reboot everything and see if you can reconnect and then access the internet not just from Ubuntu Firefox but also from Mac's Safari. If everything is working well you might save the Ubuntu config as a snapshot in Parallels. So you can always rollback to it if there is an issue. You can alter the hardware settings to give the VM as little resources as possible so that you can still use Mac os to a high degree, and there are some mimimal installs of ubuntu floating out there that would take up very little harddisk space. Just make sure they are recent and probably a debian branch of Linux so that their kernels have our built in marvel-avastar driver and firmware pieces. After getting mine to work I then tested appstore imessage facetime icloud and they all work fine, so this is compatible with Rehabman's nullethernet.kext. Thus freeing up the dongle space, cuz who doesn't need a lil extra dongle?
  11. Well done Richard, You managed to get Clover working directly, something I struggled with so I went to use shim. I will eventually get around to trying it this way. : )
  12. Surface2OSX HD 4400 i5 4300U 8GB 512GB So is there currently a group buy of the touch-base drivers going on? to those that have upgraded to Yosemite does it support touch natively? thanks, this seems to be the perfect touch-mac with the sample touch-base drivers.
  13. Surface2OSX 4400 i5 4300U 8GB 512GB Hey, I never could figure out how to get my wierd backlight refresh issue fixed via a custom dsdt. But I did figure out that ours are not the only laptops with this weird issue. To clarify, for me when I first would log in to the Mac OSX I would get default brightness from the last login, but after the very first display sleep or refresh I would then get max brightness. Also, the slider in brightness display settings was't showing up until after this refresh. very annoying to reset each time. So after searching a bit online I discovered the brightnessFix tool. just google it. It auto re-freshes the display and resets the brightness to a desired level after each login. It consists of a BrightnessFix binary that is placed into /usr/bin and a brightnessFix.plist that has the desired level set in it which goes into /System/Library/LaunchAgents, this can then be edited using sudo nano. I did decide to shut off login at each sleep so that I didn't have double login at each boot, but that is just my preference, your security concerns may be different.
  14. Richard, Hello, the script I edited with powershell to install only the DBs is originally named InstallSecureBootWithMsftUefiCertAuthToDB.ps1, so a long name for sure. Yes it is a part of the special tool MS came up with for the Surface Pros 1 & 2. Since you use a Pro 3 you may not need to find the special Tool for UEFI CA, but I like the control it gives us for customization. Keytool only lets you update .cer files to the DB while in setup mode. If your built in UEFI bios lets you add in the DBs separate from the PK, then no problem, otherwise do as I did above and find the tool to add CA to the early Surface Pros. Edit it similar to me then you can use keytool, which I find easier to use. Keytool will only allow adding certs in setup mode which means the system will be in un-secure mode. Once PK is added it will not allow you to add in the .cers to the Db and KEK. Mokmanager may let you add the .cers to MOK and try that as an alternative, you never know it may work for the DBs to have then there instead of in the MS DBs? Then you can lock down everything and see if you have Clover and Black screen. Yes you need to sign the boot.efi with sbsign as the example towards the top of this thread. Also any boot.efi you might have in a recovery partition. Also, sbsign everything .efi under /EFI/Clover and /EFI/Boot as far as shim-signed, make sure it's from a recent version of Ubuntu or equiv. 64 bit version. I used the one from 14.04, I had trouble with an earlier shim I originally found on the internet. The UEFI CA tool from MS also has a savepk.ps1 script which can be edited to save all current DBs and the PK. That is usefull once you have all the cool new certs added and you want to save everything in the combined .bins it creates from the new combined dbs. The original script only saves the current dbx and PK. You can then create a new lockdown.ps1 script that is based on the newly created combined db.bins. When you download the UEFI tool look at the documentation that comes with it and the scripts themselves to determine how to edit them for this type of customization. The new lockdown.ps1 could then have the PK line added back into it once all the newly combined DBs and Kek are created. Greatly simplifying application in the future. I have since updated my machine to Windows 10 and both the upgrade, and a further update overwrote my shim-signed(re-named to bootmgfw.efi) in /EFI/Microsoft/boot. So keep a copy of it handy to move back over to SYSTEM each time.
  15. Certainly Jah, do add it if you'd like.