From owner-freebsd-current Mon Oct 23 08:27:06 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA10110 for current-outgoing; Mon, 23 Oct 1995 08:27:06 -0700 Received: from kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA10100 for ; Mon, 23 Oct 1995 08:27:01 -0700 Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by kitten.mcs.com (8.6.10/8.6.9) with SMTP id KAA01687; Mon, 23 Oct 1995 10:26:50 -0500 Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Mon, 23 Oct 95 10:26 CDT Received: by mercury.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Mon, 23 Oct 95 10:26 CDT Message-Id: Subject: Re: ordering of isa_devtab_tty important? To: bde@zeta.org.au (Bruce Evans) Date: Mon, 23 Oct 1995 10:26:49 -0500 (CDT) From: "Lars Fredriksen" Cc: current@freebsd.org In-Reply-To: <199510220748.RAA26210@godzilla.zeta.org.au> from "Bruce Evans" at Oct 22, 95 05:48:44 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2023 Sender: owner-current@freebsd.org Precedence: bulk Bruce Evans writes: > [stuff deleted] > The support for syscons and pcvt in the same kernel broke it :(. > find_display() in isa.c requires display devices to be before serial > devices, not to mention before devices in isa_devtab_tty that aren't > really ttys. It could abuse the `sensitive_hw' flag to select the > display devices. Display devices aren't sensitive, but the sensitive_hw > flag is set for them so that they get probed early so that they don't > appear to be used before they are detected. So we need to fix config so that we can tell it what devices are able to serve as a console, and to make it put the real console devices in front of the serial ports in the table, and the other, non colsole able, at the end of the table.. I think we might be asking for trouble having config put together the list based upon the order it occurs in the file. Maybe we should have another flag to indicate the relative ordering among console devices(or any other devices for that matter). > > >Just for your information. The symptom of my non-booting kernel was that > >as soon as the cart-wheel stopped spinning, my modem lights would indicate > >TX/RX, my floppy would start to twirl and the hard drives would be accessed > >a couple of times. Some time the screen would go black and the come back > >as it normally does, however you never saw the version[] getting printed > >nor any of the device probe messages. > > This happens because sio0 becomes the console. You should get a login > prompt if the boot succeeds and you wait a little longer. Hm, even if the second device in the table is sc0? I guess I would expect the code just to walk down the table until it finds a console it can talk to rather than using sio0 if the first one failed(this does make it more predictable though :-)). > > Bruce > Lars -- ------------------------------------------------------------------- Lars Fredriksen fredriks@mcs.com (home) lars@fredriks.pr.mcs.net (home-home) fredriks@asiago.cs.wisc.edu