All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 15206] [dualhead, randr12, ppc] Second head displays nothing
Date: Thu, 19 Jun 2008 22:52:08 -0700 (PDT)	[thread overview]
Message-ID: <20080620055212.22BDD13005B@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-15206-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>

http://bugs.freedesktop.org/show_bug.cgi?id=15206





--- Comment #8 from Robin Johnson <robbat2-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>  2008-06-19 22:52:06 PST ---
Created an attachment (id=17245)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=17245)
Xorg.0.log

(In reply to comment #5)
> You might like to try again with an up-to-date checkout. Off-ship dvi is now
> fixed for nv2x and nv3x x86, but I've no idea about nv4x and PPC :) It will
> probably help to boot with both monitors plugged so the open firmware stuff can
> set up as much as possible.
Sorry about the delay, but I was busy, and didn't get a chance to test it until
now.

It's not moved forward, in fact it's even worse now. X doesn't even start on a
single display, let alone get two of them up. Here's the kernel log, and I'll
attach the Xorg.log in a moment.

From the kernel:
[   73.994279] [drm] Initialized drm 1.1.0 20060810
[   74.003382] PCI: Unable to reserve mem region #2:10000000@90000000 for
device 0000:0b:00.0
[   74.003933] [drm] Detected an NV40 generation card (0x043100a4)
[   74.003940] [drm] Initialized nouveau 0.0.10
drm-2.3.0-1298-g8712f0a17bb135d4a on minor 0
[   74.003974] [drm] Used old pci detect: framebuffer loaded
[   74.004972] [drm] OF bios successfully copied (6447 bytes)

Versions:
xf86-video-nouveau df52dc4664df11d57fcf8a6c9ae3f87a149e5392
x11-drm 8712f0a17bb135d4ad3eb85b30f47c561cf9c148
libdrm 8712f0a17bb135d4ad3eb85b30f47c561cf9c148
mesa d785a0c8b2ff45d07a8d2992d089eb96c04658db (gallium-0.1 branch)


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2008-06-20  5:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26  8:34 [Bug 15206] New: [dualhead, randr12, ppc] Second head displays nothing bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-15206-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-03-26  8:34   ` [Bug 15206] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-26  8:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-26  9:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-26  9:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-26  9:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-05-06 18:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-05 18:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-05 18:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-17  9:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-20  5:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2008-06-21  2:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-21  2:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-21  2:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-21  3:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-21 21:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-21 21:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-21 23:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-01-07 23:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-01-08  5:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-01-08 14:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-15 11:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-15 21:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-31 10:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-04-23 21:17   ` 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=20080620055212.22BDD13005B@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.