[Hardware] [gmane.linux.ide] Solution -> sata_sil + Maxtor problem

Sergey Vlasov vsu на altlinux.ru
Сб Ноя 27 21:18:39 MSK 2004


Hello!

Вот нарыл в рассылке linux-ide - возможно, это кому-то будет интересно.
Пишут, что SATA-контроллер Silicon Image 3112 не работает с материнской
платой ASUS A7V, если в настройках BIOS включена опция "Byte Merge" в
настройках PCI. Вероятно, эта проблема касается и других похожих плат.

Кстати, пишут, что эта опция вызывает проблемы и с некоторыми сетевыми
картами - например, с 3com 3C905:

http://www.adriansrojakpot.com/Speed_Demonz/New_BIOS_Guide/Byte_Merge.htm


On Sat, 27 Nov 2004 17:57:39 +0000, Rasmus Melgaard wrote:

> Thanks David, goggle on!
> 
> Well, that did it! I narrowed it a bit.
> 
> For anybody else with similar problems
>  - I have a Asus A7V (VIA chipset, early revision 1.01 of MB), absolutely 
> latest bios was installed. 
>  - Silicon Image 3112 pci-sata-controller (bios 4250). 
>  - Maxtor 160Gb SATA disk (6Y160M0), but the problem is probably not related 
> to the drive.
> 
>  - To solve problem below, disable "Byte Merge" PCI-feature in the bios. 
> Silicon Image 3112 doesn't work with it (in Linux).
> 
> Everythings peacy for now, what was I thinking of enabling byte-merge feature 
> in the bios, I knew it was buggy. 
> 
> /Rasmus Melgaard
> 
> 
> On Wednesday 24 November 2004 10:26, David Greaves wrote:
>> Just for the Google of it...
>>
>> I had almost exactly this problem with a cheap plugin sata_sil on 2.6.9
>> on Maxtor 250Gb drives with an old Asus A7V133 motherboard and solved it
>> by upgrading the motherboard BIOS and/or resetting the BIOS values to
>> defaults. I narrowed it down to PCI bus settings.
>>
>> David
>>
>> Jeff Garzik wrote:
>> > Rasmus Melgaard wrote:
>> >> Hi,
>> >>
>> >> I have a IDE/SATA problem. I have a Silicon Image 3112
>> >> sata-controller with a Maxtor 160 Gb drive connected. Controller and
>> >> drive is detected in the kernel-boot process, but an error happens
>> >> during boot, I think the linux driver gets an response it doesn't
>> >> expect.
>> >>
>> >> I'm using for testing the mm-kernel: 2.6.9-rc1-mm1. Every thing seems
>> >> to work in Windows, but since I mainly use Linux (Gentoo), I would
>> >> like it to work here.
>> >>
>> >> Does anybody have an ideer of how to proceed to solve this problem ?
>> >> Mvh
>> >> Rasmus
>> >>
>> >> Important part of log:
>> >> Sep  5 15:55:39 rasmus scsi1 : sata_sil
>> >> Sep  5 15:55:39 rasmus ata2: no device found (phy stat 00000000)
>> >> Sep  5 15:55:39 rasmus scsi2 : sata_sil
>> >> Sep  5 15:55:39 rasmus Vendor: ATA       Model: Maxtor 6Y160M0
>> >> Rev: YAR5
>> >> Sep  5 15:55:39 rasmus Type:   Direct-Access
>> >> ANSI SCSI revision: 05
>> >> Sep  5 15:55:39 rasmus SCSI device sda: 320173056 512-byte hdwr
>> >> sectors (163929 MB)
>> >> Sep  5 15:55:39 rasmus SCSI device sda: drive cache: write back
>> >> Sep  5 15:55:39 rasmus /dev/scsi/host1/bus0/target0/lun0:<3>ata1:
>> >> command 0x25 timeout, stat 0x58 host_stat 0x60
>> >> Sep  5 15:55:39 rasmus ata1: status=0x58 { DriveReady SeekComplete
>> >> DataRequest }
>> >> Sep  5 15:55:39 rasmus SCSI error : <1 0 0 0> return code = 0x8000002
>> >> Sep  5 15:55:39 rasmus Current sda: sense = 70 10
>> >> Sep  5 15:55:39 rasmus end_request: I/O error, dev sda, sector 0
>> >> Sep  5 15:55:39 rasmus Buffer I/O error on device sda, logical block 0
>> >> Sep  5 15:55:39 rasmus ATA: abnormal status 0x58 on port 0xE882E087
>> >> Sep  5 15:55:39 rasmus ATA: abnormal status 0x58 on port 0xE882E087
>> >> Sep  5 15:55:39 rasmus ATA: abnormal status 0x58 on port 0xE882E087
>> >> Sep  5 15:55:39 rasmus ata1: command 0x25 timeout, stat 0xd8
>> >> host_stat 0x61
>> >> Sep  5 15:55:39 rasmus ata1: status=0xd8 { Busy }
>> >> Sep  5 15:55:39 rasmus SCSI error : <1 0 0 0> return code = 0x8000002
>> >> Sep  5 15:55:39 rasmus Current sda: sense = 70 10
>> >> Sep  5 15:55:39 rasmus end_request: I/O error, dev sda, sector 0
>> >> Sep  5 15:55:39 rasmus Buffer I/O error on device sda, logical block 0
>> >
>> > It's quite clearly a device error...  Try upgrading your system and
>> > card BIOS, try switching cables, try booting with "noapic" or
>> > "acpi=off" or "pci=biosirq" or something like that...
>> >
>> >     Jeff

-- 
Sergey Vlasov



Подробная информация о списке рассылки Hardware