There does not seem to be an xorg-server package in the repos. You mean
xserver-xorg-core?
--
X server aborts if two primary devices found
https://bugs.launchpad.net/bugs/459512
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
White works for me, thank you!
Black fails badly for me, X.org crashes, the Xorg.log for the crash is
attached as xorg_black_crash_log.log. I don't know for sure but I wonder
if this would happen with white too if I plugged the monitor in the
other card.
Can you comment on plans for the release,
Mark,
Is it possible for you to confirm whether plugging the monitor into the
other card does cause the crash with white?
If the currently available fix is only going to correct the problem for
any given user 50% of the time, I think we should wait to be able to
address this fully and fix it via
On 26/10/09 12:55, Steve Langasek wrote:
Is it possible for you to confirm whether plugging the monitor into the
other card does cause the crash with white?
Interestingly, it did not cause a crash. So, white worked in the case
where the monitor was connected to the card it picked, and it
This bug was fixed in the package xorg-server - 2:1.6.4-2ubuntu4
---
xorg-server (2:1.6.4-2ubuntu4) karmic; urgency=low
* Add 188_default_primary_to_first_busid.patch: X can abort if multiple
video devices are present, and none are marked as primary. This makes
X just pick
Great, thanks for the testing! To follow up on the remaining loose
threads...
From the log file, the crash with black is occurring much later in the
boot cycle; it is setting primary and picking the driver correctly, it
is just failing somewhere down the road. My guess is that there is also
Attached is my Xorg.0.log. This is with your patched xserver-xorg from
the PPA.
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/34359211/Xorg.0.log
--
X server aborts if two primary devices found
https://bugs.launchpad.net/bugs/459512
You received this bug notification because
Joshua, please post your Xorg.0.log from both with my PPA and without.
(You should always post your Xorg.0.log with X bugs.)
On Sun, Oct 25, 2009 at 02:43:18AM -, Joshua Harding wrote:
I have encountered this bug as well.
# lspci
04:00.0 VGA compatible controller: nVidia Corporation G94
** Attachment added: shuttleworth-Xorg.0.log
http://launchpadlibrarian.net/34302177/shuttleworth-Xorg.0.log
--
X server aborts if two primary devices found
https://bugs.launchpad.net/bugs/459512
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: shuttleworth-lspci.txt
http://launchpadlibrarian.net/34302183/shuttleworth-lspci.txt
** Changed in: xorg-server (Ubuntu)
Importance: Undecided = High
** Changed in: xorg-server (Ubuntu)
Status: New = In Progress
** Changed in: xorg-server (Ubuntu)
From the lspci output, note the two video devices are identical types:
00:00.0 Host bridge: Intel Corporation 82X38/X48 Express DRAM Controller (rev
01)
Subsystem: ASUSTeK Computer Inc. Device 8295
01:00.0 VGA compatible controller: ATI Technologies Inc R600 [Radeon HD 2900
Series]
This patch fixes the issue of X being unable to make up its mind, by
making it just pick the one with the larger busid.
(Or technically, the last appropriate device seen... it looks like the
device list will always be sorted from lower busid to higher.)
** Attachment added:
This patch is just the inverse of the previous one - if more than one
device is present, just select the first one seen.
I'm going to go with the other patch since it's closest to what we were
doing before, however I don't have strong preferences here. The main
reason we went with the last busid
One other note worth mentioning - the ideal solution (mentioned in the
other bug referenced above) is to probe the devices and see which ones
have monitors attached. This would let us avoid setting the wrong card
as primary.
This functionality is not available currently. As I understand it, the
14 matches
Mail list logo
