Linmodems Mailing list Archives

Mailing-List: contact discuss-help@linmodems.org; run by ezmlm
Date: Sun, 16 Jun 2002 16:23:35 +0400
From: Nikolai Zhubr <s001@hotbox.ru>
Message-ID: <1864419567.20020616162335@hotbox.ru>
To: "Daniel Silva" <sildani@yunque.com>
CC: discuss@linmodems.org
Subject: Re: Conexant chipset internal modem
In-reply-To: <000001c214e2$54ff5820$24f958d1@desktop>
References: <000001c214e2$54ff5820$24f958d1@desktop>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,
Sunday, 16 June, 2002, 7:03:02, Daniel Silva wrote:
>[...]
> list.  I don't think there is much else I can do, pray someone reading
> this know what I have done wrong, or where I can go from here, and would
I'm not specifically familiar with conexant modems but I guess it
is true for any *winmodem* that modem functionality including
interpreting AT commands and most of other stuff is implemented in
a software driver, not in hardware, as you seem to expect.
The plain serial driver that comes with linux kernel is not a modem
driver by itself and perhaps has really nothing to do with it.
You need to install a dedicated driver for specific chipset, much
like on Windows (Though winmodem drivers can be included in windows
disribution so you could not notice the point).
IIRC support for some conexant chipsets appeared recently. Please
search the list arch for 'conexant' to find related URLs.
Hope this helps a bit.
-- 
Best regards,
 Nikolai Zhubr

> Hail to all,

> I am in need of some help.  I am new to the Linux world, and I am
> struggling to successfully configure my modem.

> I have an Intel Pentium III 733 PC with 384MB RAM, and on it I have
> Windows XP Professional and Red Hat Linux 7.3 installed (dual-boot).
> The device in question is a Creative Labs Modem Blaster DI5633 56k
> v.92/v.90 internal PCI modem with a Conexant chipset (a winmodem,
> unfortunately).  I have an AGP video card (GeForce3 Ti200), a PCI
> network card (Linksys standard 10/100), and a PCI SoundBlaster sound
> card.  The video, networking, and sound cards were all configured
> properly automatically during installation of Red Hat Linux 7.3.  The
> modem, alas, was not. :)

> This is what I have done (by reading many documents online) to try and
> configure the modem:

> 1. ran cat /proc/pci to see my devices.  Sure enough, there it is, PCI
> Bus 0 Device 13 function 0 IRQ 5 I/O Addresses 0xb000 - 0xb007.  It is
> recognized as a Conexant modem (my modem has this chipset).

> 2. ran setserial -g /dev/ttyS* to get a listing of my serial port setup.
> Of interest, I will note some of the findings...
> ttyS0 I/O 0x03f8 IRQ 4
> ttyS1 I/O 0x02f8 IRQ 3
> ttyS2 I/O 0x03e8 IRQ 4
> ttyS3 I/O 0x02e8 IRQ 3
> ttyS8 I/O 0x02a0 IRQ 5
> ttyS9 I/O 0x02a8 IRQ 5
> ttyS10 I/O 0x02b0 IRQ 5
> ttyS11 I/O 0x02b8 IRQ 5

> 3. ran setserial -v /dev/ttyS2 uart 16550A port 0xb000 irq 5 autconfig
> The result is:
> /dev/ttyS2, UART: Unknown, PORT: 0xb000, IRQ: 5
> Because of the failure to configure the UART properly, I conclude that
> it can't find the built-in serial port on the modem.  I admit this may
> be wrong, however...

> 4. ran minicom -s, configured it to run on serial port ttyS2, 115200
> baud, 8N1.  It can initialize the modem fine (or so it seems...).
> However when I type AT, I get no response from the port.  I turned on
> local echo just to make sure I was typing it right.  I also tried ATA,
> ATE1 (to turn on echo on the device).  I have the actual AT command text
> file printed, I tried all sorts of stuff but nothing.

> Besides the above, I also tried re-setting some of the other ttySn
> devices that were using IRQ 5 to something else, in the case of an IRQ
> conflict, but that didn't help.  My BIOS is set to auto config the PCI
> slots, as well as notifying it I don't have a PnP OS.  In Windows it
> works fine with the driver on COM3, at the same PCI settings (IRQ and
> I/O). Also worthy of noting is that I use a USB mouse, and I know the
> USB bridge is on IRQ 5, which may have something to do with it.  On that
> end I tried to force the modem to go on IRQ 3 but Linux (and Windows)
> still forced the modem on IRQ 5 COM3.  Finally, I tried removing the
> symbolic link off of /dev/modem and after all the above linking
> /dev/ttyS2 to /dev/modem and then trying to access it through there.  No
> luck.  Nada.

> After 3 days of troubleshooting, I am about ready to give up and buy a
> new external hardware modem that's already on the Linux compatibility
> list.  I don't think there is much else I can do, pray someone reading
> this know what I have done wrong, or where I can go from here, and would
> be kind enough to let me know (and save me the $80 on a new piece of
> legacy hardware).  I just don't believe it can't work, I mean, it's just
> a device that has a serial port, something has got to give!!

> That's all folks.  Thanks in advance for all the input I can get.

> Regards,
> Dan Silva from Fajardo, Puerto Rico
Webmaster: Russell Nelson
Last modified: Wed Jul 30 11:02:43 EDT 2003