There's a new version of nvidia driver available, which (among others) fixes issues with VESA console and notebook LCD panels. It would be neat to have that in portage soon :)
Does a simple copy of the current ebuild work (maybe even with minor tweaking)?
Without a problem. Simply copying the 100.14.09 ebuild works here.
Sorry for hijacking this bug, but please cancel this stupid masking before putting this package into Portage: # beta drivers for testing >x11-drivers/nvidia-drivers-100 This ('>') is a very bad way of masking beta versions - it has actually masked the current stable driver versions (100.14.09 and any newer) too.
See ebuild in bug #182622, which adds a USE flag. Copying the 100.14.09 ebuild works (I'm on x86).
(In reply to comment #3) > Sorry for hijacking this bug, but please cancel this stupid masking before > putting this package into Portage: > > # beta drivers for testing > >x11-drivers/nvidia-drivers-100 > > This ('>') is a very bad way of masking beta versions - it has actually masked > the current stable driver versions (100.14.09 and any newer) too. > This block is still in, even forcing a roll-back on ~amd64. Can this please be taken out?
Created attachment 123223 [details] my xorg.conf file
Comment on attachment 123223 [details] my xorg.conf file hello everybody ! I just bought a geforce 8600gt and put it instead of my geforce6600 which worked like a charm. my screen, a Iiyama 22inches 1680 * 1050 worked well. But since i put the card i do have troubles. The screen turns into standBy once the xserver is loaded and the system seems unusable anymore. I do installed the nv 2.0 drivers and i can use linux now but a lot of programs arent adapted anymore (video, sounds (amarok), etc). Moreover the display is disgusting (1736*1050 instead of 1680*1050). Do you know how i can do to fix that problem ?
(In reply to comment #7) > (From update of attachment 123223 [details] [edit]) > hello everybody ! > > I just bought a geforce 8600gt and put it instead of my geforce6600 which > worked like a charm. my screen, a Iiyama 22inches 1680 * 1050 worked well. > > But since i put the card i do have troubles. The screen turns into standBy once > the xserver is loaded and the system seems unusable anymore. I do installed the > nv 2.0 drivers and i can use linux now but a lot of programs arent adapted > anymore (video, sounds (amarok), etc). Moreover the display is disgusting > (1736*1050 instead of 1680*1050). > > Do you know how i can do to fix that problem ? > I don't see what this has to do with nvidia-drivers. You are using nv, which is the Open Source driver from X.Org. If I remember correctly, a new version of nv which supports 8600GT hasn't been released yet (but can be found in their Git repository). Myself I use an 8600GTS as well, and everything works like a charm using nvidia-drivers-100.14.11, including dual screen setup with or without Xinerama. I also agree on the idea to remove the mask for >x11-drivers/nvidia-drivers-100.
Is there any reason this package isn't in portage? It seems theres an ebuild and its working for everyone(including me) but no one wants to commit.
(In reply to comment #8) > I don't see what this has to do with nvidia-drivers. You are using nv, which is > the Open Source driver from X.Org. If I remember correctly, a new version of nv > which supports 8600GT hasn't been released yet (but can be found in their Git > repository). > > Myself I use an 8600GTS as well, and everything works like a charm using > nvidia-drivers-100.14.11, including dual screen setup with or without Xinerama. > > I also agree on the idea to remove the mask for > >x11-drivers/nvidia-drivers-100. Oh. I needed to use nv driver to be able to use the xserver and mozilla but the nvidia drivers crashes. Just replace nv with nvidia in my xorg.conf file and you'll have the original file. Can you tell me how do you upgraded your videocard / driver please ?
Created attachment 123306 [details] Working xorg.conf
Attached is my working xorg.conf with nvidia-drivers. I didn't update the drivers or graphics card, this is on a new system.
in my mind the problems could deals with that lines : $ lspci 05:00.0 VGA compatible controller: nVidia Corporation Unknown device 0402 (rev a1) should i update something about the pci port ?
>I just bought a geforce 8600gt and put it instead of my geforce6600 which >worked like a charm. my screen, a Iiyama 22inches 1680 * 1050 worked well. > >But since i put the card i do have troubles. The screen turns into standBy once >the xserver is loaded and the system seems unusable anymore. I do installed the >nv 2.0 drivers and i can use linux now but a lot of programs arent adapted >anymore (video, sounds (amarok), etc). Moreover the display is disgusting >(1736*1050 instead of 1680*1050). > >Do you know how i can do to fix that problem ? Hey, check your BIOS, you may need to update it. Has been a problem for some people.
bug fixed thanks to Matt Summers. the msi k8n sli platinum firmware need to be updated before using the videocard with linux (even if it worked with windows XP). maybe we should add a new bug# to explain how to fix it ?
(In reply to comment #15) > bug fixed thanks to Matt Summers. > the msi k8n sli platinum firmware need to be updated before using the videocard > with linux (even if it worked with windows XP). > > maybe we should add a new bug# to explain how to fix it ? > No need to open a bug for that, perhaps you could post a thread on the forums or even better mention it at gentoo-wiki.com.
And regarding the original reason this bug was filed, is there anything that prevents us from a) removing >x11-drivers/nvidia-drivers-100 from package.mask b) adding 100.14.11 (which fixes two major bugs found in .9) to the tree?
(In reply to comment #17) > And regarding the original reason this bug was filed, is there anything that > prevents us from a) removing >x11-drivers/nvidia-drivers-100 from package.mask > b) adding 100.14.11 (which fixes two major bugs found in .9) to the tree? > No not that im aware of. In fact thats what I was trying to ask before.
nvidia-drivers still don't compile with FEATURES="ccache" here.. (see bug http://bugs.gentoo.org/show_bug.cgi?id=137000) ------------ [...] /var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86-100.14.09-pkg0/usr/src/nv/nv-linux.h:825:2: warning: #warning "conftest.sh failed, assuming remap_page_range(4)!" i686-pc-linux-gnu-gcc -Wp,-MD,/var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86-100.14.09-pkg0/usr/src/nv/.nv-i2c.o.d -nostdinc -isystem /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include -D__KERNEL__ -Iinclude -Iinclude2 -I/usr/src/linux-2.6.21-git2/include -include include/linux/autoconf.h -I/var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86-100.14.09-pkg0/usr/src/nv -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -O2 -pipe -msoft-float -mregparm=3 -freg-struct-return -mpreferred-stack-boundary=2 -march=i686 -mtune=i686 -ffreestanding -maccumulate-outgoing-args -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -I/usr/src/linux-2.6.21-git2/include/asm-i386/mach-default -Iinclude/asm-i386/mach-default -fomit-frame-pointer -fno-stack-protector -Wdeclaration-after-statement -Wno-pointer-sign -I/var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86-100.14.09-pkg0/usr/src/nv -Wall -Wimplicit -Wreturn-type -Wswitch -Wformat -Wchar-subscripts -Wparentheses -Wno-multichar -Werror -O -fno-common -msoft-float -MD -Wno-cast-qual -Wno-error -D_LOOSE_KERNEL_NAMES -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"100.14.09\" -UDEBUG -U_DEBUG -DNDEBUG -DNV_SIGNAL_STRUCT_RLIM -DNV_MULTIPLE_BRIDGE_AGPGART_PRESENT -DNV_SYSCTL_MAX_MAP_COUNT_PRESENT -DNV_PM_MESSAGE_T_PRESENT -DNV_OLD_MM_KGDB_BREAKPOINT_PRESENT -DNV_ACPI_DEVICE_OPS_MATCH_PRESENT -DNV_CHANGE_PAGE_ATTR_PRESENT -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(nv_i2c)" -D"KBUILD_MODNAME=KBUILD_STR(nvidia)" -c -o /var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86-100.14.09-pkg0/usr/src/nv/nv-i2c.o /var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86-100.14.09-pkg0/usr/src/nv/nv-i2c.c In file included from /var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86-100.14.09-pkg0/usr/src/nv/nv-i2c.c:8: /var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86-100.14.09-pkg0/usr/src/nv/nv-linux.h:825:2: warning: #warning "conftest.sh failed, assuming remap_page_range(4)!" i686-pc-linux-gnu-gcc -Wp,-MD,/var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86-100.14.09-pkg0/usr/src/nv/.nvacpi.o.d -nostdinc -isystem /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include -D__KERNEL__ -Iinclude -Iinclude2 -I/usr/src/linux-2.6.21-git2/include -include include/linux/autoconf.h -I/var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86-100.14.09-pkg0/usr/src/nv -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -O2 -pipe -msoft-float -mregparm=3 -freg-struct-return -mpreferred-stack-boundary=2 -march=i686 -mtune=i686 -ffreestanding -maccumulate-outgoing-args -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -I/usr/src/linux-2.6.21-git2/include/asm-i386/mach-default -Iinclude/asm-i386/mach-default -fomit-frame-pointer -fno-stack-protector -Wdeclaration-after-statement -Wno-pointer-sign -I/var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86-100.14.09-pkg0/usr/src/nv -Wall -Wimplicit -Wreturn-type -Wswitch -Wformat -Wchar-subscripts -Wparentheses -Wno-multichar -Werror -O -fno-common -msoft-float -MD -Wno-cast-qual -Wno-error -D_LOOSE_KERNEL_NAMES -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"100.14.09\" -UDEBUG -U_DEBUG -DNDEBUG -DNV_SIGNAL_STRUCT_RLIM -DNV_MULTIPLE_BRIDGE_AGPGART_PRESENT -DNV_SYSCTL_MAX_MAP_COUNT_PRESENT -DNV_PM_MESSAGE_T_PRESENT -DNV_OLD_MM_KGDB_BREAKPOINT_PRESENT -DNV_ACPI_DEVICE_OPS_MATCH_PRESENT -DNV_CHANGE_PAGE_ATTR_PRESENT -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(nvacpi)" -D"KBUILD_MODNAME=KBUILD_STR(nvidia)" -c -o /var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86-100.14.09-pkg0/usr/src/nv/nvacpi.o /var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86-100.14.09-pkg0/usr/src/nv/nvacpi.c In file included from /var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86-100.14.09-pkg0/usr/src/nv/nvacpi.c:15: /var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86-100.14.09-pkg0/usr/src/nv/nv-linux.h:825:2: warning: #warning "conftest.sh failed, assuming remap_page_range(4)!" /var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86-100.14.09-pkg0/usr/src/nv/nvacpi.c:47: error: unknown field ‘match’ specified in initializer /var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86-100.14.09-pkg0/usr/src/nv/nvacpi.c:47: warning: initialization from incompatible pointer type make[4]: *** [/var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86-100.14.09-pkg0/usr/src/nv/nvacpi.o] Error 1 make[3]: *** [_module_/var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86-100.14.09-pkg0/usr/src/nv] Error 2 make[2]: *** [modules] Error 2 NVIDIA: left KBUILD. nvidia.ko failed to build! make[1]: *** [module] Error 1 make: *** [module] Error 2 * * ERROR: x11-drivers/nvidia-drivers-100.14.09 failed. * Call stack: * ebuild.sh, line 1642: Called dyn_compile * ebuild.sh, line 988: Called qa_call 'src_compile' * ebuild.sh, line 44: Called src_compile * nvidia-drivers-100.14.09.ebuild, line 207: Called linux-mod_src_compile * linux-mod.eclass, line 516: Called die * * Unable to make IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/2.6.21-git2/build clean module. * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/x11-drivers:nvidia-drivers-100.14.09:20070701-141802.log'. * ------------- when doing an FEATURES="-ccache" emerge nvidia-drivers, everything compiles fine. JG
nvidia drivers havn't compiled for over a year without doing FEATURES="-sandbox" for me. That seems like a portage problem and not a nvidia drivers problem. Upgraded or staying with the current driver aren't going to fix it.
(In reply to comment #9) > Is there any reason this package isn't in portage? It seems theres an ebuild > and its working for everyone(including me) but no one wants to commit. > People are busy. There's lots of issues with the current nvidia setups providing 3 separate series of drivers so there's work that needs to be done. Committing this will break a bunch of other people. If you're complaining about the time frame that this work happens in, you're welcome to become a Gentoo developer as well and contribute back.
(In reply to comment #21) > (In reply to comment #9) > > Is there any reason this package isn't in portage? It seems theres an ebuild > > and its working for everyone(including me) but no one wants to commit. > > > > People are busy. There's lots of issues with the current nvidia setups > providing 3 separate series of drivers so there's work that needs to be done. > Committing this will break a bunch of other people. > > If you're complaining about the time frame that this work happens in, you're > welcome to become a Gentoo developer as well and contribute back. > I didn't mean to sound pushy what I was getting at is usually when developers don't put something like the nvidia drivers in its because they break something (doesn't work with newer or older kernels etc). Since I'm using them along with a number of other people I was wondering if that was why there aren't in. If its because no one has time that fine.
> providing 3 separate series of drivers I would suggest, masking all the nvidia drivers as unstable, creating a Gentoo page showing the current situation, and letting users mask/unmask their own versions to best fit their own video cards. Nvidia created this mess, and prolonged it, and will probably change the rules in the future. Keep Gentoo flexible and fast-reacting. Anyone who doubts that *all* the nvidia versions are unstable in one way or another, can view the horror show at: http://www.nvnews.net/vbulletin/forumdisplay.php?f=14
Any reason why the ebuild version can't be bumped? Especially as it is still masked and keyworded unstable...
if you would like to criticize the speed at which Gentoo development happens, I encourage you to become a developer yourself. Otherwise, I'm sure you can contact a developer and they would happily do some consulting work for you on the side. If none of these options appeal to you, please setup your own local overlay. The issue will be addressed when it's addressed. There are more important things being worked on with the nvidia drivers then a minor "omg I DON'T HAVE THE LATEST VERSION" bug.
As long as I don't have to be available and active all the time, reading hundreds of mailinglist posts or similar, I don't mind becoming one. Where do I need to sign up?
Please take this off-topic stuff to http://forums.gentoo.org/ rather than polluting this bug. This bug is about nvidia-drivers and NOTHING ELSE.
On building on my system, I get lots of: /usr/lib/opengl/nvidia/lib/libGL.so.1: undefined reference to `_nv000330gl' While building nVidia-settings. It would appear this happens if eselect opengl set xorg-x11 is run before emerge nvidia-settings. No problems if opengl is set to nvidia. Because the nvidia-settings are now wrapped up in the driver build, this is likely to happen on any fresh system that doesn't have the drivers already installed. Is there a reason why they are now bundled together? Looks like it might cause a few headaches.
This version doesn't build on gentoo-sources-2.6.22 && linux-headers-2.6.22... i686-pc-linux-gnu-gcc -Wp,-MD,/var/tmp/portage/x11-drivers/nvidia-drivers-100.14.11/work/NVIDIA-Linux-x86-100.14.11-pkg0/usr/src/nv/.nv-vm.o.d -nostdinc -isystem /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include -D__KERNEL__ -Iinclude -include include/linux/autoconf.h -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -O2 -pipe -msoft-float -mregparm=3 -freg-struct-return -mpreferred-stack-boundary=2 -march=i686 -mtune=pentium4 -ffreestanding -maccumulate-outgoing-args -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -Iinclude/asm-i386/mach-default -fomit-frame-pointer -fno-stack-protector -Wdeclaration-after-statement -Wno-pointer-sign -I/var/tmp/portage/x11-drivers/nvidia-drivers-100.14.11/work/NVIDIA-Linux-x86-100.14.11-pkg0/usr/src/nv -Wall -Wimplicit -Wreturn-type -Wswitch -Wformat -Wchar-subscripts -Wparentheses -Wno-multichar -Werror -O -fno-common -msoft-float -MD -Wno-cast-qual -Wno-error -D_LOOSE_KERNEL_NAMES -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"100.14.11\" -UDEBUG -U_DEBUG -DNDEBUG -DNV_SIGNAL_STRUCT_RLIM -DNV_MULTIPLE_BRIDGE_AGPGART_PRESENT -DNV_PCI_GET_CLASS_PRESENT -DNV_SYSCTL_MAX_MAP_COUNT_PRESENT -DNV_PM_MESSAGE_T_PRESENT -DNV_OLD_MM_KGDB_BREAKPOINT_PRESENT -DNV_ACPI_DEVICE_OPS_MATCH_PRESENT -DNV_REMAP_PFN_RANGE_PRESENT -DNV_CHANGE_PAGE_ATTR_PRESENT -DNV_VMAP_2_PRESENT -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(nv_vm)" -D"KBUILD_MODNAME=KBUILD_STR(nvidia)" -c -o /var/tmp/portage/x11-drivers/nvidia-drivers-100.14.11/work/NVIDIA-Linux-x86-100.14.11-pkg0/usr/src/nv/.tmp_nv-vm.o /var/tmp/portage/x11-drivers/nvidia-drivers-100.14.11/work/NVIDIA-Linux-x86-100.14.11-pkg0/usr/src/nv/nv-vm.c /var/tmp/portage/x11-drivers/nvidia-drivers-100.14.11/work/NVIDIA-Linux-x86-100.14.11-pkg0/usr/src/nv/nv-vm.c: In function ‘nv_vmap’: /var/tmp/portage/x11-drivers/nvidia-drivers-100.14.11/work/NVIDIA-Linux-x86-100.14.11-pkg0/usr/src/nv/nv-vm.c:717: error: too few arguments to function ‘vmap’ make[3]: *** [/var/tmp/portage/x11-drivers/nvidia-drivers-100.14.11/work/NVIDIA-Linux-x86-100.14.11-pkg0/usr/src/nv/nv-vm.o] Error 1 make[2]: *** [_module_/var/tmp/portage/x11-drivers/nvidia-drivers-100.14.11/work/NVIDIA-Linux-x86-100.14.11-pkg0/usr/src/nv] Error 2 NVIDIA: left KBUILD. nvidia.ko failed to build! make[1]: *** [module] Error 1 make: *** [module] Error 2 * * ERROR: x11-drivers/nvidia-drivers-100.14.11 failed. * Call stack: * ebuild.sh, line 1647: Called dyn_compile * ebuild.sh, line 988: Called qa_call 'src_compile' * ebuild.sh, line 44: Called src_compile * nvidia-drivers-100.14.11.ebuild, line 217: Called linux-mod_src_compile * linux-mod.eclass, line 516: Called die * * Unable to make IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/usr/src/linux clean module. * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-100.14.11/temp/build.log'. *
Seems to be a parallel build issue: with MAKEOPTS="-j1" it compiles successfully... It is probably better to disable parallel make for this package.
A too few arguments for function XYZ error is not solved by just doing MAKEOPTS=-j1, that's a code issue. Something else was your fix.
(In reply to comment #31) > A too few arguments for function XYZ error is not solved by just doing > MAKEOPTS=-j1, that's a code issue. Something else was your fix. > Yep :P I did some deeper investigations: it seems that conftest.sh is completely broken. Its results are varying randomly each time I (fail to) re-emerge =nvidia-drivers-100.14*... Some examples follow: 1) pci_get_class() is not found and pci_find_class() is used in its place, but I do have pci_get_class, *not* pci_find_class(), so the build process produces a kernel module that is not loadable because of missing pci_find_class symbol; 2) I modified Makefile.kbuild to make it always use pci_get_class(), ignoring what conftest.sh says; this patch resulted in a very weird behaviour of the compiler: I got an error about a wrong initializer in nvacpi.c, but identifiers in gcc output were composed of strange non-human-readable characters; 3) I tried to recompile various versions (ranging from 1.0.9755-r1 to 100.14.11) of nvidia-drivers many times, always failing. 1) 2) and 3) have been done on gentoo-sources-2.6.22-r1 without X running. After that I rebooted in 2.6.21-r3, *with* X, and this time nvidia-drivers-100.14.11 + my patch compiled fine! Very strange... :s
And the build error in comment #29 is probably caused by conftest.sh, that is unable to correctly detect vmap()'s number of parameters...
This bug was originally for the bump to 100.14.11 which have been available in the tree. Marking as fixed. Any issues you may have with them should be opened as a new bug.
