Managers,
Wow, I never expected replies so quickly, thanks to all. I'll summarize
with a quick review of the quesitons, the answers, then repost the original
message at the end.
1) Keyboard works at the console prompt, but keyboard and mouse don't work
after booting Unix - I got several responses on the keyboard, looks like
the mouse failure has everyone stumped.
Richard Eisenman <eisenman_at_tricity.wsu.edu> suggested that perhaps the
console variable at the ROM prompt was incorrect. It is set to graphics
as before (and on a working system) so I think that's ok.
Eric Wyn Jones <e.w.jones_at_bangor.ac.uk> has had a similar problem and
either the upgrade to 4.0b or firmware V3.8 fixed it. We supposedly
have maintenance, but haven't received either one. I'll have to pester
DEC about that.
Tom Webster <webster_at_ssdpdc.mdc.com> was asking if we used a console
switch since he's had trouble with those. Yes, we tried that a few
months ago, but that failed miserably. Until I find a switch that works,
I'm using (or trying to use!) 2 keyboards, 2 mice, and one monitor that
I manually move from one Alpha to the other.
Alex_Nord_at_jabil.com suggested getting patch v4.0_kbd_ms_patch and
suggested not touching the keyboard/mouse AT ALL during bootup but that
didn't make any difference. He kindly included the patch as an
attachment but I doubt it'll survive being extracted from a VMS mail
message then being copied to a floppy and taken to the Unix box in
question. I'll try to get DEC to send the patch on floppy (ies) or CD.
2) How do I get the file /var/adm/sialong to record su, etc?
Several responded that all that's needed is touch /var/adm/sialog and
that did the trick. Steve Beikman <beikmas_at_cliffy.polaroid.com>
added chmod 600 sialog to the command along with a few other pointers.
Rich Frank <rnfrank_at_pierce.llnl.gov> suggested using Dxaudit instead
since it provides more detailed records.
Thanks again,
Jim
-------------------------------------------------------------------------
Original post:
Managers,
I've run into a problem with our AlphaServer 2100A 4/275 running Digital
Unix 4.0a. I haven't made any changes recently, and had to shut down
the system Friday due to a building wide power outage scheduled for
Saturday morning. I turned on the system, monitor, etc. Monday, checked
things out at the console prompt, and then booted. Once the Unix login
screen popped up the mouse didn't work and neither did the keyboard. I
tried a different known good mouse and keyboard and cycled the power.
Again, I could type all I wanted at the console prompt but after booting
nothing worked, not even the caps lock key. Anyone have any ideas why the
keyboard and mouse would quit functioning after booting Unix?
Also, there is supposed to be a file /var/adm/sialog that tracks su
commands, etc. What has to be done to start up the process that generates
that file? C2 security is enabled on this system.
Thanks, I'll summarize.
James W. DeLozier
Systems Manager
Naval Air Warfare Center Training Systems Division
Orlando, FL
systemjd_at_field.ntsc.navy.mil
Received on Thu May 01 1997 - 23:58:04 NZST