aligator
Feb 21, 2008, updated at Mar 03, 2008 (UTC)
view5941
view4
0
Goto Top

Grafikkartenprobleme bei SLES9 auf VM

GermanQuestionLinux
Hallo zusammen,

vorweg zum Host Rechner:
Der Hostrechner ist eine 64 Bit Maschine auf welcher Vista(64 Bit) zum einsatz kommt.
Auf dieser Maschine ist installiert VMware Workstation Version 6.0.0 build-45731
Nun soll eine Virtueller Suse Linux Enterprise Server 9 mithilfe von VMware aufgesetzt werden, was soweit auch ohne weiteres erfolgte.

Nach erfolgter Installation bootet die Kiste leider nur im Textmodus, Terminal oder wie auch immer. Der Versuch den x server zu starten schlägt fehl.
Durch mehrstündiger Internetrecherge (Wie schreibt man das? Oo) habe ich es geschaft mithilfe des Befehls "xf86config" die erkannte Grafikkarte bzw. Monitor unter dem Vesa Treiber zu laden und den x server zu starten.

Problem ist jetzt, dass ich eine sehr geringe Auflösung habe und so nicht wirklich arbeiten kann, schließlich soll auf die Maschine noch irgendwie ne Oracle Datenbank drauf.
Habe auch schon mehrere Varianten der konfiguration mit dem oben genannten Befehl versucht, jedoch erfolglos. Die Auflösung wird nicht höher, mit meiner Grafikkarte kann er nichts anfangen. Der x server startet nur wenn ich die niedrigste Konfiguration wähle.

Per Sax2 konnte ich auch diverse Einstellungen vornehmen, die weiter unten genannte Grafikkarte ist hier jedoch nicht aufgelistet.

Auch habe ich irgendwo aufgeschnappt dass VMware einen eigenen Grafikadapter benutzt und nicht den des Hostrechners.

Die Grafikkarte des Hostrechners ist eine RADEON XPRESS 200 Series und der Monitor ein ViewSonic 17/GS-2, ne alte Röhre.

Wie ihr sicher seht bin ich noch sehr grün hinter den Ohren was Unix Systeme angeht, kann aber lesen und lerne recht schnell, behaupte ich jetzt mal so ;)

Für Tips, hints, links usw. bin ich euch jetzt schon sehr dankbar.

Gruß

Aligator
comment-contentCommentShareShare
Share on Facebook Share on Twitter Share on Reddit Share on Linkedin

Content-Key: 81354

Url: https://administrator.de/contentid/81354

Printed on: April 23, 2024 at 08:04 o'clock

4 Comments
Latest comment
Goto Top
Member: theton
theton Feb 21, 2008 at 22:07:58 (UTC)
Goto Top
Wie sieht die /etc/X11/xorg.conf der VM aus?
Member: Aligator
Aligator Feb 22, 2008 at 07:48:33 (UTC)
Goto Top
eine xorg.conf kann ich unter dem Pfad nicht finden.

Vielleicht hilft die XF86Config?

  1. File generated by xf86config.

#
  1. Copyright (c) 1999 by The XFree86 Project, Inc.
#
  1. Permission is hereby granted, free of charge, to any person obtaining a
  2. copy of this software and associated documentation files (the "Software"),
  3. to deal in the Software without restriction, including without limitation
  4. the rights to use, copy, modify, merge, publish, distribute, sublicense,
  5. and/or sell copies of the Software, and to permit persons to whom the
  6. Software is furnished to do so, subject to the following conditions:
  8. The above copyright notice and this permission notice shall be included in
  9. all copies or substantial portions of the Software.
  11. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
  12. IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
  13. FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
  14. THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
  15. WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
  16. OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
  17. SOFTWARE.
  19. Except as contained in this notice, the name of the XFree86 Project shall
  20. not be used in advertising or otherwise to promote the sale, use or other
  21. dealings in this Software without prior written authorization from the
  22. XFree86 Project.
#

  2. Refer to the XF86Config(4/5) man page for details about the format of
  3. this file.

  2. Module section -- this section is used to specify
  3. which dynamically loadable modules to load.
#
Section "Module"

  1. This loads the DBE extension module.

Load "dbe" # Double buffer extension

  1. This loads the miscellaneous extensions module, and disables
  2. initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection

  1. This loads the Type1 and FreeType font modules
Load "type1"
Load "speedo"
Load "freetype"
  1. Load "xtt"

  1. This loads the GLX module
  2. Load "glx"
  3. This loads the DRI module
  4. Load "dri"

EndSection

  2. Files section. This allows default font and rgb paths to be set

Section "Files"

  1. The location of the RGB database. Note, this is the name of the
  2. file minus the extension (like ".txt" or ".db"). There is normally
  3. no need to change the default.

