NEW verizon lg vl600 4g(lte) aircard not working

[senor_smile]

I realize this is probably a little early to start a discussion for. I have a few of the new Verizon lte aircards and have had NO success in getting either wvdial to dial up to it or to have network manager do anything. Network manager recognizes it as eth1. When it tries to get a connection via dhcp, it spins for a while and I assume just times out. I assume there are going to be some sort of updates/extras to get these new sim card based aircards to make a connection through Linux.

As I find out any new information, I will update this thread for any future searchers.

[alexfish]

hi

don't know much about these devices

if usb can see how it lists with this code if system 10.04 , 10.10


Code:

usb-devices

locate the lines which indicate the device

hopefully it will show the drivers involved, and may point as to where to look
for possible areas as to how to connect - IE scan network - or configure and connect
via AT commands. also looking for the actual Manufacture

if system lower than mentioned can try

Code:

lsusb -t

or

lsusb -v

with the -v look for the lines wich would point to the drivers of the devices

once got info , may look up manufacturing detail , and look at the actual drivers which

are loading , and look up the source at , they may possibly fall into two areas

usb (class and serial ) and net, + need kernel version used

http://lxr.linux.no/#linux+v2.6.36/drivers

also can see how it lists in the devs , if tty allocated / the drivers may give a clue
to the appended to tty , IE ttyXXXX

Code:

ls -al /dev/tty

and look through the list

another area look is in the log file viewer

Added :since drivers of some description are loading and NM is trying to connect ; Can't imagine that your far away from getting this device to work

Also have a look at ifconfig / and the default files , maybe it will show the type of interface, and other info/ if nothing shows then possible assume , may need software or user space to kick it in
if got a serial port terminal see if it responds to AT commands ,could also try AT Command "ATI" it may list the bands it operates on
alexfish

[senor_smile]

hi

don't know much about these devices

if usb can see how it lists with this code if system 10.04 , 10.10


Code:

usb-devices

locate the lines which indicate the device

hopefully it will show the drivers involved, and may point as to where to look
for possible areas as to how to connect - IE scan network - or configure and connect
via AT commands. also looking for the actual Manufacture

if system lower than mentioned can try

Code:

lsusb -t

or

lsusb -v

with the -v look for the lines wich would point to the drivers of the devices

once got info , may look up manufacturing detail , and look at the actual drivers which

are loading , and look up the source at , they may possibly fall into two areas

usb (class and serial ) and net, + need kernel version used

http://lxr.linux.no/#linux+v2.6.36/drivers

also can see how it lists in the devs , if tty allocated / the drivers may give a clue
to the appended to tty , IE ttyXXXX

Code:

ls -al /dev/tty

and look through the list

another area look is in the log file viewer

alexfish

Thanks! That was quite a bit of information. I am running 10.10 64-bit. usb-devices yielded the following:

T: Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 6 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=02(commc) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1004 ProdID=61aa Rev=01.00
S: Manufacturer=LG ELECTRONICSInc
S: Product=LG UDC-AHB Subsystem
C: #Ifs= 4 Cfg#= 1 Atr=80 MxPwr=400mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=06 Prot=00 Driver=cdc_ether
I: If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_ether
I: If#= 2 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm
I: If#= 3 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm

I see the first two cdc_ether entries. That must be its loading as ether1, although it can't pick up an address. Everything else in that entry is greek to me.

I catch it appearing as ttyACM0 under dev when plugged in. My previous working wvdial.conf file fails however:

--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
--> Sending: ATQ0
--> Re-Sending: ATZ
--> Modem not responding.

Here's my wvdial.conf:

