SuSE Linux: Versions since 7.0
XFree86: Version 4.x.x
Following the installation, the graphical user interface is not displayed properly or not at all. Therefore, you want to reconfigure the components (mouse, keyboard, graphics card, and monitor) and try out different settings.
This article draws attention to problems that may result in connection with the configuration of the X11 system and how you can eliminate these problems.
If the X server is active, press the key combination:
CTRL+ALT+F1
to switch to the text console. If the text console is black, please take a look at the following SDB article:
http://sdb.suse.de/de/sdb/html/blackconsole.html
Subsequently, log in as root and execute the command:
init 3 (init 2 for SuSE Linux 7.0)
in order to change to runlevel 3. When runlevel 3 is reached, you receive the following message:
MASTER RESSOURCE: CONTROL LEVEL 3 HAS BEEN REACHED
Confirm this message by pressing any key, after which you will see the input prompt.
When starting the system with SuSE 7.1 or higher, you will see the LILO boot screen. Press the ESC key in order to terminate this screen. Then you will see:
boot:
Now enter the following:
linux 3
As users of version 7.0 do not have this LILO boot screen, they should start with the command:
linux 2
at the boot prompt. Users of version 7.2 or higher should just select
the requested entry from the lilo menu, and add 3 to it (the entry
linux
is already available).
Subsequently the system will be started in runlevel 3 and you can log in as root.
Once you reach runlevel 3, you can start with the configuration. All
newer graphics cards (Radeon, Rage Fury Maxx, GeForce 2 GTS/MX, Matrox
G450, etc.) should only be configured with SaX2, while some older
graphics cards (such as ATI Rage128er Serie, Mach64, S3-Karten, Matrox
G100-G400, Nvidia Riva128 as well as TNT and TNT2, etc.) are still
supported by XFree 3.3.6. Therefore, problems with the XFree 86 4.x.x
driver in connection with older cards can be avoided by means of SaX
.
You can easily determine the chipset of your graphics cards by entering the following command:
/sbin/lspci
When you receive the output of this command, look for the line that begins with "VGA-compatible controller":
01:00.0 VGA compatible controller: nVidia Corporation NV11 (rev a1)
In this example, the card has a Nvidia chipset. If you want even more information, you may also use the command:
sax2 -p This command produces the following output: Chip: 0 is -> Nvidia GeForce 2 MX 1:0:0 0x10de 0x0110 AGP nv
In this way we obtain detailed information on the graphics card. Here an explanation of the output details:
Chip: 0 = First encountered graphics chipset Nvidia GeForce 2 MX = Graphics card model. Under certain circumstances, unknown may be displayed here. If fbdev is placed in the last position, your card has been classified as not supported and the system tries to setup the frame buffer. 1:0:0 = Describes in which slot the card is inserted. This is only relevant if you plan a configuration with several graphics cards. Please note that the installation support does not cover such issues. 0x10de 0x0110 = Manufacturer and card number AGP = This is an AGP card nv = The driver module SaX starts with if no other parameters are assigned
Now that you have identified your graphics card, you can start the program SaX2 with various parameters.
The configuration file XF86Config for XFree 4.x.x is stored in /etc/X11/.
To start the configuration of the graphical user interface with SaX2, execute the command
sax2
Users of SuSE Linux version 7.0 may encounter the question whether they want to change from XFree 3.3.6 to Xfree 4.0. Confirm with "yes". Then SaX2 is started.
With some graphics cards it may happen that no suitable module can be found for the built-in graphics card. In this case SaX will be started and you can proceed with the configuration as described above. Starting from version 7.1, almost every graphics card should be configurable with XFree 4.0.2. Of course, this does not apply to exceptional cases and special graphics cards.
SaX2 offers a number of possibilites to circumvent possible problems with various parameters. The most important options are as follows:
sax2 -p = Interprets the Bus and lists all cards recognized as graphics cards. sax2 -f = Makes sure that the hardware is checked even if hardware data is already available. This -f option has been already implemented in the sax2 command in SuSE Linux 7.2 or higher. If you want to disable the hardware detection, please use the -q option. sax2 -q = Disables the hardware detection. sax2 -l = Starts Sax2 with 640*480@60Hz. DDC-probing is disabled. This option is very helpful in case your monitor shutdowns as Sax2 starts or your screen is black. sax2 -m 0= = This option chain informs SaX2 which module to use at start-up for addressing the graphics card. e.g. sax2 -m 0=r128 loads the module for ATI Rage-128 cards. All modules available for XFree 4.x.x are listed under: /usr/X11R6/lib/modules/drivers/ apm_drv.o fbdev_drv.o neomagic_drv.o sis_drv.o ark_drv.o glide_drv.o nv_drv.o tdfx_drv.o ati_drv.o glint_drv.o nvidia_drv.o tga_drv.o atimisc_drv.o i128_drv.o r128_drv.o trident_drv.o chips_drv.o i740_drv.o radeon_drv.o tseng_drv.o cirrus_alpine.o i810_drv.o vesa_drv.o rendition_drv.o cirrus_drv.o s3virge_drv.o vga_drv.o cirrus_laguna.o mga_drv.o savage_drv.o cyrix_drv.o mga_hal_drv.o siliconmotion_drv.o sax2 -c CHIP = Example: You have a Voodoo add-on card and an AGP card. SaX2 -p detects the Voodoo card as chip 0 and the AGP card as chip 1. However, SaX2 terminates the configuration, as it probably tries to configure the PCI CARD. However, if you start SaX2 with sax2 -c 1, the "second" graphics chip is addressed and you can continue with the configuration. sax2 -n = As described under SaX, SaX2, too, offers the possibility of loading the mouse options at start-up, if the mouse does not work or executes wrong functions. This command also requires the parameter -t. -n defines the mouse device sax2 -t = Determines the protocol for the mouse. Therefore, the syntax is as follows: E.g.: sax2 -n /dev/usbmouse -t ps/2 for a USB mouse. sax2 -F = This option is available from version 4.3 on. It enables to start single Sax2 modules. In case you want to modify the mouse settings, you can start Sax2 with sax2 -F mouse A list with the different options follows: [ -F | --fastpath ] set the fastpath to configure sigle parts of the configuration. Available are: a) mouse b) keyboard c) desktop d) layout sax2 -a = The option -a / --auto generates an automatic configuration under consideration of all hardware data automatically detected by SaX2. Following the launch of "sax2 -a", you can start the graphical user interface immediately and adjust the image with xfine2 or restart SaX2 in order to modify the existing configuration. Of course you can also combine the respective options, e.g.: sax2 -m 0=r128 -n /dev/psaux -t imps/2 -a
If you want to calculate and enter your modelines yourself instead of using the ones employed in XF86Config, you can use the command xmode. But please keep in mind that you can only use resolution/refresh rates admitted by your hardware (graphics card/monitor). Using the wrong values could damage your hardware!
For example, if you wish to generate a resolution of 1024*768@60Hz, the command for xmode would be as follows:
xmode -x 1024 -y 768 -r 60
The output:
44 55 Modeline "1024x768" 61.19 1024 1040 1216 1400 768 768 775 802 xmode Optionen: [ -d | --dacspeed ] ramdac speed in Mhz [ -r | --refresh ] refresh rate in Hz [ -s | --sync ] horizontal sync rate in Khz [ -x | --xdim ] X - dimension in pixels [ -y | --ydim ] Y - dimension in pixels [ -n | --nocheck ] do not check the geometry [ -f | --fbdev calculate framebuffer mode
However, you should only attempt to enter the modelines manually if nothing else works or if you need a particular modeline.
Please insert this modeline in the section "Modes" of XF86Config and disable the rest of modelines as in the example below:
The modeline above must be added to section "Modes"
Already available modelines:
Section "Modes" Identifier "Modes[0]" Modeline "640x480" 27.96 640 656 720 864 480 480 485 501 Modeline "800x600" 43.68 800 816 928 1072 600 600 606 626 Modeline "1024x768" 79.55 1024 1040 1216 1328 768 768 777 802 EndSection
After the modification:
Section "Modes" Identifier "Modes[0]" # Modeline "640x480" 27.96 640 656 720 864 480 480 485 501 # Modeline "800x600" 43.68 800 816 928 1072 600 600 606 626 # Modeline "1024x768" 79.55 1024 1040 1216 1328 768 768 777 802 Modeline "1024x768" 61.19 1024 1040 1216 1400 768 768 775 802 EndSection
Lately, SaX2 has been modified several times (since SuSE Linux 7.0) for the purpose of simplifying the configuration. Since this article attempts to be an up-to-date explanation of the different possibilities with Sax2, this article focuses on the current Sax2 version.
If you start SaX2 with
sax2
you receive the following output:
SaX: root Password: SaX: using hardware information from database SaX: to avoid this run SaX the following: sax2 -f SaX: abort sequence is [ Ctrl-C ]... SaX: continue [ yes | no ]
If the hardware is to be read, use the option -f. If, on the other hand, you only want to modify your existing configuration, you can confirm this message with "yes".
If you start SaX2 with the option -f, the hardware is read and you receive a message such as the following:
Card: Nvidia GeForce 2 MX Do you want to enable 3D for this card ? [ yes | no ]
SaX2 has detected a card that is able to provide 3D support. If you are not sure whether this feature is supported in Linux (!), please say "no". With Nvidia and Voodoo graphic cards, most likely you will be able to activate 3D hardware acceleration for games and other applications. However, please note that special drivers may be required for this support. Therefore, take a glance at our Support Database
http://support.suse.de/en/sdb/html/key_form.html
If you receive the following message while configuring Nvidia cards:
Some packages are missing. Do you want to install the missing packages now ?
please answer with "no". If you want to reconfigure the card, you should already have installed the drivers with YaST or the rpm commands. Be sure you only use drivers from the Nvidia home page
http://www.nvidia.com/view.asp?PAGE=linux
for Nvidia cards.
Now you have two possibilities:
Enable SaX autodetection mode
and
Use the current configuration
If you want to create a new configuration, please use "Enable SaX autodetection mode". If you only want to perform modifications, select "Use the current configuration". After selecting the correct option, continue with "Next >>".
Mouse settings: Click on "Properties" in order to load existing mouse settings. If you have a PS2 or USB mouse, the values should be entered automatically. However, certain mouse characteristics (e.g. wheel support) are not loaded automatically through the product names, since some mice do not work with the imps/2 protocol. You can do this manually under "Expert" by setting the following values:
Protocol = imps/2 Device = /dev/pointer0 -> is a link to /dev/psaux or /dev/usbmouseThen scroll down to the entry "wheel mouse". Change the entries as follows:
Buttons = please click Negative Movement = 4 Positive Movement = 5Confirm with OK, then click on "Next>>".
Another possibility is manually entering the values in an already available XF86Config. In order to do this, open XF86Config as root and search for the following entries:
Section "InputDevice" Driver "mouse" Identifier "Mouse[1]" Option "Device" "/dev/mouse" Option "Emulate3Buttons" "on" Option "Emulate3Timeout" "50" Option "InputFashion" "Mouse" Option "Name" "Autodetection" Option "Protocol" "ps/2" Option "Vendor" "Sysp" EndSection
Now change the "ps/2" protocol to "imps/2" and append the following line:
Option "ZAxisMapping" "4 5"
The modified section "Input Device" shall look like this:
Section "InputDevice" Driver "mouse" Identifier "Mouse[1]" Option "Device" "/dev/mouse" Option "Emulate3Buttons" "on" Option "Emulate3Timeout" "50" Option "InputFashion" "Mouse" Option "Name" "Autodetection" Option "Protocol" "imps/2" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection
You also may want to configure your laptop in such a way that allows you to use an external mouse (e.g. a PS/2 or USB mouse) apart from the internal touchpad. This can be done by inserting a second section "Input Device" (actually the third one) in XF86Config and entering the right device and protocol. Please note that internal touchpads do not work with the imps/2 protocol.
An example:
Section "InputDevice" Driver "mouse" Identifier "Mouse[1]" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "on" Option "Emulate3Timeout" "50" Option "InputFashion" "Mouse" Option "Name" "Autodetection" Option "Protocol" "ps/2" Option "Vendor" "Sysp" EndSection Section "InputDevice" Driver "mouse" Identifier "Mouse[1]" Option "Device" "/dev/input/mouse" Option "Emulate3Buttons" "on" Option "Emulate3Timeout" "50" Option "InputFashion" "Mouse" Option "Name" "Autodetection" Option "Protocol" "imps/2" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection
Please notice that a conflict between an external PS/2 mouse and the touchpad might occur, since both access /dev/psaux.
As mentioned above, in some cases mice may not work with certain protocols (ps/2 & imps/2). Possible symptoms: the mouse pointer is inactive in one of the screen corners or seems to cause commands to be executed on the desktop. Problems like these can be solved as follows:
Use an editor of your choice (vi, emacs, pico) to open the file /etc/init.d/boot.local and append the following at the end of the file:
/usr/sbin/sysp -s mouse > /dev/null
This initializes the mouse properly and the mouse will work with the imps/2 protocol.
An alternative solution consists of changing the mouse protocol. If the mouse presents any problems when using the imps/2 protocol, change the protocol to ps/2 in XF86Config.
In case certain features of the mouse (or the entire mouse) do not work, you should set the option START_GPM in the file /etc/rc.config to "no" and then execute SuSEconfig. Before you deactivate gpm completely, you can also execute the command gpm -k (to switch off gpm) and restart X (if you have a graphical login, press CTRL+ALT+BACKSPACE).
graphics cards are responsible for the drawing of the mouse pointer. In some cases it might occur that the mouse pointer is not represented. This problem can be solved by editing the Section "Device" in the file XF86Config. Please proceed as follows:
Search for the entry
Section "Device" BoardName "AutoDetected" Driver "r128" Identifier "Device[0]" VendorName "AutoDetected" EndSection
Insert the option "sw_cursor" as follows:
Section "Device" BoardName "AutoDetected" Driver "r128" Identifier "Device[0]" VendorName "AutoDetected" Option "sw_cursor" EndSection
In this way the drawing of the mouse pointer will be passed to the X server and the mouse will be represented as usual.
Symptom: The mouse pointer shows a jerky motion or can only be moved at a certain speed on the screen.
Solution: Every mouse has a determined resolution (dpi) that can be set in XF86Config. This entry's syntax is the following:
Option "Resolution" "value"Example:
Option "Resolution" "400"This entry must be added to the mouse settings in the section "Input Device" in /etc/X11/XF86Config. Please refer to the technical information that is (or should be) available for your mouse in order to find out its particular resolution value. This option does not work for USB mice at present.
Keyboard settings: By default, the correct layout (en) should be set. In case you perform modifications, confirm these with "Apply". Under "Velocity" you can set the reaction time of the keyboard (default delay time = 50 and repeat rate = 5). However, you do not need to modify these settings. In the test space you can test the selected keyboard layout. As with SaX, "General" offers you the possibility to select the keyboard type (standard = standard keyboard [ pc104 ]). Since Linux allows you to utilize TrueType fonts, you can include these under "Fonts". For more information, please check the manual on page 159. Please note that the installation of TTFs is not covered by the free installation support. More information on the installation of TTFs is provided in our Support Database:
http://sdb.suse.de/en/sdb/html/chofman_ttf_71.html
http://sdb.suse.de/en/sdb/html/chofman_ttf_72.html
Clic on Next >> to configure your graphics card.
Graphics Device Setup: Graphics card configuration. The window displays the detected graphics card. Since Linux evaluates the chipset on the card, the information on this model may differ from the information other operating systems provide. Under "Properties", you will find a list of manufacturers and graphics cards. If necessary, select your graphics card from the list. Under "Expert", you can perform some additional settings, the most important of which are introduced below:
Driver = Here you can set the drivers. Normally this should not be necessary, but if you use an additional driver (nvdia), this driver can be explicitly specified here. Memory = Determines the memory for the graphics card. If you have a card with more than 32 MB, you can enter this value (1024*64 = 65536) manually. Options = Here you can set various options, such as: SWcursor - In case the mouse pointer is displayed incorrectly or not at all noaccel - For problems that may occur when starting various graphics chipsets Raw Definition = In order to e.g. ensure the output of a graphics card with digital output on a suitable monitor, you can enter the following: Option "ConnectedMonitor" "DFP" This line must adhere to the syntax of XF86Config.
Desktop Setup: Color depth, resolution, monitor type, and frequencies are set here. The recommended default color depth is 16 bit, 24 or 32 bit may cause problems with certain cards. You can select your desired resolution from the "Resolutions" list. If you mark several resolutions, you can toggle between these in the running system with CTRL+ALT +/-. If your monitor is not included in the list, you may use one of the VESA drivers, which should work with any CRT monitor. Special drivers are available for LCD/TFT displays. Under "Frequencies" you can enter the horizontal and vertical frequencies of your monitor, in case your monitor is not included in the monitor list. This information can be obtained from the monitor's manual or from the Internet. Confirm the settings and click on "Finish".
The next window lets you save the settings or run an X server test. Launch the test with "Start".
Now you should see a successful test server. Minor deviations should be adjusted with the monitor. If the deviation is too large, terminate the test and change the algorithm to "Iterate precisely" under "Characteristics/Expert". Then start the test once more.
The option Framebuffer Timing enables you to select displays with 60 Hz directly.
If you are satisfied with the result, finish the configuration with "Save configuration" and terminate SaX2.
Now you can return to the graphical mode and check your settings with
init 5 (init 3 for SuSE 7.0)
In case you have a graphics card that is not supported yet or whose driver causes problems, you still have the possibility to set up the framebuffer device. If this should be necessary, please proceed as described in the following article in our Support Database:
http://sdb.suse.de/en/sdb/html/wessels_easy_fbdev.html
Another source of information for problematic graphics cards is
http://sdb.suse.de/en/sdb/html/wessels_problematic_chipsets.html
Similar to SaX, SaX2 has log files that track the configuration process: :
* /var/log/SaX.log * /var/log/XFree86.0.log
Simply copy these files to a floppy disk using
mcopy /path/filename a:
Please also enclose the output of
/sbin/lspci -vv
and the file
/etc/lilo.conf
You would like to activate 3D, expand your workplace through an additional monitor (dual/multihead), or perhaps install True Type Fonts.
All these issues exceed the the scope of the free installation support. For this purpose we have established the new Advanced Support Hotline. Depending on the category your question belongs to, please dial one of the following phone numbers. A Linux expert from this particular field will be pleased to help you.
From Germany, please dial 0190 86280x, replacing x with the respective final digit (0 for boot and installation issues, 1 for Internet-related issues, etc.) (EUR 1.86/minute, Monday to Friday 0900-1700 hours).
From Austria, please dial 0900 47011x, replacing x with the respective final digit (0 for boot and installation issues, 1 for Internet-related issues, etc.) (EUR 1.80/minute, Monday to Friday 0900-1700 hours).
From Switzerland, please dial 0900 70071x, replacing x with the respective final digit (0 for boot and installation issues, 1 for Internet-related issues, etc.) (sFR 3.13/minute, Monday to Friday 0900-1700 hours).
From Great Britain, please dial 0906 666001x, replacing x with the respective final digit (0 for boot and installation issues, 1 for Internet-related issues, etc.) (£ 1.50/minute, Monday to Friday 0900-1700 hours).
From the Netherlands, please dial 0900 202216x, replacing x with the respective final digit (0 for boot and installation issues, 1 for Internet-related issues, etc.) (EUR 0.70/minute, Monday to Friday 0900-1700 hours).
From Dutch-speaking Belgium, please dial 0903 4102x, replacing x with the respect final digit (0 for boot and installation issues, 1 for Internet-related issues, etc.) (EUR 1.11/minute, Monday to Friday 0900-1700 hours).
From French-speaking Belgium, please dial 0903 4103x, replacing x with the final digit (0 for boot and installation issues, 1 for Internet-related issues, etc.) (EUR 1.11/minute, Monday to Friday, 0900-1700 hours).
Final digit | Hotline subject |
---|---|
0 | Boot and installation issues |
1 | Internet (modem, ISDN, DSL, cable modem) |
2 | External peripherals (printer, scanner, zip drive, webcam, etc.) |
3 | Multimedia (sound, DVD, CD writer, TV card) |
4 | Graphical user interface X11 (graphics card, mouse, keyboard, 3D, TV-out) |
5 | Applications (office, commercial, window managers) |
6 | Laptop, PCMCIA |
7 | Basic administration and LAN (network services, user administration, permissions, small networks) |
9 | Non-i386 (MacIntosh and compatible PowerPCs, ALPHA, IA-64: Architecture-specific boot and installation issues) |
SDB-wessels_sax2
)