* cdrecord question @ Igor Gueths ` Cheryl Homiak 0 siblings, 1 reply; 32+ messages in thread From: Igor Gueths @ UTC (permalink / raw) To: speakup Hi all. I reconfigured lilo and passed the command append="hdd=ide-scsi" to the kernel so that my Cd writer wouldn't be recognized by the regular Ide driver. When I did cdrecord -scanbus, it said that it couldn't open the scsi driver, no such file or directory. Is this normal since the driver is just an emulation driver, or is there something else wrong that I have to tackle? I have both hdd, scd, and sg-type devices present in my /dev. Thanks! ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question cdrecord question Igor Gueths @ ` Cheryl Homiak ` Igor Gueths 0 siblings, 1 reply; 32+ messages in thread From: Cheryl Homiak @ UTC (permalink / raw) To: speakup 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=0,0,0 as my cdrecorder is the first such device. ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Cheryl Homiak @ ` Igor Gueths ` Gregory Nowak ` Cheryl Homiak 0 siblings, 2 replies; 32+ messages in thread From: Igor Gueths @ UTC (permalink / raw) To: speakup Hi. Ide_scsi=y CONFIG_SCSI=y. 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=ide-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: > 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=0,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 > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Igor Gueths @ ` Gregory Nowak ` Igor Gueths ` Cheryl Homiak 1 sibling, 1 reply; 32+ messages in thread From: Gregory Nowak @ UTC (permalink / raw) To: speakup 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 On Sun, May 05, 2002 at 08:04:51PM -0400, Igor Gueths wrote: > Hi. Ide_scsi=y CONFIG_SCSI=y. 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=ide-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: > > > 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=0,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 > > > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Gregory Nowak @ ` Igor Gueths ` Gregory Nowak 0 siblings, 1 reply; 32+ messages in thread From: Igor Gueths @ UTC (permalink / raw) To: speakup 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? ----- Original Message ----- From: Gregory Nowak <gnowak1@uic.edu> To: <speakup@braille.uwo.ca> Sent: Sunday, May 05, 2002 8:50 PM Subject: Re: cdrecord question > 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 > > > On Sun, May 05, 2002 at 08:04:51PM -0400, Igor Gueths wrote: > > Hi. Ide_scsi=y CONFIG_SCSI=y. 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=ide-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: > > > > > 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=0,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 > > > > > > > > > _______________________________________________ > > Speakup mailing list > > Speakup@braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Igor Gueths @ ` Gregory Nowak ` Cheryl Homiak ` Igor Gueths 0 siblings, 2 replies; 32+ messages in thread From: Gregory Nowak @ UTC (permalink / raw) To: speakup 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 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? > ----- Original Message ----- > From: Gregory Nowak <gnowak1@uic.edu> > To: <speakup@braille.uwo.ca> > Sent: Sunday, May 05, 2002 8:50 PM > Subject: Re: cdrecord question > > > > 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 > > > > > > On Sun, May 05, 2002 at 08:04:51PM -0400, Igor Gueths wrote: > > > Hi. Ide_scsi=y CONFIG_SCSI=y. 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=ide-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: > > > > > > > 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=0,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 > > > > > > > > > > > > > _______________________________________________ > > > Speakup mailing list > > > Speakup@braille.uwo.ca > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > _______________________________________________ > > Speakup mailing list > > Speakup@braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Gregory Nowak @ ` Cheryl Homiak ` Igor Gueths ` Gregory Nowak ` Igor Gueths 1 sibling, 2 replies; 32+ messages in thread From: Cheryl Homiak @ UTC (permalink / raw) To: speakup Hi greg and Igor. Maybe there are advantages to leaving your cdrom ide/atapi, but i just went ahead and changed both of mine. That meant i didn't even have ide/atapi cdrom support compiled in and I didn't have to question whether the ide/atapi driver was interfering with the scsi. But whether you use just scsi or use both, you still definitely do have to have scsi cdrom suport, as well as scsi, scsi emulation, and generic scsi enabled. From what you say in past posts, Igor, you may have thought you could leave scsi cdrom support out. I just think it's simpler not to have to deal with both drivers unless you have a really good reason for keeping the ide/atapi for your cdrom. ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Cheryl Homiak @ ` Igor Gueths ` Cheryl Homiak ` Gregory Nowak 1 sibling, 1 reply; 32+ messages in thread From: Igor Gueths @ UTC (permalink / raw) To: speakup Hi Cheryl. Well I suppose I could change the Cdrom as well, but the atapi driver doesn't interfere with the Cdrw because I tell it not to. I might change it at some point in the future though. ----- Original Message ----- From: Cheryl Homiak <chomiak@chartermi.net> To: <speakup@braille.uwo.ca> Sent: Monday, May 06, 2002 4:01 PM Subject: Re: cdrecord question > Hi greg and Igor. > Maybe there are advantages to leaving your cdrom ide/atapi, but i just went > ahead and changed both of mine. That meant i didn't even have ide/atapi cdrom > support compiled in and I didn't have to question whether the ide/atapi driver > was interfering with the scsi. But whether you use just scsi or use both, you > still definitely do have to have scsi cdrom suport, as well as scsi, scsi > emulation, and generic scsi enabled. From what you say in past posts, Igor, you > may have thought you could leave scsi cdrom support out. > I just think it's simpler not to have to deal with both drivers unless you have > a really good reason for keeping the ide/atapi for your cdrom. > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Igor Gueths @ ` Cheryl Homiak 0 siblings, 0 replies; 32+ messages in thread From: Cheryl Homiak @ UTC (permalink / raw) To: speakup Well, it sounds like your cdrw is working now anyway, and that's the main thing. If it ain't broke, don't fix it! ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Cheryl Homiak ` Igor Gueths @ ` Gregory Nowak 1 sibling, 0 replies; 32+ messages in thread From: Gregory Nowak @ UTC (permalink / raw) To: speakup Once you use the correct append line in lilo.conf, you can stop wondering if the ide/atapi driver is in the way of the scsi driver. Greg On Mon, May 06, 2002 at 03:01:36PM -0500, Cheryl Homiak wrote: > Hi greg and Igor. > Maybe there are advantages to leaving your cdrom ide/atapi, but i just went > ahead and changed both of mine. That meant i didn't even have ide/atapi cdrom > support compiled in and I didn't have to question whether the ide/atapi driver > was interfering with the scsi. But whether you use just scsi or use both, you > still definitely do have to have scsi cdrom suport, as well as scsi, scsi > emulation, and generic scsi enabled. From what you say in past posts, Igor, you > may have thought you could leave scsi cdrom support out. > I just think it's simpler not to have to deal with both drivers unless you have > a really good reason for keeping the ide/atapi for your cdrom. > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Gregory Nowak ` Cheryl Homiak @ ` Igor Gueths ` Gregory Nowak 1 sibling, 1 reply; 32+ messages in thread From: Igor Gueths @ UTC (permalink / raw) To: speakup 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! ----- Original Message ----- From: Gregory Nowak <gnowak1@uic.edu> To: <speakup@braille.uwo.ca> Sent: Monday, May 06, 2002 3:40 PM Subject: Re: cdrecord question > 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 > > > 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? > > ----- Original Message ----- > > From: Gregory Nowak <gnowak1@uic.edu> > > To: <speakup@braille.uwo.ca> > > Sent: Sunday, May 05, 2002 8:50 PM > > Subject: Re: cdrecord question > > > > > > > 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 > > > > > > > > > On Sun, May 05, 2002 at 08:04:51PM -0400, Igor Gueths wrote: > > > > Hi. Ide_scsi=y CONFIG_SCSI=y. 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=ide-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: > > > > > > > > > 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=0,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 > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Speakup mailing list > > > > Speakup@braille.uwo.ca > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > _______________________________________________ > > > Speakup mailing list > > > Speakup@braille.uwo.ca > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > _______________________________________________ > > Speakup mailing list > > Speakup@braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Igor Gueths @ ` Gregory Nowak ` Igor Gueths 0 siblings, 1 reply; 32+ messages in thread From: Gregory Nowak @ UTC (permalink / raw) To: speakup Yes, this is perfectly normal. To find out under what device name your drive now is, just examine the dmesg output. Greg 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! > ----- Original Message ----- > From: Gregory Nowak <gnowak1@uic.edu> > To: <speakup@braille.uwo.ca> > Sent: Monday, May 06, 2002 3:40 PM > Subject: Re: cdrecord question > > > > 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 > > > > > > 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? > > > ----- Original Message ----- > > > From: Gregory Nowak <gnowak1@uic.edu> > > > To: <speakup@braille.uwo.ca> > > > Sent: Sunday, May 05, 2002 8:50 PM > > > Subject: Re: cdrecord question > > > > > > > > > > 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 > > > > > > > > > > > > On Sun, May 05, 2002 at 08:04:51PM -0400, Igor Gueths wrote: > > > > > Hi. Ide_scsi=y CONFIG_SCSI=y. 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=ide-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: > > > > > > > > > > > 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=0,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 > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Speakup mailing list > > > > > Speakup@braille.uwo.ca > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > _______________________________________________ > > > > Speakup mailing list > > > > Speakup@braille.uwo.ca > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > > _______________________________________________ > > > Speakup mailing list > > > Speakup@braille.uwo.ca > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > _______________________________________________ > > Speakup mailing list > > Speakup@braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Gregory Nowak @ ` Igor Gueths ` Raul A. Gallegos ` (2 more replies) 0 siblings, 3 replies; 32+ messages in thread From: Igor Gueths @ UTC (permalink / raw) To: speakup 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. ----- Original Message ----- From: Gregory Nowak <gnowak1@uic.edu> To: <speakup@braille.uwo.ca> 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 > > > 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! > > ----- Original Message ----- > > From: Gregory Nowak <gnowak1@uic.edu> > > To: <speakup@braille.uwo.ca> > > Sent: Monday, May 06, 2002 3:40 PM > > Subject: Re: cdrecord question > > > > > > > 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 > > > > > > > > > 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? > > > > ----- Original Message ----- > > > > From: Gregory Nowak <gnowak1@uic.edu> > > > > To: <speakup@braille.uwo.ca> > > > > Sent: Sunday, May 05, 2002 8:50 PM > > > > Subject: Re: cdrecord question > > > > > > > > > > > > > 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 > > > > > > > > > > > > > > > On Sun, May 05, 2002 at 08:04:51PM -0400, Igor Gueths wrote: > > > > > > Hi. Ide_scsi=y CONFIG_SCSI=y. 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=ide-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: > > > > > > > > > > > > > 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=0,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 > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Speakup mailing list > > > > > > Speakup@braille.uwo.ca > > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > > > _______________________________________________ > > > > > Speakup mailing list > > > > > Speakup@braille.uwo.ca > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > > > > > _______________________________________________ > > > > Speakup mailing list > > > > Speakup@braille.uwo.ca > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > _______________________________________________ > > > Speakup mailing list > > > Speakup@braille.uwo.ca > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > _______________________________________________ > > Speakup mailing list > > Speakup@braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Igor Gueths @ ` Raul A. Gallegos ` Igor Gueths ` Cheryl Homiak ` Gregory Nowak 2 siblings, 1 reply; 32+ messages in thread From: Raul A. Gallegos @ UTC (permalink / raw) To: speakup After your box boots up type $ dmesg |more ----- Original Message ----- From: "Igor Gueths" <igueths@attbi.com> To: <speakup@braille.uwo.ca> Sent: Monday, May 06, 2002 3:36 PM Subject: Re: cdrecord question 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. ----- Original Message ----- From: Gregory Nowak <gnowak1@uic.edu> To: <speakup@braille.uwo.ca> 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 > > > 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! > > ----- Original Message ----- > > From: Gregory Nowak <gnowak1@uic.edu> > > To: <speakup@braille.uwo.ca> > > Sent: Monday, May 06, 2002 3:40 PM > > Subject: Re: cdrecord question > > > > > > > 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 > > > > > > > > > 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? > > > > ----- Original Message ----- > > > > From: Gregory Nowak <gnowak1@uic.edu> > > > > To: <speakup@braille.uwo.ca> > > > > Sent: Sunday, May 05, 2002 8:50 PM > > > > Subject: Re: cdrecord question > > > > > > > > > > > > > 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 > > > > > > > > > > > > > > > On Sun, May 05, 2002 at 08:04:51PM -0400, Igor Gueths wrote: > > > > > > Hi. Ide_scsi=y CONFIG_SCSI=y. 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=ide-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: > > > > > > > > > > > > > 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=0,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 > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Speakup mailing list > > > > > > Speakup@braille.uwo.ca > > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > > > _______________________________________________ > > > > > Speakup mailing list > > > > > Speakup@braille.uwo.ca > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > > > > > _______________________________________________ > > > > Speakup mailing list > > > > Speakup@braille.uwo.ca > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > _______________________________________________ > > > Speakup mailing list > > > Speakup@braille.uwo.ca > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > _______________________________________________ > > Speakup mailing list > > Speakup@braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup _______________________________________________ Speakup mailing list Speakup@braille.uwo.ca http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Raul A. Gallegos @ ` Igor Gueths 0 siblings, 0 replies; 32+ messages in thread From: Igor Gueths @ UTC (permalink / raw) To: speakup Hi Raul. When I do demsg, it sayd cdrom: open failed. This is probably that there aren't any disks in either one of my Cd drives. Wonder if this is normal? ----- Original Message ----- From: Raul A. Gallegos <raul@asmodean.net> To: <speakup@braille.uwo.ca> Sent: Monday, May 06, 2002 4:43 PM Subject: Re: cdrecord question > After your box boots up type $ dmesg |more > > ----- Original Message ----- > From: "Igor Gueths" <igueths@attbi.com> > To: <speakup@braille.uwo.ca> > Sent: Monday, May 06, 2002 3:36 PM > Subject: Re: cdrecord question > > > 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. > ----- Original Message ----- > From: Gregory Nowak <gnowak1@uic.edu> > To: <speakup@braille.uwo.ca> > 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 > > > > > > 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! > > > ----- Original Message ----- > > > From: Gregory Nowak <gnowak1@uic.edu> > > > To: <speakup@braille.uwo.ca> > > > Sent: Monday, May 06, 2002 3:40 PM > > > Subject: Re: cdrecord question > > > > > > > > > > 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 > > > > > > > > > > > > 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? > > > > > ----- Original Message ----- > > > > > From: Gregory Nowak <gnowak1@uic.edu> > > > > > To: <speakup@braille.uwo.ca> > > > > > Sent: Sunday, May 05, 2002 8:50 PM > > > > > Subject: Re: cdrecord question > > > > > > > > > > > > > > > > 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 > > > > > > > > > > > > > > > > > > On Sun, May 05, 2002 at 08:04:51PM -0400, Igor Gueths wrote: > > > > > > > Hi. Ide_scsi=y CONFIG_SCSI=y. 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=ide-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: > > > > > > > > > > > > > > > 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=0,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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > Speakup mailing list > > > > > > > Speakup@braille.uwo.ca > > > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > > > > > _______________________________________________ > > > > > > Speakup mailing list > > > > > > Speakup@braille.uwo.ca > > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > > > > > > > > _______________________________________________ > > > > > Speakup mailing list > > > > > Speakup@braille.uwo.ca > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > _______________________________________________ > > > > Speakup mailing list > > > > Speakup@braille.uwo.ca > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > > _______________________________________________ > > > Speakup mailing list > > > Speakup@braille.uwo.ca > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > _______________________________________________ > > Speakup mailing list > > Speakup@braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Igor Gueths ` Raul A. Gallegos @ ` Cheryl Homiak ` Gregory Nowak ` Gregory Nowak 2 siblings, 1 reply; 32+ messages in thread From: Cheryl Homiak @ UTC (permalink / raw) To: speakup Hi igor and Greg. It was my understanding that the coordinates are what you are supposed to use anyway. In fact, I think I remember trying sr0 and maybe some others that didn't work. I think Greg is simply referring to the output of dmesg; type dmesg, though probably what you want would be more toward the end. If you do dmesg > dmesg.txt, then you can look at the file instead of going through the whole thing. ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Cheryl Homiak @ ` Gregory Nowak ` Cheryl Homiak 0 siblings, 1 reply; 32+ messages in thread From: Gregory Nowak @ UTC (permalink / raw) To: speakup Yes. If you're using cdrecord, you would use something like dev=0,0,0. If you are trying to mount a disk in the drive, you would use something like /dev/sr0. Greg On Mon, May 06, 2002 at 03:58:49PM -0500, Cheryl Homiak wrote: > Hi igor and Greg. > It was my understanding that the coordinates are what you are supposed to use > anyway. In fact, I think I remember trying sr0 and maybe some others that didn't > work. > I think Greg is simply referring to the output of dmesg; type dmesg, though > probably what you want would be more toward the end. If you do dmesg > > dmesg.txt, then you can look at the file instead of going through the whole > thing. > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Gregory Nowak @ ` Cheryl Homiak 0 siblings, 0 replies; 32+ messages in thread From: Cheryl Homiak @ UTC (permalink / raw) To: speakup On my system, /dev/sr0 isn't a real file anyway; it's just a link to /dev/scd0. I made a new directory, /cdrecord. I then did a symlink from /dev/scd0 to /dev/cdrecord. Then I added an entry to fstab: /dev/cdrecord /cdrecord iso9660 rw,user,noauto 2 2 and now I can mount my cdrw just with the command mount /cdrecord and this also means I can mount both my cdrom and cdrw at the same time if I want to do so for some reason. ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Igor Gueths ` Raul A. Gallegos ` Cheryl Homiak @ ` Gregory Nowak 2 siblings, 0 replies; 32+ messages in thread From: Gregory Nowak @ UTC (permalink / raw) To: speakup Yes, I mean the kernel output. You can view it by typing: "dmesg |more" without the quotes of course. Greg On Mon, May 06, 2002 at 04:36:01PM -0400, Igor Gueths wrote: > 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. > ----- Original Message ----- > From: Gregory Nowak <gnowak1@uic.edu> > To: <speakup@braille.uwo.ca> > 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 > > > > > > 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! > > > ----- Original Message ----- > > > From: Gregory Nowak <gnowak1@uic.edu> > > > To: <speakup@braille.uwo.ca> > > > Sent: Monday, May 06, 2002 3:40 PM > > > Subject: Re: cdrecord question > > > > > > > > > > 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 > > > > > > > > > > > > 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? > > > > > ----- Original Message ----- > > > > > From: Gregory Nowak <gnowak1@uic.edu> > > > > > To: <speakup@braille.uwo.ca> > > > > > Sent: Sunday, May 05, 2002 8:50 PM > > > > > Subject: Re: cdrecord question > > > > > > > > > > > > > > > > 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 > > > > > > > > > > > > > > > > > > On Sun, May 05, 2002 at 08:04:51PM -0400, Igor Gueths wrote: > > > > > > > Hi. Ide_scsi=y CONFIG_SCSI=y. 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=ide-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: > > > > > > > > > > > > > > > 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=0,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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > Speakup mailing list > > > > > > > Speakup@braille.uwo.ca > > > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > > > > > _______________________________________________ > > > > > > Speakup mailing list > > > > > > Speakup@braille.uwo.ca > > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > > > > > > > > _______________________________________________ > > > > > Speakup mailing list > > > > > Speakup@braille.uwo.ca > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > _______________________________________________ > > > > Speakup mailing list > > > > Speakup@braille.uwo.ca > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > > _______________________________________________ > > > Speakup mailing list > > > Speakup@braille.uwo.ca > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > _______________________________________________ > > Speakup mailing list > > Speakup@braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Igor Gueths ` Gregory Nowak @ ` Cheryl Homiak ` Cheryl Homiak ` Igor Gueths 1 sibling, 2 replies; 32+ messages in thread From: Cheryl Homiak @ UTC (permalink / raw) To: speakup Igor: did you ever report what cdrecord -scanbus is giving you? I didn't see it. ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Cheryl Homiak @ ` Cheryl Homiak ` Igor Gueths 1 sibling, 0 replies; 32+ messages in thread From: Cheryl Homiak @ UTC (permalink / raw) To: speakup If you look at the cd-writing howto, you will find that you must have scsi emulation, scsi, scsi cdrom and generic scsi enabled. I don't know if this howto is rewritten or if I'm confusing it with another howto, but it doesn't seem as straightforward as I thought i remembered it; has all this modular information included in it now and it's hard to find the straightforward information on what to do to your kernel but it is there. ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Cheryl Homiak ` Cheryl Homiak @ ` Igor Gueths ` Cheryl Homiak 1 sibling, 1 reply; 32+ messages in thread From: Igor Gueths @ UTC (permalink / raw) To: speakup Hi Cheryl. I did report it on an earlier post yesterday. ----- Original Message ----- From: Cheryl Homiak <chomiak@chartermi.net> To: <speakup@braille.uwo.ca> Sent: Monday, May 06, 2002 11:04 AM Subject: Re: cdrecord question > Igor: did you ever report what cdrecord -scanbus is giving you? I didn't see it. > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Igor Gueths @ ` Cheryl Homiak 0 siblings, 0 replies; 32+ messages in thread From: Cheryl Homiak @ UTC (permalink / raw) To: speakup Sorry, Igor, I must have missed it. ^ permalink raw reply [flat|nested] 32+ messages in thread
* cdrecord question @ Igor Gueths ` 'Georgina' 0 siblings, 1 reply; 32+ messages in thread From: Igor Gueths @ UTC (permalink / raw) To: speakup Hi all. I also tried dev=/dev/scd0, dev=/dev/sg0, and dev=/dev/hdd. When I tried dev=/dev/hdd, I got an I/O error: Cannot open scsi driver. When I tried sg0 and scd0, I got cdrecord: Bad file descriptor. Could not open scsi driver. Any ideas on how to fix this? Thanks again! ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question Igor Gueths @ ` 'Georgina' ` Igor Gueths 0 siblings, 1 reply; 32+ messages in thread From: 'Georgina' @ UTC (permalink / raw) To: speakup Hi I think that you've neglected to send the whole message. What's your question? If its a IDE burner, are you using the generic scsi module? Have you specified hdd-scsi? Have you examined your boot messages to see how the system is seeing your burner? Gena Blindness Advocacy and Self Help Online www.bashonline.org >Hi all. I also tried dev=/dev/scd0, dev=/dev/sg0, and dev=/dev/hdd. When I >tried dev=/dev/hdd, I got an I/O error: Cannot open scsi driver. When I >tried sg0 and scd0, I got cdrecord: Bad file descriptor. Could not open >scsi driver. Any ideas on how to fix this? Thanks again! > > >_______________________________________________ >Speakup mailing list >Speakup@braille.uwo.ca >http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` 'Georgina' @ ` Igor Gueths ` Gregory Nowak 0 siblings, 1 reply; 32+ messages in thread From: Igor Gueths @ UTC (permalink / raw) To: speakup Hi. I am using an atapi drive. Also, I have passed append="hdd=ide-scsi" to /etc/lilo.conf. After rebooting the system, the scsi emulation driver maps the burner to scsi0. Doesn't that mean that /dev/scd0 should be the Cd burner, since my Cdrom drive isn't using scsi emulation? On Sun, 5 May 2002, 'Georgina' wrote: > Hi > > I think that you've neglected to send the whole message. What's your > question? If its a IDE burner, are you using the generic scsi module? > Have you specified hdd-scsi? Have you examined your boot messages to > see how the system is seeing your burner? > > Gena > > > > Blindness Advocacy and Self Help Online www.bashonline.org > > >Hi all. I also tried dev=/dev/scd0, dev=/dev/sg0, and dev=/dev/hdd. When I > >tried dev=/dev/hdd, I got an I/O error: Cannot open scsi driver. When I > >tried sg0 and scd0, I got cdrecord: Bad file descriptor. Could not open > >scsi driver. Any ideas on how to fix this? Thanks again! > > > > > >_______________________________________________ > >Speakup mailing list > >Speakup@braille.uwo.ca > >http://speech.braille.uwo.ca/mailman/listinfo/speakup > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Igor Gueths @ ` Gregory Nowak ` Igor Gueths 0 siblings, 1 reply; 32+ messages in thread From: Gregory Nowak @ UTC (permalink / raw) To: speakup Actually, your drive is and should be ide-scsi emulated. For me, my burner is at /dev/sr0. Greg On Sun, May 05, 2002 at 06:05:25PM -0400, Igor Gueths wrote: > Hi. I am using an atapi drive. Also, I have passed append="hdd=ide-scsi" > to /etc/lilo.conf. After rebooting the system, the scsi emulation driver > maps the burner to scsi0. Doesn't that mean that /dev/scd0 should be the > Cd burner, since my Cdrom drive isn't using scsi emulation? > > On Sun, 5 May 2002, 'Georgina' wrote: > > > Hi > > > > I think that you've neglected to send the whole message. What's your > > question? If its a IDE burner, are you using the generic scsi module? > > Have you specified hdd-scsi? Have you examined your boot messages to > > see how the system is seeing your burner? > > > > Gena > > > > > > > > Blindness Advocacy and Self Help Online www.bashonline.org > > > > >Hi all. I also tried dev=/dev/scd0, dev=/dev/sg0, and dev=/dev/hdd. When I > > >tried dev=/dev/hdd, I got an I/O error: Cannot open scsi driver. When I > > >tried sg0 and scd0, I got cdrecord: Bad file descriptor. Could not open > > >scsi driver. Any ideas on how to fix this? Thanks again! > > > > > > > > >_______________________________________________ > > >Speakup mailing list > > >Speakup@braille.uwo.ca > > >http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > _______________________________________________ > > Speakup mailing list > > Speakup@braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Gregory Nowak @ ` Igor Gueths ` Gregory Nowak ` Cheryl Homiak 0 siblings, 2 replies; 32+ messages in thread From: Igor Gueths @ UTC (permalink / raw) To: speakup Hi Greg. Unfortunately, I tried it with -dev=/dev/sr0, and got the following: scsidev: /dev/sr0 scsibus: 2 target: 2 lung: 2 cdrecord: bad file descriptor. Could not open scsi driver cdrecord: For possible targets try cdrecord -scanbus. Make sure you are root And when I do cdrecord -scanbus, it says: "No such file or directory, cannot open scsi driver. Is this normal since the drive isn't an actual scsi drive, rather it is being emulated as such? Also, I thought I remembered seeing an environment variable or two which cdrecord used to determine the correct /dev for the Cd recorder? Is it normal for you to do cdrecord -scanbus and to get the error I described above since you are running pretty much the same setup as me as far as I know? Thanks! On Sun, 5 May 2002, Gregory Nowak wrote: > Actually, your drive is and should be ide-scsi emulated. For me, my burner is at /dev/sr0. > Greg > > > On Sun, May 05, 2002 at 06:05:25PM -0400, Igor Gueths wrote: > > Hi. I am using an atapi drive. Also, I have passed append="hdd=ide-scsi" > > to /etc/lilo.conf. After rebooting the system, the scsi emulation driver > > maps the burner to scsi0. Doesn't that mean that /dev/scd0 should be the > > Cd burner, since my Cdrom drive isn't using scsi emulation? > > > > On Sun, 5 May 2002, 'Georgina' wrote: > > > > > Hi > > > > > > I think that you've neglected to send the whole message. What's your > > > question? If its a IDE burner, are you using the generic scsi module? > > > Have you specified hdd-scsi? Have you examined your boot messages to > > > see how the system is seeing your burner? > > > > > > Gena > > > > > > > > > > > > Blindness Advocacy and Self Help Online www.bashonline.org > > > > > > >Hi all. I also tried dev=/dev/scd0, dev=/dev/sg0, and dev=/dev/hdd. When I > > > >tried dev=/dev/hdd, I got an I/O error: Cannot open scsi driver. When I > > > >tried sg0 and scd0, I got cdrecord: Bad file descriptor. Could not open > > > >scsi driver. Any ideas on how to fix this? Thanks again! > > > > > > > > > > > >_______________________________________________ > > > >Speakup mailing list > > > >Speakup@braille.uwo.ca > > > >http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > _______________________________________________ > > > Speakup mailing list > > > Speakup@braille.uwo.ca > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > > _______________________________________________ > > Speakup mailing list > > Speakup@braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Igor Gueths @ ` Gregory Nowak ` Cheryl Homiak 1 sibling, 0 replies; 32+ messages in thread From: Gregory Nowak @ UTC (permalink / raw) To: speakup Hi Igor, Act on my previous post, then try cdrecord again. If it still doesn't work after you've rebuilt your kernel/modules in regards to my previous post, let me know what you get, and we can go from there. I'm running slackware 8.0. If this is your set up, then ... Greg On Sun, May 05, 2002 at 08:37:16PM -0400, Igor Gueths wrote: > Hi Greg. Unfortunately, I tried it with -dev=/dev/sr0, and got the > following: > scsidev: /dev/sr0 > scsibus: 2 target: 2 lung: 2 > cdrecord: bad file descriptor. Could not open scsi driver > cdrecord: For possible targets try cdrecord -scanbus. Make sure you > are root > > And when I do cdrecord -scanbus, it says: "No such file or > directory, cannot open scsi driver. Is this normal since the drive isn't > an actual scsi drive, rather it is being emulated as such? Also, I thought > I remembered seeing an environment variable or two which cdrecord used to > determine the correct /dev for the Cd recorder? Is it normal for you to do > cdrecord -scanbus and to get the error I described above since you are > running pretty much the same setup as me as far as I know? Thanks! > On Sun, 5 May 2002, Gregory Nowak wrote: > > > Actually, your drive is and should be ide-scsi emulated. For me, my burner is at /dev/sr0. > > Greg > > > > > > On Sun, May 05, 2002 at 06:05:25PM -0400, Igor Gueths wrote: > > > Hi. I am using an atapi drive. Also, I have passed append="hdd=ide-scsi" > > > to /etc/lilo.conf. After rebooting the system, the scsi emulation driver > > > maps the burner to scsi0. Doesn't that mean that /dev/scd0 should be the > > > Cd burner, since my Cdrom drive isn't using scsi emulation? > > > > > > On Sun, 5 May 2002, 'Georgina' wrote: > > > > > > > Hi > > > > > > > > I think that you've neglected to send the whole message. What's your > > > > question? If its a IDE burner, are you using the generic scsi module? > > > > Have you specified hdd-scsi? Have you examined your boot messages to > > > > see how the system is seeing your burner? > > > > > > > > Gena > > > > > > > > > > > > > > > > Blindness Advocacy and Self Help Online www.bashonline.org > > > > > > > > >Hi all. I also tried dev=/dev/scd0, dev=/dev/sg0, and dev=/dev/hdd. When I > > > > >tried dev=/dev/hdd, I got an I/O error: Cannot open scsi driver. When I > > > > >tried sg0 and scd0, I got cdrecord: Bad file descriptor. Could not open > > > > >scsi driver. Any ideas on how to fix this? Thanks again! > > > > > > > > > > > > > > >_______________________________________________ > > > > >Speakup mailing list > > > > >Speakup@braille.uwo.ca > > > > >http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > _______________________________________________ > > > > Speakup mailing list > > > > Speakup@braille.uwo.ca > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > > > > > > _______________________________________________ > > > Speakup mailing list > > > Speakup@braille.uwo.ca > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > _______________________________________________ > > Speakup mailing list > > Speakup@braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Igor Gueths ` Gregory Nowak @ ` Cheryl Homiak ` Igor Gueths 1 sibling, 1 reply; 32+ messages in thread From: Cheryl Homiak @ UTC (permalink / raw) To: speakup No, this isn't normal. And it says right in the cdwriting howto there's no point in proceeding if scanbus doesn't even recognize your driver. ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: cdrecord question ` Cheryl Homiak @ ` Igor Gueths 0 siblings, 0 replies; 32+ messages in thread From: Igor Gueths @ UTC (permalink / raw) To: speakup Hi Cheryl. However, I can mount it as a Cd-rom. It is also detected by the kernel. What the howto is probably talking about is if your cdrom isn't even detected by the kernel, then there is no point in proceeding. I actually have scsi emulation enabled, I'm just having problems with cdrecord not being able to find the emulated device. ----- Original Message ----- From: Cheryl Homiak <chomiak@chartermi.net> To: <speakup@braille.uwo.ca> Sent: Monday, May 06, 2002 11:32 AM Subject: Re: cdrecord question > No, this isn't normal. And it says right in the cdwriting howto there's no point > in proceeding if scanbus doesn't even recognize your driver. > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 32+ messages in thread
* cdrecord question @ Igor Gueths 0 siblings, 0 replies; 32+ messages in thread From: Igor Gueths @ UTC (permalink / raw) To: speakup Hi all. Also, when I do cat /proc/scsi/scsi it says that my burner is attached on id0 lung 0 channel 0. Do I have to possibly rebuild the kernel and compile out generic atapi cdrom support? ^ permalink raw reply [flat|nested] 32+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 32+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
cdrecord question Igor Gueths
` Cheryl Homiak
` Igor Gueths
` Gregory Nowak
` Igor Gueths
` Gregory Nowak
` Cheryl Homiak
` Igor Gueths
` Cheryl Homiak
` Gregory Nowak
` Igor Gueths
` Gregory Nowak
` Igor Gueths
` Raul A. Gallegos
` Igor Gueths
` Cheryl Homiak
` Gregory Nowak
` Cheryl Homiak
` Gregory Nowak
` Cheryl Homiak
` Cheryl Homiak
` Igor Gueths
` Cheryl Homiak
Igor Gueths
` 'Georgina'
` Igor Gueths
` Gregory Nowak
` Igor Gueths
` Gregory Nowak
` Cheryl Homiak
` Igor Gueths
Igor Gueths
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).