From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 16165] New: Multi-gpu Quadro NVS 400 (NV17a x2) fails to initialise xserver
Date: Fri, 30 May 2008 07:35:22 -0700 (PDT) [thread overview]
Message-ID: <bug-16165-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=16165
Summary: Multi-gpu Quadro NVS 400 (NV17a x2) fails to initialise
xserver
Product: xorg
Version: 7.3
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: elbeardo69-/E1597aS9LQAvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=16825)
--> (http://bugs.freedesktop.org/attachment.cgi?id=16825)
log
Multi-gpu Quadro NVS 400 (NV17a x2) fails to initialise xserver.
When both of the separate pci bus addresses are used in seperate
devices/screens, the xserver instance fails.
Also, making the second gpu post first (i think that's what I've managed to do
- see log3) fails when it is the sole device in use (tried IsolateDevice =
bus-id and SingleCard = true options).
The noint10 option makes the loading of the driver / connection detection get
further.
Dual screen using randr on DVI-A-0 and 1 is working.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2008-05-30 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 14:35 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-16165-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-05-30 14:36 ` [Bug 16165] Multi-gpu Quadro NVS 400 (NV17a x2) fails to initialise xserver bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-04-11 19:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-04-11 19:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-04-11 19:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-04-11 19:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-04-11 19:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-04-11 20:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-04-11 20:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-04-11 20:31 ` 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-16165-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.