Issues with Huawei E122 3G Modem (on Ubuntu 10.04)

[mvip]

Hi guys,

I'm having some major issues with my Huawei E122 3G modem. I've tried other 3G modems (such as E1750 and E180), but this card is just giving me a ton of headache. I would like to get the E122 running with wvdial (which I have gotten to work with the other cards w/out any problem on this same computer).

I've installed the regular tools, such as usb-modeswitch, and I have even gotten the modem to work using Network Manager, but it's far from stable. After configuring it inNetwork Manager to auto-connect I can get online. After shutting down the computer and booting it, it can connect properly on one boot, and then flat out refuse the next time around. And no, it's not a reception issue, as the computer is on the exact same spot.

Have anyone been able to get this modem running with wvdial? I've spent a ton of time researching this, and a few people claim to have gotten it running, but I haven't found any fully working wvdial config.

From the system log when plugged in:

1420.960035] usb 1-4: new high speed USB device using ehci_hcd and address 14
[ 1421.093232] usb 1-4: configuration #1 chosen from 1 choice
[ 1421.093949] scsi38 : SCSI emulation for USB Mass Storage devices
[ 1421.094201] usb-storage: device found at 14
[ 1421.094207] usb-storage: waiting for device to settle before scanning
[ 1421.094790] scsi39 : SCSI emulation for USB Mass Storage devices
[ 1421.095043] usb-storage: device found at 14
[ 1421.095050] usb-storage: waiting for device to settle before scanning
[ 1422.783181] usb 1-4: USB disconnect, address 14
[ 1427.068055] usb 1-4: new high speed USB device using ehci_hcd and address 15
[ 1427.200774] usb 1-4: config 1 interface 1 altsetting 0 bulk endpoint 0x85 has invalid maxpacket 256
[ 1427.200783] usb 1-4: config 1 interface 1 altsetting 0 bulk endpoint 0x5 has invalid maxpacket 256
[ 1427.200791] usb 1-4: config 1 interface 2 altsetting 0 bulk endpoint 0x86 has invalid maxpacket 256
[ 1427.200798] usb 1-4: config 1 interface 2 altsetting 0 bulk endpoint 0x6 has invalid maxpacket 256
[ 1427.201471] usb 1-4: configuration #1 chosen from 1 choice
[ 1427.202232] option 1-4:1.0: GSM modem (1-port) converter detected
[ 1427.202537] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB0
[ 1427.203383] option 1-4:1.1: GSM modem (1-port) converter detected
[ 1427.203881] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB1
[ 1427.204694] option 1-4:1.2: GSM modem (1-port) converter detected
[ 1427.204941] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB2
[ 1427.205730] scsi43 : SCSI emulation for USB Mass Storage devices
[ 1427.206205] usb-storage: device found at 15
[ 1427.206213] usb-storage: waiting for device to settle before scanning
[ 1427.206815] scsi44 : SCSI emulation for USB Mass Storage devices
[ 1427.207052] usb-storage: device found at 15
[ 1427.207058] usb-storage: waiting for device to settle before scanning

Output from 'lsusb'. Note that it is identified as a E620 which is actually a PCMCIA modem. This one is a USB dongle.

....
Bus 001 Device 015: ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem
....

I also ran the Network Manager in debug mode, and this is what I got from the log when it successfully connected:

** Message: Modem /org/freedesktop/ModemManager/Modems/4: state changed (disabled -> enabling)
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'ATZ E0 V1 +CMEE=1<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'ATE0 +CMEE=1<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'ATX4 &C1<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG=0<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CFUN=1<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>OK<CR><LF>'
** Message: Modem /org/freedesktop/ModemManager/Modems/4: state changed (enabling -> enabled)
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CPIN?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CPIN: READY<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+COPS=0,,<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: Registration state changed: 2
** Message: Modem /org/freedesktop/ModemManager/Modems/4: state changed (enabled -> searching)
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,4<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: Registration state changed: 4
** Message: Modem /org/freedesktop/ModemManager/Modems/4: state changed (searching -> enabled)
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,4<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CREG?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CREG: 0,5<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: Registration state changed: 5
** Message: Modem /org/freedesktop/ModemManager/Modems/4: state changed (enabled -> registered)
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+COPS=3,2;+COPS?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+COPS: 0,2,"24004",2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+COPS=3,0;+COPS?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+COPS: 0,0,"SWEDEN",2<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CSQ<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CSQ: 20,99<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'AT+CGDCONT?<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>+CGDCONT: 1,"IP","data.tre.se","",0,0<CR><LF>+CGDCONT: 2,"IP","bredband.tre.se","",0,0<CR><LF><CR><LF>OK< CR><LF>'
** Message: Modem /org/freedesktop/ModemManager/Modems/4: state changed (registered -> connecting)
** (modem-manager:2111): DEBUG: (ttyUSB0): --> 'ATD*99***2#<CR>'
** (modem-manager:2111): DEBUG: (ttyUSB0): <-- '<CR><LF>CONNECT 7200000<CR><LF>'
** Message: Modem /org/freedesktop/ModemManager/Modems/4: state changed (connecting -> connected)

Update: The modem is actually an "E122-2" and not "E122, which is pointed out below.

[mvip]

I just managed to get a log-snippet from Network Manager when the modem failed to connect.

** Message: (ttyUSB0) opening serial device...
** (modem-manager:1896): DEBUG: (ttyUSB0): probe requested by plugin 'Huawei'
** (modem-manager:1896): DEBUG: (ttyUSB0): --> 'AT+GCAP<CR>'
** (modem-manager:1896): DEBUG: (ttyUSB0): <-- '<CR><LF>+GCAP: +CGSM,+DS,+ES<CR><LF><CR><LF>OK<CR><LF>'
** Message: (ttyUSB0) closing serial device...
** Message: (Huawei): GSM modem /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-4 claimed port ttyUSB0
** (modem-manager:1896): DEBUG: Added modem /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-4
** (modem-manager:1896): DEBUG: Exported modem /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-4 as /org/freedesktop/ModemManager/Modems/1
** (modem-manager:1896): DEBUG: (ttyUSB2): re-checking support...
** Message: (ttyUSB2) opening serial device...
** (modem-manager:1896): DEBUG: (ttyUSB1): re-checking support...
** Message: (ttyUSB1) opening serial device...
** (modem-manager:1896): DEBUG: (ttyUSB2): <-- '<CR><LF>^SIMST:0,0<CR><LF>'
** Message: (ttyUSB2) closing serial device...
** Message: (ttyUSB1) closing serial device...
** Message: (ttyUSB2) opening serial device...
** (modem-manager:1896): DEBUG: (ttyUSB2): probe requested by plugin 'Generic'
** Message: (ttyUSB1) opening serial device...
** (modem-manager:1896): DEBUG: (ttyUSB1): probe requested by plugin 'Generic'
** (modem-manager:1896): DEBUG: (ttyUSB2): --> 'AT+GCAP<CR>'
** (modem-manager:1896): DEBUG: (ttyUSB1): --> 'AT+GCAP<CR>'
** (modem-manager:1896): DEBUG: (ttyUSB2): <-- '<CR><LF>+GCAP: +CGSM,+DS,+ES<CR><LF><CR><LF>OK<CR><LF>'
** Message: (ttyUSB2) closing serial device...

** (modem-manager:1896): CRITICAL **: mm_modem_base_add_port: assertion `port == NULL' failed

** (modem-manager:1896): WARNING **: do_grab_port: plugin 'Generic' claimed to support tty/ttyUSB2 but couldn't: (-1) (unknown)
** (modem-manager:1896): DEBUG: (ttyUSB1): --> 'AT+GCAP<CR>'
** (modem-manager:1896): DEBUG: (ttyUSB1): --> 'AT+GCAP<CR>'
** Message: (ttyUSB1) closing serial device...

This is what the system log showed when removing and re-inserting the modem:

[ 232.332028] usb 1-4: new high speed USB device using ehci_hcd and address 8
[ 232.464774] usb 1-4: config 1 interface 1 altsetting 0 bulk endpoint 0x85 has invalid maxpacket 256
[ 232.464783] usb 1-4: config 1 interface 1 altsetting 0 bulk endpoint 0x5 has invalid maxpacket 256
[ 232.464791] usb 1-4: config 1 interface 2 altsetting 0 bulk endpoint 0x86 has invalid maxpacket 256
[ 232.464798] usb 1-4: config 1 interface 2 altsetting 0 bulk endpoint 0x6 has invalid maxpacket 256
[ 232.465348] usb 1-4: configuration #1 chosen from 1 choice
[ 232.466199] option 1-4:1.0: GSM modem (1-port) converter detected
[ 232.466468] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB0
[ 232.467021] option 1-4:1.1: GSM modem (1-port) converter detected
[ 232.467224] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB1
[ 232.467750] option 1-4:1.2: GSM modem (1-port) converter detected
[ 232.467943] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB2
[ 232.470339] scsi17 : SCSI emulation for USB Mass Storage devices
[ 232.470565] usb-storage: device found at 8
[ 232.470573] usb-storage: waiting for device to settle before scanning
[ 232.471066] scsi18 : SCSI emulation for USB Mass Storage devices
[ 232.471283] usb-storage: device found at 8
[ 232.471290] usb-storage: waiting for device to settle before scanning
[ 237.468350] usb-storage: device scan complete
[ 237.468526] usb-storage: device scan complete
[ 237.468824] scsi 18:0:0:0: Direct-Access HUAWEI SD Storage 2.31 PQ: 0 ANSI: 2
[ 237.468942] scsi 17:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2
[ 237.470321] sd 18:0:0:0: Attached scsi generic sg2 type 0
[ 237.477063] sd 18:0:0:0: [sdc] Attached SCSI removable disk
[ 237.477948] sr0: scsi-1 drive
[ 237.479355] sr 17:0:0:0: Attached scsi CD-ROM sr0
[ 237.482780] sr 17:0:0:0: Attached scsi generic sg3 type 5
[ 248.071881] sr0: CDROM (ioctl) error, command: Xpwrite, Read disk info 51 00 00 00 00 00 00 00 02 00
[ 248.071907] sr: Sense Key : Hardware Error [current]
[ 248.071915] sr: Add. Sense: No additional sense information

[gradinaruvasile]

Try sakis3g:

http://www.sakis3g.org/

[mvip]

Try sakis3g:

http://www.sakis3g.org/

Thanks Gradinaruvasile. I just tried Sakis3G and it chokes too. I'm starting to believe more and more that this is a kernel issue. This is what I'm getting from Sakis3G.

$ sudo ./sakis3g connect --scanyes
Modem unable to register a network.

Anyone else got experience with this particular modem? I have seven of these modems that are supposed to go in boxes to be used for remote-access. It would suck a lot to have to buy seven new modems just because of this.

[mvip]

I just found this article written by a guy who claims to have gotten the modem to work.

After installing ModeSwitch, he used this wvdial config:

[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Init3 = AT+CGDCONT=1,”IP”,”internet”
Stupid Mode = 1
ISDN = 0
Modem Type = Analog Modem
Phone = *99#
Modem = /dev/ttyUSB0
Username = NA
Dial Command = ATDT
Password = pass
Baud = NA

However, when I run that, I get the following:

--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> 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
COMMAND NOT SUPPORT
--> Sending: ATQ0
ATQ0
OK
--> Re-Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
COMMAND NOT SUPPORT
--> Modem not responding.

For the record, the modem should be on ttyUSB0:

$ dmesg |grep ttyUSB0
[ 5.897888] usb 1-8: GSM modem (1-port) converter now attached to ttyUSB0

[mvip]

*bump*

[mvip]

So turns out the modem is of the model E122-2. The "-2"-part probably changes quite a bit and it was written very in a dark color on the modem that is only readable from an angle. It says "E122" in white, but turns out the "-2" part is very important. Since then I found this bug-report from a user getting the same kind of behavior.

Still no luck with wvdial though.

[gradinaruvasile]

Thanks Gradinaruvasile. I just tried Sakis3G and it chokes too. I'm starting to believe more and more that this is a kernel issue. This is what I'm getting from Sakis3G.



Anyone else got experience with this particular modem? I have seven of these modems that are supposed to go in boxes to be used for remote-access. It would suck a lot to have to buy seven new modems just because of this.

The idea with sakis3g is that the kernel is not necessarily supposed to know the device. I used sakis3g with modems that could not be even switched by the kernel.

Try this:

launch sakis3g with the following command line:

sudo sakis3g --console --interactive

First select "prepare modem" and then connect. If you are asked for user and password, you MUST enter something (it doesnt matter what) in those boxes, at least 1 character for both user and password. Of course, if you have user+password required for your connection, you should enter the credentials.

Something that might be related:
http://ubuntuforums.org/showthread.php?t=1583103&page=2

[mvip]

The idea with sakis3g is that the kernel is not necessarily supposed to know the device. I used sakis3g with modems that could not be even switched by the kernel.

Try this:

launch sakis3g with the following command line:

sudo sakis3g --console --interactive

First select "prepare modem" and then connect. If you are asked for user and password, you MUST enter something (it doesnt matter what) in those boxes, at least 1 character for both user and password. Of course, if you have user+password required for your connection, you should enter the credentials.

Something that might be related:
http://ubuntuforums.org/showthread.php?t=1583103&page=2

Right, but if you read the code for sagis3g, you'll find it is using usb-modeswitch. I already got the modem working that far. The problem is rather the AT commands.

[alexfish]

this post may be related

http://ubuntuforums.org/showthread.php?t=1666341

mvip can post detail of these commands from the terminal (when not working)

Codes:

uname -a

ls -al /dev/serial/by-id

usb-devices

locate the lines which indicate the device and post only those lines

also need to see the status of the modem lines : here is a small script to do this

#!/bin/sh
# the next line restarts using tclsh\
exec tclsh "$0" "$@"
set serial [open "/dev/ttyUSB0" "r+"]
fconfigure $serial -mode "115200,n,8,1"
fconfigure $serial -blocking 0 -buffering full -ttycontrol {RTS 0 DTR 1}
after 300
set stat [fconfigure $serial -ttystatus]
puts $stat
close $serial
# edit the '/dev/tty*' to suite and check all. the modem lines will show CTS 1 DSR 1 RING 0 DCD 0 or CTS 1 DSR 1 RING 0 DCD 1
################################################## ###
to run this script successfully do so from a fresh boot without the device
when running the script ensure to select run from terminal

connect the device allow the device to settle, do not try connecting

then ensure nothing in the way

Codes:

sudo poff

sudo killall modem-manager

then run the script and note the outputs : edit the script for each port as listed by
the ls -al /dev/serial/by-id command

Added: if every thing is checking out then there is a script in attachments
this will check the eventhandle response reliability

please read through the script , any queries , Please send PM

alexfish