On Nov 14 2003, Alan Stern wrote:
> On Thu, 13 Nov 2003, Rogério Brito wrote:
>
> > Yes, thinking more about the problem, that seems to be the case. David
> > Brownell already told me that.
> >
> > I sent him an e-mail telling what I see when I modify my
> > /etc/hotplug/usb.rc script to contain "modprobe -q uhci-hcd debug=2".
First of all, I am sorry that I haven't replied yet.
I had some pretty serious personal problems that aren't solved yet, but
at least now I have some little free time to devote to the problem with
the USB Drive.
Anyway, now I did a bit more of the homework and I am slighly more
informed about the situation.
According to the manual of the drive, I see that it is indeed identified
(intentionally) as two devices (quote from the manual, verbatim):
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
* Leading Driver contains 2 drives, one is standard disk, the other is
security disk.
* If you don't install driver for Windows ME, 2000, XP, MacOS, only
standard disk can be used.
* To access serutity disk, please install driver for Leading Driver
and keyin the correct password.
* It is recommended to copy Setup.exe to your standard disk for more
convenient [sic].
Security Function:
* Security disk of Leading Driver is password protected, you can not
access it, until keyin the correct password. [sic]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
In the mean time, I upgraded the BIOS of my motherboard (an Asus A7V,
going from version 1003 to version 1011), just in case.
> An alternative is after you have loaded uhci-hcd but before your device is
> plugged in, do
>
> echo 4 > /proc/driver/uhci/...
>
> where ... is the file corresponding to the controller you plug your device
> into. Debugging level 4 will provide more information than level 2, in
> any case.
Ok.
> > Anyway, what should I do? Should I just boot into single user mode
> > without hotplug enabled and load the modules by hand?
>
> That would be a good way of testing.
Well, I did that. I removed my hotplug scripts, made the initial boot
scripts load only a minimal set of modules for my system and loaded the
USB modules by hand.
I am using kernel 2.6.0-test9, just as a reminder.
I did the following steps and for most of those steps, I put the
accompanying dmesg on my site <http://www.ime.usp.br/~rbrito/usb/>:
1 - booted without any device plugged;
2 - did "modprobe -k uhci-hcd debug=2";
3 - loaded both the sd_mod and usb-storage modules;
4 - checked what I had in /proc/driver/uhci and did the "echo 4 > ..."
for each of the controllers that were there;
5 - plugged the drive (this didn't recognize it as a block device);
6 - unplugged and replugged the drive (also didn't work).
OTOH, I compiled a 2.6.0-test9 kernel for my old notebook (a Compaq
Armada V300) and for this notebook, the drive works. The appropriate
dmesgs are also included at <http://www.ime.usp.br/~rbrito/usb/>.
> It definitely is getting recognized as more than one USB device, but
> that's the point where things go wrong.
If you have further suggestions, don't hesitate to use me as a guinea
pig.
> > Is there any way to discover what may be the reason of the problem? Any
> > higher debugging level would help with that?
>
> The only way I can think of is by comparison with what happens when
> the device works. That's why I suggested trying another computer.
Ok. I did this. I hope it contains useful information. If not, then
please let me know and I will focus more my approach.
> Another approach would be to use a USB logging programs to see what
> happens when you use your device under Windows.
I don't know much Windows.
> Also, if you can collect and post the dmesg output from one of those
> occasions when the device does work, perhaps that will help.
Ok. I will try to see if I can get it working with the 2.6.0-test9
kernel, but it seems that I can't lately. :-(
Thank you *so* much for both your and David's help, Rogério Brito.
P.S.: After I removed the USB drive from my desktop, I got the following
messages in my dmesg:
usb 1-1: control timeout on ep0in
hub 1-1:1.0: hub_hub_status failed (err = -110)
hub 1-1:1.0: get_hub_status failed
hub 1-0:1.0: port 1, status 100, change 3, 12 Mb/s
usb 1-1: USB disconnect, address 2
usb 1-1: usb_disable_device nuking all URBs
uhci_hcd 0000:00:04.2: shutdown urb c7ed9480 pipe 40408280 ep1in-intr
usb 1-1: unregistering interface 1-1:1.0
usb 1-1: hcd_unlink_urb c7ed9480 fail -16
drivers/usb/core/usb.c: usb_hotplug
usb 1-1: unregistering device
drivers/usb/core/usb.c: usb_hotplug
hub 1-0:1.0: port 1 enable change, status 100
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rogério Brito - [EMAIL PROTECTED] - http://www.ime.usp.br/~rbrito
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
