Re: How do I roll back X using apt-get?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2004-10-20 at 23:24, rab wrote:
> Matthew Miller wrote:
> 
> >On Wed, Oct 20, 2004 at 07:35:38AM -0400, rab wrote:
> >  
> >
> >>I installed the latest rpms for fc2 for X using apt-get and the 
> >>dist-upgrade option. Now X crashes all the time (every 15 minutes or so 
> >>on average). How can I get back to the previous version of X (or even 
> >>fix X)?
> >>    
> >>
> >
> >I'm not sure if there's a trivial way to roll back a whole set of changes.
> >If someone who knows apt better than me knows one, cool.
> >
> >So in the meantime, let's figure out why X is crashing. The updates have
> >worked fine for me, and I hadn't heard any complaints.
> >
> >What video card do you have? Do you know what triggers the crash? (3D is a
> >likely culprit -- perhaps some of the OpenGL screensavers?) If you could
> >post the log (/var/log/Xorg.0.log) from the crash, that'd be helpful.
> >
> >
> >  
> >
> I tried sending the log file but it doesn't look like it made it to the 
> list. I switched to the generic VGA driver and it seems more stable. I 
> tried commenting out the dri part for the nvidia driver (shown below) 
> and turned off the screensaver but that did not stop the crashes with 
> the nvidia driver. I'm using an nvidia GEFORCE FX 5700 LE card on an 
> Athlon 64 system with 1 gb of memory. It worked great since I built the 
> sytem 3 weeks ago up until a few days ago when I upgraded using apt. (It 
> upgraded a lot of X-related rpms at that time.) With the nvidia driver 
> (the one that ships with fc2 not the nvidia binary driver from nvidia), 
> moving a remote window (via ssh connection) would always cause the X 
> server to crash.
> 
> Rick B.
> 
> # Xorg configuration created by system-config-display
>  
> Section "ServerLayout"
>         Identifier     "single head configuration"
>         Screen      0  "Screen0" 0 0
>         InputDevice    "Mouse0" "CorePointer"
>         InputDevice    "Keyboard0" "CoreKeyboard"
> EndSection
>  
> Section "Files"
>  
> # RgbPath is 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.
> # Multiple FontPath entries are allowed (they are concatenated together)
> # By default, Red Hat 6.0 and later now use a font server independent of
> # the X server to render fonts.
>         RgbPath      "/usr/X11R6/lib/X11/rgb"
>         FontPath     "unix/:7100"
> EndSection
>  
> Section "Module"
>         Load  "dbe"
>         Load  "extmod"
>         Load  "fbdevhw"
>         Load  "glx"
>         Load  "record"
>         Load  "freetype"
>         Load  "type1"
>         Load  "dri"

dri is NOT disabled here.

> EndSection
>  
> Section "InputDevice"
>  
> # Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
> #       Option  "Xleds"         "1 2 3"
> # To disable the XKEYBOARD extension, uncomment XkbDisable.
> #       Option  "XkbDisable"
> # 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"      "pc102"
> # 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"
> # Or if you just want both to be control, use:
> #       Option  "XkbOptions"    "ctrl:nocaps"
> #
>         Identifier  "Keyboard0"
>         Driver      "kbd"
>         Option      "XkbModel" "pc105"
>         Option      "XkbLayout" "us"
> EndSection
>  
> Section "InputDevice"
>         Identifier  "Mouse0"
>         Driver      "mouse"
>         Option      "Protocol" "IMPS/2"
>         Option      "Device" "/dev/input/mice"
>         Option      "ZAxisMapping" "4 5"
>         Option      "Emulate3Buttons" "yes"
> EndSection
>  
> Section "Monitor"
>         Identifier   "Monitor0"
>         VendorName   "Monitor Vendor"
>         ModelName    "SGI 17-inch GDM-17E21"
>         HorizSync    30.0 - 85.0
>         VertRefresh  48.0 - 160.0
>         Option      "dpms"
> EndSection
>  
> Section "Device"
>         Identifier  "Videocard0"
>         Driver      "nv"

This is the default nvidia driver, not the binary from nvidia

>         VendorName  "Videocard vendor"
>         BoardName   "NVIDIA GeForce FX (generic)"
> EndSection
>  
> Section "Screen"
>         Identifier "Screen0"
>         Device     "Videocard0"
>         Monitor    "Monitor0"
>         DefaultDepth     24
>         SubSection "Display"
>                 Viewport   0 0
>                 Depth     24
>                 Modes    "1280x1024" "1280x960" "1152x864" "1024x768" 
> "800x600" "640x480"
>         EndSubSection
> EndSection
>  
> #Section "DRI"
> #       Group        0
> #       Mode         0666
> #EndSection

This may cause problems if the dri module is loaded above.

In my experience with the nvidia driver, you need to follow the readme
they provide EXACTLY.


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux