Bug 144550
| Summary: | VESA driver fails on Gigabyte GA-K8VM800M (K8M800) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jeff Schultz <jws> |
| Component: | xorg-x11 | Assignee: | X/OpenGL Maintenance List <xgl-maint> |
| Status: | CLOSED DUPLICATE | QA Contact: | David Lawrence <dkl> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3 | CC: | k.georgiou, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-01-17 03:31:07 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
*** Bug 144549 has been marked as a duplicate of this bug. *** |
Description of problem: VESA driver in x86_64 FC3 fails during VBE calls on K8M800-based board with AMD64 3000 CPU. Can persuade it to work in a 32-bit install of SUSE 9.1, and it sort of worked with 32-bit FC2. The X server is not something I'm familiar with, but a bit of manual debugging found that the xf86ExecX86int10 call in VBEGetModeInfo is yielding 0x14f instead of the desired 0x4f for every mode tried. This leads to VESAPreInit's giving up and the line (EE) VESA(0): No matching modes in the X log. (Attempts with the unichrome project driver failed for this board. K8M800 support not there yet. The old VIA driver is not present in the x86_64 distribution for some reason, so I'm a bit stuck.) Version-Release number of selected component (if applicable): xorg-x11-6.8.1-12.FC3.21 kernel-2.6.9-1.724_FC3 How reproducible: Completely. Steps to Reproduce: 1. Install x86_64 FC3 on this hardware. 2. Try the X VESA driver. 3. Actual results: (EE) VESA(0): No matching modes Expected results: Working X in some suitable resolution. Additional info: Not restricted to this MB---from others' comments, there seems to be a bit of a problem with this chipset on all MBs using it.