From owner-freebsd-current Sun Sep 2 19:53: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 284ED37B401 for ; Sun, 2 Sep 2001 19:53:00 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.5/8.11.5) with SMTP id f832bUP36601 for ; Sun, 2 Sep 2001 22:37:31 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 2 Sep 2001 22:37:30 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: freebsd-current@FreeBSD.org Subject: Recent -current breaks console probing on dell notebook? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Until yesterday, I was running -CURRENT from around July 4th on my notebook, given that I was travelling and unwilling to break my means of giving presentations on my trip :-). Yesterday, I decided to upgrade, and built kernel/world. The userland stuff appears to work fine, but interestingly, my kernel seems not to probe the console, and instead, use the serial console. The boot loader does not have this problem, and sees the console fine. The symptoms are that as the kernel loads (spin spin) after the boot loader, it ceases spinning, the cursor changes to a block, and after a delay for hardware probes (&tc), the login prompt comes up but without the ability to type. Unfortunately, I don't have a box with me I can use as a serial console, so I can't attempt to see what it did or didn't probe successfully, just that things got that far. When I get home tomorrow, I'll attempt to debug it, but was wondering if anyone else had experienced this, or could point me at any commits that might potentially impact this. Thanks, Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message