MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[MIKX]

I won't even think about Catalina until it's finished.

Did the same with Sierra, High Sierra & Mojave; paid off as I had none of the trials & tribulations some have experienced with for example successive Build revisions in Mojave.

If I had a spare cMP I 'might' consider playing with Catalina prior to final.

 

[ohelio]

Hello everybody,
(sorry for bad english, as you surely can see i'm not a native speaker ... and sorry for the very long text ..)

I am new here in the forum, but i have been reading through this topic for about two weeks now and am very grateful that this thread exists and is kept alive.
Thanks to all the forum posts i managed to install a working Catalina on my MacPro5.1 (=> MP4.1 with FW 5.1 and 2x 6-Core Xeon) and would like to report about it here, followed by a few questions because of appearing problems concerning boot and bootpicker. Meanwhile I updated OpenCore to the 0.5.4 release.

Installation actually took place twice:
1. Clean-Install, as described in # 1
and
2. Update of existing Mojave 10.14.6.
Both only with VMM flag and "-no_compat_check", no SMC spoofing. Both successful. So far so good. ..

Difficulties naturally occurred, as others have already described here. For example, with the clean install procedure booting the existing Mojave on Disk A with the OC on Disk B. After some back and forth it worked, but i don't know why.
What i would like to solve somehow is described at the end at the bottom and concerns the selection of the startup disk for a reboot in another system or its selection in the OC boot picker. Maybe someone knows advice here and can help?

But first of all my story:
I am one of those people who run many boot partitions on the computer for various reasons, for testing and for real operation. In addition old systems for downward compatibility with old, but still used programs.
To avoid overloading the textbody here i attached a txt-file "mysystem" in which you can read about the details of how my system looks like and is configured. It somehow explains my reasons to look for possibilities of running Catalina on my unsupported MacPro, too.

Now the following experiences with my Catalina installation:
I was hoping to be able to use all of my system partitions (listed in "mysystem.txt") with Boot over OC and without in simple ways.
So first and very naive i tried to simply select a different system in Startup Disk preference pane and rebooted. That did not work! The system selected in this way is neither started with or without OC, but instead the Catalina again and again (of course "FwRuntimeServices.efi" and "RequestBootVarRouting" are included in config.plist).

Here i seem to misinterpret the meaning of the description for "RequestBootVarRouting" (true /) (due to my bad English?):
"The quirk lets default boot entry preservation at times when firmwares delete incompatible boot entries. Simply said, you are required to enable this quirk to be able to reliably use Startup Disk preference pane in a firmware that is not compatible with macOS boot entries by design ."

My experience:
Simply said, i am not able to use Startup Disk preference pane. Any chosen startup disk in the preference pane is ignored at reboot.

Now i tried the way to restart with Alt/Option. This of course led to the Apple EFI Bootscreen.
My choices in the Apple Bootscreen (as expected) :

- Mojave 10.14.6 (my main system)
- Sierra 10.12.6
- High Sierra 10.13.6
- Recovery 10.13.6
- Mojave 10.14.6 (little mojave test system)
- Catalina 10.15.2
- EFI Boot (with OpenCore)

If i select "EFI Boot", Catalina starts via Opencore.
The other selections also work, booting without OC.
(Catalina also runs this way without OC thanks to "-no_compat_check").
If i boot without the OC using the direct selection of the start system, i later can successfully select a start system in Startup Disk preferences, which then boots successful when i restart without OC (as expected). The blessing of the OC is deleted in the NVRAM by this.

When restarting with Alt/Option to Apple Bootscreen and selecting the EFI Boot, Catalina starts again via OC, as said above.
After blessing the EFI volume then, everything is again as described when starting with OC: Startup Disk preferences have no effect for the next start.
=> So i can only get to my other system partitions via the native Apple EFI boot menu :-(

Next i activated the OC boot picker. It took a while for this to work, now it runs at least in text mode. However, since i couldn't manage to call it via ESC or Alt/Option at boot, i activated it permanently with a timeout of 3 seconds.

Now the following strange thing happens:
When restarting after blessing of the EFI OC volume, the OC boot menu only shows 1) the Catalina and 2) the associated recovery partition, i.e. only volumes on the same HD or in the same APFS container. Starting the recovery partition does not work with this. Starting Catalina of course works fine.

