Summary: | media-video/nvidia-settings[stable-versions] do not compile against x11-drivers/nvidia-drivers-96.* and 173.14.XX | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Carter Young <ecyoung> |
Component: | Current packages | Assignee: | Christian Ruppert (idl0r) <idl0r> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | ecyoung, hrabe, mattsch, pappy_mcfae, tokenmathematician, xmw, xyzzy |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/539196 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Build Log
Alberto Milone's patch - See Comment Build log for initial version in portage |
Description
Carter Young
2010-05-25 05:19:40 UTC
Created attachment 232817 [details]
Build Log
Build.log from 185.xx Series.
Created attachment 232819 [details, diff]
Alberto Milone's patch - See Comment
This patch has been included in Ubuntu's build. I believe Gentoo may benefit from this also.
Hello Carter, have you tried older/really old versions of media-video/nvidia-settings? media-video/nvidia-settings versions loosly relate to x11-drivers/nvidia-drivers versions, and pulling an really old driver should be accompanied by pulling the corresponding settings tool. I can assign this to the maintainer, but i would rather improve the doc about masking nvidia-settings too. If any version works w/o this patch. Thanks, Michael Created attachment 234499 [details]
Build log for initial version in portage
Added the following to /etc/paludis/package_mask.conf and /etc/portage/package.mask. Please note that there is no nvidia-seettings tool matching the 96.xx series of drivers, so I masked every version above the initial package in portage. Both paludis and portage crash at the same spot on compilation. If you open this file in any text editor and enable line numbers the line is 113. I have yet to downgrade X Server to 1.6.5 because doing so wastes time due to having to mask and reinstall based on the following list:
#>=x11-base/xorg-server-1.7.1
#>=x11-libs/libdmx-1.1.0
#>=x11-proto/dmxproto-2.3
#>=x11-apps/xinput-1.5.0
#>=x11-base/xorg-drivers-1.7
#>=x11-libs/libX11-1.3.2
#>=x11-libs/libXScrnSaver-1.2.0
#>=x11-libs/libXext-1.1.1
#>=x11-libs/libXi-1.3
#>=x11-libs/libXinerama-1.1
#>=x11-libs/libXtst-1.1.0
#>=x11-libs/libXxf86dga-1.1.1
#>=x11-libs/libXxf86vm-1.1.0
#>=x11-proto/bigreqsproto-1.1.0
#>=x11-proto/fixesproto-4.1.1
#>=x11-proto/inputproto-2.0
#>=x11-proto/recordproto-1.14
#>=x11-proto/scrnsaverproto-1.2.0
#>=x11-proto/xcmiscproto-1.2.0
#>=x11-proto/xextproto-7.1.1
#>=x11-proto/xf86bigfontproto-1.2.0
#>=x11-proto/xf86dgaproto-2.1
#>=x11-proto/xf86driproto-2.1.0
#>=x11-proto/xf86vidmodeproto-2.3
#>=x11-proto/xineramaproto-1.2
#>=media-libs/mesa-7.7.1
#>=x11-apps/mesa-progs-7.7
Notice these are commented for when I have time. I can't now as I am using this machine for online coursework. If someone would add these to their package.mask and attempt an emerge, it would help
(In reply to comment #4) > Created an attachment (id=234499) [details] > Build log for initial version in portage > > Added the following to /etc/paludis/package_mask.conf and > /etc/portage/package.mask. Please note that there is no nvidia-seettings tool > matching the 96.xx series of drivers, so I masked every version above the > initial package in portage. Both paludis and portage crash at the same spot on > compilation. If you open this file in any text editor and enable line numbers > the line is 113. I have yet to downgrade X Server to 1.6.5 because doing so > wastes time due to having to mask and reinstall based on the following list: > #>=x11-base/xorg-server-1.7.1 > #>=x11-libs/libdmx-1.1.0 > #>=x11-proto/dmxproto-2.3 > #>=x11-apps/xinput-1.5.0 > #>=x11-base/xorg-drivers-1.7 > #>=x11-libs/libX11-1.3.2 > #>=x11-libs/libXScrnSaver-1.2.0 > #>=x11-libs/libXext-1.1.1 > #>=x11-libs/libXi-1.3 > #>=x11-libs/libXinerama-1.1 > #>=x11-libs/libXtst-1.1.0 > #>=x11-libs/libXxf86dga-1.1.1 > #>=x11-libs/libXxf86vm-1.1.0 > #>=x11-proto/bigreqsproto-1.1.0 > #>=x11-proto/fixesproto-4.1.1 > #>=x11-proto/inputproto-2.0 > #>=x11-proto/recordproto-1.14 > #>=x11-proto/scrnsaverproto-1.2.0 > #>=x11-proto/xcmiscproto-1.2.0 > #>=x11-proto/xextproto-7.1.1 > #>=x11-proto/xf86bigfontproto-1.2.0 > #>=x11-proto/xf86dgaproto-2.1 > #>=x11-proto/xf86driproto-2.1.0 > #>=x11-proto/xf86vidmodeproto-2.3 > #>=x11-proto/xineramaproto-1.2 > #>=media-libs/mesa-7.7.1 > #>=x11-apps/mesa-progs-7.7 > > Notice these are commented for when I have time. I can't now as I am using > this machine for online coursework. If someone would add these to their > package.mask and attempt an emerge, it would help > Oops thats what I get for copy/paste, I added >=media-video/nvidia-settings-173.14.09 to my mask files. *** Bug 323987 has been marked as a duplicate of this bug. *** I'm having the same problem with the 173 driver for a Geforce 5 card. None of the nvidia-settings ebuilds for 173 compile so I'm forced to unmerge it entirely and disable the gtk flag on nvidia-drivers. (In reply to comment #7) I'm having the same issue with the 173 series nvidia-drivers/nvidia-settings, required for my GeForce Fx5200 also having issues with 173.14.XX. All nvidia-drivers dependencies in the ebuilds have been fixed now. |