[opensuse-kde] KNetworkManager and UMTS connections
Hi there, I cannot get a connection with my USB UMTS stick and KNetworkManager. It does work with umtsmon, because this application does allow to specify the correct ttyUSB device name. So I wonder, whether there is a way with KNetworkManager to specify the correct ttyUSB device. I don´t see any option in the KNetworkManager GUI, so I guess it is not possible, right? openSUSE 11.4 x86_64 KDE 4.7.4 from openSUSE KDE repo Huawei UMTS Stick Thanx Malte -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Donnerstag, 29. Dezember 2011 schrieb Malte Gell:
I cannot get a connection with my USB UMTS stick and KNetworkManager.
Please, be more specific: What is in/var/log/messages and /var/log/NetworkManager?
It does work with umtsmon, because this application does allow to specify the correct ttyUSB device name. (...).
AFAIK the ModemManager is used for finding the correct ttyUSB device. That is because you cannot know the correct ttyUSB device name in advance, since the number depends on the order of connecting them. E.g. "my" Tchibo Surfstick is ttyUSB3 because the internal UMTS modem is ttyUSB1. Well, actually the internal modem uses ttyUSB0 for diagnostics, ttyUSB1 for 3G and ttyUSB2 for the NMEA GPS port. When I connect the Surfstick (Huawei E220/E230/E270), NetworkManager recognizes the modem, it starts blinking blue while the following happens in /var/log/messages: Dec 29 22:04:15 karl kernel: [86382.908596] usb 2-1.2: new high speed USB device using ehci_hcd and address 64 Dec 29 22:04:15 karl kernel: [86382.996755] usb 2-1.2: New USB device found, idVendor=12d1, idProduct=1003 Dec 29 22:04:15 karl kernel: [86382.996777] usb 2-1.2: New USB device strings: Mfr=2, Product=1, SerialNumber=0 Dec 29 22:04:15 karl kernel: [86382.996782] usb 2-1.2: Product: HUAWEI Mobile Dec 29 22:04:15 karl kernel: [86382.996785] usb 2-1.2: Manufacturer: HUAWEI Technology Dec 29 22:04:15 karl kernel: [86383.000853] scsi7 : usb-storage 2-1.2:1.0 Dec 29 22:04:15 karl mtp-probe: checking bus 2, device 64: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2" Dec 29 22:04:15 karl kernel: [86383.007044] usb 2-1.2: USB disconnect, address 64 Dec 29 22:04:15 karl mtp-probe: bus: 2, device: 64 was not an MTP device Dec 29 22:04:15 karl kernel: [86383.241447] usbcore: registered new interface driver uas Dec 29 22:04:20 karl kernel: [86388.039547] usb 2-1.2: new high speed USB device using ehci_hcd and address 65 Dec 29 22:04:20 karl kernel: [86388.126708] usb 2-1.2: New USB device found, idVendor=12d1, idProduct=1003 Dec 29 22:04:20 karl kernel: [86388.126730] usb 2-1.2: New USB device strings: Mfr=2, Product=1, SerialNumber=0 Dec 29 22:04:20 karl kernel: [86388.126734] usb 2-1.2: Product: HUAWEI Mobile Dec 29 22:04:20 karl kernel: [86388.126736] usb 2-1.2: Manufacturer: HUAWEI Technology Dec 29 22:04:20 karl kernel: [86388.131444] scsi10 : usb-storage 2-1.2:1.2 Dec 29 22:04:20 karl mtp-probe: checking bus 2, device 65: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2" Dec 29 22:04:20 karl kernel: [86388.133253] scsi11 : usb-storage 2-1.2:1.3 Dec 29 22:04:20 karl mtp-probe: bus: 2, device: 65 was not an MTP device Dec 29 22:04:20 karl kernel: [86388.319211] USB Serial support registered for GSM modem (1- port) Dec 29 22:04:20 karl kernel: [86388.319435] option 2-1.2:1.0: GSM modem (1-port) converter detected Dec 29 22:04:20 karl kernel: [86388.320129] usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB3 Dec 29 22:04:20 karl kernel: [86388.320179] option 2-1.2:1.1: GSM modem (1-port) converter detected Dec 29 22:04:20 karl kernel: [86388.320404] usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB4 Dec 29 22:04:20 karl kernel: [86388.320806] usbcore: registered new interface driver option Dec 29 22:04:20 karl kernel: [86388.320825] option: v0.7.2:USB Driver for GSM modems Dec 29 22:04:20 karl modem-manager: (Huawei): (ttyUSB4) deferring support check Dec 29 22:04:20 karl modem-manager: (ttyUSB3) opening serial device... Dec 29 22:04:20 karl modem-manager: (ttyUSB3): probe requested by plugin 'Huawei' Dec 29 22:04:21 karl kernel: [86389.133973] scsi 10:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2 Dec 29 22:04:21 karl kernel: [86389.136104] scsi 11:0:0:0: Direct-Access HUAWEI MMC Storage 2.31 PQ: 0 ANS Dec 29 22:04:21 karl kernel: [86389.137106] sd 11:0:0:0: Attached scsi generic sg2 type 0 Dec 29 22:04:21 karl kernel: [86389.147544] sd 11:0:0:0: [sdb] Attached SCSI removable disk Dec 29 22:04:21 karl kernel: [86389.155222] sr1: scsi-1 drive Dec 29 22:04:21 karl kernel: [86389.155585] sr 10:0:0:0: Attached scsi CD-ROM sr1 Dec 29 22:04:21 karl kernel: [86389.155812] sr 10:0:0:0: Attached scsi generic sg3 type 5 Dec 29 22:04:22 karl modem-manager: (ttyUSB3) closing serial device... Dec 29 22:04:22 karl modem-manager: (ttyUSB3) opening serial device... Dec 29 22:04:22 karl modem-manager: (Huawei): GSM modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2 claimed port ttyUSB3 Dec 29 22:04:22 karl modem-manager: Added modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2 Dec 29 22:04:22 karl modem-manager: (tty/ttyUSB3): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2 Dec 29 22:04:22 karl modem-manager: (tty/ttyUSB4): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2 Dec 29 22:04:22 karl modem-manager: (ttyUSB3) closing serial device... Dec 29 22:04:22 karl modem-manager: (tty/ttyUSB4): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2 Dec 29 22:04:23 karl modem-manager: (ttyUSB4): re-checking support... Dec 29 22:04:23 karl modem-manager: (ttyUSB4) opening serial device... Dec 29 22:04:28 karl modem-manager: (ttyUSB4) closing serial device... Dec 29 22:04:28 karl modem-manager: (Huawei): GSM modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2 claimed port ttyUSB4 Dec 29 22:04:28 karl modem-manager: Exported modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2 as /org/freedesktop/ModemManager/Modems/3 Dec 29 22:04:28 karl modem-manager: (/org/freedesktop/ModemManager/Modems/3): data port is ttyUSB3 jan@karl:~> nmcli dev GERAT TYP STATUS eth0 802-3-ethernet nicht verfügbar wlan0 802-11-wireless verbunden ttyUSB1 gsm nicht verbunden ttyUSB3 gsm nicht verbunden Gruß Jan -- If the opposite of pro is con, what is the opposite of Progress? -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Okay, this is what /var/log/NetworkManager says, /var/log/messages did not reveal any output..... Dec 29 23:22:34 EehxineNymgCbYSg NetworkManager[2050]: <info> Activation (ttyUSB0) starting connection 'Tchibo-Mobil' Dec 29 23:22:34 EehxineNymgCbYSg NetworkManager[2050]: <info> (ttyUSB0): device state change: 3 -> 4 (reason 0) Dec 29 23:22:34 EehxineNymgCbYSg NetworkManager[2050]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Dec 29 23:22:34 EehxineNymgCbYSg NetworkManager[2050]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Dec 29 23:22:34 EehxineNymgCbYSg NetworkManager[2050]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Dec 29 23:22:45 EehxineNymgCbYSg NetworkManager[2050]: <warn> GSM connection failed: (32) Sending command failed: 'Resource temporarily unavailable' Dec 29 23:22:45 EehxineNymgCbYSg NetworkManager[2050]: <info> (ttyUSB0): device state change: 4 -> 9 (reason 1) Dec 29 23:22:45 EehxineNymgCbYSg NetworkManager[2050]: <info> Marking connection 'Tchibo-Mobil' invalid. Dec 29 23:22:45 EehxineNymgCbYSg NetworkManager[2050]: <warn> Activation (ttyUSB0) failed. Dec 29 23:22:45 EehxineNymgCbYSg NetworkManager[2050]: <info> (ttyUSB0): device state change: 9 -> 3 (reason 0) Dec 29 23:22:45 EehxineNymgCbYSg NetworkManager[2050]: <info> (ttyUSB0): deactivating device (reason: 0). nmcli dev says GERAT TYP STATUS eth0 802-3-ethernet connected wlan0 802-11-wireless not connected ttyUSB0 gsm not connected Strangely, in /dev I have three ttyUSB devices: crw-rw---- 1 root dialout 188, 0 29. Dez 23:26 ttyUSB0 crw-rw---- 1 root dialout 188, 1 29. Dez 21:47 ttyUSB1 crw-rw---- 1 root dialout 188, 2 29. Dez 21:57 ttyUSB2 I am member of dialout. Thanx Malte -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Donnerstag, 29. Dezember 2011 schrieb Malte Gell:
Okay, this is what /var/log/NetworkManager says, /var/log/messages did not reveal any output..... (...).
And when you insert the UMTS stick? Then there should be such messages like I posted yesterday. And in /var/log/NetworkManager, there should be some messages about the ttyUSB devices the ModemManager found. If you think you get too less messages, then try the debugging modes: * killall NetworkManager * killall modem-manager * modem-manager --debug * NM_PPP_DEBUG=1 /usr/sbin/NetworkManager --no-daemon
GERAT TYP STATUS eth0 802-3-ethernet connected wlan0 802-11-wireless not connected ttyUSB0 gsm not connected
And this is the wrong ttyUSB? If so, to whom it belongs to?
Strangely, in /dev I have three ttyUSB devices:
Yes, there should only be two with nearly identical times.
crw-rw---- 1 root dialout 188, 0 29. Dez 23:26 ttyUSB0 crw-rw---- 1 root dialout 188, 1 29. Dez 21:47 ttyUSB1 crw-rw---- 1 root dialout 188, 2 29. Dez 21:57 ttyUSB2
I am member of dialout.
Same here, but I do not have to be a member of the dialout group. BTW: debugging 3G sucks! For my Gobi2000, I had to patch the kernel module of 11.3 Then, with 11.4 the patch was included in the kernel, but the modem stopped working anyhow. After some it worked again and I still do not even know why: http://www.thinkwiki.org/wiki/Installing_OpenSUSE_11.4_on_a_ThinkPad_T410s#W... Gruß Jan -- Health is merely the slowest possible rate at which one can die. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am 30.12.2011 11:33, schrieb Jan Ritzerfeld:
And when you insert the UMTS stick? Then there should be such messages like I posted yesterday. And in /var/log/NetworkManager, there should be some messages about the ttyUSB devices the ModemManager found.
Okay, below is the full output of /var/log/messages when I plug in the UMTS stick.
ttyUSB0 gsm not connected
And this is the wrong ttyUSB? If so, to whom it belongs to?
According to /var/log/messages two ttyUSBx devices are bing created or used, ttyUSB2 and ttyUSB1. Thanx for any hints Malte Dec 31 22:39:17 EehxineNymgCbYSg kernel: [ 6533.037474] usb 2-2.4: new high speed USB device using ehci_hcd and address 11 Dec 31 22:39:17 EehxineNymgCbYSg kernel: [ 6533.116574] usb 2-2.4: New USB device found, idVendor=12d1, idProduct=1446 Dec 31 22:39:17 EehxineNymgCbYSg kernel: [ 6533.116580] usb 2-2.4: New USB device strings: Mfr=3, Product=2, SerialNumber=0 Dec 31 22:39:17 EehxineNymgCbYSg kernel: [ 6533.116585] usb 2-2.4: Product: HUAWEI Mobile Dec 31 22:39:17 EehxineNymgCbYSg kernel: [ 6533.116588] usb 2-2.4: Manufacturer: HUAWEI Technology Dec 31 22:39:17 EehxineNymgCbYSg mtp-probe: checking bus 2, device 11: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2.4" Dec 31 22:39:17 EehxineNymgCbYSg kernel: [ 6533.119458] scsi6 : usb-storage 2-2.4:1.0 Dec 31 22:39:17 EehxineNymgCbYSg kernel: [ 6533.120316] scsi7 : usb-storage 2-2.4:1.1 Dec 31 22:39:17 EehxineNymgCbYSg mtp-probe: bus: 2, device: 11 was not an MTP device Dec 31 22:39:17 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x12D1, PID: 0x1446, path: /dev/bus/usb/002/011 Dec 31 22:39:17 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x12D1, PID: 0x1446, path: /dev/bus/usb/002/011 Dec 31 22:39:18 EehxineNymgCbYSg usb_modeswitch: switching 12d1:1446 (HUAWEI Technology: HUAWEI Mobile) Dec 31 22:39:18 EehxineNymgCbYSg kernel: [ 6534.141574] usb 2-2.4: USB disconnect, address 11 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:584:HPEstablishUSBNotifications() Device removed Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/003/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/004/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/001/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/001/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0xEB1A, PID: 0x51B2, path: /dev/bus/usb/001/002 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/005/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/005/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x046A, PID: 0x0023, path: /dev/bus/usb/005/002 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x046A, PID: 0x0023, path: /dev/bus/usb/005/002 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/006/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/006/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x046D, PID: 0xC043, path: /dev/bus/usb/006/002 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/007/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/008/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/002/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/002/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1A40, PID: 0x0101, path: /dev/bus/usb/002/003 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1A40, PID: 0x0101, path: /dev/bus/usb/002/006 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x03F0, PID: 0x1504, path: /dev/bus/usb/002/007 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x03F0, PID: 0x1504, path: /dev/bus/usb/002/007 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1A40, PID: 0x0101, path: /dev/bus/usb/002/006 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x046D, PID: 0x0825, path: /dev/bus/usb/002/008 Dec 31 22:39:18 pcscd: last message repeated 3 times Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1A40, PID: 0x0101, path: /dev/bus/usb/002/006 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x0A12, PID: 0x0001, path: /dev/bus/usb/002/009 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x0A12, PID: 0x0001, path: /dev/bus/usb/002/009 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1A40, PID: 0x0101, path: /dev/bus/usb/002/006 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x0C4B, PID: 0x0400, path: /dev/bus/usb/002/010 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1A40, PID: 0x0101, path: /dev/bus/usb/002/006 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1A40, PID: 0x0101, path: /dev/bus/usb/002/003 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/002/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x064E, PID: 0xA103, path: /dev/bus/usb/002/005 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x064E, PID: 0xA103, path: /dev/bus/usb/002/005 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:584:HPEstablishUSBNotifications() Device removed Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/003/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/004/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/001/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/001/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0xEB1A, PID: 0x51B2, path: /dev/bus/usb/001/002 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/005/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/005/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x046A, PID: 0x0023, path: /dev/bus/usb/005/002 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x046A, PID: 0x0023, path: /dev/bus/usb/005/002 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/006/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/006/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x046D, PID: 0xC043, path: /dev/bus/usb/006/002 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/007/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/008/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/002/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/002/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1A40, PID: 0x0101, path: /dev/bus/usb/002/003 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1A40, PID: 0x0101, path: /dev/bus/usb/002/006 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x03F0, PID: 0x1504, path: /dev/bus/usb/002/007 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x03F0, PID: 0x1504, path: /dev/bus/usb/002/007 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1A40, PID: 0x0101, path: /dev/bus/usb/002/006 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x046D, PID: 0x0825, path: /dev/bus/usb/002/008 Dec 31 22:39:18 pcscd: last message repeated 3 times Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1A40, PID: 0x0101, path: /dev/bus/usb/002/006 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x0A12, PID: 0x0001, path: /dev/bus/usb/002/009 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x0A12, PID: 0x0001, path: /dev/bus/usb/002/009 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1A40, PID: 0x0101, path: /dev/bus/usb/002/006 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x0C4B, PID: 0x0400, path: /dev/bus/usb/002/010 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1A40, PID: 0x0101, path: /dev/bus/usb/002/006 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1A40, PID: 0x0101, path: /dev/bus/usb/002/003 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/002/001 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x064E, PID: 0xA103, path: /dev/bus/usb/002/005 Dec 31 22:39:18 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x064E, PID: 0xA103, path: /dev/bus/usb/002/005 Dec 31 22:39:22 EehxineNymgCbYSg kernel: [ 6538.156479] usb 2-2.4: new high speed USB device using ehci_hcd and address 12 Dec 31 22:39:22 EehxineNymgCbYSg kernel: [ 6538.233892] usb 2-2.4: New USB device found, idVendor=12d1, idProduct=1436 Dec 31 22:39:22 EehxineNymgCbYSg kernel: [ 6538.233898] usb 2-2.4: New USB device strings: Mfr=4, Product=3, SerialNumber=0 Dec 31 22:39:22 EehxineNymgCbYSg kernel: [ 6538.233902] usb 2-2.4: Product: HUAWEI Mobile Dec 31 22:39:22 EehxineNymgCbYSg kernel: [ 6538.233905] usb 2-2.4: Manufacturer: HUAWEI Technology Dec 31 22:39:22 EehxineNymgCbYSg kernel: [ 6538.238921] scsi13 : usb-storage 2-2.4:1.5 Dec 31 22:39:22 EehxineNymgCbYSg kernel: [ 6538.239902] scsi14 : usb-storage 2-2.4:1.6 Dec 31 22:39:22 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x12D1, PID: 0x1436, path: /dev/bus/usb/002/012 Dec 31 22:39:22 pcscd: last message repeated 3 times Dec 31 22:39:22 EehxineNymgCbYSg kernel: [ 6538.324261] USB Serial support registered for GSM modem (1-port) Dec 31 22:39:22 EehxineNymgCbYSg kernel: [ 6538.324401] option 2-2.4:1.0: GSM modem (1-port) converter detected Dec 31 22:39:22 EehxineNymgCbYSg kernel: [ 6538.324987] usb 2-2.4: GSM modem (1-port) converter now attached to ttyUSB0 Dec 31 22:39:22 EehxineNymgCbYSg kernel: [ 6538.325272] option 2-2.4:1.3: GSM modem (1-port) converter detected Dec 31 22:39:22 EehxineNymgCbYSg kernel: [ 6538.325648] usb 2-2.4: GSM modem (1-port) converter now attached to ttyUSB1 Dec 31 22:39:22 EehxineNymgCbYSg kernel: [ 6538.325664] option 2-2.4:1.4: GSM modem (1-port) converter detected Dec 31 22:39:22 EehxineNymgCbYSg kernel: [ 6538.325942] usb 2-2.4: GSM modem (1-port) converter now attached to ttyUSB2 Dec 31 22:39:22 EehxineNymgCbYSg kernel: [ 6538.326293] usbcore: registered new interface driver option Dec 31 22:39:22 EehxineNymgCbYSg kernel: [ 6538.326296] option: v0.7.2:USB Driver for GSM modems Dec 31 22:39:22 EehxineNymgCbYSg pcscd: hotplug_libudev.c:261:get_driver() Looking for a driver for VID: 0x12D1, PID: 0x1436, path: /dev/bus/usb/002/012 Dec 31 22:39:22 pcscd: last message repeated 2 times Dec 31 22:39:22 EehxineNymgCbYSg modem-manager: (Huawei): (ttyUSB2) deferring support check Dec 31 22:39:22 EehxineNymgCbYSg modem-manager: (Huawei): (ttyUSB1) deferring support check Dec 31 22:39:22 EehxineNymgCbYSg modem-manager: (ttyUSB0) opening serial device... Dec 31 22:39:22 EehxineNymgCbYSg modem-manager: (ttyUSB0): probe requested by plugin 'Huawei' Dec 31 22:39:23 EehxineNymgCbYSg kernel: [ 6539.241385] scsi 13:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2 Dec 31 22:39:23 EehxineNymgCbYSg kernel: [ 6539.242318] scsi 14:0:0:0: Direct-Access HUAWEI SD Storage 2.31 PQ: 0 ANSI: 2 Dec 31 22:39:23 EehxineNymgCbYSg kernel: [ 6539.242693] sd 14:0:0:0: Attached scsi generic sg2 type 0 Dec 31 22:39:23 EehxineNymgCbYSg kernel: [ 6539.246042] sd 14:0:0:0: [sdb] Attached SCSI removable disk Dec 31 22:39:23 EehxineNymgCbYSg kernel: [ 6539.247891] sr1: scsi-1 drive Dec 31 22:39:23 EehxineNymgCbYSg kernel: [ 6539.248062] sr 13:0:0:0: Attached scsi CD-ROM sr1 Dec 31 22:39:23 EehxineNymgCbYSg kernel: [ 6539.248179] sr 13:0:0:0: Attached scsi generic sg3 type 5 Dec 31 22:39:23 EehxineNymgCbYSg modem-manager: Got failure code 14: SIM busy Dec 31 22:39:24 EehxineNymgCbYSg modem-manager: (ttyUSB0) closing serial device... Dec 31 22:39:24 EehxineNymgCbYSg modem-manager: (ttyUSB0) opening serial device... Dec 31 22:39:24 EehxineNymgCbYSg modem-manager: (Huawei): GSM modem /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2.4 claimed port ttyUSB0 Dec 31 22:39:24 EehxineNymgCbYSg modem-manager: Added modem /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2.4 Dec 31 22:39:24 EehxineNymgCbYSg modem-manager: (tty/ttyUSB0): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2.4 Dec 31 22:39:24 EehxineNymgCbYSg modem-manager: (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2.4 Dec 31 22:39:24 EehxineNymgCbYSg modem-manager: (ttyUSB0) closing serial device... Dec 31 22:39:24 EehxineNymgCbYSg modem-manager: (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2.4 Dec 31 22:39:25 EehxineNymgCbYSg modem-manager: (ttyUSB2): re-checking support... Dec 31 22:39:25 EehxineNymgCbYSg modem-manager: (ttyUSB2) opening serial device... Dec 31 22:39:25 EehxineNymgCbYSg modem-manager: (ttyUSB1): re-checking support... Dec 31 22:39:25 EehxineNymgCbYSg modem-manager: (ttyUSB1) opening serial device... Dec 31 22:39:25 EehxineNymgCbYSg modem-manager: (ttyUSB2) closing serial device... Dec 31 22:39:25 EehxineNymgCbYSg modem-manager: (Huawei): GSM modem /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2.4 claimed port ttyUSB2 Dec 31 22:39:25 EehxineNymgCbYSg modem-manager: (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2.4 Dec 31 22:39:30 EehxineNymgCbYSg modem-manager: (ttyUSB1) closing serial device... Dec 31 22:39:30 EehxineNymgCbYSg modem-manager: (Huawei): GSM modem /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2.4 claimed port ttyUSB1 Dec 31 22:39:30 EehxineNymgCbYSg modem-manager: Exported modem /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2.4 as /org/freedesktop/ModemManager/Modems/0 Dec 31 22:39:30 EehxineNymgCbYSg modem-manager: (/org/freedesktop/ModemManager/Modems/0): data port is ttyUSB0 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Samstag, 31. Dezember 2011 schrieb Malte Gell:
Am 30.12.2011 11:33, schrieb Jan Ritzerfeld:
And when you insert the UMTS stick? Then there should be such messages like I posted yesterday. And in /var/log/NetworkManager, there should be some messages about the ttyUSB devices the ModemManager found.
Okay, below is the full output of /var/log/messages when I plug in the UMTS stick.
Okay, did you follow the advice of Martin to use the networkmanagement plasmoid instead of knetworkmanager? And did you check whether it is up-to- date? Furthermore, you could try the networkmanager-gnome pendant: nm-applet IIRC? If this does not work, it is not a KDE issue.
ttyUSB0 gsm not connected
And this is the wrong ttyUSB? If so, to whom it belongs to?
According to /var/log/messages two ttyUSBx devices are bing created or used, ttyUSB2 and ttyUSB1. [...]
Actually, your log shows that there are three USB device created by your stick. Which device works with umtsmon? Gruß Jan -- You cannot strengthen the weak by weakening the strong. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am 04.01.2012 18:16, schrieb Jan Ritzerfeld:
Okay, did you follow the advice of Martin to use the networkmanagement plasmoid instead of knetworkmanager? And did you check whether it is up-to- date?
Yes, I do use the networkmanagement plasmoid, I have this version installed: plasmoid-networkmanagement-0.9.1git20111209-11.2.x86_64
According to /var/log/messages two ttyUSBx devices are bing created or used, ttyUSB2 and ttyUSB1. [...]
Actually, your log shows that there are three USB device created by your stick. Which device works with umtsmon?
umtsmon uses these devices: ATPortName=/dev/ttyUSB2 PPPPortName=/dev/ttyUSB0 It seems, umtsmon uses two different devices? Is this normal? At least, umtsmon works fine with these settings. Thanx Malte -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Donnerstag, 5. Januar 2012 schrieb Malte Gell:
[...] umtsmon uses these devices:
ATPortName=/dev/ttyUSB2 PPPPortName=/dev/ttyUSB0
It seems, umtsmon uses two different devices? Is this normal? At least, umtsmon works fine with these settings.
The first port is where the AT commands are sent to (basically the same as with the old analog modems). The second port is the data port. In the messages log you posted to the list you see that the modem-manager says data port is ttyUSB0 and nmcli dev ttyUSB0 gsm not connected Thus, at least this port is correctly detected by the modem-manager. However, the Network-Manager says GSM connection failed: (32) Sending command failed: 'Resource temporarily unavailable' Thus, could you please try the networkmanager-gnome pendant: nm-applet? If this does not work, too, then KDE cannot do much about and you should open a bug report upstream, that is, gnome AFAIK. Gruß Jan -- Don't ever slam a door, you might want to go back. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
The first port is where the AT commands are sent to (basically the same as with the old analog modems). The second port is the data port. In the messages log you posted to the list you see that the modem-manager says data port is ttyUSB0 and nmcli dev ttyUSB0 gsm not connected Thus, at least this port is correctly detected by the modem-manager.
Strangely the stick works now. I am not aware I changed important things. I just deleted the old networkmanager UMTS profile and created it new from scratch. Now the UMTS stick is able to establish a connection. I do not know why it works now, but it does work now. I will keep an eye on it. Regards Malte -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Sonntag, 8. Januar 2012 schrieb Malte Gell:
[...] Strangely the stick works now. I am not aware I changed important things. I just deleted the old networkmanager UMTS profile and created it new from scratch. Now the UMTS stick is able to establish a connection. I do not know why it works now, but it does work now. I will keep an eye on it.
Well, you are not alone: that is exactly what happened to me with the internal Qualcomm Gobi 2000 WWAN adapter. After reading tons of bug reports and writing some comments it just worked! :-D Gruß Jan -- It works better if you plug it in. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Sun, 2012-01-08 at 19:31 +0100, Jan Ritzerfeld wrote:
Am Sonntag, 8. Januar 2012 schrieb Malte Gell:
[...] Strangely the stick works now. I am not aware I changed important things. I just deleted the old networkmanager UMTS profile and created it new from scratch. Now the UMTS stick is able to establish a connection. I do not know why it works now, but it does work now. I will keep an eye on it.
Well, you are not alone: that is exactly what happened to me with the internal Qualcomm Gobi 2000 WWAN adapter. After reading tons of bug reports and writing some comments it just worked! :-D
Gruß Jan -- It works better if you plug it in. I seem to have missed the original issue, would anybody mind filling me in? I use internal CDMA with gobi, and noticed LibreOffice can export to media wiki, so I may be writing the wiki article finally.
-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Torsdag den 29. december 2011 20:36:19 skrev Malte Gell:
I cannot get a connection with my USB UMTS stick and KNetworkManager.
It does work with umtsmon, because this application does allow to specify the correct ttyUSB device name.
So I wonder, whether there is a way with KNetworkManager to specify the correct ttyUSB device. I don´t see any option in the KNetworkManager GUI, so I guess it is not possible, right?
openSUSE 11.4 x86_64 KDE 4.7.4 from openSUSE KDE repo Huawei UMTS Stick
You shouldn't use KNetworkManager even on 11.4 - use plasmoid- networkmanagement. Also you should check if plasmoid-networkmanagement in KR47/11.4 is reasonably up-to-date. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (4)
-
Jan Ritzerfeld -
Malte Gell -
Martin Schlander -
Roger Luedecke