| Summary: | intelfb doesn't work with kernel 2.6 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Bernhard Reiter <ockham> |
| Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
| Status: | RESOLVED INVALID | ||
| Severity: | minor | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://www.xfree86.org/~dawes/intelfb.html | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Bernhard Reiter
2005-03-04 05:28:54 UTC
okay, i've taken a peek into intelfbdrv.c, so apparently, it actually HAS been ported to 2.6 - so it must be another issue the intelfb driver is really weird. in 2.4 the vga= option was only used for the digital out (reusing initialization code used by vesafb that is scattered though the kernel to take care of things). This functionality is broken on 2.6 which restricts the use of that code to the vesafb driver. I assume other changes make it very hard to modify things to get the vga option to work. Thus, the intelfb driver is useless when digital out is required (like on laptop displays). All is well if you are using the vga output, just use the video=intelfb:blablabla style argument (similar to vesafb-tng and others). The reason why intelfb only works right with vga is that when it was written the author had no documentation on the digital output. Someone needs to find docs on the digital output or can figgure out how X makes it work. I looked into it a while back, but at the moment fb code is a bit beyond my skill. Closing as there is no hope to make the vga= option work on 2.6 for intelfb In fact, intelfb works on my laptop when compiled into the kernel and setting vga=791 (or any other vga mode) on kernel command line (at least up to and including on 2.6.12; on 2.6.13 it introduces a blank screen). And it works only when vesafb-tng is NOT patched into the kernel (e.g with vanilla-sources, or gentoo-sources with vesafb-tng patch manually removed). When vesafb-tng patch is applied to the kernel, then vga= option refuses to work and i get an "undefined mode number" error. |
