SDB:Problematic Chipsets

Şuraya atla: kullan, ara


Version: 8.2 - 9.0 - 10.0

Symptom:

You cannot configure your graphics card with sax or sax2.

Cause:

Problems with the drivers or your graphics card is not supported by the current XFree86 packages.

Solution:

A list of all problematic chipsets currently known to the installation support desk follows. Each device has a vendor ID (manufacturer) and subsystem ID (device ID) that identify the hardware. The command

/sbin/lspci -n | grep 0300

enables you to easily find your graphics card's data. If you have one of the graphics chipsets listed below, refer to the following articles for the configuration:

If you want to configure the framebuffer:

SDB:Setting up Unsupported Graphics Cards with the Framebuffer Device (GRUB)

General information about sax and sax2

SDB:X Server Configuration with SaX2 (8.1 or Higher)

If a solution is already available for a known problem, you will find it right below the entry.

Drivers

Nowadays, the most important graphics card manufacturers (such as ATI, Matrox, NVIDIA, and PowerVR to name a few) offer LINUX drivers. If your graphics card is not supported by XFree86 current release, we recommend you to install these drivers and use them to configure your X server. In many cases, these drivers enable many of the features of your graphics card, too.

ACPI

Kernel support for ACPI (Advanced Configuration and Power Interface) is available from SuSE Linux 8.1 on (kernel 2.4.19). Due to the wide rage of hardware available on the market, every system configuration or operation may react differently to the ACPI function. In some cases, the following error messages might be displayed during the graphics card configuration:

	lspci: cannot find any working access method
	init: no graphic card(s) found at usr/X11R6/lib/sax/init.pl

Although everything seems to suggest a SaX problem, this error message is caused by the ACPI code.

Solution: Enter the parameter pci=bios at the boot prompt.

For further information on the ACPI management and its parameters, please refer to SDB:Kernel Parameters for ACPI/APIC

Important note:

The solutions presented in this article are based on our knowledge and on the feedback sent by our customers. In some cases, even the described methods cannot exclude any damages in your hardware. SuSE Linux AG shall not be made liable for any errors derived from the solutions described in this article. You perform the following steps at your own risk!





SuSE Linux 10.0

Vendor Chipset
type
Vendor ID Device ID XFree/driver
version
Problem Solution
INTEL i830 Xorg 6.8.2 Screen blurs when switching between console and X server and resuming after hibernation. BUG 154698 Edit /etc/X11/xorg.conf. Downgrade default 24 colour depth ie:

Section "Screen"
DefaultDepth 16


SuSE Linux 9.1

Vendor Chipset
type
Vendor ID Device ID XFree/driver
version
Problem Solution
INTEL i830/i845/i865 0x1002 0x5964 Xfree86 4.3.0 Possible Problem #1: Errorous memory handling within i810 driver

Possible Problem #2: Due to a BIOS problem, only 832kb memory is allocated to the graphics chip.
To ensure that the i810 driver is not the problem, please update your SUSE LINUX 9.1. YOU will at least install the packages

XFree86-4.3.99.902-43.25
XFree86-server-4.3.99.902-43.25

which should fix the first issue. If issue with 832kb memory still persists please contact your hardware vendor for an BIOS update.

SuSE Linux 9.0

Vendor Chipset
type
Vendor ID Device ID XFree/driver
version
Problem Solution
ATI Radeon 9200 SE 0x1002 0x5964 Xfree86 4.3.0 The driver cannot detect the ID.

Use the IDs of a Radeon 9200. The procedure is similar to the configuration of a Radeon 9200 described under the 8.2 section.

echo "Device->[X]->Raw->0->ChipID=0x5960" > /tmp/radeon sax2 -m 0=radeon -b /tmp/radeon

INTEL i830/i845/i865 Xfree86 4.3.0 Due to a BIOS problem, only 832kb memory is allocated to the graphics chip. Contact the manufacturer of your mainboard or laptop regarding a BIOS update.

SuSE Linux 8.2

Vendor Chipset
type
Vendor ID Device ID XFree/driver
version
Problem Solution
ATI Mobility U1 0x1002 0x4336 4.3.0 No XFree86 support available

Refer to the following articles for the framebuffer configuration:

SDB:Setting up Unsupported Graphics Cards with the Framebuffer Device (GRUB)

ATI Radeon R300 NF [Radeon 9700] 0x1002 0x4e46 primary 0x4e66 secondary 4.3.0 Configuration problems due to unsupported dual-head function.

During the configuration, enter the chipset you want to configure and to which the monitor is attached (this is usually chip 0). You can use sax2 -p to find out what chipsets have been detected. Then start SaX2 specifying the chip:

sax2 -c 0

or

sax2 -c 1

Matrox Parhelia 0x102B 0x0527 4.3.0 No XFree86 support available

Install the driver provided by Matrox for this card.

NVIDIA GeForce chipsets 0x10de - 4.3.0

After having selected the installation or started the system, the screen remains black until X starts.

Enter the parameter vga=normal at the boot prompt.

PowerVR Kyro 0x104a 0x0010 4.3.0

For Kyro graphics cards, refer to the SDB article SDB:Support for Graphics Cards with Kyro Chipsets

<keyword>problematic,chipset,chipsets,ati,nvidia,matrox,configure,sis,trident,silicon_motion,sm,kyro,voodoo,3dfx,4000,4500,powervr,geforce2gts,geforce2mx,g200,g400,g400,g450,g550,cyberblade,3dprophet,630,geforceddr,radeon,7500,8500</keyword>