Ric95:
Exactly what Bryce said.
Turning off services can be a bit fraught and the powernowd service has
two different scripts which can cause it to be run. Unfortunately
powernowd doesn't seem to support a setting in /etc/default/powernowd to
allow users to cleanly disable it in a similar manner t
'exit 0' simply causes a script to exit. So effectively, that change
causes powernowd to exit without doing anything.
I gather this indicates the bug has something to do with power
management and cpu frequency scaling.
--
[nvidia-glx] Frequent lockups when NV 3d enabled
https://bugs.launchpad.n
I worried I may be too optimistic, but that seems to have cured it
On a hunch, I first tried turning off the service... and locked it up 30
seconds later. But then I edited that line in and have been working windows
around blender just fine :) Thanks!,... what does "exit 0" do anyhow?
--
Ric95:
That's too bad. This is a long shot but I'm out of ideas:
Add the following new line just after #! /bin/sh in /etc/init.d/powernowd
exit 0
and then reboot. Any change?
--
[nvidia-glx] Frequent lockups when NV 3d enabled
https://bugs.launchpad.net/bugs/94739
You received this bug notificati
Nope. "RenderAccel" "False" ( not "0" btw) Doesn't help.
But at least Blender is the only thing that crashes it. ( pity, Blender is the
most important piece of software for me.)
Blender is available in a static build that doesn't use system openGL
libraries. I'll try that.
If it works I could
Too early to say if "RenderAccel" "0" helps, but trying the "nvidia-glx-
new" broke it bad with a version mismatch. And reverting back to
"nvidia-glx" didn't work, I ended up re-installing from scratch!. ( now
it occurs to me that I should have purged nvidia, then re-installed. )
--
[nvidia-glx]
Ric95:
There's very little to recompile - it a binary only driver. The only thing you
could recompile is the glue layer which isn't really going to make much
difference. Given that this bug lockups up your entire system the problem can't
possibly lie with Blender so recompiling it would likely n
Ya, it looks like several people have had problems with that.
Firefox hasn't lockedup, but my beloved Blender has ( rarely ).
What can I do to fix this and hopefully help the community ?
Can I recompile the NV driver ? ( I read an old page describing an Nvidia
supplied compiler to tweak for th
Ric95's last comment makes this sounds like Bug #13530 . If so Ric95 is
less likely to see the problem but assuming that the nvidia binary
module is still being used the issue will flare up with programs like
firefox...
--
[nvidia-glx] Frequent lockups when NV 3d enabled
https://bugs.launchpad.ne
Solved.
I've noted the times when the system locks up, and in my case there was no
events logged in the log files. But I switched to Xubuntu 7.04 and it runs
clean and stable :)
[See if there is mention of NVRM: Xid in /var/log/messages ...]
Sorry, but I've wiped the partition when I installed X
John:
There is not enough information in your comment to identify what the problem
might be (plus it doesn't sound like your particular issue is a lock up).
Please can you file a new bug report (attaching your xorg.conf file and
Xorg.0.log) and post a link back here?
--
[nvidia-glx] Frequent l
I was using the nvidia-glx on my laptop with a GeForce4 420 Go 64M and
Ubuntu Edgy amd64. All was well until I upgraded to Feisty. At the end
of the upgrade the reboot dumped me to the command line and I had to
edit xorg.conf and change "nvidia" to "nv" in order to get X to load. I
tried reinstalli
I forgot to mention I am also n Feisty AMD64 7.04 and I used the
alternate installation cd.
--
[nvidia-glx] Frequent lockups when NV 3d 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.
-
Also I am using a Nvidia 7600 GT.
--
[nvidia-glx] Frequent lockups when NV 3d 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 mailing list
ubuntu-bugs@lists.ubuntu.com
h
I can confirm this bug as I had the same result using the restricted
driver manager on a fresh feisty installation. I uninstalled the driver
using the RDM them proceded to install the drivers manually. Manual
installation did not fix the issue and neither did reconfiguring xorg
using dpkg-reconfigu
15 matches
Mail list logo
