huawei e1692 don't work

[pier_andreit]

I installed a new 11.2 and my huawei e1692 isn’t recognized, before in suse 11.1 worked perfectly but now not.
I also tried installing the software given by the provider that in 11.1 worked, now not.
kde=Versione 4.3.4 (KDE 4.3.4) “release 2”
kernel=2.6.31.5-0.1-desktop

[ojio]

Hello, pier_andreeit
maybe you could try this link Huawei E1692 On Linux HOWTO.
Here is an howto for your card. this could help to solve your problem.

[pdc_2]

hi pierandreit;

in the guide that ojio points you towards, it uses usb_modeswitch as a crucial first step

you say all was good for you on Suse 11.1;

so do you need usb_modeswitch there?

Were you using Gnome in 11.1;

I have been very impressed at how Gnome of 11.2 just goes ahead and autoconfigures older modems like the Huawei E220;

to “see” the zeroCD devices, I right click on the icon and select “eject”;

so what does

lsusb
give you; as a command in a terminal?

and does the device give you an icon on your desktop?

[pier_andreit]

@ojio

Hello, pier_andreeit
maybe you could try this link Huawei E1692 On Linux HOWTO.
Here is an howto for your card. this could help to solve your problem.

yes was the one I followed when I installed in 11.1, but now the driver isn’t found. I tried also to unmount the only thing is reconized by the system, the memory card

run this
linux-dvkc:/home/pla/Documenti # modinfo option
filename: /lib/modules/2.6.31.5-0.1-desktop/kernel/drivers/usb/serial/option.ko
license: GPL
version: v0.7.2
description: USB Driver for GSM modems
author: Matthias Urlichs <smurf@smurf.noris.de>
srcversion: 694FB10D1163C2918AF5069
among them is present:
alias: usb:v12D1p140CddcdscdpicFFiscFFipFF*

1. edited usb_modeswitch.conf as suggested
2. run usb_modeswitch as root

linux-dvkc:/home/pla/Documenti # usb_modeswitch

• usb_modeswitch: tool for controlling “flip flop” mode USB devices
• Version 0.9.6 (C) Josua Dietze 2009
• Works with libusb 0.1.12 and probably other versions

Looking for target devices
No target device found
Looking for default devices
Found default devices (1)
Prepare switching, accessing latest device
Looking for active default driver to detach it
No driver found. Device probably not initialized. Trying to continue …
Setting up communication with device
Error: no MessageEndpoint given. Can’t send message. Aborting

[pier_andreit]

@pdc_2

hi pierandreit;

in the guide that ojio points you towards, it uses usb_modeswitch as a crucial first step

yes is present in both 11.2 and 11.1

@pdc_2

you say all was good for you on Suse 11.1;
so do you need usb_modeswitch there?

yes

@pdc_2

Were you using Gnome in 11.1;
I have been very impressed at how Gnome of 11.2 just goes ahead and autoconfigures older modems like the Huawei E220;

isn’t so old I bought in 2009, no I was using kde4 and kde3 in 11.1 and kde4 in 11.2

@pdc_2

to “see” the zeroCD devices, I right click on the icon and select “eject”;
so what does

no icons is visible in kde4, the zeroCD is not shown

@pdc_2

give you; as a command in a terminal?

and does the device give you an icon on your desktop?

no icons

linux-dvkc:/home/pla/Documenti # lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 05a9:2640 OmniVision Technologies, Inc. OV2640 Webcam
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 05e3:0718 Genesys Logic, Inc.
Bus 002 Device 008: ID 12d1:1446 Huawei Technologies Co., Ltd.
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 15ca:00c3 Textech International Ltd. Mini Optical Mouse
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 007 Device 003: ID 413c:8126 Dell Computer Corp. Wireless 355 Bluetooth
Bus 007 Device 004: ID 0a5c:4502 Broadcom Corp.
Bus 007 Device 005: ID 0a5c:4503 Broadcom Corp.
linux-dvkc:/home/pla/Documenti #

[akira_bel]

