From: "Ann" <tate886_thequeen@bigfoot.com>
To: <speakup@braille.uwo.ca>
Subject: Re: US Robotics 56K Voice PCI
Date: Thu, 23 May 2002 21:50:24 -0400 [thread overview]
Message-ID: <002201c202c5$601077a0$ad7d0cd8@oemcomputer> (raw)
In-Reply-To: <Pine.LNX.4.44.0205231700140.2929-100000@homerun.us>
ok, here's the output from my lspci command:
00:13.0 Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev 01)
(prog-if 02 [16550])
Subsystem: US Robotics/3Com USR 56k Internal Voice Modem (Model 2976)
Flags: medium devsel, IRQ 11
I/O ports at eff0
Capabilities: [dc] Power Management version 2
~Ann
----- Original Message -----
From: "Adam Myrow" <myrow@eskimo.com>
To: <speakup@braille.uwo.ca>
Sent: Thursday, May 23, 2002 6:14 PM
Subject: Re: US Robotics 56K Voice PCI
| Ann, type "lspci -v." You should see your modem listed with its
| resources. You will also see everyother PCI device. Copy down the info
| you see. For example, my output contains this.
|
| 00:13.0 Communication controller: TOPIC SEMICONDUCTOR Corp: Unknown device
| 0000
| Subsystem: TOPIC SEMICONDUCTOR Corp: Unknown device 0000
| Flags: medium devsel, IRQ 4
| I/O ports at 03e8 [size=8]
|
| You wouldn't know that is a modem from looking at it, but since I know
| that my modem has a chipset made by Topic, I recognize it. Send the
| output of your command to me or the list, and I'll tell you what to try.
| Basically, if you want to experiment, it involves the setserial command
| with the IRQ and address of your modem and then trying it. Once you've
| got a working setup, edit /etc/serial.conf and change the line for one of
| the com ports to match the settings. Lastly, remove the "#" from the
| beginning of the line in /etc/rc.d/rc.S that says "# .
| /etc/rc.d/rc.serial." By removing the #, you ensure that this line will
| now run when you reboot. This should get the modem working. Oh, I don't
| think it matters what com port you use for the modem as long as it is not
| in use by another real com port. I always use /dev/ttyS2 since that's
| generally free.
|
| Good luck!
|
|
|
|
| _______________________________________________
| Speakup mailing list
| Speakup@braille.uwo.ca
| http://speech.braille.uwo.ca/mailman/listinfo/speakup
|
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
Ann
` Gregory Nowak
` Janina Sajka
` Saqib Shaikh
` Janina Sajka
` Ann
` Gregory Nowak
` Ann
` Gregory Nowak
` Ann
` Gregory Nowak
` Gregory Nowak
` Adam Myrow
` Gregory Nowak
` Ann [this message]
` Toby Fisher
` Gregory Nowak
` Igor Gueths
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002201c202c5$601077a0$ad7d0cd8@oemcomputer' \
--to=tate886_thequeen@bigfoot.com \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).