Automatic Activation, Hotplug and UDEV, Configuration
Post Reply
Tomasz_O
Posts: 1
Joined: 18 Apr 2015, 16:14

Teltonika WiMAX UM62XX USB dongle on Raspberry pi

Post by Tomasz_O » 18 Apr 2015, 16:30

Hi All,

I am trying to setup Teltonika WiMAX UM62XX USB dongle on Raspberry pi with raspbian OS.
This modem normally creates virtual dhcp server and web server, and then adds eth interface connected to this virtual server.
But when I plug them to Raspberry PI it is visible as mas storage drive and I am not able to switch them to network mode.

I have installed usb_modeswitch software, but unfortunately there are some problems, network interface eth1 is created but no IP address is assigned to them, also there is some error with usb_modeswitch log.

I am attaching content of usb_modeswitch log and syslog.
I will appreciate any help.

Tomek

Code: Select all

pi@redBox ~ $ lsusb
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 007: ID 148e:099a EVATRONIX SA

Code: Select all

ifconfig -a

eth0      Link encap:Ethernet  HWaddr b8:27:eb:b0:87:e1
          inet addr:192.168.7.33  Bcast:192.168.7.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2365 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2407 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:185495 (181.1 KiB)  TX bytes:576012 (562.5 KiB)

eth1      Link encap:Ethernet  HWaddr 00:1e:42:02:6f:62
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1408 (1.3 KiB)  TX bytes:1408 (1.3 KiB)

Code: Select all

pi@redBox ~ $ cat  /var/log/usb_modeswitch_1-1.2:1.0


USB_ModeSwitch log from Sat Apr  18 14:41:42 CEST 2015

Raw args from udev: /1-1.2:1.0

Using global config file: /etc/usb_modeswitch.conf
Using top device dir /sys/bus/usb/devices/1-1.2
----------------
USB values from sysfs:
  manufacturer  Teltonika
  product       UM62XX
  serial        303137334444
----------------
bNumConfigurations is 1 - don't check for active configuration
Found packed config collection /usr/share/usb_modeswitch/configPack.tar.gz
SCSI attributes not needed, moving on
checking config: pack/148e:a000
! matched. Reading config data
Extracting config 148e:a000 from collection /usr/share/usb_modeswitch/configPack.tar.gz
config: TargetClass set to 02
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1

Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 6 -v 148e -p a000 -f $configBuffer

Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------

Reading long config from command line

 * usb_modeswitch: handle USB devices with multiple modes
 * Version 1.2.3 (C) Josua Dietze 2012
 * Based on libusb0 (0.1.12 and above)

 ! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor=  0x148e
DefaultProduct= 0xa000
TargetVendor=   not set
TargetProduct=  not set
TargetClass=    0x02
TargetProductList=""

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=1
MobileActionMode=0
CiscoMode=0
MessageEndpoint=  not set
MessageContent=""
NeedResponse=0
ResponseEndpoint= not set

InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled


Use given bus/device number: 001/006 ...
Looking for default devices ...
 bus/device number matched
  searching devices, found USB ID 148e:a000
   found matching vendor ID
   found matching product ID
   target class 02 not matching
   adding device
 Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using first interface: 0x00

USB description data (for identification)
-------------------------
Manufacturer: Teltonika
     Product: UM62XX
  Serial No.: 303137334444
-------------------------
Sending Sequans vendor request
 OK, Sequans request was sent
Bus/dev search active, referring success check to wrapper. Bye.

ok:busdev
--------------------------------
(end of usb_modeswitch output)

Checking success of mode switch for max. 20 seconds ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...

Target config not matching - current values are
    1-1.2:1.0/bInterfaceClass: 02
    bConfigurationValue:       1
    bNumConfigurations:        1
    busnum:                    1
    devnum:                    7
    idProduct:                 099a
    idVendor:                  148e
    manufacturer:              Teltonika
    product:                   UM62XX
    serial:                    303137334444

Mode switching may have failed. Exiting

Code: Select all

Syslog:

Apr 18 14:41:42 redBox kernel: [  456.724935] usb 1-1.2: new high-speed USB device number 6 using dwc_otg
Apr 18 14:41:42 redBox kernel: [  456.826020] usb 1-1.2: New USB device found, idVendor=148e, idProduct=a000
Apr 18 14:41:42 redBox kernel: [  456.826055] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 18 14:41:42 redBox kernel: [  456.826070] usb 1-1.2: Product: UM62XX
Apr 18 14:41:42 redBox kernel: [  456.826084] usb 1-1.2: Manufacturer: Teltonika
Apr 18 14:41:42 redBox kernel: [  456.826097] usb 1-1.2: SerialNumber: 303137334444
Apr 18 14:41:42 redBox kernel: [  456.833425] usb-storage 1-1.2:1.0: USB Mass Storage device detected
Apr 18 14:41:42 redBox kernel: [  456.842280] scsi1 : usb-storage 1-1.2:1.0
Apr 18 14:41:42 redBox usb_modeswitch: switching device 148e:a000 on 001/006
Apr 18 14:41:43 redBox kernel: [  457.773272] usb 1-1.2: USB disconnect, device number 6
Apr 18 14:41:43 redBox kernel: [  458.014979] usb 1-1.2: new high-speed USB device number 7 using dwc_otg
Apr 18 14:41:43 redBox kernel: [  458.116141] usb 1-1.2: New USB device found, idVendor=148e, idProduct=099a
Apr 18 14:41:43 redBox kernel: [  458.116177] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 18 14:41:43 redBox kernel: [  458.116193] usb 1-1.2: Product: UM62XX
Apr 18 14:41:43 redBox kernel: [  458.116206] usb 1-1.2: Manufacturer: Teltonika
Apr 18 14:41:43 redBox kernel: [  458.116222] usb 1-1.2: SerialNumber: 303137334444
Apr 18 14:41:43 redBox kernel: [  458.119774] cdc_ether 1-1.2:1.0 eth1: register 'cdc_ether' at usb-bcm2708_usb-1.2, CDC Ethernet Device, 00:1e:42:02:6f:62
Apr 18 14:41:43 redBox ifplugd(eth1)[2565]: ifplugd 0.28 initializing.
Apr 18 14:41:43 redBox ifplugd(eth1)[2565]: Using interface eth1/00:1E:42:02:6F:62 with driver <cdc_ether> (version: 22-Aug-2005)
Apr 18 14:41:43 redBox ifplugd(eth1)[2565]: Using detection mode: SIOCETHTOOL
Apr 18 14:41:43 redBox ifplugd(eth1)[2565]: Initialization complete, link beat detected.
Apr 18 14:41:43 redBox ifplugd(eth1)[2565]: Executing '/etc/ifplugd/ifplugd.action eth1 up'.
Apr 18 14:41:43 redBox ifplugd(eth1)[2565]: client: Ignoring unknown interface eth1=eth1.
Apr 18 14:41:44 redBox ifplugd(eth1)[2565]: Program executed successfully.

LOM
Posts: 1404
Joined: 11 Jul 2012, 15:14
Location: Koh Samui, TH

Re: Teltonika WiMAX UM62XX USB dongle on Raspberry pi

Post by LOM » 19 Apr 2015, 04:13

I can't see any usb_modeswitch problem in your logs, the device gets switched from its initial usb id of 148e:a000 to the expected target id 148e:099a and your log even shows the ethernet driver binding after the successful switch.

usb_modeswitch is only responsible for switching the device, not for bringing up the connection.

Post Reply