From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 36163] nouveau fails to render framebuffer on [GeForce 7300 GS]
Date: Sat, 16 Apr 2011 06:42:46 -0700 (PDT) [thread overview]
Message-ID: <20110416134246.2F63E13000C@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-36163-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=36163
--- Comment #3 from SanskritFritz <semmikozod-hRtevi7K+EU+Va1GwOuvDg@public.gmane.org> 2011-04-16 06:42:43 PDT ---
> Can you please attach both full kernel and X logs (as plain text).
> If for some reason you feel that some information is too sensitive to be
> shared, please remove it. Try to keep the logs as complete as possible
> as they might have some relevant information.
X logs have nothing to do with framebuffer, so I ignored that. Attached
kernel.log.
> Does the liveCD (guessing Arch as well) load nouveau? If it does it may
> be a good idea to attach those logs as well.
No, it loads nv or vesa.
> Do you recall having problems with previous "version" of nouveau on this
> system?
Yes, it never worked for years, neither on 32 bit, nor now on 64 bit. Sorry for
not reporting it earlier.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-04-16 13:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 14:29 [Bug 36163] New: nouveau fails to render framebuffer on [GeForce 7300 GS] bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-36163-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-04-12 18:39 ` Emil Velikov
2011-04-12 18:39 ` [Bug 36163] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-04-16 13:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-04-16 13:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2011-04-18 19:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-05-23 11:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-16 11:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-18 14:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-22 23:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 20:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 22:51 ` 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=20110416134246.2F63E13000C@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox