From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 29810] New: Blank screen on nouveau module load
Date: Wed, 25 Aug 2010 23:23:12 -0700 (PDT) [thread overview]
Message-ID: <bug-29810-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=29810
Summary: Blank screen on nouveau module load
Product: xorg
Version: unspecified
Platform: PowerPC
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: doi-Y8qEzhMunLyT9ig0jae3mg@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=38169)
--> (https://bugs.freedesktop.org/attachment.cgi?id=38169)
lspci output
I have an old CRT eMac with an Nvidia GeForce2 MX card. I try to make it work
with the packaged debian nouveau modules. When the system loads the nouveau
kernel module the screen goes blank. I can log into the computer with ssh and
get the console back with unloading the nouveau module. The X display does not
start at all.
Is there a way to make it work?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-08-26 6:23 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 6:23 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-29810-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-08-26 6:24 ` [Bug 29810] Blank screen on nouveau module load bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-26 6:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-26 6:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-26 6:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-26 9:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-26 12:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-26 12:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-26 13:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-26 14:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-26 14:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-26 14:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-26 14:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-26 16:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-26 16:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-26 19:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-27 4:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-27 11:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-06 8:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-06 12:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-06 14:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-06 15:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-07 12:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-07 13:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-07 13:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-07 14:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-07 15:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-07 16:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-07 18:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-07 18:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-07 19:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-07 23:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-08 3:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-08 3:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-08 14:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-08 19:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-08 19:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-09 4:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-09 12:44 ` 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=bug-29810-8800@http.bugs.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.