Huawei EC1260 USB modem is not detected in Ubuntu 13.04
I recently purchased a Huawei EC1260 USB modem sold by MTS India. On plugging it to my laptop, it was detected initially. I was told that activation of the modem would take at least 24 hrs. Even after activation, the modem wouldn't connect to the internet. I was told that, the modem contains the relevant installation files and upon plugging for the first time, it would mount as a disk drive. All I could find was two ".drive" icons which wouldn't mount. Hence I plugged the modem into a windows machine, copied the entire visible content onto a pen drive and then onto my laptop. I tried to install the driver through the "install" file present in the copied content which resulted in error messages that go like "FATAL: Module hw_cdc_driver not found." "Error: could not remove module cdc_ether: No such file or directory", "libkmod: ERROR ../libkmod/
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- Vanamali
- Solved:
- Last query:
- Last reply:
Revision history for this message
|
#1 |
vanamali@Shastry:~$ lsusb
Bus 002 Device 003: ID 174f:5216 Syntek
Bus 006 Device 004: ID 12d1:140b Huawei Technologies Co., Ltd. EC1260 Wireless Data Modem HSD USB Card
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
vanamali@Shastry:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 13.04
Release: 13.04
Codename: raring
vanamali@Shastry:~$ uname -a
Linux Shastry 3.8.0-29-generic #42-Ubuntu SMP Tue Aug 13 23:12:18 UTC 2013 i686 i686 i686 GNU/Linux
Revision history for this message
|
#2 |
Please try the solution procedure by Anisur R Mullick (anisur-mullick) at the end of the following thread:
https:/
Revision history for this message
|
#3 |
Thank you for the response. I tried the link you provided. I encountered an
error at step 3 - the folder /etc/usb_
do.
On Sep 4, 2013 7:41 PM, "Mark Rijckenberg" <
<email address hidden>> wrote:
> Your question #235153 on gnome-nettool in Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Mark Rijckenberg proposed the following answer:
> Please try the solution procedure by Anisur R Mullick (anisur-mullick)
> at the end of the following thread:
>
> https:/
> nettool/
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
>
Revision history for this message
|
#4 |
I tried to configure through wvdial and got the following output:
vanamali@Shastry:~$ sudo wvdialconf
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
Modem Port Scan<*1>: S0 S1 S2 S3 S4 S5 S6 S7
Modem Port Scan<*1>: S8 S9 S10 S11 S12 S13 S14 S15
Modem Port Scan<*1>: S16 S17 S18 S19 S20 S21 S22 S23
Modem Port Scan<*1>: S24 S25 S26 S27 S28 S29 S30 S31
ttyUSB_
ttyUSB_
ttyUSB_
ttyUSB_
ttyUSB_
ttyUSB_
ttyUSB_
ttyUSB_
ttyUSB_
ttyUSB_
ttyUSB_
ttyUSB_
ttyUSB_
ttyUSB_
ttyUSB_
ttyUSB_
ttyUSB_
ttyUSB_
ttyUSB_
ttyUSB_
ttyUSB_
ttyUSB_
ttyUSB_
Found a modem on /dev/ttyUSB_
Modem configuration written to /etc/wvdial.conf.
ttyUSB_
ttyUSB_
Upon issuing 'sudo wvdial' , I get the following output:
vanamali@Shastry:~$ sudo wvdial
--> WvDial: Internet dialer version 1.61
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT#777
--> Waiting for carrier.
ATDT#777
CONNECT 3100000
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Wed Sep 4 20:40:03 2013
--> Pid of pppd: 4427
--> Using interface ppp0
--> pppd: �I� [10]I�
--> pppd: �I� [10]I�
--> pppd: �I� [10]I�
--> pppd: �I� [10]I�
--> pppd: �I� [10]I�
--> Disconnecting at Wed Sep 4 20:40:33 2013
--> The PPP daemon has died: A modem hung up the phone (exit code = 16)
--> man pppd explains pppd error codes in more detail.
--> Try again and look into /var/log/messages and the wvdial and pppd man pages for more information.
--> Auto Reconnect will be attempted in 5 seconds
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
^CCaught signal 2: Attempting to exit gracefully...
--> Disconnecting at Wed Sep 4 20:40:37 2013
I tried to check '/var/log/messages' and found nothing by the name 'messages' in the directory '/var/log/'
Revision history for this message
|
#5 |
The output of the installation process (which I had mentioned in the question) is as follows:
vanamali@
DRIVER COPY START
STA_PATH_FLAG=.
STA_PATH_
START_PATH_
CURRENT install from ./install
INSTALL_PATH is not set ,auto install
INSTALL_
INSTALL_PATH is another path
rm /usr/local/
DRIVER COPY END
have usb_modeswitch rules to HUAWEI DataCard: COUNT=0
ls: cannot access /dev/ttyUSB?: No such file or directory
ttyUSB%n not exist,ok
libkmod: ERROR ../libkmod/
Error: could not remove module cdc_ether: No such file or directory
libkmod: ERROR ../libkmod/
Error: could not remove module usbnet: No such file or directory
libkmod: ERROR ../libkmod/
Error: could not remove module hw_cdc_driver: No such file or directory
make -C src/ clean
make[1]: Entering directory `/usr/local/
rm -rf *.o *.ko *~ core* .dep* .*.d .*.cmd *.mod.c *.a *.s .*.flags .tmp_versions Module.symvers Modules.symvers *.order
/usr/local/
rmmod -f hw_cdc_driver
libkmod: ERROR ../libkmod/
Error: could not remove module hw_cdc_driver: No such file or directory
make[1]: *** [clean] Error 1
make[1]: Leaving directory `/usr/local/
make: *** [clean] Error 2
make -C src/ modules
make[1]: Entering directory `/usr/local/
#/usr/local/
make -C /lib/modules/
make[2]: Entering directory `/usr/src/
CC [M] /usr/local/
/usr/local/
/usr/local/
cc1: some warnings being treated as errors
make[3]: *** [/usr/local/
make[2]: *** [_module_
make[2]: Leaving directory `/usr/src/
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/local/
make: *** [modules] Error 2
make -C src/ install
make[1]: Entering directory `/usr/local/
#install -m 744 -c hw_cdc_driver.o /lib/modules/
#depmod -a
#modprobe hw_cdc_driver
/usr/local/
modprobe hw_cdc_driver
FATAL: Module hw_cdc_driver not found.
make[1]: *** [install] Error 1
make[1]: Leaving directory `/usr/local/
make: *** [install] Error 2
Install NDIS driver failed.
The compiling environment is not all ready.
Please check gcc, make and kernel buid(/lib/
Now please enter any key to finish other installations.
NDIS is disabled, and only Modem can be used.
USBSERIAL_
ACM_TARGET_PATH =
AUTORUNPATH=
AUTORUNPATH=
ADDRUNLEVEL=
‘/etc/rc2.
‘/etc/rc2.
ADDRUNLEVEL=
‘/etc/rc5.
‘/etc/rc5.
ADDRUNLEVEL=
‘/etc/rc4.
‘/etc/rc4.
ADDRUNLEVEL=
‘/etc/rc3.
‘/etc/rc3.
qmi_wwan interface not exist,ok
vanamali@
Revision history for this message
|
#6 |
Revision history for this message
|
#7 |
I tried the solution given in the link. The output is the same as I
provided in the provided posts. The modem does not connect.
Why would the /etc/usb_
anything named /var/log/messages?
Revision history for this message
|
#8 |
The rule files for usb_modeswitch are in /usr/share/
And have you checked /var/log/syslog?
Revision history for this message
|
#9 |
http://
This page (and some others) recommend editing driver/
Revision history for this message
|
#10 |
@thkrueger The contents of /var/log/syslog when I call wvdial:
Sep 5 16:24:29 Shastry kernel: [ 4994.768080] usb 6-1: new full-speed USB device number 4 using uhci_hcd
Sep 5 16:24:29 Shastry kernel: [ 4994.933125] usb 6-1: New USB device found, idVendor=12d1, idProduct=1505
Sep 5 16:24:29 Shastry kernel: [ 4994.933133] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=4
Sep 5 16:24:29 Shastry kernel: [ 4994.933140] usb 6-1: Product: HUAWEI Mobile
Sep 5 16:24:29 Shastry kernel: [ 4994.933146] usb 6-1: Manufacturer: HUAÿWEI TECHNOLOGIES
Sep 5 16:24:29 Shastry kernel: [ 4994.933152] usb 6-1: SerialNumber: ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
Sep 5 16:24:29 Shastry kernel: [ 4994.935399] scsi12 : usb-storage 6-1:1.0
Sep 5 16:24:29 Shastry mtp-probe: checking bus 6, device 4: "/sys/devices/
Sep 5 16:24:29 Shastry mtp-probe: bus: 6, device: 4 was not an MTP device
Sep 5 16:24:30 Shastry udevd[5315]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:30 Shastry HWActivator: Daemon already running
Sep 5 16:24:30 Shastry udevd[5319]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:30 Shastry HWActivator: Daemon already running
Sep 5 16:24:30 Shastry udevd[5323]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:30 Shastry HWActivator: lxz send_rewind_cmd_new start
Sep 5 16:24:30 Shastry HWActivator: lxz usb-storage detached,ret=0
Sep 5 16:24:30 Shastry HWActivator: Daemon already running
Sep 5 16:24:30 Shastry kernel: [ 4995.632145] usb 6-1: USB disconnect, device number 4
Sep 5 16:24:30 Shastry HWActivator: lxz send_rewind_cmd_new end 2
Sep 5 16:24:33 Shastry kernel: [ 4999.224088] usb 6-1: new full-speed USB device number 5 using uhci_hcd
Sep 5 16:24:33 Shastry kernel: [ 4999.389134] usb 6-1: New USB device found, idVendor=12d1, idProduct=140b
Sep 5 16:24:33 Shastry kernel: [ 4999.389143] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=4
Sep 5 16:24:33 Shastry kernel: [ 4999.389154] usb 6-1: Product: HUAWEI Mobile
Sep 5 16:24:33 Shastry kernel: [ 4999.389160] usb 6-1: Manufacturer: HUAÿWEI TECHNOLOGIES
Sep 5 16:24:33 Shastry kernel: [ 4999.389165] usb 6-1: SerialNumber: ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
Sep 5 16:24:33 Shastry kernel: [ 4999.394322] option 6-1:1.0: GSM modem (1-port) converter detected
Sep 5 16:24:33 Shastry kernel: [ 4999.394528] usb 6-1: GSM modem (1-port) converter now attached to ttyUSB0
Sep 5 16:24:33 Shastry kernel: [ 4999.396344] option 6-1:1.1: GSM modem (1-port) converter detected
Sep 5 16:24:33 Shastry kernel: [ 4999.396522] usb 6-1: GSM modem (1-port) converter now attached to ttyUSB1
Sep 5 16:24:33 Shastry kernel: [ 4999.398303] option 6-1:1.2: GSM modem (1-port) converter detected
Sep 5 16:24:33 Shastry kernel: [ 4999.398507] usb 6-1: GSM modem (1-port) converter now attached to ttyUSB2
Sep 5 16:24:33 Shastry kernel: [ 4999.399192] scsi16 : usb-storage 6-1:1.3
Sep 5 16:24:33 Shastry mtp-probe: checking bus 6, device 5: "/sys/devices/
Sep 5 16:24:33 Shastry mtp-probe: bus: 6, device: 5 was not an MTP device
Sep 5 16:24:34 Shastry udevd[5344]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:34 Shastry udevd[5347]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:34 Shastry udevd[5349]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:34 Shastry udevd[5348]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:34 Shastry HWActivator: Daemon already running
Sep 5 16:24:34 Shastry udevd[5355]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:34 Shastry HWActivator: Daemon already running
Sep 5 16:24:34 Shastry udevd[5360]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:34 Shastry HWActivator: Daemon already running
Sep 5 16:24:34 Shastry HWActivator: Daemon already running
Sep 5 16:24:34 Shastry udevd[5366]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:34 Shastry HWActivator: Daemon already running
Sep 5 16:24:34 Shastry HWActivator: Daemon already running
Sep 5 16:24:34 Shastry udevd[5378]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:34 Shastry HWActivator: Daemon already running
Sep 5 16:24:34 Shastry HWActivator: Daemon already running
Sep 5 16:24:34 Shastry udevd[5394]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:34 Shastry HWActivator: Daemon already running
Sep 5 16:24:34 Shastry udevd[5055]: kernel-provided name 'ttyUSB1' and NAME= 'ttyUSB_utps_diag' disagree, please use SYMLINK+= or change the kernel to provide the proper name
Sep 5 16:24:34 Shastry udevd[5055]: device node '/dev/ttyUSB_
Sep 5 16:24:34 Shastry udevd[5343]: kernel-provided name 'ttyUSB2' and NAME= 'ttyUSB_utps_pcui' disagree, please use SYMLINK+= or change the kernel to provide the proper name
Sep 5 16:24:34 Shastry udevd[5343]: device node '/dev/ttyUSB_
Sep 5 16:24:34 Shastry udevd[5406]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:34 Shastry udevd[5407]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:34 Shastry udevd[5054]: kernel-provided name 'ttyUSB0' and NAME= 'ttyUSB_utps_modem' disagree, please use SYMLINK+= or change the kernel to provide the proper name
Sep 5 16:24:34 Shastry udevd[5054]: device node '/dev/ttyUSB_
Sep 5 16:24:34 Shastry HWActivator: Daemon already running
Sep 5 16:24:34 Shastry HWActivator: Daemon already running
Sep 5 16:24:34 Shastry udevd[5416]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:34 Shastry HWActivator: Daemon already running
Sep 5 16:24:34 Shastry modem-manager[979]: <info> (ttyUSB2) opening serial port...
Sep 5 16:24:34 Shastry modem-manager[979]: <info> (ttyUSB1) opening serial port...
Sep 5 16:24:34 Shastry modem-manager[979]: <info> (ttyUSB0) opening serial port...
Sep 5 16:24:34 Shastry modem-manager[979]: <info> (ttyUSB2) opening serial port...
Sep 5 16:24:34 Shastry modem-manager[979]: <info> (ttyUSB1) opening serial port...
Sep 5 16:24:34 Shastry modem-manager[979]: <info> (ttyUSB0) opening serial port...
Sep 5 16:24:34 Shastry kernel: [ 5000.400207] scsi 16:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 0
Sep 5 16:24:34 Shastry kernel: [ 5000.403182] scsi 16:0:0:1: Direct-Access HUAWEI SD Storage 2.31 PQ: 0 ANSI: 2
Sep 5 16:24:34 Shastry udevd[5427]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:34 Shastry HWActivator: Daemon already running
Sep 5 16:24:34 Shastry udevd[5431]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:34 Shastry HWActivator: Daemon already running
Sep 5 16:24:34 Shastry kernel: [ 5000.423171] sr1: scsi-1 drive
Sep 5 16:24:34 Shastry kernel: [ 5000.423477] sr 16:0:0:0: Attached scsi CD-ROM sr1
Sep 5 16:24:34 Shastry kernel: [ 5000.423736] sr 16:0:0:0: Attached scsi generic sg2 type 5
Sep 5 16:24:34 Shastry kernel: [ 5000.424337] sd 16:0:0:1: Attached scsi generic sg3 type 0
Sep 5 16:24:35 Shastry udevd[5438]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:35 Shastry udevd[5440]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:35 Shastry udevd[5439]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:35 Shastry HWActivator: Daemon already running
Sep 5 16:24:35 Shastry udevd[5445]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:35 Shastry HWActivator: Daemon already running
Sep 5 16:24:35 Shastry HWActivator: Daemon already running
Sep 5 16:24:35 Shastry kernel: [ 5000.440147] sd 16:0:0:1: [sdb] Attached SCSI removable disk
Sep 5 16:24:35 Shastry udevd[5455]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:35 Shastry udevd[5456]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:35 Shastry HWActivator: Daemon already running
Sep 5 16:24:35 Shastry udevd[5457]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:35 Shastry udevd[5460]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:35 Shastry HWActivator: Daemon already running
Sep 5 16:24:35 HWActivator: last message repeated 3 times
Sep 5 16:24:35 Shastry udevd[5474]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:35 Shastry HWActivator: Daemon already running
Sep 5 16:24:35 Shastry udevd[5487]: failed to execute '/path/HWActivator' '/path/
Sep 5 16:24:35 Shastry HWActivator: Daemon already running
Sep 5 16:24:36 Shastry HWActivator: HW load_for_
Sep 5 16:24:36 Shastry HWActivator: load_for_
Sep 5 16:24:36 Shastry HWActivator: load_for_
Sep 5 16:24:36 Shastry HWActivator: HW load_for_
Sep 5 16:24:36 Shastry HWActivator: fxz:The path=/usr/
Sep 5 16:24:36 Shastry HWActivator: Open config file failed, asume the autorun is activated
Sep 5 16:24:36 Shastry HWActivator: start MobilePartner, the dashboard is .bin
Sep 5 16:24:48 Shastry HWActivator: HWActivator: sockaddr is not binded.
Sep 5 16:24:48 Shastry HWActivator: /sbin/startMobi
Sep 5 16:25:04 Shastry pppd[5552]: pppd 2.4.5 started by root, uid 0
Sep 5 16:25:04 Shastry pppd[5552]: Using interface ppp0
Sep 5 16:25:04 Shastry pppd[5552]: Connect: ppp0 <--> /dev/ttyUSB_
Sep 5 16:25:04 Shastry NetworkManager[
Sep 5 16:25:04 Shastry NetworkManager[
Sep 5 16:25:04 Shastry NetworkManager[
Sep 5 16:25:34 Shastry pppd[5552]: LCP: timeout sending Config-Requests
Sep 5 16:25:34 Shastry pppd[5552]: Connection terminated.
Sep 5 16:25:34 Shastry avahi-daemon[1005]: Withdrawing workstation service for ppp0.
Sep 5 16:25:34 Shastry NetworkManager[
Sep 5 16:25:34 Shastry pppd[5552]: Modem hangup
Sep 5 16:25:34 Shastry pppd[5552]: Exit.
Revision history for this message
|
#11 |
@m-hampl Thank you for the link! It removed the errors related to NDIS during installation. But the modem doesn't connect! The contents of /var/log/syslog upon issuing 'sudo wvdial' are:
Sep 5 19:51:27 Shastry kernel: [ 1145.399726] usbcore: deregistering interface driver huawei_ether
Sep 5 19:51:28 Shastry udevd[341]: unknown key 'SYSFS{model}' in /etc/udev/
Sep 5 19:51:28 Shastry udevd[341]: invalid rule '/etc/udev/
Sep 5 19:51:28 Shastry udevd[341]: unknown key 'SYSFS{model}' in /etc/udev/
Sep 5 19:51:28 Shastry udevd[341]: invalid rule '/etc/udev/
Sep 5 19:51:28 Shastry udevd[341]: can not find '/etc/udev/
Sep 5 19:51:29 Shastry udevd[341]: unknown key 'SYSFS{model}' in /etc/udev/
Sep 5 19:51:29 Shastry udevd[341]: invalid rule '/etc/udev/
Sep 5 19:51:29 Shastry udevd[341]: unknown key 'SYSFS{model}' in /etc/udev/
Sep 5 19:51:29 Shastry udevd[341]: invalid rule '/etc/udev/
Sep 5 19:51:29 Shastry kernel: [ 1146.472076] usbserial: USB Serial deregistering driver GSM modem (1-port)
Sep 5 19:51:29 Shastry kernel: [ 1146.472220] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
Sep 5 19:51:29 Shastry kernel: [ 1146.472303] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Sep 5 19:51:29 Shastry kernel: [ 1146.472379] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Sep 5 19:51:29 Shastry kernel: [ 1146.472395] usbcore: deregistering interface driver option
Sep 5 19:51:29 Shastry kernel: [ 1146.472431] option 6-1:1.2: device disconnected
Sep 5 19:51:29 Shastry kernel: [ 1146.472459] option 6-1:1.1: device disconnected
Sep 5 19:51:29 Shastry kernel: [ 1146.474298] usb-serial ttyUSB0: option_
Sep 5 19:51:29 Shastry kernel: [ 1146.476364] option 6-1:1.0: device disconnected
Sep 5 19:51:29 Shastry kernel: [ 1146.492153] usbserial: USB Serial deregistering driver generic
Sep 5 19:51:29 Shastry kernel: [ 1146.492200] usbcore: deregistering interface driver usbserial_generic
Sep 5 19:51:29 Shastry kernel: [ 1146.492220] usbcore: deregistering interface driver usbserial
Sep 5 19:51:29 Shastry kernel: [ 1146.503722] usbcore: registered new interface driver usbserial
Sep 5 19:51:29 Shastry kernel: [ 1146.503753] usbcore: registered new interface driver usbserial_generic
Sep 5 19:51:29 Shastry kernel: [ 1146.503774] usbserial: USB Serial support registered for generic
Sep 5 19:51:29 Shastry kernel: [ 1146.517418] usbcore: registered new interface driver option
Sep 5 19:51:29 Shastry kernel: [ 1146.517444] usbserial: USB Serial support registered for GSM modem (1-port)
Sep 5 19:51:29 Shastry kernel: [ 1146.517535] option 6-1:1.0: GSM modem (1-port) converter detected
Sep 5 19:51:29 Shastry kernel: [ 1146.517680] usb 6-1: GSM modem (1-port) converter now attached to ttyUSB0
Sep 5 19:51:29 Shastry kernel: [ 1146.517706] option 6-1:1.1: GSM modem (1-port) converter detected
Sep 5 19:51:29 Shastry kernel: [ 1146.517793] usb 6-1: GSM modem (1-port) converter now attached to ttyUSB1
Sep 5 19:51:29 Shastry kernel: [ 1146.517809] option 6-1:1.2: GSM modem (1-port) converter detected
Sep 5 19:51:29 Shastry kernel: [ 1146.517889] usb 6-1: GSM modem (1-port) converter now attached to ttyUSB2
Sep 5 19:51:29 Shastry udevd[4599]: failed to execute '/path/HWActivator' '/path/
Sep 5 19:51:29 Shastry udevd[4600]: failed to execute '/path/HWActivator' '/path/
Sep 5 19:51:29 Shastry udevd[4601]: failed to execute '/path/HWActivator' '/path/
Sep 5 19:51:29 Shastry udevd[4587]: kernel-provided name 'ttyUSB2' and NAME= 'ttyUSB_utps_pcui' disagree, please use SYMLINK+= or change the kernel to provide the proper name
Sep 5 19:51:29 Shastry udevd[4585]: kernel-provided name 'ttyUSB0' and NAME= 'ttyUSB_utps_modem' disagree, please use SYMLINK+= or change the kernel to provide the proper name
Sep 5 19:51:29 Shastry udevd[4652]: failed to execute '/path/HWActivator' '/path/
Sep 5 19:51:29 Shastry udevd[4658]: failed to execute '/path/HWActivator' '/path/
Sep 5 19:51:29 Shastry udevd[4586]: kernel-provided name 'ttyUSB1' and NAME= 'ttyUSB_utps_diag' disagree, please use SYMLINK+= or change the kernel to provide the proper name
Sep 5 19:51:29 Shastry udevd[4664]: failed to execute '/path/HWActivator' '/path/
Sep 5 19:51:29 Shastry modem-manager[954]: <info> (ttyUSB2) opening serial port...
Sep 5 19:51:29 Shastry modem-manager[954]: <info> (ttyUSB2) opening serial port...
Sep 5 19:51:29 Shastry modem-manager[954]: <info> (ttyUSB0) opening serial port...
Sep 5 19:51:29 Shastry modem-manager[954]: <info> (ttyUSB1) opening serial port...
Sep 5 19:51:29 Shastry modem-manager[954]: <info> (ttyUSB0) opening serial port...
Sep 5 19:51:29 Shastry modem-manager[954]: <info> (ttyUSB1) opening serial port...
Sep 5 19:51:29 Shastry udevd[341]: unknown key 'SYSFS{model}' in /etc/udev/
Sep 5 19:51:29 Shastry udevd[341]: invalid rule '/etc/udev/
Sep 5 19:51:29 Shastry udevd[341]: unknown key 'SYSFS{model}' in /etc/udev/
Sep 5 19:51:29 Shastry udevd[341]: invalid rule '/etc/udev/
Sep 5 19:51:29 Shastry udevd[341]: unknown key 'SYSFS{model}' in /etc/udev/
Sep 5 19:51:29 Shastry udevd[341]: invalid rule '/etc/udev/
Sep 5 19:51:29 Shastry udevd[341]: unknown key 'SYSFS{model}' in /etc/udev/
Sep 5 19:51:29 Shastry udevd[341]: invalid rule '/etc/udev/
Sep 5 19:51:29 Shastry kernel: [ 1146.807747] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
Sep 5 19:51:29 Shastry kernel: [ 1146.807772] option 6-1:1.2: device disconnected
Sep 5 19:51:29 Shastry kernel: [ 1146.807884] option 6-1:1.2: GSM modem (1-port) converter detected
Sep 5 19:51:29 Shastry kernel: [ 1146.810512] usb 6-1: GSM modem (1-port) converter now attached to ttyUSB2
Sep 5 19:51:29 Shastry udevd[4719]: failed to execute '/path/HWActivator' '/path/
Sep 5 19:51:29 Shastry kernel: [ 1146.823004] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Sep 5 19:51:29 Shastry kernel: [ 1146.823030] option 6-1:1.1: device disconnected
Sep 5 19:51:29 Shastry kernel: [ 1146.823155] option 6-1:1.1: GSM modem (1-port) converter detected
Sep 5 19:51:29 Shastry kernel: [ 1146.823323] usb 6-1: GSM modem (1-port) converter now attached to ttyUSB1
Sep 5 19:51:29 Shastry kernel: [ 1146.835295] option1 ttyUSB0: option_
Sep 5 19:51:29 Shastry kernel: [ 1146.835443] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Sep 5 19:51:29 Shastry kernel: [ 1146.835465] option 6-1:1.0: device disconnected
Sep 5 19:51:29 Shastry kernel: [ 1146.835610] option 6-1:1.0: GSM modem (1-port) converter detected
Sep 5 19:51:29 Shastry kernel: [ 1146.835729] usb 6-1: GSM modem (1-port) converter now attached to ttyUSB0
Sep 5 19:51:29 Shastry udevd[4738]: failed to execute '/path/HWActivator' '/path/
Sep 5 19:51:29 Shastry udevd[4751]: failed to execute '/path/HWActivator' '/path/
Sep 5 19:51:29 Shastry HWActivator: Daemon already running
Sep 5 19:51:29 Shastry udevd[4710]: kernel-provided name 'ttyUSB2' and NAME= 'ttyUSB_utps_pcui' disagree, please use SYMLINK+= or change the kernel to provide the proper name
Sep 5 19:51:29 Shastry udevd[4710]: device node '/dev/ttyUSB_
Sep 5 19:51:29 Shastry HWActivator: Daemon already running
Sep 5 19:51:29 Shastry udevd[4785]: failed to execute '/path/HWActivator' '/path/
Sep 5 19:51:29 Shastry udevd[4723]: kernel-provided name 'ttyUSB1' and NAME= 'ttyUSB_utps_diag' disagree, please use SYMLINK+= or change the kernel to provide the proper name
Sep 5 19:51:29 Shastry udevd[4723]: device node '/dev/ttyUSB_
Sep 5 19:51:29 Shastry udevd[4797]: failed to execute '/path/HWActivator' '/path/
Sep 5 19:51:29 Shastry HWActivator: Daemon already running
Sep 5 19:51:29 Shastry modem-manager[954]: <info> (ttyUSB2) opening serial port...
Sep 5 19:51:29 Shastry modem-manager[954]: <info> (ttyUSB2) opening serial port...
Sep 5 19:51:29 Shastry udevd[4735]: kernel-provided name 'ttyUSB0' and NAME= 'ttyUSB_utps_modem' disagree, please use SYMLINK+= or change the kernel to provide the proper name
Sep 5 19:51:29 Shastry udevd[4735]: device node '/dev/ttyUSB_
Sep 5 19:51:29 Shastry udevd[4828]: failed to execute '/path/HWActivator' '/path/
Sep 5 19:51:29 Shastry HWActivator: Daemon already running
Sep 5 19:51:29 Shastry modem-manager[954]: <info> (ttyUSB1) opening serial port...
Sep 5 19:51:29 Shastry modem-manager[954]: <info> (ttyUSB1) opening serial port...
Sep 5 19:51:29 Shastry HWActivator: Daemon already running
Sep 5 19:51:29 Shastry modem-manager[954]: <info> (ttyUSB0) opening serial port...
Sep 5 19:51:29 Shastry modem-manager[954]: <info> (ttyUSB0) opening serial port...
Sep 5 19:51:29 Shastry HWActivator: HW load_for_
Sep 5 19:51:29 Shastry HWActivator: load_for_
Sep 5 19:51:29 Shastry HWActivator: load_for_
Sep 5 19:51:29 Shastry HWActivator: HW load_for_
Sep 5 19:51:29 Shastry HWActivator: fxz:The path=/usr/
Sep 5 19:51:29 Shastry HWActivator: Open config file failed, asume the autorun is activated
Sep 5 19:51:29 Shastry HWActivator: start MobilePartner, the dashboard is .bin
Sep 5 19:51:33 Shastry kernel: [ 1150.742595] usbcore: registered new interface driver huawei_ether
Sep 5 19:51:35 Shastry HWActivator: Daemon already running
Sep 5 19:51:41 Shastry HWActivator: HWActivator: sockaddr is not binded.
Sep 5 19:51:41 Shastry HWActivator: /sbin/startMobi
Revision history for this message
|
#12 |
There seem to be errors in your udev configuration.
Please execute the commands
cat -n /etc/udev/
grep /path/ /etc/udev/rules /etc/udev/rules.d/*
and copy/paste all output into this question document.
Revision history for this message
|
#13 |
vanamali@Shastry:~$ cat -n /etc/udev/
1 KERNEL=
2 KERNEL=
3 KERNEL=
vanamali@
grep: /etc/udev/rules: No such file or directory
/etc/udev/
Revision history for this message
|
#14 |
I guess you have to make the following modifications:
1. Change /etc/udev/
replace all occurences of "SYSFS{model}" by "ATTRS{model}" and
replace all occurences of "SYSFS{vendor}" by "ATTRS{vendor}"
Another possibility would be to delete that whole file, if it is not needed any more (it seems to be for a ZTE EVDO USB modem)
2. find out the real path for HWActivator and change the entry in /etc/udev/
sudo updatedb; locate HWActivator
You have to be aware that
a. For editing these files you have to use a terminal command like
gksudo gksudo gedit /etc/udev/
b. You have to reboot your system for the changes to have effect
Revision history for this message
|
#15 |
Thank you very much for the help! I followed the steps you suggested and after that, syslog doesn't show any errors when the device is plugged in. When I try wvdial though, the modem still disconnects, and the syslog for that event reads:
01 Sep 6 19:01:20 Shastry pppd[3205]: pppd 2.4.5 started by root, uid 0
02 Sep 6 19:01:20 Shastry pppd[3205]: Using interface ppp0
03 Sep 6 19:01:20 Shastry pppd[3205]: Connect: ppp0 <--> /dev/ttyUSB_
04 Sep 6 19:01:20 Shastry NetworkManager[
05 Sep 6 19:01:20 Shastry NetworkManager[
06 Sep 6 19:01:20 Shastry NetworkManager[
07 Sep 6 19:01:50 Shastry pppd[3205]: LCP: timeout sending Config-Requests
08 Sep 6 19:01:50 Shastry pppd[3205]: Connection terminated.
09 Sep 6 19:01:50 Shastry avahi-daemon[1000]: Withdrawing workstation service for ppp0.
10 Sep 6 19:01:50 Shastry NetworkManager[
11 Sep 6 19:01:50 Shastry pppd[3205]: Modem hangup
12 Sep 6 19:01:50 Shastry pppd[3205]: Exit.
Referring to lines 04 through 08, how do I rectify the error with ifupdown configuration? That might help solve my problem, as it is the only one apparent in the syslog file.
Revision history for this message
|
#16 |
Thank you everyone for your effort. It was a great learning experience. Apparently, the device has to be activated through a Windows system first. Its working fine now. Sorry for the trouble.