From owner-freebsd-hackers Mon Apr 10 10:49:01 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA13342 for hackers-outgoing; Mon, 10 Apr 1995 10:49:01 -0700 Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA13333 for ; Mon, 10 Apr 1995 10:48:48 -0700 Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.11/8.6.6) id TAA20024 for hackers@FreeBSD.ORG; Mon, 10 Apr 1995 19:50:38 +0200 From: John Hay Message-Id: <199504101750.TAA20024@zibbi.mikom.csir.co.za> Subject: syscons panic without a screen To: hackers@FreeBSD.org (FreeBSD-hackers) Date: Mon, 10 Apr 1995 19:50:38 +0200 (SAT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 661 Sender: hackers-owner@FreeBSD.org Precedence: bulk Hi, I build a new kernel for one of my machines that don't have a screen or keyboard this weekend. It panic during scattach inside one of the bcopy's. This didn't happen with a kernel build about six weeks ago. I don't build kernels for that machine very often so I only picked it up this weekend. What I actualy want to know is, shouldn't the scprobe routine determine if there is a screen? At the moment the probe will never fail. It will print a message if it has problems with the keyboard, but even then it will not fail. At the moment for a workaround I just fail the scprobe routine if the keyboard probe fails. -- John Hay -- jhay@mikom.csir.co.za