Gentoo Wiki


This is going to be the page for how I got things done for my laptop. Definitely a work in progress because the usb wacom support was only written a week before I bought the machine. I hope that this will be a 1-stop (for howto and with extra info) place for this machine.

Many thanx goes to these forums as a starting place. I hope to digest these forums and put the results here, people are more than welcome to help with this.

As people edit this I'd like them to leave a list of the actual model number that their machine is.


Models for this wiki

tx2114ca tx2010eo tx2108ca

probably entire tx2000z series...

Kernel Parameters

I may have found the kernel configuration for stable operation with neither noapic nor irqfixup flags. This option in particular may have been significant:

Linux Kernel Configuration: Bus Configuration
 Bus Options (PCI etc.)  --->
   [*] Interrupts on hypertransport devices

Here is my complete kernel config for gentoo-sources-2.6.24-r8.

If your system is still unstable, try appending the irqfixup and noapic flags to your kernel command line, though these options appear to have a significant performance cost(Firefox loads in 5-10 seconds with them, 2-3 seconds without them).


The nVidia MCP51 southbridge has a built-in Ethernet controller that works with the forcedeth driver. Don't be alarmed that it's listed under 10/100 Megabit, forcedeth appears to support full gigabit speeds despite this.

Code: /usr/sbin/lspci | grep -i eth

00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)

Linux Kernel Configuration: Ethernet configuration
 Device Drivers  --->
   [*] Network Device Support  --->
     [*] Ethernet (10 or 100Mbit) --->
       [*] EISA, VLB, PCI, and on board controllers
       <*> nForce Ethernet support

In certain buggy systems the forcedeth driver must make 100 interrupts per second to check for completed transmissions. On portable systems, these 100 extra wakeups per second interfere with power savings. The tx2108ca, and potentially the entire tx2000 series, does not appear to suffer from this flaw, hence the flag to do this in the MCP51 architecture can be safely removed from drivers/net/forcedeth.c for these systems. This patch was generated from gentoo-sources-2.6.24-r8.

Nvidia Graphics

I use the open source driver because the old binary one has a peculiar effect of turning off the display after a while and not bringing it back (well, switching to console which you do not see and back to X is a workaround, although an inconvenient one). Also, the latest stable(as of July 4 2008) nvidia drivers show only blank consoles while X11 is running. Both issues are solved in nvidia drivers >= 173.14.08.

The open source driver doesn't suffer from that, but it does bring about this "white light" effect when you start the X Server.

OpenGL performance with the closed-source drivers as reported by glxgears seems to be about 2500FPS in 16bpp and 1750fps in 24bpp.

And if you may notice that when using the 2 different drivers, the sizes are different because the open source driver ends up setting the DPI to 75, while the binary will set it to 101. I could have those backwards. And so you don't have to do the math of 1280x800 on a 12.1' screen, it's value is 125. To find out your DPI run:

xdpyinfo |grep resolution
resolution:    125x124 dots per inch

To prevent that from being huge, I have (in KDE) the Fonts module in Control Centre set to force fonts to 96 DPI. 96 DPI is a MS Windows standard. If using the nvidia drivers, you could instead add the line :

File: /etc/X11/xorg.conf


Option   "DPI" "96 x 96"


to the Device section for your nvidia card.

Other useful options for the nvidia driver:

File: /etc/X11/xorg.conf


Section "Device"
        Driver          "nvidia"
        # Allow rotation through xrandr
        Option          "RandRRotation"
        # Reduce number of interrupts to save power
        Option          "OnDemandVBlankInterrupts"      "True" 
        # Allow underclocking through nvidia-settings
        Option          "Coolbits"                      "1"



You shouldn't need to use alsa-driver for sound, the kernel's own drivers work as of 2.6.24-r8.

Make sure you add this line to get things working. Don't forget to run update-modules afterwards, and if you run alsaconf, the line may be deleted. At the moment I don't have the mute button colour changing.

The PC speaker, while it works, always plays through the speakers not the headphones, and interrupts whatever else is playing when it beeps.

File: /etc/modprobe.d/alsa


options snd-hda-intel model=hp


Afterwards run update-modules.

With alsamixer, unmute and set Master and PCM to 100%, then unmute and adjust Front and Headphone for speakers and headphone respectively. You'll have to set them fairly high.

Save and restore don't work properly for some reason. Setting

File: /etc/conf.d/alsasound




and adding

File: /etc/conf.d/local.start


/etc/init.d/alsasound restore > /dev/null 2> /dev/null


will allow it to restore properly.

Remote, Keycodes, ACPI Controls

The remote should just work because it emulates keycodes. My remote didn't work right away and all I did was take the battery out and connect the terminals in the remote to get rid of the excess charge that somehow built up, it now works. A few buttons on the screen seem to do nothing at all.

Laptop Base Keycodes
Volume -Scancode 0xae as reported by SDL
Volume MuteScancode 0xa0 as reported by SDL
Volume +Scancode 0xb0 as reported by SDL
Toggle Keypad
  • Disable: Unrecognized scancode e058/0xd8 as reported by kernel
  • Re-Enable: Unrecognized scancode e059/0xd9 as reported by kernel
WirelessNo keycode or ACPI event, causes bluetooth USB device removal or insertion and presumably enables or disables 802.11
FN-Key Keycodes
fn-F1 (help)Unrecognized scancode e031/0xb1 as reported by kernel
fn-F2 (print)LCtrl-P
fn-F3 (www)Scancode 0xb2 as reported by SDL
fn-F4 (monitor)Reports no keypress, amazingly actually tries to do its job
fn-F5 (sleep)Scancode 0xdf as reported by SDL
fn-F6 (lock)Unknown scancode e00a/0x8a as reported by kernel
fn-F7 (brightness down)Scancode 0x65 as reported by SDL, and lowers brightness, and generates unhandled ACPI event "video LCD 00000087 00000000"
fn-F8 (brightness up)Scancode 0xd4 as reported by SDL, and raises brightness, and generates unhandled ACPI event "video LCD 00000086 00000000"
fn-F9 (play/pause)Same as remote play/pause
fn-F10 (stop)Same as remote stop
fn-F11 (rewind)Same as remote rewind
fn-F12 (fast-forward)Same as remote fast-forward
Remote Keycodes
PowerScancode 0xdf as reported by SDL
ReplayUnrecognized scancode e03a/0xba as reported by kernel
Play/PauseScancode 0xa2 as reported by SDL
DVDUnrecognized scancode e034/0xb4 as reported by kernel
StopScancode 0xa4 as reported by SDL
Black Square Upper Left(rewind)Scancode 0x90 as reported by SDL
Black Square UpUp
Black Square Upper Right(fast-forward)Scancode 0x99 as repored by SDL
Black Square LeftLeft
Black Square Middle(OK)Enter
Black Square RightRight
Black Square Lower LeftBackspace
Black Square DownDown
Black Square Lower Right(i)Scancode 0x75 as reported by SDL
Volume -Same as base
Volume MuteSame as base
Volume +Same as base
Monitor Keycodes
DVDUnknown scancode e00e/0x8e as repored by kernel
ReplayUnknown scancode e008/0x88 as repored by kernel
RepeatThe goggles(do nothing)
Back of Monitor Keycodes
RewindScancode 0x90 as reported by SDL
Play/PauseScancode 0xa2 as reported by SDL
Fast ForwardScancode 0x99 as reported by SDL
StopScancode 0xa4 as reported by SDL

The brightness FN-keys will not do anything unless you have ACPI video control enabled in your kernel:

Linux Kernel Configuration: ACPI Video
 Device Drivers  --->
   Graphics support  --->
     <*> Lowlevel video output switch controls
     -*- Backlight & LCD device support  --->
     <*>   Lowlevel LCD controls
     Display device support  ---> 
       <*> Display panel/monitor support
 Power management options  --->
   [*] ACPI (Advanced Configuration and Power Interface) Support  --->
     <*>   Video [NEW]

If you disable the touchpad with the key, closing the monitor face-up seems to re-enable it even though the indicator stays red. Turning it back on then off disables it again.


I have gotten the active and the passive to work on my screen by manually adding dev wacom module. It provides two event interfaces, one for the wacom pen and one for the touch screen. If your stylus doesn't work when close to(and not touching) the screen and its calibration seems wildly off, you may have swapped them -- the calibration for the wacom pen seems perfect. /dev/input/mice includes the touchscreen interface but not the pen one for some reason, so it may be best to configure X11 for seperate interfaces. Note that /dev/input/mice excludes devices that get used explicitly.

