Hi, and sorry if this turns out to be a known issue. Actually, I'll be
thrilled if this turns out to be a known issue. But I've searched on it
forever, and although I've found some information, I've not found a
definite fix. Possibly my fault, but this is driving me nuts.
System: Asus P5N32E
conf to the kernel boot options, as well
as libata noacpi=1 to modules.conf, but now I've just had the problem
again. I'm now thinking I should try eliminating the Plextor drive. It
may be that it's the PATA drive that is causing all the trouble. I'll
report if so.
FYI, here
Tejun Heo wrote:
Hello,
rgheck wrote:
Hi, and sorry if this turns out to be a known issue. Actually, I'll be
thrilled if this turns out to be a known issue. But I've searched on it
forever, and although I've found some information, I've not found a
definite fix. Possibl
: configured for MWDMA2
ata7: EH complete
The sorts of errors I get when using the drive I've posted before.
They're intermittent and so can be hard to capture, but I can try to
post them again, too.
Richard
rgheck wrote:
Hi, and sorry if this turns out to be a known issue. Actuall
Tejun Heo wrote:
Hello,
Jim MacBaine wrote:
A co-worker, to whom I explained my problem, asked me whether I had
properly grounded my drives. In fact I had not: The drives resided in
a vibration-absorbing frame through which their exterior had no
electrical contact with the grounded case. Sin
Alan Cox wrote:
not one problem but lots---is sufficiently widespread that a Mini HOWTO,
say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil down to
- sata_nv with >4GB of RAM, knowing bein
Mark Lord wrote:
Gene Heskett wrote:
..
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx'
number when dmesg says its found ok at ata2.00? I've turned on an
option that says something about using the bios for device access
this build, but I'll be surprised if that's it. :)
Alan Cox wrote:
Is this >4GB or >=4GB? I've seen contradictory reports, and I've got 4GB.
Depends how the memory is mapped. Any memory physically above the 4GB
boundary
Don't know. Is there an easy way to find out?
By the way, and on a totally different subject. I wonder if thi
Well, it looks as if my problems weren't solved after all. I took out a
Plextor PX-W4012TA and re-installed me cherished Plextor PX-W1610A---the
latter burns at 1X, which produces glorious sounding CDs. Anyway, with
this change, my problems have re-appeared. See the dmesg excerpt below.
The s
Mark Lord wrote:
rgheck wrote:
Alan Cox wrote:
not one problem but lots---is sufficiently widespread that a Mini
HOWTO, say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part bo
Gene,
If you still want to try it, I did manage to get the old IDE subsystem
working. The issue with pata_amd concerns modprobe.conf. You probably
have an alias to it there, as Fedora seems to insert these. (I don't
know if they're actually needed or not.) If you comment out that line,
then
11 matches
Mail list logo
