On Sun, 11 May 2014 20:12:54 -0400, gottl...@nyu.edu wrote:
***IT'S LOADING BOTH NOUVEAU AND NV (NVIDIA BINARY BLOB)
DRIVERS***.
I am embarrassed to report that I missed that (perhaps nv is the nv
nvidia; but in any case it is loading two drivers, which is bad).
Thank you very much
Am 12.05.2014 02:12, schrieb gottl...@nyu.edu:
I realize you don't use gdm/gnome. But perhaps someone has seen the
following problem.
To release the screensaver, the current gnome wants you to press mouse
button1 and move the mouse up (as with phones and tablets). This fails
to end the
On Sun, May 11 2014, Canek Peláez Valdés wrote:
On Sun, May 11, 2014 at 7:12 PM, gottl...@nyu.edu wrote:
This helped considerably. No grey bands; instead gdm puts up its
screensaver and tells us the (correct) time. Moving the mouse moves the
pointer and clicking on the upper right button
On Mon, May 12 2014, Neil Bothwick wrote:
On Sun, 11 May 2014 20:12:54 -0400, gottl...@nyu.edu wrote:
***IT'S LOADING BOTH NOUVEAU AND NV (NVIDIA BINARY BLOB)
DRIVERS***.
I am embarrassed to report that I missed that (perhaps nv is the nv
nvidia; but in any case it is loading two
On Mon, May 12 2014, Stefan G. Weichinger wrote:
Am 12.05.2014 02:12, schrieb gottl...@nyu.edu:
I realize you don't use gdm/gnome. But perhaps someone has seen the
following problem.
To release the screensaver, the current gnome wants you to press mouse
button1 and move the mouse up (as
On Mon, May 12, 2014 at 7:20 PM, gottl...@nyu.edu wrote:
[...]
I did
emerge --changed-use --update --keep-going world
and
emerge --depclean --ask --ignore-default-opts
The problem remains (after a reboot).
Specifically, gdm/gnome-shell puts up the screensaver giving the time in
big
On Mon, May 12, 2014 at 7:21 PM, gottl...@nyu.edu wrote:
On Mon, May 12 2014, Stefan G. Weichinger wrote:
Am 12.05.2014 02:12, schrieb gottl...@nyu.edu:
I realize you don't use gdm/gnome. But perhaps someone has seen the
following problem.
To release the screensaver, the current gnome
On Mon, May 12 2014, Canek Peláez Valdés wrote:
On Mon, May 12, 2014 at 7:20 PM, gottl...@nyu.edu wrote:
[...]
I did
emerge --changed-use --update --keep-going world
and
emerge --depclean --ask --ignore-default-opts
The problem remains (after a reboot).
Specifically, gdm/gnome-shell
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/11/14 20:43, gottl...@nyu.edu wrote:
I have two systems with nvidia cards. Let call them OK and NG. OK
is a laptop and NG is a desktop, but I think that is irrelevant.
For both I am using the nouveau driver
[...]
This could be the
On Sun, May 11, 2014 at 12:43:59PM -0400, gottl...@nyu.edu wrote
I have two systems with nvidia cards. Let call them OK and NG.
OK is a laptop and NG is a desktop, but I think that is irrelevant.
For both I am using the nouveau driver and kernel 3.12.13.
My only monitor is a 2560x1600 dell
On Sun, May 11 2014, Walter Dnes wrote:
I copied the two messages, and compared them side-by-each in xterms.
I had done exactly that prior to posting
When X realizes that you have an Nvidia card, and no xorg.conf, it sets
up a list of all drivers that could possibly work with your card,
On Sun, May 11, 2014 at 7:12 PM, gottl...@nyu.edu wrote:
On Sun, May 11 2014, Walter Dnes wrote
[snip]:
Plan B) if Plan A fails, manually remove
/usr/lib64/xorg/modules/drivers/nv_drv.so
That's a really bad idea. If the driver is there, and Allan didn't
rememeber being the one that put it,
12 matches
Mail list logo
