You are not logged in.

#1 2005-04-15 20:29:39

rdking
Member
From: Halifax NS
Registered: 2005-04-14
Posts: 110

Nvidia Locks X

Hey all, sorry for the posts today, but trying to get completely set up and drop my bloated distro in favour of arch (no nameing set distro...it was nice to work with for awhile).

One of the reasons for exploring yet another distro was that I am forever having lock ups using nvidia drivers.  Mouse still works but keyboard locked...have to hardboot...bad.  It seems the nvidia conflicts somehow and is using 100% of the cpu throughput.  I had been running Arch without problems, but it just happened running thunderbird and firefox. 

The bug is well documented on pretty well every distros boards, but just wondering if anyone here has a work around...or has found the old 6629 driver to work better.  I have tried the  render trick to no avail.  Is there a work around, or do i also have to live with the nv generic driver and live with pour video and speed.

cheers, and thanks

Offline

#2 2005-04-15 21:09:32

phrakture
Arch Overlord
From: behind you
Registered: 2003-10-29
Posts: 7,879
Website

Re: Nvidia Locks X

it's totally dependant on alot of things - are you using *just* the driver, or have you set a whole lot of options?

can you post your xorg.conf file (in [ code ][/ code ] tags please, makes it easier to read)? did you enable SBA and things like that?
in what cases is it locking? does it happen randomly, or if you were to leave it idle for a day or so would it be fine?

I have 3 arch machines running with the newest nvidia w/o any problems... what card do you have?

Offline

#3 2005-04-15 21:28:52

rdking
Member
From: Halifax NS
Registered: 2005-04-14
Posts: 110

Re: Nvidia Locks X

Sorry, My computer is as follows:

Athlon 2600+
Nforce 2 m7ncd-a02 board
onboard sound (snd-intel8x0)
Gforce mx440 PCI video card (64 meg)

My xorg.conf is as follows.  it's a copy from my ubuntu Laptop:

# /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 commands:
#
#   cp /etc/X11/xorg.conf /etc/X11/xorg.conf.custom
#   sudo sh -c 'md5sum /etc/X11/xorg.conf >/var/lib/xfree86/xorg.conf.md5sum'
#   sudo dpkg-reconfigure xserver-xorg

Section "Files"
#    FontPath    "unix/:7100"
        # local font 
    # if the local font server has problems, we can fall back on these
    FontPath    "/usr/lib/X11/fonts/misc"
    FontPath    "/usr/lib/X11/fonts/cyrillic"
    FontPath    "/usr/lib/X11/fonts/100dpi/:unscaled"
    FontPath    "/usr/lib/X11/fonts/75dpi/:unscaled"
    FontPath    "/usr/lib/X11/fonts/Type1"
    FontPath    "/usr/lib/X11/fonts/CID"
    FontPath    "/usr/lib/X11/fonts/100dpi"
    FontPath    "/usr/lib/X11/fonts/75dpi"
        # paths to defoma fonts
    FontPath    "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
    FontPath    "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
EndSection

Section "Module"
    Load    "GLcore"
    Load    "bitmap"
    Load    "dbe"
    Load    "ddc"
    Load    "extmod"
    Load    "freetype"
    Load    "glx"
    Load    "int10"
    Load    "record"
    Load    "type1"
    Load    "vbe"
EndSection

Section "InputDevice"
    Identifier    "Generic Keyboard"
    Driver        "keyboard"
    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"        "ImPS/2"
    Option        "Emulate3Buttons"    "true"
    Option        "ZAxisMapping"        "4 5"
EndSection

Section "Device"
    Identifier    "NVIDIA Corporation NV17 [GeForce4 MX 420]"
    Driver        "nvidia"
    BusID        "PCI:1:8:0"
EndSection

Section "Monitor"
    Identifier    "Generic Monitor (ttx1556)"
    Option        "DPMS"
EndSection

Section "Screen"
    Identifier    "Default Screen"
    Device        "NVIDIA Corporation NV17 [GeForce4 MX 420]"
    Monitor        "Generic Monitor (ttx1556)"
    DefaultDepth    24
    SubSection "Display"
        Depth        1
        Modes        "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
        Depth        4
        Modes        "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
        Depth        8
        Modes        "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
        Depth        15
        Modes        "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
        Depth        16
        Modes        "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
        Depth        24
        Modes        "1024x768" "800x600" "640x480"
    EndSubSection
EndSection

Section "ServerLayout"
    Identifier    "Default Layout"
    Screen        "Default Screen"
    InputDevice    "Generic Keyboard"
    InputDevice    "Configured Mouse"
EndSection

Section "DRI"
    Mode    0666
EndSection

Lockups are frequently when using thunderbird or firefox, and if it is idle it can run for days without a hickup.  maybe there is a way that i can track it better, but i am forced to reboot on locks, so i can't get startx -- -logverbose 5 to give anything extra that isn't in the regular log.

Any help on diagnosis or fixes would be great

Offline

#4 2005-04-15 21:34:43

phrakture
Arch Overlord
From: behind you
Registered: 2003-10-29
Posts: 7,879
Website

Re: Nvidia Locks X

hmmm I thought there was one of these:

Section "Module"
   Load   "GLcore"
   Load   "bitmap"
   Load   "dbe"
   Load   "ddc"
   Load   "extmod"
   Load   "freetype"
   Load   "glx"
   Load   "int10"
   Load   "record"
   Load   "type1"
   Load   "vbe"
EndSection

that conflicted... maybe GLcore? try removing that... (int10 and record are also probably not used... and you can remove ddc and vbe as those are for letting X determine resolution settings)
also remove the DRI section at the bottom - that's for ATI cards only....

I seem to recall alot of peopel have Geforce MX problems with the newer drivers....

Offline

#5 2005-04-15 22:08:06

rdking
Member
From: Halifax NS
Registered: 2005-04-14
Posts: 110

Re: Nvidia Locks X

thanks for the tips,  will give them a try once i can. exam time and all so probably won't be able to really test it out for a couple.

cheers

Offline

#6 2005-04-15 22:13:51

phrakture
Arch Overlord
From: behind you
Registered: 2003-10-29
Posts: 7,879
Website

Re: Nvidia Locks X

rdking wrote:

thanks for the tips,  will give them a try once i can. exam time and all so probably won't be able to really test it out for a couple.

cheers

no problem - I do this stuff from work so I don't have access to any linux machines, let alone an arch machine... so I know how ya feel

Offline

#7 2005-04-16 06:25:21

TheRaginAsian
Member
From: Brooklyn MI
Registered: 2004-04-05
Posts: 70
Website

Re: Nvidia Locks X

I have an Nvidia GeForce4 MX 440 and I experience the exact same problems. I ended up just reverting to the old 6629, luckily it happened to be in my pacman cache. If anyone needs it I will feel free to send it to them.

I tried tweaking all of the settings that have been talked about and none of them actually fix the issue, just kind of stall it.

7174: No Composite, HardwareAccel, DRI Options: HARD-freeze after about 4min, regardless if firefox is running or not

7174: No Composite, No HardwareAccel, No DRI Options: Hard-freeze after about 10min. regardless if firefox is running or not.

6629: Composite enabled w/ HardwareAccel. No Problems.

The unfortunate part is that for those 4 minutes when I could actually use the new driver set I DID notice that it was faster... but look, i would rather be able to run my system indefinetly rather than 4 minutes at a time tongue


John Gallias
Technician/Friend/Bassist
http://www.concretearmy.com
john@concretearmy.com
john.gallias@gmail.com
Arch Linux v0.7 (Wombat), XFce 4.2, XOrg, Firefox

Offline

#8 2005-04-16 12:07:20

scarecrow
Member
From: Greece
Registered: 2004-11-18
Posts: 714

Re: Nvidia Locks X

The DRI settings create problems with many nvidia cards, try commenting them.
Also, composite works randomly, and this is a well known problem... what happens if you don't use it?


Microshaft delenda est

Offline

#9 2005-04-16 12:09:43

RedShift
Member
From: Belgium
Registered: 2004-07-16
Posts: 230

Re: Nvidia Locks X

I had problems with my X server locking up, and in the end it was due to a broken videocard, more specifically, the video ram b0rken.


:?

Offline

#10 2005-04-16 16:20:22

rdking
Member
From: Halifax NS
Registered: 2005-04-14
Posts: 110

Re: Nvidia Locks X

so I went back and remade my xorg.conf from scratch using the config, but an still getting crashes.  I have placed it below.  As for your comments about rendering and others, they don't seem to be in there, so the default I assume is they are off correct? I would love to get this working but if no one can add any additional solutions other than tweaks to my xorg, is there still the 6629 in the pacman repo?

# File generated by xorgconfig.

#
# Copyright 2004 The X.Org Foundation
#
# 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 X.Org Foundation 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 X.Org Foundation 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 X.Org Foundation.
#

