add strings for Huawei E1750 3G USB modem

[iav]

Binary package hint: usb-modeswitch

To add support of Huawei E1750 3G USB modem add

to etc/udev/rules.d/usb_modeswitch.rules:
SUBSYSTEM=="usb", SYSFS{idProduct}=="1446", SYSFS{idVendor}=="12d1", RUN+="/usr/sbin/usb_modeswitch"

to etc/usb_modeswitch.conf:

DefaultVendor= 0x12d1
DefaultProduct= 0x1446

TargetVendor = 0x12d1
TargetProduct= 0x1001

MessageContent="55534243000000000000000000000011060000000000000000000000000000"
MessageEndpoint=0x01
CheckSuccess=5

source: http://ubuntu-se.org/phpBB3/viewtopic.php?f=223&t=41986&p=341147
I did it, and now it works on my Eee 901, Ubuntu Jaunty, and usb-modeswitch_1.0.2-1~jaunty1~drdanz1_i386.deb

[tankdriver (stoneraider-deactivatedaccount)]

@iav: I can't find these files in ubuntu karmic alpha6.
Did you try if this device works ootb in karmic?

[iav (iav)]

I boot from iso, written to usb flash.
When I insert dongle into booted system, it mount disks, exactly as jaunty without usb-modeswitch.

Then I install usb-modeswitch from universe repository, and look into /etc/usb_modeswitch.conf.
There was no DefaultProduct= 0x1446 string.

So, "out of the box" it not work.

[Toni Spets (hifi)]

I bought a "E180" from my provider and it was infact the same as in this bug. I only added these lines into usb_modeswitch.conf and it works:

# Huawei E1692
DefaultVendor= 0x12d1
DefaultProduct= 0x1446

MessageContent="55534243000000000000000000000011060000000000000000000000000000"

Even when booting the modem starts up correctly without any additional udev configuration.

[Didier Raboud (odyx)]

@Toni Spets: Could you try with usb-modeswitch un-installed ? From Karmic's version of udev, udev might be enough to switch most devices…

Best regards, OdyX, Debian maintainer of usb-modeswitch

[Søren Holm (sgh)]

Hi

I have a Huaweg E1752. Apparently it is a little backwards with this one. It does not mout the file-system until I execute usb_modeswitch. The internet connection does not work in any of the modes.

[Przemek K. (azrael)]

Request for new modem rules should be filed against udev, since usb-modeswitch is not installed by default in Karmic.

[Didier Raboud (odyx)]

Hi,

I don't know why this bug still applies to udev. AFAICT, udev is no more supposed to handle the switching. I reported bug #519216 to get the latest usb-modeswitch version from Debian in Lucid. I can't do more.

Best regards, OdyX, Debian usb-modeswitch{,-data} maintainer

[Scott James Remnant (Canonical) (canonical-scott)]

On Mon, 2010-02-15 at 12:43 +0000, Didier Raboud wrote:

> I don't know why this bug still applies to udev. AFAICT, udev is no more
> supposed to handle the switching. I reported bug #519216 to get the
> latest usb-modeswitch version from Debian in Lucid. I can't do more.
>
> Best regards, OdyX, Debian usb-modeswitch{,-data} maintainer
>
I don't know what is supposed to handle the switching?

udev still includes extras/modem-modeswitch - so I'd say udev is
supposed to? (With my udev upstream hat on)

Scott
--
Scott James Remnant
<email address hidden>

[Martin Pitt (pitti)]

usb-modeswitch != modem-modeswitch, though (closing udev task)

@Scott: both programs are considered to be a rather bad userspace hack. Also see https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2010-February/010647.html and #ubuntu-devel:

[15:18] <cjwatson> Mirv: surely we just want the kernel to DTRT by default rather than going down the usb-modeswitch rat-hole; this is the upstream trend
[15:18] <cjwatson> Mirv: it already DTRT for quite a few devices, rendering usb-modeswitch unnecessary as well as its existing unreliable state :-)
[15:19] <cjwatson> Mirv: see e.g. linux/drivers/usb/storage/option_ms.c, the zerocd stuff
[15:19] <Mirv> cjwatson: ok, that's what I was thinking about but then again usb-modeswitch seems to continue to develop. maybe then the reason for its existence goes away soon(ish)
[15:19] <cjwatson> Mirv: personally, when I needed such a device to work, I found it *easier* to beat the kernel into shape than to wrestle with the various possible userspace nightmares
[15:20] <cjwatson> and I'm not a kernel hacker
[15:20] <cjwatson> the userspace stuff just plain didn't work for me
[15:20] <cjwatson> I'd be very concerned about advertising that it's the Way to get things to work, and thus undermining getting things fixed in the kernel
[15:21] <Mirv> I'm just thinking about the user space impact for lucid and if it's possible to evaluate it. But maybe it's indeed too hackish solution to be called a solution, no matter how it would help some.
[15:22] <cjwatson> I found that in some situations the presence of udev rules for this actually made things worse, because I ended up with races
[15:22] <Mirv> I was asking it mostly because I haven't bumped into the numerous problems described by some others, while in my case it was simply doesn't work at all / works fluently with usb-modeswitch.
[15:22] <cjwatson> in your position, I would try to get the kernel to switch the device to networking mode by default
[15:23] <cjwatson> which is probably just a matter of a quirk in the appropriate mass storage driver
[15:23] <Mirv> Well, anyway, may that thread rest in peace then.
[15:23] <Mirv> cjwatson: Ok, will put that to my todo list.
[15:23] <mvo> tkamppeter: I looked at the hplip thing again and I noticed that there is a com.hp.hplip dbus object already. I think its best to use that, maybe in cooperation with upstream and add a method to trigger the NeedPlugin signal. if the signal then is available from the app it should work. the reason it is currently not working is that there is no signal on the com.hp.hplip that is available on the bus registered
[15:23] <cjwatson> I agree that usb-modeswitch is often a way to get otherwise non-working hardware to work
[15:24] <cjwatson> I'm just not very convinced it's a real properly supportable option
[15:25] <cjwatson> but I'm just another user from this point of view, albeit one who ended up in quite a few discussions with various appropriate upstreams last time round :)
[15:25] <Mirv> ok :) well, there is still a little bit of time if someone has an undisputable perfect solution that makes all 3G modems work out-of-the-box.
[15:26] <Mirv> but otherwise let's just...

[Martin Pitt (pitti)]

I synced 1.1.0-2 from sid. Thanks Didier!

[Didier Raboud (odyx)]

I kept usb-modeswitch alive as Debian package because of this message: http://bugs.debian.org/563740#20 which points to that thread on the kernel mailing-list: http://patchwork.kernel.org/patch/67600/

Until a better solution is found in Debian/Ubuntu, I will keep maintaining usb-modeswitch…