DD-WRT :: View topic - Problem with AT&T Laptop Connect Velocity 3G/UTMS

Problem with AT&T Laptop Connect Velocity 3G/UTMS

DD-WRT Forum Index -> Broadcom SoC based Hardware

Author

Message

Bird333
DD-WRT Guru

Joined: 07 Jun 2006
Posts: 809

Posted: Sat Jul 14, 2012 14:47 Post subject: Problem with AT&T Laptop Connect Velocity 3G/UTMS
I am trying to troubleshoot this for my mom. She has a E3000 router running 15962 Big. Does anyone know how to get this going? She enabled USB core, both 1.1's and the 2.0. She has tried all three dial strings but it won't connect. Any guidance would be appreciated.

Sponsor

LOM
DD-WRT Guru

Joined: 28 Dec 2008
Posts: 7647

Posted: Sat Jul 14, 2012 14:59 Post subject:
http://www.dd-wrt.com/wiki/index.php/Mobile_Broadband#Not_Supported_Modems_or_Not_Working_Modems _________________ Kernel panic: Aiee, killing interrupt handler!

Bird333
DD-WRT Guru

Joined: 07 Jun 2006
Posts: 809

Posted: Mon Jul 16, 2012 0:10 Post subject:

If I am reading this site correctly, this modem is supported. She ran this command

Code:

cat /proc/bus/usb/devices

This is output

Vendor=0af0 ProdID=7a05 Rev= 0.00
S: Manufacturer=Option N.V.
S: Product=Globetrotter HSUPA Modem

This is the output of 'dmesg'

Code:

BusyBox v1.13.4 (2010-12-24 03:40:45 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.
root@DD-WRT:~# dmesg
Linux version 2.6.24.111 (root@dd-wrt) (gcc version 4.1.2) #3889 Fri Dec 24 03:43:37 CET 2010
CPU revision is: 00019740
Determined physical RAM map:
memory: 04000000 @ 00000000 (usable)
Entering add_active_range(0, 0, 16384) 0 entries of 256 used
Zone PFN ranges:
Normal 0 -> 16384
HighMem 16384 -> 16384
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0 -> 16384
On node 0 totalpages: 16384
Normal zone: 0 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 16384 pages, LIFO batch:3
HighMem zone: 0 pages used for memmap
Movable zone: 0 pages used for memmap
Built 1 zonelists in Zone order. Total pages: 16384
Kernel command line: console=ttyS0,115200 root=1f02 rootfstype=squashfs noinitrd
Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, linesize 32 bytes.
Synthesized TLB refill handler (20 instructions).
Synthesized TLB load handler fastpath (32 instructions).
Synthesized TLB store handler fastpath (32 instructions).
Synthesized TLB modify handler fastpath (31 instructions).
PID hash table entries: 512 (order: 9, 2048 bytes)
CPU: BCM4716 rev 1 at 480 MHz
Using 240.000 MHz high precision timer.
console [ttyS0] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 58836k/65536k available (3173k kernel code, 6644k reserved, 1482k data, 224k init, 0k highmem)
Calibrating delay loop... 239.20 BogoMIPS (lpj=1196032)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
Generic PHY: Registered new driver
PCI: Using membase 8000000
PCI: Initializing host
PCI: Reset RC
PCI: Fixing up bus 0
PCI: Fixing up bridge
PCI: Setting latency timer of device 0000:01:00.0 to 64
PCI: Fixing up bridge
PCI: Setting latency timer of device 0000:01:00.1 to 64
PCI: Enabling device 0000:01:00.1 (0004 -> 0006)
PCI: Fixing up bus 1
NET: Registered protocol family 2
Time: MIPS clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
WRT610Nv2/E3000 GPIO Init
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
squashfs: version 3.0 (2006/03/15) Phillip Lougher
io scheduler noop registered
io scheduler deadline registered (default)
HDLC line discipline: version $Revision: 4.8 $, maxframe=4096
N_HDLC line discipline registered.
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = 8) is a 16550A
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
MPPE/MPPC encryption/compression module registered
NET: Registered protocol family 24
PPPoL2TP kernel driver, V1.0
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
PCI: Setting latency timer of device 0000:00:02.0 to 64
eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.10.56.27
PCI: Setting latency timer of device 0000:00:01.0 to 64
PCI: Enabling device 0000:01:01.0 (0000 -> 0002)
PCI: Setting latency timer of device 0000:01:01.0 to 64
Physically mapped flash: Found 1 x16 devices at 0x0 in 8-bit bank
Physically mapped flash: Found an alias at 0x800000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x1000000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x1800000 for the chip at 0x0
Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
Flash device: 0x800000 at 0x1c000000
bootloader size: 262144
nvram size: 61440
Physically mapped flash: Filesystem type: squashfs, size=0x5d44bb
partition size = 6157312
Creating 5 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "cfe"
0x00040000-0x007f0000 : "linux"
0x00190c00-0x00770000 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only
0x007f0000-0x00800000 : "nvram"
0x00770000-0x007f0000 : "ddwrt"
Found a 0MB serial flash
sflash: found no supported devices
Broadcom Watchdog Timer: 0.07 initialized.
u32 classifier
Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
ctnetlink v0.93: registering with nfnetlink.
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
ip_tables: (C) 2000-2006 Netfilter Core Team
ClusterIP Version 0.8 loaded successfully
TCP bic registered
TCP cubic registered
TCP westwood registered
TCP highspeed registered
TCP hybla registered
TCP htcp registered
TCP vegas registered
TCP scalable registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Welcome to PF_RING 3.2.1
(C) 2004-06 L.Deri <deri@ntop.org>
NET: Registered protocol family 27
PF_RING: bucket length 128 bytes
PF_RING: ring slots 4096
PF_RING: sample rate 1 [1=no sampling]
PF_RING: capture TX No [RX only]
PF_RING: transparent mode Yes
PF_RING initialized correctly.
PF_RING: registered /proc/net/pf_ring/
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
decode 1f02
VFS: Mounted root (squashfs filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 224k freed
roboswitch: Probing device eth0: found a 53115!
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
USB20H mdio control register : 0x8000000c
PCI: Setting latency timer of device 0000:00:04.1 to 64
ehci_hcd 0000:00:04.1: EHCI Host Controller
ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:04.1: irq 5, io mem 0x18004000
ehci_hcd 0000:00:04.1: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
USB Universal Host Controller Interface driver v3.0
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
USB20H mdio control register : 0x8000000c
PCI: Setting latency timer of device 0000:00:04.0 to 64
ohci_hcd 0000:00:04.0: OHCI Host Controller
ohci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:04.0: irq 5, io mem 0x18009000
usb 1-1: new high speed USB device using ehci_hcd and address 2
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
usb 1-1: configuration #1 chosen from 1 choice
br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
device br0 entered promiscuous mode
Algorithmics/MIPS FPU Emulator v1.5
device vlan1 entered promiscuous mode
device eth0 entered promiscuous mode
device eth1 entered promiscuous mode
device eth2 entered promiscuous mode
br0: port 3(eth2) entering learning state
br0: port 2(eth1) entering learning state
br0: port 1(vlan1) entering learning state
device br0 left promiscuous mode
device br0 entered promiscuous mode
device br0 left promiscuous mode
device br0 entered promiscuous mode
device vlan2 entered promiscuous mode
br0: topology change detected, propagating
br0: port 3(eth2) entering forwarding state
br0: topology change detected, propagating
br0: port 2(eth1) entering forwarding state
br0: topology change detected, propagating
br0: port 1(vlan1) entering forwarding state
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for Sierra USB modem
usbcore: registered new interface driver sierra
drivers/usb/serial/sierra.c: USB Driver for Sierra Wireless USB modems: v.1.7.0
drivers/usb/serial/usb-serial.c: USB Serial support registered for GSM modem (1-port)
usbcore: registered new interface driver option
drivers/usb/serial/option.c: USB Driver for GSM modems: v0.7.1
etherip: Ethernet over IPv4 tunneling driver
root@DD-WRT:~#

What can I check/do now?

LOM
DD-WRT Guru

Joined: 28 Dec 2008
Posts: 7647

Posted: Mon Jul 16, 2012 12:14 Post subject:
The stick has been added and will be supported in future builds. _________________ Kernel panic: Aiee, killing interrupt handler!

Bird333
DD-WRT Guru

Joined: 07 Jun 2006
Posts: 809

Posted: Mon Jul 16, 2012 13:36 Post subject:
I'm confused. So this stick is not currently supported? I thought the wiki page was showing stick that were already supported. Are you in charge of adding new sticks? I am trying to get an idea of when it might be supported so I can tell my mom. Thanks!

LOM
DD-WRT Guru

Joined: 28 Dec 2008
Posts: 7647

Posted: Mon Jul 16, 2012 14:21 Post subject:

Most stick on the wiki page are supported and works but some of them are wip, others may have been added in dd-wrt without any user feedback so modem port or driver assignment may be wrong and in need of changes.

I collect user info and help troubleshoot not working sticks and I usually send the developers an update every 2-3 weeks after which it is up to them to incorporate the changes in the dd-wrt build tree.

Your mum's modem will be included later this week together with a bunch of other updates but I have no idea of when the next public dd-wrt build will be released.
_________________
Kernel panic: Aiee, killing interrupt handler!

Bird333
DD-WRT Guru

Joined: 07 Jun 2006
Posts: 809

Posted: Mon Jul 16, 2012 17:32 Post subject:
Ok, thanks. I'll let her know.

Display posts from previous:

Page 1 of 1

DD-WRT Forum Index -> Broadcom SoC based Hardware

All times are GMT

Navigation

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum

Log in

Problem with AT&T Laptop Connect Velocity 3G/UTMS

Quick Links

Log in