flanaras' adventures

Anything that I might come along :)

openSUSE Virtual box kernel error

Hello again, another problem I’ve been encountering comes as following. I used to use Virtual box on my openSUSE tumbleweed box but at some point it would complain about the kernel modules missing. I had all of the tools need to compile the module and still didn’t work. At the same time the message given by virtual box didn’t help at all. The error as shown “Kernel driver not installed (rc=-1908)”, with the hint of executing “/sbin/vboxconfig” which doesn’t exit on my openSUSE box. The other error that’s also shown is “NS_ERROR_FAILURE (0x80004005)” which is related to missing kernel modules. See below:

screenshot of virtual box showing rc=-1908 error

Assuming that you have also already installed the virtual box kernel modules you should just run as root, every time you want to run virtual box (once per boot):

 > modprobe vboxdrv

Happy Virtual boxing.


Setup OpenCL on openSUSE [Intel Integrated GPU]

Hello all,

This time I will go on how to setup and run OpenCL applications on openSUSE using an Intel HD Graphics 4400 GPU. As long you’re having an Intel integrated GPU that supports OpenCL, these steps should be able to work for your as well.

You can check in Intel_HD_and_Iris_Graphics [] about your hardware’s compatibility and what version of OpenCL you can work with.

[Note: 1] Important: This would be more or less how to setup OpenCL on a computer. The only thing that would differ from this guide is how to deal with the “Missing OpenCL environment” section.

[Note: 2] I will be skipping the verification of the binaries.

My specifications:

  • openSUSE tumbleweed
  • Intel(R) Core(TM) i5-4300U CPU
  • Intel(R) HD Graphics 4400
  • g++ (SUSE Linux) 6.2.1 20161209 [gcc-6-branch revision 243481]

I point to clDeviceQuery.cpp []  as the test source code that will be trying to run.

Now, lets try to compile it. First of all we need to add the -lOpenCL library in order to compile an OpenCL application.

To add the library to the system install libOpenCl1.

 > zypper in libOpenCL1

// Missing headers

Lets try to compile the source code

 > gcc -lOpenCL clDeviceQuery.cpp
0clDeviceQuery.cpp:8:19: fatal error: CL/cl.h: No such file or directory
#include <CL/cl.h>
compilation terminated.

We see that the OpenCL headers are absent. To install them we need the package called opencl-headers.

 > zypper in opencl-headers

// Link problem

Lets try to compile it again.

 > g++ -lOpenCL clDeviceQuery.cpp
/usr/lib64/gcc/x86_64-suse-linux/6/../../../../x86_64-suse-linux/bin/ld: cannot find -lOpenCL
collect2: error: ld returned 1 exit status

Now we have a different problem, g++ can’t find libOpenCL. We need to add a symbolic link for /usr/lib64/ to point to /usr/lib64/

 > ln -s /usr/lib64/ /usr/lib64/

// Missing OpenCL environment

Compilation succeeds this time.

 > g++ -lOpenCL clDeviceQuery.cpp
 > ./a.out
clDeviceQuery Starting...

Error -1001 in clGetPlatformIDs Call!
System Info:

Local Time/Date = 13:52:14, 01/31/2017
CPU Name: Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz
# of CPU processors: 4
Linux version 4.9.6-1-default (geeko@buildhost) (gcc version 6.2.1 20161209 [gcc-6-branch revision 243481] (SUSE Linux) ) #1 SMP PREEMPT Thu Jan 26 09:09:16 UTC 2017 (d1207ac)

Again we hit on another problem, we are missing the OpenCL runtime environment/driver for my GPU. It is required to install the OpenCL runtime for the specific computer. This will work more or less with most (?) Intel Integrated GPUs. We will need to download “OpenCL™ 2.0 GPU/CPU driver package for Linux (64-bit)” from Intel’s page containing “Driver and library(runtime) packages” [].

After downloading and unpacking we have to install the file called intel-opencl-r4.0-59481.x86_64.rpm.

 > zypper in intel-opencl-r4.0-59481.x86_64.rpm

// All working

Trying again to compile and run will give us the following result.

 > g++ -lOpenCL clDeviceQuery.cpp
 > ./a.out
clDeviceQuery Starting...

1 OpenCL Platforms found

OpenCL Device Info:

1 devices found supporting OpenCL on: Intel(R) OpenCL

Device Intel(R) HD Graphics
CL_DEVICE_NAME: Intel(R) HD Graphics
CL_DEVICE_VENDOR: Intel(R) Corporation

clDeviceQuery, Platform Name = Intel(R) OpenCL, Platform Version = OpenCL 1.2 , NumDevs = 1, Device = Intel(R) HD Graphics

System Info:

Local Time/Date = 14:16:40, 01/31/2017
CPU Name: Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz
# of CPU processors: 4
Linux version 4.9.6-1-default (geeko@buildhost) (gcc version 6.2.1 20161209 [gcc-6-branch revision 243481] (SUSE Linux) ) #1 SMP PREEMPT Thu Jan 26 09:09:16 UTC 2017 (d1207ac)

All tests have passed! This is the point that we wanted to reach. We can also see that my I run OpenCL 1.2.

Have lots of fun with your OpenCL programming.

Enjoy until next time

— flanaras

Transactional memory on Fedora [24]

Hello again,

This time I will going through on how to compile a program with g++ that has transactional memory support on Fedora 24.

The compilation command  will look like:

g++ -std=c++11 -fgnu-tm transactions.cpp -o r

Running this on Fedora will result in an error

/usr/bin/ld: cannot find -litm
collect2: error: ld returned 1 exit status

An easy way to overcome this is to install libitm and libitm-static

 sudo yum install libitm libitm-static

After that if we try to compile again we get no errors and we can also run the program with no problems!

 > g++ -std=c++11 -fgnu-tm transactions.cpp -o r
 > ./r
[meaningful results]


Have fun

— flanaras

Fix DNS problem on openSUSE


today for no reason the DNS resolving stopped working on my openSUSE tubleweed for no reason. I tried to supply a DNS server from the connection’s settings but it wouldn’t work, but directly pinging on an ip worked. On a quick look on google I found out that messing with /etc/resolv.conf and adding “nameserver DNS_IP”, it would do the trick although it doesn’t look the right way to do it.

[Check 07/07/2017 edit as well]

Originally my resolv.conf file looked like:

### /etc/resolv.conf file autogenerated by netconfig!

and with the fast patch would look like

### /etc/resolv.conf file autogenerated by netconfig!

As shown on openSUSE forum on an older thread removing previously mentioned file and restarting the NetworkServices fixes the problem. Remove the resolv.conf so it would get generated again.

 > su -c 'rm /etc/resolv.conf && systemctl restart NetworkManager.service'

— update [26/09/2016]: It seems that there is an other nifty solution to the same problem, check goinggnu’s post about the same problem!

— update [07/07/2017]: The same problem has resurfaced, DNS information from DHCP do not get used properly from the connection manager and DNS fields are not set. Check the information from the dhclient and manually insert them in the network profile. This is especially necessary when connected on a limited network that filters remote DNS queries, else you can use any other DNS server of your preference in the /etc/resolv.conf file or per profile.

 # view dhclient info
 > cat /var/lib/dhcp/dhclient.leases
 # restart network services
 > systemctl restart network

In case that you have set some DNS server in /etc/resolv.conf and you are in a filtered environment it won’t work. To make it work delete the file and then continue with the instructions in the update section.


best regards

— flanaras


Install okular on gnome

If you would like to install a good pdf viewer in gnome you might pick a kde application, sure that’s great, but it might not look so good at first.

I like to use okular in gnome but if you just install okular like

> zypper in okular

it will get installed but at the same time all of the icons will be missing from the menus and even the application image wont be there. Sure it is fully functional but it doesn’t look good.

A way to get these icons is to install a kde icon package such as oxygen (if I start okular from the command line it complains a lot about oxygen icons) but a more concrete way to do this is to install the kde base pattern. In my case on tumbleweed I had to install the “kde” pattern (more info could be on [1] but info could also be outdated, I know this will install a lot of unnecessary things but IMHO it’s safer and easier to do it this way.

> zypper install -t pattern kde

If your are not in openSUSE you should check for a pattern (if your distribution has patterns) like “KDE Desktop environment” or something that could contain the terms “KDE”, “base”, “environment” or on your distribution’s forum for help installing the KDE environment.

If you re in openSUSE and you don’t find this pattern go on yast and search for something similar under patterns.

The result would be something like this.

screenshot of okular in gnome with working icons in place


Use git with GitHub’s Two-Factor Authentication in windows

Hello everyone,

This time I will be explaining how to use Two-Factor Authentication from GitHub on git  on a command prompt or any terminal emulator on Windows.

You probably have tried already to do something like:

 > git clone

entered your username, password and never asked for your 6 digit authentication code which led to authentication error similar to this one:

 > fatal: Authentication failed for ''

The solution to this is easy, use SSH! To use SSH you need to create a private/public key pair. One way to do that is to download PuTTYgen, run it and select the number of bits that you desire for your key, in this case 4096.

selecting the number of bits for the key

press generate and start moving your mouse around. Then you will have something like this.

Screenshot 2016-06-10 23.25.05.png

Enter the passphrase you desire, this will be used when accessing your private key so do not forget it. As pointed out by @Sakrifor, you need to create the private key by the option Conversions -> Export OpenSSΗ key. Create a folder named .ssh under your user’s folder and save it as “id_rsa”, for instance:


Copy your public key, go to GitHub settings -> SSH and GPG keys, click on “New SSH Key”, give it a tittle to know where you use this key and paste the public key. After that, go to GitHub and get a SSH link to your repository by “Clone with SSH”. Continue on a command prompt and …

 > git clone
   Cloning into 'my-private-repository'...
   The authenticity of host ' (' can't be established.
   RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.
   Are you sure you want to continue connecting (yes/no)? y
   Please type 'yes' or 'no': yes
   Warning: Permanently added ',' (RSA) to the list of known hosts.
   Enter passphrase for key '/c/Users/flanaras/.ssh/id_rsa':
   remote: Counting objects: 60, done.
   Receiviemote: Total 60 (delta 0), reused 0 (delta 0), pack-reused 60ng objects:

   Receiving objects: 100% (60/60), 22.97 KiB | 0 bytes/s, done.
   Resolving deltas: 100% (25/25), done.
   Checking connectivity... done.

It works, well done! Now you will be asked to enter your passphrase and not your GitHub credentials.

Note that we previously checked the validity of the RSA fingerprint, Github’s SSH keys.

See you around


[No-Fix] Accidentally deleted nvidia’s driver files on openSUSE


some days ago I was cleaning up some old kernels that I had on my openSUSE installation and, then at point, I deleted by mistake the files on /lib/modules/4.1.12-1-default/.* which contains nvidia.ko, nvidia-modeset.ko, nvidia-uvm.ko and some other files.

After that, when I restarted my computer I had no graphics. I would get an error when the login screen should appear. Thankfully I was able to to switch to the terminal(s) [ctrl-alt{1-6}] and ctrl-alt-7 for the “graphic terminal” which would be the regular one.

I tried then to uninstall nvidia’s modules following the openSUSE guide for nvidia drivers but no luck. Nothing was happening when I disabled the repository and refreshed them through zypper. I also try to play with the blacklisted drivers in /etc/modprobe.d/.* and got to nowhere. Next thing I did is to search why and how the “> startx” would fail. Still at this I was working from the terminal, without any GUI yet, note there where a lot of attempts and reboots.

Finally, what fix the problem I caused to myself was to, manually uninstall the nvidia packages that they still existed in the system, reboot and many hours lost for no reason.

 > #This is the magic command when working
 > #with openSUSE and nvidia and something goes wrong
 > sudo zypper rm nvidia-computeG04 nvidia-gfxG04-kmp-default
 > sudo zypper rm nvidia-glG04 x11-video-nvidiaG04

I hope this doesn’t happen to anyone else, if it happens that he or she will find this article fast.


[update 05/09/2016]: There is not easy solution for this, I might had be able to get the graphics back but I was experiencing a lot of crashes so I would suggest you to make a clean installation. I ended up doing a clean installation 😦


Wish you the best

— flanaras

Install Gazebo on openSUSE Leap 42.1

I guess if you are here you have the same question as I did, how to install Gazebo on openSUSE.

What you have to do in order to install simulator Gazebo is to find or build it’s rpm package. Thankfully some guy who goes by the nickname awissu has already built an rpm package.

Go download and install it. In my case I downloaded gazebo-7.0.0-13.1.x86_64.rpm

> sudo zypper in gazebo-7.0.0-13.1.x86_64.rpm

Wow (!) installation succeeded, but if you go to run the gazebo you get an error:

> gazebo
> gazebo: error while loading shared libraries: cannot open shared object file: No such file or directory

Okay, now let’s go and solve this problem. Instructions on how to Build And Install ignition math follow. /* you will need to install package mercurial if you don’t already have it */

  1. Setup local repository:
    > hg clone /tmp/ign-math
    > cd /tmp/ign-math
    > hg up ign-math2
  2. Make build folder:
    > mkdir build
    > cd build
  3. Build and install:
    > cmake .. -DCMAKE_INSTALL_PREFIX=/usr
    > make -j4 ## Here put the number of your computer's cores instead of 4
    > sudo make install

Let’s try again!

> gazebo
> Error [] Unable to find or open SDF file[root.sdf]

Damn.. It still doesn’t work.
It’s time to install now SDFormat [Build And Install SDFormat]. Similar as ignition math we have:

  1. Init repo
    > hg clone /tmp/sdformat
    > cd /tmp/sdformat
    > hg up sdf3
  2. To make the build folder:
    > mkdir build
    > cd build
  3. And to actual build it:
    > cmake .. -DCMAKE_INSTALL_PREFIX=/usr
    > make -j4
    > sudo make install

Fingers crossed. Let’s hope third time is the charm. Yaaayyyy, it finally works!



Until next time.

— flanaras

Install Slack on openSUSE Leap 42.1

If you are trying to install slack from their fedora x64 package on openSUSE Leap 42.1 and you find that libXScrnSaver is missing and you can’t find it anywhere to install in, don’t worry! You actually don’t need this package. The package you need is libxss1.

Tested on: Leap 42.1, tumbleweed and Leap 42.2


Slack 2.0.2 working on openSUSE Leap 42.1

The first step is to be sure that you have libXss1 package. You can do this using the “1 Click Install” or simply type in a terminal:

 > sudo zypper in libXss1

Next step is to install slack. In my case I achieved this by typing: /* Note that you need to have in the same folder as the working folder in terminal */

 > sudo zypper in slack-2.0.2-0.1.fc21.x86_64.rpm

When you do so, you will get prompt to cancel the installation or to break slack by not providing a missing dependency. /* What actually happened with this is is that the package got renamed from libXScrnSaver to libXss1 but slack is still searching for the old name for some reason. I don’t know if it is available through repositories in fedora but it’s definitely not here on openSUSE.*/ Choose to break the installation and you’re done. You successfully installed slack on your openSUSE box!

To enable the auto-update function (as @Stane1983 said) you need to do one more step.

“While Slack installs it’s repository into system for update checking, it does not import GPG key of it’s repository which breaks software updates. To fix that issue, simply import GPG key by opening terminal and typing:

 > sudo rpm --import

“, as stated on his post [].

This is not only bound to Leap 42.1, it’s going to work with the rest of openSUSE’s versions. Probably it’s going to work for other rpm based distributions.

Until next time enjoy yourselves! 🙂

— flanaras

— update [19/03/2017]: Add instructions for auto-update.


Blog at

Up ↑