2.6.19.2 Kernel Headers
in [Slackware]
|
Prev: memory stick
Next: Lilo problem
From: rshepard on 15 Jan 2007 17:28 Trying to reconfigure VMware Workstation-5.5.x to work with kernel 2.6.19.2. The perl script keeps hanging when asking for the directory containing the kernel headers. The wording is: What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include] Although /usr/src/linux is a soft link to /usr/src/linux-2.6.19.2, it doesn't work. So, I try putting in the full path: /usr/src/linux-2.6.19.2/include and then I see this: The directory of kernel headers (version @@VMWARE@@ UTS_RELEASE) does not match your running kernel (version 2.6.19.2). Even if the module were to compile successfully, it would not load into the running kernel. I'm confused. That's the directory in the source tree from which the running kernel was built. I'm not seeing what I've missed here. Rich
From: Grant on 15 Jan 2007 17:43 On 15 Jan 2007 22:28:28 GMT, rshepard(a)salmo.appl-ecosys.com wrote: > Trying to reconfigure VMware Workstation-5.5.x to work with kernel >2.6.19.2. The perl script keeps hanging when asking for the directory >containing the kernel headers. The wording is: > >What is the location of the directory of C header files that match your >running kernel? [/usr/src/linux/include] My system has: grant(a)sempro:~$ ls -l /lib/modules/$(uname -r) |egrep "(build|source)" lrwxrwxrwx 1 root root 33 2007-01-12 11:29 build -> /home/grant/linux/linux-2.6.19.2a/ lrwxrwxrwx 1 root root 33 2007-01-12 11:29 source -> /home/grant/linux/linux-2.6.19.2a/ What is the location of the directory of C header files that match your running kernel? [/lib/modules/2.6.19.2a/build/include] > Although /usr/src/linux is a soft link to /usr/src/linux-2.6.19.2, it >doesn't work. So, I try putting in the full path: >/usr/src/linux-2.6.19.2/include and then I see this: You really need to follow current best practice and compile new kernels as a user -- I don't know why /usr/src/linux no longer works for you, but it is a deprecated kernel build area for many years, for most applications. >The directory of kernel headers (version @@VMWARE@@ UTS_RELEASE) does not >match your running kernel (version 2.6.19.2). Even if the module were to >compile successfully, it would not load into the running kernel. Annoying, isn't it? :) > > I'm confused. That's the directory in the source tree from which the >running kernel was built. I'm not seeing what I've missed here. Try building the kernel us user, what does the command: ls -l /lib/modules/$(uname -r) |egrep "(build|source)" say? Grant. -- http://bugsplatter.mine.nu/
From: Peter on 15 Jan 2007 18:08 On Mon, 15 Jan 2007 22:28:28 +0000, rshepard wrote: all snip.... you need an updated version of vmware. vmware < VMware Workstation 5.5.3 build-34685 won't work with kernels > 2.6.18. In addition, although I do not need this, you might need the any-any patch (see vmware.com). I assume you did make modules_install after compiling your new kernel? -- Peter
From: rshepard on 15 Jan 2007 18:38 On 2007-01-15, Grant <g_r_a_n_t_(a)dodo.com.au> wrote: > My system has: > grant(a)sempro:~$ ls -l /lib/modules/$(uname -r) |egrep "(build|source)" > lrwxrwxrwx 1 root root 33 2007-01-12 11:29 build -> /home/grant/linux/linux-2.6.19.2a/ > lrwxrwxrwx 1 root root 33 2007-01-12 11:29 source -> /home/grant/linux/linux-2.6.19.2a/ > > What is the location of the directory of C header files that match your running > kernel? [/lib/modules/2.6.19.2a/build/include] Grant, /usr/src/2.6.19.2/include Same result with /lib/modules/2.6.19.2/build/include > You really need to follow current best practice and compile new kernels as > a user -- I don't know why /usr/src/linux no longer works for you, but it > is a deprecated kernel build area for many years, for most applications. I don't know why it's not working, either. /usr/src/linux has been on my systems since Red Hat 4.0 in 1997. That's where I've continued to build kernels. And, this is the first kernel upgrade since I started with VMware pre-1.0 beta versions that's not worked. What are the differences between building kernels as a user someplace and as root in /usr/src/linux? > Annoying, isn't it? :) Yes. And time consuming when I have other things to do. > Try building the kernel us user, what does the command: > > ls -l /lib/modules/$(uname -r) |egrep "(build|source)" > say? lrwxrwxrwx 1 root root 23 2007-01-13 12:53 build -> /usr/src/linux-2.6.19.2/ lrwxrwxrwx 1 root root 23 2007-01-15 13:38 source ->/usr/src/linux-2.6.19.2/ Rich -- Richard B. Shepard, Ph.D. | The Environmental Permitting Applied Ecosystem Services, Inc. | Accelerator(TM) <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863
From: rshepard on 15 Jan 2007 19:02
On 2007-01-15, Peter <peter(a)localhost.com> wrote: > you need an updated version of vmware. vmware < VMware Workstation 5.5.3 > build-34685 won't work with kernels > 2.6.18. In addition, although I do > not need this, you might need the any-any patch (see vmware.com). Peter, I thought this might be the case, as previous kernel upgrades required upgrades to VMware, too. However, I've tried five times today to download the tarball, and each time it hangs after 30-50M of the 104M total size. Frustrating. I've asked the VMware folks if there's ftp access since ncftp will resume a partial download. > I assume you did make modules_install after compiling your new kernel? Yup. Thanks, Rich -- Richard B. Shepard, Ph.D. | The Environmental Permitting Applied Ecosystem Services, Inc. | Accelerator(TM) <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863 |