Author Message

<  Setup Discussion  ~  USB Modem working on Ubuntu 11.10 but not on 12.04

PostPosted: Tue Jul 17, 2012 4:07 pm Reply with quote
Posts: 16777215 Joined: Mon Jul 09, 2012 10:19 pm
Hello,

I have an issue with a USB modem. It was working perfectly fine on Ubuntu 11.10. But has stopped working on 12.04. I posted at ubuntu forums. But I was suggested that I also post it on this issue forum. So I am hoping that someone here would help me. It is very much possible that there is a bug in ubuntu 12.04 and nothing related to usb_modeswitch.

I plugged the usb modem device in the computer. When I typed 'usb-devices' at the command prompt I obtained the following outputs on ubuntu 12.04 and 11.10:

Quote:
Ubuntu 12.04:
*************
T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=12d1 ProdID=1446 Rev=00.00
S: Manufacturer=HUA?WEI TECHNOLOGIES
S: Product=HUAWEI Mobile
S: SerialNumber=???????????????????
C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)

Ubuntu 11.10:
*************
T: Bus=02 Lev=02 Prnt=02 Port=03 Cnt=02 Dev#= 6 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=12d1 ProdID=140b Rev=00.00
S: Manufacturer=HUA?WEI TECHNOLOGIES
S: Product=HUAWEI Mobile
S: SerialNumber=???????????????????
C: #Ifs= 4 Cfg#= 1 Atr=a0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 3 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage


Then I compared the outputs of tail /var/log -f which is as follows:

Quote:
Ubuntu 12.04:
*************
Jul 7 02:52:51 sath-VPCSA35GG mtp-probe: checking bus 2, device 13: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3"
Jul 7 02:52:51 sath-VPCSA35GG mtp-probe: bus: 2, device: 13 was not an MTP device
Jul 7 02:53:12 sath-VPCSA35GG kernel: [18025.266834] CPU3: Package power limit notification (total events = 76333)
Jul 7 02:53:12 sath-VPCSA35GG kernel: [18025.266837] CPU2: Package power limit notification (total events = 76333)
Jul 7 02:53:12 sath-VPCSA35GG kernel: [18025.266841] CPU1: Package power limit notification (total events = 75807)
Jul 7 02:53:12 sath-VPCSA35GG kernel: [18025.266843] CPU0: Package power limit notification (total events = 75791)
Jul 7 02:53:12 sath-VPCSA35GG kernel: [18025.266924] CPU1: Package power limit normal
Jul 7 02:53:12 sath-VPCSA35GG kernel: [18025.266927] CPU3: Package power limit normal
Jul 7 02:53:12 sath-VPCSA35GG kernel: [18025.266929] CPU2: Package power limit normal
Jul 7 02:53:12 sath-VPCSA35GG kernel: [18025.266931] CPU0: Package power limit normal
---------------------------------------------------------------------------------------------------------------------------------------------------------------
# The device was plugged at this instant
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Jul 7 02:55:43 sath-VPCSA35GG kernel: [18175.795452] usb 3-1: new full-speed USB device number 5 using xhci_hcd
Jul 7 02:55:43 sath-VPCSA35GG mtp-probe: checking bus 3, device 5: "/sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/usb3/3-1"
Jul 7 02:55:43 sath-VPCSA35GG mtp-probe: bus: 3, device: 5 was not an MTP device
Jul 7 02:55:43 sath-VPCSA35GG kernel: [18175.837011] scsi9 : usb-storage 3-1:1.0
Jul 7 02:55:43 sath-VPCSA35GG kernel: [18175.920135] usbcore: registered new interface driver usbserial
Jul 7 02:55:43 sath-VPCSA35GG kernel: [18175.920144] USB Serial support registered for generic
Jul 7 02:55:43 sath-VPCSA35GG kernel: [18175.920162] usbcore: registered new interface driver usbserial_generic
Jul 7 02:55:43 sath-VPCSA35GG kernel: [18175.920163] usbserial: USB Serial Driver core
Jul 7 02:55:43 sath-VPCSA35GG kernel: [18175.940683] USB Serial support registered for GSM modem (1-port)
Jul 7 02:55:43 sath-VPCSA35GG kernel: [18175.940757] usbcore: registered new interface driver option
Jul 7 02:55:43 sath-VPCSA35GG kernel: [18175.940758] option: v0.7.2:USB Driver for GSM modems
Jul 7 02:55:44 sath-VPCSA35GG kernel: [18176.838650] scsi 9:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 0
Jul 7 02:55:44 sath-VPCSA35GG kernel: [18176.851555] sr1: scsi-1 drive
Jul 7 02:55:44 sath-VPCSA35GG kernel: [18176.851691] sr 9:0:0:0: Attached scsi CD-ROM sr1
Jul 7 02:55:44 sath-VPCSA35GG kernel: [18176.851822] sr 9:0:0:0: Attached scsi generic sg4 type 5
Jul 7 02:55:45 sath-VPCSA35GG usb_modeswitch: switching device 12d1:1446 on 003/005


