Bug 12188
Summary: | Corsair Flash Voyager USB Stick not working | ||
---|---|---|---|
Product: | Drivers | Reporter: | Paul Wellner Bou (paul) |
Component: | USB | Assignee: | Greg Kroah-Hartman (greg) |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | stern |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.27.8 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Paul Wellner Bou
2008-12-09 22:32:39 UTC
The values in /etc/modprobe.d/options apply only to driver built as modules. If scsi_mod is built into the kernel instead of as a module, you can get the equivalent effect by adding the option on the kernel's boot command line (in grub or whatever boot loader you use): scsi_mod.inq_timeout=20 What relation is there between the Corsair Flash Voyager and Bug #8444? Bug #8444 is about the Corsair Flash Voyager, too. (And fixed by setting a timeout, and that the Flash Voyager works fine under Windows.) I just trusted the launchpad guys where I have the link to #8444 from and assumed that this issue is at least kind of similar. Even the logs are similar. Sorry if this is not the case. As far as I can tell, these are two separate problems. That's judging from the fact that they have two separate solutions. Anyway, if the advice in comment #1 fixes your problem, you can close out this bug report. Isn't there a way to fix it so that the Corsair Flash Voyager owners don't have to reboot the machine or rebuild the kernel of a machine where they want to use the memory stick? Would be a pity. And would be great if it was possible to fix it. On Thu, 11 Dec 2008 bugme-daemon@bugzilla.kernel.org wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=12188 > ------- Comment #4 from paul@purecodes.org 2008-12-11 23:38 ------- > Isn't there a way to fix it so that the Corsair Flash Voyager owners don't > have > to reboot the machine or rebuild the kernel of a machine where they want to > use > the memory stick? > Would be a pity. And would be great if it was possible to fix it. Would anybody object if the default value for scsi_inq_timeout was increased? There is at least one USB device for which the current 5 seconds is known to be too small. Windows XP uses 20 seconds (for USB mass-storage devices, anyway -- I don't know about other bus types). Is there any reason not to make 20 the default? Alan Stern All USB bugs should be sent to the linux-usb@vger.kernel.org mailing list, and not entered into bugzilla. Please bring this issue up there, if it is still a problem in the latest kernel release. |