Hi, AFAIK, installing a PCI modem causes problems in Linux, but external modems should always work. So I purchased a Sitecom 56k external modem. But alas, it was not recognized by Yast1 or Yast2, although I selected the right serial port (/dev/ttyS1). Has anyone got a Sitecom external modem working? Or is it true that not all external modems work? TIA, SH
On Fri, Sep 14, 2001 at 08:12:24PM +0200, Sjoerd Hiemstra wrote:
AFAIK, installing a PCI modem causes problems in Linux, but external modems should always work.
So I purchased a Sitecom 56k external modem.
But alas, it was not recognized by Yast1 or Yast2, although I selected the right serial port (/dev/ttyS1).
Has anyone got a Sitecom external modem working? Or is it true that not all external modems work?
So this modem is connect to the port which would be called COM2 under Windows? Remember, serial ports are numbered starting at 0, so: ttyS0 COM1 ttyS1 COM2 ttyS2 COM3 ttyS3 COM4 Try running: wvdialconf /dev/null to see if you modem is detected like this. Hope that helps, Chris -- http://www.tuxedo.org/~esr/faqs/smart-questions.html __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
On Fri, Sep 14, 2001 at 07:25:12PM +0100, Chris Reeves wrote:
On Fri, Sep 14, 2001 at 08:12:24PM +0200, Sjoerd Hiemstra wrote:
AFAIK, installing a PCI modem causes problems in Linux, but external modems should always work.
So I purchased a Sitecom 56k external modem.
But alas, it was not recognized by Yast1 or Yast2, although I selected the right serial port (/dev/ttyS1).
Has anyone got a Sitecom external modem working? Or is it true that not all external modems work?
So this modem is connect to the port which would be called COM2 under Windows? Remember, serial ports are numbered starting at 0, so: ttyS0 COM1 ttyS1 COM2 ttyS2 COM3 ttyS3 COM4
Try running: wvdialconf /dev/null to see if you modem is detected like this.
Hope that helps, Chris
Oh it should work, and wvdialconf should find it. PCI modems do work by the way as long as they are NOT winmodems. -- Regards Cliff
On 14 Sep 2001 20:49:36 +0200, Cliff Sarginson wrote:
Oh it should work, and wvdialconf should find it. PCI modems do work by the way as long as they are NOT winmodems.
Yes, but PCI are a real pain to get working, not sure if its changed at all now. USB modems work too, got mine working without too many issues (creative labs modem blaster). Matt
-- Regards Cliff
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
On Friday 14 September 2001 20:25, Chris Reeves wrote:
On Fri, Sep 14, 2001 at 08:12:24PM +0200, Sjoerd Hiemstra wrote:
AFAIK, installing a PCI modem causes problems in Linux, but external modems should always work.
So I purchased a Sitecom 56k external modem.
But alas, it was not recognized by Yast1 or Yast2, although I selected the right serial port (/dev/ttyS1).
Has anyone got a Sitecom external modem working? Or is it true that not all external modems work?
So this modem is connect to the port which would be called COM2 under Windows? Remember, serial ports are numbered starting at 0, so: ttyS0 COM1 ttyS1 COM2 ttyS2 COM3 ttyS3 COM4
Try running: wvdialconf /dev/null to see if you modem is detected like this.
Hope that helps, Chris
Sending this message with my new modem!! :-) wvdialconf did the trick, to my relief, it really is amazing. Thank you very much! Sjoerd
participants (4)
-
Chris Reeves -
Cliff Sarginson -
Sjoerd Hiemstra -
StarTux