LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Sorry, no modem was detected! Is it in use by another program? GPRS Modem (https://www.linuxquestions.org/questions/linux-hardware-18/sorry-no-modem-was-detected-is-it-in-use-by-another-program-gprs-modem-4175446553/)

pls_help_URGENT 01-21-2013 03:04 AM

Sorry, no modem was detected! Is it in use by another program? GPRS Modem
 
Don't have a serial port attached to my CPU, so I am using a cable connected to USB port which in turn is connected to a USB to Serial converter which in turn in connected to the GPRS modem.

openSUSE 11.4 64 bit
Kernel - 2.6.37.1-1.2-desktop

Code:

# dmesg | grep ttyUSB
[ 3327.741132] usb 5-2: pl2303 converter now attached to ttyUSB0

Code:

# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 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 002 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
Bus 005 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port

Code:

# wvdialconf /etc/wvdial.conf
Editing `/etc/wvdial.conf'.

Scanning your serial ports for a modem.

Modem Port Scan<*1>: S0  S1  S2  S3  S4  S5  S6  S7 
WvModem<*1>: Cannot set information for serial port.
ttyUSB0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyUSB0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyUSB0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.


Sorry, no modem was detected!  Is it in use by another program?
Did you configure it properly with setserial?

Please read the FAQ at http://open.nit.ca/wiki/?WvDial

If you still have problems, send mail to <wvdial-list@lists.nit.ca>.

Code:

~ zgrep -i CONFIG_PPP_MPPE /proc/config.gz
CONFIG_PPP_MPPE=y

Code:

# cat /etc/wvdial.conf

[Dialer Defaults]
Modem = /dev/ttyUSB0
Baud = 19200
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2
Init3 =
Area Code =
Phone = 0
Username =
Password =
Ask Password = 0
Dial Command = ATDT
Stupid Mode = 1
Compuserve = 0
Force Address =
Idle Seconds = 300
DialMessage1 =
DialMessage2 =
ISDN = 0
Auto DNS = 1

Have tried using minicom. It doesn't show any characters as an output of the modem.

This modem has been tested on a Windows machine and it does respond well.

The ONLY fields I have edited in wvdial.conf are Modem and Baud.

business_kid 01-21-2013 04:26 AM

I would first check if any kernel module sees it.
Quote:

lsusb -v |tail -n 25
gets you the l;ast screenful. Look for the 'kernel module in use: ' line.

Presuming some kernel module sees the modem, interrogate the port with setserial and ask, or set the baudrate. man setserial is your friend.

pls_help_URGENT 01-21-2013 04:43 AM

Quote:

Originally Posted by business_kid (Post 4874563)
gets you the l;ast screenful. Look for the 'kernel module in use: ' line.

Thanks, but couldn't see any word named kernel here:

Code:

linux-trra:~ # lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 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 002 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
Bus 005 Device 005: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port


Code:

Bus 005 Device 005: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Device Descriptor:
  bLength                18
  bDescriptorType        1
  bcdUSB              1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass        0
  bDeviceProtocol        0
  bMaxPacketSize0        8
  idVendor          0x067b Prolific Technology, Inc.
  idProduct          0x2303 PL2303 Serial Port
  bcdDevice            2.00
  iManufacturer          0
  iProduct                0
  iSerial                0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                9
    bDescriptorType        2
    wTotalLength          39
    bNumInterfaces          1
    bConfigurationValue    1
    iConfiguration          0
    bmAttributes        0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                9
      bDescriptorType        4
      bInterfaceNumber        0
      bAlternateSetting      0
      bNumEndpoints          3
      bInterfaceClass      255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                7
        bDescriptorType        5
        bEndpointAddress    0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type              None
          Usage Type              Data
        wMaxPacketSize    0x000a  1x 10 bytes
        bInterval              1
      Endpoint Descriptor:
        bLength                7
        bDescriptorType        5
        bEndpointAddress    0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type              None
          Usage Type              Data
        wMaxPacketSize    0x0040  1x 64 bytes
        bInterval              0
      Endpoint Descriptor:
        bLength                7
        bDescriptorType        5
        bEndpointAddress    0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type              None
          Usage Type              Data
        wMaxPacketSize    0x0040  1x 64 bytes
        bInterval              0
Device Status:    0x0000
  (Bus Powered)


business_kid 01-21-2013 12:05 PM

Quote:

Thanks, but couldn't see any word named kernel here:
#$@%£! Sorry, I didn't check that.
Previous versions had a 'kernel module in use: whatever' line. It's probably going to be a kernel issue
usb modules handle a usb port, serial modules handle a standard serial port (8250 or 16550) but for usb over serial, there's more modules. Find your kernel config (config-KernelVersion in /boot or .config in the kernel source) and run this check

grep CONFIG_USB_SERIAL_PL2303 <your config> to see if it's compiled in
or scour the output of 'lsmod' for something that looks like it.

If you don't have it, you'll need to recompile the kernel with that in.

ferrari 01-22-2013 03:54 AM

Is there a chance that you need a "null modem" cable (or inline adapter)? (ie maybe the TX and RX lines need to be swapped over). I've seen issues like this when using minicom to connect various network devices (for serial console connectivity).


All times are GMT -5. The time now is 12:15 AM.