“UbuntuHelp:DebuggingUSBStorage”的版本间的差异
来自Ubuntu中文
小 |
小 |
||
第2行: | 第2行: | ||
{{Languages|UbuntuHelp:DebuggingUSBStorage}} | {{Languages|UbuntuHelp:DebuggingUSBStorage}} | ||
=== USB2 Issues === | === USB2 Issues === | ||
− | |||
This can be worked around easily. Simply run this command: | This can be worked around easily. Simply run this command: | ||
− | |||
<pre><nowiki> | <pre><nowiki> | ||
sudo rmmod ehci_hcd | sudo rmmod ehci_hcd | ||
</nowiki></pre> | </nowiki></pre> | ||
− | |||
− | |||
=== Buffer I/O Errors === | === Buffer I/O Errors === | ||
− | |||
If you see errors related to Buffer I/O when attaching a USB Storage device, there are two ways to work around it. First, try using varying max_sectors settings, as such: | If you see errors related to Buffer I/O when attaching a USB Storage device, there are two ways to work around it. First, try using varying max_sectors settings, as such: | ||
− | |||
<pre><nowiki> | <pre><nowiki> | ||
sudo sh -c "echo 120 > /sys/block/sda/queue/max_sectors_kb" | sudo sh -c "echo 120 > /sys/block/sda/queue/max_sectors_kb" | ||
</nowiki></pre> | </nowiki></pre> | ||
− | |||
Try values of 120, 64 and 32. | Try values of 120, 64 and 32. | ||
− | |||
If this does not resolve the issue, then you may need an unusual_dev entry for your device. It would look something like this: | If this does not resolve the issue, then you may need an unusual_dev entry for your device. It would look something like this: | ||
− | |||
<pre><nowiki> | <pre><nowiki> | ||
UNUSUAL_DEV(0x03eb , 0x2002, 0x0100, 0x9999, | UNUSUAL_DEV(0x03eb , 0x2002, 0x0100, 0x9999, | ||
第29行: | 第20行: | ||
US_FL_IGNORE_RESIDUE), | US_FL_IGNORE_RESIDUE), | ||
</nowiki></pre> | </nowiki></pre> | ||
− | |||
The vendor and device ID's can be obtained from the output of "lsusb". The entry would be placed in drivers/usb/storage/unusual_devs.h. If you cannot compile your own kernel, please file a bug report, and we'll attempt to compile a test module for you. | The vendor and device ID's can be obtained from the output of "lsusb". The entry would be placed in drivers/usb/storage/unusual_devs.h. If you cannot compile your own kernel, please file a bug report, and we'll attempt to compile a test module for you. | ||
− | |||
[[category:CategoryDocumentation]] [[category:CategoryCleanup]] | [[category:CategoryDocumentation]] [[category:CategoryCleanup]] | ||
[[category:UbuntuHelp]] | [[category:UbuntuHelp]] |
2007年11月30日 (五) 16:41的版本
点击翻译: |
English |
请不要直接编辑翻译本页,本页将定期与来源同步。 |
USB2 Issues
This can be worked around easily. Simply run this command:
sudo rmmod ehci_hcd
Buffer I/O Errors
If you see errors related to Buffer I/O when attaching a USB Storage device, there are two ways to work around it. First, try using varying max_sectors settings, as such:
sudo sh -c "echo 120 > /sys/block/sda/queue/max_sectors_kb"
Try values of 120, 64 and 32. If this does not resolve the issue, then you may need an unusual_dev entry for your device. It would look something like this:
UNUSUAL_DEV(0x03eb , 0x2002, 0x0100, 0x9999, "Generic", "MusicDrive", US_SC_DEVICE, US_PR_DEVICE, NULL, US_FL_IGNORE_RESIDUE),
The vendor and device ID's can be obtained from the output of "lsusb". The entry would be placed in drivers/usb/storage/unusual_devs.h. If you cannot compile your own kernel, please file a bug report, and we'll attempt to compile a test module for you.