From nobody@FreeBSD.ORG Tue Mar 16 12:38:40 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 8D6EC151A8; Tue, 16 Mar 1999 12:38:40 -0800 (PST)
Message-Id: <19990316203840.8D6EC151A8@hub.freebsd.org>
Date: Tue, 16 Mar 1999 12:38:40 -0800 (PST)
From: cfr@pobox.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: RTC BIOS diagnostic error on install
X-Send-Pr-Version: www-1.0

>Number:         10626
>Category:       i386
>Synopsis:       RTC BIOS diagnostic error on install
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Mar 16 12:40:00 PST 1999
>Closed-Date:    Mon Mar 12 18:48:15 PST 2001
>Last-Modified:  Tue Mar 13 01:00:01 PST 2001
>Originator:     Charles F. Randall
>Release:        3.1R
>Organization:
>Environment:
>Description:
When trying to install FreeBSD R3.1 from I get the following
message after loading the kern and mfs root floppies.

RTC BIOS diagnostic error ff<clock_battery,ROM_cksum,config_unit,
memory_size,fixed_disk,invalid_time>
changing root device to fd0c
rootfs is 2880 Kbyte compiled in MFS

At that point the installation hangs.

This machine ran 2.2.8 without problem. I just booted with an
R2.2.8 boot floopy and got the /stand/sysinstall main menu
without problem.

Suggestions?

>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:

From: cfr@pobox.com
To: freebsd-gnats-submit@freebsd.org
Cc:  
Subject: i386/10626: RTC BIOS diagnostic error on install
Date: Tue, 16 Mar 1999 12:38:40 -0800 (PST)

 >Number:         10626
 >Category:       i386
 >Synopsis:       RTC BIOS diagnostic error on install
 >Confidential:   no
 >Severity:       serious
 >Priority:       high
 >Responsible:    freebsd-bugs
 >State:          open
 >Quarter:        
 >Keywords:       
 >Date-Required:
 >Class:          sw-bug
 >Submitter-Id:   current-users
 >Arrival-Date:   Tue Mar 16 12:40:00 PST 1999
 >Closed-Date:
 >Last-Modified:
 >Originator:     Charles F. Randall
 >Release:        3.1R
 >Organization:
 >Environment:
 >Description:
 When trying to install FreeBSD R3.1 from I get the following
 message after loading the kern and mfs root floppies.
 
 RTC BIOS diagnostic error ff<clock_battery,ROM_cksum,config_unit,
 memory_size,fixed_disk,invalid_time>
 changing root device to fd0c
 rootfs is 2880 Kbyte compiled in MFS
 
 At that point the installation hangs.
 
 This machine ran 2.2.8 without problem. I just booted with an
 R2.2.8 boot floopy and got the /stand/sysinstall main menu
 without problem.
 
 Suggestions?
 
 >How-To-Repeat:
 
 >Fix:
 
 
 >Release-Note:
 >Audit-Trail:
 >Unformatted:
 
 
 To Unsubscribe: send mail to majordomo@FreeBSD.org
 with "unsubscribe freebsd-bugs" in the body of the message
 
 
 
 

From: Charles Randall <crandall@matchlogic.com>
To: freebsd-gnats-submit@freebsd.org
Cc: cfr@pobox.com, freebsd-doc@freebsd.org, faq@freebsd.org
Subject: Re: i386/10626: RTC BIOS diagnostic error on install
Date: Thu, 18 Mar 1999 14:49:49 -0700

 I was finally able to boot the install disks from floppy and proceed with
 the installation by disabling the parallel port controller ppc0 in the
 visual kernel configuration.
 
 I tried disabling all other unused devices except ppc0 (keeping only fdc0,
 wdc0, wdc1, ppc0, atkbd0, and sc0 -- I also have the PCI-based fxp0 but you
 can't disable that without removing the card) and the problem still existed
 (even though the visual kernel configuration stated there were no
 conflicts). When I disabled ppc0 it worked. I'm able to boot the system by
 disabling _only_ ppc0.
 
 After installing, I need to disable ppc0 automatically otherwise the boot
 would hang with the same error as originally described (except it changed to
 the boot disk instead of fd0).
 
 To automatically disable ppc0, I did the following (mostly just documenting
 this in case someone else runs into the same problem):
 
 1. At the boot prompt, enter "boot -c".
 
 2. At the "config>" prompt, enter "visual" to enter the visual kernel
 configuration editor.
 
 3. Disable ppc0.
 
 4. Once the system has booted, log in as root.
 
 5. Verify that /kernel.config contains the following lines,
 
      di ppc0
      q
 
 
 6. Move /kernel.config to /boot/kernel.conf
 
      % mv /kernel.config /boot/kernel.conf
 
 7. Create /boot/loader.rc and add the following lines verbatim.
 
      load /kernel
      load -t userconfig_script /boot/kernel.conf
      autoboot
 
 8. Then reboot.
 
 I still don't know that the original problem was (and now I can't use the
 parallel port). Can this information be added to the FAQ, handbook, or
 ERRATA.TXT file? 
 
 Steps 6 and 7 are in the ERRATA.TXT file on the FTP site, but there's no
 mention of a problem with ppc0.
 
 Is there some known problem with ppc0? I can't seem to find a hardware
 conflict.
 
 Charles
 
 
State-Changed-From-To: open->feedback 
State-Changed-By: nbm 
State-Changed-When: Sat Aug 5 14:33:45 PDT 2000 
State-Changed-Why:  
Are you able to tell us if this behaviour continued in later releases? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=10626 
State-Changed-From-To: feedback->closed 
State-Changed-By: des 
State-Changed-When: Mon Mar 12 18:48:15 PST 2001 
State-Changed-Why:  
Feedback timeout. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=10626 

From: Charles Randall <crandall@matchlogic.com>
To: "'freebsd-gnats-submit@FreeBSD.org'" <freebsd-gnats-submit@FreeBSD.org>
Cc:  
Subject: Re: i386/10626: RTC BIOS diagnostic error on install
Date: Tue, 13 Mar 2001 01:58:09 -0700

 I've lost track of which machine I had this problem on. However, I'd guess
 that this was resolved in subsequent releases because I haven't seen a
 similar problem since then.
 
 -Charles
>Unformatted:
