2006/2007 Mac Pro (1,1/2,1) and OS X El Capitan

[lysergilie]

PlatformSupport.plist files tend to be referenced when installing things.

Figured it's of more concern to the (modified) installer than the OS, will add the 1,1 to PlatformSupport.plist anyway, who knows maybe it helps something sometime. Would've been great if that complements the '1,1' to the EC 'About this Mac' window, but who cares.

Thank you so much for your intricate write-ups rthpjm, learned so much from them already. Stellar performance. +1

 

[Argyboy]

Just wanted to wish everyone here that loves these old Macs a happy Christmas, and especially rthpjm. An unbelievably helpful person! Best wishes!

 

[rthpjm]

Figured it's of more concern to the (modified) installer than the OS, will add the 1,1 to PlatformSupport.plist anyway, who knows maybe it helps something sometime. Would've been great if that complements the '1,1' to the EC 'About this Mac' window, but who cares.

Thank you so much for your intricate write-ups rthpjm, learned so much from them already. Stellar performance. +1

Just wanted to wish everyone here that loves these old Macs a happy Christmas, and especially rthpjm. An unbelievably helpful person! Best wishes!

Thank you for your kind words @lysergilie and @Argyboy

Merry Christmas too.
Here's hoping for a safe and peaceful New Year....

 

[maruteru]

Just wanted to wish everyone here that loves these old Macs a happy Christmas, and especially rthpjm. ... Best wishes!

I would also like to wish everybody a Merry Christmas and a peaceful holiday season for you and your families.

Thank you so much for your intricate write-ups rthpjm, learned so much from them already. Stellar performance. +1

and especially rthpjm. An unbelievably helpful person!

I absolutely agree. @rthpjm, thank you very much for all your help and the thorough explanations. It was a pleasure reading them and they answered many longstanding questions. You are a terrific teacher !

@flygbuss, thank you very much as well. I really appreciate your help in getting El Capitan running on my good old Mac Pro.

The good news is, that I finally got Mac OS X 10.11.6 up and running on my Mac Pro 1,1 , booting and logging in work nicely. Before I had not been able to get it to boot into El Capitan. It turns out that I had simply made a stupid mistake when copying the modified boot.efi file in the terminal... I had forgotten to change the paths from /System/Library/CoreServices and /usr/standalone/i386 to the corresponding ones on the El Capitan volume. And I had not checked the file size of the efi files after copying, even though somebody had suggested to do so in this thread. Funny thing is, I had used the correct paths in the first installation. I guess, that's what I get from working on the computer all night long.

I would like to point out that @rthpjm's explanations guided me in the right direction.

So far I haven't gotten any Security Updates installed. I disabled the automatic Apple Updates, to be on the safe side. I would like to install up to and including SU 2017-005. Is it sufficient to install this particular one, similarly to a combo update? Or do I have to install all the earlier ones before installing SU 2017-005?

 

[rthpjm]

So far I haven't gotten any Security Updates installed. I disabled the automatic Apple Updates, to be on the safe side. I would like to install up to and including SU 2017-005. Is it sufficient to install this particular one, similarly to a combo update? Or do I have to install all the earlier ones before installing SU 2017-005?

The Security Updates tend to be cumulative. Get your machine to 10.11.6, then use Sec Update 2017-005 from the Apple Support downloads and you should be good to go...

 

[lysergilie]

Just because I noticed ... SecUpd2017-004.dmg is more than 200 MB bigger than SecUpd2017-005.dmg. Compared packages and all the files of 001 are also in 005, so rthpjm is probably right. As always. Fooled again!

Merry Christmas fam.

 

[flygbuss]

Merry Christmas and happy holidays, guys. Let's hope for peaceful 2019!

 

[rthpjm]

To the best of my knowledge, no you do not need to bless the Recovery volume. Starting up into the Recovery HD is an edge case. I believe it is hardcoded in the EFI firmware (although I have no definitive knowledge). The Recovery HD is not “normally” visible to the “usual” boot sequence.

