Integration of 3G Wireless Modem Detection - 4.1.2 & 4.2.1

[rerwin]

mikeb,
Keeping in mind that I do not have a wireless modem and rely on the Internet for my info, please tell me more about how you use usb_modeswitch, and then about "eject". My implementation is intended to handle the mode-switch by way of udev rules, such as the one I posted above.

My understanding of usb_modeswitch is that the normal way to use it is to first edit the usb_modeswitch.conf file. So I assume you removed (all six of) the ";"s from this entry in the file:

Code: Select all

########################################################
# Novatel Wireless Ovation MC950D HSUPA
# Novatel Wireless Merlin XU950D
# Novatel Wireless Ovation 930D
#
# Contributor: Razvan Dragomirescu, Mike Kirk

;DefaultVendor=  0x1410
;DefaultProduct= 0x5010

;TargetVendor=   0x1410
;TargetProduct=  0x4400

;MessageEndpoint=0x09
;MessageContent="5553424312345678000000000000061b000000020000000000000000000000"

# Note: detaching the storage driver might work as well


########################################################

Then you would run usb_modeswitch from the command line with no parameters. Right? If so, the rule does that for you -- if you remove the initial "#" from the "#ACTION=" line (and reboot). Please tell me whether that works for you. Thanks.

As for the hang in the full installation, we need more expertise. It is out of my league.
Richard

[mikeb]

Then you would run usb_modeswitch from the command line with no parameters. Right? If so, the rule does that for you -- if you remove the initial "#" from the "#ACTION=" line (and reboot). Please tell me whether that works for you. Thanks.

Ok exactly as you described.
eject /dev/sr0 also works for this modem though it may need sr1 or 2 if other optical drives were present but for simplicity I would stick to the usb_modeswitch as some modems cannot be toggled by eject it seems from my research.

I will try the udev command ... I noticed that the endpoint is listed in the conf...sorry I missed that one.

The hanging is a pain...did it when it had suse on too...and it's not my laptop ...just makes testing awkward but then again this might help to find a solution

regards

mike

ps as a general point having those connect/disconnect functions as separate icons or menu entries would to me be more convenient (and obvious and smarter than windows)....this machine for example has three ways to connect to a network and ne'er the twain shall meet...

[Redmun]

Hi, I have tried to get this card to work with many linux distro's....no dice. Works w/winblow's no worries. I tried your .pets to no avail, being a total linux noob, i'm sure ive done something wrong. But i followed the instructions in your guide, and i get to dial my IP.......and thats where it sits My provider is telstra bigpond. The card is actually a novatel expedite wireless EU870D usb card inside my laptop so not really accessible as far as unplugging goes. Am running puppy -4.1.2-k2.6.25.16-seamonkey from usb frugal install, (should i be running a full install?) If someone could help me also with the correct bigpond mobile broadband settings that would be great!!

thx

[tubby]

I am now using my 3g dongle to type this, i installed your pup and connected through PuPDial.
As i am very new to Linux and Puppy i cannot say if my dongle would have connected with or without your pet addition.
How i did it.
I entered *99***3* where it says phone number, and here i am.
As i cannot receive 3g at this location i am connected at normal gprs speed, to say i am delighted is an under statement as Vodaphone said it would be impossible to use Linux to connect.
The modem is a Huawei Mobile Connect-3g modem, it has a slot for a memory card as well.

[rerwin]

Fan-tastic, tubby! Glad it worked with no fuss at all. But you must also have entered an APN (like internet or Telstra-something or Vodaphone-something), didn't you? Or is that optional? BTW, you could probably connect, but only after entering some commands in the console, or maybe using the GPRS option in the Connect Wizard. My intent is for pupdial to work just as you found it to - with no fiddling.

So that I can track what works, please post or send me the vendor and product ID of the modem (from pupscan, USB interfaces). Better yet, PM me the content of the /tmp/udevtrace-modem.log file. Thanks for your positive report.

Redmun,
Welcome to our group. I responded to your PM (with the requested data) before checking this thread. Spent the day researching, finding nothing obvious to fix. So I requested more details in hope of some clues.

Regarding frugal or full installations: please stay with the frugal, since others have reported problems with the full installation even though the equivalent frugal installation works.

I advised in my PM to you to try using fake logon and password values, but tubby appears to have succeeded without setting them. Go figure -- I think I saw that wvdial requires those fields, but maybe that has been fixed.

