Importing .sdtid files with stoken

So this morning I was kindly reminded again by my corporate IT overlords that my RSA soft token was going to be expiring in 9 days. Having had this token in place for a year now I had forgotten how to update it.

After a few minutes I recalled that the trick was as simple as

stoken import --file <my>.sdtid

Well that’s simple, except for the fact that in my case, this failed. After a quick bit of googling around I found that version 0.2 (which ships with my release of ubuntu) incorrectly identifies where the tokens are within the sdtid files resulting in an annoying error:

error: no valid token in file '<my>.sdtid': General failure

UGH! Well the solution is simple here. After a quick upgrade to 0.90 I’ve had no problems importing since.

Update: Kubuntu 15.10

Well after a few days of usage I found some major problems which prevented me from adopting Kubuntu 15.10 with the lovely Plasma 5 setup.

  1. Auto mount of NFS shares is broken again
  2. Desktop backgrounds are locked to a single background image
  3. Auto mount of random key encrypted swap is broken
  4. After a day or so of uptime, Plasma 5 starts to bog down
  5. A lot of the plasma widgets are a step backwards, they’re ugly, or poorly laid out vs the older Plasma 4 widgets

I’m hoping that these issues get resolved, as Plasma 5 and the new layouts and themes were a whole lot prettier than Plasma 4, however since I can’t use it everyday successfully and without aggravation I decided to restore my backup.

Getting the Nvidia distribution drivers installed with Ubuntu 14.10 and possibly later

So do to the fact that my HTPC died, and I didn’t want to restore the OS from a backup, I opted instead to install a fresh (and reasonably modern) version of Kubuntu. Once installed I quickly ran into problems with the binary video driver installation. Yes, yes, I realize that I could simply instruct Kubuntu (or Ubuntu) to utilize the Canonical tracked binary drivers, however they’re always generally behind quiet a few versions, and for this system I like running the bleeding edge.

So my adventure in Nvidia driver installation begins yet again, a road I’ve been down many times…

Assuming you’ve downloaded the latest binary driver from Nvidia and try to install it you’ll immediately run into problems with the binary installer complaining that:

  • X windows is still running
  • The Nouveau module is loaded
  • The compiler can’t be found
  • 32bit libraries are missing (assuming you’re running 64bit OS like I am)

By far the most frustrating of these is Nouveau. Listen I’m all for open software, however the reality is that Nouveau is a poor substitute for the real deal from Nvidia. Would it be great if Nvidia open sourced their driver? Hell yes, however since they’re not willing to I’m stick using it in a binary format… Anyways, below are the steps I’ve used (recently) to achieve success in installing this driver:

  • Obtain the latest driver from Nvidia
  • Remove the packages xserver-xorg-video-nouveau and xserver-xorg-video-all
sudo dpkg -r xserver-xorg-video-nouveau xserver-xorg-video-all
  • Install the linux-headers package matching your kernel and the dkms package
sudo apt-get install linux-headers-`uname -r` dkms
  • Install GCC and make packages
sudo apt-get install gcc make
  • Install 32bit OpenGL libraries (if you’re running 64bit OS)
apt-get install libgl1-mesa-dri:i386 libgl1-mesa-glx:i386
  • Modify your GRUB configuration to set nomodeset on boot
  • edit: /etc/default/grub and find the line starting with: GRUB_CMDLINE_LINUX_DEFAULT. This usually this looks like:
  • Add nomodeset to it:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
  • Save the file and run update-grub
sudo update-grub
  • Reboot

Once rebooted make sure that X windows is shutdown. Usually if X is running on boot in Kubuntu or Ubuntu environments, it’s due to kdm, gdm, or lightdm

sudo stop lightdm

After that, try and run the nvidia binary driver installer and allow it to install the drivers. Hopefully all will go smoothly and your system will be ready to go. Once complete you can simply restart X windows:

sudo start lightdm

Good luck, and if you have problems feel free to let me know in the comments section!

My HTPC finally died…

So over the last few years I’ve been a very simple HTPC setup. It consisted of an Intel E4500, 4GB ram system with a GTX 780 Nvidia card running Kubuntu Linux 12.04.

