Mark, Perhaps you can give Tom some local guidance to the parts market. Tom, > My work involves setting up discarded corporate machines for use by refugee > families, and while Linux is ideal in many ways, peripheral support is an area of > weakness due to the proprietary nature of things like Winmodems. > > Overall I have come to the conclusion that PCI modem boards are to be avoided for > use with Linux, PCI cards per se are not the culprit. The problems reside in the particular CHIPSET on the board. For > setting up discarded corporate machines for use by refugee families, the best solution would probably a Controller Chipset (same type used in external modems) on a PCI board. The drivers are in every Linux release. Read the InfoGeneral.txt and WWW search for a cheapest source of such modems. AgereSystems (now LSI) simply isn't putting profit free effort into the Linux maintenance of this particular SV92 softmodem. When they have acquired large commercial buyers of their other chipsets to sponsor code maintenance, support of those chipsets has been quite good. MarvS On Feb 18, 2008 5:06 AM, tgillett@xxxxxxxxxxxxxx <tgillett@xxxxxxxxxxxxxx> wrote: > Hi Jacques > Thanks for your reply, it is appreciated. > I understand what you are saying about wvdial recognising only /etc/dev/ttyS* > however my problem now is that even though ttyAGS3 exists and I have made the > link to ttySAGR, wvdial is unable to communicate with the modem board at all. > Curiously the SV2 driver finds the board and communicates with it, but it won't > dial, however the SV92 driver does not. Strange. > > Overall I have come to the conclusion that PCI modem boards are to be avoided for > use with Linux, which is unfortunate, as they provide a nice solution compared to > a separate serial modem. > Also the problem can be unavoidable in the case of a laptop with built in modem. > > My work involves setting up discarded corporate machines for use by refugee > families, and while Linux is ideal in many ways, peripheral support is an area of > weakness due to the proprietary nature of things like Winmodems. > > I have to admit that I probably haven't taken the best approach to finding the > relevant information, however I have trawled through an awful lot of material on > getting modems going under Linux, much of which is out of date and contradictory. > > Thanks again for your pointer to the information. > > Regards > Terry > > On Mon Feb 18 20:59 , Jacques Goldberg <Jacques.Goldberg@xxxxxxx> sent: > > > >Dear Tgillett > > > >In your previous mail you ask how to make ttyAGS3 permanent. > >modprobe should be sufficient unless this module is in your blacklist > > > >In the present mail you report that wvdialconf has not found ttyAGS3 > >This feature is built in wvdialconf which will ONLY scan devices whose > >names follow the following pattern: > >/dev/ttyS* > >You might have discovered this yourself by reading through point 9 of > >the first section "for the impatient" of > >http://linmodems.technion.ac.il/post-install.html > >Likewise http://linmodems.technion.ac.il offers a searchable archive. > >If in the 2008 archive you search for ttyAGS3, the first item in archive > >beyond your own posts shows the solution. > >These remarks were not a criticism, but a hint how to go faster without > >waiting for an answer. > > > >Once /dev/ttyAGS3 exists, do > >ln -s /dev/ttyAGS3 /dev/ttySanything ,such as /dev/ttySAG3 for example > >for mnemonics > > > >Next, run wvdialconf which will find the modem. > >Next, while anyway editing /etc/wvdial.conf, replace your > >/dev/ttySanything by /dev/ttyAGS3 and wvdial will work without having > >to repeat the linking (command ln -s) next time. > > > >Jacques > > >
