On Mon, Oct 16 2000, Andre Hedrick wrote:
> > I if cdrecord bypassed the sg driver and spoke to the
> > cdrom driver directly. I know the CDROM_SEND_PACKET
> > ioctl() is in place for lk 2.4 but from which version
> > has it been functional in the lk 2.2 series?
>
> But the write command is not
On Mon, Oct 16 2000, Mark Cooke wrote:
> > Yes but there is a way to do this directly now, the question is can the
> > user-space apps change to go both ways.
>
> Hi Andre,
>
> Is there any tool / test code that you know of to 'do this directly' -
> I'm wanting to try to avoid ade-scsi
On Mon, Oct 16 2000, Douglas Gilbert wrote:
> As far as I know, cdrecord interfaces to Linux either
> via the sg or pg devices. No-one would be happier than
> I if cdrecord bypassed the sg driver and spoke to the
> cdrom driver directly. I know the CDROM_SEND_PACKET
> ioctl() is in place for lk
On Mon, Oct 16 2000, Mark Cooke wrote:
Yes but there is a way to do this directly now, the question is can the
user-space apps change to go both ways.
Hi Andre,
Is there any tool / test code that you know of to 'do this directly' -
I'm wanting to try to avoid ade-scsi translation, and
On Mon, Oct 16 2000, Douglas Gilbert wrote:
As far as I know, cdrecord interfaces to Linux either
via the sg or pg devices. No-one would be happier than
I if cdrecord bypassed the sg driver and spoke to the
cdrom driver directly. I know the CDROM_SEND_PACKET
ioctl() is in place for lk 2.4
On Mon, Oct 16 2000, Andre Hedrick wrote:
I if cdrecord bypassed the sg driver and spoke to the
cdrom driver directly. I know the CDROM_SEND_PACKET
ioctl() is in place for lk 2.4 but from which version
has it been functional in the lk 2.2 series?
But the write command is not included
On Tue, 17 Oct 2000, Joerg Schilling wrote:
>However it may be a broken hp7100: I suspect that all drives ever
>made are now dead because of bad quality.
Mine still works as a reader. ;)
Attempting to actually write produces a lovely "power calibration failed"
and a coaster faster than you can
>From [EMAIL PROTECTED] Tue Oct 17 01:14:32 2000
>1.8.1. A ricoh 9060 on a machine running identical kernel build /
>cdrecord binary works fine>
>I just finished compiling cdrecord-1.8.1 with debug enabled. The two
>attached log files are from the hp7100i / smp / 2.2.18pre15, and the
>ricoh
On Tue, 17 Oct 2000, Joerg Schilling wrote:
However it may be a broken hp7100: I suspect that all drives ever
made are now dead because of bad quality.
Mine still works as a reader. ;)
Attempting to actually write produces a lovely "power calibration failed"
and a coaster faster than you can
On Mon, 16 Oct 2000, Douglas Gilbert wrote:
> Sg has an ioctl called SG_SET_TRANSFORM which is only
> relevant to the ide-scsi driver. As far as I know, no
> applications use it. Still it is not clear why Mark's
> system would work on a UP machine but fail on a SMP box.
Hi Douglas, Jörg, all,
On Mon, 16 Oct 2000, Douglas Gilbert wrote:
> I if cdrecord bypassed the sg driver and spoke to the
> cdrom driver directly. I know the CDROM_SEND_PACKET
> ioctl() is in place for lk 2.4 but from which version
> has it been functional in the lk 2.2 series?
But the write command is not included
Mark Cooke wrote:
> On Mon, 16 Oct 2000, Andre Hedrick wrote:
>
> > Yes but there is a way to do this directly now, the question is can the
> > user-space apps change to go both ways.
>
> Hi Andre,
>
> Is there any tool / test code that you know of to 'do this directly' -
> I'm wanting to try to
On Mon, 16 Oct 2000, Andre Hedrick wrote:
> Yes but there is a way to do this directly now, the question is can the
> user-space apps change to go both ways.
Hi Andre,
Is there any tool / test code that you know of to 'do this directly' -
I'm wanting to try to avoid ade-scsi translation, and
On Mon, 16 Oct 2000, Ricky Beam wrote:
> There are specific notes about the HP 7100 drives not working corectly due
> to bad command translations. That was supposed to have been fixed years
> ago.
Hi Ricky,
And I know it was working on this very machine some time in the past
with a 2.2.x.
On Mon, 16 Oct 2000, Alan Cox wrote:
> > >Its a message from the drive politely requesting cd-record to talk valid
> > >commands. But as ide-scsi touches some commands (remapping old ones that are
> > >not supported on ATAPI) its possible to be kernel
> >
> > Umm, doesn't cdrecord know how to
On Mon, 16 Oct 2000, Alan Cox wrote:
>> Umm, doesn't cdrecord know how to address IDE devices directly?
>
>IDE cd burners talk ATAPI. ATAPI is just a scsi variant. SCSI won the battle
>at the protocol level
...
Yeah yeah yeah. What I meant was "you don't have to use ide-scsi." However,
after
> >Its a message from the drive politely requesting cd-record to talk valid
> >commands. But as ide-scsi touches some commands (remapping old ones that are
> >not supported on ATAPI) its possible to be kernel
>
> Umm, doesn't cdrecord know how to address IDE devices directly?
IDE cd burners
On Mon, 16 Oct 2000, Alan Cox wrote:
>> is in cdrecord itself, since I have seen that if the FIFO ever hits 0%
>> during CD burning, cdrecord has a tendency to bomb. =20
>
>If you empty the fifo and the drive fifo you burn a coaster. Thats a feature
>of CD burning and one reason I use 640Mb
I hope yu get some progress. I just saw mine bomb again at spped=4...
Jeff
Mark Cooke wrote:
>
> Hi Jeff, Alan, Jens,
>
> Thank you all for the replies. I guess I'll try to contact
> appropriate people at HP / try newer/older versions of cdrecord. I do
> know the drive was working with
Hi Jeff, Alan, Jens,
Thank you all for the replies. I guess I'll try to contact
appropriate people at HP / try newer/older versions of cdrecord. I do
know the drive was working with 2.2. a long time back.
It's just rare I use the burner.
One other thing that may be relevent - the HP doesn't
On Mon, 16 Oct 2000, Alan Cox wrote:
is in cdrecord itself, since I have seen that if the FIFO ever hits 0%
during CD burning, cdrecord has a tendency to bomb. =20
If you empty the fifo and the drive fifo you burn a coaster. Thats a feature
of CD burning and one reason I use 640Mb magneto
On Mon, 16 Oct 2000, Alan Cox wrote:
Umm, doesn't cdrecord know how to address IDE devices directly?
IDE cd burners talk ATAPI. ATAPI is just a scsi variant. SCSI won the battle
at the protocol level
...
Yeah yeah yeah. What I meant was "you don't have to use ide-scsi." However,
after
On Mon, 16 Oct 2000, Alan Cox wrote:
Its a message from the drive politely requesting cd-record to talk valid
commands. But as ide-scsi touches some commands (remapping old ones that are
not supported on ATAPI) its possible to be kernel
Umm, doesn't cdrecord know how to address IDE
On Mon, 16 Oct 2000, Ricky Beam wrote:
snip
There are specific notes about the HP 7100 drives not working corectly due
to bad command translations. That was supposed to have been fixed years
ago.
Hi Ricky,
And I know it was working on this very machine some time in the past
with a 2.2.x.
On Mon, 16 Oct 2000, Andre Hedrick wrote:
Yes but there is a way to do this directly now, the question is can the
user-space apps change to go both ways.
Hi Andre,
Is there any tool / test code that you know of to 'do this directly' -
I'm wanting to try to avoid ade-scsi translation, and
Mark Cooke wrote:
On Mon, 16 Oct 2000, Andre Hedrick wrote:
Yes but there is a way to do this directly now, the question is can the
user-space apps change to go both ways.
Hi Andre,
Is there any tool / test code that you know of to 'do this directly' -
I'm wanting to try to avoid
On Mon, 16 Oct 2000, Douglas Gilbert wrote:
I if cdrecord bypassed the sg driver and spoke to the
cdrom driver directly. I know the CDROM_SEND_PACKET
ioctl() is in place for lk 2.4 but from which version
has it been functional in the lk 2.2 series?
But the write command is not included in
On Mon, 16 Oct 2000, Douglas Gilbert wrote:
snip
Sg has an ioctl called SG_SET_TRANSFORM which is only
relevant to the ide-scsi driver. As far as I know, no
applications use it. Still it is not clear why Mark's
system would work on a UP machine but fail on a SMP box.
Hi Douglas, Jörg, all,
Alan Cox wrote:
>
> > is in cdrecord itself, since I have seen that if the FIFO ever hits 0%
> > during CD burning, cdrecord has a tendency to bomb. =20
>
> If you empty the fifo and the drive fifo you burn a coaster. Thats a feature
> of CD burning and one reason I use 640Mb magneto opticals
On Mon, Oct 16 2000, Mark Cooke wrote:
> Identifikation : 'CD-Writer+ 7100 '
>
> Blanking entire disk
> CDB: A1 00 00 00 00 00 00 00 00 00 00 00
> cdrecord: Input/output error. blank unit: scsi sendcmd: retryable error
> Sense Bytes: F0 00 05 00 00 00 00 19 00 02 89 16 A1 10 00 80
> status: 0x2
> is in cdrecord itself, since I have seen that if the FIFO ever hits 0%
> during CD burning, cdrecord has a tendency to bomb. =20
If you empty the fifo and the drive fifo you burn a coaster. Thats a feature
of CD burning and one reason I use 640Mb magneto opticals for testing CD
stuff
> >
This is bad. I am seeing problems as well, but speed=2 and even speed=4
are working here non 2.2.18 with both CDRW and CD-RW/DVD Ram. You may
have a hardware problem of some type, or perhaps the bug is more easily
reproducable for you. I have noticed that perhaps some of the problem
is in
Hi all,
Just to follow up on an earlier message / thread. I've updated to
2.2.18pre15 on the machine (dual celeron, gigabyte 6bxd) I was having
trouble writing CDRWs to, and it has made no difference,
unfortunately.
With the same tools / os on my other cdrw equipped machine
(k7/up/ricoh 9060)
Hi all,
Just to follow up on an earlier message / thread. I've updated to
2.2.18pre15 on the machine (dual celeron, gigabyte 6bxd) I was having
trouble writing CDRWs to, and it has made no difference,
unfortunately.
With the same tools / os on my other cdrw equipped machine
(k7/up/ricoh 9060)
Alan Cox wrote:
is in cdrecord itself, since I have seen that if the FIFO ever hits 0%
during CD burning, cdrecord has a tendency to bomb. =20
If you empty the fifo and the drive fifo you burn a coaster. Thats a feature
of CD burning and one reason I use 640Mb magneto opticals for
35 matches
Mail list logo