Ubuntu 11.10:
*************
Jul 16 22:24:26 sathya-Vostro-3400 acpid: 1 client rule loaded
Jul 16 22:24:26 sathya-Vostro-3400 kernel: [11211.427187] r8169 0000:13:00.0: eth0: link down
Jul 16 22:24:26 sathya-Vostro-3400 kernel: [11211.428132] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 16 22:24:26 sathya-Vostro-3400 NetworkManager[902]: <info> (wlan0): supplicant interface state: starting -> ready
Jul 16 22:24:26 sathya-Vostro-3400 NetworkManager[902]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Jul 16 22:24:26 sathya-Vostro-3400 NetworkManager[902]: <info> (wlan0): supplicant interface state: ready -> inactive
Jul 16 22:24:28 sathya-Vostro-3400 kernel: [11213.467528] EXT4-fs (sda7): re-mounted. Opts: errors=remount-ro,commit=600
Jul 16 22:25:16 sathya-Vostro-3400 xscreensaver: pam_ecryptfs: pam_sm_authenticate: /home/sathya is already mounted
Jul 16 22:25:25 sathya-Vostro-3400 kernel: [11270.310529] ieee80211 phy0: wl0: wlc_recv: dropping a frame with invalid src mac address, a2: 00:00:00:00:00:00
Jul 16 22:25:29 sathya-Vostro-3400 kernel: [11275.093407] ieee80211 phy0: wl0: wlc_recv: dropping a frame with invalid src mac address, a2: 00:00:00:00:00:00
Jul 16 22:25:47 sathya-Vostro-3400 kernel: [11292.395648] ieee80211 phy0: wl0: wlc_recv: dropping a frame with invalid src mac address, a2: 00:00:00:00:00:00
Jul 16 22:25:53 sathya-Vostro-3400 kernel: [11299.124328] ieee80211 phy0: wl0: wlc_recv: dropping a frame with invalid src mac address, a2: 2f:72:75:6e:20:74
Jul 16 22:25:56 sathya-Vostro-3400 kernel: [11301.485540] ieee80211 phy0: wl0: wlc_recv: dropping a frame with invalid src mac address, a2: 00:00:00:00:00:00
Jul 16 22:26:06 sathya-Vostro-3400 kernel: [11311.685389] ieee80211 phy0: wl0: wlc_recv: dropping a frame with invalid src mac address, a2: 00:00:00:00:00:00
Jul 16 22:26:18 sathya-Vostro-3400 kernel: [11323.568614] ieee80211 phy0: wl0: wlc_recv: dropping a frame with invalid src mac address, a2: 00:00:00:00:00:00
Jul 16 22:26:22 sathya-Vostro-3400 kernel: [11327.542950] ieee80211 phy0: wl0: wlc_recv: dropping a frame with invalid src mac address, a2: 00:00:00:00:00:00
Jul 16 22:26:23 sathya-Vostro-3400 kernel: [11328.264762] ieee80211 phy0: wl0: wlc_recv: dropping a frame with invalid src mac address, a2: 00:00:00:00:00:00
Jul 16 22:26:23 sathya-Vostro-3400 kernel: [11328.739137] ieee80211 phy0: wl0: wlc_recv: dropping a frame with invalid src mac address, a2: 00:00:00:00:00:00
Jul 16 22:26:25 sathya-Vostro-3400 kernel: [11330.476324] ieee80211 phy0: wl0: wlc_recv: dropping a frame with invalid src mac address, a2: ef:ff:ef:ef:ef:ff
---------------------------------------------------------------------------------------------------------------------------------------------------------------
# The device was plugged at this instant
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Jul 16 22:26:42 sathya-Vostro-3400 kernel: [11347.478438] usb 2-1.1: new full speed USB device number 12 using ehci_hcd
Jul 16 22:26:42 sathya-Vostro-3400 kernel: [11347.573070] scsi26 : usb-storage 2-1.1:1.0
Jul 16 22:26:42 sathya-Vostro-3400 mtp-probe: checking bus 2, device 12: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1"
Jul 16 22:26:42 sathya-Vostro-3400 mtp-probe: bus: 2, device: 12 was not an MTP device
Jul 16 22:26:43 sathya-Vostro-3400 usb_modeswitch: switching device 12d1:1446 on 002/012
Jul 16 22:26:43 sathya-Vostro-3400 kernel: [11348.431744] usb 2-1.1: USB disconnect, device number 12
Jul 16 22:26:46 sathya-Vostro-3400 kernel: [11351.950689] usb 2-1.1: new full speed USB device number 13 using ehci_hcd
Jul 16 22:26:46 sathya-Vostro-3400 kernel: [11352.045605] option 2-1.1:1.0: GSM modem (1-port) converter detected
Jul 16 22:26:46 sathya-Vostro-3400 kernel: [11352.045790] usb 2-1.1: GSM modem (1-port) converter now attached to ttyUSB0
Jul 16 22:26:46 sathya-Vostro-3400 mtp-probe: checking bus 2, device 13: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1"
Jul 16 22:26:46 sathya-Vostro-3400 kernel: [11352.046661] option 2-1.1:1.1: GSM modem (1-port) converter detected
Jul 16 22:26:46 sathya-Vostro-3400 kernel: [11352.046839] usb 2-1.1: GSM modem (1-port) converter now attached to ttyUSB1
Jul 16 22:26:46 sathya-Vostro-3400 kernel: [11352.047584] option 2-1.1:1.2: GSM modem (1-port) converter detected
Jul 16 22:26:46 sathya-Vostro-3400 kernel: [11352.047744] usb 2-1.1: GSM modem (1-port) converter now attached to ttyUSB2
Jul 16 22:26:46 sathya-Vostro-3400 kernel: [11352.048314] scsi30 : usb-storage 2-1.1:1.3
Jul 16 22:26:47 sathya-Vostro-3400 mtp-probe: bus: 2, device: 13 was not an MTP device
Jul 16 22:26:47 sathya-Vostro-3400 modem-manager[897]: <info> (ttyUSB0) opening serial port...
Jul 16 22:26:47 sathya-Vostro-3400 logger: usb_modeswitch: switched to 12d1:140b on 002/013
Jul 16 22:26:47 sathya-Vostro-3400 modem-manager[897]: <info> (ttyUSB0) closing serial port...
Jul 16 22:26:47 sathya-Vostro-3400 modem-manager[897]: <info> (ttyUSB0) serial port closed
Jul 16 22:26:47 sathya-Vostro-3400 modem-manager[897]: <info> (ttyUSB0) opening serial port...
Jul 16 22:26:47 sathya-Vostro-3400 modem-manager[897]: <info> (Huawei): CDMA modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1 claimed port ttyUSB0
Jul 16 22:26:47 sathya-Vostro-3400 kernel: [11353.046601] scsi 30:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 0
Jul 16 22:26:47 sathya-Vostro-3400 kernel: [11353.048544] scsi 30:0:0:1: Direct-Access HUAWEI SD Storage 2.31 PQ: 0 ANSI: 2
Jul 16 22:26:47 sathya-Vostro-3400 kernel: [11353.065720] sr1: scsi-1 drive
Jul 16 22:26:47 sathya-Vostro-3400 kernel: [11353.065991] sr 30:0:0:0: Attached scsi CD-ROM sr1
Jul 16 22:26:47 sathya-Vostro-3400 kernel: [11353.066204] sr 30:0:0:0: Attached scsi generic sg2 type 5
Jul 16 22:26:47 sathya-Vostro-3400 kernel: [11353.066687] sd 30:0:0:1: Attached scsi generic sg3 type 0
Jul 16 22:26:47 sathya-Vostro-3400 modem-manager[897]: <info> (ttyUSB0) closing serial port...
Jul 16 22:26:47 sathya-Vostro-3400 modem-manager[897]: <info> (ttyUSB0) serial port closed
Jul 16 22:26:48 sathya-Vostro-3400 kernel: [11353.074492] sd 30:0:0:1: [sdb] Attached SCSI removable disk
Jul 16 22:26:50 sathya-Vostro-3400 modem-manager[897]: <info> (ttyUSB1) opening serial port...
Jul 16 22:26:50 sathya-Vostro-3400 modem-manager[897]: <info> (ttyUSB2) opening serial port...
Jul 16 22:26:50 sathya-Vostro-3400 modem-manager[897]: <info> (ttyUSB2) closing serial port...
Jul 16 22:26:50 sathya-Vostro-3400 modem-manager[897]: <info> (ttyUSB2) serial port closed
Jul 16 22:26:50 sathya-Vostro-3400 modem-manager[897]: <info> (Huawei): CDMA modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1 claimed port ttyUSB2
Jul 16 22:27:02 sathya-Vostro-3400 modem-manager[897]: <info> (ttyUSB1) closing serial port...
Jul 16 22:27:02 sathya-Vostro-3400 modem-manager[897]: <info> (ttyUSB1) serial port closed
Jul 16 22:27:02 sathya-Vostro-3400 modem-manager[897]: <info> (ttyUSB1) opening serial port...
Jul 16 22:27:05 sathya-Vostro-3400 modem-manager[897]: <info> (ttyUSB1) closing serial port...
Jul 16 22:27:05 sathya-Vostro-3400 modem-manager[897]: <info> (ttyUSB1) serial port closed
Jul 16 22:27:05 sathya-Vostro-3400 modem-manager[897]: <info> (Huawei): CDMA modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1 claimed port ttyUSB1
Jul 16 22:27:05 sathya-Vostro-3400 NetworkManager[902]: <warn> (ttyUSB0): failed to look up interface index
Jul 16 22:27:05 sathya-Vostro-3400 NetworkManager[902]: <info> WWAN now disabled by management service
Jul 16 22:27:05 sathya-Vostro-3400 NetworkManager[902]: <info> (ttyUSB0): new CDMA/EVDO device (driver: 'option1' ifindex: 0)
Jul 16 22:27:05 sathya-Vostro-3400 NetworkManager[902]: <info> (ttyUSB0): exported as /org/freedesktop/NetworkManager/Devices/6
Jul 16 22:27:05 sathya-Vostro-3400 NetworkManager[902]: <info> (ttyUSB0): now managed
Jul 16 22:27:05 sathya-Vostro-3400 NetworkManager[902]: <info> (ttyUSB0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jul 16 22:27:05 sathya-Vostro-3400 NetworkManager[902]: <info> (ttyUSB0): deactivating device (reason 'managed') [2]
Jul 16 22:27:05 sathya-Vostro-3400 NetworkManager[902]: nm_system_iface_flush_routes: assertion `ifindex > 0' failed
Jul 16 22:27:05 sathya-Vostro-3400 NetworkManager[902]: nm_system_iface_flush_addresses: assertion `ifindex > 0' failed
Jul 16 22:27:05 sathya-Vostro-3400 NetworkManager[902]: <info> (ttyUSB0): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
Jul 16 22:27:09 sathya-Vostro-3400 kernel: [11374.054357] ieee80211 phy0: wl0: wlc_recv: dropping a frame with invalid src mac address, a2: 00:00:00:00:00:00
Jul 16 22:27:09 sathya-Vostro-3400 kernel: [11374.753277] ieee80211 phy0: wl0: wlc_recv: dropping a frame with invalid src mac address, a2: e7:ff:dd:e4:e7:ff
Jul 16 22:27:09 sathya-Vostro-3400 kernel: [11374.905414] ieee80211 phy0: wl0: wlc_recv: dropping a frame with invalid src mac address, a2: e5:ff:da:e1:e5:ff
Jul 16 22:27:09 sathya-Vostro-3400 kernel: [11374.923346] ieee80211 phy0: wl0: wlc_recv: dropping a frame with invalid src mac address, a2: e9:ff:e1:e7:e9:ff
Jul 16 22:27:12 sathya-Vostro-3400 kernel: [11377.427090] ieee80211 phy0: wl0: wlc_recv: dropping a frame with invalid src mac address, a2: 00:00:00:00:00:00
Jul 16 22:27:18 sathya-Vostro-3400 kernel: [11383.589891] ieee80211 phy0: wl0: wlc_recv: dropping a frame with invalid src mac address, a2: 00:00:00:00:00:00


So does anyone have any suggestion on this? Thanks!


Offline
PostPosted: Tue Jul 17, 2012 6:37 pm Reply with quote
Site Admin Posts: 6496 Joined: Sat Nov 03, 2007 12:30 am
Hmm, there seems indeed to be a problem with the mode switch.

Please enable usb_modeswitch's logging as described on the main doc page, paragraph "Troubleshooting".


Offline
PostPosted: Wed Jul 18, 2012 4:33 pm Reply with quote
Posts: 16777215 Joined: Mon Jul 09, 2012 10:19 pm
Josh,

Thanks a lot for the reply. As suggested, I have enabled logging on Ubuntu 12.04 (on which it is not working). I have attached the log. Strangely, I found the log in the file, "/var/log/usb_modeswitch.log". The device name was not attached to the filename.

Let me know if you wish to see the log on Ubuntu 11.10 as well.

Xlearner

Quote:


USB_ModeSwitch log from Wed Jul 18 19:41:03 2012

Using global config file: /etc/usb_modeswitch.conf

Raw args from udev: 3-1/3-1:1.0

Using top device dir /sys/bus/usb/devices/3-1

USB dir exists: /sys/bus/usb/devices/3-1

SCSI dir exists: /sys/bus/usb/devices/3-1
Warning: SCSI attribute "vendor" not readable.
Warning: SCSI attribute "model" not readable.
Warning: SCSI attribute "rev" not readable.
----------------
USB values from sysfs:
idVendor 12d1
idProduct 1446
manufacturer HUAÿWEI TECHNOLOGIES
product HUAWEI Mobile
serial ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
bNumConfigurations 1
----------------
bNumConfigurations is 1 - don't check for active configuration
Found packed config collection /usr/share/usb_modeswitch/configPack.tar.gz
Searching entries named: /usr/share/usb_modeswitch/12d1:1446*
Searching overriding entries named: /etc/usb_modeswitch.d/12d1:1446*
SCSI attributes not needed, moving on.

Extracting config 12d1:1446 from collection /usr/share/usb_modeswitch/configPack.tar.gz
config: TargetVendor set to 12d1
config: TargetProduct set to 1001,1406,140b,140c,1412,141b,1433,1436,14ac,1506
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
! matched, now switching
Command to be run:
/usr/sbin/usb_modeswitch -I -W -D -s 20 -c /run/usb_modeswitch/current_cfg -u -1 -v 12d1 -p 1446 2>&1

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

Reading config file: /run/usb_modeswitch/current_cfg

* 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= 0x12d1
DefaultProduct= 0x1446
TargetVendor= 0x12d1
TargetProduct= not set
TargetClass= not set
TargetProductList="1001,1406,140b,140c,1412,141b,1433,1436,14ac,1506"

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

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


Looking for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
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:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
found matching product ID
adding device
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
Found device in default mode, class or configuration (1)
Accessing device 006 on bus 003 ...
Skipping the check for the current configuration
Using first interface: 0x00
Using endpoints 0x08 (out) and 0x87 (in)

USB description data (for identification)
-------------------------
Manufacturer: HUA?WEI TECHNOLOGIES
Product: HUAWEI Mobile
Serial No.: ???????????????????
-------------------------
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached
Setting up communication with interface 0
Using endpoint 0x08 for message sending ...
Trying to send message 1 to endpoint 0x08 ...
OK, message successfully sent
Resetting response endpoint 0x87
Resetting message endpoint 0x08

Checking for mode switch (max. 20 times, once per second) ...
Searching for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0003
searching devices, found USB ID 12d1:1446
found matching vendor ID
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 046d:c31c
searching devices, found USB ID 093a:2510
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 05ca:18c0
searching devices, found USB ID 08ff:168f
searching devices, found USB ID 8087:0024
searching devices, found USB ID 1d6b:0002
No new devices in target mode or class found

Mode switch has failed. Bye.

fail:
--------------------------------
(end of usb_modeswitch output)

USB dir exists: /sys/bus/usb/devices/3-1

All done, exiting



Offline
PostPosted: Wed Jul 18, 2012 5:16 pm Reply with quote
Site Admin Posts: 6496 Joined: Sat Nov 03, 2007 12:30 am
The switching sequence seems to be transmitted, but there is no mode switch. This is unusual.

Just for double checking, can you try to use the switching command manually? You need the file "12d1:1446" from the configuration collection, probably packed in /usr/share/usb_modeswitch.

Then run (as root or with sudo):
Code:
# /usr/sbin/usb_modeswitch -I -W -s 10 -c "<path-to>/12d1:1446" -v 12d1 -p 1446


Offline
PostPosted: Thu Jul 19, 2012 4:04 pm Reply with quote
Posts: 16777215 Joined: Mon Jul 09, 2012 10:19 pm
Dear Josh,

Thanks for the tip. Executing this command works wonderfully well :-)! This time it switched properly. I was able to connect to the net.

