No, the data rate for SCSI xfers is not the same thing as the record speed.
Normally there is some technique provided to permit access to extended SCSI function on your SCSI board or chipset. The Data rate controls how fast the SCSI controller talks to the SCSI drive. CD-ROM drives (as well as tape drives) normally need slower rates (and preferably parity set to ON) for reliability. With the data rate set to high the controller will "lose sync" with the drive and you'll get errors even though there is nothing wrong with your hardware. The "blinking lights" symptom is typical of this. Check to see if your SCSI bios posts a message about devices found during the initial power up. If you see a report of attached devices, then you have a SCSI BIOS on the SCSI card. There should be some way of accessing an on board utility that will permit you to set the SCSI data rate. Worst case you may need to go to the manufacturers site and see if they provide an external util to do this... Advansys, Adaptec, etc. have "on board" bios menus that permit you to change this. -JMS |-----Original Message----- |From: Praedor [mailto:[EMAIL PROTECTED]] |Sent: Friday, November 09, 2001 9:55 PM |To: [EMAIL PROTECTED] |Cc: Mandrake Expert |Subject: Re: [expert] Enough! What is wrong with linux and cdwriters? | | |How do I turn down the data rate? I am not sure how I am |supposed to access |the controller's bios. I have set it to 2x write speed (it is |a slow CD |burner). Are you saying I must try 1x? Also...there is no |way other than a |reboot to get it back? | |On Friday 09 November 2001 07:45 pm, you wrote: |> The constant blinking activity is a SCSI command error. |> |> The SCSI "cpu" doesn't know what to do and has gone offline |hence your |> errors. |> |> If you shut down your system and restart, everything will be |ok again. |> |> You might want to TURN DOWN the data rate on the SCSI drive via the |> controller's BIOS. |> |> -JMS |> |> |-----Original Message----- |> |From: [EMAIL PROTECTED] |> |[mailto:[EMAIL PROTECTED]] On Behalf Of Praedor |> |Sent: Friday, November 09, 2001 9:41 PM |> |To: [EMAIL PROTECTED] |> |Subject: Re: [expert] Enough! What is wrong with linux and |cdwriters? |> | |> | |> |Here we go again! Just rebooted and tried to burn a CD. |It failed - |> |even though I am using supermount, it failed to mount the CDROM so |> |it failed. I |> |then tried again AFTER mounting the CD that I wanted to copy. |> |No worky. The |> |CDRW has a constant, blinking activity light and it is now |> |impossible to |> |remove the blank without rebooting. Upon trying to burn it |> |again after |> |mounting the CD with the image I wanted to burn, I get this |> |message (in |> |gcombust): |> | |> | Cdrecord 1.10 (i586-mandrake-linux-gnu) Copyright (C) |1995-2001 J�rg |> |Schilling TOC Type: 1 = CD-ROM |> |Using libscg version 'schily-0.5' |> |atapi: 1 |> |Device type : Removable CD-ROM |> |Version : 0 |> |Response Format: 1 |> |Vendor_info : 'TEAC ' |> |Identifikation : 'CD-W54E ' |> |Revision : '1.1A' |> |Device seems to be: Generic CD-ROM. |> |scsidev: '1,0,0' |> |scsibus: 1 target: 0 lun: 0 |> |Linux sg driver version: 3.1.20 |> |/usr/bin/cdrecord: Sorry, no CD/DVD-Recorder or unsupported |> |CD/DVD-Recorder |> |found on this target. |> | |> |WRONG! The CDRW did not change magically into a normal |CDROM, it is |> |STILL a CDRW. Is this the way that linux normally handles |CD-RWs? I |> |have used linux |> |for several years now and only recently started in with |> |CD-RWs. This is new |> |to me but I must say that there is something seriously wrong |> |here in the way |> |it is treating the drive, and the way it makes it impossible |> |to use or open |> |the drive after a failure to copy or burn a CD. |> | |> |I start kpm to see if there is a process associated with the drive |> |that might explain the neverending blinking activity light but I see |> |nothing obvious - |> |so I can't kill the damn thing. I am stuck with having to |> |reboot yet again. |> | |> |Someone toss me a bone here please. |> | |> |On Friday 09 November 2001 06:35 pm, you wrote: |> |> This is driving me mad! I have a Teac cd-rw set as the |slave to my |> |> cdrom master. MOST of the time I am unable to burn CDs, I get |> |> messages that the device isn't scsi or it has the wrong |driver but |> |> once in a while I am able to burn a CD, but then no more. |> |> |> |> I just burned a CD, for instance, direct CD-to-CDRW. It |worked. I |> |> then removed the source CD and the newly burned CD and replaced |> |> them with the next source CD and blank CD in the burner. |I try to |> |> burn this and now, magically, I get this error: |> |> |> |> scsidev: '1,0,0' |> |> scsibus: 1 target: 0 lun: 0 |> |> Linux sg driver version: 3.1.20 |> |> /usr/bin/cdrecord: Sorry, no CD/DVD-Recorder or unsupported |> |> CD/DVD-Recorder found on this target. |> |> |> |> Bullcrap! IT IS A BURNER. The damn activity light is |flashing and |> |> flashing and flashing too and will not stop. I cannot open |> | |> |the drive |> | |> |> and remove the blank. The ONLY way I can get the damn drive to |> |> give me the blank CD in it and try again to burn onto a |new disk is |> |> to reboot. Very windoze. |> |> |> |> Is there some magic that I am unaware of that is needed to |> | |> |be done on |> | |> |> my computer to make a CD-RW work all the time rather than |once in a |> |> blue moon? |> |> |> |> In lilo, I have: |> |> append=" hde=ide-scsi devfs=mount quiet" |> |> |> |> so that scsi emulation is used for the drive and it works |once in a |> |> while, it seems (and the ide-scsi module is loaded). |> |> |> |> Someone, before I take a frickin' bat to my CDRW, please |> | |> |tell me what |> | |> |> is the trick to getting CDs to burn in a simple burner?! I am |> |> about to reboot AGAIN to get the blank out of it. |> |> |> |> praedor |
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
