SupraExpress Modem problems

[Ianwev]

Please could you tell me were I can get a driver for windows XP to go with my
SupraExpress 56e PRO modem. I want to download this from the Internet if posible.

Yours Ian Weatherhead.

Re: More modem problems with kernel 2.4.18

[Vineet Kumar]

* Paul Johnson ([EMAIL PROTECTED]) [020621 00:17]:
> On Thu, Jun 20, 2002 at 11:44:21PM -0700, Vineet Kumar wrote:
> > Where's the misunderstanding?

On my part, to be sure. (Re-reading this I realize that I didn't word it
so as to imply that that was my guess; apologies if it sounded rude.)

> The line noise isn't worth it on the phone line.  Yeah, it cleans up the
> power lines pretty well, but it takes a bit more to keep a phone line
> noise-free and [external] modems a bit more tollerant to phone line
> voltage changes from my experiance.  You can go with a surge suppressor
> on the phone line, but you won't get quite the same speed, especially
> past 28.8kbps.

I hadn't any experience here; thanks for the info.

good times,
Vineet
-- 
http://www.doorstop.net/
-- 
Satan laughs when we kill each other. Peace is the only way.


pgpAc8luIrBDD.pgp
Description: PGP signature

Re: More modem problems with kernel 2.4.18

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Jun 20, 2002 at 11:44:21PM -0700, Vineet Kumar wrote:

> [CPU]--serial-cable--[modem]--phone-line--wall
>  |  |
>  |  power cord
>  |  |
>  +-[surge protector]---wall

[CPU]--serial cable--[modem]--phone---wall
 |  |
 |  |
 |  |
 +-power cord-[surge protector]---wall

> Where's the misunderstanding?

The line noise isn't worth it on the phone line.  Yeah, it cleans up the
power lines pretty well, but it takes a bit more to keep a phone line
noise-free and [external] modems a bit more tollerant to phone line
voltage changes from my experiance.  You can go with a surge suppressor
on the phone line, but you won't get quite the same speed, especially
past 28.8kbps.

Cable modems and televisions are a different story: surge suppressors
with coax cable hookups are pure evil.  If they decide to go flaky,
it'll start throwing line noise back onto the cable line, and you'll
slow everybody in your neighborhood down and give them bad TV reception
on 2 and 3, and in extreme cases, as high as channel 10 or 12.  The
cable company will roll trucks when there's complaints of bad signal,
and if they can't find it on thier line, they'll start trying to trace
it back to the house.  If it turns out to be your equipment doing it,
the cable company will charge you for thier inconvienence, expect an
extra $100 or so on your bill if you were the cause.  Cable surge
suppressors were a pet peeve of mine when I worked the phones for @Home. 
Don't bother with them at all, especially if you lease a cable convertor
or cable modem from them.  Those will eat it and die without passing
voltage on to your network or other AV equipment, and the cable company
will send someone out to replace them free of charge (this is a
compelling reason not to buy your own cable modem.  That, and if
something breaks, you won't get modem support from your cable operator
if you own your own modem, beyond getting it configured (which is thier
problem).  Furthermore, AT&TBI is reducing lease prices on thier cable
modems by $7 and raising service prices by $7, so you'll only save $3
with your own modem, not $10.  The increase was to cover a reduced
demand for broadband and increased costs associated dealing with flaky,
cheapass modems the cheapskates tended to buy to avoid lease fees)

- -- 
Baloo


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9EtL2NtWkM9Ny9xURAlc8AJ9zkdcFap8zLhsWN322TRwCarsiMACgm2D3
GMW1KZNocL+Uo2P7vMP21fA=
=1nZP
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: More modem problems with kernel 2.4.18

[Vineet Kumar]

* Paul Johnson ([EMAIL PROTECTED]) [020620 23:28]:
> On Thu, Jun 20, 2002 at 11:24:50PM -0700, Vineet Kumar wrote:
> > You should be able to find a surge protector with RJ11 jacks on it for
> > around $9.95 at circuit city...
> 
> These tend to introduce a considerable amount of line noise and you end
> up plugging your modem into two things that can get hit by lightning...

Really? I've actually found that surge protectors generally decrease
line noise, but that's speaking of home stereo equipment. I've never
done any testing on phone lines through it.

You've also lost me on how this is adding any points of potential
lightning. Sans surge protector, you'd have:

[CPU]--serial-cable--[modem]--phone-line--wall
 |  |
 |  power cord
 |  |
 +-[surge protector]---wall

With a surge protector, you have this:

[CPU]--serial-cable--[modem]--phone-line-+
  | ||
  | power cord   |
  | ||
  | +--[surge protector]--wall
  |  |   |
  +---power-cord-+   |
 |
wall


In either case, lightning comes in from the wall, but in the second
case, you're protected wherever it comes from.

Where's the misunderstanding?

good times,
Vineet
-- 
http://www.doorstop.net/
-- 
http://www.aclu.org/


pgpdLIT7S4vpG.pgp
Description: PGP signature

Re: More modem problems with kernel 2.4.18

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Jun 20, 2002 at 11:24:50PM -0700, Vineet Kumar wrote:

> You should be able to find a surge protector with RJ11 jacks on it for
> around $9.95 at circuit city...

These tend to introduce a considerable amount of line noise and you end
up plugging your modem into two things that can get hit by lightning...

- -- 
Baloo


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9Esd7NtWkM9Ny9xURAp/bAJ9tkmkCVDRMSsLV4GPcnD2FVe7RtgCfRiOL
8xys94kClcl1qQY2Z0ETPeQ=
=xdV3
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: More modem problems with kernel 2.4.18

[Vineet Kumar]

* Paul Johnson ([EMAIL PROTECTED]) [020620 19:43]:
> price doesn't seem to play a factor in, and the last thing I want is a
> device I plug into a line I know goes to the top of telephone poles
> subject to lightning strikes slapped directly on my motherboard. 
> 
> Another advantage with externals is you have some hope of destroying the
> modem before the strike voltage goes on to the computer...

You should be able to find a surge protector with RJ11 jacks on it for
around $9.95 at circuit city...

good times,
Vineet
-- 
http://www.doorstop.net/
-- 
Satan laughs when we kill each other. Peace is the only way.


pgp5Z3ue6t4lF.pgp
Description: PGP signature

Re: More modem problems with kernel 2.4.18

[ben]