Only if I had messaged on this forum earlier, I could have saved so much time. Of course, it would be nice if this works automatically. Anyway, thanks a million!

Xlearner :-)!


Offline
PostPosted: Thu Jul 19, 2012 4:33 pm Reply with quote
Site Admin Posts: 6496 Joined: Sat Nov 03, 2007 12:30 am
Hmm, but this success is pointing to a possible problem in the Ubuntu package.

You should be able to replace the Ubuntu distribution package with either the latest Debian package or with an installation of the source package from this site. Both methods won't break anything, and you can always re-install Ubuntu's package.

Just uninstall your current package without checking for dependencies, as there may be a whole bunch of them.

The whole point of the package is to make things work automatically ...



Offline
PostPosted: Wed Jul 25, 2012 11:57 am Reply with quote
Posts: 16777215 Joined: Mon Jul 09, 2012 10:19 pm
Dear Josh,

Thanks for the response. I tried installing the debian package. But for some reason it failed. So for now I am content doing it manually. I will not complain if it does not work automatically.

But I certainly would like to raise a bug on this with Ubuntu. Any suggestions as to where I should do this?

Let me tell you about my observation on ubuntu 12.04. The folder, /usr/share/usb_modeswitch does not have any device file information. It has only one zipped file: configPack.tar.gz. I manually unzipped this file. And then I followed your command.

Thanks
Xlearner


Offline
PostPosted: Thu Jul 26, 2012 2:18 pm Reply with quote
Posts: 25 Joined: Thu Apr 07, 2011 8:37 am Website: http://freedune.wordpress.com
Hi Josh,

I too have been facing this issue with my Ubuntu 12.04 installation - I have to switch the modem manually every time, but I just wrote a little two-line bash script for it.

I just thought the problem must have been solved by now...

Another niggling issue that I (and others too, I guess) have is having to replug the modem every time there is a disconnection, which again requires a manual switch. Now this wouldn't be a big problem if the computer weren't connected to my TV, making me get up and WALK to it.


Offline
PostPosted: Thu Jul 26, 2012 5:25 pm Reply with quote
Site Admin Posts: 6496 Joined: Sat Nov 03, 2007 12:30 am
The right place to file a bug against Ubuntu is
https://bugs.launchpad.net/ubuntu/

But I strongly recommend to try the source package first. Otherwise it is not clear if the problem results from the Ubuntu changes.



Offline
PostPosted: Fri Jul 27, 2012 9:27 am Reply with quote
Posts: 16777215 Joined: Mon Jul 09, 2012 10:19 pm
Dear Josh,

I tried to compile as you have suggested. But I am getting the following fatal error:

Code:
$ sudo make install
gcc -o usb_modeswitch usb_modeswitch.c -Wall -l usb
usb_modeswitch.c:58:17: fatal error: usb.h: No such file or directory
compilation terminated.
make: *** [usb_modeswitch] Error 1


