The problem turned out to be that disconnect was not enabled on my scsi
adapter. Everything works perfectly now. Thanks for replying.
Casey
On Saturday 11 January 2003 15:28, Casey Scott wrote:
I am using kernel 2.5.56 currently, and cdrecord is behaving strangely.
For example, when
From: Casey Scott [EMAIL PROTECTED]
Well... it seems to be fixed Out of sheer desperation, I took the
drive= =20
out and cleaned the laser with Qtip and Windex. Now the thing runs
awesome= =20
again. I don't know if the cleaning fixed it coincidently, or if the
lense= =20
13, 2003 at 11:57:54AM -0800, Casey Scott wrote:
Any idea why that happens? It used to work w/o any trouble. The
only thing that changed is that the drive that held the data being burned
was IDE, and now all the drives are scsi. Everything seems fine on the
bus. No errors from debugging
Well... it seems to be fixed Out of sheer desperation, I took the drive
out and cleaned the laser with Qtip and Windex. Now the thing runs awesome
again. I don't know if the cleaning fixed it coincidently, or if the lense
was just dirty. Either way, its working great. Thanks for everyones
I previously wrote in about a problem with cdrecord freezing my
system with a particular kernel. The problem has been narrowed down more,
and exists in any kernel I build. The system is all scsi, and the writer
is a Yamaha 4416S. While watching top, noticed a child process of cdrecord
and the burned is 50 pin scsi on an adaptec 2940u2w
Casey
On Mon, 13 Jan 2003, Joerg Schilling wrote:
From: Casey Scott [EMAIL PROTECTED]
I previously wrote in about a problem with cdrecord freezing my
system with a particular kernel. The problem has been narrowed down more
6 matches
Mail list logo
