LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 03-07-2007, 07:29 PM   #1
coldbeer
Member
 
Registered: May 2006
Distribution: Slackware 14.1 + multilib
Posts: 144

Rep: Reputation: 49
cdrecord with *real* SCSI CD-R Burner problem


I am running as root with slackware 11 and the huge.s 2.6 kernel.
I have a adaptec scsi board attached to a Philips CDD2600 CDROM burner.
I have the following problem with cdrecord:
-------------------------------------------
bash-3.1# cdrecord -scanbus
Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
cdrecord: Warning: Running on Linux-2.6.17.13
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
Linux sg driver version: 3.5.33
Using libscg version 'schily-0.8'.
scsibus2:
2,0,0 200) *
2,1,0 201) *
2,2,0 202) 'PHILIPS ' 'CDD2600 ' '1.07' Removable CD-ROM
2,3,0 203) *
2,4,0 204) *
2,5,0 205) *
2,6,0 206) *
2,7,0 207) *

----------------------------------------
But then when I try to burn:
----------------------------------------
bash-3.1# cdrecord -v dev=2,2,0 puppy-2.11-seamonkey.iso
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
cdrecord: Continuing in 5 seconds...
Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
cdrecord: Warning: Running on Linux-2.6.17.13
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
TOC Type: 1 = CD-ROM
scsidev: '2,2,0'
scsibus: 2 target: 2 lun: 0
Linux sg driver version: 3.5.33
Using libscg version 'schily-0.8'.
SCSI buffer size: 64512
atapi: 0
Device type : Removable CD-ROM
Version : 2
Response Format: 2
Capabilities :
Vendor_info : 'PHILIPS '
Identifikation : 'CDD2600 '
Revision : '1.07'
Device seems to be: Philips CDD-2600.
Using driver for Philips CDD-522 (philips_cdd522).
Driver flags :
Supported modes: TAO
FIFO size : 4194304 = 4096 KB
Track 01: data 70 MB
Total size: 81 MB (08:03.22) = 36242 sectors
Lout start: 81 MB (08:05/17) = 36242 sectors
Current Secsize: 2048
ATIP info from disk:
Is not unrestricted
Disk application code: 0
ATIP start of lead in: -11849 (97:24/01)
ATIP start of lead out: 359847 (79:59/72)
Disk type: Long strategy type (Cyanine, AZO or similar)
Manuf. index: 25
Manufacturer: Taiyo Yuden Company Limited
cdrecord: Warning: controller returns zero sized Speed/Dummy information page.
cdrecord: Warning: controller returns wrong size for Speed/Dummy information page.
cdrecord: Warning: controller returns wrong page 0 for Speed/Dummy information page (23).
cdrecord: Cannot init drive.

------------------------------------------
I have searched through the LQ.org forums for similar issues and I am still at a loss.

This same setup works fine with slackware 10.0 with the 2.4 kernel.

Now for comparison, here is the output from a SUCCESSFUL burn using slackware 10 w/2.4 (xcdroast):
------------------------------------------
Calling: /usr/local/lib/xcdroast-0.98/bin/xcdrwrap CDRECORD dev= "1,2,0" gracetime=2 fs=4096k -v speed=0 defpregap=0 -eject -waiti tsize=342576s -

