From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 2952513873B for ; Sat, 30 Dec 2017 00:23:48 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B24CEE0F00; Sat, 30 Dec 2017 00:23:41 +0000 (UTC) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 45B82E0E90 for ; Sat, 30 Dec 2017 00:23:41 +0000 (UTC) Received: by mail-wm0-x235.google.com with SMTP id b76so50330189wmg.1 for ; Fri, 29 Dec 2017 16:23:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=355ylSBPy+6ukyH/gG0IuJq1jJacBhU7lRGQ4ltXTZU=; b=Z5aRzkRVdfR9Hle1+CVyptYy7GvdrCka70D+DV5gDq2RE+N3kbrnxsY2w2PXIyfyLm ppkdZ9o4xiT5AoTGIolp87zqx/0Lxod/kLT8E1Zrgi2MlxKQJdj2vY15UUxhAnAsR2rq b9bgJ+jA9EJ3r8BG5mY9NHv9mL9V/wbxXWUnKCki3giZboeygoQKQ/a+IiQqr8ev9LOC KPTKSNSTtdYPhXCttyjxD9AqunWLgRGj6TAIMuk28LVTmrheVWocgC/XVOYsNeSi628I MQRFKP79kDtBa+IQLhlOqKrH1nICCmLrZfiNSP3sl0DPcdgRmPkKd+Uz3vxdAZ7Fh10w jrjA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=355ylSBPy+6ukyH/gG0IuJq1jJacBhU7lRGQ4ltXTZU=; b=qNscFPm3X5EdbIvtEHA9KwM8Fg2YOElGWapTFeSgi1ElJ2QgFtO2srafTPp3gWF4ze 0X2sk+TSs5BxinbSk1TcdvrCJjQydx3DEKK71PH52/kplBOv9TYd9odAPrVKUALvI3BV 8u1Ay8ScFSI4ypcRGyGFoNkssKudHUpTXJnI3JZlCgBH0JPjIezbBqyW5mWpHF0T0YB8 lpE/qReW7jkljztTM/sDxIcw/+PmaxpunqAovRwCISYnPB0sy521M9/tmSV90SvASEfx q/PP6tWXzjJrAtA7wK3Doh+u/TCEIrrxi9/2WoYWi83qANlL7gbQ6oh/QnHtzVOZp/zK BJsQ== X-Gm-Message-State: AKGB3mKygj4lCZPVx+Lt43yYgZbmTfmSBl6oewkPNyCduSfRcl0JfKe6 a4hfl+y7D+0hpNPB7iC/9vAtqJC1 X-Google-Smtp-Source: ACJfBotDEG6B+9xHeyuXi7fUGs9Hs8nIp015BXtOChPiqBHtW/P0e2zgVlE9Tfk3xn2MBfWTLo+ZIQ== X-Received: by 10.28.216.212 with SMTP id p203mr30696864wmg.50.1514593419626; Fri, 29 Dec 2017 16:23:39 -0800 (PST) Received: from [172.20.0.40] ([197.101.48.133]) by smtp.googlemail.com with ESMTPSA id m52sm39997130wrm.12.2017.12.29.16.23.38 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 Dec 2017 16:23:38 -0800 (PST) Subject: Re: [gentoo-user] Kernel 4.14.7 no longer switches to VT7 To: gentoo-user@lists.gentoo.org References: From: Alan McKinnon Message-ID: <7fd008d4-40a3-8f22-2ca2-841a9a11d1dc@gmail.com> Date: Sat, 30 Dec 2017 02:18:12 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 8bit X-Archives-Salt: b5b6d141-5602-48a0-9767-271d86851cd5 X-Archives-Hash: 4a96d92f14361ec1cf20ee6710d4e655 On 21/12/2017 17:41, Jörg Schaible wrote: > Hi, > > after the update and installation of gentoo-sources-4.14.7 my two machines no longer switch to SDDM on > VT7, it stays on VT1. However, I can switch manually using CTRL-ALT-7 to SDDM and login as usual. If I boot > with the last stable kernel 4.12.12 anything is back to normal and the login screen of SDDM appears directly > while the rest of the modules is loaded in background. > > Both machines have older Radeon chips (REDWOOD and CEDAR) and I managed to load also their firmware > with the new kernel 4.14.7, but there's still no automatic switch to VT7 anymore. > > I found nothing obvious in /var/log/messages, dmesg or Xorg.0.log. What may cause this weird behavior? > > Cheers, > Jörg > > It's probably a dodgy kernel point bersion, 4.14 is problematic. Alice Ferrazzi posted this to gentoo-dev earlier today: =====start quote===== Hello, We have recently started the stabilization of gentoo-sources-4.14.8. Very soon we received reports regarding broken e1000e driver [1] and moved to gentoo-sources-4.14.8-r1. Since then we keep receiving new problems related to 4.14.x kernel: - IPSec is broken [2] - Change in 4.14.9 broke nVIDIA driver [3] - Colors on console are broken with some Radeon HD cards [4] - BUG report on boot [5] - Unbootable system with CONFIG_MCORE2 [6] - ...more bugs [7] While not all issues are present in gentoo-sources-4.14.8-r1 we are concerned about the current stability/quality of the 4.14.x branch in general and don't feel comfortable recommending 4.14.x branch for general use at the moment. But that's what a stable USE flag means for most Gentoo users. So, for now, we have decided to drop gentoo-sources-4.14.x stable keywords. We will keep watching 4.14 branch and once the stability/quality matches our requirements we will restart stabilization. Keep in mind: We are only dropping stable USE flags. If gentoo-sources-4.14.x works for you and you want to keep it, just keyword the package on your own! ===== end quote===== If you want to fix the bugs, then by all means soldier on. But if your intent is to have a working system that boots, probably drop using 4.14.x and go back to say 4.12.x ? -- Alan McKinnon alan.mckinnon@gmail.com