From: Marcin Slusarz <marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ben Skeggs <skeggsb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] drm/nouveau: printk info about disabled modesetting
Date: Mon, 2 May 2011 18:39:15 +0200 [thread overview]
Message-ID: <20110502163915.GA3019@joi.lan> (raw)
In-Reply-To: <1304319078.23168.1.camel@nisroch>
On Mon, May 02, 2011 at 04:51:14PM +1000, Ben Skeggs wrote:
> On Mon, 2011-05-02 at 00:03 +0200, Marcin Slusarz wrote:
> > On Mon, Apr 04, 2011 at 07:27:35PM +0200, Marcin Slusarz wrote:
> > > ... to make it obvious why nouveau refused to drive the hardware.
> > >
> > > Signed-off-by: Marcin Slusarz <marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > > ---
> > > drivers/gpu/drm/nouveau/nouveau_drv.c | 4 +++-
> > > 1 files changed, 3 insertions(+), 1 deletions(-)
> > >
> > > diff --git a/drivers/gpu/drm/nouveau/nouveau_drv.c b/drivers/gpu/drm/nouveau/nouveau_drv.c
> > > index f658a04..515c656 100644
> > > --- a/drivers/gpu/drm/nouveau/nouveau_drv.c
> > > +++ b/drivers/gpu/drm/nouveau/nouveau_drv.c
> > > @@ -445,8 +445,10 @@ static int __init nouveau_init(void)
> > > nouveau_modeset = 1;
> > > }
> > >
> > > - if (!nouveau_modeset)
> > > + if (!nouveau_modeset) {
> > > + printk(KERN_INFO "nouveau: modesetting disabled by kernel parameter\n");
> > > return 0;
> > > + }
> > >
> > > nouveau_register_dsm_handler();
> > > return drm_init(&driver);
> > > --
> >
> > ping
> I just wonder how this is useful. I don't find it hard when looking at
> people's logs to scroll to the top and look at the kernel commandline.
It's not all about kernel commandline (but it's still nice to have it).
You can pass modeset=0 by modprobe.conf and there's no way to read it from
dmesg later.
It just simplifies troubleshooting by taking one of the most frequent reasons
of "nouveau does not detect my card"...
> Really, that should be done *anyway* as there are many more options that
> are relevant to what nouveau does/does not do as well...
Yes. But no other parameter silently disables whole module.
Marcin
next prev parent reply other threads:[~2011-05-02 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 17:27 [PATCH] drm/nouveau: printk info about disabled modesetting Marcin Slusarz
[not found] ` <20110404172735.GA8979-OI9uyE9O0yo@public.gmane.org>
2011-05-01 22:03 ` Marcin Slusarz
[not found] ` <20110501220341.GI6742-OI9uyE9O0yo@public.gmane.org>
2011-05-02 6:51 ` Ben Skeggs
2011-05-02 16:39 ` Marcin Slusarz [this message]
2011-05-02 16:42 ` Pekka Paalanen
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=20110502163915.GA3019@joi.lan \
--to=marcin.slusarz-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=skeggsb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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.