Ok, 3 days working on it and now it is all working.
Here is what I did to make it work.

Folow this How To:

Huawei E1692 On Linux HOWTO

But one change was necessary, where you see

Huawei E1692

DefaultVendor= 0x12d1
DefaultProduct= 0x1446

TargetVendor= 0x12d1
TargetProduct= 0x140c

MessageContent=“55534243000000000000000000000011060000000000000000000000000000”

CheckSuccess=5

Use

Huawei E1692

DefaultVendor= 0x12d1
DefaultProduct= 0x1446

TargetVendor= 0x12d1
TargetProduct= 0x140c

MessageEndpoint=0x01 <— Added this line
MessageContent=“55534243000000000000000000000011060000000000000000000000000000”

CheckSuccess=5

Now usb_modeswitch is working, after runing usb_modeswitch the zeroCD device is mounted and the modem activated.

Now all you have to do is install de application dealer
and use it to connect.

[pdc_2]

well done;

what made you insert

MessageEndpoint=0x01

(as that is different to the usb_modeswitch.conf file?)

[pier_andreit]

GRANDEEEEEEEEEEEEEEEE!!!
NOW IT WORKS!!!
Many thanks akira, a tenth af beer for you

but usb_modeswitch doesn’t start automatically, even after a restart, where I have tu put rules in /etc/udev/rules.d, because I found a couple of places (but may be them are wrong :)) and I’m in doubt
10-Huawei-Datacard.rules
with this inside about my huawei
BUS==“usb”, SYSFS{modalias}==“usb:v12D1p1446*”, KERNEL==“sr[0-9]”, NAME=“hwcdrom”, MODE=“0666”
ACTION==“add”, BUS==“usb”, SYSFS{modalias}==“usb:v12D1*”, RUN+="/usr/local/Alice_MOBILE_E1692/driver/HWActivator"
ACTION==“add”, SYSFS{idVendor}==“12d1”, KERNEL==“ttyUSB*”, RUN+="/bin/touch /dev/huawei_mobile"
ACTION==“remove”, KERNEL==“ttyUSB*”, RUN+="/bin/rm -f /dev/huawei_mobile"
BUS==“usb”, SYSFS{modalias}==“usb:v12D1p140C*”, KERNEL==“ttyUSB*”, SYSFS{bInterfaceNumber}==“00”, SYSFS{bInterfaceProtocol}==“ff”, NAME=“ttyUSB_utps_modem”
BUS==“usb”, SYSFS{modalias}==“usb:v12D1p140C*”, KERNEL==“ttyUSB*”, SYSFS{bInterfaceNumber}==“01”, SYSFS{bInterfaceProtocol}==“ff”, NAME=“ttyUSB_utps_ndis”
BUS==“usb”, SYSFS{modalias}==“usb:v12D1p140C*”, KERNEL==“ttyUSB*”, SYSFS{bInterfaceNumber}==“02”, SYSFS{bInterfaceProtocol}==“ff”, NAME=“ttyUSB_utps_diag”
BUS==“usb”, SYSFS{modalias}==“usb:v12D1p140C*”, KERNEL==“ttyUSB*”, SYSFS{bInterfaceNumber}==“03”, SYSFS{bInterfaceProtocol}==“ff”, NAME=“ttyUSB_utps_pcui”

and 51-usb-modeswitch.rules
with nothing inside regarding my huawei

or other??

[pdc_2]

but usb_modeswitch doesn’t start automatically, even after a restart

the usb_modeswitch website

talks of a file

/etc/udev/rules.d/80-usb_modeswitch.rules

that contain

the udev rules starting the wrapper if a known device ID (vendor/product) is recognized

do you have such a file: you can check graphically by clicking on the icon “MY COMPUTER” and drilling down from the etc folder; you can open the file with a text editor and read the file

[akira_bel]

About the “MessageEndpoint=0x01” line, I found it somewere in another Linux forum, and between a modem not working and a not working modem I decided to take my chances

And about the usb_modeswitch I created an icon to it in my kde menu. When I need the autostart I’ll look in this forum.

thanks