RgbPath "/usr/X11R6/lib/X11/rgb"

  1. Multiple FontPath entries are allowed (which are concatenated together),
  2. as well as specifying multiple comma-separated entries in one FontPath
  3. command (or a combination of both methods)
  5. If you don't have a floating point coprocessor and emacs, Mosaic or other
  6. programs take long to start up, try moving the Type1 and Speedo directory
  7. 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"
  1. FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
  1. FontPath "/usr/X11R6/lib/X11/fonts/TrueType/"
  2. FontPath "/usr/X11R6/lib/X11/fonts/freefont/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
  1. FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"

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

  1. ModulePath "/usr/X11R6/lib/modules"

EndSection

  2. Server flags section.

Section "ServerFlags"

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

  1. Option "NoTrapSignals"

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

  1. Option "DontVTSwitch"

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

  1. Option "DontZap"

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

  1. Option "Dont Zoom"

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

  1. Option "DisableVidModeExtension"

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

  1. Option "AllowNonLocalXvidtune"

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

  1. Option "DisableModInDev"

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

  1. Option "AllowNonLocalModInDev"

EndSection

  2. Input devices

  2. Core keyboard's InputDevice section

Section "InputDevice"

Identifier "Keyboard1"
Driver "Keyboard"

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

  1. Option "Protocol" "Xqueue"

Option "AutoRepeat" "500 30"

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

  1. Option "LeftAlt" "Meta"
  2. Option "RightAlt" "ModeShift"

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

  1. These are the default XKB settings for XFree86
  2. Option "XkbRules" "xfree86"
  3. Option "XkbModel" "pc101"
  4. Option "XkbLayout" "us"
  5. Option "XkbVariant" ""
  6. Option "XkbOptions" ""

  1. Option "XkbDisable"

Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "de"

EndSection


  2. Core Pointer's InputDevice section

Section "InputDevice"

  1. Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto"
Option "Device" "/dev/mouse"

  1. Mouse-speed setting for PS/2 mouse.

  1. Option "Resolution" "256"

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

  1. Option "Protocol" "Xqueue"

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

  1. Option "BaudRate" "9600"
  2. Option "SampleRate" "150"

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

Option "Emulate3Buttons"
  1. Option "Emulate3Timeout" "50"

  1. ChordMiddle is an option for some 3-button Logitech mice

  1. Option "ChordMiddle"

EndSection


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

  2. Monitor section

  1. Any number of monitor sections may be present

Section "Monitor"

Identifier "My Monitor"

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

HorizSync 31.5

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

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

VertRefresh 50-90

EndSection


  2. Graphics device section

  1. Any number of graphics device sections may be present

  1. Standard VGA Device:

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

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

  1. Chipset "generic"

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

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

  1. BusID "PCI:0:10:0"

  1. VideoRam 256

  1. Clocks 25.2 28.3

EndSection

  1. Device configured by xf86config:

Section "Device"
Identifier "* Generic VESA compatible"
Driver "vesa"
#VideoRam 131072
          1. Insert Clocks lines here if appropriate
          EndSection


          2. Screen sections

          1. Any number of screen sections may be present. Each describes
          2. the configuration of a single screen. A single specific screen section
          3. may be specified from the X server command line with the "-screen"
          4. option.
          Section "Screen"
          Identifier "Screen 1"
          Device "* Generic VESA compatible"
          Monitor "My Monitor"
          DefaultDepth 16

          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

          2. ServerLayout sections.

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

          Section "ServerLayout"

          1. The Identifier line must be present
          Identifier "Simple Layout"

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

          Screen "Screen 1"

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

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

          EndSection

          1. Section "DRI"
          2. Mode 0666
          3. EndSection


          Gruß und Dank für die schnelle Reaktion.
Member: theton
theton Feb 22, 2008 at 12:49:43 (UTC)
Goto Top
Du musst als Treiber für die Grafikkarte "vmware" benutzen. Dieser muss natürlich auch installiert sein. Evtl. musst du für höhere Auflösungen eine Modeline erstellen. Das kannst du mit videogen machen und die Modeline dann in die Section "Monitor" eintragen.
Member: Aligator
Aligator Mar 03, 2008 at 09:08:51 (UTC)
Goto Top
Sry dass ich erst jetzt antworte, ich war die letzte woche auf fortbildung und konnte mich demnach nicht weiter damit beschäftigen.

danke für den treiberhinweis. habe auf vmware umgestellt und siehe da, ich kann die auflösung hochschrauben und der xserver startet immer noch.

vielen Dank
GermanQuestionLinux
Hotly discussed
gleixnerdCheck of ZFW Firewallgleixnerd - 5 CommentsjstrickerWireguard VPN on UDM Pro behind Fritzbox - Handshake did not completejstricker - 3 CommentsAlexWishaHow to set up and configure a Linux GRE tunnelAlexWisha - 3 CommentsDaniEnd of Support dates for Office 2016, 2019 Apps und Productivity ServersDani - 1 Comment