[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Modem Type = USB Modem
#Baud = 460800
Baud = 240000000
New PPPD = yes
Modem = /dev/ttyACM0
ISDN = 0
; Phone = <Target Phone Number>
; Password = <Your Password>
; Username = <Your Login Name>
Carrier Check = no
Dial Command = atdt
Username = 2065555555@vzw3g.com
Password = vzw
Phone = #777
Stupid Mode = 1

[alexfish]

hi

ADDED: 11 DEC 2010: PDF documentation Worth reading : Please note this is direct download Link

CDC Ethernet model Communications class
(many Cable Modems and networked devices)Experimental/2.4, Working/2.6

The Kernel Module:
looking up first part / cdc_ether.c

http://lxr.linux.no/#linux+v2.6.36/d...sb/cdc_ether.c



here it lists the device ID's and the listing

have you found a listing in the devs for ttyXXX

then possible try for AT command response on the cdc-acm : ACMxxx ports if listing

try each port:

Also search for any dev ports on the cdc_ether.c /

if you can't find the ports

look in /sys/bus/devices/usb1/

or usb2/ try 1 first
or usb0/ if this one exits then look in here as well

look in each of the folders that list like 1-2 ; 1-3 and so on

in each folder look at the file "manufacturer" your looking for "LG ELECTRONICSInc"
when got look at the folders at top of page ;

each folder will hold other info , then in each folder holds more folders

some don't get listed by the usb-device command , any how , look for a folder
which would list as ttyXXX , or a file not listing as "driver,ep_x,power,subsystem"

[alexfish]

If you don't have Serial port terminal
and found the ttyACMx

Try this

edit the ttyACMx to suite or what evever shows from the devs

if you have no serial port terminal try this

open up first terminal and enter this command

Code:

tr -s "\n" < /dev/ttyACMx

this will show any responses from the device if any

to send commands open up a second terminal

send the commands like so this is on port ttyACM0 as said , have to edit ports to suit
something like ttyACM1 : according to the drivers it should have a data port

/* a data interface altsetting does the real i/o */
215 d = &info->data->cur_altsetting->desc;
216 if (d->bInterfaceClass != USB_CLASS_CDC_DATA) {
217 dev_dbg(&intf->dev, "slave class %u\n",
218 d->bInterfaceClass

Code:

echo -e "AT\r" > /dev/ttyACM0

Added don't forget to try other ports associate with the device , IE, ones not listing as ttyXXX, it may be worth a try

Updated some info

here are some option to look at

The device may work as a standard cdma connection with the wvdial
if the correct port is found

but know it can connect as CDC Ethernet interface (assumed by looking at the drivers)

to get the Ethernet up and running (4g ), possible need to send the correct command

one know sequence is

sending the correct at command to set the function IE: some known ones are AT+FUN=* where the * represents the number = cdma or 4g (the CDC Ethernet interface)
possible to send AT commands AT+CFUN? (to find the device setting) or AT+CFUN=? (to find the settings available): some of the bands may be revealed by the AT command " ATI "

AT+CGDCONT=1,"IP","proxy"



where the proxy is an apn or server address

these are the some known Verizon

Verizon 1
Gateway IP: 12.168.70.74
Port: 9201

Verizon 2
Gateway IP: 153.114.115.100
Port 9203
Verizon 3

APN: No configuration needed
Username for APN: No configuration needed
Password for APN: No configuration needed
WAP Gateway IP: 153.114.115.100
WAP Gateway Port: 9203

so need to find out the above {ask Verizon}

2. then need to issue a command to to start the interface this is one known AT command

AT*ENAP=1,1

to stop the interface

AT*ENAP=0

to get the interface up and running and seen on the system , I would assume need to launch dhclient

dhclient usb*

IE :

dhclient usb0

As said , I don't know the device and all the above are avenues to look at { as mention in earlier post , do you need to configure the routing tables (ifconfig, for an interface)
even may need to install a program like "resolvconf" to guide the address IE address in the /etc/resolv.conf ( Limitation of resolvconf = conflicts with wvdial , so will un-install wvdial , and also make gnomeppp useless)

[PlancksCnst]

I've been working on this today. I got both the LG and the Pantech devices in today.

The LG device is unresponsive. It does not give any responses to any commands on the tty port (and I tried turning echo on via ATE). Trying to bring up the ethernet interface only switches it to unknown state.



The Pantech device is responds to commands. I accedentally clobbered the pdp 1 context by trying an APN before first checking to see what it was set for. There were two other PDP contexts already configured as follows

+CGDCONT: 3,"IPV4V6","vzwinternet","0.0.0.0",0,0
+CGDCONT: 4,"IPV4V6","vzwapp","0.0.0.0",0,0

Originally, I was able to get it to connect to the vzwinternet context. pppd showed a successful authentication but then did not get any ip address or gateway.

On Windows, the LG device was able to connect using CDMA but not LTE. The Pantech device was able to connect to LTE and got 16Mb downlink and 0.9Mb uplink. My next avenue will be to use a USB analyzer to find what the Windows software is doing.

[alexfish]

I've been working on this today. I got both the LG and the Pantech devices in today.

The LG device is unresponsive. It does not give any responses to any commands on the tty port (and I tried turning echo on via ATE). Trying to bring up the ethernet interface only switches it to unknown state.



The Pantech device is responds to commands. I accedentally clobbered the pdp 1 context by trying an APN before first checking to see what it was set for. There were two other PDP contexts already configured as follows

+CGDCONT: 3,"IPV4V6","vzwinternet","0.0.0.0",0,0
+CGDCONT: 4,"IPV4V6","vzwapp","0.0.0.0",0,0

Originally, I was able to get it to connect to the vzwinternet context. pppd showed a successful authentication but then did not get any ip address or gateway.

On Windows, the LG device was able to connect using CDMA but not LTE. The Pantech device was able to connect to LTE and got 16Mb downlink and 0.9Mb uplink. My next avenue will be to use a USB analyzer to find what the Windows software is doing.

Hi

can you post the details and sequence of the AT commands or commands send for each instance

also are you sending the commands direct , then calling the pppd

thanks in advance

alexfish

[PlancksCnst]

The LG device continues to be unresponsive on Linux. On the Pantech device, I ran through a bunch of commands, but to get it to connect, I did

at*99***3#

This was to use the 3rd pdp context definition which was already present in the device. It returned

CONECT 100000000

I'm not sure about the number of zeros, but it was a bunch. I then connected pppd to the terminal, and it authenticated and stopped.

I was able to do some USB sniffing on the LG device when talking to the Windows driver. The software did these:

ATE0V1
AT+CPIN?
AAT+CLCK="SC",2
AT+GCAP?
AT+CMEE=1

When the software actually connected, it didn't seem to be because of any AT command. I haven't tried to decode the binary data yet, but I did see 'vzwinternet' in ASCII among the data, suggesting it connected using that APN.

Attached is a capture that you can view using TotalPhase Data Center (zero-cost). This was my attempt at talking to the device on Linux both using screen and echoing straight to the device.

[mpareja]

Expirencing the same behavior, I have been rendering the same results. Is there anything else that we may try? Also network manager os detecting it as a unknown wired device?
U 10.10 64b

[mpareja]

See Items in bold.

Bus 001 Device 006: ID 1004:61aa LG Electronics, Inc. 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            2 Communications
  bDeviceSubClass         2 Abstract (modem)
  bDeviceProtocol         1 AT-commands (v.25ter)
  bMaxPacketSize0        64
  idVendor           0x1004 LG Electronics, Inc.
  idProduct          0x61aa 
  bcdDevice            1.00
  iManufacturer           1 LG ELECTRONICSInc
  iProduct                2 LG UDC-AHB Subsystem
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength          145
    bNumInterfaces          4
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              400mA
    Interface Association:
      bLength                 8
      bDescriptorType        11
      bFirstInterface         0
      bInterfaceCount         2
      bFunctionClass          2 Communications
      bFunctionSubClass       6 Ethernet Networking
      bFunctionProtocol       0 
      iFunction               0 
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      6 Ethernet Networking
      bInterfaceProtocol      0 
      iInterface              0 
      CDC Header:
        bcdCDC               1.10
      CDC Union:
        bMasterInterface        0
        bSlaveInterface         1 
      CDC Ethernet:
        iMacAddress                      4 64995DFA3356
        bmEthernetStatistics    0x00000000
        wMaxSegmentSize              22528
        wNumberMCFilters            0x0000
        bNumberPowerFilters              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               4
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Association:
      bLength                 8
      bDescriptorType        11
      bFirstInterface         2
      bInterfaceCount         2
      bFunctionClass          2 Communications
      bFunctionSubClass       2 Abstract (modem)
      bFunctionProtocol       1 AT-commands (v.25ter)
      iFunction               0 
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol      1 AT-commands (v.25ter)
      iInterface              0 
      CDC Header:
        bcdCDC               1.00
      CDC ACM:
        bmCapabilities       0x07
          sends break
          line coding and serial state
          get/set/clear comm features
      CDC Union:
        bMasterInterface        2
        bSlaveInterface         3 
      CDC Call Management:
        bmCapabilities       0x03
          call management
          use DataInterface
        bDataInterface          3
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               4
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        3
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x05  EP 5 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)

Also I remember when configuring the device on windowz it did not create a PPP connection like previous usb broadband modems. Almost like there is an ethernet controller + serial Comm (configuration interface).