Sunday, 27 May 2018

Parrot 4 will not start LDM in Virtualbox

It seems that Parrot 4.0.1 does not contain a version of Virtualbox tools compatible with kernel 4.16. As a consequence, X will not start due to the lack of supported Kernel modules.

The fix, to install modules from the VirtualBox ISO, is detailed by Pavel at the following link:

Failed to start light display manager? - Community - Parrot Community:



When you obtain the failure message about lightdm, simply press ALT+F1 and log in there. then:
  • sudo apt-get update
  • sudo apt-get upgrade
  • sudo apt-get install build-essential module-assistant
  • sudo m-a prepare
Insert Guest Additions ISO
  • mount /media/cdrom
  • sudo sh /media/cdrom/VBoxLinuxAdditions.run
Reboot

Sunday, 11 March 2018

How to install VirtualBox Guest Additions in a Debian virtual machine - Unix & Linux Stack Exchange

How to install VirtualBox Guest Additions in a Debian virtual machine - Unix & Linux Stack Exchange:

For Debian 9, enable backports with contrib repository to /etc/apt/sources.list
  • deb http://ftp.uk.debian.org/debian stretch-backports main contrib

Then update and install:
  • sudo apt update
  • sudo apt install virtualbox-guest-utils virtualbox-guest-x11 virtualbox-guest-dkms dkms linux-headers-amd64 build-essential

'via Blog this'

Monday, 1 January 2018

Tuesday, 1 August 2017

Disable USB power saving for booting from USB

Having issues booting from USB connected SSD and disabling this in the Linux Kernal seems to solve the issues of the disk becoming unavailable.
Edit /etc/default/grub and change the following line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1"
Update the config with: sudo update-grub
Reboot
Thanks to this post.

Chromium Hardware Acceleration Issues on Mint 18,2

I'm currently testing Mint18.2 and have run into a number of issues with Chrome. It initially started with corruption issues in Youtube.
After investigation I discovered that the hardware acceleration had been disabled. By adding the following switches to the 'exec' lines in /opt/google/chrome/google-chrome I was able to force all the acceleration options on:

  • --enable-native-gpu-memory-buffers
  • --enable-zero-copy
  • --disable-gpu-driver-bug-workarounds
  • --ignore-gpu-blacklist
  • --enable-gpu-rasterization
  • --enable-checker-imaging
I added these to the file by editing it with root (sudo) options. I suspect the file will be overwritten on update. There seems to be an environment variable for chromium which allows you to set command line options to pass to chromium without editing files, but I can't tell if this works for Chrome yet.