Hi,
This below pasted, is the output from wvdial.conf
Thanks much, as always.
Henry
- - - - - - - - - - - - - ->
henry@henry-heron:~$ sudo wvdialconf /etc/wvdial.conf
[sudo] password for henry:
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS1<*1>: ATQ0 V1 E1 -- OK
ttyS1<*1>: ATQ0 V1 E1 Z -- OK
ttyS1<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyS1<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyS1<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyS1<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyS1<*1>: Modem Identifier: ATI -- 5601
ttyS1<*1>: Speed 4800: AT -- OK
ttyS1<*1>: Speed 9600: AT -- OK
ttyS1<*1>: Speed 19200: AT -- OK
ttyS1<*1>: Speed 38400: AT -- OK
ttyS1<*1>: Speed 57600: AT -- OK
ttyS1<*1>: Speed 115200: AT -- OK
ttyS1<*1>: Max speed is 115200; that should be safe.
ttyS1<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
Modem Port Scan<*1>: S3
Found a modem on /dev/ttyS1.
Modem configuration written to /etc/wvdial.conf.
ttyS1<Info>: Speed 115200; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
henry@henry-heron:~$
<- - - - - - - - - - - - - - - - - - - -
At 02:58 PM 7/27/2008, you wrote:
Send us your wvdial.conf , with
Password = XXXXXX
On Sun, Jul 27, 2008 at 2:12 PM, Henry W. Peters
<hwpeters@xxxxxxxxxxxx> wrote:
> Ok, Marv, I *think* I have the parameters set up correctly (?) on my Ubuntu
> system. Still get the hang-up after a few seconds of mutual (presumably)
> handshake. From the concerns you sent (below included) what is the (your)
> recommended course of action?
>
> Thanks,
>
> Henry
> p.s. the modem tried to dial up before I was logged in... I take it this
> would not be a usual event?
>
>
> At 10:23 PM 7/26/2008, Marvin Stodolsky wrote:
>>
>> Henry,
>>
>> The info below may/maynot be cogent to your US robotics Controller
>> chipset modem.
>> Unless a failure is encoutered, assume it is not.
>>
>> There is alternate support for the 11c1:0620 Agere modem,
>> but a bit more difficult to implement.
>>
>> MarvS
>> scanModem maintainer
>>
>>
>> ---------- Forwarded message ----------
>> From: <jb1@xxxxxxxxxxxx>
>> Date: Fri, Jul 25, 2008 at 4:55 PM
>> Subject: kernel 2.6.25 serial port bug [continued]
>> To: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>
>> Cc: btech@xxxxxxxxxxxxxxxxxxxx
>>
>>
>> Another thread discussing the kernel 2.6.25 serial port bug has
>> appeared in the minicom discussion group,"minicom 2.3 (which termcap)
>> and kernel 2.6.25.1 (DTR)". The original post:
>> http://lists.alioth.debian.org/pipermail/minicom-devel/2008/000872.html
>> implies a fairly specific way to detect the bug (and find the faulty
>> code) using minicom. The second post:
>> http://lists.alioth.debian.org/pipermail/minicom-devel/2008/000873.html
>> states, "The 8250 drivers in versions 2.6.25 through 2.6.25.7 are
>> broken. 2.6.25.8 (and later) works." I don't know R.L. Horn except
>> through his posts on this topic, but he seems quite knowledgable.
>>
>> If any of the developers or, worse yet, the modem manufacturers have
>> emulated the faulty 8250 code it might explain the difficulties and
>> inconsistencies they're encountering under 2.6 kernels. I've also
>> noticed a few users reporting problems setting up their wvdial init
>> strings; maybe some of these are related to the problem described in
>> the first minicom post above.
>>
>> A correction to my previous message (shown below): minicom is a
>> text-only *serial terminal* program, not a *browser* ... DUH!.
>>
>>
>> On Wed, 2 Jul 2008, jb1@xxxxxxxxxxxxxxxxxxxx wrote:
>>
>> > It seems that the linmodem developers are having more difficulty than
>> > usual adapting their code to recent kernels. Some time ago you
or Jacques
>> > posted a message about the kernel rejecting non-GPL modules;
now the kernel
>> > developers have introduced a bug into the serial driver in at
least some of
>> > the 2.6.25 kernels! I stumbled across three threads in the minicom
>> > discussion group. They all seem to be the same problem, but
the "subject"
>> > evolved as its nature became better understood. Here are the "original
>> > posts" of the threads:
>> > http:
>> > //lists.alioth.debian.org/pipermail/minicom-devel/2008/000849.html
>> > http:
>> > //lists.alioth.debian.org/pipermail/minicom-devel/2008/000850.html
>> > http:
>> > //lists.alioth.debian.org/pipermail/minicom-devel/2008/000852.html
>> > In case you're unfamiliar with it, "minicom" is a text-only command-line
>> > browser.
>> >
>> > It seems unlikely that the linmodem drivers would be directly affected
>> > by the bug, but the developers should at least be aware of it. I vaguely
>> > remember someone with a *hardware* modem reporting difficultly
configuring
>> > wvdial; maybe it was due to this bug.
>> >
>> > I've sent this message to you alone because I doubt that it would be of
>> > much use to the whole group but of course you may do with it
as you wish. As
>> > always, thank you, Jacques, et. al., for your great work.
>> >
>> > P.S.
>> > There's a typo in the scanModem.gz I downloaded a few minutes ago. The
>> > second line contains a space before the "y" in your last name.
>
>
>
