Hi Marvin I followed your excellent HowTo document and everything worked as it should until I cam eto the wvdial test which gave the following result: ******************************** ~$ sudo wvdialconf /etc/wvdial.conf 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 -- failed with 2400 baud, next try: 9600 baud ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. Modem Port Scan<*1>: S2 S3 ttySAGR<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttySAGR<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttySAGR<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. Sorry, no modem was detected! Is it in use by another program? Did you configure it properly with setserial? Please read the FAQ at http://open.nit.ca/wiki/?WvDial If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>. ********************************************* I also tried with the 'no acpi' and turning the sound card off in the BIOS suggested remedies with the same result. I can't see that there is anything else to try or test. It's the end of the road for this board (Dynalink 1456VQH) as a Linux modem I think. What I am still surprised about is that the SV2 driver allowed wvdial to find the board and get all the necessary responses to set up the wvconf file. It only failed when I came to make it dial out. I wonder if the remedies might help make that work?? Anyway thanks for all your help. Regards Terry On Sat Feb 16 19:10 , 'Marvin Stodolsky' <marvin.stodolsky@xxxxxxxxx> sent: >It is in the package, the agrsm-howto attached > > > >On Feb 16, 2008 6:50 PM, Marvin Stodolsky marvin.stodolsky@xxxxxxxxx> wrote: > >> $ sudo ln -s /dev/ttyAGS3 /dev/modem > >> and > >> $ sudo ln -s /dev/ttyAGS3 /dev/ttySAG3 > >> ------- > >> because wvdialconf only tests /dev/modem and /dev/ttyS* ports > >> > >> If the /dev/modem link did not suffice, your System probably has the > >> commonly encountered problem. I'll send you the HowTo later. It > >> should have been in the agrsm package, but just checking, it was > >> somehow omitted. > >> > >> MarvS > >> > >>
