Bug 23870

Summary: pci_id_match table needs to hardcode supported device IDs
Product: xorg Reporter: Mario Limonciello <mario_limonciello>
Component: Driver/nVidia (open)Assignee: Aaron Plattner <aplattner>
Status: RESOLVED WONTFIX QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: git   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Move logic for matching devices out of probe routine
none
Run the parsing script once none

Description Mario Limonciello 2009-09-11 16:11:44 UTC
The only graphics drivers that can safely use PCI_MATCH_ANY are 'vesa' and 'fbdev'.  -ati and -intel both explicitly list out their supported hardware.

By using PCI_MATCH_ANY for the device IDs, the nvidia driver erroneously reports that it is able to support ANY NVIDIA hardware but then collapses during the probe routine on any unsupported NVIDIA device.

Because the actual failure happens in the probe routine, the X server has already allocated an entity for this card, and a fallback to VESA or FBDEV is no longer possible.  This causes trouble when trying to use a system without an xorg.conf.


I'd recommend looking at -ati as they dynamically generate their list of supported IDs.

There are a few handfuls of bugs on the Ubuntu launchpad tracker for karmic that won't boot to X on a live disk, and boil down to this problem, I'd be glad to share links if requested.
Comment 1 Mario Limonciello 2009-09-12 07:27:03 UTC
Created attachment 29454 [details] [review]
Move logic for matching devices out of probe routine
Comment 2 Mario Limonciello 2009-09-12 07:27:18 UTC
Created attachment 29455 [details] [review]
Run the parsing script once
Comment 3 Corbin Simpson 2012-01-22 12:30:40 UTC
Nobody is supporting xf86-video-nv and it will be going away at some point in the future. If your problem persists with nouveau or the proprietary driver provided by nVidia, please re-file accordingly. We apologize for the inconvenience.

This is part of an automated bulk action; if you believe that this bug was closed in error, then change the targeted component and reopen it.

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.