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

[theThief]

Mark

Thanks for the help, my dmesg wasn't reporting that, it was still reporting wwan0 through the cdc_ether. I might have a slightly different version of the linux-2.6.39 kernel source, because the patch didn't work since that code change was on a slightly different line. Long story short, I changed the wrong line when I did it manually, I went back and changed the correct line and it does work now! Thanks! Just as an FYI, I am running VL600ZV4 as my firmware on the device. I had to look that up in my Windows VM, do you know how to find that in Ubuntu?

Cheers

[Prolixium]

Ah, glad that it's working now!

You can use the vl600-com.py script to display the version number using some GSM modem commands. Try using the ATI3 command. It showed this for me:

(evolution:9:54)% ./vl600-com.py
ATI3

Manufacturer: LG Electronics Inc.
Model: VL600  136
Revision:  S/W VER:  VL600ZV4
ESN: 0x80CC4F95
+GCAP: +CIS707-A, +CIS-856, CIS-856-A, +CGSM, +CLTE1

OK

You can also do some other things like send and receive SMSes, lock your SIM, brick your modem, etc., so be careful.

- Mark

[mirrorbox]

Hi,

I'm trying to get vl600 working as well. I've downloaded kernel 3.0.1:

Linux 3.0.1-030001-generic x86_64

and I was able to do ./vl600-attached.py and dhclient over wwan0 device.

9: wwan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ether 64:99:5d:fb:07:2f brd ff:ff:ff:ff:ff:ff
inet 169.254.6.76/16 brd 169.254.255.255 scope link wwan0:avahi
inet6 fe80::6699:5dff:fefb:72f/64 scope link
valid_lft forever preferred_lft forever

However, no traffic goes through. Default route is set for this interface. What could be the problem with that and how could I fix it?

[nhsb]

inet 169.254.6.76/16 brd 169.254.255.255 scope link wwan0:avahi

However, no traffic goes through. Default route is set for this interface. What could be the problem with that and how could I fix it?

169.*.*.* is self-assigned address. I guess it doesn't get IP address from DHCP.

[kjkeefe]

Thank you very much for doing so much work on this. I just got my VL600 and I'm really hoping to get it working on Ubuntu. Has there been any progress on making the config process a little more beginner friendly? Thanks!

[madhava_28]

>>>Turns out this is an easy fix, I've submitted a bug against 2.6.39:
>>>https://bugzilla.kernel.org/show_bug.cgi?id=39952

I could not open the above link. It always fails to connect.
Can some one share the one line fix in cdc_ether.c file

I have changes the line
.driver_info = (unsigned long)&wwan_info, as .driver_info = 0;

When I compile the kernel and plug in the modem I see kernel panic

Please see the dmesg below
[ 80.967002] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x1e6/0x1f0()
[ 80.967005] Hardware name: Vostro 3350
[ 80.967008] NETDEV WATCHDOG: eth3 (lg-vl600): transmit queue 0 timed out
[ 80.967010] Modules linked in: cdc_acm lg_vl600 cdc_ether usbnet binfmt_misc parport_pc ppdev snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_intel snd_hda_codec joydev i915 snd_hwdep arc4 usbhid snd_pcm hid iwlagn psmouse aesni_intel cryptd serio_raw snd_seq_midi snd_rawmidi drm_kms_helper snd_seq_midi_event drm aes_i586 snd_seq dell_wmi aes_generic i2c_algo_bit uvcvideo sparse_keymap snd_timer videodev snd_seq_device video lp dell_laptop xhci_hcd snd btusb dcdbas parport mac80211 cfg80211 soundcore snd_page_alloc bluetooth usb_storage uas ahci libahci r8169
[ 80.967059] Pid: 0, comm: kworker/0:0 Not tainted 3.1.4-lg1 #2
[ 80.967061] Call Trace:
[ 80.967068] [<c1048842>] warn_slowpath_common+0x72/0xa0
[ 80.967072] [<c1456a36>] ? dev_watchdog+0x1e6/0x1f0
[ 80.967075] [<c1456a36>] ? dev_watchdog+0x1e6/0x1f0
[ 80.967079] [<c1048913>] warn_slowpath_fmt+0x33/0x40
[ 80.967083] [<c1456a36>] dev_watchdog+0x1e6/0x1f0
[ 80.967088] [<c1056b24>] run_timer_softirq+0xf4/0x2b0
[ 80.967093] [<c10aea59>] ? __rcu_process_callbacks+0x49/0x300
[ 80.967096] [<c1456850>] ? netif_carrier_off+0x30/0x30
[ 80.967100] [<c104f352>] __do_softirq+0x82/0x170
[ 80.967104] [<c15087ad>] ? asiliantfb_pci_init+0x66/0x392
[ 80.967108] [<c10acf34>] ? irq_node_proc_open+0x14/0x20
[ 80.967112] [<c104f2d0>] ? send_remote_softirq+0x50/0x50
[ 80.967114] <IRQ> [<c104f666>] ? irq_exit+0x76/0xa0
[ 80.967121] [<c15248c9>] ? smp_apic_timer_interrupt+0x59/0x88
[ 80.967126] [<c151db99>] ? apic_timer_interrupt+0x31/0x38
[ 80.967130] [<c104007b>] ? proc_sched_show_task+0x16cb/0x1a70
[ 80.967135] [<c12bed28>] ? intel_idle+0xb8/0x110
[ 80.967140] [<c1409f0d>] ? cpuidle_idle_call+0x9d/0x100
[ 80.967144] [<c10018d7>] ? cpu_idle+0x97/0xe0
[ 80.967148] [<c1515ca8>] ? setup_APIC_timer+0x5c/0x60
[ 80.967152] [<c151532e>] ? start_secondary+0x1e0/0x1e7
[ 80.967156] ---[ end trace daf5bce0fb62e797 ]---