# **********************************************************************
# Refer to the xorg.conf(5x) 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 font modules
    Load        "type1"
#    Load        "speedo"
    Load        "freetype"
#    Load        "xtt"

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

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)
# 
# 

    FontPath   "/usr/X11R6/lib/X11/fonts/misc/"
    FontPath   "/usr/X11R6/lib/X11/fonts/TTF/"
    FontPath   "/usr/X11R6/lib/X11/fonts/Type1/"
    FontPath   "/usr/X11R6/lib/X11/fonts/CID/"
    FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/"
    FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/"
    FontPath   "/usr/X11R6/lib/X11/fonts/local/"
#    FontPath   "/usr/X11R6/lib/X11/fonts/Speedo/"
#    FontPath   "/usr/X11R6/lib/X11/fonts/TrueType/"
#    FontPath   "/usr/X11R6/lib/X11/fonts/freefont/"

# The module search path.  The default path is shown here.

#    ModulePath "/usr/X11R6/lib/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is 
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

#    Option "NoTrapSignals"

# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option "DontVTSwitch"

# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    Option "DontZap"

# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences.  This allows clients to receive these key events.

#    Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

#    Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client. 

#    Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings. 

#    Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

#    Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

    Identifier    "Keyboard1"
    Driver    "kbd"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

#    Option     "Protocol"      "Xqueue"

    Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#    Option    "Xleds"      "1 2 3"

#    Option "LeftAlt"     "Meta"
#    Option "RightAlt"    "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#    Option "XkbModel"    "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
#    Option "XkbModel"    "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#    Option "XkbLayout"   "de"
# or:
#    Option "XkbLayout"   "de"
#    Option "XkbVariant"  "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#    Option "XkbOptions"  "ctrl:swapcaps"

# These are the default XKB settings for Xorg
#    Option "XkbRules"    "xorg"
#    Option "XkbModel"    "pc105"
#    Option "XkbLayout"   "us"
#    Option "XkbVariant"  ""
#    Option "XkbOptions"  ""

#    Option "XkbDisable"

    Option "XkbRules"    "xorg"
    Option "XkbModel"    "pc105"
    Option "XkbLayout"    "us"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

    Identifier    "Mouse1"
    Driver        "mouse"
    Option        "CorePointer"
    Option        "Device"        "/dev/input/mice"
    Option        "Protocol"        "ImPS/2"
    Option        "Emulate3Buttons"    "true"
    Option        "ZAxisMapping"        "4 5"

# Mouse-speed setting for PS/2 mouse.

#    Option "Resolution"    "256"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

#    Option "Protocol"    "Xqueue"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

#    Option "BaudRate"    "9600"
#    Option "SampleRate"    "150"

# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"

# ChordMiddle is an option for some 3-button Logitech mice

#    Option "ChordMiddle"

EndSection


# **********************************************************************
# Other input device sections 
# this is optional and is required only if you
# are using extended input devices.  This is for example only.  Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice" 
#    Identifier  "Mouse2"
#    Driver      "mouse"
#    Option      "Protocol"      "MouseMan"
#    Option      "Device"        "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball"
#    Driver     "magellan"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball2"
#    Driver     "spaceorb"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen0"
#    Driver     "microtouch"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "1412"
#    Option     "MaxX"          "15184"
#    Option     "MinY"          "15372"
#    Option     "MaxY"          "1230"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen1"
#    Driver     "elo2300"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "231"
#    Option     "MaxX"          "3868"
#    Option     "MinY"          "3858"
#    Option     "MaxY"          "272"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonThreshold"       "17"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

    Identifier  "TTX"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    HorizSync   30-54

#    HorizSync    30-64         # multisync
#    HorizSync    31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync    15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    VertRefresh 50-120

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

#Section "Device"
 #   Identifier    "Standard VGA"
  #  VendorName    "Unknown"
  #  BoardName    "Unknown"


# The chipset line is optional in most cases.  It can be used to override
# the driver's chipset detection, and should not normally be specified.

#    Chipset    "generic"

# The Driver line must be present.  When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module.  Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

#    Driver     "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for.  When this line isn't present, a device
# section can only match up with the primary video device.  For PCI
# devices a line like the following could be used.  This line should not
# normally be included unless there is more than one video device
# intalled.

#    BusID      "PCI:0:10:0"

#    VideoRam    256

#    Clocks    25.2 28.3


# EndSection

# Device configured by xorgconfig:

