Quoting Marko Schulz ([EMAIL PROTECTED]): > > wenn ich Gravitywars starte, bleibt der Bildschirm schwarz. Anscheinend wird > > das Spiel aber gestartet. Ich bin echt am Verzweifeln. Hilfe! > > > > ii gravitywars 1.102-9 Clone of Gravity Force, for SVGA > > ii svgalibg1 1.2.13-3.3 SVGA display utilities > > > > Grafikkarte: Diamond Viper 330 (Riva 128) > > Laufen denn andere Programme, die die svgalib benutzen? So wie maelstrom > oder dvisvga (oder hieß es tmview, *grübel*)? Wenn nicht, dann solltest > Du wohl an Deiner /etc/vga/libvga.config mal rumbasteln.
zgv läuft (üble Auflösung), maelstrom nicht: [EMAIL PROTECTED]:~ > maelstrom Using VGA driver. VGA_FrameBuf: Video hardware doesn't support requested mode! Es scheint also an der /etc/vga/libvga.config zu liegen. Leider konnte ich sie bisher nicht davon überzeugen andere Videomodes zu benutzen. Ich schicke einfach mal meine aktuelle Datei mit. Holgi -- PGP-Key available on request. ICQ: 19527431 IRC: L3guan
# Configuration file for svgalib. Default location is /etc/vga. # Lines starting with '#' are ignored. # Have a deep look at README.config to see what can do here (especially # for mach32). # Mouse type: # mouse Microsoft # Microsoft # mouse MouseSystems # Mouse Systems # mouse MMSeries # Logitech MM Series # mouse Logitech # Logitech protocol (old, newer mice use Microsoft protocol) # mouse Busmouse # Bus mouse # mouse PS2 # PS/2 mouse # mouse MouseMan # Logitech MouseMan # mouse Spaceball # Spacetec Spaceball # mouse none # None mouse PS2 # (DEBIAN NOTE: the mouse used to default to microsoft, but this was changed # to fix bug #13458. If your mouse used to work fine, you can simply change # it back to read "microsoft" again. If you are careful to change *only that # one word*, and not to add or remove extra whitespace, the package # installation will continue to update this file without requiring user # intervention because of a modified config file. # This applies to all mouse types, not just microsoft.) # Usually /dev/mouse will be a link to the mouse device. # However, esp. with the Spacetec Spaceball you may # want to specify a different device for svgalib to use # mdev /dev/ttyS0 # mouse is at /dev/ttyS0 # Some multiprotocol mice will need one of the following: # setRTS # set the RTS wire. # clearRTS # clear the RTS wire. # leaveRTS # leave the RTS wire alone (default) (Wire is usually set) # setDTR # set the DTR wire. # clearDTR # clear the DTR wire. # leaveDTR # leave the DTR wire alone (default) (Wire is usually set) # Monitor type: # Only one range can be specified for the moment. Format: # HorizSync min_kHz max_kHz # VertRefresh min_Hz max_Hz # Typical Horizontal sync ranges # (Consult your monitor manual for Vertical sync ranges) # # 31.5 - 31.5 kHz (Standard VGA monitor, 640x480 @ 60 Hz) # 31.5 - 35.1 kHz (Old SVGA monitor, 800x600 @ 56 Hz) # 31.5 - 35.5 kHz (Low-end SVGA, 8514, 1024x768 @ 43 Hz interlaced) # 31.5 - 37.9 kHz (SVGA monitor, 800x600 @ 60 Hz, 640x480 @ 72 Hz) # 31.5 - 48.3 kHz (SVGA non-interlaced, 800x600 @ 72 Hz, 1024x768 @ 60 Hz) # 31.5 - 56.0 kHz (high frequency, 1024x768 @ 70 Hz) # 31.5 - ???? kHz (1024x768 @ 72 Hz) # 31.5 - 64.3 kHz (1280x1024 @ 60 Hz) HorizSync 27.0 92.0 VertRefresh 50 160 # Montitor timings # # These are prefered over the default timings (if monitor and chipset # can handle them). Not all drivers use them at the moment, and Mach32 # has its own syntax (see below). # The format is identical to the one used by XFree86, but the label # following the modeline keyword is ignored by vgalib. # # Here some examples: # modeline "[EMAIL PROTECTED]" 43 640 664 780 848 480 483 490 504 # modeline "[EMAIL PROTECTED]" 50 800 856 976 1024 600 637 643 666 # modeline "[EMAIL PROTECTED]" 85 1024 1048 1376 1400 768 771 780 806 #modeline "1152x864" 137.65 1152 1184 1312 1536 864 866 885 902 -hsync -vsync #modeline "1024x768" 115.50 1024 1056 1248 1440 768 771 781 802 -hsync -vsync #modeline "800x600" 69.65 800 864 928 1088 600 604 610 640 -hsync -vsync #modeline "640x480" 45.80 640 672 768 864 480 488 494 530 -hsync -vsync #modeline "320x240" 15.75 320 336 384 400 240 244 246 262 doublescan # Mach32 timings: # e.g. Setup a 320x200 mode for the mach32: #define 320x200x32K 320x200x64K 320x200x16M 320x200x16M32 # 16 320 392 464 552 200 245 265 310 # These are REQUIRED for above mode, please edit to suit your monitor. # (No, I won't pay for a new one) # HorizSync 29 65 # VertRefresh 42 93.5 # Chipset type: # # Use one of the following force chipset type. # Autodetects if no chipset is specified. # If a chipset driver gives trouble, try forcing VGA. # chipset VGA # Standard VGA # chipset EGA # EGA # chipset ET3000 # Tseng ET3000 # chipset ET4000 # Tseng ET4000 # chipset Cirrus # Cirrus Logic GD542x # chipset TVGA # Trident TVGA8900/9000 # chipset Oak # Oak Technologies 037/067/077 # chipset S3 # S3 chipsets # chipset GVGA6400 # Genoa 6400 # chipset ARK # ARK Logic # chipset ATI # old ATI VGA # chipset Mach32 # ATI Mach32 # chipset ALI # ALI2301 # chipset Mach64 # ATI Mach64 # EGA Color/mono mode: # Required if chipset is EGA. # # Use one of the following digits to force color/mono: # monotext # Card is in monochrome emulation mode # colortext # Card is in color emulation mode colortext # RAMDAC support: # Some chipsets (e.g. S3 and ARK) allows specifying a RAMDAC type. # If your RAMDAC is not autodetected, you can try specifying it. # Do NOT specify a RAMDAC if you card uses the S3 Trio chipset # (the RAMDAC is built in). # Ramdac Sierra32K # Ramdac SC15025 # Ramdac SDAC # S3 SDAC # Ramdac GenDAC # S3 GenDAC # Ramdac ATT20C490 # AT&T 20C490, 491, 492 (and compatibles) # Ramdac ATT20C498 # AT&T 20C498 # Ramdac IBMRGB52x # IBM RGB524, 526, 528 (and compatibles) # Dotclocks: # Some chipsets needs a list of dot clocks for optimum operation. Some # includes or supports a programmable clock chip. You'll need to specify # them here. # Fixed clocks example: # (The following is just an example, get the values for your card from # you XF86Config) # Clocks 25.175 28.3 40 70 50 75 36 44.9 0 118 77 31.5 110 65 72 93.5 # Programmable clockchip example: # Clockchip ICD2061A # The only one supported right now
