There are 2 usable configurations in 12d1:15c1, cfg#2 which is cdc_ether
and cfg#3 which is cdc_mbim , usb_modeswitch will select the linux
preferred mbim configuration if mbim drivers are present in the kernel.
This is by design and not a bug.
A user who prefers cdc_ether can disable the the
Does
echo on > /sys/bus/usb/devices/1-3/power/control
make any difference?
It will disable auto suspend for the port, power will always be on.
1-3 is the hub and port you had the dongle connected to
--
You received this bug notification because you are a member of Desktop
Packages, which is
@Gunnar Hjalmarsson:
Installing another version of usb-modeswitch will not solve the problem because
usb-modeswitch is not the problem.
usb-modeswitch does what it should do and that is switch the dongle from
19d2:1595 into 19d2:1592 and then leave the stage. Exit.
usb-modeswitch will do the
The around 50 seconds between each sequence matches very well the time it takes
for a Mobile Broadband device to become ready and start communicating with the
tower.
The overcurrent draw occurs when it at that time turns on its transmitter.
--
You received this bug notification because you are
I can't see any usb-modeswitch problem but your ZTE dongle does
repeatedly fall off the usb bus and moment later arriving again with its
initial id 19d2:1595 which usb_modeswitch immediately switches to
19d2:1592. This sequence is repeated through the whole log session:
09:49:38 19d2:1595
There is no SCSI attribute named ref but there is one named rev.
This is likely to be a typo from ubuntu rewrite of the original
usb_modeswitch_dispatcher.tcl which reads the rev attribute.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
As RussianNeuroMancer correctly pointed out the bug is in the concatenation of
the strings
MODULES_PATH, kversion, and CDC_MBIM_DRIVER_PATH into cdc_mbim_module_path.
The ending linefeed char in kversion is the culprit and it makes the dispatcher
unable to detect the presence of a cdc-mbim
usb_modeswitch did once upon a time check that a driver bound to the
dongles interface(s) and if not then it did a modeprobe of the option
serial driver. If it still didn't get option to bind then it added the
dongles usb id to option's new_id and if the driver bound then it asked
the user to
The lack of support for deviceid 12d1:1001 in the linux serial driver
option is not an usb_modeswitch bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1807678
Title:
usb_modeswitch 2.2.5 2015-07-17
usb_modeswitch 2.2.6 2015-11-01
usb_modeswitch 2.3.0 2016-01-13
usb_modeswitch 2.4.0 2016-06-13
usb_modeswitch 2.5.0 2017-01-17
usb_modeswitch 2.5.1 2017-08-06
z.
--
You received this bug notification because you are a member of Desktop
Packages,
usb_modeswitch is only responsible for switching a device or (as in this case)
select the config containing the cdc_mbim composition.
That's all usb_modeswitch does, what else needs to be done for bringing up the
connection is done by other programs.
--
You received this bug notification
>From the changelog:
20160112:
ATTENTION: requires usb-modeswitch version >= 2.3.0 due to new para-
meter OptionMode (further reducing config file space demand);
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in
Already fixed in usb-modeswitch-2.2.3 released 2015-07-03
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1435874
Title:
unrecognized option '--huawei-new-mode'
Status in
** Changed in: usb-modeswitch (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1416796
Title:
unable to run reliance 3G dongle
Status
Well, then upgrade your system to a version where your dongle is
supported, Ubuntu 14.10 or 15.04 supports it through usb_modeswitch
2.2.0 together with the 2014-05-29 datapackage.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
(In reply to marius from comment #1)
From the logs, it seems like there is some issue detecting/configuring the
network interface of the modem.
There is no network interface in the lsusb listing provided by the
reporter, there are 3 serial interfaces:
if#0 utps_modem
if#1 utps_pcui
if#2
Created attachment 108963
detailed interface description
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1057834
Title:
Haier CE81B is not detected on 12.04
Status in
@ Saurabh Sharma
Your E3531s is a new version, its 3 serial interfaces should be
supported by the option.ko driver in Mint17 but the direct ethernet
interface is not, it was added to net drivers two weeks ago so will be
supported from kernel 3.17.
Please do:
cat /proc/bus/usb/devices
and
@ Saurabh Sharma
12d1:1506 is a usb id for E3531s after it has been mode switched so
usb_modeswitch has done what it should do.
I think your problem is either linux driver related or NetworkManager related
so please provide the output from:
lsusb -v -d 12d1:1506
It will show how the interfaces
This may be a conflict with the storage driver, does it make any
difference if you remove the hashmark in front of the
#SetStorageDelay=4
line of /etc/usb_modeswitch.conf ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch
The lsusb listing shows that your dongle is supported by the option
driver in kernel 3.13 which Ubuntu 14.04 is built on.
The problem is most likely a usb controller driver error, can you please
test on a USB 2.0 port or with a USB 2.0 hub connected between dongle
and your computers USB 3.0 port.
Jul 3 23:44:31 usb_modeswitch: switch device 12d1:14fe on 003/005
usb_modeswitch has found the dongle in initial mode 12d1:14fe and has
switched it into modem mode
Jul 3 23:44:32 kernel: [19565.429763] usb 3-1: New USB device found,
idVendor=12d1, idProduct=1506
Jul 3 23:44:33
Please state which Ubuntu version, linux kernel version, and usb_modeswitch
version you are using and also the content of the udev popup message.
The usb_modeswitch.conf file is for global configs and should not be used for
individual device configuration, there should be a device config file
The kernel oops is btw from ModemManager and not from usb_modeswitch.
Make sure by checking the system log (after removing the faulty config in
usb_modeswitch.conf) that usb_modeswitch switches the dongle from 12d1:14fe to
12d1:1506 at every insert.
If it does, then assign the bug to
12d1:15ca is included in usb_modeswitch data package dated 20140529
which is dependent on usb_modeswitch executables ver 2.2.0 released at
the same time.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch-data in Ubuntu.
K3772, 12d1:1526 was added in usb_modeswitch data package dated 20121109
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch-data in Ubuntu.
https://bugs.launchpad.net/bugs/1066468
Title:
recent mobile broadband devices
It is 2 years since the DWM-156 was added to the usb_modeswitch data package
and this bug is still open?
There has been many updates since usb_modeswitch ver 1.23 and data package
2012-01-29, what is the Ubuntu developers definition of LTS?
--
You received this bug notification because you are
lspci or lsusb does not show any connected mobile broadband modem so
this can not be a usb_modeswitch problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch-data in Ubuntu.
https://bugs.launchpad.net/bugs/909682
Title:
This is not an usb_modeswitch problem, it is a usb core or hub driver problem.
It causes a device connect/disconnect/connect/disconnect loop not only for the
3G modem but also for the Samsung Android device:
[ 7387.580579] usb 2-3: USB disconnect, device number 6
[ 7387.860066] usb 2-3: new
usb_modeswitch has done all it should do , switched the dongle from initial
mode (cd-rom only) to modem mode ( usb id 12d1:1506 ).
The syslog clearly indicates a NetworkManager error so the bug report should go
there and mot be filed as a usb_modeswitch bug.
usb_modeswitch is not the
What bug? Please do a proper error report!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1322607
Title:
USB modesitch error
Status in “usb-modeswitch” package in Ubuntu:
Not a usb_modeswitch problem, 15eb:7153 has been in the usb_modeswitch data
package since Aug 2012.
dmesg shows a disconnect of device 6 (the hub) and device 8 (the 3G dongle
connected to that hub).
--
You received this bug notification because you are a member of Desktop
Packages, which is
E3531 with initial id 12d1:15e7 will be included in an update of
usb_modeswitch data package estimated to be released in 2nd half of May
2014.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
Can you please add a lsusb -v -d 0af0:d001 listing taken before switching the
device and also one for 0af0:d157 after switching.
What vid:pid do you get when trying to switch the device using the BAD
configpack ?
--
You received this bug notification because you are a member of Desktop
34 matches
Mail list logo
