>From [EMAIL PROTECTED] Mon Feb 9 23:12:23 2004
>> Especially if the sense code is NO SENSE. Logically that should
>> indicate the driver needed to find out whether or not there was error,
>> and it learned that there wasn't.
>For tape drives, sense key == NO SENSE is not equivalent to no erro
> Especially if the sense code is NO SENSE. Logically that should
> indicate the driver needed to find out whether or not there was error,
> and it learned that there wasn't.
For tape drives, sense key == NO SENSE is not equivalent to no error to
report. Often a tape drive returns a sense key of
On 9 Feb 2004, James Bottomley wrote:
> OK, if you want to understand what the mid-layer problem is, look at
> scsi_finish_command(). You see in there we set DRIVER_SENSE if we find
> any valid sense code in the sense buffer (including NO SENSE)
>
> We will return this to the user as a sense err
On Mon, Feb 09, 2004 at 11:50:13AM -0500, James Bottomley wrote:
> On Mon, 2004-02-09 at 11:40, Alan Stern wrote:
> > In the absence of anything better, we're forced to assume "bad" status
> > corresponds to Check Condition...
> >
> > What do you think, Matt? Should we remove the auto-sense for
On Mon, 2004-02-09 at 11:40, Alan Stern wrote:
> In the absence of anything better, we're forced to assume "bad" status
> corresponds to Check Condition...
>
> What do you think, Matt? Should we remove the auto-sense for short
> transfers when we get "good" status? Bearing in mind that it's
>
On Fri, 6 Feb 2004, Matthew Dharm wrote:
> On Fri, Feb 06, 2004 at 10:24:25AM -0500, James Bottomley wrote:
> > On Fri, 2004-02-06 at 09:59, Alan Stern wrote:
> > > Who says it's wrong to retrieve sense information when there is an
> > > underrun but not Check Condition? Can you provide a referen
On Fri, Feb 06, 2004 at 10:24:25AM -0500, James Bottomley wrote:
> On Fri, 2004-02-06 at 09:59, Alan Stern wrote:
> > Who says it's wrong to retrieve sense information when there is an
> > underrun but not Check Condition? Can you provide a reference to a
> > published (or draft) document that sta
On Fri, 2004-02-06 at 09:59, Alan Stern wrote:
> Who says it's wrong to retrieve sense information when there is an
> underrun but not Check Condition? Can you provide a reference to a
> published (or draft) document that states this?
It's not wrong according to the SCSI standards, a REQUEST SENS
>From [EMAIL PROTECTED] Fri Feb 6 15:59:52 2004
>> But as you may know, there is a Linux bug that causes the status to be 0 when
>> sense data (correctly) is available. Libscg _needs_ to add a workarounf for
>> this bug or nothing would work!
>What bug is that? Or rather, under what circumsta
On Fri, 6 Feb 2004, Thomas J Magliery PhD wrote:
> Alan, to sum up, do I understand correctly that there either needs to be
> a change to cdrecord-ProDVD, the sg driver, or the Plextor firmware?
> Any recommndations on which is best, and who I would talk to about the
> latter two?
There's no
On Fri, 6 Feb 2004, Joerg Schilling wrote:
> What you see, is that some instance in the Linux kernel completely
> misshandles this transfer:
>
> - The drive seems to return only 34 bytes although it did advertise
> to return 36.
>
> The correct behavior for Linux would be to set
>From [EMAIL PROTECTED] Fri Feb 6 06:21:39 2004
>Alan, to sum up, do I understand correctly that there either needs to be
>a change to cdrecord-ProDVD, the sg driver, or the Plextor firmware?
> Any recommndations on which is best, and who I would talk to about the
>latter two?
libscg cannot
>From [EMAIL PROTECTED] Thu Feb 5 23:05:03 2004
>The drive was asked for 36 bytes and only returned 34. So far as the
>low-level USB and SCSI transfer goes, that's legal -- the device is only
>obligated to transfer as much data as it has available.
>> > usb-storage: Bulk data transfer result 0
>From [EMAIL PROTECTED] Thu Feb 5 21:13:20 2004
>> usb-storage: Command READ DISC INFORMATION (10 bytes)
>> usb-storage: 51 00 00 00 00 00 00 00 24 00 00 00
>> usb-storage: Bulk command S 0x43425355 T 0xac Trg 0 LUN 0 L 36 F 128 CL 12
>> usb-storage: Bulk command transfer result=0
>> usb-storage
>From [EMAIL PROTECTED] Thu Feb 5 06:52:18 2004
>OK, I finally was able to recompile my kernel with usb and usb-storage
>debugging on. For reference, here is the output of the cdrecord
>command. There is a blank DVD-R in the drive. It is actually a Plextor
>PX-708UF drive hooked up through
Alan, to sum up, do I understand correctly that there either needs to be
a change to cdrecord-ProDVD, the sg driver, or the Plextor firmware?
Any recommndations on which is best, and who I would talk to about the
latter two?
Below, I ran the test you suggested.
Thanks,
Tom
Alan Stern wrote:
I
On Thu, 5 Feb 2004, Andy Polyakov wrote:
> > usb-storage: Command READ DISC INFORMATION (10 bytes)
> > usb-storage: 51 00 00 00 00 00 00 00 24 00 00 00
> > usb-storage: Bulk command S 0x43425355 T 0xac Trg 0 LUN 0 L 36 F 128 CL 12
> > usb-storage: Bulk command transfer result=0
> > usb-storage: us
> > usb-storage: Command READ DISC INFORMATION (10 bytes)
> > usb-storage: 51 00 00 00 00 00 00 00 24 00 00 00
> > usb-storage: Bulk command S 0x43425355 T 0xac Trg 0 LUN 0 L 36 F 128 CL 12
> > usb-storage: Bulk command transfer result=0
> > usb-storage: usb_stor_transfer_partial(): xfer 36 bytes
>
> usb-storage: Command READ DISC INFORMATION (10 bytes)
> usb-storage: 51 00 00 00 00 00 00 00 24 00 00 00
> usb-storage: Bulk command S 0x43425355 T 0xac Trg 0 LUN 0 L 36 F 128 CL 12
> usb-storage: Bulk command transfer result=0
> usb-storage: usb_stor_transfer_partial(): xfer 36 bytes
> usb-stora
On Wed, 28 Jan 2004, Thomas J Magliery PhD wrote:
> Hi Alan,
>
> Thanks for the reply. Does this mean recompile the kernel with usb-storage
> debugging, or is there a way to turn it on without recompiling?
You have to recompile the kernel. Or, if you already have the kernel
sources installed
Regarding my problem using the Plextor PX-708UF (USB 2.0) to burn DVD+R
media using cdrecord-ProDVD, I received the following from Andy Polyakov
(writer of dvd+/-rw-tools, which includes growisofs, which does work for
me):
> I guess the other question is: what is passing the e
Hi Alan,
Thanks for the reply. Does this mean recompile the kernel with usb-storage
debugging, or is there a way to turn it on without recompiling? I'm not
exactly a linux expert--I've never compiled a kernel. I will take a stab at
it if you think it's the best thing. Any instructions and/or a
On Wed, 28 Jan 2004, Thomas J. Magliery, Ph.D. wrote:
> David Brownell suggested that someone on this list might be able to help me.
> I am having trouble burning DVDs using a USB 2.0-connected burner, and I
> think USB might be the problem.
>
> I have a desktop PC running linux (Asus A7V333, AMD
23 matches
Mail list logo
