Ubuntu
gnome-nettool package

Huawei EC1260 USB modem is not detected in Ubuntu 13.04

Asked by Vanamali

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/libkmod-module.c:753 kmod_module_remove_module: could not remove 'usbnet': No such file or directory", etc and it ended with a message "qmi_wwan interface not exist,ok". After this, the system doesn't even recognize the device. Is there any way to get this device working? At least take the situation back to the initial state when the device was recognized. Thanks in advance.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu gnome-nettool Edit question
Assignee:
No assignee Edit question
Solved by:
Vanamali
Solved:
Last query:
Last reply:
Revision history for this message
Vanamali (vanamalishastry) said : 		#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
Mark Rijckenberg (markrijckenberg) said : 		#2

Please try the solution procedure by Anisur R Mullick (anisur-mullick) at the end of the following thread:

https://answers.launchpad.net/ubuntu/+source/gnome-nettool/+question/114695

Revision history for this message
Vanamali (vanamalishastry) said : 		#3

Thank you for the response. I tried the link you provided. I encountered an
error at step 3 - the folder /etc/usb_modeswitch.d is empty ! What do I
do.
On Sep 4, 2013 7:41 PM, "Mark Rijckenberg" <
<email address hidden>> wrote:

> Your question #235153 on gnome-nettool in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/gnome-nettool/+question/235153
>
> 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://answers.launchpad.net/ubuntu/+source/gnome-
> nettool/+question/114695
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/ubuntu/+source/gnome-nettool/+question/235153/+confirm?answer_id=1
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+source/gnome-nettool/+question/235153
>
> You received this question notification because you asked the question.
>

Revision history for this message
Vanamali (vanamalishastry) said : 		#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_utps_diag<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyUSB_utps_diag<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 9600 baud
ttyUSB_utps_diag<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyUSB_utps_modem<*1>: ATQ0 V1 E1 -- OK
ttyUSB_utps_modem<*1>: ATQ0 V1 E1 Z -- OK
ttyUSB_utps_modem<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyUSB_utps_modem<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyUSB_utps_modem<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyUSB_utps_modem<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyUSB_utps_modem<*1>: Modem Identifier: ATI -- Manufacturer: +GMI: HUAWEI TECHNOLOGIES CO., LTD
ttyUSB_utps_modem<*1>: Speed 9600: AT -- OK
ttyUSB_utps_modem<*1>: Max speed is 9600; that should be safe.
ttyUSB_utps_modem<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyUSB_utps_pcui<*1>: ATQ0 V1 E1 -- OK
ttyUSB_utps_pcui<*1>: ATQ0 V1 E1 Z -- OK
ttyUSB_utps_pcui<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyUSB_utps_pcui<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyUSB_utps_pcui<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyUSB_utps_pcui<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyUSB_utps_pcui<*1>: Modem Identifier: ATI -- Manufacturer: +GMI: HUAWEI TECHNOLOGIES CO., LTD
ttyUSB_utps_pcui<*1>: Speed 9600: AT -- OK
ttyUSB_utps_pcui<*1>: Max speed is 9600; that should be safe.
ttyUSB_utps_pcui<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK

Found a modem on /dev/ttyUSB_utps_modem.
Modem configuration written to /etc/wvdial.conf.
ttyUSB_utps_modem<Info>: Speed 9600; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
ttyUSB_utps_pcui<Info>: Speed 9600; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"

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
Vanamali (vanamalishastry) said : 		#5

