Die ATI Krise unter Slack

Dieses Thema im Forum "Slackware" wurde erstellt von z00k, 31.07.2006.

  1. z00k

    z00k I love my slack! Do u?

    Dabei seit:
    24.01.2005
    Beiträge:
    302
    Zustimmungen:
    0
    Ort:
    earth.getLocation("z00k");
    ey leutz!

    hab vor ein paar tagen meine GF4 gegen ne ATI Radeon 9500 ausgewechselt um mich endlich mal mit dem altbekannten prob: 'ATI unter Linux' auseinander zu setzen...

    Hab den Installer (v8.27.10) von ATI verwendet und bis auf das Kernel Module (das zickt so und so nur rum bei mir) alles installed und der Treiber laeuft auch brav...

    ABER:
    Zuerst mal sagt mir 'ATI Control' dass OpenGL verfuegbar waere:
    OpenGL: Vendor: ATI Version: 2.0.5946

    doch wenn ich nun zB. Quake3 oder sowas laufen lasse sieht dass eher so aus als haette ich noch ne Voodoo 2 oder ahnliches :D
    es startet ohne zicken (von wegen blaa nix OpenGL support oder sowas) aber ruckelt halt ohne ende auf 640x480 das es auf KEINEN fall speilbar waere... tippe mal so auf 4-5 FPS :D

    natuerlich habe ich mich auch mit dem von ATI mitgelieferten tool 'aticonfig' beschaeftigt und die grund settings gemacht... aber mal ehrlich: das tool ist doch voll der krampf...

    Tja also gibt es noch moeglichkeiten die karte vernueftig ans rennen zu kriegen oder ist das ein hoffnungsloser fall?

    Software:
    Slackware 10.2 mit kernel v2.6.17.7
    ATI Driver v8.27.10
    Xorg 6.8.2

    hier noch meine xorg.conf:

    xorg.conf


    tHx for help!

    gReetZ
     
  2. Anzeige

    Schau dir mal diese Kategorie an. Dort findest du bestimmt etwas.
    Registrieren bzw. einloggen, um diese und auch andere Anzeigen zu deaktivieren
  3. #2 FalseCAM, 31.07.2006
    FalseCAM

    FalseCAM Tripel-As

    Dabei seit:
    24.12.2005
    Beiträge:
    155
    Zustimmungen:
    0
    Hast du den Treiber auch aus dem Runlevel 3 heraus installiert?
    Wenn du ihn nur in der Konsole im Runlevel 5 installierst hat er keine 3d accelleration.
     
  4. z00k

    z00k I love my slack! Do u?

    Dabei seit:
    24.01.2005
    Beiträge:
    302
    Zustimmungen:
    0
    Ort:
    earth.getLocation("z00k");
    jo hab ich
     
  5. Rothut

    Rothut --------------------

    Dabei seit:
    05.10.2005
    Beiträge:
    442
    Zustimmungen:
    0
    Ort:
    Deutschland
    Hört sich an als wäre Software-Beschleunigung an?!
     
  6. z00k

    z00k I love my slack! Do u?

    Dabei seit:
    24.01.2005
    Beiträge:
    302
    Zustimmungen:
    0
    Ort:
    earth.getLocation("z00k");
    oehm... ja? :D da die OpenGL engine ja funzt denke ich schon.... aber wo mach ich die denn an bzw. aus?

    gReetZ
     
  7. theton

    theton Bitmuncher

    Dabei seit:
    27.05.2004
    Beiträge:
    4.820
    Zustimmungen:
    0
    Ort:
    Berlin, Germany
    Ohne Kernel-Modul wird auch Hardware-3D nicht zur Verfuegung stehen. Daher einfach mal das Kernel-Modul installieren. In dem Moment wo das Modul geladen wird, wird auch automatisch auf Hardware-Beschleunigung umgestellt.
     
  8. z00k

    z00k I love my slack! Do u?

    Dabei seit:
    24.01.2005
    Beiträge:
    302
    Zustimmungen:
    0
    Ort:
    earth.getLocation("z00k");
    hatte den treiber auch schon mit dem kernel module am laufen...
    war kein unterschied zu jetzt...

    OpenGL ist ja auch vorhanden, nur rennt es super rueckwaertsgang...
     
  9. theton

    theton Bitmuncher

    Dabei seit:
    27.05.2004
    Beiträge:
    4.820
    Zustimmungen:
    0
    Ort:
    Berlin, Germany
    OpenGL ist auch komplett ohne ATI-Treiber vorhanden. *anmerk* Trotzdem scheint bei dir nur die Software-Beschleunigung an zu sein. Und Hardware-3D gibt's nunmal nur mit dem Kernel-Modul.
     
  10. timg

    timg Ubuntu User

    Dabei seit:
    02.08.2006
    Beiträge:
    13
    Zustimmungen:
    0
    Ort:
    Münster
    Ich habe so ziemlich das gleiche Problem, die 3D-Beschleunigung funktioniert, nur extrem langsam.
    "lsmod" zeigt an, dass fglrx geladen ist, und "glxinfo|head -3" gibt aus:

    name of display: :0.0
    display: :0 screen: 0
    direct rendering: Yes

    glxgears hat trotz anscheinender 3D-Beschleunigung nur ~200fps

    Weiß jemand wie man das besser hinbekommt?
     
  11. theton

    theton Bitmuncher

    Dabei seit:
    27.05.2004
    Beiträge:
    4.820
    Zustimmungen:
    0
    Ort:
    Berlin, Germany
    Was reicht dir an 200 Frames pro Sekunde nicht? Glaubst du, dass es wirklich was ausmacht, wenn du noch nen paar mehr rauskitzelst? Deine Augen (bzw. dein Gehirn) arbeiten eh nicht schnell genug um dort einen Unterschied zu bemerken.
     
  12. timg

    timg Ubuntu User

    Dabei seit:
    02.08.2006
    Beiträge:
    13
    Zustimmungen:
    0
    Ort:
    Münster
    Darum geht es doch gar nicht, natürlich wäre ich bei einem topmodernen 3D-Programm froh, wenn es mit 200fps liefe, bei diesem benchmark (probier in doch selber mal aus^^) habe ich schon mit software-rendering 120fps...

    ausserdem laufen z.b. OpenGL- Bildschirmschoner nur mit höchsten 2fps oder etwas in der richtung, das ist ja wohl nicht normal.
    Ich habe keine Ahnung woran das liegen kann?!
     
  13. theton

    theton Bitmuncher

    Dabei seit:
    27.05.2004
    Beiträge:
    4.820
    Zustimmungen:
    0
    Ort:
    Berlin, Germany
    Ist das DRI-Modul in deiner xorg.conf eingetragen?
     
  14. timg

    timg Ubuntu User

    Dabei seit:
    02.08.2006
    Beiträge:
    13
    Zustimmungen:
    0
    Ort:
    Münster
    jop

    übrigens handelt es sich bei der karte um eine Radeon 9800Pro
    Code:
    # 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.
    # **********************************************************************
    
    # NOTE:  This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa
    # driver instead of the fbdev driver.  Thanks to Kenneth Fanyo who pointed
    # this out to me. :)
    
    # This XF86Config file is designed for use with the VESA framebuffer.
    # This generic interface should work with nearly all video cards
    # (although not every card will support every resolution).
    
    # With the new driver, it should no longer be required to have frame buffer
    # support in the kernel, or to run it on the console.
    #
    # Enjoy! :)
    # -- volkerdi@slackware.com
    #
    
    # **********************************************************************
    # 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        "freetype"
        #Load        "speedo"
    
    # This loads the GLX module
        Load       "glx"
        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/Type1/"
        FontPath   "/usr/X11R6/lib/X11/fonts/CID/"
        FontPath   "/usr/X11R6/lib/X11/fonts/Speedo/"
        FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/"
        FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/"
        FontPath   "/usr/X11R6/lib/X11/fonts/cyrillic/"
    
    # ModulePath can be used to set a search path for the X server modules.
    # 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     "DontZoom"
    
    # 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"
    
    # Set the basic blanking screen saver timeout.
    
    #    Option      "blank time"    "10"    # 10 minutes
    
    # Set the DPMS timeouts.  These are set here because they are global
    # rather than screen-specific.  These settings alone don't enable DPMS.
    # It is enabled per-screen (or per-monitor), and even then only when
    # the driver supports it.
    
    #    Option      "standby time"  "20"
    #    Option      "suspend time"  "30"
    #    Option      "off time"      "60"
    
    # On some platform the server needs to estimate the sizes of PCI
    # memory and pio ranges. This is done by assuming that PCI ranges
    # don't overlap. Some broken BIOSes tend to set ranges of inactive
    # devices wrong. Here one can adjust how aggressive the assumptions
    # should be. Default is 0.
    
    # Option   "EstimateSizesAggresively" "0"
    
    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"
    
    # Set the keyboard auto repeat parameters.  Not all platforms implement
    # this.
    
    #    Option     "AutoRepeat"    "500 5"
    
    # Specifiy 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 European
    # keyboard, you will probably want to use one of:
    #
    #    Option     "XkbModel"      "pc102"
    #    Option     "XkbModel"      "pc105"
    #
    # If you have a Microsoft Natural keyboard, you can use:
    #
    #    Option     "XkbModel"      "microsoft"
    #
    # If you have a US "windows" keyboard you will want:
    #
    #    Option     "XkbModel"      "pc104"
    #
    # 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 X.Org
    #
    #    Option     "XkbRules"      "xorg"
    #    Option     "XkbModel"      "pc101"
    #    Option     "XkbLayout"     "us"
    #    Option     "XkbVariant"    ""
    #    Option     "XkbOptions"    ""
    
    EndSection
    
    
    # **********************************************************************
    # Core Pointer's InputDevice section
    # **********************************************************************
    
    Section "InputDevice"
    
    # Identifier and driver
    
        Identifier	"Mouse1"
        Driver	"mouse"
    
        Option "ZAxisMapping" "4 5"
    # On platforms where PnP mouse detection is supported the following
    # protocol setting can be used when using a newer PnP mouse:
    
    #    Option     "Protocol"      "Auto"
    
    # The available mouse protocols types that you can set below are:
    #    Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
    #    Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
    #    MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
    #    ThinkingMouse ThinkingMousePS/2 Xqueue
        Option "Protocol"    "IMPS/2"
    
    # The mouse device.  The device is normally set to /dev/mouse,
    # which is usually a symbolic link to the real device.
    
        Option "Device"      "/dev/mouse"
    #   Option "Device"      "/dev/psaux"
    #   Option "Device"      "/dev/ttyS0"
    #   Option "Device"      "/dev/ttyS1"
    
    # 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
    
    # Some examples of extended input devices
    
    # 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  "My 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 80.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 56-75
    
    EndSection
    
    
    # **********************************************************************
    # Graphics device section
    # **********************************************************************
    
    # Any number of graphics device sections may be present
    
    Section "Device"
        Identifier  "fglrx"
        Driver      "fglrx"
        #VideoRam    4096
        # 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      "fglrx"
        Monitor     "My Monitor"
    
    # If your card can handle it, a higher default color depth (like 24 or 32)
    # is highly recommended.
    
    #   DefaultDepth 8
    #   DefaultDepth 16
       DefaultDepth 24
    #   DefaultDepth 32
    
    # "1024x768" is also a conservative usable default resolution.  If you
    # have a better monitor, feel free to try resolutions such as
    # "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
    # card/monitor can produce)
    
        Subsection "Display"
            Depth       8
            Modes "1024x768" "800x600" "640x480"
        EndSubsection
        Subsection "Display"
            Depth       16
            Modes "1024x768" "800x600" "640x480"
        EndSubsection
        Subsection "Display"
            Depth       24
            Modes "1280x1024" "1024x768" "800x600" "640x480"
        EndSubsection
        Subsection "Display"
            Depth       32
            Modes "1024x768" "800x600" "640x480"
        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"
    	Group 0
    	Mode 0666
    EndSection
     
  15. Anzeige

    Vielleicht findest du HIER Antworten.
    Registrieren bzw. einloggen, um diese und auch andere Anzeigen zu deaktivieren
  16. theton

    theton Bitmuncher

    Dabei seit:
    27.05.2004
    Beiträge:
    4.820
    Zustimmungen:
    0
    Ort:
    Berlin, Germany
    Das DRM-Modul vermisse ich bei dir. *anmerk*

    Meine Modules-Section
    Code:
    Section "Module"
      Load         "type1"
      Load         "dri"
      Load         "dbe"
      Load         "extmod"
      Load         "freetype"
      Load         "drm"
      Load         "glx"
      Load         "v4l"
    EndSection
    
     
  17. timg

    timg Ubuntu User

    Dabei seit:
    02.08.2006
    Beiträge:
    13
    Zustimmungen:
    0
    Ort:
    Münster
    sieht schon besser aus, so ~270fps,
    ich hab grad noch kein spiel zum testen,
    aber erstmal danke
     
