Confirm: stock kernel 2.6.31-16.53 does not fix the issue for (my) Huawei E270.
A custom kernel that includes the patch
diff --git a/drivers/usb/storage/initializers.c b/drivers/usb/storage/initializers.c index 105d900..ec17c96 100644 --- a/drivers/usb/storage/initializers.c +++ b/drivers/usb/storage/initializers.c @@ -102,5 +102,5 @@ int usb_stor_huawei_e220_init(struct us_data *us) USB_TYPE_STANDARD | USB_RECIP_DEVICE, 0x01, 0x0, NULL, 0x0, 1000); US_DEBUGP("Huawei mode set result is %d\n", result); - return 0; + return (result ? 0 : -ENODEV); }
which differentiated the 'apw10' test kernel from 'apw5 works correctly.
Needless to say I'm holding on to that patch like grim death ;-)
Confirm: stock kernel 2.6.31-16.53 does not fix the issue for (my) Huawei E270.
A custom kernel that includes the patch
diff --git a/drivers/ usb/storage/ initializers. c b/drivers/ usb/storage/ initializers. c usb/storage/ initializers. c usb/storage/ initializers. c huawei_ e220_init( struct us_data *us)
USB_ TYPE_STANDARD | USB_RECIP_DEVICE,
0x01, 0x0, NULL, 0x0, 1000);
US_DEBUGP( "Huawei mode set result is %d\n", result);
index 105d900..ec17c96 100644
--- a/drivers/
+++ b/drivers/
@@ -102,5 +102,5 @@ int usb_stor_
- return 0;
+ return (result ? 0 : -ENODEV);
}
which differentiated the 'apw10' test kernel from 'apw5 works correctly.
Needless to say I'm holding on to that patch like grim death ;-)