For storage I booted off a simple USB stick, after 3 years I’ve killed 5 USB sticks with constant writes, caching, swapping etc. Clearly not an ideal environment for a USB stick to operate in but hey, who cares they’re cheap and easy to backup / restore.

That said, this last time around I decided that it was time to upgrade, and I happen to have some spare parts laying around, including a spare case, so that’s exactly what I did.

New system is still running Kubuntu, however upgraded to 14.10, I salvaged the video card and the 4GB of ram, and added another 4GB of ram with new motherboard and E8500 CPU. Additionally the new case and better (and quieter) cooling as well as more room, and of course, the major bonus, I tossed an SSD in for the system disk.

I’ve thought about running Kodi on this system for a while but haven’t had much time to configure it, I did leave myself plenty of room on the SSD for additional operating system partitions in the future.

Dell XPS 13 (9333) with A05 BIOS

So over the last few weeks I’ve been trying to sort out the final problems with my XPS 13. The last, and most annoying problem I’ve seen is the frequent and seemingly random lockups on suspend.

This bothers me a lot because it effectively means I can’t just close the lid on the laptop and toss it in a bag and go.

Based on what I’ve observed the issue seems to be solidly within the A05 BIOS. From my understanding, speaking with Dell Pro Support, this BIOS revision is beta, and only available to those users who have either received new systems after October 15th 2014, or had their motherboards replaced to address the coil whine problem.

The issue it self appears to relate closely to the power state the laptop is in, and the fact that the OS may change the power state when plugged in, to something not regonized or supported by the BIOS at the time.

So effectively you can suspend and resume reliably, so long as you don’t have the power plug, plugged in while the system is running. Of that, it seems to take some time (i.e. secondary power state change) for it to reliably trigger the hang when suspending into memory.

I can’t seem to determine much past that as the OS has handed off duties to the BIOS and it’s the BIOS which fails to bring the system down to sleep.

If you want to comment with Dell on this, I have an active thread here:

My Dell XPS 13 `sputnik’ Linux configuration

So, back in September I decided to purchase a new laptop, the one I decided on was the Dell XPS 13 Sputnik (9333). This is an Intel Core i7, 8GB RAM, 256GB mSATA based laptop which ships with Ubuntu 12.04 LTS.


My first thoughts on this laptop are positive, in general the build quality is high, screen looks great, as fast (very fast for such a thin ultrabook). That said the unit initially shipped to me suffered from the dreaded coil whine issue discussed on this thread, as well as a few other issues which, with the help of others I’ve been able to solve pretty quickly.

There’s a great blog which details most of the things which you need to take care of to get this system working well. That said there’s a few more things that you’ll need to do. If you’re like me, you’ve probably blown away the stock OS, and installed something more recent.

First thing I did was modify the script on the xps13 blog:

---      2014-10-15 22:20:26.592234453 -0600
+++ /usr/local/bin/       2014-10-11 23:37:33.150956572 -0600
@@ -85,15 +85,17 @@
 # Check idle time
-. /usr/share/acpi-support/power-funcs
-currIdleTime=`su $XUSER -c "dbus-send --session --dest=org.freedesktop.ScreenSaver \
-                            --type=method_call --print-reply --reply-timeout=1000 \
-                            /ScreenSaver org.freedesktop.ScreenSaver.GetSessionIdleTime \
-                            | grep uint32 | sed 's:.*uint32 \+\([0-9]\+\).*:\1:g'"`
-if [ $currIdleTime -gt $idleTimeout ]; then
-    echo "Timeout expired, ignoring ambient light changes"
-    exit 0
+if [ -f /usr/share/acpi-support/power-funcs ]; then
+       . /usr/share/acpi-support/power-funcs
+       getXuser
+       currIdleTime=`su $XUSER -c "dbus-send --session --dest=org.freedesktop.ScreenSaver \
+                                   --type=method_call --print-reply --reply-timeout=1000 \
+                                   /ScreenSaver org.freedesktop.ScreenSaver.GetSessionIdleTime \
+                                   | grep uint32 | sed 's:.*uint32 \+\([0-9]\+\).*:\1:g'"`
+       if [ $currIdleTime -gt $idleTimeout ]; then
+           echo "Timeout expired, ignoring ambient light changes"
+           exit 0
+       fi
 # Use xbacklight if the given path is wrong
@@ -115,6 +117,7 @@
         for i in `seq $curr $incr $target`; do
             echo $i > $backlightPath
+            echo $i > /tmp/als_state
             sleep $timeout
@@ -129,4 +132,4 @@
\ No newline at end of file

Effectively the patch above simply checks to see if power-funcs  actually exists.

Next I upgraded to 3.17 kernel. This solved problems with white noise, as well as wireless stability issues.

After that you’ll want to disable power features on the mSATA SSD by creating /etc/pm/config.d/hook_blacklist.conf and adding the following line:

HOOK_BLACKLIST="95hdparm-apm sata_alpm"


After some discovery, I found that not all power control features are here. A large number of them are stored in /etc/power.d/10-power_script. you’ll want to patch this file to omit the features which will adversely affect the SSD

--- power.d/10-power_script     2014-10-18 15:34:15.820269065 -0600
+++ power.d/10-power_script     2014-10-18 15:33:08.976265876 -0600
@@ -41,16 +41,16 @@
 #echo $GOVERNOR > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
 # Enable SATA link power Managmenet for host0
-echo $SATA > /sys/class/scsi_host/host0/link_power_management_policy
+#echo $SATA > /sys/class/scsi_host/host0/link_power_management_policy
 # Enable SATA link power Managmenet for host1
-echo $SATA > /sys/class/scsi_host/host1/link_power_management_policy
+#echo $SATA > /sys/class/scsi_host/host1/link_power_management_policy
 # Enable SATA link power Managmenet for host2 - it used to slow down keyboard typing
-echo $SATA > /sys/class/scsi_host/host2/link_power_management_policy
+#echo $SATA > /sys/class/scsi_host/host2/link_power_management_policy
 # Enable SATA link power Managmenet for host3
-echo $SATA > /sys/class/scsi_host/host3/link_power_management_policy
+#echo $SATA > /sys/class/scsi_host/host3/link_power_management_policy
 # Autosuspend for USB device Synaptics Large Touch Screen [SYNAPTICS]
 findPath 06cb 0af8
@@ -79,7 +79,7 @@
 echo $CONTROL > /sys/bus/pci/devices/0000:00:1f.3/power/control
 # Runtime PM for PCI Device Intel Corporation Lynx Point-LP SATA Controller 1 [AHCI mode]
-echo $CONTROL > /sys/bus/pci/devices/0000:00:1f.2/power/control
+#echo $CONTROL > /sys/bus/pci/devices/0000:00:1f.2/power/control
 # Runtime PM for PCI Device Intel Corporation Haswell-ULT Integrated Graphics Controller
 echo $CONTROL > /sys/bus/pci/devices/0000:00:02.0/power/control

Lastly, I had to upgrade xserver-xorg-video-intel to at least version 2.99.916 to ensure that resume would function correctly.

EeePC wireless performance

After updating my 1005PE with an Intel 6300 network card and additional antennas I wanted to see how fast a real world copy could be through wireless.

So I hopped on my internal file server and a large file

Intel 6300 speed test

9.88 MB/s or about 80 MBps through an SSL web host. Not bad…

The next few tests I’ll try will be lower level trials sourcing data from a memory disk.

EeePC upgrades

For a while now I’ve owned an older EeePC 1005PE.


I love the thing, running kubuntu 12.04 LTS it’s been a work horse for me. Recently I noticed that my wireless was becoming less reliable, plus it lacked 5GHz support which was a major bummer.

So I started digging around and discovered that these little laptops use a standard, half-height mini-PCIe wireless card. $40 later from Amazon Prime I had a new Intel 6300 and 2 extra internal antennas.

45 minutes later the new antennas and dual band wireless NIC were successfully installed. Kubuntu found the card and connected it directly to my network.

So far so good, better overall performance, less battery drain (slightly) and I can now see my lovely 5GHz router.

All around, this was a great upgrade and compliments the laptop nicely. Now if only I could upgrade the memory capacity beyond the 2GB limit!

Oh and for those of you wondering about wiring this particular card:

  1. white cable (main connector)
  2. black cable (aux connector)
  3. grey cable (middle connector for MIMO)