| 1 |
Michael P. Soulier wrote: |
| 2 |
> So, like a good gentoo user I'm emerging some updates available for my system. |
| 3 |
> |
| 4 |
> To my surprise when I happen to look at the screen (as it's taking some time |
| 5 |
> to build and I'm obviously not watching the entire time), I see this: |
| 6 |
> |
| 7 |
> |
| 8 |
> * ***** WARNING ***** |
| 9 |
> * |
| 10 |
> * You are currently installing a version of nvidia-drivers that is |
| 11 |
> * known not to work with a video card you have installed on your |
| 12 |
> * system. If this is intentional, please ignore this. If it is not |
| 13 |
> * please perform the following steps: |
| 14 |
> * |
| 15 |
> * Add the following mask entry to /etc/portage/package.mask by |
| 16 |
> * echo ">=x11-drivers/nvidia-drivers-177.0.0" >> /etc/portage/package.mask |
| 17 |
> * |
| 18 |
> * Failure to perform the steps above could result in a non-working |
| 19 |
> * X setup. |
| 20 |
> * |
| 21 |
> * For more information please read: |
| 22 |
> * http://www.nvidia.com/object/IO_32667.html |
| 23 |
> * You must be in the video group to use the NVIDIA device |
| 24 |
> * For more info, read the docs at |
| 25 |
> * http://www.gentoo.org/doc/en/nvidia-guide.xml#doc_chap3_sect6 |
| 26 |
> * |
| 27 |
> * This ebuild installs a kernel module and X driver. Both must |
| 28 |
> * match explicitly in their version. This means, if you restart |
| 29 |
> * X, you most modprobe -r nvidia before starting it back up |
| 30 |
> * |
| 31 |
> * To use the NVIDIA GLX, run "eselect opengl set nvidia" |
| 32 |
> * |
| 33 |
> * nVidia has requested that any bug reports submitted have the |
| 34 |
> * output of /usr/bin/nvidia-bug-report.sh included. |
| 35 |
> * |
| 36 |
> * To work with compiz, you must enable the AddARGBGLXVisuals option. |
| 37 |
> * |
| 38 |
> * If you are having resolution problems, try disabling DynamicTwinView. |
| 39 |
> |
| 40 |
> Sure enough, X no longer works. I'm following the instructions now, but... |
| 41 |
> Don't you think the default action here should be to do nothing instead of |
| 42 |
> breaking my system? |
| 43 |
> |
| 44 |
> Not impressed. Hopefully this critical message would be summarized at the end |
| 45 |
> of the build too. Kind of important. I got lucky and happened to see it... |
| 46 |
> |
| 47 |
> Thanks, |
| 48 |
> Mike |
| 49 |
> |
| 50 |
|
| 51 |
I just did a reinstall on my rig and it did the exact same thing. I had |
| 52 |
to mask the one it installed and re-emerge the older one that does |
| 53 |
work. Isn't there some way for it to pick the right one? After all, it |
| 54 |
new it was the WRONG one it was installing. Looks to me like it could |
| 55 |
pick the right one. |
| 56 |
|
| 57 |
Dale |
| 58 |
|
| 59 |
:-) :-) |
Archives