This bug was fixed in the package nvidia-prime - 0.5~hybrid0.0.3
---------------
nvidia-prime (0.5~hybrid0.0.3) precise-proposed; urgency=low
[ Daniel Dadap ]
* prime-xconfig:
- Format the BusID string correctly (LP: #1282796).
The BusID string created by prime-xconfig had several problems:
1) It was missing the bus type "PCI", as recommended by
xorg.conf(5).
2) Values were written in hexadecimal, as reported by lspci,
instead of decimal, as expected by the server. (See the
comment at the top of xf86ParsePciBusString().)
3) The PCI domain was not specified.
Giving the BusID string in the wrong format could cause the X
server to fail to parse the BusID, or to parse numbers in the
wrong base. On systems with more than one PCI domain, `lspci -n`
output would include the domain number, which is omitted by
default on systems with only one PCI domain. nv_get_id()
expects the bus number to be the first field, which would not be
correct when `lspci -n` reports the domain, as it does on
systems with multiple domains.
Fix these issues by always reporting the domain with `lspci -Dn`
and using it in the BusID string, prepending "PCI:" to the
BusID string, and printing all numeric values in decimal.
-- Alberto Milone <[email protected]> Fri, 21 Feb 2014 09:59:12
+0100
** Changed in: nvidia-prime (Ubuntu Precise)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1282796
Title:
prime-xconfig can write an invalid BusID string
Status in “nvidia-prime” package in Ubuntu:
Fix Released
Status in “nvidia-prime” source package in Precise:
Fix Released
Bug description:
SRU request:
Please accept nvidia-prime (0.5~hybrid0.0.3) into precise-proposed.
[Rationale]
The fix .
[Impact]
Without this work, X will fail to start in some cases (see the "Full
Explanation" section) on systems with hybrid graphics (Intel/NVIDIA).
[Test Case]
1) Install the update on a hybrid system with Intel/NVIDIA GPUs
2) Make sure that the system can boot and that X doesn't fail.
[Regression Potential]
Low. Thanks to this fix, the xorg.conf, if anything, will have greater
chances to work.
[Full Explanation]
The BusID string created by prime-xconfig could be incorrect in any of the
following cases:
a) Any numeric component of the bus ID is greater than 9: prime-xconfig will
write a hexadecimal value, but X will parse it as decimal.
b) The system has more than one PCI domain: `lspci -Dn` will show the PCI
domain, which is normally hidden on systems with a single PCI domain. This
breaks the formatting assumptions made by nv_get_id() about which fields are in
which position.
Besides the potential correctness issues, the generated BusID string
is missing the following recommended (but optional) information:
a) Bus type. According to xorg.conf(5) this should be "PCI:"
b) PCI domain: omission of this field could lead to problems on systems with
multiple PCI domains
A patch against nvidia-prime 0.5.5 from Trusty is attached. The
version on github seems to be behind that version by quite a bit.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1282796/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