The output of the installation process (which I had mentioned in the question) is as follows:
vanamali@Shastry:~/Documents/Drivers/MTS/MBlaze linux Installation/driver$ sudo ./install
DRIVER COPY START
STA_PATH_FLAG=.
STA_PATH_FULL=/home/vanamali/Documents/Drivers/MTS/MBlaze linux Installation/driver/install
START_PATH_DRIVER=/home/vanamali/Documents/Drivers/MTS/MBlaze linux Installation/driver
CURRENT install from ./install
INSTALL_PATH is not set ,auto install
INSTALL_PATH=/usr/local/Mobile_Partner
INSTALL_PATH is another path
rm /usr/local/Mobile_Partner/driver
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/libkmod-module.c:753 kmod_module_remove_module: could not remove 'cdc_ether': No such file or directory
Error: could not remove module cdc_ether: No such file or directory
libkmod: ERROR ../libkmod/libkmod-module.c:753 kmod_module_remove_module: could not remove 'usbnet': No such file or directory
Error: could not remove module usbnet: No such file or directory
libkmod: ERROR ../libkmod/libkmod-module.c:753 kmod_module_remove_module: could not remove 'hw_cdc_driver': No such file or directory
Error: could not remove module hw_cdc_driver: No such file or directory
make -C src/ clean
make[1]: Entering directory `/usr/local/Mobile_Partner/driver/ndis_driver/ndis_src/src'
rm -rf *.o *.ko *~ core* .dep* .*.d .*.cmd *.mod.c *.a *.s .*.flags .tmp_versions Module.symvers Modules.symvers *.order
/usr/local/Mobile_Partner/driver/ndis_driver/ndis_src/src/add_header.sh "clean" "/lib/modules/3.8.0-29-generic/build/include/linux/usb"
rmmod -f hw_cdc_driver
libkmod: ERROR ../libkmod/libkmod-module.c:753 kmod_module_remove_module: could not remove 'hw_cdc_driver': No such file or directory
Error: could not remove module hw_cdc_driver: No such file or directory
make[1]: *** [clean] Error 1
make[1]: Leaving directory `/usr/local/Mobile_Partner/driver/ndis_driver/ndis_src/src'
make: *** [clean] Error 2
make -C src/ modules
make[1]: Entering directory `/usr/local/Mobile_Partner/driver/ndis_driver/ndis_src/src'
#/usr/local/Mobile_Partner/driver/ndis_driver/ndis_src/src/add_header.sh "modules" "/lib/modules/3.8.0-29-generic/build/include/linux/usb"
make -C /lib/modules/3.8.0-29-generic/build SUBDIRS=/usr/local/Mobile_Partner/driver/ndis_driver/ndis_src/src modules
make[2]: Entering directory `/usr/src/linux-headers-3.8.0-29-generic'
  CC [M] /usr/local/Mobile_Partner/driver/ndis_driver/ndis_src/src/hw_cdc_driver.o
