On Feb 18, 1:46am, Raphael Becker wrote:
> Subject: TEAC CD-R55S =3D?iso-8859-1?Q?doesn=3DB4t?=3D work
>
> [ text/plain
> Encoded with "quoted-printable" ]:
>
> Hi *
>
> I have some preoblems with my new CD-R (it never works and I don=B4t
> have Win9$ to check out if this a Linux-Problem or a
> SCSI/hardware-failure).
>
> I use cdrecord to roast CDs (I tried to use it).
> Some facts about my machine:
> CPU: K6-2 300
> RAM: 96 MB
> SCSI: (Read the attached files scsi_*.txt.gz)
> Adaptec 2940AU <=3D=3D>ZIP100(int)<=3D=3D>TEAC CD-R<=3D=3D>Pioneer
> 32x<=3D=3D>Micropolis9.1
> Controller and HDD terminated.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> What I tried: I tried to burn an image, I built with xcdroast -->
> Master (but I think that makes no sense). After some output (see
> attached cdrecord-error.txt.gz) I get this error:
>
> [...]
> Waiting for reader process to fill input-buffer ... input-buffer
> ready.
> Judging disk...done.
> Calibrating laser...done.
> cdrecord: Cannot allocate memory. Cannot send SCSI cmd via ioctl
I have the same model of cdr and it is working fine for me with XCD-Roast=
=2E
(Under 2.0.36 and 2.2.1.)
I seriously doubt if it is a kernel issue.
A couple of recomendations:
First, get the zip drive out of the scsi chain. The zip scsi drives I ha=
ve
seen are 25 pin and cause all sorts of havok on the scsi chain. You may =
have
some sort of odd cabling issue.
Second, what version of the kernel are you using? Hard to debug without
knowing what you are even using.
Third, why did you not set the vendor specific extensions? It might be
expecting them for that card.
Fourth, what scsi-ids are you using? ("SCSI is voodoo -- you have to kno=
w
where to stick the pins.")
This should probably be handled off-list. I am willing to help out, but =
I need
more info.
> ^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^
> [1] [2]
> [1] cdrecord reserved the default amount of memory while in progress,
> I watched to a "top" while loading it.
>
> [2] Is this just an error becausee of [1] or do I have a problem with
> my SCSI-System? I think not that there=B4s a general SCSI-problem
> because copiing a large file (>600M) from disk to /dev/null brings me
> 7.5 MB/s thats a lot for my old Micropolis I think.
>
> Another thing: This CD-R is able to read CD=B4s with 8.1x speed
> (tested by "time cp /dev/scd1 /dev/null" on a very scratched ~610MB
> CD-R)
>
> Laser should be ok, SCSI-Interface too
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> My Kernel Setup is like that:
>
> <*> SCSI disk support
> < > SCSI tape support
> <*> SCSI CD-ROM support
> [ ] Enable vendor-specific extensions (for SCSI CDROM)
Why is this not set?
> <*> SCSI generic support
> --- Some SCSI devices (e.g. CD jukebox) support multiple LUNs
> [ ] Probe all LUNs on each SCSI device
> [*] Verbose SCSI error reporting (kernel size +=3D12K)
> [ ] SCSI logging facility
-- =
Alan Olsen "Carpe Aptenodytes!"
alano@ncd.com
--PART-BOUNDARY=.19902171714.ZM20689.pcx.ncd.com--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/