Sunday, 28 August 2016

Crappy Netflix Playback? Here’s How to Test Your Streaming Speed | WIRED

Google Chrome will play NetFlix on Linux but Chromium will not.

Linux is therefore limited to 720 and not 1080 as it doesn't run crappy IE or Edge.



Crappy Netflix Playback? Here’s How to Test Your Streaming Speed | WIRED:



'via Blog this'

Screen tearing problem on Cub Linux

I've been testing Cub Linux RC1 (based upon Ubuntu 14.04) and had some problems with video playback. After some research I found that editing ~/.config/compton.conf and changing the following lines removed the issue:

Replace backend = "xrender"; with backend = "glx";

Replace vsync = "none"; with vsync = "opengl";

Note: This works fine on the Integrated Intel HD5500 graphics but still produces tearing if I switch to the Radeon Discrete graphics. Not sure if I can find a setting that works with both... Thoughts?

How to force Linux appliaction to run using discrete graphics card

On a laptop with integrated (Intel HD5500) and discrete (AMD Radeon R7 M265) the applications startup using the integrated graphics by default. setting the variable DRI_PRIME=1 causes the applications to use the discrete graphics instead.

e.g.

"glmark2" runs on the integrated graphics vs "DRI_PRIME=1 glmark2" runs on the discrete graphics.
"chromium-browser" runs on the integrated graphics vs "DRI_PRIME=1 chromium-browser" runs on the discrete graphics.

You can also force the use of radeon graphics by the use of a grub flag.

ati - Very Low Temperature Reading for graphics driver using lm-sensors - Ask Ubuntu:



'via Blog this'

Monday, 22 August 2016

How to shrink a dynamically-expanding guest virtualbox image | dantwining.co.uk

How to shrink a dynamically-expanding guest virtualbox image | dantwining.co.uk:



'via Blog this'



This worked for me on Debian Testing which has a habit of increasing in size purely due to the number of updates required.



I first tried compacting the disk without zeroing the space and the disk size went down from 12.485GB to 12.476, a massive 9MB saving. ;)



I then followed the procedure in the post modified slightly for Debian:



  1. Install zerofree using 'sudo apt install zerofree'
  2. Power off the virtual system using 'sudo poweroff'
  3. Boot the system holding left shift
  4. Select advanced options
  5. Select recovery mode using the latest installed kernel
  6. Identify your root filesystem (and any other filesystems you want to compact) using 'mount'; take a note of the filesystem type they are using as well
  7. 'service rsyslog stop'
  8. 'service network-manager stop'
  9. Run the following two commands for all the required filesystems:
    1. 'mount -n -o remount,ro -t ext4 /dev/sda1 /'
    2. 'zerofree -v /dev/sda1'
    3. Replace ext3 with the required filesystem type, / with the required mount point, and /dev/sda1 with the required device
  10. 'poweroff'
  11. Compact the files system using cmd prompt if on Windows:
    1. 'cmd' (run as administrator)
    2. 'C:'
    3. 'cd "\Program Files\Oracle\VirtualBox"'
    4. 'vboxmanage modifyhd "D:\VMs\Debian Testing\Debian Testing.vdi"' (replace the .vdi path with our own disk image)
My Debian testing disk image was then reduced to 7.333GB saving a further 5.143GB or 41% of the total space.

Monday, 4 July 2016

Creating a tiered virtual disk in Windows Server 2016 VM using VirtualBox as hypervisor

I've been playing with Windows Server 2016 as a VM inside VirtualBox, but despite VirtualBox being able to mark virtual disks as an SSD disk, I was unable to create any tiered Storage Spaces inside the guest VM.


The VM disks (hosted as virtual disks on an actual SSD) were marked as SSD correctly:



























Turns out that the SSD disks weren't the problem, it was the HDD which were coming up as UnSpecified:

Get-PhysicalDisk | select FriendlyName, UniqueId, MediaType, Size

