Mailinglist Archive: opensuse (3644 mails)

< Previous Next >
Re: [SLE] US Robotics 3Com 5610 Internal Modem Does Work in Linux
  • From: "" <martinr_richard@xxxxxxx>
  • Date: Sat, 09 Mar 2002 21:17:10 -0500
  • Message-id: <F18TkUD5euwdUTaGmvS00017feb@xxxxxxxxxxx>

Probably a stupid questions but with lspci -v which IO I obtain for the modem is
I/O ports at e000
and it doesn't like what you told me I should expect.
What I must write in the setserial command for the IO?


From: Bryan Tyson <bryantyson@xxxxxxxxxxxxx>
Reply-To: bryantyson@xxxxxxxxxxxxx
To: suse-linux-e@xxxxxxxx
Subject: [SLE] US Robotics 3Com 5610 Internal Modem Does Work in Linux
Date: Sat, 9 Mar 2002 12:45:26 -0500

On Saturday 09 March 2002 03:37, Wolfi wrote:

> My idea is: Check linmodems, and do a new post here, saying: 'US
> Robotics/3Com 56K FaxModem Model 5610 internal, Anyone got it
> working?' or similar, and if there are no results, it's maybe better
> to get yourself an external modem, as far as I have heared from
> others here on this list - I can only quote from my memory, see
> above, I was never involved in internal modem setup myself!

I missed the beginning of this thread, so pardon me if I repeat
something already said.

I think it's safe to say that most internal PCI modems are winmodems.
However, just because a modem is internal and PCI does not
automatically mean it is a winmodem. Similarly, just because a modem is
a winmodem does not automatically mean it won't work, although
certainly your chances of it working are way down vs. a hardware modem.
My personal philosophy is the same as Wolfi's, namely that I'd rather
just get an external hardware modem in the first place so I know I can
simply plug it in and start using it.

Regarding US Robotics/3Com, I know of at least one PCI model they make
that is a true hardware modem: the 5610. I have personally used this in
3 different computers with a variety of different Linux distros,
including SuSE, and it works great.

The key is that this modem insists on being on com 5. I called USR tech
support and was told that this is hardwired in and cannot be changed.
In my opinion the com5 issue is why it won't auto detect in Linux. At
least for me, it never autodetects.

To get this working, use setserial. Basically setserial just tells
linux, find the com port at the address I give you, and assign it to
ttyS3 (or whatever).

An example of the syntax is:

setserial /dev/ttyS3 uart 16550a port 0xb800 irq3

You would have to change the above to reflect the I/O and IRQ the modem
is using on your system and the ttyS* that you want to use.

One way of finding the I/O and IRQ is type lspci -v in a terminal (1st
character is an L)

Some have had success with the following variation of the setserial

setserial /dev/ttyS1 port 0xc800 auto_irq autoconfig (again
substituting the correct I/O being used on your system).

Powered by SuSE Linux 7.3 Professional
KDE 2.2.1 KMail 1.3.1
This is a Microsoft-free computer

Bryan S. Tyson

To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the FAQ at and the
archives at

MSN Photos est le moyen le plus simple de partager, modifier et imprimer vos photos préférées.

< Previous Next >
This Thread
  • No further messages