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.
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.
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.
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.