🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.sys.sgi.misc
9 messages
9 total messages Started by Jim Meyering Mon, 25 Jan 1993 20:11
uucp w/SupraFax modem
#273
Author: Jim Meyering
Date: Mon, 25 Jan 1993 20:11
76 lines
2812 bytes
Re: call Id #153007

I'm not very familiar with UUCP (I used to be proud of that :-),
so I may be making some obvoius error, but here goes...

I'm using a SupraFax v42.bis modem on port2 (connected by a cable
bought from SGI).

% uname -a
IRIX [deleted] 4.0.5 06151813 IP12

I can dial out using cu -- like this:

    % cu -l /dev/tty[fmd]2 -s 38400 <phone-number>

The problem comes when I try to verify that uucp works by running Uutry.
The first time I ran it this morning, it got to the point at which it
starts the chat dialog.  But since there was a problem with the Dialers
entry, that didn't work and I interrupted it.

All subsequent times I've tried it today I get this output:

> # ./Uutry -x9 uunoname
> ./uucico -r1 -suunoname  -x9 >/tmp/uunoname 2>&1&
> tmp=/tmp/uunoname
> mchFind called (uunoname)
> list (rmail) num = 1
> list (/usr/spool/uucppublic) num = 1
> list (/usr/spool/uucppublic) num = 1
> list (rmail) list (uucp) list (rnews) list (uucico) num = 4
> _Request (TRUE), _Switch (TRUE), _CallBack (FALSE), _MyName ([deleted]), _Commands rmail
> _Commands uucp
> _Commands rnews
> _Commands uucico
> chdir(/usr/spool/uucp/uunoname)
> conn([deleted])
> Device Type ACU wanted
> mlock ttyf2 succeeded
> timed out
> generic open timeout
> set interface UNIX
> getto ret -1
> Call Failed: CAN'T ACCESS DEVICE
> exit code 101
> Conversation Complete: Status FAILED

> TM_cnt: 0

After the first failed try I reinitialized the modem to make sure
it's state was the same as for the initial successful connection.
But it still failed.

