Bug 19711 - error messages when BusID specification is malformed or incorrect syntax
Summary: error messages when BusID specification is malformed or incorrect syntax
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: unspecified
Hardware: All All
: medium enhancement
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-23 15:53 UTC by Bobby Krupczak
Modified: 2018-06-12 18:43 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Bobby Krupczak 2009-01-23 15:53:32 UTC
Hi!

I've been struggling for quite some time to get the Xorg server to use a particular video card.  My machine has two and I kept getting errors in Xorg.log that stated that no device was found.

It turns out that I had improperly specified the BusID as 3:00.00 instead of 3:00:00.  Note the colons vs. periods.  A very subtle difference that I originally missed despite reading the man pages and looking on the net and googling.

I would like to suggest that the Xorg server code that parses the xorg.conf file spit out a more descriptive error code that says something to the effect that the BusID specification was incorrect rather than implying that the device was not found.  This change in error message would have forced me to focus more on the man page and how to correctly specify the busid.  The error is compounded by the fact that dmesg and /proc/driver/nvidia/cards/#card file gives BusID specs that do not conform to the requirements in the xorg.conf file.

Alternatively, one could enhance the xorg.conf parsing code to be more flexible with busid specifications.

Thanks,

Bobby
Comment 1 Adam Jackson 2018-06-12 18:43:08 UTC
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please file a new report if you continue to experience issues with a current server.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.