On Tuesday 03 April 2001 12:43, Jonathan Paul Cowherd wrote:
I' m using SuSE 7.1 and I have a Plextor scsi cdwriter. Allthougth my system recognizes the device when I run the command "cdrecord -scanbus" as root I get the following message: "bash-2.04# cdrecord -scanbus Cdrecord 1.9 (i686-suse-linux) Copyright (C) 1995-2000 Jörg Schilling cdrecord: No such file or directory. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. bash-2.04# " Can anyone help me? Thanks. Gerassimos
This sounds like there is no scsi driver loaded. If your kernel has SCSI support compiled in, make sure that it is finding your card. You can type the command "dmesg" to see what the kernel has found and what is loaded as far as compile in.
Did that. Found nothing out of the ordinary....irq, ioports, device, lun... the kernel appears to see it fine.
If your SCSI card driver is compiled as a module, you can check to see if the module is loaded by typing "lsmod" and if not, you can "modprobe -a" the name of your SCSI card driver to load it.
I am using an IDE with ide-scsi emulation. It is a mod which loads without any error messages. It is listed ok in the /proc scsi var.
You may need /proc support compile in too.
Always do. Wouldn't fire up without it!
mmm... I'm using 7.1 and I have an IDE PleXWriter W8432Ti attached. When I use ide-scsi I can get it to be recognized, but if I try to read or burn more than about 60MB it dies. I thought I might switch to a scsi PleXWriter, but if you are having problems getting 7.1 to recognize it I'm not so sure I will use a PleXWriter... JLK
I use the gtk version of xcdroast called "xcdrgtk" to burn CDs with. The 7.1 release is beta, but it works great and has support for almost everything you want to do with burning CDs.
I tried that one too. In fact I have tried EVERY cdburner software on the SuSE cd set.
As far as you only being able to burn about 60MBs before an error, it sounds like there maybe be some protocol issues. There are some things to take into consideration when burning:
- Make sure that you have your device settings correct. Autodetection doesn't always return the correct results for you SCSI CDRW. (Although xcdrgtk has done so with the new version).
I wouldn't have a clue as to what to change if the ide-scsi emulation misconfigures the ide cdrw.
- Make sure the CDR you are using is compatible with your burner and always take the time to verify your burns against your image afterward.
That's a good point. I am using CD-R 80 minutes... I also tried CD-RW 74 minutes.
- With the ide-scsi.o driver, make sure that you don't have the ide-cd.o driver loaded, only the scsi-cd.o module loaded. If your kernel has UDMA support for you controller, make sure that is compile in too. I've got UDMA support for my motherboard compiled in and it seems as if I am getting better performance with the ide-scsi.o driver that with the native drivers for my motherboard as far as the CDROM is concerned... I'll need to do actual test to back this statement.
mmm... a new lead! I'll check this one out.
I think the vanilla kernels come with ide-cd.o compile in so you may need to either use a SCSI kernel or compile your own.
I'm using 2.4.2 currently and recommend it for anyone's workstation. I prefer to roll my own tweaked kernel opposed to using the vanilla SuSE or Linus kernel. Since SuSE patches their source on their kernel, I would make sure that you stick with SuSE kernel source opposed to mixing between the SuSE and Linus code.
While I usually recompile my kernel to match my workstation, I always use the SuSE kernel and never patch it.
- If you are using a old, slow computer, you may experience problems. The documentation for xcdrgtk talks about this a little.
My Beast is a 1GHz Athlon with 512MB of RAM... neither old nor slow! Thanks JLK
I hope this helps some.
===========
Jonathan Paul Cowherd jpcowh01@slug.louisville.edu http://www.slug.louisville.edu/~jpcowh01