Why are my other system drives not shown here? ScanPolicy is set to "0". ..and why the recovery cannot be started?

After restarting the computer again with Alt/Option into the Apple boot menu and selecting EFI Boot, the OC boot menu suddenly appears with all system drives in the selection!
Starting the systems is also possible and everyone now starts via OC. Unfortunately, the APFS recovery volumes does not either (neither Mojave Recovery nor Catalina Recovery). Only the Recovery 10.13.6 (Apple_Boot) from High Sierra (HFS+) can be started successfully here.

Back and bootet with newly blessed EFI-OC volume: Again only 1) Catalina and 2) Recovery appear in the OC boot menu .... the other systems are not displayed again!
What is wrong here?

Has anyone had similar experiences on this?

I want to make it somehow possible that in every running system i can make a selection about the system to boot on next reboot, with OC and/or without OC. All system drives should also be offered in the OC boot picker. It has to work somehow. What is my mistake?
If someone can help and would like to, i add my config.plist here, too. It is a very simple one, not much changes to the initial one in #1...

kind regards and thanks,
Ohelio

 

[cdf]

I want to make it somehow possible that in every running system i can make a selection about the system to boot on next reboot, with OC and/or without OC. All system drives should also be offered in the OC boot picker. It has to work somehow. What is my mistake?

This is a known issue. See the remark in step 5d of the guide.

 

[ohelio]

This is a known issue. See the remark in step 5d of the guide.

ok, thanks for that hint!
-------------
5d) Shut down the Mac and do an SMC reset (unplug the power cord, wait 15 seconds, plug the power cord back in, wait 5 seconds, and then press the power button).

Remark: Being installed on Disk A, OC can have trouble seeing Disk B. Doing an SMC reset helps ensure that Disk B is seen when OC starts.
-------------

...but i did that (SMC-Reset) several times, both during the installation process to boot from Disk B (Mojave) and in present after blessing the EFI OC-Volume when booting into the bootpicker.

At installation this already didn't work and i've then done some strange things to initiate booting i can't remember anymore and suddenly OC bootet Mojave on Disk B after all.

Now again after SMC-Reset:
- Booting the "blessed way" only shows the two boot partition in the APFS-Folder of the catalina disk (catalina + recovery) in bootpicker.
- Booting in Apple EFI Bootscreen and from there choosing "EFI Boot" (with OC) shows the whole list of my bootable system- and recovery-Volumes in bootpicker.

Maybe it would help to swap the OC/Catalina SSD from bay 4 to bay 1 and put the Mojave SSD in bay2 ?

 

[ohelio]

Maybe it would help to swap the OC/Catalina SSD from bay 4 to bay 1 and put the Mojave SSD in bay2 ?

Quoting to myself: It needed that little asskick from cdf to start my brain gear wheels again...

Swapping disks seems to be the solution!!!

What i did now:
My main working system with Mojave formerly on SATA bay 1 in my MP5.1 migrates to bay 2. In parallel the Catalina with OC-Bootloader, formerly in bay 4 now resides in bay 1. The data-disk formerly in bay 2 now is in bay 4. To be on the safe side i did a new smc-Reset before booting into bootpicker. ...et voila:

All systems there, even some i didn't expected... I let it boot to the obviously new default on Pos. 1, Sierra. This runs well. Sierra with OC on a MacPro ;-).

Now i tried the impossible and chosed in Startup Disk preference pane of Sierra my main System "OSX" with Mojave. After Reboot now the following view in bootpicker:

After my configured timout of 3 sec it booted without problem into "OSX" to my Mojave. And so on... changed to Catalina in Mojaves Startup Disk preference pane and then restarted again. Bootpicker shows the asterisk in Pos.9 and the machine did boot into Catalina. That seems to solve all my questioned problems. This way all systems starts with OC Bootloader by chosing the Startdisk in prefpane!

But to start the machine without OC it seems i have to go to Apple EFI Bootscreen and later go back to OC again i have to do a new blessing of OC. I will try to tinker together some scripts that can do it with one mouseclick, let' see... i will report.

Thank to cdf for that little flip .. and of course for the whole thing!

