Hello, I think there is a problem with kernel-image-2.6.8-1-686, but I'm not sure whether I messed up something...
I installed sarge on a SATA host a while ago (Intel ICH, worked just fine!). Now I upgraded from the installer's kernel-image-2.6.8-1-386 to version 2.6.8-10 of the kernel-image-2.6.8-1-[36]86 package. The problem: The SATA code is built as modules in the regular kernel package, but it mustn't be. You need the following kernel config: CONFIG_SCSI_SATA=y CONFIG_SCSI_SATA_SVW=y CONFIG_SCSI_ATA_PIIX=y CONFIG_SCSI_SATA_NV=y CONFIG_SCSI_SATA_PROMISE=y CONFIG_SCSI_SATA_SX4=y CONFIG_SCSI_SATA_SIL=y CONFIG_SCSI_SATA_SIS=y CONFIG_SCSI_SATA_VIA=y CONFIG_SCSI_SATA_VITESSE=y config-2.6.8-1-386 from the package in the archive lists all these as "=m". I suspect that the debian-boot folks realized what the problem was, but didn't tell debian-kernel to build SATA into the kernel. Obviously, you cannot load the SATA modules if you need the SATA code to access the hard disc. Cheers, Richard PS: ALSA does not work on that SATA machine with 2.6.8, only with 2.6.9. -- __ _ |_) /| Richard Atterer | GnuPG key: | \/¯| http://atterer.net | 0x888354F7 ¯ '` ¯
