On Mon, Dec 03, 2007 at 08:54:09PM -0800, Matthew Dharm wrote:
> On Fri, Nov 30, 2007 at 05:14:42PM -0800, Greg KH wrote:
> > If anyone has the git id for the current U3 patch, I'll be glad to
> > revert it.
>
> Greg --
>
> Are you reverting this or should someone generate a patch?
I'll revert t
On Fri, Nov 30, 2007 at 05:14:42PM -0800, Greg KH wrote:
> If anyone has the git id for the current U3 patch, I'll be glad to
> revert it.
Greg --
Are you reverting this or should someone generate a patch?
Matt
--
Matthew Dharm Home: [EMAIL PROTECTED]
Maintainer,
On Fri, 2007-11-30 at 17:14 -0800, Greg KH wrote:
> On Fri, Nov 30, 2007 at 07:56:09PM -0500, Ben Collins wrote:
> >
> > On Fri, 2007-11-30 at 12:46 -0800, Matthew Dharm wrote:
> > > (Adding Ben Collins, who put another U3 patch into the system.)
> > >
> > > On Fri, Nov 30, 2007 at 08:40:25PM +0
On Fri, Nov 30, 2007 at 08:40:42PM -0500, Kyle McMartin wrote:
> On Fri, Nov 30, 2007 at 05:14:42PM -0800, Greg KH wrote:
> > I agree with Matt, this should not be done in the kernel. If you don't
> > like seeing the additional LUN, which is really present in the device,
> > do something in HAL or
On Fri, Nov 30, 2007 at 05:14:42PM -0800, Greg KH wrote:
> I agree with Matt, this should not be done in the kernel. If you don't
> like seeing the additional LUN, which is really present in the device,
> do something in HAL or your window manager. That kind of "policy"
> should not be in the usb
On Fri, Nov 30, 2007 at 05:14:42PM -0800, Greg KH wrote:
> On Fri, Nov 30, 2007 at 07:56:09PM -0500, Ben Collins wrote:
> >
> > On Fri, 2007-11-30 at 12:46 -0800, Matthew Dharm wrote:
> > > (Adding Ben Collins, who put another U3 patch into the system.)
> > >
> > > On Fri, Nov 30, 2007 at 08:40:2
On Fri, Nov 30, 2007 at 07:56:09PM -0500, Ben Collins wrote:
>
> On Fri, 2007-11-30 at 12:46 -0800, Matthew Dharm wrote:
> > (Adding Ben Collins, who put another U3 patch into the system.)
> >
> > On Fri, Nov 30, 2007 at 08:40:25PM +0100, Hans de Goede wrote:
> > > David Brown wrote:
> > > > On F
On Fri, 2007-11-30 at 12:46 -0800, Matthew Dharm wrote:
> (Adding Ben Collins, who put another U3 patch into the system.)
>
> On Fri, Nov 30, 2007 at 08:40:25PM +0100, Hans de Goede wrote:
> > David Brown wrote:
> > > On Fri, Nov 30, 2007 at 10:55:09AM -0800, Matthew Dharm wrote:
> > >
> > >> Th
(Adding Ben Collins, who put another U3 patch into the system.)
On Fri, Nov 30, 2007 at 08:40:25PM +0100, Hans de Goede wrote:
> David Brown wrote:
> > On Fri, Nov 30, 2007 at 10:55:09AM -0800, Matthew Dharm wrote:
> >
> >> This is overly complex, and doesn't really solve anything. The fake
> >
David Brown wrote:
> On Fri, Nov 30, 2007 at 10:55:09AM -0800, Matthew Dharm wrote:
>
>> This is overly complex, and doesn't really solve anything. The fake
>> CD-ROM
>> is there. Who knows what's on it? If the desktop wants to ignore it,
>> that's fine... but as a transport-oriented driver, u
On Fri, Nov 30, 2007 at 10:55:09AM -0800, Matthew Dharm wrote:
>This is overly complex, and doesn't really solve anything. The fake CD-ROM
>is there. Who knows what's on it? If the desktop wants to ignore it,
>that's fine... but as a transport-oriented driver, usb-storage should
>cleanly transp
On Fri, Nov 30, 2007 at 07:38:12PM +0100, Hans de Goede wrote:
> Matthew Dharm wrote:
> > On Fri, Nov 30, 2007 at 10:35:56AM -0500, Kyle McMartin wrote:
> >> On Fri, Nov 30, 2007 at 12:33:28AM -0800, Matthew Dharm wrote:
> >>> Someone remind me again why we bother masking out the fake CD-ROM in the
Matthew Dharm wrote:
> On Fri, Nov 30, 2007 at 10:35:56AM -0500, Kyle McMartin wrote:
>> On Fri, Nov 30, 2007 at 12:33:28AM -0800, Matthew Dharm wrote:
>>> Someone remind me again why we bother masking out the fake CD-ROM in these
>>> devices?
>>>
>> It's confusing to users, and completely useless
On Fri, Nov 30, 2007 at 10:35:56AM -0500, Kyle McMartin wrote:
> On Fri, Nov 30, 2007 at 12:33:28AM -0800, Matthew Dharm wrote:
> > Someone remind me again why we bother masking out the fake CD-ROM in these
> > devices?
> >
>
> It's confusing to users, and completely useless -- it's added by the
Mark Lord wrote:
> Mark Lord wrote:
>> Something may be broken in USB / usb-storage land.
>>
>> I've got a 2GB USB stick here.
>> I want to copy it to an image file on my hard drive:
>>
>>cat /dev/sdb > usbkey.image1
>>
>> Make a second copy, with or without unplugging/replugging the stick:
>>
Mark Lord wrote:
> Something may be broken in USB / usb-storage land.
>
> I've got a 2GB USB stick here.
> I want to copy it to an image file on my hard drive:
>
>cat /dev/sdb > usbkey.image1
>
> Make a second copy, with or without unplugging/replugging the stick:
>
>cat /dev/sdb > usbk
On Sat, 10 Nov 2007, Mark Lord wrote:
> Something may be broken in USB / usb-storage land.
>
> I've got a 2GB USB stick here.
> I want to copy it to an image file on my hard drive:
>
> cat /dev/sdb > usbkey.image1
>
> Make a second copy, with or without unplugging/replugging the stick:
>
>
Something may be broken in USB / usb-storage land.
I've got a 2GB USB stick here.
I want to copy it to an image file on my hard drive:
cat /dev/sdb > usbkey.image1
Make a second copy, with or without unplugging/replugging the stick:
cat /dev/sdb > usbkey.image2
After doing this, the tw
On Sun, 9 Sep 2007, Peter Rasmussen wrote:
> OK, I added that change as well, and it seems to make mount'ing and
> accessing the mobile and its micro-SD card much more stable.
> However, as the fixes are adding an unusual device and otherwise
> removing checks in the code, it isn't the way to go
Alan Stern wrote:
> On Sat, 8 Sep 2007, Peter Rasmussen wrote:
>
>
>>> Did you also make the change to usb-storage for ignoring wrong Tag
>>> values?
>>>
>>>
>>>
>> I'm not sure what you mean,
>>
>
> See: http://marc.info/?l=linux-usb-users&m=118859379130423&w=2
>
>
OK, I ad
On Sat, 8 Sep 2007, Peter Rasmussen wrote:
> > Did you also make the change to usb-storage for ignoring wrong Tag
> > values?
> >
> >
> I'm not sure what you mean,
See: http://marc.info/?l=linux-usb-users&m=118859379130423&w=2
> > Evidently the phone didn't report that the micro-SD card wa
Alan Stern wrote:
> On Sat, 8 Sep 2007, Peter Rasmussen wrote:
>
>
>>> In fact there was another patch from earlier in the email thread, which
>>> was needed to work around the PQ = 1 problem. Since you didn't apply
>>> that patch, the SCSI disk driver wasn't bound to your Z6.
>>>
>>>
>>>
On Sat, 8 Sep 2007, Peter Rasmussen wrote:
> > In fact there was another patch from earlier in the email thread, which
> > was needed to work around the PQ = 1 problem. Since you didn't apply
> > that patch, the SCSI disk driver wasn't bound to your Z6.
> >
> >
> Now I applied that patch, to
Alan Stern wrote:
> On Fri, 7 Sep 2007, Peter Rasmussen wrote:
>
>
>> I'm sorry if this is a little late, but I had once had access to a Z6
>> and believe I had it successfully connected to my Linux host, and was
>> therefore puzzled by this message exchange.
>>
>> I have now borrowed the devi
On Fri, 7 Sep 2007, Peter Rasmussen wrote:
> I'm sorry if this is a little late, but I had once had access to a Z6
> and believe I had it successfully connected to my Linux host, and was
> therefore puzzled by this message exchange.
>
> I have now borrowed the device again for the weekend to ch
I'm sorry if this is a little late, but I had once had access to a Z6
and believe I had it successfully connected to my Linux host, and was
therefore puzzled by this message exchange.
I have now borrowed the device again for the weekend to check it out a
little more.
Using Alan's patch below,
On Sat, 1 Sep 2007, Andreas Koenecke wrote:
> I' done this, too.
> The non-debug-messages are now:
>
> Sep 1 13:09:17 kocom kernel: usb 3-1: new high speed USB device using
> ehci_hcd and address 12
> Sep 1 13:09:17 ko
* Freitag, 31. August 2007 um 16:56 (-0400) schrieb Alan Stern:
>
> All those reset messages are caused by a bug in the device. Every
> command sent to the device is labelled with a "Tag" value; it shows up
> in the debugging log on each "Bulk Command" line as the number
> following the T. Fo
On Fri, 31 Aug 2007, Andreas Koenecke wrote:
> * Mittwoch, 29. August 2007 um 10:07 (-0400) schrieb Alan Stern:
> >
> > You can edit the source code of the SCSI core to make it ignore the PQ
> > value. In the file drivers/scsi/scsi_sysfs.c, find the
> > scsi_bus_match() routine and change the
* Mittwoch, 29. August 2007 um 10:07 (-0400) schrieb Alan Stern:
>
> You can edit the source code of the SCSI core to make it ignore the PQ
> value. In the file drivers/scsi/scsi_sysfs.c, find the
> scsi_bus_match() routine and change the last line from:
>
> return (sdp->inq_periph_qual
On Tue, 28 Aug 2007, Andreas Koenecke wrote:
> * Dienstag, 28. August 2007 um 14:48 (-0600) schrieb Matthew Wilcox:
> >
> > On Tue, Aug 28, 2007 at 04:45:59PM -0400, Alan Stern wrote:
> > > Can any SCSI experts explain what's going wrong here?
> >
> > It's the PQ 1 -- the device is telling us th
> > $ cat /proc/partitions
> --
> major minor #blocks name
>
>3 0 120060864 hda
>3 1 19543041 hda1
>3 2 1 hda2
>3 59775521 hda5
>3 6 987966 hda6
>3 7
* James Shatto wrote:
>
> It would probably help to have .config and lsmod details.
>
>$ lsmod
Module Size Used by
nls_iso8859_1 3840 0
nls_cp850 4672 0
videodev 27200 0
v4l2_comm
* Dienstag, 28. August 2007 um 14:48 (-0600) schrieb Matthew Wilcox:
>
> On Tue, Aug 28, 2007 at 04:45:59PM -0400, Alan Stern wrote:
> > Can any SCSI experts explain what's going wrong here?
>
> It's the PQ 1 -- the device is telling us that it's not actually there
> right now.
Is anything I can
Can any SCSI experts explain what's going wrong here?
Alan Stern
-- Forwarded message --
Date: Tue, 28 Aug 2007 22:13:16 +0200
From: Andreas Koenecke <[EMAIL PROTECTED]>
To: USB users list
Cc: [EMAIL PROTECTED]
Subject: Re: [Linux-usb-users] usb-storage and
On Tue, Aug 28, 2007 at 04:45:59PM -0400, Alan Stern wrote:
> Can any SCSI experts explain what's going wrong here?
It's the PQ 1 -- the device is telling us that it's not actually there
right now.
> > > > Aug 28 09:54:33 kocom kernel: scsi 4:0:0:0: Direct-Access Motorola
> > > > MSnc.
> > >
> > Everything looks correct except that sd_mod isn't
> > loaded.
>
> sd_mod is build fix into the kernel because of the
> real SCSI card. All other usb-storage devices
> (flash sticks, card reader and USB HDDs) are working
> without problems.
>
> I connected the phone to a complete different com
* Dienstag, 28. August 2007 um 15:13 (-0400) schrieb Alan Stern:
>
> > > Aug 28 09:54:33 kocom kernel: usb-storage: device scan complete
> > >
> > > Aug 28 09:54:33 kocom kernel: scsi 4:0:0:0: Direct-Access Motorola
> > > MSnc.
> > > PQ: 1 ANSI: 0 CCS
> > >
> > > Aug 28 09:54:33 kocom kernel
* Dienstag, 28. August 2007 um 20:39 (+0200) schrieb Peter Rasmussen:
>
> I can't see from your post what is missing, but I have myself had access to a
> Z6 (Linux based by the way) and it worked well with
> regard to copying files between the phone, it's microSD card and my Linux
> PC.
I wish
On Tue, 28 Aug 2007, Peter Rasmussen wrote:
> I can't see from your post what is missing, but I have myself had access
> to a Z6 (Linux based by the way) and it worked well with regard to
> copying files between the phone, it's microSD card and my Linux PC.
>
> My guess is that your kernel conf
I can't see from your post what is missing, but I have myself had access
to a Z6 (Linux based by the way) and it worked well with regard to
copying files between the phone, it's microSD card and my Linux PC.
My guess is that your kernel configuration isn't quite right.
What catches my eye from
Hallo.
I've got a new Motorola Z6 GSM phone, which should be "usb-storage capable"
(and ist is in Windows). But in Linux (Kernel 2.6.22.5) there are no mountable
block-devices:
--
Aug 28 09:54:28 kocom kernel: usb 3-1: ne
On Sat, 28 Jul 2007, Jean-Claude Repetto wrote:
> Sorry, my fault. This is the right log :
> Jul 28 08:39:53 corborant sd 2:0:0:0: [sdb] Spinning up
> disk...<7>usb-storage: queuecommand called
> Jul 28 08:39:53 corborant usb-storage: *** thread awakened.
> Jul 28 08:39:53 corborant usb-storage:
Alan Stern a écrit :
> On Fri, 27 Jul 2007, Jean-Claude Repetto wrote:
>
>>> You can do it yourself pretty easily. In drivers/scsi/sd.c, find the
>>> sd_spinup_disk() routine and comment out the call to
>>> media_not_present() near its start. You also have to comment out the
>>> check of sdkp
On Fri, 27 Jul 2007, Jean-Claude Repetto wrote:
> > You can do it yourself pretty easily. In drivers/scsi/sd.c, find the
> > sd_spinup_disk() routine and comment out the call to
> > media_not_present() near its start. You also have to comment out the
> > check of sdkp->device->no_start_on_add
Alan Stern a écrit :
> On Fri, 27 Jul 2007, Jean-Claude Repetto wrote:
>
>>> I wonder if a START_UNIT would help I've heard through the grapevine
>>> that a common OS reponse to "Not ready" is START_UNIT.
>>>
>>> Matt
>>>
>> How can I test that ? Could you send me a patch against the kernel
>
On Fri, Jul 27, 2007 at 09:24:15AM +0200, Jean-Claude Repetto wrote:
> Alan Stern a ?crit :
> > On Thu, 26 Jul 2007, Jean-Claude Repetto wrote:
> >
> >> Alan Stern wrote:
> >>> On Wed, 25 Jul 2007, Jean-Claude Repetto wrote:
> >>>
> Hi,
>
> I have a device (a TomTom GPS) that is see
On Fri, 27 Jul 2007, Jean-Claude Repetto wrote:
> > I wonder if a START_UNIT would help I've heard through the grapevine
> > that a common OS reponse to "Not ready" is START_UNIT.
> >
> > Matt
> >
>
> How can I test that ? Could you send me a patch against the kernel
> 2.6.22 driver ?
You
Matthew Dharm a écrit :
> On Fri, Jul 27, 2007 at 03:07:39PM -0400, Alan Stern wrote:
>> On Fri, 27 Jul 2007, Jean-Claude Repetto wrote:
>>
>>> Alan Stern wrote :
The device claims not to have any media present. I don't have any idea
why it does this when plugged in after booting but no
On Fri, Jul 27, 2007 at 03:07:39PM -0400, Alan Stern wrote:
> On Fri, 27 Jul 2007, Jean-Claude Repetto wrote:
>
> > Alan Stern wrote :
> > >
> > > The device claims not to have any media present. I don't have any idea
> > > why it does this when plugged in after booting but not when plugged in
On Fri, 27 Jul 2007, Jean-Claude Repetto wrote:
> Alan Stern wrote :
> >
> > The device claims not to have any media present. I don't have any idea
> > why it does this when plugged in after booting but not when plugged in
> > before booting.
> >
> > Anyway, you need to force the device to be
Alan Stern wrote :
>
> The device claims not to have any media present. I don't have any idea
> why it does this when plugged in after booting but not when plugged in
> before booting.
>
> Anyway, you need to force the device to be revalidated. I'm not sure
> when this happens automatically,
On Fri, 27 Jul 2007, Alan Stern wrote:
> On Fri, 27 Jul 2007, Jean-Claude Repetto wrote:
>
> > > That all looks normal.
> >
> > Yes, on Ubuntu it is working.
>
> Well then, can you post a debugging from the system where it is not
> working?
Oops, sorry, you already have.
The device claims no
On Fri, 27 Jul 2007, Jean-Claude Repetto wrote:
> > That all looks normal.
>
> Yes, on Ubuntu it is working.
Well then, can you post a debugging from the system where it is not
working?
Alan Stern
-
This SF.net email is
Alan Stern a écrit :
> On Thu, 26 Jul 2007, Jean-Claude Repetto wrote:
>
>> Alan Stern wrote:
>>> On Wed, 25 Jul 2007, Jean-Claude Repetto wrote:
>>>
Hi,
I have a device (a TomTom GPS) that is seen as a memory device when
connected via USB.
s
If I plug the device bef
On Thu, 26 Jul 2007, Jean-Claude Repetto wrote:
> Alan Stern wrote:
> > On Wed, 25 Jul 2007, Jean-Claude Repetto wrote:
> >
> >> Hi,
> >>
> >> I have a device (a TomTom GPS) that is seen as a memory device when
> >> connected via USB.
> >> s
> >> If I plug the device before booting the PC, it is
Alan Stern wrote:
> On Wed, 25 Jul 2007, Jean-Claude Repetto wrote:
>
>> Hi,
>>
>> I have a device (a TomTom GPS) that is seen as a memory device when
>> connected via USB.
>> s
>> If I plug the device before booting the PC, it is detected and
>> accessible via /dev/sdb .
>> But, if I plug the d
On Wed, 25 Jul 2007, Jean-Claude Repetto wrote:
> Hi,
>
> I have a device (a TomTom GPS) that is seen as a memory device when
> connected via USB.
> s
> If I plug the device before booting the PC, it is detected and
> accessible via /dev/sdb .
> But, if I plug the device after the PC has booted
Hi,
I have a device (a TomTom GPS) that is seen as a memory device when
connected via USB.
s
If I plug the device before booting the PC, it is detected and
accessible via /dev/sdb .
But, if I plug the device after the PC has booted, the device is not
accessible (the /dev/sdb device is not creat
On Mon, 18 Jun 2007, Balan, Vineeth (IE10) wrote:
> Hi Alan
>
>
> We checked the command and data sent by a RedHat 9 Linux host. (EHCI).
> After enumeration this is the sequence followed by Linux:
>
> 1. Test Unit Ready CSW returns 01 - command failed
> 2. Request sense
> 18 byte sense dat
Hi Alan
We checked the command and data sent by a RedHat 9 Linux host. (EHCI).
After enumeration this is the sequence followed by Linux:
1. Test Unit Ready CSW returns 01 - command failed
2. Request sense
18 byte sense data is:
70 00 06 00 00 00 00 0A 00 00 00 00 28 00 00 00 00 00 (UNIT A
On Tue, 12 Jun 2007, Balan, Vineeth (IE10) wrote:
> Hi Alan
>
> We are not still able to get the device to respond .The command
> sequence that we are using:
>
> 1. Read 10 - response is STALL.
> We then clear feature command. And a Bulk in to retrieve the CSW of
> failed Read 10.
> 2. Reques
Guys, are you even using linux? You're asking generalized USB questions to
linux-specific mailing lists.
Matt
On Tue, Jun 12, 2007 at 11:03:26AM +0530, Balan, Vineeth (IE10) wrote:
> Hi Alan
>
> We are not still able to get the device to respond .The command
> sequence that we are using:
>
>
Hi Alan
We are not still able to get the device to respond .The command
sequence that we are using:
1. Read 10 - response is STALL.
We then clear feature command. And a Bulk in to retrieve the CSW of
failed Read 10.
2. Request Sense: 18 bytes of sense data and CSW. Sense data shows 06 -
UNIT A
On Thu, 12 Oct 2006, Paul Burke wrote:
> > > My best attempt has come from this:
> > >
> > > UNUSUAL_DEV ( 0x045e, 0x0280, 0x, 0x, "Microsoft Corp.", "Xbox
> > > Memory Unit", US_SC_SCSI, US_PR_DEVICE, NULL, US_FL_SINGLE_LUN |
> > > US_FL_FIX_INQUIRY ),
> >
> > You shouldn't use the FIX_IN
> My best attempt has come from this:
>
> UNUSUAL_DEV ( 0x045e, 0x0280, 0x, 0x, "Microsoft Corp.", "Xbox
> Memory Unit", US_SC_SCSI, US_PR_DEVICE, NULL, US_FL_SINGLE_LUN |
> US_FL_FIX_INQUIRY ),
You shouldn't use the FIX_INQUIRY flag, and you probably don't need the
SINGLE_LUN flag either
On Wed, 11 Oct 2006, Paul Burke wrote:
> Hi all,
>
> I'm attempting to read the contents of Microsoft-branded Xbox memory
> units. The Action Replay for the Xbox includes a USB to memory unit
> adapter, presenting the devices as standard mass storage objects. The
> Interact-branded memory unit
Hi all,
I'm attempting to read the contents of Microsoft-branded Xbox memory
units. The Action Replay for the Xbox includes a USB to memory unit
adapter, presenting the devices as standard mass storage objects. The
Interact-branded memory unit included with the Action Replay registers
properly i
Hi Alan,
Am Dienstag, 26. September 2006 20:40 schrieben Sie:
> Evidently you haven't installed the second patch I sent you. Otherwise
> the Quirks: line would list FIX_CAPACITY and IGNORE_RESIDUE.
you are right I have installed the second patch you sent me but I
inadvertently patched a kernel
On Tue, 26 Sep 2006, Jon Hart wrote:
> Hi Alan,
>
> Am Freitag, 22. September 2006 22:48 schrieb Alan Stern:
> > Try copying 1 MB instead of 180 MB. Does that take 10 seconds? What
> > does the complete system log for the transfer show?
>
> Copying 1MB takes about 3 minutes, the complete syste
On Sat, Sep 02, 2006 at 06:39:10PM +0300, you [Ville Herva] wrote:
>
> I found the following addition to unusual_devs.h necessary to use E70 with
> 2.6 usb-storage:
>
>
> UNUSUAL_DEV( 0x0421, 0x0433, 0x0100, 0x0100,
Hi Alan,
Am Mittwoch, 20. September 2006 17:26 schrieb Alan Stern:
> It's like I guessed, the E60 needs US_FL_IGNORE_RESIDUE. Use the patch
> below instead of the one from before.
the symptoms are now as follws: Copying about 180MB to the phone takes more
than 30 minutes. The Log I captured fro
On Fri, 22 Sep 2006, Jon Hart wrote:
> Hi Alan,
>
> Am Mittwoch, 20. September 2006 17:26 schrieb Alan Stern:
> > It's like I guessed, the E60 needs US_FL_IGNORE_RESIDUE. Use the patch
> > below instead of the one from before.
>
> the symptoms are now as follws: Copying about 180MB to the phone
Hi Alan,
thank you for your help. Mounting the E60 works now but unmounting the device
takes an unusual long time.
Please can you have a look at the attached syslog output?
Thank you very much
J. Hart
Am Montag, 18. September 2006 18:01 schrieb Alan Stern:
> It looks like the E60, in common wi
On Wed, 20 Sep 2006, Jon Hart wrote:
> Hi Alan,
>
> thank you for your help. Mounting the E60 works now but unmounting the device
> takes an unusual long time.
>
> Please can you have a look at the attached syslog output?
>
> Thank you very much
> J. Hart
>
> Am Montag, 18. September 2006 18:
On Sun, 17 Sep 2006 [EMAIL PROTECTED] wrote:
> Hi,
>
> I can't get my mobile e60 mounted with kernel 2.6.17 and 2.6.18-rc6. Using
> windows xp all went fine.
>
> A mount attempt ends with "mount: /dev/sdb: can't read superblock".
> Please can anybody give me a hint how to solve this problem?
>
On Sat, Sep 02, 2006 at 06:22:26PM +0300, you [Ville Herva] wrote:
>
> end_request: I/O error, dev sda, sector 1824527
> sd 0:0:0:0: SCSI error: return code = 0x1007
> end_request: I/O error, dev sda, sector 1824535
> sd 0:0:0:0: SCSI error: return code = 0x1007
>
> even with the patch, t
I found the following addition to unusual_devs.h necessary to use E70 with
2.6 usb-storage:
UNUSUAL_DEV( 0x0421, 0x0433, 0x0100, 0x0100,
"Nokia",
"E70",
US_SC_DEVICE, US_PR_DEVICE, NULL,
US_FL_IGNORE_RESIDUE | US_FL_FIX_CAPACITY ),
Looks reasonable.
Greg, please apply.
Matt
Signed-off-by: Matthew Dharm <[EMAIL PROTECTED]>
On Thu, Aug 31, 2006 at 10:24:03PM +0200, Cedric Le Goater wrote:
> Matthew Dharm wrote:
>
> > The URL in MAINTAINERS is correct, please don't remove it. The server
> > seems to need fixing, however...
luigi rensinghoff wrote:
Hello.List
I am having trouble with a usb-hard-drive on a gentoo-linux ibm-thinkpad...
kernel is 2.6.15
The strange thing is, that sometimes it works and sometimes (most of the
times) it does notand it keeps on spinning (clicking) but its
impossible to get it
Hello.List
I am having trouble with a usb-hard-drive on a gentoo-linux ibm-thinkpad...
kernel is 2.6.15
The strange thing is, that sometimes it works and sometimes (most of the
times) it does notand it keeps on spinning (clicking) but its
impossible to get it mounted.
It is a small
On Wed, 1 Feb 2006, Alexey Golovachov wrote:
> Thank you a lot, Alan. Information you've provided is really helpful for me.
> I'VE GET THIS DEVICE WORKED.
> Let me explain briefly:
>
> This device has memory stick 64MB. But for unknown reason it reports 127MB
> geometry (in Windows as well), con
> > Hi.
> > Jan 30 09:45:55 Xenon kernel: usb-storage: Command READ_10 (10 bytes)
> > Jan 30 09:45:55 Xenon kernel: usb-storage: 28 00 00 03 cb 80 00 00 08 00
>
> Trying to read 8 sectors starting at sector 0x03cb80 = 248704 shouldn't
> present any problem since the total number of sectors is 2
On Tue, 31 Jan 2006, Alexey Golovachov wrote:
> Hi.
>
> I've completely lost to get SonyEricsson K750i working on my linux box.
> It should be discovered as usb-mass-storage device with no additional issues.
> But, ufrtunately, not for me.
> I've already tried kernels 2.6.11.4-21.9 (SuSE9.3), fre
On Monday 19 December 2005 21:43, Alan Stern wrote:
> David might have some ideas about investigating the bad controller in
> further detail. It would be nice at least for things to fail cleanly
> instead of hanging.
I'd be more than happy to add debug messages you may need, test any
patches y
On Mon, 19 Dec 2005, Andreas Klauer wrote:
> Hello Alan,
>
> thank you very much for your quick reply. :-)
>
> On Monday 19 December 2005 00:30, Alan Stern wrote:
> > This could be either a controller bug or a device bug. The easiest way to
> > tell would be to plug the player into a different
Hello Alan,
thank you very much for your quick reply. :-)
On Monday 19 December 2005 00:30, Alan Stern wrote:
> This could be either a controller bug or a device bug. The easiest way to
> tell would be to plug the player into a different computer, one with a
> non-VIA chipset.
The only other
David:
This might be a good test case for determining what those crazy VIA EHCI
controllers are doing.
On Sun, 18 Dec 2005, Andreas Klauer wrote:
> Hi all,
>
> I'm new to this list. Please don't hurt me. m(_)m
>
> I've got a weird problem with one of my USB storage devices (a Trekstor
> MP3
Hi all,
I'm new to this list. Please don't hurt me. m(_)m
I've got a weird problem with one of my USB storage devices (a Trekstor
MP3 player which supports USB2). When I connect it to the computer while
the ehci_hcd module is loaded, some part of the USB subsystem seems to
freeze indefinitely.
De facto, best as I mis/remember, Windows ME/ 98/ 95 asked often for
x0E (14) bytes and Win XP/ 2K/ NT now asks often for x12 (18) bytes.
Furthermore, Windows ignores the additional length byte.
Consequently, naturally, yes, because of the rudeness of those many
hosts, now many commodity peripher
On Sat, 2005-12-03 at 07:00 -0800, Pat LaVarre wrote:
> >> I have a USB bridge that's implementing SAT passthru cdbs. We ran
> >> into an
> >> issue with the usb-storage driver in that when it does auto-sense
> >> (because
> >> the CK_COND bit is set in the passthru cdb), the driver does a
>
On Fri, 2 Dec 2005, Timothy Thelin wrote:
> Here is a patch that makes the test a separate routine and uses the
> ATA_12/16 opcode defines found in scsi.h. Thoughts?
Looks good. I would have declared the new routine and variable as
unsigned instead of u8 (since they are only temporaries), but it
I have a USB bridge that's implementing SAT passthru cdbs. We ran
into an
issue with the usb-storage driver in that when it does auto-sense
(because
the CK_COND bit is set in the passthru cdb), the driver does a
sense with
only 18 bytes for the sense buffer. The problem is that SAT
passth
> > I have a USB bridge that's implementing SAT passthru cdbs. We ran into an
> > issue with the usb-storage driver in that when it does auto-sense (because
> > the CK_COND bit is set in the passthru cdb), the driver does a sense with
> > only 18 bytes for the sense buffer. The problem is that S
On Fri, 2 Dec 2005, Timothy Thelin wrote:
> > The sense buffer length is yet another quantity that ought to
> > have an SG
> > passthru but doesn't.
> >
>
> SG_IO provides a field that allows the application to dictate
> the maximum sense buffer length to be passed back. Could this
> field al
> > Hi all,
> >
> > I have a USB bridge that's implementing SAT passthru cdbs.
> We ran into an
> > issue with the usb-storage driver in that when it does
> auto-sense (because
> > the CK_COND bit is set in the passthru cdb), the driver
> does a sense with
> > only 18 bytes for the sense buff
On Fri, 2 Dec 2005, Timothy Thelin wrote:
> Hi all,
>
> I have a USB bridge that's implementing SAT passthru cdbs. We ran into an
> issue with the usb-storage driver in that when it does auto-sense (because
> the CK_COND bit is set in the passthru cdb), the driver does a sense with
> only 18 byt
Hi all,
I have a USB bridge that's implementing SAT passthru cdbs. We ran into an
issue with the usb-storage driver in that when it does auto-sense (because
the CK_COND bit is set in the passthru cdb), the driver does a sense with
only 18 bytes for the sense buffer. The problem is that SAT pass
@lists.sourceforge.net
Subject: RE: [Linux-usb-users] USB Storage on Linux 2.4.30
On Mon, 19 Sep 2005, Singh, Brijeshkumar wrote:
> Thanks Alan,
>
> This weekend, I'll install 2.6.13 and will let you know about my
> observations.
>
> Actually, on our custom hardware we are using linux-2.4
On Mon, 19 Sep 2005, Singh, Brijeshkumar wrote:
> Thanks Alan,
>
> This weekend, I'll install 2.6.13 and will let you know about my
> observations.
>
> Actually, on our custom hardware we are using linux-2.4.30 and would
> like to know any pointer on how I can proceed to fix this problem. As
> y
1 - 100 of 377 matches
Mail list logo
