Re: [ubuntu-in] Continuing Problems with Huawei ETS2288

2009-03-31 Thread Moz
Ram

Ramnarayan.K wrote:
 :~$ sudo modprobe usbserial vendor=0x0451 product=0x3410

 :~$ sudo mknod /dev/ttyUSB0 c 188 0

 :~$ sudo mknod /dev/ttyUSB1 c 188 1
Perhaps it might be an idea to create ttyUSB2, ttyUSB3 etc to see if 
those could be allotted to the WLL modem. Can you try that?

Moz

-- 
ubuntu-in mailing list
ubuntu-in@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-in


Re: [ubuntu-in] Continuing Problems with Huawei ETS2288

2009-03-29 Thread Ramnarayan.K
Hi Moz,

Thanks for putting in so much time.

replies below your mail

On Sat, Mar 28, 2009 at 3:57 PM, Moz list...@gmail.com wrote:
 When I was trying the configuration for the first time I did all this
 from the command line, not from rc.local or anywhere else. So, lets try
 this:

 1. Change your rc.local to the original state.
 2. Change your /etc/modprobe.d/ to the original state too.
 3. run the above commands without the password file, just enter the
 password manually, all three in the above sequence.
 4. backup your /etc/wvdial.conf and create a clean /etc/wvdial.conf,
 with the following lines:

Changed edits from rc.local

Completely  removed wvdial as it was

then did
:~$ sudo modprobe usbserial vendor=0x0451 product=0x3410

:~$ sudo mknod /dev/ttyUSB0 c 188 0

:~$ sudo mknod /dev/ttyUSB1 c 188 1


edited wvdial using both of moz's suggestions (separately)

still got this error
~$ sudo wvdial

[sudo] password for ram:

-- Ignoring malformed input line: ;Do NOT edit this file by hand!

-- WvDial: Internet dialer version 1.60

-- Cannot open /dev/ttyUSB0: No such device


this is from the wvdial extracted from GNOME PPP

**
Ok few more things – I am using on this same laptop two different data
cards which too have to be setup using the modprobe route

the Huawei EC 325 and the ZTE880

both work well.

So something else is amiss.

Checked dmesg and got this error message
[  218.090612] type=1503 audit(1238346819.369:9):
operation=inode_permission requested_mask=w:: denied_mask=w::
fsuid=0 name=/dev/ttyUSB0 pid=9672 profile=/usr/sbin/cupsd

[  218.090658] type=1503 audit(1238346819.369:10):
operation=inode_permission requested_mask=w:: denied_mask=w::
fsuid=0 name=/dev/ttyUSB1 pid=9672 profile=/usr/sbin/cupsd


Now what is this and could this have anything to do with my system not
being able to allocated /dev/ttyUSB* ??

Tried the above setup methods on live Ubuntu and openSuse sessions.
Net result the same error. I have (earlier) used a live session on
Ubuntu 7.10 to get this same device to work. So cannot figure whats
gone wrong.

ram

-- 
ubuntu-in mailing list
ubuntu-in@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-in


Re: [ubuntu-in] Continuing Problems with Huawei ETS2288

2009-03-29 Thread Moz
Hi Ram
 Thanks for putting in so much time.
   
Welcome, I live in a remote area, and I know what it is to get stuck 
like this without any support.
 then did
 :~$ sudo modprobe usbserial vendor=0x0451 product=0x3410

 :~$ sudo mknod /dev/ttyUSB0 c 188 0

 :~$ sudo mknod /dev/ttyUSB1 c 188 1
   
Since you have no error messages here, things seem to be okay so far.
 ~$ sudo wvdial

 [sudo] password for ram:

 -- Ignoring malformed input line: ;Do NOT edit this file by hand!

 -- WvDial: Internet dialer version 1.60

 -- Cannot open /dev/ttyUSB0: No such device
   
I think for some reason even sudo has no write permission to /dev/ttyUSB0.
 Checked dmesg and got this error message
 [  218.090612] type=1503 audit(1238346819.369:9):
 operation=inode_permission requested_mask=w:: denied_mask=w::
 fsuid=0 name=/dev/ttyUSB0 pid=9672 profile=/usr/sbin/cupsd

 [  218.090658] type=1503 audit(1238346819.369:10):
 operation=inode_permission requested_mask=w:: denied_mask=w::
 fsuid=0 name=/dev/ttyUSB1 pid=9672 profile=/usr/sbin/cupsd
   