Please let me know if I missed anything.

[Prolixium]

>>>Turns out this is an easy fix, I've submitted a bug against 2.6.39:
>>>https://bugzilla.kernel.org/show_bug.cgi?id=39952

I could not open the above link. It always fails to connect.
Can some one share the one line fix in cdc_ether.c file

I have changes the line
.driver_info = (unsigned long)&wwan_info, as .driver_info = 0;

When I compile the kernel and plug in the modem I see kernel panic

Please see the dmesg below
[ 80.967002] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x1e6/0x1f0()
[ 80.967005] Hardware name: Vostro 3350
[ 80.967008] NETDEV WATCHDOG: eth3 (lg-vl600): transmit queue 0 timed out
[ 80.967010] Modules linked in: cdc_acm lg_vl600 cdc_ether usbnet binfmt_misc parport_pc ppdev snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_intel snd_hda_codec joydev i915 snd_hwdep arc4 usbhid snd_pcm hid iwlagn psmouse aesni_intel cryptd serio_raw snd_seq_midi snd_rawmidi drm_kms_helper snd_seq_midi_event drm aes_i586 snd_seq dell_wmi aes_generic i2c_algo_bit uvcvideo sparse_keymap snd_timer videodev snd_seq_device video lp dell_laptop xhci_hcd snd btusb dcdbas parport mac80211 cfg80211 soundcore snd_page_alloc bluetooth usb_storage uas ahci libahci r8169
[ 80.967059] Pid: 0, comm: kworker/0:0 Not tainted 3.1.4-lg1 #2
[ 80.967061] Call Trace:
[ 80.967068] [<c1048842>] warn_slowpath_common+0x72/0xa0
[ 80.967072] [<c1456a36>] ? dev_watchdog+0x1e6/0x1f0
[ 80.967075] [<c1456a36>] ? dev_watchdog+0x1e6/0x1f0
[ 80.967079] [<c1048913>] warn_slowpath_fmt+0x33/0x40
[ 80.967083] [<c1456a36>] dev_watchdog+0x1e6/0x1f0
[ 80.967088] [<c1056b24>] run_timer_softirq+0xf4/0x2b0
[ 80.967093] [<c10aea59>] ? __rcu_process_callbacks+0x49/0x300
[ 80.967096] [<c1456850>] ? netif_carrier_off+0x30/0x30
[ 80.967100] [<c104f352>] __do_softirq+0x82/0x170
[ 80.967104] [<c15087ad>] ? asiliantfb_pci_init+0x66/0x392
[ 80.967108] [<c10acf34>] ? irq_node_proc_open+0x14/0x20
[ 80.967112] [<c104f2d0>] ? send_remote_softirq+0x50/0x50
[ 80.967114] <IRQ> [<c104f666>] ? irq_exit+0x76/0xa0
[ 80.967121] [<c15248c9>] ? smp_apic_timer_interrupt+0x59/0x88
[ 80.967126] [<c151db99>] ? apic_timer_interrupt+0x31/0x38
[ 80.967130] [<c104007b>] ? proc_sched_show_task+0x16cb/0x1a70
[ 80.967135] [<c12bed28>] ? intel_idle+0xb8/0x110
[ 80.967140] [<c1409f0d>] ? cpuidle_idle_call+0x9d/0x100
[ 80.967144] [<c10018d7>] ? cpu_idle+0x97/0xe0
[ 80.967148] [<c1515ca8>] ? setup_APIC_timer+0x5c/0x60
[ 80.967152] [<c151532e>] ? start_secondary+0x1e0/0x1e7
[ 80.967156] ---[ end trace daf5bce0fb62e797 ]---


Please let me know if I missed anything.

Looks like bugzilla.kernel.org is hosed at the moment. I'd recommend using the following full patches, since they contains a stability fix in the case of corrupted packets and fix the LG-VL600 being marked as wwan:

https://lkml.org/lkml/2011/8/6/131
https://lkml.org/lkml/2011/11/9/380

I've submitted all of the above to the Linux kernel, and they've been applied in linux-next, I believe. Hopefully 3.2 won't require any patching!

- Mark

[madhava_28]

Mark,

Thank you for the help.
I was able to get the modem connected with the patches using wwan interface.
However there seems to be some issue with the coexistence with Wifi.

I have done the following testing.
Connect WiFi and run ping with WiFi Interface ping www.google.com -I wlan0

Now plug in the LG modem and run the script, when the green light starts blinking, ping through the wlan0 interface stops. and I ping fails with wwan0 interface also.

When the LG modem is unplugged and replugged again ping was successful with wwan0 interface.

Is this a limitation with Modem. Originally I had 2.6.38 kernel version, I have downloaded 3.1.4 version of kernel and applied the patches.

Thanks,
Madhava

[Prolixium]

Mark,

Thank you for the help.
I was able to get the modem connected with the patches using wwan interface.
However there seems to be some issue with the coexistence with Wifi.

I have done the following testing.
Connect WiFi and run ping with WiFi Interface ping www.google.com -I wlan0

Now plug in the LG modem and run the script, when the green light starts blinking, ping through the wlan0 interface stops. and I ping fails with wwan0 interface also.

When the LG modem is unplugged and replugged again ping was successful with wwan0 interface.

Is this a limitation with Modem. Originally I had 2.6.38 kernel version, I have downloaded 3.1.4 version of kernel and applied the patches.

Thanks,
Madhava

Hmm, first off, I think having both Wi-Fi and the LG modem enabled w/both addressed by DHCP is not the best scenario (or Wi-Fi and wired Ethernet, etc.). You'll have two default routes and connections that bind to the IP of one of the interfaces may send packets out the other interface in a round-robin fashion (I think), making it look like the source address is spoofed.

Although I haven't tried your exact scenario, I think I have a guess why your ping commands stop working. Verizon's LTE service seems to immediately drop the connection if it sees a packet sourcing from an IPv4 address other than the one received by DHCP. I hit this when testing some things with OpenVPN and I had my tun0 IP traffic routed out wwan0 by accident. It can also happen with iptables and SNAT rules if you don't drop INVALID packets on the internal interface (some packets will leak through untranslated).

It's not specific to the LG-VL600 since it happened to me with the Pantech UML290 too. I had the same problem on Mac OS X with the LG-VL600, as well.

Yes, it does require a replug of the USB modem, unfortunately.

I'm guessing that you've got some traffic that's leaking out wwan0 with a source IP that's bound to your wlan0 interface, most likely your ping traffic causing Verizon to terminate the connection. With two default routes, the -I flag might not help, it'll just set the source IPv4 address to whatever's on the interface you specify, but the packets might still be sent out the wrong interface.

If you're curious about this, bring up wlan0 and wwan0, start a tcpdump on wwan0, then issue the ping commands to nuke the wwan0 connection. Most likely you'll see some packets leaving wwan0 with the wlan0 source IP.

Hope this helps..

- Mark

[jwilliams77006]

Thank you very much for doing so much work on this. I just got my VL600 and I'm really hoping to get it working on Ubuntu. Has there been any progress on making the config process a little more beginner friendly? Thanks!

I have taken the plunge away from Windows, and have been following this thread carefully. As a noob, I would love a bit more info on the procedure for getting the VL600 to work on Ubuntu 10.0