| View previous topic :: View next topic |
| Author |
Message |
nutbar21
Apprentice
Joined: 05 Dec 2004
Posts: 205
Location: USA
|
 Posted: Mon Feb 04, 2008 1:26 am Post subject: |
 |
|
I have the exact same error as above poster with kernel 2.6.24 from portage. If I boot my 2.6.23 kernel I can still compile nvidia-drivers as normal, but that doesn't help me (I need the new kernel for ivtv reasons). Any ideas?
_________________
"Your voice is like the sound of sirens to a house on fire..." -The Alkaline Trio |
|
| Back to top |
|
 |
Xaid
Guru
Joined: 30 Oct 2004
Posts: 474
Location: Edmonton / Alberta
|
| Posted: Wed Feb 06, 2008 5:14 am Post subject: |
|
|
I just ran into the same problem and i think i know the reason its failing. It looks like in 2.6.24, there is no more "include/asm-i386" but we can use "include/asm-x86" (someone correct me if i'm wrong).
I think ideally, nvidia-drivers should be using asm-x86 in this case but that will probably come in the next version.
Doing the following should take care of the errors:
| Code: |
cd /usr/src/linux/include
ln -s asm-x86 asm-i386
|
Let me know if you are still getting errors in building the nvidia-drivers after that. |
|
| Back to top |
|
|
fatcop
n00b
Joined: 14 Mar 2005
Posts: 18
|
| Posted: Wed Feb 13, 2008 2:57 am Post subject: Worked for me. |
|
|
Thaaaank you very much.
FYI:
I had recently upgraded to 2.6.24-r2, copied my old .config from 2.6.19 over and done a "make oldconfig".
Things seemed ok, but got quite a lot of system instability.
I didn't have this problem.
So went thru menuconfig trying to tidy up.
I think I noticed the Processor Family was on PIII (doh!). I have an Athlon, so changed it to that.
That is when I started to have this problem.
Still can't get my nvidia modules to load now, but I guess that is for another thread  |
|
| Back to top |
|
|
bjk2007
n00b
Joined: 05 Mar 2007
Posts: 30
Location: Michigan
|
| Posted: Mon Feb 18, 2008 10:45 pm Post subject: |
|
|
| This issue just came up again for me while installing vmware-server, but I did manage to finally solve my original problem this time. In my case, I had FEATURES="userpriv" set in make.conf, causing insufficient permissions to be present to read the kernel headers during the compile. The simple solution was to just prepend FEATURES="-userpriv" to the emerge command. Hopefully this helps someone out in the future. |
|
| Back to top |
|
|
baldeante
Guru
Joined: 17 Jan 2004
Posts: 498
Location: Caldas da Rainha, Portugal
|
| Posted: Tue May 20, 2008 6:41 pm Post subject: |
|
|
Thanks Xaid this error drove nuts for the last two days ...
_________________
Never Quit, Never Get Mad, Get Even |
|
| Back to top |
|
|
|
Portage & Programming
