Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 35479 Details for
Bug 50631
svgalib 1.9.17 don't work on nvidia GeForce MX 200, while svgalib 1.4.3 without r128 patch do
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
My configure file.
libvga.config (text/plain), 19.20 KB, created by
Honza
on 2004-07-15 07:06:14 UTC
(
hide
)
Description:
My configure file.
Filename:
MIME Type:
Creator:
Honza
Created:
2004-07-15 07:06:14 UTC
Size:
19.20 KB
patch
obsolete
># Configuration file for svgalib. Default location is /etc/vga. ># Other config file locations: ~/.svgalibrc ># where SVGALIB_CONFIG_FILE points ># Lines starting with '#' are ignored. > > ># This needs to be before "chipset" line, since chipset option opens ># the device. /dev/svga is the default. > >Helper /dev/svga > ># If you have two vga cards with the same pci vendor id, svgalib will try ># to use the first one, even if the second one is active. In that case, ># use PCIStart to force starting the search for a vga card only at a ># specific bus and device numbers. For example, an AGP card is usually on ># bus 1, while pci is on bus 0, so to use the AGP card, uncomment: > ># PCIStart 1 0 > ># 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 IntelliMouse # Microsoft IntelliMouse or Logitech MouseMan+ on serial port ># mouse IMPS2 # Microsoft IntelliMouse or Logitech MouseMan+ on PS/2 port ># mouse pnp # plug'n'pray ># mouse WacomGraphire # Wacom Graphire tablet/mouse ># mouse DRMOUSE4DS # Digital Research double-wheeled mouse ># mouse ExplorerPS2 # Microsoft Intellimouse Explorer PS/2 ># mouse none # None > >mouse Microsoft > ># Mouse/keyboard customisation by 101 (Attila Lendvai). If you have any good ># ideas you can reach me at 101@kempelen.inf.bme.hu > ># mouse_accel_type normal # No acceleration while delta is less then > # threshold but delta is multiplied by > # mouse_accel_mult if more. Originally done by > # Mike Chapman mike@paranoia.com > ># mouse_accel_type power # The acceleration factor is a power function > # of delta until it reaches m_accel_mult. It > # starts from the coordinate > # [1, 1 + m_accel_offset] and goes to > # [m_accel_thresh, m_accel_mult]. If delta > # is bigger then m_accel_thresh it is a plain > # constant (m_accel_mult). It is the f(delta) > # function with which the delta itself will be > # multiplied. m_accel_offset is 1 by default, > # so for delta = 1 the accelerated delta will > # remain 1 (You don't lose resolution). The > # starting point of the f(delta) function > # might be moved along the Y axis up/down with > # m_accel_offset thus defining the initial > # minimum acceleration (for delta = 1). > # Basically it's like the normal mode but the > # acceleration factor grows as you move your > # mouse faster and faster, not just turns in > # and out. Threshold is the point from where > # the f(delta) function gets linear. > # This is the one I use for *uaking... =) > >mouse_accel_type off # No comment... > > >mouse_accel_mult 60 # This is the number with which delta will > # be multiplied. Basically it's the number > # that defines how big the acceleration will > # be > >mouse_accel_thresh 4 # This is the threshold. See description by > # power > >mouse_accel_power 0.8 # This is the second parameter of the power > # function used in power mode. Used only by > # the power mode > >mouse_accel_offset 30 # This is the offset of the starting point > # on the Y axis. With this you can define the > # number that will multiply delta = 1 so it's > # the initial acceleration. > ># mouse_accel_maxdelta 600 # This is an upper limit for delta after > # the acceleration was applied > ># mouse_maxdelta 30 # This is an upper limit for the delta > # before the acceleration. With this one you > # can limit the biggest valid delta that > # comes from the mouse. > ># mouse_force # Force parameters even if they seem strange > # By default svgalib prints an error if any > # of the numbers are somhow out of the > # reasonable limit, (Like a negative mult :) > # and uses the default that's in vgamouse.h > ># 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) > ># On mice such as the Microsoft IntelliMouse and Logitech MouseMan+, turning ># the wheel rotates the mouse around the X axis. mouse_wheel_steps controls ># how many steps make up a full 360-degree turn and thus how much rotation ># occurs with each step. The default is 18 steps (20 degrees per step), the ># real-world value for the IntelliMouse. Adjust it to match your mouse or to ># suit your preferences; a negative number reverses the direction and zero ># disables rotation. > >mouse_wheel_steps 18 # For MS IntelliMouse (default) ># mouse_wheel_steps 24 # For Logitech FirstMouse+ ># mouse_wheel_steps -18 # Reverses direction ># mouse_wheel_steps 0 # Disables rotation > ># mouse_fake_kbd_event sends a fake keyboard event to the program when the ># wheel on a Microsoft IntelliMouse, Logitech MouseMan+, or similar wheel ># mouse is turned. This can be useful for programs that do not recognize the ># Z axis, but only works with some programs that use raw keyboard. ># The format is: ># ># mouse_fake_kbd_event upscancode downscancode ># ># The up and down scancodes are the scancodes of the keys to simulate when ># the wheel is turned up and down, respectively. ># ># Scancodes can be specified numerically or symbolically; the symbolic names ># are determined by the keymap (see below), if no keymap is loaded the default ># is the standard US QWERTY keyboard with the following names available: ># letters (a-z), numbers (zero-nine), function keys (F1-F12), the keypad ># numbers (KP_0-KP_9) and other keys (KP_Multiply, KP_Subtract, KP_Add, ># KP_Period, KP_Enter, and KP_Divide), and the following - minus, equal, ># Delete, Tab, bracketleft, bracketright, Return, Control, semicolon, ># apostrophe, grave, Shift, backslash, comma, period, slash, Shift, Alt, space, ># Caps_Lock, Num_Lock, Scroll_Lock, Last_Console, less, Control_backslash, ># AltGr, Break, Find, Up, Prior, Left, Right, Select, Down, Next, Insert, ># and Remove. ># ># Note that this option has no effect unless the IntelliMouse or IMPS2 mouse ># type is used (see above). Also note that the simulated keypresses are ># instantaneous, so they cannot be used for functions that require a key to ># be held down for a certain length of time. > ># This example simulates a press of the left bracket ([) when the wheel is ># turned up and a press of the right bracket (]) when the wheel is turned ># down (good for selecting items in Quake II): ># mouse_fake_kbd_event bracketleft bracketright > ># Keyboard config: > ># kbd_keymap allows you to use an alternate keyboard layout with programs that ># use raw keyboard support by translating scancodes from the desired layout to ># their equivalents in the layout expected by the program. This option has no ># affect on programs that do not use raw keyboard. ># ># Keymap files to convert between any two arbitrary keyboard layouts can be ># generated with the svgakeymap utility, but there are limitations to the ># translations that can be performed. Read the file README.keymap in the ># svgalib documentation directory for more in-depth information. ># ># You must specify the full path to the keymap file; it is recommended that ># keymaps be kept in the same directory as libvga.config, normally /etc/vga. ># The keymap specified in the configuration file can be overriden by setting ># the environment variable SVGALIB_KEYMAP to point to another keymap file; ># this can be useful for setting keymaps on a per-program basis. ># ># This example will use the provided US-Dvorak to US-QWERTY map to allow a ># Dvorak keyboard layout to be used with a program that expects a standard US ># QWERTY keyboard, for instance Quake: ># kbd_keymap /etc/vga/dvorak-us.keymap > ># There is a potential security risk in allowing users to remap keyboard ># scancodes at will; with this option enabled only keymap files owned by ># root can be used. Normally you should leave this on, but if you have a ># single-user box or you really trust your users you may find it convenient ># to run without it and allow users to load arbitrary keymaps. > >kbd_only_root_keymaps > ># kbd_fake_mouse_event, as it says, sends a fake mouse event to the program. ># The format is: kbd_fake_mouse_event scancode [flag(s)] command [argument] ># Scancode is a raw scancode or a descriptive name, the same as with fake ># keyboard events (see above). If you use keymap conversion, specify ># scancodes for the keyboard layout the program will receive. ># Flags: down - trigger event when the key is pressed (default) ># up - the opposite ># both - trigger in both case, if pressed/released ># repeat - repeat events if the key is kept pressed (off by default) ># commands: delta[xyz] - send a fake delta event as if you have moved your ># mouse. If the parameter is 'off' / 'on' it will turn ># off/on the respective mouse axis (requires a ># parameter, of course) ># button[123] - send a fake event that the mouse button is pressed ># or released that's given by the parameter. ># ('pressed' or 'released') ># Here are some examples: > ># This is one I use in *uake: it turns around, looks down a bit and when the ># key is released it does the opposite, so it gets back to the starting state. ># With this one and the help of a rocket you can fly though the whole map :) ># (Scancode 28 is enter) ># kbd_fake_mouse_event 28 both deltax 8182 down deltay -1500 up deltay 1500 > ># This one will switch off the y axis of the mouse while the key (right ctrl) ># is kept pressed. ># kbd_fake_mouse_event 97 down deltay off up deltay on > ># This one is the same as if you were pressing the left mouse button. (But ># if you move your mouse then the button state will reset even if you keep ># right ctrl down...) ># kbd_fake_mouse_event 97 down button1 pressed up button1 released > ># 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 31.5 35.5 ># VertRefresh 50 90 >HorizSync 30 95 >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 svgalib. ># ># Here some examples: > ># modeline "640x480@100" 43 640 664 780 848 480 483 490 504 ># modeline "800x600@73" 50 800 856 976 1024 600 637 643 666 ># modeline "1024x768@75" 85 1024 1048 1376 1400 768 771 780 806 > ># It seems there is a need for a 512x384 mode, this timing was donated ># by Simon Hosie <gumboot@clear.net.nz>: (it is 39kHz horz by 79Hz vert) > ># Modeline "512x384@79" 25.175 512 522 598 646 384 428 436 494 > ># Here's a 400x300 Modeline (created by svidtune). Note that for ># doublescan modes, the Vertical values are half the real one (so XFree86 ># modelines can be used). > ># Modeline "400x300@72" 25.000 400 440 504 520 300 319 322 333 doublescan > ># Here is a mode for a ZX Spectrum emulator: ># Modeline "256x192@73" 12.588 256 269 312 360 192 208 212 240 doublescan ># newmode 256 192 256 256 1 > ># the width must be divisible by 8. Some cards require even divisiblity by ># 16, so that's preferable, since there are no standard modes where the ># width is not divisible by 16. > ># The following modes are defined in svgalib, but have no timings in ># timing.c, so you'll have to add a modeline in order to use them: ># 1280x720, 1360x768, 1800x1012, 1920x1080, 1920x1440, 2048x1152 ># and 2048x1536 > ># 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 > >Modeline "1024x768" 65.00 1024 1080 1224 1344 768 771 777 806 -hsync -vsy Modeline "800x600" 50.00 800 844 964 1040 600 625 631 666 +hsync +vsync ># Modeline "640x480" 36.00 640 696 752 832 480 481 484 509 -hsync -vsync >Modeline "640x480" 36.00 640 696 752 796 480 481 484 509 -hsync -vsync ># Modeline "640x400" 31.50 640 672 736 832 400 401 404 445 -hsync +vsync >Modeline "512x384" 22.00 512 528 592 640 384 385 388 404 -hsync -vsync ># Protoze stale casteji pouzivam mplayer -svga, rusim mody co nejsou 4:3 ># Modeline "480x300" 29.95 480 504 584 624 300 319 322 333 Doublescan >Modeline "400x300" 25.00 400 424 488 520 300 319 322 333 Doublescan ># Modeline "320x240" 15.75 320 336 384 400 240 244 246 262 Doublescan >Modeline "320x240" 15.75 320 336 384 416 240 244 246 262 Doublescan ># Modeline "320x200" 12.59 320 336 384 400 200 204 205 225 Doublescan ># 1280x960 @ 60Hz (VESA) hsync: 60.0kHz >Modeline "V1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync ># 1280x960 @ 85Hz (VESA) hsync: 85.9kHz >Modeline "V1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync ># 1280x1024 @ 60Hz (VESA) hsync: 64.0kHz >Modeline "V1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync ># 1280x1024 @ 75Hz (VESA) hsync: 80.0kHz >Modeline "V1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync ># 1280x1024 @ 85Hz (VESA) hsync: 91.1kHz >Modeline "V1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync ># 640x480 @ 100 Hz, 52.01 kHz hsync >Modeline "640x480" 45.8 640 672 768 864 480 488 494 530 -HSync -VSync ># 800x600 @ 85 Hz, 55.84 kHz hsync >Modeline "800x600" 60.75 800 864 928 1088 600 616 621 657 -HSync -VSync ># 800x600 @ 100 Hz, 64.02 kHz hsync >Modeline "800x600" 69.65 800 864 928 1088 600 604 610 640 -HSync -VSync ># 1024x768 @ 76 Hz, 62.5 kHz hsync >Modeline "1024x768" 85 1024 1032 1152 1360 768 784 787 823 ># 1024x768 @ 85 Hz, 70.24 kHz hsync >Modeline "1024x768" 98.9 1024 1056 1216 1408 768 782 788 822 -HSync -VSync ># 1024x768 @ 100Hz, 80.21 kHz hsync >Modeline "U1024x768" 115.5 1024 1056 1248 1440 768 771 781 802 -HSync -VSync >Modeline "1024x768" 115.5 1024 1056 1248 1440 768 769 779 802 -HSync -VSync > > # 1024x768x100Hz, 81 kHz hsync >Modeline "S1024x768" 110.16 1024 1056 1168 1360 768 772 776 810 > # 512x384 @ 100Hz, 40.50 kHz hsync >Modeline "S512x384" 23.98 512 552 576 592 384 386 388 405 > # 800x600 @ 100Hz, 63.30 kHz hsync >Modeline "S800x600" 62.79 800 816 880 992 600 603 606 633 > # 400x300 @ 100Hz, 2*31.80 kHz hsync >Modeline "400x300" 29 400 436 452 456 300 302 304 318 DoubleScan > # 320x240 @ 100Hz, 2*25.50 kHz hsync >Modeline "320x240" 18.36 320 328 344 360 240 242 244 255 DoubleScan > ># Chipset type: ># ># Use one of the following force chipset type. ># Autodetects if no chipset is specified. ># ># If you have a PCI or AGP card, don't use chipset type forcing. ># If the card is not autodetected, its a bug, and it will probably ># not work even with forcing. Try running vgatest (with no chipset ># line), and send to me (matan@svgalib.org) the output, a copy of ># /proc/pci (or lspci -n -vv) and whatever info you have on the card. ># ># 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/543x/544x ># 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 - deprecated, use RAGE driver ># chipset ET6000 # Tseng ET6000 ># chipset APM # Alliance Technology AT 24/25/3D >chipset NV3 # nVidia Riva 128 ># chipset VESA # nicely behaved Vesa Bioses ># chipset MX # MX86251 (some Voodoo Rush boards) ># chipset PARADISE # WD90C31 ># chipset RAGE # RagePro (and might work with some older mach64) ># chipset BANSHEE # Banshee/V3. ># chipset SIS # SiS 5597/6326/620/530 cards / integrated vga. ># chipset I740 # Intel i740 based cards. ># chipset NEOMAGIC ># chipset LAGUNA # Cirrus Logic Laguna series (546X) ># chipset FBDEV # Use kernel fbdev, instead of direct hardware. ># chipset G400 # Matrox Mystique/G100/G200/G400/G450 ># chipset R128 # Ati Rage128 and Radeon ># chipset SAVAGE # S3 chipsets Savage, Virge, and some Trio64 ># chipset MILLENNIUM # Matrox Millennium and Millennium II ># chipset I810 # Intel i810/815 integrated video - not yet working. ># chipset TRIDENT # Trident PCI and AGP chipsets ># chipset RENDITION # Rendition V2100/V2200 ># chipset G450C2 > ># 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 > > ># VesaText # Helps the VESA driver with text mode restoration > # problems. > ># VesaSave 14 # changing value might help text mode restoring > # problems with VESA driver. Legal values: 0-15 > ># NoVCControl # Disables svgalib's finding a new VC if run > # from X. Good fo using dumpreg under X, but > # probably bad for standard usage. > ># RageDoubleClock # If your card is based on ATI's rage card, and > # the pixel clock is double what it should be > # (main symptom is some modes are out of sync), > # try enabling this. If it helps, please report to > # me (matan@svgalib.org) > >linear
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 50631
: 35479