Click to See Complete Forum and Search --> : [SOLVED] Gamma errors attempting to compile 2.6.12.x kernel


tody4me
08-15-2005, 04:13 PM
I keep getting errors with Gamma_Drv.c file refrencing back to some DRM files that appear to be missing. I'm guessing that during the compile process, the .H files turn to .O files, and therefore the links are broken. Don't know much C programming, more into C# and VB, but what I can tell there are some include lines refrencing these .H files that are no longer there at this point in the process. Also, getting Errors - DRM is a function returning a function. I remeber something about being able to pass a pointer to a function back but I haven't heard of passing a function back to a calling function, per se. Was wondering if there is some option that I need to turn off for this to work, or if there is some modification that I could make to the .c files or .h files to make this kernel compile. I have the latest kernel that I'm working on with a Debian Sarge distro (2.6.12.4). Debian Sarge kernel is currently 2.6.8.2. I have all the packages (I think) that i need before i compile. I have installed the QT3 package, with dev, fakeroot, gc++, g++, make, standard dev stuff that was asked for by other programs, such as wine.

TIA for any help you could give.
ToDy4Me

tody4me
08-16-2005, 03:19 PM
A fix for this (for me at least) was to comment out the two lines in the Makefile that refrence the gamma_drivers. There was one in the definitions section (i would guess, first time editing Makefiles) and one actually calling the process to compile the gamma driver. If there is a better fix for this, please let me know, but this seems to work now, the kernel is in the process of compiling and has gotten past the place that I got the error from.

bwkaz
08-16-2005, 06:43 PM
You could have just turned off CONFIG_DRM_GAMMA (in menuconfig, xconfig, or gconfig, that's Device Drivers --> Character devices --> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) --> 3dlabs GMX 2000.

It's reportedly a "broken" driver, so it should be disabled (and unavailable), as long as you've turned on CONFIG_CLEAN_COMPILE (Code maturity level options --> Select only drivers expected to compile cleanly).