Thema:

Die ATI Krise unter Slack

Die Seite wird geladen...

Die ATI Krise unter Slack - Ähnliche Themen

  1. Jolla nimmt Stellung zur Finanzkrise des Unternehmens

    Jolla nimmt Stellung zur Finanzkrise des Unternehmens: Jollas Mitbegründer und Vorstandsvorsitzender Antti Saarnio hat in einem offenen Brief an die Community dargelegt, wie die jetzige Finanzkrise...
  2. LinuxTag 2009 widersteht der Krise

    LinuxTag 2009 widersteht der Krise: Ohne eine Spur von Krise ist der LinuxTag 2009 in Berlin zu Ende gegangen, der über 10.000 Besucher anzog. Weiterlesen...
  3. Update auf Apache >=2.4.12 unter Debian Jessie

    Update auf Apache >=2.4.12 unter Debian Jessie: Hi, aufgrund eines Bugs in Apache 2.4 benötige ich zum Deployment von Seafile unter Debian Jessie das Paket apache2 in der Version >= 2.4.12...
  4. Was mache ich falsch? Tiniywm und Mate Install unter OpenBSD

    Was mache ich falsch? Tiniywm und Mate Install unter OpenBSD: Hallo, # make tiny make: don't know how to make tiny Stop in /root/Downloads/tiny/tinywm-1.3 # make tinywm cc -O2 -pipe -o tinywm tinywm.c...
  5. Samba unter Windows 10

    Samba unter Windows 10: Hallo zusammen, ich habe auf meinen Ubuntu Server Samba installiert und eingerichtet. ich kann mich bei Windows 10 mit den Daten anmelden und...