ubuntuusers.de

Funktionert das ZTE MF180 USB-UMTS Modem (Bob Austria)?

Status: Gelöst | Ubuntu-Version: Ubuntu 10.10 (Maverick Meerkat)
Antworten |

principito

Anmeldungsdatum:
12. Dezember 2008

Beiträge: Zähle...

Hallo!

Hat das jemand den ZTE MF180 unter 10.10 zum Laufen bekommen?

uname:

Linux bunny 2.6.35-22-generic #35-Ubuntu SMP Sat Oct 16 20:45:36 UTC 2010 x86_64 GNU/Linux

lsusb:

root@bunny:~# lsusb
...
Bus 002 Device 003: ID 19d2:0117 ONDA Communication S.p.A. 
...

Habe in /etc/usb_modeswitch.d/19d2:2000 die usb-id 117 hinzugefügt. Weiß aber nicht wirklich ob das das richtige ist/war, was ich tue. Modeswitch scheint dann aber zu funktionieren. s.u.

TargetProductList="0001,0002,0015,0016,0017,0031,0037,0052,0055,0063,0064,0108,0117,0128"

Nach dem Einstecken passiert folgendes:

dmesg:

[  171.600054] usb 2-3: new high speed USB device using ehci_hcd and address 2
[  171.757778] scsi9 : usb-storage 2-3:1.0
[  173.839398] usb 2-3: USB disconnect, address 2
[  174.231325] usb 2-3: new high speed USB device using ehci_hcd and address 3
[  174.393758] scsi10 : usb-storage 2-3:1.3
[  174.446206] usbcore: registered new interface driver usbserial
[  174.446221] USB Serial support registered for generic
[  174.446252] usbcore: registered new interface driver usbserial_generic
[  174.446254] usbserial: USB Serial Driver core
[  174.459516] USB Serial support registered for GSM modem (1-port)
[  174.459591] option 2-3:1.0: GSM modem (1-port) converter detected
[  174.459710] usb 2-3: GSM modem (1-port) converter now attached to ttyUSB0
[  174.459724] option 2-3:1.1: GSM modem (1-port) converter detected
[  174.459782] usb 2-3: GSM modem (1-port) converter now attached to ttyUSB1
[  174.459793] option 2-3:1.2: GSM modem (1-port) converter detected
[  174.459861] usb 2-3: GSM modem (1-port) converter now attached to ttyUSB2
[  174.459915] usbcore: registered new interface driver option
[  174.459917] option: v0.7.2:USB Driver for GSM modems
[  175.396124] scsi 10:0:0:0: CD-ROM            ZTE      USB SCSI CD-ROM  2.31 PQ: 0 ANSI: 2
[  175.428085] sr1: scsi-1 drive
[  175.428321] sr 10:0:0:0: Attached scsi CD-ROM sr1
[  175.428469] sr 10:0:0:0: Attached scsi generic sg3 type 5

/var/log/messages:

