Difference between revisions of "Dell Latitude D600"

From ArchWiki
Jump to: navigation, search
(Xorg.conf: outdated config and it's not needed anyway)
Line 200: Line 200:
An Epson Stylus Color C86 is used in this setup. It uses <tt>gutenprint</tt> (formerly <tt>gimp-print</tt>) for it's driver and can be setup via Firefox at http://localhost:631.
An Epson Stylus Color C86 is used in this setup. It uses <tt>gutenprint</tt> (formerly <tt>gimp-print</tt>) for it's driver and can be setup via Firefox at http://localhost:631.
mbeisser - (Jan '08) Initial version completed.

Revision as of 15:58, 13 January 2011

The d600 was a released by Dell on 3/12/03. At the time of its release it was met with great reviews. Despite being almost 5 years old this business laptop is perfectly capable of delivering a satisfying Linux experience.


This is not a guide on how to install Arch (for help with that see the installation guide), but rather an attempt to cover the steps of how to take full advantage of the laptop's hardware. Despite being an Arch-wiki page, everything explained here should apply to other Linux distributions as well.

Getting most of the hardware to work correctly under Linux, is not overly difficult (in fact these days most things are auto-detected, and "just work"TM. Keep in mind I am by no means an expert of hardware in Linux so you may find better solutions than the ones presented here. If you do please edit this guide so that other people may benefit as well.


As always the documentation for a Dell laptop is almost non-existant. The only documentation you are going to find for the d600 is the spec sheet and some useless pdf files (although the service guide can be useful if you need to take the laptop apart for some reason). So with that being said the only way to find out useful information is to inspect each individual hardware component.


Here's the output of Template:Command


  • Intel Pentium M Processor
  • ATI Radeon 9000 (RV250 Mobility FireGL 9000 4x AGP)
  • Intel 2200 Pro/Wireless LAN card OR
    • Broadcom 54g Wireless card
  • Broadcom BCM570 Ethernet card
  • Integrated Intel 82801 (intel8x0) sound card
  • PCMCIA card port
  • Alps touchpad
  • Function/Audio keys
  • CD/RW, DVD+/-RW
  • IRDA


  • Cpu frequency scaling
  • Video Card: including framebuffer (open source radeon driver)
  • Intel 2200 Pro/Wireless Lan card (ipw2200 driver)
    • Broadcom 54g Wireless card (ndiswrapper with windows driver bcmwl5 or native kernel module)
  • Soundcard (including mixing with alsa)
  • Function/audio keys
  • Touchpad
  • CD/RW, DVD+/-RW
  • Ethernet Card
  • Hardware monitoring (i8k kernel module)


  • IRDA
  • Modem (not planning on testing)
  • ACPI Sleep States


Bios Update

Now before you delete the Windows partition, you'll want to update the bios to the newest version (rev. A16 as of this writing), to avoid any potential non-OS hardware related problems. Grab the executable and install it.

Post Installation


The D600 comes with either an Intel Pro Wireless 2200 or a Broadcom BCM43xx. The BCM43xx can be quite fickle under Linux, however the Intel Pro Wireless works flawlessly and is trivial to install. As the driver is already included in the kernel the only thing that needs to be done is to install the firmware.

# pacman -S ipw2200-fw

Now add the entry ipw2200 in the modules section of Template:Filename, and add/change the line NET_PROFILES=(main). Now make a main network-profile in Template:Filenamefollowing the template in that directory. It will look something like the following.


If you run into the strange problem of your wireless interface switching between eth0 and eth1 at boot then you may want to use nameif. Simply put your network id followed by the mac address in /etc/mactab.

eth0 00:0C:DB:E8:38:5A
wlan0 00:1F:12:62:2E:CC

(Taken from here.) In addition, a small change to /etc/rc.d/network is necessary to run the nameif command prior to configuring the interfaces. The following excerpt from /etc/rc.d/network shows the lines that need to be added. This change simply checks for the existance of the /etc/mactab file and if it exists executes nameif to assign interface names.

              stat_busy "Starting Network"
              ##### begin nameif change #####
              # set names
              if [ -n /etc/mactab ]; then
              ##### end nameif change #####
              # bring up bridge interfaces
              # bring up ethernet interfaces

If you are using a Broadcom wireless card you will probably have issues trying to get the Gnome or KDE network gui's to manage your card correctly. wicd doesn't seem to have any problems managing this card, however.

CPU Scaling

See cpufrequtils.

Suspend to Ram

This is easily accomplished by installing uswsusp from AUR. Contrary to the ominous output from pacman no additional configuration is needed. Additionally, s2ram will probably output an error message saying that This machine can only suspend without framebuffer. but I have not encountered problems with resuming from suspend.


# s2ram -f


The pre-compiled Arch kernel certainly works, however, it has a lot of bloat so you'll probably want to compile your own. It's possible to make a custom kernel via ABS, however, building a kernel manually is just as easy. Grab the source from kernel.org and extract it to Template:Filename. Make a simlink (ln -s /usr/src/linux /usr/src/kernel-folder) and then make menuconfig.

(NOTE: You probably need to install make (for obvious reasons) and diffutils or you will probably get the following error message.)

/bin/sh: cmp: command not found
Inconsistent kallsyms data
make: *** [vmlinux] Error 1

If you need a starting point for your kernel, here is a .config.

(IMPORTANT: if you use this you will probably have to edit Template:Filenameand Template:Filename/Template:Filenameto use /dev/hdax and not /dev/sdax or else your kernel will not boot!!)

When the .config is to your liking do:

# make prepare 
# make 
# make modules_install;
# cp /usr/src/linux/arch/i386/boot/bzImage /boot/kernel_name

Before you reboot be sure to edit Template:Filename/Template:Filename.


Aside: The kernel line processor.max_cstate=2 disables the CPU from going into the 2 higher power saving states. While this causes the battery to use several hundred more mW of power it also disables the annoying CPU wine that is usually very noticeable. (This problem also exists in Windows.) It seems that the kernel module usb-uhci is partially related to this problem. Disabling this is an option but it will disables USB support...


With the constant stream of updates, and TONS of outdated documentation on the web, Xorg can be a pain to configure.

Video Card

Use the open source "xf86-video-ati" radeon driver. ATI dropped support for the Radeon (RV250) Mobility FireGL 9000 after catalyst driver version 8.28.8. The binary and the userspace tools are available in the AUR, however they WILL NOT load with Xorg >= 7.2.

Dual Monitors

Setting up dual monitors used to be an insanely frustrating ordeal because you would have to edit xorg.conf and then start/test/reset X. Luckily RandR fixes this. To summarize from here and here "RandR 1.2 provides automatic discovery of modes (resolutions, refresh rates, etc.) coupled with the ability to configure outputs dynamically (resize, rotate, move, etc.)." The only thing required by the user is to specify a virtual display area, and run the appropriate xrandr command. (For a nice tutorial see here.)


  1. Xinerama is deprecated and will cause X to segfault. This is a known regression by the X developers and they have no intention of fixing it as Xinerama was basically a hack anyways.
  2. MergedFB has now been completely replaced by RandR.

This particular setup uses an external 20" LCD running at 1680x1050 and is connected to a docking station via a DVI cable. Now, it would be useful if the external monitor was auto detected and configured whenever we started the computer. Now because the computer is a laptop we also don't want to try and configure the screen if it isn't connected. The following bash script will do just that.

monitor=`xrandr | grep -i DVI | cut -d" " -f2`
if [ $monitor = "connected" ]; then
    xrandr --output DVI-0 --right-of LVDS --mode 1680x1050
    xrandr --output DVI-0 --off


Getting both the touchpad and an external mouse to play nicely together can be tricky. If you use the evdev driver then you don't have to specify the ButtonMapping, however, I've had better luck using the regular mouse driver. This particular setup specifies a Logitech MX400 USB mouse as the core pointer and Alps touchpad as a secondary device. (For more complete instructions see here.)


An Epson Stylus Color C86 is used in this setup. It uses gutenprint (formerly gimp-print) for it's driver and can be setup via Firefox at http://localhost:631.