Kevanf1 wrote:

On 11/08/05, Bernie Gardner <bernie.gardner@umb.edu> wrote:

...

I've been trying to set up suse 9.2 pro on a friends computer for several months. Everything seems to work ok except the dial up modem. The computer has a US Robotics V92 internal modem, definitely not a winmodem. It is recognized in the YAST hardware listing, and is identified as being on /dev/ttyS3. This is consistent with win2k finding it on com4 (as I understand it, linux starts at 0, windows at 1.) The modem works fine in win2k. In linux, trying to dialup with either kinternet or wvdial, the modem does not seem to be detected. With kinternet, the log shows

'Modem not responding'

and with wvdial, we get

'cannot open /dev/ttys3 input/output err' (repeated 3 times>)

Any suggestions would be greatly appreciated. It doesn't seem like this should be so hard!

Bernie Gardner w1az@adelphia.net

Sorry to say this but are 'absolutely' sure it is not a windmodem. USR have made some internal v92 winmodems and I nearly got caught out buying one once. I realised at the last minute and changed my order at the time for an external one. Doesn't mean it will not work under Linux but it may be a bit harder getting it to.

Now, COM4 in Windows? I have a sneaking suspicion that COM4 is set up in software not as an actual port.

Have you tried a Google search with the exact modem model entered into the search terms? It may be a start.

Thanks for the replies. For various reasons, I was pretty sure the it was a hardware modem, but I'm not sure now. I'm going to work on the computer tomorrow and hopefully will sort it out. I may be back for more help if I can't.

Kevanf1 wrote:

On 11/08/05, Bernie Gardner <bernie.gardner@umb.edu> wrote:

...

I've been trying to set up suse 9.2 pro on a friends computer for several months. Everything seems to work ok except the dial up modem. The computer has a US Robotics V92 internal modem, definitely not a winmodem. It is recognized in the YAST hardware listing, and is identified as being on /dev/ttyS3. This is consistent with win2k finding it on com4 (as I understand it, linux starts at 0, windows at 1.) The modem works fine in win2k. In linux, trying to dialup with either kinternet or wvdial, the modem does not seem to be detected. With kinternet, the log shows

'Modem not responding'

and with wvdial, we get

'cannot open /dev/ttys3 input/output err' (repeated 3 times>)

Any suggestions would be greatly appreciated. It doesn't seem like this should be so hard!

Bernie Gardner w1az@adelphia.net

Sorry to say this but are 'absolutely' sure it is not a windmodem. USR have made some internal v92 winmodems and I nearly got caught out buying one once. I realised at the last minute and changed my order at the time for an external one. Doesn't mean it will not work under Linux but it may be a bit harder getting it to.

Now, COM4 in Windows? I have a sneaking suspicion that COM4 is set up in software not as an actual port.

Have you tried a Google search with the exact modem model entered into the search terms? It may be a start.

Thanks for the replies. For various reasons, I was pretty sure the it was a hardware modem, but I'm not sure now. I'm going to work on the computer tomorrow and hopefully will sort it out. I may be back for more help if I can't.