Category Archives: Uncategorized

Advarsel: DIBO BARF hundefoder

Dette er an advarsel til andre hundeejere som benytter DIBO BARF hundefoder.

2 gange har jeg fundet glasskår i foder fra DIBO.

Fundet er sket i 2 uafhængige køb af foderet og det er derfor ikke bare en tilfældighed.

Undskyldningen fra forhandleren er, at en ko har spist glas, hvilket kan tænkes, men at en ko spiser glas 2 gange og det findes i fodret i 2 uafhængige købe finder jeg er usandsynligt.

Jeg tror at der sket et uheld under produktionen og at de har været ligeglad og brugt foderet i stedet for at smide det ud.

Jeg har derfor valgt at holde op med at fodre min hund med DIBO BARF hundefoder og jeg vil opfordre dig til at holder dig langt væk fra det produkt.

Aftershot Pro plugins

Here is the plugins I compiled out of Spoilerheads source code:

Wavelet Sharpen 64-bit
Wavelet Sharpen 32-bit

Wavelet Denoise 64-bit
Wavelet Denoise 32-bit

Silicon Bonk 64-bit
Silicon Bonk 32-bit

Grain 64-bit
Grain 32-bit

Gelatin 64-bit
Gelatin 32-bit

FatToni 64-bit
FatToni 32-bit

Angy 64-bit
Angy 32-bit

Please, visit Spoilerhead, Thanks him for his great work and donate to keep him working…

Have a look at your router before you make changes

I have always been able to watch a movie using kodi, downloading big files and ripping BD on the same time.

No problems, copy 6-8 movies at the same time over to my Synology box while watching tv with Kodi.

After I upgrade to Kubuntu 15.04 this was not possible anymore.
I was crushed by the fact I could only do 1 thing at the time.

First it was Kubuntu fault, tried all kinds of settings but no luck. No lost network packages.

It was until my daugther came to me and said: “Dad, Harry Potter, is chops and will not run smooth”. This was while I was downloading some big files.

Well, then it can’t be Kubuntu!!!

After moving wires around a bit I found out it was a switch make troubles.
A restart of the switch solved the problem.

So the next time I have network problems, the first thing I will be doing is:

RESTART the network hardware!!!

Installing Kubuntu 15.04 with a Nvidia GTX 970/980 on board.

I really had some problems installing Kubuntu on my new computer.

When I tried to boot up the LiveCD I was presented a black screen with a lot of output from the Nouveau display driver (you might a complete black screen with a blinking cursor).


After some investigation I found out Grub had a option called nomodeset to prevent the Nouveau driver to start.

But HOW do I set this option when there is no menu or anyway to stop the boot up?

The only way I could figure out was to booth my LiveCD USB stick in UEFI mode and pressing F8 just after the computer bios was loaded.

There I was presented with option to

*Start Kubuntu
OEM install (for manufactorers)
Check disc for defects.

By pressing the ‘e’ key on the keyboard each menu item is editable.

Edit the line starting with "linux /casper..." and add the nomodeset somewhere, press F10 will start the LiveCD (see above gallery picture number 3).

After this change would the LiveCD boot up and I could install Kubuntu.

I had was the same problem with the Nouveau driver during boot up after the installation.
To solve this I had to install the Nvidia driver (I use the one from Xorg Edgers).

Press F8 just after the computer bios has loaded during bootup.

In the boot menu select the Start Kubuntu recover.
The will startup the recover menu.

In the recovery menu select: network.

This make sure you can download the new driver for the Nvidia GPU but it also make the hard disc writable. When starting up in recovery mode is the hard disc mounted as read only and nothing can be installed or modified.

Next start a shell as root select: root.

This startup a shell is where drivers and other configuration can be executed.
In the shell type:

$ apt-add-repository ppa:xorg-edgers/ppa

You will have to agree all kind of dangerous stuff that you are playing with (Its really not, its only a driver).

Next you can install the driver. At the moment is the nvidia-349 the latest so type:

$ apt-get install nvidia-349

The driver installs and when finished type

$ exit

This will return you to the recovery menu where you can continue the starting Kubuntu.

Select Continue booting Kubuntu.

When Kubuntu have started successful, reboot Kubuntu to make sure the system starts up normally. It would be a waste of time configuring everything and finding out the system will not start.

Have fun!


While we are waiting for Beyond Trust…

