My apologies to everyone who tried to help me.
The problem was in my BIOS. When I installed My PCI-Express video card the BIOS
set itself to PCI, so the OS would end up looking in the wrong slot for video :(
** Summary changed:
- [nvidia-glx] Frequent lockups when NV 3d is enabled
+
I'm back just to post an update in hopes I can help make Ubuntu the best ever.
( a postcard from the edge ;) )
I've used many Linux distros lately, and almost all had a similar lockup on my
hardware. ( note to self: no more compaq )
Now I'm using Sabayon/Gentoo. 2.6.21, 64 bit, it had the lockup
(I'm not an Ubuntu dev). I don't think you are going to have much luck
debugging this unless you know how to set up a serial console and I
would be surprised if someone built a debug kernel just for you, however
there's nothing stopping you rebuilding your own kernel with various
extra options. My
Its hard to say. But I'm now thinking that I'm chasing two bugs that cause the
same lockup :(
After making that change as per bug115267 I didn't notice the random lockup,
but I still induced a lockup by dragging a window. I'll try to find time to
chase that separately.
Would it be possible
Ric95:
Hopefully you will get this before you switch drivers...
Can you check that using the module parameter specified in
https://bugs.launchpad.net/bugs/115267 doesn't make a difference while
you are still on the older drivers?
--
[nvidia-glx] Frequent lockups when NV 3d is enabled
Ric95:
Currently _not_ the most up to date one - see Bug ##120943, .
** Changed in: linux-restricted-modules-2.6.20 (Ubuntu)
Status: Needs Info = Unconfirmed
--
[nvidia-glx] Frequent lockups when NV 3d is enabled
https://bugs.launchpad.net/bugs/94739
You received this bug notification
(That should have been Bug #120943)
Ric95:
Just before you switch to newer drivers can you also check whether the module
parameter specified in Bug #115267 makes any difference?
BTW: if you want to try building a package of the newer drivers you may
want to give Envy
Ric95:
Could you also post the output of
lspci -vnn | grep -i nv -A 5
?
--
[nvidia-glx] Frequent lockups when NV 3d is enabled
https://bugs.launchpad.net/bugs/94739
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
[EMAIL PROTECTED]:~$ lspci -vnn | grep -i nv -A 5
01:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 7300 GS
[10de:01df] (rev a1) (prog-if 00 [VGA])
Subsystem: Unknown device [19f1:1fe2]
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at fa00
[EMAIL PROTECTED]:~$ lspci -nn | grep -i nv
01:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 7300 GS
[10de:01df] (rev a1)
[I suspect your best bet is to talk to NVIDIA directly about this] . Ya,
I would need to use the most up to date driver. They didn't exactly make
that
Ric95:
Can you include the output of
lspci -nn | grep -i nv
in this bug report?
** Changed in: linux-restricted-modules-2.6.20 (Ubuntu)
Status: Unconfirmed = Needs Info
--
[nvidia-glx] Frequent lockups when NV 3d is enabled
https://bugs.launchpad.net/bugs/94739
You received this bug
** Summary changed:
- [nvidia-glx] Frequent lockups when NV 3d is enabled and cpu scaling is on
+ [nvidia-glx] Frequent lockups when NV 3d is enabled
--
[nvidia-glx] Frequent lockups when NV 3d is enabled
https://bugs.launchpad.net/bugs/94739
You received this bug notification because you are a
Ric95:
I suspect your best bet is to talk to NVIDIA directly about this (e.g. via
http://www.nvnews.net/vbulletin/forumdisplay.php?f=14 ). Before they look at
any problem they will ask you to install the latest drivers from their website.
Instructions for doing so on Ubuntu can be found on
Hi again. I've been exploring many other distros and they seem to have
the same problems with Nvidia combined with the more recent Linux
kernels. A redhat bugchase may implicate the'i2c handler' ( beyond my
knowledge what that is).
--
[nvidia-glx] Frequent lockups when NV 3d is enabled and cpu
** This bug is no longer a duplicate of bug 109643
[nvidia-glx] System frequently locks up with white screen with black lines
when using nvidia binary driver with CPU speed scaling/Cool 'n Quiet
--
[nvidia-glx] Frequent lockups when NV 3d is enabled and cpu scaling is on
Unduplicating this bug based on Ric95's recent comment.
Ric95:
Generally speaking only one driver (the latest driver that supports your card)
will be recommended for a given card. Anything else may coincidentally work but
won't be supported by NVIDIA (but you will have to check with NVIDIA on
*** This bug is a duplicate of bug 109643 ***
https://bugs.launchpad.net/bugs/109643
I may try nvidia-glx-new when I have time to tinker with it. I would be nice if
there was an easier way to revert back to nvidia-glx. Hopefully with Gutsy both
drivers will be in the driver manager. It
*** This bug is a duplicate of bug 109643 ***
https://bugs.launchpad.net/bugs/109643
Ric95:
Drat. It looks like powernowd wasn't the sole cause of your problems. It's
probably unwise to uninstall powernowd though. There's nothing the coders of
powernowd can do about because their program is
*** This bug is a duplicate of bug 109643 ***
https://bugs.launchpad.net/bugs/109643
Yes this is definatly a big improvement.
But I still get a lockup very rarely. More like once/ 2 hours rather than once/
10 min.
Is it safe to uninstall Powernowd ?
Is Nvidia and the coders of Powernowd
I'm just glad we could resolve it :) Thats wierd that Nvidia would
effect that, but now that I think about it That sort of makes sense.
--
[nvidia-glx] Frequent lockups when NV 3d is enabled and cpu scaling is on
https://bugs.launchpad.net/bugs/94739
You received this bug notification because
*** This bug is a duplicate of bug 109643 ***
https://bugs.launchpad.net/bugs/109643
** This bug has been marked a duplicate of bug 109643
[nvidia-glx] System frequently locks up with white screen with black lines
when using nvidia binary driver with CPU speed scaling/Cool 'n Quiet
--
Ric95, excellent to hear the problem is resolved for you. :-) Of
course, the underlying issue of powernowd being bugged still exists, but
that's covered by the other bug report.
Sitsofe, cool, that bug already has one dupe for it, so I'll mark this a
dupe of it as well, and update its
22 matches
Mail list logo
