Dan Gray wrote:
I've been into the source and played with usb.c, basicly fetching the
device_descriptor before I try to set the address. At the moment this
seems to allow the device to work (it's actually transfering at full
speed as I write this) but it's still quite flakey.
That's interesti
Hi,
I've got (but maybe fixed) this same problem.
I've got a VIA chipset and was trying to mount a 2.0 HDD ( 067b:3507
Prolific Technology, Inc) which was failing with various ep0out and
'device failed to accept address' errors.
I've been into the source and played with usb.c, basicly fetching
> Not at this time. Am I correct to assume that this is the
> disk in question, connected to Linux 2.4 at full speed?
Yes.
> Matched with an ALI EHCI controller, which 2.6 boots like this:
Yes.
>
> Nobody has yet reported problems with ALI's EHCI silicon, so
> I wouldn't expect that to be a
Chris Carter wrote:
Hi,
I have not heard anything back from my last post (see below). Does this
mean that I can forget about running Linux with this hardware because my
USB2.0 is/will not be supported?
Nope, it just means that I got behind in that part of my email; you
should just have gotten a re
Chris Carter wrote:
Compiled with USB debug and Mass storage debug enabled, plugged device
in with ehci loaded. Output from dmesg in dmesg.txt (boot process -
removed non-usb messages) and dmesg2.txt (after switching usb HD on).
I don't understand what much of this means (I can only guess part of
h 2004 18:05
> To: 'David Brownell'
> Cc: '[EMAIL PROTECTED]'
> Subject: RE: [linux-usb-devel] Problems with ehci 2.0:
> devices not recognized
>
>
> > So if it's working, what does /proc/bus/usb/devices say
> > about the device?
>
&g
> So if it's working, what does /proc/bus/usb/devices say
> about the device?
See attached usbdevices-detected.txt.
> And how does it behave through an external USB 2.0 powered hub?
Don't have one to play around with. Sorry. What I do know is that the
same hardware running Windows recognizes the
Chris Carter wrote:
2. inserted the device (output in file dmesg-after-plugindevice.txt).
Sure enough the device is registered and I can mount it, however I am
not getting hi-speed throughput (which I presume is because I have
unloaded ehci).
So if it's working, what does /proc/bus/usb/devices say
> And "rmmod" is needed to answer the second question.
This is what I did:
1. rmmod ehci-hcd, recorded the output from dmesg and ran lsmod to
confirm ehci had been unloaded.
2. inserted the device (output in file dmesg-after-plugindevice.txt).
Sure enough the device is registered and I can mount
Chris Carter wrote:
"error=-71" measn "-EPROTO", a protocol error of some
kind from your device ... it should be responding to
that very first request.
When you hook it up through an external hub, or without
EHCI loaded, what happens?
Hi David,
Thanks for your response. EHCI is loaded automatica
Hi,
Chris Carter wrote:
Thanks for your response. EHCI is loaded automatically by hotplug.
If you enable module unloading, you will be able to use "rmmod" to unload the
module before you plug a device in. The perhaps more sensible option would be
to remove EHCI support from your kernel.
Daniel
> "error=-71" measn "-EPROTO", a protocol error of some
> kind from your device ... it should be responding to
> that very first request.
>
> When you hook it up through an external hub, or without
> EHCI loaded, what happens?
Hi David,
Thanks for your response. EHCI is loaded automatically by h
Chris Carter wrote:
This is what happens:
hub.c: new USB device 00:0b.3-6, assigned address 10
usb.c: USB device not accepting new address=10 (error=-71)
hub.c: new USB device 00:0b.3-6, assigned address 11
usb.c: USB device not accepting new address=11 (error=-71)
Nothing else.
"error=-71"
Check the FAQ then.
On Sun, 21 Mar 2004, Chris Carter wrote:
> Daniel Drake wrote:
> > You didn't describe the actual problem - what happens when
> > you plug the device in?
>
> This is what happens:
> hub.c: new USB device 00:0b.3-6, assigned address 10
> usb.c: USB device not accepting new addr
Daniel Drake wrote:
> You didn't describe the actual problem - what happens when
> you plug the device in?
This is what happens:
hub.c: new USB device 00:0b.3-6, assigned address 10
usb.c: USB device not accepting new address=10 (error=-71)
hub.c: new USB device 00:0b.3-6, assigned address 11
Hi,
Chris Carter wrote:
I have tried both kernels 2.4.25 and 2.6.5 and got the same results; and
reaching the end of my tether. I am trying to get a 2.0 Hi-speed
harddisk detected but it fails (regardless of what I do). The usb-disk
is detected properly under Windows (so it is not a hardware fault
Hi,
I have tried both kernels 2.4.25 and 2.6.5 and got the same results; and
reaching the end of my tether. I am trying to get a 2.0 Hi-speed
harddisk detected but it fails (regardless of what I do). The usb-disk
is detected properly under Windows (so it is not a hardware fault).
I have attached
17 matches
Mail list logo
