From owner-freebsd-alpha Sun Dec 10 15:30:50 2000 From owner-freebsd-alpha@FreeBSD.ORG Sun Dec 10 15:30:48 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 3BC7837B400 for ; Sun, 10 Dec 2000 15:30:48 -0800 (PST) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 145Fva-0003gp-00; Mon, 11 Dec 2000 00:30:46 +0100 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.1/8.11.1) id eBAMibE00699 for freebsd-alpha@freebsd.org; Sun, 10 Dec 2000 23:44:37 +0100 (CET) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: SRM: "ISA table corrupt!"? Date: Sun, 10 Dec 2000 22:44:37 +0000 (UTC) Message-ID: <91110l$am$1@kemoauc.mips.inka.de> References: <90ouu9$2ni$1@kemoauc.mips.inka.de> <20001207223833.A2651@freebie.demon.nl> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: daemon@mips.inka.de Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte wrote: > > ERROR: ISA table corrupt! > > Initializing table to defaults > > Guessing: would this possibly be related to: > > " > SRM quirks: > PC164 the SRM sometimes seems to loose its variable settings. Possibly. What's strange is that if I do "isacfg -init" followed by "isacfg -all" I get another warning about a corrupted ISA table. My SRM indeed doesn't seem to hold variable settings across power cycling. There's no special action to take, it should just remember things like "set bootdef_dev dka0", shouldn't it? -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message