Anyone know where FC5 kernel build files end up.

sass10151 · 08-28-2006, 12:22 PM

I do not need a link to the rpm, they are already installed. But other rpms expect them in /lib/modules/build, and they are not there. I can't even search for them, because I don't know their names. I have to leave, will check back later. TIA.

MensaWater · 08-28-2006, 12:39 PM

/lib/modules/<kernel>/build should be a link to /lib/modules/<kernel>/source. Where kernels it the one reported by uname -r.

If you have something that actually expects it in /lib/modules/build you could create a symbolic link that points to /lib/modules/<kernel>/build.

sass10151 · 08-29-2006, 03:58 AM

I thought it was an empty directory and madwifi/ndiswrapper threw errors when I tried to run them. I didn't realized when I first ran the madwifi rpm that it was looking for files that are supposed to be in lib/modules/build. I need to know the path that the link pointed to so I can recreate it.
Also, the rpms that look in lib/modules/build for the kernel source apparently cannot use that link, so I will need to enter the path when I run the package. But I am having one heck of a time getting anyone to tell me what the path is. I've seen a lot of posts with this same problem, but none of the replies solve the problem.

MensaWater · 08-29-2006, 01:35 PM

Do "ls -l /lib/modules". Post its output here.

Do "uname -r". Post its output here.

Essentially it sounds like you just need to create a symbolic link from your kernel source to /lib/modules/build.

sass10151 · 08-29-2006, 07:18 PM

I'm at work now. I think I messed up that path in the original post. I believe it is /lib/modules/<kernel>/build. I know I need to recreate the symbolic link, but I can't find anyone who can tell me where it should point.

fozner · 08-29-2006, 11:32 PM

Here's what mine looks like:

Code:

$ ls /lib/modules/$(uname -r)
total 1100
lrwxrwxrwx  1 root root     49 Aug 11 01:11 build -> ../../../usr/src/kernels/2.6.17-1.2174_FC5-x86_64drwxr-xr-x  2 root root   4096 Aug  8 11:52 extra
drwxr-xr-x 10 root root   4096 Aug 11 01:11 kernel
drwxr-xr-x  2 root root   4096 Aug 27 02:15 misc
-rw-r--r--  1 root root 236385 Aug 29 02:50 modules.alias
-rw-r--r--  1 root root     69 Aug 29 02:50 modules.ccwmap
-rw-r--r--  1 root root 234434 Aug 29 02:50 modules.dep
-rw-r--r--  1 root root    813 Aug 29 02:50 modules.ieee1394map
-rw-r--r--  1 root root    375 Aug 29 02:50 modules.inputmap
-rw-r--r--  1 root root   2468 Aug 29 02:50 modules.isapnpmap
-rw-r--r--  1 root root     74 Aug 29 02:50 modules.ofmap
-rw-r--r--  1 root root 180461 Aug 29 02:50 modules.pcimap
-rw-r--r--  1 root root   4411 Aug 29 02:50 modules.seriomap
-rw-r--r--  1 root root 109028 Aug 29 02:50 modules.symbols
-rw-r--r--  1 root root 289970 Aug 29 02:50 modules.usbmap
lrwxrwxrwx  1 root root      5 Aug 11 01:11 source -> build
drwxr-xr-x  2 root root   4096 Aug  8 11:52 updates

Does that help?

sass10151 · 08-30-2006, 03:22 AM

[Larry@luger ~]$ ls -l /lib/modules/2.6.15-1.2054_FC5
total 1148
drwxr-xr-x 2 root root 4096 Mar 14 14:02 extra
drwxr-xr-x 10 root root 4096 Aug 27 00:46 kernel
-rw-r--r-- 1 root root 239062 Aug 27 00:47 modules.alias
-rw-r--r-- 1 root root 69 Aug 27 00:47 modules.ccwmap
-rw-r--r-- 1 root root 238199 Aug 27 00:47 modules.dep
-rw-r--r-- 1 root root 813 Aug 27 00:47 modules.ieee1394map
-rw-r--r-- 1 root root 206 Aug 27 00:47 modules.inputmap
-rw-r--r-- 1 root root 11158 Aug 27 00:47 modules.isapnpmap
-rw-r--r-- 1 root root 182372 Aug 27 00:47 modules.pcimap
-rw-r--r-- 1 root root 799 Aug 27 00:47 modules.seriomap
-rw-r--r-- 1 root root 104167 Aug 27 00:47 modules.symbols
-rw-r--r-- 1 root root 279653 Aug 27 00:47 modules.usbmap
lrwxrwxrwx 1 root root 5 Aug 27 00:46 source -> build
drwxr-xr-x 2 root root 4096 Mar 14 14:02 updates

Of course, what I need to know is what the build symbolic link "build" is supposed to point to. Mine is missing because I did not know about symbolic links until I had already deleted it. Lart me if you must, but I am learning and now I think I can fix it if I just know where it pointed when it was there.

Here's the other command requested:

[Larry@luger ~]$ uname -r
2.6.15-1.2054_FC5

I guess I'll just have to reinstall to find out what "Link target" says for /lib/modules/2.6.15-1.2054_FC5/build. Maybe the problem is that I'm too GUI based. Someone would need to browse to the link in Nautilus (or equivilent) to check the properties. Although, I would think there is a command line way to determine the target. I just don't know what it is yet.

fozner · 08-31-2006, 12:49 AM

No need to reinstall. Just make a simlink, something like:
su
cd /lib/modules
ln -s /lib/modules/$(uname -r) build

If it still has problems just boot to an earlier kernel and get rid of the new kernel. Might work without booting the earlier kernel but I haven't tried it. Oh, and back-up any compiled modules (such as nvidia.ko) unless you want to recompile them.

rpm -qa kernel
rpm -e kernel-2.6.15-1.2054_FC5

Now remove the lib/modules/2.6.15-1.2054_FC5 folder

rm -rf /lib/modules/2.6.15-1.2054_FC5

and restore it all

yum update kernel

sass10151 · 09-01-2006, 12:10 AM

But I finally learned what the problem is.
The basic FC5 install apparently has a bug.
/lib/modules/2.6.15-1.2054_FC5/build is a broken link.

After the reinstall, I updated the kernel and then installed the kernel headers and source, all with yum.

Now, I have /lib/modules/2.6.17-1.2174_FC5/build with stuff actually in "build". Everything looks good, but I am seeking opinions now on the best way to proceed with setting up my DWL-G650 wireless card (madwifi vs. ndiswrapper vs. Linuxant DriverLoader.)

I plan to post a definitive thread with all relevant search terms to help others find it, because it seems a lot of folks are running into the same problem.

Boy, I sure learned a lot from this, though!