Re: Nvidia driver lock-up (was (Re: Flightgear crashes (the program,not the pilot))

2006-10-15 Thread Hans-J. Ullrich
Am Sonntag, 15. Oktober 2006 18:43 schrieb Russ Cook:
> Hans-J. Ullrich wrote:
> > Am Montag, 9. Oktober 2006 03:38 schrieben Sie:
> >> Hans-J. Ullrich wrote:
> >>> Am Samstag, 7. Oktober 2006 03:38 schrieben Sie:
>  Hans-J. Ullrich wrote:
> > Hi Russ,
> >
> > sry, my late answer, I did somehow miss your mail.
> >
> > Well, if nv crashes and nvidia without "Load GLX"-Option, then there
> > might be another non nvidia dependent problem.
> >
> > What does it show, if you disable "kdm" and start manually X with the
> > command "startx" from the shell ? Is there a difference between root
> > and normal user ?
> >
> > If starting with "startx" from the shell, you can see, what really
> > happens.
> >
> > In doubt, just send me the output and your /var/log/xorg.log.
> >
> > You can additionally start "startx" with the strace command. Just do
> > "strace startx" on the shell. Caution: This is a huge output. Just
> > pipe it into a file, so you can examine it later.
> >
> > Good luck and regards !
> >
> >
> > Hans
> 
>  Hans,
>   Per your suggestion, I ran strace startx, and piped the output to
>  startx.log (attached).  Also attached is /var/log/Xorg.0.log .  I was
>  running the nvidia driver for this test (config file also attached).
>  After starting the Xserver, I tried to open my Home folder.  The frame
>  came up, but the files never appeared.  SSH from another machine,
>  and running top showed Xorg running 100% on one processor (I have
>  a dual core machine).
>    Any further advice or suggestions are most welcome.  I am currently
>  running with the Vesa driver, as it is stable (if slow).
> 
>  Thanks,
>    Russ
> >>>
> >>> Hi Russ,
> >>>
> >>> I looked at your attachements and I could see some things, you should
> >>> change:
> >>>
> >>> In xorg.conf there are the wrong paths for the fonts. Those have
> >>> changed since xorg is used ! Here are my entries:
> >>>
> >>> Section "Files"
> >>>   FontPath"unix/:7100"# local font server
> >>>   # if the local font server has problems, we can fall back on these
> >>>   FontPath"/usr/share/fonts/X11/misc"
> >>>   FontPath"/usr/share/fonts/X11/cyrillic"
> >>>   FontPath"/usr/share/fonts/X11/100dpi/:unscaled"
> >>>   FontPath"/usr/share/fonts/X11/75dpi/:unscaled"
> >>>   FontPath"/usr/share/fonts/X11/Type1"
> >>>   FontPath"/usr/share/fonts/X11/CID"
> >>>   FontPath"/usr/share/fonts/X11/100dpi"
> >>>   FontPath"/usr/share/fonts/X11/75dpi"
> >>> EndSection
> >>>
> >>>
> >>> Second thing:
> >>>
> >>> In xorg.conf cooment the section  DRI out:
> >>>
> >>> # Section "DRI"
> >>> # Group "video"
> >>> # Mode0666
> >>> # EndSection
> >>>
> >>> They are not used for Nvidia-cards.
> >>>
> >>> I will send you my xorg.conf from my Nvidia-computer later (this
> >>> message is written on my ATI-Notebook :=)), so this one will not
> >>> work as it is for ATI.
> >>>
> >>> If everything fails, so you should create a very new xorg.conf. But
> >>> just don't do it with dpkg-reconfigure, do it using "xorgconfig" as
> >>> root on a shell.
> >>>
> >>> Answer the questions. Then save it as xorg.conf as suggested.
> >>>
> >>> At last change the entry for the video driver from "nv" to "nvidia" and
> >>> activate the Load GLX option.
> >>>
> >>> Do not forget to backup your old xorg.conf, so, if it works with the
> >>> new one, you can test why the old did not work.
> >>>
> >>> Good luck !
> >>>
> >>> Hans
> >>
> >> Hans,
> >>   Thanks for the continued help.  I tried the changes you suggested
> >> here,
> >
> > Its a pleasure for me.
> >
> >> but no help.  I do not seem to have the command 'xorgconfig'.  A search
> >> of packages on the Debian web site does not give a response either.
> >
> > O.k., might be, this is no more in the pacgages, as I could not find it
> > any more. On my system it is no more, too. Sorry !
> >
> >> Where can I find this program?  I am at latest version of xbase-clients,
> >> but no such command is available to me.
> >
> > Maybe some maintainer could answer this. I am wondering myself, now.
> >
> >> Thanks,
> >>   Russ
> >
> > Did you test my xorg.conf I sent to you ?
> >
> > Regards
> >
> > Hans
>
> I did test your config file you sent me.  That is, I entered the
> appropriate areas that were different from mine.  The result is the same. 
> I was hoping that running strace and providing the output would enable
> someone
> to identify where the system was hanging.  I certainly don't understand it.
> Thanks for your willingness to help!  I suppose I could just buy a more
> recent Nvidia-supported video card and hope for the best, but I was
> hoping to resolve the issues with my old card first.
>
> Thanks again,
>Russ

