Finding the right name for your Intel graphics chipset

The output of lspci does not always provide enough information about graphics card and integrated graphics chipsets :

fool@localhost:~$ lspci -nn |egrep “VGA|Display”
00:02.0 VGA compatible controller [0300]: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03)
00:02.1 Display controller [0380]: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e33] (rev 03)

In this case, this information “Intel Corporation 4 Series Chipset Integrated Graphics Controller”  is not sufficient to find the right name of this Intel graphics chipset.  There are two solutions to solve it :

fool@localhost:~$grep -i chipset /var/log/Xorg.0.log

[    17.764] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
[    17.770] (II) intel(0): Integrated Graphics Chipset: Intel(R) G41
[    17.770] (–) intel(0): Chipset: “G41”

fool@localhost:~$dmesg |grep -i agp

[    1.008912] Linux agpgart interface v0.103
[    1.009057] agpgart-intel 0000:00:00.0: Intel G41 Chipset
[    1.009142] agpgart-intel 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
[    1.010058] agpgart-intel 0000:00:00.0: detected 32768K stolen memory
[    1.010181] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xe0000000

With this information, it will be much more easier to use the right driver and tune the Xorg configuration file. (if necessary)

Hope this helps !

mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining

Here is a message which was appearing in my syslog file until I solved the problem :

[drm] Initialized drm 1.1.0 20060810
mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining

MTRR stands for Memory Type range registers. Its a new feature available in the latest Intel processors.It is a new way of partitioning and managing memory resources in your system.There are two solutions for using the right values for mtrr.
The first one is to add this option to your grub command line :  enable_mtrr_cleanup mtrr_spare_reg_nr=1
The second one is to recompile your current kernel and choose the value 1 instead of 0 for MTRR cleanup enable value (0-1) while issuing the command make menuconfig.

I chose the first solution and I do not get any error messages no more :

dmesg |grep mtrr
[    0.000000] MTRR default type: uncachable
[    0.000000] MTRR fixed ranges enabled:
[    0.000000] MTRR variable ranges enabled:
[    0.000000] original variable MTRRs
[    0.000000] Found optimal setting for mtrr clean up
[    0.000000] New variable MTRRs
[    0.000000] Kernel command line: root=/dev/sda2 ro quiet enable_mtrr_cleanup mtrr_spare_reg_nr=1

cat /proc/mtrr
reg00: base=0x000000000 (    0MB), size= 2048MB, count=1: write-back
reg01: base=0x080000000 ( 2048MB), size= 1024MB, count=1: write-back
reg02: base=0x0bdd00000 ( 3037MB), size=    1MB, count=1: uncachable
reg03: base=0x0bde00000 ( 3038MB), size=    2MB, count=1: uncachable
reg04: base=0x0be000000 ( 3040MB), size=   32MB, count=1: uncachable
reg05: base=0x0e0000000 ( 3584MB), size=  256MB, count=2: write-combining

For more information :

(EE) AIGLX error: dlopen of /usr/lib/dri/ failed (/usr/lib/dri/ cannot open shared object file: No such file or directory)

If you get this message(EE) AIGLX error: dlopen of /usr/lib/dri/ failed (/usr/lib/dri/ cannot open shared object file: No such file or directory) in your Xorg log file, install the following package :

root@localhost:~#apt-get install libgl1-mesa-dri

Restart your X server and this message will disappear from your logs.

Cannot locate a core pointer device / Cannot locate a core keyboard device.

With Debian, the X11 config file can automatically filled with default values after a dpkg-reconfigure xserver-xorg.
If any X11-related error occurs, some lines are added to the X11 default log file : /var/log/Xorg.0.log

There are several levels of warnings : EE for error, WW for warning and here II for informational.
In order to have a X11 config file very close to my hardware and software configuration, I try to remove any message such as this one below :

(II) Cannot locate a core pointer device.                    
(II) Cannot locate a core keyboard device.                   
(II) The server relies on HAL to provide the list of input devices.
        If no devices become available, reconfigure HAL or disable AllowEmptyInput.

To avoid having this lines each time the X11 server is started, you have to add these information to your X11 config file in the “Server Flags” section :

Option “AllowEmptyInput” “off”

To see the changes, restart your X11 server and check your X11 log file.

radeon_cp: Failed to load firmware « radeon/R200_cp.bin »

I recently found this error in the output of the command dmesg:

“radeon_cp: Failed to load firmware “radeon/R200_cp.bin

It seems that there is a missing file R200_cp.bin requested by the radeon firmware.
To find the package to which the file R200_cp.bin belongs to :

root@localhost:~# apt-file search R200_cp.bin
firmware-linux: /lib/firmware/radeon/R200_cp.bin
firmware-linux-nonfree: /lib/firmware/radeon/R200_cp.bin

So, the missing packages firmware-linux and firmware-linux-nonfree must be installed :

root@localhost:~# apt-get install firmware-linux firmware-linux-nonfree

To verify that the missing file is correctly installed, restart your X server and check again the output of dmesg :

root@localhost:~ # dmesg |grep radeon
[drm] Setting GART location based on new memory map
[drm] Loading R200 Microcode
platform radeon_cp.0: firmware: requesting radeon/R200_cp.bin
[drm] writeback test succeeded in 1 usecs


xclip is a command line program which interacts with X11 clipboard.

To install it :

root@localhost:~# apt-get install xclip

To use, have a look at the example below :

fool@localhost:~$ ls |xclip

I have just listed the content of my current working directory and then put it to X11 clipboard through the “|” command.

To insert this content to a program like a GUI text editor, I have to paste by clicking on the middle button of my mouse.

xclip can receive the content of a whole file  :

fool@localhost:~$ xclip /etc/fstab

To display the content of xclip :

fool@localhost:~$ xclip -o

Grabbing infos on your X server version

It can be pretty useful to know the version of your X server installation.

There are at least two ways to get this piece of information. As root, issue one of the following commands :

root@localhost:~#X -version


root@localhost:~# xdpyinfo | head

The last command will display the first 20 lines from the output of xdpyinfo

Make sure you have the package x11-utils installed so that the command xdpyinfo will be available.