First thing I'd check is in the sound preferences. See where the sounds are directed to. Internal speaker, audio out, etc.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
2006/2007 Mac Pro (1,1/2,1) and OS X El Capitan
- Thread starter Mr. Zarniwoop
- Start date
-
- Tags
- mac pro 2006 mac pro 2007
- Sort by reaction score
First thing I'd check is in the sound preferences. See where the sounds are directed to. Internal speaker, audio out, etc.
Hi all,
I ran into an issue running MacPro2,1 using El Capitan with Pike R Alpha boot.efi.
On my MacPro2,1 I was running the latest El Capitan version without any particular problem, using an ADSL connection with a download speed of about 16 Mbit/s.
Then I switched to a 1 Gbit/s fiber connection.
The first thing I did was to run a speed test (http://www.speedtest.net). Bummer. Mac crashed. So I turned to a recent MacBook to run the test and everything went fine.
From that time on I noticed that, on the MacPro2,1, as soon as I had "high" bandwidth traffic (say over 30 MByte/s) a crash soon followed (generally under a minute).
Crash reports were various, many of this kind:
panic(cpu 6 caller 0xffffff801cbe7897): slab_nextptr_panic: mcache.bigcl buffer 0xffffff819020d000 in slab 0xffffff81554bb9a8 modified after free at offset 0: 0x6b05020000000d out of range [0xffffff818f32f000-0xffffff819532f000)
Sorry I can't be more precise, but I re-installed OS many times and forgot to keep crash reports.
A strange thing is that local network traffic doesn't lead to crash, only internet traffic. My wild guess is that this difference is due to higher round-trip time, hence higher window size and higher buffer needs.
At first, I suspected a hardware issue, so I ran Apple Hardware Tests (long tests), removed non-Apple extension cards or memory, swapped memory banks and video cards, tried a third party Gigabit Ethernet card, reinstalled OS on a freshly formatted spare disk etc etc but had no success. Whatever the conditions, a week of tests went by but the issue remained.
Then I tried the same tests with a fresh install from OS X 10.10.5 and the issue was gone, re-ran tests with bare 10.11.0 or 10.11.6 and the issue immediately re-appeared.
So I'm back to 10.10 and my MacPro is rock solid again.
I wonder if anyone with a high-speed connection has hit the same issue?
Any clues?
I ran into an issue running MacPro2,1 using El Capitan with Pike R Alpha boot.efi.
On my MacPro2,1 I was running the latest El Capitan version without any particular problem, using an ADSL connection with a download speed of about 16 Mbit/s.
Then I switched to a 1 Gbit/s fiber connection.
The first thing I did was to run a speed test (http://www.speedtest.net). Bummer. Mac crashed. So I turned to a recent MacBook to run the test and everything went fine.
From that time on I noticed that, on the MacPro2,1, as soon as I had "high" bandwidth traffic (say over 30 MByte/s) a crash soon followed (generally under a minute).
Crash reports were various, many of this kind:
panic(cpu 6 caller 0xffffff801cbe7897): slab_nextptr_panic: mcache.bigcl buffer 0xffffff819020d000 in slab 0xffffff81554bb9a8 modified after free at offset 0: 0x6b05020000000d out of range [0xffffff818f32f000-0xffffff819532f000)
Sorry I can't be more precise, but I re-installed OS many times and forgot to keep crash reports.
A strange thing is that local network traffic doesn't lead to crash, only internet traffic. My wild guess is that this difference is due to higher round-trip time, hence higher window size and higher buffer needs.
At first, I suspected a hardware issue, so I ran Apple Hardware Tests (long tests), removed non-Apple extension cards or memory, swapped memory banks and video cards, tried a third party Gigabit Ethernet card, reinstalled OS on a freshly formatted spare disk etc etc but had no success. Whatever the conditions, a week of tests went by but the issue remained.
Then I tried the same tests with a fresh install from OS X 10.10.5 and the issue was gone, re-ran tests with bare 10.11.0 or 10.11.6 and the issue immediately re-appeared.
So I'm back to 10.10 and my MacPro is rock solid again.
I wonder if anyone with a high-speed connection has hit the same issue?
Any clues?
And I think that you're using Speedtest and it sucks because it relies on buggy Flash. Try http://speedof.me or (at least ) http://beta.speedtest.net (Flash-free). And uninstall the Flash plugin. Safari X makes it obsolete.
The panic is probably memory related, the panic line you posted above refers to mcache.bigcl. I haven't looked it up but cache is probably memory cache. Some part of your software attempted to modify that memory location after it has free'd.
That gives us three possibilities from my perspective:
- A software bug. Have you got any third party software installed or is this an OS-only install. Did it start crashing before you installed other software, and/or restored data and apps from a previous system?
- It could be a manifestation of the well known memory issue. El Capitan will panic under certain conditions if you have any 512MB memory cards installed.
- A disk problem. Modern operating systems use disk as temporary swap space. The difference with most modern OSEs is that it's baked in, older systems you could specify and/or control it. If memory is being swapped to disk, and there's a disk problem....
For (1), build to 10.11.6 again as you would normally. Test again, hopefully you can replicate the same issue. Reboot into safe mode (reboot, listen for the chime, hold down the shift key - https://support.apple.com/en-gb/HT201262). This will turn off all non-Apple software and non-Apple kernel extensions. Test again. Hopefully this time things will be stable. In which case you are looking for a non-Apple piece of software which probably has a kernel extension...
You could double-check by building a fresh install (OS-only).
If it's still unstable, check your RAM (2). If you have 512MB RAM sticks in the machine, take them out.
Also, run disk first aid on all you disks and their partitions (3). (You should probably boot from the Recovery partition to do this).
Last edited:
I really did extensive tests...
No 512 MB cards. Memory tested, the long way, thru AHT. Disk tested, 3rd party hardware removed etc.
I've tested on different validated disks, OS-only fresh installation.
Software is OS only, so the bug lies in it, or else in boot.efi, which is the only 3rd party software. The later option is why I posted here...
But it also may be that OS X 10.11 has a bug that is revealed only by the high bandwidth usage and higher round trip time, which appears only on some non-supported configuration, such as a MacPro1,1 or 2,1. Can't blame Apple in this case.
No 512 MB cards. Memory tested, the long way, thru AHT. Disk tested, 3rd party hardware removed etc.
I've tested on different validated disks, OS-only fresh installation.
Software is OS only, so the bug lies in it, or else in boot.efi, which is the only 3rd party software. The later option is why I posted here...
But it also may be that OS X 10.11 has a bug that is revealed only by the high bandwidth usage and higher round trip time, which appears only on some non-supported configuration, such as a MacPro1,1 or 2,1. Can't blame Apple in this case.
This is a good article on mixing/matching Dimms in these machines. Remember the "daughter cards" CAN go bad/flaky also.
http://www.xlr8yourmac.com/tips/Mac_Pro_FBdimm_Pairing.html
Last edited:
Uhm... Lemme understand it correctly... older OS X - it's OK. ElCap+boot.efi equals crash.
I will set up a test bed in a couple of minutes using Ethernet between my Pro and another Mac and will try to replicate the issue (my Mini is running Sierra now, the Pro runs ElCap, obviously, with boot.efi).
Will come back (if my Pro doesn't burn to the ground in the process, that is) soon.
Good idea, but as I stated before, Gbit/s local traffic didn't lead to a crash here. Only Gbit/s internet traffic. That is, crash occurs when internet traffic is above about 30 MB/s, which I didn't met until switching to fiber (BTW, did I tell you that Gb fiber internet rocks?). Anyway, thank you for conducting a test. I'm eager to hear about your results.
Check the MTU settings on your router (I assume you have a new edge router). Try matching the Mac's MTU to that of the router.
MTU is one of those weird settings, if components in your network have radically differing MTU values, it will cause lots of network packet fragmentation (and possibly lots of retransmissions), which in turn requires lots of cache/buffering in memory. The MacPro 1,1 Ethernet interfaces maybe just on the edge. (I assume you are using Ethernet with your MacPro?).
OK, I'm back and got (no) good news:
So apparently my 2,1 Pro with boot.efi and ElCap is able to sustain ~1 gigabit connection... Sadly, I have no way to even dream of +30 megabytes/sec internet traffic 
Regarding MTU, I believe most, if not all, hardware comes with 1500 MTU and unless your router is running jumbo frames (9000) you should not be even aware of the difference.
Code:
Wojteks-Mac-Pro:bin wojtek$ iperf301 -c 192.168.255.2
Connecting to host 192.168.255.2, port 5201
[ 4] local 192.168.255.1 port 50851 connected to 192.168.255.2 port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 113 MBytes 945 Mbits/sec
[ 4] 1.00-2.00 sec 112 MBytes 940 Mbits/sec
[ 4] 2.00-3.00 sec 112 MBytes 939 Mbits/sec
[ 4] 3.00-4.00 sec 112 MBytes 939 Mbits/sec
[ 4] 4.00-5.00 sec 112 MBytes 940 Mbits/sec
[ 4] 5.00-6.00 sec 112 MBytes 939 Mbits/sec
[ 4] 6.00-7.00 sec 112 MBytes 940 Mbits/sec
[ 4] 7.00-8.00 sec 112 MBytes 939 Mbits/sec
[ 4] 8.00-9.00 sec 112 MBytes 940 Mbits/sec
[ 4] 9.00-10.00 sec 112 MBytes 939 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 1.09 GBytes 940 Mbits/sec sender
[ 4] 0.00-10.00 sec 1.09 GBytes 940 Mbits/sec receiverRegarding MTU, I believe most, if not all, hardware comes with 1500 MTU and unless your router is running jumbo frames (9000) you should not be even aware of the difference.
Last edited:
So I finally got a clean El Cap installer app. Been using the rth pjm method, and I got this...
Running Apple's createinstallmedia tool...
Failed to start erase of disk due to error (-9999, 0).
A error occurred erasing the disk.
=================================================================================================================================
==
== ERROR
==
=================================================================================================================================
==
== A problem occurred when creating the install media with Apple's createinstallmedia tool
== The most common issue is that the installer volume could not be unmounted because some other process is using it
== Close all other windows (especially terminal windows) and try again
==
=================================================================================================================================
It seemed to persist even when the only thing open was the terminal window itself (I had only Chrome open the first time I tried it). I thought the volume I was installing to might've gone bad, so I verified and repaired it with Disk Utility. Just to be safe, I repartitioned it to 1 partition, GUID, etc. Any thoughts on what I might be doing wrong? I'm running a 1,1 Mac Pro, flashed to 2,1. Processors upgraded to 2 x quad-core 2.66 Xeons. I pulled the 512 ram so I'm at 12 GB now. Currently on 10.6.8. I'll try upgrading to Lion and doing this again.
Running Apple's createinstallmedia tool...
Failed to start erase of disk due to error (-9999, 0).
A error occurred erasing the disk.
=================================================================================================================================
==
== ERROR
==
=================================================================================================================================
==
== A problem occurred when creating the install media with Apple's createinstallmedia tool
== The most common issue is that the installer volume could not be unmounted because some other process is using it
== Close all other windows (especially terminal windows) and try again
==
=================================================================================================================================
It seemed to persist even when the only thing open was the terminal window itself (I had only Chrome open the first time I tried it). I thought the volume I was installing to might've gone bad, so I verified and repaired it with Disk Utility. Just to be safe, I repartitioned it to 1 partition, GUID, etc. Any thoughts on what I might be doing wrong? I'm running a 1,1 Mac Pro, flashed to 2,1. Processors upgraded to 2 x quad-core 2.66 Xeons. I pulled the 512 ram so I'm at 12 GB now. Currently on 10.6.8. I'll try upgrading to Lion and doing this again.
Can you do three things please?....
Get yourself into a position as if you were ready to run the createpikeinstallmedia script
1. Copy and paste the exact command that you are typing into the terminal (starting ./createpikeinstallmedia)
2. Run the following command in the terminal
Code:
diskutil list3. Type
Code:
pwdThe code I've been using is...
./createpikeinstallmedia /Volumes/Untitled\ 1/
Here are the results from diskutil list...
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk0
1: EFI 209.7 MB disk0s1
2: Apple_RAID_Offline 2.0 TB disk0s2
3: Apple_Boot Boot OSX 134.2 MB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI 209.7 MB disk1s1
2: Apple_HFS ElCapHD 999.3 GB disk1s2
3: Apple_Boot Recovery HD 650.0 MB disk1s3
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk2
1: EFI 209.7 MB disk2s1
2: Apple_HFS SSD 999.9 GB disk2s2
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk3
1: EFI 209.7 MB disk3s1
2: Apple_HFS Media-SoftRAID 2.0 TB disk3s2
/dev/disk4
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *15.6 GB disk4
1: EFI 209.7 MB disk4s1
2: Apple_HFS Untitled 1 15.3 GB disk4s2
Here are the results from pwd...
/Users/d
[doublepost=1474926073][/doublepost]Sorry, I'm unsure how to tag the code so it displays in a code box...
./createpikeinstallmedia /Volumes/Untitled\ 1/
Here are the results from diskutil list...
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk0
1: EFI 209.7 MB disk0s1
2: Apple_RAID_Offline 2.0 TB disk0s2
3: Apple_Boot Boot OSX 134.2 MB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI 209.7 MB disk1s1
2: Apple_HFS ElCapHD 999.3 GB disk1s2
3: Apple_Boot Recovery HD 650.0 MB disk1s3
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk2
1: EFI 209.7 MB disk2s1
2: Apple_HFS SSD 999.9 GB disk2s2
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk3
1: EFI 209.7 MB disk3s1
2: Apple_HFS Media-SoftRAID 2.0 TB disk3s2
/dev/disk4
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *15.6 GB disk4
1: EFI 209.7 MB disk4s1
2: Apple_HFS Untitled 1 15.3 GB disk4s2
Here are the results from pwd...
/Users/d
[doublepost=1474926073][/doublepost]Sorry, I'm unsure how to tag the code so it displays in a code box...
The code entry is performed most easily from the blue-grey menu bar above the text input window. Click on the icon that looks like a plus sign inside a box (between the film strip and disk icons).
OR
type [ CODE ]example code text[ /CODE ] (omitting the spaces between the brackets, I had to put the spaces in so that the interpreter didn't display a code box!)
Okay one more task for you, please
in the terminal please type
Code:
diskutil info /Volumes/Untitled\ 1Yes 940 out of 1000 Mbits/s is max bandwitdh on a GB/s connection. The missing 60 Mb/s are ethernet headers, IP-TCP-UDP control data, then there are checksums etc.
I'm pretty sure my router is not configured for jumbo frames, and neither is my mac.
Sigh. While 10.10 is stable for now, I miss 10.11.
[doublepost=1474927642][/doublepost]@hwojtek:
maybe "Network Link Conditioner.prefPane" from "Hardware IO Tools for Xcode 7.3" available from https://developer.apple.com/download/more/ (developer account required) might help to run such a test by increasing the round trip time.
I used it to limit the bandwidth in 10.11 hoping it would avoid crashes, but it didn't help. Maybe you want to give it a try?
Hello everyone !
Problems :
1: I have the rigth hardware... I installed el capitan using this method :
After the installation, I tried to install le latest drivers of the first version of my Apogee Duet (firewire) which is now discontinued (so no up to date drivers thanks Apple...). I got this error message (see picture) and impossible to start back the session after that (so I need to reinstall Capitan with the previous method and load back my softwares and... with time machine...).
No problem with the installation of a UR22mkII (steinberg USB external soundcard) but again the same session corruption with the installation of the drivers of a RME fireface UFX (firewire external soundcard).
2 : While creating a USB key with pike's El capitan installation :
...
The script will end with ######### DONE PIKIFYING ########### if all goes well
=================================================================================================================================
==
== Warning:
==
=================================================================================================================================
==
== BaseSystem.dmg is already mounted, attempting to detach...
==
=================================================================================================================================
==
== ERROR
==
=================================================================================================================================
==
== BaseSystem.dmg is already mounted, could not detach. Stopping...
==
I tougth about redownloading the El Capitan install app but it just changed for a new OSX and is not on the appstore anymore...
I am in the middle of 2 big mixing contracts. I have backups but I would love to stop loosing my time in endless intallations, partition corruptions and problems with a machine I spent tome and money on...
Thanks for your help guys !
Problems :
1: I have the rigth hardware... I installed el capitan using this method :
No problem with the installation of a UR22mkII (steinberg USB external soundcard) but again the same session corruption with the installation of the drivers of a RME fireface UFX (firewire external soundcard).
2 : While creating a USB key with pike's El capitan installation :
...
The script will end with ######### DONE PIKIFYING ########### if all goes well
=================================================================================================================================
==
== Warning:
==
=================================================================================================================================
==
== BaseSystem.dmg is already mounted, attempting to detach...
==
=================================================================================================================================
==
== ERROR
==
=================================================================================================================================
==
== BaseSystem.dmg is already mounted, could not detach. Stopping...
==
I tougth about redownloading the El Capitan install app but it just changed for a new OSX and is not on the appstore anymore...
I am in the middle of 2 big mixing contracts. I have backups but I would love to stop loosing my time in endless intallations, partition corruptions and problems with a machine I spent tome and money on...
Thanks for your help guys !
Attachments
Ah ha! Thanks for the tip. Here's the result from the diskutil info on the USB key...
Code:
Device Identifier: disk4s2
Device Node: /dev/disk4s2
Part of Whole: disk4
Device / Media Name: Untitled 1
Volume Name: Untitled 1
Escaped with Unicode: Untitled%FF%FE%20%001
Mounted: Yes
Mount Point: /Volumes/Untitled 1
Escaped with Unicode: /Volumes/Untitled%FF%FE%20%001
File System Personality: Journaled HFS+
Type (Bundle): hfs
Name (User Visible): Mac OS Extended (Journaled)
Journal: Journal size 8192 KB at offset 0x74000
Owners: Disabled
Partition Type: Apple_HFS
OS Can Be Installed: Yes
Media Type: Generic
Protocol: USB
SMART Status: Not Supported
Volume UUID: 2D3F3720-3E4D-386B-B9D0-CE7FBDA04C0B
Total Size: 15.3 GB (15266603008 Bytes) (exactly 29817584 512-Byte-Blocks)
Volume Free Space: 15.2 GB (15227949056 Bytes) (exactly 29742088 512-Byte-Blocks)
Device Block Size: 512 Bytes
Read-Only Media: No
Read-Only Volume: No
Ejectable: Yes
Whole: No
Internal: NoI have this prefpane on another computer, will try it tomorrow (CET, it's well past midnight in here).
I am not sure the downloaded version of El Cap in the video will work with The Pikify Script - it seems to be mixing 2 installation methods. How did you install originally? If you downloaded El Cap from the App Store it should still be available to download in your 'purchased' list.
Have you tried other trouble shooting? A complete install may not be necessary.
Okay, so it all looks good. You have a USB attached disk (or memory stick), probably 16GB (slightly less formatted), it's writable (Read-Only No).
I can't see why it is having trouble. So let us try the following:
Perform an eject of the USB volume named 'Untitled 1'. Wait for the volume to eject. Physically unplug the USB device. Count to five "elephants" (or Mississippi's perhaps). Re-insert the USB device. Wait for it to mount onto the desktop.
in a terminal
(I am assuming your copy of the pikify3.1 folder is in your Downloads folder, if not amend the path to suit)
Code:
cd ~/Downloads/pikify3.1
sudo -s
your_password
./createpikeinstallmedia /Volumes/Untitled\ 1Because the previous run of createpikeinstallmedia was successful up to the point of writing it to the USB stick, the mods are already in place. You will be prompted to reset or continue.
Try continue
The problem you had previously was that the Apple command line executable "createinstallmedia" (after which I named my script with the addition of pike!) could not unmount and/or format your USB device. I'm hoping that by ejecting, disconnecting, reconnecting, and mounting the USB device afresh, this will clear whatever was causing the issue.
If it fails again, try opening the Disk Utility from the Applications > Utilities folder, and try to completely reformat your USB device with Disk Utility, then try again...
[doublepost=1474976363][/doublepost]
Hello Lifemaster,
1.
The video you reference is a completely separate entity - I don't think the author has ever been active here on this thread. Some users have reported the method works okay.
Your issue then appears to be an incompatibility with the RME fireface UFX kernel extension (kext). We cannot help you with that (unless someone here knows of an update or a workaround). The only people who can fix the issue will be the supplier/manufacturer of the card.
2.
When trying to use my createpikeinstallmedia tool, the script checks to see if there are Volumes already mounted with names that the script want's to use later. It found that you have a Volume mounted called 'OS X Base System' and it tried to unmount it. For some unknown reason it would not unmount and therefore the script stopped.
Check your system for a volume named 'OS X Base System' and manually unmount it
Also, check your system for a volume named 'OS X Install ESD' and manually unmount it
Then you should be able to run my script.
3.
Open the App Store app, click the Purchased tab. You should find the older OSes listed there (assuming you used the App Store to download a copy previously).
Remember, you must delete (or otherwise remove) all other copies of the 'Install OS X El Capitan' app from your system, otherwise the App Store app won't let you download a fresh copy. (If Spotlight can find an old copy, the App Store will refuse)
Pascal,
here are the results. First, the "Very bad network" profile:
Now for the WiFi profile:
And now a custom profile I created with 1 Gbit bandwidth up/down, but 250 ms delay:
Hope this helps a bit.
here are the results. First, the "Very bad network" profile:
Code:
Wojteks-Mac-Pro:~ wojtek$ iperf301 -c 192.168.255.2
Connecting to host 192.168.255.2, port 5201
[ 4] local 192.168.255.1 port 51549 connected to 192.168.255.2 port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-15.83 sec 256 KBytes 132 Kbits/sec
[ 4] 15.83-15.83 sec 0.00 Bytes 0.00 bits/sec
[ 4] 15.83-15.83 sec 0.00 Bytes 0.00 bits/sec
[ 4] 15.83-15.83 sec 0.00 Bytes 0.00 bits/sec
[ 4] 15.83-15.83 sec 0.00 Bytes 0.00 bits/sec
[ 4] 15.83-15.83 sec 0.00 Bytes 0.00 bits/sec
[ 4] 15.83-15.83 sec 0.00 Bytes 0.00 bits/sec
[ 4] 15.83-15.83 sec 0.00 Bytes 0.00 bits/sec
[ 4] 15.83-15.83 sec 0.00 Bytes 0.00 bits/sec
[ 4] 15.83-15.83 sec 0.00 Bytes 0.00 bits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-15.83 sec 256 KBytes 132 Kbits/sec sender
[ 4] 0.00-15.83 sec 134 KBytes 69.6 Kbits/sec receiverNow for the WiFi profile:
Code:
[ 4] local 192.168.255.1 port 51551 connected to 192.168.255.2 port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.04 sec 2.62 MBytes 21.2 Mbits/sec
[ 4] 1.04-2.03 sec 4.00 MBytes 33.8 Mbits/sec
[ 4] 2.03-3.02 sec 3.75 MBytes 31.9 Mbits/sec
[ 4] 3.02-4.01 sec 4.12 MBytes 34.8 Mbits/sec
[ 4] 4.01-5.01 sec 4.00 MBytes 33.5 Mbits/sec
[ 4] 5.01-6.02 sec 4.00 MBytes 33.1 Mbits/sec
[ 4] 6.02-7.04 sec 3.62 MBytes 30.0 Mbits/sec
[ 4] 7.04-8.02 sec 4.25 MBytes 36.3 Mbits/sec
[ 4] 8.02-9.07 sec 3.75 MBytes 30.1 Mbits/sec
[ 4] 9.07-10.01 sec 4.12 MBytes 36.5 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.01 sec 38.2 MBytes 32.0 Mbits/sec sender
[ 4] 0.00-10.01 sec 37.9 MBytes 31.8 Mbits/sec receiverAnd now a custom profile I created with 1 Gbit bandwidth up/down, but 250 ms delay:
Code:
[ 4] local 192.168.255.1 port 51553 connected to 192.168.255.2 port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.01 sec 2.62 MBytes 21.7 Mbits/sec
[ 4] 1.01-2.01 sec 4.00 MBytes 33.7 Mbits/sec
[ 4] 2.01-3.01 sec 4.00 MBytes 33.6 Mbits/sec
[ 4] 3.01-4.01 sec 4.00 MBytes 33.4 Mbits/sec
[ 4] 4.01-5.02 sec 4.00 MBytes 33.2 Mbits/sec
[ 4] 5.02-6.03 sec 4.00 MBytes 33.2 Mbits/sec
[ 4] 6.03-7.05 sec 3.62 MBytes 29.8 Mbits/sec
[ 4] 7.05-8.02 sec 4.25 MBytes 36.8 Mbits/sec
[ 4] 8.02-9.01 sec 3.50 MBytes 29.6 Mbits/sec
[ 4] 9.01-10.02 sec 4.38 MBytes 36.5 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.02 sec 38.4 MBytes 32.1 Mbits/sec sender
[ 4] 0.00-10.02 sec 38.0 MBytes 31.8 Mbits/sec receiverHope this helps a bit.
Hello
i'm trying to update my macpro 1.1 with new graphic card to reach elcapitan.
I have been reading topic and first post but i have a few questio s.
As it seems el capitan will be last system for our mac i want to get a nice card in order to max it and be able to edit some randoms family videos on final cut or premiere with bootcamp.
I was checking ati hd7950 or 7970 etc but i'm not sure about the need of a mac version card and the benefits of it between pc version. Will a flashed pc version works ok too?
Whats people recomendations?
Thank you
i'm trying to update my macpro 1.1 with new graphic card to reach elcapitan.
I have been reading topic and first post but i have a few questio s.
As it seems el capitan will be last system for our mac i want to get a nice card in order to max it and be able to edit some randoms family videos on final cut or premiere with bootcamp.
I was checking ati hd7950 or 7970 etc but i'm not sure about the need of a mac version card and the benefits of it between pc version. Will a flashed pc version works ok too?
Whats people recomendations?
Thank you
The PC flashed versions will work - unflashed they will work but not show a boot screen which isn't essential, but helpful. The HD5770 works well and is cheaper than the more powerful HD 7950. There are Mac versions of both these available if you don't have the ability to flash the PC version of the card. It depends on how much you wish to spend on this - the Mac cards have a premium price even now. Things to watch are the power leads - not all PC cards have the same pins (6/8) so may need an adapter cable.