Summary: | Huawei E169 doesn't work as mass storage anymore | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | justXi <gentoo> |
Component: | Current packages | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | jlec, ssuominen |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | ff | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
justXi
2009-10-06 08:54:44 UTC
Please tell us which kernel sources you use and which are affected. I use gentoo-sources and vanilla-sources. I testet these sources since 2.6.29 and had to patch all versions I want to be able to use the sd card feature of the huawei stick. Latest version that I patched was gentoo-sources-2.6.31-r1. Thanks for the info, assigning to maintainer Can you clarify what you're doing to get it working? Do you remove the patch? Or patch the kernel? An already applied patch or change removes some code: { int result; - us->iobuf[0] = 0x1; result = usb_stor_control_msg(us, us->send_ctrl_pipe, USB_REQ_SET_FEATURE, USB_TYPE_STANDARD | USB_RECIP_DEVICE, - 0x01, 0x0, us->iobuf, 0x1, 1000); + 0x01, 0x0, NULL, 0x0, 1000); US_DEBUGP("usb_control_msg performing result is %d\n", result); return (result ? 0 : -1); } I reverse this by hand, so the working version is: { int result; us->iobuf[0] = 0x1; result = usb_stor_control_msg(us, us->send_ctrl_pipe, USB_REQ_SET_FEATURE, USB_TYPE_STANDARD | USB_RECIP_DEVICE, 0x01, 0x0, us->iobuf, 0x1, 1000); US_DEBUGP("usb_control_msg performing result is %d\n", result); return (result ? 0 : -1); } btw: It is not an official patch file, I use a diff from working to not working revision or write it by hand. (In reply to comment #5) > An already applied patch or change removes some code: > > { > int result; > What file are you patching? /drivers/usb/storage/initializers.c I've got E169 as well, and I can confirm this is still a problem with Linux 2.6.32.1. Feel free to poke me at Freenode if you need something tested Have you gentlemen tried this patch: http://launchpadlibrarian.net/33442788/patch0 which is supposed to be included in the 2.6.31.1 release? (In reply to comment #9) > I've got E169 as well, and I can confirm this is still a problem with Linux > 2.6.32.1. > Weird, I thought that the problem was solved in the 2.6.31 series with the patch above. Check if the above patch fails, and I'll research thoroughly. Greg reports this as being from a buggy firmware: http://lkml.indiana.edu/hypermail/linux/kernel/0902.2/03459.html The old upstream bug has been closed as invalid relating to this: http://bugzilla.kernel.org/show_bug.cgi?id=12559 Unless a fix comes from them, not sure what else we can do here. My suggestions is too take this upstream to the manufacturer. |