Perhaps this gives the clue to why root has no permission to write to 
/dev/ttyUSB0. Who is the owner of /dev/ttyUSB0? Is it lp?

Perhaps the first thing to try is to uninstall cupsd, do you want to do 
that? It may not be worth it. But since cupsd is taking over ttyUSB0, 
removing it to check might help. Or perhaps you kill -9 9672? Or 
whatever is the process during a particular boot that grabs /dev/ttyUSB0?

Ideally chown  /dev/ttyUSB0 and chown ... /dev/ttyUSB1 should also 
help. Along with that, you'd have to do chmod too.

Here's the output for my config:

m...@ubu:~$ ls -l /dev/ttyU*
crw-r--r-- 1 root root 188, 0 2009-03-29 16:51 /dev/ttyUSB0
crw-r--r-- 1 root root 188, 1 2009-03-29 16:51 /dev/ttyUSB1

I am still reading about this problem, will let you know if I find 
something.

Moz

-- 
ubuntu-in mailing list
ubuntu-in@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-in


Re: [ubuntu-in] Continuing Problems with Huawei ETS2288

2009-03-29 Thread Moz
Ram,


 Checked dmesg and got this error message
 [  218.090612] type=1503 audit(1238346819.369:9):
 operation=inode_permission requested_mask=w:: denied_mask=w::
 fsuid=0 name=/dev/ttyUSB0 pid=9672 profile=/usr/sbin/cupsd

 [  218.090658] type=1503 audit(1238346819.369:10):
 operation=inode_permission requested_mask=w:: denied_mask=w::
 fsuid=0 name=/dev/ttyUSB1 pid=9672 profile=/usr/sbin/cupsd
   
If your /dev/ttyUSB* seem to be grabbed by cupsd, is the ETS2288 
attached to /dev/ttyACM0 or something similar? Can you check the 
existence of these? Perhaps try to talk to these ports using minicom or 
something similar?

Moz

-- 
ubuntu-in mailing list
ubuntu-in@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-in


Re: [ubuntu-in] Continuing Problems with Huawei ETS2288

2009-03-28 Thread Ramnarayan.K
Hi Moz,

Thanks for the suggestions, but still no success. This is what i did.

first checked ls /dev/ttyU*

your right there were no ttyUSBO or USB1

so did
-$sudo mknod /dev/ttyUSB0 c 188 0
-$sudo mknod /dev/ttyUSB1 c 188 1

voila next time it did ls /dev/ttyU*
i got
/dev/ttyUSB0 /dev/ttyUSB1

edited RC Local with the lines'
sudo -S modprobe usbserial vendor=0x0451 product=0x3401 /home/ram/foo/foo.txt
sudo mknod /dev/ttyUSB0 c 188 0
sudo mknod /dev/ttyUSB1 c 188 1

edited the line in wvdial crtcts to crtscts

tried wvdial 93

got error
--- cannot open /dev/ttyUSB0 . No such device

restarted and  found that the ttyUSB0 had disappeared so did mknod
again and tried
tried wvdial 93
same error

edited the line containing crtscts and # it out completely

same error.

So back to square one

Very frustrating.

I tried the same thing on Opensuse 11.1 and get the same errors.



