cdrecord reports size vs. capabilities error....

cdrecord reports size vs. capabilities error....

[Jeff]

This I believed may have been asked before, but I am new to this list
and I hope I can get it resolved.
I have a IDE CDR as hdb and a IDE CDRW as hdc, no problem. I know in
order to use cdrecord I must use ide-scsi, no problem as I had this
exact same setup working with cdrecord when this was a 2.2.x system. Ok,
I upgrade the hard drive, hda, and install 2.4.5 kernel from Slackware
8.0. I always install just what I need,and install things as I need
them, usually from source. That's how you learn.
Ok, I need cdrecord working. No problem, I've done this before. Get the
cdrtools-1.10.tar.gz and have at. builds no problem. Build kernel with
scsi emulation, put the append command in lilo.conf, do the modules.conf
thing and link /dev/cdrom to /dev/scd0 and /dev/cdrw to /dev/scd1.
Reboot and I can mount both /dev/cdrom and /dev/cdrw as ro filesystems.
lsmod shows:
Module                  Size  Used by
isofs                  18032   1  (autoclean)
sr_mod                 13024   1  (autoclean)
sg                     21408   0  (autoclean)
ide-scsi                7904   1 
ide-cd                 26432   0 
cdrom                  27520   0  [sr_mod ide-cd]
scsi_mod               81904   3  (autoclean) [sr_mod sg ide-scsi]
3c59x                  24224   1 

Ok, I try cdrecord -scanbus, and get he following warning:
Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling
Linux sg driver version: 3.1.17
Using libscg version 'schily-0.5'
scsibus0:
cdrecord: Warning: controller returns wrong size for CD capabilities
page.
        0,0,0     0) 'E-IDE   ' 'CD-ROM 50X      ' '50  ' Removable
CD-ROM
        0,1,0     1) 'HP      ' 'CD-Writer+ 9100 ' '1.0c' Removable
CD-ROM
        0,2,0     2) *
        0,3,0     3) *
        0,4,0     4) *
        0,5,0     5) *
        0,6,0     6) *
        0,7,0     7) *
Where did the Warning: come from? Trying to burn from xcdroast causes an
error box stating the same and refuses to write.
I did everything like the cd writer how-to specifies, just like I did
before, I think? Did I miss something?

I google searched and found plenty of postings with the same problem,
but couldn't find any with the answer. One thing I did notice that they
all involved 2.4.x kernel. Is that  the problem?

Jeff
piercejhsd009@earthlink.net

Re: cdrecord reports size vs. capabilities error....

[Kristian Peters]

Jeff wrote:

> cdrecord: Warning: controller returns wrong size for CD capabilities
> page.
>         0,0,0     0) 'E-IDE   ' 'CD-ROM 50X      ' '50  ' Removable
> CD-ROM

Correct me if I'm wrong, but that looks like cdrecord doesn't recognize your 
cd-rom correctly. Do you have added that drive also to your lilo.conf ?

Normally it would be enough to load the modules without any specific parameters.

Could you post your dmesg-output + lilo.conf parameters if possible ?

*Kristian

Re: cdrecord reports size vs. capabilities error....

[Wakko Warner]

> > cdrecord: Warning: controller returns wrong size for CD capabilities
> > page.
> >         0,0,0     0) 'E-IDE   ' 'CD-ROM 50X      ' '50  ' Removable
> > CD-ROM

I get this same thing with a scsi cdrom at work.  I have 2 of the exact same
drives.  a Teac cd-535s v1.0a  the first one I get that message, the second
works.  However, the first one won't pull the tray back in via software.

> Correct me if I'm wrong, but that looks like cdrecord doesn't recognize your 
> cd-rom correctly. Do you have added that drive also to your lilo.conf ?
> 
> Normally it would be enough to load the modules without any specific parameters.
> 
> Could you post your dmesg-output + lilo.conf parameters if possible ?
-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

Re: cdrecord reports size vs. capabilities error....

[Kristian Peters]

Wakko Warner wrote:

> I get this same thing with a scsi cdrom at work.  I have 2 of the exact same
> drives.  a Teac cd-535s v1.0a  the first one I get that message, the second
> works.  However, the first one won't pull the tray back in via software.


Is the first drive connected to /dev/hdb ? Does eject work on /dev/scd0 or 
/dev/hdb ?

*Kristian

Re: cdrecord reports size vs. capabilities error....

[war]

