| Summary: | x11-drivers/nvidia-driver-71.86.* should depend on <x11-base/xorg-server-1.4.99 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Brian Beardall <brian> |
| Component: | New packages | Assignee: | Doug Goldstein (RETIRED) <cardoe> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | garyhunt, jer, napalmllama, ricmm |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Brian Beardall
2009-07-06 19:14:11 UTC
any chance of leaving one ebuild <= xorg-server-1.4.99 as well in the tree. I know its been marked for removal, but it would be helpful for those using the 71 series legacy drivers. What is being done about these legacy drivers? Presumably X.org won't continue to support this old version indefinitely just because some proprietary driver depends on it. Sooner or later, (if it hasn't happened already), too many bugs/security issues are going to come to light for Gentoo's maintainers to keep the package in the tree any longer, and we'll all have to move onto nv or nouveau. I guess the best that we can do is keep <=xorg-server-1.4.99 in the tree for as long as possible, until removal becomes unavoidable. It'd be nice to see an experimental ebuild for nouveau, though, so those of us affected can begin to transition across. Just my 2ยข. [http://nouveau.freedesktop.org/wiki/FeatureMatrix] OK, i have looked on the net, but can not found any solution :( till someone does not find a permanent solution: OK, the following packages are not compatible with nvidia-drivers-71.86.09, so downgrade them to work as before: package - version (this or later) - reason : gentoo-sources - 2.6.28 - nvidia-drivers not compile xorg-server - 1.4 - nvidia-driver not load nvidia-drivers - 71.86.09 - xf86-input-mouse - 1.3.0 xf86-input-keyboard - 1.3.0 libpciaccess - 0.10.3 - mouse / keyboard freezes (only the reset button helps) mesa - 7.1 - some app freeze Fixed. for Nouveau see bug #253705 |
