| View previous topic :: View next topic |
| Author |
Message |
leyoy n00b

Joined: 06 Oct 2010 Posts: 26 Location: France
|
Posted: Thu Oct 14, 2010 8:28 am Post subject: [SOLVED]problem with nvidia-drivers and rt kernel |
|
|
Hi everyone
I have a rt-kernel:
(I want to build a music system)
I have this hardware:
| Code: | | 05:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8400M GS] (rev a1) |
and try to emerge nvidia-drivers but there is ERRORS.
Here is part of /var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/temp/build.log
| Code: |
ERROR: kernel configuration is invalid
include/generated/autoconf.h or include/config/auto.conf are missing.
Run 'make oldconfig && make prepare' on kernel src to fix it.
make[4]: *** [/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/
usr/src/nv/nv.o] ERROR 1
make[3]: *** [_module_/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/
usr/src/nv] ERROR 2
make[2]: *** [sub-make] ERROR 2
NVIDIA: left KBUILD.
nvidia.ko failed to build
make[1] *** [module] ERROR 1
make: *** [module] ERROR 2
* ERROR: x11-drivers/nvidia-drivers-195.36.31 failed
* Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= IGNORE_CC_MISMATCH=yes
v=1 SYSSRC=/usr/src/linux
SYSOUT=/lib/modules/2.6.33.7-rt29/build HOST_CC=x86_64-pc-linux-gnu-gcc CC=x86_64-pc-linux-gnu-gcc clean module
*
* Call stack:
* ebuild.sh, line 54: Called src_compile
* environment, line 4121: Called linux_mod_src_compile
* environment, line 3051: Called die
* The specific snippet of code:
* eval "emake HOSTCC=\"$(tc-getBUILD_CC)\"
CROSS_COMPILE=${CHOST}-
LDFLAGS=\"$(get_abi_LDFLAGS)\"
${BUILD_FIXES} ${BUILD_PARAMS}
${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)"
${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS};
*
* If you need support, post post the output of 'emerge --info =x11-drivers/nvidia-drivers-195.36.31'.
* The complete build log and the output of 'emerge -pqv = x11-drivers/nvidia-drivers-195.36.31'.
* The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/temp/build.log'
* The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/temp/environment'.
* S: '/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-linux-x86_64-195.36.31-pkg2'
|
If I do:
| Code: | | make oldconfig && make prepare |
It does nothing more
Can you help me to install these drivers ?
Thank you.
Last edited by leyoy on Sun Oct 17, 2010 7:16 pm; edited 1 time in total |
|
| Back to top |
|
 |
krinn Watchman


Joined: 02 May 2003 Posts: 7470
|
|
| Back to top |
|
 |
chiefbag Guru


Joined: 01 Oct 2010 Posts: 542 Location: The Kingdom
|
Posted: Thu Oct 14, 2010 1:41 pm Post subject: |
|
|
You should disable the following in the kernel.
Device Drivers --->
Graphics support --->
< > nVidia Framebuffer Support
< > nVidia Riva support |
|
| Back to top |
|
 |
leyoy n00b

Joined: 06 Oct 2010 Posts: 26 Location: France
|
Posted: Thu Oct 14, 2010 7:31 pm Post subject: |
|
|
Thanks for your answers:
I had already deselected nVidia Framebuffer Support and nVidia Riva support when I compiled the kernel.
| Code: | | eselect kernel list |
return this:
| Code: |
Available kernel symlink targets:
[1] linux-2.6.33.7-rt29 *
|
So every thing seams to be OK.
Why doens't it work ?
Any another Ideas ? |
|
| Back to top |
|
 |
krinn Watchman


Joined: 02 May 2003 Posts: 7470
|
Posted: Thu Oct 14, 2010 11:55 pm Post subject: |
|
|
eselect is good, but you still need to check that your sources are present |
|
| Back to top |
|
 |
leyoy n00b

Joined: 06 Oct 2010 Posts: 26 Location: France
|
Posted: Fri Oct 15, 2010 8:28 am Post subject: |
|
|
Thanks for your help,
I have read the post, thanks but it's not the same kind of error ...
But if I understand you, if I will upgrade my kernel I will loose my .config, that's it ?
| Code: |
linux linux-2.6.33.7-rt29
|
So I think I have the sources.
My question is:
where do I 'make oldconfig && make prepare' is it in the linux' link ?
And the other question is:
After do make oldconfig && make prepare what must I do ?
Thanks for your answers |
|
| Back to top |
|
 |
