UMTS Huawei E160


15 posts
by Dachshound » Wed Jan 30, 2013 4:50 pm
Hi guys,

I try to set up the raspi as a router. I would like to use my old Huawei E160, because i can use a external antenna. But i can't get it work.
I pluged the stick in and all i get ar these continously messanges.
Code: Select all
Jan 1 01:04:22 pi kernel:[262.961547] sub 1-1.2.1: new full-speed USB device number 26 using dwc_otg
Jan 1 01:06:06 pi kernel:[366.141432] sub 1-1.2.1: new full-speed USB device number 63 using dwc_otg
Jan 1 01:07:05 pi kernel:[425.541382] sub 1-1.2.1: new full-speed USB device number 51 using dwc_otg
Jan 1 01:08:04 pi kernel:[484.941454] sub 1-1.2.1: new full-speed USB device number 39 using dwc_otg
Jan 1 01:10:16 pi kernel:[616.031395] sub 1-1.2.1: new full-speed USB device number 63 using dwc_otg
Jan 1 01:11:15 pi kernel:[675.431457] sub 1-1.2.1: new full-speed USB device number 51 using dwc_otg

Further if is us lsusb i cant find the stick
Code: Select all
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. LAN9500 Ethernet 10/100 Adapter
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 004: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 005: ID 413c:2105 Dell Computer Corp. Model L100 Keyboard

and i don't get a new device at /dev after i pluged it in
Code: Select all
autofs         core             hidraw0  loop2         mapper     network_latency     ram1   ram2  ram9       spidev0.1  tty10  tty17  tty23  tty3   tty36  tty42  tty49  tty55  tty61    ttyprintk  vcs   vcsa   zero
block          cpu_dma_latency  initctl  loop3         mem        network_throughput  ram10  ram3  random     stderr     tty11  tty18  tty24  tty30  tty37  tty43  tty5   tty56  tty62    uhid       vcs1  vcsa1  zram0
btrfs-control  disk             input    loop4         mmcblk0    null                ram11  ram4  raw        stdin      tty12  tty19  tty25  tty31  tty38  tty44  tty50  tty57  tty63    uinput     vcs2  vcsa2
bus            fb0              kmsg     loop5         mmcblk0p1  ppp                 ram12  ram5  rfkill     stdout     tty13  tty2   tty26  tty32  tty39  tty45  tty51  tty58  tty7     urandom    vcs3  vcsa3
cachefiles     fd               log      loop6         mmcblk0p2  ptmx                ram13  ram6  shm        tty        tty14  tty20  tty27  tty33  tty4   tty46  tty52  tty59  tty8     vc-cma     vcs4  vcsa4
char           full             loop0    loop7         mqueue     pts                 ram14  ram7  snd        tty0       tty15  tty21  tty28  tty34  tty40  tty47  tty53  tty6   tty9     vchiq      vcs5  vcsa5
console        fuse             loop1    loop-control  net        ram0                ram15  ram8  spidev0.0  tty1       tty16  tty22  tty29  tty35  tty41  tty48  tty54  tty60  ttyAMA0  vc-mem     vcs6  vcsa6
I thought ttyAMA0 might be the stick, but it still exist with or without the modem.

I use
Code: Select all
Linux pi 3.6.11-4-ARCH+ #1 PREEMPT Wed Jan 16 19:06:54 UTC 2013 armv6l GNU/Linux

If some one has an idea, it would be great!

Thnaks a lot.
Posts: 5
Joined: Wed Jan 30, 2013 4:32 pm
by Cloudcentric » Wed Jan 30, 2013 5:51 pm
Maybe use Sakis3g software forE160 USB 3G Dongle, the software seems to work out-of-the-box with most 3G dongles.


I have used on Arch Linux Arm and Raspbian Distros, the Sakis3g web site is down and out but if you read this blog there is an alternative download link and instructions about half way down page.
I know everything about nothing"
Posts: 982
Joined: Fri Sep 14, 2012 9:13 am
by redhawk » Wed Jan 30, 2013 6:12 pm
I have a Huawei E160 dongle too and it doesn't work with Raspbian.
I can communicate with it using a terminal emulator but any attempt to use dial-up just hangs:

viewtopic.php?f=66&t=13936&p=144902

This was a long time ago and perhaps firmware updates have fixed this problem but if it doesn't work it doesn't work.

Richard S.
User avatar
Posts: 3519
Joined: Sun Mar 04, 2012 2:13 pm
Location: ::1
by pepedog » Wed Jan 30, 2013 6:46 pm
Original poster, is this via a powered hub, or directly into rpi?
Posts: 982
Joined: Fri Oct 07, 2011 9:55 am
by sdjf » Wed Jan 30, 2013 6:53 pm
I see two issues that need taking care of to get dialup working with your device:

1. the device needs to be recognized and bound to a driver on the pi. What drivers work with it? Are they on the Pi?

2. getting dialup working, once your dongle is recognized. That is the easy part, when you know how. and there are lots of choices about how to get ppp0 started. I am using the ppp package, but there also is wvdial you could also try.

But number 1 seems to be the most important. until you can get it to show as bound to a driver, you are stuck. Maybe someone else can address that issue now, I know there are devices listed in a file somewhere, but cannot look for that now, will do so later if nobody else comes along with a more complete answer to the module/driver issue. IF lsusb is not finding the device, bet your power supply is not good enough, test rating at TP1-TP2. We need the product number and manufacturer number to identify the device in the modules.alias file, if it is there, and it should be.

Now I see pepedog's reply, I think he hit the nail on the head.
FORUM TIP: To view just one person's posting history, sign in, click on their user name, then click on "Search User's Posts." || This Pi owner is running Arch on 512MB Model B.
Posts: 1298
Joined: Fri Mar 16, 2012 5:20 am
Location: California
by Dachshound » Thu Jan 31, 2013 9:10 am
I use a powerd USB-HUB (ATEN UH-275). It suport up to 500mA per port. The raspi works fine. I know that he needs up to 700mA. I will look for a new one.
But it tryed the USB-Hub inside the Dell U2412M and hafe the same problems.

@ Cloudcentric
I will try this and responed if it works later.

@ sdjf
I assumed, that are the driver.
Posts: 5
Joined: Wed Jan 30, 2013 4:32 pm
by Spid » Thu Jan 31, 2013 9:14 am
I will always assume you are running Raspbian for desktop and Raspbmc for XMBC !
Posts: 525
Joined: Sat Jan 19, 2013 12:47 pm
by pepedog » Thu Jan 31, 2013 9:42 am
If you try this
http://blog.pew.cc/blog/Getting+the+Hua ... +to+work+/
usb_modeswitch can be installed with pacman -Sy usb_modeswitch
Posts: 982
Joined: Fri Oct 07, 2011 9:55 am
by sdjf » Thu Jan 31, 2013 3:35 pm
Dachshound: You cannot assume anything. If things do not work, you need to verify your assumptions.

If the usb_modeswitch pepedog recommended does not solve your problem, I still think you need to:

1. test power at TP1-TP2 because power supplies do not always deliver the power that they say they deliver

2. find out what driver works with your dongle, and make sure you have that driver on the Pi, and that your device is listed in modules.aliases. Since your device does not show up in lsusb, you can find the product ID by googling for the number.

3. after you get it attached to the right driver, then you can work with ppp, wvdial is probably the easiest way to configure your pppd connection.
FORUM TIP: To view just one person's posting history, sign in, click on their user name, then click on "Search User's Posts." || This Pi owner is running Arch on 512MB Model B.
Posts: 1298
Joined: Fri Mar 16, 2012 5:20 am
Location: California
by kghunt » Thu Jan 31, 2013 8:36 pm
I use an e156 no probs using wvdial to connect to Internet.
Posts: 360
Joined: Sun Mar 04, 2012 9:28 am
by Dachshound » Mon Feb 04, 2013 1:14 pm
I did some voltage measurements today. I used
Code: Select all
openssl speed
to stress the core.
Voltage drop wit the Dell U2412M as a hub.
4.67V idle and 4.61V on load

Voltage drop wit the ATEN UH-275 as a hub.
4.68V idle and 4.63V on load

Voltage drop wit the Belkin F5U237 Rev3 as a hub.
5.4V idle and 5.3V on load
And a grafik of this votage across TP1 and TP2.
Image

But wirh all of them the pi worked with out problems that i noticed.

I use the Huawei 160. I created the usb_
Code: Select all
DefaultVendor=  0x12d1
DefaultProduct= 0x1003

TargetClass= 0xff

HuaweiMode=1
Posts: 5
Joined: Wed Jan 30, 2013 4:32 pm
by Dachshound » Mon Feb 04, 2013 1:57 pm
After several modification it work now. I don't know why excactly.
I measuerd the voltage at the Hub-Port -> at the end of the micro-USB (ok, i did a short ciruit vor a part of a second between V++ and Ground (because it is so damm tiny) -> and thean at the TP1 and TP2 again.....
Voltage TP1 and TP2 DC
Image
Voltage TP1 and TP2 AC
Image
Posts: 5
Joined: Wed Jan 30, 2013 4:32 pm
by pepedog » Mon Feb 04, 2013 2:05 pm
I use the Huawei 160. I created the usb_

So you used usb_modeswitch to get this working?
Posts: 982
Joined: Fri Oct 07, 2011 9:55 am
by Dachshound » Mon Feb 04, 2013 3:42 pm
I think I did a mistake in the usb_modeswitch.conf. I had behind the DefaultVendor a semicolon. But it still cause a lot of trouble. I get with wvdial or sakis3g for few seconds a connection.

Code: Select all
...
Jan  1 01:00:07 WildnisCAM kernel: [    2.761759] usb 1-1.2.6: new full-speed USB device number 5 using dwc_otg
Jan  1 01:00:07 WildnisCAM kernel: [    2.921768] usb 1-1.2.6: new high-speed USB device number 6 using dwc_otg
Jan  1 01:00:07 WildnisCAM kernel: [    3.032924] usb 1-1.2.6: New USB device found, idVendor=12d1, idProduct=1003
Jan  1 01:00:07 WildnisCAM kernel: [    3.032959] usb 1-1.2.6: New USB device strings: Mfr=3, Product=2, SerialNumber=0
Jan  1 01:00:07 WildnisCAM kernel: [    3.032992] usb 1-1.2.6: Manufacturer: HUAWEI Technology
Jan  1 01:00:07 WildnisCAM kernel: [    3.061623] scsi2 : usb-storage 1-1.2.6:1.2
Jan  1 01:00:07 WildnisCAM kernel: [    3.071954] scsi3 : usb-storage 1-1.2.6:1.3
Jan  1 01:00:07 WildnisCAM kernel: [    4.065223] scsi 2:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 2
Jan  1 01:00:07 WildnisCAM kernel: [    4.075432] scsi 3:0:0:0: Direct-Access     HUAWEI   MMC Storage      2.31 PQ: 0 ANSI: 2
Jan  1 01:00:07 WildnisCAM kernel: [    4.086270] sd 3:0:0:0: [sda] Attached SCSI removable disk
Jan  1 01:00:07 WildnisCAM kernel: [    4.606379] usbcore: registered new interface driver usbserial
Jan  1 01:00:07 WildnisCAM kernel: [    4.606502] usbcore: registered new interface driver usbserial_generic
Jan  1 01:00:07 WildnisCAM kernel: [    4.606605] USB Serial support registered for generic
Jan  1 01:00:07 WildnisCAM kernel: [    4.606633] usbserial: USB Serial Driver core
Jan  1 01:00:07 WildnisCAM kernel: [    4.751103] usbcore: registered new interface driver option
Jan  1 01:00:07 WildnisCAM kernel: [    4.751236] USB Serial support registered for GSM modem (1-port)
Jan  1 01:00:07 WildnisCAM [    4.907306] systemd-journald[56]: Received SIGUSR1
Jan  1 01:00:07 WildnisCAM kernel: [    4.930220] option 1-1.2.6:1.0: GSM modem (1-port) converter detected
Jan  1 01:00:07 WildnisCAM kernel: [    4.955387] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB0
Jan  1 01:00:07 WildnisCAM kernel: [    4.959569] option 1-1.2.6:1.1: GSM modem (1-port) converter detected
Jan  1 01:00:07 WildnisCAM kernel: [    4.960128] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB1
Jan  1 01:00:07 WildnisCAM kernel: [    5.905882] NET: Registered protocol family 10
Jan  1 01:00:07 WildnisCAM kernel: [    7.422589] sr0: scsi-1 drive
Jan  1 01:00:07 WildnisCAM kernel: [    7.422623] cdrom: Uniform CD-ROM driver Revision: 3.20
Jan  1 01:00:07 WildnisCAM kernel: [    7.423695] sr 2:0:0:0: Attached scsi CD-ROM sr0
Jan  1 01:00:15 WildnisCAM kernel: [   15.061621] option1 ttyUSB0: option_instat_callback: error -108
Jan  1 01:00:15 WildnisCAM kernel: [   15.062083] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Jan  1 01:00:15 WildnisCAM kernel: [   15.062209] option 1-1.2.6:1.0: device disconnected
Jan  1 01:00:15 WildnisCAM kernel: [   15.062586] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Jan  1 01:00:15 WildnisCAM kernel: [   15.062675] option 1-1.2.6:1.1: device disconnected
Jan  1 01:00:15 WildnisCAM kernel: [   15.141714] usb 1-1.2.6: reset high-speed USB device number 6 using dwc_otg
Jan  1 01:00:15 WildnisCAM kernel: [   15.247917] option 1-1.2.6:1.1: GSM modem (1-port) converter detected
Jan  1 01:00:15 WildnisCAM kernel: [   15.251823] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB0
Jan  1 01:00:15 WildnisCAM kernel: [   15.257174] option 1-1.2.6:1.0: GSM modem (1-port) converter detected
Jan  1 01:00:15 WildnisCAM kernel: [   15.257750] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB1


Code: Select all
Feb  4 16:24:48 WildnisCAM systemd[1]: Startup finished in 1s 813ms 320us (kernel) + 16s 162ms 246us (userspace) = 17s 975ms 566us.
Feb  4 16:24:48 WildnisCAM ntpd[190]: set local clock to Mon Feb  4 16:24:48 CET 2013 (offset 1359991470.993542s)
Feb  4 16:25:01 WildnisCAM kernel: [   30.245623] option1 ttyUSB1: option_instat_callback: error -108
Feb  4 16:25:01 WildnisCAM kernel: [   30.246103] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Feb  4 16:25:01 WildnisCAM kernel: [   30.246231] option 1-1.2.6:1.0: device disconnected
Feb  4 16:25:01 WildnisCAM kernel: [   30.246611] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Feb  4 16:25:01 WildnisCAM kernel: [   30.246699] option 1-1.2.6:1.1: device disconnected
Feb  4 16:25:01 WildnisCAM kernel: [   30.282967] usb 1-1.2.6: USB disconnect, device number 6
Feb  4 16:25:01 WildnisCAM kernel: [   30.541737] usb 1-1.2.6: new high-speed USB device number 8 using dwc_otg
Feb  4 16:25:01 WildnisCAM kernel: [   30.652967] usb 1-1.2.6: New USB device found, idVendor=12d1, idProduct=1003
Feb  4 16:25:01 WildnisCAM kernel: [   30.653003] usb 1-1.2.6: New USB device strings: Mfr=3, Product=2, SerialNumber=0
Feb  4 16:25:01 WildnisCAM kernel: [   30.653021] usb 1-1.2.6: Product: HUAWEI Mobile
Feb  4 16:25:01 WildnisCAM kernel: [   30.653036] usb 1-1.2.6: Manufacturer: HUAWEI Technology
Feb  4 16:25:01 WildnisCAM kernel: [   30.664352] option 1-1.2.6:1.0: GSM modem (1-port) converter detected
Feb  4 16:25:01 WildnisCAM kernel: [   30.665084] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB0
Feb  4 16:25:01 WildnisCAM kernel: [   30.666242] option 1-1.2.6:1.1: GSM modem (1-port) converter detected
Feb  4 16:25:01 WildnisCAM kernel: [   30.666868] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB1
Feb  4 16:25:01 WildnisCAM kernel: [   30.674238] scsi8 : usb-storage 1-1.2.6:1.2
Feb  4 16:25:01 WildnisCAM kernel: [   30.681599] scsi9 : usb-storage 1-1.2.6:1.3
Feb  4 16:25:02 WildnisCAM kernel: [   31.675185] scsi 8:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 2
Feb  4 16:25:02 WildnisCAM kernel: [   31.686353] scsi 9:0:0:0: Direct-Access     HUAWEI   MMC Storage      2.31 PQ: 0 ANSI: 2
Feb  4 16:25:02 WildnisCAM kernel: [   31.692236] sr0: scsi-1 drive
Feb  4 16:25:02 WildnisCAM kernel: [   31.693595] sr 8:0:0:0: Attached scsi CD-ROM sr0
Feb  4 16:25:02 WildnisCAM kernel: [   31.698569] sd 9:0:0:0: [sda] Attached SCSI removable disk


Code: Select all
Feb  4 16:33:39 WildnisCAM kernel: [  548.982153] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB0
Feb  4 16:33:39 WildnisCAM kernel: [  548.988628] option 1-1.2.6:1.0: GSM modem (1-port) converter detected
Feb  4 16:33:39 WildnisCAM kernel: [  548.989393] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB1
Feb  4 16:34:07 WildnisCAM kernel: [  576.152032] option1 ttyUSB1: option_instat_callback: error -108
Feb  4 16:34:07 WildnisCAM kernel: [  576.152504] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Feb  4 16:34:07 WildnisCAM kernel: [  576.152603] option 1-1.2.6:1.0: device disconnected
Feb  4 16:34:07 WildnisCAM kernel: [  576.155439] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Feb  4 16:34:07 WildnisCAM kernel: [  576.155545] option 1-1.2.6:1.1: device disconnected
Feb  4 16:34:07 WildnisCAM kernel: [  576.232181] usb 1-1.2.6: reset high-speed USB device number 14 using dwc_otg
Feb  4 16:34:07 WildnisCAM kernel: [  576.337741] option 1-1.2.6:1.1: GSM modem (1-port) converter detected
Feb  4 16:34:07 WildnisCAM kernel: [  576.342193] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB0
Feb  4 16:34:07 WildnisCAM kernel: [  576.344793] option 1-1.2.6:1.0: GSM modem (1-port) converter detected
Feb  4 16:34:07 WildnisCAM kernel: [  576.345478] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB1
Feb  4 16:34:25 WildnisCAM kernel: [  594.156223] option1 ttyUSB1: option_instat_callback: error -108
Feb  4 16:34:25 WildnisCAM kernel: [  594.157535] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Feb  4 16:34:25 WildnisCAM kernel: [  594.157660] option 1-1.2.6:1.0: device disconnected
Feb  4 16:34:25 WildnisCAM kernel: [  594.162145] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Feb  4 16:34:25 WildnisCAM kernel: [  594.162253] option 1-1.2.6:1.1: device disconnected
Feb  4 16:34:25 WildnisCAM kernel: [  594.242139] usb 1-1.2.6: reset high-speed USB device number 14 using dwc_otg
Feb  4 16:34:25 WildnisCAM kernel: [  594.347988] option 1-1.2.6:1.1: GSM modem (1-port) converter detected
Feb  4 16:34:25 WildnisCAM kernel: [  594.352129] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB0
Feb  4 16:34:25 WildnisCAM kernel: [  594.354571] option 1-1.2.6:1.0: GSM modem (1-port) converter detected
Feb  4 16:34:25 WildnisCAM kernel: [  594.355320] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB1
Feb  4 16:34:27 WildnisCAM kernel: [  596.392620] option1 ttyUSB1: option_instat_callback: error -108
Feb  4 16:34:27 WildnisCAM kernel: [  596.393075] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Feb  4 16:34:27 WildnisCAM kernel: [  596.393223] option 1-1.2.6:1.0: device disconnected
Feb  4 16:34:27 WildnisCAM kernel: [  596.393624] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Feb  4 16:34:27 WildnisCAM kernel: [  596.393712] option 1-1.2.6:1.1: device disconnected
Feb  4 16:34:58 WildnisCAM kernel: [  627.192108] usb 1-1.2.6: reset high-speed USB device number 14 using dwc_otg
Feb  4 16:34:58 WildnisCAM kernel: [  627.298024] option 1-1.2.6:1.1: GSM modem (1-port) converter detected
Feb  4 16:34:58 WildnisCAM kernel: [  627.300473] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB0
Feb  4 16:34:58 WildnisCAM kernel: [  627.307977] option 1-1.2.6:1.0: GSM modem (1-port) converter detected
Feb  4 16:34:58 WildnisCAM kernel: [  627.308641] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB1
Feb  4 16:34:58 WildnisCAM kernel: [  627.322032] option1 ttyUSB1: option_instat_callback: error -108Feb  4 16:34:58 WildnisCAM kernel: [  627.322626] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Feb  4 16:34:58 WildnisCAM kernel: [  627.322626] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Feb  4 16:34:58 WildnisCAM kernel: [  627.322725] option 1-1.2.6:1.0: device disconnected
Feb  4 16:34:58 WildnisCAM kernel: [  627.323289] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Feb  4 16:34:58 WildnisCAM kernel: [  627.323437] option 1-1.2.6:1.1: device disconnected
Feb  4 16:34:58 WildnisCAM kernel: [  627.402297] usb 1-1.2.6: reset high-speed USB device number 14 using dwc_otg
Feb  4 16:34:58 WildnisCAM kernel: [  627.507882] option 1-1.2.6:1.1: GSM modem (1-port) converter detected
Feb  4 16:34:58 WildnisCAM kernel: [  627.508865] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB0
Feb  4 16:34:58 WildnisCAM kernel: [  627.509993] option 1-1.2.6:1.0: GSM modem (1-port) converter detected
Feb  4 16:34:58 WildnisCAM kernel: [  627.511050] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB1
Feb  4 16:35:03 WildnisCAM kernel: [  633.062265] option1 ttyUSB1: option_instat_callback: error -71
Feb  4 16:35:07 WildnisCAM kernel: [  636.294702] option1 ttyUSB1: option_instat_callback: error -71
Feb  4 16:35:08 WildnisCAM kernel: [  637.222831] option1 ttyUSB1: option_instat_callback: error -71
Feb  4 16:35:08 WildnisCAM kernel: [  637.464861] option1 ttyUSB1: option_instat_callback: error -71
Feb  4 16:35:09 WildnisCAM kernel: [  638.635168] option1 ttyUSB1: option_instat_callback: error -108
Feb  4 16:35:09 WildnisCAM kernel: [  638.635878] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Feb  4 16:35:09 WildnisCAM kernel: [  638.636017] option 1-1.2.6:1.0: device disconnected
Feb  4 16:35:09 WildnisCAM kernel: [  638.636480] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Feb  4 16:35:09 WildnisCAM kernel: [  638.636590] option 1-1.2.6:1.1: device disconnected
Feb  4 16:35:09 WildnisCAM kernel: [  638.673246] usb 1-1.2.6: USB disconnect, device number 14
Feb  4 16:35:09 WildnisCAM kernel: [  638.942028] usb 1-1.2.6: new high-speed USB device number 15 using dwc_otg
Feb  4 16:35:14 WildnisCAM kernel: [  644.047256] usb 1-1.2.6: New USB device found, idVendor=12d1, idProduct=1003
Feb  4 16:35:14 WildnisCAM kernel: [  644.047291] usb 1-1.2.6: New USB device strings: Mfr=3, Product=2, SerialNumber=0
Feb  4 16:35:14 WildnisCAM kernel: [  644.047309] usb 1-1.2.6: Product: HUAWEI Mobile
Feb  4 16:35:14 WildnisCAM kernel: [  644.047325] usb 1-1.2.6: Manufacturer: HUAWEI Technology
Feb  4 16:35:15 WildnisCAM kernel: [  644.056789] option 1-1.2.6:1.0: GSM modem (1-port) converter detected
Feb  4 16:35:15 WildnisCAM kernel: [  644.057567] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB0
Feb  4 16:35:15 WildnisCAM kernel: [  644.064804] option 1-1.2.6:1.1: GSM modem (1-port) converter detected
Feb  4 16:35:15 WildnisCAM kernel: [  644.065429] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB1
Feb  4 16:35:15 WildnisCAM kernel: [  644.074667] scsi48 : usb-storage 1-1.2.6:1.2
Feb  4 16:35:15 WildnisCAM kernel: [  644.086109] scsi49 : usb-storage 1-1.2.6:1.3
Feb  4 16:35:16 WildnisCAM kernel: [  645.075491] scsi 48:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 2
Feb  4 16:35:16 WildnisCAM kernel: [  645.087189] scsi 49:0:0:0: Direct-Access     HUAWEI   MMC Storage      2.31 PQ: 0 ANSI: 2
Feb  4 16:35:16 WildnisCAM kernel: [  645.089547] sr0: scsi-1 drive
Feb  4 16:35:16 WildnisCAM kernel: [  645.090488] sr 48:0:0:0: Attached scsi CD-ROM sr0
Feb  4 16:35:16 WildnisCAM kernel: [  645.097469] sd 49:0:0:0: [sda] Attached SCSI removable disk
Feb  4 16:35:43 WildnisCAM kernel: [  672.235714] option1 ttyUSB0: option_instat_callback: error -108
Feb  4 16:35:43 WildnisCAM kernel: [  672.242001] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Feb  4 16:35:43 WildnisCAM kernel: [  672.242151] option 1-1.2.6:1.0: device disconnected
Feb  4 16:35:43 WildnisCAM kernel: [  672.242619] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Feb  4 16:35:43 WildnisCAM kernel: [  672.242708] option 1-1.2.6:1.1: device disconnected
Feb  4 16:35:43 WildnisCAM kernel: [  672.322131] usb 1-1.2.6: reset high-speed USB device number 15 using dwc_otg
Feb  4 16:35:43 WildnisCAM kernel: [  672.427914] option 1-1.2.6:1.1: GSM modem (1-port) converter detected
Feb  4 16:35:43 WildnisCAM kernel: [  672.432197] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB0
Feb  4 16:35:43 WildnisCAM kernel: [  672.438704] option 1-1.2.6:1.0: GSM modem (1-port) converter detected
Feb  4 16:35:43 WildnisCAM kernel: [  672.439419] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB1
Feb  4 16:35:58 WildnisCAM kernel: [  687.914928] option1 ttyUSB1: option_instat_callback: error -108
Feb  4 16:35:58 WildnisCAM kernel: [  687.916347] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Feb  4 16:35:58 WildnisCAM kernel: [  687.916475] option 1-1.2.6:1.0: device disconnected
Feb  4 16:35:58 WildnisCAM kernel: [  687.919349] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Feb  4 16:35:58 WildnisCAM kernel: [  687.919456] option 1-1.2.6:1.1: device disconnected
Feb  4 16:36:29 WildnisCAM kernel: [  718.152083] usb 1-1.2.6: reset high-speed USB device number 15 using dwc_otg
Feb  4 16:36:29 WildnisCAM kernel: [  718.258870] option 1-1.2.6:1.1: GSM modem (1-port) converter detected
Feb  4 16:36:29 WildnisCAM kernel: [  718.261184] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB0
Feb  4 16:36:29 WildnisCAM kernel: [  718.268488] option 1-1.2.6:1.0: GSM modem (1-port) converter detected
Feb  4 16:36:29 WildnisCAM kernel: [  718.269216] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB1
Feb  4 16:36:29 WildnisCAM kernel: [  718.282019] option1 ttyUSB1: option_instat_callback: error -108
Feb  4 16:36:29 WildnisCAM kernel: [  718.282847] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Feb  4 16:36:29 WildnisCAM kernel: [  718.283005] option 1-1.2.6:1.0: device disconnected
Feb  4 16:36:29 WildnisCAM kernel: [  718.283508] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Feb  4 16:36:29 WildnisCAM kernel: [  718.283604] option 1-1.2.6:1.1: device disconnected
Feb  4 16:36:29 WildnisCAM kernel: [  718.382282] usb 1-1.2.6: reset high-speed USB device number 15 using dwc_otg
Feb  4 16:36:29 WildnisCAM kernel: [  718.487894] option 1-1.2.6:1.1: GSM modem (1-port) converter detected
Feb  4 16:36:29 WildnisCAM kernel: [  718.488915] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB0
Feb  4 16:36:29 WildnisCAM kernel: [  718.490078] option 1-1.2.6:1.0: GSM modem (1-port) converter detected
Feb  4 16:36:29 WildnisCAM kernel: [  718.491281] usb 1-1.2.6: GSM modem (1-port) converter now attached to ttyUSB1
Posts: 5
Joined: Wed Jan 30, 2013 4:32 pm
by steve_gulick » Mon Feb 04, 2013 4:37 pm
with the Huawei E160 (and some other models) you can issue AT commands that will disable the CD-drive function of the stick - then you don't need to use modeswitch (also it is faster on booting) (I hate that "feature"!!)

issue the AT command....

AT^U2DIAG=0

This is persistent through re-booting. If you ever need to re-enable the CD-rom function (to use in a windows machine, it can be re-ennabled via AT^U2DIAG=1)

After booting there will be created a ttyUSB0, ttyUSB1, and ttyUSB2 device node. You want to use the /dev/ttyUSB0 device

I use pppd ...
$ pppd call att /dev/ttyUSB0 115200 &

works fine.

I can boot with the stick plugged directly into the RasPi if it is plugged in before power is applied. But don't try plugging it into a booted system or it will reboot. (using a 5.2v solid power supply)

Steve
Posts: 26
Joined: Wed Jul 18, 2012 12:06 pm