From owner-freebsd-alpha Mon Dec 11 5:32:57 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 05:32:55 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from home.se (smtphost2.home.se [195.66.35.198]) by hub.freebsd.org (Postfix) with ESMTP id B141837B400 for ; Mon, 11 Dec 2000 05:32:54 -0800 (PST) Received: from daniel.n.nilsson@home.se [161.114.88.74] by home.se with Novell Internet Messaging System Web Client; Mon, 11 Dec 2000 14:31:33 Subject: Re: Re: SRM: "ISA table corrupt!"? From: Daniel Nilsson To: naddy@mips.inka.de, freebsd-alpha@freebsd.org, Date: Mon, 11 Dec 2000 13:31:33 GMT X-Sender: Novell Internet Messaging System Web Client MIME-Version: 1.0 Message-ID: <976541493.190daniel.n.nilsson@home.se> Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Naddy, Some SRM versions requires you to do an init after changing the parameters. The SRM in may machines uses the NVRAM that hangs off the RTC to store some parameters. Check if your battery is dead. Regards Daniel Nilsson > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message