This chapter contains a brief description of the video and notebook support included in this Video Driver Update, followed by release notes, known problems, diskette image creation procedures, and installation instructions. Read the entire chapter once before installing the Video Driver Update. Note that this Video Driver Update is cumulative so this update includes all previous Solaris 2.6 Video Driver Updates.
This release contains software improvements and support for the video devices listed below.
Table 2-1 lists the video devices supported by this Video Driver Update.
While this table includes the resolution and color depth capabilities of each device, note that the resolution and color depth you select are also dependent on the capabilities of your monitor and the amount of video memory. See the Configuring Devices module in Information Library for Solaris 2.6 (Intel Platform Edition) for more information.
Table 2-1 Video Display Devices Supported in This Video Driver Update
"--" in the Bus column indicates a video controller model that is used on video display adapters and motherboards.
If your video display device is not included in the list of supported video devices, make a note of its video chip. If you can find an entry for another device with this video chip, this support may work for your video device.
Table 2-2 lists the notebooks supported with this Video Driver Update.
Table 2-2 Notebook Displays Supported in This Video Driver Update
Notebook Display Video Support |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|
Vendor |
Model |
Video Chip |
Resolution and Color Depth E=With External Monitor I=With Internal Monitor |
|||||||
640x480 |
800x600 |
1024x768 |
1280x1024 |
|||||||
8 |
24 |
8 |
24 |
8 |
24 |
8 |
24 |
|||
Toshiba |
Satellite 200CDS |
Chips & Technology 65550 |
|
|
E,I |
|
E |
|
E |
|
|
Satellite 220CDS |
Chips & Technology 65554 |
|
|
E,I |
|
E |
|
E |
|
|
Tecra 520CDT |
Chips & Technology 65555 |
|
|
E,I |
|
E |
|
E |
|
|
Tecra 530CDT |
Chips & Technology 65555 |
|
|
|
|
E,I |
|
E |
|
When running a Solaris 2.6 window system on most newer notebooks, the resolution to use for the internal notebook display will be automatically determined. However, you must still run kdmconfig to configure the notebook as well as the characteristics of a possible external display. In kdmconfig, you should select the Monitor Type, Screen Size, and Resolution/Colors entries that apply to your external display. If you do not plan to use an external display, select one of the Notebook entries as your Monitor. The window system software will automatically switch between the available resolution for your internal notebook display and the configured resolution for the external monitor.
If you have an older notebook for which the resolution of the display is not automatically determined, the resolution selected by kdmconfig will be used on both internal and external displays. On these notebooks, make sure you don't select a resolution that is higher than the internal display supports, because this may damage the display.
Support for ATI 3D RAGE II+ chips has been updated. Support for ATI 3D Pro Turbo cards with 8 Mbytes of video memory has been added.
Support for ATI Mach64VT chips has been enhanced to eliminate some screen noise.
Support for S3 ViRGE chips (86C325) has been enhanced to prevent screen corruption.
Support for Cirrus Logic 542x chips has been updated to eliminate some screen noise.
Support for notebooks using Chips and Technology 65555 chips has been updated to eliminate text distortion and vertical line problems.
Support has been added for monitor refresh rates up to 115kHz horizontal and 120Hz vertical.
Minor improvements have been made to kdmconfig.
Support for S3 Trio64V2/DX chips (86C775) has been updated to work on motherboards where it previously failed.
Support for new Siemens Nixdorf monitors has been added: MCM 1703 NTD, MCM 1704 NTD, MCM 1753 ND, MCM 1755 NTD, MCM 2103 ND, MCM 2105 NTD, MCM 2106 NTD, MCM 2107 NTD, MCM 2108 NTD, MCM 2109 NTD, MCM 2110 NTD.
This section describes the diskette images in this Video Driver Update and known problems in this release.
The Solaris 2.6 Intel Platform Edition Video Driver Update is distributed as DOS diskette images. This allows the required diskettes to be created on non Solaris systems as well as on Solaris systems. This release consists of five diskette images. Each diskette image is for a specific set of video devices or notebooks. The images in Video Driver Update 3 and their corresponding devices are:
du3vnbk |
Updated video support for notebooks |
du3vati |
Updated video support for video cards and motherboards using video chips from ATI Technologies |
du3vmat |
Updated video support for video cards and motherboards using video chips from Matrox Graphics |
du3vs3 |
Updated video support for video cards and motherboards using video chips from S3 |
du3vcir |
Updated video support for video cards and motherboards using video chips from Cirrus Logic |
You only need to install the images for the video devices you intend to use, although you may install all the images if you want. They can be installed in any order.
(4076832) On boards using the Cirrus Logic GD5480 at 1280x1024 resolution with 24-bit color depth, moving windows aound may cause the X Server to crash.
Workaround: Select a different resolution..
(4033255) Boards using S3 ViRGE/VX (86C988) chips are not able to switch from 24-bit color depth resolutions to 8-bit color depth resolutions without rebooting.
(4023063) The display at resolution 800x600 on the Intel TMI/IPG system is not correct. In a window system environment, the right edge of the screen appears to have synchronization problems.
(4023057) XSun core dumps when attempting to display raster files. Using Image Tool to display raster files on the Intel TMI/IPG system using the WD9031A-based video adapter fails.
Workaround: Use the program xv.
(1250528) Onboard mouse configuration for the Dell Latitude XPi 75D notebook computer will fail due to interrupt conflicts with the pcic driver.
Workaround: Edit /kernel/drv/pcic.conf and remove IRQ 12 from the res-irq line as shown below. Change:
res-irq=3,5,9,11,12,15
to:
res-irq=3,5,9,11,15
Run kdmconfig to reconfigure the mouse.
(1192967) Due to hardware conflicts on some VESA local bus (VLB) systems, the Diamond Viper Pro VLB card may not function when configured at the default memory address (0xA0000000). If you see a blank screen and your system appears hung after starting window system software, do the following:
Reboot your system.
Run the kdmconfig program and choose a different memory address from the Memory Address screen. The three possible choices are: 0x20000000, 0x80000000, or 0xA0000000.
Restart the window system software.
Follow these steps for each address until your system works correctly.
(1179340) Using the Intel Professional GX High Resolution system in 1280x1024 with 256 colors mode and an 80-kHz monitor causes problems when returning to text mode after exiting the window system. The foreground color is set to purple; the background color is set to blue.
Workaround: Select either a different resolution or a different monitor frequency when configuring the window system.
(1179339) The ATI Graphics Ultra Pro VLB video card with a Mach32 graphics chip, a TI68875 BFN RAMDAC, and 2 Mbytes of DRAM may not work properly if the "ATI Graphic Ultra Pro (2MB)" entry is selected when configuring the window system. Vertical bars get displayed on the screen.
Workaround: If you have this version of the card, choose the "ATI Graphic Ultra Pro (1MB)" entry when configuring the window system, but note that you will not be able to use a resolution of 1280x1024. Note also that the ATI Graphics Ultra Pro VLB video card with VRAM does not have this problem.
(1173773) After running xlock, there may be a white border around the screen on systems with video cards that use the Tseng Labs W32p chipset. This border disappears after the screen is unlocked.
(1176285) Programs that use the SolarisTM PEXTM extension may fail if a user's XGLHOME variable is set incorrectly. If the XGLHOME shell environment variable points to a nonexistent path (or one that doesn't contain the XGLTM runtime binaries), then any program that uses the Solaris PEX extension (including XGL programs on most display adapters) will cause the server to abort.
Workaround: Before you start the window system, make sure your XGLHOME environment variable is not set or that it points to a valid path for the system you are using.
(1161494) Under the Solaris operating environment, the Diamond Viper video card based on the P9000 chipset is not compatible with a motherboard that has a Symphony chipset. This combination may cause the system to panic or reboot. If the Symphony chipset is present on the motherboard, do not use the Diamond Viper video card.
The VLB versions of the Diamond Viper and Diamond Viper Pro adapters do not work on some systems that have both PCI and VESA local bus support on the motherboard. The window system will fail with an error message when you attempt to start it. The Solaris software expects a PCI version of the Diamond Viper boards if the system supports PCI.
Workaround: Use a PCI version of the Diamond Viper adapters on those systems that support both bus types.
The VLB version of the Diamond Viper SE adapter is not supported in this release.
Some versions of the Orchid Kelvin 64 VLB video card have memory addressing limitations that may cause problems if your system contains 32 Mbytes or more of RAM. A newer revision of this board addresses these problems. Unfortunately, there is no distinction made between revisions of this card. If your system has 32 Mbytes or more of RAM and you observe symptoms such as a fuzzy display or random vertical lines when using the window system, contact Orchid Technology to request a newer version of this card.
The Number Nine Imagine 128, the #9GXE64, and #9GXE64 Pro video cards do not support interlaced mode. Configuring the window system using a monitor type of "MultiFrequency-38kHz (up to 1024x768 interlaced)" or "MultiFrequency-56kHz (up to 1280x1024 interlaced)" will cause the window system to fail.
Workaround: Use a monitor that can support 1024x768 or 1280x1024 in non-interlaced mode.
The following problems apply only to 24-bit depth color:
(1174561) The STB LIGHTSPEED VL video card used in 800x600 resolution, 24-bit color mode, does not work properly with the Sony CPD 1604S monitor.
Workaround: Do not use this particular monitor type at that resolution and color depth.
(1173985) Icon Editor dies when saving a 24-bit image to a file.
The IslandPaint application does not work properly under 24-bit mode. All of the button icons on the left side of the window are either missing images or display incorrect ones.
This Video Driver Update must be installed from diskettes. The diskette images are available either in a compressed (.Z file) or zipped (.zip file) format. Since either file produces the same diskette image, you only need to download the file in one of the formats.
To uncompress a compressed (.Z) file, type:
# uncompress du3vxxx |
where du3vxxx is the name of the uncompressed diskette image.
If you use Netscape to download a .Z file, it may remove the .Z suffix but not uncompress it. If this happens, rename the file before you uncompress it.
# mv du3vxxx du3vxxx.Z |
To unzip a zipped (.zip) file, follow the instructions that are appropriate for your unzip program.
When you are done, you should have files of size 1474560 bytes.
The contents of the Video Driver Update diskette are installed as patches on your Solaris 2.6 Intel Platform Edition system. To do this, you must already have the Solaris 2.6 Intel Platform Edition Driver Update installed and running on your system.
In Video Driver Update 3, there are six patches, each associated with a particular driver:
Each diskette image consists of one of the first five patches and v-common.
After installing this Video Driver Update as described in this chapter, at the system prompt, you may type:
% pkgparam SUNWxwpls TOPDRVLIST |
to see a sorted list showing all video drivers installed on the system as well as the current version number of each.
If you are installing Solaris 2.6 Intel Platform Edition software on a system that contains one of the video devices listed in Table 2-1, or on a notebook listed in Table 2-2, your video device or notebook will not be supported during the installation. When you get to the point in the Solaris installation when the kdmconfig - Introduction screen appears, press F4_Bypass to skip the window system configuration at this time. Skipping the configuration allows you to install with a non-window-system interface. Toward the end of the installation, you will be given the opportunity to install the Video Driver Update. This is the correct time to install this update. When you reboot the machine following the installation, kdmconfig will be run again, and you can configure your video device or notebook at this time.
Exit your window system to install the Video Driver Update.
If you are running the Common Desktop Environment (CDE), exit it and choose Command Line Login from Options. If you are running the OpenWindows environment, exit it.
Become root.
Type ps -ef | grep vold to see if the Volume Management software is running on the machine you are updating.
For more information about managing diskettes and drives, see System Administration Guide.
If Volume Management is running, temporarily stop it:
# /etc/init.d/volmgt stop |
Transfer each diskette image to diskette by inserting a writable diskette into your diskette drive and typing:
# dd if=du3vxxx of=/dev/rdiskette bs=10240 |
After the copy completes, you should see the messages:
144+0 records in144+0 records out # |
You only need to install the images for the video devices you intend to use.
Label the Solaris 2.6 Video Diver Update 3 diskette and insert it into the diskette drive.
Mount the diskette at the /mnt mount point:
# mount -F pcfs /dev/diskette /mnt |
You must mount the diskette at this point in the file structure to update your system successfully.
Execute the install script on the diskette by typing:
# /mnt/DU/sol_26/i86pc/Tools/install.sh -i |
The install.sh script searches for all new drivers on the diskette. When a new driver is found, the following prompt is displayed:
Install patch driver-name? [y] |
If the driver is the one you want to install, at the prompt, type y for yes or press Enter. If the driver is not the one you want to install, type n for no.
If you specify yes, the install.sh script installs the driver you indicated.
Whenever the driver v-common is available in a Video Driver Update, you should always install it.
When you're done and the install.sh script exits, unmount the diskette by typing the following command at the system prompt:
# umount /mnt |
Remove the diskette from the diskette drive.
Repeat Steps 5 through 11 for any additional Video Driver Update diskettes.
If Volume Management was turned off in Step 4, you may turn it on again:
# /etc/init.d/volmgt start |
After the Video Driver Update software has been installed, reconfigure the window system by typing:
# kdmconfig |
kdmconfig attempts to identify your video device, monitor, keyboard, and pointing device. The identification may be incorrect in some cases, so you should verify each selection. kdmconfig will give you an opportunity to change each of these selections, as well as the desired resolution and color depth. After the selections are made, kdmconfig will allow you to test the selected configuration by displaying a sample screen.
When you are satisfied with the configuration, click the Yes button on the sample screen to save the configuration and exit kdmconfig.
End your root login session and restart the CDE or OpenWindows environment.