cach0rr0 Bodhisattva


Joined: 13 Nov 2008 Posts: 4123 Location: Houston, Republic of Texas
|
Posted: Fri Oct 15, 2010 8:42 am Post subject: |
|
|
| leyoy wrote: |
My question is:
where do I 'make oldconfig && make prepare' is it in the linux' link ?
|
yes. under /usr/src/linux
make oldconfig assumes you already have a .config file in /usr/src/linux
if you don't, it will ask you a boatload of questions - if it does this, stop, ask for help
| leyoy wrote: |
And the other question is:
After do make oldconfig && make prepare what must I do ?
Thanks for your answers |
emerge nvidia-drivers
post back with any errors _________________ Lost configuring your system?
dump lspci -n here | see Pappy's guide | Link Stash |
|
| Back to top |
|
 |
leyoy n00b

Joined: 06 Oct 2010 Posts: 26 Location: France
|
Posted: Fri Oct 15, 2010 9:40 am Post subject: |
|
|
Ok thanks,
even if I do the commands 'make oldconfig && make prepare' I can't install drivers:
Log asks me again to do 'make oldconfig && make prepare'.
It's what I mean on the first post.
I have read somewhere that there is some problem to install nvidia-drivers with a rt-kernel.
Any suggestion |
|
| Back to top |
|
 |
cach0rr0 Bodhisattva


Joined: 13 Nov 2008 Posts: 4123 Location: Houston, Republic of Texas
|
Posted: Fri Oct 15, 2010 9:55 am Post subject: |
|
|
to ask the possibly obvious question - do those files exist for you, at all?
| Code: |
# find /usr/src/linux/include -type f -iname 'autoconf.h' -or -iname 'auto.conf'
/usr/src/linux/include/generated/autoconf.h
/usr/src/linux/include/config/auto.conf
|
and as of right now we don't know what exists in your kernel source directory
-we know that /usr/src/linux-2.6.33.7-rt29 is an existing directory
-we know that /usr/src/linux is a symlink to /usr/src/linux-2.6.33.7-rt29
-we do not know the contents of /usr/src/linux. Seeing just an 'ls' and/or 'du -sh' of /usr/src/linux/ might be worthwhile
-whenever you unmerge blah-sources, the directory does not get deleted. So you could, for example, unmerge rt-sources, and you would still have a /usr/src/linux-2.6.33.7-rt29 directory, that isn't completely empty. Maybe a --depclean went wrong somewhere? Who knows. But we should verify the actual *source itself* for the kernel exists in that directory, not just the directory. For example, go to /usr/src/linux/drivers, and do a find . |wc -l. For me this returns 13752. Doing this on just /usr/src/linux returns 42693. Not an exact science, but if you only have a few dozen, you are missing loads of stuff. _________________ Lost configuring your system?
dump lspci -n here | see Pappy's guide | Link Stash |
|
| Back to top |
|
 |
leyoy n00b

Joined: 06 Oct 2010 Posts: 26 Location: France
|
Posted: Fri Oct 15, 2010 12:05 pm Post subject: |
|
|
Thanks for your help
if I do:
| Code: | | find /usr/src/linux/include -type f -iname 'autoconf.h' -or -iname 'auto.conf' |
I have this:
| Code: |
/usr/src/linux/include/generated/autoconf.h
/usr/src/linux/include/config/auto.conf
|
ls /usr/src/linux give me:
| Code: |
COPYING README firmware mm security
CREDITS REPORTING-BUGS fs modules.builtin sound
Documentation System.map include modules.order tools
Kbuild arch init net usr
MAINTAINERS block ipc patches.txt virt
Makefile crypto kernel samples vmlinux
Module.symvers drivers lib scripts vmlinux.o
|
here's the command find . | wc -l in some directories:
| Code: |
drivers=1624 arch=14268 block=75 crypto=160 firmware=218 fs=2197 include=3762
init=35 ipc=43 kernel=521 lib=318 mm=170 net=1912 samples=25
scripts=275 security=202 sound=1626 tools=183 usr=20 virt=13
|
on /usr/src/linux:
I don't know if it will help you |
|
| Back to top |
|
 |
cach0rr0 Bodhisattva