If you are using Pbis-open to connect to the Windows AD and you have upgraded to Ubuntu 15.04 you will have noticed that Pbis-open >= will not start the service lwsmd.

The reason is the service environment on Ubuntu 15.04 have switched to systemd.

Systemd uses a completely different concept for handling services so the package is not compatible.

I was saved by the user kavirondo from Ask Ubuntu, he/she made this instruction:

You need to create a systemd unit file for this service, and then enable it. The following worked for me on Ubuntu 15.04 (upgraded from 14.04) with PBIS 8.2.2.

Create the file lwsmd.service in /lib/systemd/system like this:

nano /lib/systemd/system/lwsmd.service

Here are the contents (paste this in to the file you created above) (taken from a redhat one) so thanks to them:

Description=BeyondTrust PBIS Service Manager

ExecStart=/opt/pbis/sbin/lwsmd --start-as-daemon
ExecReload=/opt/pbis/bin/lwsm refresh
ExecStop=/opt/pbis/bin/lwsm shutdown
# We want systemd to give lwsmd some time to finish gracefully, but still want
# it to kill lwsmd after TimeoutStopSec if something went wrong during the
# graceful stop. Normally, Systemd sends SIGTERM signal right after the
# ExecStop, which would kill lwsmd. We are sending useless SIGCONT here to give
# lwsmd time to finish.


Once this is done, make a symlink to this file in /etc/systemd/system:

cd /etc/systemd/system
ln -s /lib/systemd/system/lwsmd.service

At this point you should be able to type:

service lwsmd status

and see that the service exists and is enabled.

Then typing:

service lwsmd start

should start it up and have pbis working as expected.

Now to make it work at boot time. Enable the service with this command:

systemctl enable lwsmd.service

It should give some feedback about creating some symlinks.

Then reboot your comp and all should be working.

I hope it was clear enough, and please forgive any typos… Good luck!


Kodi, MCE Remote and Ubuntu

I have always had problems with wakeup of my media PC’s after a suspend or hibernation using my MCE (Microsoft media center) remote.

The problem was solved by enabling wakeup on the USB bus device. On some of my devices I also had to enable port on the ACPI (Advanced Configuration and Power Interface). The grub bootloader parameters might also need some changes.

The first thing to do is finding out which usb port Infrared reciever is connected.

lsusb will list your attached usb devices:

$ lsusb
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 005: ID 046d:c71f Logitech, Inc. diNovo Mini Wireless Keyboard
 Bus 003 Device 004: ID 046d:c71e Logitech, Inc.
 Bus 003 Device 003: ID 046d:0b07 Logitech, Inc.
 Bus 003 Device 002: ID 1784:0008 TopSeed Technology Corp. eHome Infrared Transceiver
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

The bold line of text is my usb ir receiver. Use the device id (0008 in my case) with the following command to find your device in /sys/bus/usb/devices

