|
Bugzilla – Full Text Bug Listing |
| Summary: | sax2: Nvidia driver shows up as vesa in sax2 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Kristian Alvestad <antikristian> |
| Component: | SaX2 | Assignee: | Marcus Schaefer <ms> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | sndirsch |
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Kristian Alvestad
2007-09-18 17:40:25 UTC
what does "sax2 -p" show you ? I think this card is like many others set to be configured with the vesa driver whereas it was "nv" before. The problem is we had an automatic mapping from nv to nvidia if the binary nvidia driver is installed but if the original PCI table set this card to be configured as vesa this magic doesn't apply Using the -m 0=nvidia option should allow you to configure the device but that option is by design evil and shouldn't be needed Stefan is there a reason why you changed that many cards to vesa ? I got tons of reports that we now use vesa and -m 0=nvidia works for most people IIRC SaX2 always shows you the default driver to use, no matter which driver you explicitely specify with "-m 0=<driver>". Indeed we need to know the output of "sax2 -p". There should be only a very small set of NVIDIA cards, which default to fbdev driver. sax2 -p Chip: 0 is -> VESA Vesa-BIOS Graphics 01:00:0 0x10de 0x0429 AGP vesa *** This bug has been marked as a duplicate of bug 300604 *** |