Very Computer

We have an HP Visualize machine (similar to a Kayak) with a Yamaha
CRW4416S CD burner.  The SCSI card is a sym53c875.  

Under RH 6.1 (with most of the security upgrades), burning CDs went
fine.  We just upgraded to RH 7.2, and now we can't burn CDs.  The
output from cdrecord is this:

Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 J
TOC Type: 1 = CD-ROM
scsidev: '0,4,0'
scsibus: 0 target: 4 lun: 0
Linux sg driver version: 3.1.19
Using libscg version 'schily-0.5'
atapi: 0
Device type    : Removable CD-ROM
Version        : 2
Response Format: 2
Capabilities   : SYNC
Vendor_info    : 'YAMAHA  '
Identifikation : 'CRW4416S        '
Revision       : '1.0f'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags   : SWABAUDIO
Drive buf size : 1566432 = 1529 KB
FIFO size      : 4194304 = 4096 KB
Track 01: data   88 MB        
Total size:     101 MB (10:02.80) = 45210 sectors
Lout start:     101 MB (10:04/60) = 45210 sectors
Current Secsize: 2048
ATIP info from disk:
  Indicated writing power: 4
  Is not unrestricted
  Is not erasable
  Disk sub type: Medium Type A, high Beta category (A+) (3)
  ATIP start of lead in:  -11849 (97:24/01)
  ATIP start of lead out: 359848 (79:59/73)
Disk type:    Long strategy type (Cyanine, AZO or similar)
Manuf. index: 25
Manufacturer: Taiyo Yuden Company Limited
Blocks total: 359848 Blocks current: 359848 Blocks remaining: 314638
Starting to write CD/DVD at speed 4 in write mode for single session.
Last chance to quit, starting real write in 0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
cdrecord: Input/output error. send opc: scsi sendcmd: no error
CDB:  54 01 00 00 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 06 00 00 00 00 0A 00 00 00 00 29 00 00 00
Sense Key: 0x6 Unit Attention, Segment 0
Sense Code: 0x29 Qual 0x00 (power on, reset, or bus device reset occurred) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 62.246s timeout 60s
cdrecord: Resource temporarily unavailable. OPC failed.
cdrecord: Input/output error. prevent/allow medium removal: scsi sendcmd: no error
CDB:  1E 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 04 01 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x04 Qual 0x01 (logical unit is in process of becoming ready) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.005s timeout 40s
cdrecord: fifo had 64 puts and 0 gets.
cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%.

1) What do these messages really mean?

2) Is there a way to allow SCSI devices to dis- and re-connect
themselves from the bus, without re-compiling the kernel?  (E.g. by
setting parameters in /etc/modules.conf?

Modules.conf is as follows:

alias parport_lowlevel parport_pc
alias scsi_hostadapter sym53c8xx
alias eth0 pcnet32
alias usb-controller usb-uhci

--
P. Douglas Reeder     Lecturer, Dept. Computer/Info. Science, Ohio State Univ.


R>+ tv+ b+++>$ DI+ D- G e+++ h r+>+++ y+>++

Do you use the same blanks (Brand and type) that used to work fine under
6.1?

I have two cd burners at work. Yamaha CDR-400t under RH 5.1 and
Yamaha 8424S under 7.2 and they both work. Though CDR-400t
is a bit old and screws up a lot of blanks lately.

I see 0x2 rarely. Try different brand. TDK's from Costco work just fine.
As do FujiFilms from Fry's :-)

Verbatim DataLifePlus CD-RWs worked without a hitch under RH 6.1,
and always always have this problem under 7.2.  We also used Maxel
CD-R74s, also without a problem.  The CD-Rs I'm trying now
are TDK 700MB CDs, and they have exactly the same problem as the
Verbatim DataLifePlus CD-RWs that worked fine before.

Quote:>I see 0x2 rarely. Try different brand. TDK's from Costco work just fine.
>As do FujiFilms from Fry's :-)

--
P. Douglas Reeder     Lecturer, Dept. Computer/Info. Science, Ohio State Univ.


R>+ tv+ b+++>$ DI+ D- G e+++ h r+>+++ y+>++

Then it must be something with the recording program.
Try to statically link cdrecord or whatever you're using on a decent
Linux system (RH 6.1 is good enough) and install that executable on
that 7.2

(I must say though in all fairness to 7.2 that cdrecord that came with
7.2 is working fine on my linux box at work).

If that won't work I don't really know what could be the problem.
Kernel version maybe? If you can replace 2.4.7 whatever that came with
7.2 with 2.4.18 or something and try it out that will eliminate one
more possible source of your trouble.