Author |
Message |
beejay
|
Posted: Sat Feb 10, 2007 9:32 am |
|
Joined: Wed Feb 07, 2007 8:28 pm
Posts: 15
Location:
Melbourne, Vic
|
anyone come forward with how to setup the headers properly?
|
|
Top |
|
 |
jimmyfergus
|
Posted: Sat Feb 10, 2007 10:50 am |
|
Joined: Tue Jan 18, 2005 12:11 pm
Posts: 100
Location:
MA, USA
|
beejay wrote: anyone come forward with how to setup the headers properly?
It's listed earlier in the thread, and in the VMWareServer Wiki page. I can't say whether this is overkill though, there may be easier ways.
|
|
Top |
|
 |
neutron68
|
Posted: Sat Feb 10, 2007 11:20 am |
|
Joined: Tue Mar 28, 2006 8:26 pm
Posts: 804
Location:
Minneapolis, MN
|
jimmyfergus wrote: It's listed earlier in the thread, and in the VMWareServer Wiki page. I can't say whether this is overkill though, there may be easier ways.
I looked at the cited wiki page. The word headers was mentioned but does not explain what they are, where to find them or what they look like.
Also, I can see people using the word header in this thread, but it is NOT connected with any file or set of commands - it's only mentioned in passing. Clarification of what these elusive headers look like is necessary.
I think most of the people seeing answers on these forums are trying to learn Linux by example. It's impossible to learn how-to when the examples are not complete.
_________________ KnoppMyth R5.5, Asus A8N-VM CSM (nvidia 6150 onboard video), AMD Athlon 64 dual-core 4200+, two 1GB sticks DDR 400, HD-3000 HDTV card, PVR-150 card, Iguanaworks RS-232 IR receiver/transmitter, Pioneer DVR-110 DVD burner
|
|
Top |
|
 |
jimmyfergus
|
Posted: Sat Feb 10, 2007 11:44 am |
|
Joined: Tue Jan 18, 2005 12:11 pm
Posts: 100
Location:
MA, USA
|
Apologies for causing you frustration, but it's very hard to anticipate what may be confusing people.
C code (like the linux kernel), is typically composed of headers and source. Headers are effectively a definition of the interface to the source, which is the actual code - so given the headers a package knows how to interact with the kernel properly. Other packages require this to build.
R5E50 installs the headers by default - they're all there. However, many packages seem to reject them as inadequate for various reasons (like VMWare), so a solution is to get the kernel source and compile it in full - then VMWare et al seem happy with the headers contained in the built source tree. That's what the steps in the VMWare wiki do, and it does say "The installation needs kernel headers and those installed don't cut it.", before explaining how to resolve this issue.
If what you're trying to achieve isn't satisfied by the installed headers, try installing the source as laid out here and in the wiki, and it should be ok.
|
|
Top |
|
 |
randomhtpcguy
|
Posted: Sat Feb 10, 2007 3:01 pm |
|
Joined: Mon Nov 07, 2005 10:09 am
Posts: 153
|
Which method is best for getting the source ready for compiling everything it seems people are needing to compile: LIRC, Nvidia drivers, VMWare.
#1 Code: # rebuild the kernel package using the existing configuration cd /usr/src/linux-source-2.6.18-chw-13 cp /boot/config-2.6.18-chw-13 .config make-kpkg kernel_image # change the main source symlink to point at the sources cd /usr/src rm linux ln -s linux-source-2.6.18-chw-13 linux Pasted from <http://mysettopbox.tv/phpBB2/viewtopic.php?t=13281&sid=986702dda46ebb1b33774b3153aa0357> #2 Code: cd /usr/src/linux-source-2.6.18-chw-13; cp /boot/config-2.6.18-chw-13 .config; make cd /usr/src; rm linux; ln -s linux-source-2.6.18-chw-13 linux
Pasted from <http://knoppmythwiki.org/index.php?page=VMWareServer>
#3 Quote: cd /usr/src/linux-headers-2.6.18-chw-13 cp -r . ../linux-source-2.6.18-chw-13 This merges the kernel-headers with the kernel-source, since the source by itself doesn't have the configuration files that were used. Next, on my system at least, I had to at least partially make the kernel again, because certain kernel module scripts weren't in a usable state until you did that. So I did the following: cd /usr/src/linux-source-2.6.18-chw-13 make [wait about 20 seconds and then hit ctrl-c]
Pasted from [url]<http://mysettopbox.tv/phpBB2/viewtopic.php?t=13443&highlight=>[/url]
I hope one of them will work with LIRC because I still have no remotes on my two machines.
Last edited by randomhtpcguy on Mon Feb 12, 2007 4:06 pm, edited 1 time in total.
|
|
Top |
|
 |
