From owner-freebsd-stable Sun Jul 25 19: 9:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from poboxer.pobox.com (ferg5200-1-41.cpinternet.com [208.149.16.41]) by hub.freebsd.org (Postfix) with ESMTP id CF5C214E35 for ; Sun, 25 Jul 1999 19:09:14 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id VAA02005; Sun, 25 Jul 1999 21:04:09 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 25 Jul 1999 21:04:07 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: yokota@zodiac.mech.utsunomiya-u.ac.jp Cc: stable@freebsd.org Subject: Re: Lost console References: <14235.26016.454033.194916@avalon.east> <199907260141.KAA05141@zodiac.mech.utsunomiya-u.ac.jp> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14235.49122.970966.568427@avalon.east> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Kazutaka YOKOTA on Mon, 26 July: : : >After upgrading from 3.2 CD to 3.2-STABLE, the console disappears : >when the kernel boots. How can I stop this behaviour? : : I think you should still be able to login to the system via network. : Send me /var/run/dmesg.out, /boot.config, /boot/loader.rc and your : kernel configuration file for examination. (Sorry. Insufficient clarity is ever the petty hobgoblin that haunts my email. Or is it otiose purple? I forget.) What I mean to describe is that, from the time /boot/loader beings a "boot" until "Login:", no console activity is visible. If it never gets that far -- c'est perdu. Attempting to "boot -s" results in no better results: No prompt ever appears. Sometimes I can ctl-alt-del my way back to the BIOS, in order to boot a different kernel, and sometimes I can't. I'm expecting that there is a config element required in order to avoid this behaviour. Inspection of GENERIC and LINT did not make it evident, however, and a bisection search on LINT would take an absurd amount of time, hence my query. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message