US Robotics 56K Voice PCI

US Robotics 56K Voice PCI

[Ann]

Hi Folks,

First, let me apologize if this message is off topic, and anyone who wants
can feel free to reply to me off list.

Does anyone know if my US Robotics 56K PCI modem, model 2976, will work
under my Linux Zipspeak distribution - or under any Linux distribution? So
far, I haven't been able to figure out how to get it  to work or even how to
enable the com port it seems to be on, which according to Windows is Com5.

Thanks for any advice and/or help. And, please, when providing instructions,
be as specific as you can since I'm  still fairly new to Linux.

Re: US Robotics 56K Voice PCI

[Gregory Nowak]

Yes, and it does the job very well (or at least that was true when I was on dial-up). For me it is on /dev/ttyS4. Look at your dmesg output by typing "dmesg |more" or "dmesg |less" which ever pager you like best.
Greg



On Thu, May 23, 2002 at 01:36:33PM -0400, Ann wrote:
> Hi Folks,
> 
> First, let me apologize if this message is off topic, and anyone who wants
> can feel free to reply to me off list.
> 
> Does anyone know if my US Robotics 56K PCI modem, model 2976, will work
> under my Linux Zipspeak distribution - or under any Linux distribution? So
> far, I haven't been able to figure out how to get it  to work or even how to
> enable the com port it seems to be on, which according to Windows is Com5.
> 
> Thanks for any advice and/or help. And, please, when providing instructions,
> be as specific as you can since I'm  still fairly new to Linux.
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: US Robotics 56K Voice PCI

[Janina Sajka]

What Windows calls com6 would be ttyS7 on Linux, but it may not
have been assigned there by the.

If you're not sure after looking at dmesg you can always do:

echo ata >/dev/ttys0

and keep incrementing through /dev/ttyS1, /dev/ttys2, etc., etc.

When you hit a dial tone, you've found your port. Of course, at
that point you'll be eager to do a:

echo ath >/dev/ttySX

where X is the number of the port you just identified.

For dialing look at wvdial. You might also want to find eznet.

A good way to configure is to start minicom -s as root. Minicom
is a lot like that old DOS Telex program.

Of course, what I don't know at all is how much of this comes to
you via zipspeak.


-- 
	
				Janina Sajka, Director
				Technology Research and Development
				Governmental Relations Group
				American Foundation for the Blind (AFB)

Email: janina@afb.net		Phone: (202) 408-8175

Chair, Accessibility SIG
Open Electronic Book Forum (OEBF)
http://www.openebook.org

Re: US Robotics 56K Voice PCI

[Saqib Shaikh]

> What Windows calls com6 would be ttyS7 on Linux

Oopse, I think you meant ttyS5.

Saqib

Re: US Robotics 56K Voice PCI

[Janina Sajka]

Thanks, Saqib. Just call me dyslexic! <grin>
On Thu, 23 May 2002, Saqib Shaikh wrote:

> > What Windows calls com6 would be ttyS7 on Linux
> 
> Oopse, I think you meant ttyS5.
> 
> Saqib
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

-- 
	
				Janina Sajka, Director
				Technology Research and Development
				Governmental Relations Group
				American Foundation for the Blind (AFB)

Email: janina@afb.net		Phone: (202) 408-8175

Chair, Accessibility SIG
Open Electronic Book Forum (OEBF)
http://www.openebook.org

Re: US Robotics 56K Voice PCI

[Ann]

When I try the commands

echo ata >/dev/ttyS4

and anything above ttyS4, I get the message "no such device"

Do I need to enable com ports 5 and up, and  how is that done? I'm assuming
that the command setserial might have something to do with it?

~Ann

Re: US Robotics 56K Voice PCI

[Gregory Nowak]

Did you enable the extended serial options when you configured your kernel?
Greg


On Thu, May 23, 2002 at 04:26:10PM -0400, Ann wrote:
> When I try the commands
> 
> echo ata >/dev/ttyS4
> 
> and anything above ttyS4, I get the message "no such device"
> 
> Do I need to enable com ports 5 and up, and  how is that done? I'm assuming
> that the command setserial might have something to do with it?
> 
> ~Ann
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: US Robotics 56K Voice PCI

[Ann]

LOL! As far as I know, I haven't actually configured anything. With
Zipspeak, all you need to do is extract the files to the root of whatever
drive you want, edit the LInux.bat file to point in the right direction, and
start in Dos, type linux, and away you go. Wouldn't have a clue as to how to
enable extended serial options in the kernel yet - I'm new to this stuff.
~Ann


