> The amd64 kernel in Etch will not boot on motherboards based on the
> nvidia chipset


Way too general. And way too incorrect.
I have about 10 etch/amd64 machines with sata_nv, and they work fine.

~# uname -a
Linux mailhost 2.6.18-5-vserver-amd64 #1 SMP Sun Aug 12 21:05:24 UTC
2007 x86_64 GNU/Linux

sata_nv 0000:00:07.0: version 2.0
ACPI: PCI Interrupt Link [APSI] enabled at IRQ 20
GSI 19 sharing vector 0x32 and IRQ 19
ACPI: PCI Interrupt 0000:00:07.0[A] -> Link [APSI] -> GSI 20 (level,
low) -> IRQ 50
PCI: Setting latency timer of device 0000:00:07.0 to 64
ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xCC00 irq 50
ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xCC08 irq 50
scsi0 : sata_nv
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth 0/32)
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/133
scsi1 : sata_nv
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth 0/32)
ata2.00: ata2: dev 0 multi count 16
ata2.00: configured for UDMA/133
Vendor: ATA Model: ST3250623NS Rev: 5.01
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: ST3250623NS Rev: 5.01
Type: Direct-Access ANSI SCSI revision: 05
ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 23
ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [APSJ] -> GSI 23 (level,
low) -> IRQ 217
PCI: Setting latency timer of device 0000:00:08.0 to 64
ata3: SATA max UDMA/133 cmd 0x9E0 ctl 0xBE2 bmdma 0xB800 irq 217
ata4: SATA max UDMA/133 cmd 0x960 ctl 0xB62 bmdma 0xB808 irq 217
scsi2 : sata_nv
ata3: SATA link down (SStatus 0 SControl 300)
scsi3 : sata_nv
ata4: SATA link down (SStatus 0 SControl 300)





--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org