From: Abhishek Kaul <abhishek.kaul@wipro.com>
To: blinux-list@redhat.com
Subject: Re: cdrecord and Sony IDE Drives
Date: Mon, 21 Oct 2002 09:41:32 +0530 [thread overview]
Message-ID: <3DB37E74.7060508@wipro.com> (raw)
In-Reply-To: <200210210154.g9L1s7G80612@dc.cis.okstate.edu>
[-- Attachment #1: Type: text/plain, Size: 1983 bytes --]
want to unsubscribe from the list.
pls let me know whom to send the mail regarding this
regards,
abhi
Martin McCormick wrote:
> I upgraded to Linux3.0 this Summer and my ability to
>record CD's using SCSI emulation died on two different systems.
>On one system, I finally got it working with some help, but it
>does work again like it should. It turns out that you must
>enable SCSI emulation in your kernel which is no big surprise.
>You also must enable CDROM support even though your CDRW drive is
>an IDE drive, and you must also enable generic SCSI support.
>
> That fixed things for that system.
>
> My work station at my job location seems very similar in
>that it is a Dell Dimension series system only slightly newer
>than the one I got back to good health again. Its IDE drive is a
>Sony drive but is otherwise a normal IDE device. After I did the
>same three things to that system, it showed all the correct test
>results one can look for. If, for example, you type
>
>cat /proc/scsi/scsi, you will get a listing of all the SCSI
>devices you have. I see the CDRW drive and it also shows up
>properly in a second test one can run that will make your system
>output a little form which describes your CDRW drive and its
>capabilities.
>
> At this point, both systems behave the same way.
>
> The trouble comes any time I want to use cdrecord on the
>system with the Sony drive.
>
> Cdrecord starts out normally and then fails with an error
>saying that it can't find /dev/pg0. /dev/pg0 is the first
>parallel port SCSI device. I could certainly build a new kernel
>with parallel SCSI support, but is this really necessary? The
>CDRW drive connects to an IDE controller, not the Printer port.
>
> I am confused. That system does appear to be otherwise
>quite functional.
>
>Martin McCormick
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
>
>
[-- Attachment #2: Wipro_Disclaimer.txt --]
[-- Type: text/plain, Size: 522 bytes --]
**************************Disclaimer**************************************************
Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged'
and 'confidential' and intended for use only by the individual or entity to which it is
addressed. You are notified that any use, copying or dissemination of the information
contained in the E-MAIL in any manner whatsoever is strictly prohibited.
****************************************************************************************
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Martin McCormick
` Abhishek Kaul [this message]
` Willem van der Walt<vdwaltw@health.gov.za>
` Wojtek Pilorz
Martin McCormick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DB37E74.7060508@wipro.com \
--to=abhishek.kaul@wipro.com \
--cc=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).