On Fri, Mar 27, 2009 at 10:08 PM, Moz list...@gmail.com wrote:
 Hi Ram,

 Your email is very well written and is specific, so I am reading it very
 carefully, but I am travelling so my response might be in pieces.


 ~$ sudo modprobe usbserial vendor=0x0451 product=0x3410


 So far so good. But why did you not give the mknod command right after
 this, before configuring wvdial

 PPPD Options = crtcts multilink usepeerdns lock defaultroute

 Wonder why you need PPPD options. I don't with my ETS1201. But there is
 a spelling error above. Did you copy-paste? It should be crtscts.
 Then tried the options given by Moz and Onkar

 1 Made a file called
 :~$ sudo gedit /etc/rc.local

 Added the following lines (without the -S and the path to the password file)
 sudo modprobe usbserial vendor=0x0451 product=0x3410
 sudo mknod /dev/ttyUSB0 c 188 0
 sudo mknod /dev/ttyUSB1 c 188 1
 exit 0


 I am currently using the above, but without any modifications to any
 /etc/modprobe.d/ . I did that because it might conflict. But no idea. I
 also tried everything else, but only the above (without any other
 modifications) works.
 Then checked to see if there was a file called /dev/ttyUSB0

 this is the result
  -$ls /dev/ttyu*
 /dev/ttyu0  /dev/ttyu3  /dev/ttyu6  /dev/ttyu9  /dev/ttyuc  /dev/ttyuf
 /dev/ttyu1  /dev/ttyu4  /dev/ttyu7  /dev/ttyua  /dev/ttyud
 /dev/ttyu2  /dev/ttyu5  /dev/ttyu8  /dev/ttyub  /dev/ttyue

 So no ttyUSB0 or 1

 You did not look for ttyUSB0, you looked for something with ttyu*, which
 is different than ttyU*.
 While setting up in 7.10 the following are the things done
 dmesg

 the lines below are dmesg output from 7.10 (note the difference)
 #kr# error message that i get

 [  646.188000] ti_usb_3410_5052 2-1:1.0: TI USB 3410 1 port adapter
 converter detected
 [  646.188000] ti_usb_3410_5052: probe of 2-1:1.0 failed with error -5
 [  646.188000] usb 2-1: device_add(2-1:1.0) -- -5

 after which a rules file is setup
 Now we have to make one rule file in
 /etc/udev/rules.d/026_ti_usb_3410.rules . with the following lines
 #TI USB 3410

 SUBSYSTEM==usb_device ACTION==add
 SYSFS{idVendor}==0451,SYSFS{idProduct}==3410 \

 SYSFS{bNumConfigurations}==2 \

 SYSFS{bConfigurationValue}==1 \

 RUN+=/bin/sh -c 'echo 2  /sys%p/device/bConfigurationValue'

 after which when dmesg is queried we get
 dmesg

  ti_usb_3410_5052 1-2:2.0: TI USB 3410 1 port adapter converter detected
 [ 2081.24] usb 1-2: TI USB 3410 1 port adapter converter now
 attached to ttyUSB0
 [ 2081.356000] ti_usb_3410_5052_1 ttyUSB0: TI USB 3410 1 port adapter
 converter now disconnected from ttyUSB0
 [ 2081.356000] ti_usb_3410_5052 1-2:2.0: device disconnected
 [ 2081.364000] ti_usb_3410_5052 1-2:2.0: TI USB 3410 1 port adapter
 converter detected
 [ 2081.364000] usb 1-2: TI USB 3410 1 port adapter converter now
 attached to ttyUSB0

 and then the device works well.

 ***
 So the question is what is this
 [ 1642.274280] firmware: requesting ti_usb-3410.bin

 and why am i getting the /dev/ttyUSB0 error

 Since there are many devices being setup would like to know if anyone
 has got this device ets2288 working on Ubuntu 8.04 or 8.10

 I have been using ETS1201 under Ubuntu 8.04 (64 bit) and earlier under
 Ubuntu 8.10 (32 bit) for months now. And in between I also used it under
 Kubuntu 8.10 for a short while. And I had no problems. I had problems
 only when I tinkered with the config as per advice by Onkar, and my
 internet connection stopped working. But I do think that that is a more
 correct way of doing, only that someone more knowledgeable than me has
 to figure out the exact method, I can not do that.

 Warm regards

 Moz


 --
 ubuntu-in mailing list
 ubuntu-in@lists.ubuntu.com
 https://lists.ubuntu.com/mailman/listinfo/ubuntu-in


-- 
ubuntu-in mailing list
ubuntu-in@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-in


Re: [ubuntu-in] Continuing Problems with Huawei ETS2288

2009-03-28 Thread Ramnarayan.K
Hi

On Sat, Mar 28, 2009 at 1:09 PM, Ramnarayan.K ramnaraya...@gmail.com wrote:

 edited RC Local with the lines'
 sudo -S modprobe usbserial vendor=0x0451 product=0x3401 /home/ram/foo/foo.txt
 sudo mknod /dev/ttyUSB0 c 188 0
 sudo mknod /dev/ttyUSB1 c 188 1

in the /etc/rc.local there are two lines on top
#!/bin/sh -e

# rc.local

