If i understand it right there is a problem that cdrecord scans for some
reason( ?) the pg device which is normally not necessary in my
case(connection of the CD-RW via ieee1394 not via the Parallel Port). Is this
a bug in cdrecord and was addressed already(solved? and appear again?)? Can i
suppress the scanning of this pg-device in cdrecord somehow?
Thanks for your hints.
Wolfram
On Saturday 09 February 2002 10:56, Douglas Gilbert wrote:
> Carsten Neumann wrote:
> > On Fri, 08 Feb 2002, Joerg Schilling wrote:
> >>>From: Giuseppe Corbelli <[EMAIL PROTECTED]>
> >>>
> >>>>I try to setup a Rico MP9060A DVD/CD-RW drives via an external ieee1394
> >>>>connection. I have a 2.4.10 Kernel(Suse 7.3 distribution). When i load
> >>>> the kernelmodules for iee1394(ieee1394,ohci1394,sbp2) everything seems
> >>>> to be ok. I can mount CD's. The CD-Combo is detected as SCSI Drive 1.
> >>>>But when i start cdrecord(cdrecord -scanbus) the system hangs?
> >>>> According to the attached part of the /var/log/messages there is a
> >>>> problem with the paride/pg kernel module?
> >>>>
> >>>>
> >>>>Can somebody help me or had some similiar experience and found a way
> >>>> out?
> >>>
> >>>...
> >>>
> >>>>Feb 5 22:14:47 pc modprobe: modprobe: Can't locate module
> >>>> paride_protocol
> >>>
> >>>...
> >>>I have no direct experience but this line seems to suggest you need the
> >>>right low level module, as found in
> >>>Block Devices->Parallel Ide Protocol Modules
> >>
> >>If you really have IEEE1394 problems, write to a 1394 related Linux
> >> group.
> >>
> >>
> >>If you have problems with PP kernel error messages that should be
> >> suppressed by the Linux kernel write to Linux PAride.
> >>
> >>J�rg
> >
> > Is the FireWire interface indeed handled via the paride module?
>
> It is probably safe to assume that a cd reader or writer on
> an ieee1394 bus is using the "sbp2" protocol which is effectively
> the SCSI command set over 1394. [Actually sbp-2 is a SCSI standard,
> see www.t10.org ]
>
> From a Linux perspective this means various ieee1394 modules
> should be loaded, including sbp2. The sbp2 driver appears to
> the linux scsi subsystem as a lower level (pseudo) driver. Hence
> the writer is listed when you do "cat /proc/scsi/scsi". Cdrecord
> should then be able to access it (via the sg or sr drivers) just
> like any other scsi device. Note that this is similar to the
> way ATAPI (via the ide-scsi driver) and USB (via usb-storage)
> cd writers are accessed by cdrecord.
>
>
> Note than none of this has anything to do with the linux
> pg driver which is a pass through style driver (in that
> sense like sg) for the parallel port subsystem ("parport").
> In the past, I have exchanged emails with Joerg on
> the subject of the cdrecord scanning logic getting confused
> by some scsi devices which resulted in the pg interface
> being scanned. From memory that problem was addressed long
> ago.
>
>
> Hope this helps [and meets Carsten's literary standards :-)].
>
> Doug Gilbert
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
