On Sun, 2003-11-02 at 01:09, Charlie wrote:
> On Sun, 2 Nov 2003 01:08 pm, many eyes noted that James Sparenberg wrote:
> 
> <snip>
> > > So I took a panel of the box, left the CD drives where they were, but
> > > just jumpered the writer as slave again, and the reader as master.
> > > Invoked k3b, it now recognised the writer as such and the reader
> > > correctly also. The reader still worked and the writer with k3b burned
> > > CD's without and trouble.
> > >
> > > Thought I would pass this on in case it might help anyone that was having
> > > trouble with k3b not recognising writers>
> > >
> > > Charlie.
> >
> > Charlie this almost sounds like a problem FreeBSD had around the time of
> > 2.7/2.8 In order to do a media install from CD the Reader had to be
> > slave to the drive you intended to install on. Curiosity here.  If they
> > are in the position of being two readers (as far as k3b is concerned
> > what is the output of cdrecord -scanbus ?  I'm curious if the problem is
> > in k3b or lower down in cdrecord.
> >
> > James
> 
> Sorry James, because I didn't know to do that and even now don't know what it 
> shows; I didn't try that to find out whatever information it displays. But 
> here is is as it is now, though it might be no help :-
> 
> [EMAIL PROTECTED] root]# cdrecord -scanbus
> Cdrecord 2.0 (i586-mandrake-linux-gnu) Copyright (C) 1995-2002 J�rg Schilling
> Linux sg driver version: 3.1.24
> Using libscg version 'schily-0.7'
> scsibus0:
>         0,0,0     0) 'LITE-ON ' 'LTR-40125S      ' 'ZS0N' Removable CD-ROM
>         0,1,0     1) *
>         0,2,0     2) *
>         0,3,0     3) *
>         0,4,0     4) *
>         0,5,0     5) *
>         0,6,0     6) *
>         0,7,0     7) *
> [EMAIL PROTECTED] root]#
> 
> Charlie.

hmmm it would seem that in this configuration cdrecord is able to find
the drive ok.   Now I'm going to ask the group as a whole.  Given the
above should Charlie submit a bug on k3b?

James



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to