On Wed, 30 Jul 2003, Matthew Dharm wrote:
> My guess is that the vast majority of devices will be fine with any length
> over the header size -- some of James' code tries to guarantee that.
>
> Do we have any idea how large that page is supposed to be?
In Daniel's case we actually know, because
On Wed, Jul 30, 2003 at 10:08:27AM -0400, Alan Stern wrote:
> Matt:
>
> Daniel reports that the patch to change the length of the
> cache-determination MODE-SENSE worked (patch included below). Here is the
> relevant part of the system log. It turns out that only the first 11
> bytes of the c
Matt:
Daniel reports that the patch to change the length of the
cache-determination MODE-SENSE worked (patch included below). Here is the
relevant part of the system log. It turns out that only the first 11
bytes of the cache page are needed...
On 30 Jul 2003, Daniel Stöckner wrote:
> It wo
It works! Here the log when connecting the device:
Jul 30 00:30:15 lapp31000 kernel: hub 1-0:0: debounce: port 1: delay 100ms stable 4
status 0x101
Jul 30 00:30:15 lapp31000 kernel: hub 1-0:0: new USB device on port 1, assigned
address 2
Jul 30 00:30:15 lapp31000 kernel: Initializing USB Mass St
Daniel:
Try using this patch. It reduces the length of the failing request from
128 bytes to 11 bytes; that might make a significant difference.
Let me know how it works out. And if you still get an error, be sure to
send another debugging log.
Alan Stern
= sd.c 1.52 vs edited =
--
Matt:
Look at Daniel Stöckner's posting:
http://sourceforge.net/mailarchive/forum.php?thread_id=2842723&forum_id=5398
He's using UHCI, and the drive fails with a Babble error on the very first
data transfer that's more than 64 bytes long, which coincidentally is a
MODE-SENSE transfer. The log
On Mon, Jul 28, 2003 at 05:20:22PM -0400, Alan Stern wrote:
> Matt:
>
> Look at Daniel Stöckner's posting:
>
> http://sourceforge.net/mailarchive/forum.php?thread_id=2842723&forum_id=5398
>
> He's using UHCI, and the drive fails with a Babble error on the very first
> data transfer that's more
Mode sense page length is 1536.
/var/log/messages:
Jul 27 10:01:59 lapp31000 kernel: hub 1-0:0: debounce: port 1: delay 100ms stable 4
status 0x101
Jul 27 10:01:59 lapp31000 kernel: hub 1-0:0: new USB device on port 1, assigned
address 2
Jul 27 10:01:59 lapp31000 kernel: Initializing USB Mass S
On 17 Jul 2003, Daniel Stöckner wrote:
> With kernel 2.5.70 and kernel 2.6.0-test1 I did exactly the same
> actions. Both kernels have the same (as similar as possible)
> configuration. I tested in both cases directly after booting into
> Runlevel 3 without doing anything before my test.
>
> Here
With kernel 2.5.70 and kernel 2.6.0-test1 I did exactly the same actions. Both kernels
have the same (as similar as possible) configuration. I tested in both cases directly
after booting into Runlevel 3 without doing anything before my test.
Here the /proc/bus/usb/devices of kernel 2.5.70 after
On 15 Jul 2003, Daniel Stöckner wrote:
> I´m not in this list. In earlier Versions of Kernel 2.5., in Version
> 2.4.21-pre7 and in Windows XP :( it works. It is a Maxtor 120GB
> Harddisk-drive connected to a USB2 usb-atapi-interface. After some
> seconds of powering up, the traffic LED turns on an
I´m not in this list. In earlier Versions of Kernel 2.5., in Version
2.4.21-pre7 and in Windows XP :( it works. It is a Maxtor 120GB
Harddisk-drive connected to a USB2 usb-atapi-interface. After some
seconds of powering up, the traffic LED turns on and stays lid. But the
device hangs. No access pos
I´m not in this list. In earlier Versions of Kernel 2.5., in Version
2.4.21-pre7 and in Windows XP :( it works. It is a Maxtor 120GB
Harddisk-drive connected to a USB2 usb-atapi-interface. After some
seconds of powering up, the traffic LED turns on and stays lid. But the
device hangs. No access pos
13 matches
Mail list logo
