To configure a system in any kind of RAID mode you have to set the jumper like shown here. Then with F8 enter the BIOS settings and change the Main Board to RAID mode.

The systems will most propably not see the RAID mode, we were unable to localize/solve this issue. The only thing that did work was installing a RAID card. Then the following jumper has to be modified accordingly: After doing so press Ctrl+A to enter the RAID card settings and set up the Disks accordingly.

For the screen to work properly we use a Nvidia graphic card (Quadro 600). To install is follow this steps:

1. sudo ubuntu-drivers devices

This shows a list of recommended drivers, chose the one that corresponds to the graphic cards

1. sudo apt install nvidia-driver-390
2. sudo reboot
3. nvidia-smi

The last command should display some information's regarding the graphic card.

To install LabVIEW you need a ni account. Download the iso file, make sure you have downloaded the correct version in regards to operating system and version compatibility. After you have downloaded the iso file follow these steps:

1. Install libncurses5 and libopenal1 from the repositories of your Linux distribution.
2. mount the iso file
3. Run the install script INSTALL as root (e.g.,sudo ./INSTALL)

If you go with a different linux/LabVIEW version the guide above may not work, but there exists a Guide for different verisons of linux/LabVIEW

To use a gpib-usb connection you have to install the driver. For this follow these steps, missing directories have to be made accordingly:

1. Download the newest version of the driver here.
2. Install the kernel
   1. make
   2. sudo make install
3. Install the user
   1. ./bootstrap
   2. ./configure –sysconfdir=/etc
   3. make
   4. sudo make install
4. replace the original gpib.conf file in /etc/gpib.conf with this modified file
5. move the config file to /etc/gpib/
6. make it executable sudo chmod 644 /etc/gpib/gpib.conf
7. copy the ni_usb_gpib file from your_linux_gpib_dir/usb/ni_usb_gpib/ to /lib/udev
8. download the newest firmware and unzip the necessary ones
9. move the firmware files to /lib/firmware/, then rename the folder ni_gpib_usb_b to ni_usb_gpib
10. modifie the /lib/udev/ni_usb_gpib file accordingly
11. sudo apt-get install fxload
12. create a file in /etc/udev/rules.d/ named 99-linux_gpib_ni_usb.rules with this content
13. initialize the config file: sudo gpib_config
14. initialize the udev rules:
    1. sudo udevadm control –reload-rules
    2. sudo udevadm trigger
    3. sudo udevadm settle
15. test communication: sudo ibtest

If you get an error that looks something like this: …. libgip: IBOPENDEV ioctl failed ibdev error …. it means that your system uses the gpib.conf file located in /usr/local/etc/gpib.conf, which is wrong to solve this either modify this file according to the above one or use this command:

1. sudo ln -s /etc/gpib.conf /usr/local/etc/gpib.conf
2. sudo gpib_config

This should resolve the error. If you update your kernel version, the kernel module gets nopt automatically moved into the new kernel, either change back or recompile the kernel module.

When trying to install the ARC66 it will give the following Warning: modules_install: missing 'System.map' file. Skipping depmod. Which can be ignored. When trying to install Owl it will say: Invalid source file! This comes from an error in the Install file itself, scroll down until you find the line, which specifies the source file, there change the file name to OwlFiles3.6.2.tar. You have to be super user to start the installation process. For both cases make sure that all the files have read write and execute permission:

• sudo chmod -R 777 /path/to/directory

To install root follow these commands:

1. wget https://root.cern/download/root_v6.32.04.Linux-ubuntu20.04-x86_64-gcc9.4.tar.gz
2. tar -xzf root_v6.32.04.Linux-ubuntu20.04-x86_64-gcc9.4.tar.gz -C ~/
3. nano ~/.bashrc
4. add this to the end of the file: source ~/root/bin/thisroot.sh
5. source ~/.bashrc
6. root

the last command should start the root interactive shell, if not something went wrong.

Before you start the tmux session make sure, that the cdaq_env is activated (source cdaq_env/bin/activate) otherwise it will complaine.