----- Original Message -----
From: "Gregory Nowak" <greg@romualt.dhs.org>
To: <speakup@braille.uwo.ca>
Sent: Thursday, May 23, 2002 4:35 PM
Subject: Re: US Robotics 56K Voice PCI


| Did you enable the extended serial options when you configured your
kernel?
| Greg
|
|
| On Thu, May 23, 2002 at 04:26:10PM -0400, Ann wrote:
| > When I try the commands
| >
| > echo ata >/dev/ttyS4
| >
| > and anything above ttyS4, I get the message "no such device"
| >
| > Do I need to enable com ports 5 and up, and  how is that done? I'm
assuming
| > that the command setserial might have something to do with it?
| >
| > ~Ann
| >
| >
| >
| > _______________________________________________
| > Speakup mailing list
| > Speakup@braille.uwo.ca
| > http://speech.braille.uwo.ca/mailman/listinfo/speakup
|
| _______________________________________________
| Speakup mailing list
| Speakup@braille.uwo.ca
| http://speech.braille.uwo.ca/mailman/listinfo/speakup
|

Re: US Robotics 56K Voice PCI

[Gregory Nowak]

I'm sorry about that. I forgot that you might not have gotten around to building your own kernel yet. I haven't used zipspeak for 2 years or so. Does anyone out there remember if the standard zipspeak kernel comes with extended serial options configured into it. If not, then you will need to build your own kernel. If you're up to reading a couple of docs, it is not as hard as it sounds, as long as you know what hardware you have in your system.
Greg


On Thu, May 23, 2002 at 04:42:16PM -0400, Ann wrote:
> LOL! As far as I know, I haven't actually configured anything. With
> Zipspeak, all you need to do is extract the files to the root of whatever
> drive you want, edit the LInux.bat file to point in the right direction, and
> start in Dos, type linux, and away you go. Wouldn't have a clue as to how to
> enable extended serial options in the kernel yet - I'm new to this stuff.
> ~Ann
> 
> 

Re: US Robotics 56K Voice PCI

[Ann]

I don't mind reading a couple of docs. What docs do I need, and where can
they be found?
~Ann


----- Original Message -----
From: "Gregory Nowak" <greg@romualt.dhs.org>
To: <speakup@braille.uwo.ca>
Sent: Thursday, May 23, 2002 4:49 PM
Subject: Re: US Robotics 56K Voice PCI


| I'm sorry about that. I forgot that you might not have gotten around to
building your own kernel yet. I haven't used zipspeak for 2 years or so.
Does anyone out there remember if the standard zipspeak kernel comes with
extended serial options configured into it. If not, then you will need to
build your own kernel. If you're up to reading a couple of docs, it is not
as hard as it sounds, as long as you know what hardware you have in your
system.
| Greg
|
|
| On Thu, May 23, 2002 at 04:42:16PM -0400, Ann wrote:
| > LOL! As far as I know, I haven't actually configured anything. With
| > Zipspeak, all you need to do is extract the files to the root of
whatever
| > drive you want, edit the LInux.bat file to point in the right direction,
and
| > start in Dos, type linux, and away you go. Wouldn't have a clue as to
how to
| > enable extended serial options in the kernel yet - I'm new to this
stuff.
| > ~Ann
| >
| >
|
| _______________________________________________
| Speakup mailing list
| Speakup@braille.uwo.ca
| http://speech.braille.uwo.ca/mailman/listinfo/speakup
|

Re: US Robotics 56K Voice PCI

[Gregory Nowak]

The first doc you want to read is 
http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Kernel-HOWTO.html

In addition, you may want to look at any other docs mentioned at the end of this howto. You may rebuild your existing kernel, or build the latest and gratest stable one which is 2.4.18 right now. If you build the latest kernel, don't forget to get the speakup sources, and read the documentation that comes with the speakup sources. This should get you started.
Greg


On Thu, May 23, 2002 at 04:58:26PM -0400, Ann wrote:
> I don't mind reading a couple of docs. What docs do I need, and where can
> they be found?
> ~Ann
> 
> 

Re: US Robotics 56K Voice PCI

[Gregory Nowak]

Just to add to this, here is my serial portion of /usr/src/linux/.config for kernel 2.4.17.


CONFIG_SERIAL=y
CONFIG_SERIAL_CONSOLE=y
# CONFIG_SERIAL_ACPI is not set
CONFIG_SERIAL_EXTENDED=y
# CONFIG_SERIAL_MANY_PORTS is not set
CONFIG_SERIAL_SHARE_IRQ=y
# CONFIG_SERIAL_DETECT_IRQ is not set
# CONFIG_SERIAL_MULTIPORT is not set
# CONFIG_HUB6 is not set
# CONFIG_SERIAL_NONSTANDARD is not set