scsidev: '1,2,0'
scsibus: 1 target: 2 lun: 0
Linux sg driver version: 3.1.25
Cdrecord 2.00.3 (i686-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling
TOC Type: 1 = CD-ROM
Waiting for data on stdin...
Using libscg version 'schily-0.7'
atapi: 0
Device type : Removable CD-ROM
Version : 2
Response Format: 2
Capabilities :
Vendor_info : 'PHILIPS '
Identifikation : 'CDD2600 '
Revision : '1.07'
Device seems to be: Philips CDD-2600.
Using driver for Philips CDD-522 (philips_cdd522).
Driver flags :
Supported modes: TAO
FIFO size : 4194304 = 4096 KB
cdrecord: Warning: controller returns zero sized Speed/Dummy information page.
cdrecord: Warning: controller returns wrong size for Speed/Dummy information page.
cdrecord: Warning: controller returns wrong page 0 for Speed/Dummy information page (23).
Track 01: data 669 MB
Total size: 768 MB (76:07.70) = 342578 sectors
Lout start: 768 MB (76:09/53) = 342578 sectors
Current Secsize: 2048
ATIP info from disk:
Is not unrestricted
Disk application code: 0
ATIP start of lead in: -11849 (97:24/01)
ATIP start of lead out: 359847 (79:59/72)
Disk type: Long strategy type (Cyanine, AZO or similar)
Manuf. index: 25
Manufacturer: Taiyo Yuden Company Limited
Blocks total: 359847 Blocks current: 359847 Blocks remaining: 17269
Starting to write CD/DVD at speed 0 in real TAO mode for single session.
Waiting for reader process to fill input buffer ...
input buffer ready.
Starting new track at sector: 0

Track 01: Total bytes read/written: 701595648/701595648 (342576 sectors).
Writing time: 2290.187s
Average write speed 2.0x.
Fixating...
Fixating time: 126.081s
cdrecord: fifo had 11051 puts and 11051 gets.
cdrecord: fifo was 0 times empty and 10976 times full, min fill was 93%.
-----------------------------------------------

So those first 3 warnings are not the issue, this is the issue:
cdrecord: Cannot init drive.

I'm at a loss here.
 
Old 03-07-2007, 08:07 PM   #2
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
Might wanna try booting with 'hdc=scsi' boot parameter or whatever the name of the drive is.

I know 'hdc=ide-scsi' turns ide-scsi emulation on, so I'm betting 'hdc=scsi' turns it off.

Last edited by H_TeXMeX_H; 03-07-2007 at 08:08 PM.
 
Old 03-07-2007, 08:19 PM   #3
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,450
Blog Entries: 4

Rep: Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505
Hi,

Try this coasterless link, very informative for cdrecord disk reading and writing.

I think you should be looking at dao instead of tao.

Code:
your command;
#cdrecord -v dev=2,2,0 puppy-2.11-seamonkey.iso

should be something like this;

#cdrecord dev=2,2,0 speed=10 padsize=63s -pad -dao -v -eject puppy-2.11-seamonkey.iso
The padding is very important when you burn. Read the referenced link, very helpful.

Your hardware is recognized by cdrecord.
 
Old 03-07-2007, 08:22 PM   #4
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,450
Blog Entries: 4

Rep: Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505Reputation: 1505
Quote:
Originally Posted by H_TeXMeX_H
Might wanna try booting with 'hdc=scsi' boot parameter or whatever the name of the drive is.

I know 'hdc=ide-scsi' turns ide-scsi emulation on, so I'm betting 'hdc=scsi' turns it off.
Hi,

The 2.6 kernel uses the ide-cd module not the ide-scsi. If the OP omits the ide-cd from the 2.6 kernel then that could be a problem.
 
Old 03-07-2007, 08:25 PM   #5
guzzi
Member
 
Registered: Jun 2004
Location: Lawrence, KS
Distribution: Slackware
Posts: 294

Rep: Reputation: 32
scsi cdrom burning

H_TeXMeX_H may have a good point.

I am using an Adaptec AIC7XXX card with a Plextor drive without any problem. In fact I just cooked up several CD's to confirm. Using a 2.6.19 kernel there were no "Warning"
messages like you received. Also, I used the same commands as you, but changed to reflect
my system and files.

Could this be unique to your kernel version?
 
Old 03-08-2007, 01:57 AM   #6
rkrishna
Member
 
Registered: Mar 2005
Location: chennai(madras), India
Distribution: slackware ofcourse
Posts: 654

Rep: Reputation: 32
try the complete command as onebuck suggested with simulation option ie "- dummy "1.always use "-dummy" option if you are trying for first time
2. i doubt the necessity of dev=, ,, thing, it will work with
Code:
cdrecord dev=/dev/cdrom -v speed=X  -eject -dummy puppy-2.11-seamonkey.iso
check device name and speed
 
Old 03-08-2007, 05:30 AM   #7
coldbeer
Member
 
Registered: May 2006
Distribution: Slackware 14.1 + multilib
Posts: 144

Original Poster
Rep: Reputation: 49
If I use:
cdrecord dev=2,2,0 speed=2 padsize=63s -dummy -pad -dao -v -eject puppy-2.11-seamonkey.iso

I get:
cdrecord: Drive does not support SAO recording.
cdrecord: Illegal write mode for this drive.
-----------------------------------------------------
If I use:
cdrecord dev=2,2,0 speed=2 padsize=63s -dummy -pad -tao -v -eject puppy-2.11-seamonkey.iso

I get: cdrecord: Cannot init drive.
--------------------------------------------------------
If I use:
cdrecord dev=/dev/cdrom -v speed=2 -eject -dummy puppy-2.11-seamonkey.iso

I get:
Vendor_info : 'LITE-ON '
Identifikation : 'CD-ROM LTN-5291S'
Revision : 'NS0D'
Device seems to be: Generic mmc CD-ROM.
Current: 0x0000
Profile: 0x0008
cdrecord: Sorry, no CD/DVD-Recorder or unsupported CD/DVD-Recorder found on this target.

This is my other plain ide CDROM.
I've tried dev=/media/cdrecorder too.
I've also tried all the other philips drivers and the mmc_cdr.
All the philips drivers sy cannot init drive and mmc_cdr says Try to use other driver on known device.

I'm thinking its not a cdrecord options issue?
----------------------------------------------------
 
Old 03-08-2007, 06:13 AM   #8
coldbeer
Member
 
Registered: May 2006
Distribution: Slackware 14.1 + multilib
Posts: 144

Original Poster
Rep: Reputation: 49
I also installed the latest cdrtools from:

ftp://ftp.berlios.de/pub/smake/alpha/

where it says:

"Important information: Linux-2.6.8.1 breaks CD/DVD writing for suid root applications
If you have related problems, use a recent original cdrecord and install cdrecord suid-root or go back to Linux-2.4. An original recent cdrecord correctly deals with the problems on Linux-2.6."

And I still get "cdrecord: Cannot init drive." where it worked on 2.4
 
Old 03-08-2007, 01:47 PM   #9
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
Try another kernel.
 
Old 03-08-2007, 03:35 PM   #10
coldbeer
Member
 
Registered: May 2006
Distribution: Slackware 14.1 + multilib
Posts: 144

Original Poster
Rep: Reputation: 49
Quote:
Originally Posted by H_TeXMeX_H
Try another kernel.
yep. That's what I'm planning on doing tonight. Thanks.
 
Old 03-10-2007, 12:36 PM   #11
coldbeer
Member
 
Registered: May 2006
Distribution: Slackware 14.1 + multilib
Posts: 144

Original Poster
Rep: Reputation: 49
Talking Fixed

I found a solution to my problem and its pretty simple. I copied the cdrecord executable version 2.00 from my Slackware 10.0 distribution into my Slackware 11.

cdrecord version 2.00 does not give the Cannot init drive error and it burns just fine.

I should say that I also downloaded the Linux kernel version 2.6.20 and recompiled it with ALL SCSI options set to compile as modules so that I could make sure that no scsi drivers were stepping on each other (i.e. to make sure there were no drivers loaded AT ALL) I just did "modprobe aic7xxx" to load this one driver (and of course its dependents).

I find it curious that cdrecord version 2.01 that comes with Slackware 11.0 is the version that has all the "messages" about how 2.6.8 broke the scsi system and that the Debian people are uncooperative (comments inside of cdrecord.c 2.01 file). From my searching the www the past few days and reading all the dirty laundry that was aired by both the author of cdrecord and also Linus himself (I guess being successful is no guarantee people will at like adults - a little compassion on either side is all it would have taken.) Not to mention, and I'm mentioning it anyways , that THEN cdrecord 2.01.01 alpha was posted under a new license. GOD this is a &^$%$ soap opera isn't it ;p

So I find it extremely odd that after all that, cdrecord version 2.00 works JUST FINE on the 2.6.20 kernel.
Riddle me that, Batman! LOL

Have a Great Day.
--coldbeer

Last edited by coldbeer; 03-10-2007 at 01:01 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
slackware 11 scsi cd burner problem coldbeer Slackware 7 11-18-2006 06:52 AM
2.6.15.6, scsi burner, cdrecord won't see drive ardya Slackware 2 03-13-2006 12:49 PM
cdrecord fails, claims scsi problem. Dave_K Linux - Software 1 01-13-2006 11:00 AM
cdrecord ide/scsi problem azacid Linux - Software 8 03-04-2004 05:37 PM
scsi cd burner problem frieza Linux - Hardware 4 01-10-2004 05:44 PM


All times are GMT -5. The time now is 12:14 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration