AudunSæther Skrevet 18. februar 2005 Del Skrevet 18. februar 2005 Hepp. Anskaffet en likedan skjerm som jeg har fra før, og prøver å sette opp et såkalt "Big Desktop" via fglrxconfig. Når X starter fungerer den ene skjermen (som er koblet til VGA-utgangen) som vanlig (altså skjermen til venstre), og skrivebordet er så stort som det skal være (om jeg maksimerer et vindu ser jeg altså bare halvparten her). Den andre skjermen (som er koblet i DVI-utgangen, med en DVI->VGA overgang, om det har noe å si) er derimot helt svart. Den er ikke av, eller i noe "standby-mode", det lyser akkurat slik det skal gjøre. Men altså ikke noe bilde. X-config'en; # File: XF86Config-4 # File generated by fglrxconfig (C) ATI Research, a substitute for xf86config. # ********************************************************************** # Refer to the XF86Config(4/5) man page for details about the format of # this file. # ********************************************************************** # ********************************************************************** # DRI Section # ********************************************************************** Section "dri" # Access to OpenGL ICD is allowed for all users: Mode 0666 # Access to OpenGL ICD is restricted to a specific user group: # Group 100 # users # Mode 0660 EndSection # ********************************************************************** # 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 "freetype" # This loads the GLX module Load "glx" # libglx.a Load "dri" # libdri.a 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" # 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/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" 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 <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 "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" "pc104" Option "XkbLayout" "no" EndSection # ********************************************************************** # Core Pointer's InputDevice section # ********************************************************************** Section "InputDevice" # Identifier and driver Identifier "Mouse1" Driver "mouse" Option "Protocol" "ImPS/2" Option "ZAxisMapping" "4 5" Option "Device" "/dev/input/mice" # 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 # ** # ********************************************************************** # Monitor section # ********************************************************************** # Any number of monitor sections may be present Section "Monitor" Identifier "Monitor0" HorizSync 31.5 - 80.5 VertRefresh 60 - 75 Option "DPMS" EndSection Section "Monitor" Identifier "Monitor1" HorizSync 31.5 - 80.5 VertRefresh 60 - 75 Option "DPMS" 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" Driver "vga" # BusID "PCI:0:10:0" # VideoRam 256 # Clocks 25.2 28.3 EndSection # === ATI device section === Section "Device" Identifier "ATI Graphics Adapter" Driver "fglrx" # ### generic DRI settings ### # === disable PnP Monitor === #Option "NoDDC" # === disable/enable XAA/DRI === Option "no_accel" "no" Option "no_dri" "no" # === misc DRI settings === Option "mtrr" "off" # disable DRI mtrr mapper, driver has its own code for mtrr # ### FireGL DDX driver module specific settings ### # === Screen Management === Option "DesktopSetup" "0x00000201" Option "MonitorLayout" "AUTO, AUTO" Option "IgnoreEDID" "off" Option "HSync2" "31.5 - 80.5" Option "VRefresh2" "60 - 75" Option "ScreenOverlap" "0" # === TV-out Management === Option "NoTV" "yes" Option "TVStandard" "NTSC-M" Option "TVHSizeAdj" "0" Option "TVVSizeAdj" "0" Option "TVHPosAdj" "0" Option "TVVPosAdj" "0" Option "TVHStartAdj" "0" Option "TVColorAdj" "0" Option "GammaCorrectionI" "0x00000000" Option "GammaCorrectionII" "0x00000000" # === OpenGL specific profiles/settings === Option "Capabilities" "0x00000000" # === Video Overlay for the Xv extension === Option "VideoOverlay" "on" # === OpenGL Overlay === # Note: When OpenGL Overlay is enabled, Video Overlay # will be disabled automatically Option "OpenGLOverlay" "off" # === Center Mode (Laptops only) === Option "CenterMode" "off" # === Pseudo Color Visuals (8-bit visuals) === Option "PseudoColorVisuals" "off" # === QBS Management === Option "Stereo" "off" Option "StereoSyncEnable" "1" # === FSAA Management === Option "FSAAEnable" "no" Option "FSAAScale" "1" Option "FSAADisableGamma" "no" Option "FSAACustomizeMSPos" "no" Option "FSAAMSPosX0" "0.000000" Option "FSAAMSPosY0" "0.000000" Option "FSAAMSPosX1" "0.000000" Option "FSAAMSPosY1" "0.000000" Option "FSAAMSPosX2" "0.000000" Option "FSAAMSPosY2" "0.000000" Option "FSAAMSPosX3" "0.000000" Option "FSAAMSPosY3" "0.000000" Option "FSAAMSPosX4" "0.000000" Option "FSAAMSPosY4" "0.000000" Option "FSAAMSPosX5" "0.000000" Option "FSAAMSPosY5" "0.000000" # === Misc Options === Option "UseFastTLS" "0" Option "BlockSignalsOnLock" "on" Option "UseInternalAGPGART" "yes" Option "ForceGenericCPU" "no" Option "KernelModuleParm" "agplock=0" # AGP locked user pages: disabled BusID "PCI:1:0:0" # vendor=1002, device=4150 Screen 0 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 "Screen0" Device "ATI Graphics Adapter" Monitor "Monitor0" DefaultDepth 24 #Option "backingstore" Subsection "Display" Depth 24 Modes "1280x1024" ViewPort 0 0 # initial origin if mode is smaller than desktop # Virtual 1280 1024 EndSubsection EndSection # ********************************************************************** # ServerLayout sections. # ********************************************************************** Section "ServerLayout" # The Identifier line must be present Identifier "Server Layout" Screen "Screen0" InputDevice "Mouse1" "CorePointer" InputDevice "Keyboard1" "CoreKeyboard" EndSection ### EOF ### Noen som kan hjelpe meg her ? Lenke til kommentar
objorkum Skrevet 18. februar 2005 Del Skrevet 18. februar 2005 (endret) Trur nok at Big Desktop ikkje fungerar skikkeleg for mange endå. Big Desktop suger på ATi-drivarane uansett. Xinerama-emulering hadde vore best. Uansett, spør her, der dei har peiling: http://www.rage3d.com/board/forumdisplay.php?f=61 Gå inn i Drivers forumet Endret 18. februar 2005 av objorkum Lenke til kommentar
AudunSæther Skrevet 18. februar 2005 Forfatter Del Skrevet 18. februar 2005 (endret) Okey, skal se der. Hva er forskjellen på Big Desktop og xinerama ? EDIT: glem det, jeg kan vel RTFM Endret 18. februar 2005 av Izte Lenke til kommentar
objorkum Skrevet 18. februar 2005 Del Skrevet 18. februar 2005 Kan godt forklare det eg: Big Desktop er kva det betyr, ein einaste stor desktop. Vindaugsbehandlaren du bruker (KDE/GNOME/Anna) ser dei 2 skjermane som ein einaste stor skjerm. Det er ikkje satt opp 2 skjermar og screens i xorg.conf, men Big Desktop vert definert i ATi-drivarens options. Om du har vore borti fleire skjermar i Windows, er Xinerama mykje det same. F.eks om du maksimerar eit vindauge på den eine skjermen, vert vindauget kun maksimert på den skjermen. Med Big Desktop vert vindauge over begge skjermane, og mange ting kjem midt i mellom skjermane. Det som er bra med Big Desktop i motsetning til Xinerama er at BD bruker GPU (skjermkortets prosessor), mens Xinerama belastar CPU. NVIDIA har eit flott system for Xinerama gjennom GPU. Lenke til kommentar
AudunSæther Skrevet 18. februar 2005 Forfatter Del Skrevet 18. februar 2005 Okey, da har jeg fått litt innsikt.. Har sett litt på Dualhead også. Har jeg forstått det slik at det da kjøres to helt forskjellige X-servere? Hvordan får jeg startet den andre serveren med en vm ? Tror jeg skal sette ett NVIDIA-kort litt høyere på prioriteringslisten Lenke til kommentar
LessThanJake Skrevet 18. februar 2005 Del Skrevet 18. februar 2005 Hvis du har to X-servere startet vil du ikke kunne flytte musen fra den ene til den andre helt uten videre. Hvis du ikke har behov for 3d-ytelse, på begge skjermer fungerer xinerama glimrene. Lenke til kommentar
Anbefalte innlegg
Opprett en konto eller logg inn for å kommentere
Du må være et medlem for å kunne skrive en kommentar
Opprett konto
Det er enkelt å melde seg inn for å starte en ny konto!
Start en kontoLogg inn
Har du allerede en konto? Logg inn her.
Logg inn nå