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 baudrate 230400 (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 ...