One note about the new "-6" version: It seems possible that things might not work the first time you boot up with the dotpets installed, but a reboot should straighten that out. Please report any such behavior, just so we know. I no one reports it, I will assume it never happens.

Keep those reports coming! Thanks.
Richard

[tubby]

Here is the pupdial log,
--> WvDial: Internet dialer version 1.53
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT*99***3#
--> Waiting for carrier.
ATDT*99***3#
CONNECT
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Thu Feb 26 08:10:16 2009
--> pid of pppd: 4053

As you can see i have no entry in ATZ left it blank, the only entry is the ATDT which is for my supplier who is
Vodaphone Mobile Connect 9 by the way i am in the UK.
I looked at the other log you asked for but it is very long and seems to say that device not found at every entry but i noticed it did show my modem
This is part of log,




Looking for default devices
No default device found. Is it connected? Bye

module_usbserial
module_option
Rule_triggered_for_E169_loading_ of_option_driver.
usb_v12d1_p1001_00_____________________HUAWEI Mobile_
tty_ttyUSB0
Rule_triggered_for_E169_loading_ of_option_driver.
usb_v12d1_p1001_00_____________________HUAWEI Mobile_
tty_ttyUSB2
Rule_triggered_for_E169_loading_ of_option_driver.
usb_v12d1_p1001_00_____________________HUAWEI Mobile_
tty_ttyUSB1
Rule_triggered_for_E169_loading_ of_option_driver.
usb_v12d1_p1001_00_____________________HUAWEI Mobile_

* 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

DefaultVendor=0x12d1
DefaultProduct=0x1001
TargetVendor=0x0
TargetProduct=0x0
TargetClass=0x0
DetachStorageOnly=0
HuaweiMode=1
SierraMode=0
SonyMode=0
MessageEndpoint=0x0
MessageContent=""
Interface=0x0

Hope this helps, i have connected using said modem to send this.

[tubby]

I forgot to say that my dongle must be plugged in before booting otherwise it does not get connected, also there is no icon on the desktop.
As it has memory slot i tried with memory but still no desktop icon.

[Redmun]

half your luck, linux in general seems to hate my laptop modem.

[zgp152]

I see that E220 can be used to connect via Dialing function.
I understand that Rerwin is developing autodetection to make it easier. Pls correct me if I am wrong.
Good timing: I plan to take Huawei E220 into use in the near future.

Is the Puppy 4.2 (now in beta) planned to include autodetection or what will be the most handy way to add it if not included.

Rgds zgp152

[rerwin]

Tubby,
Thanks for the info on your modem. It is the same as muggins'. But the last I heard from him is that the driver did not load automatically for him. You demonstrate that it is possible. So I can update the status listing, in the second posting in this thread.

Redmun,
I am distressed that you cannot connect, but sense that others have had such problems, and I saw no solution. However, a change is being made to the latest "option" driver that appears to involve your modem, but not clear how. Assuming your settings are good, the only other thing I have seen is a report that you have to wait a long time for something to time out, before Telstra (I think) connects. Maybe that does not apply to you.

zgp152,
Yes, I am automating the PupDial wireless dialup process, and think I have it done, other than handling individual problems with it. The downloads are in the first posting in this thread and should work with 4.2 when it comes out, as well as 4.1.x-standard. It is too late for me to request its inclusion in 4.2, and the package awaits further input from users, to this thread, to determine whether it works generally. Please try out the "-6" version of the dotpet and the driver dotpets, and tell us how it goes. I think someone reported that the E220 does work.
Richard

UPDATE 3/2/09: Redmun has sent me data for diagnosing his difficulty with pupdial. It got me to question my choice of some pupdial logic, so I want to mention it here. While designing the changes, all the examples I used as reference suggested to me that an APN is required for all wireless-modem connections; I coded that into pupdial. Without an APN, pupdial assumes an ordinary analog modem; with one, it adds the wireless-related initialization strings, particularly the ones specifying the APN and PIN (if specified).

If an APN is actually optional or forbidden for some ISPs, please tell me. In the meantime, please use a dummy APN that the ISP would ignore. If an APN is not always required, I would modify pupdial to look for "none" to indicate wireless-but-no-APN. Right now I use the presence of an APN, the presence of a wireless driver module in the lsmod listing, and certain tty* device names as the way to know the modem is wireless. Ideas on other ways to do this are welcome. I assume that ttyACM? and ttyUSB? can be either wired or wireless; please correct me, if wrong.
Richard

