Linmodems Mailing list Archives
Return-Path: <goldberg@phep2.technion.ac.il>
Mailing-List: contact discuss-help@linmodems.org; run by ezmlm
Delivered-To: mailing list discuss@linmodems.org
Received: (qmail 11597 invoked from network); 9 Oct 2002 19:07:54 -0000
Received: from techunix.technion.ac.il (132.68.1.28)
by www.linmodems.org with SMTP; 9 Oct 2002 19:07:54 -0000
Received: from phep2.technion.ac.il (phep2.technion.ac.il [132.68.64.53])
by techunix.technion.ac.il (Postfix) with ESMTP
id 57479154C2; Wed, 9 Oct 2002 21:07:29 +0200 (IST)
Date: Wed, 9 Oct 2002 21:07:28 +0200 (IST)
From: Jacques Goldberg <goldberg@phep2.technion.ac.il>
Reply-To: Jacques Goldberg <Jacques.Goldberg@cern.ch>
To: evm@mail.nascentnde.com
Cc: LinModems <discuss@linmodems.org>
Subject: Re: Software vs hardware [Was: Lucent V92 softmodem: NO DIALTONE]
In-Reply-To: <3DA47AE1.43BE69A2@rcn.com>
Message-ID: <Pine.LNX.4.05_heb2.08.10210092056240.29234-100000@phep2.technion.ac.il>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Wed, 9 Oct 2002, Marvin Stodolsky wrote:
[see below] and Marvin is of course right.
What Eugene (and he is not alone) seems not to know is that a modem
driver can always be loaded in memory just as any other program, and the
keyboard and display can talk with the software just loaded, thus many
AT.. commands work, because they talk with the driver software only, not
with the chipset.
But when it comes to ATD (dial), of course, it will never work, because
the hardware (chipset) is only correctly operated by the driver software
written for that specific chipset, which, as Marv writes, does not (yet)
exist in the present case. The driver sends your ATD.. commands "in the
air", to nothing existing, waits for the DIAL TONE which will never come
because no signal was created on the phone line nor detected, and gives up
after some time.
> Eugene,
>
> Regrettable this:
> -----------------
> ***lspci -nv:
> 01:04.0 Class 0780: 11c1:048c(rev 02)
> Subsystem: 11c1:044c
> ----------------
> is an AMR soft modem not supported by the DSP chipset ltmodem drivers.
> Agere has not projected a date for their support of these AMR chipset
> modems.
>
>
> VendorID:DeviceID == PCI_IDs of AC '97 soft modem slots
> ==================================================================
> Vendor
> ------
> ALI 10b9:5450 10b9:5457
> Intel 8086:2416* 8086:2426 8086:2446* 8086:2486* 8086:7196
> VIA 1106:3068* - some supported by PCTEL or Conexant drivers
> SIS 1039:7013 - some supported by PCTEL drivers
> Lucent 11c1:048c 11c1:048e 11c1:048f - Linux service not yet
> available inOct, 2002
>
> -------------------------------------------------------------------------------
> Possible support by drivers available at:
> * Conexant - http://www.mbsi.ca/cnxtlindrv/hsf/index.html
> PCTEL - http://pctelcompdb.sourceforge.net/
>
> ===================
>
> MarvS
> ltmodem co-maintainer
>
> >evm wrote:
> >
> > Hi,
> >
> > I recently bought an Acorp M-56ISL softmodem with Lucent chipset
> > and trying to make it work under Linux.
> >
> > In brief, ltmodem driver installs, I can talk to modem without any problems,
> > but I keep getting a NO DIALTONE message.
> >
> > I have gathered ALL the information from the Internet about Linmodems
> > including "ltmodem-8.22a5" driver.
> >
> > I successfully compiled and installed the driver under Red Hat 7.3
> > with kernel 2.4.18-3 (have source).
> >
> > After I start wvdial, minicom or kppp driver successfully loads, I can talk
> > to it, retrieve its settings with AT&V, set whatever I want, but nothing solves
> > the NO DIALTONE problem.
> >
> > Finally, I am in Ukraine. I tried various t.35 country codes (no Ukrainian one)
> > but this didn't help. I also tried a ATH1 command - no success.
> > Changing my BIOS to non-PnP seems impossible in my situation.
> >
> > What else can I do? Maybe something in the driver itself?
> >
> > Below are some command outputs to judge about my driver:
> >
> > ***tail -f /var/log/messages:
> > Oct9 11:26:56 localhost kernel: Loading Lucent Modem Controller driver version 8.22
> > Oct9 11:26:56 localhost kernel: Detected Parameters Irq=10 BaseAddress=0xc400 ComAddress=0xc000
> > Oct9 11:26:56 localhost kernel: Lucent Modem Interface driver version 8.22 (2002-04-11) with SHARE_IRQ enabled
> > Oct9 11:26:56 localhost kernel: ttyLT00 at 0xc400 (irq = 10) is a Lucent Modem
> > ***lsmod:
> > lt_serial 20768 0 (autoclean)
> > lt_modem 529019 0 (autoclean) [lt_serial]
> >
> > ***cat/proc/interrupts:
> > 0: 100413 XT-PIC timer
> > 1: 2219 XT-PIC keyboard
> > 2: 0 XT-PIC cascade
> > 8: 1 XT-PIC rtc
> > 9: 0 XT-PIC ehci-hcd
> >10: 0 XT-PIC usb-uhci
> >11: 0 XT-PIC usb-uhci, usb-uhci
> >12: 13990 XT-PIC PS/2 Mouse
> >14: 17246 XT-PIC ide0
> >15: 5924 XT-PIC ide1
> >
> > (The last shows that IRQ 10 is used by usb modules but my problem does
> > not go away when I unload them).
> >
> > ***lspci -v:
> > 01:04.0 Communication controller: Lucent Microelectronics: Unknown device 048c (rev 02)
> > Subsystem: Lucent Microelectronics: Unknown device 044c
> > Flags: bus master, medium devsel, latency 32, IRQ 10
> > Memory at ed001000 (32-bit, non-prefetchable) [size=256]
> > I/O ports at c000 [size=8]
> > I/O ports at c400 [size=256]
> > Capabilities: [f8] Power Management version 2
> >
> > ***lspci -nv:
> > 01:04.0 Class 0780: 11c1:048c (rev 02)
> > Subsystem: 11c1:044c
> > Flags: bus master, medium devsel, latency 32, IRQ 10
> > Memory at ed001000 (32-bit, non-prefetchable) [size=256]
> > I/O ports at c000 [size=8]
> > I/O ports at c400 [size=256]
> > Capabilities: [f8] Power Management version 2
> >
> > Thank you for any help,
> > Eugene Malyarenko
> >
> > evm@nascentnde.com
>
Jacques.Goldberg@cern.ch
>>>> Currently at TECHNION <<<<
PHONE: Technion=+(972)(0)(4)829.36.63
CERN=+(41)(22)767.73.85
FAX: Technion=+(972)(0)(4)829.36.68
CERN=+(41)(22)767.31.00
HOME: Haifa=+(972)(4)825.29.04
GSM portable: +(972)(0)54.29.36.63
Webmaster: Russell Nelson
Last modified: Wed Jul 30 11:02:43 EDT 2003