O.k., so I will wait for this. Maybe you will test an older driver from the 
Nvi

Re: Nvidia driver lock-up (was (Re: Flightgear crashes (the program,not the pilot))

2006-10-15 Thread Russ Cook

Hans-J. Ullrich wrote:

Am Montag, 9. Oktober 2006 03:38 schrieben Sie:
  

Hans-J. Ullrich wrote:


Am Samstag, 7. Oktober 2006 03:38 schrieben Sie:
  

Hans-J. Ullrich wrote:


Hi Russ,

sry, my late answer, I did somehow miss your mail.

Well, if nv crashes and nvidia without "Load GLX"-Option, then there
might be another non nvidia dependent problem.

What does it show, if you disable "kdm" and start manually X with the
command "startx" from the shell ? Is there a difference between root
and normal user ?

If starting with "startx" from the shell, you can see, what really
happens.

In doubt, just send me the output and your /var/log/xorg.log.

You can additionally start "startx" with the strace command. Just do
"strace startx" on the shell. Caution: This is a huge output. Just pipe
it into a file, so you can examine it later.

Good luck and regards !


Hans
  

Hans,
 Per your suggestion, I ran strace startx, and piped the output to
startx.log (attached).  Also attached is /var/log/Xorg.0.log .  I was
running the nvidia driver for this test (config file also attached).
After starting the Xserver, I tried to open my Home folder.  The frame
came up, but the files never appeared.  SSH from another machine,
and running top showed Xorg running 100% on one processor (I have
a dual core machine).
  Any further advice or suggestions are most welcome.  I am currently
running with the Vesa driver, as it is stable (if slow).

Thanks,
  Russ


Hi Russ,

I looked at your attachements and I could see some things, you should
change:

In xorg.conf there are the wrong paths for the fonts. Those have changed
since xorg is used ! Here are my entries:

Section "Files"
FontPath"unix/:7100"  # local font server
# if the local font server has problems, we can fall back on these
FontPath"/usr/share/fonts/X11/misc"
FontPath"/usr/share/fonts/X11/cyrillic"
FontPath"/usr/share/fonts/X11/100dpi/:unscaled"
FontPath"/usr/share/fonts/X11/75dpi/:unscaled"
FontPath"/usr/share/fonts/X11/Type1"
FontPath"/usr/share/fonts/X11/CID"
FontPath"/usr/share/fonts/X11/100dpi"
FontPath"/usr/share/fonts/X11/75dpi"
EndSection


Second thing:

In xorg.conf cooment the section  DRI out:

# Section "DRI"
#   Group "video"
#   Mode0666
# EndSection

They are not used for Nvidia-cards.

I will send you my xorg.conf from my Nvidia-computer later (this message
is written on my ATI-Notebook :=)), so this one will not work as it
is for ATI.

If everything fails, so you should create a very new xorg.conf. But just
don't do it with dpkg-reconfigure, do it using "xorgconfig" as root on a
shell.

Answer the questions. Then save it as xorg.conf as suggested.

At last change the entry for the video driver from "nv" to "nvidia" and
activate the Load GLX option.

Do not forget to backup your old xorg.conf, so, if it works with the new
one, you can test why the old did not work.

Good luck !

Hans
  

Hans,
  Thanks for the continued help.  I tried the changes you suggested here,



Its a pleasure for me.
  

but no help.  I do not seem to have the command 'xorgconfig'.  A search
of packages on the Debian web site does not give a response either.



O.k., might be, this is no more in the pacgages, as I could not find it any 
more. On my system it is no more, too. Sorry ! 
  

Where can I find this program?  I am at latest version of xbase-clients,
but no such command is available to me.



Maybe some maintainer could answer this. I am wondering myself, now.

  

Thanks,
  Russ




Did you test my xorg.conf I sent to you ?

Regards 


Hans


  

I did test your config file you sent me.  That is, I entered the appropriate
areas that were different from mine.  The result is the same.  I was hoping
that running strace and providing the output would enable someone
to identify where the system was hanging.  I certainly don't understand it.
Thanks for your willingness to help!  I suppose I could just buy a more
recent Nvidia-supported video card and hope for the best, but I was
hoping to resolve the issues with my old card first.

Thanks again,
  Russ


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Nvidia driver lock-up (was (Re: Flightgear crashes (the program,not the pilot))

2006-10-10 Thread Hans-J. Ullrich
Am Montag, 9. Oktober 2006 03:38 schrieben Sie:
> Hans-J. Ullrich wrote:
> > Am Samstag, 7. Oktober 2006 03:38 schrieben Sie:
> >> Hans-J. Ullrich wrote:
> >>> Hi Russ,
> >>>
> >>> sry, my late answer, I did somehow miss your mail.
> >>>
> >>> Well, if nv crashes and nvidia without "Load GLX"-Option, then there
> >>> might be another non nvidia dependent problem.
> >>>
> >>> What does it show, if you disable "kdm" and start manually X with the
> >>> command "startx" from the shell ? Is there a difference between root
> >>> and normal user ?
> >>>
> >>> If starting with "startx" from the shell, you can see, what really
> >>> happens.
> >>>
> >>> In doubt, just send me the output and your /var/log/xorg.log.
> >>>
> >>> You can additionally start "startx" with the strace command. Just do
> >>> "strace startx" on the shell. Caution: This is a huge output. Just pipe
> >>> it into a file, so you can examine it later.
> >>>
> >>> Good luck and regards !
> >>>
> >>>
> >>> Hans
> >>
> >> Hans,
> >>  Per your suggestion, I ran strace startx, and piped the output to
> >> startx.log (attached).  Also attached is /var/log/Xorg.0.log .  I was
> >> running the nvidia driver for this test (config file also attached).
> >> After starting the Xserver, I tried to open my Home folder.  The frame
> >> came up, but the files never appeared.  SSH from another machine,
> >> and running top showed Xorg running 100% on one processor (I have
> >> a dual core machine).
> >>   Any further advice or suggestions are most welcome.  I am currently
> >> running with the Vesa driver, as it is stable (if slow).
> >>
> >> Thanks,
> >>   Russ
> >
> > Hi Russ,
> >
> > I looked at your attachements and I could see some things, you should
> > change:
> >
> > In xorg.conf there are the wrong paths for the fonts. Those have changed
> > since xorg is used ! Here are my entries:
> >
> > Section "Files"
> > FontPath"unix/:7100"# local font server
> > # if the local font server has problems, we can fall back on these
> > FontPath"/usr/share/fonts/X11/misc"
> > FontPath"/usr/share/fonts/X11/cyrillic"
> > FontPath"/usr/share/fonts/X11/100dpi/:unscaled"
> > FontPath"/usr/share/fonts/X11/75dpi/:unscaled"
> > FontPath"/usr/share/fonts/X11/Type1"
> > FontPath"/usr/share/fonts/X11/CID"
> > FontPath"/usr/share/fonts/X11/100dpi"
> > FontPath"/usr/share/fonts/X11/75dpi"
> > EndSection
> >
> >
> > Second thing:
> >
> > In xorg.conf cooment the section  DRI out:
> >
> > # Section "DRI"
> > #   Group "video"
> > #   Mode0666
> > # EndSection
> >
> > They are not used for Nvidia-cards.
> >
> > I will send you my xorg.conf from my Nvidia-computer later (this message
> > is written on my ATI-Notebook :=)), so this one will not work as it
> > is for ATI.
> >
> > If everything fails, so you should create a very new xorg.conf. But just
> > don't do it with dpkg-reconfigure, do it using "xorgconfig" as root on a
> > shell.
> >
> > Answer the questions. Then save it as xorg.conf as suggested.
> >
> > At last change the entry for the video driver from "nv" to "nvidia" and
> > activate the Load GLX option.
> >
> > Do not forget to backup your old xorg.conf, so, if it works with the new
> > one, you can test why the old did not work.
> >
> > Good luck !
> >
> > Hans
>
> Hans,
>   Thanks for the continued help.  I tried the changes you suggested here,

Its a pleasure for me.
> but no help.  I do not seem to have the command 'xorgconfig'.  A search
> of packages on the Debian web site does not give a response either.

O.k., might be, this is no more in the pacgages, as I could not find it any 
more. On my system it is no more, too. Sorry ! 
> Where can I find this program?  I am at latest version of xbase-clients,
> but no such command is available to me.

Maybe some maintainer could answer this. I am wondering myself, now.

>
> Thanks,
>   Russ


Did you test my xorg.conf I sent to you ?

Regards 