So it looks like it is not able to locate the usb.h file. Does this have something to do with libusb? I installed libusb through synaptic package manager. Any suggestions here? Thanks!

Xlearner


Offline
PostPosted: Fri Jul 27, 2012 10:07 am Reply with quote
Site Admin Posts: 6496 Joined: Sat Nov 03, 2007 12:30 am
Don't forget the "dev" package for libusb. It contains the header file "usb.h".


Offline
PostPosted: Fri Jul 27, 2012 11:51 am Reply with quote
Posts: 16777215 Joined: Mon Jul 09, 2012 10:19 pm
Josh,

After including the the dev package the code compiled without any problems. Now, the modem connects automatically as well :-) (after wating for a few mins since the device has been plugged in) ! Nothing better I can ask for :-))!

Thanks
Xlearner


Offline
PostPosted: Fri Jul 27, 2012 1:30 pm Reply with quote
Posts: 25 Joined: Thu Apr 07, 2011 8:37 am Website: http://freedune.wordpress.com
Hey this is good news! I will compile one myself tonight, and probably make it standard practice. I am not even sure if Ubuntu has been updating usb_modeswitch.

Josh, is having to replug the modem after disconnection expected behaviour on Linux, or is it an Ubuntu-only problem?


Offline
PostPosted: Fri Jul 27, 2012 6:40 pm Reply with quote
Site Admin Posts: 6496 Joined: Sat Nov 03, 2007 12:30 am
dune, this is not at all expected. I assume something is messing around with the device, and I suspect it's "modem-manager", the companion of "Network Manager", responsible for the "dirty work".

The problem is often that the Ubuntu/Gnome standard network software is trying to use advanced features of modems like signal strength display etc.

Unfortunately, the sheer multitude of modem models - and even firmware variants within the same family - makes it almost impossible to achieve this without device-specific information. So "modem-manager" is running lots of tests on the various interfaces/ports of a newly plugged modem; also, during connection the "Network Manager" attempts to get regular diagnosis updates from the device.

This all may or may not succeed - in the latter case often making the modem unresponsible ...

My advice is to use other and possibly more simple software if you run into trouble, like wvdial or others. While you are losing a bit of convenience and some features, you may gain a more reliable way of connecting (and disconnecting).



Offline

Display posts from previous:  Sort by:

All times are UTC+02:00
Page 1 of 1
14 posts
Users browsing this forum: No registered users and 1 guest
Search for:
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 post attachments in this forum