Hello,
> Peter Favrholdt wrote:
>> My feeling is this is not caused by 1.5Gbps or 3.0Gbps operation.
>> <...snip>
>> My next test will be a plain 2.6.21rc2. Then I'll apply the patches one
>> by one.
>
> I've tested 2.6.21-rc2 which fails (sdc down after 27 minutes & sdd down
> after 46 minutes).
Mark Lord wrote:
> The READ/WRITE LONG commands are theoretically obsolete,
> but the majority of drives in existance still implement them.
>
> The WRITE_LONG and WRITE_LONG_ONCE commands are of particular
> interest for fault injection testing -- eg. creating "media errors"
> at specific location
On Tue, Mar 13, 2007 at 01:11:44AM -0400, Andreas Dilger wrote:
> I'd guess a vast majority of IO will have the end similarly
> misaligned as the start. Very little filesystem IO is 512 bytes,
> possibly excluding XFS in an unusual mode.
XFS (mkfs.xfs) can be told what the native sector size is
Hello, Brian.
Brian King wrote:
> Tejun Heo wrote:
>> * ipr is now the only user of ata_host_init(). Either kill it by
>> converting ipr to use ata_host_alloc() and friends or rename and
>> move it to libata-scsi.c
>
> One of the problems with converting ipr to use ata_host_alloc and
> frien
Jamie Clark wrote:
> Add Adaptec 1220SA (SIL3132) to devices claimed by sata_sil24
> Patch generated against 2.6.20.2
>
> Signed-off-by: Jamie Clark <[EMAIL PROTECTED]>
Acked-by: Tejun Heo <[EMAIL PROTECTED]>
--
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the
On Mar 12, 2007 10:26 -0400, Jeff Garzik wrote:
> In my own experiments on my own Fedora workstation, ~66% of IOs in Linux
> start on an odd sector, and ~33% started on even-numbered sectors. For
> a 1K-sector drive with 'odd' alignment, the configuration Microsoft will
> likely want, that mea
Add Adaptec 1220SA (SIL3132) to devices claimed by sata_sil24
Patch generated against 2.6.20.2
Signed-off-by: Jamie Clark <[EMAIL PROTECTED]>
--- drivers/ata/sata_sil24.c.orig 2007-03-10 02:58:04.0 +0800
+++ drivers/ata/sata_sil24.c2007-03-12 20:41:02.0 +0800
@@ -352,6
Why is the access to Control register needed?
To execute soft reset for example.
> In the perfect case i would like to be able to execute vendor command
> set (reverse engineered).
Sounds interesting. :-)
Could you give some more details on what are you going to implement?
Reading/writing
It works! I'm having trouble getting the hdparm info for you, it
doesn't seem to like the libata interface? Appears to be the newest
version of hdparm (6.9). Something I'm missing?
luna:~# hdparm -I /dev/sr0
HDIO_DRIVE_CMD(identify) failed: Input/output error
Yes, well, Jeff has patches in h
hi
I got it running on amd64 (with my minimalistic patch)
I checked out the 2.6.21-rc3-mm there's some marvell
related stuff but I think it's for a mixed marvell cards with
serail and parallel ata. Still this patch has chip id 0x6145
while my 0x6141 (it's serial ata only) has to be added
to get r
It is a pata cd drive, attached to the JMicron controller.
I'll look into whether the usb ports power off on shutdown.
Thanks,
Phil
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/
Tejun Heo wrote:
>> Testing the new libata ICH PATA drivers. There's one PATA port on this
>> chip, and I've got two optical drives connected to it. The master drive
>> fails to detect. The slave detects and works properly.
> Can you test 2.6.20.1 and post full dmesg?
Here's
Alan Cox wrote:
Umm... someone reported originally getting problems with R/W LONG and PIIX
but not AHCI and we discussed whether we might need to turn the
prefetch/postwrite off for it. Would have been about October last year.
Ah, well, yes, they would have problems unless my patch had been ap
On Mon, 12 Mar 2007 18:23:22 -0400
Mark Lord <[EMAIL PROTECTED]> wrote:
> Alan Cox wrote:
> > On Mon, 12 Mar 2007 15:08:19 -0400
> > Mark Lord <[EMAIL PROTECTED]> wrote:
> >
> >> The READ/WRITE LONG commands are theoretically obsolete,
> >> but the majority of drives in existance still implement
> Is that a PATA cd-drive? If so, then you must have hooked it up
> to the JMicron IDE controller. That driver is just plain buggy.
It ought to be rock solid, perhaps you can send me a detailed bug report.
In fact it actually doesn't do very much at all as the controller is
smart enough to do al
Phil Kaslo wrote:
Hello,
I have a new machine, Asus motherboard, in which the cd drive malfunctions
if the internal nic on the mb (RealTek RTL8168b/8111b) is actively in use.
The cd drive, on ide2, is, as per dmesg, a Sony:
ide2: BM-DMA at 0xa400-0xa407, BIOS settings: hde:pio, hdf:pio
hd
I have built and booted a 2.6.21-rc3 kernel with the sata_inic162x
driver compiled as a module. The machine has a SIIG-branded SATA-II
150 card in it with two drives attached, a matching pair of 320GB
Seagates currently containing no data. I am aware of the driver's
"highly experimental" status a
Hello,
I have a new machine, Asus motherboard, in which the cd drive malfunctions
if the internal nic on the mb (RealTek RTL8168b/8111b) is actively in use.
The cd drive, on ide2, is, as per dmesg, a Sony:
ide2: BM-DMA at 0xa400-0xa407, BIOS settings: hde:pio, hdf:pio
hde: SONY DVD RW AW-Q1
Tejun Heo wrote:
> * ipr is now the only user of ata_host_init(). Either kill it by
> converting ipr to use ata_host_alloc() and friends or rename and
> move it to libata-scsi.c
One of the problems with converting ipr to use ata_host_alloc and
friends is that it then forces ipr to tell libata
Alan Cox wrote:
On Mon, 12 Mar 2007 15:08:19 -0400
Mark Lord <[EMAIL PROTECTED]> wrote:
The READ/WRITE LONG commands are theoretically obsolete,
but the majority of drives in existance still implement them.
The WRITE_LONG and WRITE_LONG_ONCE commands are of particular
interest for fault inject
On Mon, 12 Mar 2007 22:00:15 +
Alan Cox <[EMAIL PROTECTED]> wrote:
> > Meanwhile, to solve the problem for these people, and without introducing
> > a lot of new code at this stage in the release, perhaps you can suggest
> > a more accurate way to detect PATA vs. SATA so we can fix the bug?
On Mon, 12 Mar 2007 15:08:19 -0400
Mark Lord <[EMAIL PROTECTED]> wrote:
> The READ/WRITE LONG commands are theoretically obsolete,
> but the majority of drives in existance still implement them.
>
> The WRITE_LONG and WRITE_LONG_ONCE commands are of particular
> interest for fault injection testi
> Meanwhile, to solve the problem for these people, and without introducing
> a lot of new code at this stage in the release, perhaps you can suggest
> a more accurate way to detect PATA vs. SATA so we can fix the bug?
I think the problem starts with the question. It supposes the BIOS knows
the
>> I don't get this. If you mean partitions defined by the classic DOS
>> partition table format, then AFAICS, such a partition can start in any
>> sector.
>
>Only at "logical cylinder boundary" (except for the first partition).
That's a requirement in ancient DOS systems that use CHS addre
Applied on top of latest GIT this patch make the warning[1] disappear.
Thanks,
Fabio
[1] ata2: reset failed, giving up
On 3/12/07, Tejun Heo <[EMAIL PROTECTED]> wrote:
->prereset() returns -ENOENT to tell libata that the port is empty and
reset sequencing should be stopped. This is not an erro
Stephen Hemminger wrote:
> On Tue, 13 Mar 2007 04:03:00 +0900
> Tejun Heo <[EMAIL PROTECTED]> wrote:
>
>> Stephen Hemminger wrote:
1. the controller has IRQ stuck high (infrequent but possible)
2. the IRQ is already requested by another device
3. the IRQ gets disabled due to screami
On Tue, 13 Mar 2007 04:03:00 +0900
Tejun Heo <[EMAIL PROTECTED]> wrote:
> Stephen Hemminger wrote:
> >> 1. the controller has IRQ stuck high (infrequent but possible)
> >> 2. the IRQ is already requested by another device
> >> 3. the IRQ gets disabled due to screaming interrupts at the moment
> >>
Douglas Gilbert wrote:
Bryan Henderson wrote:
What is an odd-aligned disk?
s/disk/partition/ ?
Example: An odd-aligned disk in the 512-b logical / 1K-physical
scenario is where odd LBAs indicate the start of a 1K physical sector.
An even-aligned disk is where even LBAs indicate the start
Bryan Henderson wrote:
>> DOS partitions start partitions on odd-numbered sectors
>
> I don't get this. If you mean partitions defined by the classic DOS
> partition table format, then AFAICS, such a partition can start in any
> sector.
Bryan,
Typically the first partition on a DOS partitioned
Mark Lord wrote:
The READ/WRITE LONG commands are theoretically obsolete,
but the majority of drives in existance still implement them.
The WRITE_LONG and WRITE_LONG_ONCE commands are of particular
interest for fault injection testing -- eg. creating "media errors"
at specific locations on a dis
The READ/WRITE LONG commands are theoretically obsolete,
but the majority of drives in existance still implement them.
The WRITE_LONG and WRITE_LONG_ONCE commands are of particular
interest for fault injection testing -- eg. creating "media errors"
at specific locations on a disk.
The fussy bit
Stephen Hemminger wrote:
>> 1. the controller has IRQ stuck high (infrequent but possible)
>> 2. the IRQ is already requested by another device
>> 3. the IRQ gets disabled due to screaming interrupts at the moment
>> ata_piix does pci_enable_device().
>>
>> I think we can be much more resilient to
On Tue, 13 Mar 2007 01:56:36 +0900
Tejun Heo <[EMAIL PROTECTED]> wrote:
> Thomas Gleixner wrote:
> > On Mon, 2007-03-12 at 17:31 +0100, Michal Piotrowski wrote:
> >> Calling initcall 0xc19154d8: piix_ide_init+0x0/0xbb()
> >> Calling initcall 0xc19155b6: generic_ide_init+0x0/0x16()
> >> Calling ini
Hello.
Bryan Henderson wrote:
DOS partitions start partitions on odd-numbered sectors
I don't get this. If you mean partitions defined by the classic DOS
partition table format, then AFAICS, such a partition can start in any
sector.
Only at "logical cylinder boudary" (except for the f
>DOS partitions start partitions on odd-numbered sectors
I don't get this. If you mean partitions defined by the classic DOS
partition table format, then AFAICS, such a partition can start in any
sector.
>so presuming you have odd-aligned disks, life is good.
What is an odd-aligned disk?
-
T
On 12/03/07, Tejun Heo <[EMAIL PROTECTED]> wrote:
Thomas Gleixner wrote:
> On Tue, 2007-03-13 at 01:37 +0900, Tejun Heo wrote:
>> Michal Piotrowski wrote:
>>> Calling initcall 0xc19154d8: piix_ide_init+0x0/0xbb()
>>> Calling initcall 0xc19155b6: generic_ide_init+0x0/0x16()
>>> Calling initcall 0x
Tejun Heo wrote:
> Hello,
>
> James Clark wrote:
>> I have an Adaptec 1220SA which I originally thought was just a re-badged
>> Sil3132 design. Externally it appears that way (the stamp on the chip
>> reads 3132), however it identifies as a Silicon Image type 0x0242
>> according to lspci. sata_si
On Sat, 10 Mar 2007 16:40:59 +
Alan Cox <[EMAIL PROTECTED]> wrote:
> Instead merge the one that fixe the non PCI
> crashes and we might get further.
In bugzilla #7907 you could post your patch and see if the reporters there
can at least confirm that it fixes their problem.
Meanwhile, to solv
Thomas Gleixner wrote:
> On Mon, 2007-03-12 at 17:31 +0100, Michal Piotrowski wrote:
>> Calling initcall 0xc19154d8: piix_ide_init+0x0/0xbb()
>> Calling initcall 0xc19155b6: generic_ide_init+0x0/0x16()
>> Calling initcall 0xc191572e: ide_init+0x0/0x81()
>> Uniform Multi-Platform E-IDE driver Revisi
Thomas Gleixner wrote:
> On Tue, 2007-03-13 at 01:37 +0900, Tejun Heo wrote:
>> Michal Piotrowski wrote:
>>> Calling initcall 0xc19154d8: piix_ide_init+0x0/0xbb()
>>> Calling initcall 0xc19155b6: generic_ide_init+0x0/0x16()
>>> Calling initcall 0xc191572e: ide_init+0x0/0x81()
>>> Uniform Multi-Plat
On Mon, 2007-03-12 at 17:31 +0100, Michal Piotrowski wrote:
> Calling initcall 0xc19154d8: piix_ide_init+0x0/0xbb()
> Calling initcall 0xc19155b6: generic_ide_init+0x0/0x16()
> Calling initcall 0xc191572e: ide_init+0x0/0x81()
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assumin
On Tue, 2007-03-13 at 01:37 +0900, Tejun Heo wrote:
> Michal Piotrowski wrote:
> > Calling initcall 0xc19154d8: piix_ide_init+0x0/0xbb()
> > Calling initcall 0xc19155b6: generic_ide_init+0x0/0x16()
> > Calling initcall 0xc191572e: ide_init+0x0/0x81()
> > Uniform Multi-Platform E-IDE driver Revision
Michal Piotrowski wrote:
> Calling initcall 0xc19154d8: piix_ide_init+0x0/0xbb()
> Calling initcall 0xc19155b6: generic_ide_init+0x0/0x16()
> Calling initcall 0xc191572e: ide_init+0x0/0x81()
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO mo
Hi,
Tejun Heo napisał(a):
> Michal Piotrowski wrote:
>> Hi Jeff,
>>
>> I've got some problems with my SATA controller on crashdump kernel.
>>
>> Calling initcall 0xc1916081: fc_transport_init+0x0/0x35()
>> Calling initcall 0xc19160b6: init_sd+0x0/0xbc()
>> Calling initcall 0xc19161ec: piix_init+0x
> "Doug" == Douglas Gilbert <[EMAIL PROTECTED]> writes:
Doug> SAT is now a standard and an agenda item for SAT-2 is to wire
Doug> ATA8-ACS's large sector size support to the additions to SBC-3
Doug> mentioned above.
Doug> I'm not sure how this stuff plays with end to end data
Doug> protection
> It sounds like your tree is out-of-date. Your patch to fix that went in
> days ago, applied by Linus directly:
Its purposefully not tracking every Linus update so I can build a
replicable environment. I missed the list mail it went in tho.
> I lean towards disabling it by default in 2.6.21 an
Ric Wheeler wrote:
> Alan Cox wrote:
>>> First generation of 1K sector drives will continue to use the same
>>> 512-byte ATA sector size you are familiar with. A single 512-byte
>>> write will cause the drive to perform a read-modify-write cycle.
>>> This configuration is physical 1K sector, logi
Alan Cox wrote:
I think it might be better to give up ACPI support in 2.6.21 and target
2.6.22. What do you think?
I removed it from my tree already so that I can actually use libata and
do real work. The "crash every non PCI controller" feature in the current
ACPI hacks means PCMCIA and ISAPn
On Mon, Mar 12, 2007 at 10:45:16AM -0400, Jeff Garzik wrote:
> Christoph Hellwig wrote:
> >the occasional 2k sector SCSI MO device aswell. It would be nice to
> >get samples of large sector size ATA devices into the hands of developers
> >to do real world testing of the whole stack.
>
> "hands of
Vitaliyi wrote:
Good Day
Say i want to implement extended set of ATA commands available to
userspace for building diagnostic tools.
I need 0x40 -- read verify and 0x32 -- write long with error handling,
for example. I was trying ide driver through ioctl's, but seems it
lack of functionality and
Christoph Hellwig wrote:
the occasional 2k sector SCSI MO device aswell. It would be nice to
get samples of large sector size ATA devices into the hands of developers
to do real world testing of the whole stack.
"hands of developers" meaning you specifically? :)
I've had a 512b-logical/1K-ph
> I think it might be better to give up ACPI support in 2.6.21 and target
> 2.6.22. What do you think?
I removed it from my tree already so that I can actually use libata and
do real work. The "crash every non PCI controller" feature in the current
ACPI hacks means PCMCIA and ISAPnP do not work a
Jan Engelhardt wrote:
On Mar 11 2007 22:45, Ric Wheeler wrote:
Jan Engelhardt wrote:
On Mar 11 2007 18:51, Ric Wheeler wrote:
During the recent IO/FS workshop, we spoke briefly about the
coming change to a 4k sector size for disks on linux. If I
recall correctly, the general feeling was that
> For 1K/4K logical sector sizes, who knows. EFI?
> Certainly seems incompatible with the current popular DOS partition format.
Its a bit messier than that. There are two interpretations of "DOS"
partition formats found on 2K sector size magneto opticals. One is that
everything is the same as b
On Mon, 2007-03-12 at 08:18 +, Christoph Hellwig wrote:
> The FS stack and higher levels of the I/O stack should be mostly ready.
> The S/390 DASDs are commonly used with 4k sector sizes, and we've had
> the occasional 2k sector SCSI MO device aswell. It would be nice to
> get samples of large
Jan Engelhardt wrote:
On Mar 11 2007 18:51, Ric Wheeler wrote:
During the recent IO/FS workshop, we spoke briefly about the
coming change to a 4k sector size for disks on linux. If I
recall correctly, the general feeling was that the impact was
not significant since we already do most file syste
Hello, all.
Currently, libata-acpi has the following problems.
1. Matching controller/device to ACPI node. It currently uses ap->cbl
== ATA_CBL_SATA test to choose between two formats - the traditional ATA
nodes with master/slave devices and new native SATA nodes. This is
incorrect as ata_piix
Alan Cox wrote:
First generation of 1K sector drives will continue to use the same
512-byte ATA sector size you are familiar with. A single 512-byte write
will cause the drive to perform a read-modify-write cycle. This
configuration is physical 1K sector, logical 512b sector.
The problem ca
Tejun Heo wrote:
[libata]
And, as the device requires custom high level driver, libata fails
miserably. Would it be worth to try support these devices? Or are
they just too outdated to put the effort in?
What SCSI peripheral device type does it report, when booted under libata?
Jeff
Tejun Heo wrote:
Hello,
James Clark wrote:
sata_sil24 :04:00.0: version 0.3
ACPI: PCI Interrupt :04:00.0[A] -> GSI 32 (level, low) -> IRQ 32
PCI: Setting latency timer of device :04:00.0 to 64
ata3: SATA max UDMA/100 cmd 0xC20012378000 ctl 0x0 bmdma 0x0 irq 32
ata4: SATA max
Alan Cox wrote:
First generation of 1K sector drives will continue to use the same
512-byte ATA sector size you are familiar with. A single 512-byte write
will cause the drive to perform a read-modify-write cycle. This
configuration is physical 1K sector, logical 512b sector.
The problem ca
Hello.
Tejun Heo wrote:
Stanislav Brabec reported that IOMEGA IDE ZIP drive doesn't work with
recent kernels. Low level driver is via82cxxx. Relevant part of
2.6.20.1 boot message follows.
VP_IDE: IDE controller at PCI slot :00:11.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native
Hello.
Bartlomiej Zolnierkiewicz wrote:
[PATCH] siimage: fix wrong ->swdma_mask
This driver doesn't support SWDMA so use the correct ->swdma_mask.
While at it:
* no need to call config_chipset_for_pio() in config_chipset_for_dma(),
if DMA is not available config_chipset_for_pio() will
Bartlomiej Zolnierkiewicz wrote:
Hello.
Bartlomiej Zolnierkiewicz wrote:
[PATCH] sl82c105: add ->speedproc support
* add sl82c105_tunepio() wrapper for sl82c105_tune_drive()
(just to get the error value)
* add sl82c105_tune_chipset() (->speedproc method) for setting
transfer mode
Berck E. Nash wrote:
> Tejun Heo wrote:
>> Hello, Berck.
>>
>> Berck E. Nash wrote:
>>> Tejun Heo wrote:
Berck E. Nash wrote:
> Testing the new libata ICH PATA drivers. There's one PATA port on this
> chip, and I've got two optical drives connected to it. The master drive
> fails
Hello, all.
Stanislav Brabec reported that IOMEGA IDE ZIP drive doesn't work with
recent kernels. Low level driver is via82cxxx. Relevant part of
2.6.20.1 boot message follows.
VP_IDE: IDE controller at PCI slot :00:11.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe
Tejun Heo wrote:
> Hello, Berck.
>
> Berck E. Nash wrote:
>> Tejun Heo wrote:
>>> Berck E. Nash wrote:
Testing the new libata ICH PATA drivers. There's one PATA port on this
chip, and I've got two optical drives connected to it. The master drive
fails to detect. The slave detects
Mathieu Bérard wrote:
> Jeff Garzik a écrit :
>> Adrian Bunk wrote:
>>> Subject: NCQ problem with ahci and Hitachi drive
>>> References : http://lkml.org/lkml/2007/3/4/178
>>> Submitter : Mathieu Bérard <[EMAIL PROTECTED]>
>>> Status : unknown
>> according to the last message in that threa
> First generation of 1K sector drives will continue to use the same
> 512-byte ATA sector size you are familiar with. A single 512-byte write
> will cause the drive to perform a read-modify-write cycle. This
> configuration is physical 1K sector, logical 512b sector.
The problem case is "rea
> Now, if this disk was copied byte per byte (/bin/dd) to a
> 4096-based disk, and Linux would start using a sector size of
> 4096, then I would suddenly have
The ATA drives I'm aware of report 512 byte sector size, do 512 byte
I/O's but use 4K physical sectors and to get sane performance except t
> 1. I think these ports should be made dummy instead of returning
> -ENOENT on prereset(). -ENOENT from prereset() was a hack to keep
> ata_piix's behavior unchanged while converting it to new EH. If no
> one objcts, I'll convert similar usages to use dummy ports after new
> init model and drop
Hello,
James Clark wrote:
> I have an Adaptec 1220SA which I originally thought was just a re-badged
> Sil3132 design. Externally it appears that way (the stamp on the chip
> reads 3132), however it identifies as a Silicon Image type 0x0242
> according to lspci. sata_sil24 does not attach.
>
> I
Hello,
> > That sounds a quite expensive solution ;)
>
> You should be able to just move the drive attached at ata1 to ata2.
> Please report whether that works.
I'll try to find an unused disk... As I said, these ports are part of
Asus EZRaid solution, and i'd prefer this piece of code not to tr
HI
For i386 it works (2.6.20.2).
(hotswap has bug,
disk has to first be inserted (nothing happens), then removed and
insterted again
then it's recognized)
However for amd64 (2.6.20.2) on the same hardware it doesn't work.
During boot the ata* messages appear on the ata4 controller where
the disk
Mikael Pettersson wrote:
> This patch changes sata_promise so that the PATA ports
> on TX2plus chips are bound to the pdc_pata_ops structure.
> This means that operations called from the SATA ops
> structures don't need any SATA-vs-PATA tests any more.
> Instead, operations that depend on a port be
Michal Piotrowski wrote:
> Hi Jeff,
>
> I've got some problems with my SATA controller on crashdump kernel.
>
> Calling initcall 0xc1916081: fc_transport_init+0x0/0x35()
> Calling initcall 0xc19160b6: init_sd+0x0/0xbc()
> Calling initcall 0xc19161ec: piix_init+0x0/0x27()
> ata_piix :00:1f.2:
->prereset() returns -ENOENT to tell libata that the port is empty and
reset sequencing should be stopped. This is not an error condition.
Update ata_eh_reset() such that it sets device classes to ATA_DEV_NONE
and return success in on -ENOENT. This makes spurious error message
go away.
Signed-of
On Sun, Mar 11, 2007 at 06:51:53PM -0400, Ric Wheeler wrote:
>
> During the recent IO/FS workshop, we spoke briefly about the coming
> change to a 4k sector size for disks on linux. If I recall correctly,
> the general feeling was that the impact was not significant since we
> already do most f
Paul Rolland wrote:
>> I keep forgetting about this. I'll ask SIMG how to deal with
>> this. For
>> the time being, connecting a device to the PMP port should remove the
>> timeouts.
>
> That sounds a quite expensive solution ;)
You should be able to just move the drive attached at ata1 to ata
Hello,
> It involves a long timeout, so it's bothersome. This is caused by
> Silicon Image 4726/3726 storage processor (SATA Port Multiplier with
> extra features) attached to one of the ICH ports.
Yes, I think this is the part Asus is using for it's EZ-Raid feature
on this motherboard, and they
80 matches
Mail list logo