I decided to double-check my statement above. As it turns out, the Recovery HD does indeed appear to be "blessed". For reference, here's how to check...

1. Find the disk id of your Recovery HD using diskutil

diskutil list

This will list all your partitions, typically your Recovery HD partition will be "slice 3" of your boot "disk 0", but there there will be a Recovery HD associated with each Mac OS X partition.
For reference, my list is...

/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS Untitled1               2.0 TB     disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                  Apple_HFS Games                   1.5 TB     disk1s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
   4:       Microsoft Basic Data Windows10               499.9 GB   disk1s4
/dev/disk2 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS macos10.6               800.1 GB   disk2s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk2s3
   4:                  Apple_HFS macos10.7               799.0 GB   disk2s4
   5:                 Apple_Boot Recovery HD             650.0 MB   disk2s5
   6:                  Apple_HFS install10.6             199.9 GB   disk2s6
   7:                  Apple_HFS test10.11               199.1 GB   disk2s7
/dev/disk3 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *4.0 TB     disk3
   1:                        EFI EFI                     209.7 MB   disk3s1
   2:                  Apple_HFS Macintosh HD            4.0 TB     disk3s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk3s3

You can use the bless command to find out if the partition is blessed. However you will need to mount the partition first because bless expects it to be mounted...
In my example, I will mount the Recovery HD associated with my macos10.6 partition (change the numbering to suit your system)

diskutil mount disk2s3

Now you can get the bless info...

bless --info /Volumes/Recovery\ HD/

The output should look similar to this...

finderinfo[0]:     39 => Blessed System Folder is /Volumes/Recovery HD/com.apple.recovery.boot
finderinfo[1]:     41 => Blessed System File is /Volumes/Recovery HD/com.apple.recovery.boot/boot.efi
finderinfo[2]:      0 => Open-folder linked list empty
finderinfo[3]:     39 => Alternate OS blessed file/folder is /Volumes/Recovery HD/com.apple.recovery.boot
finderinfo[4]:      0 => Unused field unset
finderinfo[5]:     39 => OS X blessed folder is /Volumes/Recovery HD/com.apple.recovery.boot
64-bit VSDB volume id:  0x8AB93558F5A09760

if you compare that to the typical bless command of "bless --folder /some/path/to/a/folder --file /some/path/to/a/folder/boot.efi"
you can see that finderinfo[0] is the path to the folder, finderinfo[1] is the path to the boot.efi file.

If your system is not showing these, then you can run the bless command to set it.
Assuming the Recovery HD is mounted, and that it has the correct files and folders...

sudo bless --folder /Volumes/Recovery\ HD/com.apple.recovery.boot --file /Volumes/Recovery\ HD/com.apple.recovery.boot/boot.efi

(You will need to authenticate the sudo with your password)

You can check the effect...

bless --info /Volumes/Recovery\ HD/

Now unmount the Recovery HD

diskutil unmount /Volumes/Recovery\ HD/

Caveats:

• I have used "escaped spaces" in my path, where there is a space preceed it with a back-slash. /Volumes/Recovery\ HD/.
  • The alternative is to enclose a path in quotation marks. This method does not require back-slash. "/Volumes/Recovery HD/", or '/Volumes/Recovery HD/'
• The boot.efi file that resides at "/Volumes/Recovery HD/com.apple.recovery.boot/boot.efi" is a Pike version.

Merry Christmas everyone...

 

[godzfire]

Hello @godzfire

Let me know if you want to use CCC as @jbarley suggests above, or if you’d like to work through the manual steps yourself. I’m happy to write the steps...

Hello. But wouldn't CCC create the Recovery Drive with a non-usable boot.efi?

 

[flygbuss]

Hello. But wouldn't CCC create the Recovery Drive with a non-usable boot.efi?

Yes. You’d still have to mount the created recovery portion via terminal and replace the boot.efi inside.

 

[godzfire]

 

[overshoot]

Hi,