Joined: 13 Nov 2008 Posts: 4123 Location: Houston, Republic of Texas
|
Posted: Fri Oct 15, 2010 9:40 pm Post subject: |
|
|
hrm...your sources are there, they are fine
Can you upload the entire build log somewhere? (e.g. pastebin)
I'm interested in seeing the text far above the part that says 'ERROR'
I think the error is possibly misleading.
May even be a problem with linux-headers. _________________ Lost configuring your system?
dump lspci -n here | see Pappy's guide | Link Stash |
|
| Back to top |
|
 |
leyoy n00b

Joined: 06 Oct 2010 Posts: 26 Location: France
|
Posted: Sat Oct 16, 2010 5:54 pm Post subject: |
|
|
Well here is all the log !
Thank you to help me
| Code: |
[32;01m*[0m CPV: x11-drivers/nvidia-drivers-195.36.31
[32;01m*[0m REPO: gentoo
[32;01m*[0m USE: amd64 elibc_glibc gtk kernel_linux multilib userland_GNU
[32;01m*[0m Determining the location of the kernel source code
[32;01m*[0m Found kernel source directory:
[32;01m*[0m /usr/src/linux
[32;01m*[0m Found kernel object directory:
[32;01m*[0m /lib/modules/2.6.33.7-rt29/build
[32;01m*[0m Found sources for kernel version:
[32;01m*[0m 2.6.33.7-rt29
[32;01m*[0m Checking for MTRR support ...
[A[72C [34;01m[ [32;01mok[34;01m ][0m
>>> Unpacking source...
>>> Unpacking NVIDIA-Linux-x86_64-195.36.31-pkg2.run to /var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2
>>> Source unpacked in /var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work
>>> Preparing source in /var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2 ...
[32;01m*[0m Applying NVIDIA_glx-defines.patch ...
[A[72C [34;01m[ [32;01mok[34;01m ][0m
[32;01m*[0m Applying NVIDIA_glx-glheader.patch ...
[A[72C [34;01m[ [32;01mok[34;01m ][0m
[32;01m*[0m Applying 195.30-unified-arch.patch ...
[A[72C [34;01m[ [32;01mok[34;01m ][0m
[32;01m*[0m Converting NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/Makefile.kbuild to use M= instead of SUBDIRS= ...
[A[72C [34;01m[ [32;01mok[34;01m ][0m
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2 ...
[32;01m*[0m Preparing nvidia module
make HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/2.6.33.7-rt29/build HOST_CC=x86_64-pc-linux-gnu-gcc CC=x86_64-pc-linux-gnu-gcc clean module
NVIDIA: calling KBUILD...
make -C /lib/modules/2.6.33.7-rt29/build \
KBUILD_SRC=/usr/src/linux-2.6.33.7-rt29 \
KBUILD_EXTMOD="/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv" -f /usr/src/linux-2.6.33.7-rt29/Makefile \
modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo; \
echo " ERROR: Kernel configuration is invalid."; \
echo " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo; \
/bin/false)
mkdir -p /var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/.tmp_versions ; rm -f /var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/.tmp_versions/*
make -f /usr/src/linux-2.6.33.7-rt29/scripts/Makefile.build obj=/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv
x86_64-pc-linux-gnu-gcc -Wp,-MD,/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/.nv.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.3/include -I/usr/src/linux-2.6.33.7-rt29/arch/x86/include -Iinclude -I/usr/src/linux-2.6.33.7-rt29/include -include include/generated/autoconf.h -I/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m64 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -Wframe-larger-than=2048 -fno-stack-protector -fno-omit-frame-pointer -fno-optimize-sibling-calls -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-dwarf2-cfi-asm -fconserve-stack -I/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv -Wall -Wimplicit -Wreturn-type -Wswitch -Wformat -Wchar-subscripts -Wparentheses -Wno-multichar -Werror -mcmodel=kernel -mno-red-zone -fno-defer-pop -MD -Wno-cast-qual -Wno-error -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"195.36.31\" -UDEBUG -U_DEBUG -DNDEBUG -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(nv)" -D"KBUILD_MODNAME=KBUILD_STR(nvidia)" -c -o /var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/.tmp_nv.o /var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c
In file included from /var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:14:
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv-linux.h:219: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'nv_spinlock_t'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv-linux.h:1274: error: expected specifier-qualifier-list before 'nv_spinlock_t'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv-linux.h:1349: error: expected specifier-qualifier-list before 'nv_spinlock_t'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'verify_pci_bars':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:212: error: 'nv_linux_state_t' has no member named 'next'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nvos_proc_create':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:659: error: 'nv_linux_state_t' has no member named 'next'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nvl_add_alloc':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:865: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:868: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nvidia_init_module':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:1509: error: 'nv_linux_state_t' has no member named 'next'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:1681: error: 'nv_linux_state_t' has no member named 'next'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:1715: error: 'nv_linux_state_t' has no member named 'next'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nvidia_exit_module':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:1758: error: 'nv_linux_state_t' has no member named 'next'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:1821: error: 'nv_linux_state_t' has no member named 'next'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nv_alloc_file_private':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2012: error: implicit declaration of function 'semaphore_init'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2013: error: 'nv_file_private_t' has no member named 'waitqueue'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2014: error: implicit declaration of function 'atomic_spin_lock_init'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2014: error: 'nv_file_private_t' has no member named 'fp_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nv_kern_open':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2092: error: 'nv_linux_state_t' has no member named 'device_num'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2094: error: 'nv_linux_state_t' has no member named 'next'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2106: error: 'nv_linux_state_t' has no member named 'ldata_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2262: error: 'nv_linux_state_t' has no member named 'ldata_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nv_kern_close':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2325: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2336: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2344: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2350: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2352: error: 'nv_linux_state_t' has no member named 'ldata_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2395: error: 'nv_linux_state_t' has no member named 'ldata_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nv_kern_mmap':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2627: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2639: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2648: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2655: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2681: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2687: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2707: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2716: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2725: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2732: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nv_kern_poll':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2796: error: 'nv_file_private_t' has no member named 'waitqueue'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2799: error: implicit declaration of function 'atomic_spin_lock_irqsave'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2799: error: 'nv_file_private_t' has no member named 'fp_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2810: error: implicit declaration of function 'atomic_spin_unlock_irqrestore'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2810: error: 'nv_file_private_t' has no member named 'fp_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nv_kern_ioctl':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:2960: error: 'nv_linux_state_t' has no member named 'next'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nv_kern_ctl_open':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:3175: error: 'nv_linux_state_t' has no member named 'ldata_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:3195: error: 'nv_linux_state_t' has no member named 'ldata_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nv_kern_ctl_close':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:3217: error: 'nv_linux_state_t' has no member named 'ldata_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:3229: error: 'nv_linux_state_t' has no member named 'ldata_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nv_alloc_kernel_mapping':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:3690: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:3709: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:3724: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:3730: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:3734: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nv_free_pages':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4068: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4083: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4088: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nv_lock_init_locks':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4143: error: 'nv_linux_state_t' has no member named 'rm_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4145: error: 'nv_linux_state_t' has no member named 'ldata_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4146: error: 'nv_linux_state_t' has no member named 'at_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4153: error: 'nv_linux_state_t' has no member named 'rm_lock_cpu'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4154: error: 'nv_linux_state_t' has no member named 'rm_lock_count'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nv_lock_rm':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4167: error: 'nv_linux_state_t' has no member named 'rm_lock_cpu'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4169: error: 'nv_linux_state_t' has no member named 'rm_lock_count'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4175: error: implicit declaration of function 'atomic_spin_unlock_wait'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4175: error: 'nv_linux_state_t' has no member named 'rm_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4176: error: implicit declaration of function 'atomic_spin_lock_irq'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4176: error: 'nv_linux_state_t' has no member named 'rm_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4178: error: 'nv_linux_state_t' has no member named 'rm_lock_cpu'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4179: error: 'nv_linux_state_t' has no member named 'rm_lock_count'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nv_unlock_rm':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4189: error: 'nv_linux_state_t' has no member named 'rm_lock_count'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4192: error: 'nv_linux_state_t' has no member named 'rm_lock_cpu'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4193: error: implicit declaration of function 'atomic_spin_unlock_irq'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4193: error: 'nv_linux_state_t' has no member named 'rm_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nv_post_event':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4220: error: 'nv_file_private_t' has no member named 'fp_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4237: error: 'nv_file_private_t' has no member named 'waitqueue'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4238: error: 'nv_file_private_t' has no member named 'fp_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nv_get_event':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4253: error: 'nv_file_private_t' has no member named 'fp_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4256: error: 'nv_file_private_t' has no member named 'fp_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4281: error: 'nv_file_private_t' has no member named 'fp_lock'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nv_kern_probe':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4709: error: 'nv_linux_state_t' has no member named 'next'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4709: error: 'nv_linux_state_t' has no member named 'next'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4710: error: 'nv_linux_state_t' has no member named 'next'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4713: error: 'nv_linux_state_t' has no member named 'device_num'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4832: error: 'nv_linux_state_t' has no member named 'next'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4836: error: 'nv_linux_state_t' has no member named 'next'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4836: error: 'nv_linux_state_t' has no member named 'next'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4837: error: 'nv_linux_state_t' has no member named 'next'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:4837: error: 'nv_linux_state_t' has no member named 'next'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c: In function 'nv_get_adapter_state':
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.c:5154: error: 'nv_linux_state_t' has no member named 'next'
make[4]: *** [/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv.o] Error 1
make[3]: *** [_module_/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv] Error 2
make[2]: *** [sub-make] Error 2
NVIDIA: left KBUILD.
nvidia.ko failed to build!
make[1]: *** [module] Error 1
make: *** [module] Error 2
[31;01m*[0m ERROR: x11-drivers/nvidia-drivers-195.36.31 failed:
[31;01m*[0m Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/2.6.33.7-rt29/build HOST_CC=x86_64-pc-linux-gnu-gcc CC=x86_64-pc-linux-gnu-gcc clean module
[31;01m*[0m
[31;01m*[0m Call stack:
[31;01m*[0m ebuild.sh, line 54: Called src_compile
[31;01m*[0m environment, line 4121: Called linux-mod_src_compile
[31;01m*[0m environment, line 3051: Called die
[31;01m*[0m The specific snippet of code:
[31;01m*[0m eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" CROSS_COMPILE=${CHOST}- LDFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}";
[31;01m*[0m
[31;01m*[0m If you need support, post the output of 'emerge --info =x11-drivers/nvidia-drivers-195.36.31',
[31;01m*[0m the complete build log and the output of 'emerge -pqv =x11-drivers/nvidia-drivers-195.36.31'.
[31;01m*[0m The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/temp/build.log'.
[31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/temp/environment'.
[31;01m*[0m S: '/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2'
|
Tell me what doesn't work. |
|
| Back to top |
|
 |
cach0rr0 Bodhisattva


Joined: 13 Nov 2008 Posts: 4123 Location: Houston, Republic of Texas
|
Posted: Sat Oct 16, 2010 8:48 pm Post subject: |
|
|
ah right
so you aren't actually getting an error about those files missing
notice the 'test -e' bit before that string you posted:
| Code: |
test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo; \
echo " ERROR: Kernel configuration is invalid."; \
echo " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo;
|
That's just saying it will echo that if those files are missing
The actual errors that are causing your build failure look like this:
| Code: |
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv-linux.h:219: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'nv_spinlock_t'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv-linux.h:1274: error: expected specifier-qualifier-list before 'nv_spinlock_t'
/var/tmp/portage/x11-drivers/nvidia-drivers-195.36.31/work/NVIDIA-Linux-x86_64-195.36.31-pkg2/usr/src/nv/nv-linux.h:1349: error: expected specifier-qualifier-list before 'nv_spinlock_t'
|
What you're likely running into is tihs: https://bugs.gentoo.org/show_bug.cgi?id=308945
I'll read through that log snippet above as time permits and confirm one way or another. _________________ Lost configuring your system?
dump lspci -n here | see Pappy's guide | Link Stash |
|
| Back to top |
|
 |
leyoy n00b

Joined: 06 Oct 2010 Posts: 26 Location: France
|
Posted: Sat Oct 16, 2010 9:17 pm Post subject: |
|
|
Thanks a lot for your help.
Here's all the soft that I have emerge perhaps there is a way in this ...
| Code: | links, rt-sources, layman, subversion, dhcpcd, syslog-ng, logrotate, slocate, grub, xorg-server, xf86-video-nv, nouveau, vesa,
fbdev |
|
|
| Back to top |
|
 |
cach0rr0 Bodhisattva


Joined: 13 Nov 2008 Posts: 4123 Location: Houston, Republic of Texas
|
Posted: Sat Oct 16, 2010 10:32 pm Post subject: |
|
|
ok, I don't have an nvidia machine I can test this with, so unfortunately I have not tried this myself, but I've edited the existing ebuild to use the patch from that bug (and threw it on my web server to make things easier)
instructions are as such
-su to root if you havent already
(you can copy and paste these)
| Code: |
mkdir -p /root/overlays/rt-nvidia/x11-drivers/nvidia-drivers/files
cp -r /usr/portage/x11-drivers/nvidia-drivers/files/* /root/overlays/rt-nvidia/x11-drivers/nvidia-drivers/files/
cd /root/overlays/rt-nvidia/x11-drivers/nvidia-drivers
wget http://whitehathouston.com/gentoo/nvidia-drivers-195.36.31.ebuild
cd files/
wget http://whitehathouston.com/gentoo/nvidia-drivers-195.36-2.6.33-rt.patch
cd ..
ebuild nvidia-drivers-195.36.31.ebuild digest
|
now edit your /etc/make.conf, and add the following:
| Code: |
PORTDIR_OVERLAY="/root/overlays/rt-nvidia"
|
Then try emerge -pv nvidia-drivers, make sure it looks like it will use the one from the local overlay. If so, go ahead and remove the -p, and emerge -v nvidia-drivers
Post back one way or another and let me know if you have any errors, or if the build is successful. _________________ Lost configuring your system?
dump lspci -n here | see Pappy's guide | Link Stash |
|
| Back to top |
|
 |
leyoy n00b

Joined: 06 Oct 2010 Posts: 26 Location: France
|
Posted: Sun Oct 17, 2010 7:16 pm Post subject: |
|
|
You are great
It works !! The nvidia drivers have been installed now !!
I was scared, cause the same message "make oldconfig bla bla bla ..." start again, but after that everythings was good.
Thank you very much.
ps: If other people have the same problem, could they do the same things, will you let the patch on your site ? |
|
| Back to top |
|
 |
cach0rr0 Bodhisattva


Joined: 13 Nov 2008 Posts: 4123 Location: Houston, Republic of Texas
|
Posted: Mon Oct 18, 2010 8:16 am Post subject: |
|
|
yep, ill leave it on my site.
Actually I think the best thing to do would, if possible, have the maintainers of the pro-audio overlay maintain their own ebuild for the nvidia-drivers package
I don't know who maintains it, but I'll ask around and see.
Glad it's working, especially since I couldn't test it at all myself  _________________ Lost configuring your system?
dump lspci -n here | see Pappy's guide | Link Stash |
|
| Back to top |
|
 |
LEVIAYAN n00b

Joined: 10 Aug 2010 Posts: 2
|
Posted: Fri Nov 19, 2010 9:07 am Post subject: |
|
|
Thanks cach0rr0, it works fine for me,
Yann |
|
| Back to top |
|
 |
McGruff Tux's lil' helper


Joined: 28 Dec 2004 Posts: 148
|
Posted: Thu Dec 02, 2010 4:09 am Post subject: |
|
|
Worked for me too - many thanks  |
|
| Back to top |
|
 |
cach0rr0 Bodhisattva


Joined: 13 Nov 2008 Posts: 4123 Location: Houston, Republic of Texas
|
Posted: Thu Dec 02, 2010 9:04 am Post subject: |
|
|
glad it's working for people
I've been somewhat away and busy with work life. I did chat to the overlay folks, I need to make some changes to that ebuild before I can submit it it to the overlay folks. Namely, I need to make the ebuild check and make sure someone is running rt-sources before applying the patch. I don't know how to do that, and at the moment don't have much time for reading doc.
Anyone else wants to have a go at that while I'm partially out of commission, have at it! _________________ Lost configuring your system?
dump lspci -n here | see Pappy's guide | Link Stash |
|
| Back to top |
|
 |
McGruff Tux's lil' helper


Joined: 28 Dec 2004 Posts: 148
|
Posted: Thu Dec 02, 2010 3:35 pm Post subject: |
|
|
I don't have much bash experience but what about:
| Code: | | eselect kernel list | grep "*" | grep "\-rt" |
This relies on rt kernels always having an "-rt" in the name, and no other kind of kernel having an "-rt" in the name. Anyone know if that could produce false positives? |
|
| Back to top |
|
 |
|