does the first line need to be un#ed , tried editing the hash out but
nothing happedn /dev/ttyUSB did not get created on start up

Second the path to the pwd file /home is there a space between  and
the path name.


Last
dmesg gives me the following error
usb 1-2: ti_download_firmware - firmware not found
ti_usb_3041_5052: probe of 1:2:1.0 failed with error 5

***
So what next.

thanks
ram

-- 
ubuntu-in mailing list
ubuntu-in@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-in


Re: [ubuntu-in] Continuing Problems with Huawei ETS2288

2009-03-28 Thread Moz
Hi Ram

 edited RC Local with the lines'
 sudo -S modprobe usbserial vendor=0x0451 product=0x3401 
 /home/ram/foo/foo.txt
 sudo mknod /dev/ttyUSB0 c 188 0
 sudo mknod /dev/ttyUSB1 c 188 1
When I was trying the configuration for the first time I did all this 
from the command line, not from rc.local or anywhere else. So, lets try 
this:

1. Change your rc.local to the original state.
2. Change your /etc/modprobe.d/ to the original state too.
3. run the above commands without the password file, just enter the 
password manually, all three in the above sequence.
4. backup your /etc/wvdial.conf and create a clean /etc/wvdial.conf, 
with the following lines:

[Dialer Defaults]
Modem = /dev/ttyUSB0
Init1 = ATZ
Phone = #777
Username = cdma
Password = cdma
New PPPD = yes
Stupid Mode = 1


This is the exact wvdial.conf I am using. As you can notice, there are 
no pppd options.

And try connecting using sudo wvdial. Sometimes, it will take almost 90 
seconds to connect, so go make tea or have a cup or coffee or something, 
in case it is taking unusually long to connect. It just might after a 
long time.


5. If this does not work, try installing minicom or something similar 
and try sending commands to the ETS2288 directly using mincom and see if 
it responds correctly.

I got my ETS1201 working as above first, used that, and found no one 
could deal with running wvdial from the shellprompt, so I have installed 
GNOME-PPP and it works well with that for the past month or so. And 
GNOME-PPP is using the following file (this is the exact copy):

[Dialer Defaults]
Modem = /dev/ttyUSB0
ISDN = off
Modem Type = Analog Modem
Baud = 115200
Init = ATZ
Init2 = ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0
Init3 =
Init4 =
Init5 =
Init6 =
Init7 =
Init8 =
Init9 =
Phone = #777
Phone1 =
Phone2 =
Phone3 =
Phone4 =
Dial Prefix =
Dial Attempts = 3
Dial Command = ATM1L3DT
Ask Password = off
Password = cdma
Username = cdma
Auto Reconnect = off
Abort on Busy = on
Carrier Check = on
Check Def Route = on
Abort on No Dialtone = on
Stupid Mode = on
Idle Seconds = 0
Auto DNS = on
;Minimize = off
;Dock = on
;Do NOT edit this file by hand!


Tell me if this works for you.

If all this works, only then create the appropriate /etc/rc.local and 
/etc/wvdial.conf. I am beginning to read about the ETS2288 in case I can 
find something about it.

Regards

Moz


-- 
ubuntu-in mailing list
ubuntu-in@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-in


Re: [ubuntu-in] Continuing Problems with Huawei ETS2288

2009-03-28 Thread Ninad Pundalik
Hi,

 in the /etc/rc.local there are two lines on top
 #!/bin/sh -e

 # rc.local

 does the first line need to be un#ed , tried editing the hash out but
 nothing happedn /dev/ttyUSB did not get created on start up

Please do not remove the '#' from the first line.  The entire line is
known as a 'shebang' among other names, and is used to tell the system
what shell to run it in.  The line has to be the first line in a shell
script, for it to be correctly recognised and run as a shell script
across all systems.

Hope this helps in removing one of your doubts in solving your
problem.  Sadly, I don't have the answer to your complete problem.

Ninad S. Pundalik
http://ninadpundalik.co.cc/blog
GPG Key Fingerprint: 2DF7 B856 C75E C9F9 0504 C0EF D456 1946 7C45 2C69

-- 
ubuntu-in mailing list
ubuntu-in@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-in


Re: [ubuntu-in] Continuing Problems with Huawei ETS2288

2009-03-27 Thread Moz
Hi Ram,

Your email is very well written and is specific, so I am reading it very 
carefully, but I am travelling so my response might be in pieces.


 ~$ sudo modprobe usbserial vendor=0x0451 product=0x3410

   
So far so good. But why did you not give the mknod command right after 
this, before configuring wvdial

 PPPD Options = crtcts multilink usepeerdns lock defaultroute
   
Wonder why you need PPPD options. I don't with my ETS1201. But there is 
a spelling error above. Did you copy-paste? It should be crtscts.
 Then tried the options given by Moz and Onkar

 1 Made a file called
 :~$ sudo gedit /etc/rc.local

 Added the following lines (without the -S and the path to the password file)
 sudo modprobe usbserial vendor=0x0451 product=0x3410
 sudo mknod /dev/ttyUSB0 c 188 0
 sudo mknod /dev/ttyUSB1 c 188 1
 exit 0

   
I am currently using the above, but without any modifications to any 
/etc/modprobe.d/ . I did that because it might conflict. But no idea. I 
also tried everything else, but only the above (without any other 
modifications) works.
 Then checked to see if there was a file called /dev/ttyUSB0

 this is the result
  -$ls /dev/ttyu*
 /dev/ttyu0  /dev/ttyu3  /dev/ttyu6  /dev/ttyu9  /dev/ttyuc  /dev/ttyuf
 /dev/ttyu1  /dev/ttyu4  /dev/ttyu7  /dev/ttyua  /dev/ttyud
 /dev/ttyu2  /dev/ttyu5  /dev/ttyu8  /dev/ttyub  /dev/ttyue

 So no ttyUSB0 or 1
   
You did not look for ttyUSB0, you looked for something with ttyu*, which 
is different than ttyU*.
 While setting up in 7.10 the following are the things done
 dmesg

 the lines below are dmesg output from 7.10 (note the difference)
 #kr# error message that i get

 [  646.188000] ti_usb_3410_5052 2-1:1.0: TI USB 3410 1 port adapter
 converter detected
 [  646.188000] ti_usb_3410_5052: probe of 2-1:1.0 failed with error -5
 [  646.188000] usb 2-1: device_add(2-1:1.0) -- -5

 after which a rules file is setup
 Now we have to make one rule file in
 /etc/udev/rules.d/026_ti_usb_3410.rules . with the following lines
 #TI USB 3410

 SUBSYSTEM==usb_device ACTION==add
 SYSFS{idVendor}==0451,SYSFS{idProduct}==3410 \

 SYSFS{bNumConfigurations}==2 \

 SYSFS{bConfigurationValue}==1 \

 RUN+=/bin/sh -c 'echo 2  /sys%p/device/bConfigurationValue'

 after which when dmesg is queried we get
 dmesg

  ti_usb_3410_5052 1-2:2.0: TI USB 3410 1 port adapter converter detected
 [ 2081.24] usb 1-2: TI USB 3410 1 port adapter converter now
 attached to ttyUSB0
 [ 2081.356000] ti_usb_3410_5052_1 ttyUSB0: TI USB 3410 1 port adapter
 converter now disconnected from ttyUSB0
 [ 2081.356000] ti_usb_3410_5052 1-2:2.0: device disconnected
 [ 2081.364000] ti_usb_3410_5052 1-2:2.0: TI USB 3410 1 port adapter
 converter detected
 [ 2081.364000] usb 1-2: TI USB 3410 1 port adapter converter now
 attached to ttyUSB0

 and then the device works well.

 ***
 So the question is what is this
 [ 1642.274280] firmware: requesting ti_usb-3410.bin

 and why am i getting the /dev/ttyUSB0 error

 Since there are many devices being setup would like to know if anyone
 has got this device ets2288 working on Ubuntu 8.04 or 8.10
   
I have been using ETS1201 under Ubuntu 8.04 (64 bit) and earlier under 
Ubuntu 8.10 (32 bit) for months now. And in between I also used it under 
Kubuntu 8.10 for a short while. And I had no problems. I had problems 
only when I tinkered with the config as per advice by Onkar, and my 
internet connection stopped working. But I do think that that is a more 
correct way of doing, only that someone more knowledgeable than me has 
to figure out the exact method, I can not do that.

Warm regards

Moz


-- 
ubuntu-in mailing list
ubuntu-in@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-in