At the edge of tweaking
Advertisement
I am a big fan of Arch Linux and I use it everywhere - as my main OS, at all my computers and even on SoCs like Banana Pro. Recently I installed the Arch Linux image on my Banana Pro and faced an issue that every time I would install a package with pacman, it produced the following error:
error: command failed to execute correctly
Here is a fix to get rid of this message.
Banana Pro is a card-sized low-power single board ARM-based computer (SoC) which can run Android, Linux distros and other systems. In this article, we will see how to change the default CPU overclocking settings for the Banana Pro board. As a result, it will be possible to get a fine-tuned CPU clock and reduced chip temperature. Let's see how.
If you own a SoC (System-on-a-chip) named Banana Pro, you might face the issue that most Linux distros available for this board do not respect the display resolution that you set in the uEnv.txt file. Especially in case you are using some HDMI -> VGA converter, this resolution-related issue can be expected. Here is a working solution to fix it.
Recently, I built a media centre device using Raspberry Pi 2. I am using Arch Linux + Kodi as its software. When plugged to my TV, I noticed the very small fonts that Kodi is using for the controls and information shown on the screen. While I don't care that much about the controls, (because I use my smartphone to control Kodi), the file list font size was terribly small. It was hard to read anything on the TV screen. Here is a very simple way to increase the file list font size in Kodi. Using the method described below, you can change the font size of any element in Kodi's user interface.
During WinHEC (Windows Hardware Engineering Conference), Microsoft announced that PCs with Windows 10 and UEFI must ship with Secure Boot enabled by default. Secure Boot is a feature to protect PCs from malware which can infect the OS boot loader to load itself at the earliest stage of booting. What Secure Boot does it allows only a Microsoft-verified / signed boot loader to be used. So boot loaders that are not signed can no longer boot other operating systems like Linux. With Windows 8, Microsoft had not mandated that Secure Boot be enabled by default. With Windows 10, now hardware manufacturers (OEMs) must enable it by default if they want Windows logo certification, and it is up to the OEM to decide whether they even want to give you the ability to disable Secure Boot. This is an extremely alarming situation as you can potentially be locked out of using other operating systems thanks to Microsoft. Here is what you should do to avoid this.
Today I will write a Linux article for a change. Windows fans, don't worry I am not ditching Windows. As you know I use Linux too alongside Windows to keep an eye on the best distros and best window managers. Fluxbox is one such awesome window manager for Linux, my favorite one. It is extremely lightweight, blazingly fast, easily configurable and very feature rich. You can use it without any Desktop Environment and still manage windows comfortably and productively. By default, Fluxbox places newly opened windows ordered in a row until the screen width allows them. I did not find this behavior very useful and would like to share with you how it is possible to place newly opened Fluxbox windows at the center of the screen.
Although I use Windows as well and our blog has primarily been about Windows so far, I also use Linux regularly. I just installed Debian Jessie on my work PC and noticed that none of the shutdown actions work from the GUI. The Desktop Environment I've installed is Mate, the fork of the good old Gnome 2. Every time I try to execute some shutdown action, the system requests for the root password. In this article, I would like to share with you an easy way to get it working and get rid of the root password request.
