SEO

Hi all

When I start X using the nvidia driver, X locks after a few seconds.
CTRL-ALT-FNx does not work, neither does CTRL-ALT-BACKSPACE. When I login
remote, I can see that the X process uses up to 99% of CPU. When I 'kill -9
pid' remotely, X goes down but I can not acces the local console. Only when
I reboot from remote, soon after sending the reboot command, I can see the
local framebuffer console again (and access it locally until machine finaly
reboots).

When using the nv driver instead of the nvidia, everything works fine, only
that I don't have glx support.

I'm using the latest (~x86) nvidia-kernel and nvidia-glx packages with a
2.4.25 kernel

The XF86config file can be found on
<http://www.trash.net/~man/XF86config>

The log files for the nvidia and the nv driver can be found on
<http://www.trash.net/~man/XFree86.0.log.nvidia>
<http://www.trash.net/~man/XFree86.0.log.nv>

And last but not least, my kernel config is on
<http://www.trash.net/~man/kernelconfig>

First of all, do you have the right frequencies on the monitor?
Try commenting out option dpms in your X configuration. And also, DRI should
not be enabled in the "modules" section (comment this one out).

In your kernel config I see that you have made a module of AGPGART, but you
have compiled it to support VIA, AMD, ALI, and NVIDIA. I don't know if this
can cause trouble, but remember this is only what chipset that is on the
motherboard, and has nothing to do with the graphics adapter.

And at last, there is a good troubleshooting guide in the
/usr/share/doc/nvidia-*/ folder.

Regards:
Espen

Marco Nierlich wrote:

> Hi all
>
> When I start X using the nvidia driver, X locks after a few seconds.
> CTRL-ALT-FNx does not work, neither does CTRL-ALT-BACKSPACE.

For some reason, the posting of Espen disapeared from the server. I tried
to deactivate all the settings he told but no effect. So I recompiled my
kernel and removed all the chipset support from the agpgart module and it
got better. X still froze but at least CTRL-ALT-FNx and CTRL-ALT-BACKSPACE
worked. So I had a look in the bios and saw there that years ago I disabled
the 'plug-and-play-aware-os' flag. I enabled it now and my X-Server is up
and running for 30 minutes now. Seems that was the 'bug'. Seems even that
my video card supports DRI and DPMS. I'll try this out with the next
restart.

cheers
Marco

Marco Nierlich wrote:

> Marco Nierlich wrote:
>
>> Hi all
>>
>> When I start X using the nvidia driver, X locks after a few seconds.
>> CTRL-ALT-FNx does not work, neither does CTRL-ALT-BACKSPACE.
>
> For some reason, the posting of Espen disapeared from the server. I tried
> to deactivate all the settings he told but no effect. So I recompiled my
> kernel and removed all the chipset support from the agpgart module and it
> got better. X still froze but at least CTRL-ALT-FNx and CTRL-ALT-BACKSPACE
> worked. So I had a look in the bios and saw there that years ago I
> disabled the 'plug-and-play-aware-os' flag. I enabled it now and my
> X-Server is up and running for 30 minutes now.

Just after 2 hours of uptime, I got the freeze again, this time again with
no possibility to interact by the keyboard. I could only kill the server
with remote login :-(
Seems it has to do someting with resource allocation, but I don't figuere
out what. Any hint?

cheers
Marco

Marco Nierlich wrote:
> Just after 2 hours of uptime, I got the freeze again, this time again with
> no possibility to interact by the keyboard. I could only kill the server
> with remote login :-(
> Seems it has to do someting with resource allocation, but I don't figuere
> out what. Any hint?

Are you sure it is the nvidia module? Have you tried running with nv? I have
a similar problem where I can work for days without any problem and then,
while viweing a website or typing something, X freezes. I can login
remotely and kill -9 the X server which is taking 99.99% CPU. But I have
not tried with nv and you're the first person that seems to have the same
problem.


Alex

Hi Alex

Alexander Gretencord wrote:

> Marco Nierlich wrote:
>> Just after 2 hours of uptime, I got the freeze again, this time again
>> with no possibility to interact by the keyboard. I could only kill the
>> server with remote login :-(
>> Seems it has to do someting with resource allocation, but I don't figuere
>> out what. Any hint?
>
> Are you sure it is the nvidia module? Have you tried running with nv? I
> have a similar problem where I can work for days without any problem and
> then, while viweing a website or typing something, X freezes. I can login
> remotely and kill -9 the X server which is taking 99.99% CPU. But I have
> not tried with nv and you're the first person that seems to have the same
> problem.
>
>

100% sure! With the nv module, I have uptime of several days (until I power
down manually ;-)

Can you once disabe the pnp-os-aware bios flag and see wether it also
freezes after 2-30 seconds? Maybe together (with some external help) we can
debug this thing. What NVidia chipset do you exactly have? Mine is: RIVA
TNT2 Mode 64 [Pro]

cheers
Marco

Marco Nierlich wrote:
> 100% sure! With the nv module, I have uptime of several days (until I
> power down manually ;-)

I can have day after day without a problem (I power down each evening) and
then I get it over and over again. Right now I have a problem less phase.

> Can you once disabe the pnp-os-aware bios flag and see wether it also
> freezes after 2-30 seconds?

I'm gonna reboot in a few minutes anyway so I could try that yes. I dunno to
what it's set anyway.

> What NVidia chipset do you exactly have?

A GeForce 3 Ti200.


Alex

Alexander Gretencord wrote:
>> Can you once disabe the pnp-os-aware bios flag and see wether it also
>> freezes after 2-30 seconds?

Couldn't find such a setting (though I know I at least had that with my last
mobo).