Translation(s): none

(!) ?Discussion

DebianOn is an effort to document how to install, configure and use Debian on some specific hardware. Therefore potential buyers would know if that hardware is supported and owners would know how get the best out of that hardware.

The purpose is not to duplicate the Debian Official Documentation, but to document how to install Debian on some specific hardware.

If you need help to get Debian running on your hardware, please have a look at our user support channels where you may find specific channels (mailing list, IRC channel) dedicated to certain types of hardware.

Models covered
HP Pavilion DV6 2113sa Entertainment PC

Features :

Overall Status

Core Components


Boot Standard Kernel:


LAN network card:


Detect CD/DVD:


Detect hard drives:


Extra Features

CPU Frequency Scaling




Sleep / Suspend




- OpenGL


- Resize-and-Rotate(randr)


Switch to External Screen



- Built-in (Touchpad)






Keyboard's Hotkeys


Legend :
{OK} = OK ; {X} Unsupported(No Driver) ; /!\ = Error (Couldn't get it working); [?] Unknown, Not Test ; [-] Not-applicable
{i} = Configuration Required; X-( = Only works with a non-free driver and or firmware

Important Note

Some of the hardware requires that the user installs the 2.6.32 kernel from lenny-backports, however linux-kbuild-2.6.32 is not yet in backports, and this is required if you wish to build the proprietary ATI module. You can download this from the squeeze or sid sources. It will not break anything in Lenny.

As it's just one package, and to reduce complication, you can do this:

$ wget
$ sudo dpkg -i linux-kbuild-2.6.32_2.6.32-1_amd64.deb

A better way would be to add squeeze to your apt sources and pay attention to the priorities to ensure no other packages from Squeeze end up in your Lenny install. See AptPreferences.



The driver out of the box with Lenny will work. For 3D support you can use the proprietary fglrx driver from ATI. See ATIProprietary.

A simple way to automate the install and management of the driver is to use the scripts from smxi. Log out of X and switch to a terminal by pressing ctrl-alt-f1. Log in and type the following as root:

# cd /usr/local/bin
# wget -Nc
# unzip
# ./smxi

After proceeding through the options you will arrive at an option called 'proceed to graphics'. Follow this and choose the latest ATI driver from the menu, this will download, compile, install and configure the fglrx module. You can run this script anytime you change your kernel to keep it simple.


The ATI Technologies Inc SBx00 Azalia card uses Alsa's snd_hda_intel driver. You will need at least kernel 2.6.32 to get this to work properly (or compile your own ALSA driver). You can get 2.6.32 from Lenny-backports:

  1. To add the Debian Backports repository, create /etc/apt/sources.list.d/lenny-backports.list and add the following:

    # Backported packages for Debian Lenny
    deb lenny-backports main
  2. Update the list of available packages and install the lenny-backports/debian-backports-keyring package:

    # apt-get update
    # apt-get -t lenny-backports install debian-backports-keyring
  3. Install the 2.6.32 (or later) kernel image.

    # apt-get -t lenny-backports install linux-image-2.6.32-bpo.2-$(uname -r | sed 's,.*-,,g')

Before rebooting into your new kernel edit /etc/modprobe.d/alsa-base and add the following to the end:

options snd-hda-intel model=hp-dv5 enable_msi=1

Failure to do so will mean that sound will continue to be emitted from the laptops internal speakers after a jack is plugged into the front.

After rebooting your machine you may need to play around with the mixer controls to adjust the volume of the front outputs and the laptop speakers. Test to make sure the laptop speakers are automatically muted when external speakers or headphones are plugged in.

(Sound recording not yet tested)

Power Management


The driver for the wireless uses the ath9k driver, so once you install 2.6.32 as per above it should load automatically. See ath9k.

IR Remote

The IR remote is mapped directly to the keyboard. The keys on the remote directly correspond with keys or key combinations from the keyboard, which makes it easy to configure to control window manager or application features. You may find that the remote is not working as it should or at all. The cure is to turn off the laptop, remove the power and the battery, then replace the battery and power and use the remote's on button to power on the laptop again. To check if this is working, try using the arrow keys on the remote to switch between choices on the grub menu. If this works then it should continue working in the OS. If not, check the battery in the remote.

System Summary



lsusb -v | grep -E '\<(Bus|iProduct|bDeviceClass|bDeviceProtocol)' 2>/dev/null

USB Host controllers entries (without OHCI, UHCI, EHCI) are removed too.



Some configuration files and sample outputs.