FriendlyName  UniqueId                               MediaType           Size
------------  --------                               ---------           ----
VBOX HARDDISK {01c1a62b-e1d6-1910-b251-09f3ae1b2047} UnSpecified 214748364800
VBOX HARDDISK {12fcf70b-b805-183a-f1a8-103d6b91ba70} UnSpecified  34359738368
VBOX HARDDISK {31b25faa-db05-490a-7acd-a8927a2b569f} UnSpecified 214748364800
VBOX HARDDISK {45fc2705-9a13-1afc-a554-0ded23d9e78b} UnSpecified 214748364800
VBOX HARDDISK {50642166-ca99-47ce-2f87-b5b4f2c19254} SSD          21474836480
VBOX HARDDISK {57b897e4-f98a-3330-dbc2-6a5ab6749742} SSD          21474836480
VBOX HARDDISK {769a2aa9-a289-7627-24ef-6b3a2fcff2bb} SSD          21474836480
VBOX HARDDISK {a1a9e55d-68b9-7eb3-11dd-6348bb837642} UnSpecified 214748364800
VBOX HARDDISK {d98baa0d-b0df-74ea-ac87-d107998e79ed} SSD          21474836480


The commands below won't work if the disks are still in the primordial pool, so you need to use either the GUI or PowerShell to create the pool first. Once that is done you can edit change the FriendlyName and the MediaType using Powershell.


I was able to rename and reclassify the HDD's like so:

Set-PhysicalDisk -UniqueId '{01c1a62b-e1d6-1910-b251-09f3ae1b2047}' -NewFriendlyName HDD1 -MediaType HDD
Set-PhysicalDisk -UniqueId '{31b25faa-db05-490a-7acd-a8927a2b569f}' -NewFriendlyName HDD2 -MediaType HDD
Set-PhysicalDisk -UniqueId '{45fc2705-9a13-1afc-a554-0ded23d9e78b}' -NewFriendlyName HDD3 -MediaType HDD
Set-PhysicalDisk -UniqueId '{a1a9e55d-68b9-7eb3-11dd-6348bb837642}' -NewFriendlyName HDD4 -MediaType HDD


I was also able to rename the SSD devices to make them more obvious:

Set-PhysicalDisk -UniqueId '{50642166-ca99-47ce-2f87-b5b4f2c19254}' -NewFriendlyName SDD1
Set-PhysicalDisk -UniqueId '{57b897e4-f98a-3330-dbc2-6a5ab6749742}' -NewFriendlyName SDD2
Set-PhysicalDisk -UniqueId '{769a2aa9-a289-7627-24ef-6b3a2fcff2bb}' -NewFriendlyName SDD3
Set-PhysicalDisk -UniqueId '{d98baa0d-b0df-74ea-ac87-d107998e79ed}' -NewFriendlyName SDD4


The disks were now identified correctly and I could create my tiered virtual disks:

FriendlyName  UniqueId                               MediaType           Size
------------  --------                               ---------           ----
HDD1          {01c1a62b-e1d6-1910-b251-09f3ae1b2047} HDD         214748364800
VBOX HARDDISK {12fcf70b-b805-183a-f1a8-103d6b91ba70} UnSpecified  34359738368
HDD2          {31b25faa-db05-490a-7acd-a8927a2b569f} HDD         214748364800
HDD3          {45fc2705-9a13-1afc-a554-0ded23d9e78b} HDD         214748364800
SDD1          {50642166-ca99-47ce-2f87-b5b4f2c19254} SSD          21474836480
SDD2          {57b897e4-f98a-3330-dbc2-6a5ab6749742} SSD          21474836480
SDD3          {769a2aa9-a289-7627-24ef-6b3a2fcff2bb} SSD          21474836480
HDD4          {a1a9e55d-68b9-7eb3-11dd-6348bb837642} HDD         214748364800
SDD4          {d98baa0d-b0df-74ea-ac87-d107998e79ed} SSD          21474836480


Everything looked good in the GUI too:



Friday, 24 June 2016

Google Chrome on Ubuntu 16.04

On reinstalling this today onto a stock install of Ubuntu 16.04, I had a couple of unmet dependencies. I sorted it out with:
sudo apt install libappindicator1 libindicator7

Wednesday, 8 June 2016

renew Openvas 8 Certificates

This happens on a yearly basis and always left my scratching my head:

openvas-mkcert -q -f 'Refreshes the server certificate for a year
openvas-mkcert-client -n -i 'Refresahes the client certificate for a year
reboot