Section "Device"
    Identifier  "GF4 mx440"
    Driver      "nvidia"
    # unsupported card
    VideoRam    65536
    # Insert Clocks lines here if appropriate
EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
    Identifier  "Screen 1"
    Device      "GF4 mx440"
    Monitor     "TTX"
    DefaultDepth 24

    Subsection "Display"
        Depth       8
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
    Identifier  "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.

    Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection

# Section "DRI"
#    Mode 0666
# EndSection

all thanks in advance,

Ryan

Offline

#11 2005-04-16 19:29:45

shadowhand
Member
From: MN, USA
Registered: 2004-02-19
Posts: 1,142
Website

Re: Nvidia Locks X

I believe that video card works better with older version of the driver. (I read it somewhere?) The newer drivers have obsoleted a lot of the older NV cards, maybe that's the problem.

I had lockup issues with a couple versions of the driver as well, I guess I would try a few different versions and find out if one works better.


·¬»· i am shadowhand, powered by webfaction

Offline

#12 2005-04-18 07:18:32

Cinna
Member
Registered: 2005-04-18
Posts: 15

Re: Nvidia Locks X

Hi everyone

I have the same problem vith new driver Nvidia

I have an Nvidia GeForce4 MX 440 and I experience the exact same problems. I ended up just reverting to the old 6629, luckily it happened to be in my pacman cache. If anyone needs it I will feel free to send it to them.

TheRaginAsian: Is it possible you send me this old 6629 Driver ??
If it's ok , can you send it to archlinux@free.fr
Thanks in advance

Offline

#13 2005-04-19 05:21:00

TheRaginAsian
Member
From: Brooklyn MI
Registered: 2004-04-05
Posts: 70
Website

Re: Nvidia Locks X

Ok, I apologize for the delay in response to the couple of people who have asked me for the package:

E-Mailing would have been a real... yeah... so I decided I'd just host it on my skateboarding website. Please feel free to download if you need it.

nvidia-1.0.6629-5.pkg.tar.gz

In case you didnt know:

cd [location of package]
pacman -A nvidia-1.0.6629-5.pkg.tar.gz

You will have to "pacman -R nvidia" if you currently have the package installed from Repo's.

I also didnt want my Nvidia to be updated during -Syu, and I figured it'd save you guys some time if I put that in here too!

add this line under [options] in pacman.conf

IgnorePkg   = nvidia

you will recieve verbose output during -Syu about how Pacman is ignoring the update of said package. I have no idea how to get rid of that or if its even possible, but I figure its a small annoyance compared to constant X Freeze.

Best of luck! any questions, reply or please e-mail: john.gallias@gmail.com

hope that helps.


John Gallias
Technician/Friend/Bassist
http://www.concretearmy.com
john@concretearmy.com
john.gallias@gmail.com
Arch Linux v0.7 (Wombat), XFce 4.2, XOrg, Firefox

Offline

#14 2005-04-19 18:58:23

rdking
Member
From: Halifax NS
Registered: 2005-04-14
Posts: 110

Re: Nvidia Locks X

thanks for all your help.  Gonna give them a shot, and hope they work better.  Have noticed poorer glxgears numbers from this versus the 7174, but I care about stability and using some programs which require 3d (blender for example).  Thanks and I'll keep an update on whether these drivers make a difference in stability and preformance on mx440 cards

so less than 25 min into the attempt I started have locks in both ubuntu and arch.  Guess the roll-back wasn't the answer!  that would lead me to believe that it is a problem with X-org release.  The 6629 worked excellent under XF86 and an older release of Xorg.

Offline

#15 2005-04-19 22:56:10

kth5
Member
Registered: 2004-04-29
Posts: 655
Website

Re: Nvidia Locks X

downgrading the driver to 6629 worked like a charm. everything seems to run fine now. no weird firefox crashed, windows managed by KDE's WM work like usual again and glxgears doesn't totally hang my machine anymore.

but what bugs me is that i do not have one of those "obsoleted cards". there's a FX5200 AGP card warming my feet under my desk... roll


I recognize that while theory and practice are, in theory, the same, they are, in practice, different. -Mark Mitchell

Offline

#16 2005-04-19 23:43:30

SavageMessiah
Member
Registered: 2004-03-20
Posts: 76

Re: Nvidia Locks X

I got wierd crashes in konquerer as well as firefox. I just downgraded to 6629 as well, so hopefully I'm good to go.

Offline

Board footer

Powered by FluxBB