https://bugzilla.novell.com/show_bug.cgi?id=462604 User linux-clusters@mindspring.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462604#c3 --- Comment #3 from Steven DuChene <linux-clusters@mindspring.com> 2008-12-28 17:15:06 MST --- I have discovered the Fedora10 only find the SATA disk in the system if the SATA mode in the system BIOS is set to AHCI. If the SATA mode in the system BIOS is set to SATA, then Fedora10 is not able to detect a sata disk. If the SATA mode setting in the BIOS is set to AHCI then Fedora10 is able to see the disk. If I leave the SATA mode set to AHCI and boot into OpenSuSE-11.1 then I see the following errors in the dmesg output: SCSI subsystem initialized libata version 3.00 loaded. pata_amd 0000:00:06.0: version 0.3.10 pata_amd 0000:00:06.0: setting latency timer to 64 scsi0 : pata_amd scsi1 : pata_amd ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14 ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15 ata2: port disabled. ignoring. ahci 0000:00:09.0: version 3.0 ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 23 ahci 0000:00:09.0: PCI INT A -> Link[LSA0] -> GSI 23 (level, low) -> IRQ 23 ahci 0000:00:09.0: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x3f impl SATA mode ahci 0000:00:09.0: flags: 64bit ncq sntf led clo pmp pio ahci 0000:00:09.0: setting latency timer to 64 scsi2 : ahci scsi3 : ahci scsi4 : ahci scsi5 : ahci scsi6 : ahci scsi7 : ahci ata3: SATA max UDMA/133 abar m8192@0xfce76000 port 0xfce76100 irq 4347 ata4: SATA max UDMA/133 abar m8192@0xfce76000 port 0xfce76180 irq 4347 ata5: SATA max UDMA/133 abar m8192@0xfce76000 port 0xfce76200 irq 4347 ata6: SATA max UDMA/133 abar m8192@0xfce76000 port 0xfce76280 irq 4347 ata7: SATA max UDMA/133 abar m8192@0xfce76000 port 0xfce76300 irq 4347 ata8: SATA max UDMA/133 abar m8192@0xfce76000 port 0xfce76380 irq 4347 ata3: SATA link down (SStatus 0 SControl 300) ata4: SATA link down (SStatus 0 SControl 300) ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata5.00: qc timeout (cmd 0xec) ata5.00: failed to IDENTIFY (I/O error, err_mask=0x4) ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata5.00: qc timeout (cmd 0xec) ata5.00: failed to IDENTIFY (I/O error, err_mask=0x4) ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata5.00: qc timeout (cmd 0xec) ata5.00: failed to IDENTIFY (I/O error, err_mask=0x4) ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata6: SATA link down (SStatus 0 SControl 300) ata7: SATA link down (SStatus 0 SControl 300) ata8: SATA link down (SStatus 0 SControl 300) ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 19 The Fedora10 kernel correctly detects and identifies the SATA disk in the system without the above sort of SATA link down errors. Also at the beginning of the boot.msg file in /var/tmp/ I see the following errors at the beginning: Inspecting /boot/System.map-2.6.27.7-9-default Cannot find map file. No module symbols loaded - kernel modules not enabled. Cannot build symbol table - disabling symbol lookups klogd 1.4.1, log source = ksyslog started. <6>Initializing cgroup subsys cpuset <6>Initializing cgroup subsys cpu <5>Linux version 2.6.27.7-9-default (geeko@buildhost) (gcc version 4.3.2 [gcc-4_3-branch revision 141291] (SUSE Linux) ) #1 SMP 2008-12-04 18:10:04 +0100 <6>Command line: root=/dev/disk/by-id/scsi-SIBM_DNES-318350W_AKG5X817-part2 resume=/dev/disk/by-id/scsi-SIBM_DNES-318350W_AKG5X817-part1 splash=silent vga=0x31a I do not know if the kernel module errors has an effect on this or not. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.