Changes
Outdated. See [[AMD: Installing Linux Mint 19]]
== Prepare installation media ==
* A USB DVD-ROM drive or a USB Flash drive of at least 2GB should be used as installation media
* Download [http://www.linuxmint.com/edition.php?id=174 190 Linux Mint 17 .2 "RebeccaRafaela" - MATE Cinnamon (64-bit)"]
* For installation with a USB DVD-ROM - flash the downloaded image directly onto a DVD
* For installation with a USB Flash drive, please follow [http://community.linuxmint.com/tutorial/view/744 How to install Linux Mint via USB] tutorial
== ATI Catalyst video driver ==
* fglrx is a proprietary ATI Catalyst video driver that provides XvBA (X-video Bitstream Acceleration) support.
* '''WARNING!!!''' fglrx driver has been updated on 2015-05-19, from version 13.350 to 15.200. There is a bug or some incompatibility in the new package. Please blacklist new version until Ubuntu or ATI will release the fix. Create file /etc/apt/preferences.d/fglrx.13.350.pref
Package: fglrx*
Pin-Priority: 1001
* Install fglrx driver and other required utilities with the command below:
$ sudo apt-get update $ sudo apt-get install fglrx-updates fglrx-amdcccle-updates xvba-va-driver vainfo
* Note: system reboot is required after the installation of the fglrx driver.
* Both of them use GPU accelerated video decoding and give excellent playback quality
* Both of them compatible with the most popular video formats
$ sudo add-apt-repository ppa:team-xbmc/ppa $ sudo apt-get update $ sudo apt-get install kodi vlc
* Kodi will support GPU accelerated video decoding out of the box
* In VLC you need to check Tools->Preferences->Input and Codecs->Use GPU accelerated decoding checkbox to take advantage of GPU accelerated video decoding
== Thermal monitoring ==
* Install tools for monitoring CPU and storage temperature
$ sudo apt-get install lm-sensors hddtemp
$ sensors
== Aggressive Link Power Management (ALPM) ==
* It's a mechanism where a SATA controller can put the disk into a very low power mode during periods of zero I/O activity and into an active power state when work needs to be done. Tests show that this can save around 0.4 Watts of some power and decrease mSATA average temperature.
* Create text file /etc/pm/power.d/sata_alpm
#!/bin/sh
done
* Make it executable
$ sudo chmod +x /etc/pm/power.d/sata_alpm* Reboot, check that SATA power management policy have has been changed
$ cat /sys/class/scsi_host/host*/link_power_management_policy
min_power
min_power
== Watchdog ==
* '''NOTE!''' Not supported in mainline Linux kernel yet. [[Fitlet:_Linux:_Kernel:_3.16 | Linux Kernel 3.16 for Fitlet]] should be installed to make this feature work
* The AMD FCH (Fusion Controller Hub) supports a user configurable watchdog
* Once the watchdog is enabled the system restarts once the timeout period elapses, in order to prevent it the user needs to either feed the watchdog or to disable it
$ sudo apt-get install watchdog
* Uncomment watchdog-device line in /etc/watchdog.conf
watchdog-device = /dev/watchdog
* Set responsible kernel module to sp5100_tco in /etc/default/watchdog
watchdog_module="sp5100_tco"
* By default the timeout value is 60 sec and the watchdog deamon feeds the watchdog every 10 sec
* As example you can simulate kernel panic (as root user):
$ echo c > /proc/sysrq-trigger
* As a result, the watchdog is not fed and the system will reboot after 60 sec
== GPIO ==
* '''NOTE!''' Not supported in mainline Linux kernel. [[Fitlet:_Linux:_Kernel:_3.16 | Linux Kernel 3.16 for Fitlet]] should be installed to make this feature work
* GPIO interface on fitlet consists of 9 GPIOs provided by AMD FCH (Fusion Controller Hub)
* The responsible kernel module is gpio_fch
* The kernel module uses the following pin naming convention:
{| cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
|+ GPIO connector pinout
|-
| Pin Number
| Color Code
| GPIO name
| Power domain
| HW source
| Notes
|-
| 1
| Brown
| GPIO89
| 3.3V
| SoC
|
|-
| 2
| Red
| GPIO132
| 3.3V
| SoC
|
|-
| 3
| Orange
| GPIO65
| 3.3V
| SoC
|
|-
| 4
| Yellow
| GPIO66
| 3.3V
| SoC
|
|-
| 5
| Green
| GPIO29
| 1.5V
| Soc
|
|-
| 6
| Blue
| I2C Clock
| 3.3V
| SoC
|
|-
| 7
| Purple
| I2C Data
| 3.3V
| SoC
|
|-
| 8
| Grey
| GPIO73
| 3.3V
| SoC
|
|-
| 9
| White
| GPIO27
| 1.5V
| SoC
|
|-
| 10
| Black
| GPIO28
| 1.5V
| SoC
|
|-
| 11
| Brown
| GPIO12
| 3.3V
| SoC
|
|-
| 12
| Red
| UART Rx
| 3.3V
| SuperIO
|
|-
| 13
| Orange
| UART Tx
| 3.3V
| SuperIO
|
|-
| 14
| Yellow
|
|
| GND
|
|}
* The GPIO sysfs interface allows users to manipulate any GPIO from userspace dynamically.
* A basic example of GPIO P-1 (Brown) usage (as root user):
$ modprobe fch_gpio
$ echo 89 > /sys/class/gpio/export
$ echo out > /sys/class/gpio/gpio89/direction
$ echo 1 > /sys/class/gpio/gpio89/value
## at this point voltage measuring on P-1 (Brown) should give 3.3V
$ echo 0 > /sys/class/gpio/gpio89/value
## at this point voltage measuring on P-1 (Brown) should give 0.0V
$ echo 89 > /sys/class/gpio/unexport
* The GPIO framework and GPIO sysfs interface are documented in https://www.kernel.org/doc/Documentation/gpio/gpio.txt