What makes me wonder a little is the sequence of the bootpartitions in OpenCore Bootmenu.
This view from booted in "B. OSX" (my main Mojave system)

1. OSX_Sierra => disk7s3 (SSD on Dual SSD PCIe Card)
2. OSX_High_Sierra => disk7s4 (SSD on Dual SSD PCIe Card)
3. Recovery 10.13.6 => disk7s5 (SSD on Dual SSD PCIe Card)
4. Recovery 10.13.6 (dmg)=> probably BaseSystem.dmg in disk7s5
5. OSX_14_Mini => disk8s1 (disk8 is APFS Container in Disk7s7, SSD on Dual SSD PCIe Card)
6. Recovery => disk8s3 (see above)
7. Recovery 10.13.6 => disk1s3 (additional Rescue Recovery on Data-disk without MacOs in SATA Bay 3)
8. Recovery 10.13.6 (dmg)=> probably BaseSystem.dmg in disk1s3
9. OSX_Catalina_Mini => disk5s1 (disk5 is APFS Container in Disk4s2, SATA Bay 1)
A. Recovery => disk5s3 (see Catalina 9. above)
B. OSX => disk6s1 (disk6 is APFS Container in Disk0s2, SATA Bay 4)
C. Recovery => disk6s3 (see Mojave in B. above)

Only cosmetics, but how to get i.e. "OSX" (now B.) to Pos 1.?

 

[jt_69.V]

Can you enable "-v" verbose flag maybe it will be more descriptive?

Here is the output of the bless command:

-bash-3.2# bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/EFI/OC/OpenCore.efi --verbose
EFI found at IODeviceTree:/efi
Mount point for /Volumes/EFI is /Volumes/EFI
Mount point is '/Volumes/EFI'
No BootX creation requested
No boot.efi creation requested
found ioreg "FirmwareFeaturesMask"; featureMaskValue=0xFF1FFF3F
found ioreg "FirmwareFeatures"; featureFlagsValue=0xC00C5417
isPreBootEnvironmentUEFIWindowsBootCapable=0
preboot environment is not UEFI boot capable
isDVDWithElToritoWithUEFIBootableOS=0
Checking if disk is complex (if it is associated with booter partitions)
GPT detected
Booter partition required at index 2
System partition found
Preferred system partition found: disk0s1
Preferred system partition found: disk2s1
Returning booter information dictionary:
<CFBasicHash 0x7f8aa8e00340 [0x10b4da8e0]>{type = mutable dict, count = 3,
entries =>
0 : <CFString 0x10aefcbe0 [0x10b4da8e0]>{contents = "System Partitions"} = (
disk0s1,
disk2s1
)
1 : <CFString 0x10aefd3c0 [0x10b4da8e0]>{contents = "Data Partitions"} = (
disk0s1
)
2 : <CFString 0x10aefd3e0 [0x10b4da8e0]>{contents = "Auxiliary Partitions"} = (
)
}

Relative path of /Volumes/EFI/EFI/OC/OpenCore.efi is \EFI\OC\OpenCore.efi
IOMedia disk0s1 has UUID EFBC16DD-1AD7-4032-B91D-BAA31BF4A7DD
Setting EFI NVRAM:
efi-boot-device='<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>EFBC16DD-1AD7-4032-B91D-BAA31BF4A7DD</string></dict></dict><key>BLLastBSDName</key><string>disk0s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\EFI\OC\OpenCore.efi</string></dict></array>'
Setting EFI NVRAM:
IONVRAM-DELETE-PROPERTY='efi-boot-file'
Setting EFI NVRAM:
IONVRAM-DELETE-PROPERTY='efi-boot-mkext'
Setting EFI NVRAM:
IONVRAM-DELETE-PROPERTY='efi-boot-kernelcache'
NVRAM variable "boot-args" not set.

Is there something wrong here ?

Thanks
Jean

 

[h9826790]

The latest OpenCore 0.5.5 fixed something. Despite the system info still shows 3.5GHz for my W3690, but the CPU power management / actual clock speed is correct.

1) Linpack shows that the CPU can boost to 3.73GHz

2) GeekBench score also suggest that TurboBoost back to normal

3) iStat shows that the CPU now can idle at real low power mode

4) "pmset -g thermlog" also work properly in terminal

