Welp, this is the n-dozenth time that the ATA driver has wedged large parts
of my entire system because it feels it needs to reset my CD-R when I'm
trying to start burning a CD. I get the good old
acd0: WRITE_BIG command timeout - resetting
ata3: resetting devices ..
and then, like always,
It seems Brian F. Feldman wrote:
Welp, this is the n-dozenth time that the ATA driver has wedged large parts
of my entire system because it feels it needs to reset my CD-R when I'm
trying to start burning a CD. I get the good old
acd0: WRITE_BIG command timeout - resetting
ata3:
Welp, this is the n-dozenth time that the ATA driver has
wedged large parts
of my entire system because it feels it needs to reset my
CD-R when I'm
trying to start burning a CD. I get the good old
acd0: WRITE_BIG command timeout - resetting
ata3: resetting devices ..
I don't
Greetings:
If the formatting of this msg is mucked, I apologize -- this is the only mailer
available to me at the moment (ISP problems, and I'm not going to email from work).
Welp, this is the n-dozenth time that the ATA driver has
wedged large parts
of my entire system because it
On 16-May-01 (15:14:50/GMT) Phil Knaack wrote:
on udma controller. take a look at sysctl hw.atamodes (may look
like 'dma,---,---,dma') and try change it to PIO mode.
I noticed a few days ago that a new command was added to -current,
called atacontrol. This command provides a real handy
In article [EMAIL PROTECTED],
Riccardo Torrini [EMAIL PROTECTED] wrote:
Maybe I am missing some important information, but on my -CURRENT
box (FreeBSD 5.0-CURRENT #17: Sat Apr 28 03:30:53 CEST 2001) I'm
unable to find hw.atamodes :-(
It has been replaced by the atacontrol(8) command.
PS:
In the last episode (May 16), John Polstra said:
PS: It is safer a world this days? I wouldn't like to loose all
files and rest only with lost+found as on HEADS-UP of same days
ago...
Actually, I found that to be a very cleansing experience. ;-)
Me too; I would probably have
