Fedora Core 3, kernel headers, DRI

davetrainer · 01-21-2005, 09:52 AM

A problem with my video card has led me to a problem with (lacking) Fedora kernel header files.

I will briefly outline my video card issue for some background: I start out at 800x600 resolution, which I personally can't stand. But when I bump my settings up to 1600x1200 and restart, my monitor displays a "signal out of range" error and nothing else (I had to login without X and restore the previous config manually just to be able to see my desktop again.) I decide the best way to remedy this is to update my video card drivers. Here is the Intel support doc that describes this process:

support.intel.com/support/graphics/sb/CS-010512.htm

You'll notice one of the requirements is "kernel header files installed," which of course they aren't. Thanks to another linuxquestions.org thread and the Fedora release notes, I learn that "In order to eliminate the redundancy inherent in providing a separate package for the kernel source code when that source code already exists in the kernel's .src.rpm file, Fedora Core 3 no longer includes the kernel-source package."

Great.

So I go get a kernel .src.rpm from

download.fedora.us/fedora/fedora/3/i386/SRPMS.updates-testing/

and follow the steps laid out in the release notes, although I didn't fully understand what was going on after step 3 (rpmbuild). Still...

Code:

[atg@atgtest ~]$ rpm -a |grep kernel-source
[atg@atgtest ~]$

...nothing.

And of course the installer chokes because it can't find the package...

Code:

[root@atgtest dripkg]# ./install.sh
 
<snip>

Compiling new agpgart module...
Compiling DRM module...

ERROR: Kernel modules did not compile

The DRI drivers can not be installed without the latest kernel modules.
Installation will be aborted. See the dri.log file for information on
what went wrong.

[root@atgtest dripkg]# cat dri.log
make: *** No rule to make target `gdg.ko'.  Stop.

So my questions are, how do I know if I built the source tree successfully? And do I have to register the kernel-source package somehow so the DRI installer will know that it's there? Has anyone encountered this video signal issue before and is there an easier resolution that I've totally missed? I routinely find answers from this site but this is the first time I have been compelled to ask a question as I am really at a dead end. Thanks in advance.

(Sorry, this is my first post and I can't post URLs)

Vookimedlo · 01-21-2005, 10:43 AM

Kernel headers are in Feodra Core 3 at this place /lib/modules/2.6.10-1.741_FC3/source/include

davetrainer · 01-21-2005, 10:46 AM

OK, but how do I get the driver installer to understand this?

steveq9t4 · 02-02-2005, 08:37 AM

Your makefile should supply the include directory to use via the -I parameter. I use a
symlink at /usr/src/linux that points to the correct /lib/modules/... directory.
Here's my Makefile:

---------------------------------------------------------------------------------------------------------
# Include directory to point to kernel include
INCLUDE = /usr/src/linux/include
# /usr/src/linux -> /lib/modules/2.6.10-1.741_FC3/build/include

# Compiler
CC = gcc

# Compiler flags.
CFLAGS = -DDEBUG_OUTPUT -D__KERNEL__ -DMODULE -DLINUX -Wall -I$(INCLUDE)

TARGET = pcifinder.o

OBJS = pcifinder.o

all: $(OBJS)

pcifinder.o: pcifinder.cIn file included from /usr/src/linux/include/linux/config.h:4,
from /usr/src/linux/include/linux/fs.h:9,
from pcifinder.c:45:
/usr/include/linux/autoconf.h:1:2: #error Invalid kernel header included in userspace
In file included from /usr/src/linux/include/linux/fs.h:10,
from pcifinder.c:45:

clean:
@rm -f *.o
-------------------------------------------------------------------------------------------------------------

I actually have my own question. Everything appears to be setup correctly but gcc complains
in a few ways. A couple of the relavant error messages (out of many

are:

1. #error Invalid kernel header included in userspace
2. /usr/src/linux/include/linux/linkage.h:5:25: asm/linkage.h: No such file or directory

I am building a kernel module (-D__KERNEL__ -DMODULE) so I don't understand the first message. Also, linkage.h does in fact exist at <asm/linkage.h> so again, this is a mystery. My guess is that gcc is using some other include directory and it is not being initialized correctly to build a kernel module. This exact same Makefile worked fine under kernel 2.4 however. Any ideas?

Steve Q.
ALT Software Inc.