/usr/local/Mobile_Partner/driver/ndis_driver/ndis_src/src/hw_cdc_driver.c: In function ‘hw_cdc_probe’:
/usr/local/Mobile_Partner/driver/ndis_driver/ndis_src/src/hw_cdc_driver.c:2718:9: error: implicit declaration of function ‘dbg’ [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[3]: *** [/usr/local/Mobile_Partner/driver/ndis_driver/ndis_src/src/hw_cdc_driver.o] Error 1
make[2]: *** [_module_/usr/local/Mobile_Partner/driver/ndis_driver/ndis_src/src] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-3.8.0-29-generic'
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/local/Mobile_Partner/driver/ndis_driver/ndis_src/src'
make: *** [modules] Error 2
make -C src/ install
make[1]: Entering directory `/usr/local/Mobile_Partner/driver/ndis_driver/ndis_src/src'
#install -m 744 -c hw_cdc_driver.o /lib/modules/3.8.0-29-generic/kernel/drivers/usb/net
#depmod -a
#modprobe hw_cdc_driver
/usr/local/Mobile_Partner/driver/ndis_driver/ndis_src/src/add_header.sh "install"
modprobe hw_cdc_driver
FATAL: Module hw_cdc_driver not found.
make[1]: *** [install] Error 1
make[1]: Leaving directory `/usr/local/Mobile_Partner/driver/ndis_driver/ndis_src/src'
make: *** [install] Error 2

Install NDIS driver failed.
The compiling environment is not all ready.
Please check gcc, make and kernel buid(/lib/modules/3.8.0-29-generic/build) to be all installed?
Now please enter any key to finish other installations.

NDIS is disabled, and only Modem can be used.
USBSERIAL_TARGET_PATH =
ACM_TARGET_PATH =
AUTORUNPATH=/home/vanamali/.config/autostart
AUTORUNPATH=/home/vanamali/glassfish-3.1.2.2/glassfish/modules/autostart
ADDRUNLEVEL=/etc/rc2.d
‘/etc/rc2.d/S99runhwactivator’ -> ‘/etc/init.d/runhwactivator’
‘/etc/rc2.d/K10runhwactivator’ -> ‘/etc/init.d/runhwactivator’
ADDRUNLEVEL=/etc/rc5.d
‘/etc/rc5.d/S99runhwactivator’ -> ‘/etc/init.d/runhwactivator’
‘/etc/rc5.d/K10runhwactivator’ -> ‘/etc/init.d/runhwactivator’
ADDRUNLEVEL=/etc/rc4.d
‘/etc/rc4.d/S99runhwactivator’ -> ‘/etc/init.d/runhwactivator’
‘/etc/rc4.d/K10runhwactivator’ -> ‘/etc/init.d/runhwactivator’
ADDRUNLEVEL=/etc/rc3.d
‘/etc/rc3.d/S99runhwactivator’ -> ‘/etc/init.d/runhwactivator’
‘/etc/rc3.d/K10runhwactivator’ -> ‘/etc/init.d/runhwactivator’
qmi_wwan interface not exist,ok
vanamali@Shastry:~/Documents/Drivers/MTS/MBlaze linux Installation/driver$

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#6

http://delogics.blogspot.co.uk/2011/11/huawei-ec1260-12d1140b-reliance-tata.html

Revision history for this message
Vanamali (vanamalishastry) said : 		#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_modeswitch.d folderbe empty? Also, why don't I find
anything named /var/log/messages?

Revision history for this message
Thomas Krüger (thkrueger) said : 		#8

The rule files for usb_modeswitch are in /usr/share/usb_modeswitch/configPack.tar.gz not in /etc/usb_modeswitch.d.
And have you checked /var/log/syslog?

Revision history for this message
Manfred Hampl (m-hampl) said : 		#9

http://askubuntu.com/questions/299519/huawei-linux-driver-on-ubuntu-13-04

This page (and some others) recommend editing driver/ndis_driver/ndis_src/src/hw_cdc_driver.c and to comment out (put // in front of) line 2715 ('dbg ("can't kmalloc dev");')

Revision history for this message
Vanamali (vanamalishastry) said : 		#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/pci0000:00/0000:00:1d.1/usb6/6-1"
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/HWActivator': No such file or directory
Sep 5 16:24:30 Shastry HWActivator: Daemon already running
Sep 5 16:24:30 Shastry udevd[5319]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
Sep 5 16:24:30 Shastry HWActivator: Daemon already running
Sep 5 16:24:30 Shastry udevd[5323]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
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/pci0000:00/0000:00:1d.1/usb6/6-1"
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/HWActivator': No such file or directory
Sep 5 16:24:34 Shastry udevd[5347]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
Sep 5 16:24:34 Shastry udevd[5349]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
Sep 5 16:24:34 Shastry udevd[5348]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
Sep 5 16:24:34 Shastry HWActivator: Daemon already running
Sep 5 16:24:34 Shastry udevd[5355]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
Sep 5 16:24:34 Shastry HWActivator: Daemon already running
Sep 5 16:24:34 Shastry udevd[5360]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
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/HWActivator': No such file or directory
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/HWActivator': No such file or directory
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/HWActivator': No such file or directory
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_utps_diag' already exists, link to '/dev/ttyUSB_utps_diag' will not overwrite it
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_utps_pcui' already exists, link to '/dev/ttyUSB_utps_pcui' will not overwrite it
Sep 5 16:24:34 Shastry udevd[5406]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
Sep 5 16:24:34 Shastry udevd[5407]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
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_utps_modem' already exists, link to '/dev/ttyUSB_utps_modem' will not overwrite it
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/HWActivator': No such file or directory
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/HWActivator': No such file or directory
Sep 5 16:24:34 Shastry HWActivator: Daemon already running
Sep 5 16:24:34 Shastry udevd[5431]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
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/HWActivator': No such file or directory
Sep 5 16:24:35 Shastry udevd[5440]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
Sep 5 16:24:35 Shastry udevd[5439]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
Sep 5 16:24:35 Shastry HWActivator: Daemon already running
Sep 5 16:24:35 Shastry udevd[5445]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
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/HWActivator': No such file or directory
Sep 5 16:24:35 Shastry udevd[5456]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
Sep 5 16:24:35 Shastry HWActivator: Daemon already running
Sep 5 16:24:35 Shastry udevd[5457]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
Sep 5 16:24:35 Shastry udevd[5460]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
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/HWActivator': No such file or directory
Sep 5 16:24:35 Shastry HWActivator: Daemon already running
Sep 5 16:24:35 Shastry udevd[5487]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
Sep 5 16:24:35 Shastry HWActivator: Daemon already running
Sep 5 16:24:36 Shastry HWActivator: HW load_for_dynamic_pid start
Sep 5 16:24:36 Shastry HWActivator: load_for_dynamic_pid is called start
Sep 5 16:24:36 Shastry HWActivator: load_for_dynamic_pid is called end
Sep 5 16:24:36 Shastry HWActivator: HW load_for_dynamic_pid end
Sep 5 16:24:36 Shastry HWActivator: fxz:The path=/usr/local/Mobile_Partner/config/autorun/config
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/startMobilePartner done
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_utps_modem
Sep 5 16:25:04 Shastry NetworkManager[1027]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Sep 5 16:25:04 Shastry NetworkManager[1027]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
Sep 5 16:25:04 Shastry NetworkManager[1027]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
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[1027]: SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Sep 5 16:25:34 Shastry pppd[5552]: Modem hangup
Sep 5 16:25:34 Shastry pppd[5552]: Exit.

Revision history for this message
Vanamali (vanamalishastry) said : 		#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/rules.d/10-ztemtEVDO.rules:1
Sep 5 19:51:28 Shastry udevd[341]: invalid rule '/etc/udev/rules.d/10-ztemtEVDO.rules:1'
Sep 5 19:51:28 Shastry udevd[341]: unknown key 'SYSFS{model}' in /etc/udev/rules.d/10-ztemtEVDO.rules:2
Sep 5 19:51:28 Shastry udevd[341]: invalid rule '/etc/udev/rules.d/10-ztemtEVDO.rules:2'
Sep 5 19:51:28 Shastry udevd[341]: can not find '/etc/udev/rules.d/50-Huawei-Datacard.rules': No such file or directory
Sep 5 19:51:29 Shastry udevd[341]: unknown key 'SYSFS{model}' in /etc/udev/rules.d/10-ztemtEVDO.rules:1
Sep 5 19:51:29 Shastry udevd[341]: invalid rule '/etc/udev/rules.d/10-ztemtEVDO.rules:1'
Sep 5 19:51:29 Shastry udevd[341]: unknown key 'SYSFS{model}' in /etc/udev/rules.d/10-ztemtEVDO.rules:2
Sep 5 19:51:29 Shastry udevd[341]: invalid rule '/etc/udev/rules.d/10-ztemtEVDO.rules:2'
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_instat_callback: error -108
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/HWActivator': No such file or directory
Sep 5 19:51:29 Shastry udevd[4600]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
Sep 5 19:51:29 Shastry udevd[4601]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
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/HWActivator': No such file or directory
Sep 5 19:51:29 Shastry udevd[4658]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
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/HWActivator': No such file or directory
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/rules.d/10-ztemtEVDO.rules:1
Sep 5 19:51:29 Shastry udevd[341]: invalid rule '/etc/udev/rules.d/10-ztemtEVDO.rules:1'
Sep 5 19:51:29 Shastry udevd[341]: unknown key 'SYSFS{model}' in /etc/udev/rules.d/10-ztemtEVDO.rules:2
Sep 5 19:51:29 Shastry udevd[341]: invalid rule '/etc/udev/rules.d/10-ztemtEVDO.rules:2'
Sep 5 19:51:29 Shastry udevd[341]: unknown key 'SYSFS{model}' in /etc/udev/rules.d/10-ztemtEVDO.rules:1
Sep 5 19:51:29 Shastry udevd[341]: invalid rule '/etc/udev/rules.d/10-ztemtEVDO.rules:1'
Sep 5 19:51:29 Shastry udevd[341]: unknown key 'SYSFS{model}' in /etc/udev/rules.d/10-ztemtEVDO.rules:2
Sep 5 19:51:29 Shastry udevd[341]: invalid rule '/etc/udev/rules.d/10-ztemtEVDO.rules:2'
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/HWActivator': No such file or directory
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_instat_callback: error -108
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/HWActivator': No such file or directory
Sep 5 19:51:29 Shastry udevd[4751]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
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_utps_pcui' already exists, link to '/dev/ttyUSB_utps_pcui' will not overwrite it
Sep 5 19:51:29 Shastry HWActivator: Daemon already running
Sep 5 19:51:29 Shastry udevd[4785]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
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_utps_diag' already exists, link to '/dev/ttyUSB_utps_diag' will not overwrite it
Sep 5 19:51:29 Shastry udevd[4797]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
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_utps_modem' already exists, link to '/dev/ttyUSB_utps_modem' will not overwrite it
Sep 5 19:51:29 Shastry udevd[4828]: failed to execute '/path/HWActivator' '/path/HWActivator': No such file or directory
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_dynamic_pid start
Sep 5 19:51:29 Shastry HWActivator: load_for_dynamic_pid is called start
Sep 5 19:51:29 Shastry HWActivator: load_for_dynamic_pid is called end
Sep 5 19:51:29 Shastry HWActivator: HW load_for_dynamic_pid end
Sep 5 19:51:29 Shastry HWActivator: fxz:The path=/usr/local/Mobile_Partner/config/autorun/config
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/startMobilePartner done

Revision history for this message
Manfred Hampl (m-hampl) said : 		#12

There seem to be errors in your udev configuration.

Please execute the commands

cat -n /etc/udev/rules.d/10-ztemtEVDO.rules
grep /path/ /etc/udev/rules /etc/udev/rules.d/*

and copy/paste all output into this question document.

Revision history for this message
Vanamali (vanamalishastry) said : 		#13

vanamali@Shastry:~$ cat -n /etc/udev/rules.d/10-ztemtEVDO.rules
1 KERNEL=="sg[0-9]*",SUBSYSTEM=="scsi_generic",SUBSYSTEMS=="scsi",DRIVERS=="sr",SYSFS{model}=="USB Storage FF??",SYSFS{vendor}=="ZTE*",NAME="sgZTEMT"
     2 KERNEL=="sr[0-9]*",SUBSYSTEM=="block",SUBSYSTEMS=="scsi",DRIVERS=="sr",SYSFS{model}=="USB Storage FF??",SYSFS{vendor}=="ZTE*",ACTION=="add",RUN+="ztemtEVDO.sh"
     3 KERNEL=="ttyUSB[0-9]*",MODE=="0666"

 vanamali@Shastry:~$ grep /path/ /etc/udev/rules /etc/udev/rules.d/*
grep: /etc/udev/rules: No such file or directory
/etc/udev/rules.d/10-Huawei-Datacard.rules:ACTION=="add", SUBSYSTEMS=="usb", ATTRS{modalias}=="usb:v12D1*", RUN+="/path/HWActivator"

Revision history for this message
Manfred Hampl (m-hampl) said : 		#14

I guess you have to make the following modifications:

1. Change /etc/udev/rules.d/10-ztemtEVDO.rules and
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/rules.d/10-Huawei-Datacard.rules accordingly
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/rules.d/10-Huawei-Datacard.rules
b. You have to reboot your system for the changes to have effect

Revision history for this message
Vanamali (vanamalishastry) said : 		#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_utps_modem
 04 Sep 6 19:01:20 Shastry NetworkManager[1022]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
 05 Sep 6 19:01:20 Shastry NetworkManager[1022]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
 06 Sep 6 19:01:20 Shastry NetworkManager[1022]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
 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[1022]: SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
 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
Vanamali (vanamalishastry) said : 		#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.