Verizon wireless UM150 USB Modem works on ubuntu v7.1 but not v8.04
UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
When I got to this step, (I was connected) I entered
sudo route add gw xx.xxx.xxx.x (I entered the local ip address)
I got this message
gw: Unknown host
I don't think a gateway is necessary for a ppp connections, by design all traffic goes through the peer. At lease I've never had to set one and I've been using a verizon cell phone for internet connection going back to at least 2005 & ubuntu 5.04
Since I posted my original problem, I've found that the answer is simpler than I thought.
the article: article,"/feature/52729", on linux.com was sufficient but seemed a little complicated.
It is only necessary to:
1. use a windows XP computer to initialize the UM150 using the Verizon Access Manager software that comes with the UM150.
2. For Linux, create two text files: 1xevdo and 1xevdo_chat in the directory: /etc/ppp/peers/.
3. execute the command:
art@art-HP:~$ sudo pppd call 1xevdo
The first file can be listed as follows (where the ########### is replaced by the phone number for the UM159):
After executing the third step, the UM150 should be working. This process now works on at least one Dell Inspiron 1100 Laptop and a Dell Dimension 3000 for Ubunbtu V8.04, and for the Dell Inspiron 300 and 1100 laptops, a Gateway GPS-400 desktop and a HP Pavilion 7920 Desktop with V7.1.
I am trying to implement the above process on an HP Mini 1000 Mi. When I execute step 3, terminal reports "unrecognized option 'ttyACMO'". Any ideas?
I am trying to implement the above process on an HP Mini 1000 Mi. When I execute step 3, terminal reports "unrecognized option 'ttyACMO'". Any ideas?
Nevermind the prior post. I realized the line was supposed to be tty ACM0, corrected it and step 3 executed, but I am still not online and could still use ideas.
Nevermind the prior post. I realized the line was supposed to be tty ACM0, corrected it and step 3 executed, but I am still not online and could still use ideas.
I apologize for the multiple postings, but I just got this working. I am still not sure what the ultimate problem was, but it may have been in the line " ATZ in 1xevdo chat, which took me several tries to get the spacing correct.
I also configured the ppp connection in Network Settings on the Mini 1000 Mi. Not sure if this is necessary, but I'm not going to mess with it since its working. For the record, my settings are
connection type GPRS/UMTS
access point name vzw3g
username **********@vzw3g.com
password vzw3g
modem port /dev/ttyS0
Even though I didn't get any replies, many thanks to awcrooke for his enormously helpful recipe.
Because the Verizon service is so bad here and I need to connect more than one PC to the internet (Verizon goes out of their way to not help you) I ended up with an external antenna to the UM150 and installing a Kyocera wireless router with a USB connection which automagically does it all via 'normal' linux wireless connectivity.
Verizon still stinks, but is better now mainly due to the external antenna.
I apologize for the multiple postings, but I just got this working. I am still not sure what the ultimate problem was, but it may have been in the line " ATZ in 1xevdo chat, which took me several tries to get the spacing correct.
I also configured the ppp connection in Network Settings on the Mini 1000 Mi. Not sure if this is necessary, but I'm not going to mess with it since its working. For the record, my settings are
connection type GPRS/UMTS
access point name vzw3g
username **********@vzw3g.com
password vzw3g
modem port /dev/ttyS0
Even though I didn't get any replies, many thanks to awcrooke for his enormously helpful recipe.
It seems I spoke too fast last Friday. After getting the UM150 to connect exactly once, I have been unable to reconnect again, although I have not changed any settings since the one successful connection. I know the UM150 is working, because I can use it to establish a connection on a WinXP laptop. Also the HP Mini 1000 Mi recognizes the UM150, because when I plug it in, ttyACM0 pops up in the /dev folder. But I cannot establish a point to point connection. Any thoughts and suggestions would be appreciated.
It seems I spoke too fast last Friday. After getting the UM150 to connect exactly once, I have been unable to reconnect again, although I have not changed any settings since the one successful connection. I know the UM150 is working, because I can use it to establish a connection on a WinXP laptop. Also the HP Mini 1000 Mi recognizes the UM150, because when I plug it in, ttyACM0 pops up in the /dev folder. But I cannot establish a point to point connection. Any thoughts and suggestions would be appreciated.
This will, I hope, be my last post in this thread, but perhaps nevertheless helpful to other newbies dealing with this issue. My problem turned out to be a very simple one, the clue to which I found in the syslog file once I figured out how to access logging. Line 6 of the 1xevdo_chat file is '' ATZ, which I had read and typed as " ATZ, that is two single quotes with no spaces between them, rather than a double quote. Why it worked once for me with the incorrect line, I still have no idea. Also, no need to configure the ppp0 setting in the HP Mini 1000 Mi Network settings. I do still have a question if anyone cares to respond. Is there a disconnect command, or is simply removing the UM150 OK?
using dial setup mentioned in prior posts (pppd). Add the following lines to an executable script in /etc/ppp/ip-up.d. I called the script ttyACM0. Ensure the script is executable. HTH
using dial setup mentioned in prior posts (pppd). Add the following lines to an executable script in /etc/ppp/ip-up.d. I called the script ttyACM0. Ensure the script is executable. HTH
#!/bin/sh -e
route add default gw $PPP_LOCAL
Please forgive me if this is a stupid question, but what is the need for/advantage of automatically creating a default gateway, as connection through the device by calling the 1xevdo script seems to work fine without it?
The one problem I have had is that where an open Wi-Fi connection is available, my netbook wants to connect to it, rather than through the UM150. Does the above force the UM150 as the default, or if not, is there another way to force disconnection from the Wi-Fi to enable the UM150 to take precedence?
Since I posted my original problem, I've found that the answer is simpler than I thought.
the article: article,"/feature/52729", on linux.com was sufficient but seemed a little complicated.
It is only necessary to:
1. use a windows XP computer to initialize the UM150 using the Verizon Access Manager software that comes with the UM150.
2. For Linux, create two text files: 1xevdo and 1xevdo_chat in the directory: /etc/ppp/peers/.
3. execute the command:
art@art-HP:~$ sudo pppd call 1xevdo
I have been using this fix for several months with success. However, I have found one annoying problem, and wonder whether there is a further workaround. Sometimes, when I plug in the UM150 device, the system identifies it as ttyUSBn, where n=1,2 and/or 3, rather than ttyACM0. Usually when this happens, though not always, if I restart with the UM150 plugged in, it is properly identified, and there is no further problem. This seems to happen randomly. Is there a way to force the system to identify the UM150 as ttyACM0, or to alias it so that it doesn't matter?
I have been using this fix for several months with success. However, I have found one annoying problem, and wonder whether there is a further workaround. Sometimes, when I plug in the UM150 device, the system identifies it as ttyUSBn, where n=1,2 and/or 3, rather than ttyACM0. Usually when this happens, though not always, if I restart with the UM150 plugged in, it is properly identified, and there is no further problem. This seems to happen randomly. Is there a way to force the system to identify the UM150 as ttyACM0, or to alias it so that it doesn't matter?
I have found one answer to my own question, which I am sure is not the most efficient way of doing this, but it works. I created a second version of 1xevdo, which references ttyUSB1, rather than ttyACM0 (ttyUSB0 didn't work), and called it 1xevdo_usb. I can manually check in /dev whether the UM150 has been installed as ttyACM0 or ttyUSB1, and then call the right 1xevdo file, whichever it happens to be.
When I have a little time, I will experiment with combining commands in a single file and other approaches, but in the meantime, if someone can help with a simple efficient way to do this, I would appreciate it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
