Ocitno ne beres vse maile, povedal sem, da je modem I-courier in da v
minicomu vse AT komande, ki jih uporabljam za init string delajo.
cu
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Nejc Skoberne
Sent: Monday, September 25, 2000 3:23 PM
To: [EMAIL PROTECTED]
Subject: Re: [ LUGOS ] mgetty
> 09/24 23:27:52 yS0 send: ATZ[0d]
> 09/24 23:27:53 yS0 waiting for ``OK''
> 09/24 23:27:53 yS0 got: ATZ[0d]
> 09/24 23:28:13 yS0 timeout in chat script, waiting for `OK'
> 09/24 23:28:13 yS0 init chat timed out, trying force-init-chat
> 09/24 23:28:13 yS0 send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
> 09/24 23:28:17 yS0 waiting for ``OK''
> 09/24 23:28:17 yS0 got: [10][03]+++[0d]ATQ0V1H0[0d]
> 09/24 23:28:36 ##### failed dev=ttyS0, pid=3890, got signal 15,
To pomeni, da mgetty sploh ne more govoriti z modemom. (trying
force-init-chat)
Torej najprej preveri, ce je ttyS0 sploh pravi port (to je COM1), na
katerega je modem prikljucen. Ko to naredis, lahko sprobas tudi s
kaksnim terminal klientom (minicom) ce ti modem sploh odgovarja na AT
komande. Ko ti tudi to uspe, pogledas kaksen modem imas, pogledas
modemske specifikacije in sam napises init string, ki ga potrebuje tvoj
modem... ATS0=0X3 recimo... al kaj vem kaj... Vsekakor mora biti ATS0=0,
saj to preprica modem, da ne odgovarja na klice sam, ampak da mu sle
mgetty pove, kdaj mora to storiti. Ko tudi to naredis, pa bi morala
stvar zaceti pocasi delovati... mimogrede: ce ti uspe nastaviti
callback, mi sporoci :>
Nejk0
