Re: [Cooker] minicom and ppp broken for pcmcia modems

2002-05-28 Thread Steven J Mackenzie

andrej wrote
==
> My problem is that neither minicom, nor the ifup/usernetctl command line
> tools can communicate with the modem. As root, minicom starts, but the
> modem does not reply "OK" to the initialisation string, or to "AT".
==

> First, do not post in HTML. Second, what strace shows?
>
> strace -f -o /tmp/foo minicom

Thanks for the tips.

I tested 2 minicoms, minicom.mdk, (renamed from the Mandrake RPM minicom),
and minicom.sjm that I built from the source out of the SRPM.

They both used the same minirc.dfl configuration file:
pr port/dev/ttyS1   [[[WRONG]]]
pu baudrate230400

(It looks like I configured this wrongly, the pr port value should be
/dev/ttyS2.)

The strace logs are both big. The only obvious difference to my eyes is that
the minicom.sjm opened /dev/modem, ignoring the config file.

On my computer /dev/modem is linked to /dev/tts/2, which is correct, which
is why my compiled version worked. Odd behaviour, but I can't claim the
minicom rpm package is broken any more, as both versions of minicom now work
with a corrected minirc.dfl.

Which leaves me stumped about why "ifup ppp0" is not working:
May 28 23:37:14 waterloo ifup-ppp: pppd started for ppp0 on /dev/modem at
115200
May 28 23:37:14 waterloo pppd[12382]: pppd 2.4.1 started by root, uid 0
May 28 23:37:15 waterloo pppd[12382]: Connect script failed
May 28 23:37:16 waterloo pppd[12382]: Exit.

I think I'll sleep on it ...









RE: [Cooker] minicom and ppp broken for pcmcia modems

2002-05-28 Thread Borsenkow Andrej


===š
My PCMCIA net card works fine, and the modems both work with kppp (ie,
the hardware is fine!). I have configured my modem and ppp scriptsšfrom
a shellšusing netconf.
š
My problem is that neither minicom, nor the ifup/usernetctl command line
tools can communicate with the modem. As root, minicom starts, but the
modem does not reply "OK" to the initialisation string, or to "AT".
===
[...]
===
What would I need to recompile to get ifup working (I *need* this ...)?
I tried ppp, but it didn't make any difference.


First, do not post in HTML. Second, what strace shows?

strace -f -o /tmp/foo minicom

And what is in /tmp/foo?

-andrej 




[Cooker] minicom and ppp broken for pcmcia modems

2002-05-28 Thread Steven J Mackenzie

[Reposted in plain text]

This is a bug I spotted after installing MD8.2 on an old laptop. (Yes, I
have seen the hotplug errata :)  The same version of minicom and ppp are in
cooker still, I think.

My laptop (HP Omnibook CS5500) has PCMCIA bridge Cirrus Logic CL6729 (rev
e2). The PCMCIA modem card is a Pace NB56 56K card. I also have a Prolink
1436C 33.6K card, which behaves the same way. (These are both full hardware
modems and work fine with kppp.)

My PCMCIA net card works fine, and the modems both work with kppp (ie, the
hardware is fine!). I have configured my modem and ppp scripts from a shell
using netconf.

My problem is that neither minicom, nor the ifup/usernetctl command line
tools can communicate with the modem. As root, minicom starts, but the modem
does not reply "OK" to the initialisation string, or to "AT".

ifup leaves this message in the logs:
May 13 08:47:09 waterloo ifup-ppp: pppd started for ppp0 on /dev/modem at
115200
May 13 08:47:09 waterloo pppd[2375]: pppd 2.4.1 started by root, uid 0
May 13 08:47:11 waterloo pppd[2375]: Connect script failed
May 13 08:47:12 waterloo pppd[2375]: Exit.

Note that the script has "failed" before an attempt to dial a number.

If I create and install a new minicom RPM (rpm -ba minicom.spec) from the
SRPM, minicom is still broken. If I just extract the raw minicom source from
the SRPM and compile that (./configure, make), then then minicom works
fine -- the Mandrake rpm build script is doing something that stops minicom
from communicating with my PCMCIA modem.

What would I need to recompile to get ifup working (I *need* this ...)? I
tried ppp, but it didn't make any difference.

Steven





[Cooker] minicom and ppp broken for pcmcia modems

2002-05-28 Thread Steven J Mackenzie



This is a bug I spotted after installing MD8.2 on 
an old laptop. (Yes, I have seen the hotplug errata :)  The same version of minicom and ppp are in cooker still, I 
think.
 
My laptop (HP Omnibook CS5500) has PCMCIA 
bridge Cirrus Logic CL6729 (rev e2). The PCMCIA modem card is a Pace NB56 
56K card. I also have a Prolink 1436C 33.6K card, which behaves the same way. 
(These are both full hardware modems and work fine with kppp.)
 
My PCMCIA net card works fine, and the modems both 
work with kppp (ie, the hardware is fine!). I have configured my modem and ppp 
scripts from a shell using netconf.
 
My problem is that neither minicom, nor the 
ifup/usernetctl command line tools can communicate with the modem. As root, 
minicom starts, but the modem does not reply "OK" to the initialisation string, 
or to "AT".
 
ifup leaves this message in the logs:
May 13 08:47:09 waterloo ifup-ppp: pppd started for 
ppp0 on /dev/modem at 115200May 13 08:47:09 waterloo pppd[2375]: pppd 2.4.1 
started by root, uid 0May 13 08:47:11 waterloo pppd[2375]: Connect script 
failedMay 13 08:47:12 waterloo pppd[2375]: Exit.
Note that the script has "failed" before an attempt 
to dial a number.
 
If I create and install a new minicom RPM (rpm -ba 
minicom.spec) from the SRPM, minicom is still broken. If I just extract the raw 
minicom source from the SRPM and compile that (./configure, make), then then 
minicom works fine -- the Mandrake rpm build script is doing something that 
stops minicom from communicating with my PCMCIA modem.What would I need 
to recompile to get ifup working (I *need* this ...)? I tried ppp, but it didn't 
make any difference.
 
Steven