That just means it is not a standard compliant CDRW drive.
I've asked Joerg Schilling about this and that's what he said.
I get the same thing.

Linux sg driver version: 3.1.20
Using libscg version 'schily-0.5'
scsibus0:
        0,0,0     0) *
        0,1,0     1) *
        0,2,0     2) 'IOMEGA  ' 'ZIP 100         ' 'J.03' Removable Disk
        0,3,0     3) 'MATSHITA' 'CD-ROM CR-8008  ' '8.0e' Removable CD-ROM
        0,4,0     4) *
        0,5,0     5) *
        0,6,0     6) *
        0,7,0     7) *
scsibus1:
        1,0,0   100) '        ' 'SMART100X/2400  ' '1.44' Removable CD-ROM
        1,1,0   101) 'PLEXTOR ' 'CD-R   PX-W1210A' '1.09' Removable CD-ROM
cdrecord: Warning: controller returns wrong size for CD capabilities page.
        1,2,0   102) 'MATSHITA' 'CD-ROM CR-581-M ' '1.05' Removable CD-ROM
        1,3,0   103) 'HP      ' 'CD-Writer+ 7500 ' '1.0a' Removable CD-ROM
        1,4,0   104) 'SONY    ' 'CD-ROM CDU77E-Q ' '1.3a' Removable CD-ROM
        1,5,0   105) *
        1,6,0   106) *
        1,7,0   107) *


Kristian Peters wrote:

> Wakko Warner wrote:
>
> > I get this same thing with a scsi cdrom at work.  I have 2 of the exact same
> > drives.  a Teac cd-535s v1.0a  the first one I get that message, the second
> > works.  However, the first one won't pull the tray back in via software.
>
> Is the first drive connected to /dev/hdb ? Does eject work on /dev/scd0 or
> /dev/hdb ?
>
> *Kristian
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: cdrecord reports size vs. capabilities error....

[Wakko Warner]

> > I get this same thing with a scsi cdrom at work.  I have 2 of the exact same
> > drives.  a Teac cd-535s v1.0a  the first one I get that message, the second
> > works.  However, the first one won't pull the tray back in via software.
> 
> 
> Is the first drive connected to /dev/hdb ? Does eject work on /dev/scd0 or 
> /dev/hdb ?

Those drives are scsi drives, not IDE.  they are the exact same drive but on
different scsi controllers.  I *HAVE* swapped them, it's the drive.

The scsi controllers are both adaptec aha-2940u cards.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

Re: cdrecord reports size vs. capabilities error....

[Wakko Warner]

> That just means it is not a standard compliant CDRW drive.
> I've asked Joerg Schilling about this and that's what he said.
> I get the same thing.
> 
> Linux sg driver version: 3.1.20
> Using libscg version 'schily-0.5'
> scsibus0:
>         0,0,0     0) *
>         0,1,0     1) *
>         0,2,0     2) 'IOMEGA  ' 'ZIP 100         ' 'J.03' Removable Disk
>         0,3,0     3) 'MATSHITA' 'CD-ROM CR-8008  ' '8.0e' Removable CD-ROM
>         0,4,0     4) *
>         0,5,0     5) *
>         0,6,0     6) *
>         0,7,0     7) *
> scsibus1:
>         1,0,0   100) '        ' 'SMART100X/2400  ' '1.44' Removable CD-ROM
>         1,1,0   101) 'PLEXTOR ' 'CD-R   PX-W1210A' '1.09' Removable CD-ROM
> cdrecord: Warning: controller returns wrong size for CD capabilities page.
>         1,2,0   102) 'MATSHITA' 'CD-ROM CR-581-M ' '1.05' Removable CD-ROM
>         1,3,0   103) 'HP      ' 'CD-Writer+ 7500 ' '1.0a' Removable CD-ROM
>         1,4,0   104) 'SONY    ' 'CD-ROM CDU77E-Q ' '1.3a' Removable CD-ROM
>         1,5,0   105) *
>         1,6,0   106) *
>         1,7,0   107) *

Ok, but why would having 2 identical cdroms be different?  they both have
the same firmware, yet cdrecord -scanbus shows one of them with the wrong
size thing.  There's 2 scsi controllers, but if I swap them, the wrong size
stays with the drive, not the controller.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

Re: cdrecord reports size vs. capabilities error....

[war]

Yeah, when I switched controllers etc it puts the message in different spots.
I'm not sure why it does that.
You'll have to ask the guy who wrote the driver I guess.


