Terry, The bottom of the Howto or the Readme (not with my Linux resources now) specifies a line to implement automation, with which $ sudo modprobe agrserial will read instructions from a /etc/modprobe.d/agrmodem file and sequentially do: modprobe agrmodem modprobe agrserial which co creates the /dev/ttyAGR3 ln -s /dev/ttyAGR3 /dev/ttySAG3 which sets a symbolic link /dev/ttySAG3 --> /dev/ttyAGR3 The latter is desirable because wvdialconf will follow the symbolic to /dev/ttyAGR3 But you can alternately should proceed again with the manual driver loading and then: $ sudo ln -s /dev/ttyAGR3 /dev/ttySAG3 after which $ sudo wvdialconf /etc/wvdial.conf will hopefully find the modem. This recognition step is where some Systems fail, and then the follow through steps desccribed in the HowTo have to be tested. If the modem is found, use $ sudo wvdialconf /etc/wvdial.conf to edit in your dialout info. Subsequently try a a dialout with: $ sudo wvdial MarvS On Feb 16, 2008 2:56 AM, tgillett@xxxxxxxxxxxxxx <tgillett@xxxxxxxxxxxxxx> wrote: > Thanks to Marvin and Marcus for pointing me to the sv92 packages. > > I have downloaded and installed as per the Readme.1st file in the package. > This has resulted in the creation of ttyAGS3 in /dev similar to the entries > for ttyS0, 1, 2, 3 as shown below. > > crw-rw---- 1 root dialout 62, 67 2008-02-16 19:24 ttyAGS3 > > crw-rw---- 1 root dialout 4, 64 2008-02-16 19:25 ttyS0 > crw-rw-rw- 1 root tty 3, 49 2008-02-16 19:14 ttys1 > > I don't know where to go next. (Just new to Linux!) > > Is this the expected outcome of the installation? > > What should I do to try to test the modem? > wvdialconf looks for a modem on ttyS0 and ttyS1, but doesn't know about > ttyAGS3 > > Also ttyAGS3 disappears on reboot, but re-appears after the modprobe steps: > > $ sudo modprobe agrmodem > $ sudo modprobe agrserial > $ lsmod | grep agr > agrserial 13872 0 > agrmodem 1188580 1 agrserial > > What do I need to do to make it permanent? > > Thanks again for your help > > Regards > Terry > > > On Fri Feb 15 17:51 , "Marvin Stodolsky" sent: > > > > Use the latest agrsm package at > http://linmodems.technion.ac.il/packages/ltmodem/sv92/ > > The package has good documentation. > Report back to the List if you have problems. > Hugo is the expert, not me. > > MarvS > > On Feb 15, 2008 3:37 PM, tgillett@xxxxxxxxxxxxxx > <tgillett@xxxxxxxxxxxxxx> wrote: > > Hi Marvin > > Thanks for your help. > > I have attached the ModemData.txt file. > > Regards > > Terry > > > > > > > > On Sat Feb 16 1:06 , 'Marvin Stodolsky' sent: > > > > > > > > Terry, > > > > There was no attachment. > > Also please send us the entire ModemData.txt output. > > The ltmodem/martian and SV92P code support entirely different modem > chips. > > There are occassion mislabelings of modem packages. So we need the > > entire ModemData.txt > > > > MarvS > > scanModem maintainer > > > > On Thu, Feb 14, 2008 at 7:19 PM, tgillett@xxxxxxxxxxxxxx > > <tgillett@xxxxxxxxxxxxxx> wrote: > > > > > > Hello > > > > > > I have been trying to get a Dynalink PCI modem board with the Agere > SV92P > > chipset > > > working, following the HowTo page at Ubuntu > > > (https://help.ubuntu.com/community/DialupModemHowto\) which in turn > took > > me to > > > linmodems and the scanModem pages. > > > > > > The modem is detected as the Agere SV2P as follows in ModemData.txt as > > shown below. > > > > > > I have installed the Lucent driver as per the instructions here: > > > https://help.ubuntu.com/community/DialupModemHowto/Lucent > > > > > > and the modem is happily detected by wvdialconf as /dev/ttyLTM0. > > > > > > However when I attempt to dial out, it can't get dial tone (see wvdial > > output below). > > > > > > I have seen a number of older references to the SV92P chipset not being > > supported > > > under Linux, however it seems that the SV2P driver is communicating > with > > the modem. > > > > > > My question is: should the SV92P based board work with the SV2P driver? > > > Or am I wasting my time with it? > > > > > > Thanks in advance for any help on this. > > > > > > Terry > > > > > > >
