[gutsy] after activating nvidia-glx with a nvidia mx 460 card and a crt connected to, the screen goes black

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in linux-restricted-modules-2.6.22.

Hi,

I get a black screen on my Ubuntu 7.10 AMD64 (Asus M2A-VM HDMI with AMD 690G chipset with ATI driver) after switching to the restricted driver (as offered by Ubuntu on the first post-install boot) & rebooting.

I've got a CRT too, but I don't know whether that matters.

Anyway: How can I switch back to the non-restricted driver?

You can edit manually the /etc/X11/xorg.conf and change the driver "flglx" to "vesa" or "ati". Then restart gdm "sudo /etc/init.d/gdm restart" or "start".
I've just find out that the nvidia mx460 has two vga-ports but on our asus card only one is build on so i think in this case it is the second one - i think the autoconfig thing see the two ports but takes and activates the wrong one. A workaraound is to set booth monitors to the same settings! (The best workaround is to buy a lcd!)

Similar situation here:

I did a fresh install of gutsy amd64 on an ASUS M2N-E SLI (nForce 500 chipset), AMD 5200+, ASUS EN8500GT (nvidia).

After booting using the vesa driver (nv won't work for some reason), used the Restricted Driver Manager to install nvidia-glx-new. It installed ok and the nvidia module loads ok (as per dmesg).

After rebooting, when X starts the monitor (LCD) goes into standby mode. It won't go to the console, but can reboot using ctrl-alt-del.

Hopefully someone can help me out of 640x480, it's so 1990's :)

Hi matti-lx,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

The output of lspci -vvnn would also be worth having.

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.