I didn't say he has to reinstall the kernel source. I just asked him to make sure he installs the latest kernel & kernel- devel using yum, and reboot the machine *only* if a new kernel is installed. Never the less, I did miss his kernel version. My bad. Gilboa On Sun, 2005-10-09 at 16:32 +0100, Craig McLean wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > > Gilboa Davara wrote: > > Cause as far as I could see, the kernel-devel package version didn't > > match the running kernel version. > > While your solution (re-link build) *might* work, if he's running a > > 2.6.12 kernel but builds against a 2.6.13 kernel source, nothing will > > work. > > - From the OP: > Currently I'm running kernel 2.6.13-1.1526_FC4 > ... > rpm -ivh kernel-2.6.13-1.1526_FC4.src.rpm > > Then: > rpm -ivh kernel-devel-2.6.13-1.1526_FC4.i686.rpm > > So that's not a problem, same kernel everywhere. Also, you can tell he's > booted to the new kernel because: > > make[1]: Entering directory `/root/ndiswrapper-1.4/driver' > Can't find kernel sources in /lib/modules/2.6.13-1.1526_FC4/build; > > The make is using `uname -r` here... > > > I never use debuggers... for a single reason (Which relates to this > > problem) > > You tend to solve the symptoms (invalid/non-matching kernel source link) > > instead of solving the source of the problem. > > Debuggers? I just said that because he had installed the kernel source > package the link in /lib/modules/`uname -r` would be broken, and it was. > As long as you link the correct build directory to the correct > kernel-devel installation, you won't have any problems. You certainly > don't need to install the whole kernel source and then rpmbuild the > kernel just to install ndiswrapper. > > C. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.1 (GNU/Linux) > > iD8DBQFDSTgbMDDagS2VwJ4RAvlwAKDyUy5pkCA0Z77nY+W1tLSZk7sqWgCg+ZmV > uor9QM0BePwUTffFs+hVrvY= > =eK7q > -----END PGP SIGNATURE----- >
