Author Archives: Hans Henrik

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!

Source:

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 >= 8.2.2.2993 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:

[Unit]
Description=BeyondTrust PBIS Service Manager
After=network.target

[Service]
Type=forking
EnvironmentFile=/opt/pbis/libexec/init-base.sh
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.
KillSignal=SIGCONT
PrivateTmp=true

[Install]
WantedBy=multi-user.target nss-lookup.target

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!

Source:

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
 /sys/bus/usb/devices/3-1/idProduct:0008

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

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

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

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_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
acpi_enforce_resources=lax"
GRUB_CMDLINE_LINUX=""

# 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 ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

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

# 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'
#GRUB_GFXMODE=640x480

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

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# 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"

to

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.

 

Sources:

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” (http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/). 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

wget http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/stable/syno-mvkw-bootstrap_1.2-7_arm.xsh
chmod 700 syno-mvkw-bootstrap_1.2-7_arm.xsh
sh syno-mvkw-bootstrap_1.2-7_arm.xsh

Edit the bootstrap.sh file

vi bootstrap.sh

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
#fi

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

Run bootstrap

sh bootstrap.sh

Reboot your diskstation

/opt/bin/ipkg update

/opt/bin/ipkg list

/opt/bin/ipkg install pkg

Set PATH

Add the following line to /etc/profile:

PATH=/opt/bin:/opt/sbin:$PATH

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:

#!/bin/sh

# 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
REAL_OPT_DIR=/volume1/@optware
fi

case "$1" in
    start)
        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
            fi  
        fi
    [ -x /opt/etc/rc.optware ] && /opt/etc/rc.optware
    ;;
    reconfig)
    true
    ;;
    stop)
        echo "Shutting down Optware."
    true
    ;;
    *)
        echo "Usage: $0 {start|stop|reconfig}"
        exit 1
esac

exit 0

(source: a working optware env)

Nvidia GTX 970 and HDMI Audio

Just bought my self a Asus GTX 970 and happily installed it.

Everything worked fine but I couldn’t get audio from the HDMI port to my receiver.
The only option I had was stereo and no sound from my speakers.

My previous card was an Asus 650 Ti Boost and it had no problems with 5.1 surround audio to my receiver. Actually there where the option of either sending it to the Display port or the HDMI port.

I also was using the latest 346.22 Nvidia driver from “xorg crack pushers” team.

So I was scratching my head for half a day until I remembered that there were some updates for Nvidia in the latest Linux kernels.

I checked the kernel version on my system and it was 3.13 on Ubuntu 14.04 LTS.

At kernel.org I found the latest kernel to be 18.1 and packages could be downloaded from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18.1-vivid

The new kernel was easy to install just follow the instructions at http://linuxg.net/how-to-install-kernel-3-18-1-on-ubuntu-15-04-ubuntu-14-10-ubuntu-14-04-and-derivatives

After a reboot was I able to set-up audio to use the HDMI port again.

It works!!!

For some time have I had problems running Kububtu and 3 monitors at the same time on a Nvidia card.

I solved by having each monitor running on each own xserver. That worked fine but certain things where not optimal.

I could only change display configuration by using Nvidia setting and I couldn’t disable the screen saver. Not a big problem but when I was watching TV suddenly I would miss a coal because of the screen saver.

I also have a Wacom tablet. It isn’t very often I use it but the other day there were a question at Ask Ububtu about pressure sensibility and I wanted to the answer question.
I just wanted to test if everything was working fine and to my surprise it was not.

Again I did the BIG investigation and hours went by. I could not the get pressure sensibility to work.

Even Krita wouldn’t work at all with the tablet.

So in the end I tried to remove (rename) the /etc/X11/xorg.conf file and reboot.

As the computer was rebooting I was getting grumpy because I suspected the X configuration was the problem and I could not get the 3 monitors to work at the same time.

But Kubuntu booted up, X started and everything looked normal, YES! It works now.
I Just had to goto the Diaplay and Monitor settings and configure the display order to my needs.

Was I one happy little boy and the grumpiness was gone 🙂

I suspect the problem is solved in KDE ver. 4.13.2

To install on Kubuntu add to the repository search:

ppa:kubuntu-ppa/backports

Or, from a command line:

sudo add-apt-repository ppa:kubuntu-ppa/backports

Then

sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade

Hope you will enjoy!

Upgradeing XBMCbuntu

I use XBMC as my entertainment center and had XBMCbuntu install on a ZBOX ID41.

The XBMCbuntu was based on an 12.10 version of ubuntu (maybe lubuntu).

As 12.10 was going out of support I couldn’t install XBMC 13.1 from the XBMC’s PPA. I had to compile it my self. I tried to compile but forgot some setting related to the ION chip set. Not at big success and I decided it was not worth the hassle to compile every time I need to update XBMC.

I decided to try lubuntu as it is a small distrio of Ubuntu.

I made an USB key and booted lubuntu from the USB key to see if everything looked fine and it didn’t seem to be problem to install lubuntu on the ID41.

From the desktop I installed lubuntu and to my big surprise it asked me if I wanted to upgrade from XBMCbuntu 12.10 to lubuntu 14.04.
What! That can’t be possible??? But let’s give it a try…

During the install everything was left at default except I enabled auto login to prevent having to login when I started the computer.

The only problem was when I typed in the computer name. Lubuntu notified that there was another computer with the same name. But as my DHCP server register all my devices so they get the same IP address when they start I knew it was just finding it self. After a reboot there wouldn’t be any problems.

I rebooted and lubuntu started up and to my big surprise everything worked fine.

I just had to add the XBMC repository (http://wiki.xbmc.org/index.php?title=Installing_XBMC_for_Linux) and then install XBMC.

The remote didn’t work and after installing LIRC everything was back to normal.

A logout and login to the XBMC desktop and my entertainment center was back to normal. You can select the XBMC desktop in top right corner at the login screen.

Well there was problems that need to be solved but it was the same problems I had with XBMCbuntu. One was the computer would not suspend but I will write about that in another post.