The answer turned out to be that I could only use the console in
single-user mode. (duh!) That had not been the case previously,
so I was trying to use it in multi-user mode. My original plaint
and some responses below.
-Amy Skowronek
------------- Begin Forwarded Message -------------
>From alpha-osf-managers-relay_at_sws1.ctd.ornl.gov Tue Dec 24 11:22:19 1996
Sender: alpha-osf-managers-relay_at_sws1.ctd.ornl.gov
Followup-To: poster
Date: Tue, 24 Dec 1996 11:09:19 -0500
From: "Amy E. Skowronek" <amy_at_aloha.nascom.nasa.gov>
To: alpha-osf-managers_at_ornl.gov
Subject: console not responding on alphaserver 1000a
Content-Transfer-Encoding: 7bit
Content-Md5: yDCvYfgbFaCcPjD5yecDLQ==
I have an Alphaserver 1000a running DU 3.2G. I think it worked
before, but this time when I plugged in the console I couldn't
get a response. System messages get printed on the console,
but when I hit return I don't get a prompt. The console is a
vt510. I have it plugged in on COM1.
I don't get any error messages regarding the console.
------------- End Forwarded Message -------------
From: "Richard L. Eisenman" <eisenman_at_tricity.wsu.edu>
Check your console configuration. Be sure it's set to vt510. You might
also try another common console def, such as vt100.
From: "Robert L. McMillin" <rlm_at_syseca-us.com>
One of two possibilities come to mind immediately: either the system
thinks it should be booting on the video console (do you have one?), or
your terminal is broken. In the first case, attach a conventional
monitor and keyboard to the 1000A and see what happens. In the second,
swap out the terminal. After that, I'm stumped.
From: "Jeffrey G. Micono 6533 (Ktech)" <jgmicon_at_sandia.gov>
I'm not sure about the 1000, but I think you need to do a
"set console X" (I think X is "serial", but check your
User Information) at the ">>>" prompt while you have the keyboard and
display attached. Then on the next power cycle, the system should
respond on the serial port.
From: rp001ns_at_ccnmuc.net (.)
1. if the console variable is set to graphics:
check if a getty process is running for /dev/tty00. (ps aux |grep getty)
2. if the console variable is set to serial:
check if a getty process is running for /dev/console. double check the
communication parameters (baudrate etc.) between the terminal and the /etc/gettydefs
entry.
3. Switch the console on and off, because the vt510 is programmable and maybe
the terminal have some problem with the received data!
4. Look into your hardware manual, maybe port 2 is the console port (on some alpha machines)
Received on Tue Feb 11 1997 - 00:43:54 NZDT