From owner-freebsd-questions@FreeBSD.ORG Thu Oct 16 16:12:35 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2CBEAB72 for ; Thu, 16 Oct 2014 16:12:35 +0000 (UTC) Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B6B31B91 for ; Thu, 16 Oct 2014 16:12:33 +0000 (UTC) Received: by mail-wi0-f175.google.com with SMTP id d1so1955877wiv.14 for ; Thu, 16 Oct 2014 09:12:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:mime-version:content-type:content-disposition :user-agent; bh=0AKEiyxZnOugQThObIMktuozP76n7P8UFI27zymsgEA=; b=mpkQd9fHxmf7x9WJbUpwRSG1+0xoZ2eoyxqI2Oj9bafdohe7oeY2KBoDJBUwVVfHYj BQgV5Zh/agvyPumhJxyMElAzDPbZdbCX15u0A33L7Omr34inOzNXUBxUbJyeKksbW8ib fgrpHQMAwytKh5fn87c0JsujouWEBfcbRu+V4nYXOy1i8Iu8edNrmhlYWVVNTg/amnE5 17JDCdlh1lAiCGDONbpSL8BwA7RjNq7R4LzsC8gM6nl9exVF29e2eXL0EaVgTVwMlQ/p 9j+bo1Rr7l4fnPsKqtv5yyGoV1WrL+JcWq1IJPSJlbjXNyu6LxWdovyccxqzFLTEdo94 lhxg== X-Gm-Message-State: ALoCoQnxH9j0Iq27Bh71PX/beONen1+3dW53teow5jEqjbCroEDnYJsm5dFmHBJrXsKIKb9NK1i4 X-Received: by 10.180.20.43 with SMTP id k11mr7433224wie.28.1413475952062; Thu, 16 Oct 2014 09:12:32 -0700 (PDT) Received: from localhost (itcom245.staff.itd.umich.edu. [141.213.135.249]) by mx.google.com with ESMTPSA id ny6sm2483374wic.22.2014.10.16.09.12.30 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Oct 2014 09:12:31 -0700 (PDT) Date: Thu, 16 Oct 2014 12:09:54 -0400 From: William Bulley To: Lowell Gilbert Subject: Re: exiting Xorg locks up 9.2-STABLE system Message-ID: <20141016160954.GD3631@itcom245.staff.itd.umich.edu> Mail-Followup-To: Lowell Gilbert , freebsd-questions@freebsd.org, Warren Block MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2014 16:12:35 -0000 According to Lowell Gilbert on Thu, 10/16/14 at 11:22: > > Me too (since 1.1.5.1), but I expect to solve my own problems with my > kernel configuration. Then you must be at least 35 years old! ;^) I hear you, but this wasn't a kernel issue at the outset. It was a failure of x11/Xorg to cleanly exit to the ASCII console (vty) as has been the case going back to at least 6.x IIRC. :-) Something had changed -- I knew about the WITH_NEW_XORG flag, and the GENERIC kernel comes with sc(4) as it has for some time now. My kernel also contained the sc(4) device as it was based on the (watered down) GENERIC kernel config file (MYKERNEL). Warren's suggestion to use vt(4) resulted in the hang behaviour that I alluded to earlier -- no output at the "Booting ..." message. So I was forced to fall back to the original kernel which is where things stand now until I can get back in front of this system to try the suggestion of adding the vt(4) device to the 9.3-STABLE GENERIC kernel config file and trying again. Wish me luck! :-) BTW, I did solve my own problems when adding the vt(4) device to my kernel config file -- I listed the additions and deletions in an earlier reply. Until I try again with the above GENERIC mod, I will have to assume it was my problem with my kernel config... Regards, web... -- /"\ ASCII RIBBON / William Bulley \ / CAMPAIGN AGAINST / X HTML E-MAIL AND / E-MAIL: web@umich.edu / \ LISTSERV POSTINGS / 72 characters width template ----------------------------------------->|