Tag Archives: linux


# ./deviceQuery
./deviceQuery Starting...

CUDA Device Query (Runtime API) version (CUDART static linking)

Detected 1 CUDA Capable device(s)

Device 0: "GeForce GTX 1050 Ti"
CUDA Driver Version / Runtime Version 10.0 / 10.0
CUDA Capability Major/Minor version number: 6.1
Total amount of global memory: 4039 MBytes (4234936320 bytes)
( 6) Multiprocessors, (128) CUDA Cores/MP: 768 CUDA Cores
GPU Max Clock rate: 1418 MHz (1.42 GHz)
Memory Clock rate: 3504 Mhz
Memory Bus Width: 128-bit
L2 Cache Size: 1048576 bytes
Maximum Texture Dimension Size (x,y,z) 1D=(131072), 2D=(131072, 65536), 3D=(16384, 16384, 16384)
Maximum Layered 1D Texture Size, (num) layers 1D=(32768), 2048 layers
Maximum Layered 2D Texture Size, (num) layers 2D=(32768, 32768), 2048 layers
Total amount of constant memory: 65536 bytes
Total amount of shared memory per block: 49152 bytes
Total number of registers available per block: 65536
Warp size: 32
Maximum number of threads per multiprocessor: 2048
Maximum number of threads per block: 1024
Max dimension size of a thread block (x,y,z): (1024, 1024, 64)
Max dimension size of a grid size (x,y,z): (2147483647, 65535, 65535)
Maximum memory pitch: 2147483647 bytes
Texture alignment: 512 bytes
Concurrent copy and kernel execution: Yes with 2 copy engine(s)
Run time limit on kernels: No
Integrated GPU sharing Host Memory: No
Support host page-locked memory mapping: Yes
Alignment requirement for Surfaces: Yes
Device has ECC support: Disabled
Device supports Unified Addressing (UVA): Yes
Device supports Compute Preemption: Yes
Supports Cooperative Kernel Launch: Yes
Supports MultiDevice Co-op Kernel Launch: Yes
Device PCI Domain ID / Bus ID / location ID: 0 / 1 / 0
Compute Mode:
< Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) >

deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 10.0, CUDA Runtime Version = 10.0, NumDevs = 1
Result = PASS

Tinkering with the cheaper Intel Compute Stick

So, a while ago Intel released a “Intel Compute Stick”. It’s kindof tiny, doesn’t perform perfectly – but is quite a nice, quiet alternative for those whack-a-terminal-an-stream-some-music nights.

Problem is – I don’t care that much for the Ubuntu 14.04 LTS pre-loaded (yes, I am talking about the version with only 1Gb mem, and whatissit – 8gb storage?).

Good thing is – if you can survive with the built in realtek wifi, only thing you need to take heed to is the Intel drivers, from the proprietary locked down section of the binary world (or, almost – they are available in slightly different format..).

So far, you can grab ’em from https://01.org/linuxgraphics.

Problem is – if you really wanna use the built in wifi, mail realtek. Yes.. email – to get drivers. It’s lovely.


Wireless LAN ICs
Email: wlanfae@realtek.com

There is someone that seems to have put the source on git for a working wifi-driver;

do the following;

sudo apt-get install build-essential linux-headers-generic git
git clone https://github.com/codeTom/rtl8723bs.git
cd rtl8723bs
sudo make install
sudo depmod -a
sudo modprobe r8723bs

Either way, I got it cheap – works – and runs. Yay.

Trying out Windows Subsystem for Linux on Windows 10.

It is on… Trying out the … scary co-inhabitant partnership that currently is undergoing a beta period.

Point here is (according to a terrible video by MS) is that it is “brand new”. They seem to have forgotten their old subsystem for UNIX, that was.. horrid – and not even close to something that at least today should be able to touch production machines.

However.. They did stress quite a lot that it is still beta, and only a small subset of actual syscalls via the “adapter” works against the NT Kernel.
No suprises there at all. We will see how many they might be able to cover, and if it might even be proven to gain any kind of trust.

For the real world – the primary claim is that it will work perfectly for developers etc.. I would say it would prolly work as at best a better approach than pulling out resources for a virtual machine.

They seem to take pride in that it will share the current network stack – that we all know is fracked from the beginning. Windows can barely handle anything in this sense, and workload, no – this is only for simple tasks, and a easier way on a local machine to get you hopefully at least the normal GNU toolset to work out of the box.


At least – getting it to run is easy.

To get this horrid beta on your machine – first you need to grab a beer. Then some coffee, then I would say either a bottle of whiskey or a energy drink.

Step by step …

1 – Jump onto your windows 10 box, login, grab the first beer.
2 – register for Windows Insider Previews
3 – dig into the updates and advanced settings, input your account details for the preview
4 – guessing a reboot, and a new beer.
5 – now, go back to the insider preview part in updates – adjust the slider to the outer dangerous position. Grab coffee or whiskey..
6 – reboot – refill drink
7 – Reboot a couple of more times
8 – Apply all the patches, reboot
9 – Do all the logins, verify that your screen is now filled in the lower right corner with at least build number 14332
10 – grab the turn windows features on and off – locate the magical new windows subsystem for linux (beta)
11 – reboot
12 – login again, grab a new drink
13 – punch in bash and accept the canonical licence if you dare, create a local account
14 – grab hopefully that last drink
15 – wait for it to download the ubuntu data, from the microsoft market…
16 – wait for it..

(PS – Seems like they fixed top, kinda – DS.)

Toy around. Enjoy – destroy – and remember – even if this leaves beta – we rely on the NT Kernel, The underlying windows features – Windows networkstack – and the permission of Microsoft to use our software…

Go fish!

So, just for fun I started thinking of getting myself a new shell – I’m not tied down to bash in anyway – just some of the basic features.

So I found Fish.

It has the initial feel of a hippie shell – it’s colorfull, all over the place with completions – let’s see how it works out :).