$ grep 0008 /sys/bus/usb/devices/*/idProduct

Now use that location to check if wakeup from the device is enabled with:

$ cat /sys/bus/usb/devices/3-1/power/wakeup

The following command will change this setting to enabled:

$ sudo sh -c 'echo "enabled" > /sys/bus/usb/devices/3-1/power/wakeup'

This setting will be reset on boot so to enable it on every boot you have to add the line to your /etc/rc.local file. You must be root to update the rc.local file.

$ sudo nano /etc/rc.local

and add the below below line before exit(0):

echo enabled > /sys/bus/usb/devices/3-1/power/wakeup

Save with <Ctrl>o and exit with <Ctrl x>.

Make sure /etc/rc.local is executable with the command

$ sudo chmod +x /etc/rc.local

The next is the ACPI needs to up updated as well. First inspect the ACPI wakeup configuration:

$ cat /proc/acpi/wakeup 
Device  S-state   Status   Sysfs node
PCI0      S5    *disabled  no-bus:pci0000:00
PEX0      S5    *disabled  pci:0000:00:1c.0
PEX1      S5    *disabled
PEX2      S5    *disabled
PEX3      S5    *disabled  pci:0000:00:1c.3
PEX4      S5    *disabled  pci:0000:00:1c.4
PEX5      S5    *disabled
HUB0      S5    *disabled  pci:0000:00:1e.0
USB0      S3    *disabled   pci:0000:00:1d.0
USB1      S3    *enabled   pci:0000:00:1d.1
USB2      S3    *disabled   pci:0000:00:1d.2
USB3      S3    *enabled   pci:0000:00:1a.0
USB4      S3    *enabled   pci:0000:00:1a.1
USB5      S3    *enabled   pci:0000:00:1a.2
USBE      S3    *enabled   pci:0000:00:1d.7
USE2      S3    *disabled   pci:0000:00:1a.7
AZAL      S5    *disabled

As you can see is USB0,USB2 and USE3 not enabled. For you is might be different.
I added the below lines  as root to rc.local before exit(0):

$ sudo nano /etc/rc.local

The lines add is different to what others recommend. This is because you cat switch enable and disable by executing the echo  “USB0” >   /proc/acpi/wakeup twice.

status=`cat /proc/acpi/wakeup | grep "USB0" | awk {'print $3}'`
if [ "$status" = "disabled" -o "$status" = "*disabled" ]; then
      echo "USB0" > /proc/acpi/wakeup
status=`cat /proc/acpi/wakeup | grep "USB2" | awk {'print $3}'`
if [ "$status" = "disabled" -o "$status" = "*disabled" ]; then
      echo "USB2" > /proc/acpi/wakeup
status=`cat /proc/acpi/wakeup | grep "USE2" | awk {'print $3}'`
if [ "$status" = "disabled" -o "$status" = "*disabled" ]; then
      echo "USE2" > /proc/acpi/wakeup

The last thing was changing the grub startup paramerters.

$ cat /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)

# Uncomment to disable graphical terminal (grub-pc only)

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux

# Uncomment to disable generation of recovery mode menu entries

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

You will have to change the GRUB_CMDLINE_LINUX_DEFAULT (marked bold).

$ sudo nano /etc/default/grub

and change



GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1 acpi_enforce_resources=lax"

At last you will have to update grub:

$ sudo update-grub

Reboot and test.

Enjoy (some of) your suspend problems is over.



Bootstrap DS414 on DSM 5.0

Install ipkg on a ds414 DSM 5

Actually there is no xsh bootstrap for the ds414 (Marvell Armada XP armv7l) although the existing Marvell Kirkwood mv6281 binaries “are ~ compatible” ( So this is a small guide to setup manually the optware environment, which based partly on trepmag’s guide – many thanks.

Create optware root directory

$ mkdir /volume1/@optware
$ mkdir /opt
$ mount -o bind /volume1/@optware /opt

chmod 700 syno-mvkw-bootstrap_1.2-7_arm.xsh
sh syno-mvkw-bootstrap_1.2-7_arm.xsh

Edit the file


disable these lines by adding the # as line prefix

#if [ -e "$REAL_OPT_DIR" ] ; then
#    echo "Backup your configuration settings, then type:"
#    echo "  rm -rf $REAL_OPT_DIR"
#    echo "  rm -rf /usr/lib/ipkg"
#    echo "This will remove all existing optware packages."
#    echo
#    echo "You must *reboot* and then restart the bootstrap script."
#    exit 1

#if ! grep Feroceon-KW /proc/cpuinfo >/dev/null 2>&1; then
#    echo "Error: CPU not Marvell Kirkwood, probably wrong bootstrap.xsh"
#    exit 3

Run bootstrap


Reboot your diskstation

/opt/bin/ipkg update

/opt/bin/ipkg list

/opt/bin/ipkg install pkg


Add the following line to /etc/profile:


Create init scripts

The following steps will allow to automatically bind the /volume1/@optware directory to /opt and trigger the /opt/etc/init.d/* scripts.

Create the /etc/rc.local file (chmod 755) and insert:


# Optware setup
[ -x /etc/rc.optware ] && /etc/rc.optware start

Create the /etc/rc.optware file (chmod 755) and insert:

#! /bin/sh

if test -z "${REAL_OPT_DIR}"; then
# next line to be replaced according to OPTWARE_TARGET

case "$1" in
        echo "Starting Optware."
        if test -n "${REAL_OPT_DIR}"; then
            if ! grep ' /opt ' /proc/mounts >/dev/null 2>&1 ; then
                mkdir -p /opt
                mount -o bind ${REAL_OPT_DIR} /opt
    [ -x /opt/etc/rc.optware ] && /opt/etc/rc.optware
        echo "Shutting down Optware."
        echo "Usage: $0 {start|stop|reconfig}"
        exit 1

exit 0

(source: a working optware env)