On Thursday 20 June 2002 10:22 pm, Paul Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, Jun 20, 2002 at 09:43:14PM -0700, ben wrote:
> > you might have a case there, baloo (don't even pardon the pun). give us a
> > date on the settlement party.
>
> I'm not suing Koolance.  The case edge was obviously capable of breaking
> skin (as is anything made of any gauge of sheet metal, really).  And I
> should have let the lid fall to the floor where the worst it would do is
> go *thud* on the carpet.  I'd love to LART folks who do things as stupid
> as what I did and then sue the manufacturer of the product they did it
> with...
>

bummer. no party, then. neosporin is the way to go.

ben


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: More modem problems with kernel 2.4.18

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Jun 20, 2002 at 09:43:14PM -0700, ben wrote:

> you might have a case there, baloo (don't even pardon the pun). give us a 
> date on the settlement party.

I'm not suing Koolance.  The case edge was obviously capable of breaking
skin (as is anything made of any gauge of sheet metal, really).  And I
should have let the lid fall to the floor where the worst it would do is
go *thud* on the carpet.  I'd love to LART folks who do things as stupid
as what I did and then sue the manufacturer of the product they did it
with...

- -- 
Baloo


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9ErgBNtWkM9Ny9xURAs+pAJ4o2ftQC9/XoTFdzg2fTPnSd72p4ACfW6lx
HHVt0Mccpi0YHZbL0b8vdS4=
=fb2m
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: More modem problems with kernel 2.4.18

[ben]

On Thursday 20 June 2002 09:07 pm, Paul Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, Jun 20, 2002 at 09:05:47PM -0700, ben wrote:
> > On Thursday 20 June 2002 08:32 pm, Paul Johnson wrote:
> > > a clean cut and healed nicely without professional attention.  The case
> > > in question is a Koolance PC6-2 not a bad case, the lid has rounded
> > > corners, I just really caught it wrong.
> >
> > so the rounded corner isn't simply a benign logical fallacy, but a
> > dangerous physical illusion? who knew?
>
> Basically, yes.  I think I'm going to have a permanent scar on the palm
> of my hand now from that experiance...
>

you might have a case there, baloo (don't even pardon the pun). give us a 
date on the settlement party.

ben


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: More modem problems with kernel 2.4.18

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Jun 20, 2002 at 09:05:47PM -0700, ben wrote:
> On Thursday 20 June 2002 08:32 pm, Paul Johnson wrote:
> > a clean cut and healed nicely without professional attention.  The case
> > in question is a Koolance PC6-2 not a bad case, the lid has rounded
> > corners, I just really caught it wrong.
> 
> so the rounded corner isn't simply a benign logical fallacy, but a dangerous 
> physical illusion? who knew?

Basically, yes.  I think I'm going to have a permanent scar on the palm
of my hand now from that experiance...

- -- 
Baloo


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9EqZ8NtWkM9Ny9xURAm6sAJ0RBpFs0ip5NeWYXvJW2Ip/uaV87QCfQIrV
Lh0i7dWDaBiRn73o7MjureE=
=7AYQ
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: More modem problems with kernel 2.4.18

[ben]

On Thursday 20 June 2002 08:32 pm, Paul Johnson wrote:
[snip]
>
> I hate dealing with opening the case, even though it's held on by two
> thumbscrews and a padlock.  Last time I opened it, I dropped the case
> lid, and when I tried to catch it, one corner stuck into the wall, and
> the other corner stabbed into my hand to the bone.  Fortunately, it was
> a clean cut and healed nicely without professional attention.  The case
> in question is a Koolance PC6-2 not a bad case, the lid has rounded
> corners, I just really caught it wrong.
>

so the rounded corner isn't simply a benign logical fallacy, but a dangerous 
physical illusion? who knew?

ben


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: More modem problems with kernel 2.4.18

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Jun 20, 2002 at 08:16:03PM -0700, ben wrote:

> modems also generate heat; an external modem reduces the cooling load on the 
> system. on top of that, anything that, on breakage, demands that i take the 
> cover off the box just pisses me off for at least half a day. so, at least in 
> my case, that's two good reasons to use an external.

That, and you don't loose your uptime if you need to replace an external
modem.  8:o)

I hate dealing with opening the case, even though it's held on by two
thumbscrews and a padlock.  Last time I opened it, I dropped the case
lid, and when I tried to catch it, one corner stuck into the wall, and
the other corner stabbed into my hand to the bone.  Fortunately, it was 
a clean cut and healed nicely without professional attention.  The case
in question is a Koolance PC6-2 not a bad case, the lid has rounded
corners, I just really caught it wrong.

- -- 
Baloo


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9Ep5WNtWkM9Ny9xURAkgNAJ9qKLD2vWqkubOXkGR7wgCJ+AhzXQCfSAKs
cwD5qKzOGlWZm2SplZaoerw=
=64gY
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: More modem problems with kernel 2.4.18

[ben]

On Thursday 20 June 2002 07:36 pm, Paul Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, Jun 20, 2002 at 04:54:25PM -0700, Seth Carbon wrote:
> > I have seen the light.  External good.  LEDs are *very helpful* for
> > diagnostics.
>
> Wouldn't that be, "I have seen the lights?"  8:o)
>
> See how much easier that was?  I hate internal modems because they're a
> pain to diagnose, they're typically of extremely poor quality of which
> price doesn't seem to play a factor in, and the last thing I want is a
> device I plug into a line I know goes to the top of telephone poles
> subject to lightning strikes slapped directly on my motherboard.
>
> Another advantage with externals is you have some hope of destroying the
> modem before the strike voltage goes on to the computer...
>

modems also generate heat; an external modem reduces the cooling load on the 
system. on top of that, anything that, on breakage, demands that i take the 
cover off the box just pisses me off for at least half a day. so, at least in 
my case, that's two good reasons to use an external.

ben


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: More modem problems with kernel 2.4.18

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Jun 20, 2002 at 04:54:25PM -0700, Seth Carbon wrote:

> I have seen the light.  External good.  LEDs are *very helpful* for
> diagnostics.

Wouldn't that be, "I have seen the lights?"  8:o)

See how much easier that was?  I hate internal modems because they're a
pain to diagnose, they're typically of extremely poor quality of which
price doesn't seem to play a factor in, and the last thing I want is a
device I plug into a line I know goes to the top of telephone poles
subject to lightning strikes slapped directly on my motherboard. 

Another advantage with externals is you have some hope of destroying the
modem before the strike voltage goes on to the computer...

- -- 
Baloo


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9EpE6NtWkM9Ny9xURAhHFAJ9M7gsqwNw3w5Gj/hyc7uzdFytaNACdHCVy
3zK9wAV+RBdO43MYJZ7iC5E=
=LLZf
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: More modem problems with kernel 2.4.18

[Seth Carbon]

> Your internal modem, if roasted and ground sufficiently fine, will make
> a surprisingly strong espresso.  Go get an external modem.
> 
> http://www.linuxmafia.com/~rick/faq/#internalmodem

*Sigh*

At first I thought this advice was unhelpful and a bit short.  Then I
spent another two days playing with the kernel and jumpers on the mother
board and ISA card.

Finally, out of despair, I bought an external modem (a USR, but not a
Courier--I'm on a tight budget right now--but when I get some
money...).  I was able to troubleshoot and get things to work in ten
minutes.

I have seen the light.  External good.  LEDs are *very helpful* for
diagnostics.

Thanks,

-Seth



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Re: More modem problems with kernel 2.4.18

[Seth Carbon]

> Have you taken a look in /etc/serial.conf?  Check very carefully to see if
> any lines are uncommented, and if so that they match what your modem setup
> really is.

Thanks for the idea :)

I have just checked my serial.conf and it seemed alright--but I've
played with it for the past hour anyways.  Still no progress--no matter
what I put in there, the irq still shows as 5 with dmesg and does not
exist in /proc/interrupt.

-Seth
 [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Re: More modem problems with kernel 2.4.18

[Bob Hauck]

On 18 Jun 2002, Seth Carbon wrote:

> 1) The modem has worked fine with every kernel I've put in since I
> installed potato.  Now both potato (with bunk's upgrades) and woody
> fail.

Have you taken a look in /etc/serial.conf?  Check very carefully to see if
any lines are uncommented, and if so that they match what your modem setup
really is.


-- 
 -| Bob Hauck
 -| To Whom You Are Speaking
 -| http://www.haucks.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

[sjcarbon@eskimo.com: Re: More modem problems with kernel 2.4.18]

[Paul Johnson]

Throwing this back over the fence...

-- 
Baloo


--- Begin Message ---
On Tue, 2002-06-18 at 03:13, Paul Johnson wrote:
> Your internal modem, if roasted and ground sufficiently fine, will make
> a surprisingly strong espresso.  Go get an external modem.
> 
> http://www.linuxmafia.com/~rick/faq/#internalmodem

Even if I'm destined for a good string cup, I'd still like to be able to
figure out what's going on :)

Some thoughts before I go the external road:

1) The modem has worked fine with every kernel I've put in since I
installed potato.  Now both potato (with bunk's upgrades) and woody
fail.

2) /proc/* information and setserial information are at odds with each
other.  I mean--jeez--the irq info is missing altogether...

3) The system refuses to even acknowledge that there may be a modem
there in the first place, making it hard to diagnose once running.

All of this seems to indicate to me that there may be some kernel
bug--but I have no idea where to start if it is. This modem is
definitely not a win/linmodem.  I have also spend some time playing with
the jumpers trying to give the kernel (if it even is a kernel problem) a
friendly reminder of what the proper information is--but to no avail.

Any further thoughts (would I like cream with that? :) ) are greatly
appreciated.

-Seth

--- End Message ---


pgpeQ4svFnSXW.pgp
Description: PGP signature

Re: Re: More modem problems with kernel 2.4.18

[Seth Carbon]

On Tue, 2002-06-18 at 03:13, Paul Johnson wrote:
> Your internal modem, if roasted and ground sufficiently fine, will
make
> a surprisingly strong espresso.  Go get an external modem.
> 
> http://www.linuxmafia.com/~rick/faq/#internalmodem

Even if I'm destined for a good string cup, I'd still like to be able to
figure out what's going on :)

Some thoughts before I go the external road:

1) The modem has worked fine with every kernel I've put in since I
installed potato.  Now both potato (with bunk's upgrades) and woody
fail.

2) /proc/* information and setserial information are at odds with each
other.  I mean--jeez--the irq info is missing altogether...

3) The system refuses to even acknowledge that there may be a modem
there in the first place, making it hard to diagnose once running.

All of this seems to indicate to me that there may be some kernel
bug--but I have no idea where to start if it is. This modem is
definitely not a win/linmodem.  I have also spend some time playing with
the jumpers trying to give the kernel (if it even is a kernel problem) a
friendly reminder of what the proper information is--but to no avail.

Any further thoughts (would I like cream with that? :) ) are greatly
appreciated.

-Seth



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: More modem problems with kernel 2.4.18

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Jun 17, 2002 at 07:22:59PM -0700, Seth Carbon wrote:
> Summary: I cannot get my USR modem to work with the 2.4.18 kernel.

> modem: US Robotic internal ISA 56k Data (on-card DSP) (prod#: 005687-03)

> Any help or pointers would be greatly appreciated :)

Your internal modem, if roasted and ground sufficiently fine, will make
a surprisingly strong espresso.  Go get an external modem.

http://www.linuxmafia.com/~rick/faq/#internalmodem

- -- 
Baloo


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9DwewNtWkM9Ny9xURApvTAKCK7J0HjkWUQVWGBzhBRrDlFlCBDACeORIw
KT11byPsRo32Jd0K0S1f3x8=
=AvDJ
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

More modem problems with kernel 2.4.18

[Seth Carbon]

Summary: I cannot get my USR modem to work with the 2.4.18 kernel.

I have recently started trying to upgrade my Debian Potato sytem to the
newer 2.4.18 kernel.  Everything is fine except that my USR PnP modem no
longer works.  When I check, it is listed in /proc/isapnp (although with
the incorrect irq--5 instead of 3), and seems to have the correct entry
in /proc/ioports, but has no entry in /proc/interrupts.  Also, dmesg
reports the irq for the modem incorrectly as 5 instead of 3.

The same things happened when I installed Woody on a different disk.

os: Both Debian Potato/Stable and Woody/testing with kernel 2.4.18
modem: US Robotic internal ISA 56k Data (on-card DSP) (prod#: 005687-03)
pppd version 2.4.1
setserial version 2.17, 27-Jan-2000

I have tried searching for help on the net in comp.os.linux.*, the
Debian mail archives, various kernel sites, and the net in general, but
have not yet found any promising leads.

Any help or pointers would be greatly appreciated :)
I will be happy to provide any further necessary information.

Thanks,

-Seth





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Cable Modem Problems

[Luke Reeves]

Thanks, the article was good.  Turns out the problem was a faulty 
network card - I know, I should have checked this first.  But it 
literally gave out while I was installing Debian, so I kinda ignored 
that possibility.


Luke

Josh McKinney wrote:


On approximately Thu, Oct 11, 2001 at 12:50:25PM -0400, Luke Reeves wrote:

Hello everyone.  I've recently erased my RedHat Linux machine and 
installed Debian Woody.  I used [EMAIL PROTECTED] (in Canada) with RedHat just 
fine, using either Pump or DHCPCD - specifying the hostname and 
interface - with no problems whatever.  Now when I try to use the 
dynamic IP configuration programs with Debian, nothing works.  Pump, 
dh-client and dhcpcd all give operation failed errors.  I even 
recompiled the 2.4.10-ac11 kernel (which is the version I used on 
RedHat) and it still doesn't work.  Does anyone have any ideas?  Thanks!


Luke Reeves
[EMAIL PROTECTED]



There was an article about this exact same thing on linux.com that may help
you. 


http://www.linux.com/learn/newsitem.phtml?sid=1&aid=12537

Josh




--
Luke Reeves, Director of Development
Oceanlake Commerce Inc.
http://www.oceanlake.com/
[EMAIL PROTECTED]

Re: Cable Modem Problems

[Kyle Girard]

Nope i'm using the stock debian kernel

On Thu, 2001-10-11 at 14:37, Luke Reeves wrote:
> Strange.  I'll try that when I get home today.  Did you change any of 
> the kernel parameters in the /proc filesystem?  I remember reading a 
> blurb about that somewhere affecting DHCP systems.  Thanks!
> 
>   Luke
> 
> Kyle Girard wrote:
> 
> > I have rogers and I'm working fine although my setup is a little
> > different from yours (2.2.17 kernel, unstable).  I used dhcp-client and
> > here's my dhclient.conf file
> > 
> > send host-name "hostname";
> > 
> > and here's my /etc/network/interfaces
> > 
> > iface lo inet loopback
> > iface eth0 inet dhcp
> > 
> > And everything works great.
> > 
> > 
> > On Thu, 2001-10-11 at 12:50, Luke Reeves wrote:
> > 
> >>Hello everyone.  I've recently erased my RedHat Linux machine and 
> >>installed Debian Woody.  I used [EMAIL PROTECTED] (in Canada) with RedHat 
> >>just 
> >>fine, using either Pump or DHCPCD - specifying the hostname and 
> >>interface - with no problems whatever.  Now when I try to use the 
> >>dynamic IP configuration programs with Debian, nothing works.  Pump, 
> >>dh-client and dhcpcd all give operation failed errors.  I even 
> >>recompiled the 2.4.10-ac11 kernel (which is the version I used on 
> >>RedHat) and it still doesn't work.  Does anyone have any ideas?  Thanks!
> >>
> >>Luke Reeves
> >>[EMAIL PROTECTED]
> >>
> >>
> >>-- 
> >>To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> >>with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> >>
> >>
> > 
> > 
> > 
> 
> 

Re: Cable Modem Problems

[Josh McKinney]

On approximately Thu, Oct 11, 2001 at 12:50:25PM -0400, Luke Reeves wrote:
> Hello everyone.  I've recently erased my RedHat Linux machine and 
> installed Debian Woody.  I used [EMAIL PROTECTED] (in Canada) with RedHat 
> just 
> fine, using either Pump or DHCPCD - specifying the hostname and 
> interface - with no problems whatever.  Now when I try to use the 
> dynamic IP configuration programs with Debian, nothing works.  Pump, 
> dh-client and dhcpcd all give operation failed errors.  I even 
> recompiled the 2.4.10-ac11 kernel (which is the version I used on 
> RedHat) and it still doesn't work.  Does anyone have any ideas?  Thanks!
> 
>   Luke Reeves
>   [EMAIL PROTECTED]
> 
There was an article about this exact same thing on linux.com that may help
you. 

http://www.linux.com/learn/newsitem.phtml?sid=1&aid=12537

Josh
-- 
Linux, the choice| Traveling through hyperspace isn't like
of a GNU generation   -o)| dusting crops, boy.   -- Han Solo 
Kernel 2.4.10-ac11 /\| 
on a i586 _\_v   | 
 | 

Re: Cable Modem Problems

[Luke Reeves]

Strange.  I'll try that when I get home today.  Did you change any of 
the kernel parameters in the /proc filesystem?  I remember reading a 
blurb about that somewhere affecting DHCP systems.  Thanks!


Luke

Kyle Girard wrote:


I have rogers and I'm working fine although my setup is a little
different from yours (2.2.17 kernel, unstable).  I used dhcp-client and
here's my dhclient.conf file

send host-name "hostname";

and here's my /etc/network/interfaces

iface lo inet loopback
iface eth0 inet dhcp

And everything works great.


On Thu, 2001-10-11 at 12:50, Luke Reeves wrote:

Hello everyone.  I've recently erased my RedHat Linux machine and 
installed Debian Woody.  I used [EMAIL PROTECTED] (in Canada) with RedHat just 
fine, using either Pump or DHCPCD - specifying the hostname and 
interface - with no problems whatever.  Now when I try to use the 
dynamic IP configuration programs with Debian, nothing works.  Pump, 
dh-client and dhcpcd all give operation failed errors.  I even 
recompiled the 2.4.10-ac11 kernel (which is the version I used on 
RedHat) and it still doesn't work.  Does anyone have any ideas?  Thanks!


Luke Reeves
[EMAIL PROTECTED]


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Cable Modem Problems

[Kyle Girard]

I have rogers and I'm working fine although my setup is a little
different from yours (2.2.17 kernel, unstable).  I used dhcp-client and
here's my dhclient.conf file

send host-name "hostname";

and here's my /etc/network/interfaces

iface lo inet loopback
iface eth0 inet dhcp

And everything works great.


On Thu, 2001-10-11 at 12:50, Luke Reeves wrote:
> Hello everyone.  I've recently erased my RedHat Linux machine and 
> installed Debian Woody.  I used [EMAIL PROTECTED] (in Canada) with RedHat 
> just 
> fine, using either Pump or DHCPCD - specifying the hostname and 
> interface - with no problems whatever.  Now when I try to use the 
> dynamic IP configuration programs with Debian, nothing works.  Pump, 
> dh-client and dhcpcd all give operation failed errors.  I even 
> recompiled the 2.4.10-ac11 kernel (which is the version I used on 
> RedHat) and it still doesn't work.  Does anyone have any ideas?  Thanks!
> 
>   Luke Reeves
>   [EMAIL PROTECTED]
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 

Cable Modem Problems

[Luke Reeves]

Hello everyone.  I've recently erased my RedHat Linux machine and 
installed Debian Woody.  I used [EMAIL PROTECTED] (in Canada) with RedHat just 
fine, using either Pump or DHCPCD - specifying the hostname and 
interface - with no problems whatever.  Now when I try to use the 
dynamic IP configuration programs with Debian, nothing works.  Pump, 
dh-client and dhcpcd all give operation failed errors.  I even 
recompiled the 2.4.10-ac11 kernel (which is the version I used on 
RedHat) and it still doesn't work.  Does anyone have any ideas?  Thanks!


Luke Reeves
[EMAIL PROTECTED]

Re: *Working* Modem problems

[Robert Waldner]

>> It's also interesting to note that the modem works fine under W2k.  Oh, and
>> I thought that that it could have been pppd not correctly telling my modem
>> to disconnect, so I tried echoing "ATH0" to the device after the connection
>> was brought down, which didn't help...
>> 
>> Any ideas?

>sounds more like the modem is not getting reset properly.  The modem book (or
>online docs on cdrom) should have a AT string that will reset the modem, try
>adding that just before the dial command.  When I worked at an ISP we had to d
>o
>this sometimes.

Yeah, some modems need that. Try "ATZ" or "AT&F" ("AT&F0" and "AT&F1", 
 too). The first should issue a reset, the AT&F´s a reset back to 
 factory-defaults. Works with most modems. Of course, YMMV.

cheers,
&rw
-- 
-- Better to teach a man to fish than to give him a fish.  And if
-- he can't be bothered to learn to fish and starves to death,
-- that's a good enough outcome for me.   - Steve VanDevender





pgptySwYj3xio.pgp
Description: PGP signature

RE: *Working* Modem problems

[Sean 'Shaleh' Perry]

> 
> It's also interesting to note that the modem works fine under W2k.  Oh, and
> I thought that that it could have been pppd not correctly telling my modem
> to disconnect, so I tried echoing "ATH0" to the device after the connection
> was brought down, which didn't help...
> 
> Any ideas?
> 

sounds more like the modem is not getting reset properly.  The modem book (or
online docs on cdrom) should have a AT string that will reset the modem, try
adding that just before the dial command.  When I worked at an ISP we had to do
this sometimes.

*Working* Modem problems

[Matthew Kopishke]

This isn't really a debian problem, but a general Linux problem.  Anyway, I
have an internal 56k ISA *jumpered* (not the most common things these days)
modem.  For simplicity, I disabled the first serial port on my mother board,
and set the modem to live it's space (I'm just use to pointing to
/dev/ttyS0, I always used external modems up until I bought this modem).
Well it works fine on the first dial (after a reboot or cold start), but
after I disconnect I can't reconnect unless I start a new connection, stop
it, then start it again.  When I refer to connecting I'm talking about ppp.
I'm running potato with the 2.4 package updates the 2.4.5 kernel, and the
basic pon/poff uitilites.

The reason this is a real problem is I just set up masqdial, and of course
it's hard to explain to my family members whey they have to start the
connection, stop it, then start it again to get on the internet.

It's also interesting to note that the modem works fine under W2k.  Oh, and
I thought that that it could have been pppd not correctly telling my modem
to disconnect, so I tried echoing "ATH0" to the device after the connection
was brought down, which didn't help...

Any ideas?

Matthew Kopishke
[EMAIL PROTECTED]

Re: Modem problems after kernel upgrade (long, w/ Radeon VE sidenot

[J.A.Serralheiro]

uar=unknown means that you dont have any hardware on those devices ttyS2
and ttyS3. You can put you device ttySx on any io address you want. That
is , you only need to have as many devices as serial ports.
your problem is that very likely your modem doesnt get identified.
try documentation for the serial.o module and see if something is wrong.
maybe you need to give to serial.o some detail in /etc/modules.conf so
that on start up it identifies correctly your modem.
chek /proc/pci and see if your modem is detected as some hardware.

Re: Modem problems after kernel upgrade (long, w/ Radeon VE sidenote)

[Joost Kooij]

On Mon, Jul 23, 2001 at 09:31:42PM -0500, Jeremy wrote:
> output of dmesg:
> 
> Serial driver version 5.05a (2001-03-20) with MANY_PORTS SHARE_IRQ SERIAL_PCI 
> ISAPNP enabled
> ttyS00 at 0x03f8 (irq = 4) is a 16550A
> ttyS01 at 0x02f8 (irq = 3) is a 16550A
> Redundant entry in serial pci_table.  Please send the output of
> lspci -vv, this message (4793,4104,4793,215)
> and the manufacturer and name of serial board or modem board
> to [EMAIL PROTECTED]
  ^
  you should perhaps do this
  
> ttyS04 at port 0xac00 (irq = 5) is a 16550A
> 
> output of setserial /dev/ttyS2 uart 16550A port 0xac00 irq 5:
> Cannot set serial info: Address already in use

Edit /etc/init.d/setserial to not autodetect ttyS2 and ttyS3
and setup ttyS2 with the above parameters specified.

> output of setserial /dev/ttyS04 uart 16550A port 0xac00 irq 5:
> /dev/ttyS04: No such file or directory

Maybe it works after you "MAKEDEV /dev/ttyS4", but it would be
more interesting to get the pci_table problem solved.

> > > with anyone and if anyone has any suggestions.

Please sanitize your emails when participating in a thread on
a mailing list.  There's no need to keep resending text that
has already been received before by everyone on the list.

Cheers,


Joost

Re: Modem problems after kernel upgrade (long, w/ Radeon VE sidenote)

[Jeremy]

Dang it all... I went and forgot my Radeon sidenote.  Anyway, I was wondering 
if anyone has gotten the ATI Radeon VE video card (AGP) working with X.  
(preferably 4.0.3).  Anytime I try to use it, I get broken server connection 
messages.  Any suggestions?

TIA,
Jeremy

Re: Modem problems after kernel upgrade (long, w/ Radeon VE sidenote)

[Jeremy]

"D. Hoyem" <[EMAIL PROTECTED]> writes:

> Did you also get the 2.4.? ppp? That is required when
> you upgrade to a 2.4.* kernel. You can also try
> setserial -g /dev/ttyS* and see what is listed as the
> modem.  It should be listed as UART 16550A if memory
> serves me right.
> Don

Okay...  here's the nitty gritty...  (a LOT of it) I do have ppp 2.4.1-4, so
that's good.  I took the output from a lot of things and have them listed
below.  There's one thing that seems to strike me, and that is when I had
kernel 2.2.18pre21, I had more serial ports in /dev/ than ttyS3.  Now I just
have the 4 basic devices, 0-3.  The output of using setserial on a
nonexistant device is also below.  I'm wondering, do I need to make a new
device in /dev? (ie, ttyS4?)  If so, how do I go about doing it?  Also,
another thing that strikes me as strange is that even though it lists devices
00, 01, and 04 (in the dmesg output below), all of those also come up as
invalid if I try to adjust them via setserial.

So if someone can make sense of all this gibberish and help me get this dang
modem recognized by pppconfig or wvdial or SOMETHING, then I would greatly
appreciate it.  If there is any further output from anything that is needed
to help out, please don't hesitate to let me know.

Jeremy


output of setserial -g /dev/ttyS*:

/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
/dev/ttyS1, UART: 16550A, Port: 0x02f8, IRQ: 3
/dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4
/dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3

output of cat /proc/ioports:

02f8-02ff : serial(set)
03f8-03ff : serial(set)
ac00-ac07 : US Robotics/3Com 56K FaxModem Model 5610
  ac00-ac07 : serial(auto)

output of cat /proc/pci:

Bus  0, device  16, function  0:
  Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev 1).
IRQ 5.
I/O at 0xac00 [0xac07].

output of lspci -v:

00:10.0 Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev 01) 
(prog-if 02 [16550])
 Subsystem: US Robotics/3Com: Unknown device 00d7
 Flags: medium devsel, IRQ 5
 I/O ports at ac00 [size=8]
 Capabilities: [dc] Power Management version 2

output of dmesg:

Serial driver version 5.05a (2001-03-20) with MANY_PORTS SHARE_IRQ SERIAL_PCI 
ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Redundant entry in serial pci_table.  Please send the output of
lspci -vv, this message (4793,4104,4793,215)
and the manufacturer and name of serial board or modem board
to [EMAIL PROTECTED]
ttyS04 at port 0xac00 (irq = 5) is a 16550A

output of setserial /dev/ttyS2 uart 16550A port 0xac00 irq 5:
Cannot set serial info: Address already in use

output of setserial /dev/ttyS04 uart 16550A port 0xac00 irq 5:
/dev/ttyS04: No such file or directory

=

> --- Jeremy Whetzel <[EMAIL PROTECTED]> wrote:
> > I have a USR 5610A pci modem that worked fine with
> > the
> > 2.2.18 series kernel if I set the parameters in my
> > /etc/serial.conf file (it was /dev/ttyS2), but last
> > night I got the 2.4.6 source from Sid and built my
> > own
> > kernel, and now my modem doesn't work.  I have ISA
> > PNP
> > enabled (although it says it doesn't say it finds
> > anything on boot).  I've also noticed that it says
> > it
> > finds a serial board and right after it lists
> > /dev/ttyS04, so I'm assuming that's the serial port
> > I'm supposed to access to use it, but if I point
> > pppconfig or wvdial to it, it tells me it's invalid.
> > 
> > I'm not at my box to get the exact error at the
> > moment, but I was wondering if this strikes anything
> > with anyone and if anyone has any suggestions.
> > 
> > Thanks In Advance,
> > Jeremy
> > 
> > __
> > Do You Yahoo!?
> > Make international calls for as low as $.04/minute
> > with Yahoo! Messenger
> > http://phonecard.yahoo.com/
> > 
> > 
> > -- 
> > To UNSUBSCRIBE, email to
> > [EMAIL PROTECTED] 
> > with a subject of "unsubscribe". Trouble? Contact
> > [EMAIL PROTECTED]
> > 
> 
> 
> __
> Do You Yahoo!?
> Make international calls for as low as $.04/minute with Yahoo! Messenger
> http://phonecard.yahoo.com/
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Modem problems after kernel upgrade

[J.A.Serralheiro]

well
probably you have 3 serial ports. two on board and one for your modem.
one way to find wich ports are detect is listing /proc/ioports

3f8 states as ttyS0
2f8   ttyS1
3e8   ttyS2
238   ttyS3
that is, if you stick with the normal settings in /etc/serial.conf

You can assign any I/O port to any ttySx. 
Because you board is pci, isa pnp will not interfere.

Chek /proc/pci and see what io address your modem is using.  If its pci it
will be listed. if not listed, its not detected.
then,  edit /etc/serial.conf accordingly. Even if on start up the module
serial.o assigns your modem to ttyS4, you can override this.
see the setserial man pages for more details

Re: Modem problems after kernel upgrade

[J.A.Serralheiro]

further more, I remember I also had a strange problem

I had to recompile pppd in order to work with 2.4

Re: Modem problems after kernel upgrade

[D. Hoyem]

Did you also get the 2.4.? ppp? That is required when
you upgrade to a 2.4.* kernel. You can also try
setserial -g /dev/ttyS* and see what is listed as the
modem.  It should be listed as UART 16550A if memory
serves me right.
Don
--- Jeremy Whetzel <[EMAIL PROTECTED]> wrote:
> I have a USR 5610A pci modem that worked fine with
> the
> 2.2.18 series kernel if I set the parameters in my
> /etc/serial.conf file (it was /dev/ttyS2), but last
> night I got the 2.4.6 source from Sid and built my
> own
> kernel, and now my modem doesn't work.  I have ISA
> PNP
> enabled (although it says it doesn't say it finds
> anything on boot).  I've also noticed that it says
> it
> finds a serial board and right after it lists
> /dev/ttyS04, so I'm assuming that's the serial port
> I'm supposed to access to use it, but if I point
> pppconfig or wvdial to it, it tells me it's invalid.
> 
> I'm not at my box to get the exact error at the
> moment, but I was wondering if this strikes anything
> with anyone and if anyone has any suggestions.
> 
> Thanks In Advance,
> Jeremy
> 
> __
> Do You Yahoo!?
> Make international calls for as low as $.04/minute
> with Yahoo! Messenger
> http://phonecard.yahoo.com/
> 
> 
> -- 
> To UNSUBSCRIBE, email to
> [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]
> 


__
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/

Modem problems after kernel upgrade

[Jeremy Whetzel]

I have a USR 5610A pci modem that worked fine with the
2.2.18 series kernel if I set the parameters in my
/etc/serial.conf file (it was /dev/ttyS2), but last
night I got the 2.4.6 source from Sid and built my own
kernel, and now my modem doesn't work.  I have ISA PNP
enabled (although it says it doesn't say it finds
anything on boot).  I've also noticed that it says it
finds a serial board and right after it lists
/dev/ttyS04, so I'm assuming that's the serial port
I'm supposed to access to use it, but if I point
pppconfig or wvdial to it, it tells me it's invalid. 
I'm not at my box to get the exact error at the
moment, but I was wondering if this strikes anything
with anyone and if anyone has any suggestions.

Thanks In Advance,
Jeremy

__
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/

Re: USR modem problems

[Mark Garland]

- Original Message -
From: "Mark Garland" <[EMAIL PROTECTED]>
To: "Debian List" 
Sent: Monday, July 09, 2001 7:34 PM
Subject: Re: USR modem problems


> I forwarded this installation instruction for a PCI modem:
>
> 
> IV. To set Linux to configure the modem upon boot-up.
>
> There are several options.  One method is going to the /etc/rc.d/
> directory, and using an editing program such as "jed" edit the
> rc.local file, and insert
> setserial /dev/ttyS3 uart 16550A port 0x6400 irq 11
> as the last line.
> 
>
> I inserted a line like that at the end of /etc/serial.conf (with
appropriate
> ttyS*, port, and irq) and things worked fine.
>

To clarify--a line like that *without* "setserial" at the beginning.  Argh.
Must shut up now.

Mark Garland
Tallahassee, Florida


NetZero Platinum
No Banner Ads and Unlimited Access
Sign Up Today - Only $9.95 per month!
http://www.netzero.net

Re: USR modem problems

[Mark Garland]

I forwarded this installation instruction for a PCI modem:


IV. To set Linux to configure the modem upon boot-up.

There are several options.  One method is going to the /etc/rc.d/
directory, and using an editing program such as "jed" edit the
rc.local file, and insert
setserial /dev/ttyS3 uart 16550A port 0x6400 irq 11
as the last line.


I inserted a line like that at the end of /etc/serial.conf (with appropriate
ttyS*, port, and irq) and things worked fine.

Mark Garland
Tallahassee, Florida


NetZero Platinum
No Banner Ads and Unlimited Access
Sign Up Today - Only $9.95 per month!
http://www.netzero.net

Re: USR modem problems

[Mark Garland]

- Original Message -
From: "Jeremy" <[EMAIL PROTECTED]>
To: "Debian List" 
Sent: Monday, July 09, 2001 12:10 PM
Subject: USR modem problems


> I recently purchased a USR internal 56k PCI modem (model 3CP5610A), but
> I've had no luck getting it working on my woody box.  In the
> instructions in the box, it tells me that to get it working with linux,
> I need kernel 2.3 or above.  "Good time to upgrade!" I thought, and I
> went for the 2.4.6 kernel.  I did a little research on in the
> debian-user archives, and found some suggestions of enabling ISA
> plug-n-play, and also changing some serial settings within the kernel
> config.  After doing these things, I still can't seem to get anything
> to identify my modem.  Under *cough* Winders *cough*, it's on COM port
> 5.  I enabled the "Many Serial Ports" option in the kernel after I
> found this out, but to no avail.  No matter what COM port I try, it
> doesn't seem to find it.  dmesg gives me something about (I'm not at my
> box right now... I'm at work) finding a serial board and right under it
> lists /dev/tty4 with an IRQ.  I thought this was my modem, so I tried
> connecting to it in minicom, but I couldn't get it to show up.  One
> thing I found strange about using minicom, though, was that it said
> "online" in the bottom right corner.  I'd try to tell it to hang up,
> and it would do it for about 1 second, and then it would go back to
> online.  I'm sorry that I don't have exact error messages with me right
> now, but if any of this sounds familiar to anyone and you have
> suggestions, please let me know.  Also, if there's some specific info
> you need, let me know.
>
> TIA,
> Jeremy

Jeremy,

I'm no expert, but got a USR 5610A internal modem working under potato
(kernel 2.2.19pre17) by slightly modifying the instructions posted at
http://www.math.sunysb.edu/~comech/tools/PCImodems.html  (going down at the
end of this month, BTW). Don't know why woody would be different.  I've
attached the relevant part below.  Step IV is different in Debian--I'll get
back to you when I check my Debian installation.

Hope this helps,
  Mark Garland
  Tallahassee, Florida



   ***INSTALLATION OF V90 PCI LUCENT VENUS BASED MODEM***


I. After physically installing the modem, log into your "Root" account.

II. To determine resource settings.

Type the following command: cat /proc/pci
An example of the outcome will look like this;

5.Non-prefetchable 32 bit memory at 0x.

Bus 0, device 17, function 0:
Communication controller: Unknown vendor Unknown device (rev 0).
Vendor id=11c1.  Device id=480.
Medium devsel.   Fast back-to-back capable.  IRQ 11.  Master
Capable.
No bursts.
Min Gnt=252.Max Lat=14
 Non-prefetchable 32 bit memory at 0xe400.
 I/O at 0x6400.
 I/O at 0x6800.
 I/O at 0x6c00.

III. Take note of the IRQ, and FIRST I/O address, then type in this command;

 cd /dev; test -c ttyS3 || ./MAKEDEV ttyS3; chmod 666 /dev/ttyS3
 setserial /dev/ttyS3 uart 16550A port 0x6400 irq 11
 ln -sf /dev/ttyS3 /dev/modem

 You can probably use any other ttySX as well.

NOTE: THE IRQ AND PORT MAY VARY, IT IS DEPENDANT UPON THE RESULTS FROM STEP
II

IV. To set Linux to configure the modem upon boot-up.

There are several options.  One method is going to the /etc/rc.d/
directory, and using an editing program such as "jed" edit the
rc.local file, and insert
setserial /dev/ttyS3 uart 16550A port 0x6400 irq 11
as the last line.
_

*TEST CONDITIONS:

OS: RedHat Linux 5.2 Boxed CD with Linux kernel 2.0.36
BIOS: AWARD
MOTHERBOARD: Shuttle Hot 557 w/i437 VX chipset and latest BIOS update.
CPU: Intel Pentium 166MMX cpu
MEMORY: 32 MB EDO RAM
VIDEO: PCI S3 Virge DX with 2mb memory
STORAGE: 820 Quantum EIDE Hard Drive, ATAPI CD-ROM, 3.5'' floppy
SOUND: Creative Labs Sound Blaster AWE 32 PNP

* As each user with Linux is more than likely to have a unique setup,
the details listed above should comply with other versions of Linux as
well, ie Slackware, Redhat, etc.  But are NOT 100% guaranteed to have
an identical setup method as far as exact commends, etc. are concerned.


Richard Nelson
Actiontec Electronics, INC





NetZero Platinum
No Banner Ads and Unlimited Access
Sign Up Today - Only $9.95 per month!
http://www.netzero.net

USR modem problems

[Jeremy]

I recently purchased a USR internal 56k PCI modem (model 3CP5610A), but
I've had no luck getting it working on my woody box.  In the
instructions in the box, it tells me that to get it working with linux,
I need kernel 2.3 or above.  "Good time to upgrade!" I thought, and I
went for the 2.4.6 kernel.  I did a little research on in the
debian-user archives, and found some suggestions of enabling ISA
plug-n-play, and also changing some serial settings within the kernel
config.  After doing these things, I still can't seem to get anything
to identify my modem.  Under *cough* Winders *cough*, it's on COM port
5.  I enabled the "Many Serial Ports" option in the kernel after I
found this out, but to no avail.  No matter what COM port I try, it
doesn't seem to find it.  dmesg gives me something about (I'm not at my
box right now... I'm at work) finding a serial board and right under it
lists /dev/tty4 with an IRQ.  I thought this was my modem, so I tried
connecting to it in minicom, but I couldn't get it to show up.  One
thing I found strange about using minicom, though, was that it said
"online" in the bottom right corner.  I'd try to tell it to hang up,
and it would do it for about 1 second, and then it would go back to
online.  I'm sorry that I don't have exact error messages with me right
now, but if any of this sounds familiar to anyone and you have
suggestions, please let me know.  Also, if there's some specific info
you need, let me know.

TIA,
Jeremy


__
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/

Re: Cable modem problems (hardware or software?)

[jbardin]

i would just use apt-get install dhcp-client also check out the dhcp
client setup at http://home.cfl.rr.com/aawtrey/ he has laid out a nice
howto.begin:vcard 
n:Bardin;Jon
x-mozilla-html:FALSE
adr:;;
version:2.1
email;internet:[EMAIL PROTECTED]
note:www.gamesig.com -uniting the linux gaming community
x-mozilla-cpt:;0
fn:Jon Bardin
end:vcard

Cable modem problems (hardware or software?)

[Brooks R. Robinson]

Greetings,
I am using road runner for cable modem service.  I am using pump for my
dhcp client ob a potato box (Pentium 233MMX -- 16MB RAM).  The cable modem
I've got is a SURFboard 2100.  My problem is that occasionally that my cable
modem will "lock up" -- The activity LED will light up and stay on, and I
cannot connect to the box from elsewhere (I'm using a www.dyndns.org client
to get the address).
This only seems to happen when I have the potato box going.  Anyone 
have an
idea if this is a pump problem or if it's just a hardware thing that I have
to live with?  Will it get better if I use another DHCP client?  Help!
Help!  Help!

Thanks,

Brooks

Re: Modem problems (was :Can't use USRobotics detect)

[Leonardo Stern]

> > I tried pppconfig too : with "windows configurations" or "non /dev/ttyS1"
> ^^  ^^


> ??

I mean I tried the modem configurations used in windows and all other 3
ports ... (even ttyS0 , used by my mouse). With ttyS0, ttyS2 and ttyS3
pon didn't send anything to modem
> 

> Does the modem respond to minicom?
minicom tries to initialize modem .. no error messages appears
but when I try to dial .. the modem don't respond

Re: Modem problems (was :Can't use USRobotics detect)

[John Hasler]

Leonardo Stern writes:
> I tried pppconfig too : with "windows configurations" or "non /dev/ttyS1"
^^  ^^

??

> with /dev/ttyS1 IRQ X (x = 3,4,5,6,7) the modem don't respond to pon

Does the modem respond to minicom?
-- 
John Hasler
[EMAIL PROTECTED]
Dancing Horse Hill
Elmwood, Wisconsin

Re: Modem problems (was :Can't use USRobotics detect)

[Leonardo Stern]

*** on bottom ***

> > I also did :
> >  pnpdump > test.txt
> >  isapnp test.txt
> > .. found 3 devices (the modem too) .. now what ?
> > (also tried pnpdump then setting a com port with the values from
> > pnpdump)
> 
> If I remember correctly, wvdial has a configure file that tells it
> which ttyS? to use.  Did you configure wvdial?  Also, why not just use
> pppconfig?  It's all around easier to use, and usually gets things
> right.

I tried pppconfig too :
 with "windows configurations" or "non /dev/ttyS1" pon don't send
anything
 with /dev/ttyS1 IRQ X (x = 3,4,5,6,7) the modem don't respond to pon
(but pon send ATZ , or AT&F1 (manual recommended this initstring))

PS : My modem is pnp

Re: Modem problems (was :Can't use USRobotics detect)

[Eric G . Miller]

On Tue, Jul 04, 2000 at 09:22:20PM -0300, Leonardo Stern wrote:
> I also did :
>  pnpdump > test.txt
>  isapnp test.txt
> .. found 3 devices (the modem too) .. now what ?
> (also tried pnpdump then setting a com port with the values from
> pnpdump) 

If I remember correctly, wvdial has a configure file that tells it
which ttyS? to use.  Did you configure wvdial?  Also, why not just use
pppconfig?  It's all around easier to use, and usually gets things
right.


-- 
#! /bin/sh
echo 'Linux Must Die!' | wall
dd if=/dev/zero of=/vmlinuz bs=1 \
 count=`du -Lb /vmlinuz | awk '{ /^([0-9])+/ ; print $1 }'`
shutdown -r now

Modem problems (was :Can't use USRobotics detect)

[Leonardo Stern]

I also did :
 pnpdump > test.txt
 isapnp test.txt
.. found 3 devices (the modem too) .. now what ?
(also tried pnpdump then setting a com port with the values from
pnpdump) 

> Are you sure this isn't a winmodem?
I don't think .. its supposed to run on DOS 6.0
> 
> On Tue, 04 Jul 2000, Leonardo Stern wrote:
> > Wvdialconf can't detect my modem [usrobotics sporster 33.6 intenal, pnp]
> >
> > on win98 he appears on
> > Port : COM3
> > IRQ : 4
> > Adress : 3E8
> >
> > so I used the following command :
> > setserial /dev/ttyS2 port 0x03E8 irq 4 uart 16550A
> > ... rerun wvdialconfig .. no results
> >
> >
> > --
> > Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
> --
> Christopher Thompson  http://hypocrite.org/
> "Act only on that maxim whereby thou canst at the same
> time will that it should become a universal law."

Re: LLP Modem problems

[Graeme Mathieson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

[EMAIL PROTECTED] writes:

> Has anyone experienced the problem where uucp system produces Low Level
> Protocol (LLP) errors?

I've never had any problems with UUCP.  I must admit to being fairly new
to it though.  What protocol are you using?  Is it UUCP-over-TCP or
dialup?  Post a copy of you're UUCP sys file[1].  I've been fiddling with
the parameters on mine to try and improve performance a little.

[1] Feel free to blank out any bits that contain too much information,
like usernames, passwords, telephone numbers. :)

- -- 
Graeme.
[EMAIL PROTECTED]

"Life's not fair," I reply. "But the root password helps." - BOFH
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)

iD8DBQE5IAmCPjGH3lNt65URAte6AKCErgC/rjy/tDpepVPRJBD+FL5OWgCfTStg
nS+DJZJBqVHM+VmiWQIp/A8=
=jZX4
-END PGP SIGNATURE-

LLP Modem problems

[zdrysdal]

Hi all

Has anyone experienced the problem where uucp system produces Low Level
Protocol (LLP) errors?

ie.  our system uploads hl7files to a mailbox via uucp... when i dial up
the mailbox and download the hl7 files (emulating a doctors practice) i get
a random amount of LLP/CRC errors.  But most of the files are ok.

I have tried changing modems and playing with the modem settings etc. but
to no avail.  So now I am asking around...

BTW, this is an AIX box... sorry if this offends anyone.

Zane

Re: Modem Problems

[Isabelle Poueriet]

Your serial port that your modem uses is probable using an IRQ greater
than 4.  If so, Linux won't detect the serial port.  You have to tell
Linux that the serial port is using IRQ n.  Check in windows first:
find out which COM your modem is in. Then check which IRQ this COM is
usin:
control pannel ==> system ==> device manager ==> computer 

If your modem is in COM3 (ttyS2 in Linux) and COM3 is using IRQ 5 then you
have to issue the command 
setserial /dev/ttyS2 irq 5. And boom! your modem will be found by wvdial.


\_\_\_\_\_\_\_\_\_\_\_\_
\_ Isabelle Poueriet   \_ 
\_ [EMAIL PROTECTED]  \_
\_ http://www.bway.net \_
\_\_\_\_\_\_\_\_\_\_\_\_
Q. How many Microsoft Engineers does it take to screw in a light bulb?
A. None.  They declare "darkness", the standard.

On Tue, 10 Aug 1999, Joop Stakenborg wrote:

> On Tue, Aug 10, 1999 at 11:13:46AM +0100, Thys van der Merwe wrote:
> > Hi
> > 
> > I hope someone can help me with this.
> > 
> > I loaded the Debian base on my laptop, hoping to get the rest of the
> > packages off the net using dselect.
> > 
> > At first I thought that I had a problem using pppconfig, so I got Minicom
> > and wvdial and found that after issuing ATZ to the modem that the modem
> > wasn't responding.  It is an external modem on the serial port.  The laptop
> > has a trackball and no other mouse.  The modem was on and when issuing ATZ
> > did flicker a few lights, but other than that did nothing.  In fact,
> > wvdialconf doesn't even detect the modem.
> > 
> > I then thought the modem was broken and took it off, attached it to a win
> > machine and could connect to the net within minutes.
> > 
> > If anyone could help me with this problem, I would be very greatful.
> >
> 
> Is your serial port detected at boot-time?
> Did you configure the serial port with setserial?
> You need to go through /etc/serial.conf to see if the settings
> are there
> 
> > Thanks
> > 
> > Thys
> 
> Joop
> -- 
> 
>  Joop Stakenborg PA4TU, ex-PA3ABA 
>   <[EMAIL PROTECTED]>
>  Linux Amateur Radio Software Database
> http://radio.linux.org.au
> 
> 
> -- 
> Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
> 

Re: Modem Problems

[Joop Stakenborg]

On Tue, Aug 10, 1999 at 11:13:46AM +0100, Thys van der Merwe wrote:
> Hi
> 
> I hope someone can help me with this.
> 
> I loaded the Debian base on my laptop, hoping to get the rest of the
> packages off the net using dselect.
> 
> At first I thought that I had a problem using pppconfig, so I got Minicom
> and wvdial and found that after issuing ATZ to the modem that the modem
> wasn't responding.  It is an external modem on the serial port.  The laptop
> has a trackball and no other mouse.  The modem was on and when issuing ATZ
> did flicker a few lights, but other than that did nothing.  In fact,
> wvdialconf doesn't even detect the modem.
> 
> I then thought the modem was broken and took it off, attached it to a win
> machine and could connect to the net within minutes.
> 
> If anyone could help me with this problem, I would be very greatful.
>

Is your serial port detected at boot-time?
Did you configure the serial port with setserial?
You need to go through /etc/serial.conf to see if the settings
are there

> Thanks
> 
> Thys

Joop
-- 

 Joop Stakenborg PA4TU, ex-PA3ABA 
  <[EMAIL PROTECTED]>
 Linux Amateur Radio Software Database
http://radio.linux.org.au

Modem Problems

[Thys van der Merwe]

Hi

I hope someone can help me with this.

I loaded the Debian base on my laptop, hoping to get the rest of the
packages off the net using dselect.

At first I thought that I had a problem using pppconfig, so I got Minicom
and wvdial and found that after issuing ATZ to the modem that the modem
wasn't responding.  It is an external modem on the serial port.  The laptop
has a trackball and no other mouse.  The modem was on and when issuing ATZ
did flicker a few lights, but other than that did nothing.  In fact,
wvdialconf doesn't even detect the modem.

I then thought the modem was broken and took it off, attached it to a win
machine and could connect to the net within minutes.

If anyone could help me with this problem, I would be very greatful.

Thanks

Thys

Re: SupraExpress Modem problems

[Brad]

On Wed, 21 Jul 1999, David Karlin wrote:

> > > > Out of curiousity, did you properly set up the modem with isapnptools, 
> > > > and
> > > > then use setserial to set the irq, port, and everything?
> > > 
> > > Nope.  I disabled PNP and set everything with the jumpers as described
> > > in appendix A of the manual.  This seems to have worked fine.  Is there
> > > an advantange to using isapnptools over disabling PNP?
> > 
> > Probably not. i was just curious, since in part of your previous post
> > (that you cut) you had indicated that it didn't work until you disabled
> > PnP. i was wondering if you had set things up correctly and it _still_
> > didn't work, or if you just took the easy way like i did ;)
>
> I'm not sure that isapnptools is a more "proper" way of setting up a
> PNP card than disabling PNP and setting options with jumpers.

i didn't say it was more "proper". What's wrong with the easy way when it
works just as well or better than the hard? ;)
 
> According to another poster, disabling PNP is preferred.

i'd have to agree, just because ISA PnP doesn't work too well a lot of the
time and it's difficult to configure. i've seen a sig somewhere to the
effect that the problem with Plug-and-Play is that it only works 50% of
the time--specifically, 'Plug' almost always succeeds.

Re: SupraExpress Modem problems

[Ray]

On Wed, Jul 21, 1999 at 10:07:45AM -0500, John Hasler wrote:
> David Karlin writes:
> > Is there an advantange to using isapnptools over disabling PNP?
> 
> Quite the contrary.  PNP is best avoided even in Windows.

The problem is that Windows insists on re-detecting everything every time
you re-boot (that is, all too often).  In Linux everything stays put until
you tell the system otherwise.

-- 
Ray

Re: SupraExpress Modem problems

[Ray]

On Wed, Jul 21, 1999 at 02:11:52AM -0600, David Karlin wrote:
> Is there an advantange to using isapnptools over disabling PNP?

1.  It's easier to change your settings later on.  For example, lets say you
used IRQ 7 for your modem because your printer doesn't need it's IRQ anyway
but later you decide to add a Zip drive.  With ISA-PnP you probably won't
even have to re-boot.

2.  ISA-PnP gives you feedback if you try to assign a resource that is
already in use.  With jumpers, chances are your only clue will be the fact
that the device doesn't work.

3.  Jumper settings are often poorly documented and easy to screw up.

-- 
Ray

Re: SupraExpress Modem problems

[David Karlin]

> > > Out of curiousity, did you properly set up the modem with isapnptools, and
> > > then use setserial to set the irq, port, and everything?
> > 
> > Nope.  I disabled PNP and set everything with the jumpers as described
> > in appendix A of the manual.  This seems to have worked fine.  Is there
> > an advantange to using isapnptools over disabling PNP?
> 
> Probably not. i was just curious, since in part of your previous post
> (that you cut) you had indicated that it didn't work until you disabled
> PnP. i was wondering if you had set things up correctly and it _still_
> didn't work, or if you just took the easy way like i did ;)
I'm not sure that isapnptools is a more "proper" way of setting up a
PNP card than disabling PNP and setting options with jumpers.

According to another poster, disabling PNP is preferred.

--D

P.S. I assume the original poster has solved his modem problem as we
haven't heard back from him.

-- 
===
David Karlin
mailto:[EMAIL PROTECTED]
http://funk48.home.travelin.com
Powered by Debian GNU/Linux 2.1
===

Re: SupraExpress Modem problems

[Brad]

On Wed, 21 Jul 1999, David Karlin wrote:

> > > I disabled the pnp and set the irq and com port with the jumpers.
> > 
> > Out of curiousity, did you properly set up the modem with isapnptools, and
> > then use setserial to set the irq, port, and everything?
> 
> Nope.  I disabled PNP and set everything with the jumpers as described
> in appendix A of the manual.  This seems to have worked fine.  Is there
> an advantange to using isapnptools over disabling PNP?

Probably not. i was just curious, since in part of your previous post
(that you cut) you had indicated that it didn't work until you disabled
PnP. i was wondering if you had set things up correctly and it _still_
didn't work, or if you just took the easy way like i did ;)

Re: SupraExpress Modem problems

[John Hasler]

David Karlin writes:
> Is there an advantange to using isapnptools over disabling PNP?

Quite the contrary.  PNP is best avoided even in Windows.
-- 
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI

Re: SupraExpress Modem problems

[David Karlin]

> > I disabled the pnp and set the irq and com port with the jumpers.
> 
> Out of curiousity, did you properly set up the modem with isapnptools, and
> then use setserial to set the irq, port, and everything?

Nope.  I disabled PNP and set everything with the jumpers as described
in appendix A of the manual.  This seems to have worked fine.  Is there
an advantange to using isapnptools over disabling PNP?

-- 
===
David Karlin
mailto:[EMAIL PROTECTED]
http://funk48.home.travelin.com
Powered by Debian GNU/Linux 2.1
===

RE: SupraExpress Modem problems

[Brad]

On Tue, 20 Jul 1999, David Karlin wrote:

> As I said in an earlier post, I installed one of these modems in a
> slink box last evening.  I think I remember a similar plog entry before
> I disabled the pnp and set the irq and com port with the jumpers.

Out of curiousity, did you properly set up the modem with isapnptools, and
then use setserial to set the irq, port, and everything?

> What seems to have been happening here was the software would send the
> initialization string (I did not change the default) but it never got
> the "OK" or whatever it was waiting for.  Once the hardware and software
> were configured properly, there was no problem at all.

i would be inclined to agree. minicom is a good tool for this problem (and
it can be fun to make your modem jump through hoops ;)

i discovered that mine (a 3Com) will return a small bit of help with AT$,
ATD$, or ATS$. And i was able to fine-tune my init string so it didn't
dial so loudly and would dial faster. And i found out which line in
ppp.log will give my connection speed.

> My modem is a Diamond Supra Express 56K V.90 (ISA), and I think it is
> the same as the original poster's.

IIRC the original poster's was an Sp, not a V.90, but in this case that
may not make much difference...

RE: SupraExpress Modem problems

[David Karlin]

> To: Julian Gilbey
> Cc: debian-user@lists.debian.org
> Subject: Re: SupraExpress Modem problems
>
>
> Julian writes:
> > - the /var/log/ppp.log file showed that the intial connection had
> >   been attempted, and that after precisely 45 seconds, an alarm
> >   happened and the connection attempt failed.  Nothing happened
> >   between the "expect OK" and the alarm lines in the log.

> John writes:
> Sounds like the modem did not respond to the ATZ string which is the first
> thing chat sends.  This could be because the modem is not on that port or
> because the modem is configured in an unusual way.  Try connecting to the
> modem with minicom.
> --
> John HaslerThis posting is in the public domain.
> [EMAIL PROTECTED]Do with it what you will.
> Dancing Horse Hill Make money from it if you can; I don't mind.
> Elmwood, Wisconsin Do not send email advertisements to
> this address.

Hi,
As I said in an earlier post, I installed one of these modems in a
slink box last evening.  I think I remember a similar plog entry before
I disabled the pnp and set the irq and com port with the jumpers.

What seems to have been happening here was the software would send the
initialization string (I did not change the default) but it never got
the "OK" or whatever it was waiting for.  Once the hardware and software
were configured properly, there was no problem at all.

My modem is a Diamond Supra Express 56K V.90 (ISA), and I think it is
the same as the original poster's.

--David

Re: SupraExpress Modem problems

[Pollywog]

This is the init string I use for my SupraExpress external modem

from /etc/diald/connect:

MODEM_INIT="AT&F2&C1&D2&K3M0"


Some Supra modems use &F2 instead of &F

--
Andrew

Re: SupraExpress Modem problems

[John Hasler]

Julian writes:
> - the /var/log/ppp.log file showed that the intial connection had
>   been attempted, and that after precisely 45 seconds, an alarm
>   happened and the connection attempt failed.  Nothing happened
>   between the "expect OK" and the alarm lines in the log.

Sounds like the modem did not respond to the ATZ string which is the first
thing chat sends.  This could be because the modem is not on that port or
because the modem is configured in an unusual way.  Try connecting to the
modem with minicom.
-- 
John HaslerThis posting is in the public domain.
[EMAIL PROTECTED]Do with it what you will.
Dancing Horse Hill Make money from it if you can; I don't mind.
Elmwood, Wisconsin Do not send email advertisements to this address.

Re: SupraExpress Modem problems

[David Karlin]

Julian,
I just installed a Diamond Supra Express in a slink box this
evening.

The first thing I did was disable PNP and set the com port
and irq via the jumpers (see Appendix A of the Supra Express
"Getting Started Manual").

I was lucky that I knew the com port and irq settings of the
old modem; com2 (/dev/ttyS1) and irq3.  Then it was out with
the old and in with the new.  Pon worked the same as ever.

HTH,

--David

On Tue, Jul 20, 1999 at 02:03:51AM +0100, Julian Gilbey wrote:
> [Please Cc: me in replies.]
> 
> I have just tried setting up a Debian system for someone, and have
> been unable to get his modem to work.  The details are:
> 
>  - fresh slink (Debian 2.1) installation from the official CDs on a
>Pentium.
>  - Windows reports the modem to be a SupraExpress 56i Sp Intl
>  - I configured the PPP details using pppconfig with no special
>options or anything similar
>  - the /var/log/ppp.log file showed that the intial connection had
>been attempted, and that after precisely 45 seconds, an alarm
>happened and the connection attempt failed.  Nothing happened
>between the "expect OK" and the alarm lines in the log.
> 
> Does anyone have any idea what to do or how to go about fixing this
> problem?
> 
> Thanks in advance,
> 
>Julian

-- 
===
David Karlin
mailto:[EMAIL PROTECTED]
http://funk48.home.travelin.com
Powered by Debian GNU/Linux 2.1
===

RE: SupraExpress Modem problems

[Pollywog]

On 20-Jul-99 Julian Gilbey wrote:
> [Please Cc: me in replies.]
> 
> I have just tried setting up a Debian system for someone, and have
> been unable to get his modem to work.  The details are:
> 
>  - fresh slink (Debian 2.1) installation from the official CDs on a
>Pentium.
>  - Windows reports the modem to be a SupraExpress 56i Sp Intl
>  - I configured the PPP details using pppconfig with no special
>options or anything similar
>  - the /var/log/ppp.log file showed that the intial connection had
>been attempted, and that after precisely 45 seconds, an alarm
>happened and the connection attempt failed.  Nothing happened
>between the "expect OK" and the alarm lines in the log.
> 
> Does anyone have any idea what to do or how to go about fixing this
> problem?

Check the init string.  If you have AT&F1 change it to AT&F2
Some Supra modems should use &F2

--
Andrew

SupraExpress Modem problems

[Julian Gilbey]

[Please Cc: me in replies.]

I have just tried setting up a Debian system for someone, and have
been unable to get his modem to work.  The details are:

 - fresh slink (Debian 2.1) installation from the official CDs on a
   Pentium.
 - Windows reports the modem to be a SupraExpress 56i Sp Intl
 - I configured the PPP details using pppconfig with no special
   options or anything similar
 - the /var/log/ppp.log file showed that the intial connection had
   been attempted, and that after precisely 45 seconds, an alarm
   happened and the connection attempt failed.  Nothing happened
   between the "expect OK" and the alarm lines in the log.

Does anyone have any idea what to do or how to go about fixing this
problem?

Thanks in advance,

   Julian

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  Julian Gilbey, Dept of Maths, QMW, Univ. of London. [EMAIL PROTECTED]
Debian GNU/Linux Developer,  see http://www.debian.org/~jdg

ppp/modem problems .. suggestions?

[ferret]

Interesting little problem here. I have two machines, one at work, one at
home, both running slink.
As far as I know, both systems are running the same package versions for
everything installed (Synced from Slink CD and www.us.debian.org using
APT) and both have kernel 2.2.2 from www.us.kernel.org mirror. I have ppp,
pppconfig, and ppp-pam installed on both.

What's happening is that the machine at home will pass UDP packets but not
TCP packets, so I can ping and traceroute from it, but I can't telnet,
rlogin, or use ssh. The machine at work can connect and do everything just
fine. Also, the machine at work runs the ppp connection fine using the
kernel shipped with slink, and was running on another computer with a
custom 2.0.3x kernel.

The machine at work has a Creative Labs modem blaster jumpered for ttyS0,
while the machine at home is an external Ricochet modem on ttyS1. I
remember seeing a few posts last month about a similar problem, but I
can't seem to locate them ATM. And no, I can't take the Ricochet to work
to test on that computer for the time being.

Suggestions on what to try?

--Ian

Re: modem problems

[Ben Collins]

On Thu, Dec 31, 1998 at 11:33:08AM -0600, Brent Hueth wrote:
>
> Ok, got my new debian system up and running at work (yahoo!!), now i'm
> trying to do the same at home. Everything seems to have installed
> properly, but i can't get my modem to respond. I tried a cat > /dev/
> ttyS1 atdt## to see if i could get a response, and nothing. I'm sure
> that the modem is on comm2, and that it works, because my wife is able to
> connect to our ISP on the windows side of the machine (I'm not doing a
> very good job of convincing her that she should abandon the dark
> side :)). Any suggestions?

Well the line should be `echo atdt### > /dev/ttyS1` One thing you need
to be sure of that the modem is not classified as a WinModem which
means that it wont work under Linux. If you post the make and model,
some one should be able to tell you if it is or isn't.

--
--- -  -   ---  -  - - ---   
Ben Collins <[EMAIL PROTECTED]>  Debian GNU/Linux
UnixGroup Admin - Jordan Systems Inc. [EMAIL PROTECTED]
-- -- - - - ---   --- -- The Choice of the GNU Generation

modem problems

[Brent Hueth]

Ok, got my new debian system up and running at work (yahoo!!), now i'm 
trying to do the same at home. Everything seems to have installed 
properly, but i can't get my modem to respond. I tried a cat > /dev/
ttyS1 atdt## to see if i could get a response, and nothing. I'm sure 
that the modem is on comm2, and that it works, because my wife is able to 
connect to our ISP on the windows side of the machine (I'm not doing a 
very good job of convincing her that she should abandon the dark 
side :)). Any suggestions? 

Thanks.

Brent

Re: modem problems

[Raymond A. Ingles]

On Sun, 27 Sep 1998, Tracheotomy Bob wrote:

> I am damned if I can get my modem to work under linux. Here's the
> general situation.

 From your symptoms, it seems *very* doubtful that it's a Winmodem, but
*just* for the sake of paranoia, are you sure it's not? Does it work under
DOS?

> Poking around found wvdial, but according to that I do not have a modem
> installed. I have /dev/ttyS0, S1 and S2 but no modem. It appears that
> /dev/ttyS2 (com3 irq4 jumpered) is configured to be just another com
> port.

 No, no, the "com port" is just the place where Linux will send
information. If there's a modem there, it will receive it and send back
appropriate answers.

 UNLESS... there's an IRQ problem. The symptoms you describe are just
classic IRQ issues. What you need to do is tell Linux that /dev/ttyS2
("COM3" in DOS-speak) is using IRQ 4 instead of IRQ3. Take a look at
/etc/rc.boot/0setserial. In there, you can set ttyS2 to be any IRQ you
like. Try "man setserial" and the comments in the 0setserial file to see
how.

 Sincerely,

 Ray Ingles(248) 377-7735 [EMAIL PROTECTED]

  "...Windows - which is often referred to as 'the French labor union
 of software'..." - Dave Barry

modem problems

[Tracheotomy Bob]

I am damned if I can get my modem to work under linux. Here's the
general situation.
While I installed from the floppies and selected to do an ftp install,
the modem seemed to work. I say seemed because I was having problems
with it under Windows 98 that have now been resolved. However on the
latest install (many fdisk later) I elected not to do an ftp install
because I now have a CD. Whether this has any bearing on the situationor
not I don't know, but this is what happens.
If I run pppconfig to create a user account "virgin" (virgin.net) then I
get two scripts one in /etc/chatscripts and the other in /etc/ppp/peers.
That seems OK. If I do a "pon virgin" though and watch events through
"plog" then the /etc/chatscript/virgin sends the modem an ATZ command
which the modem takes TWENTY seconds to answer. Then ATDT takes a
further TEN seconds before the modem dials out. Once the modem has
dialed out, it is unable to establish a serial connection with a message
about always having bit 7 set to zero.
Poking around found wvdial, but according to that I do not have a modem
installed. I have /dev/ttyS0, S1 and S2 but no modem. It appears that
/dev/ttyS2 (com3 irq4 jumpered) is configured to be just another com
port.
If I do a "more /proc/interrupts" irq 4 says "4+serial"

So I suppose I want to know, what script does the debian install routine
run that's different? How do I tell the OS that /dev/ttyS2 is a modem?
What exactly is the relationship between com1 and com3? The serial howto
implies that I cannot use com3 if com1 is in use, and /proc/interrupts
implies com1 is in use, but if I remove it in the BIOS then the modem
doesn't work in windows. What's going on?
I've read the ppp and serial howtos and the setserial manpage and at the
moment it doesn't make any sense. Is someone able to give me a clear
explanation of what to do.
I will be eternally grateful.
If anyone needs more information mail me and I will try to be as clear
as possible.

Thanks.

Re: PCMCIA modem problems after hamm upgrade

[Julian Gilbey]

Just a little more info on this one: I have compiled all of the
requisite parts of the kernel, and I even compiled them in directly
rather than as modules, as I thought that might be part of the
problem.

> I have just upgraded from bo to hamm (which was quite a task -- I put
> in the wrong directory structure into dpkg-ftp and it completely
> corrupted my status file -- thank Gd for backups...).
> 
> I've now updated all my packages to the versions in the stable hamm
> release, and have recompiled my kernel (2.0.34).  I have a laptop with
> a PCMCIA modem (Psion Dacom Gold 56K).  I have compiled my pcmcia
> utils to match the current kernel.  I have the latest versions of
> netbase, dip, ppp, etc.  However, when I try to connect to either my
> college (via SLIP) or my ISP (via PPP), the connection appears to be
> made with no problems (I use dip, with the same script I used before
> upgrading), but then the line is disconnected immediately.  So I can't
> connect to the outside world from home.  8-(
> 
> Has anyone got any suggestions for how to fix this problem?  All help
> appreciated
> 
>Julian

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

   Julian Gilbey Email: [EMAIL PROTECTED]
   Dept of Mathematical Sciences,
   Queen Mary & Westfield College,
   Mile End Road, London E1 4NS, ENGLAND


--  
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

PCMCIA modem problems after hamm upgrade

[Julian Gilbey]

I have just upgraded from bo to hamm (which was quite a task -- I put
in the wrong directory structure into dpkg-ftp and it completely
corrupted my status file -- thank Gd for backups...).

I've now updated all my packages to the versions in the stable hamm
release, and have recompiled my kernel (2.0.34).  I have a laptop with
a PCMCIA modem (Psion Dacom Gold 56K).  I have compiled my pcmcia
utils to match the current kernel.  I have the latest versions of
netbase, dip, ppp, etc.  However, when I try to connect to either my
college (via SLIP) or my ISP (via PPP), the connection appears to be
made with no problems (I use dip, with the same script I used before
upgrading), but then the line is disconnected immediately.  So I can't
connect to the outside world from home.  8-(

Has anyone got any suggestions for how to fix this problem?  All help
appreciated

   Julian

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

   Julian Gilbey Email: [EMAIL PROTECTED]
   Dept of Mathematical Sciences,
   Queen Mary & Westfield College,
   Mile End Road, London E1 4NS, ENGLAND


--  
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

Re: modem problems

[Eric]

1) Is the modem plug and play, and if so, are you using isapnp?
2) What version of Debian are you using?

If you are using hamm you should be able to allow normal users to use
dial-up services by adding them to group dip.  This probably holds true in
bo also, but I'm not sure (I had to change some permissions in the version
of bo that I had, but that was a long time ago).

 _  _ 
| |(_)
|  _|  | |
| |___ | |
|__/ |
 |__/ 

On Sat, 4 Jul 1998, Micha Feigin wrote:

> I tried to connect a 33600 modem to my system.
> This is a deferent computer then the one the hardisk usually runs on
> if that changes anything (on the regular computer there is a 14400
> modem which works fine)
> I tried to set up using pppconfig.
> when i start pon i get a response (in plog)
> pppd 2.3.3 started by root uid0
> tcetattr invalid argument
> 
> It sends a connect string to the modem but gets no responce.
> I tried every com port in case i got the port mistaken.
> I know the modem works because it runs fine one win95 that i've got
> installed on this computer.
> 
> I've also got another problem with setup on the running modem.
> How do i enable pon to be run users other then root?
> It works fine when i run it as root, but when i run it as another user
> it just gets stuck


--  
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

modem problems

[Micha Feigin]

I tried to connect a 33600 modem to my system.
This is a deferent computer then the one the hardisk usually runs on
if that changes anything (on the regular computer there is a 14400
modem which works fine)
I tried to set up using pppconfig.
when i start pon i get a response (in plog)
pppd 2.3.3 started by root uid0
tcetattr invalid argument

It sends a connect string to the modem but gets no responce.
I tried every com port in case i got the port mistaken.
I know the modem works because it runs fine one win95 that i've got
installed on this computer.

I've also got another problem with setup on the running modem.
How do i enable pon to be run users other then root?
It works fine when i run it as root, but when i run it as another user
it just gets stuck


_
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com


--  
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

Re: Modem Problems

[shaul]

The log files could help you tracking the problem. 
Perhaps sending the relevant parts to the list might also help.

> When connecting to the internet via pppd, my connection is 
> VERY slow, i average 400bytes/sec, ping time to my isp is
> ...


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ISDN modem problems (SOLVED)

[Christian Lynbech on satellite]

I have now my Zyxel Omni.net plus ISDN modem up and running. The
crucial informaton seemed to have comed from the Serial-programing
HOWTO and involves IRQ priorities. Enabling `irqtune' in
/etc/rc.boot/hwtools seems to have done the trick.


---+--
Christian Lynbech  | Telebit Communications A/S   
Fax:   +45 8628 8186   | Fabrik 11, DK-8260 Viby J
Phone: +45 8628 8177 + 28  | email: [EMAIL PROTECTED] --- URL: 
http://www.telebit.dk
---+--
Hit the philistines three times over the head with the Elisp reference manual.
- [EMAIL PROTECTED] (Michael A. Petonic)


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Modem Problems

[Norbert Veber]

On Sat, Apr 25, 1998 at 12:13:42AM -0400, Brent Wooden wrote:
> 
> When connecting to the internet via pppd, my connection is 
> VERY slow, i average 400bytes/sec, ping time to my isp is
> ~.500ms.  I am using an ACER 28.8 and the modem worked
> "speedily" in windows, but ever since the crossover to linux
> i have been plagued by this annoying problem, if anyone
> has had similar problems with their modem, or knows what
> could be causing this, speak up...
> 
> i have tried other modems, 56ks and the like that work 
> perfectly fine on other computers but are slowed to a halt
> (nearly) when installed on mine.  I'd like to reitterate
> that the modem did work fine in windows (nor be it a
> winmodem), and so it is not a hardware problem to my 
> knowledge... any help would be appreciated...

what is your pppd configuration?  You need to use the crtscts option in
order to enable hardware flow control.  If that is not the problem, then
look into irqtune, I can't remember the url right now for the web page, but 
I'm pretty sure its somewhere on ftp://sunsite.unc.edu.


pgpGDb4tEVgOf.pgp
Description: PGP signature

Modem Problems

[Brent Wooden]

When connecting to the internet via pppd, my connection is 
VERY slow, i average 400bytes/sec, ping time to my isp is
~.500ms.  I am using an ACER 28.8 and the modem worked
"speedily" in windows, but ever since the crossover to linux
i have been plagued by this annoying problem, if anyone
has had similar problems with their modem, or knows what
could be causing this, speak up...

i have tried other modems, 56ks and the like that work 
perfectly fine on other computers but are slowed to a halt
(nearly) when installed on mine.  I'd like to reitterate
that the modem did work fine in windows (nor be it a
winmodem), and so it is not a hardware problem to my 
knowledge... any help would be appreciated...

brent


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ISDN modem problems

[Christian Lynbech on satellite]

> "Jens" == Jens B Jorgensen <[EMAIL PROTECTED]> writes:

Jens> I use a Zyxel OMNI TA 128U (almost the exact same beast) with a single 64K
Jens> channel. It has no problems. My server machine is a P90 overclocked to 
100 with
Jens> 40MB of memory. Perhaps you're getting buffer overruns on your serial 
port. What
Jens> baud rate are you running your serial  port at?

I am using 115200 in my pppd options file, and use setserial with the
spd_vhi flag on the device. And I am only using a single channel.

I have made some progress though. I was using an extra serial port I had
installed. Though there should be no IRQ conflicts, removing that
board and using the builtin one (COM2) made the whole thing run much
better.

However, I am still not able to get the ISDN line up when X11 is
running (due to massive ppp frame fcs problems). 

I am suspecting that I am experiencing IRQ priority problems (could be
that X increased the latency of some higher priority IRQ), but having
spent a couple of hours with my nose in Serial-programming HOWTO did
not help much. Irqtune did not seem to make any difference to that
problem.

Is my PC just too slow?


---+--
Christian Lynbech  | Telebit Communications A/S   
Fax:   +45 8628 8186   | Fabrik 11, DK-8260 Viby J
Phone: +45 8628 8177 + 28  | email: [EMAIL PROTECTED] --- URL: 
http://www.telebit.dk
---+--
Hit the philistines three times over the head with the Elisp reference manual.
- [EMAIL PROTECTED] (Michael A. Petonic)


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ISDN modem problems

[Jens B. Jorgensen]

I use a Zyxel OMNI TA 128U (almost the exact same beast) with a single 64K
channel. It has no problems. My server machine is a P90 overclocked to 100 with
40MB of memory. Perhaps you're getting buffer overruns on your serial port. What
baud rate are you running your serial  port at?

Christian Lynbech on satellite wrote:

> I have just got myself an ISDN line and a Zyxel Omni.net plus modem,
> but I have problems in getting it to work smoothly.
>
> The problem is that I keep getting error messages saying something to
> the effect of:
>
> ppp: frame with bad fcs, excess = 4de9
>
> The more trafic (for instance with ping) I generate, the less packages
> comes through. The limit seems to be around packet sizes of 2048/4096.
>
> If I stress my machine (which is a pentium 75 with 48Mb of RAM, a
> couple of years old), more packages are dropped.
>
> If my machine is only lightly loaded, pppd will only come up if I use
> the option:
>
> kdebug 7
>
> Otherwise it fails rather eraly in the initial negotiations when a
> ConfReq never sees the corresponding ConfAck.
>
> However, if I run a heavy job (such as a kernel compilation), the
> kdebug is not necessary to get pppd up. It will drop a few packages
> with ping -s 4096, but now silently. With ping -s 8192, almost nothing
> gets through.
>
> If I run X11, the connection can not get up (with kdebug 7).
>
> Does anybody have an idea where and how I should investigate? Should I
> suspect my serial port? Is my machine simply too slow to handle a
> 64kps connection? Is there any kernel option I can set?

--
Jens B. Jorgensen
[EMAIL PROTECTED]



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

ISDN modem problems

[Christian Lynbech on satellite]

I have just got myself an ISDN line and a Zyxel Omni.net plus modem,
but I have problems in getting it to work smoothly.

The problem is that I keep getting error messages saying something to
the effect of:

ppp: frame with bad fcs, excess = 4de9

The more trafic (for instance with ping) I generate, the less packages
comes through. The limit seems to be around packet sizes of 2048/4096.

If I stress my machine (which is a pentium 75 with 48Mb of RAM, a
couple of years old), more packages are dropped.

If my machine is only lightly loaded, pppd will only come up if I use
the option:

kdebug 7

Otherwise it fails rather eraly in the initial negotiations when a
ConfReq never sees the corresponding ConfAck.

However, if I run a heavy job (such as a kernel compilation), the
kdebug is not necessary to get pppd up. It will drop a few packages
with ping -s 4096, but now silently. With ping -s 8192, almost nothing
gets through.

If I run X11, the connection can not get up (with kdebug 7).

Does anybody have an idea where and how I should investigate? Should I
suspect my serial port? Is my machine simply too slow to handle a
64kps connection? Is there any kernel option I can set?


---+--
Christian Lynbech  | Telebit Communications A/S   
   | Fabrikvej 11, DK-8260 Viby J 
Phone: +45 8628 8176   | email: [EMAIL PROTECTED] --- URL: 
http://www.tbit.dk
---+--
Hit the philistines three times over the head with the Elisp reference manual.
- [EMAIL PROTECTED] (Michael A. Petonic)




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Modem Problems....

[shaul]

>Is there a neat utility to display what things are using what IRQs?

Does not 
cat /proc/interrupts 
be of some help ?


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Modem Problems....

[shaul]

> I was trying to setup debian on another computer:
> The serial module only detects /dev/ttyS1.

Is the modem on differenet tty ? Perhaps it is a PNP modem ?

> I tried to get minicom to dial out on /dev/ttyS1, but it doesnt seem to
> initialize it, and the modem doesn't make any noise when I try to dial.

Does minicom set up is correct ?
What does minicom replies when you try to initialize the modem ?

> Any suggestions as to where I should go from here to try and get the
> modem to work?





--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Modem Problems....

[Bob Hilliard]

cat /proc/interrupts
bob

[EMAIL PROTECTED] writes:
> Is there a neat utility to display what things are using what IRQs?


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Modem Problems....

[Nathan E Norman]

On Tue, 24 Feb 1998, Timothy M. Hospedales wrote:

: Is there a neat utility to display what things are using what IRQs?
: 
: Thanks,
: Timothy

cat /proc/interrupts

: 
: > Sounds like you have an IRQ conflict. Read the 'dmesg' output and see
: > exactly what interrupt the serial port is on, and make sure it's not
: > the same interrupt as another card.
: >
: 
: 
: 
: 
: --
: TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
: [EMAIL PROTECTED] . 
: Trouble?  e-mail to [EMAIL PROTECTED] .
: 
: 

--
Nathan Norman
MidcoNet - 410 South Phillips Avenue - Sioux Falls, SD  57104
phone: (605) 334-4454 fax: (605) 335-1173
mailto://[EMAIL PROTECTED]   http://www.midco.net
PGP Key ID: 0xA33B86E9 - Public key available at keyservers
PGP Key fingerprint: CE03 10AF 3281 1858  9D32 C2AB 936D C472



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Modem Problems....

[Jeff Noxon]

On Tue, Feb 24, 1998 at 11:36:19PM +0400, Timothy M. Hospedales wrote:
> Is there a neat utility to display what things are using what IRQs?

cat /proc/interrupts

Jeff


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Modem Problems....

[Timothy M. Hospedales]

Is there a neat utility to display what things are using what IRQs?

Thanks,
Timothy

> Sounds like you have an IRQ conflict. Read the 'dmesg' output and see
> exactly what interrupt the serial port is on, and make sure it's not
> the same interrupt as another card.
>




--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Modem Problems....

[David Stern]

On Mon, 23 Feb 1998 13:16:47 +0400, "Timothy M. Hospedales" wrote:
> I was trying to setup debian on another computer:
> The serial module only detects /dev/ttyS1.
> I tried to get minicom to dial out on /dev/ttyS1, but it doesnt seem to
> initialize it, and the modem doesn't make any noise when I try to dial.
> Any suggestions as to where I should go from here to try and get the
> modem to work?

When I went through this, I found the Net3 and Serial HOWTO's quite 
useful.
-- 
David Stern  
--
 http://weber.u.washington.edu/~kotsya
   [EMAIL PROTECTED]




--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Modem Problems....

[Ben Gertzfield]

> "Timothy" == Timothy M Hospedales <[EMAIL PROTECTED]> writes:

Timothy> I was trying to setup debian on another computer: The
Timothy> serial module only detects /dev/ttyS1.  I tried to get
Timothy> minicom to dial out on /dev/ttyS1, but it doesnt seem to
Timothy> initialize it, and the modem doesn't make any noise when
Timothy> I try to dial.  Any suggestions as to where I should go
Timothy> from here to try and get the modem to work?  Thanks,
Timothy> Timtohy.

Sounds like you have an IRQ conflict. Read the 'dmesg' output and see
exactly what interrupt the serial port is on, and make sure it's not
the same interrupt as another card.

-- 
Brought to you by the letters T and U and the number 9.
"Disobeying me?" "No, I don't." -- Final Fantasy II
Ben Gertzfield  Finger me for my public
PGP key. I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Modem Problems....

[Timothy M. Hospedales]

I was trying to setup debian on another computer:
The serial module only detects /dev/ttyS1.
I tried to get minicom to dial out on /dev/ttyS1, but it doesnt seem to
initialize it, and the modem doesn't make any noise when I try to dial.
Any suggestions as to where I should go from here to try and get the
modem to work?
Thanks,
Timtohy.


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: modem problems

[Hamish Moffatt]

On Sat, Jan 03, 1998 at 01:58:10PM -0600, Mark W. Blunier wrote:
> That seems odd.  I thought that Linux would only set
> tty00 and tty01 at bootup.

/etc/rc.boot/0setserial will only set up the first two ports,
because the ttyS2 and S3 have less standard locations (especially
IRQs), and also S3 and 0x2e8 may clash with some video cards.
The configuration IS in there though, it just has to be uncommented.

0setserial here configures and autoIRQs all four ports
correctly (3F8/4, 2F8/3, 3E8/5, 2E8/7).

hamish
-- 
Hamish Moffatt, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5
CCs of replies from mailing lists are welcome.   http://hamish.home.ml.org


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

modem problems

[Dennis Drapeau]

hi again

when I run  :

setserial -a /dev/ttyS3 I get:

/dev/ttyS3, Line 3, UART: 16550A, Port: 0x02e8, IRQ: 3
   Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000, closing_wait2: infinte
   Flags: spd_vhi split_termios session_lockout

and setserial -a /dev/ttyS3 :

/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
   Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000, closing_wait2: infinte
   Flags: spd_normal skip_test split_termios session_lockout

when I say cannot dialout, I mean I can get DIP to show the port and set
speed, but if I try to reset the modem or dialout, it hangs.

ls -l /dev/ttyS3 :

crw-rw   1 root dialout4,  64 Jan  3 18:17 /dev/ttyS0
crw-rw   1 root dialout4,  65 Jan  2 21:10 /dev/ttyS1
crw-rw   1 root dialout4,  66 May 27  1997 /dev/ttyS2
crw-rw   1 root dialout4,  67 Jan  3 18:36 /dev/ttyS3

I have no /dev/cua* defined  does that make a difference?

still confused,

dennis


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: modem problems

[Mark W. Blunier]

On Sat, 3 Jan 1998, Dennis Drapeau wrote:

> Please help.   I can't get my modem to work under linux, but it works
> fine in NT.  The settings in NT are:
> 
> IRQ 3  and IO 0x2e8   (COM4) .
> 
> When booting linux, it sees my serial ports at :
> 
> /dev/tty00 at 0x03f8 (irq = 4) is a 16550A
> /dev/tty03 at 0x02e8 (irq = 3) is a 16550A

That seems odd.  I thought that Linux would only set
tty00 and tty01 at bootup.

> 
> and after /rc.boot/0setserial is run they are configured to :
> 
> /dev/ttyS0  at 0x03f8 (irq = 4) is a 16550A
> /dev/ttyS3  at 0x02e8 (irq = 3) is a 16550A
> 
> Seems ok to me, but I cannot dial out from port /dev/ttyS3.The group
> on /dev/ttyS3 is dialout.
> 
> When I checked /proc/interrupts ,  there is no assignment for IRQ 3 .  I
> have no idea what to do next .

A stab in the dark, but try setserial -a /dev/ttyS1
setserial -a /dev/ttyS3 to see how they are configured.
Also make sure that you have the serial module loaded, or that serial
devices are compiled into the kernel.


Mark
[EMAIL PROTECTED]



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: modem problems

[Miquel van Smoorenburg]

In article <[EMAIL PROTECTED]>,
Dennis Drapeau <[EMAIL PROTECTED]> wrote:
>/dev/ttyS0  at 0x03f8 (irq = 4) is a 16550A
>/dev/ttyS3  at 0x02e8 (irq = 3) is a 16550A
>
>Seems ok to me, but I cannot dial out from port /dev/ttyS3.The group
>on /dev/ttyS3 is dialout.

What do you mean with "cannot dialout" ?

>When I checked /proc/interrupts ,  there is no assignment for IRQ 3 .  I
>have no idea what to do next .

That's right, the IRQ is only allocated when the port is in use. Multiple
ports can use the same IRQ, only not at the same time (with ISA that is).

Mike.
-- 
 Miquel van Smoorenburg |  The dyslexic, agnostic, insomniac lay in his bed
[EMAIL PROTECTED]  |  awake all night wondering if there is a doG


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

modem problems

[Dennis Drapeau]

Please help.   I can't get my modem to work under linux, but it works
fine in NT.  The settings in NT are:

IRQ 3  and IO 0x2e8   (COM4) .

When booting linux, it sees my serial ports at :

/dev/tty00 at 0x03f8 (irq = 4) is a 16550A
/dev/tty03 at 0x02e8 (irq = 3) is a 16550A

and after /rc.boot/0setserial is run they are configured to :

/dev/ttyS0  at 0x03f8 (irq = 4) is a 16550A
/dev/ttyS3  at 0x02e8 (irq = 3) is a 16550A

Seems ok to me, but I cannot dial out from port /dev/ttyS3.The group
on /dev/ttyS3 is dialout.

When I checked /proc/interrupts ,  there is no assignment for IRQ 3 .  I
have no idea what to do next .

thanks in advance...

dennis



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re[2]: modem problems

[TENCC01.LEWIS01]

Actually, it's worse than just what follows the "CONNECT".  If the line
quality goes down, most modems will drop speed accordingly.  That would
mean an change in speed at the tty "on the fly".  That is rather hard to
predict...

jim


__ Reply Separator _____
Subject: Re: modem problems
Author:  [EMAIL PROTECTED] at ~AMSCCSSW
Date:10/26/97 9:13 PM


Andrew J Tarr <[EMAIL PROTECTED]> writes:

> No, it wasn't. Yes, it fixed it, thanks a lot. I don't suppose anyone
> wants to explain why it needs fixed serial speed?

Because there is very little Linux software that adjusts the TTY speed
according to what follows the "CONNECT".  I suspect that it might be
possible to convince mgetty to do it, but minicom and pppd won't.
Also, a 14.4K connection can sometimes get more data - I got 3K/s
downloading some Postscript files.

--
Carey Evans  <*>  http://home.clear.net.nz/pages/c.evans/  gc

   Neniu anticipas la hispanan Inkvizicion.


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble?  e-mail to [EMAIL PROTECTED] .


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: modem problems

[Carey Evans]

Andrew J Tarr <[EMAIL PROTECTED]> writes:

> No, it wasn't. Yes, it fixed it, thanks a lot. I don't suppose anyone
> wants to explain why it needs fixed serial speed? 

Because there is very little Linux software that adjusts the TTY speed
according to what follows the "CONNECT".  I suspect that it might be
possible to convince mgetty to do it, but minicom and pppd won't.
Also, a 14.4K connection can sometimes get more data - I got 3K/s
downloading some Postscript files.

-- 
Carey Evans  <*>  http://home.clear.net.nz/pages/c.evans/  gc

   Neniu anticipas la hispanan Inkvizicion.


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .