Kezdőlap › Fórumok › Slackware, Slax problémák › Slackware 10.0
- This topic has 483 hozzászólás, 39 résztvevő, and was last updated 20 years, 6 months telt el by
kmARC.
-
SzerzőBejegyzés
-
2004-09-03-20:19 #1955300
az igazán szar, hogy dcop server gondja van mindig így nem tudom ezeket root-ként indítani
valahogy ezt a dcop_server nyvaját el lehet indítani? vag valamit csinálni vele, hoyg ne szórakozzon itt velem…2004-09-03-21:30 #1955301asszem megvan a gond!!!!!
ez is összeomlott grafikusan…
bekopizom ide a xf86conf-ot meg a legvégét a lognak és ha lehet akkor segítsetek légyszíves
köszi 😀 😀 😀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”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 „/usr/X11R6/lib/X11/fonts/local/”
FontPath „/usr/X11R6/lib/X11/fonts/misc/”
FontPath „/usr/X11R6/lib/X11/fonts/75dpi/:unscaled”
FontPath „/usr/X11R6/lib/X11/fonts/100dpi/:unscaled”
FontPath „/usr/X11R6/lib/X11/fonts/Speedo/”
FontPath „/usr/X11R6/lib/X11/fonts/Type1/”
# FontPath „/usr/X11R6/lib/X11/fonts/TrueType/”
# FontPath „/usr/X11R6/lib/X11/fonts/freefont/”
FontPath „/usr/X11R6/lib/X11/fonts/75dpi/”
FontPath „/usr/X11R6/lib/X11/fonts/100dpi/”# 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 VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.# Option „DontVTSwitch”
# Uncomment this to disable the server abort sequence
# This allows clients to receive this key event.# Option „DontZap”
# Uncomment this to disable the / 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 „Keyboard”# 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” „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”# These are the default XKB settings for XFree86
# Option „XkbRules” „xfree86”
# Option „XkbModel” „pc101”
# Option „XkbLayout” „us”
# Option „XkbVariant” „”
# Option „XkbOptions” „”# Option „XkbDisable”
Option „XkbRules” „xfree86”
Option „XkbModel” „chicony9885”
Option „XkbLayout” „hu”EndSection
# **********************************************************************
# Core Pointer’s InputDevice section
# **********************************************************************Section „InputDevice”
# Identifier and driver
Identifier „Mouse1”
Driver „mouse”
Option „Protocol” „IMPS/2”
Option „Device” „/dev/mouse”
Option „ZAxisMapping” „4 5 6 7”
Option „Buttons” „12”# 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 XF86Config 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 „monitor”
# 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 31.5 – 57.0
# 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-90
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 „nvidia”
# 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 xf86config:
Section „Device”
Identifier „card”
Driver „nvidia”
# unsupported card
#VideoRam 131072
# 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 „card”
Monitor „monitor”
DefaultDepth 24Subsection „Display”
Depth 8
Modes „1280×1024” „1024×768” „800×600” „640×480”
ViewPort 0 0
EndSubsection
Subsection „Display”
Depth 16
Modes „1280×1024” „1024×768” „800×600” „640×480”
ViewPort 0 0
EndSubsection
Subsection „Display”
Depth 24
Modes „1280×1024” „1024×768” „800×600” „640×480”
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
# EndSectionez meg a log
(II) NVIDIA(0): AGP 8X successfully initialized
(II) NVIDIA(0): Setting mode „1024×768”
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(II) Loading extension NV-CONTROL
(EE) NVIDIA(0): Failed to load GLX <<<<
csak ez az error van!!!!!
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUPtaláltam még két-három warningot is.
kérdésem: ez okozhattja-e ezt az összeomlást?
mit kéne még beállítanom?tényleg köszi a segítséget és bocs a hosszért…
2004-09-03-22:27 #1955302rakd ujra az nvidia drivert.
2004-09-03-22:59 #1955303összehasonlítottam az uhu konfigjával is , hát elég gyenge…
itt nem kell komment a glx és a dri elé, meg a fontok elé sem…na ma is tanultam valamit 😀 😀 😀 😀
2004-09-04-08:27 #1955304Semmilyen distribben nem kell elé (elvileg, aztán ki tudja). Az x kiír egy hibaüzit, aztán csókolom, megy anélkül.
2004-09-04-11:24 #1955305tudom, de lusta vagyok és szeretem megoldani a dolgokat copy-paste megoldásokkal, de úgy látom, hoyg ez slacki alatt nem egy…
[align=right][snapback]80751[/snapback][/align]Ezt nemértem… Nekem a konzolrol copy is megy pld a firefoxba
2004-09-04-11:41 #1955306Neki opera -> gedit nem megy.
Nem tudom, de szerintem opera -> konzol is megy. (Spec. ezt slack alatt nem próbáltam, de miért ne menne.)2004-09-04-13:24 #1955307megvan, hoyg mi volt a gond!!!!
a home egy külön partición volt és nem voltak teljesen átadva a jogok egyik esetben sem…
mostmár oké
a sylpheed is meggyógyult a meg szerintem azért nem adta át az url -címet a böngészõnek mert egyrészt nem ment a dcop meg lehet, hoyg a glx -nek is szerepe volt…
jelenleg megy minden… 😀 😀 😀
2004-09-04-13:41 #1955308Akkor jó!
2004-09-04-14:04 #1955309Akkor jó!
[align=right][snapback]80942[/snapback][/align]egy frászt!!!
reboot és minden hullik szét megint…kérdés: lehet-e az a gond, hoyg home nak egy particiót felcsatolk nem pedig szimlinkezem?
már csak ez jut eszembe, hoyg mi a franc baja lehet… -
SzerzőBejegyzés
- Be kell jelentkezni a hozzászóláshoz.
legutóbbi hsz