jimmyfergus
|
Posted: Sat Feb 10, 2007 3:10 pm |
|
Joined: Tue Jan 18, 2005 12:11 pm
Posts: 100
Location:
MA, USA
|
randomhtpcguy wrote: Which method is best for getting the source ready for compiling everything it seems people are needing to compile
I suspect they all work, but I can definitely say that #2 works.
|
|
Top |
|
 |
randomhtpcguy
|
Posted: Mon Feb 12, 2007 12:32 pm |
|
Joined: Mon Nov 07, 2005 10:09 am
Posts: 153
|
Thanks. #2 above works. i was able to install the latest nvidia drivers with it. It didn't work for compiling LIRC from the sid source (failed at the make step). A warning is that it takes a long time to run make on the kernel source.
|
|
Top |
|
 |
ebeighe
|
Posted: Mon Feb 12, 2007 3:49 pm |
|
Joined: Tue Jan 30, 2007 11:28 pm
Posts: 8
|
I am still failing to build lirc (version 0.8.1).
I have installed kernel source, copied the .config, built, and set the /usr/src/linux link to the source directory -- as described in the first posting in this thread. That seems to have gone fine (it DOES take a long time!)
The lirc configure still fails... the last several messages are:
Code: checking for linux/input.h... yes checking sys/soundcard.h usability... yes checking sys/soundcard.h presence... yes checking for sys/soundcard.h... yes configure: error: *** you need to have the Linux kernel source installed for this driver
Any suggestions would be appreciated.
Last edited by ebeighe on Mon Feb 12, 2007 4:25 pm, edited 1 time in total.
|
|
Top |
|
 |
randomhtpcguy
|
Posted: Mon Feb 12, 2007 4:05 pm |
|
Joined: Mon Nov 07, 2005 10:09 am
Posts: 153
|
|
Top |
|
 |
ebeighe
|
Posted: Mon Feb 12, 2007 5:31 pm |
|
Joined: Tue Jan 30, 2007 11:28 pm
Posts: 8
|
Thanks. Those two extra switches in configure.sh did the trick -- at least insofar as I can now configure and compile lirc without errors.
I had thought it was a problem with the way my kernel sources were installed or whatever. But i guess it was just a peculiarity in lirc(?)
|
|
Top |
|
 |
randomhtpcguy
|
Posted: Tue Feb 13, 2007 11:07 am |
|
Joined: Mon Nov 07, 2005 10:09 am
Posts: 153
|
did you need to apt-get remove lirc first?
can you make && make install?
If you can that almost certainly means I need to reinstall and start with a clean R5E50. I think something in my kernel module configuration got screwed up in my early attempts to get this working.
|
|
Top |
|
 |
rpao
|
Posted: Thu Feb 15, 2007 11:12 am |
|
Joined: Tue Jul 13, 2004 8:18 am
Posts: 11
|
Is there any possibility of upgrading the kernel to 2.6.19 or higher to get the k8temp module into R5E50? sensors-detect added k8temp to /etc/modules. GkrellM will not display AMD Athlon 64 core temperatures without it.
_________________
R5E50, AMD Athlon 64 X2 3800+, GA-K8N Pro SLi F9, 1024MB, GeForce 6600 GT 128MB, 400GB, PVR-350, PVR-150MCE, no TV out. xbmcmythtv for TV out.
|
|
Top |
|
 |
tjc
|
Posted: Thu Feb 15, 2007 7:17 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
Sure, just DL the source from kernel.org, and build it. You may want to grab the configuration (and any patches) that Cecil used from his 2.6.18 bundle.
|
|
Top |
|
 |
buckaboobob
|
Posted: Sat Feb 17, 2007 10:25 am |
|
Joined: Mon Oct 18, 2004 11:28 am
Posts: 20
|
Do they even sell 640 MB CD's anymore?
|
|
Top |
|
 |
craigtv
|
Posted: Tue Feb 20, 2007 9:25 pm |
|
Joined: Mon Oct 09, 2006 11:27 am
Posts: 75
Location:
Raleigh, NC
|
randomhtpcguy wrote: Which method is best for getting the source ready for compiling everything it seems people are needing to compile: LIRC, Nvidia drivers, VMWare.
I had to build the kernel source to get the latest ivtv (0.10.0) to build. Option 2 worked for me with one additional step ...
Code: cd /lib/modules/2.6.18-chw-13 rm build ln -s /usr/src/linux-source-2.6.18-chw-13 build
that link was still pointing at the headers, and that was tripping up the make.
|
|
Top |
|
 |