Path: utzoo!censor!geac!jtsv16!uunet!cs.utexas.edu!sun-barr!ames!pacbell!att!laidbak!obdient!simon!steve From: steve@simon.UUCP (Steven E. Piette) Newsgroups: comp.sys.apollo Subject: Re: Apollo Serial IO line problems (HELP!) Keywords: help! Message-ID: <353@simon.UUCP> Date: 9 Aug 89 01:11:58 GMT References: <1594@cod.NOSC.MIL> Distribution: usa Organization: ACT, Inc., Dank Dark Cave, Algonquin, IL. Lines: 42 In article <1594@cod.NOSC.MIL>, cynthia@cod.NOSC.MIL (Cynthia G. Anderson) writes: > help! > > i have run CPU.DEX on it--with and without a loopback connector-- > both ways (internal and external logic) came up perfectly fine. From to sounds of it the port is working, but .... > > I've tried using emt, (terminal emulation) as well as kermit. > These same programs with identical configurations work on > other apollo's around here. > > Hopefully significant: > the error i get whenever i use emt now is > Unable to open stream to SIO line: /dev/sio1 --cannot open a remote sio > line (stream manager/open) What we need now is an ld -a of the /sys/node_data/dev directory. It sounds like the entry for sio1 is something other than a file of type sio. Given the problems you had with software and system crashes this could be wrong. The files for the sio ports in the dev directory ARE special. They have a type of sio and contain information on which port they are for. (I never tried to find out where. Maybe it was via a canned ACL in the VTOCE that gave the port.) Anyway, let's see what the dev directory looks like since the error message looks like /dev/sio1 (really /dev -> `node_data/dev) is linked or pointing to another system and so the remote part of the message. I hope this helps. > > cynthia anderson > Naval Ocean Systems Center, San Diego, CA 92107 -- Steven E. Piette Applied Computer Technology Inc. UUCP: {smarthost}!simon!steve 1750 Riverwood Drive INET: steve@simon.CHI.IL.US or spiette@SUN.COM Algonquin, IL 60102 -------------------------------------------------------------------------------