[ubuntu-in] Continuing Problems with Huawei ETS2288

[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 <listmoz at 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