[Redmun]

hi richard, I tried again...no luck. I looked at various logs in windows to see how it connects to bigpond. It uses APN: telstra.bigpond and username. Ive attached tbwbcm.log from windows if thats any help. Bigpond uses its own connection manager (i have not been able to connect through the bundled dell windows conn manager). Perhaps that has something to do with why Linux can't connect to the internet?

WINDOWS XP
tbwbcm.log (verbose logging)

[rerwin]

This new version of the wireless modem integration package (downloadable from the first posting in this thread) does not affect most users. But anyone who's tried editing initialization strings Init4 and Init6-9 would see them become corrupted over time, making them useless. That is now corrected. I have also "refined" the determination of which modems are "wireless", requiring the option of adding a PIN or APN, versus those that merely emulate the behavior of wired analog modems. In addition, I have added mode-switching support for the Huawei C300, which is otherwise not recognized by either USB_modeswitch or the "option" driver module.

1. For those affected by the init4/Init6-9 corruption, after installing the -7 package, please delete from /etc/wvdial.conf all of the lines in the [wireless] section (except for Init5 if you have used an APN). Then run PupDial and immediately exit from it, to restore the default content for re-editing. Those Init lines should not contain any "\" or "$" characters, which constitute the corruption.

2. Here is how I set up the logic for selecting wireless Init-string groups. This affects what modems allow use of the PIN, APN and edited Init strings. Wired analog and some USB modems do not accommodate the added initialzation strings. The USB modems include those using the cdc-acm and pl2303 drivers and device ttyACM0, because they are either wired or are controlled in the same way as wired. Some of those use device ttyUSB0, as do the newer 3G modems. The extended modem control Init4-9 strings are sent by pupdial only for modems using devices ttyUSB*, ttyHS*, and ttynoz* AND that use drivers hso, option, nozomi, and sierra. If you have a modem that needs the PIN or APN, etc., parameters and is not included in the "wireless" category just defined, please notify me to change my assumptions about this.

3. I have attempted support for the Huawei C300 in response to a request from rajesh009 in another thread:
http://www.murga-linux.com/puppy/viewto ... 985#280985
Here is the essence of the thread:

How to install HUAWEI USB CDC MODEM (C300)?
rajesh009:
I have a Huawei CDMA Mobile C5320 which supports three modes:
1. USB Disk
2. Data
3. PC Sync

Windows XP detects it as HUAWEI USB CDC C300 modem in data mode and dial to the internet. Problem is that I cannot install my HUAWEI USB CDC MODEM (C300) on Puppy Linux. I tried the Connect panel on the Puppy Linux desktop, through dial-up...
I would be grateful if you dedicated Puppy Linux users help me out for solving this problem with simple easy steps. I am yet to understand the confusing coding used to deliver commands in Linux overall.Then again I will try if coding has to be done.

Patriot:
While looking up info on this issue back then, someone seems to have a method to get it to work, here :
http://anand.tch.in/2008/06/connecting- ... uawei.html
http://ubuntuforums.org/showthread.php?t=836952

rerwin:
I see elsewhere [including in the above links] that your modem IDs are vendor 12d1, product 3197, which is apparently not yet supported in linux, except that someone has posted a fix to a good driver to add it...
I could attempt to make that fix; however, the modem may require a "mode switch specification", which has not yet been published. There might be a chance that a mode switching is not needed; so give me a couple of days to work on the fix.

Instead of providing commands, I prefer to try to integrate support for the modem into the wireless-integration package, so it "just works". I have created a mode-switch rule most likely to work as it does for other Huawei modems. However, the driver, module option, must be forced to load, using the BootManager to add it to the load list (with no parameters). (Eventually the driver will probably support automatic loading for the modem; I prefer not to change and recompile the driver unless forcing fails.) I depend on feedback from anyone trying this modem, to know whether it works with Puppy.

Again, if you are not affected by the above modifications to pupdial, do not feel pressured to upgrade to "-7". And if you notice anything not quite right with pupdial (however you may define that), please notify me so I can correct it. Thank you, all, for helping me with this project. I am please with the results so far, but need reports on more different 2G/3G modems in order to feel comfortable submitting it for the "official" puppy.
Richard

[Aitch]

Hi Richard

Well done for your efforts