All you need to activate here are SERIAL_EXTENDED and SERIaL_SHARE_IRQ. I've just included my entire serial config for purposes of context.
Greg


On Thu, May 23, 2002 at 03:49:53PM -0500, Gregory Nowak wrote:
> I'm sorry about that. I forgot that you might not have gotten around to building your own kernel yet. I haven't used zipspeak for 2 years or so. Does anyone out there remember if the standard zipspeak kernel comes with extended serial options configured into it. If not, then you will need to build your own kernel. If you're up to reading a couple of docs, it is not as hard as it sounds, as long as you know what hardware you have in your system.
> Greg
> 
> 

Re: US Robotics 56K Voice PCI

[Adam Myrow]

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!

Re: US Robotics 56K Voice PCI

[Gregory Nowak]

Adam, for this modem it matters which serial port you use. Since you gave me the idea, here is the output of "lspci -v" for my and Ann's modem.


00:09.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 10
        I/O ports at c400 [size=8]
        Capabilities: [dc] Power Management version 2
 

Hth.
Greg


On Thu, May 23, 2002 at 05:14:48PM -0500, Adam Myrow wrote:
> 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

Re: US Robotics 56K Voice PCI

[Ann]

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
|

Re: US Robotics 56K Voice PCI

[Toby Fisher]

On Thu, 23 May 2002, Gregory Nowak wrote:

> I'm sorry about that. I forgot that you might not have gotten around
> to building your own kernel yet. I haven't used zipspeak for 2 years
> or so. Does anyone out there remember if the standard zipspeak kernel
> comes with extended serial options configured into it. If not, then
> you will need to build your own kernel. If you're up to reading a
> couple of docs, it is not as hard as it sounds, as long as you know
> what hardware you have in your system.

Greg,
I can't answer this question about the Zipspeak kernel, but since it comes
with all the modules you can possibly imagine, it might be as simple as
issuing a modprobe command or two.

Cheers.

-- 
Toby Fisher	Email: toby@g0ucu.freeserve.co.uk
Tel.: +44(0)1480 417272	Mobile: +44(0)7974 363239
ICQ: #61744808
   Please avoid sending me Word or PowerPoint attachments.
   See http://www.fsf.org/philosophy/no-word-attachments.html

Re: US Robotics 56K Voice PCI

[Gregory Nowak]

Since the options I'm talking about here are not modularizable (they have to be configured into the kernel itself), this fact doesn't help.
Greg


On Fri, May 24, 2002 at 03:17:47AM +0100, Toby Fisher wrote:
> On Thu, 23 May 2002, Gregory Nowak wrote:
> 
> > I'm sorry about that. I forgot that you might not have gotten around
> > to building your own kernel yet. I haven't used zipspeak for 2 years
> > or so. Does anyone out there remember if the standard zipspeak kernel
> > comes with extended serial options configured into it. If not, then
> > you will need to build your own kernel. If you're up to reading a
> > couple of docs, it is not as hard as it sounds, as long as you know
> > what hardware you have in your system.
> 
> Greg,
> I can't answer this question about the Zipspeak kernel, but since it comes
> with all the modules you can possibly imagine, it might be as simple as
> issuing a modprobe command or two.
> 
> Cheers.
> 
> -- 
> Toby Fisher	Email: toby@g0ucu.freeserve.co.uk
> Tel.: +44(0)1480 417272	Mobile: +44(0)7974 363239
> ICQ: #61744808
>    Please avoid sending me Word or PowerPoint attachments.
>    See http://www.fsf.org/philosophy/no-word-attachments.html
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: US Robotics 56K Voice PCI

[Igor Gueths]

Hi Ann. Is anything supposedly plugged into that port? Do you really have 4 serial ports? Because I would say in normal cases you would use ttyS0 or ttyS1. I haven't ben following this thread, so possibly my reply isn't relevant. 
----- Original Message ----- 
From: Ann <tate886_thequeen@bigfoot.com>
To: <speakup@braille.uwo.ca>
Sent: Thursday, May 23, 2002 4:26 PM
Subject: Re: US Robotics 56K Voice PCI


> When I try the commands
> 
> echo ata >/dev/ttyS4
> 
> and anything above ttyS4, I get the message "no such device"
> 
> Do I need to enable com ports 5 and up, and  how is that done? I'm assuming
> that the command setserial might have something to do with it?
> 
> ~Ann
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup