Hello,
2.6.17.13 works OK on this VIA Epia SP8000.
(remember vaguely about some (PCI?) fixups to get things going)
Now I try to get 2.6.18.1 working. SATA is detected by this kernel but
disk gives timeout while 2.6.17.13 boots fine.
Some burbs:
Links is up but SStatus 113 SControl 300
qc timeout (cmd 0xec)
failed to IDENTIFY
This results in a kernel panic.
Any ideas?
2.6.17.13 gives stuff like this:
scsi0 : sata_via
ata2: SATA link up 1.5 Gbps (SStatus 113)
ata2: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3c01 87:4023
88:40ff
ata2: dev 0 ATA-7, max UDMA7, 312581808 sectors: LBA48
ata2: dev 0 configured for UDMA/133
scsi1 : sata_via
Vendor: ATA Model: SAMSUNG HD160JJ Rev: ZM10
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 sda10 >
sd 1:0:0:0: Attached scsi disk sda
Udo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]