summaryrefslogtreecommitdiffstats
path: root/release
diff options
context:
space:
mode:
authorwilko <wilko@FreeBSD.org>2000-12-13 19:57:08 +0000
committerwilko <wilko@FreeBSD.org>2000-12-13 19:57:08 +0000
commit451a5f61115c9c7d3deeaa763a1296bec1e1999c (patch)
treef7991065ade0c59a011aa8335973479a8ed0c895 /release
parent1575d4ecd73853fc50aaf5fa415028d4ec039917 (diff)
downloadFreeBSD-src-451a5f61115c9c7d3deeaa763a1296bec1e1999c.zip
FreeBSD-src-451a5f61115c9c7d3deeaa763a1296bec1e1999c.tar.gz
For PC164: document "ERROR: ISA table corrupt!" and workaround
Thanks to: naddy@mips.inka.de
Diffstat (limited to 'release')
-rw-r--r--release/texts/alpha/HARDWARE.TXT5
1 files changed, 4 insertions, 1 deletions
diff --git a/release/texts/alpha/HARDWARE.TXT b/release/texts/alpha/HARDWARE.TXT
index 41d58c1..1df8dbd 100644
--- a/release/texts/alpha/HARDWARE.TXT
+++ b/release/texts/alpha/HARDWARE.TXT
@@ -789,7 +789,10 @@ SRM quirks:
PC164 the SRM sometimes seems to loose its variable settings.
"For PC164, current superstition says that, to avoid losing settings,
you want to first downgrade to SRM 4.x and then upgrade to a 5.x"
-Other PC164 owners report they have never seen the problem.
+One sample error that was observed was: "ERROR: ISA table corrupt!".
+A sequence of a downgrade to SRM4.9, an 'isacfg -init' and an 'init'
+made the problem go away. Some PC164 owners report they have never seen
+the problem.
On PC164SX the AlphaBIOS allows you a selection to select 'SRM' to
be used as console on the next power up. This selection does not appear to
OpenPOWER on IntegriCloud