It looked like the state of something had changed since the first Uutry
run -- and maybe that something is what's causing the `time out'.
So I deleted all uucp lock files and ran `fuser /dev/tty[fdm]' to see
if some other process had one of those devices open -- but none did.
Uutry still fails.

----------------------
More background; some uucp configuration files

/usr/lib/uucp/Systems:
uunoname Any ACU 9600 9999999 "" ... [chat script deleted]

/usr/lib/uucp/Devices:
ACU ttyf2 - Any suprafax

/usr/lib/uucp/Dialers:
suprafax        =,-,    "" \dAT&F2\r\c OK ATDT\T\r\c CONNECT-\c-Connect
----------------------

If anyone can give me a lead I'd appreciate it.
-- 
Jim Meyering             | Member of the League for Programming Freedom
meyering@cs.utexas.edu   | Contact me or lpf@uunet.uu.net for more info.
Looking for SNMP agent
#274
Author: Andrew Schmidt
Date: Mon, 25 Jan 1993 20:35
11 lines
687 bytes
I'd like to know if someone has a public domain SNMP 
agent for IRIX Release 4.0.1?  

I've attempted to build the CMU 2.1 toolkit, but it
is rather Sun specific.

Any help would be much appreciated.

Thanks,
Andrew Schmidt
Re: uucp w/SupraFax modem
#282
Author: Andy Rabagliati
Date: Tue, 26 Jan 1993 08:12
30 lines
1609 bytes
In article <lm8icaINNr8@ai.cs.utexas.edu> meyering@cs.utexas.edu (Jim Meyering) writes:

>I'm using a SupraFax v42.bis modem on port2 (connected by a cable
>bought from SGI).
>
>
>The problem comes when I try to verify that uucp works by running Uutry.

I had exactly the same problem, and found that a solution was to have
uugetty running on the port, through an entry in /etc/inittab.

Private Email from them 'elpful souls at SGI was inconclusive, and did
not solve the problem. Actually, it was not really a problem for me as I
usually have uugetty running, but when testing the modem with Sams fax
software I had to switch uugetty off, and that is when I noticed it.

If it helps, faxd in the flexfax package also 'enables' uucico as well.

Maybe my modem swings on some lines it shouldn't.

And yes, permissions are OK all round, and nothing else is using
/dev/tty[dmf]2. I have a full house modem cable. Honest. Switch on
uugetty, it works, switch it off, it doesn't.

I would be very interested if this solves your problem.

Cheers,    Andy.
-- 
Amendment 2 information newsgroup co.politics.amend2.info - mailing list also.
andyr@wizzy.com          W.Z.I. Consulting (719)635-6099               pgp-2.1
Re: uucp w/SupraFax modem
#309
Author: Kevin Brokaw
Date: Tue, 26 Jan 1993 23:22
60 lines
3549 bytes
In article <C1GC43.2oz@wizzy.com>, andyr@wizzy.com (Andy Rabagliati) writes:
|> In article <lm8icaINNr8@ai.cs.utexas.edu> meyering@cs.utexas.edu (Jim Meyering) writes:
|> I had exactly the same problem, and found that a solution was to have
|> uugetty running on the port, through an entry in /etc/inittab.
|> 
|> Private Email from them 'elpful souls at SGI was inconclusive, and did
|> not solve the problem. Actually, it was not really a problem for me as I
|> usually have uugetty running, but when testing the modem with Sams fax
|> software I had to switch uugetty off, and that is when I noticed it.
|> 
|> If it helps, faxd in the flexfax package also 'enables' uucico as well.
|> 
|> Maybe my modem swings on some lines it shouldn't.
|> 
|> And yes, permissions are OK all round, and nothing else is using
|> /dev/tty[dmf]2. I have a full house modem cable. Honest. Switch on
|> uugetty, it works, switch it off, it doesn't.
|> 
|> I would be very interested if this solves your problem.
|> 

The problem in using Supra v32bis modems is due to uutry needing to 
see carrier detect on the modem before it will communicate. While running a 
uugetty is one way, possibly an easier way is to load the "Macintosh" profile
into the Supra as the default power-on profile. Most Supra modems shipped 
individually or as part of a DOS/WINDOWS package, use factory stored profile
number 2 as the power-up profile, which is listed in the Supra manual as
being for IBM (and all others except Macintosh), and asserts an AT&C1, 
which tells the modem to have DCD reflect a remote carrier. What the SGI
needs is to see DCD high before uutry will talk to the modem. This implies
an AT&C (or AT&C0) option, which is part of the Macintosh profile. If your
modem was not shipped specifically for use with a Macintosh, it will have 
the wrong profile (as far as using on an SGI goes) loaded as the power-up
profile. Here's how you change that....

start a session with the modem via cu

issue an AT&F1<enter>   /* Load Macintosh profile as active profile */
issue an AT&W0<enter>   /* Save this as user-stored profile 0 (or use 
                           an AT&W1 if you wish to store it as profile 1) */
issue an AT&Y0<enter>   /* To set stored user profile 0 as the power-up 
                           profile (or use AT&Y1 if you issued an AT&W1 ) */

This should do the trick... I brought my Supra in to the office and we tried
it on my indigo... uutry worked flawlessly, but if we broke out of the loop,
we had to remember to kill the uucico process before we tried it again.

I have sent e-mail to Supra suggesting that they may want to modify
their manual in future revisions to suggest &F1 as the profile for 
Macs as well as UUCP use.
Cheers,
Kevin



-- 
Kevin Brokaw   (kevinb@csd.sgi.com)     | 
Product support engineer                | Sorry, this closet is for anxieties.
Silicon Graphics Computer Systems       | Pipe dreams are under the bed. 
(Forgive them,they know not what I post)| 
Re: uucp w/SupraFax modem
#301
Author: Vernon Schryver
Date: Wed, 27 Jan 1993 02:46
20 lines
1252 bytes
In article <1993Jan26.232211.11996@news.csd.sgi.com>, kevinb@oblivion.csd.sgi.com (Kevin Brokaw) writes:
> 
> The problem in using Supra v32bis modems is due to uutry needing to 
> see carrier detect on the modem before it will communicate....


Whatever is happening is more complicated that that.

/usr/lib/uucp/Uutry simply runs uucico.
/usr/lib/uucp/uucio opens the port with NDELAY (given an appropriate
line in Devices), which is supposed to tell the port to not bother
waiting for DCD.

As far as I know, only the Supra is associated with this problem.
Other modems, including those programmed by /usr/lib/uucp/fix-*,
leave DCD false until carrier is finally detected, and uucico
works whether uugetty is on or not.


Vernon Schryver,  vjs@sgi.com
Re: uucp w/SupraFax modem
#296
Author: Andy Rabagliati
Date: Wed, 27 Jan 1993 10:52
29 lines
1428 bytes
In article <1993Jan26.232211.11996@news.csd.sgi.com> kevinb@oblivion.csd.sgi.com (Kevin Brokaw) writes:

>
>The problem in using Supra v32bis modems is due to uutry needing to 
>see carrier detect on the modem before it will communicate.

Ding !!!

This indeed solved my problem. I am not using a Supra, but a Twincom, a
Rockwell chip V.32bis modem.

I have AT&D3, so it does an ATZ on DTR loss.

So, if I put AT&C0&W0 to set profile 0 correctly, Uutry will pick up the
phone.

I also had ATZ in my Dialers script - which appears to be a rather
brutal way to start the day. With &C1 it was not a problem, but with &C0
I get "lost line errno - 0" - so there is a glitch on CD or something
that disappoints Uutry.

If I take ATZ out of my Dialers script it is smiles all round.

Chalk up another success to them Tech support guys ...

Cheers,  Andy.
-- 
Amendment 2 information newsgroup co.politics.amend2.info - mailing list also.
andyr@wizzy.com          W.Z.I. Consulting (719)635-6099               pgp-2.1
Re: uucp w/SupraFax modem
#299
Author: Kevin Brokaw
Date: Wed, 27 Jan 1993 19:20
28 lines
2082 bytes
In article <vcnnv9k@rhyolite.wpd.sgi.com>, vjs@rhyolite.wpd.sgi.com (Vernon Schryver) writes:
|> 
|> Whatever is happening is more complicated that that.
|>

You are correct... the response was a "nutshell" one. It is a basic 
design issue on the Rockwell chipset that the Supra (as well as nearly all
of the other V32bis fax/data modems costing under 275 dollars) uses.. some
shortcuts are taken in the modem design, and it isn't as flexable as 
Hayes/TB/USR/etc modems. I am trying to nail down the specifics, but
suffice at this point to say that I have verified that NDELAY is being
used when the port is opened, but nothing is sent to the modem anyway.
I've tested Uutry/uucico with another non-typical modem (IBM 7855), and 
it works flawlessly with DCD low. It seems that the only way to get 
a Supra to init w/uucico is to set DCD high on it... perhaps it has something
to do with the way the Supra handles DSR or RLSD, but that's a wild
guess. If I use cu it doesn't seem to matter whether or not I set DCD high. 

 
I apologize if my answer was too misleading as to the cause. I realize 
in hindsight that it seemed to point to uucico being the culpret, but
that was not my intent.

-- 
Kevin Brokaw   (kevinb@csd.sgi.com)     | 
Product support engineer                | Sorry, this closet is for anxieties.
Silicon Graphics Computer Systems       | Pipe dreams are under the bed. 
(Forgive them,they know not what I post)| 
Re: uucp w/SupraFax modem
#321
Author: Kevin Brokaw
Date: Wed, 27 Jan 1993 19:25
25 lines
1538 bytes
In article <C1IE7B.G9n@wizzy.com>, andyr@wizzy.com (Andy Rabagliati) writes:
|> I also had ATZ in my Dialers script - which appears to be a rather
|> brutal way to start the day. With &C1 it was not a problem, but with &C0
|> I get "lost line errno - 0" - so there is a glitch on CD or something
|> that disappoints Uutry.
|> 

Same results here... the default ATZ sets &C1, which will in effect turn
off CD if you had previously defined &C0. When I tested with Uutry,
I inserted an ATZ1 in the dial string, after init, and had stored a &C1
in profile 1. Same problem. I stored a &C0 in profile 0, and an ATZ0
did no damage.

|> Chalk up another success to them Tech support guys ...

Glad to help...

Cheers,
Kevin

-- 
Kevin Brokaw   (kevinb@csd.sgi.com)     | 
Product support engineer                | Sorry, this closet is for anxieties.
Silicon Graphics Computer Systems       | Pipe dreams are under the bed. 
(Forgive them,they know not what I post)| 
Re: uucp w/SupraFax modem
#306
Author: Vernon Schryver
Date: Thu, 28 Jan 1993 02:19
20 lines
1455 bytes
In article <1993Jan27.192545.1103@news.csd.sgi.com>, kevinb@oblivion.csd.sgi.com (Kevin Brokaw) writes:
> In article <C1IE7B.G9n@wizzy.com>, andyr@wizzy.com (Andy Rabagliati) writes:
> |> I also had ATZ in my Dialers script - which appears to be a rather
> |> brutal way to start the day. With &C1 it was not a problem, but with &C0
> |> I get "lost line errno - 0" - so there is a glitch on CD or something
> |> that disappoints Uutry.
> |> 
> 
> Same results here... the default ATZ sets &C1, which will in effect turn
> off CD if you had previously defined &C0. When I tested with Uutry,
> I inserted an ATZ1 in the dial string, after init, and had stored a &C1
> in profile 1. Same problem. I stored a &C0 in profile 0, and an ATZ0
> did no damage.


I don't quite understand, but it sounds as if the result will be
that DCD from the modem will "glitch."  That would mess things up.


Vernon Schryver,  vjs@sgi.com
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads