SlaXBMC 14.2 is released

YES IT IS TRUE! The wait is officially over....and without further ado let me introduce you our latest creation

SlaXBMC 14.2

Yeap you've read it right. With the dawn of a sparkling new Slackware release and the evolution of our favorite multimedia application (XBMC) into the refined open source Home Theater software named KODI we are back with another SlaXBMC release powered by Slackware 14.2 and KODI 16.1 'Jarvis'.

As per the SlaXBMC tradition the installer allows the generation of two (out of the box) setup profiles (Minimal, Developer) where both upon completion provide a machine booting directly into KODI Jarvis and still maintain the capability to get back into the Desktop when exiting KODI. The footprint of the SlaXBMC Linux filesystem for each profile is as follows:

x86 - Developer < 4.2 GB

x86 - Minimal < 2.8 GB

x86_64 - Developer < 4.2 GB

x86_64 - Minimal < 2.8 GB

ARM RPi1 - Developer < 3.5 GB

ARM RPi1 - Minimal < 2.2 GB

ARM RPi23 - Developer < 3.5 GB

ARM RPi23 - Minimal < 2.2 GB

NOTE: Further improvement on the Minimal profile disk space is possible for those wishing to experiment a little more };)

All x86* flavors and profiles contain the latest Slackware, SlackwareARM software suite and come Firefox and NetSurf browser ready while the ARM* flavors contain only NetSurf and the usual overclock settings menu!

Last but not least the ISO images of the x86* flavor, pre-built ARM Raspberry Pi 1,2/3 images of both profiles and sources are available on our official SlaXBMC home (http://www.slackware.org.uk/slaxbmc/) and below.

P.S: This will be the last release of SlaXBMC supporting the Raspberry Pi 1 hardware due to the father OS (Slackware ARM) moving to a hard-float built supporting minimum armv7 targets (i.e Raspberry Pi 2 and above)

6 comments:

Anonymous
said...

Thanks for the work! I installed slaxbmc on a raspberry pi 2 that has the official 7" touchscreen. When kodi/xbmc starts it only shows the lower left corner of the kodi GUI the rest is cut off. Do you know how to work around this problem?

I'm afraid I don't have a touchscreen to check this out but if I were you I would try enabling and adjusting the overscan_left, overscan_right, overscan_top and overscan_bottom parameters in the boot sector config.txt file until the screen is centered. You could edit that at the desktop through the right click "System Tools -> Overclock Settings -> Manual" menu

Btw, I found a bug where the gui settings are not saved on exit (at least on my x86_64 ION), I will be posting a generic patch asap.

Thanks again for the feedback and please let me know if you finally manage to get the touchscreen working.