And the key parameter is... again... the VMM flag. The CPU's power management only works properly when the VMM flag is OFF. I only do this test in Mojave (18G2022), not in Catalina yet [Update 1: Catalina also tested, same as Mojave]

But anyway, apart from that 3.5GHz cosmetic error. Everything now is truly working properly in Mojave.
A) Full HWAccel
B) DRM Streaming
C) CPU run at full speed

 

[tsialex]

The latest OpenCore 0.5.5 fixed something. Despite the system info still shows 3.5GHz for my W3690, but the CPU power management / actual clock speed is correct.

1) Linpack shows that the CPU can boost to 3.73GHz
View attachment 890079

2) GeekBench score also suggest that TurboBoost back to normal
View attachment 890078

3) iStat shows that the CPU now can idle at real low power mode

4) "pmset -g thermlog" also work properly in terminal
View attachment 890080

And the key parameter is... again... the VMM flag. The CPU's power management only works properly when the VMM flag is OFF. I only do this test in Mojave, not in Catalina yet.
View attachment 890081

But anyway, apart from that 3.5GHz cosmetic error. Everything now is truly working properly in Mojave.
A) Full HWAccel
B) DRM Streaming
C) CPU run at full speed

I suspect that when macOS see that is running behind Apple Hypervisor, power management settings change to a different state more appropriate to a VM than bare metal. This could explain the power management problems with VMM spoofing.

 

[aacemyan]

I wanted to confirm that with latest version of OpenCore 0.5.5, Catalina also has proper CPU behavior when running Geekbench. Best part is that the VMM bug with dual processors seems to be fixed. When i used to turn the flag off, performance would drop in half but that is no longer the case.

All in all i have CPU performance working, full HW acceleration, but still can’t wrap my head around the all my DRM content having sound but showing black screen

 

[startergo]

I wanted to confirm that with latest version of OpenCore 0.5.5, Catalina also has proper CPU behavior when running Geekbench. Best part is that the VMM bug with dual processors seems to be fixed. When i used to turn the flag off, performance would drop in half but that is no longer the case.

All in all i have CPU performance working, full HW acceleration, but still can’t wrap my head around the all my DRM content having sound but showing black screen

As far as the black screen try installing another operating system on a spare partition/drive and check again. I have the same issue, but while it shows black screen in one OS it works fine in the other.
[automerge]1579776411[/automerge]
It might be something related to the default writes.

 

[TECK]

but i did that (SMC-Reset) several times, both during the installation process to boot from Disk B (Mojave) and in present after blessing the EFI OC-Volume when booting into the bootpicker.

I had the same issue. The fix is to make sure Mojave is on Bay 1 of your four internal disk SATA slots. You can install Catalina on the moon, after that. I have Catalina installed on a Syba+970 EVO ssd.

The latest OpenCore 0.5.5 fixed something.

@cdf how can I generate myself the updated config file you attached into OP?

 

[cdf]

@cdf how can I generate myself the updated config file you attached into OP?

You have to modify the file so that it conforms to the specifications described in the documentation. To see what needs to be changed, you can take a look at the "differences" document. As of this writing, the current config should be compatible.

 

[aacemyan]

As far as the black screen try installing another operating system on a spare partition/drive and check again. I have the same issue, but while it shows black screen in one OS it works fine in the other.
[automerge]1579776411[/automerge]
It might be something related to the default writes.

Unbelievable, so I finally found the culprit for the black screen after banging my head against the wall for the past few days. It was Chrome Remote Desktop host that was running in the background. My hunch is that the process running in the background makes MacOS think that a potential recording could be happening, thus turning DRM content black. The instant I uninstalled the program, everything went back to normal.

 

[startergo]

Unbelievable, so I finally found the culprit for the black screen after banging my head against the wall for the past few days. It was Chrome Remote Desktop host that was running in the background. My hunch is that the process running in the background makes MacOS think that a potential recording could be happening, thus turning DRM content black. The instant I uninstalled the program, everything went back to normal.

Yes I was thinking along the same route, but I looked in

Here and screen recording was allowed so I did not suspect it to be the case. But here it is...
[automerge]1579834636[/automerge]
GB results:

MacPro5,1
667
Single-Core Score
5079
Multi-Core Score
Geekbench 5.1.0 Tryout for macOS x86 (64-bit)
Result Information

