On Friday 07 December 2007, crosvera wrote: > syslog it's attached Thanks for the additional info. I think we can now say this is a kernel problem. The lspci info showed that the IDE controller should be supported by ahci and your lsmod output shows that that module is loaded.
If I look at your syslog, I see the following: scsi0 : ahci scsi1 : ahci scsi2 : ahci scsi3 : ahci ata1: SATA max UDMA/133 cmd 0xffffc200001ec100 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 1277 ata2: SATA max UDMA/133 cmd 0xffffc200001ec180 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 1277 dma 0x0000000000000000 irq 1277 ata4: SATA max UDMA/133 cmd 0xffffc200001ec280 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 1277 ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2: SATA link down (SStatus 0 SControl 300) ata3: SATA link down (SStatus 0 SControl 300) ata4: SATA link down (SStatus 0 SControl 300) This shows that the driver is loaded correctly and sees that there is a something connected to the port ata1. However, compare that to the dmesg output from my own system (I have 2 SATA harddisks and a SATA DVD-RW): scsi0 : ahci scsi1 : ahci scsi2 : ahci scsi3 : ahci ata1: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0x903c4100 irq 1274 ata2: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0x903c4180 irq 1274 ata3: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0x903c4200 irq 1274 ata4: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0x903c4280 irq 1274 ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7: HDT722516DLA380, V43OA96A, max UDMA/133 ata1.00: 321672960 sectors, multi 16: LBA48 NCQ (not used) ata1.00: configured for UDMA/133 ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [...] ata4: SATA link down (SStatus 0 SControl 300) scsi 0:0:0:0: Direct-Access ATA HDT722516DLA380 V43O PQ: 0 ANSI: 5 scsi 1:0:0:0: Direct-Access ATA HDT722516DLA380 V43O PQ: 0 ANSI: 5 scsi 2:0:0:0: CD-ROM Optiarc DVD RW AD-7170S 1.00 PQ: 0 ANSI: 5 Clearly something is missing in your output: the kernel fails to detect the harddisk itself. There is a pretty good chance this has been fixed in later kernels, so that should be checked first. There are two things you could try: - try changing the BIOS setting for your SATA controller and see if you can install then; if that works, install the 2.6.23 kernel from unstable, change the BIOS settings back and see if the disk is recognized then - try an installation using this unofficial Etch image, which already has a 2.6.23 kernel: http://kmuto.jp/debian/d-i/ (etch-custom-1013.iso for amd64) If the 2.6.23 kernel does not detect the disk either, a mail to the upstream kernel developers would be the next step. Did you have to manually load the forcedeth module again? From the syslog it seems to be loaded correctly automatically: main-menu[1168]: INFO: Menu item 'ethdetect' selected net/hw-detect.hotplug: Detected hotpluggable network interface lo kernel: forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60. kernel: ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 20 kernel: ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LMAC] -> GSI 20 (level, low) -> IRQ 20 kernel: PCI: Setting latency timer of device 0000:00:0a.0 to 64 kernel: forcedeth: using HIGHDMA kernel: 0000:00:0a.0: Invalid Mac address detected: db:88:c2:24:1b:00 kernel: Please complain to your hardware vendor. Switching to a random MAC. kernel: eth0: forcedeth.c: subsystem: 01025:0127 bound to 0000:00:0a.0 net/hw-detect.hotplug: Detected hotpluggable network interface eth0 Note the line about "Invalid Mac address" though! The fact that a random MAC gets assigned could cause problems with udev assigning an interface name on reboots. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]