I am trying to use your installer package to install El Capitan onto an XServe 1,1
I am using the script from my Lion installation onto the XServe.
The machine has 2 drives, 1 with Lion, 1 with the supposed El Capitan install.

I have to mention I have edited your script to add the XServe model and board ID to platformsupport.plist...

When using your script, I am targeting the El Capitan (Macintosh HD in my case) drive and rebooting from it.
No errors until the end when it asks to reboot
Once it boots into the El Capitan installer, it fails telling that El Capitan is already installed on this Mac (it's obviously not)

Here is the partition list from diskutil command where Macintosh HD is supposed to be El Capitan:

Phukets-Xserveikify3.1 phuketmymac$ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh HD 499.8 GB disk0s2
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI 209.7 MB disk1s1
2: Apple_HFS Lion 999.3 GB disk1s2
3: Apple_Boot Recovery HD 650.0 MB disk1s3

Any help would be greatly appreciated.
Thanks!

 

[rthpjm]

Hi,

I am trying to use your installer package to install El Capitan onto an XServe 1,1
I am using the script from my Lion installation onto the XServe.
The machine has 2 drives, 1 with Lion, 1 with the supposed El Capitan install.

I have to mention I have edited your script to add the XServe model and board ID to platformsupport.plist...

When using your script, I am targeting the El Capitan (Macintosh HD in my case) drive and rebooting from it.
No errors until the end when it asks to reboot
Once it boots into the El Capitan installer, it fails telling that El Capitan is already installed on this Mac (it's obviously not)

Here is the partition list from diskutil command where Macintosh HD is supposed to be El Capitan:

Phukets-Xserveikify3.1 phuketmymac$ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh HD 499.8 GB disk0s2
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI 209.7 MB disk1s1
2: Apple_HFS Lion 999.3 GB disk1s2
3: Apple_Boot Recovery HD 650.0 MB disk1s3

Any help would be greatly appreciated.
Thanks!

Hello @overshoot

Firstly, I have to say that the Pikify tools have not been tested on an Xserve. I’ve never owned one, sorry.

From memory, other members have managed to get Xserves running. You might need to manually fix things though. Fundamental, the MacPros just need assistance to get past the boot sequence. Once the EFI/boot hands over to the kernel/MacOS, El Capitan runs great.

With Mountain Lion (10.8) Apple stopped shipping the secondary EFI-boot file with 32-bit-EFI code, they began shipping 64-bit-EFI only boot.efi files. (EFI has an intermediate binary format called EFI Byte Code, often referred to as EBC. EFI implemtations are usually required to support an EBC interpreter within the basic firmware version. EBC is neither 32-bit, nor 64-bit, therefore it is supported by any underlying EFI firmware implementations). Apple (as well as other manufacturers) now ship only 64-bit-EFI code (technology progresses!). That’s why fundamentally “we only have to replace the boot.efi files” on our MacPros with the community-modified boot.efi file first produced by user @tiamo, and then picked up and extended by user @pikeralpha.

Let’s walk through the sequence then, to see if it will work with your Xserve...

1. You need to get the El Capitan installer to run on your hardware. There are two approaches here. You could...
   1. Use my Pikify tool (script or app) to build a pre-modified Installer, OR
   2. Connect your Xserve HDD to a supported Mac (Target Disk mode, or USB caddie, or directly)

If you use Pikify.
You say that you have added the Xserve board-ID into the script. Pikify should write the modified installer to your selected drive. You must now boot from the modified installer location (OS X Install Data).

Check the modified installer is on your hard disk (whilst booted from Lion)

ls “/Volumes/Macintosh HD”

Notes:
I’ve used @overshoot’s path name, change to suit your installation...
I’ve enclosed the path inside quotation marks because it contains a space. The alternative is to escape the space with a backslash

ls /Volumes/Macintosh\ HD

Look for the folder named OS X Install Data. You could also check that the folder contains some data

ls “/Volumes/Macintosh HD/OS X Install Data”

It should contain...

InstallESD.dmg
PlatformSupport.plist
boot.efi
com.apple.Boot.plist
prelinkedkernel

Now check to see if the location is correctly blessed

bless --info “/Volumes/Macintosh HD”

This should point to the boot.efi file at /Volumes/Macintosh HD/OS X Install Data
If not fix it as above...

You can check which disk the system is set to boot from

nvram efi-boot-device

On your system that should refer to disk0, probably disk0s2

At this point you should be able to reboot.
Your system should boot from disk0 (Macintosh HD), using /OS X Install Data/com.apple.Boot.plist

If it boots to the Installer, great. I have occasionally found the Installer won't run, in which case try to reset the PRAM (links to instructions in my signature). If you do this you may need to hold the ALT key down to enter the Boot Disk Selector and choose Macintosh HD. Sometimes there are residual PRAM values that make the Installer think that El Capitan is already installed.

If you don't boot into the Installer after the PRAM reset, then boot into Lion and bless the OS X Install Data folder again

bless --folder “/Volumes/Macintosh HD/OS X Install Data” --file “/Volumes/Macintosh HD/OS X Install Data/boot.efi” --options="config=\\OS X Install Data\\com.apple.Boot" --label "(Pike) El Capitan Installer" --setBoot --nextonly

 

[lysergilie]

Almost done guys, I'll need to switch settings on a bluetooth dongle but don't want to download and install the entire Xcode package for the required 2 MB app (if it's even possible to download an older Xcode).

Can anyone with Xcode already set up (preferably v8) hook me up with a 'Bluetooth Explorer.app' that runs on El Capitan, please?

It's in /Developer/Applications/Utilities/Bluetooth/ btw.

Thank you so much, Happy New Year!

 

[grimblegrumble]

Dear
Thanks to your information and the "pikify" method
I managed to restart my "old man".
Everything is fine, as many, however, I do not read / see the usb ports and wifi.
I ask you if you can write me or list, the pages from which I can get useful information, to solve the problem.
I ask you why not being a native speaker nor less able in English I find it hard to find what I need.
I add info on my "old man":
Mac Pro 2006 1.1
osx el capitain 10.11.6 (15G31)
2 x 2 GHz Dual-Core Intel Xeon
32 GB DDR2 FB-DIMM with 667 MHz
ATI Radeon HD 5770 1024 MB

Thank you very much

 

[rthpjm]

Dear
Thanks to your information and the "pikify" method
I managed to restart my "old man".
Everything is fine, as many, however, I do not read / see the usb ports and wifi.
I ask you if you can write me or list, the pages from which I can get useful information, to solve the problem.
I ask you why not being a native speaker nor less able in English I find it hard to find what I need.
I add info on my "old man":
Mac Pro 2006 1.1
osx el capitain 10.11.6 (15G31)
2 x 2 GHz Dual-Core Intel Xeon
32 GB DDR2 FB-DIMM with 667 MHz
ATI Radeon HD 5770 1024 MB

Thank you very much

USB is not an issue for most MacPro users.

You may try an SMC reset, see post #3460

Perhaps a PRAM reset too.

 

[grimblegrumble]

USB is not an issue for most MacPro users.

You may try an SMC reset, see post #3460

Perhaps a PRAM reset too.

thanks for the quick answer, I tried reset pram, but it is restarted by lion partition, I turned off selecting el capitain as a boot disk, it started normally with el cap but still does not read usb devices ..
tomorrow I try with the second method you recommended. Meanwhile, thank you very much

 

[grimblegrumble]

so, I tried reset pram and reset smc, but el cap continues to see neither usb nor wifi.
I noticed a thing: when I reset pram, the second "boing" is of a higher volume (and that's right, I think, the reset worked), but it starts lion.
Restart with el cap and "boing" is with low volume ...
but if I invert the hd, I put on bay 1 el capitain that currently and on bay 2 I could improve the situation? or not?
I did not try to start verbose mode because I could not read the results.
I await your kind feedback
Thank you

 

[jaxparo]

The Pikify App.

Version 1.0 had a bug which took me while to track down.
Version 1.1 would not run correctly on Snow Leopard 10.6. Turns out I was using a method for 10.7 or higher!
Version 1.2 fixes the 10.6 usage
Versions 1.3 through 1.7 weren't released
Version 1.8 contains many fixes and better progress visuals
Version 1.9 contains a small number of fixes, a new feature that detects an existing Data folder giving you the option to re-use it or build a new one, and I finally added a Help Book! If you choose to re-use the existing Data folder, the App will re-bless it to make it bootable again!

The current stable release is version 1.9 (build 148)

The App is not signed, therefore you may need to right-click on the app and select Open the first time you run it. This forces Gatekeeper to allow the app.


The same conditions apply:

• You must have a unmodified copy of the Apple 'Install OS X El Capitan' app in your Applications folder.
  • See https://support.apple.com/en-us/HT206886 if you are having difficulty finding a copy of El Capitan.
• If you are running from a MacPro, you must have 12Gb of RAM or more.

Notes: The app is designed to run from Mac OS X 10.6 Snow Leopard or later;
Tested on:

• 10.6 Snow Leopard
• 10.7 Lion
• 10.11 El Capitan
  • If you are going to use this app from El Capitan, be aware that SIP prevents the bless command from setting the boot partition. There are two workarounds:
    1. Reboot and hold the ALT key down, select the Pike Installer
    2. Reboot into the Recovery HD, turn off SIP, reboot back into El Capitan and run the App again...

USAGE:

It's an app, double-click it (or right-click and choose 'Open' if you get a unsigned/unknown developer warning). The rest should be self-explanatory...

​

The script-based Pikify tools

Version 14 marks a shift in technique. With V14 the installation process is much simpler, becomes a single pass, does not require an intermediate installer volume (USB memory stick), and does not require the use of the EFI boot selector (which should be a great help to those people with graphics cards that do not show boot screens).

NO USB!

Also note: I have tested V14 on Snow Leopard 10.6.8. It will work (even though the video says "Lion 10.7.x or higher" as the starting point.

See https://support.apple.com/en-us/HT206886 if you are having difficulty finding a copy of El Capitan.

12Gb or more of RAM is required

I made a video

To use v14, pass the path to your target disk. Let's say you want to install El Capitan onto the Macintosh HD disk....

sudo ./createpikeinstallmedia /Volumes/Macintosh\ HD
[your password]

============== Previous Versions ===========================

Are now retired....

V14 can build on a USB stick, then you can install from there...

==================== Version 12 ==================================
Version 12 saves the unmodified software in a format that makes it easier to restore. Also adds more checks. The biggest change is that the disk images are now mounted on specific mount points so that my script doesn't conflict with the default mount points.

==================== Version 13 ==================================
Not released

==================== Version 14 ==================================
Version 14 is a major change in strategy. With this version you no longer need an intermediate installation media (USB memory stick). Version 14 emulates the way Apple is currently performing the installation. With version 14 you target the disk you want to install El Capitan onto (not the USB memory stick). New users should use v14. If you encounter any issues, please post an entry on this thread.

One really big advantage to V14 is that it will reboot directly into the installer. This should be a great boon for those people with graphics cards that do NOT show boot screens. There's no more need to guess how to boot into the installer.

The only exception is using El Capitan to install another copy of El Capitan. If SIP is active, then the bless command is not allowed to change the boot device settings (setBoot). This is a security feature and should be applauded, but it means with SIP enabled, you must reboot and manually select the installer...



++++++++++++++++ MD5 ++++++++++++++++++++++++++++++++++++++++++

MD5 (pikify3.1.v14.zip) = e7b1699c8db8335c2331e1e8b247efa8
MD5 (PikifyAppV1-9.zip) = 981af2253c9610f2d13257a4368501c3

[doublepost=1546569026][/doublepost]My MacPro 1,1 updated to 2,1 firmware is using a generic PC Radeon 7750 card that I haven't flashed with Mac firmware because of my lack of PC/Windows to enable the flash. Thus, I don't have an OS X boot screen, my monitors only enable late in the boot process. To make matters worse, the kext which drives my card, AMDRadeonX4000.kext, will scramble the video output unless the Contents/info.plist file is modified under the key AMDVerdeGraphicsAccelerator under the “cail_properties” so that each integer is “1” except for the next-to-last CAIL_DisableUVDPowerGating which is “0”. It's likely other PC video cards have similar video scrambling issues and need their respective model key info.plist patched too. It's really a pain to install fresh El Capitan then have to figure a way to patch AMDRadeonX4000.kext/Contents/info.plist in order to get perfect video. It would be nice if a newer version of Pikify.app could patch these info.plist files so that unmodified PC video cards will not display scrambled upon initial reboot.

 

[Argyboy]

so, I tried reset pram and reset smc, but el cap continues to see neither usb nor wifi.
I noticed a thing: when I reset pram, the second "boing" is of a higher volume (and that's right, I think, the reset worked), but it starts lion.
Restart with el cap and "boing" is with low volume ...
but if I invert the hd, I put on bay 1 el capitain that currently and on bay 2 I could improve the situation? or not?
I did not try to start verbose mode because I could not read the results.
I await your kind feedback
Thank you

Does the USB and WiFi work fine under an older OS like 10.7 Lion? I have El Capitan on my MacPro 1.1 (upgraded to 2.1) and everything works fine.

 

[grimblegrumble]

Does the USB and WiFi work fine under an older OS like 10.7 Lion? I have El Capitan on my MacPro 1.1 (upgraded to 2.1) and everything works fine.

yes on lion everything works fine ... maybe I miss the passage to 2.1, in fact I made no move to 2.1
Is it something I can do now, already with el cap?

 

[lysergilie]

Can anyone with Xcode already set up (preferably v8) hook me up with a 'Bluetooth Explorer.app' that runs on El Capitan, please?

Downloaded Xcode, all good you guys.

I don't think it was even necessary, one can get 'Hardware_IO_Tools_for_Xcode_7.3.dmg' from developer.apple.com - the included 'Bluetooth Explorer 4.4.0' is the last version that will run on El Capitan. Hopefully this info will help someone sometime.

Also: USB and WiFi still work with the original 2006 AirPort Extreme in a Mac Pro 1,1 - the card reads "IOName" = "pci14e4,4328" and "Model No.: BCM94321MC".

 

[Argyboy]

yes on lion everything works fine ... maybe I miss the passage to 2.1, in fact I made no move to 2.1
Is it something I can do now, already with el cap?

You should be able to flash it to 2,1 at any time as it's a machine firmware upgrade, as far as I know, but I'm not the most knowledgeable person here at all. Maybe someone else could shed some light on this?

 

[SuperMatt]

You should be able to flash it to 2,1 at any time as it's a machine firmware upgrade, as far as I know, but I'm not the most knowledgeable person here at all. Maybe someone else could shed some light on this?

There is no need to flash it to 2,1 unless you need to upgrade the processor and/or go up to 64GB of RAM, as far as I know. And be aware, if you flash it, any software that uses the hardware ID for its licensing (MS Office and others) will now see the computer as a new machine and you'll probably have to contact the vendor and explain what happened for them to reactivate the software. The more knowledgable types on here can correct my errors, but I'd say unless you need to upgrade the firmware for a specific reason such as processor or RAM upgrade, there is no benefit to it.

 

[Macschrauber]

so, I tried reset pram and reset smc, but el cap continues to see neither usb nor wifi.
I noticed a thing: when I reset pram, the second "boing" is of a higher volume (and that's right, I think, the reset worked), but it starts lion.
Restart with el cap and "boing" is with low volume ...
but if I invert the hd, I put on bay 1 el capitain that currently and on bay 2 I could improve the situation? or not?
I did not try to start verbose mode because I could not read the results.
I await your kind feedback
Thank you

What Airport Card do you have in the box ? Afair BMC94311 and or BXB6 blocks USB on El Cap Mac Pro 1.1