On Tue, 13 Mar 2007 13:13:12 +0100 (CET)
[EMAIL PROTECTED] wrote:
> Hi,
> I reported this also for 2.6.20 kernel.
> new libata with controller nVidia CK804 initializes the disk in DMA/33,
> with with 2.6.19.5 and previous the disk is correctly inizialized in
> DMA/100.
> Tha cable is OK, and
[EMAIL PROTECTED] wrote:
> Hi,
> I reported this also for 2.6.20 kernel.
> new libata with controller nVidia CK804 initializes the disk in DMA/33,
> with with 2.6.19.5 and previous the disk is correctly inizialized in
> DMA/100.
> Tha cable is OK, and with older kernels the disks runs without
Hi,
I reported this also for 2.6.20 kernel.
new libata with controller nVidia CK804 initializes the disk in DMA/33,
with with 2.6.19.5 and previous the disk is correctly inizialized in
DMA/100.
Tha cable is OK, and with older kernels the disks runs without troubles.
The sistem has two sata
Hi,
I reported this also for 2.6.20 kernel.
new libata with controller nVidia CK804 initializes the disk in DMA/33,
with with 2.6.19.5 and previous the disk is correctly inizialized in
DMA/100.
Tha cable is OK, and with older kernels the disks runs without troubles.
The sistem has two sata
[EMAIL PROTECTED] wrote:
Hi,
I reported this also for 2.6.20 kernel.
new libata with controller nVidia CK804 initializes the disk in DMA/33,
with with 2.6.19.5 and previous the disk is correctly inizialized in
DMA/100.
Tha cable is OK, and with older kernels the disks runs without troubles.
On Tue, 13 Mar 2007 13:13:12 +0100 (CET)
[EMAIL PROTECTED] wrote:
Hi,
I reported this also for 2.6.20 kernel.
new libata with controller nVidia CK804 initializes the disk in DMA/33,
with with 2.6.19.5 and previous the disk is correctly inizialized in
DMA/100.
Tha cable is OK, and with
6 matches
Mail list logo