I am still in Germany, but my friend & his Icon225 are no longer here - going to Czechoslovakia, I believe, so my chances of testing any further have sadly ended

Aitch

[plumtreed]

Hello rerwin, got back to Australia after months in the UK trying to use the 3 USB network. You got it going in Puppy and my problems seemed to be mostly with the network, remoteness and climatic conditions.

In Australia I use an ethernet connection and a 'tethered' Telstra 3g mobile with Ubuntu but haven't been able to get it working in Puppy yet. It goes ok with GnomePPP but is not fired up via NetworkManager. Oddly, in GnomePPP it just fired up with the configuration details I used on the 3 unit in the UK???? I didn't have to change a thing, Just plugged it in and it connected.

Some details, ZTE F156 dual band UMTS-HSDPA. lsusb reports the vendor=05c6 product=0x6000 It usually gets recognized as E220 but also as a CDMA which is no longer used in Australia!

I'm trying to sort in on 4.1.2 on a live CD, I've downloaded your -7pet

Any suggestions?

[rerwin]

plumtreed,
Welcome back. I am curious how your modem seems to work in Ubuntu (8.10?). Given my understanding of how devices get associated with drivers, I see no connection in either Ubuntu nor Puppy that matches vendor=05c6 and product=0x6000. When your modem is connected (to the internet) in Ubuntu, would you do the following?:
- On command line, enter "lsmod" and look for drivers "option", "usbserial", hso", and "nozomi". I expect you to find usbserial and option.
- On command line, enter "lsusb" and post the result. (Puppy doesn't have lsusb.)

As for what to try next:
- After installing only the pupdial...-7 dotpet, reboot and try to connect. Use lsmod to check for modules usbserial and option (or whichever you found in Ubuntu).
- If that doesn't work and option is not in the lsmod output, use BootManager to force loading of the option module, and reboot.
- Verify with lsmod that option got loaded, then try Io connect.
If that doesn't work ,install the usb_modeswitch dotpet, reboot and try again.

If none of those steps works, I can send you a udev rule to cause a mode switch of the device, although there is nothing released by the usb_modeswitch developer. Be sure your pupdial values are correct -- errors generate messages that seem unrelated, but stop connection.

Also, when you are in Puppy with the modem plugged in, please post the content of PupScan's USB interfaces list. The device could exist as both a usbstorage and option/usbserial device; I wonder if the vendor and device/product IDs are the same. The product ID both Ubuntu and Puppy recognize is 6613; I wonder if the product ID gets switched from 6000 to 6613 in Ubuntu somehow.
Richard

[plumtreed]

I use Ubuntu 8.04LTS but have updated NetworkManager to 0.7 so it works as it would in at least 8.10. I have edited the phone no and included something for the name and password so I now get auto detect on this 'modem'..

Lsusb in Ubuntu provides 05c6 & 6000

lsmod in Ubuntu provides 'usbserial' 35688 4 AIRPRIME
...the others don't show.

lsmod in Puppy doesn't comment on either option,usbserial,hso or nozomi

After following all the other Ideas I am no further ahead. There is no recognition of this 'modem' nor is there any in the pupscan.

I have double checked the values and think they are OK

I can connect by using ...modprobe usbserial vendor=0x05c6 product=0x6000

[tempestuous]

Lsusb in Ubuntu provides 05c6 & 6000

Forum members wescht and dejan555 both report the USB ID for the E220 as
vendor=0x12d1 product=0x1003

So it appears that the E220 wireless modem is known by more than one set of USB ID's.
The "option" module recognises USB ID 12d1:1003, but not 05c6:6000
so in the latter case the old-fashioned method of loading the usbserial module with the correct USB ID's specified is clearly necessary.

[tempestuous]

Vendor 05c6 is Qualcomm, so assuming that 05c6:6000 is the same product as the Huawei 12d1:1003, it should be possible to hack the option module to recognise 05c6:6000 as an E220.
The updated version of the option module is now available here -
http://www.murga-linux.com/puppy/viewto ... 448#254448

[Dougal]

Vendor 05c6 is Qualcomm, so assuming that 05c6:6000 is the same product as the Huawei 12d1:1003, it should be possible to hack the option module to recognise 05c6:6000 as an E220.

That is probably the correct thing to do, as newer kernels have it included in "option".

[plumtreed]

Thanks Tempetuous, that certainly does the job! Smooth as silk and comfortable to use.