NVRM: Xid (0001:00): 30, L1 -> L0 NOT FIXED YET !!!!!

[jokx]

First I wanna reply to AaronP who said before closing this thread (#1) :

Originally Posted by AaronP

freeDrivers,
netllama already explained the situation to you. Without a means of reproducing the bug, there's nothing he can do. You really do need to contact your hardware vendor to work out your hardware problems, since netllama said that the problem didn't reproduce with a reference motherboard. To everyone else, the message in the subject is a very generic error message with no one fixed cause, so you should create new threads if you continue to experience problems.
This thread has spun in circles going nowhere for long enough. Closing.

So, my reply in 6 points is :

1) As you can see, freeDrivers is not the only one who experimente this problem, unaware other body is very displeasing.

2) The problem IS NOOOOOOOT a hardware problem !!, if you look at my own post (#2) you will see that this bug doesn't appears with Edgy Eft release of Ubuntu, but only with Feisty Fawn.

3) It's work with the reference motherboard ? OOOooooh splendid ! Every body buy a reference motherboard with it N'Vidia card ? Yeeeees ? ... If it's a motherboard problem, it's not an isolated case because mine have the problem and :
- the one of freeDrivers too !
- the one of stuorguk too !
- the one of at0mik too !
- the one of alpilotx too !
- the one of cognos too !
- the one of zeb too !
- the one of devanhoe too !
- the one of cookiecaper too !
- the one of Zzozo2 too !
(Has we know for now ).

4) We all have your "very generic error message" with who you are unable to found the cause. YOU manage the driver source code so YOU was able to obtain a better message from your software about this bug, give here a more verbose driver and I will test it for you !

5) I have created a new thread because I continue to experience this problem. Another time, netllama turn around the bug... In this thread I'm waiting for command ... Since 2 weeks !

6) the initial thread has spun in circles because N'vidia team don't look to solve the problem !

Again : This bug appear with software modification. Give us a new drivers to test or don't reply, it will not be useful...

And Hooo ! I'm going to forget, netllama : you know this movie ? http://en.wikipedia.org/wiki/Liar_Liar.

***

#1 - http://www.nvnews.net/vbulletin/showthread.php?t=91091
#2 - http://www.nvnews.net/vbulletin/show....php?p=1250057

[adamk75]

Excuse me, but you can remove my name from your list. I never experienced this problem, and never said I did. How do you expect people to take you seriously if you can't even people's posts to see if they actually have this problem?

Adam

[jokx]

Sorry, just a mistake...

[zander]

Does the problem reproduce if you use a Linux kernel older than Linux 2.6.20 or a driver modified per these instructions: http://www.nvnews.net/vbulletin/show...3&postcount=15?

[pgs]

I do not want to take over the thread, but why don't you provide a debug version of the driver with output encrypted with some public key?
This will allow the users to produce verbose output, which will be readable only by nVidia engineers.

[jokx]

So, here you will find 3 more nvidia-bug-report's.

All have been done on Feisty Fawn with "restricted-modules" packages removed and --purged. The Nvidia drivers used is the 100.14.06 found here, it was tuned with your instructions. Compositing is disabled and X server is started with "startx -- -logverbose 6" command.

The 2 first is done under generic Linux image release : 2.6.20.16.28.1 (last update on Feisty) with and without acpi. (acpi=off passed to kernel at boot time).

The last one is done with generic Linux image release : 2.6.17.1-11.38 "backported" from Edgy Eft found here.

In all case, I launch Open Arena and it's freeze in 3 to 6 seconds for 10 to 20 seconds.

I feel that 100.14.06 beta driver freeze much more than 100.14.03.

***

Wanna buy a Intel graphics powered motherboard meter : [###### - - - - ] 60% ;-)

[jokx]

Originally Posted by pgs

I do not want to take over the thread, but why don't you provide a debug version of the driver with output encrypted with some public key?
This will allow the users to produce verbose output, which will be readable only by nVidia engineers.

I think no code is "Uncrackable". If the output driver information is sooo important, competitor will crack it quickly.

My card made long time freeze with big driver output in syslog, if the driver need to crypte it ! Aaahhheeee

[jokx]

Again, I wait for command guy's ....

***
Wanna buy a Intel graphics powered motherboard meter : [######## - - ] 80% ;-)

[jay8378]

OK i just wanted to say that i have this problem too. I've tested it in kubuntu and ubuntu so its not a window manager all though the bug did act different in both.
I ran a few ssh terms for cat /proc/kmsg while loading a couple games in ubuntu and seen the l1 -> l0 and so forth (this is why i found this thread and the last one) see compressed file. I also have a tail of syslog after it happened.
I have kubuntu installed thinking it might have been gnome but it does almost the same thing in it. So i did the nvidia-bug-report.sh in kubuntu i was going to try suse10.2 but the binary drivers from nvidia will not let me boot into x. it did that in 10.1 as well on a different motherboard. the manual install worked fine tho.
I really like ubuntu and i do not want to use suse. maybe if we all list our hardware we can find a similarity between us causing this.

O and one more important thing!!!!!! It only happens when I enable SLI in xorg.conf with SLI off it runs fine.

my hardware is as listed
nvidia evga 7600gt sli
m2n32-sli deluxe
socket am2 nforce 590-sli 2000MT/s
full dual PCI-ex16 8 phase power design
2GB ddr2-800 sli ready corsair
athlon 6000+ dual core 3ghz
audigy 2 zs
ultra 700w powersupply

all i can think of atm

[kriko]

@jay8378: try to reinstall nvidia drivers on suse 10.2 and try to see if you can reproduce the problem.

[jay8378]

i will reinstall tonight gotta goto work now

[jay8378]

OK i started from scratch.
installed SuSe 10.2 x64 again.
As soon as i got into SuSe, i installed the latest driver from nvidias site released june 8th
i hope they release this driver in the ubuntu repo soon.
anyways.. i had to download nexuiz and manual install it and it ran great with --SLI=auto, no crash.
i re-ran it a few times still no crash.
I got swg running in wine.
it was all messed up and not playable but still no crash.
re-booted and re-tested, still fine.
So it has to be in the ubuntu/deb system somewhere.
I can run SLI in windows vista64 fine as well.