--- "Guy T. Rice" [EMAIL PROTECTED] wrote:
On Fri, 07 Jul 2000, Thierry Vignaud wrote:
I don't think it's an eide driver bug : it's just
that the new driver stress
more hardware (if your eide hd and controller
reports to support udma, you
just want to use it).
Huh. According to
On Fri, 07 Jul 2000, Thierry Vignaud wrote:
I don't think it's an eide driver bug : it's just that the new driver stress
more hardware (if your eide hd and controller reports to support udma, you
just want to use it).
Huh. According to hdparm, it's not using dma at all.
/dev/hdb:
"Guy T. Rice" [EMAIL PROTECTED] writes:
I installed Mandrake 7.1 on several computers at work and everything
worked flawlessly. However, I installed it on my home computer, and
discovered a bug. My primary HD remains readable, but my second HD
(slave drive on the same IDE bus) becomes
For me, it's a hardware bug (hd or cable; eg, for
udma66, lots of read error
were due to bad cables ...)
No way!
The 2.2.17-*mdk rpms have IDE fucked up. On my machine
it hangs (lock keys don't switch lights) when it goes
to check the partition tables, with an UDMA time-out.
2.2.16-9mdk
Eugenio Diaz wrote:
For me, it's a hardware bug (hd or cable; eg, for
udma66, lots of read error
were due to bad cables ...)
No way!
The 2.2.17-*mdk rpms have IDE fucked up. On my machine
it hangs (lock keys don't switch lights) when it goes
to check the partition tables, with an
I installed Mandrake 7.1 on several computers at work and everything
worked flawlessly. However, I installed it on my home computer, and
discovered a bug. My primary HD remains readable, but my second HD
(slave drive on the same IDE bus) becomes unreadable. Actually, it
appears to read, but