Wakko Warner wrote:

> > That just means it is not a standard compliant CDRW drive.
> > I've asked Joerg Schilling about this and that's what he said.
> > I get the same thing.
> >
> > Linux sg driver version: 3.1.20
> > Using libscg version 'schily-0.5'
> > scsibus0:
> >         0,0,0     0) *
> >         0,1,0     1) *
> >         0,2,0     2) 'IOMEGA  ' 'ZIP 100         ' 'J.03' Removable Disk
> >         0,3,0     3) 'MATSHITA' 'CD-ROM CR-8008  ' '8.0e' Removable CD-ROM
> >         0,4,0     4) *
> >         0,5,0     5) *
> >         0,6,0     6) *
> >         0,7,0     7) *
> > scsibus1:
> >         1,0,0   100) '        ' 'SMART100X/2400  ' '1.44' Removable CD-ROM
> >         1,1,0   101) 'PLEXTOR ' 'CD-R   PX-W1210A' '1.09' Removable CD-ROM
> > cdrecord: Warning: controller returns wrong size for CD capabilities page.
> >         1,2,0   102) 'MATSHITA' 'CD-ROM CR-581-M ' '1.05' Removable CD-ROM
> >         1,3,0   103) 'HP      ' 'CD-Writer+ 7500 ' '1.0a' Removable CD-ROM
> >         1,4,0   104) 'SONY    ' 'CD-ROM CDU77E-Q ' '1.3a' Removable CD-ROM
> >         1,5,0   105) *
> >         1,6,0   106) *
> >         1,7,0   107) *
>
> Ok, but why would having 2 identical cdroms be different?  they both have
> the same firmware, yet cdrecord -scanbus shows one of them with the wrong
> size thing.  There's 2 scsi controllers, but if I swap them, the wrong size
> stays with the drive, not the controller.
>
> --
>  Lab tests show that use of micro$oft causes cancer in lab animals

Re: cdrecord reports size vs. capabilities error....

[Jeff]

I guess the problem was in my module.conf file, I forgot to add alias
scd1 sr_mod. I didn't remember the capabilities error from before. The
warning is still there in scanbus, but everything is now working
correctly.
Thanks to everybody for their help.

war wrote:
> 
> Yeah, when I switched controllers etc it puts the message in different spots.
> I'm not sure why it does that.
> You'll have to ask the guy who wrote the driver I guess.
> 
> Wakko Warner wrote:
> 
> > > That just means it is not a standard compliant CDRW drive.
> > > I've asked Joerg Schilling about this and that's what he said.
> > > I get the same thing.
> > >
> > > Linux sg driver version: 3.1.20
> > > Using libscg version 'schily-0.5'
> > > scsibus0:
> > >         0,0,0     0) *
> > >         0,1,0     1) *
> > >         0,2,0     2) 'IOMEGA  ' 'ZIP 100         ' 'J.03' Removable Disk
> > >         0,3,0     3) 'MATSHITA' 'CD-ROM CR-8008  ' '8.0e' Removable CD-ROM
> > >         0,4,0     4) *
> > >         0,5,0     5) *
> > >         0,6,0     6) *
> > >         0,7,0     7) *
> > > scsibus1:
> > >         1,0,0   100) '        ' 'SMART100X/2400  ' '1.44' Removable CD-ROM
> > >         1,1,0   101) 'PLEXTOR ' 'CD-R   PX-W1210A' '1.09' Removable CD-ROM
> > > cdrecord: Warning: controller returns wrong size for CD capabilities page.
> > >         1,2,0   102) 'MATSHITA' 'CD-ROM CR-581-M ' '1.05' Removable CD-ROM
> > >         1,3,0   103) 'HP      ' 'CD-Writer+ 7500 ' '1.0a' Removable CD-ROM
> > >         1,4,0   104) 'SONY    ' 'CD-ROM CDU77E-Q ' '1.3a' Removable CD-ROM
> > >         1,5,0   105) *
> > >         1,6,0   106) *
> > >         1,7,0   107) *
> >
> > Ok, but why would having 2 identical cdroms be different?  they both have
> > the same firmware, yet cdrecord -scanbus shows one of them with the wrong
> > size thing.  There's 2 scsi controllers, but if I swap them, the wrong size
> > stays with the drive, not the controller.
> >
> > --
> >  Lab tests show that use of micro$oft causes cancer in lab animals
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Jeff
piercejhsd009@earthlink.net