The AHCI mode of the ICH6-R serial ATA chipset, although its specification is open and published by Intel, is still rather new and Jeff Garzik's driver code isn't in any Linux distribution I could find. See Jeff's Serial ATA (SATA) Linux status report for the latest on the AHCI driver. The machine comes with the BIOS set to run the ICH6 in AHCI mode.
Since the machine also luckily came with two separate drives, one empty and the other containing some weird software from a big company that should know better, I disconnected the SATA-0 cable from the first drive and after removing the SATA-2 connector from the second drive, connected the SATA-0 cable to the empty second drive. If you look closely at the motherboard, you can see the SATA numbers "0", "1", "2", "3" at various positions close to the cluster of connectors for the blue SATA cables. Then I went into the BIOS (by pressing F2), and in the "Drives" section I selected "RAID Autodetect / ATA" instead of "RAID Autodetect / SATA". Essentially, this makes the drive run in ICH5-like mode instead of in AHCI mode, so the linux installer can see it by using the ata_piix driver without the need to update libata to add in AHCI support. I left the SATA-2 connector disconnected during the install, since if I remember correctly the linux drive was only detected if it was the only one connected. For pointers to more detailed discussion of ICH5, see Rick Moen's Knowlegdebase article on Serial ATA.
I then installed SuSE SLES-9 SP1 Beta 1, selecting the "ACPI disabled" installation option. I'm not sure if disabling ACPI is absolutely necessary for the install to be successful, but the first attempt to install with ACPI enabled resulted in a bunch of packages being reported as missing by YaST, and also the installer eventually hung when installing grub, so when that sort of thing happens, I usually disable ACPI.
You would probably be able to install any recent 2.6 based linux distribution, and have it work fine. I'm testing SLES-9, so that's why I'm putting it on this machine.
During the installation, the monitor will show weird colors (this has since been fixed in SLES-9 SP1 Beta 2). Don't worry, once you install the ATI driver (see below), X11 will be fine.
I also tested using the drive in AHCI mode with kernel 2.6.9 with the 2.6.10-rc1 patch applied, but this seems to hang for me during the ahci module load, still need to debug this. Gabriel Rosa also posted this message on the linux kernel mailing list about SATA drives (beyond the first one) not being found, but this problem seems to have been fixed and both drives show up fine in linux on my system when booting in non-AHCI mode.
The following are the boot messages showing libata's ata_piix driver finding the drives when the BIOS is configured to run the ICH6 in non-AHCI mode ("RAID Autodetect / ATA"):
SCSI subsystem initialized libata version 1.02 loaded. ata_piix version 1.02 PCI: Setting latency timer of device 0000:00:1f.2 to 64 ata1: SATA max UDMA/133 cmd 0xFE00 ctl 0xFE12 bmdma 0xFEA0 irq 20 ata2: SATA max UDMA/133 cmd 0xFE20 ctl 0xFE32 bmdma 0xFEA8 irq 20 ata1: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01 87:4003 88:207f ata1: dev 0 ATA, max UDMA/133, 156250000 sectors ata1: dev 1 cfg 49:2f00 82:3469 83:7f61 84:4003 85:3469 86:3c41 87:4003 88:207f ata1: dev 1 ATA, max UDMA/133, 312500000 sectors (lba48) ata1: dev 0 configured for UDMA/133 ata1: dev 1 configured for UDMA/133 scsi0 : ata_piix ATA: abnormal status 0x7F on port 0xFE27 ata2: disabling port ata2: thread exiting scsi1 : ata_piix Vendor: ATA Model: Maxtor 6Y080M0 Rev: 1.02 Type: Direct-Access ANSI SCSI revision: 05 ata1: dev 0 max request 124KB SCSI device sda: 156250000 512-byte hdwr sectors (80000 MB) SCSI device sda: drive cache: write through sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 > Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 Vendor: ATA Model: WDC WD1600JD-75H Rev: 1.02 Type: Direct-Access ANSI SCSI revision: 05 ata1: dev 1 max request 512KB (lba48) SCSI device sdb: 312500000 512-byte hdwr sectors (160000 MB) SCSI device sdb: drive cache: write through sdb: sdb1 sdb2 sdb3 Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
This section has moved to a separate page, as the card can be used in quite a few different ways, for example when using the proprietary fglrx driver, it's now possible to get a wide desktop spanning two monitors, with 3D acceleration working. The new page describing some of these more complicated configurations is here
The Audigy 2 soundcard also works with the alsa drivers, including digital output. The line-in doesn't appear to work at all, so it's not possible to do any recording on linux using this card: tested with kernel 2.6.12.3. It seems that there's something different about this Dell OEM Audigy 2 card as compared to a standard Audigy 2, card which works fine for recording in linux.
See here for more details.
ssh -X root@localhost # Remember to enable DMA on the optical drives, before writing to them: hdparm -d1 /dev/hda hdparm -d1 /dev/hdb k3b
Although k3b is able to use the NEC ND-3100AD drive to write to DVD+RW, DVD+R and CD-R media, it isn't able to write to DVD-R media. Strangely, it doesn't seem to be able to write to CD-RW media either, and errors out. Yet to investigate this. For now, k3b is able to write CD-RW media using the Samsung SW-252S CD-RW drive instead.
For reference, the contents of /proc/sys/dev/cdrom/info are shown below.
cat /proc/sys/dev/cdrom/info
CD-ROM information, Id: cdrom.c 3.20 2003/12/17
drive name: hdb hda
drive speed: 48 48
drive # of slots: 1 1
Can close tray: 1 1
Can open tray: 1 1
Can lock tray: 1 1
Can change speed: 1 1
Can select disk: 0 0
Can read multisession: 1 1
Can read MCN: 1 1
Reports media changed: 1 1
Can play audio: 1 1
Can write CD-R: 1 1
Can write CD-RW: 1 1
Can read DVD: 1 0
Can write DVD-R: 0 0
Can write DVD-RAM: 0 0
Can read MRW: 0 0
Can write MRW: 0 0
Can write RAM: 1 0
dmesg|grep hdb
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA
hdb: _NEC DVD+RW ND-3100AD, ATAPI CD/DVD-ROM drive
hdb: ATAPI 48X DVD-ROM CD-R/RW drive, 2048kB Cache
component input doesn't correctly filter Macrovision (e.g. from a DVD player), and passes the messy signal on through to the monitor's Genesis gm1601 scaler processor, resulting in it becoming "confused" and rendering the video with a thin "wavy" segment, usually near the top of the video. So if you're seeing this effect, don't worry, there's nothing wrong with your monitor. The 2405FPW also doesn't support HDCP, so you can't use it as a TV. Probably this is all intended by Dell, to help us get more work done. Recently, I found that the Samsung DVD-HD841 players have a useful workaround for these problems: if you power on a DVD-HD841 with no disc in the drive, and press the following sequence of keys on its remote control: "ANGLE", "4", "3", "2", "7" (which will display the message "HDCP Free") it will cause the player to turn off the HDCP on its DVI output, making it nicely compatible with the Dell 2405FPW monitor. Also, the component output, when run at either 720p (1280x720) or 1080i (1920x1080) displays no wavy lines and looks almost as good as the DVI output (colors look a bit more realistic on the DVI output), making it convenient if you prefer not to switch the DVI connector from your computer to the DVD player and back again each time.