Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Wildcat II gfx board is not supported under Linux (except if I want to pay a license to XIG ~$230) but I still want to be able to boot linux on this sytem
and have a decent screen.
The only driver supported is VESA (as I said I'm fine with that); The system is booting and gfx working but X resolution is always 640x480 (depth 24) or 800x600 (depth 16) what ever is the config file I have for XF86. In addition the default X screen is always larger than the monitor
I have tested all depth and all modes , but not able to figure out how to solve this problem. Does someone has a GREAT idea ?
# RgbPath is 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.
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "unix/:7100"
EndSection
# Specify 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 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"
# Or if you just want both to be control, use:
# Option "XkbOptions" "ctrl:nocaps"
#
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "fr"
EndSection
# If the normal CorePointer mouse is not a USB mouse then
# this input device can be used in AlwaysCore mode to let you
# also use USB mice at the same time.
Identifier "DevInputMice"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection
So for depth 24 the maximum is 800x600. If I switch for depth 8 I have a window of 1024x768 max, but in both case the visual is not all in the monitor. I have to play with CTRL+ALT + + (numeric pad) to scroll the desktop window.
The result is just like if I have a 640x480 monitor looking at a larger window.
Hmm, that is strange. I have a couple of guesses: first, is the "Monitor" section correct? If the HorizSync and VertRefresh are incorrect, it's possible that X is unable to figure out how to get the higher resolutions out of your monitor. If you know those are correct (i.e., have verified them against your monitor's specifications), then you can probably rule that out.
Another thing is that maybe the generic "vesa" driver is not good enough for your video card. Obviously it'd be ridiculous to pay a $230 fee for a mere driver, but perhaps there's another generic video driver that would support your card better than the generic vesa driver. If you've already researched this, though, that may not be an option.
One thing you can check to narrow down the problem is the XFree86 log files. Look in /var/log/XFree86.0.log for messages to the effect of "no usable screens found" or the like. Lines containing errors, for example if it tried to use 1280x1024 and failed, will begin with (EE), so if there are error messages like that in the log, it may tell you what went wrong.
Beyond that, I'm afraid I don't have much to offer... hopefully someone else can lend some advice!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.