@ Sitsofe
I think you're doing (and have been doing) a good job - you will always have
some people overreact or not understand you, however your advice was valid and
given in a nice way.
@ Simon
We all learn by making mistakes (at the beginning). Actually, we all learn *if*
we accept we can
The bug is reproducible and the fix too. It happens on scratch Feisty
install and upgrades from Edgy as well. It is not linked to
Beryl/Compiz.
** Changed in: linux-restricted-modules-2.6.20 (Ubuntu)
Status: Needs Info = Confirmed
--
[nvidia-glx] Using nvidia-glx driver, X is blank after
Simon:
The comment was not aimed at you. I don't expect people to be psychic and
magically know that they can get faster (and sometimes better) responses
without an endless back and for (which can last days, months or even years on
bug reports) elsewhere depending on their problem. I don't
I upgraded my old laptop from edgy to feisty yesterday, I only use this
laptop to view videos on my TV and the upgrade broke this completely, I
cannot get my TV-out to work anymore using the nvidia glx drivers.
the graphics hardware is the GeForce4 420 Go
the relevant sections of my xorg.conf:
I can't get 8776 to compile on the feisty kernel and 9629 doesn't fix
the problem.
Could it be a kernel-nvidiamodule interaction problem?
Anyway, I'll be reverting to edgy on this machine :-(
--
[nvidia-glx] X is blank after upgrade (laptop/Geforce Go)
https://bugs.launchpad.net/bugs/82312
You
I think the problem is that the current nvidia drivers interact with
x.org in strange and wondrous ways, and work more things out for
themselves than they used to, and take less notice of some bits of
xorg.conf than they used to. So before you give up on Feisty: start
with the stock Feisty
thanks, the line
Option ConnectedMonitor dfp, crt, tv
did help eventually!
After I got a working single monitor display going and this line in the
Screen section, the nvidia-settings picked it up and configured it
(first with the screens in the wrong order, causing the login screen to
appear on
A warning to potential future posters:
Please do not post new queries saying My X is broken please help me fix it to
this bug report. The correct place to ask these types of queries is over at
https://answers.launchpad.net/ , http://ubuntuforums.org/ and the other means
described on
Hey, nice warning, but I thought the problem was related and relevant,
turned out it wasn't and as a side effect, I got a fix.
If you discourage people from posting additional information (which may
not be relevant, but not everyone can tell), you will discourage people
from writing bugreports
Sitsofe, is there anything you think can be done about this, beyond
possible inclusion of a warning about known issues on upgrade and a
link to the BinaryDriverHowto/Nvidia page in the package description?
--
[nvidia-glx] X is blank after upgrade (laptop/Geforce Go)
Sorry for taking so long to reply. Unfortunately my laptop broke 2 weeks
ago. So I am working on a PC now. I will check if this solves the
problem once I get the laptop to work again, if that ever happens.
Thanks.
--
[nvidia-glx] X is blank after upgrade (laptop/Geforce Go)
** Summary changed:
- [nvidia-glx] X is blank after upgrade (laptop)
+ [nvidia-glx] X is blank after upgrade (laptop/Geforce Go)
--
[nvidia-glx] X is blank after upgrade (laptop/Geforce Go)
https://bugs.launchpad.net/bugs/82312
You received this bug notification because you are a member of
12 matches
Mail list logo