hp2100: Wacom tablets 009x isn`t working with linuxwacom driver from 2.6.25. (Not listed in wacom_wac.c)

File: /etc/X11/xorg.conf


# Synaptics Touchpad device
Section "InputDevice"
    Identifier "touchpad"
    Option     "Protocol"        "IMPS/2"
    Option     "Device"          "/dev/input/mice"
    Option     "Emulate3Buttons"
#   Option     "Emulate3Timeout" "50"

# wacom pen device
Section "InputDevice"
    Driver     "wacom"
    Identifier "stylus"
    Option     "type"           "stylus"
    Option     "device"         "/dev/input/by-path/pci-0000:00:0b.1-usb-0:2.3:1.0-wacom"
    Option     "USB"            "on"
    Option     "ForceDevice"    "ISDV4"
# Make the stylus button a right-click
    Option     "Button2"        "3"

Section "InputDevice"
    Driver     "wacom"
    Identifier "stylus"
    Option     "type"           "eraser"
    Option     "device"         "/dev/input/by-path/pci-0000:00:0b.1-usb-0:2.3:1.0-wacom"
    Option     "USB"            "on"
    Option     "ForceDevice"    "ISDV4"

# Wacom touchscreen
Section "InputDevice"
    Driver     "wacom"
    Identifier "touch"
    Option     "type"           "stylus"
    Option     "device"         "/dev/input/by-path/pci-0000:00:0b.1-usb-0:2.3:1.1-wacom"
    Option     "USB"            "on"
    Option     "ForceDevice"    "ISDV4"
# Calibration for the touch screen.  Yours may vary.
    Option     "TopX"           "1025"
    Option     "TopY"           "800"
    Option     "BottomX"        "25400"
    Option     "BottomY"        "15500"


Section "ServerLayout"
    InputDevice "touchpad"      "CorePointer"
    InputDevice "stylus"        "SendCoreEvents"
    InputDevice "eraser"        "SendCoreEvents"
    InputDevice "touch"         "SendCoreEvents"



Until the driver makes it into kernel You can try this e-build in overlay:

Bluetooth and Wireless

I got Bluetooth to work on paper following the Bluetooth guide. I also installed net-wireless/kdebluetooth. Also to make the start up behave better I added rfcomm to /etc/modules.autoload.d/kernel-2.6 and let udev handle the rest. I want to note that I don't have any other Bluetooth devices so I haven't tried any beyond this.

For the broadcom (4328 (rev 03)) device see the Broadcom 43xx article. A Windows driver that seems to fit ndiswrapper is referenced by this Ubuntu thread. (alternative driver URL) This driver can scan for networks, but is unable to connect to them, generating dmesg errors about being unable to change the bitrate, etc.


The HP tx2000 series uses a Suyin Corp. USB webcam with USB ID 064e:a110, compatible with the media-video/linux-uvc driver. You must have Video for Linux enabled in your kernel to emerge this driver. This driver does not support read()/write() operations, just memory-mapped I/O, so don't be alarmed when cat /dev/video0 reports 'no such device'.

Linux Kernel Configuration: Wireless configuration
 Device Drivers  --->
   Multimedia Devices  --->
     <*> Video for Linux
     [*] Video Capture Devices  --->

The media-video/luvcview application can be used to test the webcam once the module is loaded. Note that this webcam supports yuv capture, but not jpg capture.

luvcview -L -d /dev/video0
luvcview version 0.2.1 
Video driver: x11
A window manager is available
video /dev/video0 
/dev/video0 does not support read i/o
{ pixelformat = 'YUYV', description = 'YUV 4:2:2 (YUYV)' }
{ discrete: width = 640, height = 480 }
        Time interval between frame: 1/30, 1/20, 1/15, 1/10, 1/5, 1/1, 
{ discrete: width = 352, height = 288 }
        Time interval between frame: 1/30, 1/20, 1/15, 1/10, 1/5, 1/1, 
{ discrete: width = 320, height = 240 }
        Time interval between frame: 1/30, 1/20, 1/15, 1/10, 1/5, 1/1, 
{ discrete: width = 176, height = 144 }
        Time interval between frame: 1/30, 1/20, 1/15, 1/10, 1/5, 1/1, 
{ discrete: width = 160, height = 120 }
        Time interval between frame: 1/30, 1/20, 1/15, 1/10, 1/5, 1/1, 
luvcview -d /dev/video0 -f yuv
luvcview version 0.2.1 
Video driver: x11
A window manager is available
video /dev/video0


Stop asked
 Clean Up done Quit 


I have tried to get suspend to disk (with Tuxonice) to work with 3 different results. The first was a complete file system corruption (occurred while trying to hibernate to ram). The 2nd was a freeze on hibernate (to disk). And lastly I got it to work once (to disk, with an "<unsupported>" error popping up). Unfortunately, I don't remember that exact configuration (probably a 2.6.25 kernel). I will try again once I get ndiswrapper working in a kernel higher than 2.6.24.


The official software recognizes the drive, but hasn't been tested with an actual lightscribe disk yet. The official software is provided as a 32-bit x86 library and self-contained qt application, not a kernel driver, so it may actually work on both 32-bit and 64-bit kernels provided emulation libraries are installed where needed.

Fingerprint Reader

The tx2108ca, and perhaps the entire tx2000 series, uses the fairly common AuthenTec aes1610 fingerprint reader.

Code: lsusb
Bus 001 Device 006: ID 08ff:1600 AuthenTec, Inc.

The libraries and software for this model are still in an overlay, so installing them may be a bit involved. One can use the howto in the Asus M50SV fingerprint section to get the reader working for the tx2108ca.

As of July 12 2008, the aes1610 only works with the 0.0.x series of libfprint, not the 9999 series which is actually built from the latest source from git(a CVS-like system). The aes1610 driver has not yet been converted to the newer driver model.

The combination of =app-misc/fprint_demo-0.4, =sys-auth/pam_fprint-0.2, and =media-libs/libfprint-0.0.5 works for fingerprint authentication.

SD/MS/MMC/XD Card Reader

The card reader imitates a full-fledged USB mass storage device that works with the normal usb-storage driver. It presents actual USB device insertions and removals when media is added and removed. The reader has been tested with MMC, SD, and Memory Stick media so far. It properly reports the position of write-protect tabs.

Retrieved from ""

Last modified: Mon, 11 Aug 2008 04:45:00 +0000 Hits: 3,508