From owner-freebsd-hackers Sat Oct 12 17:24:38 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7013237B401 for ; Sat, 12 Oct 2002 17:24:37 -0700 (PDT) Received: from pepcross.com (pc-80-192-15-110-az.blueyonder.co.uk [80.192.15.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32F8143EA9 for ; Sat, 12 Oct 2002 17:24:36 -0700 (PDT) (envelope-from steve@pepcross.com) Received: (from steve@localhost) by pepcross.com (8.11.6/8.11.6) id g9D0OKE00957 for freebsd-hackers@freebsd.org; Sun, 13 Oct 2002 01:24:20 +0100 (BST) (envelope-from steve) Date: Sun, 13 Oct 2002 01:24:20 +0100 From: Stephen Roome To: freebsd-hackers@freebsd.org Subject: Strange: syscons SC_PIXEL_MODE and userconfig interactions Message-ID: <20021013012420.A931@dylan.home> Mail-Followup-To: Stephen Roome , freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG So far I think that this is the weirdest problem I've had with any FreeBSD box. I've just recompiled a kernel for this laptop (old Compaq Armada 1550) which is a P133 with 16Mb of RAM. (Stop laughing you at the back!) This is running 4.7-RELEASE. Anyway, it's a reasonably cut down kernel which was all working fine until I added options SC_PIXEL_MODE to the kernel. (This is because the 100x37 VESA_800x600 mode is nicer than 80x25) Now it hangs straight after finding sbc/pcm devices and right before where it would normally find the hard disk (ad0). The kernel IS NOT compiled with any userconfig stuff at all, however if I boot from either BTX with -c or the loader with boot -c then it boots up fine. I'm typing this in 100x37 mode on this very laptop after two sucessful boots through the -c madness. Without the -c it just hangs. I'd include an output for debugging but I can't get any easily (no spare serial leads). I can compile a kernel with the debugger and try and find out a little more about where it's hanging but there is someone about who has the faintest idea what is going on without me trying to boot a debugging kernel on this slightly ageing machine then that would be a better start. (ctrl-alt-escape does at least tell me that there is no debugger in the kernel, but I know it's not really getting much further because pccardd and perhaps init and whatnot are not starting up and a power-off doesn't result in anything telling me I'd not unmounted.. So I don't think it got that far.) (I almost posted this to -questions, so feel free to flame me for asking something that's prolly been round the lists before but which I didn't find.) Many thanks in advance, Steve Roome (not subscribed to the list so please CC me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message