[Dirigible]

My Huawei E173 USB Modem was working in Sabayon 10 KDE 64bit until late January when an update to that distro broke something.

At the time I thought it could be something Sabayon specific which caused the problem, so I kept computing on my backup distro which is Mint 13 KDE 64bit. A few weeks later updates became available for Mint 13 as well, but I've been denying them for fear of losing connectivity there as well.

A couple of days ago I tried reinstalling Sabayon 11, Huawei E173 still won't work.
Tried installing Mint 14.1 Cinnamon 64bit alongside, Huawei E173 still won't work.

My problem seems not to be distro specific. Looks to be hardware specific.

Looking at the “40-usb_modeswitch.rules” file in all 3 distros and I can see additional references to the Huawei E173 Sab 11 and Mint 14. Something has changed in usb-modeswitch and it's preventing my Huawei E173 from functioning.

Some symptoms worth mentioning. If I try to connect in Sabayon it says “Setting the network address” and then after about 15 seconds it says connection failed or words to that effect. Here's the interesting bit... If I reboot to Mint 13 without a cold start it fails there in the same way. I have to power the modem down and up again (unplugging) before it will function properly. It is as if it was incorrectly initialised at powerup in Sabayon. Mint 14 has the same effect.

Wireless modem is my only means of connecting to the internet.
Can this be fixed?

[Josh]

Note that usb_modeswitch is only responsible for the mode change of 3G sticks.

For a working connection, there are several other components involved, like the kernel itself, "modem-manager" and of course the frontend "Network Manager"

To check if the mode switching is to blame, enable usb_modeswitch's logging as described on the main doc page, paragraph "Troubleshooting".

[Dirigible]

Hope someone here can interpret this stuff.

From Mint13 functional

Code: Select all

USB_ModeSwitch log from Mon Mar 11 11:47:01 2013

Using global config file: /etc/usb_modeswitch.conf

Raw args from udev: /1-8:1.0

Bus ID for device not given by udev.
 Trying to determine it from kernel name (1-8:1.0) ...
Using top device dir /sys/bus/usb/devices/1-8

USB dir exists: /sys/bus/usb/devices/1-8
Warning: USB attribute "serial" not readable.

SCSI dir exists: /sys/bus/usb/devices/1-8
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	1c0b
  manufacturer	HUAWEI
  product	HUAWEI Mobile
  serial	(null)
  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:1c0b*
Searching overriding entries named: /etc/usb_modeswitch.d/12d1:1c0b*
SCSI attributes not needed, moving on.

Extracting config 12d1:1c0b from collection /usr/share/usb_modeswitch/configPack.tar.gz
config: TargetVendor set to 12d1
config: TargetProduct set to 1c05,1c07,1c08
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 1c0b 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= 0x1c0b
TargetVendor=   0x12d1
TargetProduct=  not set
TargetClass=    not set
TargetProductList="1c05,1c07,1c08"

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:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 04e8:324c
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 12d1:1c0b
   found matching vendor ID
  searching devices, found USB ID 058f:6377
  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 04e8:324c
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 12d1:1c0b
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 058f:6377
  searching devices, found USB ID 1d6b:0002
 Found device in default mode, class or configuration (1)
Accessing device 004 on bus 001 ...
Skipping the check for the current configuration
Using first interface: 0x00
Using endpoints 0x0f (out) and 0x8f (in)

USB description data (for identification)
-------------------------
Manufacturer: HUAWEI
     Product: HUAWEI Mobile
  Serial No.: not provided
-------------------------
Looking for active driver ...
 OK, driver found ("usb-storage")
 OK, driver "usb-storage" detached
Setting up communication with interface 0
Using endpoint 0x0f for message sending ...
Trying to send message 1 to endpoint 0x0f ...
 OK, message successfully sent
Resetting response endpoint 0x8f
Resetting message endpoint 0x0f
 Could not reset endpoint (probably harmless): -71
 Device is gone, skipping any further commands

