From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from rwcrmhc53.attbi.com ([204.127.198.39]) by speech.braille.uwo.ca with esmtp (Exim 3.35 #1 (Debian)) id 174pEr-0002tO-00 for ; Mon, 06 May 2002 16:37:41 -0400 Received: from mycomputer ([24.62.33.141]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with SMTP id <20020506203713.BJWN5896.rwcrmhc53.attbi.com@mycomputer> for ; Mon, 6 May 2002 20:37:13 +0000 Message-ID: <001101c1f53d$a3311e80$02213e18@mycomputer> From: "Igor Gueths" To: References: <20020505195040.A190@uic.edu> <009b01c1f52f$c753a3e0$02213e18@mycomputer> <20020506144034.A324@uic.edu> <002001c1f538$f5e53ee0$02213e18@mycomputer> <20020506152213.B411@uic.edu> Subject: Re: cdrecord question Date: Mon, 6 May 2002 16:36:01 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: speakup-admin@braille.uwo.ca Errors-To: speakup-admin@braille.uwo.ca X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.0.8 Precedence: bulk Reply-To: speakup@braille.uwo.ca List-Help: List-Post: List-Subscribe: , List-Id: Speakup is a screen review system for Linux. List-Unsubscribe: , List-Archive: Hi Greg. You mean the kernel hardware detection messages? Where can I = find this output? Is it in /proc somewhere? I'll dig around for it. = Also, when I tried using /dev/sr0 cdrecord still reports a bad file = descriptor, even though the scsi emulation driver seems to have attached = it as /dev/sr0. I can still use the device with no problems by = specifying the coordinates, which is no big deal for me. I'm just = wondering because it might affect me sometime in the future. I just = don't know yet.=20 ----- Original Message -----=20 From: Gregory Nowak To: Sent: Monday, May 06, 2002 4:22 PM Subject: Re: cdrecord question > Yes, this is perfectly normal. To find out under what device name your = drive now is, just examine the dmesg output. > Greg >=20 >=20 > On Mon, May 06, 2002 at 04:02:32PM -0400, Igor Gueths wrote: > > Hi Greg. Well I got it to work, but it doesn't work under /dev/sr0. = It still says bad file descriptor, but I can specify the dev by using = 0,0,0 the device coordinates. However, when I am blanking a Cd, it just = sits on last chance to quit, starting real write in one seconds. Is this = normal to have it sit like that while blanking? I can hear the drive = working, so its obviously doing something. Just asking this because I = have never seen cdrecord working, so I'm not sure on the normal status = msgs. Thanks!=20 > > ----- Original Message -----=20 > > From: Gregory Nowak > > To: > > Sent: Monday, May 06, 2002 3:40 PM > > Subject: Re: cdrecord question > >=20 > >=20 > > > When I had a regular cd-rom drive in addition to my burner in this = box, I didn't do scsi-emulation on it, just on my burner. However, a = while back, Kerry said that the regular cdrom drive should also be = scsi-emulated. So, it's your call I guess. When I had the regular cd-rom = drive, the fact that it wasn't ide-scsi emulated didn't cause any = problems for me, although I gathered from Kerry's posts that that may = cause problems for others. > > > Greg > > >=20 > > >=20 > > > On Mon, May 06, 2002 at 02:56:48PM -0400, Igor Gueths wrote: > > > > Hi Greg. I don't have to make my regular Cdrom emulated right? I = can just compile in atapi_cdrom support, tell the regular ide driver not = to grab the burner, and leave the scsi cdrom support for the cd writer. = Is this setup sort of what you are refering to?=20 > > > > ----- Original Message -----=20 > > > > From: Gregory Nowak > > > > To: > > > > Sent: Sunday, May 05, 2002 8:50 PM > > > > Subject: Re: cdrecord question > > > >=20 > > > >=20 > > > > > Yes, your drive is ide/atapi, but you're emulating it as = ide-scsi. This means that even though your drive is ide/atapi, your = system now thinks that it is a scsi drive. So, you need both scsi cd-rom = support, and generic scsi. > > > > > Greg > > > > >=20 > > > > >=20 > > > > > On Sun, May 05, 2002 at 08:04:51PM -0400, Igor Gueths wrote: > > > > > > Hi. Ide_scsi=3Dy CONFIG_SCSI=3Dy. I don't see why I would = need Scsi Cdrom > > > > > > support, because both my Cdrom and Cdrw drives are both = ide/atapi. > > > > > > According to the Cd writing howto, I had to pass = hdd=3Dide-scsi to the scsi > > > > > > emulation driver. As a result, my Cd burner appears as a = device in > > > > > > /proc/scsi/scsi. However, cdrecord says that it can't open = scsi driver > > > > > > when I > > > > > > use /dev/sg0? I am currently only doing everything as root = for testing > > > > > > purposes, then I'll deal with the users once I get it = working. Also, does > > > > > > CONFIG_CHR_SG refer to generic scsi character devices, not = scsi Cdroms? > > > > > > Thanks! On Sun, 5 May 2002, Cheryl Homiak wrote: > > > > > >=20 > > > > > > > Hi Igor. > > > > > > > 1. Did you also make sure that your kernel has scsi = emulation, scsi, scsi cdrom, > > > > > > > and generic scsi compiled in? I think the standard kernel = with redhat has these > > > > > > > compiled in, but with debian you may have to recompile = your kernel. Don't know > > > > > > > about other distros? > > > > > > > 2. Check your permissions for sg0 or which ever generic = device matches. I don't > > > > > > > remember if this was a problem for cdrecord, but it was a = problem for some > > > > > > > programs that had me stumped for a while. If you can run = it as root but not as > > > > > > > you, this may be the problem. > > > > > > > 3. there are changes you have to make in order to run = cdrecord as a user instead > > > > > > > of root. I don't have them right at hand but the needed = changes are shown in the > > > > > > > cdrw howto. > > > > > > > > > > > > > > You should be able to find what to use for the device by = running cdrecord > > > > > > > -scanbus. For instance, when i use cdrecord, I do > > > > > > > dev=3D0,0,0 > > > > > > > as my cdrecorder is the first such device. > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > Speakup mailing list > > > > > > > Speakup@braille.uwo.ca > > > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > > > > > >=20 > > > > > >=20 > > > > > > _______________________________________________ > > > > > > Speakup mailing list > > > > > > Speakup@braille.uwo.ca > > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > >=20 > > > > > _______________________________________________ > > > > > Speakup mailing list > > > > > Speakup@braille.uwo.ca > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > >=20 > > > >=20 > > > > _______________________________________________ > > > > Speakup mailing list > > > > Speakup@braille.uwo.ca > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > >=20 > > > _______________________________________________ > > > Speakup mailing list > > > Speakup@braille.uwo.ca > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > >=20 > >=20 > > _______________________________________________ > > Speakup mailing list > > Speakup@braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup >=20 > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup