Getting Google Earth in Gentoo Linux to display Panoramio photos

Well, I decided to get Panoramio photos working in Google Earth installed using the hacked ebuild I posted in April 2014 (see my post Work-around if 64-bit Google Earth crashes in Gentoo Linux).

The modification devised by user amirpli (see Comment #9 in Gentoo Bugzilla Bug Report No. 490066) does not work in my case, as explained in detail in the above-mentioned April 2014 post. I believe this is because I am using the FGLRX video driver, as I have successfully applied amirpli‘s modification in an installation on a PC that has an Intel GPU.

Here is how I got Panoramio photos to display on my main laptop running the FGLRX driver, although my fix is yet another hack: I use 32-bit libraries downloaded from the Web. It works for me, though!

Background

I am running Google Earth 7.1.2.2041 installed from a local overlay (see my above-mentioned April 2014 post) in KDE 4.14.3 under Gentoo Linux ~amd64 with the 3.17.1-gentoo-r1 kernel and FGLRX driver:

# eix ati-drivers
[I] x11-drivers/ati-drivers
     Available versions:
     (legacy) 13.1_pre897^td
     (1)    13.4^td 13.9^td 13.12^td 14.4_p1^td (~)14.6_beta2^td (~)14.9-r2^ftd (~)14.12-r2^td 14.12-r3^td
       {debug disable-watermark +modules multilib pax_kernel qt4 static-libs ABI_X86="32 64" KERNEL="linux"}
     Installed versions:  14.12-r3(1)^td(20:22:04 13/02/15)(modules qt4 -debug -pax_kernel -static-libs ABI_X86="32 64" KERNEL="linux")
     Homepage:            http://www.amd.com
     Description:         Ati precompiled drivers for Radeon Evergreen (HD5000 Series) and newer chipsets

Procedure

1. Download into ~/Downloads/ the following Ubuntu 32-bit packages from http://packages.ubuntu.com/utopic/i386/libs/

$ ls -la *.deb
-rw-r--r-- 1 fitzcarraldo users  24060 Mar  1 23:59 libecore-imf1_1.8.6-2ubuntu1_i386.deb
-rw-r--r-- 1 fitzcarraldo users 274206 Mar  1 22:59 libfreeimage3_3.15.4-3build1_i386.deb
-rw-r--r-- 1 fitzcarraldo users  52154 Mar  1 23:45 libilmbase6_1.0.1-6.1_i386.deb
-rw-r--r-- 1 fitzcarraldo users 135300 Mar  2 00:28 libjasper1_1.900.1-debian1-2ubuntu0.2_i386.deb
-rw-r--r-- 1 fitzcarraldo users 106868 Mar  1 23:00 libjpeg-turbo8_1.3.0-0ubuntu2_i386.deb
-rw-r--r-- 1 fitzcarraldo users  98500 Mar  1 23:39 libopenjpeg5_1.5.2-2_i386.deb
-rw-r--r-- 1 fitzcarraldo users 189420 Mar  2 00:21 libraw10_0.16.0-6_i386.deb

2. Download into ~/Downloads/ the following 32-bit packages from http://rpmfind.net/linux/rpm2html/search.php and http://pkgs.org/

$ ls -la *.rpm
-rw-r--r-- 1 fitzcarraldo users  57976 Mar  2 00:13 libilmbase6-1.0.2-11.1.2.i586.rpm
-rw-r--r-- 1 fitzcarraldo users 148379 Mar  2 00:03 libilmimf6-1.6.1-alt9.i586.rpm

3. Extract into ~/Downloads/ the following 32-bit libraries from the above-mentioned .deb and .rpm packages:

$ ls -la lib*.so*
-rw-r--r-- 1 fitzcarraldo users 644568 Apr 27  2014 libfreeimage-3.15.4.so
-rw-r--r-- 1 fitzcarraldo users 677340 Apr 27  2014 libfreeimageplus-3.15.4.so
-rwxr-xr-x 1 fitzcarraldo users 271780 Jul 15  2012 libHalf.so.6.0.0
-rwxr-xr-x 1 fitzcarraldo users 104044 Jul 15  2012 libIex.so.6.0.0
-rw-r--r-- 1 fitzcarraldo users 671896 Dec  3 15:06 libIlmImf.so.6.0.0
-rwxr-xr-x 1 fitzcarraldo users  22260 Jul 15  2012 libIlmThread.so.6.0.0
-rw-r--r-- 1 fitzcarraldo users 342116 Jan 22 18:46 libjasper.so.1.0.0
-rw-r--r-- 1 fitzcarraldo users 300776 Dec 19  2013 libjpeg.so.8.0.2
-rw-r--r-- 1 fitzcarraldo users 142604 Apr 26  2014 libopenjpeg.so.1.5.2
-rw-r--r-- 1 fitzcarraldo users 657336 Jul 22  2014 libraw.so.10.0.0

4. Merge the 32-bit Google Earth package from a local overlay, using the ebuild listed in my above-mentioned April 2014 post:

# emerge -C googleearth
# rm -rf /opt/googleearth/
# emerge googleearth::local_overlay

5. Delete the four bundled Qt libs, compile the shim devised by user amirpli (see Comment #9 in Gentoo Bugzilla Bug Report No. 490066) but compile it for 32 bits (‘-m32‘), and edit the googleearth script to use the 32-bit libfreeimage.so.3 that you will copy into /opt/googleearth/ later:

# cd /opt/googleearth
# rm libQt*
# touch baifaao.cpp
# nano baifaao.cpp
# cat baifaao.cpp
/* amirpli 2013/11/28 */
#include
extern "C" {
        int _Z34QBasicAtomicInt_fetchAndAddOrderedPVii(QAtomicInt* a, int b) {
                return a->fetchAndAddOrdered(b);
        }
}
# gcc -I/usr/include/qt4 -O3 -m32 -fPIC --shared baifaao.cpp -o baifaao.so
# nano googleearth
# tail googleearth
}

script_path=$(FindPath $0);

cd $script_path;

export LD_PRELOAD=/opt/googleearth/libfreeimage.so.3:/opt/googleearth/baifaao.so
export LC_NUMERIC=en_US.UTF-8 # Must do this if you are using non-US locale.

LD_LIBRARY_PATH=.:$LD_LIBRARY_PATH ./googleearth-bin "$@"

6. Copy into the Google Earth directory all the libraries downloaded and extracted in Steps 1 to 3 above, and create the necessary symlinks and permissions:

# cd /opt/googleearth
# cp /home/fitzcarraldo/Downloads/libfreeimage-3.15.4.so .
# cp /home/fitzcarraldo/Downloads/libfreeimageplus-3.15.4.so .
# ln -s libfreeimage-3.15.4.so libfreeimage.so.3
# ln -s libfreeimage.so.3 libfreeimage.so
# ln -s libfreeimageplus-3.15.4.so libfreeimageplus.so.3
# ln -s libfreeimageplus.so.3 libfreeimageplus.so
# chmod +x libfreeimage-3.15.4.so
# chmod +x libfreeimageplus-3.15.4.so
# cp /home/fitzcarraldo/Downloads/libjpeg.so.8.0.2 .
# ln -s libjpeg.so.8.0.2 libjpeg.so
# ln -s libjpeg.so libjpeg.so.8
# chmod +x libjpeg.so.8.0.2
# cp /home/fitzcarraldo/Downloads/libopenjpeg.so.1.5.2 .
# ln -s libopenjpeg.so.1.5.2 libopenjpeg.so
# ln -s libopenjpeg.so libopenjpeg.so.5
# chmod +x libopenjpeg.so.1.5.2
# cp /home/fitzcarraldo/Downloads/libIlmImf.so.6.0.0 .
# ln -s libIlmImf.so.6.0.0 libIlmImf.so
# ln -s libIlmImf.so libIlmImf.so.6
# chmod +x libIlmImf.so.6.0.0
# cp /home/fitzcarraldo/Downloads/libHalf.so.6.0.0 .
# ln -s libHalf.so.6.0.0 libHalf.so
# ln -s libHalf.so libHalf.so.6
# chmod +x libHalf.so.6.0.0
# cp /home/fitzcarraldo/Downloads/libIex.so.6.0.0 .
# ln -s libIex.so.6.0.0 libIex.so
# ln -s libIex.so libIex.so.6
# chmod +x libIex.so.6.0.0
# cp /home/fitzcarraldo/Downloads/libraw.so.10.0.0 .
# ln -s libraw.so.10.0.0 libraw.so
# ln -s libraw.so libraw.so.10
# chmod +x libraw.so.10.0.0
# cp /home/fitzcarraldo/Downloads/libIlmThread.so.6.0.0 .
# ln -s libIlmThread.so.6.0.0 libIlmThread.so
# ln -s libIlmThread.so libIlmThread.so.6
# chmod +x libIlmThread.so.6.0.0
# cp /home/fitzcarraldo/Downloads/libjasper.so.1.0.0 .
# ln -s libjasper.so.1.0.0 libjasper.so
# ln -s libjasper.so libjasper.so.1
# chmod +x libjasper.so.1.0.0

Finally, launch Google Earth from your user account, not the root user’s account:

$ googleearth

Clicking on any photo icon in Google Earth should now display Panoramio photos.

If you click on a photo icon and the frame that opens displays several thumbnails, clicking on a thumbnail may result in a white Panoramio frame without any photo and thumbnails displayed. According to user amirpli this problem occurs in KDE but not GNOME. If it does happen in your case, to view the other photos right-click on a thumbnail and select ‘Open in New Window’. This way you will be able to view any of the photos.

It’s nice to be able to see the Panoramio photos again in Linux with the FGLRX driver.

Using a Samsung Xpress C460FW with Gentoo Linux and Android KitKat for printing and scanning

INTRODUCTION

A work colleague has just received a Samsung Xpress C460FW MFP (laser printer, scanner, copier and fax machine) for small print jobs. It is possible to connect to it via USB, Direct USB, wired network, wireless network, Wi-Fi Direct and NFC; that’s impressive for a MFP that can be purchased for GBP 270 in the UK.

I wanted to use the C460FW to print and scan from my laptop running Gentoo Linux, and also to print and scan from my Samsung Galaxy Note 4 running Android KiKat. It turned out that I was able to do all of those, and it was not difficult to set up.

A technician from the IT Support department had already entered a static IP address, subnet mask and default gateway IP address via the C460FW’s control panel to connect it to the office’s wired network. So my options to connect to this particular C460FW are: the wired network for Linux; Wi-Fi Direct for Linux and Android; NFC for Android.

I had never used Wi-Fi Direct before, but it turned out to be easy in Gentoo Linux on my laptop, and also easy in Android KitKat on my Samsung Galaxy Note 4. I had never used NFC before either, and that also turned out to be easy on my Samsung Galaxy Note 4.

Samsung has a series of videos on YouTube explaining how to use Wi-Fi Direct and NFC for printing, scanning and faxing with the C460FW from a Samsung smartphone; here are links to a few of them:

Samsung Smart Printing – 01 NFC Connect

Samsung Smart Printing – 02 Wi Fi Direct

Samsung Smart Printing – 03 Wi Fi

Samsung Smart Printing – 04 NFC Print

Samsung Smart Printing – 05 NFC Scan

Samsung Smart Printing – 06 NFC Fax

Samsung Smart Printing – 11 Samsung Mobile Print App(Printer Status)

PRINTING

Linux

Wired connection

I had installed the package net-print/samsung-unified-linux-driver Version 1.02 from a Portage local overlay back in March 2013 when I needed to print to a different model of Samsung MFP, so I thought I would see if that driver would work with the C460FW. I opened the CUPS Printer Manager in a browser window (http://localhost:631/) to configure my Gentoo installation to print to the device via the wired network. ‘Samsung C460 Series‘ was in the list of discovered network printers in the CUPS Printer Manager, and the driver ‘Samsung C460 Series PS‘ was displayed at the top of the list of models, so it was a piece of cake to set up the printer via CUPS, and I was able to print a test page in no time at all. My colleague uses a laptop running Windows 7, and he had to install the Windows driver from a Samsung CD that came with the C460FW.

Wireless connection

As the IT Support technician had configured the C460FW to print via the office wired network rather than the office wireless network, I decided to configure my laptop to print via Wi-Fi Direct, just to learn about Wi-Fi Direct, really. On the C460FW’s control panel I selected Network > Wireless > Wi-Fi Direct and enabled Wi-Fi Direct. Scrolling through the Wi-Fi Direct entries in the LCD I saw the following information:

Device Name: C460 Series
Network Key: <an 8-digit code>
IP address: 192.168.003.001

Two new networks were listed under ‘Available connections’ in plasma-nm (the KDE GUI front-end to NetworkManager) on my laptop: ‘DIRECT-HeC460 Series‘ and ‘DIRECT-SqC460 Series‘, both using WPA2-PSK encryption. I used the control panel of the C460FW to print a network configuration report in order to check which of the two SSIDs I should select, and it is ‘DIRECT-HeC460 Series‘ (I found out later that an adjacent room also has a C460FW and its Wi-Fi Direct SSID is ‘DIRECT-SqC460 Series‘). So I selected ‘DIRECT-HeC460 Series‘ and plasma-nm prompted me to enter a network password. I entered the 8-digit key I had found from the C460FW’s LCD panel (it’s also listed in the printed network configuration report), and NetworkManager connected to the printer.

In exactly the same way as I do when setting up any printer in Linux, I launched Firefox, opened the CUPS Printer Manager page, clicked on ‘Administration’ > ‘Add Printer’ and entered the user name ‘root’ and the password in the pop-up window. Again the ‘Add Printer’ page had ‘Samsung C460 Series‘ in the list of discovered network printers, so I just selected it and clicked on ‘Continue’. As I had already set up the printer in CUPS for the wired network connection and given it the name ‘Samsung_C460FW_office‘, I entered the name ‘Samsung_C460FW_office_WiFi_Direct‘ to distinguish it from the wired network entry, entered a Description and Location, and clicked on ‘Continue’. The next page had ‘Samsung C460 Series PS‘ first in the driver list so I selected that, clicked on ‘Add Printer’ and that was it. I was able to print a test page from the CUPS Printer Manager, and the printer is now included the list of printers in Linux applications’ print dialogues.

When I want to print using Wi-Fi Direct the only thing I need to remember to do first is select ‘DIRECT-HeC460 Series‘ in the network GUI on the KDE Panel, so that the connection is active when I click ‘Print’ in whichever application I want to print from.

Given the ease of printing via the wired network and Wi-Fi Direct, I have no doubts that printing would also work had the C460FW been configured for the office wireless network instead of the wired network.

Duplex printing

The only downside to the Samsung Xpress C460FW is that it only supports manual duplex printing. If you specify duplex printing when printing from Windows, Samsung’s Windows driver prints all the odd-numbered pages in reverse order and displays a message in Windows telling you what to do next (turn over the pile of paper and put it back in the paper tray!), but in Linux it’s not difficult to work out what you have to do: you simply have to print all the odd-numbered sides first, turn over the paper, then print all the even-numbered sides. The print dialogue in Linux applications gives you the option to print only odd-numbered pages or only even-numbered pages, so there is no problem. The print dialogue in some Linux applications allows you to print pages in reverse order as well but, if not, you have to reverse the order yourself before printing the even-numbered pages (i.e. put Page 1 face down at the top of the pile then Page 3 face down under it, and so on). It’s not a big deal unless the document has a large number of pages.

Android

As you would expect with devices from the same manufacturer, setting up my Samsung Galaxy Note 4 to print with the Samsung Xpress C460FW via WPS (Wi-Fi Protected Setup) was easy. When I selected ‘Print’ on the Galaxy Note 4, it gave me the option to print via wireless network or Wi-Fi Direct. I chose the latter and, as I had already enabled Wi-Fi Direct on the C460FW’s control panel, the printer name was displayed in the list of available devices. I selected it, a blue LED began flashing on the C460FW’s control panel and the LCD prompted me to press the WPS button (on the left of the control panel). As soon as I pressed that, the C460FW printed the document sent by my Galaxy Note 4. From then onwards, I just needed to select ‘Print’ on the Galaxy Note 4, select the printer from the list of available devices, and the document is printed. When I want to print using Wi-Fi Direct the only thing I need to remember to do first on the Galaxy Note 4 is select ‘DIRECT-HeC460 Series‘ as the Wi-Fi network.

NFC

I then decided to try to print using NFC. I placed the Galaxy Note 4, without Wi-Fi enabled and with the Home Screen displayed (not the Lock Screen), on the NFC label on top of the C460FW; Android launched Play Store and prompted me to install Samsung Mobile Print, which I did. Now when I place the Galaxy Note 4 on the NFC label, the Galaxy Note 4 automatically enables Wi-Fi, connects to the C460FW directly and displays the Mobile Print app showing the options Print, Scan and Fax, and a page of icons labelled: Gallery, Camera, Google Drive, E-mail, Web page, Document, Facebook, DropBox, Evernote, OneDrive and Box, as well as a Settings icon to configure the printer (paper size etc.). I am able to select a document, photograph, Web page, etc. on the Galaxy Note 4 and print it. It is also possible to launch the Mobile Print app first and then place the Galaxy Note 4 on the C460FW.

NFC is not entirely trouble-free, though. Sometimes the Galaxy Note 4 displays a ‘Device not found‘ message but I can still print. Sometimes the Galaxy Note 4 displays the message ‘Connecting printer. There was some error while connecting to this device. Check your printer and try again. If NFC Pin was changed then please enter new NFC Pin.‘ and the two devices will not connect. Powering off then on the C460FW solves that. Sometimes the Galaxy Note 4 connects to another wireless network instead of to the C460FW via Wi-Fi Direct and the Samsung Galaxy Note 4 then has to disconnect automatically from the other network. Sometimes the C460FW prompts me to press its WPS button and the Galaxy Note 4 then connects via Wi-Fi Direct but the Mobile Print app then displays the error message ‘Device not found. To troubleshoot please check – C460 Series is powered on. – Wi-Fi direct is enabled on C460 Series. – C460 Series and Mobile are connected to the same network.‘. Again, powering off then on the C460FW solves that. Despite these hiccups, printing via NFC is still handy.

SCANNING

Linux

I found out how to get the C460FW scanner working by consulting the third-party Web site The Samsung Unified Linux Driver Repository which someone created to provide .deb packages for the Samsung driver as well as tips on how to get Samsung printers and scanners working in Linux. It turned out to be relatively straightforward to scan, both via the office wired network and via Wi-Fi Direct. I edited the file /etc/sane.d/xerox_mfp.conf and replaced the following:

#Samsung C460 Series
usb 0x04e8 0x3468

with the following in order to use the C460FW to scan via the office wired network:

#Samsung C460 Series
#usb 0x04e8 0x3468
#Wired network static address of this C460FW:
tcp 10.90.21.125

or with the following in order to use the C460FW to scan via Wi-Fi Direct:

#Samsung C460 Series
#usb 0x04e8 0x3468
#Wi-Fi Direct address of this C460FW:
tcp 192.168.3.1

I found the IP addresses from the network configuration report I printed earlier.

I was able to use the two Linux scanning applications I normally use, XSane and gscan2pdf, to scan via the wired network and via Wi-Fi Direct. The resulting scans were very good. Given the ease of scanning via the wired network and Wi-Fi Direct, I have no doubts that scanning would work via a wireless network had the C460FW been configured for the office wireless network instead of the wired network.

Android

To use NFC to scan a document I place the Galaxy Note 4, without Wi-Fi enabled and with the Home Screen displayed (not the Lock Screen), on the NFC label on top of the C460FW. The Galaxy Note 4 enables Wi-Fi, connects automatically to the C460FW directly and launches the Mobile Print app showing the options Print, Scan and Fax. It is also possible to launch the Mobile Print app first and then place the Galaxy Note 4 on the C460FW. In other words, the procedure is exactly the same as when wanting to print via NFC. If I select Scan, the Galaxy Note 4 displays buttons for previewing and scanning. Amongst other things, the app’s Settings menu allows you to select whether you want to save the scanned image as a JPEG, PNG or PDF file. The hiccups mentioned above when printing via NFC also apply to scanning. Nevertheless, scanning from the C460FW to the Samsung Galaxy Note 4 via NFC is still handy.

CONCLUSION

As I am mainly interested in printing text documents I have only tried to print a few colour photographs on plain copier paper, and they look good. Text in documents looks crisp. Despite the lack of automatic duplex printing the C460FW is an excellent peripheral, especially for the price, although I don’t pay for the consumables so I have no idea of the operating costs. The ease with which I got it printing and scanning in Gentoo Linux (laptop) and Android KitKat (Samsung Galaxy Note 4) means that I would definitely consider purchasing this model for home use.

NetworkManager creates a new connection ‘eth0′ that does not work

Several months ago a new entry ‘eth0′ began appearing under ‘Available connections‘ in the KDE plasma-nm widget (the KDE GUI front-end to NetworkManager) in my Gentoo Linux installation. However, there was already an automatically-created entry ‘Wired connection 1′ for the wired interface. In the plasma-nm GUI I could see that both entries were for the same interface (eth0) and MAC address. My laptop could access the Internet via the connection ‘Wired connection 1′ as usual, but not via the new connection ‘eth0′. And if I deleted ‘eth0′ in the plasma-nm GUI, ‘Wired connection 1′ could not access the Internet until I recreated ‘eth0′ manually.

Apart from the fact that two entries for the same interface is unnecessary, it was annoying because sometimes ‘eth0′ automatically became the active connection instead of ‘Wired connection 1′, despite the fact that only ‘Wired connection 1′ had ‘Automatically connect to this network when it is available’ ticked in the plasma-nm GUI. When this happened, the network icon on the Panel showed an active connection but in fact the laptop could not connect to the Internet. However, the connection did work as expected on the occasions when ‘Wired connection 1′ automatically became the active connection or if I switched manually to ‘Wired connection 1′ via the plasma-nm GUI.

Even more strangely, if I happened to be using WiFi when no Ethernet cable was connected, very occasionally the network icon on the Panel would change from a wireless icon to a wired icon and connection to the Internet would be lost. I would then have to re-select the wireless network in order to reconnect to the Internet.

As my laptop has only one Ethernet port, and as there was previously no ‘eth0′ entry under ‘Available connections‘, initially I thought that the new entry occurred because I had recently installed a new version of udev. I have the parameter net.ifnames=0 in the kernel boot line to stop udev/eudev using the so-called Predictable Network Interface Names, and I have the following udev/eudev rules files relating to networking:

# ls -la /etc/udev/rules.d/*net*
lrwxrwxrwx 1 root root    9 Nov 30 15:25 80-net-setup-link.rules -> /dev/null
# ls -la /lib64/udev/rules.d/*net*
-rw-r--r-- 1 root root  452 Nov  7 09:57 /lib64/udev/rules.d/75-net-description.rules
-rw-r--r-- 1 root root 1734 Jan 28 18:29 /lib64/udev/rules.d/77-mm-huawei-net-port-types.rules
-rw-r--r-- 1 root root  491 Nov  7 09:57 /lib64/udev/rules.d/80-net-name-slot.rules
-rw-r--r-- 1 root root  280 Jan 24 00:41 /lib64/udev/rules.d/90-network.rules

Perhaps udev (well, eudev, as I switched to using eudev after the problem started) did have something to do with the new entry, but I began to suspect that NetworkManager was the culprit. I think the problem first occurred after installing NetworkManager 0.9.10.0 last October, but it remained after I installed NetworkManager 1.0.0, until today when I made the various changes described further on.

I had merged NetworkManager 1.0.0 and preceding versions since 0.9.8.8 with USE flags -dhclient and dhcpcd, i.e. NetworkManager in my installation uses the DHCP client dhcpcd instead of dhclient. (I used to merge NetworkManager to use dhclient but found it did not work with 0.9.8.8 and later versions of NetworkManager.)

The relevant network services running in my installation are as follows, and nothing looks incorrect to me:

# rc-update show | grep -i net
       NetworkManager |      default
                local |      default nonetwork
               net.lo | boot
             netmount |      default
# rc-status | grep -i net
NetworkManager                                                    [ started ]
netmount                                                          [ started ]
# rc-update show | grep dh
# rc-status | grep dh
# rc-update -v show | grep supplicant
wpa_supplicant |
# rc-status | grep supplicant
#

NetworkManager itself launches the DHCP client, so the installation should not be configured to launch a DHCP client. Indeed the output above shows that no DHCP client service is configured to run independently of NetworkManager, and I also double-checked that multiple instances of a DHCP client are not running (they’re not):

# ps -C NetworkManager
  PID TTY          TIME CMD
 6481 ?        00:00:22 NetworkManager
# ps -C dhcpcd
  PID TTY          TIME CMD
10378 ?        00:00:00 dhcpcd
# ps -C dhclient
  PID TTY          TIME CMD
#

As far as WiFi is concerned, NetworkManager itself launches wpa_supplicant, so the installation should not be configured to launch wpa_supplicant. Indeed the output from rc-update and rc-status above shows that no wpa_supplicant service is configured to run independently of NetworkManager, and I also double-checked that multiple instances of wpa_supplicant are not running (they’re not):

# ps -C wpa_supplicant
  PID TTY          TIME CMD
 6491 ?        00:00:00 wpa_supplicant
#

So, as far as I could tell, there was nothing wrong with the non-NetworkManager side of my installation.

I thought the problem might be due to the settings in the file /etc/NetworkManager/NetworkManager.conf, which contained the following:

[main]
plugins=keyfile
dhcp=dhcpcd

[ifnet]
managed=true
auto_refresh=false

[keyfile]
hostname=meshedgedx

I studied the manual pages for NetworkManager.conf:

# man NetworkManager.conf

If I understand correctly, the ifnet plug-in is Gentoo-specific (see References 3, 4 and 5 further on). The entries under [ifnet] in my NetworkManager.conf file were redundant in any case because the ifnet plug-in was not included in the plugins list under [main], so I deleted the entire [ifnet] section. There is no mention of the ifnet plug-in on the NetworkManager.conf manual page or in the Gentoo Linux Wiki article on NetworkManager, and a cursory look in the Gentoo ebuild for NetworkManager 1.0.0 clearly indicates the ifnet plug-in is broken. See, for example, the following comment in the ebuild:

# ifnet plugin always disabled until someone volunteers to actively
# maintain and fix it

and the following warning messages in the ebuild if the user has included ifnet in plugin=<plugin list> in NetworkManager.conf:

ewarn "Ifnet plugin is now disabled because of it being unattended"
ewarn "and unmaintained for a long time, leading to some unfixed bugs"
ewarn "and new problems appearing. We will now use upstream 'keyfile'"
ewarn "plugin."
ewarn "Because of this, you will likely need to reconfigure some of"
ewarn "your networks. To do this you can rely on Gnome control center,"
ewarn "nm-connection-editor or nmtui tools for example once updated"
ewarn "NetworkManager version is installed."
ewarn "You seem to use 'ifnet' plugin in ${EROOT}etc/NetworkManager/NetworkManager.conf"
ewarn "Since it won't be used, you will need to stop setting ifnet plugin there."

I modified NetworkManager.conf to contain the following:

[main]
plugins=keyfile
dhcp=dhcpcd
no-auto-default=eth0

[keyfile]
hostname=meshedgedx

Note that the ifnet plug-in was not specified in the plugins list in the [main] section of my previous NetworkManager.conf so it was not the cause of my problem, but I hoped that adding no-auto-default=eth0 to NetworkManager.conf would solve the problem. I deleted the ‘Wired connection 1′ entry from the plasma-nm GUI, ticked ‘Automatically connect to this network when it is available’ for the ‘eth0′ entry and made sure that option was not ticked for any of the other entries under ‘Available connections‘, then rebooted. There was no longer an entry ‘Wired connection 1′ in the plasma-nm widget GUI, just an entry for ‘eth0′, and the installation connected automatically to the wired network and I could access the Internet, but did not reconnect to the wired network if I removed and reinserted the Ethernet cable when also connected to a wireless network. So I was not home and dry yet.

I have read on various Web sites that NetworkManager prefers wired connections over wireless connections. I assume this is because NetworkManager sets a higher metric for the wired connection.

I am on a work trip at the moment and cannot use a dynamic wired connection, only a static wired connection, but I can see that NetworkManager 1.0.0 does set a higher-priority metric for wired connections:

# # Now with both dynamic wireless and static wired:
# ip route show
default via 10.90.21.1 dev eth0  proto static  metric 100
default via 10.96.0.1 dev wlan0  proto static  metric 600
10.90.21.0/24 dev eth0  proto kernel  scope link  src 10.90.21.112  metric 100
10.96.0.0/16 dev wlan0  proto kernel  scope link  src 10.96.87.86
10.96.0.0/16 dev wlan0  proto kernel  scope link  src 10.96.87.86  metric 303
127.0.0.0/8 dev lo  scope host
127.0.0.0/8 via 127.0.0.1 dev lo
192.0.2.1 via 10.96.0.1 dev wlan0  proto dhcp  metric 600
#

10.90.21.1 is the IP address of the gateway for the wired connection, and 10.90.21.112 is the IP address of my laptop’s wired interface. The smaller the metric value, the higher the routing priority. Notice that the metric for the eth0 interface is 100 whereas the metric for the wlan0 interface is 600, so it does appear that NetworkManager favours a wired connection over a wireless connection when both are active.

After doing all the above, I came across Debian bug report no. 755202: network-manager: keeps creating and using new connection “eth0″ that does not work which appears to be exactly what I was experiencing. Various people posted solutions that worked in their particular circumstances, so I am none the wiser. Gentoo user Keivan Moradi posted message no. 79 on that bug report, about a warning message he found in the NetworkManager log file regarding a file /etc/NetworkManager/system-connections/.keep_net-misc_networkmanager-0, and he then deleted the latter file. I found the same message in /var/log/messages:

# grep networkmanager /var/log/messages
Feb  9 04:10:05 localhost NetworkManager[10355]: <warn>      error in connection /etc/NetworkManager/system-connections/.keep_net-misc_networkmanager-0: invalid connection: connection.type: property is missing
Feb 11 15:53:05 localhost NetworkManager[13143]: <warn>      error in connection /etc/NetworkManager/system-connections/.keep_net-misc_networkmanager-0: invalid connection: connection.type: property is missing

The file /etc/NetworkManager/system-connections/.keep_net-misc_networkmanager-0 also existed in my installation, so I also deleted it. It was a zero-length file and I do not know if it had anything to do with my problem:

# ls -la /etc/NetworkManager/system-connections/.keep_net-misc_networkmanager-0
-rw------- 1 root root 0 Jan 20 00:09 /etc/NetworkManager/system-connections/.keep_net-misc_networkmanager-0
# rm /etc/NetworkManager/system-connections/.keep_net-misc_networkmanager-0
#

Anyway, the file /etc/NetworkManager/system-connections/.keep_net-misc_networkmanager-0 has not reappeared since I deleted it.

Keivan Moradi had ‘id=Wired‘ under [connection] in the file /etc/NetworkManager/system-connections/eth0, and he decided to change the name of the file from ‘eth0‘ to ‘Wired‘. However, in my case the file name and the id in the file /etc/NetworkManager/system-connections/eth0 are both ‘eth0‘:

# cat /etc/NetworkManager/system-connections/eth0
[ethernet]
mac-address=70:5A:B6:3E:C1:8A
mac-address-blacklist=

[connection]
id=eth0
uuid=cb3d5786-f947-44b8-92f7-8471fc94c568
type=ethernet
permissions=
secondaries=

[ipv6]
method=ignore
dns-search=

[ipv4]
method=auto
dns-search=

I had already deleted and recreated the connection ‘eth0′ in the plasma-nm GUI by the time I checked the contents of the directory /etc/NetworkManager/system-connections/ so I do not know if the original file name and id were the same. I had also already deleted the connection ‘Wired connection 1′ in the plasma-nm GUI by the time I checked the contents of the directory; presumably files for connections ‘Wired connection 1′ and ‘eth0′ both existed in /etc/NetworkManager/system-connections/ before then. I do not know why the zero-length file .keep_net-misc_networkmanager-0 was created, but no further files have appeared in the directory since I deleted the connection ‘Wired connection 1′ and the file .keep_net-misc_networkmanager-0.

Keivan Moradi was also previously using a buggy r8169 kernel module (Realtek Ethernet hardware) and switched to using the r8168 module, but I am using a Qualcomm Atheros AR8131 Gigabit Ethernet card and an Intel Corporation Ultimate N WiFi Link 5300 card, so that part of his problem cannot be a factor in my case.

Anyway, as I wrote earlier, I no longer have two connection entries for the wired interface, and NetworkManager no longer creates automatically a second connection entry for the wired interface. And now if I am already connected to a wireless network, NetworkManager connects/reconnects automatically to a wired network with the ‘Automatically connect’ option ticked. So it looks like my problem is completely solved, although I reserve judgement until I have been able to use the laptop in my home network (which has the same router for both wired and wireless connections, whereas the wired network and wireless network are separate networks in the office in which I am now working).

Conclusion

If you had the patience to read all the above, I am impressed! If you also understood it, I am doubly impressed!

To cut a long story short, if you are experiencing a similar problem to mine, I recommend you do the following:

  1. Check that your network driver is reliable. You can search the Web to see if other users have experienced problems with the same driver you are using.

  2. Make sure the contents of NetworkManager.conf are correct. Read the NetworkManager.conf man page and the GNOME Wiki page on NetworkManager settings to find out what options are available.

  3. Delete all the files (i.e. including hidden files) in the directory /etc/NetworkManager/system-connections/ and recreate your connections via either the NetworkManager GUI (e.g. plasma-nm in KDE or nm-applet in GNOME) or NetworkManager TUI (nmtui).

References

  1. man NetworkManager.conf
  2. Gentoo Linux Wiki – NetworkManager
  3. GNOME Wiki – NetworkManager SystemSettings – Configuration Plugins
  4. Gentoo NetworkManager Plugin
  5. Another Gentoo Dev – Ifnet updates for NetworkManager 0.9

Fixing unperceived errors in my X Windows configuration

Prologue

Last week I decided to bite the bullet and upgrade X Windows to the latest version available in the main Portage tree: 1.16.3-r1. I updated my entire installation (I ‘emerged world’, in Gentoo parlance). The package eselect-opengl was one of various other packages updated as well (it was updated to Version 1.3.1-r1). Fortunately I scan the Gentoo Forums regularly and noticed the threads ‘new x11 update breaks glx‘ and ‘After xorg-server-1.16.2.901-r1 update 3D stopped working‘, so I was forewarned that a "Files" section is not allowed in more than one X Windows configuration file if an installation has more than one (e.g. /etc/X11/xorg.conf and /etc/X11/xorg.conf.d/*.conf). The eselect-opengl ebuild was subsequently bumped to 1.3.1-r2 to display a warning to users regarding this restriction.

I’m using ~amd64 multilib and the FGLRX driver (ATI Mobility Radeon HD 5650 GPU). Before updating, my laptop’s installation had a file /etc/X11/xorg.conf and no /etc/X11/xorg.conf.d/ directory.

Before updating I cleaned up a few broken symlinks (indicated by flashing red text in Konsole) relating to the FGLRX driver — presumably left over from previous updates several years ago judging by the file dates — that I found during a cursory search:

# ls -la /usr/lib32/xorg/modules/extensions/
# rm /usr/lib32/xorg/modules/extensions/fglrx-libglx.so
# rm /usr/lib32/xorg/modules/extensions/libglx.so
# ls -la /usr/lib64/xorg/modules/extensions/
# rm /usr/lib64/xorg/modules/extensions/FGL.renamed.libglx.so
# rm /usr/lib64/xorg/modules/extensions/fglrx-libglx.so

(There may have been other broken symlinks relating to the FGLRX driver and GLX, but I didn’t look further.)

Then I updated all packages using the Portage command ‘emerge -uvDN --keep-going world‘ as usual. After the update was complete, the contents of the file /etc/X11/xorg.conf included the following two consecutive lines:

Section "Files"
EndSection

and there is a new directory /etc/X11/xorg.conf.d/ which contained a single file 20opengl.conf with only five lines:

Section "Files"
        ModulePath "/usr/lib32/xorg/modules"
        ModulePath "/usr/lib64/opengl/ati"
        ModulePath "/usr/lib64/xorg/modules"
EndSection

Heeding posts in the aforementioned two Gentoo Forums threads I deleted the above-mentioned two lines in xorg.conf and I also deleted the first ModulePath (the one with ‘lib32‘) in 20opengl.conf. After rebooting, X Windows, GLX and Direct Rendering worked fine as usual. (I subsequently discovered it is not necessary to delete that ModulePath in my case, as there are no longer any files in /usr/lib32/xorg/modules and its subdirectories in my case.)

So everything was good. Well, not quite. Although the installation was working properly, there were still some long-standing messages in the X.Org log file /var/log/Xorg.0.log that indicated my installation was not configured completely correctly. I had ignored them for too long and resolved to find their causes and eliminate them. Here is what I did.

AIGLX error message

The contents of log file Xorg.0.log included the following error message:

(EE) AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]

Despite the error message, AIGLX was working, but I resolved to get rid of the message anyway by creating a symlink for the missing file mentioned in the message:

# ls /usr/X11R6/lib64/modules
extensions
# mkdir -p /usr/X11R6/lib64/modules/dri/
# ls -la /usr/lib/dri/fglrx_dri.so
-rwxr-xr-x 1 root root 37365968 Jan 10 18:16 /usr/lib/dri/fglrx_dri.so
# ln -s /usr/lib/dri/fglrx_dri.so /usr/X11R6/lib64/modules/dri/fglrx_dri.so
# cd /usr/X11R6/lib64/modules/dri
# ls -liat
total 8
2229069 drwxr-xr-x 2 root root 4096 Jan 22 22:30 .
2230340 lrwxrwxrwx 1 root root 25 Jan 22 22:30 fglrx_dri.so -> /usr/lib/dri/fglrx_dri.so
685665 drwxr-xr-x 4 root root 4096 Jan 22 22:29 ..

Now there is no error message and functionality has not been affected:

# grep -i GLX /var/log/Xorg.0.log
[ 30.773] (II) "glx" will be loaded by default.
[ 31.098] (II) LoadModule: "glx"
[ 31.098] (II) Loading /usr/lib64/opengl/ati/extensions/libglx.so
[ 31.167] (II) Module glx: vendor="Advanced Micro Devices, Inc."
[ 38.949] (II) AIGLX: Loaded and initialized OpenGL driver(II) GLX: Initialized DRI GL provider for screen 0

Touchpad

In looking through /var/log/Xorg.0.log I noticed some messages (not all contiguous) relating to the touchpad which indicated there were other problems:

[    31.940] (**) |-->Input Device "SynapticsTouchpad"
[    32.538] (II) LoadModule: "synaptics"
[    32.538] (II) Loading /usr/lib64/xorg/modules/input/synaptics_drv.so
[    32.576] (II) Module synaptics: vendor="X.Org Foundation"
[    33.416] (II) LoadModule: "synaptics"
[    33.416] (II) Loading /usr/lib64/xorg/modules/input/synaptics_drv.so
[    33.416] (II) Module synaptics: vendor="X.Org Foundation"
[    41.253] (II) Using input driver 'synaptics' for 'SynapticsTouchpad'
[    41.253] (**) SynapticsTouchpad: always reports core events
[    41.282] (EE) synaptics: SynapticsTouchpad: Synaptics driver unable to detect protocol
[    41.282] (EE) PreInit returned 11 for "SynapticsTouchpad"
[    41.282] (II) UnloadModule: "synaptics"

The touchpad was working fine, but I didn’t understand why the synaptics module was being loaded twice, then unloaded. Also, the message about an undetectable ‘protocol’ indicated a problem.

Now, as I mentioned at the beginning of this post, previously my installation did not have the directory /etc/X11/xorg.conf.d/ and there was only the file /etc/X11/xorg.conf. Below is what xorg.conf contained before I updated:

Section "ServerLayout"
	Identifier     "Main Layout"
	Screen      0  "aticonfig-Screen[0]-0" 0 0
	InputDevice    "SynapticsTouchpad" "SendCoreEvents"
EndSection

Section "Files"
EndSection

Section "Module"
	SubSection "extmod"
		Option	    "omit xfree86-dga"
	EndSubSection
	Load  "i2c"
	Load  "ddc"
	Load  "vbe"
	Load  "dri"
	Load  "glx"
	Load  "synaptics"
EndSection

Section "ServerFlags"
	Option	    "AllowMouseOpenFail" "true"
EndSection

Section "InputDevice"
	Identifier  "SynapticsTouchpad"
	Driver      "synaptics"
	Option	    "AlwaysCore" "true"
	Option	    "Device" "/dev/psaux"
	Option	    "Protocol" "auto-dev"
	Option	    "SHMConfig" "false"
	Option	    "LeftEdge" "1700"
	Option	    "RightEdge" "5300"
	Option	    "TopEdge" "1700"
	Option	    "BottomEdge" "4200"
	Option	    "FingerLow" "25"
	Option	    "FingerHigh" "30"
	Option	    "MaxTapTime" "180"
	Option	    "VertEdgeScroll" "true"
	Option	    "HorizEdgeScroll" "true"
	Option	    "CornerCoasting" "true"
	Option	    "CoastingSpeed" "0.30"
	Option	    "VertScrollDelta" "100"
	Option	    "HorizScrollDelta" "100"
	Option	    "MinSpeed" "0.10"
	Option	    "MaxSpeed" "0.60"
	Option	    "AccelFactor" "0.0020"
	Option	    "VertTwoFingerScroll" "true"
	Option	    "HorizTwoFingerScroll" "true"
	Option	    "TapButton1" "1"
	Option	    "TapButton2" "2"
	Option	    "TapButton3" "3"
EndSection

Section "Monitor"
	Identifier  "aticonfig-Monitor[0]-0"
	Option	    "VendorName" "ATI Proprietary Driver"
	Option	    "ModelName" "Generic Autodetecting Monitor"
	Option	    "DPMS" "true"
EndSection

Section "Device"
	Identifier  "aticonfig-Device[0]-0"
	Driver      "fglrx"
	BusID       "PCI:1:0:0"
EndSection

Section "Screen"
	Identifier  "aticonfig-Screen[0]-0"
	Device      "aticonfig-Device[0]-0"
	Monitor     "aticonfig-Monitor[0]-0"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection

Section "DRI"
	Mode         0666
EndSection

The only mention of a ‘protocol’ in xorg.conf was the line:

Option	    "Protocol" "auto-dev"

Searching the Web soon showed me that auto-dev is obsolete (Debian Bug report #649003 – xserver-xorg-input-synaptics: Option “Protocol” “auto-dev” does not work anymore – documentation needs fixing), so I simply deleted that line from xorg.conf. Another error message eliminated, but several more to go.

I knew that, since Version 1.8 (I believe that was the release), X Windows allows the use of /etc/X11/xorg.conf.d/*.conf files instead of, or as well as, /etc/X11/xorg.conf as a means of configuring X Windows (see e.g. Gentoo Xorg-server 1.8 Upgrade Guide).

As my latest installation update had resulted in the creation of the directory /etc/X11/xorg.conf.d/, I decided to move the touchpad configuration from the xorg.conf file to a new file in that directory, and therefore I created the file /etc/X11/xorg.conf.d/50-synaptics.conf containing the following:

Section "InputClass"
        Identifier "touchpad"
        Driver "synaptics"
        MatchIsTouchpad "on"
        MatchDevicePath "/dev/input/event*"
        Option "TapButton1" "1"
        Option "TapButton2" "2"
        Option "TapButton3" "3"
        Option "VertEdgeScroll" "on"
        Option "VertTwoFingerScroll" "on"
        Option "HorizEdgeScroll" "on"
        Option "HorizTwoFingerScroll" "on"
        Option "CircularScrolling" "on"
        Option "CircScrollTrigger" "0"
        Option "EmulateTwoFingerMinZ" "40"
        Option "EmulateTwoFingerMinW" "8"
        Option "CoastingSpeed" "0"
        Option "FingerLow" "35"
        Option "FingerHigh" "40"
EndSection

However the log file Xorg.0.log still contained messages such as the following:

[    41.535] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"

Notice that I had named the InputClass "touchpad" in the file /etc/X11/xorg.conf.d/50-synaptics.conf, not "evdev touchpad catchall", so I began to wonder if X Windows configuration files existed in other directories and were also being parsed by X Windows. I searched and found three in the directory /usr/share/X11/xorg.conf.d/:

# ls /usr/share/X11/xorg.conf.d/
10-evdev.conf  10-quirks.conf  50-synaptics.conf

These three files contained, respectively, the following:

10-evdev.conf

Section "InputClass"
        Identifier "evdev pointer catchall"
        MatchIsPointer "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev keyboard catchall"
        MatchIsKeyboard "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev touchpad catchall"
        MatchIsTouchpad "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev tablet catchall"
        MatchIsTablet "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev touchscreen catchall"
        MatchIsTouchscreen "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

10-quirks.conf

  
# Collection of quirks and blacklist/whitelists for specific devices.


# Accelerometer device, posts data through ABS_X/ABS_Y, making X unusable
# http://bugs.freedesktop.org/show_bug.cgi?id=22442 
Section "InputClass"
        Identifier "ThinkPad HDAPS accelerometer blacklist"
        MatchProduct "ThinkPad HDAPS accelerometer data"
        Option "Ignore" "on"
EndSection

# https://bugzilla.redhat.com/show_bug.cgi?id=523914
# Mouse does not move in PV Xen guest
# Explicitly tell evdev to not ignore the absolute axes.
Section "InputClass"
        Identifier "Xen Virtual Pointer axis blacklist"
        MatchProduct "Xen Virtual Pointer"
        Option "IgnoreAbsoluteAxes" "off"
        Option "IgnoreRelativeAxes" "off"
EndSection

# https://bugs.freedesktop.org/show_bug.cgi?id=55867
# Bug 55867 - Doesn't know how to tag XI_TRACKBALL
Section "InputClass"
        Identifier "Tag trackballs as XI_TRACKBALL"
        MatchProduct "trackball"
        MatchDriver "evdev"
        Option "TypeName" "TRACKBALL"
EndSection

# https://bugs.freedesktop.org/show_bug.cgi?id=62831
# Bug 62831 - Mionix Naos 5000 mouse detected incorrectly
Section "InputClass"
        Identifier "Tag Mionix Naos 5000 mouse XI_MOUSE"
        MatchProduct "La-VIEW Technology Naos 5000 Mouse"
        MatchDriver "evdev"
        Option "TypeName" "MOUSE"
EndSection

50-synaptics.conf

# Example xorg.conf.d snippet that assigns the touchpad driver
# to all touchpads. See xorg.conf.d(5) for more information on
# InputClass.
# DO NOT EDIT THIS FILE, your distribution will likely overwrite
# it when updating. Copy (and rename) this file into
# /etc/X11/xorg.conf.d first.
# Additional options may be added in the form of
#   Option "OptionName" "value"
#
Section "InputClass"
        Identifier "touchpad catchall"
        Driver "synaptics"
        MatchIsTouchpad "on"
# This option is recommend on all Linux systems using evdev, but cannot be
# enabled by default. See the following link for details:
# http://who-t.blogspot.com/2010/11/how-to-ignore-configuration-errors.html
#       MatchDevicePath "/dev/input/event*"
EndSection

Section "InputClass"
        Identifier "touchpad ignore duplicates"
        MatchIsTouchpad "on"
        MatchOS "Linux"
        MatchDevicePath "/dev/input/mouse*"
        Option "Ignore" "on"
EndSection

# This option enables the bottom right corner to be a right button on clickpads
# and the right and middle top areas to be right / middle buttons on clickpads
# with a top button area.
# This option is only interpreted by clickpads.
Section "InputClass"
        Identifier "Default clickpad buttons"
        MatchDriver "synaptics"
        Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
        Option "SecondarySoftButtonAreas" "58% 0 0 15% 42% 58% 0 15%"
EndSection

# This option disables software buttons on Apple touchpads.
# This option is only interpreted by clickpads.
Section "InputClass"
        Identifier "Disable clickpad buttons on Apple touchpads"
        MatchProduct "Apple|bcm5974"
        MatchDriver "synaptics"
        Option "SoftButtonAreas" "0 0 0 0 0 0 0 0"
EndSection

Looking at the InputClass section names and the messages in Xorg.0.log, the penny dropped: X Windows uses all the configuration files it finds in the /usr/share/X11/xorg.conf.d/,  /etc/X11/ and /etc/X11/xorg.conf.d/ directories. I had not realised this before; I had simply assumed X Windows only uses configuration files in the latter two directories (I should have looked more closely in Xorg.0.log, as it mentions /usr/share/X11/xorg.conf.d/). So I did the following:

1.  Deleted the file /usr/share/X11/xorg.conf.d/50-synaptics.conf (my laptop does not have a clickpad, so I don’t need the sections relating to a clickpad anyway).

2.  Modified the file /etc/X11/xorg.conf.d/50-synaptics.conf to contain the parts of /usr/share/X11/xorg.conf.d/50-synaptics.conf that stop X Windows assuming the touchpad is a mouse (udev detects it as a mouse in addition to detecting it as a touchpad):

 
Section "InputClass"
        Identifier "touchpad catchall"
        Driver "synaptics"
        MatchIsTouchpad "on"
        MatchDevicePath "/dev/input/event*"
        Option "TapButton1" "1"
        Option "TapButton2" "2"
        Option "TapButton3" "3"
        Option "VertEdgeScroll" "on"
        Option "VertTwoFingerScroll" "on"
        Option "HorizEdgeScroll" "on"
        Option "HorizTwoFingerScroll" "on"
        Option "CircularScrolling" "on"
        Option "CircScrollTrigger" "0"
        Option "EmulateTwoFingerMinZ" "40"
        Option "EmulateTwoFingerMinW" "8"
        Option "CoastingSpeed" "0"
        Option "FingerLow" "35"
        Option "FingerHigh" "40"
EndSection

Section "InputClass"
        Identifier "touchpad ignore duplicates"
        MatchIsTouchpad "on"
        MatchDevicePath "/dev/input/mouse*"
        Option "Ignore" "on"
EndSection

Notice that I also changed the Identifier of the first section from “touchpad” to “touchpad catchall”, although I could have left it as it was.

Note that the following pair of messages in the file /var/log/Xorg.0.log do not worry me, as I believe they indicate that an InputClass section named "touchpad ignore duplicates" in an X Windows configuration file made X Windows ignore udev when it detected the touchpad again, this time as a mouse instead of a touchpad. As X Windows has already loaded the synaptics module for the touchpad device /dev/input/event5 (it could be a different event number in your case), it is therefore correct to make the synaptics driver ignore /dev/input/mouse*.

[    41.581] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[    41.581] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"

3.  Moved the file /etc/X11/xorg.conf.d/10-evdev.conf to /etc/X11/xorg.conf.d/10-evdev.conf and edited it to contain the following:

Section "InputClass"
        Identifier "evdev pointer catchall"
        MatchIsPointer "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev keyboard catchall"
        MatchIsKeyboard "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev tablet catchall"
        MatchIsTablet "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev touchscreen catchall"
        MatchIsTouchscreen "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Note that I removed the section "evdev touchpad catchall" because I believe its purpose is already covered by the section "touchpad catchall" in the file /etc/X11/xorg.conf.d/50-synaptics.conf.

Actually, as my laptop does not have a tablet connected and neither does it have a touchscreen, I could also have removed the last two sections, but I left them in as they would do no harm.

4.  Checked in the file /var/log/Xorg.0.log which modules loaded by /etc/X11/xorg.conf are loaded anyway, and therefore do not need to be included in xorg.conf:

$ grep extmod /var/log/Xorg.0.log
[ 30.773] (II) LoadModule: "extmod"
[ 30.773] (II) Module "extmod" already built-in

$ grep i2c /var/log/Xorg.0.log
[ 30.775] (II) LoadModule: "i2c"
[ 30.775] (II) Module "i2c" already built-in

$ grep ddc /var/log/Xorg.0.log
[ 30.775] (II) LoadModule: "ddc"
[ 30.775] (II) Module "ddc" already built-in
[ 35.114] (II) Loading sub module "ddc"
[ 35.114] (II) LoadModule: "ddc"
[ 35.114] (II) Module "ddc" already built-in
[ 35.421] (II) Loading sub module "ddc"
[ 35.421] (II) LoadModule: "ddc"
[ 35.421] (II) Module "ddc" already built-in

$ grep vbe /var/log/Xorg.0.log
[ 30.775] (II) LoadModule: "vbe"
[ 31.162] (II) Loading /usr/lib64/xorg/modules/libvbe.so
[ 31.175] (II) Module vbe: vendor="X.Org Foundation"
[ 35.073] (II) Loading sub module "vbe"
[ 35.073] (II) LoadModule: "vbe"
[ 35.073] (II) Loading /usr/lib64/xorg/modules/libvbe.so
[ 35.073] (II) Module vbe: vendor="X.Org Foundation"

$ grep \"dri\" /var/log/Xorg.0.log
[ 31.175] (II) LoadModule: "dri"
[ 31.175] (II) Module "dri" already built-in

$ grep glx /var/log/Xorg.0.log
[ 30.775] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[ 31.175] (II) LoadModule: "glx"
[ 31.175] (II) Loading /usr/lib64/opengl/ati/extensions/libglx.so
[ 31.193] (II) Module glx: vendor="Advanced Micro Devices, Inc."

The module vbe was the only one being loaded exclusively because of a Load command in the xorg.conf file.

5.  Edited /etc/X11/xorg.conf to: a) remove the unecessary loading of those modules that are already being loaded; b) remove the section relating to the touchpad, as I had moved it to /etc/X11/xorg.conf.d/50-synaptics.conf:

Section "ServerLayout"
        Identifier     "Main Layout"
        Screen      0  "aticonfig-Screen[0]-0" 0 0
EndSection

Section "Module"
        Load  "vbe"
EndSection

Section "ServerFlags"
        Option      "AllowMouseOpenFail" "true"
EndSection

Section "Monitor"
        Identifier  "aticonfig-Monitor[0]-0"
        Option      "VendorName" "ATI Proprietary Driver"
        Option      "ModelName" "Generic Autodetecting Monitor"
        Option      "DPMS" "true"
EndSection

Section "Device"
        Identifier  "aticonfig-Device[0]-0"
        Driver      "fglrx"
        BusID       "PCI:1:0:0"
EndSection

Section "Screen"
        Identifier  "aticonfig-Screen[0]-0"
        Device      "aticonfig-Device[0]-0"
        Monitor     "aticonfig-Monitor[0]-0"
        DefaultDepth     24
        SubSection "Display"
                Viewport   0 0
                Depth    24
        EndSubSection
EndSection

Section "DRI"
        Mode         0666
EndSection

According to the xorg.conf(5) manual page:

Option “AllowMouseOpenFail”boolean

This tells the mousedrv(4) and vmmouse(4) drivers to not report failure if the mouse device can’t be opened/initialised. It has no effect on the evdev(4) or other drivers. Default: false.

so I left the section ServerFlags in xorg.conf, as the global X.Org Server option "AllowMouseOpenFail" does no harm. I could have deleted it, though.

6.  I left /usr/share/X11/xorg.conf.d/10-quirks.conf as it was, because there is nothing in it that relates to the specific hardware in my laptop. I could have just deleted the file.

Outcome

Now that I have removed the superflous X windows configuration files with some duplicate sections, /var/log/Xorg.0.log no longer contains duplicate messages relating to the touchpad and evdev. As I have also removed superflous module-loading commands from xorg.conf, there are also no longer any messages regarding already-loaded modules or the unloading of a module. And my removal of the obsolete auto-dev protocol option also eliminated the error message regarding an undetectable protocol and the PreInit error message. The file Xorg.0.log in my installation now looks like this:

[    29.801] 
X.Org X Server 1.16.3
Release Date: 2014-12-20
[    29.801] X Protocol Version 11, Revision 0
[    29.801] Build Operating System: Linux 3.17.1-gentoo-r1 x86_64 Gentoo
[    29.801] Current Operating System: Linux meshedgedx 3.17.1-gentoo-r1 #1 SMP Wed Nov 5 16:41:59 GMT 2014 x86_64
[    29.801] Kernel command line: BOOT_IMAGE=/kernel-genkernel-x86_64-3.17.1-gentoo-r1 root=/dev/sda6 ro BOOT_IMAGE=/kernel-genkernel-x86_64-3.17.1-gentoo-r1 root=/dev/ram0 ramdisk=8192 real_root=/dev/sda6 init=/linuxrc splash=silent,theme:Emergance console=tty1 quiet resume=swap:/dev/sda5 real_resume=/dev/sda5 intel_iommu=off net.ifnames=0 snd_hda_intel.power_save=0
[    29.801] Build Date: 20 January 2015  08:46:39AM
[    29.801]  
[    29.801] Current version of pixman: 0.32.6
[    29.801]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[    29.801] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    29.801] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jan 25 23:59:52 2015
[    29.846] (==) Using config file: "/etc/X11/xorg.conf"
[    29.846] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    29.846] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    29.918] (==) ServerLayout "Main Layout"
[    29.918] (**) |-->Screen "aticonfig-Screen[0]-0" (0)
[    29.918] (**) |   |-->Monitor "aticonfig-Monitor[0]-0"
[    30.063] (**) |   |-->Device "aticonfig-Device[0]-0"
[    30.063] (**) Option "AllowMouseOpenFail" "true"
[    30.063] (==) Automatically adding devices
[    30.063] (==) Automatically enabling devices
[    30.063] (==) Automatically adding GPU devices
[    30.166] (==) FontPath set to:
        /usr/share/fonts/misc/,
        /usr/share/fonts/TTF/,
        /usr/share/fonts/OTF/,
        /usr/share/fonts/Type1/,
        /usr/share/fonts/100dpi/,
        /usr/share/fonts/75dpi/
[    30.166] (**) ModulePath set to "/usr/lib32/xorg/modules,/usr/lib64/opengl/ati,/usr/lib64/xorg/modules"
[    30.166] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[    30.166] (II) Loader magic: 0x805c60
[    30.166] (II) Module ABI versions:
[    30.166]    X.Org ANSI C Emulation: 0.4
[    30.166]    X.Org Video Driver: 18.0
[    30.166]    X.Org XInput driver : 21.0
[    30.166]    X.Org Server Extension : 8.0
[    30.167] (--) PCI:*(0:1:0:0) 1002:68c1:14c0:0043 rev 0, Mem @ 0xc0000000/268435456, 0xd8000000/131072, I/O @ 0x00006000/256, BIOS @ 0x????????/131072
[    30.167] (II) "glx" will be loaded by default.
[    30.167] (II) LoadModule: "vbe"
[    30.679] (II) Loading /usr/lib64/xorg/modules/libvbe.so
[    30.692] (II) Module vbe: vendor="X.Org Foundation"
[    30.692]    compiled for 1.16.3, module version = 1.1.0
[    30.692]    ABI class: X.Org Video Driver, version 18.0
[    30.692] (II) LoadModule: "glx"
[    30.692] (II) Loading /usr/lib64/opengl/ati/extensions/libglx.so
[    30.710] (II) Module glx: vendor="Advanced Micro Devices, Inc."
[    30.710]    compiled for 6.9.0, module version = 1.0.0
[    30.710] (II) LoadModule: "fglrx"
[    30.710] (II) Loading /usr/lib64/xorg/modules/drivers/fglrx_drv.so
[    31.508] (II) Module fglrx: vendor="FireGL - AMD Technologies Inc."
[    31.508]    compiled for 1.4.99.906, module version = 14.50.2
[    31.508]    Module class: X.Org Video Driver
[    31.509] (II) Loading sub module "fglrxdrm"
[    31.509] (II) LoadModule: "fglrxdrm"
[    31.509] (II) Loading /usr/lib64/xorg/modules/linux/libfglrxdrm.so
[    31.554] (II) Module fglrxdrm: vendor="FireGL - AMD Technologies Inc."
[    31.554]    compiled for 1.4.99.906, module version = 14.50.2
[    31.554] (II) AMD Proprietary Linux Driver Version Identifier:14.50.2
[    31.554] (II) AMD Proprietary Linux Driver Release Identifier: 14.501.1003                          
[    31.554] (II) AMD Proprietary Linux Driver Build Date: Nov 20 2014 21:22:54
[    31.554] (++) using VT number 7

[    31.671] (WW) Falling back to old probe method for fglrx
[    31.855] (II) Loading PCS database from /etc/ati/amdpcsdb /etc/ati/amdpcsdb.default
[    31.892] ukiDynamicMajor: found major device number 241
[    31.893] ukiDynamicMajor: found major device number 241
[    31.893] ukiOpenByBusid: Searching for BusID PCI:1:0:0
[    31.893] ukiOpenDevice: node name is /dev/ati/card0
[    31.893] ukiOpenDevice: open result is 9, (OK)
[    33.746] ukiOpenByBusid: ukiOpenMinor returns 9
[    33.746] ukiOpenByBusid: ukiGetBusid reports PCI:1:0:0
[    34.157] (--) Chipset Supported AMD Graphics Processor (0x68C1) found
[    34.174] (WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
[    34.180] (II) fglrx(0): pEnt->device->identifier=0x1fe9bc0
[    34.180] (II) fglrx(0): === [xdl_xs116_atiddxPreInit] === begin
[    34.180] (II) fglrx(0): FB driver is enabled
[    34.180] (II) Loading sub module "vgahw"
[    34.180] (II) LoadModule: "vgahw"
[    34.180] (II) Loading /usr/lib64/xorg/modules/libvgahw.so
[    34.354] (II) Module vgahw: vendor="X.Org Foundation"
[    34.354]    compiled for 1.16.3, module version = 0.1.0
[    34.354]    ABI class: X.Org Video Driver, version 18.0
[    34.355] (**) fglrx(0): Depth 24, (--) framebuffer bpp 32
[    34.355] (II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[    34.355] (==) fglrx(0): Default visual is TrueColor
[    34.355] (**) fglrx(0): Option "DPMS" "true"
[    34.355] (==) fglrx(0): RGB weight 888
[    34.355] (II) fglrx(0): Using 8 bits per RGB 
[    34.355] (==) fglrx(0): Buffer Tiling is ON
[    34.355] (II) Loading sub module "fglrxdrm"
[    34.355] (II) LoadModule: "fglrxdrm"
[    34.355] (II) Loading /usr/lib64/xorg/modules/linux/libfglrxdrm.so
[    34.355] (II) Module fglrxdrm: vendor="FireGL - AMD Technologies Inc."
[    34.355]    compiled for 1.4.99.906, module version = 14.50.2
[    34.358] ukiDynamicMajor: found major device number 241
[    34.358] ukiDynamicMajor: found major device number 241
[    34.358] ukiOpenByBusid: Searching for BusID PCI:1:0:0
[    34.358] ukiOpenDevice: node name is /dev/ati/card0
[    34.358] ukiOpenDevice: open result is 11, (OK)
[    34.358] ukiOpenByBusid: ukiOpenMinor returns 11
[    34.358] ukiOpenByBusid: ukiGetBusid reports PCI:1:0:0
[    34.358] (**) fglrx(0): NoAccel = NO
[    34.358] (**) fglrx(0): AMD 2D Acceleration Architecture enabled
[    34.358] (--) fglrx(0): Chipset: "AMD Mobility Radeon HD 5000 Series" (Chipset = 0x68c1)
[    34.358] (--) fglrx(0): (PciSubVendor = 0x14c0, PciSubDevice = 0x0043)
[    34.358] (==) fglrx(0): board vendor info: third party graphics adapter - NOT original AMD
[    34.358] (--) fglrx(0): Linear framebuffer (phys) at 0xc0000000
[    34.358] (--) fglrx(0): MMIO registers at 0xd8000000
[    34.358] (--) fglrx(0): I/O port at 0x00006000
[    34.358] (==) fglrx(0): ROM-BIOS at 0x000c0000
[    34.561] (II) fglrx(0): AC Adapter is used
[    34.585] (II) fglrx(0): Primary V_BIOS segment is: 0xc000
[    34.631] (II) Loading sub module "vbe"
[    34.631] (II) LoadModule: "vbe"
[    34.631] (II) Loading /usr/lib64/xorg/modules/libvbe.so
[    34.631] (II) Module vbe: vendor="X.Org Foundation"
[    34.631]    compiled for 1.16.3, module version = 1.1.0
[    34.631]    ABI class: X.Org Video Driver, version 18.0
[    34.709] (II) fglrx(0): VESA BIOS detected
[    34.709] (II) fglrx(0): VESA VBE Version 3.0
[    34.709] (II) fglrx(0): VESA VBE Total Mem: 16384 kB
[    34.709] (II) fglrx(0): VESA VBE OEM: ATI ATOMBIOS
[    34.709] (II) fglrx(0): VESA VBE OEM Software Rev: 12.17
[    34.709] (II) fglrx(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies Inc. 
[    34.709] (II) fglrx(0): VESA VBE OEM Product: MADISON
[    34.709] (II) fglrx(0): VESA VBE OEM Product Rev: 01.00
[    34.709] (II) fglrx(0): AMD Video BIOS revision 9 or later detected
[    34.709] (--) fglrx(0): Video RAM: 1048576 kByte, Type: DDR3
[    34.709] (II) fglrx(0): PCIE card detected
[    34.709] (--) fglrx(0): Using per-process page tables (PPPT) as GART.
[    34.709] (WW) fglrx(0): board is an unknown third party board, chipset is supported
[    34.709] (II) fglrx(0): [FB] MC range(MCFBBase = 0xf00000000, MCFBSize = 0x40000000)
[    34.709] (II) fglrx(0): RandR 1.2 support is enabled!
[    34.709] (II) fglrx(0): RandR 1.2 rotation support is enabled!
[    34.709] (II) Loading sub module "fb"
[    34.709] (II) LoadModule: "fb"
[    34.709] (II) Loading /usr/lib64/xorg/modules/libfb.so
[    34.731] (II) Module fb: vendor="X.Org Foundation"
[    34.731]    compiled for 1.16.3, module version = 1.0.0
[    34.731]    ABI class: X.Org ANSI C Emulation, version 0.4
[    34.731] (II) fglrx(0): EDID Management option: EDID Management is enabled
[    34.731] (II) Loading sub module "ddc"
[    34.731] (II) LoadModule: "ddc"
[    34.731] (II) Module "ddc" already built-in
[    35.087] (II) fglrx(0): Output LVDS using monitor section aticonfig-Monitor[0]-0
[    35.087] (II) fglrx(0): Output DFP1 has no monitor section
[    35.087] (II) fglrx(0): Output CRT1 has no monitor section
[    35.087] (II) Loading sub module "ddc"
[    35.087] (II) LoadModule: "ddc"
[    35.087] (II) Module "ddc" already built-in
[    35.087] (II) fglrx(0): Connected Display0: LVDS
[    35.087] (II) fglrx(0): Display0 EDID data ---------------------------
[    35.087] (II) fglrx(0): Manufacturer: AUO  Model: 10ed  Serial#: 0
[    35.087] (II) fglrx(0): Year: 2008  Week: 1
[    35.087] (II) fglrx(0): EDID Version: 1.3
[    35.087] (II) fglrx(0): Digital Display Input
[    35.087] (II) fglrx(0): Max Image Size [cm]: horiz.: 34  vert.: 19
[    35.087] (II) fglrx(0): Gamma: 2.20
[    35.087] (II) fglrx(0): No DPMS capabilities specified
[    35.087] (II) fglrx(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 
[    35.087] (II) fglrx(0): First detailed timing is preferred mode
[    35.087] (II) fglrx(0): redX: 0.620 redY: 0.340   greenX: 0.330 greenY: 0.570
[    35.087] (II) fglrx(0): blueX: 0.150 blueY: 0.060   whiteX: 0.313 whiteY: 0.329
[    35.087] (II) fglrx(0): Manufacturer's mask: 0
[    35.087] (II) fglrx(0): Supported detailed timing:
[    35.087] (II) fglrx(0): clock: 134.4 MHz   Image Size:  344 x 193 mm
[    35.088] (II) fglrx(0): h_active: 1920  h_sync: 1950  h_sync_end 1970 h_blank_end 1982 h_border: 0
[    35.088] (II) fglrx(0): v_active: 1080  v_sync: 1090  v_sync_end 1100 v_blanking: 1130 v_border: 0
[    35.088] (II) fglrx(0): Unknown vendor-specific block f
[    35.088] (II) fglrx(0):  AUO
[    35.088] (II) fglrx(0):  B156HW01 V0
[    35.088] (II) fglrx(0): EDID (in hex):
[    35.088] (II) fglrx(0):     00ffffffffffff0006afed1000000000
[    35.088] (II) fglrx(0):     01120103802213780ac8959e57549226
[    35.088] (II) fglrx(0):     0f505400000001010101010101010101
[    35.088] (II) fglrx(0):     0101010101018034803e703832401e14
[    35.088] (II) fglrx(0):     aa0058c1100000180000000f00000000
[    35.088] (II) fglrx(0):     00000000000000000020000000fe0041
[    35.088] (II) fglrx(0):     554f0a202020202020202020000000fe
[    35.088] (II) fglrx(0):     004231353648573031205630200a0054
[    35.088] (II) fglrx(0): End of Display0 EDID data --------------------
[    35.088] (II) fglrx(0): Connected Display1: CRT1
[    35.088] (II) fglrx(0): Display1 EDID data ---------------------------
[    35.088] (II) fglrx(0): Manufacturer: ACR  Model: ad52  Serial#: 1426067087
[    35.088] (II) fglrx(0): Year: 2005  Week: 50
[    35.088] (II) fglrx(0): EDID Version: 1.3
[    35.088] (II) fglrx(0): Analog Display Input,  Input Voltage Level: 0.700/0.700 V
[    35.088] (II) fglrx(0): Sync:  Separate
[    35.088] (II) fglrx(0): Max Image Size [cm]: horiz.: 41  vert.: 26
[    35.088] (II) fglrx(0): Gamma: 2.20
[    35.088] (II) fglrx(0): DPMS capabilities: Off; RGB/Color Display
[    35.088] (II) fglrx(0): Default color space is primary color space
[    35.088] (II) fglrx(0): First detailed timing is preferred mode
[    35.088] (II) fglrx(0): redX: 0.642 redY: 0.348   greenX: 0.288 greenY: 0.601
[    35.088] (II) fglrx(0): blueX: 0.143 blueY: 0.072   whiteX: 0.313 whiteY: 0.329
[    35.088] (II) fglrx(0): Supported established timings:
[    35.088] (II) fglrx(0): 720x400@70Hz
[    35.088] (II) fglrx(0): 640x480@60Hz
[    35.088] (II) fglrx(0): 640x480@67Hz
[    35.088] (II) fglrx(0): 640x480@72Hz
[    35.088] (II) fglrx(0): 640x480@75Hz
[    35.088] (II) fglrx(0): 800x600@56Hz
[    35.088] (II) fglrx(0): 800x600@60Hz
[    35.088] (II) fglrx(0): 800x600@72Hz
[    35.088] (II) fglrx(0): 800x600@75Hz
[    35.088] (II) fglrx(0): 832x624@75Hz
[    35.088] (II) fglrx(0): 1024x768@60Hz
[    35.088] (II) fglrx(0): 1024x768@70Hz
[    35.088] (II) fglrx(0): 1024x768@75Hz
[    35.088] (II) fglrx(0): 1280x1024@75Hz
[    35.088] (II) fglrx(0): Manufacturer's mask: 0
[    35.088] (II) fglrx(0): Supported standard timings:
[    35.088] (II) fglrx(0): #0: hsize: 1280  vsize 1024  refresh: 60  vid: 32897
[    35.088] (II) fglrx(0): #1: hsize: 1280  vsize 960  refresh: 60  vid: 16513
[    35.088] (II) fglrx(0): #2: hsize: 1152  vsize 864  refresh: 75  vid: 20337
[    35.088] (II) fglrx(0): #3: hsize: 1440  vsize 900  refresh: 60  vid: 149
[    35.088] (II) fglrx(0): Supported detailed timing:
[    35.088] (II) fglrx(0): clock: 106.5 MHz   Image Size:  408 x 255 mm
[    35.088] (II) fglrx(0): h_active: 1440  h_sync: 1520  h_sync_end 1672 h_blank_end 1904 h_border: 0
[    35.088] (II) fglrx(0): v_active: 900  v_sync: 903  v_sync_end 909 v_blanking: 934 v_border: 0
[    35.088] (II) fglrx(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 82 kHz, PixClock max 145 MHz
[    35.088] (II) fglrx(0): Monitor name: Acer AL1916W
[    35.088] (II) fglrx(0): Serial No: ETL5209014
[    35.088] (II) fglrx(0): EDID (in hex):
[    35.088] (II) fglrx(0):     00ffffffffffff00047252ad8f0e0055
[    35.088] (II) fglrx(0):     320f010368291a782e4fa5a459499924
[    35.088] (II) fglrx(0):     125054bfef0081808140714f95000101
[    35.088] (II) fglrx(0):     0101010101019a29a0d0518422305098
[    35.088] (II) fglrx(0):     360098ff1000001c000000fd00384c1e
[    35.088] (II) fglrx(0):     520e000a202020202020000000fc0041
[    35.088] (II) fglrx(0):     63657220414c31393136570a000000ff
[    35.088] (II) fglrx(0):     0045544c35323039303134202020008c
[    35.088] (II) fglrx(0): End of Display1 EDID data --------------------
[    35.088] (II) fglrx(0): Dynamic Surface Resizing Enabled
[    35.205] (II) fglrx(0): EDID for output LVDS
[    35.205] (II) fglrx(0): Manufacturer: AUO  Model: 10ed  Serial#: 0
[    35.205] (II) fglrx(0): Year: 2008  Week: 1
[    35.205] (II) fglrx(0): EDID Version: 1.3
[    35.205] (II) fglrx(0): Digital Display Input
[    35.205] (II) fglrx(0): Max Image Size [cm]: horiz.: 34  vert.: 19
[    35.205] (II) fglrx(0): Gamma: 2.20
[    35.205] (II) fglrx(0): No DPMS capabilities specified
[    35.205] (II) fglrx(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 
[    35.205] (II) fglrx(0): First detailed timing is preferred mode
[    35.205] (II) fglrx(0): redX: 0.620 redY: 0.340   greenX: 0.330 greenY: 0.570
[    35.205] (II) fglrx(0): blueX: 0.150 blueY: 0.060   whiteX: 0.313 whiteY: 0.329
[    35.205] (II) fglrx(0): Manufacturer's mask: 0
[    35.205] (II) fglrx(0): Supported detailed timing:
[    35.205] (II) fglrx(0): clock: 134.4 MHz   Image Size:  344 x 193 mm
[    35.205] (II) fglrx(0): h_active: 1920  h_sync: 1950  h_sync_end 1970 h_blank_end 1982 h_border: 0
[    35.205] (II) fglrx(0): v_active: 1080  v_sync: 1090  v_sync_end 1100 v_blanking: 1130 v_border: 0
[    35.205] (II) fglrx(0): Unknown vendor-specific block f
[    35.205] (II) fglrx(0):  AUO
[    35.205] (II) fglrx(0):  B156HW01 V0
[    35.205] (II) fglrx(0): EDID (in hex):
[    35.205] (II) fglrx(0):     00ffffffffffff0006afed1000000000
[    35.205] (II) fglrx(0):     01120103802213780ac8959e57549226
[    35.205] (II) fglrx(0):     0f505400000001010101010101010101
[    35.205] (II) fglrx(0):     0101010101018034803e703832401e14
[    35.205] (II) fglrx(0):     aa0058c1100000180000000f00000000
[    35.205] (II) fglrx(0):     00000000000000000020000000fe0041
[    35.205] (II) fglrx(0):     554f0a202020202020202020000000fe
[    35.205] (II) fglrx(0):     004231353648573031205630200a0054
[    35.205] (II) fglrx(0): EDID vendor "AUO", prod id 4333
[    35.205] (II) fglrx(0): Printing DDC gathered Modelines:
[    35.205] (II) fglrx(0): Modeline "1920x1080"x0.0  134.40  1920 1950 1970 1982  1080 1090 1100 1130 -hsync -vsync (67.8 kHz eP)
[    35.205] (II) fglrx(0): Printing probed modes for output LVDS
[    35.205] (II) fglrx(0): Modeline "1920x1080"x60.0  134.40  1920 1950 1970 1982  1080 1090 1100 1130 -hsync -vsync (67.8 kHz eP)
[    35.205] (II) fglrx(0): Modeline "1680x1050"x60.0  134.40  1680 1950 1970 1982  1050 1090 1100 1130 -hsync -vsync (67.8 kHz e)
[    35.205] (II) fglrx(0): Modeline "1400x1050"x60.0  134.40  1400 1950 1970 1982  1050 1090 1100 1130 -hsync -vsync (67.8 kHz e)
[    35.205] (II) fglrx(0): Modeline "1600x900"x60.0  134.40  1600 1950 1970 1982  900 1090 1100 1130 -hsync -vsync (67.8 kHz e)
[    35.205] (II) fglrx(0): Modeline "1280x1024"x60.0  134.40  1280 1950 1970 1982  1024 1090 1100 1130 -hsync -vsync (67.8 kHz e)
[    35.205] (II) fglrx(0): Modeline "1440x900"x60.0  134.40  1440 1950 1970 1982  900 1090 1100 1130 -hsync -vsync (67.8 kHz e)
[    35.205] (II) fglrx(0): Modeline "1280x960"x60.0  134.40  1280 1950 1970 1982  960 1090 1100 1130 -hsync -vsync (67.8 kHz e)
[    35.205] (II) fglrx(0): Modeline "1280x768"x60.0  134.40  1280 1950 1970 1982  768 1090 1100 1130 -hsync -vsync (67.8 kHz e)
[    35.205] (II) fglrx(0): Modeline "1280x720"x60.0  134.40  1280 1950 1970 1982  720 1090 1100 1130 -hsync -vsync (67.8 kHz e)
[    35.205] (II) fglrx(0): Modeline "1024x768"x60.0  134.40  1024 1950 1970 1982  768 1090 1100 1130 -hsync -vsync (67.8 kHz e)
[    35.205] (II) fglrx(0): Modeline "1024x600"x60.0  134.40  1024 1950 1970 1982  600 1090 1100 1130 -hsync -vsync (67.8 kHz e)
[    35.205] (II) fglrx(0): Modeline "800x600"x60.0  134.40  800 1950 1970 1982  600 1090 1100 1130 -hsync -vsync (67.8 kHz e)
[    35.205] (II) fglrx(0): Modeline "800x480"x60.0  134.40  800 1950 1970 1982  480 1090 1100 1130 -hsync -vsync (67.8 kHz e)
[    35.205] (II) fglrx(0): Modeline "640x480"x60.0  134.40  640 1950 1970 1982  480 1090 1100 1130 -hsync -vsync (67.8 kHz e)
[    35.205] (II) fglrx(0): EDID for output DFP1
[    35.205] (II) fglrx(0): EDID for output CRT1
[    35.205] (II) fglrx(0): Manufacturer: ACR  Model: ad52  Serial#: 1426067087
[    35.205] (II) fglrx(0): Year: 2005  Week: 50
[    35.205] (II) fglrx(0): EDID Version: 1.3
[    35.205] (II) fglrx(0): Analog Display Input,  Input Voltage Level: 0.700/0.700 V
[    35.205] (II) fglrx(0): Sync:  Separate
[    35.205] (II) fglrx(0): Max Image Size [cm]: horiz.: 41  vert.: 26
[    35.205] (II) fglrx(0): Gamma: 2.20
[    35.205] (II) fglrx(0): DPMS capabilities: Off; RGB/Color Display
[    35.205] (II) fglrx(0): Default color space is primary color space
[    35.205] (II) fglrx(0): First detailed timing is preferred mode
[    35.205] (II) fglrx(0): redX: 0.642 redY: 0.348   greenX: 0.288 greenY: 0.601
[    35.205] (II) fglrx(0): blueX: 0.143 blueY: 0.072   whiteX: 0.313 whiteY: 0.329
[    35.205] (II) fglrx(0): Supported established timings:
[    35.205] (II) fglrx(0): 720x400@70Hz
[    35.205] (II) fglrx(0): 640x480@60Hz
[    35.205] (II) fglrx(0): 640x480@67Hz
[    35.205] (II) fglrx(0): 640x480@72Hz
[    35.205] (II) fglrx(0): 640x480@75Hz
[    35.205] (II) fglrx(0): 800x600@56Hz
[    35.205] (II) fglrx(0): 800x600@60Hz
[    35.205] (II) fglrx(0): 800x600@72Hz
[    35.205] (II) fglrx(0): 800x600@75Hz
[    35.205] (II) fglrx(0): 832x624@75Hz
[    35.205] (II) fglrx(0): 1024x768@60Hz
[    35.205] (II) fglrx(0): 1024x768@70Hz
[    35.205] (II) fglrx(0): 1024x768@75Hz
[    35.205] (II) fglrx(0): 1280x1024@75Hz
[    35.205] (II) fglrx(0): Manufacturer's mask: 0
[    35.205] (II) fglrx(0): Supported standard timings:
[    35.205] (II) fglrx(0): #0: hsize: 1280  vsize 1024  refresh: 60  vid: 32897
[    35.205] (II) fglrx(0): #1: hsize: 1280  vsize 960  refresh: 60  vid: 16513
[    35.205] (II) fglrx(0): #2: hsize: 1152  vsize 864  refresh: 75  vid: 20337
[    35.205] (II) fglrx(0): #3: hsize: 1440  vsize 900  refresh: 60  vid: 149
[    35.205] (II) fglrx(0): Supported detailed timing:
[    35.205] (II) fglrx(0): clock: 106.5 MHz   Image Size:  408 x 255 mm
[    35.205] (II) fglrx(0): h_active: 1440  h_sync: 1520  h_sync_end 1672 h_blank_end 1904 h_border: 0
[    35.205] (II) fglrx(0): v_active: 900  v_sync: 903  v_sync_end 909 v_blanking: 934 v_border: 0
[    35.205] (II) fglrx(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 82 kHz, PixClock max 145 MHz
[    35.205] (II) fglrx(0): Monitor name: Acer AL1916W
[    35.205] (II) fglrx(0): Serial No: ETL5209014
[    35.205] (II) fglrx(0): EDID (in hex):
[    35.205] (II) fglrx(0):     00ffffffffffff00047252ad8f0e0055
[    35.205] (II) fglrx(0):     320f010368291a782e4fa5a459499924
[    35.205] (II) fglrx(0):     125054bfef0081808140714f95000101
[    35.205] (II) fglrx(0):     0101010101019a29a0d0518422305098
[    35.205] (II) fglrx(0):     360098ff1000001c000000fd00384c1e
[    35.205] (II) fglrx(0):     520e000a202020202020000000fc0041
[    35.205] (II) fglrx(0):     63657220414c31393136570a000000ff
[    35.205] (II) fglrx(0):     0045544c35323039303134202020008c
[    35.205] (II) fglrx(0): Printing probed modes for output CRT1
[    35.205] (II) fglrx(0): Modeline "1440x900"x60.0  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz eP)
[    35.205] (II) fglrx(0): Modeline "1280x1024"x75.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[    35.205] (II) fglrx(0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[    35.205] (II) fglrx(0): Modeline "1280x960"x60.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
[    35.205] (II) fglrx(0): Modeline "1280x800"x60.0  108.00  1280 1376 1488 1800  800 961 964 1000 +hsync +vsync (60.0 kHz e)
[    35.205] (II) fglrx(0): Modeline "1152x864"x75.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[    35.205] (II) fglrx(0): Modeline "1152x864"x60.0  106.50  1152 1520 1672 1904  864 903 909 934 -hsync +vsync (55.9 kHz e)
[    35.205] (II) fglrx(0): Modeline "1280x768"x60.0  108.00  1280 1376 1488 1800  768 961 964 1000 +hsync +vsync (60.0 kHz e)
[    35.205] (II) fglrx(0): Modeline "1280x720"x60.0  108.00  1280 1376 1488 1800  720 961 964 1000 +hsync +vsync (60.0 kHz e)
[    35.205] (II) fglrx(0): Modeline "1024x768"x75.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[    35.205] (II) fglrx(0): Modeline "1024x768"x70.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[    35.205] (II) fglrx(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    35.205] (II) fglrx(0): Modeline "1024x600"x75.0   78.75  1024 1040 1136 1312  600 769 772 800 +hsync +vsync (60.0 kHz e)
[    35.205] (II) fglrx(0): Modeline "1024x600"x70.0   75.00  1024 1048 1184 1328  600 771 777 806 -hsync -vsync (56.5 kHz e)
[    35.205] (II) fglrx(0): Modeline "1024x600"x60.0   65.00  1024 1048 1184 1344  600 771 777 806 -hsync -vsync (48.4 kHz e)
[    35.205] (II) fglrx(0): Modeline "800x600"x72.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz e)
[    35.205] (II) fglrx(0): Modeline "800x600"x75.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[    35.206] (II) fglrx(0): Modeline "800x600"x60.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    35.206] (II) fglrx(0): Modeline "800x600"x56.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[    35.206] (II) fglrx(0): Modeline "800x480"x72.0   50.00  800 856 976 1040  480 637 643 666 +hsync +vsync (48.1 kHz e)
[    35.206] (II) fglrx(0): Modeline "800x480"x75.0   49.50  800 816 896 1056  480 601 604 625 +hsync +vsync (46.9 kHz e)
[    35.206] (II) fglrx(0): Modeline "800x480"x60.0   40.00  800 840 968 1056  480 601 605 628 +hsync +vsync (37.9 kHz e)
[    35.206] (II) fglrx(0): Modeline "800x480"x56.0   36.00  800 824 896 1024  480 601 603 625 +hsync +vsync (35.2 kHz e)
[    35.206] (II) fglrx(0): Modeline "640x480"x75.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[    35.206] (II) fglrx(0): Modeline "640x480"x72.0   31.50  640 656 696 832  480 481 484 520 -hsync -vsync (37.9 kHz e)
[    35.206] (II) fglrx(0): Modeline "640x480"x67.0   27.28  640 664 728 816  480 481 484 499 -hsync +vsync (33.4 kHz e)
[    35.206] (II) fglrx(0): Modeline "640x480"x60.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    35.206] (II) fglrx(0): Output LVDS connected
[    35.206] (II) fglrx(0): Output DFP1 disconnected
[    35.206] (II) fglrx(0): Output CRT1 connected
[    35.206] (II) fglrx(0): Using exact sizes for initial modes
[    35.206] (II) fglrx(0): Output LVDS using initial mode 1440x900
[    35.206] (II) fglrx(0): Output CRT1 using initial mode 1440x900
[    35.206] (II) fglrx(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[    35.206] (II) fglrx(0): Setting highest common mode
[    35.206] (II) fglrx(0): Display dimensions: (340, 190) mm
[    35.206] (II) fglrx(0): DPI set to (107, 120)
[    35.206] (II) fglrx(0): Eyefinity capable adapter detected.
[    35.206] (II) fglrx(0): Adapter AMD Mobility Radeon HD 5000 Series has 6 configurable heads and 2 displays connected.
[    35.206] (==) fglrx(0):  PseudoColor visuals disabled
[    35.206] (II) Loading sub module "ramdac"
[    35.206] (II) LoadModule: "ramdac"
[    35.206] (II) Module "ramdac" already built-in
[    35.206] (==) fglrx(0): NoDRI = NO
[    35.206] (==) fglrx(0): Capabilities: 0x00000000
[    35.206] (==) fglrx(0): CapabilitiesEx: 0x00000000
[    35.206] (==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
[    35.206] (==) fglrx(0): UseFastTLS=0
[    35.206] (II) fglrx(0): Shadow Primary option: ShadowPrimary is enabled
[    35.206] (--) Depth 24 pixmap format is 32 bpp
[    35.206] (II) fglrx(0): doing swlDriScreenInit
[    35.206] (II) fglrx(0): swlDriScreenInit for fglrx driver
[    35.206] ukiDynamicMajor: found major device number 241
[    35.206] ukiDynamicMajor: found major device number 241
[    35.206] ukiDynamicMajor: found major device number 241
[    35.206] ukiOpenByBusid: Searching for BusID PCI:1:0:0
[    35.206] ukiOpenDevice: node name is /dev/ati/card0
[    35.206] ukiOpenDevice: open result is 12, (OK)
[    35.206] ukiOpenByBusid: ukiOpenMinor returns 12
[    35.206] ukiOpenByBusid: ukiGetBusid reports PCI:1:0:0
[    35.206] (II) fglrx(0): [uki] DRM interface version 1.0
[    35.206] (II) fglrx(0): [uki] created "fglrx" driver at busid "PCI:1:0:0"
[    35.206] (II) fglrx(0): [uki] added 8192 byte SAREA at 0x2000
[    35.206] (II) fglrx(0): [uki] mapped SAREA 0x2000 to 0x7f5337485000
[    35.206] (II) fglrx(0): [uki] framebuffer handle = 0x3000
[    35.206] (II) fglrx(0): [uki] added 1 reserved context for kernel
[    35.206] (II) fglrx(0): swlDriScreenInit done
[    35.206] (II) fglrx(0): Kernel Module Version Information:
[    35.206] (II) fglrx(0):     Name: fglrx
[    35.206] (II) fglrx(0):     Version: 14.50.2
[    35.206] (II) fglrx(0):     Date: Nov 20 2014
[    35.206] (II) fglrx(0):     Desc: AMD FireGL DRM kernel module
[    35.206] (II) fglrx(0): Kernel Module version matches driver.
[    35.206] (II) fglrx(0): Kernel Module Build Time Information:
[    35.206] (II) fglrx(0):     Build-Kernel UTS_RELEASE:        3.17.1-gentoo-r1
[    35.206] (II) fglrx(0):     Build-Kernel MODVERSIONS:        yes
[    35.206] (II) fglrx(0):     Build-Kernel __SMP__:            yes
[    35.206] (II) fglrx(0):     Build-Kernel PAGE_SIZE:          0x1000
[    35.206] (II) fglrx(0): [uki] register handle = 0x00004000
[    35.209] (II) fglrx(0): Display width adjusted to to 1536 due to alignment constraints
[    35.209] (II) fglrx(0): DRI initialization successfull
[    35.240] (II) fglrx(0): FBADPhys: 0xf00000000 FBMappedSize: 0x010e0000
[    35.252] (==) fglrx(0): Backing store enabled
[    35.252] (**) fglrx(0): DPMS enabled
[    35.252] (II) fglrx(0): Initialized in-driver Xinerama extension
[    35.252] (**) fglrx(0): Textured Video is enabled.
[    35.252] (II) LoadModule: "glesx"
[    35.252] (II) Loading /usr/lib64/xorg/modules/glesx.so
[    35.649] (II) Module glesx: vendor="X.Org Foundation"
[    35.649]    compiled for 1.4.99.906, module version = 1.0.0
[    35.649] (II) fglrx(0): GLESX enableFlags = 8784
[    35.656] (II) fglrx(0): GLESX is enabled
[    35.656] (II) LoadModule: "amdxmm"
[    35.656] (II) Loading /usr/lib64/xorg/modules/amdxmm.so
[    35.667] (II) Module amdxmm: vendor="X.Org Foundation"
[    35.667]    compiled for 1.4.99.906, module version = 2.0.0
[    35.758] (II) fglrx(0): UVD feature is enabled(II) fglrx(0): 
[    35.768] (II) fglrx(0): Enable composite support successfully
[    35.768] (WW) fglrx(0): Option "VendorName" is not used
[    35.768] (WW) fglrx(0): Option "ModelName" is not used
[    35.768] (II) fglrx(0): X context handle = 0x1
[    35.768] (II) fglrx(0): [DRI] installation complete
[    35.768] (==) fglrx(0): Silken mouse enabled
[    35.776] (==) fglrx(0): Using HW cursor of display infrastructure!
[    35.777] (II) fglrx(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[    35.780] (II) fglrx(0): 'LVDS LCD' ConnectorType, abstracted as 'Panel'
[    35.780] (II) fglrx(0): 'eDP LCD' ConnectorType, abstracted as 'Panel'
[    36.472] (--) RandR disabled
[    36.495] ukiDynamicMajor: found major device number 241
[    36.495] ukiDynamicMajor: found major device number 241
[    36.495] ukiOpenByBusid: Searching for BusID PCI:1:0:0
[    36.495] ukiOpenDevice: node name is /dev/ati/card0
[    36.496] ukiOpenDevice: open result is 13, (OK)
[    36.496] ukiOpenByBusid: ukiOpenMinor returns 13
[    36.496] ukiOpenByBusid: ukiGetBusid reports PCI:1:0:0
[    36.834] ukiDynamicMajor: found major device number 241
[    36.834] ukiDynamicMajor: found major device number 241
[    36.834] ukiDynamicMajor: found major device number 241
[    36.834] ukiOpenDevice: node name is /dev/ati/card0
[    36.834] ukiOpenDevice: open result is 14, (OK)
[    36.834] ukiGetBusid returned 'PCI:1:0:0'
[    36.834] ukiOpenDevice: node name is /dev/ati/card1
[    36.834] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: Open failed
[    36.835] ukiOpenDevice: node name is /dev/ati/card2
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: Open failed
[    36.835] ukiOpenDevice: node name is /dev/ati/card3
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: Open failed
[    36.835] ukiOpenDevice: node name is /dev/ati/card4
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: Open failed
[    36.835] ukiOpenDevice: node name is /dev/ati/card5
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: Open failed
[    36.835] ukiOpenDevice: node name is /dev/ati/card6
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: Open failed
[    36.835] ukiOpenDevice: node name is /dev/ati/card7
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: Open failed
[    36.835] ukiOpenDevice: node name is /dev/ati/card8
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: Open failed
[    36.835] ukiOpenDevice: node name is /dev/ati/card9
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: Open failed
[    36.835] ukiOpenDevice: node name is /dev/ati/card10
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: Open failed
[    36.835] ukiOpenDevice: node name is /dev/ati/card11
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: Open failed
[    36.835] ukiOpenDevice: node name is /dev/ati/card12
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: Open failed
[    36.835] ukiOpenDevice: node name is /dev/ati/card13
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: Open failed
[    36.835] ukiOpenDevice: node name is /dev/ati/card14
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: Open failed
[    36.835] ukiOpenDevice: node name is /dev/ati/card15
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: open result is -1, (No such device)
[    36.835] ukiOpenDevice: Open failed
[    36.835] ukiDynamicMajor: found major device number 241
[    36.835] ukiOpenByBusid: Searching for BusID PCI:1:0:0
[    36.835] ukiOpenDevice: node name is /dev/ati/card0
[    36.835] ukiOpenDevice: open result is 14, (OK)
[    36.835] ukiOpenByBusid: ukiOpenMinor returns 14
[    36.835] ukiOpenByBusid: ukiGetBusid reports PCI:1:0:0
[    38.352] (II) AIGLX: Loaded and initialized OpenGL driver(II) GLX: Initialized DRI GL provider for screen 0
[    38.353] ukiDynamicMajor: found major device number 241
[    38.353] ukiDynamicMajor: found major device number 241
[    38.353] ukiDynamicMajor: found major device number 241
[    38.353] ukiOpenDevice: node name is /dev/ati/card0
[    38.353] ukiOpenDevice: open result is 15, (OK)
[    38.353] ukiGetBusid returned 'PCI:1:0:0'
[    38.353] ukiOpenDevice: node name is /dev/ati/card1
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: Open failed
[    38.353] ukiOpenDevice: node name is /dev/ati/card2
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: Open failed
[    38.353] ukiOpenDevice: node name is /dev/ati/card3
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: Open failed
[    38.353] ukiOpenDevice: node name is /dev/ati/card4
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: Open failed
[    38.353] ukiOpenDevice: node name is /dev/ati/card5
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: Open failed
[    38.353] ukiOpenDevice: node name is /dev/ati/card6
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: Open failed
[    38.353] ukiOpenDevice: node name is /dev/ati/card7
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: Open failed
[    38.353] ukiOpenDevice: node name is /dev/ati/card8
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: Open failed
[    38.353] ukiOpenDevice: node name is /dev/ati/card9
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: Open failed
[    38.353] ukiOpenDevice: node name is /dev/ati/card10
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: Open failed
[    38.353] ukiOpenDevice: node name is /dev/ati/card11
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: Open failed
[    38.353] ukiOpenDevice: node name is /dev/ati/card12
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: Open failed
[    38.353] ukiOpenDevice: node name is /dev/ati/card13
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: Open failed
[    38.353] ukiOpenDevice: node name is /dev/ati/card14
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: Open failed
[    38.353] ukiOpenDevice: node name is /dev/ati/card15
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: open result is -1, (No such device)
[    38.353] ukiOpenDevice: Open failed
[    38.353] ukiDynamicMajor: found major device number 241
[    38.353] ukiOpenByBusid: Searching for BusID PCI:1:0:0
[    38.353] ukiOpenDevice: node name is /dev/ati/card0
[    38.353] ukiOpenDevice: open result is 15, (OK)
[    38.353] ukiOpenByBusid: ukiOpenMinor returns 15
[    38.353] ukiOpenByBusid: ukiGetBusid reports PCI:1:0:0
[    38.707] (II) fglrx(0): Setting screen physical size to 381 x 238
[    39.511] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[    39.511] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    39.511] (II) LoadModule: "evdev"
[    39.511] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
[    39.776] (II) Module evdev: vendor="X.Org Foundation"
[    39.776]    compiled for 1.16.3, module version = 2.9.1
[    39.776]    Module class: X.Org XInput Driver
[    39.776]    ABI class: X.Org XInput driver, version 21.0
[    39.776] (II) Using input driver 'evdev' for 'Power Button'
[    39.776] (**) Power Button: always reports core events
[    39.776] (**) evdev: Power Button: Device: "/dev/input/event3"
[    39.776] (--) evdev: Power Button: Vendor 0 Product 0x1
[    39.776] (--) evdev: Power Button: Found keys
[    39.776] (II) evdev: Power Button: Configuring as keyboard
[    39.776] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
[    39.776] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[    39.776] (**) Option "xkb_rules" "evdev"
[    39.776] (**) Option "xkb_model" "pc104"
[    39.776] (**) Option "xkb_layout" "us"
[    39.803] (II) config/udev: Adding input device Video Bus (/dev/input/event9)
[    39.803] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[    39.803] (II) Using input driver 'evdev' for 'Video Bus'
[    39.803] (**) Video Bus: always reports core events
[    39.803] (**) evdev: Video Bus: Device: "/dev/input/event9"
[    39.803] (--) evdev: Video Bus: Vendor 0 Product 0x6
[    39.803] (--) evdev: Video Bus: Found keys
[    39.803] (II) evdev: Video Bus: Configuring as keyboard
[    39.803] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:08/LNXVIDEO:01/input/input10/event9"
[    39.803] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[    39.803] (**) Option "xkb_rules" "evdev"
[    39.803] (**) Option "xkb_model" "pc104"
[    39.803] (**) Option "xkb_layout" "us"
[    39.804] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[    39.804] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    39.804] (II) Using input driver 'evdev' for 'Power Button'
[    39.804] (**) Power Button: always reports core events
[    39.804] (**) evdev: Power Button: Device: "/dev/input/event0"
[    39.804] (--) evdev: Power Button: Vendor 0 Product 0x1
[    39.804] (--) evdev: Power Button: Found keys
[    39.804] (II) evdev: Power Button: Configuring as keyboard
[    39.804] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:10/PNP0C0C:00/input/input0/event0"
[    39.804] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[    39.804] (**) Option "xkb_rules" "evdev"
[    39.804] (**) Option "xkb_model" "pc104"
[    39.804] (**) Option "xkb_layout" "us"
[    39.805] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
[    39.805] (II) No input driver specified, ignoring this device.
[    39.805] (II) This device may have been added with another device file.
[    39.805] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
[    39.805] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[    39.805] (II) Using input driver 'evdev' for 'Sleep Button'
[    39.805] (**) Sleep Button: always reports core events
[    39.805] (**) evdev: Sleep Button: Device: "/dev/input/event2"
[    39.805] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[    39.805] (--) evdev: Sleep Button: Found keys
[    39.805] (II) evdev: Sleep Button: Configuring as keyboard
[    39.805] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:10/PNP0C0E:00/input/input2/event2"
[    39.805] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
[    39.805] (**) Option "xkb_rules" "evdev"
[    39.805] (**) Option "xkb_model" "pc104"
[    39.805] (**) Option "xkb_layout" "us"
[    39.805] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=3 (/dev/input/event11)
[    39.805] (II) No input driver specified, ignoring this device.
[    39.805] (II) This device may have been added with another device file.
[    39.806] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event12)
[    39.806] (II) No input driver specified, ignoring this device.
[    39.806] (II) This device may have been added with another device file.
[    39.806] (II) config/udev: Adding input device HDA Intel MID Mic (/dev/input/event13)
[    39.806] (II) No input driver specified, ignoring this device.
[    39.806] (II) This device may have been added with another device file.
[    39.807] (II) config/udev: Adding input device HDA Intel MID Headphone (/dev/input/event14)
[    39.807] (II) No input driver specified, ignoring this device.
[    39.807] (II) This device may have been added with another device file.
[    39.808] (II) config/udev: Adding input device Microsoft Microsoft Optical Mouse with Tilt Wheel (/dev/input/event6)
[    39.808] (**) Microsoft Microsoft Optical Mouse with Tilt Wheel: Applying InputClass "evdev pointer catchall"
[    39.808] (II) Using input driver 'evdev' for 'Microsoft Microsoft Optical Mouse with Tilt Wheel'
[    39.808] (**) Microsoft Microsoft Optical Mouse with Tilt Wheel: always reports core events
[    39.808] (**) evdev: Microsoft Microsoft Optical Mouse with Tilt Wheel: Device: "/dev/input/event6"
[    39.808] (--) evdev: Microsoft Microsoft Optical Mouse with Tilt Wheel: Vendor 0x45e Product 0xd1
[    39.808] (--) evdev: Microsoft Microsoft Optical Mouse with Tilt Wheel: Found 9 mouse buttons
[    39.808] (--) evdev: Microsoft Microsoft Optical Mouse with Tilt Wheel: Found scroll wheel(s)
[    39.808] (--) evdev: Microsoft Microsoft Optical Mouse with Tilt Wheel: Found relative axes
[    39.808] (--) evdev: Microsoft Microsoft Optical Mouse with Tilt Wheel: Found x and y relative axes
[    39.808] (II) evdev: Microsoft Microsoft Optical Mouse with Tilt Wheel: Configuring as mouse
[    39.808] (II) evdev: Microsoft Microsoft Optical Mouse with Tilt Wheel: Adding scrollwheel support
[    39.808] (**) evdev: Microsoft Microsoft Optical Mouse with Tilt Wheel: YAxisMapping: buttons 4 and 5
[    39.808] (**) evdev: Microsoft Microsoft Optical Mouse with Tilt Wheel: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    39.808] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/0003:045E:00D1.0001/input/input7/event6"
[    39.808] (II) XINPUT: Adding extended input device "Microsoft Microsoft Optical Mouse with Tilt Wheel" (type: MOUSE, id 10)
[    39.808] (II) evdev: Microsoft Microsoft Optical Mouse with Tilt Wheel: initialized for relative axes.
[    39.809] (**) Microsoft Microsoft Optical Mouse with Tilt Wheel: (accel) keeping acceleration scheme 1
[    39.809] (**) Microsoft Microsoft Optical Mouse with Tilt Wheel: (accel) acceleration profile 0
[    39.809] (**) Microsoft Microsoft Optical Mouse with Tilt Wheel: (accel) acceleration factor: 2.000
[    39.809] (**) Microsoft Microsoft Optical Mouse with Tilt Wheel: (accel) acceleration threshold: 4
[    39.809] (II) config/udev: Adding input device Microsoft Microsoft Optical Mouse with Tilt Wheel (/dev/input/mouse1)
[    39.809] (II) No input driver specified, ignoring this device.
[    39.809] (II) This device may have been added with another device file.
[    39.810] (II) config/udev: Adding input device USB 2.0 Camera (/dev/input/event15)
[    39.810] (**) USB 2.0 Camera: Applying InputClass "evdev keyboard catchall"
[    39.810] (II) Using input driver 'evdev' for 'USB 2.0 Camera'
[    39.810] (**) USB 2.0 Camera: always reports core events
[    39.810] (**) evdev: USB 2.0 Camera: Device: "/dev/input/event15"
[    39.810] (--) evdev: USB 2.0 Camera: Vendor 0x64e Product 0xa115
[    39.810] (--) evdev: USB 2.0 Camera: Found keys
[    39.810] (II) evdev: USB 2.0 Camera: Configuring as keyboard
[    39.810] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/input/input16/event15"
[    39.810] (II) XINPUT: Adding extended input device "USB 2.0 Camera" (type: KEYBOARD, id 11)
[    39.810] (**) Option "xkb_rules" "evdev"
[    39.810] (**) Option "xkb_model" "pc104"
[    39.810] (**) Option "xkb_layout" "us"
[    39.812] (II) config/udev: Adding input device NOVATEK USB Keyboard (/dev/input/event7)
[    39.812] (**) NOVATEK USB Keyboard: Applying InputClass "evdev keyboard catchall"
[    39.812] (II) Using input driver 'evdev' for 'NOVATEK USB Keyboard'
[    39.812] (**) NOVATEK USB Keyboard: always reports core events
[    39.812] (**) evdev: NOVATEK USB Keyboard: Device: "/dev/input/event7"
[    39.812] (--) evdev: NOVATEK USB Keyboard: Vendor 0x603 Product 0xf2
[    39.812] (--) evdev: NOVATEK USB Keyboard: Found keys
[    39.812] (II) evdev: NOVATEK USB Keyboard: Configuring as keyboard
[    39.812] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.4/2-1.6.4:1.0/0003:0603:00F2.0002/input/input8/event7"
[    39.812] (II) XINPUT: Adding extended input device "NOVATEK USB Keyboard" (type: KEYBOARD, id 12)
[    39.812] (**) Option "xkb_rules" "evdev"
[    39.812] (**) Option "xkb_model" "pc104"
[    39.812] (**) Option "xkb_layout" "us"
[    39.812] (II) config/udev: Adding input device NOVATEK USB Keyboard (/dev/input/event8)
[    39.812] (**) NOVATEK USB Keyboard: Applying InputClass "evdev keyboard catchall"
[    39.812] (II) Using input driver 'evdev' for 'NOVATEK USB Keyboard'
[    39.812] (**) NOVATEK USB Keyboard: always reports core events
[    39.812] (**) evdev: NOVATEK USB Keyboard: Device: "/dev/input/event8"
[    39.812] (--) evdev: NOVATEK USB Keyboard: Vendor 0x603 Product 0xf2
[    39.812] (--) evdev: NOVATEK USB Keyboard: Found 20 mouse buttons
[    39.812] (--) evdev: NOVATEK USB Keyboard: Found keys
[    39.812] (II) evdev: NOVATEK USB Keyboard: Forcing relative x/y axes to exist.
[    39.812] (II) evdev: NOVATEK USB Keyboard: Configuring as mouse
[    39.812] (II) evdev: NOVATEK USB Keyboard: Configuring as keyboard
[    39.812] (**) evdev: NOVATEK USB Keyboard: YAxisMapping: buttons 4 and 5
[    39.812] (**) evdev: NOVATEK USB Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    39.812] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.4/2-1.6.4:1.1/0003:0603:00F2.0003/input/input9/event8"
[    39.812] (II) XINPUT: Adding extended input device "NOVATEK USB Keyboard" (type: KEYBOARD, id 13)
[    39.812] (**) Option "xkb_rules" "evdev"
[    39.812] (**) Option "xkb_model" "pc104"
[    39.812] (**) Option "xkb_layout" "us"
[    39.813] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event4)
[    39.813] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[    39.813] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[    39.813] (**) AT Translated Set 2 keyboard: always reports core events
[    39.813] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event4"
[    39.813] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[    39.813] (--) evdev: AT Translated Set 2 keyboard: Found keys
[    39.813] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[    39.813] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input4/event4"
[    39.813] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 14)
[    39.813] (**) Option "xkb_rules" "evdev"
[    39.813] (**) Option "xkb_model" "pc104"
[    39.813] (**) Option "xkb_layout" "us"
[    39.813] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event5)
[    39.813] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[    39.813] (II) LoadModule: "synaptics"
[    39.814] (II) Loading /usr/lib64/xorg/modules/input/synaptics_drv.so
[    39.857] (II) Module synaptics: vendor="X.Org Foundation"
[    39.857]    compiled for 1.16.3, module version = 1.8.1
[    39.857]    Module class: X.Org XInput Driver
[    39.857]    ABI class: X.Org XInput driver, version 21.0
[    39.857] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[    39.857] (**) SynPS/2 Synaptics TouchPad: always reports core events
[    39.857] (**) Option "Device" "/dev/input/event5"
[    39.887] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5772 (res 69)
[    39.887] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 5086 (res 118)
[    39.887] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[    39.887] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[    39.887] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right
[    39.887] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[    39.887] (**) Option "FingerLow" "35"
[    39.887] (**) Option "FingerHigh" "40"
[    39.887] (**) Option "EmulateTwoFingerMinZ" "40"
[    39.887] (**) Option "EmulateTwoFingerMinW" "8"
[    39.887] (**) Option "VertEdgeScroll" "on"
[    39.887] (**) Option "HorizEdgeScroll" "on"
[    39.887] (**) Option "VertTwoFingerScroll" "on"
[    39.887] (**) Option "HorizTwoFingerScroll" "on"
[    39.887] (**) Option "TapButton1" "1"
[    39.887] (**) Option "TapButton2" "2"
[    39.887] (**) Option "TapButton3" "3"
[    39.887] (**) Option "CircularScrolling" "on"
[    39.887] (**) Option "CircScrollTrigger" "0"
[    39.887] (**) Option "CoastingSpeed" "0"
[    39.887] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[    39.887] (**) SynPS/2 Synaptics TouchPad: always reports core events
[    39.899] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input6/event5"
[    39.899] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 15)
[    39.899] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[    39.899] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
[    39.899] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.035
[    39.899] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[    39.899] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[    39.899] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[    39.899] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[    39.899] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[    39.900] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[    39.900] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
[    39.900] (II) config/udev: Adding input device PC Speaker (/dev/input/event10)
[    39.900] (II) No input driver specified, ignoring this device.
[    39.900] (II) This device may have been added with another device file.
[    39.906] (II) fglrx(0): Restoring Recent Mode via PCS is not supported in RANDR 1.2 capable environments
[    70.796] (II) fglrx(0): EDID vendor "ACR", prod id 44370
[    70.796] (II) fglrx(0): Using hsync ranges from config file
[    70.796] (II) fglrx(0): Using vrefresh ranges from config file
[    70.796] (II) fglrx(0): Printing DDC gathered Modelines:
[    70.796] (II) fglrx(0): Modeline "1440x900"x0.0  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz eP)
[    70.796] (II) fglrx(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    70.796] (II) fglrx(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[    70.796] (II) fglrx(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[    70.796] (II) fglrx(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz e)
[    70.796] (II) fglrx(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
[    70.796] (II) fglrx(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    70.796] (II) fglrx(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[    70.796] (II) fglrx(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[    70.796] (II) fglrx(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[    70.796] (II) fglrx(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[    70.797] (II) fglrx(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    70.797] (II) fglrx(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz e)
[    70.797] (II) fglrx(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[    70.797] (II) fglrx(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz e)
[    70.797] (II) fglrx(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[    70.797] (II) fglrx(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
[    70.797] (II) fglrx(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[    72.599] (II) fglrx(0): EDID vendor "ACR", prod id 44370
[    72.599] (II) fglrx(0): Using hsync ranges from config file
[    72.599] (II) fglrx(0): Using vrefresh ranges from config file
[    72.599] (II) fglrx(0): Printing DDC gathered Modelines:
[    72.599] (II) fglrx(0): Modeline "1440x900"x0.0  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz eP)
[    72.599] (II) fglrx(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    72.599] (II) fglrx(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[    72.599] (II) fglrx(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[    72.599] (II) fglrx(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz e)
[    72.599] (II) fglrx(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
[    72.599] (II) fglrx(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    72.599] (II) fglrx(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[    72.599] (II) fglrx(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[    72.599] (II) fglrx(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[    72.599] (II) fglrx(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[    72.599] (II) fglrx(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    72.599] (II) fglrx(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz e)
[    72.599] (II) fglrx(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[    72.600] (II) fglrx(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz e)
[    72.600] (II) fglrx(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[    72.600] (II) fglrx(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
[    72.600] (II) fglrx(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[    76.950] (II) fglrx(0): EDID vendor "ACR", prod id 44370
[    76.950] (II) fglrx(0): Using hsync ranges from config file
[    76.950] (II) fglrx(0): Using vrefresh ranges from config file
[    76.950] (II) fglrx(0): Printing DDC gathered Modelines:
[    76.950] (II) fglrx(0): Modeline "1440x900"x0.0  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz eP)
[    76.950] (II) fglrx(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    76.950] (II) fglrx(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[    76.950] (II) fglrx(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[    76.950] (II) fglrx(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz e)
[    76.950] (II) fglrx(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
[    76.950] (II) fglrx(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    76.950] (II) fglrx(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[    76.950] (II) fglrx(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[    76.950] (II) fglrx(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[    76.950] (II) fglrx(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[    76.950] (II) fglrx(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    76.950] (II) fglrx(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz e)
[    76.950] (II) fglrx(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[    76.950] (II) fglrx(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz e)
[    76.950] (II) fglrx(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[    76.950] (II) fglrx(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
[    76.950] (II) fglrx(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[    76.951] (II) fglrx(0): xdl_xs116_atiddxDisplayScreenEnableDisplays
[    78.915] (II) fglrx(0): EDID vendor "ACR", prod id 44370
[    78.915] (II) fglrx(0): Using hsync ranges from config file
[    78.915] (II) fglrx(0): Using vrefresh ranges from config file
[    78.916] (II) fglrx(0): Printing DDC gathered Modelines:
[    78.916] (II) fglrx(0): Modeline "1440x900"x0.0  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz eP)
[    78.916] (II) fglrx(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    78.916] (II) fglrx(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[    78.916] (II) fglrx(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[    78.916] (II) fglrx(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz e)
[    78.916] (II) fglrx(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
[    78.916] (II) fglrx(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    78.916] (II) fglrx(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[    78.916] (II) fglrx(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[    78.916] (II) fglrx(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[    78.916] (II) fglrx(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[    78.916] (II) fglrx(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    78.916] (II) fglrx(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz e)
[    78.916] (II) fglrx(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[    78.916] (II) fglrx(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz e)
[    78.916] (II) fglrx(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[    78.916] (II) fglrx(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
[    78.916] (II) fglrx(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[   134.000] (II) fglrx(0): EDID vendor "ACR", prod id 44370
[   136.027] (II) fglrx(0): Using hsync ranges from config file
[   136.027] (II) fglrx(0): Using vrefresh ranges from config file
[   136.027] (II) fglrx(0): Printing DDC gathered Modelines:
[   136.027] (II) fglrx(0): Modeline "1440x900"x0.0  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz eP)
[   136.027] (II) fglrx(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[   136.027] (II) fglrx(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[   136.027] (II) fglrx(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[   136.027] (II) fglrx(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz e)
[   136.027] (II) fglrx(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
[   136.027] (II) fglrx(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[   136.027] (II) fglrx(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[   136.027] (II) fglrx(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[   136.027] (II) fglrx(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[   136.027] (II) fglrx(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[   136.027] (II) fglrx(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[   136.027] (II) fglrx(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz e)
[   136.027] (II) fglrx(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[   136.027] (II) fglrx(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz e)
[   136.027] (II) fglrx(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[   136.027] (II) fglrx(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
[   136.027] (II) fglrx(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[   136.035] (II) fglrx(0): EDID vendor "ACR", prod id 44370
[   136.035] (II) fglrx(0): Using hsync ranges from config file
[   136.035] (II) fglrx(0): Using vrefresh ranges from config file
[   136.035] (II) fglrx(0): Printing DDC gathered Modelines:
[   136.035] (II) fglrx(0): Modeline "1440x900"x0.0  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz eP)
[   136.035] (II) fglrx(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[   136.035] (II) fglrx(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[   136.035] (II) fglrx(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[   136.035] (II) fglrx(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz e)
[   136.035] (II) fglrx(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
[   136.035] (II) fglrx(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[   136.035] (II) fglrx(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[   136.035] (II) fglrx(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[   136.035] (II) fglrx(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[   136.035] (II) fglrx(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[   136.035] (II) fglrx(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[   136.035] (II) fglrx(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz e)
[   136.035] (II) fglrx(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[   136.035] (II) fglrx(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz e)
[   136.035] (II) fglrx(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[   136.035] (II) fglrx(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
[   136.035] (II) fglrx(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[   139.822] (II) fglrx(0): EDID vendor "ACR", prod id 44370
[   139.822] (II) fglrx(0): Using hsync ranges from config file
[   139.822] (II) fglrx(0): Using vrefresh ranges from config file
[   139.822] (II) fglrx(0): Printing DDC gathered Modelines:
[   139.822] (II) fglrx(0): Modeline "1440x900"x0.0  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz eP)
[   139.822] (II) fglrx(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[   139.822] (II) fglrx(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[   139.822] (II) fglrx(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[   139.822] (II) fglrx(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz e)
[   139.822] (II) fglrx(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
[   139.822] (II) fglrx(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[   139.822] (II) fglrx(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[   139.822] (II) fglrx(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[   139.822] (II) fglrx(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[   139.822] (II) fglrx(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[   139.822] (II) fglrx(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[   139.822] (II) fglrx(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz e)
[   139.822] (II) fglrx(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[   139.822] (II) fglrx(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz e)
[   139.822] (II) fglrx(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[   139.822] (II) fglrx(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
[   139.822] (II) fglrx(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[   139.829] (II) fglrx(0): EDID vendor "ACR", prod id 44370
[   139.829] (II) fglrx(0): Using hsync ranges from config file
[   139.829] (II) fglrx(0): Using vrefresh ranges from config file
[   139.829] (II) fglrx(0): Printing DDC gathered Modelines:
[   139.829] (II) fglrx(0): Modeline "1440x900"x0.0  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz eP)
[   139.829] (II) fglrx(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[   139.829] (II) fglrx(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[   139.829] (II) fglrx(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[   139.829] (II) fglrx(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz e)
[   139.829] (II) fglrx(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
[   139.829] (II) fglrx(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[   139.829] (II) fglrx(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[   139.829] (II) fglrx(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[   139.829] (II) fglrx(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[   139.829] (II) fglrx(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[   139.829] (II) fglrx(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[   139.829] (II) fglrx(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz e)
[   139.829] (II) fglrx(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[   139.829] (II) fglrx(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz e)
[   139.829] (II) fglrx(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[   139.829] (II) fglrx(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
[   139.829] (II) fglrx(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)

The Xorg.0.log file is now cleaner, and I noticed a tiny improvement (I estimate a couple of seconds) in the loading of X Windows when the laptop starts up. Although there has been no change in video and touchpad functionality as far as I can tell, tidying up and removing redundant and incorrect X Windows configuration lines was a worthwhile exercise as I learned something in the process.

You will notice that no keyboard layout and variant are specified in any X Windows configuration file listed above. This laptop has an English (UK) keyboard layout, but sometimes I use it with external USB keyboards having English (UK), English (US), Portuguese (Brazil) and Spanish (Spain) layouts. As the laptop runs KDE, I had already configured KDE to allow me to toggle between the four keyboard layouts and so did not need to configure X Windows for the keyboard layout. However, on machines running Linux with desktop environments that do not have such a facility I add a file with a name such as /etc/X11/xorg.conf.d/15-keyboard.conf containing the following to suit my particular requirements:

Section "InputClass"
        Identifier "keyboard"
        MatchIsKeyboard "yes"
        Option "XkbLayout" "gb,us,br,es"
        Option "XkbVariant" "pc104"
        Option "XkbOptions" "grp:alt_shift_toggle"
EndSection

As the last option suggests, pressing Alt+Shift would toggle between the layouts specified.

Installing and configuring the CUPS-PDF virtual printer driver

Some applications, such as LibreOffice, have built-in support for exporting their output to PDF files. For applications without built-in support for creating PDF files there may already be an installed ‘Print to File (PDF)’ driver in your installation that you can use. However, the Print to File (PDF) option does not appear in the list of available printers in all applications. Fortunately, CUPS has a driver named CUPS-PDF which you can install to create a virtual printer that will produce PDF files.

I install the package net-print/cups-pdf and use the CUPS Printer Manager in a browser to set up a virtual printer to ‘print’ PDF files. I use the driver in conjunction with a shell script that calls a utility to display a ‘Save As’ dialogue box so the user can specify the directory and name of the PDF file.

KDialog (KDE/Qt) and Zenity (GTK+) are two well-known dialogue box tools for use in shell scripts (see, for example, the Linux Magazine article Adding graphic elements to your scripts with Zenity and KDialog). However, although I use KDE on my main laptop, I was unable to get KDialog working properly in a shell script launched by the CUPS PDF driver, so I resorted to using Zenity, which I found simple to use and reliable. My shell script using Zenity is listed further down.

Although Zenity has performed this job perfectly for me in all releases of KDE since 2007, it rankled that I could not get KDialog to do the job. However, a couple of Gentoo users were able to use KDialog successfully with the CUPS PDF driver, each with a different approach to the other, but their approaches both consisted of two shell scripts. In contrast, a solution using Zenity uses only one shell script. You can see the KDialog solutions by the two users (Havin_it and sicvolo) in Gentoo Forums thread [TIP] CUPS-PDF “Save As” with kdialog. I was determined to have a single shell script using KDialog, and was able to conflate sicvolo‘s two-script solution. My thanks go to him for his clever code in his two shell scripts, as I would never have worked it out myself. My single shell script using KDialog is listed further down.

First I will explain how to install the CUPS PDF driver package, then how to use the CUPS Printer Manager to install the virtual printer, and finally how to use a shell script with either Zenity or KDialog in order to display a graphical dialogue box prompting you to specify the directory and file name for the PDF file to be created. I use Gentoo Linux, but the procedure will be similar in other distributions (package manager commands excepted).

1.0  Installation of the cups-pdf driver and virtual printer

1.1  Install the cups-pdf package:

# emerge cups-pdf

1.2  Launch a Web browser and enter http://localhost:631/ in the Address bar to display the CUPS Printer Manager.

1.3  Click on ‘Administration’ to call up the Administration page, then click ‘Add Printer’. If prompted, enter the username ‘root’ (without the quotes) and the root user’s password.

1.4  Select ‘CUPS-PDF (Virtual PDF Printer)’ in the list of local printers, and click ‘Continue’.

1.5  Enter a name, decription and location for the virtual printer. For example, I entered ‘Virtual_PDF_Printer’, ‘Virtual PDF Printer’ and ‘Mesh Edge DX’ (without the quotes), respectively. Then click ‘Continue’.

1.6  Select ‘Generic’ in the ‘Make:’ box, and click ‘Continue’.

1.7  Select ‘Generic CUPS-PDF Printer (w/ options) (en)’ in the ‘Model:’ box, and click ‘Add Printer’. The virtual printer should now be available for you to use.

1.8  When you come to print from an application, if you select Virtual_PDF_Printer from the list of available printers the PDF file will be saved in the directory /var/spool/cups-pdf/<your username>/. Note that the directory will be created automatically the first time you ‘print’ to PDF.

1.9  Optionally, you could create a shortcut (Desktop Config File) on your Desktop to open the directory mentioned in Step 1.8 above.

1.10 Optionally, instead of Step 1.9 you could edit the file /etc/cups/cups-pdf.conf as root user to get cups-pdf to ‘print’ PDF documents to your Desktop instead of in /var/spool/cups-pdf/<your username>/, by changing the line:

#Out /var/spool/cups-pdf/${USER}

to:

Out ${HOME}/Desktop


2.0  How to display a dialog box prompting for the directory and file name of the PDF file

If you prefer to be prompted for a file name so that you can save the PDF file wherever you want and give it any name you want, perform the steps below instead of Steps 1.9 or 1.10 above. Either perform the steps in 2.1 (Zenity) or the steps in 2.2 (KDialog). Then perform the steps in 2.3, which apply in both cases.

2.1   Zenity (GTK+)

2.1.1   Install Zenity:

# emerge zenity

2.1.2   Check it is installed:

# eix -I zenity
[I] gnome-extra/zenity
Available versions: 3.12.1 {debug libnotify test +webkit}
Installed versions: 3.12.1(13:49:47 04/12/14)(libnotify webkit -debug -test)
Homepage: https://wiki.gnome.org/Projects/Zenity
Description: Tool to display dialogs from the commandline and shell scripts

2.1.3   Using a text editor, create the following shell script in your home directory and give it a meaningful name, such as cups-pdf_script.sh:

#!/bin/bash
CURRENT_PDF="${1}"
CURRENT_USER="${2}"
DISPLAY=:0.0
export DISPLAY
XAUTHORITY=/home/${CURRENT_USER}/.Xauthority
export XAUTHORITY
PDFNAME=$(zenity --file-selection --save --confirm-overwrite)
mv "$CURRENT_PDF" "$PDFNAME"

2.2   KDialog (KDE/Qt)

2.2.1   Install KDialog:

# emerge kde-base/kdialog

2.2.2   Check it is installed:

# eix -I kde-base/kdialog
[I] kde-base/kdialog
Available versions: (4) 4.12.5(4/4.12) (~)4.14.2(4/4.14) (~)4.14.3(4/4.14)
{aqua debug}
Installed versions: 4.14.3(4)(00:56:36 04/12/14)(-aqua -debug)
Homepage: http://www.kde.org/
Description: KDialog can be used to show nice dialog boxes from shell scripts

2.2.3   Using a text editor, create the following shell script in your home directory and give it a meaningful name such as cups-pdf_script.sh:

#!/bin/bash

get_dbus()
{
if [ -z $1 ]; then
    echo "specify user" >> $HOME/cups-pdf_script.log
    return 1
fi
# Search these processes for the session variable (they are run as the current user and have the DBUS session variable set)
compatiblePrograms=( kdeinit kded4 pulseaudio trackerd )

# Attempt to get a program pid
for index in ${compatiblePrograms[@]}; do
   PID=$(ps -ef | grep $1 | grep ${index} | head -1 | awk '{print $2}')
   if [[ "${PID}" != "" ]]; then
      break
   fi
done
if [[ "${PID}" == "" ]]; then
   echo "Could not detect active login session" >> $HOME/cups-pdf_script.log
   return 1
fi
QUERY_ENVIRON="$(tr '\0' '\n' < /proc/${PID}/environ | grep "DBUS_SESSION_BUS_ADDRESS" | cut -d "=" -f 2-)"
if [[ "${QUERY_ENVIRON}" != "" ]]; then
#   echo ${QUERY_ENVIRON} >> $HOME/cups-pdf_script.log
   return 0
else
   echo "Could not find dbus session ID in user environment." >> $HOME/cups-pdf_script.log
   return 1
fi
}

CURRENT_PDF="$1"
CURRENT_USER="$2"

export DISPLAY=:0
export XAUTHORITY=/home/${CURRENT_USER}/.Xauthority
export HOME=/home/${CURRENT_USER}/
CONFIG_FILE="/home/${CURRENT_USER}/.pdf-writer.conf"
CANCELLED="No"

date > $HOME/cups-pdf_script.log

get_dbus ${CURRENT_USER}
if [ $? -eq 0 ]; then
   export DBUS_SESSION_BUS_ADDRESS=${QUERY_ENVIRON}
   while [ True ]; do
      CURDATE=$(/bin/date +%Y%m%d)
      CURNAME=$(/bin/cat "$CONFIG_FILE")
      BASENAME=$(basename $CURRENT_PDF)
      FILENAME=$(/usr/bin/kdialog --getsavefilename "$CURNAME$CURDATE-" "*.pdf" --title="Save PDF")
      if [ $? -eq 1 ]; then
         CANCELLED="Yes"
         break
      fi
      echo $FILENAME
      if [ ! "$FILENAME" = "" ]; then
         if [ -e "$FILENAME" ]; then
            /usr/bin/kdialog --warningcontinuecancel "File already exists"
            if [ $? -eq 1 ]; then
               continue;
            fi
         fi
         FILENAME=$(echo $FILENAME.pdf | sed -re "s/(\.pdf)+$/.pdf/g")
         break;
      else
         /usr/bin/kdialog --error "You must select a file or hit Cancel."
      fi
      break
   done
   if [ "${CANCELLED}" == "No" ]; then
      /bin/cp "${CURRENT_PDF}" "${FILENAME}"
      okular "${FILENAME}" &
   fi
   /bin/rm "${CURRENT_PDF}"
   echo "No errors encountered." >> $HOME/cups-pdf_script.log
   exit 0
else
   /bin/rm "${CURRENT_PDF}"
   echo "Errors encountered." >> $HOME/cups-pdf_script.log
   exit 1
fi

2.3   Whichever of the above two options (Zenity or KDialog) you chose, do the following:

2.3.1   Make the shell script file executable:

# chmod +x /home/<your username>/cups-pdf_script.sh

2.3.2   Edit the file /etc/cups/cups-pdf.conf, find the line starting with ‘#PostProcessing‘, and change it to:

PostProcessing /home/<your username>/cups-pdf_script.sh

2.3.3   Restart CUPS:

# /etc/init.d/cupsd restart # If your installation uses OpenRC.

# systemctl restart cups.service # If your installation uses systemd.

Now, when you select Virtual_PDF_Printer from your applications’ list of available printers and click ‘Print’, a pop-up window should appear, allowing you to select the target directory for the PDF file and enter a file name of your choice.

Fix for ALSA Speaker volume level resetting to zero at boot

Up until 2011 the problem of the volume level in ALSA resetting to zero at boot was a common occurrence in my Linux installations. Actually it was a common occurrence in Linux, full stop; search the Web using keywords such as “alsa reset volume” and you’ll find umpteen links. In 2012 the situation improved and I thought the problem had become a thing of the past, but it resurfaced in 2013 on my main laptop and has plagued me through every update since (well, apart from in one release of KDE). Every time I reboot, the ALSA Speaker channel’s volume is zero when I log-in to KDE. And, as KMix is a PulseAudio mixer by default these days, I have to launch ALSAMixer and raise the volume of the Speaker channel manually.

I don’t know if the source of the problem lies in KDE, PulseAudio or ALSA itself. It did disappear after one upgrade to KDE earlier this year (I don’t recall which release of KDE) but returned in the next KDE upgrade, so I suspect it is a KDE issue. In earlier days I could resolve the problem using the commands alsactrl store and alsactl restore and similar approaches. However, this time none of those fixes work for me. The problem never bothered me much, as I always connect external speakers to my laptop’s headphone socket when I’m at home, and I don’t want my laptop emitting sounds at the office. Nevertheless, the fact the problem exists niggled me, so I decided to try and fix it. Rather than expending any more effort trying to get the usual approaches to work (the Web is littered with suggested fixes over the years), I decided to reset the Speaker volume to the same level at each boot by using an automatically-launched shell script. The method I use is given below, and should work with either OpenRC or systemd in Gentoo Linux.

1. Create the file /etc/local.d/20set_alsa_volume.start containing the following:

#!/bin/bash
# Reset ALSA Speaker channel on the first sound card to 90% after booting.
su -c "amixer -c 0 -- sset Speaker playback 90%" -s /bin/sh fitzcarraldo

(Replace “fitzcarraldo” with your own user name, of course.)

2. Make the script executable:

# chmod +x 20set_alsa_volume.start

That’s all there is to it. The volume of the ALSA Speaker channel is always set to 90% after I reboot and login to the desktop environment. KMix remembers the PulseAudio volume setting from the previous session, so I can still avoid blasting the laptop’s speakers.

By the way, the manual pages for the amixer and alsamixer commands make useful reading:

$ man amixer
$ man alsamixer

For example, the first audio card (Card 0) in my main laptop has the following controls:

$ amixer -c 0 scontrols
Simple mixer control ‘Master’,0
Simple mixer control ‘Headphone’,0
Simple mixer control ‘Speaker’,0
Simple mixer control ‘PCM’,0
Simple mixer control ‘Mic’,0
Simple mixer control ‘Mic Boost’,0
Simple mixer control ‘Beep’,0
Simple mixer control ‘Capture’,0
Simple mixer control ‘Auto-Mute Mode’,0
Simple mixer control ‘Digital’,0
Simple mixer control ‘Internal Mic’,0
Simple mixer control ‘Internal Mic Boost’,0

Update (January 29, 2015): I found the cause of the problem: PulseAudio. I edited the file /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf as per user agmg‘s January 2013 post Re: [SOLVED] Problems with PulseAudio 3.0 in the PCLinuxOS Forums:

Again, I had to edit the file: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf

and change this:

[Element Speaker]
switch = mute
volume = off

to this:

[Element Speaker]
switch = mute
volume = merge

I realized that editing the [Element Desktop Speaker] section of the above file, has no effect on the issue. Only the edit to [Element Speaker] is needed in my case.

In my case this change forces the ALSA Speaker channel volume to 100% after rebooting (irrespective of the volume levels I set via ALSAMixer and KMix before shutdown).

The contents of the file /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf also include the following comment:

; See analog-output.conf.common for an explanation on the directives

The contents of the file analog-output.conf.common include the following comment:

; volume = ignore | merge | off | zero | <volume step> # What to do with this volume: ignore it, merge it into the device
;                                                      # volume slider, always set it to the lowest value possible, or always
;                                                      # set it to 0 dB (for whatever that means), or always set it to
;                                                      # <volume step> (this only makes sense in path configurations where
;                                                      # the exact hardware and driver are known beforehand).

So I could have tried volume = <volume step> instead of volume = merge, although I have no idea what value <volume step> would need to be. Anyway, the Bash script /etc/local.d/20set_alsa_volume.start that I created does the job in a different way without me having to tinker with the troublesome PulseAudio, so I reverted to volume = off in the file analog-output.conf and reverted to using /etc/local.d/20set_alsa_volume.start as explained earlier.

Updating Intel CPU microcode from Gentoo Linux

Updates to CPU microcode have to be re-applied each time the computer is booted, because the memory updated is volatile (despite the term ‘firmware’ also being used for microcode). Below I describe two methods (there are others) of applying CPU microcode updates in Gentoo Linux. My main laptop has an Intel CPU so I focus here on Intel microcode updates. The procedure is almost the same for AMD CPUs, but the AMD CPU binary update file (‘binary blob’) is installed by the sys-kernel/linux-firmware package.

METHOD 1: Use an initscript in the boot runlevel with a kernel module

Until recently I was using an initscript named microcode_ctl, which uses a program (also named microcode_ctl) and a kernel module (microcode.ko) to update the Intel CPU microcode during boot. This was straightforward to set up in Gentoo Linux:

1. Build the kernel with CONFIG_MICROCODE=m and CONFIG_MICROCODE_INTEL=y.

This is what I configured in the kernel:

# grep -i microcode /usr/src/linux/.config
CONFIG_MICROCODE=m
CONFIG_MICROCODE_INTEL=y
# CONFIG_MICROCODE_AMD is not set
CONFIG_MICROCODE_OLD_INTERFACE=y
# CONFIG_MICROCODE_INTEL_EARLY is not set
# CONFIG_MICROCODE_AMD_EARLY is not set

2. Install two packages and add an OpenRC initscript to the boot runlevel:

# emerge microcode-data microcode-ctl
# rc-update add microcode_ctl boot

The initscript will re-update the CPU microcode every time the computer is rebooted.

Installing the package microcode-data downloads a compressed file (microcode-yyyymmdd.tgz) from the Intel Download Centre, extracts a text file named microcode.dat and parses the text in it to create a set of binary ‘blobs’ in the directory /lib/firmware/intel-ucode/ (one blob for each model of Intel CPU).

Before rebooting, check the revision of microcode in the CPU (the microcode revision is shown for each logical core):

# This is for the Core i7-720QM CPU in my Compal NBLB2 laptop.
# grep microcode /proc/cpuinfo
microcode : 0x3
microcode : 0x3
microcode : 0x3
microcode : 0x3
microcode : 0x3
microcode : 0x3
microcode : 0x3
microcode : 0x3

If I use this method of updating the microcode, the initscript runs after the message ‘Waiting for uevents to be processed ...‘ is displayed on VT1 while booting. After the module has performed the update, the microcode revision in the CPU’s logical cores has changed:

# grep microcode /proc/cpuinfo
microcode : 0x7
microcode : 0x7
microcode : 0x7
microcode : 0x7
microcode : 0x7
microcode : 0x7
microcode : 0x7
microcode : 0x7
# dmesg | grep microcode
[ 15.749533] microcode: CPU0 sig=0x106e5, pf=0x10, revision=0x3
[ 15.834790] microcode: CPU0 sig=0x106e5, pf=0x10, revision=0x3
[ 15.835530] microcode: CPU0 updated to revision 0x7, date = 2013-08-20
[ 15.835544] microcode: CPU1 sig=0x106e5, pf=0x10, revision=0x3
[ 15.835587] microcode: CPU1 sig=0x106e5, pf=0x10, revision=0x3
[ 15.836241] microcode: CPU1 updated to revision 0x7, date = 2013-08-20
[ 15.836257] microcode: CPU2 sig=0x106e5, pf=0x10, revision=0x3
[ 15.836299] microcode: CPU2 sig=0x106e5, pf=0x10, revision=0x3
[ 15.836953] microcode: CPU2 updated to revision 0x7, date = 2013-08-20
[ 15.837063] microcode: CPU3 sig=0x106e5, pf=0x10, revision=0x3
[ 15.837128] microcode: CPU3 sig=0x106e5, pf=0x10, revision=0x3
[ 15.837767] microcode: CPU3 updated to revision 0x7, date = 2013-08-20
[ 15.837857] microcode: CPU4 sig=0x106e5, pf=0x10, revision=0x3
[ 15.837968] microcode: CPU4 sig=0x106e5, pf=0x10, revision=0x3
[ 15.838605] microcode: CPU4 updated to revision 0x7, date = 2013-08-20
[ 15.838634] microcode: CPU5 sig=0x106e5, pf=0x10, revision=0x3
[ 15.838681] microcode: CPU5 sig=0x106e5, pf=0x10, revision=0x3
[ 15.839357] microcode: CPU5 updated to revision 0x7, date = 2013-08-20
[ 15.839390] microcode: CPU6 sig=0x106e5, pf=0x10, revision=0x3
[ 15.839453] microcode: CPU6 sig=0x106e5, pf=0x10, revision=0x3
[ 15.840121] microcode: CPU6 updated to revision 0x7, date = 2013-08-20
[ 15.840180] microcode: CPU7 sig=0x106e5, pf=0x10, revision=0x3
[ 15.840274] microcode: CPU7 sig=0x106e5, pf=0x10, revision=0x3
[ 15.840911] microcode: CPU7 updated to revision 0x7, date = 2013-08-20
[ 15.840997] microcode: Microcode Update Driver: v2.00 , Peter Oruba
[ 26.940662] microcode: Microcode Update Driver: v2.00 removed.

Notice that the microcode update occurred in the period from 15.749533 to 15.840997 seconds after the kernel started running, and the microcode was updated from revision 0x3 to 0x7.

METHOD 2: Use the kernel’s built-in Early Update driver

Although the initscript method works perfectly in my case and the update is complete by the time the laptop has finished booting, I wanted to update the CPU microcode earlier. Updating microcode early can fix CPU issues before they occur during kernel boot time. It is possible to configure the kernel to update microcode early by setting CONFIG_MICROCODE_EARLY and CONFIG_MICROCODE_INTEL_EARLY in the kernel. See /usr/src/linux/Documentation/x86/early-microcode.txt for details. That document only refers to initrd files, but, in fact, it also applies to initramfs files.

The Early Update kernel driver will align misaligned microcode data (see Notes on Intel Microcode Updates and [PATCH 7/8] x86, microcode, intel: guard against misaligned microcode data), but you can pre-align the data yourself if you wish by using a .padding file as explained on the latter page. However I did not bother doing that; I leave the Early Update kernel driver to take care of aligning the microcode, as the time penalty to align it is small compared to the overall update time.

It is possible to download the latest compressed Intel microcode data file yourself from the Intel Download Centre. The latest file released is microcode-20140913.tgz at the time of writing. It contains only a text file named microcode.dat, not the required binary blob. Actually, microcode.dat contains data in text format for several Intel CPU models. The microcode.dat file should reside in the directory /lib/firmware/. In the case of Gentoo it is a waste of time manually obtaining the microcode.dat file this way, as there is no tool in Gentoo specifically for creating a binary blob from the microcode.dat file. Therefore just install the Gentoo package sys-apps/microcode-data (which you would have done in any case if you were using the microcode_ctl initscript to load the microcode update to the CPU) and it will automatically download the compressed file from the Intel Web site, unpack it, copy the file microcode.dat to /lib/firmware/ and create the binary blobs in the directory /lib/firmware/intel-ucode/.

You may have read of a tool named intel-microcode2ucode used in other Linux distributions. Gentoo does not build intel-microcode2ucode (the source code of which is included in the Gentoo package sys-apps/microcode-data) as a stand-alone tool, but the act of installing microcode-data creates the required binary files in /lib/firmware/intel-ucode/. i.e. the following command does the complete job:

# emerge microcode-data

Check that the microcode files for the various CPU models were created when microcode-data was installed:

# ls /lib/firmware/intel-ucode/
06-03-02 06-05-03 06-06-0d 06-08-01 06-09-05 06-0b-04 06-0f-02 06-0f-0b 06-17-07 06-1c-02 06-1e-05 06-2a-07 06-3a-09 06-3e-07 0f-00-07 0f-02-05 0f-03-02 0f-04-03 0f-04-09 0f-06-05
06-05-00 06-06-00 06-07-01 06-08-03 06-0a-00 06-0d-06 06-0f-06 06-0f-0d 06-17-0a 06-1c-0a 06-25-02 06-2d-06 06-3c-03 06-3f-02 0f-00-0a 0f-02-06 0f-03-03 0f-04-04 0f-04-0a 0f-06-08
06-05-01 06-06-05 06-07-02 06-08-06 06-0a-01 06-0e-08 06-0f-07 06-16-01 06-1a-04 06-1d-01 06-25-05 06-2d-07 06-3e-04 06-45-01 0f-01-02 0f-02-07 0f-03-04 0f-04-07 0f-06-02
06-05-02 06-06-0a 06-07-03 06-08-0a 06-0b-01 06-0e-0c 06-0f-0a 06-17-06 06-1a-05 06-1e-04 06-26-01 06-2f-02 06-3e-06 06-46-01 0f-02-04 0f-02-09 0f-04-01 0f-04-08 0f-06-04

I looked in /proc/cpuinfo to confirm the model of CPU in my laptop:

$ grep model /proc/cpuinfo
model : 30
model name : Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz
model : 30
model name : Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz
model : 30
model name : Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz
model : 30
model name : Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz
model : 30
model name : Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz
model : 30
model name : Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz
model : 30
model name : Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz
model : 30
model name : Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz

I was able to find the CPUID and other data for that model from the Web site CPU World:

CPUID 106E5
Family 6 (06 hex)
Model 30 (1E hex)
Stepping 5 (05 hex)

Therefore the file /lib/firmware/intel-ucode/06-1e-05 (Family-Model-Stepping in hexadecimal) is the binary blob for my specific CPU model.

First I used genkernel to rebuild the current kernel with CONFIG_MICROCODE_EARLY=y and CONFIG_MICROCODE_INTEL_EARLY=y.

# mount /dev/sda3 /boot # /boot is on a separate partition in my installation.

# Backup the files of the existing kernel image and initramfs:
# cp /boot/initramfs-genkernel-x86_64-3.17.1-gentoo-r1 /home/fitzcarraldo/initramfs-genkernel-x86_64-3.17.1-gentoo-r1.bak
# cp /boot/kernel-genkernel-x86_64-3.17.1-gentoo-r1 /home/fitzcarraldo/kernel-genkernel-x86_64-3.17.1-gentoo-r1.bak
# cp /boot/System.map-genkernel-x86_64-3.17.1-gentoo-r1 /boot/fitzcarraldo/System.map-genkernel-x86_64-3.17.1-gentoo-r1.bak

# Now rebuild the kernel:
# zcat /proc/config.gz > /usr/src/config
# genkernel --kernel-config=/usr/src/config --menuconfig --splash=Emergance --disklabel all # Set CONFIG_MICROCODE_EARLY and CONFIG_MICROCODE_INTEL_EARLY.
# emerge @module-rebuild
# grub2-mkconfig -o /boot/grub/grub.cfg

This is what I have after rebuilding the kernel:

# grep -i microcode /usr/src/linux/.config
CONFIG_MICROCODE=y
CONFIG_MICROCODE_INTEL=y
# CONFIG_MICROCODE_AMD is not set
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_MICROCODE_INTEL_EARLY=y
# CONFIG_MICROCODE_AMD_EARLY is not set
CONFIG_MICROCODE_EARLY=y

Then I prepended the cpio file containing the binary blob to the initramfs file (see the instructions in /usr/src/linux/Documentation/x86/early-microcode.txt):

# mkdir -p /boot/initrd/kernel/x86/microcode
# cd /boot/initrd
# cp /lib/firmware/intel-ucode/06-1e-05 kernel/x86/microcode/GenuineIntel.bin
# find . | cpio -o -H newc >../ucode.cpio
# cd ..
# cp /boot/initramfs-genkernel-x86_64-3.17.1-gentoo-r1 /home/fitzcarraldo/initramfs-genkernel-x86_64-3.17.1-gentoo-r1.bak.early # Backup the recently-built initramfs first.
# cat ucode.cpio /boot/initramfs-genkernel-x86_64-3.17.1-gentoo-r1 >/boot/initramfs-genkernel-x86_64-3.17.1-gentoo-r1.ucode
# cp /boot/initramfs-genkernel-x86_64-3.17.1-gentoo-r1.ucode /boot/initramfs-genkernel-x86_64-3.17.1-gentoo-r1
# rm /boot/initramfs-genkernel-x86_64-3.17.1-gentoo-r1.ucode
# umount /boot
# rc-update del microcode_ctl boot # Disable the initscript so that microcode.ko will no longer be used when I reboot.

Reboot.

Use the following commands to check if the CPU microcode has been updated:

# grep microcode /proc/cpuinfo
# dmesg | grep microcode

There is no point looking in /var/log/messages, because syslog-ng has not started running when the early microcode update occurs.

# grep microcode /proc/cpuinfo
microcode : 0x7
microcode : 0x7
microcode : 0x7
microcode : 0x7
microcode : 0x7
microcode : 0x7
microcode : 0x7
microcode : 0x7
# dmesg | grep microcode
[ 0.252234] CPU1 microcode updated early to revision 0x7, date = 2013-08-20
[ 0.265389] CPU2 microcode updated early to revision 0x7, date = 2013-08-20
[ 0.278696] CPU3 microcode updated early to revision 0x7, date = 2013-08-20
[ 1.888471] microcode: CPU0 sig=0x106e5, pf=0x10, revision=0x7
[ 1.888481] microcode: CPU1 sig=0x106e5, pf=0x10, revision=0x7
[ 1.888491] microcode: CPU2 sig=0x106e5, pf=0x10, revision=0x7
[ 1.888498] microcode: CPU3 sig=0x106e5, pf=0x10, revision=0x7
[ 1.888506] microcode: CPU4 sig=0x106e5, pf=0x10, revision=0x7
[ 1.888515] microcode: CPU5 sig=0x106e5, pf=0x10, revision=0x7
[ 1.888523] microcode: CPU6 sig=0x106e5, pf=0x10, revision=0x7
[ 1.888534] microcode: CPU7 sig=0x106e5, pf=0x10, revision=0x7
[ 1.888597] microcode: Microcode Update Driver: v2.00 , Peter Oruba

Compare the update time in the dmesg output above with the update time in the dmesg output for an update done using the initscript (Method 1, further up). With the Early Update driver, the update was complete in 0.278696 seconds. With the initscript and kernel module, the update was complete in 15.840911 seconds. Quite a difference.

I do not know why the dmesg output does not have a message for Core 0 in the group of messages before 1.000000 second elapsed. The message at 1.888471 shows it was updated, so I assume the kernel ring buffer was not large enough and the message was overwritten. Cores 1, 2 and 3 were updated in the period between 0.252234 and 0.278696 seconds, and then all eight logical cores are listed in the period between 1.888471 and 1.888597 seconds. I’m not sure of the precise messages expected, but they look similar to the results obtained by users in other distributions, such as the following CrunchBang Linux output:

$ uname -a
Linux crunchbang 3.10-12.dmz.1-liquorix-amd64 #1 ZEN SMP PREEMPT Sun Sep 15 17:29:51 UTC 2013 x86_64 GNU/Linux
$ dmesg | grep microcode
CPU0 microcode updated early to revision 0x19, date = 2013-06-13
CPU1 microcode updated early to revision 0x19, date = 2013-06-13
CPU2 microcode updated early to revision 0x19, date = 2013-06-13
CPU3 microcode updated early to revision 0x19, date = 2013-06-13
microcode: CPU0 sig=0x306a9, pf=0x10, revision=0x19
microcode: CPU1 sig=0x306a9, pf=0x10, revision=0x19
microcode: CPU2 sig=0x306a9, pf=0x10, revision=0x19
microcode: CPU3 sig=0x306a9, pf=0x10, revision=0x19
microcode: CPU4 sig=0x306a9, pf=0x10, revision=0x19
microcode: CPU5 sig=0x306a9, pf=0x10, revision=0x19
microcode: CPU6 sig=0x306a9, pf=0x10, revision=0x19
microcode: CPU7 sig=0x306a9, pf=0x10, revision=0x19
microcode: Microcode Update Driver: v2.00 , Peter Oruba
$ cat /proc/cpuinfo | grep microcode | uniq
microcode : 0x19

Finally, I deleted the temporary work directory and files:

# mount /dev/sda3 /boot
# rm -rf /boot/initrd/
# rm /boot/ucode.cpio
# rm /home/fitzcarraldo/kernel-genkernel-x86_64-3.17.1-gentoo-r1.bak
# rm /home/fitzcarraldo/initramfs-genkernel-x86_64-3.17.1-gentoo-r1.bak
# rm /home/fitzcarraldo/System.map-genkernel-x86_64-3.17.1-gentoo-r1.bak

# Optional. Could keep the following file in case Intel issues a new microcode.dat file and I want to create a new concatenated initramfs file:
# rm /home/fitzcarraldo/initramfs-genkernel-x86_64-3.17.1-gentoo-r1.bak.early

Of course, you will need to repeat the whole process and create a new concatenated initramfs file in any of the following cases:

a) you build a new version of the kernel;

b) you rebuild the current version of the kernel with different configuration settings;

c) Intel releases a new version of the microcode (which does not happen often).

It seems the Early Update driver still has some bugs, so I expect the message output to change in future kernel releases. See e.g. [PATCH 0/8] x86, microcode, intel: fixes and enhancements, [PATCH 3/8] x86, microcode, intel: clarify log messages, Re: [PATCH 3/8] x86, microcode, intel: clarify log messages and a bunch of other very recent posts in the kernel mailing list regarding the Early Update driver and CPU microcode updates.

Laptop Mode Tools revisited due to a change in its functionality

The site statistics for this blog can be quite revealing. For example, over the last two or three months I noticed that my post How to prevent a USB mouse auto-suspending in Linux when a laptop’s power supply is disconnected has consistently been one of the most viewed. Given the problems I experienced with Laptop Mode Tools 1.65 (see my Gentoo Linux Forums post Bug in laptop-mode-tools-1.65? and Gentoo Linux Bugzilla Bug Report No. 520124), I was not entirely surprised. Thanks to fellow Gentoo Linux and Laptop Mode Tools user Ted Tanberry I learned that Version 1.65 had stopped using Laptop Mode Tools module usb-autosuspend, and started using Laptop Mode Tools module runtime-pm instead. At least that was the developer’s intention, but he had not implemented it correctly. The aforementioned Gentoo Linux bug report explains in detail the problem with Version 1.65.

The situation in my Gentoo Linux installation with laptop-mode-tools-1.64 installed, providing the functionality I desired, was as follows:

a. The precise package installed:

# eix -I laptop-mode-tools
[U] app-laptop/laptop-mode-tools
Available versions: 1.64 (~)1.65 (~)1.65-r1 (~)1.66 {+acpi apm bluetooth scsi}
Installed versions: 1.64(10:04:43 21/10/14)(acpi bluetooth -apm -scsi)
Homepage: http://www.samwel.tk/laptop_mode/
Description: Linux kernel laptop_mode user-space utilities

b. The auto-suspend state when the laptop PSU was connected:

# for d in /sys/bus/usb/devices/[0-9]* ; do if [[ -e $d/product ]] ; then echo -e "`basename $d`\t`cat $d/power/control`\t`cat $d/speed`\t`cat $d/product`" ; fi ; done
1-1.2 on 1.5 USB Laser Mouse
2-1.2 on 12 Fingerprint Sensor
2-1.3 on 480 USB 2.0 Camera

c. The contents of the file /lib64/udev/rules.d/99-laptop-mode.rules:

ACTION=="change", SUBSYSTEM=="power_supply", RUN+="lmt-udev auto"
ACTION=="add|remove", SUBSYSTEM=="machinecheck", RUN+="lmt-udev auto"
ACTION=="add|remove", SUBSYSTEM=="usb", RUN+="lmt-udev force modules=usb-autosuspend devices=%k"

d. The contents of file /etc/laptop-mode/conf.d/usb-autosuspend.conf:

#
# Configuration file for Laptop Mode Tools module usb-autosuspend.
#
# For more information, consult the laptop-mode.conf(8) manual page.
#
 
 
###############################################################################
# USB autosuspend settings
# ------------------------
#
# If you enable this setting, laptop mode tools will automatically enable the
# USB autosuspend feature for all devices.
#
# NOTE: Some USB devices claim they support autosuspend, but implement it in a
# broken way. This can mean keyboards losing keypresses, or optical mice turning
# their LED completely off. If you have a device that misbehaves, add its USB ID
# to the blacklist below and complain to your hardware vendor.
################################################################################
 
# Enable debug mode for this module
# Set to 1 if you want to debug this module
DEBUG=0
 
# Enable USB autosuspend feature?
# Set to 0 to disable
CONTROL_USB_AUTOSUSPEND="auto"
 
# Set this to use opt-in/whitelist instead of opt-out/blacklist for deciding
# which USB devices should be autosuspended.
# AUTOSUSPEND_USE_WHITELIST=0 means AUTOSUSPEND_*_BLACKLIST will be used.
# AUTOSUSPEND_USE_WHITELIST=1 means AUTOSUSPEND_*_WHITELIST will be used.
AUTOSUSPEND_USE_WHITELIST=0
 
# The list of USB IDs that should not use autosuspend. Use lsusb to find out the
# IDs of your USB devices.
# Example: AUTOSUSPEND_USBID_BLACKLIST="046d:c025 0123:abcd"
AUTOSUSPEND_USBID_BLACKLIST="046d:c052"
 
# The list of USB driver types that should not use autosuspend.  The driver
# type is given by "DRIVER=..." in a USB device's uevent file.
# Example: AUTOSUSPEND_USBID_BLACKLIST="usbhid usb-storage"
AUTOSUSPEND_USBTYPE_BLACKLIST=""
 
# The list of USB IDs that should use autosuspend. Use lsusb to find out the
# IDs of your USB devices.
# Example: AUTOSUSPEND_USBID_WHITELIST="046d:c025 0123:abcd"
AUTOSUSPEND_USBID_WHITELIST=""
 
# The list of USB driver types that should use autosuspend.  The driver
# type is given by "DRIVER=..." in a USB device's uevent file.
# Example: AUTOSUSPEND_USBTYPE_WHITELIST="usbhid usb-storage"
AUTOSUSPEND_USBTYPE_WHITELIST=""
 
# Trigger auto-suspension of the USB deivce under conditional circumstances
BATT_SUSPEND_USB=1
LM_AC_SUSPEND_USB=0
NOLM_AC_SUSPEND_USB=0
 
# USB Auto-Suspend timeout in seconds
# Number of seconds after which the USB devices should suspend
AUTOSUSPEND_TIMEOUT=2

Having experienced the problems with the buggy Laptop Mode Tools 1.65, I re-installed 1.64 and had been using that successfully until a week ago. Then I noticed that 1.66 had been released, so I installed it:

# emerge laptop-mode-tools
.
.
.
>>> Installing (1 of 1) app-laptop/laptop-mode-tools-1.66::gentoo
* To enable automatic power state event handling,
* e.g. enabling laptop_mode after unplugging the battery,
* both laptop_mode and the acpid daemon must be
* added to default runlevel:
* # rc-update add laptop_mode default
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.

* GNU info directory index is up-to-date.

I would not have expected that ewarn message about adding laptop_mode to the default runlevel, as the ebuild is only supposed to display the warning if laptop_mode is not assigned to the default runlevel. But, sure enough, something had removed it:

# rc-update show -v | grep laptop
laptop_mode |
# rc-update show -v | grep acpi
acpid |      default

I don’t know what removed laptop_mode from the default runlevel. It was certainly assigned previously, as proved by Laptop Mode Tools 1.64 working as expected when I connected and disconnected the laptop’s PSU from the mains (see my earlier post). Anyway, I re-added it:

# rc-update add laptop_mode default
* service laptop_mode added to runlevel default

If you use systemd instead of OpenRC, instead of adding laptop_mode to the default runlevel you would need to use the following command:

# systemctl enable laptop_mode.service

Notice that the incorrect contents of 99-laptop-mode.rules and /etc/laptop-mode/laptop-mode.conf that were present in Laptop Mode Tools 1.65 have been fixed in 1.66:

# cat /lib64/udev/rules.d/99-laptop-mode.rules
ACTION=="change", SUBSYSTEM=="power_supply", RUN+="lmt-udev auto"
ACTION=="add|remove", SUBSYSTEM=="machinecheck", RUN+="lmt-udev auto force"
ACTION=="add|remove", SUBSYSTEM=="usb", RUN+="lmt-udev force modules=runtime-pm devices=%k"

# cat /etc/laptop-mode/laptop-mode.conf | grep usb-autosuspend
#

The ebuild for Laptop Mode Tools 1.66 did not delete the now-redundant file /etc/laptop-mode/conf.d/usb-autosuspend.conf but it is presumably ignored by 1.66 anyway.

From now on I must configure the contents of /etc/laptop-mode/conf.d/runtime-pm.conf instead. After installing Laptop Mode Tools 1.66 it contained the following:

#
# Configuration file for Laptop Mode Tools module runtime-pm
#
# For more information, consult the laptop-mode.conf(8) manual page.
#


###############################################################################
# Runtime Power Management Settings
# ---------------------------------
#
#__COMMENT If you enable this setting, laptop mode tools will automatically enable
#__COMMENT the Runtime Power Management feature for all devices.
#__COMMENT
#__COMMENT NOTE: Some devices claim they support autosuspend, but implement it in a
#__COMMENT broken way. This can mean keyboards losing keypresses, or optical mice
#__COMMENT turning their LED completely off. If you have a device that misbehaves,
#__COMMENT add its DEVICE ID to the blacklist section below and complain to your
#__COMMENT hardware / device driver contact
#
################################################################################

# Enable debug mode for this module
# Set to 1 if you want to debug this module
DEBUG=0

# Enable Runtime autosuspend feature?
# Set to 0 to disable
CONTROL_RUNTIME_AUTOSUSPEND=1

# Set this to use opt-in/whitelist instead of opt-out/blacklist for deciding
# which devices should be autosuspended.
# AUTOSUSPEND_USE_WHITELIST=0 means AUTOSUSPEND_*_BLACKLIST will be used.
# AUTOSUSPEND_USE_WHITELIST=1 means AUTOSUSPEND_*_WHITELIST will be used.
AUTOSUSPEND_USE_WHITELIST=0

# The list of Device IDs that should not use autosuspend. Use system commands or
# look into sysfs to find out the IDs of your devices.
# Example: AUTOSUSPEND_DEVID_BLACKLIST="046d:c025 0123:abcd"
AUTOSUSPEND_RUNTIME_DEVID_BLACKLIST=""

# The list of device driver types that should not use autosuspend.  The driver
# type is given by "DRIVER=..." in a device's uevent file.
# Example: AUTOSUSPEND_DEVID_BLACKLIST="usbhid usb-storage"
AUTOSUSPEND_RUNTIME_DEVTYPE_BLACKLIST=""

# The list of Device IDs that should use autosuspend. Use system commands or
# look into sysfs to find out the IDs of your devices.
# Example: AUTOSUSPEND_DEVID_WHITELIST="046d:c025 0123:abcd"
AUTOSUSPEND_RUNTIME_DEVID_WHITELIST=""

# The list of device driver types that should use autosuspend.  The driver
# type is given by "DRIVER=..." in a device's uevent file.
# Example: AUTOSUSPEND_DEVTYPE_WHITELIST="usbhid usb-storage"
AUTOSUSPEND_RUNTIME_DEVTYPE_WHITELIST=""

# Trigger auto-suspension of the deivce under conditional circumstances
# Warning: DO NOT CHANGE THESE DEFAUTLS UNLESS YOU KNOW
BATT_SUSPEND_RUNTIME=1
LM_AC_SUSPEND_RUNTIME=1
NOLM_AC_SUSPEND_RUNTIME=1

# Auto-Suspend timeout in seconds
# Number of seconds after which the USB devices should suspend
AUTOSUSPEND_TIMEOUT=2

So, in order to stop my laptop’s USB mouse, USB external keyboard and some internal USB devices from going to sleep when my laptop is only on battery power, I made the following change to a line in /etc/laptop-mode/conf.d/runtime-pm.conf:

# External keyboard at one office, internal Webcam, internal fingerprint sensor, Logitek NX50 notebook mouse
AUTOSUSPEND_RUNTIME_DEVID_BLACKLIST="03f0:0024 064e:a115 147e:1001 046d:c052"

My earlier post about Laptop Mode Tools explained one method for finding the device ID for each USB device, but the lsusb command can also be used:

# lsusb
Bus 002 Device 005: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard <---- External keyboard at one office
Bus 002 Device 004: ID 064e:a115 Suyin Corp. <---- Built-in Webcam
Bus 002 Device 003: ID 147e:1001 Upek TCS5B Fingerprint sensor <---- Built-in fingerprint sensor
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 046d:c052 Logitech, Inc. <----Logitech NX50 notebook mouse
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Although the Laptop Mode Tools usb-autosuspend module is supposed to be unused in 1.66, I edited /etc/laptop-mode/conf.d/usb-autosuspend.conf (which was not deleted by the 1.66 ebuild) and changed CONTROL_USB_AUTOSUSPEND="auto" to CONTROL_USB_AUTOSUSPEND="0" just to be on the safe side.

My thoughts on systemd

When I first read about systemd a few years ago, the main ‘marketing point’ seemed to be that Linux boots faster using it rather than SysVinit — see, for example, On to better booting. When I read that article back in September 2012, a paragraph caught my eye:

It looks like the crowd lining up behind systemd is growing fast. With Fedora, OpenSUSE, Mandiva, Arch, Debian, Gentoo, Frugalware — Did I forget anyone? And RedHat will probably be joining with the release of RedHat7. Ubuntu seems to be sticking with Upstart.

As a Gentoo user I was surprised to read that the distribution was ‘lining up behind systemd’ — systemd was not even mentioned in the Gentoo Handbook — so I started a thread in the Gentoo Forums enquiring whether there were plans to change the default init system from OpenRC to systemd: Gentoo ‘lining up behind systemd’?.

Revisiting that ITWorld article two years later, I notice the paragraph was subsequently changed, as it now reads:

It looks like the crowd lining up behind systemd is growing fast. With Fedora, OpenSUSE, Mandiva, Arch, Debian, Frugalware — Did I forget anyone? And RedHat will probably be joining with the release of RedHat7. Gentoo has its own next generation rc system called OpenRC, which competes with both systemd and upstart, but provides its users with the option of installing systemd. Ubuntu seems to be sticking with Upstart.

OpenRC works fine for me; I know how to use it and I do not particularly want to have to learn how to use another system when what I use now works perfectly well for my purposes. By no means do I begrudge others the use of systemd, as long as my freedom of choice is not curtailed. Each to his own, as the saying goes. But events over the past couple of years have left me wondering about my freedom to choose in the future, and indeed about the future form of the operating system itself.

Faster startup?

As I mentioned above, the main marketing point when I first read about systemd was its boot time. When I tried systemd in May 2013 on a 2009 Acer Aspire 5536-643G25Mn laptop (dual-core CPU; 3 GB RAM) — no match for today’s state-of-the-art hardware — the times to boot from the GRUB 2 menu to the DM login screen for a fully-updated 64-bit Sabayon Linux Xfce installation were as follows:

OpenRC with rc_parallel=”NO” 33 seconds
OpenRC with rc_parallel=”YES” 31 seconds
systemd 29 seconds

I posted the above timings in the Sabayon Linux Forums and the developer of the distribution responded:

speed improvements heavily depend on the CPU and I/O subsystem. In particular, systemd is able to leverage multi-core CPUs much better (because it spawns services in parallel). Spawning services in parallel also puts more pressure on the I/O subsystem, which means that if you have faster I/O (like with SSDs), the speed boost compared to OpenRC becomes quite relevant.

Indeed a few users of newer machines with 8 GB or more RAM and/or SSD drives wrote in the Sabayon Linux Forums that their boot times had almost been halved (e.g. from circa 40 seconds to circa 21 seconds). However, I expect the boot times for OpenRC and systemd would not be dramatically different from each other on any of my existing machines and, in any case, I’m not bothered about saving a few seconds in boot time on my machines (and I don’t reboot often either).

Nowadays one hears less mention of faster boot times from systemd proponents. For example, the author of the December 2011 article Here We Go Again, Another Linux Init: Intro to systemd mentioned ‘Faster Startups’ early on, whereas in a September 2014 article Understanding and Using Systemd, the same author states:

For whatever reason, it seems that the proponents of SysVInit replacements are obsessed with boot times. My systemd systems, like CentOS 7, don’t boot up all that much faster than the others. It’s not something I particularly care about in any case, since most boot speed measurements only measure reaching the login prompt, and not how long it takes for the system to completely start and be usable.

Erosion of choice?

A couple of Gentoo developers commented in the above-mentioned 2012 Gentoo Forums thread that adoption of systemd as the default init system in Gentoo would be extremely unlikely. Several posters pointed out that alternative init systems exist and Gentoo users could simply install an alternative if desired. However, I started to wonder about the long-term availability of choice when I began to see blog posts such as Red Hat Flag and, indeed, when I myself was affected by systemd’s subsumption of udev (see e.g. udev is doomed) earlier this year and, more recently, when a Gentoo developer had to create the package upower-pm-utils because systemd subsumed hibernate & suspend support from upower (UPower 0.99.0 was released to ~arch as of 2014-06-01).

Whatever one’s views on systemd, the impact on non-systemd users when systemd developers change something that previously worked fine is frustrating. Gentoo developers have been doing a good job working around such nugatory subsumptions, but it’s extra work for them and extra effort for the Gentoo user who doesn’t use systemd. I began to wonder how long this state of affairs could continue.

Another layer of abstraction?

Although my main laptop has Gentoo installed with OpenRC, on a couple of other machines I tinker with Sabayon Linux, which uses systemd. Sabayon Linux is pre-compiled Gentoo with an overlay and its own binary package manager, so there is some synergy in using the two distributions. Also, it is clear from several threads requesting help in the Gentoo Forums that a number of Gentoo users are migrating to systemd. In answering or just reading forum posts involving systemd, and in writing blog posts of my own explaining how to use systemd for certain tasks, in some cases it feels to me as if systemd sometimes adds a layer of abstraction that is not necessarily helpful. Two examples that spring to mind are given below.

  1. The Gentoo Forums thread [SOLVED]I don’t understand transient hostnames in which a Gentoo user using systemd was trying to stop the hostname being changed when he connected to some networks:

    I’m running a systemd based system for the first time and I’m having an issue with my hostname. Basically, when I connect to (some) networks the network assigns me a transient hostname. This transient hostname seems to completely break everything with my desktop manager (KDM). I have to log out, and then log in with the new transient hostname (which is presumably assigned shortly after I log in and network manager connects to the network). Is this expected? I have set my hostname as described in the handbook and the systemd wiki page. How do I make my hostname *never* change based on dhcp crap?

    After I pointed out that it is possible to force a persistent hostname by specifying the hostname in NetworkManager.conf if NetworkManager is being used with either systemd or OpenRC, he wrote:

    My hostname is now written in 3 places (/etc/hosts, /etc/hostname, and /etc/NetworkManager/NetworkManager.conf). Oh, and I have some random executable (hostnamectl) sitting on my system doing a seemingly poor job of ‘controlling’ my hostname.

    Out of curiosity I then experimented with hostnamectl and compared the outcome with the outcome of setting the hostname in an installation that does not use systemd, and the results differed, so I’m not sure of the scope of hostnamectl.

  2. Time (Arch Wiki)

    The hardware clock can be queried and set with the timedatectl command. To change the hardware clock time standard to localtime, use:

    # timedatectl set-local-rtc 1

    If you want to revert to the hardware clock being in UTC, do:

    # timedatectl set-local-rtc 0

    These will generate /etc/adjtime automatically and update the RTC accordingly; no further configuration is required.

    During kernel startup, at the point when the RTC driver is loaded, the system clock may be set from the hardware clock. Whether this occurs depends on the hardware platform, the version of the kernel and kernel build options. If this does occur, at this point in the boot sequence, the hardware clock time is assumed to be UTC and the value of /sys/class/rtc/rtcN/hctosys (N=0,1,2,..) will be set to 1.

    Later, the system clock is set again from the hardware clock by systemd, dependent on values in /etc/adjtime. Hence, having the hardware clock using localtime may cause some unexpected behavior during the boot sequence; e.g system time going backwards, which is always a bad idea (there is a lot more to it). To avoid it systemd (>215) will only synchronize back, if the hardware clock is set to UTC and keep the kernel uninformed about the local timezone. As a consequence timestamps on a FAT filesystem touched by the Linux system will be in UTC.

    Note: The use of timedatectl requires an active dbus. Therefore, it may not be possible to use this command under a chroot (such as during installation). In these cases, you can revert back to the hwclock command.

Swimming against the tide?

There have been a number of dissenting voices on the Internet. Some argue against systemd on technical grounds, others on philosophical grounds. Here are are few examples:

One of the few distributions bucking the trend is Void Linux, which has replaced systemd with runit as the default init system, with systemd becoming an option.

Slackware and Gentoo are two distributions that do not use systemd by default, although it is actually reasonably straightforward to switch to systemd in Gentoo. It seems one or two people are moving to Gentoo, or contemplating it, because systemd isn’t the default in Gentoo (see, for examples, Re: OT: Open letter to the Linux World and IgnorantGuru’s Hiatus).

Several threads in the Gentoo Forums contain prolonged discussions on systemd, and it is clear that some Gentoo users have strong reservations about systemd. As I write this, a poll in the Gentoo Forums shows only 13 per cent of respondents support the idea of Gentoo adopting systemd as the default init system. I suspect that users of binary-based distributions find this lack of enthusiasm odd, but I believe it is because Gentoo is a source-based distribution and its users are usually more familiar with Linux internals and more comfortable, more adept and more interested in getting ‘under the hood’ than are users of binary-based distributions. Gentoo is not quite Linux From Scratch, but Gentoo users build their installations almost from the ground up (Gentoo does not even have an installer application, for example). I believe that anything interfering with the current way of doing things, or adding a level of abstraction, is not of interest to many Gentoo users. On the other hand, I think users of binary-based distributions who just want to get something done in the quickest way possible are less likely to object.

The beginnings of a new OS?

systemd is not just an init system, it has grown into much more than that and continues to add functionality (referred to by some as ‘feature creep’). Below is the current list of functionality provided in systemd, and the list is growing.

init system, journal logging, login management, device management, temporary and volatile file management, binary format registration, backlight save/restore, rfkill save/restore, bootchart, read-ahead, encrypted storage setup, EFI/GPT partition discovery, virtual machine/container registration, minimal container management, hostname management, locale management, time management, random seed management, sysctl variable management, console management, network management, time synchronisation

I think more of the seasoned GNU/Linux users are waking up to the impact of what Lennart Poettering (the chief architect of systemd) and his fellow systemd ‘cabal’ (his word) members are doing. They are re-designing GNU/Linux from the ground up, and I don’t think it would be an exaggeration to call the end result ‘systemd/Linux’, a de facto new OS. Personally I’m not interested in using that, but I think the vast majority of existing users or newcomers to ‘Linux’ — to use the popular term for the OS — simply don’t care. As long as it works out-of-the-box, that’s all that matters to most people.

And as far as distribution developers are concerned, the status quo says it all: most have already switched their distributions to systemd or have committed to doing so in the future. I suspect it is because they see systemd as being easier to maintain, thus making their lives easier, and they also see systemd as being easier for their desktop users (and with a boot time closer to Windows 8/8.1 Fast Startup). Ultimately the systemd ‘cabal’ will effectively make the different package managers obsolete too, as the latest plan Revisiting How We Put Together Linux Systems shows.

In my opinion, the end result of the radical systemd redesign of the OS could be greater take-up of the OS on the desktop, but the distinction between distributions will lessen and many will cease to exist, as there will be little point choosing one over another. The greater commonality and the larger user base of systemd/Linux will attract more crackers than at present. In some respects the de facto new OS will be much more like Windows or Mac OS than the current GNU/Linux.

Widening the net?

In a Chromium OS discussion group thread earlier this year — The future of initsystem in Chromium OS — a systemd proponent (a Fedora developer?) offered to help the Chrome OS developers switch from Upstart to systemd, but the Chrome OS developers saw no reason to do so without proof of tangible benefits. I believe there is too much revenue at stake to risk switching an important component of the OS of a commercial product (Chromebooks) on a whim. With Chromebooks looking increasingly like the main threat to Microsoft’s hegemony on the desktop, I’m sure Google has no interest in jeopardising that without a very good reason.

The future?

The future seemed clear to me once Mark Shuttleworth announced Ubuntu would drop Upstart and adopt systemd (he made the announcement after Debian developers decided to adopt systemd). Given the number of Ubuntu users (I’ve seen figures in the tens of millions bandied about), I believe Ubuntu will be the making or breaking of systemd. In my opinion, as was the case with PulseAudio (another Lennart Poettering project) there will be a couple of choppy years with plenty of posts in the Ubuntu Forums seeking help, more bugs will be shaken out, and I believe the vast majority of Linux users will end up as accepting users of systemd. In some cases systemd does make configuration a little easier for a newcomer (see, for example, my post Configuring the Linux clock). Personally I find systemd no easier to use than what I use now; in some cases I find systemd more complicated than what I use now (e.g. OpenRC’s local.d). My concerns regarding abstraction, subsumption, loss of choice and the morphing of the OS into something closer to the Windows approach remain, although I can see that many people, including newcomers to Linux, would actually welcome those things. Ironically, although I used to get frustrated with the large number of Linux distributions and their differences, the implications of greater commonality now worry me from a security (predominantly cybercrime) point of view. I am satisfied and comfortable with the existing GNU/Linux tools, configuration files, modus operandi and OpenRC (which works with no problems whatsoever in my case), so I have no desire to migrate to systemd on my main machine running Gentoo Linux. I will also continue to tinker with Sabayon Linux, and thus with systemd, but it will be several years hence before this jury returns a verdict on systemd.

Configuring the Linux clock

A problem often reported by users in Linux forums is that the time displayed by the system clock is incorrect. Typically the problem is that it displays UTC instead of local time. The most common cause is incorrect configuration, although dual booting with Windows will also change the Linux system clock’s time unless either a) Linux is configured to use local time for the hardware clock, or b) Windows is configured to use UTC* and Windows’ time synchronisation with an Internet time server is disabled.

* A change to the Windows Registry is required in order to enable Windows to use UTC for hardware clock time, but even then you may still face problems (see e.g. Force Windows 8 to use UTC when dealing with BIOS clock).

Some terms you need to know: ‘hardware clock’, ‘RTC’ (real-time clock), ‘CMOS clock’ and ‘BIOS clock’ are terms commonly used for the same thing. The hardware clock is non-volatile. ‘system clock’ is the software clock the operating system uses. It is volatile (it is in the kernel). The system clock is normally set from the hardware clock when the operating system boots, taking into account various configuration options. I recommend that you read the manual for the hwclock command, as it explains in detail about clocks in Linux:

# man hwclock

To configure your time zone and clocks correctly, follow the steps below.

If your installation uses the OpenRC init system

  1. Set the time zone:

    1. Specify your time zone in the file /etc/timezone. If you are in Spain, for example, the contents of that file should be ‘Europe/Madrid‘ (without the quotes).

      # nano /etc/timezone

      You can find out which time zones are available by looking in the directory /usr/share/zoneinfo/ and its sub-directories.

    2. Provide the information for your time zone. If you are in Spain, for example, you would enter the following command:

      # cp /usr/share/zoneinfo/Europe/Madrid /etc/localtime

      Note: Some people recommend making /etc/localtime a symlink rather than creating it by copying a file from /usr/share/zoneinfo/, however I recommend copying. You should definitely not use a symlink if /usr is on a different partition (see Ref. 1).

  2. Set the system clock’s time to your local time now (I’ll assume it is 23:54:30 on 21 September 2014 when you press Enter):

    # date 092123542014.30

  3. Specify whether the hardware clock time is UTC:

    # hwclock --utc

    or local time:

    # hwclock --localtime

    It is preferable for the hardware clock time to be in UTC. However, if you dual boot with Windows it is recommended for the hardware clock time to be in local time rather than UTC unless both the following are true: a) the Windows Registry has been configured for hardware clock time in UTC; b) Windows’ time synchronisation with an Internet time server is disabled.

  4. Set the hardware clock’s time by specifying your local time (I’ll assume it is 23:54:50 on 21 September 2014 when you press Enter):

    # rm /etc/adjtime
    # hwclock --set --date="2014-09-21 23:54:50"

    Note: You must specify local time in the above command, even if you intend the hardware clock time to be UTC.

    Note that the third line in /etc/adjtime should be ‘UTC’ if the hardware clock time is in UTC, or ‘LOCAL’ if the hardware clock time is in local time. For example:

    # cat /etc/adjtime
    0.000000 1412038530 0.000000
    1412038530
    UTC

  5. Tell OpenRC whether the hardware clock uses UTC or local time, and to update the hardware clock time from the system clock time at every shutdown (taking into account any time zone difference between the two clocks):

    # nano /etc/conf.d/hwclock

    1. Make clock="UTC" (or clock="local" if you dual boot with Windows and the Windows Registry is not configured to use UTC for hardware clock time).

    2. Make clock_systohc="YES" to adjust the hardware clock time at shutdown based on the software clock time (taking time zone into account). However, you don’t need to bother doing this if your kernel configuration has CONFIG_RTC_SYSTOHC=y and your installation is configured to synchronise the system clock with a NTP time server (see my post Synchronise your Gentoo Linux clock with an Internet time server). You can check if the hardware clock time is being updated from the software clock time (taking time zone into account) by looking at the kernel messages displayed when in verbose mode during shutdown to see if the following message is displayed:

      Setting hardware clock using the system clock [UTC] ...

    3. Make clock_hctosys="YES" to adjust the system clock time at start up based on the hardware clock time (taking time zone into account). However, you don’t need to bother doing this if your kernel configuration has CONFIG_RTC_HCTOSYS=y. You can check by looking at the kernel messages displayed when in verbose mode during boot to see if the following message is displayed:

      Setting system clock using the hardware clock [UTC] ...

  6. Reboot and check everything is working as expected:

    # date
    Tue 30 Sep 01:55:55 BST 2014
    # hwclock
    Tue 30 Sep 2014 01:55:59 BST -0.031877 seconds

    The hwclock command always shows local time, even if you keep your hardware clock in UTC.

  7. Optionally (but I recommend it), configure your installation to synchronise the system clock with an Internet NTP server (see my post Synchronise your Gentoo Linux clock with an Internet time server).

If your installation uses systemd

  1. Set the time zone:

    1. Find out the available time zones:

      # timedatectl list-timezones

    2. Specify your time zone (I’ll assume you are in Spain in this example):

      # timedatectl set-timezone Europe/Madrid

  2. Set the system clock time to your local time (I’ll assume it is 23:54:30 on 21 September 2014 when you press Enter):

    # timedatectl set-time "2014-09-21 23:54:30"

  3. Inform systemd that the hardware clock uses UTC, and set the current UTC in the hardware clock now:

    # timedatectl set-local-rtc 0

    Note that, by default, systemd assumes the hardware clock uses UTC. Although systemd can be configured to assume the hardware clock uses local time, for technical reasons it is not recommended (see man timedatectl and Arch Wiki article Time for an explanation of why this is not advisable).

    Note that the third line in /etc/adjtime should be ‘UTC’ if the hardware clock time is in UTC, or ‘LOCAL’ if the hardware clock time is in local time. For example:

    # cat /etc/adjtime
    0.000000 1412038530 0.000000
    1412038530
    UTC

  4. Reboot and check everything is working as expected:

    $ timedatectl

  5. Optionally (but I recommend it), configure your installation to synchronise the system clock with an Internet NTP server (see my post Synchronising the clock using NTP in Sabayon Linux).

References

[1] Gentoo Forums – how exactly to set timezone in /etc/localtime ?[solved]

Follow

Get every new post delivered to your Inbox.

Join 54 other followers