Your drive could need cleaning, or have worn out, or in some way have been disconnected. Those kind of drives have to be replaced every so often. If it's a usb drive, have you done a modprobe usbmass yet? If not, that may be all you need to get things going. If you read dmesg does the cd drive even show up as a valid device now? If not, maybe insmod usbmass will fix that and get you burning.
On Sat, 9 Jun 2012, Javier Vasquez wrote: > Hi, > > I've been using the original cdrecord (cdrtools) for more than 10 > years now, however I hadn't burned anything in the last 3 months (or > even more). With the current linux kernel image from Arch: > > % uname -a > Linux jvasquez14 3.3.8-1-ARCH #1 SMP PREEMPT Tue Jun 5 15:20:32 CEST > 2012 x86_64 GNU/Linux > > I can't get cdrecord to recognize any cd/dvd writer, not the laptop > one neither an external USB one... I might be mistaken, but with 3.0 > image I believe things worked (can't be sure, as I said I haven't been > burning anything for months). > > When I try to identify the cd/dvd writers: > > % cdrecord -scanbus > Cdrecord-ProDVD-ProBD-Clone 3.01a07 (x86_64-unknown-linux-gnu) > Copyright (C) 1995-2012 Joerg Schilling > cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot > open or use SCSI driver. > cdrecord: For possible targets try 'cdrecord -scanbus'. > cdrecord: For possible transport specifiers try 'cdrecord dev=help'. > > I looked through google, but the responses I get are pretty old, some > from 2004, talking about early 2.6 kernels... I found one page (an > old one as well) that suggests using ide-scsi emulation, but that > seems to me old as well: > > http://xpt.sourceforge.net/techdocs/media/cd/cd03-DeviceConfiguration/ar01s06.html > > Besides for quiet a while we don't get hdc or sdc, just plain sr0/sr1 > (even the scd0/scd1 was removed), and that seemed to work before if > I'm not mistaken... Perhaps now the way is "sr0=scsi"? > > Any ways, maybe someone knows better, :-) I can try the boot loading > thing, but before, I wanted to see if someone has experienced this, > and there's a known work around. > > Thanks, > > ---------------------------------------------------------------- Jude <jdashiel-at-shellworld-dot-net> <http://www.shellworld.net/~jdashiel/nj.html>