Checking for mode switch (max. 20 times, once per second) ...
 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 04e8:324c
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 058f:6377
  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 04e8:324c
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 058f:6377
  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 04e8:324c
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 058f:6377
  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 04e8:324c
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 058f:6377
  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 04e8:324c
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 058f:6377
  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 04e8:324c
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 12d1:1c05
   found matching vendor ID
   found matching product ID from list
  searching devices, found USB ID 058f:6377
  searching devices, found USB ID 1d6b:0002

Found target device, now opening

Found target device 005 on bus 001

Target device description data
-------------------------
Manufacturer: HUAWEI
     Product: HUAWEI Mobile
  Serial No.: not provided
-------------------------
 Found correct target device

Mode switch succeeded. Bye.

ok:12d1:1c05
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ... Reading attributes ...
USB dir exists: /sys/bus/usb/devices/1-8
Warning: USB attribute "serial" not readable.
 All attributes matched
Mode switching was successful, found 12d1:1c05 (HUAWEI: HUAWEI Mobile)Now checking for bound driver ...
 driver has bound, device is known
Checking for AVOID_RESET_QUIRK kernel attribute
 AVOID_RESET_QUIRK activated

All done, exiting

From Sab11 non-functional

Code: Select all

USB_ModeSwitch log from Mon Mar 11 22:02:29 EST 2013

Raw args from udev: /1-8:1.0

Using global config file: /etc/usb_modeswitch.conf
Using top device dir /sys/bus/usb/devices/1-8
Using interface 1.0
----------------
USB values from sysfs:
  manufacturer	HUAWEI
  product	HUAWEI Mobile
  serial	
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /usr/share/usb_modeswitch/12d1:1c0b
! matched. Reading config data
config: TargetVendor set to 12d1
config: TargetProductList set to 1c05,1c07,1c08,1c10
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1

Command to be run:
usb_modeswitch -W -D -s 20 -u -1 -b 1 -g 5 -v 12d1 -p 1c0b -f $configBuffer

Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
usb_set_debug: Setting debugging level to 15 (on)
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 005
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 001 on 003
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 005 on 001
usb_os_find_devices: Found 003 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device

Reading long config from command line

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

 ! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor=  0x12d1
DefaultProduct= 0x1c0b
TargetVendor=   0x12d1
TargetProduct=  not set
TargetClass=    not set
TargetProductList="1c05,1c07,1c08,1c10"

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


Use given bus/device number: 001/005 ...
Looking for default devices ...
 bus/device number matched
  searching devices, found USB ID 12d1:1c0b
   found matching vendor ID
   found matching product ID
   adding device
 Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x0f (out) and 0x8f (in)

USB description data (for identification)
-------------------------
Manufacturer: HUAWEI
     Product: HUAWEI Mobile
  Serial No.: not provided
-------------------------
Looking for active driver ...
 OK, driver found ("usb-storage")
 OK, driver "usb-storage" detached
Setting up communication with interface 0
Using endpoint 0x0f for message sending ...
Trying to send message 1 to endpoint 0x0f ...
USB error: could not clear/halt ep 15: Protocol error
USB error: could not release intf 0: No such device
 OK, message successfully sent
Resetting response endpoint 0x8f
Resetting message endpoint 0x0f
 Could not reset endpoint (probably harmless): -71
 Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.

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

Checking success of mode switch for max. 20 seconds ...
 Waiting for device file system (1 sec.) ...
 Waiting for device file system (2 sec.) ...
 Waiting for device file system (3 sec.) ...
 Waiting for device file system (4 sec.) ...
 Waiting for device file system (5 sec.) ...
 Reading attributes ...
 All attributes matched
Mode switching was successful, found 12d1:1c05 (HUAWEI: HUAWEI Mobile)
Logger is /usr/bin/logger
Now checking for bound driver ...
 driver has bound, device is known
Checking for AVOID_RESET_QUIRK kernel attribute
 AVOID_RESET_QUIRK activated

All done, exiting

Perhaps it would be easiest if I just bought a different make of usb modem?

[Josh]

The log shows that the mode switch works fine in both cases.

The bug must be somewhere else - as I said, there may be a problem with "modem-manager".

Either you follow through, report the problem (at Fedora), test the solution - or you use annother 3G stick. However you can't be sure that the problem will not affect your new modem as well ...