Upload Date	January 24 2020 02:50 AM
Views	1

System Information
�

System Information
Operating System	macOS 10.15.2 (Build 19C57)
Model	MacPro5,1
Motherboard	Apple Inc. Mac-7BA5B2D9E42DDD94

�

Processor Information
Name	Intel Xeon X5690
Topology	2 Processors, 12 Cores, 24 Threads
Identifier	GenuineIntel Family 6 Model 44 Stepping 2
Base Frequency	3.50 GHz

�

Memory Information
Size	131072 MB
Frequency	666 MHz
Type	DDR3

Single-Core Performance

Floating Point Score	705
Integer Score	652
Crypto Score	628
Single-Core Score	667
AES-XTS	628 1.07 GB/sec
Text Compression	901 4.56 MB/sec
Image Compression	679 32.1 Mpixels/sec
Navigation	683 1.93 MTE/sec
HTML5	597 700.9 KElements/sec
SQLite	623 195.2 Krows/sec
PDF Rendering	660 35.8 Mpixels/sec
Text Rendering	524 167.1 KB/sec
Clang	618 4.81 Klines/sec
Camera	644 7.46 images/sec
N-Body Physics	574 718.6 Kpairs/sec
Rigid Body Physics	889 5508.4 FPS
Gaussian Blur	569 31.3 Mpixels/sec
Face Detection	724 5.57 images/sec
Horizon Detection	688 17.0 Mpixels/sec
Image Inpainting	1205 59.1 Mpixels/sec
HDR	1204 16.4 Mpixels/sec
Ray Tracing	765 614.1 Kpixels/sec
Structure from Motion	519 4.65 Kpixels/sec
Speech Recognition	830 26.5 Words/sec
Machine Learning	307 11.8 images/sec

Multi-Core Performance

Floating Point Score	5444
Integer Score	5117
Crypto Score	2385
Multi-Core Score	5079
AES-XTS	2385 4.07 GB/sec
Text Compression	10051 50.8 MB/sec
Image Compression	7784 368.2 Mpixels/sec
Navigation	2089 5.89 MTE/sec
HTML5	7051 8.28 MElements/sec
SQLite	6338 1.99 Mrows/sec
PDF Rendering	4047 219.6 Mpixels/sec
Text Rendering	2911 927.4 KB/sec
Clang	6736 52.5 Klines/sec
Camera	4149 48.1 images/sec
N-Body Physics	5226 6.54 Mpairs/sec
Rigid Body Physics	11719 72602.0 FPS
Gaussian Blur	6542 359.6 Mpixels/sec
Face Detection	8352 64.3 images/sec
Horizon Detection	4978 122.7 Mpixels/sec
Image Inpainting	6577 322.6 Mpixels/sec
HDR	9376 127.8 Mpixels/sec
Ray Tracing	9519 7.64 Mpixels/sec
Structure from Motion	5271 47.2 Kpixels/sec
Speech Recognition	2113 67.6 Words/sec
Machine Learning	1143 44.2 images/sec

Compare
Set Baseline


[automerge]1579834861[/automerge]
Oh I found the culprit for my random shutdowns during GB test and even during OS X update.
It was...
a click. Yes a click from the processor tray when you reseat it. I replaced the wifi and BT and apparently did not firmly reseated the CPU tray. It will cause all kind of unexpected behavior.

 

[aacemyan]

Your multicore score seems low. I have the same processors and am getting 667 / 6865 on Catalina with VMM flag off.

 

[startergo]

I only do this test in Mojave (18G2022), not in Catalina yet [Update 1: Catalina also tested, same as Mojave]

For dual CPU's I can only test PMset.
Intel gadget does not work with dual CPU's and Istat shows 0% in the processor log. GB5 score is low: 5234 for multicore CPU, 666 for single core.
[automerge]1579838617[/automerge]
Plus I already found some bugs in the latest commit of OC.

 

[handheldgames]

The latest OpenCore 0.5.5 fixed something. Despite the system info still shows 3.5GHz for my W3690, but the CPU power management / actual clock speed is correct.

1) Linpack shows that the CPU can boost to 3.73GHz
View attachment 890079

2) GeekBench score also suggest that TurboBoost back to normal
View attachment 890078

