All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>, Lyude Paul <lyude@redhat.com>
Cc: linux-fbdev@vger.kernel.org, "Kees Cook" <keescook@chromium.org>,
	"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
	"Jan H. Schönherr" <jschoenh@amazon.de>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	"Bjorn Helgaas" <bhelgaas@google.com>
Subject: Re: [PATCH] video/console/vgacon: Print big fat warning with nomodeset
Date: Tue, 03 Jul 2018 11:57:08 +0000	[thread overview]
Message-ID: <87a7r8r0q3.fsf@intel.com> (raw)
In-Reply-To: <20180703073452.GD7880@phenom.ffwll.local>

On Tue, 03 Jul 2018, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Mon, Jul 02, 2018 at 05:04:40PM -0400, Lyude Paul wrote:
>> 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 <lyude@redhat.com>
>
> Yeah makes tons of sense. I think we should also perhaps mark the option
> as a tainting one, but I think that's only wired up for module option.

You could do that by adding

	add_taint(TAINT_USER, LOCKDEP_STILL_OK);

in text_mode(). If you do that, you should probably amend the warning
message accordingly.

Either way,

Acked-by: Jani Nikula <jani.nikula@intel.com>

> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
>> ---
>>  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
>> 
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Jani Nikula, Intel Open Source Graphics Center

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>, Lyude Paul <lyude@redhat.com>
Cc: linux-fbdev@vger.kernel.org, "Kees Cook" <keescook@chromium.org>,
	"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
	"Jan H. Schönherr" <jschoenh@amazon.de>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	"Bjorn Helgaas" <bhelgaas@google.com>
Subject: Re: [PATCH] video/console/vgacon: Print big fat warning with nomodeset
Date: Tue, 03 Jul 2018 14:57:08 +0300	[thread overview]
Message-ID: <87a7r8r0q3.fsf@intel.com> (raw)
In-Reply-To: <20180703073452.GD7880@phenom.ffwll.local>

On Tue, 03 Jul 2018, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Mon, Jul 02, 2018 at 05:04:40PM -0400, Lyude Paul wrote:
>> 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 <lyude@redhat.com>
>
> Yeah makes tons of sense. I think we should also perhaps mark the option
> as a tainting one, but I think that's only wired up for module option.

You could do that by adding

	add_taint(TAINT_USER, LOCKDEP_STILL_OK);

in text_mode(). If you do that, you should probably amend the warning
message accordingly.

Either way,

Acked-by: Jani Nikula <jani.nikula@intel.com>

> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
>> ---
>>  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
>> 
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>, Lyude Paul <lyude@redhat.com>
Cc: linux-fbdev@vger.kernel.org, "Kees Cook" <keescook@chromium.org>,
	"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
	"Jan H. Schönherr" <jschoenh@amazon.de>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	"Bjorn Helgaas" <bhelgaas@google.com>
Subject: Re: [PATCH] video/console/vgacon: Print big fat warning with nomodeset
Date: Tue, 03 Jul 2018 14:57:08 +0300	[thread overview]
Message-ID: <87a7r8r0q3.fsf@intel.com> (raw)
In-Reply-To: <20180703073452.GD7880@phenom.ffwll.local>

On Tue, 03 Jul 2018, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Mon, Jul 02, 2018 at 05:04:40PM -0400, Lyude Paul wrote:
>> 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 <lyude@redhat.com>
>
> Yeah makes tons of sense. I think we should also perhaps mark the option
> as a tainting one, but I think that's only wired up for module option.

You could do that by adding

	add_taint(TAINT_USER, LOCKDEP_STILL_OK);

in text_mode(). If you do that, you should probably amend the warning
message accordingly.

Either way,

Acked-by: Jani Nikula <jani.nikula@intel.com>

> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
>> ---
>>  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
>> 
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2018-07-03 11:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180702210516epcas3p151aefd4a0217c4cd30143147f0bafe1d@epcas3p1.samsung.com>
2018-07-02 21:04 ` [PATCH] video/console/vgacon: Print big fat warning with nomodeset Lyude Paul
2018-07-02 21:04   ` Lyude Paul
2018-07-03  7:34   ` Daniel Vetter
2018-07-03  7:34     ` Daniel Vetter
2018-07-03  7:34     ` Daniel Vetter
2018-07-03 11:57     ` Jani Nikula [this message]
2018-07-03 11:57       ` Jani Nikula
2018-07-03 11:57       ` Jani Nikula
2018-07-24 15:24   ` Bartlomiej Zolnierkiewicz
2018-07-24 15:24     ` Bartlomiej Zolnierkiewicz
2018-07-24 15:24     ` Bartlomiej Zolnierkiewicz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a7r8r0q3.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=bhelgaas@google.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jschoenh@amazon.de \
    --cc=keescook@chromium.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lyude@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.