From: "Thomas D. Ward" <tward1978@earthlink.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Slack 9 problems!!!
Date: Sat, 5 Apr 2003 11:32:56 -0500 [thread overview]
Message-ID: <003501c2fb91$04041000$0a859641@tward1978> (raw)
In-Reply-To: <Pine.LNX.4.53.0304050949001.10748@homerun.midsouth.rr.com>
Ok, I have an internal isa modem. The problem is dmesg shows a really fishy
message.
It says /dev/ttyS1 LSR safety engaged. What in the world is that suppose to
mean? I've never seen a message like that before in my life.
----- Original Message -----
From: Adam Myrow <amyrow@midsouth.rr.com>
To: <speakup@braille.uwo.ca>
Sent: Saturday, April 05, 2003 11:05 AM
Subject: Re: Slack 9 problems!!!
> Yes, Redhat is very automated when it comes to detecting hardware and
> loading it up. This process also added about 10 seconds to the startup
> time for me. It's good and bad. Going from Redhat to Slackware is a
> great way to discover how vastly different two Linux distributions can be.
> Slackware is very much a distribution for somebody who wants to learn how
> to set up things manually and how things actually work. I've found that
> most Slackware users detest Redhat and vise versa. They are, IMHO, really
> designed for different types of people. I am the type who likes to
> tinker, so Slackware appeals to me.
>
> What sort of modem do you have? Is it PCI or ISA? If it's ISA, you may
> need to run a Plug 'N Play utility to get it working. You may also need
> setserial to configure it. You can edit /etc/serial.conf to give the
> right parameters to set serial, and then remove the "#" in front of the
> line in /etc/rc.d/rc.S to call on the rc.serial script. It is disabled
> by default because I guess it can hang the computer if it tries to
> configure a nonexistent port. The scripts in the /etc/rc.d directory
> are good to look at because they explain fairly well what they are
> doing. /etc/rc.d/rc.local is a good place for customized stuff like
> setting up Speakup the way you like it.
>
> For ISA Plug 'n Play, there is a kernel module called isa-pnp. Try
> running "modprobe isa-pnp" by hand and type dmesg and read the last few
> lines to see if it found and configured anything. If it did, add a
> "/sbin/modprobe isa-pnp" to the bottom of /etc/rc.d/rc.modules. For the
> network, run netconfig. It lets you choose either DHCP or static IP.
>
>
> _______________________________________________
> 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: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
Thomas D. Ward
` Doug
` Adam Myrow
` Thomas D. Ward [this message]
` Adam Myrow
` Doug
` Lorenzo Prince
` Thomas D. Ward
` Doug
` Steve Holmes
` Doug Sutherland
` Thomas D. Ward
` Doug Sutherland
` Luke Davis
` Thomas D. Ward
` Alex Snow
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='003501c2fb91$04041000$0a859641@tward1978' \
--to=tward1978@earthlink.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).