Unix & Linux Stack Exchange
Q&A for users of Linux, FreeBSD and other Unix-like operating systems
Latest Questions
1
votes
0
answers
163
views
Trouble getting gammu to identify brovi LTE stick
I have a USB LTE modem "Brovi E3372-325". With that and a Raspberry Pi 4 (latest and fresh Raspbian OS bookworm) I want to use gammu to send and retrieve sms messages. LTE functuality is currently not needed. However, `gammu detect` seems not to recognize this modem. I followed Pavel's excellent gui...
I have a USB LTE modem "Brovi E3372-325". With that and a Raspberry Pi 4 (latest and fresh Raspbian OS bookworm) I want to use gammu to send and retrieve sms messages.
LTE functuality is currently not needed.
However,
gammu detect
seems not to recognize this modem.
I followed Pavel's excellent guide (https://blog.tanatos.org/posts/huawei_e3372h-325_brovi_with_linux_stickmode/) to switch the modem to stick mode.
Running mmcli -m 0
works and returns modem information, including information on the system:
System | device: /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2
| drivers: option, cdc_ncm
| plugin: generic
| primary port: ttyUSB1
| ports: ttyUSB1 (at), ttyUSB2 (ignored), ttyUSB4 (ignored),
| usb0 (net)
Running dmesg returns
[ 9.868002] usbcore: registered new interface driver option
[ 9.868043] usbserial: USB Serial support registered for GSM modem (1-port)
[ 9.869796] option 1-1.2:1.0: GSM modem (1-port) converter detected
[ 9.869994] option 1-1.2:1.1: GSM modem (1-port) converter detected
[ 9.870146] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB1
[ 9.870237] option 1-1.2:1.2: GSM modem (1-port) converter detected
[ 9.870348] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB2
[ 9.870435] option 1-1.2:1.3: GSM modem (1-port) converter detected
[ 9.870542] option 1-1.2:1.4: GSM modem (1-port) converter detected
[ 9.870647] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB4
[ 10.007369] cdc_ncm 1-1.2:1.5: MAC-Address: 5a:d0:6c:f4:22:67
[ 10.013166] cdc_ncm 1-1.2:1.5 usb0: register 'cdc_ncm' at usb-0000:01:00.0-1.2, CDC NCM (NO ZLP), 5a:d0:6c:f4:22:67
[ 10.013392] usbcore: registered new interface driver cdc_ncm
[ 10.021546] usbcore: registered new interface driver cdc_wdm
[ 10.031318] usbcore: registered new interface driver cdc_mbim
gammu-detect
lists ttyUSB1, ttyUSB2 and ttyUSB3, however running gammu identify
it results in timeouts regardless of the port.
I also set ttyUSB1 to be unmanaged by NetworkManager service, which did not help with my problem.
Also, I have firmware version 3.0.2.61 with no available update.
Is there anything else I can check or do?
Andreas
(131 rep)
Mar 5, 2024, 01:28 PM
• Last activity: May 10, 2025, 10:24 AM
2
votes
2
answers
2467
views
Trigger usb_modeswitch on boot for Huawei E3372 Modem
I am trying to make a Huawei Brovi E3372-325 USB LTE model work with a Raspberry Pi. Out of the box, it shows as a CDROM when plugging it in. (This is apparently used to automatically run the driver installation on Windows.) So far, I found [this post][1] with a udev rules configuration file. That e...
I am trying to make a Huawei Brovi E3372-325 USB LTE model work with a Raspberry Pi. Out of the box, it shows as a CDROM when plugging it in. (This is apparently used to automatically run the driver installation on Windows.)
So far, I found this post with a udev rules configuration file. That enables the modem when hotplugging it while the system is running by running usb_modeswitch. However, if the modem is plugged in on boot, it does not work, instead showing as a CD ROM.
Therefore, I am now trying to write a system service to run usb_modeswitch on boot. As a step towards that, I booted with the modem plugged in and then tried executing the usb_modeswitch commands from the configuration file manually. However, that does not have the intended effect.
The commands are
/sbin/usb_modeswitch -v 3566 -p 2001 -W -R -w 400
/sbin/usb_modeswitch -v 3566 -p 2001 -W -R
What do I need to do to make this work? Does the udev rules configuration trigger more actions that just the two listed commands? Or why do the seemingly same commands not have the same effect?
**Update**
Apparently, upon being powered on, the modem shows itself as a modem for a second, then switches to CDROM mode, but does not seem to accept commands switching it back to modem mode. The CDROM mode is intended for automatic driver installation in Windows. Though, that also means that when the driver is installed, the drive *can* be switched back to modem mode. So, it seems that usb_modeswitch and the Windows driver use different commands to switch to modem mode?
LiterallyCode
(21 rep)
Mar 4, 2024, 12:04 AM
• Last activity: Mar 8, 2024, 02:47 PM
1
votes
2
answers
3586
views
how to access Internet using modemmanager and not network-manager
I recently bought a tata docomo dongle. On inserting it I got the below details :- Aug 05 17:30:46 think-debian kernel: usb 1-2: new high-speed USB device number 5 using xhci_hcd Aug 05 17:30:46 think-debian kernel: usb 1-2: New USB device found, idVendor=12d1, idProduct=1f01 Aug 05 17:30:46 think-d...
I recently bought a tata docomo dongle.
On inserting it I got the below details :-
Aug 05 17:30:46 think-debian kernel: usb 1-2: new high-speed USB device number 5 using xhci_hcd
Aug 05 17:30:46 think-debian kernel: usb 1-2: New USB device found, idVendor=12d1, idProduct=1f01
Aug 05 17:30:46 think-debian kernel: usb 1-2: New USB device strings: Mfr=3, Product=2, SerialN
Aug 05 17:30:46 think-debian kernel: usb 1-2: Product: HUAWEI Mobile
Aug 05 17:30:46 think-debian kernel: usb 1-2: Manufacturer: Huawei Technologies
Aug 05 17:30:47 think-debian mtp-probe: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2"
Aug 05 17:30:47 think-debian mtp-probe: bus: 1, device: 5 was not an MTP device
Aug 05 17:30:47 think-debian systemd: Created slice system-usb_modeswitch.slice.
Aug 05 17:30:47 think-debian systemd: Starting USB_ModeSwitch__1-2:1.0...
Aug 05 17:30:47 think-debian laptop-mode: Laptop mode
Aug 05 17:30:47 think-debian laptop-mode: enabled, active
Aug 05 17:30:48 think-debian kernel: usb-storage 1-2:1.0: USB Mass Storage device detected
Aug 05 17:30:48 think-debian kernel: scsi host3: usb-storage 1-2:1.0
Aug 05 17:30:48 think-debian kernel: usbcore: registered new interface driver usb-storage
Aug 05 17:30:48 think-debian kernel: usbcore: registered new interface driver uas
Aug 05 17:30:48 think-debian usb_modeswitch: switch device 12d1:1f01 on 001/005
Aug 05 17:30:49 think-debian kernel: usb 1-2: USB disconnect, device number 5
Aug 05 17:30:58 think-debian kernel: usb 1-2: new high-speed USB device number 6 using xhci_hcd
Aug 05 17:30:58 think-debian kernel: usb 1-2: New USB device found, idVendor=12d1, idProduct=14db
Aug 05 17:30:58 think-debian kernel: usb 1-2: New USB device strings: Mfr=4, Product=3, SerialNumber=0
Aug 05 17:30:58 think-debian kernel: usb 1-2: Product: HUAWEI Mobile
Aug 05 17:30:58 think-debian kernel: usb 1-2: Manufacturer: Huawei Technologies
Aug 05 17:30:58 think-debian mtp-probe: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2"
Aug 05 17:30:58 think-debian mtp-probe: bus: 1, device: 6 was not an MTP device
Aug 05 17:30:58 think-debian laptop-mode: Laptop mode
Aug 05 17:30:58 think-debian laptop-mode: enabled, active
Aug 05 17:30:58 think-debian laptop-mode: Laptop mode
Aug 05 17:30:58 think-debian laptop-mode: enabled, active
Aug 05 17:30:58 think-debian kernel: cdc_ether 1-2:1.0 eth1: register 'cdc_ether' at usb-0000:00:14.0-2, CDC Ethernet Device, 00:a0:c6:09:5c:40
Aug 05 17:30:58 think-debian kernel: usbcore: registered new interface driver cdc_ether
Aug 05 17:30:58 think-debian kernel: cdc_ether 1-2:1.0 enx00a0c6095c40: renamed from eth1
Aug 05 17:30:58 think-debian root: usb_modeswitch: switched to 12d1:14db on 001/006
Aug 05 17:30:58 think-debian systemd: Started USB_ModeSwitch__1-2:1.0.
Aug 05 17:31:01 think-debian ModemManager: Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2': not supported by any plugin
Aug 05 17:32:24 think-debian kernel: usb 1-1: new low-speed USB device number 7 using xhci_hcd
Aug 05 17:32:24 think-debian kernel: usb 1-1: New USB device found, idVendor=192f, idProduct=0916
Aug 05 17:32:24 think-debian kernel: usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
Aug 05 17:32:24 think-debian kernel: usb 1-1: Product: USB Optical Mouse
Aug 05 17:32:24 think-debian kernel: usb 1-1: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
Aug 05 17:32:24 think-debian mtp-probe: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1"
Aug 05 17:32:24 think-debian mtp-probe: bus: 1, device: 7 was not an MTP device
Aug 05 17:32:24 think-debian laptop-mode: Laptop mode
Aug 05 17:32:24 think-debian laptop-mode: enabled, active
The same was confirmed via
lsusb
as well :-
Bus 003 Device 002: ID 8087:8000 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 04f2:b39a Chicony Electronics Co., Ltd
Bus 001 Device 003: ID 8087:07dc Intel Corp.
Bus 001 Device 002: ID 138a:0017 Validity Sensors, Inc.
Bus 001 Device 006: ID 12d1:1f01 Huawei Technologies Co., Ltd.
Bus 001 Device 005: ID 0781:5567 SanDisk Corp. Cruzer Blade
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Then I tried these two commands using https://askubuntu.com/questions/78164/configuring-tata-photon-usb-modem-huawei-ec156 as base. I am on Debian stretch ;-
sudo modprobe usbserial vendor=0x12d1 product=0x14db
sudo usb_modeswitch -v 0x12d1 -p 0x14db -H -W
The following is the output :-
Take all parameters from the command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 2.2.5 (C) Josua Dietze 2015
* Based on libusb1/libusbx
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x12d1
DefaultProduct= 0x14db
HuaweiMode=1
NeedResponse=0
ifconfig -a
gives :-
xxxxxxxxxx Link encap:Ethernet HWaddr xx:xx:xx:xx:xx
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:20 Memory:e0600000-e0620000
eth0:avahi Link encap:Ethernet HWaddr xx:xx:xx:xx:xx
inet addr:169.254.7.244 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:20 Memory:e0600000-e0620000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:468 errors:0 dropped:0 overruns:0 frame:0
TX packets:468 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:44602 (43.5 KiB) TX bytes:44602 (43.5 KiB)
wlan0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
The first one in ifconfig -a
is the usb dongle which I have shared as *xxxxxxx*.
This is the latest I could get via sudo journalctl -f
Aug 07 12:17:06 think-debian kernel: usb 1-1: new high-speed USB device number 11 using xhci_hcd
Aug 07 12:17:06 think-debian kernel: usb 1-1: New USB device found, idVendor=12d1, idProduct=1f01
Aug 07 12:17:06 think-debian kernel: usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=0
Aug 07 12:17:06 think-debian kernel: usb 1-1: Product: HUAWEI Mobile
Aug 07 12:17:06 think-debian kernel: usb 1-1: Manufacturer: Huawei Technologies
Aug 07 12:17:06 think-debian kernel: usb-storage 1-1:1.0: USB Mass Storage device detected
Aug 07 12:17:06 think-debian kernel: scsi host6: usb-storage 1-1:1.0
Aug 07 12:17:06 think-debian mtp-probe: checking bus 1, device 11: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1"
Aug 07 12:17:06 think-debian mtp-probe: bus: 1, device: 11 was not an MTP device
Aug 07 12:17:06 think-debian systemd: Starting USB_ModeSwitch__1-1:1.0...
Aug 07 12:17:07 think-debian usb_modeswitch: switch device 12d1:1f01 on 001/011
Aug 07 12:17:08 think-debian kernel: usb 1-1: USB disconnect, device number 11
Aug 07 12:17:16 think-debian kernel: usb 1-1: new high-speed USB device number 12 using xhci_hcd
Aug 07 12:17:16 think-debian kernel: usb 1-1: New USB device found, idVendor=12d1, idProduct=14db
Aug 07 12:17:16 think-debian kernel: usb 1-1: New USB device strings: Mfr=4, Product=3, SerialNumber=0
Aug 07 12:17:16 think-debian kernel: usb 1-1: Product: HUAWEI Mobile
Aug 07 12:17:16 think-debian kernel: usb 1-1: Manufacturer: Huawei Technologies
Aug 07 12:17:16 think-debian kernel: cdc_ether 1-1:1.0 eth1: register 'cdc_ether' at usb-0000:00:14.0-1, CDC Ethernet Device, xx:xx:xx:xx:xx
Aug 07 12:17:16 think-debian mtp-probe: checking bus 1, device 12: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1"
Aug 07 12:17:16 think-debian mtp-probe: bus: 1, device: 12 was not an MTP device
Aug 07 12:17:16 think-debian kernel: cdc_ether 1-1:1.0 xxxxxxxxx: renamed from eth1
Aug 07 12:17:17 think-debian root: usb_modeswitch: switched to 12d1:14db on 001/012
Aug 07 12:17:17 think-debian systemd: Started USB_ModeSwitch__1-1:1.0.
Aug 07 12:17:19 think-debian ModemManager: Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1': not supported by any plugin
It seems to need something with modem-manager. Any help ?
This is my /etc/network/interfaces
output :-
$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
auto eth0
allow-hotplug eth0
iface eth0 inet dhcp
so eth0 is already given/occupied for the wired interface.
route
gives this :-
$ sudo route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default * 0.0.0.0 U 1002 0 0 eth0
link-local * 255.255.0.0 U 0 0 0 eth0
Update - I updated usbids and now the listing is far better than before :-
$ lsusb
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 04f2:b39a Chicony Electronics Co., Ltd
Bus 002 Device 003: ID 8087:07dc Intel Corp.
Bus 002 Device 002: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
Bus 002 Device 009: ID 192f:0916 Avago Technologies, Pte.
Bus 002 Device 007: ID 12d1:14db Huawei Technologies Co., Ltd. E353/E3131
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
For now I am using network-manager, but I would like modemmanager to do the needed changes.
shirish
(12954 rep)
Aug 7, 2015, 07:12 AM
• Last activity: Feb 3, 2024, 05:38 AM
0
votes
5
answers
10474
views
USB LTE modem "Brovi E3372-325" not working
I have problem new USB LTE modem [Brovi E3372-325][1] I can't get it to work on linux. When connected to a USB port, the modem identifies itself as: ``` # dmesg ... [ 6731.401923] usb 1-3.4.4: new high-speed USB device number 22 using xhci_hcd [ 6731.503252] usb 1-3.4.4: New USB device found, idVend...
I have problem new USB LTE modem Brovi E3372-325
I can't get it to work on linux. When connected to a USB port, the modem identifies itself as:
# dmesg
...
[ 6731.401923] usb 1-3.4.4: new high-speed USB device number 22 using xhci_hcd
[ 6731.503252] usb 1-3.4.4: New USB device found, idVendor=3566, idProduct=2001, bcdDevice=ff.ff
[ 6731.503261] usb 1-3.4.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 6731.503265] usb 1-3.4.4: Product: Mobile
[ 6731.503268] usb 1-3.4.4: Manufacturer: Mobile
[ 6731.503271] usb 1-3.4.4: SerialNumber: 123456789ABCD
[ 6731.505527] usb-storage 1-3.4.4:1.0: USB Mass Storage device detected
[ 6731.505830] scsi host1: usb-storage 1-3.4.4:1.0
[ 6732.534864] scsi 1:0:0:0: CD-ROM Linux File-Stor Gadget 0310 PQ: 0 ANSI: 2
[ 6732.535947] sr 1:0:0:0: Power-on or device reset occurred
[ 6732.536717] sr 1:0:0:0: [sr0] scsi3-mmc drive: 0x/0x caddy
[ 6732.540429] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 6732.540983] sr 1:0:0:0: Attached scsi generic sg1 type 5
[ 6732.803382] ISO 9660 Extensions: RRIP_1991A
# lsusb -vvv
...
Bus 001 Device 028: ID 3566:2001 Mobile Mobile
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x3566
idProduct 0x2001
bcdDevice ff.ff
iManufacturer 2 Mobile
iProduct 3 Mobile
iSerial 4 123456789ABCD
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0020
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 1 Mass Storage
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 0x0016
bNumDeviceCaps 2
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000000
(Missing must-be-set LPM bit!)
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x00
wSpeedsSupported 0x0004
Device can operate at High Speed (480Mbps)
bFunctionalitySupport 4
Lowest fully-functional device speed is at an unknown speed!
bU1DevExitLat 1 micro seconds
bU2DevExitLat 500 micro seconds
Device Status: 0x0000
(Bus Powered)
now I switch them to "modem": usb_modeswitch -v 3566 -p 2001 -X
:
# dmesg
...
[ 6971.308148] usb 1-3.4.4: USB disconnect, device number 22
[ 6971.544052] usb 1-3.4.4: new high-speed USB device number 23 using xhci_hcd
[ 6971.645772] usb 1-3.4.4: New USB device found, idVendor=3566, idProduct=2001, bcdDevice=ff.ff
[ 6971.645787] usb 1-3.4.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 6971.645794] usb 1-3.4.4: Product: Mobile
[ 6971.645799] usb 1-3.4.4: Manufacturer: Mobile
[ 6971.645804] usb 1-3.4.4: SerialNumber: 123456789ABCD
[ 6971.647121] usb 1-3.4.4: Interface #0 referenced by multiple IADs
[ 6971.647643] usb 1-3.4.4: Interface #1 referenced by multiple IADs
[ 6971.678702] cdc_ncm 1-3.4.4:1.5: MAC-Address: c2:ab:11:ee:2f:15
[ 6971.679449] cdc_ncm 1-3.4.4:1.5 usb0: register 'cdc_ncm' at usb-0000:00:14.0-3.4.4, CDC NCM, c2:ab:11:ee:2f:15
[ 6971.743416] cdc_ncm 1-3.4.4:1.5 enxc2ab11ee2f15: renamed from usb0
# ip a s enxc2ab11ee2f15
14: enxc2ab11ee2f15: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether c2:ab:11:ee:2f:15 brd ff:ff:ff:ff:ff:ff
# mmcli -L
No modems were found
# lsusb -vvv
Bus 001 Device 029: ID 3566:2001 Mobile Mobile
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x3566
idProduct 0x2001
bcdDevice ff.ff
iManufacturer 2 Mobile
iProduct 3 Mobile
iSerial 4 123456789ABCD
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x00f9
bNumInterfaces 7
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 2mA
Interface Association:
bLength 8
bDescriptorType 11
bFirstInterface 0
bInterfaceCount 2
bFunctionClass 2 Communications
bFunctionSubClass 2 Abstract (modem)
bFunctionProtocol 1 AT-commands (v.25ter)
iFunction 10 CDC Serial
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 8 CDC Abstract Control Model (ACM)
** UNRECOGNIZED: 05 24 00 10 01
** UNRECOGNIZED: 05 24 01 00 01
** UNRECOGNIZED: 04 24 02 02
** UNRECOGNIZED: 05 24 06 00 01
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x000a 1x 10 bytes
bInterval 9
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 9 CDC ACM Data
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 11 Marvell DIAG
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Association:
bLength 8
bDescriptorType 11
bFirstInterface 3
bInterfaceCount 2
bFunctionClass 2 Communications
bFunctionSubClass 2 Abstract (modem)
bFunctionProtocol 1 AT-commands (v.25ter)
iFunction 14 CDC Serial
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 12 CDC Abstract Control Model (ACM)
** UNRECOGNIZED: 05 24 00 10 01
** UNRECOGNIZED: 05 24 01 00 04
** UNRECOGNIZED: 04 24 02 02
** UNRECOGNIZED: 05 24 06 03 04
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x000a 1x 10 bytes
bInterval 9
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 4
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 13 CDC ACM Data
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Association:
bLength 8
bDescriptorType 11
bFirstInterface 0
bInterfaceCount 2
bFunctionClass 2 Communications
bFunctionSubClass 13
bFunctionProtocol 0
iFunction 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 5
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 13
bInterfaceProtocol 0
iInterface 0
CDC Header:
bcdCDC 1.10
CDC Union:
bMasterInterface 5
bSlaveInterface 6
CDC Ethernet:
iMacAddress 17 FE1EA1E4D9D7
bmEthernetStatistics 0x00000000
wMaxSegmentSize 1514
wNumberMCFilters 0x0000
bNumberPowerFilters 0
CDC NCM:
bcdNcmVersion 1.00
bmNetworkCapabilities 0x01
packet filter
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x88 EP 8 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 9
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 6
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0
bInterfaceProtocol 1
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 6
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x87 EP 7 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x05 EP 5 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 0x0016
bNumDeviceCaps 2
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000000
(Missing must-be-set LPM bit!)
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x00
wSpeedsSupported 0x0004
Device can operate at High Speed (480Mbps)
bFunctionalitySupport 4
Lowest fully-functional device speed is at an unknown speed!
bU1DevExitLat 1 micro seconds
bU2DevExitLat 500 micro seconds
Device Status: 0x0000
(Bus Powered)
But there is missing /dev
interface (something like /dev/cdc*
//dev/ttyUSB*
).
Tested on Ubuntu 22.04 with kernel 5.15 and Ubuntu 23.04 (daily build) with kernel 5.19. Without success.
I tried dhclient enxc2ab11ee2f15
, ip link enxc2ab11ee2f15 up
- without success.
For qmicli
/mbimcli
there is missing /dev/cdc*
interface.
On Windows 10 PC it connects automatically and gets IP from DHCP. It uses RNDIS driver.
Can you please help me? How can I switch modem to the right mode?
martin
(111 rep)
Feb 1, 2023, 04:32 PM
• Last activity: Jan 18, 2024, 02:53 PM
0
votes
1
answers
349
views
Vodafone E3730 unable to usb_modeswitch
### tl;dr Vodafone E3730 HSPA Express Data Card seems not to work at all in Kubuntu 18.04 LTS. How can I fix this? --- ### Description The card used to work. Frankly I don't remember if it worked in 18.04 LTS or in some earlier LTS version, but it did. In my current KDE Plasma in 18.04 LTS there are...
### tl;dr
Vodafone E3730 HSPA Express Data Card seems not to work at all in Kubuntu 18.04 LTS. How can I fix this?
---
### Description
The card used to work. Frankly I don't remember if it worked in 18.04 LTS or in some earlier LTS version, but it did. In my current KDE Plasma in 18.04 LTS there are saved network settings that used to work. I expected them to kick in as soon as I insert the card but no; it's as if the card isn't there.
The SIM card was never removed and it should still work.
From the time it worked I remember no problems whatsoever. It probably worked almost out of the box. The hardware was recognized and I only had to set details like APN.
---
### Technical details
This information is printed on a sticker:
> Vodafone Mobile Connect
> Model: E3730
> HSPA Express Data Card
>
> Designed in E.U. by Option
> Made in Ireland by Option
> QUALCOMM 3G CDMA
This is from
lsusb
:
Bus 001 Device 006: ID 0af0:7301 Option
And this is from usb-devices
:
T: Bus=01 Lev=02 Prnt=02 Port=01 Cnt=02 Dev#= 6 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0af0 ProdID=7301 Rev=00.00
S: Manufacturer=Option N.V.
S: Product=Globetrotter HSUPA Modem
S: SerialNumber=Serial Number
C: #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
cat /etc/issue
:
Ubuntu 18.04.5 LTS \n \l
uname -a
:
Linux whatever 4.15.0-121-generic #123-Ubuntu SMP Mon Oct 5 16:16:40 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
---
### Research
It seems the right driver for the device is option
.
I learnt what usb_modeswitch
is:
> Several new USB devices have their proprietary Windows drivers onboard, most of them WWAN and WLAN dongles. When plugged in for the first time, they act like a flash storage and start installing the Windows driver from there. If the driver is installed, it makes the storage device disappear and a new device, mainly composite (e.g. with modem ports), shows up.
>
> On Linux, in most cases the drivers are available as kernel modules, such as usbserial
or option
. However, the device initially binds to usb-storage
by default. usb_modeswitch
can then send a provided bulk message (most likely a mass storage command) to the device; this message has to be determined by analyzing the actions of the Windows driver.
I confirmed the packages usb-modeswitch
and usb-modeswitch-data
are installed. I believe they should work automatically. At least they seemingly used to work when my card used to work, without me knowing anything about usb_modeswitch
.
I noticed the device does not even act like a flash storage. In the output of usb-devices
(above) it states Cls=08(stor.)
, which I believe indicates Base Class 08h (Mass Storage) ; but the driver is none
. No block device appears.
Then I found this answer and tried to adjust it to my hardware.
At first I created an empty file named 0af0:7301
in /etc/usb_modeswitch.d/
. I removed and re-inserted the device. Then usb-device
gave me this:
T: Bus=01 Lev=02 Prnt=02 Port=01 Cnt=02 Dev#= 7 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0af0 ProdID=7301 Rev=00.00
S: Manufacturer=Option N.V.
S: Product=Globetrotter HSUPA Modem
S: SerialNumber=Serial Number
C: #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
The driver was usb-storage
and I could actually mount a newly created block device (/dev/sr0
in my case) and see it contains a Windows driver. I think the empty file had prevented usb_modeswitch
from doing anything to the device.
Next I tried to run usb_modeswitch
manually:
sudo usb_modeswitch -v 0x0af0 -p 0x7301 --option-mode
# or
sudo usb_modeswitch -v 0x0af0 -p 0x7301 --option-mode -C 0xff
Any of the above commands printed output suggesting it worked, but the only change in the output of usb-device
was in this line:
I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
This is what I had seen before I started to mess with usb_modeswitch
. It seems I managed to manually recreate what usb_modeswitch
had been doing automatically. My interpretation is the tool works only partially: it is able to remove the driver (usb-storage
changes to none
) but it doesn't switch the mode (08(stor.)
remains).
---
### Question
How to proceed from here? How can I make the modem work?
Kamil Maciorowski
(24294 rep)
Nov 30, 2020, 10:36 AM
• Last activity: May 8, 2023, 04:33 PM
2
votes
1
answers
2705
views
Use Huawei E8231 as a 3g modem
I'm using Gentoo, and I have a problem with the 3g modem Huawei E8231. As far as I understand, to make it work I should switch its mode: $ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0...
I'm using Gentoo, and I have a problem with the 3g modem Huawei E8231. As far as I understand, to make it work I should switch its mode:
$ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 8087:07dc Intel Corp.
Bus 001 Device 004: ID 0bda:572a Realtek Semiconductor Corp.
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 011: ID 12d1:1f01 Huawei Technologies Co., Ltd. E353/E3131 (Mass storage mode)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
# usb_modeswitch -v 12d1 -V 12d1 -p 1f01 -P 14db -M "55534243123456780000000000000011062000000101000100000000000000"
$ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 8087:07dc Intel Corp.
Bus 001 Device 004: ID 0bda:572a Realtek Semiconductor Corp.
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 012: ID 12d1:14db Huawei Technologies Co., Ltd. E353/E3131
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
# dmesg
[19469.255798] usb 1-3: new high-speed USB device number 11 using xhci_hcd
[19469.396894] usb 1-3: New USB device found, idVendor=12d1, idProduct=1f01
[19469.396898] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[19469.396900] usb 1-3: Product: HUAWEI Mobile
[19469.396901] usb 1-3: Manufacturer: HUAWEI
[19469.396903] usb 1-3: SerialNumber: FFFFFFFFFFFFFFFF
[19469.397809] usb-storage 1-3:1.0: USB Mass Storage device detected
[19469.397868] scsi host5: usb-storage 1-3:1.0
[19470.397691] scsi 5:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2
[19470.470961] sr 5:0:0:0: [sr0] scsi-1 drive
[19470.471189] sr 5:0:0:0: Attached scsi CD-ROM sr0
[19470.471320] sr 5:0:0:0: Attached scsi generic sg1 type 5
[19591.778652] usb 1-3: USB disconnect, device number 11
[19592.095020] usb 1-3: new high-speed USB device number 12 using xhci_hcd
[19592.238652] usb 1-3: New USB device found, idVendor=12d1, idProduct=14db
[19592.238655] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[19592.238658] usb 1-3: Product: HUAWEI Mobile
[19592.238659] usb 1-3: Manufacturer: HUAWEI
[19592.311677] cdc_ether 1-3:1.0 eth1: register 'cdc_ether' at usb-0000:00:14.0-3, CDC Ethernet Device, 00:1e:10:1f:00:00
# usb-devices
T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 12 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=02(commc) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=12d1 ProdID=14db Rev=01.02
S: Manufacturer=HUAWEI
S: Product=HUAWEI Mobile
C: #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=06 Prot=00 Driver=cdc_ether
I: If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_ether
It seems that everything is ok, but there aren't any new devices or interfaces:
$ ls /dev | grep ttyUSB #empty result
$ ifconfig #no usb0
eth0: flags=4099 mtu 1500
ether c4:54:44:b2:ca:45 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73 mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 0 (Local Loopback)
RX packets 9445 bytes 5167034 (4.9 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 9445 bytes 5167034 (4.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163 mtu 1500
inet 192.168.0.100 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::fa16:54ff:fe6e:2940 prefixlen 64 scopeid 0x20
ether f8:16:54:6e:29:40 txqueuelen 1000 (Ethernet)
RX packets 875123 bytes 1243972975 (1.1 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 391840 bytes 42394343 (40.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Wat's wrong?
*note: I also asked this question on gentoo forum *
erthalion
(323 rep)
Oct 25, 2015, 05:08 PM
• Last activity: Apr 29, 2019, 08:58 AM
1
votes
0
answers
354
views
How to switch Huawei CDMA 2252+ to USB from CD-ROM?
I have Huawei CDMA 2252+ phone and I want to connect it to Linux to send SMS. In Fedora 15 (64bit) it is taken as CD-ROM. This is the output of `dmesg` after the phone is plugged in. [10887.524339] USB Mass Storage support registered. [10888.614507] scsi 3:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ:...
I have Huawei CDMA 2252+ phone and I want to connect it to Linux to send SMS. In Fedora 15 (64bit) it is taken as CD-ROM. This is the output of
dmesg
after the phone is plugged in.
[10887.524339] USB Mass Storage support registered.
[10888.614507] scsi 3:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2
[10888.786098] sr1: scsi-1 drive
[10888.788583] sr 3:0:0:0: Attached scsi CD-ROM sr1
[10888.788904] sr 3:0:0:0: Attached scsi generic sg2 type 5
[10899.106066] sr1: CDROM (ioctl) error, command: Xpwrite, Read disk info 51 00 00 00 00 00 00 00 02 00
[10899.106073] sr: Sense Key : Hardware Error [current]
[10899.106075] sr: Add. Sense: No additional sense information
This is the output of lsusb
:
Bus 002 Device 004: ID 12d1:1010 Huawei Technologies Co., Ltd.
Then I tried to use usb_modeswitch
to change the device to USB as following. (My device is not in the usb_modewitch
supported device list.)
The output of usb_modeswitch --verbose -H -v 0x12d1 -p 0x1010
:
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.1.6 (C) Josua Dietze 2010
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x12d1
DefaultProduct= 0x1010
TargetVendor= not set
TargetProduct= not set
TargetClass= not set
TargetProductList=""
DetachStorageOnly=0
HuaweiMode=1
SierraMode=0
SonyMode=0
GCTMode=0
KobilMode=0
MessageEndpoint= not set
MessageContent=""
NeedResponse=0
ResponseEndpoint= not set
Interface=0x00
InquireDevice enabled (default)
Success check disabled
System integration mode disabled
Looking for default devices ...
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 12d1:1010
found matching vendor ID
found matching product ID
adding device
searching devices, found USB ID 0e0f:0003
searching devices, found USB ID 0e0f:0002
Found devices in default mode, class or configuration (1)
Accessing device 005 on bus 002 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using endpoints 0x0b (out) and 0x8a (in)
Using endpoints 0x0b (out) and 0x8a (in)
Not a storage device, skipping SCSI inquiry
USB description data (for identification)
-------------------------
Manufacturer: Huawei, Incorporated
Product: Huawei Technologies
Serial No.: not provided
-------------------------
Sending Huawei control message ...
OK, Huawei control message sent
-> Run lsusb to note any changes. Bye.
After this I ran the lsusb
and I did not notice any changes. However following are notified in dmesg
:
[ 180.438107] usb 2-2.1: USB disconnect, address 4
[ 199.385604] usb 2-2.1: new full speed USB device using uhci_hcd and address 5
[ 199.648757] usb 2-2.1: New USB device found, idVendor=12d1, idProduct=1010
[ 199.648759] usb 2-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 199.648761] usb 2-2.1: Product: Huawei Technologies
[ 199.648762] usb 2-2.1: Manufacturer: Huawei, Incorporated
The following is taken from /var/log/messages
.
kernel: [ 180.438107] usb 2-2.1: USB disconnect, address 4
kernel: [ 199.385604] usb 2-2.1: new full speed USB device using uhci_hcd and address 5
kernel: [ 199.648757] usb 2-2.1: New USB device found, idVendor=12d1, idProduct=1010
kernel: [ 199.648759] usb 2-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
kernel: [ 199.648761] usb 2-2.1: Product: Huawei Technologies
kernel: [ 199.648762] usb 2-2.1: Manufacturer: Huawei, Incorporated
mtp-probe: checking bus 2, device 5: "/sys/devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2/2-2/2-2.1"
mtp-probe: bus: 2, device: 5 was not an MTP device
I'm not sure whether I have successfully switched the phone from CD-ROM to USB. Is there any way to confirm this? I don't have any ttyUSB
file under /dev
folder. How to find which file corresponds to the above device? Further, I want to send AT commands to the phone. How to do that?
Viraj
(115 rep)
Oct 24, 2015, 11:38 AM
• Last activity: Sep 27, 2016, 01:50 PM
Showing page 1 of 7 total questions