From owner-freebsd-current Thu Sep 28 11:37:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailhotel.chrillesen.dk (vax.chrillesen.dk [193.88.12.35]) by hub.freebsd.org (Postfix) with ESMTP id 4266437B43E for ; Thu, 28 Sep 2000 11:37:26 -0700 (PDT) Received: by mailhotel.chrillesen.dk (Postfix, from userid 1009) id D53DC5D08; Thu, 28 Sep 2000 20:37:22 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mailhotel.chrillesen.dk (Postfix) with ESMTP id C683F1F20 for ; Thu, 28 Sep 2000 20:37:22 +0200 (CEST) Date: Thu, 28 Sep 2000 20:37:22 +0200 (CEST) From: Anonymous Coward X-Sender: barry@vax.chrillesen.dk Reply-To: freebsd-haX0rs@netscum.dk To: current@freebsd.org Subject: No kezboard with any -current snap floppies... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy. I tried booting from a pair of kern/mfsroot floppies downloaded from current.freebsd.org, and no go. the kbd attach fails with 6. This also happens with grabbing the most current pair of floppies from today, as well as the beginning of Aug floppies, so this seems to be b0rken for quite some time, spanning the range of available snaps. This is on an HP NetSwerver LPr, and I had no problems with a pair of NetBSD floppies on the same hardware. Anyone else sees this, or do I need to copy down some info before the boot dmesg disappears? Be happy to do this if nobody sees the same thing. Otherwise, I'll probably try some different hardware just to get something happening... thanks barry bouwsma, all-purpose nobody (reply-to is valid) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message