CentOS 6 on HP Compaq 6710b

A few days ago a have got from a “second hand” HP Compaq 6710b laptop. Of course I wanted and I did installed on it CentOS 6 🙂

The first failure was the black screen when I was trying to install the CentOS 6 in the “Install of upgrade and existing system“. So I decided to install from the second option “Install system with basic video driver”. I was possible to install the system, but the resolution was only 1024×768 not 1280×800. The video driver in that laptop is (according to lspci):

00:02.1 Display controler: Intel Corporation Mobile GM965/GM960 Integrated Graphics Controller (rev0c)

I started to “google” the internet and I have found a solution at CentOS Forum page https://www.centos.org/modules/newbb/viewtopic.php?topic_id=33201. The problem was that the kernel cannot load a proper module, and in /etc/X11 was a xorg.conf file containing configuration like this:

Section “Device”

Identifier “Videocard0”
Driver “vesa”


According to CentOS Forum the solution was simple:

    1. delete file /etc/X11/xorg.conf
    2. remove in /boot/grub/grub.conf entry “nomodeset”
It’s all 🙂 After rebooting CentOS found and loaded the prober module for my video card.


4 thoughts on “CentOS 6 on HP Compaq 6710b

  1. Robin


    My laptop is now loading the good driver i think. Only after the loading screen of centos 6 (the loadingcircle thing) the only thing i get is a black screen with an blinking ‘-‘.

    Do you heave any suggestions to fix this issue?

    1. Dominik

      Did You try to press the ‘ESC’ key during the loading screen with CentOS circle during the boot process? You will see all processes which are currently starting. Then you will see on which one it hangs… I think 🙂

  2. Robin

    Thanks for your reply Dominik, my laptop is only showing a blinking line after ‘starting adt’. The screen blinks a few times when loading adt. Do you heave any suggestions to fix this problem?

  3. Brian Maly

    I got the blank screen too when I tried to install. Adding “vga=771” on the boot line resolved the issue for me.


Leave a Reply

Your email address will not be published. Required fields are marked *