Fri, 02 Dec 2005 @ 17:07 -0500, Alan Stern said:
> > Does that give you the information you need, or do you want me to keep
> > stepping it down until it breaks?
>
> 50 ms isn't bad, but it would be nice to know the minimum.
OK.
The machine will be busy for awhile so I can't do it immediately.
On Fri, 2 Dec 2005, Charles Shannon Hendrix wrote:
> Wed, 23 Nov 2005 @ 15:04 -0500, Alan Stern said:
>
> > On Wed, 9 Nov 2005, Charles Shannon Hendrix wrote:
> >
> > > Wed, 09 Nov 2005 @ 10:38 -0500, Alan Stern said:
> > >
> > > > A 1-second delay is kind of long. Does the iPod continue to wo
Wed, 23 Nov 2005 @ 15:04 -0500, Alan Stern said:
> On Wed, 9 Nov 2005, Charles Shannon Hendrix wrote:
>
> > Wed, 09 Nov 2005 @ 10:38 -0500, Alan Stern said:
> >
> > > A 1-second delay is kind of long. Does the iPod continue to work if you
> > > decrease the delay length? How low can you go?
>
Wed, 23 Nov 2005 @ 15:04 -0500, Alan Stern said:
> On Wed, 9 Nov 2005, Charles Shannon Hendrix wrote:
>
> > Wed, 09 Nov 2005 @ 10:38 -0500, Alan Stern said:
> >
> > > A 1-second delay is kind of long. Does the iPod continue to work if you
> > > decrease the delay length? How low can you go?
>
On Wed, 9 Nov 2005, Charles Shannon Hendrix wrote:
> Wed, 09 Nov 2005 @ 10:38 -0500, Alan Stern said:
>
> > A 1-second delay is kind of long. Does the iPod continue to work if you
> > decrease the delay length? How low can you go?
>
> Not sure yet.
Any word yet on how long a delay is needed
On Wed, 9 Nov 2005, Charles Shannon Hendrix wrote:
> Something I just noticed: For some reason if hal and dbus are activated,
> the iPod is recognized by usb-storage, but gets caught in an endless
> loop trying to init a SCSI device.
>
> I don't know if that is relevant or not.
>
> I generally h
Wed, 09 Nov 2005 @ 10:38 -0500, Alan Stern said:
> A 1-second delay is kind of long. Does the iPod continue to work if you
> decrease the delay length? How low can you go?
Not sure yet.
Something I just noticed: For some reason if hal and dbus are activated,
the iPod is recognized by usb-stor
On Tue, 8 Nov 2005, Charles Shannon Hendrix wrote:
> Regarding a pause after hub_port_reset() to allow a device some time to
> get ready, I applied the following patch suggested by Alan Stern:
>
> --- drivers/usb/core/hub.c.orig 2005-10-27 20:02:08.0 -0400
> +++ drivers/usb/core/hub.c
Tue, 08 Nov 2005 @ 11:45 -0500, Charles Shannon Hendrix said:
> OK. You want this:
>
> retval = hub_port_reset(hub, port1, udev, delay);
> + msleep(500);
> if (retval < 0)
> ...
>
> I'll get to that later tonight or tomorrow and post any results.
Regarding a pause after
On Sat, 5 Nov 2005, Charles Shannon Hendrix wrote:
> Sat, 05 Nov 2005 @ 18:06 -0500, Alan Stern said:
>
> > It's bad because there's no way to tell the relative order of lines
> > between the different files. If each log file has a line timestamped
> > 16:34:41, which one came first?
>
> That's
Sat, 05 Nov 2005 @ 18:06 -0500, Alan Stern said:
> It's bad because there's no way to tell the relative order of lines
> between the different files. If each log file has a line timestamped
> 16:34:41, which one came first?
That's not normally a concern for everyday use, which is what the
default
On Sat, 5 Nov 2005, Charles Shannon Hendrix wrote:
> > You have ruled out the first two options, and the third option is
> > ruled out by the fact that so many other people use the same driver with
> > no difficulties at all. What does that leave?
>
> It fails to work for a lot of people from
On Sat, 5 Nov 2005, Charles Shannon Hendrix wrote:
> Sat, 05 Nov 2005 @ 15:54 -0500, Alan Stern said:
>
> > You still have a syslog configuration problem. You're sending the
> > debug-level messages to /var/log/debug and everything else to
> > /var/log/syslog, or something like that?
>
> It's S
Sat, 05 Nov 2005 @ 15:54 -0500, Alan Stern said:
> You still have a syslog configuration problem. You're sending the
> debug-level messages to /var/log/debug and everything else to
> /var/log/syslog, or something like that?
It's Slackware's default setup.
I understand it isn't your preference
Sat, 05 Nov 2005 @ 15:44 -0500, Alan Stern said:
> > I don't see anything wrong with my EHCI controller. Works fine from
> > where I sit.
> >
> > Is there something specific you think is wrong with it?
>
> Like I said, I don't know what might be going wrong. It just seemed like
> a good possi
On Sat, 5 Nov 2005, Charles Shannon Hendrix wrote:
> OK, syslog configuration issue. I have it working now.
>
> I rebuilt my kernel to have usbcore as a module, so I could try the old
> method parameter.
>
> Some things have changed, and I have a small amount of additional
> information.
>
> I
Sat, 05 Nov 2005 @ 13:18 -0500, Charles Shannon Hendrix said:
> Interestingly, now if I plug in my iPod, there is no reaction from the
> kernel at all. No interrupts generated either.
Unfortunately, during testing of this problem, something has happened
to my iPod. It won't connect to another com
On Sat, 5 Nov 2005, Charles Shannon Hendrix wrote:
> Thu, 03 Nov 2005 @ 10:26 -0500, Alan Stern said:
>
> > On Wed, 2 Nov 2005, Charles Shannon Hendrix wrote:
> >
> > > I have been using my USB2 devices with Linux for some time now, but
> > > recently have started having troubles with them.
> >
Sat, 05 Nov 2005 @ 11:33 -0500, Charles Shannon Hendrix said:
> > I'd expect that CONFIG_USB_DEBUG=y would show some more messages.
>
> I've enabled it specifically to debug this, but it isn't showing me
> anything extra.
OK, syslog configuration issue. I have it working now.
I rebuilt my kern
Thu, 03 Nov 2005 @ 07:57 -0800, David Brownell said:
> A similar issue -- often also with VIA hardware -- is devices that work
> for a while and then spontaneously disconnect themselves. It might be
> this is another case where VIA hardware needs to be stroked in ways that
> other hardware doesn'
Thu, 03 Nov 2005 @ 10:26 -0500, Alan Stern said:
> On Wed, 2 Nov 2005, Charles Shannon Hendrix wrote:
>
> > I have been using my USB2 devices with Linux for some time now, but
> > recently have started having troubles with them.
>
> I don't know what's going wrong with your EHCI controller, or h
On Thu, 3 Nov 2005, David Brownell wrote:
> On Thursday 03 November 2005 9:33 am, Alan Stern wrote:
> > On Thu, 3 Nov 2005, David Brownell wrote:
> >
> > > > One way to test this theory is to use the undocumented
> > > > "old_scheme_first=y" parameter for the usbcore module.
> > >
> > > Actuall
On Thursday 03 November 2005 9:33 am, Alan Stern wrote:
> On Thu, 3 Nov 2005, David Brownell wrote:
>
> > > One way to test this theory is to use the undocumented
> > > "old_scheme_first=y" parameter for the usbcore module.
> >
> > Actually that doesn't get rid of the fault mode (short reads), i
On Thu, 3 Nov 2005, David Brownell wrote:
> > One way to test this theory is to use the undocumented
> > "old_scheme_first=y" parameter for the usbcore module.
>
> Actually that doesn't get rid of the fault mode (short reads), it just
> moves it to a different place.
It gets moved to a place wh
On Thursday 03 November 2005 8:31 am, Alan Stern wrote:
> On Thu, 3 Nov 2005, David Brownell wrote:
>
> > > When I do see syslog messages, they look like this:
> > >
> > > Nov 2 20:51:38 daydream kernel: usb 1-8: device descriptor read/64,
> > > error -71
> > > Nov 2 20:51:38 daydream last mes
On Thu, 3 Nov 2005, David Brownell wrote:
> > When I do see syslog messages, they look like this:
> >
> > Nov 2 20:51:38 daydream kernel: usb 1-8: device descriptor read/64, error
> > -71
> > Nov 2 20:51:38 daydream last message repeated 3 times
> > Nov 2 20:51:39 daydream kernel: usb 1-8: de
On Wednesday 02 November 2005 6:36 pm, Charles Shannon Hendrix wrote:
>
> Beginning with Linux 2.6.10, my 1GB USB drive sometimes required more
> than one attempt before it would connect. In other words, I often had
> to remove it and reinsert it in its port before the kernel would see it.
>
> .
On Wed, 2 Nov 2005, Charles Shannon Hendrix wrote:
> I have been using my USB2 devices with Linux for some time now, but
> recently have started having troubles with them.
I don't know what's going wrong with your EHCI controller, or how to fix
it. However I can answer your general questions.
I have been using my USB2 devices with Linux for some time now, but
recently have started having troubles with them.
Beginning with Linux 2.6.10, my 1GB USB drive sometimes required more
than one attempt before it would connect. In other words, I often had
to remove it and reinsert it in its p
29 matches
Mail list logo
