Summary: | All current ebuilds of nvidia-drivers in portage block xorg-sever-1.8 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Robert Cabrera <robcab666> |
Component: | [OLD] Unspecified | Assignee: | Doug Goldstein (RETIRED) <cardoe> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | boltomli, caster, cedric.godin, creffett, DarkNRG, deduktionstheorem, evert.gentoo, giovanni.bobbio, jlec, proteuss, schulz.benjamin, steffen.weber, tampakrap, tschenturs, x11 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Robert Cabrera
2010-04-13 23:38:56 UTC
It was the decision by the X11 team that proprietary drivers will not hinder progress in X.org packages. If you use proprietary drivers, you have to handle masking yourself. *** Bug 315143 has been marked as a duplicate of this bug. *** Apparently none of nvidia-drivers support the xorg-server-1.8 ABI. According to these: http://forums.gentoo.org/viewtopic-p-6234182.html#6234182 http://www.nvnews.net/vbulletin/showthread.php?t=149721 nvidia-drivers-195.36.15 may work with xorg-server-1.8 if add the line Option "IgnoreABI" "on" to the serverlayout section of xorg.conf. I did this and so far it works without problems,save some warnings in the logs. I hope it helps. (In reply to comment #1) > It was the decision by the X11 team that proprietary drivers will not hinder > progress in X.org packages. If you use proprietary drivers, you have to handle > masking yourself. > The x11 team may not want to hinder progress, fine and dandy, but the vast majority of Linux users who don't have some crappy onboard Intel graphics are using Nvidia, as only recently has ATI given any kind of decent Linux support. Therefore, you're alienating a majority of the installed base with this xorg-server release. Frankly, I run the Gentoo OS not the "xorg OS", decisions made upstream shouldn't have to be mimicked here. There are hundreds of examples in the Gentoo repository where currently released "stable" applications are hardmasked here. Why is this being treated so much differently? In reply to comment #3) >nvidia-drivers-195.36.15 may work with xorg-server-1.8 if add the line >Option "IgnoreABI" "on" >to the serverlayout section of xorg.conf. >I did this and so far it works without problems,save some warnings in the logs. >I hope it helps. > I've tried this now and it appears to work, however this messes up portage. After forcibly installing the nvidia-drivers any subsequent emerge either wants to downgrade xorg-server or remove the nvidia-drivers for updates to proceed. This is a very dirty hack, IMHO. On a project as large and as complex as Gentoo better, more thoughtful, consideration for end users should be taken into account before radical changes are made, IMHO. Ciao (In reply to comment #4) > This is a very dirty hack, IMHO. > > On a project as large and as complex as Gentoo better, more thoughtful, > consideration for end users should be taken into account before radical changes > are made, IMHO. Dirty hack or not, it enables one to try xorg-server-1.8 until nvidia-drivers support fully the new ABI. Alternativelly we mask ourselves xorg-server-1.8 and stop whining. This discussion comes up at _every_ release. It's systematic, like the sun rising every morning. If we don't provide the new stuff, some users will be angry because they need it for their hardware to work. If we do provide the new stuff, some users will be angry because it breaks binary drivers or it breaks existing hardware. In the light of all this, I'm sure you'll agree that we _cannot_ please everyone. We just can't. So we take the most *pragmatic* approach, which is to provide the upgrade. History has proven us that this approach was the best for the Gentoo Project and, down the road, for our users. Now, NVidia has always been prompt in providing new drivers when new servers are released, I'm sure that will happen soon. And I'm certain Doug will do an outstanding job of putting it in portage like he always does. So please, be a little patient and try to understand the situation from our side. Thanks *** Bug 315233 has been marked as a duplicate of this bug. *** (In reply to comment #0) > the portage tree this needs resolution. If all current nvidia-drivers are truly > incompatible with the new xorg-server than it should be hard masked. Why mask it for everyone when the blockers effectively masks it only for those that need the mask? I don't get it. Is the 'skipped update' warning something you can't bear to see, or what? (In reply to comment #4) > (In reply to comment #1) > I've tried this now and it appears to work, however this messes up portage. > After forcibly installing the nvidia-drivers any subsequent emerge either wants > to downgrade xorg-server or remove the nvidia-drivers for updates to proceed. > This is a very dirty hack, IMHO. To avoid this, copy the nvidia-drivers package in a local overlay and remove the blocker there. Portage won't complain anymore then. What about a USE flag like "ignoredABI", making the ebuild to ignore the block? How long does it usually take nvidia to publish a driver compatible to the new xserver? (In reply to comment #10) > How long does it usually take nvidia to publish a driver compatible to the new > xserver? > Sometimes its before the release, sometimes its same day, sometimes its a few days. I have a feeling however that this will be a longer cycle because they're unable to give me a ballpark number. There should be absolutely nothing that people have to do for this issue. Portage 2.1.7.x supports backtracking which means everything will be handled fine. You will get a message that will say: !!! One or more updates have been skipped due to a dependency conflict: x11-base/xorg-server:0 ('ebuild', '/', 'x11-base/xorg-server-1.8.0', 'merge') conflicts with <x11-base/xorg-server-1.7.99 required by ('installed', '/', 'x11-drivers/nvidia-drivers-195.36.15', 'nomerge') And Portage won't upgrade xorg-server past 1.7.x and everything will continue to work fine. You just will have an extra message when you upgrade. Once a new version of nvidia-drivers is released that properly supports nvidia-drivers, I'll push it into the tree and everyone will get upgraded then. now a new nvidia driver prerelease is out that has official 1.8 abi: http://www.nvnews.net/vbulletin/showthread.php?p=2239062 195.36.24 for Linux x86/x86_64 released * Added support for the following GPUs: o GeForce GTX 480 o GeForce GTX 470 o Tesla C2050 * Fixed a problem that caused occasional red flashes in XVideo frames. * Added official support for xserver 1.8. The -ignoreABI option is no longer required with this version of the server. * Updated the "Supported NVIDIA GPU Products" list to include various supported GPUs that were missing previously. seems that the ebuild jusr requires a name change to ***.24 At least for me no other changes were required to emerge the new driver (amd64). I'm out of town, if someone wants to bump it go ahead. Make sure to set the next blocker at 1.8.99 (In reply to comment #15) > I'm out of town, if someone wants to bump it go ahead. Make sure to set the > next blocker at 1.8.99 > done. (In reply to comment #6) > In the light of all this, I'm sure you'll agree that we _cannot_ please > everyone. We just can't. So we take the most *pragmatic* approach, which > is to provide the upgrade. Just a thought: Would it be an idea to introduce new profiles for nvidia-drivers users which can be selected using eselect? Something like: default/linux/x86/10.0/desktop/nvidia default/linux/x86/10.0/desktop/nvidia/gnome default/linux/x86/10.0/desktop/nvidia/kde In these profiles, xorg-server versions incompatible to the current nvidia-drivers could be hard masked. If this would be possible, it would not only make most nvidia-drivers users happy, but it would also reduce the number of discussions coming up at every release, saving everybody a lot of time. Versions are bumped and stabled. Not doing anything insane with profiles. |