Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 Jan 1997 22:40:02 -0800 (PST)
From:      uhclem@nemesis.lonestar.org (Frank Durda IV)
To:        freebsd-bugs
Subject:   Re: conf/2426: At end of install, panic: Going nowhere without init - FDIV050 
Message-ID:  <199701160640.WAA05879@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR conf/2426; it has been noted by GNATS.

From: uhclem@nemesis.lonestar.org (Frank Durda IV)
To: jkh@time.cdrom.com, FreeBSD-gnats-submit@freebsd.org
Cc: uhclem@nemesis.lonestar.org
Subject: Re: conf/2426: At end of install, panic: Going nowhere without init - FDIV050 
Date: Thu, 16 Jan 97 00:29 CST

 uhclem wrote in conf/2426:
 [0]	Information Dialog
 [0]	Saving any boot -c changes to new kernel...
 [0]	panic: Going nowhere without init!
 
 jkh writes:
 [1]This may have been due to an error in the SaveUserconfig() code which
 [1]somehow gets confused by certain SCSI configurations.  Since we don't
 [1]save that information here anyway, this was recently disabled in
 [1]sysconfig.  Can you try the 3.0-970114-SNAP floppies/newer/boot.flp
 [1]image and see if this still occurs?  Thanks!
 
 FYI, systems I ran into the problem on did not have any SCSI adapters or
 devices.
 
 However, I tried both the floppies/boot.flp and the floppies/newer/boot.flp
 from the 3.0 SNAP.
 
 FYI, floppies/boot.flp failed attempting to FTP the file "bin/bin.tgz",
 but in changing to a different FTP site for a retry, the "going nowhere"
 panic message occurred after selecting FTP Passive in error and then
 selecting Cancel in the next menu, so the bug still exists in some
 form here.  
 
 The newer/floppies/boot.flp successfully installed the minimal 
 2.2-BETA tree (via a symlinked to 3.0-970114-SNAP on the local FTP
 system), without producing this particular error message.  The
 system was configured back with the SMC 8013 network adapter for
 this test.  I'll try doing the developer distribution install of
 2.2-BETA next.
 
 Despite the fix mentioned being targeted at SCSI issues, it seems to
 correct the problem on non-SCSI platforms as well.  But this makes me
 think the true cause of the problem is not well-understood at this
 time.
 
 Thanks!
 
 Frank Durda IV <uhclem@nemesis.lonestar.org>|"The Knights who say "LETNi"
 or uhclem%nemesis@rwsystr.nkn.net           | demand...  A SEGMENT REGISTER!!!"
 					    |"A what?"
 or ...letni!rwsys!nemesis!uhclem	    |"LETNi! LETNi! LETNi!"  - 1983
 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701160640.WAA05879>