AMMYY router don't start on Oracle linux 7.9 - linux

community! :)
When I try start binary ammyy_router on Oracle linux 7.9, that hosted on Oracle cloud free tier, I get following error:
-bash: ./ammyy_router: cannot execute binary file
without any additional errors :(
Official man AMMYY router recommends:
Note:
On x64 system you can get error when run ammyy_router, to fix them you need
yum install glibc.i686
yum install libstdc++.i686
but
yum install glibc.i686
yum install libstdc++.i686
get following error:
[opc#instance-20210623-1400 ammyy]$ sudo yum install libstdc++.i686
Loaded plugins: langpacks, ulninfo
ol7_MySQL80 | 2.5 kB 00:00
ol7_MySQL80_connectors_community | 2.5 kB 00:00
ol7_MySQL80_tools_community | 2.5 kB 00:00
ol7_UEKR6 | 2.5 kB 00:00
ol7_ksplice | 2.5 kB 00:00
ol7_latest | 2.7 kB 00:00
ol7_oci_included | 2.9 kB 00:00
ol7_optional_latest | 2.5 kB 00:00
ol7_software_collections | 2.5 kB 00:00
(1/2): ol7_ksplice/aarch64/primary_db | 21 kB 00:00
(2/2): ol7_ksplice/aarch64/updateinfo | 2.8 kB 00:00
No package libstdc++.i686 available.
Error: Nothing to do
[opc#instance-20210623-1400 ammyy]$ sudo yum install glibc.i686
Loaded plugins: langpacks, ulninfo
No package glibc.i686 available.
Error: Nothing to do
File output:
[opc#instance-20210623-1400 ammyy]$ file ./ammyy_router
./ammyy_router: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, BuildID[sha1]=01167db09551003ca92a10734d7dd0a1b332d7d6, not stripped
Uname output:
[opc#instance-20210623-1400 ammyy]$ uname -a
Linux instance-20210623-1400 5.4.17-2102.202.5.el7uek.aarch64 #2 SMP Sat May 22 17:03:57 PDT 2021 aarch64 aarch64 aarch64 GNU/Linux
So, can you help me, what I doing wrong? :(
UPD: I'm trying add official x86_64 repo to yum but get follwing error:
[opc#instance-20210623-1400 ammyy]$ sudo yum-config-manager --add-repo http://yu m.oracle.com/repo/OracleLinux/OL7/latest/x86_64
Loaded plugins: langpacks
adding repo from: http://yum.oracle.com/repo/OracleLinux/OL7/latest/x86_64
[yum.oracle.com_repo_OracleLinux_OL7_latest_x86_64]
name=added from: http://yum.oracle.com/repo/OracleLinux/OL7/latest/x86_64
baseurl=http://yum.oracle.com/repo/OracleLinux/OL7/latest/x86_64
enabled=1
[opc#instance-20210623-1400 ammyy]$ sudo yum check-update Loaded plugins: langpacks, ulninfo
ol7_MySQL80 | 2.5 kB 00:00
ol7_MySQL80_connectors_community | 2.5 kB 00:00
ol7_MySQL80_tools_community | 2.5 kB 00:00
ol7_UEKR6 | 2.5 kB 00:00
ol7_ksplice | 2.5 kB 00:00
ol7_latest | 2.7 kB 00:00
ol7_oci_included | 2.9 kB 00:00
ol7_optional_latest | 2.5 kB 00:00
ol7_software_collections | 2.5 kB 00:00
yum.oracle.com_repo_OracleLinux_OL7_latest_x86_64 | 2.7 kB 00:00
(1/8): ol7_software_collections/aarch64/updateinfo | 81 B 00:00
(2/8): ol7_software_collections/aarch64/primary_db | 1.7 MB 00:00
(3/8): yum.oracle.com_repo_OracleLinux_OL7_latest_x86_64/g | 660 kB 00:00
(4/8): ol7_latest/aarch64/updateinfo | 1.9 MB 00:00
(5/8): yum.oracle.com_repo_OracleLinux_OL7_latest_x86_64/u | 3.2 MB 00:00
(6/8): ol7_optional_latest/aarch64/updateinfo | 1.1 MB 00:00
(7/8): yum.oracle.com_repo_OracleLinux_OL7_latest_x86_64/p | 36 MB 00:01
(8/8): ol7_latest/aarch64/primary_db | 65 MB 00:03
dmidecode.aarch64 1:3.2-5.0.1.el7_9.1 ol7_latest
kernel-uek-debug-devel.aarch64 5.4.17-2102.202.5.el7uek ol7_UEKR6
kexec-tools.aarch64 2.0.20-1.0.6.el7 ol7_latest
ksplice.aarch64 1.0.53-1.el7 ol7_ksplice
ksplice-core0.aarch64 1.0.53-1.el7 ol7_ksplice
ksplice-tools.aarch64 1.0.53-1.el7 ol7_ksplice
oci-utils.noarch 0.12.5-0.el7 ol7_oci_included
oraclelinux-release-el7.aarch64 1.0-13.4.el7 ol7_latest
pciutils.aarch64 3.5.1-3.0.1.el7 ol7_latest
pciutils-libs.aarch64 3.5.1-3.0.1.el7 ol7_latest
perf.aarch64 5.4.17-2102.202.5.el7uek ol7_UEKR6
Update notice ELBA-2021-9327 (from yum.oracle.com_repo_OracleLinux_OL7_latest_x8 6_64) is broken, or a bad duplicate, skipping.
You should report this problem to the owner of the yum.oracle.com_repo_OracleLin ux_OL7_latest_x86_64 repository.
To help pinpoint the issue, please attach the output of "yum updateinfo --verbos e" to the report.
Update notice ELBA-2021-9326 (from yum.oracle.com_repo_OracleLinux_OL7_latest_x8 6_64) is broken, or a bad duplicate, skipping.
and packages glibc*i686 doesn't avaiable to install.

Related

AUR problems with installations

i've a problem in my arch linux distribution, i've added the black arch repo to this one.
When i try to install the impacket suit or crackmapexec using
sudo pacman -S impacket
This is my output
Packages (12) python-click-8.1.2-1 python-flask-2.1.1-1 python-itsdangerous-2.1.2-2 python-jinja-1:3.0.3-1 python-ldap3-2.9.1-3 python-markupsafe-2.1.1-1 python-pcapy-1.0.5-1
python-pyasn1-0.4.8-7 python-pycryptodome-3.14.1-1 python-pycryptodomex-3.12.0-1 python-werkzeug-2.1.1-1 impacket-0.9.24-1
Total Download Size: 5.49 MiB
Total Installed Size: 35.42 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
impacket-0.9.24-1-any 1802.1 KiB 1502 KiB/s 00:01 [#####################################################################] 100%
python-pycryptodomex-3.12.0-1-x86_64 1354.7 KiB 7.47 MiB/s 00:00 [#####################################################################] 100%
python-pycryptodome-3.14.1-1-x86_64 980.6 KiB 6.38 MiB/s 00:00 [#####################################################################] 100%
python-ldap3-2.9.1-3-any 442.8 KiB 3.52 MiB/s 00:00 [#####################################################################] 100%
python-werkzeug-2.1.1-1-any 328.6 KiB 3.31 MiB/s 00:00 [#####################################################################] 100%
python-jinja-1:3.0.3-1-any 240.5 KiB 2.45 MiB/s 00:00 [#####################################################################] 100%
python-click-8.1.2-1-any 154.7 KiB 2.07 MiB/s 00:00 [#####################################################################] 100%
python-flask-2.1.1-1-any 133.6 KiB 1284 KiB/s 00:00 [#####################################################################] 100%
python-pyasn1-0.4.8-7-any 115.2 KiB 1496 KiB/s 00:00 [#####################################################################] 100%
python-itsdangerous-2.1.2-2-any 24.9 KiB 324 KiB/s 00:00 [#####################################################################] 100%
python-pcapy-1.0.5-1-x86_64 22.5 KiB 271 KiB/s 00:00 [#####################################################################] 100%
python-markupsafe-2.1.1-1-x86_64 18.6 KiB 295 KiB/s 00:00 [#####################################################################] 100%
Total (12/12) 5.5 MiB 1803 KiB/s 00:03 [#####################################################################] 100%
(12/12) checking keys in keyring [#####################################################################] 100%
(12/12) checking package integrity [#####################################################################] 100%
(12/12) loading package files [#####################################################################] 100%
(12/12) checking for file conflicts [#####################################################################] 100%
error: failed to commit transaction (conflicting files)
python-pycryptodomex: /usr/lib/python3.10/site-packages/Cryptodome/Cipher/AES.py exists in filesystem
python-pycryptodomex: /usr/lib/python3.10/site-packages/Cryptodome/Cipher/AES.pyi exists in filesystem
python-pycryptodomex: /usr/lib/python3.10/site-packages/Cryptodome/Cipher/ARC2.py exists in filesystem
python-pycryptodomex: /usr/lib/python3.10/site-packages/Cryptodome/Cipher/Blowfish.pyi exists in filesystem
python-pycryptodomex: /usr/lib/python3.10/site-packages/Cryptodome/Cipher/_EKSBlowfish.pyi exists in filesystem
python-pycryptodomex: /usr/lib/python3.10/site-packages/Cryptodome/Cipher/_Salsa20.abi3.so exists in filesystem
<SNIP>
python-click: /usr/lib/python3.10/site-packages/click/shell_completion.py exists in filesystem
python-click: /usr/lib/python3.10/site-packages/click/termui.py exists in filesystem
python-click: /usr/lib/python3.10/site-packages/click/testing.py exists in filesystem
python-click: /usr/lib/python3.10/site-packages/click/types.py exists in filesystem
python-click: /usr/lib/python3.10/site-packages/click/utils.py exists in filesystem
Errors occurred, no packages were upgraded.
As aditional information after the configuration of user i've installed python and python3-pip before the other installation.
did you already check the following thread on the arch forums?
https://bbs.archlinux.org/viewtopic.php?id=249702[1]
Also this one:
https://wiki.archlinux.org/title/Pacman#%22Failed_to_commit_transaction_(conflicting_files)%22_error [2]
my pacman installation of impacket runs apparently without issues:
$ sudo pacman -S impacket
resolving dependencies...
looking for conflicting packages...
Packages (6) python-ldap3-2.9.1-3 python-pcapy-1.0.5-1 python-pyasn1-0.4.8-7 python-pycryptodome-3.14.1-1
python-pycryptodomex-3.12.0-1 impacket-0.9.24-1
Total Download Size: 4.61 MiB
Total Installed Size: 30.25 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
impacket-0.9.24-1-any 1802.1 KiB 2.42 MiB/s 00:01 [#######################################] 100%
python-pycryptodomex-3.12.0-1-x86_64 1354.7 KiB 4.35 MiB/s 00:00 [#######################################] 100%
python-pycryptodome-3.14.1-1-x86_64 980.6 KiB 5.04 MiB/s 00:00 [#######################################] 100%
python-ldap3-2.9.1-3-any 442.8 KiB 3.70 MiB/s 00:00 [#######################################] 100%
python-pyasn1-0.4.8-7-any 115.2 KiB 1719 KiB/s 00:00 [#######################################] 100%
python-pcapy-1.0.5-1-x86_64 22.5 KiB 561 KiB/s 00:00 [#######################################] 100%
Total (6/6) 4.6 MiB 2.53 MiB/s 00:02 [#######################################] 100%
(6/6) checking keys in keyring [#######################################] 100%
(6/6) checking package integrity [#######################################] 100%
(6/6) loading package files [#######################################] 100%
(6/6) checking for file conflicts [#######################################] 100%
(6/6) checking available disk space [#######################################] 100%
:: Processing package changes...
(1/6) installing python-pycryptodome [#######################################] 100%
(2/6) installing python-pycryptodomex [#######################################] 100%
(3/6) installing python-pyasn1 [#######################################] 100%
(4/6) installing python-pcapy [#######################################] 100%
(5/6) installing python-ldap3 [#######################################] 100%
(6/6) installing impacket [#######################################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...

Dealing with two Python libraries from PyPi with same import name?

Just realized that these two Python libraries:
colour · PyPI (pip install colour)
colour-science · PyPI (pip install colour-science)
... use the exact same import - and are therefore in conflict:
import colour
In my MSYS2 installation, I have noticed this:
$ pacman -Ss colour
mingw32/mingw-w64-i686-python-colour 1~0.1.5-1
converts and manipulates various color representation (HSL, RVB, web, X11, ...) (mingw-w64)
mingw32/mingw-w64-i686-python-colour-science 0.3.16-1
Python library for a multitude of colour science applications (mingw-w64)
mingw64/mingw-w64-x86_64-python-colour 1~0.1.5-1 [installed]
converts and manipulates various color representation (HSL, RVB, web, X11, ...) (mingw-w64)
mingw64/mingw-w64-x86_64-python-colour-science 0.3.16-1
Python library for a multitude of colour science applications (mingw-w64)
... and my earlier use of colour-science was gone, so I tried this:
$ pacman -S mingw-w64-x86_64-python-colour-science
resolving dependencies...
looking for conflicting packages...
:: mingw-w64-x86_64-python-colour-science and mingw-w64-x86_64-python-colour are in conflict. Remove mingw-w64-x86_64-python-colour? [Y/n] y
Packages (3) mingw-w64-x86_64-python-colour-1~0.1.5-1 [removal] mingw-w64-x86_64-python-imageio-2.9.0-2
mingw-w64-x86_64-python-colour-science-0.3.16-1
Total Download Size: 2.66 MiB
Total Installed Size: 20.19 MiB
Net Upgrade Size: 20.08 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
mingw-w64-x86_64-python-imageio-2.9.0-2-any 379.3 KiB 1574 KiB/s 00:00 [#################################################] 100% mingw-w64-x86_64-python-colour-science-0.3.16-1-any 2.3 MiB 2.17 MiB/s 00:01 [#################################################] 100% (2/2) checking keys in keyring [#################################################] 100% (2/2) checking package integrity [#################################################] 100% (2/2) loading package files [#################################################] 100% (2/2) checking for file conflicts [#################################################] 100% (3/3) checking available disk space [#################################################] 100% :: Processing package changes...
(1/1) removing mingw-w64-x86_64-python-colour [#################################################] 100% (1/2) installing mingw-w64-x86_64-python-imageio [#################################################] 100% Optional dependencies for mingw-w64-x86_64-python-imageio
mingw-w64-x86_64-freeimage [installed]
mingw-w64-x86_64-python-tifffile
(2/2) installing mingw-w64-x86_64-python-colour-science [#################################################] 100%
So, I cannot use both colour and colour-science libraries via pacman in MSYS2, which does make sense ...
But in principle - is there any way I could use both of these libraries at the same time, even if not via the package manager?

tensorflow/stream_executor/cuda/cuda_driver.cc:328] failed call to cuInit: CUDA_ERROR_UNKNOWN: unknown error

I am trying to use GPU with Tensorflow. My Tensorflow version is 2.4.1 and I am using Cuda version 11.2. Here is the output of nvidia-smi.
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 460.39 Driver Version: 460.39 CUDA Version: 11.2 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|===============================+======================+======================|
| 0 GeForce MX110 Off | 00000000:01:00.0 Off | N/A |
| N/A 52C P0 N/A / N/A | 254MiB / 2004MiB | 8% Default |
| | | N/A |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=============================================================================|
| 0 N/A N/A 1151 G /usr/lib/xorg/Xorg 37MiB |
| 0 N/A N/A 1654 G /usr/lib/xorg/Xorg 136MiB |
| 0 N/A N/A 1830 G /usr/bin/gnome-shell 68MiB |
| 0 N/A N/A 5443 G /usr/lib/firefox/firefox 0MiB |
| 0 N/A N/A 5659 G /usr/lib/firefox/firefox 0MiB |
+-----------------------------------------------------------------------------+
I am facing a strange issue. Previously when I was trying to list all the physical devices using tf.config.list_physical_devices() it was identifying one cpu and one gpu. AFter that I tried to do a simple matrix multiplication on the GPU. It failed with this error : failed to synchronize cuda stream CUDA_LAUNCH_ERROR (the error code was something like that, I forgot to note it). But after that when I again tried the same thing from another terminal, it failed to recognise any GPU. This time, listing physical devices produce this:
>>> tf.config.list_physical_devices()
2021-04-11 18:56:47.504776: I tensorflow/compiler/jit/xla_cpu_device.cc:41] Not creating XLA devices, tf_xla_enable_xla_devices not set
2021-04-11 18:56:47.507646: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcuda.so.1
2021-04-11 18:56:47.534189: E tensorflow/stream_executor/cuda/cuda_driver.cc:328] failed call to cuInit: CUDA_ERROR_UNKNOWN: unknown error
2021-04-11 18:56:47.534233: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:169] retrieving CUDA diagnostic information for host: debadri-HP-Laptop-15g-dr0xxx
2021-04-11 18:56:47.534244: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:176] hostname: debadri-HP-Laptop-15g-dr0xxx
2021-04-11 18:56:47.534356: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:200] libcuda reported version is: 460.39.0
2021-04-11 18:56:47.534393: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:204] kernel reported version is: 460.39.0
2021-04-11 18:56:47.534404: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:310] kernel version seems to match DSO: 460.39.0
[PhysicalDevice(name='/physical_device:CPU:0', device_type='CPU')]
My OS is Ubuntu 20.04, Python version 3.8.5 and Tensorflow , as mentioned before 2.4.1 with Cuda version 11.2. I installed cuda from these instructions. One additional piece of information; when I import tensorflow , it shows the following output:
import tensorflow as tf
2021-04-11 18:56:07.716683: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudart.so.11.0
What am I missing? Why is it failing to recognise the GPU even though it was recognising previously?
tldr: Disable Secure Boot before installing the Nvidia Driver.
I had the exact same error, and I spent a ton of time trying to figure out if I had installed Tensorflow related stuff incorrectly. After many hours of problem solving, I found that my NVIDIA driver was having some problems because I never disabled secure boot in my BIOS when setting up Ubuntu 20.4. Here's what I suggest (I opted for using Docker w/ Tensorflow, which avoids having to install all theCuda related stuff) - I hope it works for you!
Disable Secure Boot in your BIOS
Make a fresh install on Ubuntu 20.4
Install Docker according to nvidia-container-toolkit's page.
curl https://get.docker.com | sh \
&& sudo systemctl --now enable docker
Install nvidia-container-toolkit from the same page.
distribution=$(. /etc/os-release;echo $ID$VERSION_ID) \
&& curl -s -L https://nvidia.github.io/nvidia-docker/gpgkey | sudo apt-key add - \
&& curl -s -L https://nvidia.github.io/nvidia-docker/$distribution/nvidia-docker.list | sudo tee /etc/apt/sources.list.d/nvidia-docker.list
sudo apt-get update
sudo apt-get install -y nvidia-docker2
sudo systemctl restart docker
Test to make sure that's working with
sudo docker run --rm --gpus all nvidia/cuda:11.0-base nvidia-smi
Finally, use Tensorflow with Docker w/ GPU support!
docker run --gpus all -u $(id -u):$(id -g) -it -p 8888:8888 tensorflow/tensorflow:latest-gpu-jupyter jupyter notebook --ip=0.0.0.0
I just made an account to say that #Nate's answer worked for me.
I have the exact same setting as you and have been trying for two days.
What I did in the end was
Reboot - F10 to the setting - Security - BIOS Secure Boot (or something like that I don't remember exactly) - Disabled
Then there was some extra steps with the confirmation but it worked fine. I did not re-install the whole Unbuntu. It was a bit too technically risky for me.
Then I tried the tf.config line and I got this:
2021-06-14 17:12:19.546509: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudart.so.10.1
2021-06-14 17:12:26.754680: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations: SSE4.1 SSE4.2 AVX AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2021-06-14 17:12:26.909679: I tensorflow/core/platform/profile_utils/cpu_utils.cc:112] CPU Frequency: 3593460000 Hz
2021-06-14 17:12:26.910016: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x55a8352501c0 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2021-06-14 17:12:26.910040: I tensorflow/compiler/xla/service/service.cc:176] StreamExecutor device (0): Host, Default Version
2021-06-14 17:12:26.972350: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcuda.so.1
2021-06-14 17:12:27.074861: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:941] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2021-06-14 17:12:27.075289: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1720] Found device 0 with properties:
pciBusID: 0000:0c:00.0 name: GeForce GTX 1650 computeCapability: 7.5
coreClock: 1.665GHz coreCount: 14 deviceMemorySize: 3.81GiB deviceMemoryBandwidth: 119.24GiB/s
There are more red lines on devices properties towards the end but I got
Default GPU Device: /device:GPU:0
Don't know why it works, but it works. Just change the security boot setting.
I don't have enough experience points to upvote Nate's answer. I will come back later. But he/she really offers a good solution.
Disabling Secure Boot solved the problem immediately. No need to reinstall anything.
> import tensorflow as tf
> tf.config.list_physical_devices("GPU")
[PhysicalDevice(name='/physical_device:GPU:0', device_type='GPU')]

Theano Not Able To Find Gpu - Ubuntu 16.04

WARNING (theano.sandbox.cuda): CUDA is installed, but device gpu is not available (error: cuda unavailable)
I get this error when trying to run any sample Theano program.
I have tried all the suggested fixes provided in this thread.
nvcc --version output:
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2015 NVIDIA Corporation
Built on Tue_Aug_11_14:27:32_CDT_2015
Cuda compilation tools, release 7.5, V7.5.17
nvidia-smi output:
Sat Dec 10 00:46:14 2016
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 367.57 Driver Version: 367.57 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 1070 Off | 0000:01:00.0 Off | N/A |
| 0% 37C P0 33W / 151W | 0MiB / 8112MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| No running processes found |
+-----------------------------------------------------------------------------+
gcc version:
(venv) rgalbo#blueberry:~$ gcc --version
gcc (Ubuntu 4.9.3-13ubuntu2) 4.9.3
I have been trying to get this to work for a while now, would like someone to point me in the right direction.
So I was finally able to get Theano to find the gpu, I went through the steps provided here in order to clean up any corrupt installation that may have occured from my initial installation of CUDA.
After this I ran sudo apt-get install cuda which installed the right driver packages for my nvidia graphics card. I then proceeded to install CUDA 8.0 from the deb and this was able to over-write the 7.5 version that was giving me issues.
This is the output I am now able to get from theano_test.py:
(venv) rgalbo#blueberry:~$ python theano_test.py
Using gpu device 0: GeForce GTX 1070 (CNMeM is disabled, cuDNN 5103)
[GpuElemwise{exp,no_inplace}(<CudaNdarrayType(float32, vector)>), HostFromGpu(GpuElemwise{exp,no_inplace}.0)]
Looping 1000 times took 0.185949 seconds
Result is [ 1.23178029 1.61879349 1.52278066 ..., 2.20771813 2.29967761
1.62323296]
Used the gpu
and here is my ~/.theanorc file:
(venv) rgalbo#blueberry:~$ cat ~/.theanorc
[global]
floatX = float32
device = gpu
[nvcc]
flags=-D_FORCE_INLINE
[cuda]
root = /usr/local/cuda-8.0
After each separate install I updated and rebooted the server just for good luch, which I found to be helpful.

Can't install crossbar.io binary package on FreeBSD 10.1

I'm unable to install the crossbar.io WAMP router's binary distro on FreeBSD 10.1
I'm doing it step-by-step by the manual (http://crossbar.io/docs/Installation-on-FreeBSD/), but during the pkg install crossbar i get this output:
Updating FreeBSD repository catalogue...
Fetching meta.txz: 100% 944 B 0.9kB/s 00:01
Fetching packagesite.txz: 100% 6 MiB 2.9MB/s 00:02
Processing entries: 100%
FreeBSD repository update completed. 25427 packages processed.
Updating crossbar repository catalogue...
crossbar repository is up-to-date.
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):
New packages to be INSTALLED:
crossbar: 0.13.2 [crossbar]
Number of packages to be installed: 1
The process will require 161 MiB more space.
Proceed with this action? [y/N]: y
[1/1] Installing crossbar-0.13.2...
[1/1] Extracting crossbar-0.13.2: 0%
pkg: Directory /opt/crossbar/lib-python/2.7/plat-mac/lib-scriptpackages/SystemEvents not specified in the manifest
[1/1] Extracting crossbar-0.13.2: 100%
And nothing's get installed only empty folders under /opt/crossbar
Am I doing something wrong?
Any input will be appreciated.

Resources