Huawei E160 with Lucid - still not working permanently

[rsw1965]

This solution also worked for my Huawei e169 - although I took a slightly different path to the rule.

I created a file called "temp-e169-modem.rules" in the /etc/udev/rules.d directory. I used the same settingsline as in the post above - except that I changed the product ID to 1001.

ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1001", RUN+="modem-modeswitch -v 0x%s{idVendor} -p 0x%s{idProduct} -t option-zerocd"

Nothing else in the file.

Rebooted and now the e169 has been picked up each time, unplugged and reconnected etc - all seems to work now.

The README in the /etc/udev/rules.d directory explained that rules written there would be persistent (while those in /lib/udev/ would be overwritten with any update. It also noted that simply using any text based name for the file was sufficient for it to be executed after all other rules.

Excellent outcome - Lucid was not happy with the e169 before this.

rsw1965

Thanks for the solution

[2badgersblue]

So, we're probably better off creating our own file in the /etc/udevrules.d directory or we may find the modem stops working after some future update.

Thanks for the heads up!

[RonCam]

This solution also worked for my Huawei e169 - ... Excellent outcome - Lucid was not happy with the e169 before this.

Your assistance will be appreciated to learn why I wasn't able to reproduce your success, also with Lucid / 10.04. From other posts, I suspect that in some cases, there may be a kernel problem, as well.

Could you please give the following command at your Command Prompt and, if you don't see the same kernel version, please paste what you see in a reply?

~$ cat /proc/version
Linux version 2.6.32-21-generic (buildd@rothera) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #32-Ubuntu SMP Fri Apr 16 08:10:02 UTC 2010

This is quite a mystery as to why some, such as yourself, have success in getting the E169 going, and others, with apparently the same Ubuntu version, have no luck. Something must be different ... I'll be curious to learn whether or not we have the same kernel version.

While we're comparing notes, would you please also give this command and see if your modem gives the identical read-out?

~$ lsusb
Bus 003 Device 006: ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem

When this modem installed 'without a hitch' on Jaunty, I recall a box popping up identifying it as a model E620. I now see that this came from its firmware.

The model number printed on the modem and its box is E169. I am wondering if the difference in results may (also) be due to a difference in firmware on various E169's? Is this model number I'm seeing just a typo, or could some E169's actually have incorrect firmware? Since your modem works so well, does the above line from yours read exactly the same, as mine?

[rsw1965]

cat/proc

Linux version 2.6.32-23-generic (buildd@rothera) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #37-Ubuntu SMP Fri Jun 11 07:54:58 UTC 2010


lsusb
Bus 007 Device 003: ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem

The kernel was updated in the last day or so and the modem has continued to work without any further changes required.

I had no problems at all out of the box on Ubuntu 9.04 with the e169 - but have only got it to work by creating the rules file above in Ubuntu 10.04.

rsw1965

[rsw1965]

This is the tail end of dmesg that I get after connecting and watching the e169 modem startup.

[ 48.292039] usb 7-1: new full speed USB device using uhci_hcd and address 2
[ 48.458185] usb 7-1: configuration #1 chosen from 1 choice
[ 50.496069] usb 7-1: USB disconnect, address 2
[ 50.739205] Initializing USB Mass Storage driver...
[ 50.739260] usbcore: registered new interface driver usb-storage
[ 50.739990] USB Mass Storage support registered.
[ 51.232038] usb 7-1: new full speed USB device using uhci_hcd and address 3
[ 51.399180] usb 7-1: configuration #1 chosen from 1 choice
[ 51.411085] scsi8 : SCSI emulation for USB Mass Storage devices
[ 51.414818] usb-storage: device found at 3
[ 51.414821] usb-storage: waiting for device to settle before scanning
[ 51.453349] usbcore: registered new interface driver usbserial
[ 51.454092] USB Serial support registered for generic
[ 51.454881] usbcore: registered new interface driver usbserial_generic
[ 51.454884] usbserial: USB Serial Driver core
[ 51.464572] USB Serial support registered for GSM modem (1-port)
[ 51.465431] option 7-1:1.0: GSM modem (1-port) converter detected
[ 51.465635] usb 7-1: GSM modem (1-port) converter now attached to ttyUSB0
[ 51.465650] option 7-1:1.1: GSM modem (1-port) converter detected
[ 51.465775] usb 7-1: GSM modem (1-port) converter now attached to ttyUSB1
[ 51.465790] option 7-1:1.2: GSM modem (1-port) converter detected
[ 51.465906] usb 7-1: GSM modem (1-port) converter now attached to ttyUSB2
[ 51.465930] usbcore: registered new interface driver option
[ 51.465932] option: v0.7.2:USB Driver for GSM modems
[ 56.413112] usb-storage: device scan complete
[ 56.418109] scsi 8:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2
[ 56.421100] scsi 8:0:0:1: Direct-Access HUAWEI SD Storage 2.31 PQ: 0 ANSI: 2
[ 56.443080] sr1: scsi-1 drive
[ 56.443224] sr 8:0:0:0: Attached scsi CD-ROM sr1
[ 56.443310] sr 8:0:0:0: Attached scsi generic sg2 type 5
[ 56.443453] sd 8:0:0:1: Attached scsi generic sg3 type 0
[ 56.475102] sd 8:0:0:1: [sdb] Attached SCSI removable disk
[ 61.098844] PPP BSD Compression module registered
[ 61.111114] PPP Deflate Compression module registered
[ 77.800424] ISO 9660 Extensions: Microsoft Joliet Level 3
[ 77.943347] ISOFS: changing to secondary root


Hope that might help you.

rsw1965

[rsw1965]

Have now been able to access a Windows machine to examine the diagnostics on the device.

This shows

IMEI: (not disclosing publicly)
IMSI: (not disclosing publicly)
FIRMWARE: 11.314.17.00.00
HARDWARE: CD57TCPU
MODEL: E169
SERIAL: (not disclosing publicy)

So that might also help identify why your modem is or is not responding.

[RonCam]

Thanks, rsw1965, for all the details.

I think we've ruled out a kernel problem and both E169's appear identical. I'm going to completely uninstall USB-ModeSwitch, reinstall, and start over. But, before I do, two questions:

Where did you get your USB-ModeSwitch package, the one that gives good results with the E169?

The version from the Ubuntu repository (including its configuration file) is a few months old, and the one from the Debian repository is only a couple of weeks old. A version number would be helpful, if not too much trouble.

Is ModemManager installed on your system?

On my system, Synaptic shows it's not installed, and a search for its files confirms this. NetworkManager is installed, of course.

There are differing opinions on this, one post saying the E169 started to work after a missing M-M was installed, and another, saying it shouldn't make any difference.

At this point all the differences between your success and my continuing problems will be resolved, so I'll make a fresh start and see what happens.

[rsw1965]

I am using the usb-modeswitch below - I am pretty sure from the Ubuntu repo.

* usb-modeswitch: handle USB devices with multiple modes
* Version 1.1.0 (C) Josua Dietze 2010
* Based on libusb 0.1.12

! PLEASE REPORT NEW CONFIGURATIONS !


As for the Modemmanager - synaptic shows it as installed - 0.3-0Ubuntu2 version.

I have had other GSM modem devices connected to the laptop such as a Nokia 6220c classic phone and a ZTE F156 phone - both of which can operate and were recognised as GSM modems prior to finally getting the e169 to work. In fact I was relying on the Nokia 6220c while I tried to get the e169 back into operation after upgrading from Ubuntu 9.04. Perhaps modem manager was installed as part of the that recognition process?

Hope this helps.

rsw1965

[RonCam]

As for the Modemmanager - synaptic shows it as installed - 0.3-0Ubuntu2 version.

This is likely the difference between your success and my failure, though through the info received on USB-ModeSwitch forum, they are saying it should make no difference. But, in my distro the box is clear, vs. dark green, for properly-installed packages.

But, apparently it does make a difference in some cases. I will go back, install both programs, and see what happens. We will do this, ModemManager first, then ModeSwitch on top of that.

Someone else on the Leeenux forum made passing reference to ModemManager helping for the E169, but then dropped the thread when more details were requested. So thanks so much.

Thanks for the interest and your reply - was in the hospital for 8 days right after I posted the message. Will get back to the "important things in life" (i.e., having my wireless connection set-up right ) ASAP.

[edit]
Yes, you are correct. They are telling me on the ModeSwitch forum that having the latest version of their utility is NOT necessary for the E169.
[/edit]

[dougfractal]

Thanks guys. I'm working now too. E169g

After following to many different guides, I ended up here.

I did reinstall usb-modeswitch and modemmanager

lsusb | grep -e "modem" 

Bus 003 Device 003: ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem

cat /proc/version
Linux version 2.6.32-23-generic (buildd@rothera) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #37-Ubuntu SMP Fri Jun 11 07:54:58 UTC 2010

sudo apt-get install usb-modeswitch-data usb-modeswitch

sudo nano /lib/udev/rules.d/61-option-modem-modeswitch.rules

insert this line.

ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1001", RUN+="modem-modeswitch -v 0x%s{idVendor} -p 0x%s{idProduct} -t option-zerocd"

Rebooted and working.