From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 16792] modesetting on NV86: cannot allocate framebuffer
Date: Wed, 18 Mar 2009 15:50:41 -0700 (PDT) [thread overview]
Message-ID: <20090318225042.0FADE130016@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-16792-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
http://bugs.freedesktop.org/show_bug.cgi?id=16792
Hervé Cauwelier <debian@oursours.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|modesetting on NV86: text |modesetting on NV86: cannot
|mode goes blank, machine |allocate framebuffer
|freeze on gdm stop |
--- Comment #9 from Hervé Cauwelier <debian@oursours.net> 2009-03-18 15:50:41 PST ---
I installed nouveau master, drm modesetting-gem and rebooted.
I modprobed drm, then nouveau with "modeset=1", the screen went black, like
when X start, then the console came back but at panel native resolution.
I then started GDM but X gave the error I attach.
I then tried to remove the nouveau module but it said it was busy, though
"lsmod" told no other module was using it.
I forgot to save "dmesg" before reboot. It contained many information about the
DRM. Do you need it?
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2009-03-18 22:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 14:20 [Bug 16792] New: modesetting on NV86: text mode goes blank, machine freeze on gdm stop bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-16792-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-07-21 14:26 ` [Bug 16792] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-07-21 14:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-07-21 18:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-07-21 19:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-07-27 20:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-13 0:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-13 11:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-13 22:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-18 22:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2009-03-18 22:53 ` [Bug 16792] modesetting on NV86: cannot allocate framebuffer bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-19 5:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-19 9:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-19 9:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-13 3:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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=20090318225042.0FADE130016@annarchy.freedesktop.org \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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.