I managed to use downgrade to nvidia-glx driver. The problem seems to
be on the package that fails to remove the control file /lib/linux-
restricted-modules/.nvidia_new_installed
This file is checked by lrm-video script to see if it needs to load
nvidia or nvidia_new
Just by installing
hello, i have exactly the same problem see:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-
modules-2.6.22/+bug/154843
a man said :Please read https://wiki.ubuntu.com/X/Debugging and add info about;
- How complete is the X failure?
+ Does ctrl+alt+f1 take you to a console?
+ Does
NVIDIA has already identified/acknowledged that there is a regression in the
100.14.11 100.14.19 drivers for G72 based cards (7300 Go, GS...)
on certain systems:
http://www.nvnews.net/vbulletin/showpost.php?p=1399253postcount=36
Note that most of the time, when using 100.14.11/19, the freeze is
just to note the freezes occur with desktop effects disabled.
so the options are:
disable a core
downgrade drivers
switch to nv
--
Random NVidia Proprietary Driver Lynches / Lock-Ups
https://bugs.launchpad.net/bugs/145112
You received this bug notification because you are a member of Ubuntu
Hot off the NVidia presses:
http://www.nvnews.net/vbulletin/showthread.php?t=58498
--
Random NVidia Proprietary Driver Lynches / Lock-Ups
https://bugs.launchpad.net/bugs/145112
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
i tried idle=poll and it did not help. nothing else on that link seems
relivant. did you post the wrong link?
--
Random NVidia Proprietary Driver Lynches / Lock-Ups
https://bugs.launchpad.net/bugs/145112
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
That was the initial response from NVidia's Linux bug email.
I don't know if it helps us much, but I would think we should at least
try to follow their bug trail path.
If everyone could send them a similar mail, it might help to get their
attention on the matter.
--
Random NVidia Proprietary
So all subscribers of this bug need to follow the instructions on that
NVidia page and submit the reports accordingly -- as per instructions
sent from Lonni J Friedman of NVidia's Linux support.
I have just run through the entire list with no success.
Please ship off the log that the shell
No errors here:
[EMAIL PROTECTED]:~$ cat /etc/modprobe.d/lrm-video
# Make nvidia/nvidia_legacy and fglrx use /sbin/lrm-video to load
install fglrx /sbin/lrm-video fglrx $CMDLINE_OPTS
install nvidia /sbin/lrm-video nvidia $CMDLINE_OPTS
install nvidia_legacy /sbin/lrm-video nvidia_legacy
Apparently one can install the archived driver with restricted installed
as well.
When I do a full purge on all of the restricted bits, /sbin/lrm-video
ceases to exist. This will result in X generating the lrm-video not
found error when it attempts to load the NVidia module. modprobe nvidia
From: [EMAIL PROTECTED] To: [EMAIL
PROTECTED] Date: Sat, 6 Oct 2007 05:01:51 + Subject: [Bug 145112] Re:
Random NVidia Proprietary Driver Lynches / Lock-Ups Wow. Thanks for the
reversion version number -- 09. Compiled the new binary nasty blob
I have sent off a bug report with a link to this thread to NVidia as I
strongly suspect it is a binary driver issue. Hopefully we will get
this resolved. At any rate, if anyone in this thread still has the
crashing driver installed, what would be of use is to send off a similar
mail to them with
Just to clarify, you _will_ get an error with the NVidia module trying
to load thanks to some funky garbage that Ubuntu has stuck into the
modprobe script. The new modprobe will attempt to use lrm-video to
launch the NVidia module. This of course, won't work as lrm-video is
part of the
Wow. Thanks for the reversion version number -- 09.
Compiled the new binary nasty blob driver and so far no lockups.
Also edited the Python to enable desktop effects.
Thus far, stable with glx!
Hopefully the driver will get resolved with the next version.
To recap -- download the 09 series
For those (like me %-)) who experience hard lockups with the
100.14.11/14 drivers, here is a horrible hack to get 100.14.09 installed
AND to get l-r-m to recognize it, while keeping other restricted
modules you may require available. This has only been tested on an up-
to-date Gutsy
DO NOT report
Also having the same problem here. Nvidia 7300, on an ASUS M2NVP-VM, have a
6150 onboard but disabled. AMD X2 4200+ with 2G DDR2 800 ram (4 X 512). I am
running Gutsy beta, video driver is 100.14.19 with Compiz-Fusion enable,
experiencing about 1 or more an hour. None with affects disabled. I
Just picked up the following from the Nvidia support site
nV News Forums Linux Support Forums NVIDIA Linux
RE: Demand on WORKING drivers
10-03-07, 12:59 PM #36
zander
NVIDIA Corporation
Join Date: Aug 2002
Posts: 2,781
Default Re: Demand on WORKING drivers
I'd like to follow up on Aaron's
I have exactly the same problem with a geforce 7300 GO.
--
Random NVidia Proprietary Driver Lynches / Lock-Ups
https://bugs.launchpad.net/bugs/145112
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Troy:
Does disabling cpufreq (as mentioned on
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/109643/comments/9
) help?
--
Random NVidia Proprietary Driver Lynches / Lock-Ups
https://bugs.launchpad.net/bugs/145112
You received this bug notification because you
same unstability / flickering on my hp pavilion dv6159eu (nvidia go 7200) and
nvidia-glx-new (ALL 100.x series drivers).
Could be this drivers bug on turbocache memory access??
--
Random NVidia Proprietary Driver Lynches / Lock-Ups
https://bugs.launchpad.net/bugs/145112
You received this bug
andrea 'shinji' delfino wrote:
same unstability
Does this mean that you are experiencing lockups?
If this is the case, we might want to do some digging to see exactly
what chipset goes into the 7200 and 7300 lines to see if there is the
possibility that this is a related bug.
--
Random NVidia
i have had a go at the DebuggingSystemCrash.
after the crash i am unable to ping or ssh to the machine (over wired
ethernet).
this happens with just metacity (i think it happens faster with compiz),
and a few gnome apps open (epiphany, liferea). the frequency of once or
twice an hour is about
i have let memtest86 run for an hour. it completed two passes with no
errors found.
--
Random NVidia Proprietary Driver Lynches / Lock-Ups
https://bugs.launchpad.net/bugs/145112
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
i managed to ssh after a freeze
dmesg has.
[ 92.954972] NET: Registered protocol family 17
[ 107.488611] eth0: no IPv6 routers present
[ 278.449711] NVRM: Xid (0008:00): 6, PE 0fb8 00ff f0a0 00ff
00ff
[ 565.402594] NVRM: Xid (0008:00): 26, Ch 01ff M 1ffc D
Sam Tygier wrote:
i have let memtest86 run for an hour. it completed two passes with no errors
found. I let it run on my machine for twelve hours. Not a single error.
Have you tried the remote debugging technique where you ssh into the box
before the crash and watch the output?
All we can do
Troy:
You're getting Xids which could make this very tough to track down. I really
hope your system is performing lynches though, that could be rather deadly.
You might be able to use some of the information on
https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia#troubleshooting
to help
is performing lynches should have been
isn't performing lynches
Lynching is not behaviour to be engaged in : )
--
Random NVidia Proprietary Driver Lynches / Lock-Ups
https://bugs.launchpad.net/bugs/145112
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
sometimes the freeze is only temporary, i can ssh in (or stay ssh'ed
in). if i run top the xorg is at 100%. i get the Xid errors in my dmesg.
the computer appears to be frozen hard, the capslock key does not light
the caps light, ctrl-alt-del/backspace ignored.
after around 5 mins, it recovers
** Summary changed:
- Random nvidia-glx-new Lynches / Lock-Ups
+ Random NVidia Proprietary Driver Lynches / Lock-Ups
** Description changed:
Binary package hint: nvidia-glx-new
- Summary: A newer unknown update now results in an unstable system with
- regards to random freezes. Last
29 matches
Mail list logo
