Hello Daniel, or anyone else affected,

Accepted nvidia-prime into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/nvidia-
prime/0.5~hybrid0.0.3 in a few hours and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Description changed:

  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 -n` 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.
+ 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.

** Changed in: nvidia-prime (Ubuntu Precise)
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282796

Title:
  prime-xconfig can write an invalid BusID string

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1282796/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to