Summary: | [vesafb-tng] kernel 2.6.14-r* vesafb-tng problem with nvidia and 8 bpp depth | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Christian Loosli <spam> |
Component: | [OLD] Core system | Assignee: | Michal Januszewski (RETIRED) <spock> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | cycoone |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Christian Loosli
2005-12-16 08:43:44 UTC
Is this still a problem with the latest version of gentoo-sources? (In reply to comment #1) > Is this still a problem with the latest version of gentoo-sources? > It is at least with 2.6.17-r4, still CONFIG_FB_VESA=y # CONFIG_FB_VESA_STD is not set CONFIG_FB_VESA_TNG=y and still cat /proc/fb0/modes 640x400-8 640x480-8 800x600-8 1024x768-8 320x200-16 320x200-32 640x480-16 640x480-32 800x600-16 800x600-32 1024x768-16 1024x768-32 1280x800-0 I am using 1024x768 now, because it is the highest working resolution. I can't reproduce this at all with current gentoo-sources. Hopefully uvesafb will be accepted upstream and then we can simply remove vesafb-tng from gentoo-sources without any loss of functionality. I'm closing this bug as WONTFIX, since we're dropping support for vesafb-tng. vesafb-tng has been replaced by uvesafb in gentoo-sources-2.6.23. uvesafb provides the same functionality, but is completely redesigned and hopefully will prove to be free of any bugs that might have been present in vesafb-tng. If you encounter a similar problem with uvesafb, please open a new bug. |