Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp418684imm; Mon, 2 Jul 2018 14:07:30 -0700 (PDT) X-Google-Smtp-Source: AAOMgpdBd3nyMlC1A+i4Nn+Ue0V3EgV8TfobqFm3Buyo8UeZ8VErIv8uyUjYZxz+7/elmVbWNrHx X-Received: by 2002:aa7:83d1:: with SMTP id j17-v6mr27182618pfn.236.1530565650886; Mon, 02 Jul 2018 14:07:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530565650; cv=none; d=google.com; s=arc-20160816; b=A0+hRzVbJgA6Vydpl0UTh+OA3c2ADxUXLOiW95jCCUod17bYMjdae7x1GeAmBZvM91 ZMKVyW498lBo5CDKPghhQkFaSal25W1fkwlfONhlEv13j9I+N+hHPSc2cu9HnxcLUMLF UiOIaxJXzwzpZFZuSHo2KExS+SfBUQjyT1DshYr1LibSiZMFAhShldQ6/SQsNkWOtBW0 n5KFWo9pK021/EIVJ4Yop1/jO2dylH8i4v6jalYC2viKP/754uLJWcxM4G7pYAuf0aYz mHw4nuz9IxF3jESulqnCj6ABKsrWQgyGL+54sNYGwhqL7XVjfpJftJlMWWzv8+vG4Dd6 Ia0A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from :arc-authentication-results; bh=Q3fWDeLmQ40baTWe830Rg/HkZiLX1U2ys1YvFWcO/6c=; b=Gr1FrFIW3+PmDVYUKspf9GllxLoNlTMhJxgZb+0j+g09m8FZi9TiENgCQ9c2YWnmh0 gPWPniGA9ROF4/DN8JblicXkNswzz0gzPJWPXzOCJSGdx7kpRjmo8i6SnzQPugjnmI/w F9o0slfjZfLiLUCKWk7fx9WMk6+R8N1uS3mEmtDQVhDF3k9iHA3hUE0H99ENj+clkURH 6f6IyTdB6EAI9iP/QtDU5/Nz4qKROCFMWMarZvq7HAwMpSV6NIC5ex4ycNLJtg5MVFRZ wlgbvqD8EOTiCgnHOLAAqIDNa+xKC48rtxzNNGm9WwdjEiD/y4BM8MHI+xXQsyG2qD5J Wtqg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e85-v6si6408676pfl.132.2018.07.02.14.07.16; Mon, 02 Jul 2018 14:07:30 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752927AbeGBVFO (ORCPT + 99 others); Mon, 2 Jul 2018 17:05:14 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:60848 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752391AbeGBVFN (ORCPT ); Mon, 2 Jul 2018 17:05:13 -0400 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id DFEA281A4EB9; Mon, 2 Jul 2018 21:05:12 +0000 (UTC) Received: from malachite.bss.redhat.com (dhcp-10-20-1-11.bss.redhat.com [10.20.1.11]) by smtp.corp.redhat.com (Postfix) with ESMTP id 567C12026D5B; Mon, 2 Jul 2018 21:05:11 +0000 (UTC) From: Lyude Paul To: dri-devel@lists.freedesktop.org Cc: Bartlomiej Zolnierkiewicz , Kees Cook , =?UTF-8?q?Jan=20H=2E=20Sch=C3=B6nherr?= , Bjorn Helgaas , linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH] video/console/vgacon: Print big fat warning with nomodeset Date: Mon, 2 Jul 2018 17:04:40 -0400 Message-Id: <20180702210442.18648-1-lyude@redhat.com> X-Scanned-By: MIMEDefang 2.78 on 10.11.54.4 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.8]); Mon, 02 Jul 2018 21:05:12 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.8]); Mon, 02 Jul 2018 21:05:12 +0000 (UTC) for IP:'10.11.54.4' DOMAIN:'int-mx04.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'lyude@redhat.com' RCPT:'' Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org It's been a pretty good while since kernel modesetting was introduced. It has almost entirely replaced previous solutions which required userspace modesetting, and I can't even recall any drivers off the top of my head for modern day hardware that don't only support one or the other. Even nvidia's ugly blob does not require the use of nomodeset, and only requires that nouveau be blacklisted. Effectively, the only thing nomodeset does in the year 2018 is disable your graphics drivers. Since VESA is a thing, this will give many users the false impression that they've actually fixed an issue they were having with their machine simply because the laptop will boot up to a degraded GUI. This of course, is never actually the case. Things get even worse when you consider that there's still an enormous amount of tutorials users find on the internet that still suggest adding nomodeset, along with various users who have been around long enough to still suggest it. There really isn't any legitimate reason I can see for this to be an option that's used by anyone else other then developers, or properly informed users. So, let's end the confusion and start printing warnings whenever it's enabled. Signed-off-by: Lyude Paul --- drivers/video/console/vgacon.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/drivers/video/console/vgacon.c b/drivers/video/console/vgacon.c index f09e17b60e45..09731b2f6815 100644 --- a/drivers/video/console/vgacon.c +++ b/drivers/video/console/vgacon.c @@ -112,6 +112,11 @@ EXPORT_SYMBOL(vgacon_text_force); static int __init text_mode(char *str) { vgacon_text_mode_force = true; + + pr_warning("You have booted with nomodeset. This means your GPU drivers are DISABLED\n"); + pr_warning("Any video related functionality will be severely degraded, and you may not even be able to suspend the system properly\n"); + pr_warning("Unless you actually understand what nomodeset does, you should reboot without enabling it\n"); + return 1; } -- 2.17.1