3) iStat shows that the CPU now can idle at real low power mode
View attachment 890082

4) "pmset -g thermlog" also work properly in terminal
View attachment 890080

And the key parameter is... again... the VMM flag. The CPU's power management only works properly when the VMM flag is OFF. I only do this test in Mojave (18G2022), not in Catalina yet [Update 1: Catalina also tested, same as Mojave]
View attachment 890081

But anyway, apart from that 3.5GHz cosmetic error. Everything now is truly working properly in Mojave.
A) Full HWAccel
B) DRM Streaming
C) CPU run at full speed

Any thought if on if this config ready to run windows? I'm setting up an 8.1 media center as a DVR with 48GB of ram and looking for a fresh approach in 2020.

 

[jt_69.V]

I finally succeeded to install and run Catalina on my MacPro5,1 with OC 0.5.4. The only difference with my previous setup is that I re-formatted disk B (which is a HDD, not a SSD) in HFS+ instead of APFS and re-installed Mojave. Is it the reason why OC could not boot it ?

 

[w1z]

Any thought if on if this config ready to run windows? I'm setting up an 8.1 media center as a DVR with 48GB of ram and looking for a fresh approach in 2020.

I think using SMBIOS spoofing under Windows may reset an active license. I personally have not tested it yet but I am planning to.

I also came across this fork of OC - https://github.com/n-d-k/OpenCorePkg, which enables Quirks, SMBIOS, device properties for macOS only... might be worth checking out if you run into issues with Windows or other OSes.

 

[h9826790]

Any thought if on if this config ready to run windows? I'm setting up an 8.1 media center as a DVR with 48GB of ram and looking for a fresh approach in 2020.

Windows is fine.

I simply keep

RequestBootVarRouting = False

Therefore, I can still use the system preference -> start up disk to select next boot to Windows.

But when I boot back MacOS by using Bootcamp panel (in Windows), OC will be disabled. So that I need to re-bless it. But I am happy with this extra step, I only use Windows occasionally.

 

[w1z]

Windows is fine.

I simply keep

RequestBootVarRouting = False

Therefore, I can still use the system preference -> start up disk to selectnext boot to Windows.

But when I boot back MacOS by using Bootcamp panel (in Windows), OC will be disabled. So that I need to re-bless it. But I am happy with this extra step, I only use Windows occasionally.

Funny, I'm doing it the other way around. I'm using OC with RequestBootVarRouting = True to boot Windows 10 EFI from a dedicated NVMe by manually blessing the Windows drive. It will not boot any other way.

Booting from Windows into Windows or macOS works perfectly fine via Bootcamp panel (in Windows).

 

[vit9696]

Funny, I'm doing it the other way around. I'm using OC with RequestBootVarRouting = True to boot Windows 10 EFI from a dedicated NVMe by manually blessing the Windows drive. It will not boot any other way.

Booting from Windows into Windows or macOS works perfectly fine via Bootcamp panel (in Windows).

This looks like a bug as from the description it is supposed to work. If your Windows installation was done in UEFI mode and it shows up in OpenCore, go to macOS and select it in the Startup Disk preference panel. Reboot and collect OpenCore debug log, then file a bugreport in our bugtracker. MBR Windows installations are not supported though.

 

[df3475]

edit: solved

 

[startergo]

This looks like a bug as from the description it is supposed to work. If your Windows installation was done in UEFI mode and it shows up in OpenCore, go to macOS and select it in the Startup Disk preference panel. Reboot and collect OpenCore debug log, then file a bugreport in our bugtracker. MBR Windows installations are not supported though.

I don't think you can select UEFI boot Windows from the system startup disk (you can but it never worked on reboot). It will give you something like "cannot find the system disk". Only through blessing manually or through the boot picker it was possible. I believe I tested the OC boot picker too it works fine.

 

[vit9696]

I don't think you can select UEFI boot Windows from the system startup disk (you can but it never worked on reboot). It will give you something like "cannot find the system disk". Only through blessing manually or through the boot picker it was possible. I believe I tested the OC boot picker too it works fine.

This works just fine on hackintosh, and we particularly designed it the same way it works on Macs for full compatibility. The fact it does not work for you must be some peculiarity of a certain setup.