How to mount an Xbox formatted drive on Ubuntu

When I finally get a PCIe IDE adapter that works, this is gonna come in handy: How to mount an Xbox formatted drive on Ubuntu.

The IDE adapter that I have is this one, but it reports all disks as damaged (and they’re not). I think maybe it’s too new for the drives maybe? Speaking a newer version of the ATA protocol? I have no idea really.

Install Docker Engine on Ubuntu

Reading about how to Install Docker Engine on Ubuntu. I suppose it’s about time.

Thu Nov 11 20:38:18 [bash:5.0.17 jobs:0 error:0]
# docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
2db29710123e: Pull complete
Digest: sha256:cc15c5b292d8525effc0f89cb299f1804f3a725c8d05e158653a563f15e4f685
Status: Downloaded newer image for hello-world:latest

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:

For more examples and ideas, visit:

Installing Kubuntu

So basically I want to run KDE Plasma under Ubuntu and this can be called Kubuntu.

This article is a little bit cargo-clutish. I.e. “I did this and it seemed to work.” and “I don’t do this because it didn’t seem to work.”

I have a pretty heavy reliance on Salt Stack for system configuration. My salt config is all built around Ubuntu 18.04 LTS.

When I need to install a Kubuntu desktop, this is how I do it:

  1. install Ubuntu Server 18.04 LTS from live installer
  2. apt update && apt dist-upgrade && apt autoremove && reboot
  3. apt install kubuntu-desktop && reboot
  4. apt install virtualbox-guest-dkms virtualbox-guest-utils virtualbox-guest-x11 && reboot
  5. apt install salt-minion
  6. vim /etc/salt/minion_id
  7. vim /etc/salt/minion.d/minion.conf
    • master:
  8. service salt-minion restart
  9. salt-call state.highstate

Note that if your Kubuntu install is a VirtualBox guest you need to start it with a normal start if you want the shared clipboard to work. If you start headless or detachable the shared clipboard will not work (in my experience).

If your Kubuntu install is not a VirtualBox guest you can skip the virtualbox-guest-* package installation above.

Shared clipboard for Ubuntu 18.04 guest in Ubutnu 18.04 host under VirtualBox 6.0

My shared clipboard wasn’t working for my Ubuntu 18.04 guests running on my Ubutnu 18.04 host under VirtualBox 6.0.

To fix first make sure that the shared clipboard is enabled in VirtualBox for the VM. The setting for that is under General -> Advanced -> Shared Clipboard.

Then try running these commands in the guest:

  • sudo apt install virtualbox-guest-dkms virtualbox-guest-utils virtualbox-guest-x11
  • sudo reboot

These steps (or something similar) got the shared clipboard working for me. Hooray!

Note that these instructions will vary if you’re running a HWE kernel.


Today I was reading How to Install The Latest AMD Radeon Drivers on Ubuntu 18.04 Bionic Beaver Linux wherein I read that “[enabling] DRI3 will increase graphical performance with the AMDGPU drivers”. You can read about DRI3 but the bottom line was to add the following to your /etc/X11/xorg.conf file:

Section "Device"
  Identifier "AMDGPU"
  Driver "amdgpu"
  Option "AccelMethod" "glamor"
  Option "DRI" "3"


I had a system which failed to boot. The last lines printed to the screen, which were not relevant to the problem, were:

 [19.957783] async_tx: api initialized (async)
 [20.899732] Btrfs loaded, crc32c=crc32c-intel

Then a little bit later:

 [32.469926] random: crng init done
 [32.470551] random: 7 urandom warning(s) missed due to ratelimiting

The full problem description is here. And the solution is here (careful about the typo on that page, the only relevant setting is GRUB_CMDLINE_LINUX_DEFAULT).

Basically the problem was a bogus GRUB_CMDLINE_LINUX_DEFAULT setting in /etc/default/grub applied by my salt config. I fixed the setting which fixed the issue.