Hans


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Nvidia driver lock-up (was (Re: Flightgear crashes (the program,not the pilot))

2006-10-07 Thread Hans-J. Ullrich
Am Samstag, 7. Oktober 2006 03:38 schrieb Russ Cook:
> Hans-J. Ullrich wrote:
> > Hi Russ,
> >
> > sry, my late answer, I did somehow miss your mail.
> >
> > Well, if nv crashes and nvidia without "Load GLX"-Option, then there
> > might be another non nvidia dependent problem.
> >
> > What does it show, if you disable "kdm" and start manually X with the
> > command "startx" from the shell ? Is there a difference between root and
> > normal user ?
> >
> > If starting with "startx" from the shell, you can see, what really
> > happens.
> >
> > In doubt, just send me the output and your /var/log/xorg.log.
> >
> > You can additionally start "startx" with the strace command. Just do
> > "strace startx" on the shell. Caution: This is a huge output. Just pipe
> > it into a file, so you can examine it later.
> >
> > Good luck and regards !
> >
> >
> > Hans
>
> Hans,
>  Per your suggestion, I ran strace startx, and piped the output to
> startx.log (attached).  Also attached is /var/log/Xorg.0.log .  I was
> running the nvidia driver for this test (config file also attached).
> After starting the Xserver, I tried to open my Home folder.  The frame
> came up, but the files never appeared.  SSH from another machine,
> and running top showed Xorg running 100% on one processor (I have
> a dual core machine).
>   Any further advice or suggestions are most welcome.  I am currently
> running with the Vesa driver, as it is stable (if slow).
>
> Thanks,
>   Russ

Hi Russ, 

just as promised: Here is my running xorg.conf. I have a Nvidia GF5700 Ultra, 
but it is the same configuration as for gf4400:


 snip ---
# File generated by xf86config.

#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# 
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# 
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# 
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#

# **
# Refer to the XF86Config(4/5) man page for details about the format of 
# this file.
# **

# **
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **
#
Section "Module"

# This loads the DBE extension module.

Load"dbe"   # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
#SubSection  "extmod"
#  Option"omit xfree86-dga"   # don't initialise the DGA extension
#EndSubSection

# This loads the Type1 and FreeType font modules
Load"type1"
Load"speedo"
Load"freetype"
Load"xtt"

# This loads the GLX module
Load   "glx"
# This loads the DRI module
#Load   "dri"
Load"extmod"
EndSection

# **
# Files section.  This allows default font and rgb paths to be set
# **

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

RgbPath "/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
# 
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
# 

#FontPath 

Re: Nvidia driver lock-up (was (Re: Flightgear crashes (the program,not the pilot))

2006-10-07 Thread Jo Shields
Russ Cook wrote:
> Hans-J. Ullrich wrote:
>> Hi Russ,
>>
>> sry, my late answer, I did somehow miss your mail.
>>
>> Well, if nv crashes and nvidia without "Load GLX"-Option, then there
>> might be another non nvidia dependent problem.
>>
>> What does it show, if you disable "kdm" and start manually X with the
>> command "startx" from the shell ? Is there a difference between root
>> and normal user ?
>>
>> If starting with "startx" from the shell, you can see, what really
>> happens.
>>
>> In doubt, just send me the output and your /var/log/xorg.log.
>>
>> You can additionally start "startx" with the strace command. Just do
>> "strace startx" on the shell. Caution: This is a huge output. Just
>> pipe it into a file, so you can examine it later.
>>
>> Good luck and regards !
>>
>>
>> Hans
>>
>>  
>>
>>   
> Hans,
> Per your suggestion, I ran strace startx, and piped the output to
> startx.log (attached).  Also attached is /var/log/Xorg.0.log .  I was
> running the nvidia driver for this test (config file also attached).
> After starting the Xserver, I tried to open my Home folder.  The frame
> came up, but the files never appeared.  SSH from another machine,
> and running top showed Xorg running 100% on one processor (I have
> a dual core machine).
>  Any further advice or suggestions are most welcome.  I am currently
> running with the Vesa driver, as it is stable (if slow).
>
> Thanks,
>  Russ

Option   "NvAGP"   "1"


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Re: Nvidia driver lock-up (was (Re: Flightgear crashes (the program,not the pilot))

2006-09-29 Thread Hans-J. Ullrich
Hi Russ,

sry, my late answer, I did somehow miss your mail.

Well, if nv crashes and nvidia without "Load GLX"-Option, then there might be 
another non nvidia dependent problem.

What does it show, if you disable "kdm" and start manually X with the command 
"startx" from the shell ? Is there a difference between root and normal user ?

If starting with "startx" from the shell, you can see, what really happens.

In doubt, just send me the output and your /var/log/xorg.log.

You can additionally start "startx" with the strace command. Just do 
"strace startx" on the shell. Caution: This is a huge output. Just pipe it 
into a file, so you can examine it later.

Good luck and regards !


Hans

  


-- 
Hans-J. Ullrich
Postmaster: pop-h.niedersachsen.de izn.niedersachsen.de
Informatikzentrum Niedersachsen
Göttinger Chaussee 259
30459 Hannover
Germany

Tel.:   ++49 511 120 3749
Mobile: ++49 177 739 666 04

E-Mail: hans.ullrich (at) pop-h.niedersachsen.de



-- 
Hans-J. Ullrich
Postmaster: pop-h.niedersachsen.de izn.niedersachsen.de
Informatikzentrum Niedersachsen
Göttinger Chaussee 259
30459 Hannover
Germany

Tel.:   ++49 511 120 3749
Mobile: ++49 177 739 666 04

E-Mail: hans.ullrich (at) pop-h.niedersachsen.de



-- 
Firma
Ullrich-IT-Consult
Inh.: Hans-J. Ullrich
Münstedter Weg 10
31246 Oberg
Tel.: 0160 8156 079
ICQ : 113448999
WWW : http://www.ullrich-it.de

Ihr Spezialist für Linux-Server und -Clients,
IT-Sicherheit, Linux-Schulungen und Workshops 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Nvidia driver lock-up (was (Re: Flightgear crashes (the program, not the pilot))

2006-09-19 Thread Russ Cook

Hans wrote:

Am Dienstag, 19. September 2006 02:28 schrieb Russ Cook:
  

Russ Cook wrote:


Hans-J. Ullrich wrote:
  

Am Sonntag, 17. September 2006 19:27 schrieb Russ Cook:


Flightgear crashes on startup on my system.  I'm running
2.6.16-2-amd64-k8-smp generic kernel.  My system:

An Asus A8N32-SLI Deluxe motherboard with AMD Athlon 4800 dual

  

core cpu, with 4 MB of Corsair TwinX ram sticks.  I have an older
GeForce4 MX 420 graphics board with 64 MB ram.  I have updated my bios
to version 1303.


I'm running Debian unstable, with latest version of Flightgear and
all required packages.  I'm NOT running nvidia drivers because
they cause my system to hang.  I'm also running the VESA driver,
for the same reason.  I've attached the error message that Flightgear
generates on startup.  Is this error indicative of the video driver I'm
using?

Thanks for any help.

Regards,
  Russ
  

Hi Russ,

as far as I know flightgear needs rendering software, just opengl.
At start it looks in its configfile, and tries to set the settings
and initialising the scenery.
IMO you MUST have an opengl-driver working ! Otherwise it will crash.
Why does the nvidia-driver not work ? It should, if you use the
Debian packages and compile the nvidia-kernel-module on your own,
and, additionally install the package nvidia-glx.

Good luck !

Hans


Hans,
 Today I upgraded to 2.6.17-2-amd64, used the debian Nvidia packages,
compiled nvidia-kernel-module, and installed nvidia-glx.  I made the
appropriate changes to xorg.conf (attached), added nvidia to
/etc/modules,
and restarted my xserver.  As soon as I log in to gdm, the system
locks up.
I have to use ssh from another linux box to restart kill gdm.  If I
try to
log in as an invalid user, it checks password, rejects the login, and
gives
a new login prompt without locking up.  As soon as I successfully login,
the system locks up.
 I have reverted back to the vesa driver (again).  If anyone can help me
troubleshoot this problem, I'll be happy to reload the nvidia driver and
run whatever tests you can walk me through.  I'd really like to be able
to use the nvidia driver, for the performance boost it's supposed to
provide.  It also seems necessary in order to run Flightgear.

Thanks for any help.

   Russ


# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool,
using # values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual
page. # (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades
*only* # if it has not been modified since the last upgrade of the
xserver-xorg # package.
#
# If you have edited this file but would like it to be automatically
updated # again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
FontPath"/usr/share/fonts/X11/misc"
FontPath"/usr/X11R6/lib/X11/fonts/misc"
FontPath"/usr/share/fonts/X11/cyrillic"
FontPath"/usr/X11R6/lib/X11/fonts/cyrillic"
FontPath"/usr/share/fonts/X11/100dpi/:unscaled"
FontPath"/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath"/usr/share/fonts/X11/75dpi/:unscaled"
FontPath"/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath"/usr/share/fonts/X11/Type1"
FontPath"/usr/X11R6/lib/X11/fonts/Type1"
FontPath"/usr/share/fonts/X11/100dpi"
FontPath"/usr/X11R6/lib/X11/fonts/100dpi"
FontPath"/usr/share/fonts/X11/75dpi"
FontPath"/usr/X11R6/lib/X11/fonts/75dpi"
# path to defoma fonts
FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
Load"i2c"
Load"bitmap"
Load"ddc"
# "dri" module disabled for proprietary Nvidia driver
#   Load"dri"
Load"extmod"
Load"freetype"
Load"glx"
Load"int10"
Load"type1"
Load"vbe"
EndSection

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "kbd"
Option  "CoreKeyboard"
Option  "XkbRules""xorg"
Option  "XkbModel""pc104"
Option  "XkbLayout"   "us"
EndSection

Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device"  "/dev/input/mice"
Option  "Protocol""ExplorerPS/2"
Option  "Emulate3Buttons" "true"
EndSection

Section "Device"
Identifier  "NVIDIA Corporation NV17 [GeForce4 MX 420]"
#  

Re: Nvidia driver lock-up (was (Re: Flightgear crashes (the program, not the pilot))

2006-09-19 Thread Hans
Am Dienstag, 19. September 2006 02:28 schrieb Russ Cook:
> Russ Cook wrote:
> > Hans-J. Ullrich wrote:
> >> Am Sonntag, 17. September 2006 19:27 schrieb Russ Cook:
> >>> Flightgear crashes on startup on my system.  I'm running
> >>> 2.6.16-2-amd64-k8-smp generic kernel.  My system:
> >>>
> >>> An Asus A8N32-SLI Deluxe motherboard with AMD Athlon 4800 dual
> >>>
>  core cpu, with 4 MB of Corsair TwinX ram sticks.  I have an older
>  GeForce4 MX 420 graphics board with 64 MB ram.  I have updated my bios
>  to version 1303.
> >>>
> >>> I'm running Debian unstable, with latest version of Flightgear and
> >>> all required packages.  I'm NOT running nvidia drivers because
> >>> they cause my system to hang.  I'm also running the VESA driver,
> >>> for the same reason.  I've attached the error message that Flightgear
> >>> generates on startup.  Is this error indicative of the video driver I'm
> >>> using?
> >>>
> >>> Thanks for any help.
> >>>
> >>> Regards,
> >>>   Russ
> >>
> >> Hi Russ,
> >>
> >> as far as I know flightgear needs rendering software, just opengl.
> >> At start it looks in its configfile, and tries to set the settings
> >> and initialising the scenery.
> >> IMO you MUST have an opengl-driver working ! Otherwise it will crash.
> >> Why does the nvidia-driver not work ? It should, if you use the
> >> Debian packages and compile the nvidia-kernel-module on your own,
> >> and, additionally install the package nvidia-glx.
> >>
> >> Good luck !
> >>
> >> Hans
> >
> > Hans,
> >  Today I upgraded to 2.6.17-2-amd64, used the debian Nvidia packages,
> > compiled nvidia-kernel-module, and installed nvidia-glx.  I made the
> > appropriate changes to xorg.conf (attached), added nvidia to
> > /etc/modules,
> > and restarted my xserver.  As soon as I log in to gdm, the system
> > locks up.
> > I have to use ssh from another linux box to restart kill gdm.  If I
> > try to
> > log in as an invalid user, it checks password, rejects the login, and
> > gives
> > a new login prompt without locking up.  As soon as I successfully login,
> > the system locks up.
> >  I have reverted back to the vesa driver (again).  If anyone can help me
> > troubleshoot this problem, I'll be happy to reload the nvidia driver and
> > run whatever tests you can walk me through.  I'd really like to be able
> > to use the nvidia driver, for the performance boost it's supposed to
> > provide.  It also seems necessary in order to run Flightgear.
> >
> > Thanks for any help.
> >
> >Russ
> > 
> >
> > # /etc/X11/xorg.conf (xorg X Window System server configuration file)
> > #
> > # This file was generated by dexconf, the Debian X Configuration tool,
> > using # values from the debconf database.
> > #
> > # Edit this file with caution, and see the /etc/X11/xorg.conf manual
> > page. # (Type "man /etc/X11/xorg.conf" at the shell prompt.)
> > #
> > # This file is automatically updated on xserver-xorg package upgrades
> > *only* # if it has not been modified since the last upgrade of the
> > xserver-xorg # package.
> > #
> > # If you have edited this file but would like it to be automatically
> > updated # again, run the following command:
> > #   sudo dpkg-reconfigure -phigh xserver-xorg
> >
> > Section "Files"
> > FontPath"/usr/share/fonts/X11/misc"
> > FontPath"/usr/X11R6/lib/X11/fonts/misc"
> > FontPath"/usr/share/fonts/X11/cyrillic"
> > FontPath"/usr/X11R6/lib/X11/fonts/cyrillic"
> > FontPath"/usr/share/fonts/X11/100dpi/:unscaled"
> > FontPath"/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
> > FontPath"/usr/share/fonts/X11/75dpi/:unscaled"
> > FontPath"/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
> > FontPath"/usr/share/fonts/X11/Type1"
> > FontPath"/usr/X11R6/lib/X11/fonts/Type1"
> > FontPath"/usr/share/fonts/X11/100dpi"
> > FontPath"/usr/X11R6/lib/X11/fonts/100dpi"
> > FontPath"/usr/share/fonts/X11/75dpi"
> > FontPath"/usr/X11R6/lib/X11/fonts/75dpi"
> > # path to defoma fonts
> > FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
> > EndSection
> >
> > Section "Module"
> > Load"i2c"
> > Load"bitmap"
> > Load"ddc"
> > # "dri" module disabled for proprietary Nvidia driver
> > #   Load"dri"
> > Load"extmod"
> > Load"freetype"
> > Load"glx"
> > Load"int10"
> > Load"type1"
> > Load"vbe"
> > EndSection
> >
> > Section "InputDevice"
> > Identifier  "Generic Keyboard"
> > Driver  "kbd"
> > Option  "CoreKeyboard"
> > Option  "XkbRules"  "xorg"
> > Option  "XkbModel"  "pc104"
> > Option  "XkbLayout" "us"
> > EndSection
> >
> > Section "InputDevice"
> > Identifier  "Configured Mouse"
> > Driver  "mouse"
> >   

Re: Nvidia driver lock-up (was (Re: Flightgear crashes (the program, not the pilot))

2006-09-18 Thread Russ Cook

Russ Cook wrote:

Hans-J. Ullrich wrote:

Am Sonntag, 17. September 2006 19:27 schrieb Russ Cook:
 

Flightgear crashes on startup on my system.  I'm running
2.6.16-2-amd64-k8-smp generic kernel.  My system:

An Asus A8N32-SLI Deluxe motherboard with AMD Athlon 4800 dual

   

core cpu, with 4 MB of Corsair TwinX ram sticks.  I have an older
GeForce4 MX 420 graphics board with 64 MB ram.  I have updated my bios
to version 1303.
  

I'm running Debian unstable, with latest version of Flightgear and
all required packages.  I'm NOT running nvidia drivers because
they cause my system to hang.  I'm also running the VESA driver,
for the same reason.  I've attached the error message that Flightgear
generates on startup.  Is this error indicative of the video driver I'm
using?

Thanks for any help.

Regards,
  Russ



Hi Russ,

as far as I know flightgear needs rendering software, just opengl.
At start it looks in its configfile, and tries to set the settings 
and initialising the scenery.
IMO you MUST have an opengl-driver working ! Otherwise it will crash.  
Why does the nvidia-driver not work ? It should, if you use the 
Debian packages and compile the nvidia-kernel-module on your own, 
and, additionally install the package nvidia-glx.


Good luck !

Hans



  

Hans,
 Today I upgraded to 2.6.17-2-amd64, used the debian Nvidia packages,
compiled nvidia-kernel-module, and installed nvidia-glx.  I made the
appropriate changes to xorg.conf (attached), added nvidia to 
/etc/modules,
and restarted my xserver.  As soon as I log in to gdm, the system 
locks up.
I have to use ssh from another linux box to restart kill gdm.  If I 
try to
log in as an invalid user, it checks password, rejects the login, and 
gives

a new login prompt without locking up.  As soon as I successfully login,
the system locks up.
 I have reverted back to the vesa driver (again).  If anyone can help me
troubleshoot this problem, I'll be happy to reload the nvidia driver and
run whatever tests you can walk me through.  I'd really like to be able
to use the nvidia driver, for the performance boost it's supposed to
provide.  It also seems necessary in order to run Flightgear.

Thanks for any help.

   Russ


# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
FontPath"/usr/share/fonts/X11/misc"
FontPath"/usr/X11R6/lib/X11/fonts/misc"
FontPath"/usr/share/fonts/X11/cyrillic"
FontPath"/usr/X11R6/lib/X11/fonts/cyrillic"
FontPath"/usr/share/fonts/X11/100dpi/:unscaled"
FontPath"/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath"/usr/share/fonts/X11/75dpi/:unscaled"
FontPath"/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath"/usr/share/fonts/X11/Type1"
FontPath"/usr/X11R6/lib/X11/fonts/Type1"
FontPath"/usr/share/fonts/X11/100dpi"
FontPath"/usr/X11R6/lib/X11/fonts/100dpi"
FontPath"/usr/share/fonts/X11/75dpi"
FontPath"/usr/X11R6/lib/X11/fonts/75dpi"
# path to defoma fonts
FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
Load"i2c"
Load"bitmap"
Load"ddc"
# "dri" module disabled for proprietary Nvidia driver
#   Load"dri"
Load"extmod"
Load"freetype"
Load"glx"
Load"int10"
Load"type1"
Load"vbe"
EndSection

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "kbd"
Option  "CoreKeyboard"
Option  "XkbRules""xorg"
Option  "XkbModel""pc104"
Option  "XkbLayout"   "us"
EndSection

Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device"  "/dev/input/mice"
Option  "Protocol""ExplorerPS/2"
Option  "Emulate3Buttons" "true"
EndSection

Section "Device"
Identifier  "NVIDIA Corporation NV17 [GeForce4 MX 420]"
#	Driver "vesa" disabled 
	Driver		"vesa"

#   Driver "Nvidia" enabled
Driver  "nvidia"
  

Nvidia driver lock-up (was (Re: Flightgear crashes (the program, not the pilot))

2006-09-18 Thread Russ Cook

Hans-J. Ullrich wrote:

Am Sonntag, 17. September 2006 19:27 schrieb Russ Cook:
  

Flightgear crashes on startup on my system.  I'm running
2.6.16-2-amd64-k8-smp generic kernel.  My system:

An Asus A8N32-SLI Deluxe motherboard with AMD Athlon 4800 dual



core cpu, with 4 MB of Corsair TwinX ram sticks.  I have an older
GeForce4 MX 420 graphics board with 64 MB ram.  I have updated my bios
to version 1303.
  

I'm running Debian unstable, with latest version of Flightgear and
all required packages.  I'm NOT running nvidia drivers because
they cause my system to hang.  I'm also running the VESA driver,
for the same reason.  I've attached the error message that Flightgear
generates on startup.  Is this error indicative of the video driver I'm
using?

Thanks for any help.

Regards,
  Russ



Hi Russ,

as far as I know flightgear needs rendering software, just opengl.
At start it looks in its configfile, and tries to set the settings and 
initialising the scenery. 

IMO you MUST have an opengl-driver working ! Otherwise it will crash. 
 
Why does the nvidia-driver not work ? It should, if you use the Debian 
packages and compile the nvidia-kernel-module on your own, and, additionally 
install the package nvidia-glx.


Good luck !

Hans



  

Hans,
 Today I upgraded to 2.6.17-2-amd64, used the debian Nvidia packages,
compiled nvidia-kernel-module, and installed nvidia-glx.  I made the
appropriate changes to xorg.conf (attached), added nvidia to /etc/modules,
and restarted my xserver.  As soon as I log in to gdm, the system locks up.
I have to use ssh from another linux box to restart kill gdm.  If I try to
log in as an invalid user, it checks password, rejects the login, and gives
a new login prompt without locking up.  As soon as I successfully login,
the system locks up.
 I have reverted back to the vesa driver (again).  If anyone can help me
troubleshoot this problem, I'll be happy to reload the nvidia driver and
run whatever tests you can walk me through.  I'd really like to be able
to use the nvidia driver, for the performance boost it's supposed to
provide.  It also seems necessary in order to run Flightgear.

Thanks for any help.

   Russ
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
FontPath"/usr/share/fonts/X11/misc"
FontPath"/usr/X11R6/lib/X11/fonts/misc"
FontPath"/usr/share/fonts/X11/cyrillic"
FontPath"/usr/X11R6/lib/X11/fonts/cyrillic"
FontPath"/usr/share/fonts/X11/100dpi/:unscaled"
FontPath"/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath"/usr/share/fonts/X11/75dpi/:unscaled"
FontPath"/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath"/usr/share/fonts/X11/Type1"
FontPath"/usr/X11R6/lib/X11/fonts/Type1"
FontPath"/usr/share/fonts/X11/100dpi"
FontPath"/usr/X11R6/lib/X11/fonts/100dpi"
FontPath"/usr/share/fonts/X11/75dpi"
FontPath"/usr/X11R6/lib/X11/fonts/75dpi"
# path to defoma fonts
FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
Load"i2c"
Load"bitmap"
Load"ddc"
# "dri" module disabled for proprietary Nvidia driver
#   Load"dri"
Load"extmod"
Load"freetype"
Load"glx"
Load"int10"
Load"type1"
Load"vbe"
EndSection

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "kbd"
Option  "CoreKeyboard"
Option  "XkbRules"  "xorg"
Option  "XkbModel"  "pc104"
Option  "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device""/dev/input/mice"
Option  "Protocol"  "ExplorerPS/2"
Option  "Emulate3Buttons"   "true"
EndSection

Section "Device"
Identifier  "NVIDIA Corporation NV17 [GeForce4 MX 420]"
#   Driver "vesa" disabled 
Driver  "vesa"
#   Driver "Nvidia" enabled
Driver  "nvidia"
BusID   "PCI:4:7:0"
EndSection

Section "Monit