Dear Ryan, In case you are not skilled enough in using Windows Explorer, activate a search on all *.log files on the Windows system disk and containing the string ATZ (exact case). This should help you quicker identifying the correspondant log file where to look after the AT commands Windows uses to successfully connect you to Internet. This ought to give you hints on the relevant AT commands you should enter into /etc/wvdial.conf and which should match your geographical and electrical situation. - http://vouters.dyndns.org:8080/ Philippe Vouters (Fontainebleau/France) Le vendredi 10 juillet 2009 à 22:40 +0200, Philippe Vouters a écrit : > Ryan, > > Use Windows Explorer and its search facility to make a search on all > C:\ of .log files. One of these is likely to be your modem log file. > - > http://vouters.dyndns.org:8080/ > Philippe Vouters (Fontainebleau/France) > > > Le vendredi 10 juillet 2009 à 20:57 +0100, Ryan a écrit : > > Philippe. > > > > How to I find out what AT commands Windows XP uses? > > > > Ryan > > ----- Original Message ----- > > From: "Philippe Vouters" <Philippe.Vouters@xxxxxxxxxxx> > > To: "Ryan" <ryanmckeown@xxxxxxxxxxx> > > Cc: "Marvin Stodolsky" <marvin.stodolsky@xxxxxxxxx>; "Antonio Olivares" > > <olivares14031@xxxxxxxxx> > > Sent: Friday, July 10, 2009 8:50 PM > > Subject: Re: NO DIALTONE > > > > > > Ryan, > > > > As you say your modem does work without no problem under Windows XP, > > please do attempt making your best to pick up from the exact AT commands > > Windows XP uses to successfully connect you to Internet. Once you > > discover these AT commands Windows XP uses you will be able to introduce > > them in your Init strings in the /etc/wvdial.conf file. > > - > > http://vouters.dyndns.org:8080/ > > Philippe Vouters (Fontainebleau/France) > > > > > > Le vendredi 10 juillet 2009 à 20:28 +0100, Ryan a écrit : > > > Philippe, Marvin, Antonio. > > > > > > I am very interested in the idea of Marvin's. > > > There are no problems with the wires connecting my modem to the phone > > > line. > > > I know this because I have 2 operating systems installed (Ubuntu and > > > Windows) and my modem works perfectly fine in my Windows XP OS as I am > > > connected to the internet even now to send you this email. > > > > > > My home is in the countryside and as far as I know the "phone central" is > > > not anywhere near where I live. I wouldn't say that I am in the most rural > > > place imaginable, but Northern Ireland (Irlande du Nord en français) is > > > not > > > exactly the > > > most urban place. Also, the sound from my telephone when making a phone > > > call > > > is slightly disrupted (there is a slight crackle at times), but this never > > > effects Windows XP at all. > > > > > > > > > Thank you Marvin for that input, you may be onto something. > > > Hope this helps. > > > Ryan > > > > > > ----- Original Message ----- > > > From: "Philippe Vouters" <Philippe.Vouters@xxxxxxxxxxx> > > > To: "Marvin Stodolsky" <marvin.stodolsky@xxxxxxxxx> > > > Cc: "Ryan" <ryanmckeown@xxxxxxxxxxx>; "Antonio Olivares" > > > <olivares14031@xxxxxxxxx> > > > Sent: Thursday, July 09, 2009 3:58 PM > > > Subject: Re: [Fwd: Re: New Intel 537EP .tar.bz2] > > > > > > > > > Ryan, > > > > > > Marv's suggestion looks at first glance to be very relevant. This ought > > > to be even more relevant if your home is located in the countryside and > > > far away from the phone central. Another symptom of it would eventually > > > (I am not sure) a poor audio quality using your phone apparatus when > > > hearing and speaking to a correspondant. > > > > > > Yours sincerely, > > > - > > > http://vouters.dyndns.org:8080/ > > > Philippe Vouters (Fontainebleau/France) > > > > > > > > > Le jeudi 09 juillet 2009 à 08:30 -0400, Marvin Stodolsky a écrit : > > > > Philippe, > > > > > > > > Commonly in Italy but more rarely elsewhere, low line voltage blocks > > > > dialtone detection. > > > > The sometimes cure in these cases is to put an X3 (dial without > > > > dialtone detection) in the Init2 line. > > > > > > > > Separately, I presume the hardware functions under Microsoft. > > > > > > > > MarvS > > > > > > > > On Thu, Jul 9, 2009 at 8:17 AM, Philippe > > > > Vouters<Philippe.Vouters@xxxxxxxxxxx> wrote: > > > > > Dear Ryan, > > > > > > > > > > A possibility which just came up to my mind is that you call your > > > > > phone > > > > > supplier requesting them to test your phone line while your 537EP > > > > > modem > > > > > connector is plugged in and is the only one apparatus connected to the > > > > > phone line. > > > > > > > > > > With their electrical tests, they ought to be able to detect short or > > > > > opened electrical circuits. > > > > > > > > > > Yours sincerely, > > > > > - > > > > > http://vouters.dyndns.org:8080/ > > > > > Philippe Vouters (Fontainebleau/France) > > > > > > > > > > > > > > > Le jeudi 09 juillet 2009 à 13:48 +0200, Philippe Vouters a écrit : > > > > >> Ryan, > > > > >> > > > > >> Since very recently I am aware of another identical as yours 537EP > > > > >> modem > > > > >> board owner I am in touch with. His current problem is that his > > > > >> computer > > > > >> looks to be suffering from IRQ conflicts causing both his 536EP and > > > > >> 537EP modems to be extremely slow in responding to AT commands. Once > > > > >> this slowliness is solved, I may request from him the very same > > > > >> tests. > > > > >> > > > > >> Yours sincerely, > > > > >> - > > > > >> http://vouters.dyndns.org:8080/ > > > > >> Philippe Vouters (Fontainebleau/France) > > > > >> > > > > >> > > > > >> -------- Message transféré -------- > > > > >> De: Philippe Vouters <Philippe.Vouters@xxxxxxxxxxx> > > > > >> À: Ryan <ryanmckeown@xxxxxxxxxxx> > > > > >> Sujet: Re: New Intel 537EP .tar.bz2 > > > > >> Date: Thu, 09 Jul 2009 13:02:15 +0200 > > > > >> > > > > >> Dear Ryan, > > > > >> > > > > >> Tapan never got yet his modem working as he owns a Silicon 537 > > > > >> [Winmodem] board which was NOT initially supported by the 537 driver. > > > > >> He > > > > >> is getting a "Can't initialize h/w" in dmesg because the Intel's > > > > >> binary > > > > >> code in 537core.lib fails to initialize his modem. Under Windows and > > > > >> from data from another such modem owner, the board is recognized as a > > > > >> Motorola SM56K modem. There used to be an SM56K Linux driver but > > > > >> unfortunately this was for very old Linux kernels and the driver > > > > >> could > > > > >> not evolve. > > > > >> > > > > >> As for you, your board is indeed fully supported by the 537 driver. > > > > >> The > > > > >> fact that both your efax and wvdial below tests invariably report a > > > > >> NO > > > > >> DIALTONE seems to put away any software problem. > > > > >> > > > > >> This would rather lead to a cabling problem between the modem and the > > > > >> phone line. efax looks to be extremely well and correctly behaving. > > > > >> > > > > >> Would you eventually foresee a test possibility to thorough test the > > > > >> cabling between your modem and your phone line ? For example, would > > > > >> it > > > > >> be possible for you to test the connection with your ISP using > > > > >> another > > > > >> modem cable ? Would it eventually happen you may plug the modem cable > > > > >> into your phone apparatus and check for the presence of the phone > > > > >> line > > > > >> tone ? Or using the very same cable and eventually the very same 537 > > > > >> board plugged into your very same computer under another operating > > > > >> system such as some version of Windows ? You might also consider > > > > >> checking the stacking of your phone connectors onto your phone line. > > > > >> For > > > > >> this, you could temporarily eliminate your phone apparatus connector > > > > >> from the phone line and directly plug your modem connector onto it. > > > > >> > > > > >> For all these cabling tests, you may repeat the provided efax command > > > > >> until you do no longer get a NO DIALTONE error. > > > > >> - > > > > >> http://vouters.dyndns.org:8080/ > > > > >> Philippe Vouters (Fontainebleau/France) > > > > >> > > > > >> > > > > >> Le jeudi 09 juillet 2009 à 11:10 +0100, Ryan a écrit : > > > > >> > Philippe. > > > > >> > > > > > >> > I changed the first line on my intel-536-537/537_boot to "#! > > > > >> > /bin/bash" and > > > > >> > ran: > > > > >> > $ sudo make uninstall > > > > >> > $ sudo make install > > > > >> > $ sudo /etc/init.d/537_boot status > > > > >> > > > > > >> > And here is the output: > > > > >> > ryan@Ryan:~$ cd intel-536-537 > > > > >> > ryan@Ryan:~/intel-536-537$ sudo gedit 537_boot > > > > >> > ryan@Ryan:~/intel-536-537$ sudo make uninstall > > > > >> > make[1]: Entering directory `/home/ryan/intel-536-537' > > > > >> > Uninstalling on system V boot like only. > > > > >> > killall usrsound || echo > > > > >> > usrsound: no process killed > > > > >> > > > > > >> > killall hamregistry || echo > > > > >> > hamregistry: no process killed > > > > >> > > > > > >> > rm -f /etc/rc.d/init.d/537_boot > > > > >> > rm -f /etc/hamregistry.bin > > > > >> > rm -f /usr/sbin/usrsound > > > > >> > rm -f /usr/sbin/hamregistry > > > > >> > rmmod Intel537 > > > > >> > rm -f `find /lib/modules -name Intel537.o` > > > > >> > rm -f `find /lib/modules -name Intel537.ko` > > > > >> > Uninstalling done. > > > > >> > make[1]: Leaving directory `/home/ryan/intel-536-537' > > > > >> > ryan@Ryan:~/intel-536-537$ sudo make install > > > > >> > make[1]: Entering directory `/home/ryan/intel-536-537' > > > > >> > rm -f /usr/sbin/hamregistry.bin > > > > >> > bash 537_inst > > > > >> > running kernel 2.6.28-11-generic > > > > >> > installing hamregistry, used for persistant storage > > > > >> > installing usrsound, a soft buzzer > > > > >> > installing 537 module > > > > >> > install DEBIAN 537 boot script and links > > > > >> > starting module and utilities > > > > >> > usrsound: no process killed > > > > >> > > > > > >> > hamregistry: no process killed > > > > >> > > > > > >> > done > > > > >> > make[1]: Leaving directory `/home/ryan/intel-536-537' > > > > >> > ryan@Ryan:~/intel-536-537$ sudo /etc/init.d/537_boot status > > > > >> > PID TTY TIME CMD > > > > >> > 3450 pts/0 00:00:00 hamregistry > > > > >> > PID TTY TIME CMD > > > > >> > 3453 ? 00:00:00 usrsound > > > > >> > ryan@Ryan:~/intel-536-537$ > > > > >> > > > > > >> > As you can see, the output to $ sudo /etc/init.d/537_boot status is > > > > >> > very > > > > >> > similar to yours. It also suggest usrsound is now running, (which I > > > > >> > think > > > > >> > was the objective). > > > > >> > > > > > >> > Therefore, I was feeling hopefull when I again ran wvdial but, > > > > >> > unfortunatly, > > > > >> > it still return the NO DIALTONE error: > > > > >> > ryan@Ryan:~/intel-536-537$ sudo wvdial > > > > >> > --> WvDial: Internet dialer version 1.55 > > > > >> > --> Initializing modem. > > > > >> > --> Sending: ATZ > > > > >> > --> Sending: ATQ0 > > > > >> > --> Re-Sending: ATZ > > > > >> > ATZ > > > > >> > OK > > > > >> > --> Initializing modem. > > > > >> > --> Sending: ATZ > > > > >> > ATZ > > > > >> > OK > > > > >> > --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=2 > > > > >> > ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=2 > > > > >> > OK > > > > >> > --> Sending: ATM2L3 > > > > >> > ATM2L3 > > > > >> > OK > > > > >> > --> Modem initialized. > > > > >> > --> Sending: ATDT08440575000 > > > > >> > --> Waiting for carrier. > > > > >> > ATDT08440575000 > > > > >> > NO DIALTONE > > > > >> > --> No dial tone. > > > > >> > --> Disconnecting at Thu Jul 9 10:38:55 2009 > > > > >> > ryan@Ryan:~/intel-536-537$ > > > > >> > > > > > >> > > > > > >> > I tried to send myself a fax using efax and here is what that looks > > > > >> > like: > > > > >> > ryan@Ryan:~$ cd efax > > > > >> > ryan@Ryan:~/efax$ ./efax -vewinchmart -t <MY PHONE NUMBER> README > > > > >> > ./efax: Thu Jul 9 10:40:28 2009 efax v 0.9a-001114 Copyright 1999 > > > > >> > Ed > > > > >> > Casas > > > > >> > ./efax: Thu Jul 9 10:40:28 2009 efax v 0.9a-001114 Copyright 1999 > > > > >> > Ed > > > > >> > Casas > > > > >> > efax: 40:28 compiled Jun 19 2009 11:00:46 > > > > >> > efax: 40:28 using built-in 128x0 font > > > > >> > efax: 40:28 argv[0]=./efax > > > > >> > efax: 40:28 argv[1]=-vewinchmart > > > > >> > efax: 40:28 argv[2]=-t > > > > >> > efax: 40:28 argv[3]=02837551305 > > > > >> > efax: 40:28 argv[4]=README > > > > >> > efax: 40:28 using built-in 128x0 font > > > > >> > efax: 40:30 opened /dev/modem > > > > >> > efax: 40:30 command "Q0V1" > > > > >> > efax: 40:30 waiting 2.0 s > > > > >> > efax: 40:34 command "Q0V1" > > > > >> > efax: 40:34 waiting 2.0 s > > > > >> > efax: 40:34 .395 [ATQ0V1<CR><CR><LF>] > > > > >> > efax: 40:34 .463 [OK<CR><LF>] > > > > >> > efax: 40:34 response "OK" > > > > >> > efax: 40:34 command "E0" > > > > >> > efax: 40:34 waiting 5.0 s > > > > >> > efax: 40:34 .483 [ATE0<CR><CR><LF>] > > > > >> > efax: 40:34 .535 [OK<CR><LF>] > > > > >> > efax: 40:34 response "OK" > > > > >> > efax: 40:34 command "I3" > > > > >> > efax: 40:34 waiting 5.0 s > > > > >> > efax: 40:34 .583 [<CR><LF>537EP <CR><LF>] > > > > >> > efax: 40:34 .603 [<CR><LF>OK<CR><LF>] > > > > >> > efax: 40:34 response "OK" > > > > >> > efax: 40:34 command "+FCLASS=?" > > > > >> > efax: 40:34 waiting 5.0 s > > > > >> > efax: 40:34 .656 [<CR><LF>0,1,2,2.0,8<CR><LF>] > > > > >> > efax: 40:34 .675 [<CR><LF>OK<CR><LF>] > > > > >> > efax: 40:34 response "OK" > > > > >> > efax: 40:34 command "+FCLASS=2.0" > > > > >> > efax: 40:34 waiting 5.0 s > > > > >> > efax: 40:34 .743 [<CR><LF>OK<CR><LF>] > > > > >> > efax: 40:34 response "OK" > > > > >> > efax: 40:34 command "+FMI?" > > > > >> > efax: 40:34 waiting 5.0 s > > > > >> > efax: 40:34 .795 [<CR><LF>Intel Corporation<CR><LF>] > > > > >> > efax: 40:34 .815 [<CR><LF>OK<CR><LF>] > > > > >> > efax: 40:34 response "OK" > > > > >> > efax: 40:34 command "+FMM?" > > > > >> > efax: 40:34 waiting 5.0 s > > > > >> > efax: 40:34 .863 [<CR><LF>Intel V92 Data Fax Voice<CR><LF>] > > > > >> > efax: 40:34 .863 [<CR><LF>H.324 video-ready rev. 1.0<CR><LF>] > > > > >> > efax: 40:34 .883 [<CR><LF>OK<CR><LF>] > > > > >> > efax: 40:34 response "OK" > > > > >> > efax: 40:34 command "+FMR?" > > > > >> > efax: 40:34 waiting 5.0 s > > > > >> > efax: 40:34 .935 [<CR><LF>RSA REV 4.04 <CR><LF>] > > > > >> > efax: 40:34 .955 [<CR><LF>OK<CR><LF>] > > > > >> > efax: 40:34 response "OK" > > > > >> > efax: 40:34 using 537EP Intel Corporation Intel V92 Data Fax Voice > > > > >> > RSA REV > > > > >> > 4.04 in class 2.0 > > > > >> > efax: 40:34 command "+FIP" > > > > >> > efax: 40:34 waiting 5.0 s > > > > >> > efax: 40:35 .015 [<CR><LF>ERROR<CR><LF>] > > > > >> > efax: 40:35 response "ERROR" > > > > >> > efax: 40:35 Warning: wrong response after command: +FIP > > > > >> > efax: 40:35 command "+FNR=1,1,1,0" > > > > >> > efax: 40:35 waiting 5.0 s > > > > >> > efax: 40:35 .083 [<CR><LF>OK<CR><LF>] > > > > >> > efax: 40:35 response "OK" > > > > >> > efax: 40:35 command "+FLO=1" > > > > >> > efax: 40:35 waiting 5.0 s > > > > >> > efax: 40:35 .155 [<CR><LF>OK<CR><LF>] > > > > >> > efax: 40:35 response "OK" > > > > >> > efax: 40:35 command "+FBO=0" > > > > >> > efax: 40:35 waiting 5.0 s > > > > >> > efax: 40:35 .223 [<CR><LF>OK<CR><LF>] > > > > >> > efax: 40:35 response "OK" > > > > >> > efax: 40:35 command "+FCR=1" > > > > >> > efax: 40:35 waiting 5.0 s > > > > >> > efax: 40:35 .295 [<CR><LF>OK<CR><LF>] > > > > >> > efax: 40:35 response "OK" > > > > >> > efax: 40:35 command "+FIS?" > > > > >> > efax: 40:35 waiting 5.0 s > > > > >> > efax: 40:35 .443 [<CR><LF>1,5,0,2,0,0,0,0<CR><LF>] > > > > >> > efax: 40:35 .463 [<CR><LF>OK<CR><LF>] > > > > >> > efax: 40:35 response "OK" > > > > >> > efax: 40:35 command "+FLI=" "" > > > > >> > efax: 40:35 waiting 5.0 s > > > > >> > efax: 40:35 .635 [<CR><LF>OK<CR><LF>] > > > > >> > efax: 40:35 response "OK" > > > > >> > efax: 40:35 dialing 02837551305 > > > > >> > efax: 40:35 command "D02837551305" > > > > >> > efax: 40:35 waiting 120.0 s > > > > >> > efax: 40:45 .883 [<CR><LF>NO DIALTONE<CR><LF>] > > > > >> > efax: 40:45 response "NO DIALTONE" > > > > >> > efax: 40:45 Error: dial command failed > > > > >> > efax: 40:45 failed -> README > > > > >> > efax: 40:45 failed -> README > > > > >> > efax: 40:45 command "Q0V1" > > > > >> > efax: 40:45 waiting 2.0 s > > > > >> > efax: 40:45 .963 [<CR><LF>OK<CR><LF>] > > > > >> > efax: 40:45 response "OK" > > > > >> > efax: 40:46 command "H" > > > > >> > efax: 40:46 waiting 5.0 s > > > > >> > efax: 40:46 .823 [<CR><LF>OK<CR><LF>] > > > > >> > efax: 40:46 response "OK" > > > > >> > efax: 40:46 done, returning 2 (unrecoverable error) > > > > >> > ryan@Ryan:~/efax$ > > > > >> > > > > > >> > As you can see, the response was not like yours with the "efax: > > > > >> > 24:03 > > > > >> > done, > > > > >> > returning 1 (number busy or modem in use)", but it did return > > > > >> > "efax: > > > > >> > 40:45 > > > > >> > response "NO DIALTONE"" > > > > >> > > > > > >> > I made a file /home/ryan/wvdial.conf with the following inside: > > > > >> > [Modem0] > > > > >> > Modem = /dev/modem > > > > >> > Dial Command = ATDT > > > > >> > Init1= ATZ > > > > >> > #Init2 = AT+GCI=3D > > > > >> > Baud = 115200 > > > > >> > Init3 = ATM1L3 > > > > >> > SetVolume = 0 > > > > >> > FlowControl = CRTSCTS > > > > >> > Carrier Check = no > > > > >> > [Dialer tiscali] > > > > >> > Username = <My ISP Username> > > > > >> > Password = <My ISP password> > > > > >> > Phone = <My ISP phone number> > > > > >> > #Stupid Mode = 1 > > > > >> > Init1 = ATZ > > > > >> > Inherits = Modem0 > > > > >> > > > > > >> > and ran the command $ sudo wvdial --config ./wvdial.conf tiscali > > > > >> > with > > > > >> > the > > > > >> > following response: > > > > >> > --> WvDial: Internet dialer version 1.55 > > > > >> > --> Initializing modem. > > > > >> > --> Sending: ATZ > > > > >> > ATZ > > > > >> > OK > > > > >> > --> Sending: ATM1L3 > > > > >> > ATM1L3 > > > > >> > OK > > > > >> > --> Modem initialized. > > > > >> > --> Sending: ATDT08440575000 > > > > >> > --> Waiting for carrier. > > > > >> > ATDT08440575000 > > > > >> > NO DIALTONE > > > > >> > --> No dial tone. > > > > >> > --> Disconnecting at Thu Jul 9 10:47:36 2009 > > > > >> > ryan@Ryan:~$ > > > > >> > > > > > >> > > > > > >> > Can you help me any further? > > > > >> > By the way, did that Tapan fellow ever get his modem working, I > > > > >> > remember you > > > > >> > mentioning that he had a similar problem to me. > > > > >> > > > > > >> > Ryan. > > > > >> > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
