Jacques, Many thanks for your help. 1. version 1.61 2. I haven't tried CTRL-C, but had tried tabbing to another window without success. 3. I have waited maybe a minute - and I know in the past I have waited a couple of minutes - shall I try again and wait/ try CTRL-C? The last tip didn't hang my laptop, so I have included the output below. When I looked to see if I could access the ttyS16 as a modem using mosSerial, all the ttySn devices were listed - except ttyS16! What should I try now?! Many thanks for your help, it's greatly appreciated. Kind Regards, Ian ian@ian-laptop:~$ wvdialconf --version WvDialConf 1.61 Copyright (c) 1997-2005 Net Integration Technologies, Inc. ian@ian-laptop:~$ sudo ln -sf /dev/ttyAGS3 /dev/ttyS16 [sudo] password for ian: ian@ian-laptop:~$ sudo wvdialconf wvtest.conf Editing `wvtest.conf'. Scanning your serial ports for a modem. Modem Port Scan<*1>: S0 S1 S2 S3 S4 S5 S6 S7 Modem Port Scan<*1>: S8 S9 S10 S11 S12 S13 S14 S15 Modem Port Scan<*1>: S16 S17 S18 S19 S20 S21 S22 S23 Modem Port Scan<*1>: S24 S25 S26 S27 S28 S29 S30 S31 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://alumnit.ca/wiki/?WvDial On 29/08/11 14:44, Jacques Goldberg wrote: > Ian, > > I am getting old. I just suddenly remember that I got mad, long ago, > trying to help somebody, with wvdialconf hanging up on my own computer > with no modem installed. I got rid of the problem using an older > version of wvdialconf. The difference was that the older would only > scan /dev/ttyS* addresses while the newer one also looked for USB, > ACM, ISDN and perhaps other devices. > Remembering that, I just downloaded the source code for wvdialconf. > Analyzing it I already have three trivial questions to ask you, please > forgive me for such stupid questions: > 1-Which version are you using? The command wvdialconf --version > gives the answer > 2-When the computer hangs, just where you at least tried to give a > carriage return, have you tried to give CTRL C (that is hit C while > holding down the CTRL key)? > 3-This one comes from an other user: have you tried to wait, doing > nothing after having started wvdialconf , for at least one timed > minute, a feeling of the time elapsed is not enough, just to make > sure that it does not come back to life without intervention? That > user had observed that the additions beyond the basic /dev/ttyS* > pattern cause wvdialconf to silently work for quite a bit of time > before reporting null results. > > From the photo there is something puzzling. It shows a device named > /dev/ttyAGS3 (yellow), probably created when loading the driver, > linked to an object /dev/ttySAGR for the obvious and unique purpose > of respecting the old convention of naming serial ports according to > /dev/ttyS<something> . If my hint that wvdialconf hangs AFTER having > completed scanning for /dev/ttyS* , and therefore having failed to > find /dev/ttySAGR, I can see at least two reasons: the driver does not > correctly create /dev/ttyAGS3 , or, the version of wvdialconf which > you use insists that /dev/ttyS<something> requires a number withing > some range for <something>. > > Elder readers who remember the early days of the Lucent driver > LTMODEM from which is some way your driver is derived will > understand why in your place I would give this a try: > Once only, sudo ln -sf /dev/ttyAGS3 /dev/ttyS16 > S16 exists and is never used, so choose S16 and link with a force > (the f in -sf) to override its current definition > Try wvdialconf again to see if before hanging (or not) it will find > your modem as /dev/ttyS16 or not. > > Jacques > > > On 08/29/2011 11:35 AM, Ian Smith wrote >> Marvin, >> >> Up to the wvdialconf command, the text below was from the console - >> after the wvdialconf command, the laptop froze - and I hav > >
