Connecting to the Internet ; editing LIO; setting up the sound card

Connecting to the Internet ; editing LIO; setting up the sound card

[Darragh]

Hello all,
At last I have a perfectly working Red Hat Linux installation fully
accessible thanks to Speak up.  Now that I have it working I'd like to be
able to read Email, visit web pages, listen to MP3's.  Unfortunately to do
this I have to know how to set up my Modem and sound card.  Can any one
help?  I'm using a 56K hardware modem and a - Typhoon digital sound card.

I have also heard some of you talking about customizing the Lilo menu to be
slightly easier to use.  Could this be customized to beep when I pass over
the Linux option?  Failing this does any one have any other suggestions on
making it easier to use?

Thanks again for all your help.

Darragh

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[John]

First, a reminder. I'm not blind, I'l here to learn what problems the blind 
have and how they're addressed. However, I have been using Linux for some 
years.

Sound is ordinarily quite easy. I install Linux, and on the first boot kudzu 
leaps in and asks if I want to configure my sound card. I say, "Yes," and it 
does.

Configuring the modem itself is generally almost as easy. Login as root and 
run this command
wvdialconf /etc/wvdial.conf

There will be lots of messages, hopefully some of them resulting from it 
finding and testing your modem.

The result will be a file called /etc/wvdial.conf which should contain 
something like this:
[Dialer Defaults]
Modem = /dev/ttyS0
Baud = 115200
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0
; Phone = <Target Phone Number>
; Username = <Your Login Name>
; Password = <Your Password>


Remember, not those particular values, but like that.

To this you can add something like this:
[Dialer isp]
Username = summer
Password = shooter
Phone = 92503951
Inherits = Dialer Defaults
[root@gw root]#


Connecting might be as simple as issuing the command
wvdial isp

where isp matches the word after "Dialer" above.
But then, it might not be so simple, but this is a good start.



On Monday 19 August 2002 20:42, Darragh wrote:
> At last I have a perfectly working Red Hat Linux installation fully
> accessible thanks to Speak up.  Now that I have it working I'd like to be
> able to read Email, visit web pages, listen to MP3's.  Unfortunately to do
> this I have to know how to set up my Modem and sound card.  Can any one
> help?  I'm using a 56K hardware modem and a - Typhoon digital sound card.
> 
> 

-- 


Cheers
John.

Please, no off-list mail. You will fall foul of my spam treatment.
Join the "Linux Support by Small Businesses" list at 
http://mail.computerdatasafe.com.au/mailman/listinfo/lssb

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Jude DaShiell]

I'd put an ampersand after that wvdialconf command or be prepared to have
my speech synthesizer hosed.

x

On Tue, 20 Aug 2002, John wrote:

> First, a reminder. I'm not blind, I'l here to learn what problems the blind
> have and how they're addressed. However, I have been using Linux for some
> years.
>
> Sound is ordinarily quite easy. I install Linux, and on the first boot kudzu
> leaps in and asks if I want to configure my sound card. I say, "Yes," and it
> does.
>
> Configuring the modem itself is generally almost as easy. Login as root and
> run this command
> wvdialconf /etc/wvdial.conf
>
> There will be lots of messages, hopefully some of them resulting from it
> finding and testing your modem.
>
> The result will be a file called /etc/wvdial.conf which should contain
> something like this:
> [Dialer Defaults]
> Modem = /dev/ttyS0
> Baud = 115200
> Init1 = ATZ
> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0
> ; Phone = <Target Phone Number>
> ; Username = <Your Login Name>
> ; Password = <Your Password>
>
>
> Remember, not those particular values, but like that.
>
> To this you can add something like this:
> [Dialer isp]
> Username = summer
> Password = shooter
> Phone = 92503951
> Inherits = Dialer Defaults
> [root@gw root]#
>
>
> Connecting might be as simple as issuing the command
> wvdial isp
>
> where isp matches the word after "Dialer" above.
> But then, it might not be so simple, but this is a good start.
>
>
>
> On Monday 19 August 2002 20:42, Darragh wrote:
> > At last I have a perfectly working Red Hat Linux installation fully
> > accessible thanks to Speak up.  Now that I have it working I'd like to be
> > able to read Email, visit web pages, listen to MP3's.  Unfortunately to do
> > this I have to know how to set up my Modem and sound card.  Can any one
> > help?  I'm using a 56K hardware modem and a - Typhoon digital sound card.
> >
> >
>
> --
>
>
> Cheers
> John.
>
> Please, no off-list mail. You will fall foul of my spam treatment.
> Join the "Linux Support by Small Businesses" list at
> http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
>
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[John]

On Tuesday 20 August 2002 10:37, Jude DaShiell wrote:
> I'd put an ampersand after that wvdialconf command or be prepared to have
> my speech synthesizer hosed.

The ampersand won't help;-)

If you don't want to hear what happens
wvdialconf /etc/wvdial.conf >/dev/null 2>&1

and then inspect /etc/wvdial.conf.

If it doesn't work, I guess you'll have to put up with the noise.

 

-- 


Cheers
John.

Please, no off-list mail. You will fall foul of my spam treatment.
Join the "Linux Support by Small Businesses" list at 
http://mail.computerdatasafe.com.au/mailman/listinfo/lssb

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Darragh]

Hello again,
I've tried all the suggestions with no success.  It keeps telling me that a
modem cant be found and I should check the setserial configuration.  I've
briefly read the man pages for set serial and as far as I can tell these
options are set at boot up.  I don't yet have the knowledge to start editing
it my self.  One further thing, when I type wvdialconf /etc/wvdial.conf &
create I get the same error message but no command prompt.  I've waited for
up to twenty minutes with no luck.  I can get the command prompt back by
pressing return but I get a message saying [1]+ EXIT 1     /etc/wvdial.conf
Does any one know what this means?

Thanks

Darragh
----- Original Message -----
From: "John" <valhalla@computerdatasafe.com.au>
To: <blinux-list@redhat.com>
Sent: Tuesday, August 20, 2002 4:32 AM
Subject: Re: Connecting to the Internet ; editing LIO; setting up the sound
card


> On Tuesday 20 August 2002 10:37, Jude DaShiell wrote:
> > I'd put an ampersand after that wvdialconf command or be prepared to
have
> > my speech synthesizer hosed.
>
> The ampersand won't help;-)
>
> If you don't want to hear what happens
> wvdialconf /etc/wvdial.conf >/dev/null 2>&1
>
> and then inspect /etc/wvdial.conf.
>
> If it doesn't work, I guess you'll have to put up with the noise.
>
>
>
> --
>
>
> Cheers
> John.
>
> Please, no off-list mail. You will fall foul of my spam treatment.
> Join the "Linux Support by Small Businesses" list at
> http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
>
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[John]

In a sense the ampersand disconnects the program from your terminal so it can 
run in the background while you do other things. The advice to type the 
ampersand was not useful. What you see is just the way bash works.

I've been using Linux for some years, and been using it for dialup since Red 
Hat 4.2. I've never needed to use setserial.

What I would like to see is the output of wvdialconf, but what it writes to 
the screen and the configuration file it creates.

You can capture the screen output like this:
wvdialconf /etc/wvdial.conf >wvdialreport 2>&1

Before you do that, though, check whether the modem is plugged in to power and 
the computer and that it is turned on.

btw, you said you have "a 56K hardware modem." You did not say whether it's 
internal or external. My instructions above assume external.

On Tuesday 20 August 2002 15:09, Darragh wrote:
> Hello again,
> I've tried all the suggestions with no success.  It keeps telling me that a
> modem cant be found and I should check the setserial configuration.  I've
> briefly read the man pages for set serial and as far as I can tell these
> options are set at boot up.  I don't yet have the knowledge to start editing
> it my self.  One further thing, when I type wvdialconf /etc/wvdial.conf &
> create I get the same error message but no command prompt.  I've waited for
> up to twenty minutes with no luck.  I can get the command prompt back by
> pressing return but I get a message saying [1]+ EXIT 1     /etc/wvdial.conf
> Does any one know what this means?



-- 


Cheers
John.

Please, no off-list mail. You will fall foul of my spam treatment.
Join the "Linux Support by Small Businesses" list at 
http://mail.computerdatasafe.com.au/mailman/listinfo/lssb

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Darragh]

Ah, sorry about that, its an internal

Darragh
----- Original Message -----
From: "John" <valhalla@computerdatasafe.com.au>
To: <blinux-list@redhat.com>
Sent: Tuesday, August 20, 2002 8:29 AM
Subject: Re: Connecting to the Internet ; editing LIO; setting up the sound
card


>
> In a sense the ampersand disconnects the program from your terminal so it
can
> run in the background while you do other things. The advice to type the
> ampersand was not useful. What you see is just the way bash works.
>
> I've been using Linux for some years, and been using it for dialup since
Red
> Hat 4.2. I've never needed to use setserial.
>
> What I would like to see is the output of wvdialconf, but what it writes
to
> the screen and the configuration file it creates.
>
> You can capture the screen output like this:
> wvdialconf /etc/wvdial.conf >wvdialreport 2>&1
>
> Before you do that, though, check whether the modem is plugged in to power
and
> the computer and that it is turned on.
>
> btw, you said you have "a 56K hardware modem." You did not say whether
it's
> internal or external. My instructions above assume external.
>
> On Tuesday 20 August 2002 15:09, Darragh wrote:
> > Hello again,
> > I've tried all the suggestions with no success.  It keeps telling me
that a
> > modem cant be found and I should check the setserial configuration.
I've
> > briefly read the man pages for set serial and as far as I can tell these
> > options are set at boot up.  I don't yet have the knowledge to start
editing
> > it my self.  One further thing, when I type wvdialconf /etc/wvdial.conf
&
> > create I get the same error message but no command prompt.  I've waited
for
> > up to twenty minutes with no luck.  I can get the command prompt back by
> > pressing return but I get a message saying [1]+ EXIT 1
/etc/wvdial.conf
> > Does any one know what this means?
>
>
>
> --
>
>
> Cheers
> John.
>
> Please, no off-list mail. You will fall foul of my spam treatment.
> Join the "Linux Support by Small Businesses" list at
> http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
>
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[pawel_l]

On Tue, 20 Aug 2002, John wrote:

> btw, you said you have "a 56K hardware modem." You did not say whether it's 
> internal or external. My instructions above assume external.

So, should I understand that your instruction wouldn't work at all for 
internal modem? What would you suggest to use for internal one, then?

Thanks,
Pawel.

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Jude DaShiell]

Try setserial -a <cr> first.  kudzu didn't detect your serial card; not an
infrequent occurrence either.

x

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Jude DaShiell]

Probably the only help available is the linmodem project if that's the
case.

x

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Darragh]

Again nothing, I used the command setserial -a <cr> and setserial -a create
but still nothing that doesn't seem to be a modem problem but a syntax
error.  I've being trying to decompress the rpm's for linuxconf but I've had
no luck, the speakup method of reading the man pages is taking some getting
use to.  Its pronouncing some words as broken words example house is hou se.
Its very distracting.  To make things worse, I cant use the up and down
arrows to read the man pages as speakup reads SS in front of every line,
I've found from experimentation that the E key will do the same thing
without calling out the SS string.  Also, I cant read in pico with the arrow
keys, I have to use the speakup navigation keys.  that makes it nearly
impossible to edit text and incert  text into certain parts of configuration
files.  I'll probably get use to it but for the moment its frustrating.
Back to the modem though, this is getting on my nerves, I specifically asked
for a hardware modem when buying this computer to make it as easy as
possible to install it.  Looks like I'm going to need some more time.  For
thoughs of you on the list sick of hearing from me by now, I'll get there
eventually, I am use to having full independence in Windows, its difficult
to go to an operating system where absolutely everything is different.

Thanks again

Darragh
----- Original Message -----
From: "Jude DaShiell" <jdashiel@shellworld.net>
To: <blinux-list@redhat.com>
Sent: Tuesday, August 20, 2002 11:29 PM
Subject: Re: Connecting to the Internet ; editing LIO; setting up the sound
card


> Try setserial -a <cr> first.  kudzu didn't detect your serial card; not an
> infrequent occurrence either.
>
> x
>
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Jude DaShiell]

try setserial /a <cr> or try the setup command sinze one of the services
it offers is to allow you to configure your sound card. You do not have a
file called /etc/wvdial.conf right?  If that command had run at all
correctly you should have at least a skeleton there. linuxconf may or may
not work for you, you can try rpm -IVh linuxconf then hit escape when in
the directory where it's at.  That won't uncompress the rpm package but
should install it for you if it's not corrupted.

x

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[John]

On Tuesday 20 August 2002 22:22, pawel_l@adaptech.net wrote:
> On Tue, 20 Aug 2002, John wrote:
> 
> 
> > btw, you said you have "a 56K hardware modem." You did not say whether 
it's 
> > internal or external. My instructions above assume external.
> 
> 
> 
> So, should I understand that your instruction wouldn't work at all for 
> internal modem? What would you suggest to use for internal one, then?

Well, if it's an internal modem you can't so easily check the power switch 
etc;-)

If it really is a hardware modem it may appear at /dev/ttyS2 or /dev/ttyS3. If 
it's "winmodem" that is also supported on Linux - a "Linmodem" it will work 
quite well, but you need to download drivers and build kernel modules. I can 
do it, but describing it from memory is not on.

A good website though is http://www.linmodems.org/

You will need some technical detail about the modem - the lspci command (log 
in as root) will probably give you that, and then find the best match on this 
website and follow instructions. I found getting a modem with the Lucent 
chipset working no great problem, but then I know my way round Linux.
 



-- 


Cheers
John.

Please, no off-list mail. You will fall foul of my spam treatment.
Join the "Linux Support by Small Businesses" list at 
http://mail.computerdatasafe.com.au/mailman/listinfo/lssb

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[John]

On Wednesday 21 August 2002 06:29, Jude DaShiell wrote:
> Try setserial -a <cr> first.  kudzu didn't detect your serial card; not an
> infrequent occurrence either.

Very likely it's not going to work without a kernel patch, and that's 
basically the process the website I mentioned takes you through.

-- 


Cheers
John.

Please, no off-list mail. You will fall foul of my spam treatment.
Join the "Linux Support by Small Businesses" list at 
http://mail.computerdatasafe.com.au/mailman/listinfo/lssb

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[John]

On Wednesday 21 August 2002 08:48, Darragh wrote:
> I specifically asked
> for a hardware modem when buying this computer to make it as easy as
> possible to install it.

External modems are good.


-- 


Cheers
John.

Please, no off-list mail. You will fall foul of my spam treatment.
Join the "Linux Support by Small Businesses" list at 
http://mail.computerdatasafe.com.au/mailman/listinfo/lssb

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[L. C. Robinson]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 4496 bytes --]

On Wed, 21 Aug 2002, Darragh wrote:

> Again nothing, I used the command setserial -a <cr> and

You probably don't need setserial, unless you need to set up a
serial port other than the the standard first 2 (ttyS0 and ttyS1,
linux equivalent of com1 and com2).

> I've being trying to decompress the rpm's for linuxconf but
> I've had no luck,

Good: linuxconf is poorly maintained junk, with security
problems, and hard to follow menus, and is only included for
backward compatibility in later RedHat versions.  I have deleted
it from my systems.

> speakup method of reading the man pages is taking some getting
> use to.  Its pronouncing some words as broken words example
> house is hou se.  Its very distracting.  To make things worse,
> I cant use the up and down arrows to read the man pages as
> speakup reads SS in front of every line, I've found from
> experimentation that the E key will do the same thing without

The man command uses the "less" pager by default, and the
lowercase e key moves down a line at a time in that utility.
Use the the h key from within "less" (better than "more") for
help on other ways to move around (use "y" to move up a line):
"less" uses vi editor conventions for movement where possible.  

> calling out the SS string.  Also, I cant read in pico with the
> arrow keys, I have to use the speakup navigation keys.  that

pico -- ugh.  Many other choices: vi is widely used, and of
course emacspeak uses -- emacs.

> makes it nearly impossible to edit text and incert  text into
> certain parts of configuration files.  I'll probably get use to
> it but for the moment its frustrating.  Back to the modem
> though, this is getting on my nerves, I specifically asked for
> a hardware modem when buying this computer to make it as easy

Did I miss a message?  I saw nothing to indicate you have a
winmodem (which is not the same as having an internal modem).
Have you tried minicom (a terminal emulator program) to see if
you can talk directly to the modem with "AT" commands, and get an
"OK" response?

Now, concerning the previous messages concerning wvdial, and the
RedHat ppp setup help page:

There were a great many ways invented to set up ppp, probably
still in some aging directory in the linux archives on ibiblio
(formerly metalab), and it's many mirrors around the world (see
/pub/Linux/system/network/serial/ppp/*): wvdial obsoleted many of
these by making things easy for the average user in the most
common situations.  But as it's man page says, it doesn't cover
every situation.  If it doesn't work for you, you are probably
better off using one of the old dated text based scripts, which
may still work, even though not well maintained.  Failing that,
it may be easiest to configure by hand editing config files: the
pppd documentation may help, though terse, but the PPP-HOWTO is
probably your friend here (skip the first sections on the newer
GUI config programs, and the sections on kernel compiling and the
like -- RedHat has already done that stuff for you).  You
probably have installed the HOWTO package on your system, and can
find it by doing something like:

locate PPP-HOWTO

Resulting in a path something like:
/usr/share/doc/HOWTO/PPP-HOWTO
for the ascii version.

or
locate PPP-HOWTO.html
returning something like:
/usr/share/doc/HOWTO/other-formats/html/PPP-HOWTO.html

The most recent HOWTOs are always on www.linuxdoc.org

If you want to configure things with the Red Hat style network
config files, see the initscripts package, (do:
rpm -qd initscripts
)
which should lead you to a terse file giving info on the
textmode config files used in their GUI utilities:
/usr/share/doc/initscripts-6.67/sysconfig.txt
for RH7.3,
and you can edit them by hand, as I do (easier and more flexible
than the GUI -- which I can use, but dislike -- too limited).
They are:
/etc/sysconfig/network-scripts/chat-ppp0
/etc/sysconfig/network-scripts/ifcfg-ppp0
(see attached examples)
You may have to create the ifcfg file by copying and changing
one of the other ifcfg files in that directory.

Then you could use the Redhat utils to bring up and take
down your ppp connection:
/sbin/ifup ppp0
/sbin/ifdown ppp0

LCR

-- 
L. C. Robinson
reply to no_spam+munged_lcr@onewest.net.invalid

People buy MicroShaft for compatibility, but get incompatibility and
instability instead.  This is award winning "innovation".  Find
out how MS holds your data hostage with "The *Lens*"; see
"CyberSnare" at http://www.netaction.org/msoft/cybersnare.html

[-- Attachment #2: chat-ppp0 --]
[-- Type: TEXT/PLAIN, Size: 404 bytes --]

ECHO OFF
'' 'ATZ'
'OK-+++\c-OK' ATH0 
ABORT BUSY
ABORT ERROR
ABORT 'NO CARRIER'
ABORT 'NO DIALTONE'
ABORT 'Invalid Login'
ABORT 'Login incorrect'
REPORT CARRIER
REPORT 'Welcome'
# put in your ISP's phone number:
OK 'ATDT555-1234'
SAY 'Waiting for connection...\n'
CONNECT ''
ogin:--ogin: your-name
# Use the \q escape to keep the password from showing up in logs:
word: \qyour-password

[-- Attachment #3: ifcfg-ppp0 --]
[-- Type: TEXT/PLAIN, Size: 494 bytes --]

DEVICE="ppp0"
NAME=myISP's-name
# WVDIALSECT=

# For com2:
MODEMPORT="/dev/ttyS1"

LINESPEED="115200"
PAPNAME="your-login-name"
USERCTL="yes"
ONBOOT="no"

# keep RH scripts from messing with resolv.conf file:
PEERDNS="no"
RESOLV_MODS="no"

PERSIST="yes"
DEFABORT="yes"
DEBUG="yes"
INITSTRING=""
DEFROUTE="yes"
HARDFLOWCTL="yes"
ESCAPECHARS="no"
PPPOPTIONS=""
REMIP=""
NETMASK=""
IPADDR=""
MRU=""
MTU=""
DISCONNECTTIMEOUT="30"
RETRYTIMEOUT="120"
BOOTPROTO="none"

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Darragh]

Ok, I've tried all the suggestions more or less, I haven't tried the
initscripts as of yet because I'm not entirely comfortable with them.  The
linux setup program didn't have anything about modems, I did fix the network
card though so that's got me somewhere.  I got an error message that may be
of use to some of you: spurious 8259A interrupt: IRQ7.  Any ideas what
that's about?  It happened as I was mounting my fat32 drive.  I was about
half way threw the line and it came up.  Wvdialconf still isn't working, it
still cant find anything.  I tried typing wvdialconf /etc/wvdial.conf create
but it says first of all that there is no configuration file, then it says
that it cant access /dev/modem:  it says this could be because the path is
missing or in use.  I looked for /dev/ttyS0 to 2 but couldn't find it.  It
said that the directory didn't exist.  When I launched minicom it said that
the default configuration file was missing then as it was entering the
program it said loading default settings.  I got the messages telling me to
press control A to Z to access special keys or something like that but they
didn't work.  I'm going to read over some more manuals to see if I find
anything new.

Thanks again

Jinksed as always
Darragh
----- Original Message -----
From: "L. C. Robinson" <lcr@onewest.net>
To: <blinux-list@redhat.com>
Sent: Wednesday, August 21, 2002 9:56 AM
Subject: Re: Connecting to the Internet ; editing LIO; setting up the sound
card


> On Wed, 21 Aug 2002, Darragh wrote:
>
> > Again nothing, I used the command setserial -a <cr> and
>
> You probably don't need setserial, unless you need to set up a
> serial port other than the the standard first 2 (ttyS0 and ttyS1,
> linux equivalent of com1 and com2).
>
> > I've being trying to decompress the rpm's for linuxconf but
> > I've had no luck,
>
> Good: linuxconf is poorly maintained junk, with security
> problems, and hard to follow menus, and is only included for
> backward compatibility in later RedHat versions.  I have deleted
> it from my systems.
>
> > speakup method of reading the man pages is taking some getting
> > use to.  Its pronouncing some words as broken words example
> > house is hou se.  Its very distracting.  To make things worse,
> > I cant use the up and down arrows to read the man pages as
> > speakup reads SS in front of every line, I've found from
> > experimentation that the E key will do the same thing without
>
> The man command uses the "less" pager by default, and the
> lowercase e key moves down a line at a time in that utility.
> Use the the h key from within "less" (better than "more") for
> help on other ways to move around (use "y" to move up a line):
> "less" uses vi editor conventions for movement where possible.
>
> > calling out the SS string.  Also, I cant read in pico with the
> > arrow keys, I have to use the speakup navigation keys.  that
>
> pico -- ugh.  Many other choices: vi is widely used, and of
> course emacspeak uses -- emacs.
>
> > makes it nearly impossible to edit text and incert  text into
> > certain parts of configuration files.  I'll probably get use to
> > it but for the moment its frustrating.  Back to the modem
> > though, this is getting on my nerves, I specifically asked for
> > a hardware modem when buying this computer to make it as easy
>
> Did I miss a message?  I saw nothing to indicate you have a
> winmodem (which is not the same as having an internal modem).
> Have you tried minicom (a terminal emulator program) to see if
> you can talk directly to the modem with "AT" commands, and get an
> "OK" response?
>
> Now, concerning the previous messages concerning wvdial, and the
> RedHat ppp setup help page:
>
> There were a great many ways invented to set up ppp, probably
> still in some aging directory in the linux archives on ibiblio
> (formerly metalab), and it's many mirrors around the world (see
> /pub/Linux/system/network/serial/ppp/*): wvdial obsoleted many of
> these by making things easy for the average user in the most
> common situations.  But as it's man page says, it doesn't cover
> every situation.  If it doesn't work for you, you are probably
> better off using one of the old dated text based scripts, which
> may still work, even though not well maintained.  Failing that,
> it may be easiest to configure by hand editing config files: the
> pppd documentation may help, though terse, but the PPP-HOWTO is
> probably your friend here (skip the first sections on the newer
> GUI config programs, and the sections on kernel compiling and the
> like -- RedHat has already done that stuff for you).  You
> probably have installed the HOWTO package on your system, and can
> find it by doing something like:
>
> locate PPP-HOWTO
>
> Resulting in a path something like:
> /usr/share/doc/HOWTO/PPP-HOWTO
> for the ascii version.
>
> or
> locate PPP-HOWTO.html
> returning something like:
> /usr/share/doc/HOWTO/other-formats/html/PPP-HOWTO.html
>
> The most recent HOWTOs are always on www.linuxdoc.org
>
> If you want to configure things with the Red Hat style network
> config files, see the initscripts package, (do:
> rpm -qd initscripts
> )
> which should lead you to a terse file giving info on the
> textmode config files used in their GUI utilities:
> /usr/share/doc/initscripts-6.67/sysconfig.txt
> for RH7.3,
> and you can edit them by hand, as I do (easier and more flexible
> than the GUI -- which I can use, but dislike -- too limited).
> They are:
> /etc/sysconfig/network-scripts/chat-ppp0
> /etc/sysconfig/network-scripts/ifcfg-ppp0
> (see attached examples)
> You may have to create the ifcfg file by copying and changing
> one of the other ifcfg files in that directory.
>
> Then you could use the Redhat utils to bring up and take
> down your ppp connection:
> /sbin/ifup ppp0
> /sbin/ifdown ppp0
>
> LCR
>
> --
> L. C. Robinson
> reply to no_spam+munged_lcr@onewest.net.invalid
>
> People buy MicroShaft for compatibility, but get incompatibility and
> instability instead.  This is award winning "innovation".  Find
> out how MS holds your data hostage with "The *Lens*"; see
> "CyberSnare" at http://www.netaction.org/msoft/cybersnare.html
>

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Darragh]

Hello again, I had an update today, I found out the manufacturor of my
modem, e-tech.  I bought it from a German company and although they sent me
manuals with it they neglected to send me any drivers.  There are no drivers
for Linux as far as I can tell on the e-tech.nu web site but there is a PDF
manual.  I'll have to spend a while getting around the security protection
before JAWS will read it for me but hopefully it will give me some ideas.

DArragh
----- Original Message -----
From: "L. C. Robinson" <lcr@onewest.net>
To: <blinux-list@redhat.com>
Sent: Wednesday, August 21, 2002 9:56 AM
Subject: Re: Connecting to the Internet ; editing LIO; setting up the sound
card


> On Wed, 21 Aug 2002, Darragh wrote:
>
> > Again nothing, I used the command setserial -a <cr> and
>
> You probably don't need setserial, unless you need to set up a
> serial port other than the the standard first 2 (ttyS0 and ttyS1,
> linux equivalent of com1 and com2).
>
> > I've being trying to decompress the rpm's for linuxconf but
> > I've had no luck,
>
> Good: linuxconf is poorly maintained junk, with security
> problems, and hard to follow menus, and is only included for
> backward compatibility in later RedHat versions.  I have deleted
> it from my systems.
>
> > speakup method of reading the man pages is taking some getting
> > use to.  Its pronouncing some words as broken words example
> > house is hou se.  Its very distracting.  To make things worse,
> > I cant use the up and down arrows to read the man pages as
> > speakup reads SS in front of every line, I've found from
> > experimentation that the E key will do the same thing without
>
> The man command uses the "less" pager by default, and the
> lowercase e key moves down a line at a time in that utility.
> Use the the h key from within "less" (better than "more") for
> help on other ways to move around (use "y" to move up a line):
> "less" uses vi editor conventions for movement where possible.
>
> > calling out the SS string.  Also, I cant read in pico with the
> > arrow keys, I have to use the speakup navigation keys.  that
>
> pico -- ugh.  Many other choices: vi is widely used, and of
> course emacspeak uses -- emacs.
>
> > makes it nearly impossible to edit text and incert  text into
> > certain parts of configuration files.  I'll probably get use to
> > it but for the moment its frustrating.  Back to the modem
> > though, this is getting on my nerves, I specifically asked for
> > a hardware modem when buying this computer to make it as easy
>
> Did I miss a message?  I saw nothing to indicate you have a
> winmodem (which is not the same as having an internal modem).
> Have you tried minicom (a terminal emulator program) to see if
> you can talk directly to the modem with "AT" commands, and get an
> "OK" response?
>
> Now, concerning the previous messages concerning wvdial, and the
> RedHat ppp setup help page:
>
> There were a great many ways invented to set up ppp, probably
> still in some aging directory in the linux archives on ibiblio
> (formerly metalab), and it's many mirrors around the world (see
> /pub/Linux/system/network/serial/ppp/*): wvdial obsoleted many of
> these by making things easy for the average user in the most
> common situations.  But as it's man page says, it doesn't cover
> every situation.  If it doesn't work for you, you are probably
> better off using one of the old dated text based scripts, which
> may still work, even though not well maintained.  Failing that,
> it may be easiest to configure by hand editing config files: the
> pppd documentation may help, though terse, but the PPP-HOWTO is
> probably your friend here (skip the first sections on the newer
> GUI config programs, and the sections on kernel compiling and the
> like -- RedHat has already done that stuff for you).  You
> probably have installed the HOWTO package on your system, and can
> find it by doing something like:
>
> locate PPP-HOWTO
>
> Resulting in a path something like:
> /usr/share/doc/HOWTO/PPP-HOWTO
> for the ascii version.
>
> or
> locate PPP-HOWTO.html
> returning something like:
> /usr/share/doc/HOWTO/other-formats/html/PPP-HOWTO.html
>
> The most recent HOWTOs are always on www.linuxdoc.org
>
> If you want to configure things with the Red Hat style network
> config files, see the initscripts package, (do:
> rpm -qd initscripts
> )
> which should lead you to a terse file giving info on the
> textmode config files used in their GUI utilities:
> /usr/share/doc/initscripts-6.67/sysconfig.txt
> for RH7.3,
> and you can edit them by hand, as I do (easier and more flexible
> than the GUI -- which I can use, but dislike -- too limited).
> They are:
> /etc/sysconfig/network-scripts/chat-ppp0
> /etc/sysconfig/network-scripts/ifcfg-ppp0
> (see attached examples)
> You may have to create the ifcfg file by copying and changing
> one of the other ifcfg files in that directory.
>
> Then you could use the Redhat utils to bring up and take
> down your ppp connection:
> /sbin/ifup ppp0
> /sbin/ifdown ppp0
>
> LCR
>
> --
> L. C. Robinson
> reply to no_spam+munged_lcr@onewest.net.invalid
>
> People buy MicroShaft for compatibility, but get incompatibility and
> instability instead.  This is award winning "innovation".  Find
> out how MS holds your data hostage with "The *Lens*"; see
> "CyberSnare" at http://www.netaction.org/msoft/cybersnare.html
>

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Darragh]

Ok, I've got a bit further.  I got into that PDF file at last.  I've being
trying to use set serial the way it says for the last half an hour.  the
line that I'm using is:  setserial ttys2 uart 16550A irq 5 port 0xd400 thats
giving me an error ttys2: input/output error.  I've tried putting different
numbers between 0 and 6 after ttys but no difference.  I've found two
numbers at the port/I/O line one was 0xd400 and the other was 0xd407.  I've
tried both of these with still no affect.  The other part of the line is
uart 16550A.  I have no idea what thats about, I'm just taking that one from
the document.  I've put the readme at the end of this mail, hopefully
someone could shed some light on it.  I thought at first that I had to edit
the pci file located in the /proc directory but I noticed thanks to pico
that its read only.  There are lines in the read me that aren't found in the
pci file.  Could this be the problem? The lines are "Vender id=151f. Device
id=0." and "medium devsel." After that it goes onto the IRQ.  There is a
line before which says modem rev=0 or something like that, that wasn't
mentioned in the read me but I surmise that this is because it isn't
relivent?

Readme follows:

With Internal Modem:
4.4.1 Manual mode:
1. Find file pci from path / proc, then use vi editor to find Topic vender
ID
"151f" and the I/O-address, IRQ-number that Linux assigns to Topic
modem.
For example : cd / proc
vi pci
---------------------------------------
Vendor id=151f. Device id=0.
Medium devsel. IRQ=5.
I/O at 0xe400 [0xe401].
(Then type q to quit vi)
2. Under path / dev, type setserial tty-number uart 16550A irq IRQ-number
port I/O-address
For example: setserial ttyS2 uart 16550A irq 5 port 0xe400
3. Under path / dev, firstly, remove the default settings that the modem may
linked to, and then link the modem to the tty that you assign on step 2.
For example: rm modem
1n -s ttyS2 modem
4. Now, you can use minicom to test the modem and type ATI3 to check the
type of this
modem.
For example : minicom
----------------
ATI3
4.4.2 Automatic Mode
1. Copy topic.modem executable file to / bin
2. Copy script file rc.serial to /etc/rc.d
3. When you start Linux again, you may see the message of " Setup topic
modem." and it means working properly. If not, you can type topic.modem
TOPIC chipset User's Guide
33
directly.
4. You can use minicom to test the modem.


Thanks again

Darragh

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Henry Yen]

On Wed, Aug 21, 2002 at 03:26:13AM +0100, Darragh wrote:
> Hello again, I had an update today, I found out the manufacturor of my
> modem, e-tech.  I bought it from a German company and although they sent me
> manuals with it they neglected to send me any drivers.  There are no drivers
> for Linux as far as I can tell on the e-tech.nu web site but there is a PDF

according to their website, it appears that they sell both "real hardware"
as well as winmodems, and they do have some support (downloadable drivers)
even for their winmodems -- that's more support than a lot of modem
sellers will give you!

which model of their modems do you have?

> manual.  I'll have to spend a while getting around the security protection
> before JAWS will read it for me but hopefully it will give me some ideas.

if you send me the URL to the pdf, i'll be happy to try to convert it to
plain text.

-- 
Henry Yen                                       Aegis Information Systems, Inc.
Senior Systems Programmer                       Hicksville, New York

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[John]

On Wednesday 21 August 2002 19:11, Darragh wrote:
> purious 8259A interrupt: IRQ7

There's been recent discussion about this on another list. Concensus: it's 
harmless.


-- 


Cheers
John.

Please, no off-list mail. You will fall foul of my spam treatment.
Join the "Linux Support by Small Businesses" list at 
http://mail.computerdatasafe.com.au/mailman/listinfo/lssb

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[John]

Try ttyS2 - capital S.

You almost certainly do not need setserial. PCI devices configure themselves 
inless they're broken.

Using vi to read stuff in /proc is a bad idea - vi will probably try to write 
there. Use the less command instead.

In the particular case of PCI information, best to use the lspci command. It 
has a database and can translate stuff into somewhat compreshensible terms.

Use of minicom is sensible.

On Thursday 22 August 2002 00:24, Darragh wrote:
> Ok, I've got a bit further.  I got into that PDF file at last.  I've being
> trying to use set serial the way it says for the last half an hour.  the
> line that I'm using is:  setserial ttys2 uart 16550A irq 5 port 0xd400 thats
> giving me an error ttys2: input/output error.  I've tried putting different
> numbers between 0 and 6 after ttys but no difference.  I've found two
> numbers at the port/I/O line one was 0xd400 and the other was 0xd407.  I've
> tried both of these with still no affect.  The other part of the line is
> uart 16550A.  I have no idea what thats about, I'm just taking that one from
> the document.  I've put the readme at the end of this mail, hopefully
> someone could shed some light on it.  I thought at first that I had to edit
> the pci file located in the /proc directory but I noticed thanks to pico
> that its read only.  There are lines in the read me that aren't found in the
> pci file.  Could this be the problem? The lines are "Vender id=151f. Device
> id=0." and "medium devsel." After that it goes onto the IRQ.  There is a
> line before which says modem rev=0 or something like that, that wasn't
> mentioned in the read me but I surmise that this is because it isn't
> relivent?
> 
> Readme follows:
> 
> With Internal Modem:
> 4.4.1 Manual mode:
> 1. Find file pci from path / proc, then use vi editor to find Topic vender
> ID
> "151f" and the I/O-address, IRQ-number that Linux assigns to Topic
> modem.
> For example : cd / proc
> vi pci
> ---------------------------------------
> Vendor id=151f. Device id=0.
> Medium devsel. IRQ=5.
> I/O at 0xe400 [0xe401].
> (Then type q to quit vi)
> 2. Under path / dev, type setserial tty-number uart 16550A irq IRQ-number
> port I/O-address
> For example: setserial ttyS2 uart 16550A irq 5 port 0xe400
> 3. Under path / dev, firstly, remove the default settings that the modem may
> linked to, and then link the modem to the tty that you assign on step 2.
> For example: rm modem
> 1n -s ttyS2 modem
> 4. Now, you can use minicom to test the modem and type ATI3 to check the
> type of this
> modem.
> For example : minicom
> ----------------
> ATI3
> 4.4.2 Automatic Mode
> 1. Copy topic.modem executable file to / bin
> 2. Copy script file rc.serial to /etc/rc.d
> 3. When you start Linux again, you may see the message of " Setup topic
> modem." and it means working properly. If not, you can type topic.modem
> TOPIC chipset User's Guide
> 33
> directly.
> 4. You can use minicom to test the modem.
> 
> 
> Thanks again
> 
> Darragh
> 
> 
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
> 

-- 


Cheers
John.

Please, no off-list mail. You will fall foul of my spam treatment.
Join the "Linux Support by Small Businesses" list at 
http://mail.computerdatasafe.com.au/mailman/listinfo/lssb

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Darragh]

Hello all,
Some more updates today.  I have the right name for the modem and a
different web site that allegedly has drivers.  The modem that I'm using is
a Conexant HCF PCI modem and the modle number is 1456pci-r.  I haven't been
able to find drivers on the site for it so haven't got further than that.
In Linux, I've still being trying.  I fixed my error and put a capital S in
ttyS2.  Now, I'm getting an error saying ttyS2 lsr safety check engaged.
trying to free non existant resource 0000b401-0000b400.  ttyS2 lsr safety
check engaged.  When I run wvdialconf again it says ttyS2 safety check
enabled.  I take it by this that its not finding anything on ttys2?  In
windows my modem is on com 3 which in Linux is ttyS2.  Maybe its a driver
thing.  If I don't hear back from the manufacturors I'm going to get another
modem.  The manufacturer of this modem can be found at www.mri.co.uk Could
someone have a look for a driver?  I've had a brief look but Winblows
doesn't like my packet modem so keeps conflicting with the 56K one.

By the way, I could have made a mistake in remembering the second part of
the error message, there were a lot of numbers.  If more information would
be beneficial please mail me and I'll do my best to get it for you.

Thanks again

Darragh
----- Original Message -----
From: "Henry Yen" <blinux-mail@AegisInfoSys.com>
To: <blinux-list@redhat.com>
Sent: Wednesday, August 21, 2002 8:15 PM
Subject: Re: Connecting to the Internet ; editing LIO; setting up the sound
card


> On Wed, Aug 21, 2002 at 03:26:13AM +0100, Darragh wrote:
> > Hello again, I had an update today, I found out the manufacturor of my
> > modem, e-tech.  I bought it from a German company and although they sent
me
> > manuals with it they neglected to send me any drivers.  There are no
drivers
> > for Linux as far as I can tell on the e-tech.nu web site but there is a
PDF
>
> according to their website, it appears that they sell both "real hardware"
> as well as winmodems, and they do have some support (downloadable drivers)
> even for their winmodems -- that's more support than a lot of modem
> sellers will give you!
>
> which model of their modems do you have?
>
> > manual.  I'll have to spend a while getting around the security
protection
> > before JAWS will read it for me but hopefully it will give me some
ideas.
>
> if you send me the URL to the pdf, i'll be happy to try to convert it to
> plain text.
>
> --
> Henry Yen                                       Aegis Information Systems,
Inc.
> Senior Systems Programmer                       Hicksville, New York
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Jude DaShiell]

I wonder what chip set that modem carries?  If it's rockwell, then any of
the rockwell linux drivers should work.

x

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Darragh]

Just a quick one, I'm not too sure what message you were replying to.  I'll
give you the information that I have so far.  www.mri.co.uk  Serial number =
1456pci-r. Name = Conexant HCF PCI modem.  I've found a load of web sites
with drivers.  I'm going to have a look at in the morning again, its now
3.04AM and I've spent a lot of time at it over the last three days.  I've
downloaded two drivers.  I haven't got a clue if their the right ones, they
are:  riptide-0.3mbsibeta02061200k2.4.18_3-1rh.athlon.rpm and
riptide-0.3mbsibeta02061200k2.4.18_4-1rh.athlon.rpm. I don't know if I'm
just giving you useless information but I downloaded the two of them because
I wasn't sure about the number at the end.

Darragh
----- Original Message -----
From: "Jude DaShiell" <jdashiel@shellworld.net>
To: <blinux-list@redhat.com>
Sent: Friday, August 23, 2002 1:37 AM
Subject: Re: Connecting to the Internet ; editing LIO; setting up the sound
card


> I wonder what chip set that modem carries?  If it's rockwell, then any of
> the rockwell linux drivers should work.
>
> x
>
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Buddy Brannan]

Yep, the HCF modems are definitely soft modems.

I'll check linmodems.org for you--I know there are drivers of some sort.
-- 
Buddy Brannan, KB5ELV/3   | "And if the ground yawned,
Phone: (814) 455-7333     | I'd step to the side and say,
Email: davros@ycardz.com  | "Hey ground! I'm nobody's lunch!"
http://www.ycardz.com/    | --Eddie From Ohio

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[John]

On Friday 23 August 2002 10:08, Darragh wrote:
> are:  riptide-0.3mbsibeta02061200k2.4.18_3-1rh.athlon.rpm and
> riptide-0.3mbsibeta02061200k2.4.18_4-1rh.athlon.rpm. I don't know if I'm
> 


Those will not work unless you have an Athlon or Duron. On any Intel system 
they will croak very quickly.
However, there should be i386 rpms or the source rpms somewhere nearby.


-- 


Cheers
John.

Please, no off-list mail. You will fall foul of my spam treatment.
Join the "Linux Support by Small Businesses" list at 
http://mail.computerdatasafe.com.au/mailman/listinfo/lssb

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Henry Yen]

On Thu, Aug 22, 2002 at 08:26:52AM +0100, Darragh wrote:
> a Conexant HCF PCI modem and the modle number is 1456pci-r.  I haven't been
> able to find drivers on the site for it so haven't got further than that.
> In Linux, I've still being trying.  I fixed my error and put a capital S in
> ttyS2.  Now, I'm getting an error saying ttyS2 lsr safety check engaged.
> trying to free non existant resource 0000b401-0000b400.  ttyS2 lsr safety
> check engaged.  When I run wvdialconf again it says ttyS2 safety check
> enabled.  I take it by this that its not finding anything on ttys2?  In

looking on groups.google.com, this message seems to be pointing to an error
during plug-and-play initialization of the modem (search words:
linux lsr safety check modem).

one of the hits there for "conexant hcf linux" yields this little gem:
   http://www.idir.net/~gromitkc/winmodem.html
lots of links there...

-- 
Henry Yen                                       Aegis Information Systems, Inc.
Senior Systems Programmer                       Hicksville, New York

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[John]

On Friday 23 August 2002 10:35, Buddy Brannan wrote:
> Yep, the HCF modems are definitely soft modems.
> 
> 
> I'll check linmodems.org for you--I know there are drivers of some sort.
 

Broken link to the relevant page.

-- 


Cheers
John.

Please, no off-list mail. You will fall foul of my spam treatment.
Join the "Linux Support by Small Businesses" list at 
http://mail.computerdatasafe.com.au/mailman/listinfo/lssb

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[L. C. Robinson]

On Thu, 22 Aug 2002, Darragh wrote:

> Hello all, Some more updates today.  I have the right name for
> the modem and a different web site that allegedly has drivers.
> The modem that I'm using is a Conexant HCF PCI modem and the
> model number is 1456pci-r.

Well, a bit of web searching turned up this site:
http://www.mbsi.ca/cnxtlindrv/index.html

Conexant apparently acquired Rockwell, and the chipset your
modem uses, denoted by the HFC, is a controllerless modem,
which means that it is partially implemented in software (ie,
is not truly a hardware modem).  I believe you said previously
that you asked for a hardware modem, if I remember right, and
made the purchase based on that assumption: if so, you were
ripped off, and that is the primary reason for the many hours you
have wasted, and for the waste of lister's time, too.  My search
was done in hopes of ending that, now that we have enough info.

> I haven't been able to find drivers on the site for it so
> haven't got further than that.

But you can download unsupported linux drivers for it from the
above site.  That doesn't mean you should do so, though.  These
are indeed linux drivers, and there is a Red Hat rpm package
there for you -- but -- and think carefully about this, you may
be buying into a long continued stream of headaches if you use
the modem, even in Winblows (I turned up other sites with drivers
for that OS too, but will not be bothered with posting that).
And you will likely not get the full functionality of the modem
anyway, as explained on the above site.  Plus what do you do when
you need to upgrade the kernel?  Don't even think about using
this modem until you find and read up on the problems and
disadvantages of winmodems, software modems, and the like.  I
have no experience with them, and so, will say no more, and have
no interest in them.

> In Linux, I've still being trying.  I fixed my error and put a
> capital S in ttyS2.

You have more trouble than that, if you are talking about
setserial.  You MUST use "lspci -v" to get the right parameters
for irq and port, as instructed by another poster: guessing
doesn't cut it.

But the better idea is to force your vendor to deliver what he
promised and you paid for: why put up with reduced functionality,
extra hassles, and reduced performance?

> ....
> thing.  If I don't hear back from the manufacturors I'm going
> to get another modem.  The manufacturer of this modem can be
> found at www.mri.co.uk Could someone have a look for a driver?
> I've had a brief look but Winblows doesn't like my packet modem
> so keeps conflicting with the 56K one.

So it doesn't even work in Windoze?....  Ugh.

-- 
L. C. Robinson
reply to no_spam+munged_lcr@onewest.net.invalid

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Darragh]

I'm using an athlon processor.

----- Original Message -----
From: "John" <valhalla@computerdatasafe.com.au>
To: <blinux-list@redhat.com>
Sent: Friday, August 23, 2002 3:58 AM
Subject: Re: Connecting to the Internet ; editing LIO; setting up the sound
card


> On Friday 23 August 2002 10:08, Darragh wrote:
> > are:  riptide-0.3mbsibeta02061200k2.4.18_3-1rh.athlon.rpm and
> > riptide-0.3mbsibeta02061200k2.4.18_4-1rh.athlon.rpm. I don't know if I'm
> >
>
>
> Those will not work unless you have an Athlon or Duron. On any Intel
system
> they will croak very quickly.
> However, there should be i386 rpms or the source rpms somewhere nearby.
>
>
> --
>
>
> Cheers
> John.
>
> Please, no off-list mail. You will fall foul of my spam treatment.
> Join the "Linux Support by Small Businesses" list at
> http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
>
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Darragh]

Looks like my modem was actually recognised by Linux.  I took it out and put
a Trust PCI 56K V92 modem to see what would happen.  It sees that as an
unknown device.  I'm going to take it back out again in try the other one
once more.  I may have this completely wrong, but if Linux recognised my
modem, why was the wvdialconf command not working?  I suppose, It wasn't
just telling me that it couldn't find a modem, it told me that the modem
could be in use by another program.  I'll have to look at my outbox to find
the exact message.  If I put the other modem back in again, I am hoping that
the configuration screen will come back up again.  I may then get a chance
to configure the modem.  Its worth a try any way.

Darragh
----- Original Message -----
From: "L. C. Robinson" <lcr@onewest.net>
To: <blinux-list@redhat.com>
Sent: Friday, August 23, 2002 7:16 AM
Subject: Re: Connecting to the Internet ; editing LIO; setting up the sound
card


> On Thu, 22 Aug 2002, Darragh wrote:
>
> > Hello all, Some more updates today.  I have the right name for
> > the modem and a different web site that allegedly has drivers.
> > The modem that I'm using is a Conexant HCF PCI modem and the
> > model number is 1456pci-r.
>
> Well, a bit of web searching turned up this site:
> http://www.mbsi.ca/cnxtlindrv/index.html
>
> Conexant apparently acquired Rockwell, and the chipset your
> modem uses, denoted by the HFC, is a controllerless modem,
> which means that it is partially implemented in software (ie,
> is not truly a hardware modem).  I believe you said previously
> that you asked for a hardware modem, if I remember right, and
> made the purchase based on that assumption: if so, you were
> ripped off, and that is the primary reason for the many hours you
> have wasted, and for the waste of lister's time, too.  My search
> was done in hopes of ending that, now that we have enough info.
>
> > I haven't been able to find drivers on the site for it so
> > haven't got further than that.
>
> But you can download unsupported linux drivers for it from the
> above site.  That doesn't mean you should do so, though.  These
> are indeed linux drivers, and there is a Red Hat rpm package
> there for you -- but -- and think carefully about this, you may
> be buying into a long continued stream of headaches if you use
> the modem, even in Winblows (I turned up other sites with drivers
> for that OS too, but will not be bothered with posting that).
> And you will likely not get the full functionality of the modem
> anyway, as explained on the above site.  Plus what do you do when
> you need to upgrade the kernel?  Don't even think about using
> this modem until you find and read up on the problems and
> disadvantages of winmodems, software modems, and the like.  I
> have no experience with them, and so, will say no more, and have
> no interest in them.
>
> > In Linux, I've still being trying.  I fixed my error and put a
> > capital S in ttyS2.
>
> You have more trouble than that, if you are talking about
> setserial.  You MUST use "lspci -v" to get the right parameters
> for irq and port, as instructed by another poster: guessing
> doesn't cut it.
>
> But the better idea is to force your vendor to deliver what he
> promised and you paid for: why put up with reduced functionality,
> extra hassles, and reduced performance?
>
> > ....
> > thing.  If I don't hear back from the manufacturors I'm going
> > to get another modem.  The manufacturer of this modem can be
> > found at www.mri.co.uk Could someone have a look for a driver?
> > I've had a brief look but Winblows doesn't like my packet modem
> > so keeps conflicting with the 56K one.
>
> So it doesn't even work in Windoze?....  Ugh.
>
> --
> L. C. Robinson
> reply to no_spam+munged_lcr@onewest.net.invalid
>
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[John]

I'm not at all sure where you are up to. However, there is a significant 
difference between Linux recognising a device and Linux having a driver for 
it.

A few months ago I installed a Netcomm (Australian brand) internal modem. It 
uses a Lucent chipset.

It was a new computer, and first I installed Linux. Linux immediately 
recognised that the modem was there, it finds it by inspecting the PCI bus.

I then went to the linmodems website and located the driver for the Lucent 
chipset, downloaded it and built it according to the instructions.

When that was complete I was able to use the modem to dial the number of my 
mobile phone and so confirm it worked.

Similarly, Linux recognises the AMR devices on the motherboards of many modern 
motherboards, but it doesn't do anything useful with them.

On Saturday 24 August 2002 04:04, Darragh wrote:
> once more.  I may have this completely wrong, but if Linux recognised my
> modem, why was the wvdialconf command not working?  I suppose, It wasn't
> just telling me that it couldn't find a modem, it told me that the modem




-- 


Cheers
John.

Please, no off-list mail. You will fall foul of my spam treatment.
Join the "Linux Support by Small Businesses" list at 
http://mail.computerdatasafe.com.au/mailman/listinfo/lssb

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Darragh]

Hello all,

I've made a few advances today.  I downloaded two drivers for the modem one
was I686 and the other for Athlon.  The one for I686 detected the modem but
got no further but the one for the Athlon processor didn't find it at all.
The reason that this is so strange is this computer is running an Athlon
processor but yet Linux sees it as an I686.  I was briefly thinking that if
Linux correctly detected the processor, would the modem driver that runs
with the athlon processor work?  If so, how can I make the kernel think that
its an Athlon.

Thanks again

Darragh
----- Original Message -----
From: "John" <valhalla@computerdatasafe.com.au>
To: <blinux-list@redhat.com>
Sent: Sunday, August 25, 2002 6:59 AM
Subject: Re: Connecting to the Internet ; editing LIO; setting up the sound
card


>
> I'm not at all sure where you are up to. However, there is a significant
> difference between Linux recognising a device and Linux having a driver
for
> it.
>
> A few months ago I installed a Netcomm (Australian brand) internal modem.
It
> uses a Lucent chipset.
>
> It was a new computer, and first I installed Linux. Linux immediately
> recognised that the modem was there, it finds it by inspecting the PCI
bus.
>
> I then went to the linmodems website and located the driver for the Lucent
> chipset, downloaded it and built it according to the instructions.
>
> When that was complete I was able to use the modem to dial the number of
my
> mobile phone and so confirm it worked.
>
> Similarly, Linux recognises the AMR devices on the motherboards of many
modern
> motherboards, but it doesn't do anything useful with them.
>
> On Saturday 24 August 2002 04:04, Darragh wrote:
> > once more.  I may have this completely wrong, but if Linux recognised my
> > modem, why was the wvdialconf command not working?  I suppose, It wasn't
> > just telling me that it couldn't find a modem, it told me that the modem
>
>
>
>
> --
>
>
> Cheers
> John.
>
> Please, no off-list mail. You will fall foul of my spam treatment.
> Join the "Linux Support by Small Businesses" list at
> http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
>
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[L. C. Robinson]

On Mon, 26 Aug 2002, Darragh wrote:

> I've made a few advances today.  I downloaded two drivers
> for the modem one was I686 and the other for Athlon.  The
> one for I686 detected the modem but got no further but the
> one for the Athlon processor didn't find it at all.

Well, no one is likely to be able to help with info this
vague.  You did not post the URL where you got it, the
package name, whether it was source or binary, whether you
can compile source packages (success would be far more
probable with source, even though it would be only partial).
And specifics about your machine would be necessary, and a
reminder about your exact modem model, brand, etc -- ALL the
particulars.  And the output of "lspci -v", lsdev, "cat
/proc/interrupts", and also similarly the one for the ports,
and any other relevant info.

> The reason that this is so strange is this computer is
> running an Athlon processor but yet Linux sees it as an
> I686.  I was briefly thinking that if Linux correctly
> detected the processor, would the modem driver that runs
> with the athlon processor work?  If so, how can I make the
> kernel think that its an Athlon.

Not strange at all: it's the kernel that matters most here:
the driver must be compiled for that kernel version and
architecture, since it is presumably a kernel module.

You clearly don't understand enough about linux yet to wend
your way through such a complicated problem as getting the
proper driver and getting it working, which is pretty
normal, and to be expected.  And it would be very difficult
to guide you through it on a list for which it is really off
topic, and without enough info.  Look at the Linmodem HOWTO
and web sites that other posters told you about, and see if
there is a mailing list you can join where you can get help
from other masochists <grin> who insist on running what many
of us regard as junk modems (even if you get them "working"
-- in a fashion).

The bottom line here is that getting a winmodem, linmodem,
or other software based modem (or win-printers, or anything
else of that type) to work is a task for advanced users
only, and a questionable, experimental enterprise even at
that: such drivers are likely to be unstable and of low
quality, and may even make your whole system unstable.  It's
not likely that any such drivers are at a gamma or
production release level or similar quality, or ever will
be; certainly, the ones at the web site I gave you clearly
state that they are no where near such quality, and take
they pains to warn you about that; they're not kidding or
just only making a legal disclaimer.  They include
unsupported propriety binary code, too: my advice is never
to accept hardware that requires proprietary driver code
under linux -- that's generally a warning sign of poor
quality, and future support problems (are you prepared to
throw out such hardware when you get a kernel upgrade, and
you cannot recompile the code, because you don't have
source)?  I am, therefore, opposed to supporting them for
new users, lest they give Linux a bad name (you certainly
won't get any help from me).

Such hardware can be obsoleted when there is a windoze
upgrade, too, for similar reasons: M$ says that one if the
biggest reasons for the well known Windoze OS instability is
poorly written 3rd party drivers (and for once, their claims
are credible).

Your best bet is to junk it, and get an external modem
(external modems cannot be implemented as winmodems, or
require special drivers).  An external modem should be easy
to set up -- indeed, it would possibly be automatically
detected and configured for you during bootup, by the kudzu
utility.

So now I have helped you, after all, more than if I had
guided you through installing a buggy driver for inferior
hardware.

Good luck and best wishes, LCR

-- 
L. C. Robinson
reply to no_spam+munged_lcr@onewest.net.invalid

People buy MicroShaft for compatibility, but get incompatibility and
instability instead.  This is award winning "innovation".  Find
out how MS holds your data hostage with "The *Lens*"; see
"CyberSnare" at http://www.netaction.org/msoft/cybersnare.html

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Shaun Oliver]

*SNIP*
how can I make the kernel think that
its an Athlon.
the answer is simple.
You need to recompile the kernel.  However, if you've had no experience
with kernel compiling, I'd suggest you go read all the docs you can before
attempting it.
it's not hard once you figure out you're configuration but, at first it
can appear daunting. I speak from experience as would most of us here
would agree.
hth


-- 
Shaun Oliver


In a world without fences
          and walls who needs Windows and Gates?

EMAIL: shaun_oliver@optusnet.com.au
ICQ: 76958435

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[L. C. Robinson]

On Tue, 27 Aug 2002, Shaun Oliver wrote:

> how can I make the kernel think that
> its an Athlon.
> the answer is simple.
> You need to recompile the kernel.  However, if you've had no experience
> ...

Or even simpler.  Just install the athlon kernel Red Hat
provides:
kernel-2.4.18-3.athlon.rpm from the CD (out of date,
insecure)

But you need the updated version anyway:
ftp://updates.redhat.com/7.3/en/os/athlon/kernel-2.4.18-10.athlon.rpm

It used to be traditional to recompile your kernel with each
new patchlevel, from the beta kernel version 0.99 days, when
I started, but now I have better things to do with my time:
Red Hat maintains it for me, with all the hundreds of
modules (drivers).  You may need speakup: see the speakup
site about that (still not complicated -- just follow the
recipe).

And what will you get for your trouble?  You will NOT be
rewarded with a noticeable performance difference, unless
you are operating a heavily loaded server, not the personal
home machine you have.  So the reason for the upgrade is
primarily for security and bug fixes.

Note that installing an athlon optimized kernel WILL NOT
make your modem work (but your driver module package
architecture must match if you download the right binary
package -- among many other more important things).

Oh, and be sure to read the Red Hat advisory about the
kernel upgrade, and carefully follow the procedure they
direct you to -- or your system will be bootable only with a
rescue disk.  You should be subscribed to the RH mailing
list for announcements (and probably their help list, too),
so you get these advisories, and know where to get the
previous ones.

LCR

-- 
L. C. Robinson
reply to no_spam+munged_lcr@onewest.net.invalid

People buy MicroShaft for compatibility, but get incompatibility and
instability instead.  This is award winning "innovation".  Find
out how MS holds your data hostage with "The *Lens*"; see
"CyberSnare" at http://www.netaction.org/msoft/cybersnare.html

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Shaun Oliver]

ok, I'll conceed that point,
given that I use slackware, I'd have to recompile my kernel but in any
case, it would give him good kernel building practise.
you've got to learn sometime unless something breaks.
besides does red hat allow for speakup, I know that bill acker might
maintain a kernel image for the athlon but I won't be quoted on it unless
I'm proved to be wrong.


-- 
Shaun Oliver


In a world without fences
          and walls who needs Windows and Gates?

EMAIL: shaun_oliver@optusnet.com.au
ICQ: 76958435

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Darragh]

Hello
I've got further today than I have all week.  I found a generic driver on a
French web site that I found this morning.  I got it to work at last and ran
the wvdialconf command.  at first it said that it couldn't write to the
config file because it was busy.  I tried a few variations of the wvdialconf
command and eventually got it to work by typing /usr/bin/wvdialconf
/etc/wvdial.conf that worked and I edited the file.  I ran wvdial but it
said that it couldn't find the right phone number, user name or password.  I
updated cron and found a file called wvdial.conf~ but when I try to edit it
in emacs it tells me that the buffer is read only.  I tried to rename the
wvdial.conf file to wvdial.conf~ but that didn't work either.  Can any one
help?  I was under the impression that if I used the line wvdialconf
/usr/bin/wvdialconf it would edit the /etc/wvdial.conf config file.

Darragh
P.S. I've found somewhere that I should use touch /etc/wvdial.conf to create
the file /etc/wvdial.conf to allow wvdialconf to edit it.
----- Original Message -----
From: "Shaun Oliver" <shaun_oliver@optusnet.com.au>
To: <blinux-list@redhat.com>
Sent: Tuesday, August 27, 2002 11:30 AM
Subject: Re: Connecting to the Internet ; editing LIO; setting up the sound
card


> ok, I'll conceed that point,
> given that I use slackware, I'd have to recompile my kernel but in any
> case, it would give him good kernel building practise.
> you've got to learn sometime unless something breaks.
> besides does red hat allow for speakup, I know that bill acker might
> maintain a kernel image for the athlon but I won't be quoted on it unless
> I'm proved to be wrong.
>
>
> --
> Shaun Oliver
>
>
> In a world without fences
>           and walls who needs Windows and Gates?
>
> EMAIL: shaun_oliver@optusnet.com.au
> ICQ: 76958435
>
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Shaun Oliver]

*SNIP*
I was under the impression that if I used the line wvdialconf
/usr/bin/wvdialconf it would edit the /etc/wvdial.conf config file.
a fake.
try wvdialconf /etc/wvdial.conf
and run it as root.
otherwise you won't be able to edit it.
hth


-- 
Shaun Oliver


In a world without fences
          and walls who needs Windows and Gates?

EMAIL: shaun_oliver@optusnet.com.au
ICQ: 76958435

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Darragh]

Hello Sean,

Unfortunately I got the same result.  Maybe if I could change the attributes
on that wvdial.conf~ file to let me change it the wvdial command might work?
I have a feeling that its trying to read the information from that file
instead of the normal wvdial.conf file.

Darragh
----- Original Message -----
From: "Shaun Oliver" <shaun_oliver@optusnet.com.au>
To: <blinux-list@redhat.com>
Sent: Tuesday, August 27, 2002 1:17 PM
Subject: Re: Connecting to the Internet ; editing LIO; setting up the sound
card


> *SNIP*
> I was under the impression that if I used the line wvdialconf
> /usr/bin/wvdialconf it would edit the /etc/wvdial.conf config file.
> a fake.
> try wvdialconf /etc/wvdial.conf
> and run it as root.
> otherwise you won't be able to edit it.
> hth
>
>
> --
> Shaun Oliver
>
>
> In a world without fences
>           and walls who needs Windows and Gates?
>
> EMAIL: shaun_oliver@optusnet.com.au
> ICQ: 76958435
>
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Darragh]

By the way, I just thought I should give some more information.  I
downloaded some drivers today but I kept getting an error message that they
weren't compatible with my kernel.  As you may see, I downloaded drivers for
both the athlon and i386 configurations but I had the same results for them
all.  My computer specification modem type and moddle number plus the
drivers that I've download so far are below.

Thanks

Darragh
Computer and operating system details follow
Modem name : Conexant HCF PCI modem
Moddle number : 1456pci-r
AMD XP 2100+
Globalwin cooler
Epox 8KHAL
32MB TNT2 AGP graphics card
512MB DDR
80GB hard drive
16x/10x/40x CD-RW
16x/48x DVD Slot in
Typhoon digital sound card
3Com 10/100 network card
Floppy drive
300W ATX Midi tower
Operating system name : Red hat 7.3
Kurnel version : 2.4.18_5spk
The kurnel sees my processor as an I686

Drivers downloaded so far are:
hsflinmodem-5.03.03.L3mbsibeta02082400k2.4.18_5-1rh.athlon.rpm
hsflinmodem-5.03.03.L3mbsibeta02082400k2.4.18_5-1rh.i686.rpm
hcfpcimodem-0.97mbsibeta02070500k2.4.18_4-1rh.i686.rpm
hcfpcimodem-0.97mbsibeta02070500k2.4.18_4-1rh.athlon.rpm
hcfpcimodem-0.97mbsibeta02070500-1.i386.rpm


----- Original Message -----
From: "Shaun Oliver" <shaun_oliver@optusnet.com.au>
To: <blinux-list@redhat.com>
Sent: Tuesday, August 27, 2002 1:17 PM
Subject: Re: Connecting to the Internet ; editing LIO; setting up the sound
card


> *SNIP*
> I was under the impression that if I used the line wvdialconf
> /usr/bin/wvdialconf it would edit the /etc/wvdial.conf config file.
> a fake.
> try wvdialconf /etc/wvdial.conf
> and run it as root.
> otherwise you won't be able to edit it.
> hth
>
>
> --
> Shaun Oliver
>
>
> In a world without fences
>           and walls who needs Windows and Gates?
>
> EMAIL: shaun_oliver@optusnet.com.au
> ICQ: 76958435
>
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Darragh]

Ok, I made a very stupid mistake yesterday which I was able to fix with
chmod this morning.  Now, I'm getting as far as wvdial asining the computer
an IP address, then it says connecting to pppd on "date" but doesn't go any
further.  It is dialling though so I'm getting there slowly but surely.

Darragh
----- Original Message -----
From: "Jude DaShiell" <jdashiel@shellworld.net>
To: "Darragh" <darraghoheiligh@eircom.net>
Sent: Tuesday, August 27, 2002 10:35 PM
Subject: Re: Connecting to the Internet ; editing LIO; setting up the sound
card


> You have to put the right phone number into wvdial.conf along with the
> right user name and password.  Read the man page on wvdial to learn how.
> The stuff you need is well into the man page but it'll show you correct
> entries for wvdial.conf so the system won't hurl on you on your next
> connect attempt.
>
> x
>
>
>

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[L. C. Robinson]

On Wed, 28 Aug 2002, Darragh wrote:

> Now, I'm getting as far as wvdial asining the computer an
> IP address, then it says connecting to pppd on "date" but
> doesn't go any further.  It is dialling though so I'm
> getting there slowly but surely.

Well, it sounds like you have fully succeeded in getting
your modem to work, if it is logging in to your ISP with
username and password, which seems to be implied here.  When
wvdial invokes pppd, it is done, control is passed to pppd,
and any output from then on will come from pppd.  The pppd
output normally goes through syslogd (you don't want to see
any of it while you are reading email, browsing, etc), and
syslogd normally adds it to /var/log/messages.  Any problems
pppd reports there (hopefully none) are due to
misconfiguration of pppd.  Maybe you are online!  In any
event, congratulations for this step forward: your average
new user just isn't tenacious enough to go through what you
have, in order to get a winmodem working.

LCR

-- 
L. C. Robinson
reply to no_spam+munged_lcr@onewest.net.invalid

People buy MicroShaft for compatibility, but get incompatibility and
instability instead.  This is award winning "innovation".  Find
out how MS holds your data hostage with "The *Lens*"; see
"CyberSnare" at http://www.netaction.org/msoft/cybersnare.html

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[Darragh]

Well, after getting your mail I went to the system.conf file and changed a
few lines around to send the log files from pppd from the messages file to a
new ppp file.  I then used the tail -f command to read that file as its been
written.  when I use wvdial I don't think it tells pppd to write a log by
default.  In any case nothings being written to the file.  On the output
from wvdial I get as far as the line "Starting pppd on [date]" then it just
stops.  I've tried a few pppd commands in different consoles such as pppd
debug CONNECT '\d\c' or '\client' with no success.  A line that I typed did
connect but couldn't validate my log in information This as I understand it
is because wvdial passes the user name and password to the ISP not pppd.
The Line that I used to connect with pppd was /usr/sbin/pppd /dev/ttyS3
57600 debug connect "/usr/sbin/chat -v   ''   'AT&F0'   OK   ATD1891110110
CONNECT   '\d\c' " That line is from memory so excuse me if I have written
any mistakes.  I realize that I have the modem speed very low, this is
because I wanted to make sure that any faults were not as a result of speed.

Could the problem be that wvdial can not find pppd?  I doubt this as it says
starting pppd but at this stage anything's possible.  Or, Could there be a
line missing in wvdial.conf?  The last line that I have is password.

Darragh

----- Original Message -----
From: "L. C. Robinson" <lcr@onewest.net>
To: <blinux-list@redhat.com>
Sent: Thursday, August 29, 2002 1:08 AM
Subject: Re: Connecting to the Internet ; editing LIO; setting up the sound
card


> On Wed, 28 Aug 2002, Darragh wrote:
>
> > Now, I'm getting as far as wvdial asining the computer an
> > IP address, then it says connecting to pppd on "date" but
> > doesn't go any further.  It is dialling though so I'm
> > getting there slowly but surely.
>
> Well, it sounds like you have fully succeeded in getting
> your modem to work, if it is logging in to your ISP with
> username and password, which seems to be implied here.  When
> wvdial invokes pppd, it is done, control is passed to pppd,
> and any output from then on will come from pppd.  The pppd
> output normally goes through syslogd (you don't want to see
> any of it while you are reading email, browsing, etc), and
> syslogd normally adds it to /var/log/messages.  Any problems
> pppd reports there (hopefully none) are due to
> misconfiguration of pppd.  Maybe you are online!  In any
> event, congratulations for this step forward: your average
> new user just isn't tenacious enough to go through what you
> have, in order to get a winmodem working.
>
> LCR
>
> --
> L. C. Robinson
> reply to no_spam+munged_lcr@onewest.net.invalid
>
> People buy MicroShaft for compatibility, but get incompatibility and
> instability instead.  This is award winning "innovation".  Find
> out how MS holds your data hostage with "The *Lens*"; see
> "CyberSnare" at http://www.netaction.org/msoft/cybersnare.html
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>

Re: Connecting to the Internet ; editing LIO; setting up the sound card

[L. C. Robinson]

On Thu, 29 Aug 2002, Darragh wrote:

> Well, after getting your mail I went to the system.conf

You mean /etc/syslog.conf?

> file and changed a few lines around to send the log files
> from pppd from the messages file to a new ppp file.

Not possible to send just pppd lines off to a different
file.  You can only control "facilities", such as "daemon",
which affects other things than just pppd.  It's a bad idea
to mess with syslog.conf, unless you really know what your
doing.  Use the:

logfile /var/log/pppd.log(or whatever)

option to pppd instead (you can put your options in the
/etc/ppp/options file).  Syslog will still send stuff to the
usual logfile at the same time: don't try to change that.

> I then used the tail -f command to read that file as its
> been written. 

Good approach.  You could also just do:
tail -f /var/log/messages

We monitor the messages file on a separate tty (virtual
screen) all the time with a similar option to the "less"
command.

> In any case nothings being written to the file.

And now you know why.

> On the output from wvdial I get as far as the line
> "Starting pppd on [date]" then it just stops.

Which is what it's supposed to do.

> I've tried a few pppd commands in different consoles such
> as pppd debug CONNECT '\d\c' or '\client' with no success.
> A line that I typed did connect but couldn't validate my
> log in information This as I understand it is because
> wvdial passes the user name and password to the ISP not
> pppd.  The Line that I used to connect with pppd was
> /usr/sbin/pppd /dev/ttyS3

ttyS2, or ttyS3?  (change in script below, as necessary).

> 57600 debug connect "/usr/sbin/chat -v   ''   'AT&F0'   OK
> ATD1891110110 CONNECT   '\d\c' "

Yes, these pppd commands are broken.  Chat is a dialer you
use as an alternative to wvdial, to dial up your ISP, not at
the same time: chat is a bit trickier to configure than
wvdial, but more reliable and flexible (I prefer it).  Do
you still have your copy of the example chat script I sent
to you earlier in this thread?  Wvdial fails with my ISP
around 5% of the time, for no identifiable reason.  Chat
always works.

The Red Hat connection scripts I mentioned to you earlier
generate a pppd command something like this, depending on
your configuration:

#!/bin/sh
# The actual ppp startup command that is generated by 
# RedHat ppp startup scripts is stored here each time
# we start up, from a modification in
# /etc/sysconfig/network-scripts/ifup-ppp

# Cut first word off for direct use (commented out):
# exec \

/usr/sbin/pppd -detach lock modem crtscts asyncmap \
00000000 defaultroute user Darragh remotename ppp0 \
/dev/ttyS2 115200 ipparam ppp0 linkname ppp0 noauth \
debug \
logfile /var/log/pppd.log \
connect "/usr/sbin/chat  -f /etc/sysconfig/network-scripts/chat-ppp0"

# ***** end of script -- cut here ****

Make sure you install that last chat script file (the quoted
argument to the "connect" option).  Note that the ppp
command is all one line: I used backslashes to "hide" the
newline for continuation lines, so that the mailer couldn't
mung the long command.  I added the debug and logfile
options.

Actually, you can store all the options in the pppd options
file mentioned, and just start pppd as root (see "man pppd"
for details).

You mentioned something about authentication problems: it
may be that your ISP uses PAP authentication, instead of
logging in directly through your chat script or wvdial
(again, see the man page).  You should be able to figure out
what is going on, and debug the connection process by
watching the log files, as you guessed.  Post actual copies
of problematic parts of logfile output, in context, if you
have more questions, along with the options and
configurations used.  Do this in labeled attachments if
voluminous, so that listers need not all read the nitty
gritty details.

After you get it all working:

Red Hat has a scheme where ordinary users can start pppd
safely: see "man usernetctl" which is really called from
scripts detailed on that man page.  You don't want to have
to become root everytime you connect -- root power should be
used as sparingly as possible.  Never make pppd SUID root.

LCR
 
> ----- Original Message -----
> From: "L. C. Robinson" <lcr@onewest.net>
> To: <blinux-list@redhat.com>
> Sent: Thursday, August 29, 2002 1:08 AM
> Subject: Re: Connecting to the Internet ; editing LIO; setting up the sound
> card
> 
> > On Wed, 28 Aug 2002, Darragh wrote:
> >
> > > Now, I'm getting as far as wvdial asining the computer an
> > > IP address, then it says connecting to pppd on "date" but
> > > doesn't go any further.  It is dialling though so I'm
> > > getting there slowly but surely.
> >
> > Well, it sounds like you have fully succeeded in getting
> > your modem to work, if it is logging in to your ISP with
> > username and password, which seems to be implied here.  When
> > wvdial invokes pppd, it is done, control is passed to pppd,
> > and any output from then on will come from pppd.  The pppd
> > output normally goes through syslogd (you don't want to see
> > any of it while you are reading email, browsing, etc), and
> > syslogd normally adds it to /var/log/messages.  Any problems
> > pppd reports there (hopefully none) are due to
> > misconfiguration of pppd.  Maybe you are online!  In any
> > event, congratulations for this step forward: your average
> > new user just isn't tenacious enough to go through what you
> > have, in order to get a winmodem working.

-- 
L. C. Robinson
reply to no_spam+munged_lcr@onewest.net.invalid

People buy MicroShaft for compatibility, but get incompatibility and
instability instead.  This is award winning "innovation".  Find
out how MS holds your data hostage with "The *Lens*"; see
"CyberSnare" at http://www.netaction.org/msoft/cybersnare.html