rainer@bunny:~$ sudo -s
[sudo] password for rainer: 
root@bunny:~# tail -f /var/log/messages
Nov 15 12:27:04 bunny kernel: [  171.600054] usb 2-3: new high speed USB device using ehci_hcd and address 2
Nov 15 12:27:05 bunny kernel: [  171.757778] scsi9 : usb-storage 2-3:1.0
Nov 15 12:27:05 bunny usb_modeswitch: switching 19d2:2000 (ZTE,Incorporated: ZTE WCDMA Technologies MSM)
Nov 15 12:27:07 bunny kernel: [  173.839398] usb 2-3: USB disconnect, address 2
Nov 15 12:27:07 bunny kernel: [  174.231325] usb 2-3: new high speed USB device using ehci_hcd and address 3
Nov 15 12:27:07 bunny kernel: [  174.393758] scsi10 : usb-storage 2-3:1.3
Nov 15 12:27:07 bunny kernel: [  174.446206] usbcore: registered new interface driver usbserial
Nov 15 12:27:07 bunny kernel: [  174.446221] USB Serial support registered for generic
Nov 15 12:27:07 bunny kernel: [  174.446252] usbcore: registered new interface driver usbserial_generic
Nov 15 12:27:07 bunny kernel: [  174.446254] usbserial: USB Serial Driver core
Nov 15 12:27:07 bunny kernel: [  174.459516] USB Serial support registered for GSM modem (1-port)
Nov 15 12:27:07 bunny kernel: [  174.459591] option 2-3:1.0: GSM modem (1-port) converter detected
Nov 15 12:27:07 bunny kernel: [  174.459710] usb 2-3: GSM modem (1-port) converter now attached to ttyUSB0
Nov 15 12:27:07 bunny kernel: [  174.459724] option 2-3:1.1: GSM modem (1-port) converter detected
Nov 15 12:27:07 bunny kernel: [  174.459782] usb 2-3: GSM modem (1-port) converter now attached to ttyUSB1
Nov 15 12:27:07 bunny kernel: [  174.459793] option 2-3:1.2: GSM modem (1-port) converter detected
Nov 15 12:27:07 bunny kernel: [  174.459861] usb 2-3: GSM modem (1-port) converter now attached to ttyUSB2
Nov 15 12:27:07 bunny kernel: [  174.459915] usbcore: registered new interface driver option
Nov 15 12:27:07 bunny kernel: [  174.459917] option: v0.7.2:USB Driver for GSM modems
Nov 15 12:27:08 bunny kernel: [  175.396124] scsi 10:0:0:0: CD-ROM            ZTE      USB SCSI CD-ROM  2.31 PQ: 0 ANSI: 2
Nov 15 12:27:08 bunny usb_modeswitch: switched to 19d2:0117 (ZTE,Incorporated: ZTE WCDMA Technologies MSM)
Nov 15 12:27:08 bunny kernel: [  175.428085] sr1: scsi-1 drive

Debug Output von Modeswitch:

root@bunny:/var/log# cat /var/log/usb_modeswitch_2-3\:1.0 


USB_ModeSwitch log from Mon Nov 15 12:27:05 CET 2010

Using global config file: /etc/usb_modeswitch.conf
raw args from udev: /2-3:1.0
Bus ID for device not given by udev.
 Trying to determine it from kernel name (2-3:1.0) ...
USB dir exists: /sys/bus/usb/devices/2-3
----------------
USB values from sysfs:
  manufacturer	ZTE,Incorporated
  product	ZTE WCDMA Technologies MSM
  serial	MF1800ZTED010000
----------------
SCSI attributes not needed, moving on
checking config: /etc/usb_modeswitch.d/19d2:2000
! matched, now switching
 (running command: /usr/sbin/usb_modeswitch -I -W -c /etc/usb_modeswitch.d/19d2:2000)

verbose output of usb_modeswitch:
--------------------------------
usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 007
usb_os_find_busses: Found 006
usb_os_find_busses: Found 005
usb_os_find_busses: Found 004
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 001 on 007
usb_os_find_devices: Found 001 on 006
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 005 on 004
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 004 on 004
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 003 on 004
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 004
usb_os_find_devices: Found 001 on 004
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 003 on 003
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 003
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 002 on 002
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 004 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
Reading config file: /etc/usb_modeswitch.d/19d2:2000
Warning: TargetProductList overrides TargetProduct!
 * usb_modeswitch: handle USB devices with multiple modes
 * Version 1.1.4 (C) Josua Dietze 2010
 * Based on libusb0 (0.1.12 and above)

 ! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor=  0x19d2
DefaultProduct= 0x2000
TargetVendor=   0x19d2
TargetProduct=  not set
TargetClass=    not set
TargetProductList="0001,0002,0015,0016,0017,0031,0037,0052,0055,0063,0064,0108,0117,0128"

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
GCTMode=0
MessageEndpoint=  not set
MessageContent="5553424312345678000000000000061e000000000000000000000000000000"
MessageContent2="5553424312345679000000000000061b000000020000000000000000000000"
MessageContent3="55534243123456702000000080000c85010101180101010101000000000000"
NeedResponse=1
ResponseEndpoint= not set
Interface=0x00

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


Looking for target devices ...
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 050d:016a
  searching devices, found USB ID 0a5c:4503
  searching devices, found USB ID 0a5c:4502
  searching devices, found USB ID 0a5c:4500
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 046d:c043
  searching devices, found USB ID 046d:c318
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 19d2:2000
   found matching vendor ID
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 05e3:0723
  searching devices, found USB ID 05e3:0608
  searching devices, found USB ID 1d6b:0002
 No devices in target mode or class found
Looking for default devices ...
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 050d:016a
  searching devices, found USB ID 0a5c:4503
  searching devices, found USB ID 0a5c:4502
  searching devices, found USB ID 0a5c:4500
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 046d:c043
  searching devices, found USB ID 046d:c318
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 19d2:2000
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 05e3:0723
  searching devices, found USB ID 05e3:0608
  searching devices, found USB ID 1d6b:0002
 Found devices in default mode or class (1)
Accessing device 002 on bus 002 ...
Using endpoints 0x01 (out) and 0x81 (in)
Using endpoints 0x01 (out) and 0x81 (in)

USB description data (for identification)
-------------------------
Manufacturer: ZTE,Incorporated
     Product: ZTE WCDMA Technologies MSM
  Serial No.: MF1800ZTED010000
-------------------------
Looking for active driver ...
 OK, driver found ("usb-storage")
 OK, driver "usb-storage" detached
Setting up communication with interface 0 ...
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to the message (CSW) ...
 OK, response successfully read (13 bytes).
Trying to send message 2 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to message 2 ...
 OK, response successfully read (13 bytes).
Trying to send message 3 to endpoint 0x01 ...
USB error: could not claim interface 0: No such device
usb_os_find_devices: Found 001 on 007
usb_os_find_devices: Found 001 on 006
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 005 on 004
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 004 on 004
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 003 on 004
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 004
usb_os_find_devices: Found 001 on 004
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 003 on 003
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 003
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 004 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 007
usb_os_find_devices: Found 001 on 006
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 005 on 004
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 004 on 004
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 003 on 004
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 004
usb_os_find_devices: Found 001 on 004
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 003 on 003
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 003
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 003 on 002
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 004 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
 OK, message successfully sent
Reading the response to message 3 ...
 OK, response successfully read (0 bytes).
Resetting response endpoint 0x81
Resetting message endpoint 0x01

Checking for mode switch (max. 20 times, once per second) ...
 Waiting for original device to vanish ...
 Original device can't be accessed anymore. Good.
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 050d:016a
  searching devices, found USB ID 0a5c:4503
  searching devices, found USB ID 0a5c:4502
  searching devices, found USB ID 0a5c:4500
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 046d:c043
  searching devices, found USB ID 046d:c318
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 05e3:0723
  searching devices, found USB ID 05e3:0608
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 050d:016a
  searching devices, found USB ID 0a5c:4503
  searching devices, found USB ID 0a5c:4502
  searching devices, found USB ID 0a5c:4500
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 046d:c043
  searching devices, found USB ID 046d:c318
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 19d2:0117
   found matching vendor ID
   found matching product ID from list
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 05e3:0723
  searching devices, found USB ID 05e3:0608
  searching devices, found USB ID 1d6b:0002

Found target device 003 on bus 002

Target device description data
-------------------------
Manufacturer: ZTE,Incorporated
     Product: ZTE WCDMA Technologies MSM
  Serial No.: MF1800ZTED010000
-------------------------
 Found correct target device

Mode switch succeeded. Bye.

ok:19d2:0117
--------------------------------
(end of usb_modeswitch output)

Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1

Now checking for newly created serial devices ...
 new serial devices found, driver has bound
Checking for AVOID_RESET_QUIRK attribute
 AVOID_RESET_QUIRK activated

All done, exiting

Nach einer gewissen Zeit fragt mich der Netzwerk-Manager auch nach dem PIN der Sim-Karte worauf sich die LED-Farbe des Sticks von rot auf blau ändernt - PIN akzeptiert. Nur Verbindung kann ich dann ich mit dem Netzwerk Manager keine herstellen. Er bricht nach kurzem ab.

Zugangsdaten des Netzwerk Manger sind die Standard-Einstellungen von bob - Österreich.

Vielen Dank!

Klaus_P

Anmeldungsdatum:
10. August 2009

Beiträge: 2050

Hallo principito,

schau mal hier rein.

Gruß

Klaus P

hakunamatata Team-Icon

Supporter
Avatar von hakunamatata

Anmeldungsdatum:
30. Juni 2009

Beiträge: 5130

Hallo principito,

Habe in /etc/usb_modeswitch.d/19d2:2000 die usb-id 117 hinzugefügt. Weiß aber nicht wirklich ob das das richtige ist/war, was ich tue.

USB ModeSwitch könnte zwar eventuell auch ohne dieser Änderung funktionieren, aber der Eintrag ist auf jeden Fall richtig 👍 USB ModeSwitch funktioniert nach deinen Ausgaben ja auch problemlos. Treiber ist auch geladen. Also ich würde einmal sagen, es liegt an der Konfiguration des NetworkManagers.

Kannst du mal auf das NetworkManager-Symbol klicken und nachsehen, ob du unter Mobiles Breitband ein UMTS-Netz siehst. Die Anzeige musst du eventuell mit der rechten Maustaste bei Mobiles Breitband aktivieren noch sichtbar machen. Wenn beim Netz Roaming steht, muss diese Option bei der Verbindung auch aktiviert sein. Auch, wenn es kein Roaming ist, wenn bob das Netz von A1 mitnutzt.

edit: Beim NetworkManager könnte das Protokoll in /var/log/daemon.log aussagekräftig sein.

principito

(Themenstarter)

Anmeldungsdatum:
12. Dezember 2008

Beiträge: 8

Hallo!

Danke an alle. Ich habs geschafft.

Die Ursachen bzw. was ich getan habe:

  • Im Network Manager muss "Roaming" aktiviert sein, da BOB über das A1 netzt läuft.

  • Deaktivieren der Pin-Abfrage in einem "normalen" Handy ist hilfreich und vereinfacht die Problemfindung.

  • Der Autoboot Modus der CD kann deaktiviert werden, was das ganze auch vereinfacht.

siehe: http://ubuntuforums.org/showthread.php?t=1302235

PS: Das Kernelmodul für das Modem heißt übrigens "option". Ich hab gedacht das wäre ein Fehler - ist aber wirklich so. Dann läuft der Stick auf einem WNDR3700 Router mit Open-Wrt.

lgR

helfried

Anmeldungsdatum:
8. Februar 2007

Beiträge: 14

Ich hatte mit dem Stick größere Probleme unter Debian/Squeeze. Mal lief er, mal lief er nicht. Die Lösung sah dann folgendermaßen aus: Der Stick musste nicht nur in der Datei /lib/udev/rules.d/40-usb_modeswitch.rules bekanntgemacht werden

# ZTE MF180 ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0117", RUN+="usb_modeswitch '%b/%k'"

sondern auch in der Datei /lib/udev/rules.d/77-mm-zte-port-types.rules

ATTRS{idProduct}=="0117", ENV{.MM_USBIFNUM}=="03", ENV{ID_MM_ZTE_PORT_TYPE_MODEM}="1" ATTRS{idProduct}=="0117", ENV{.MM_USBIFNUM}=="01", ENV{ID_MM_ZTE_PORT_TYPE_AUX}="1"

Auf diese zweite Datei wurde ich durch http://www.ubuntu-austria.at/viewtopic.php?t=3770&sid=b44d8670dd193387b402aa29ff7db734 aufmerksam gemacht. Jetzt funktioniert der Stick!

chris-p-1

Anmeldungsdatum:
5. September 2011

Beiträge: 57

Hallo,

nachdem ich den USB-Stick eingesteckt habe, wird er von Ubuntu 11.04 einwandfrei erkannt. Nach Auswahl von Bob (Austria) und Aktivierung von Roaming:

"Im Network Manager muss 'Roaming' aktiviert sein, da BOB über das A1 netzt läuft"

läuft er einwandfrei.

Bearbeitet von Antiqua:

chris-p-1 schrieb: > Siehe auch: http://forum.ubuntuusers.de/topic/funktionert-das-zte-mf180-usb-umts-modem-bob-a/
Genau da angehängt und den Buntstift rauseditiert.

Antworten |