public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: 'Georgina' <gena@gena-j.net>
To: speakup@braille.uwo.ca
Subject: Re: Minicom problem
Date: Wed, 29 May 2002 01:55:53 +0100	[thread overview]
Message-ID: <E17Crkn-0000HA-00@debian.debian_fan> (raw)
In-Reply-To: Your message of Tue, 28 May 2002 19:02:33 -0400. <001d01c2069b$c164c720$977b0cd8@oemcomputer>

Hi

Have you looked in your devices '/dev' directory to see if you have more
than the standard 0 -3 or in DOS terms com 1 - 4 ports?  I think that
you have to have to select advanced com ports or something in the kernel
to use com 5 or ttyS4 as your modem appears to being attempting to do.
The old way was to put the modem on com3 ttyS2 and set it to use irq 5
maybe that's an option.  Either way, I'm sure someone here will step in
and help.


Gena



Blindness Advocacy and Self Help Online www.bashonline.org

>That is how I was accessing minicom, as root.
>~Ann
>
>
>----- Original Message -----
>From: "Janina Sajka" <janina@afb.net>
>To: <speakup@braille.uwo.ca>
>Sent: Tuesday, May 28, 2002 6:31 PM
>Subject: Re: Minicom problem
>
>
>| Have you tried accessing minicom as root? Try with the following
>| switch:
>|
>| minicom -s
>|
>| This should take you to a setup screen.
>|
>| Once out of the setup screen, an ath should return 'ok'
>|
>| Exit minicom with Ctrl-a q enter
>|
>| On Tue, 28 May 2002, Ann wrote:
>|
>| > Hi folks,
>| >
>| > Well, my Linux saga continues. :) I finally got a working 2.4.18 kernel
>to
>| > work with Zipspeak8.0. My modem is detected on the correct port, with
>the
>| > correct IRq and everything, but when I try and open minicom, I get the
>| > following message. (Note: This is not a type O)
>| >
>| > : No such file or directorytyS4
>| >
>| > I think Gregory and I could use some brainstorming on this one, folks.
>There
>| > is a file called /dev/ttyS4, so I don't know why Minicom refuses to find
>it.
>| > ~Ann
>| >
>| >
>| > _______________________________________________
>| > 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
>|
>|
>| _______________________________________________
>| 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


  reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Ann
 ` Janina Sajka
   ` Ann
     ` 'Georgina' [this message]
       ` Janina Sajka
         ` Gregory Nowak

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=E17Crkn-0000HA-00@debian.debian_fan \
    --to=gena@gena-j.net \
    --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).