Насчет того, что так все должно работать, скажу так: весь день промучался, пробовал разные конфиги иксов, вычислял и на онлайн-калькуляторе, и на gtf 800 600 75, gtf 800 600 72, ... С modeline ничего не запускается, ругается на режимы. На каком-то форуме в инете прочитал, что "определило нормально мою видюху ...", а "Х-сервер запускается с рефрешем в 60 Гц". Там посоветовали подправить конфиги Х-сервера, а именно, рассчитать и прописать моделайн.
P.S. В свое время написал *.inf файлик для своего монитора под Win NT, чтоб разные дурные игрушки не пытались установить на моем моне режимы вроде 1024x768@85 и выше, из-за чего сбивалась его частота синхронизации и он "пищал". Сейчас под виндой у меня 3 доступных разрешения: 640x480@60, 800x600@75, 1024@768@60. И больше никаких. При всем своем желании при опросе оборудования винда скажет, что мой мон других разрешений не держит. Но 800x600@75 реализуется только при наличии дров под видео. Я не разбираюсь как там под линухом, но подозреваю, что моделайн - это аналог подобного *.inf, а дрова, наверно, все-таки нужны (если их поддержки нет в иксах) ... Хотя ... На видео должны же быть какие-то станд. средства выставления частоты рефреша.
Driver Status for XFree86[tm] 4.3.0
29. S3
3.3.6:
Support (accelerated) for the S3 911, 924, 801, 805, 928, 864, 868, 964, 968, Trio32, Trio64, Trio64V+, Trio64UV+, Aurora64V+, Trio64V2, and PLATO/PX is provided by the XF86_S3 server and the XF86_SVGA server with the s3_svga driver. Support (accelerated) for the ViRGE, ViRGE/VX, ViRGE/DX, ViRGE/GX, ViRGE/GX2, ViRGE/MX, ViRGE/MX+ is provided by the XF86_S3V server. Support (accelerated) for the ViRGE chipsets, as well as the Trio3D and Trio3D/2X, is provided by the XF86_SVGA server with the s3v driver. Support (accelerated) for the Savage3D, Savage3D/MV, Savage4, and Savage2000, is provided by the XF86_SVGA server with the s3_savage driver on some OSes (Linux, *BSD).
4.3.0:
Support (accelerated) for the 964 (revisions 0 and 1), 968, Trio32, Trio64, Trio64, Trio64V+, Trio64UV+, Aurora64V+, Trio64V2, and PLATO/PX is provided by the "s3" driver (however, only models using the IBM RGB 524, Texas Instruments 3025, or an internal TrioDAC RAMDAC chip are supported). Support (accelerated) for the ViRGE, ViRGE/VX, ViRGE/DX, ViRGE/GX, ViRGE/GX2, ViRGE/MX, ViRGE/MX+, Trio3D and Trio3D/2X is provided by the "s3virge" driver. Support (accelerated) for the Savage3D, Savage3D/MV, Savage4, Savage2000, and SuperSavage, is provided by the "savage" driver. Support for the other S3 chipsets has not yet been ported.
Summary:
All hardware supported in 3.3.6 is also supported in 4.3.0 except for the 911, 924, 801, 805, 928, 864, and 868, and versions of the 964 and 968 that do not use the RAMDAC chips listed above. The SuperSavage chipset is supported only in 4.3.0.
Самая близкая модель - S3 Savage (более старая версия интегрированного видео). Вот что про нее написано:
savage is an XFree86 driver for the S3 Savage family video accelerator chips. The savage driver supports PCI and AGP boards with the following chips:
Savage3D
(8a20 and 8a21)
Savage4
(8a22)
Savage2000
(9102)
Savage/MX
(8c10 and 8c11)
Savage/IX
(8c12 and 8c13)
ProSavage PM133
(8a25)
ProSavage KM133
(8a26)
Twister (ProSavage PN133)
(8d01)
TwisterK (ProSavage KN133)
(8d02)
ProSavage DDR
(8d03)
ProSavage DDR-K
(8d04)
{Configuration Details}
Please refer to {XF86Config(5)} for general configuration details. This section only covers configuration details specific to this driver.
The following driver Options are supported:
Option "HWCursor" "boolean"
Option "SWCursor" "boolean"
These two options interact to specify hardware or software cursor. If the SWCursor option is specified, any HWCursor setting is ignored. Thus, either "HWCursor off" or "SWCursor on" will force the use of the software cursor. On Savage/MX and Savage/IX chips which are connected to LCDs, a software cursor will be forced, because the Savage hardware cursor does not correctly track the automatic panel expansion feature. Default: hardware cursor.
Option "NoAccel" "boolean"
Disable or enable acceleration. Default: acceleration is enabled.
Option "Rotate" "CW"
Option "Rotate" "CCW"
Rotate the desktop 90 degrees clockwise or counterclockwise. This option forces the ShadowFB option on, and disables acceleration. Default: no rotation.
Option "ShadowFB" "boolean"
Enable or disable use of the shadow framebuffer layer. See {shadowfb(4)} for further information. This option disables acceleration. Default: off.
Option "LCDClock" "frequency"
Override the maximum dot clock. Some LCD panels produce incorrect results if they are driven at too fast of a frequency. If UseBIOS is on, the BIOS will usually restrict the clock to the correct range. If not, it might be necessary to override it here. The frequency parameter may be specified as an integer in Hz (135750000), or with standard suffixes like "k", "kHz", "M", or "MHz" (as in 135.75MHz).
Option "UseBIOS" "boolean"
Enable or disable use of the video BIOS to change modes. Ordinarily, the savage driver tries to use the video BIOS to do mode switches. This generally produces the best results with the mobile chips (/MX and /IX), since the BIOS knows how to handle the critical but unusual timing requirements of the various LCD panels supported by the chip. To do this, the driver searches through the BIOS mode list, looking for the mode which most closely matches the XF86Config mode line. Some purists find this scheme objectionable. If you would rather have the savage driver use your mode line timing exactly, turn off the UseBios option. Default: on (use the BIOS).
Option "ShadowStatus" q*boolean"
Enables the use of a shadow status register. There is a chip bug in the Savage graphics engine that can cause a bus lock when reading the engine status register under heavy load, such as when scrolling text or dragging windows. The bug affects about 4% of all Savage users. If your system hangs regularly while scrolling text or dragging windows, try turning this option on. This uses an alternate method of reading the engine status which is slightly more expensive, but avoids the problem. Default: off (use normal status register).
P.S. В свое время написал *.inf файлик для своего монитора под Win NT, чтоб разные дурные игрушки не пытались установить на моем моне режимы вроде 1024x768@85 и выше, из-за чего сбивалась его частота синхронизации и он "пищал". Сейчас под виндой у меня 3 доступных разрешения: 640x480@60, 800x600@75, 1024@768@60. И больше никаких. При всем своем желании при опросе оборудования винда скажет, что мой мон других разрешений не держит. Но 800x600@75 реализуется только при наличии дров под видео. Я не разбираюсь как там под линухом, но подозреваю, что моделайн - это аналог подобного *.inf, а дрова, наверно, все-таки нужны (если их поддержки нет в иксах) ... Хотя ... На видео должны же быть какие-то станд. средства выставления частоты рефреша.
Driver Status for XFree86[tm] 4.3.0
29. S3
3.3.6:
Support (accelerated) for the S3 911, 924, 801, 805, 928, 864, 868, 964, 968, Trio32, Trio64, Trio64V+, Trio64UV+, Aurora64V+, Trio64V2, and PLATO/PX is provided by the XF86_S3 server and the XF86_SVGA server with the s3_svga driver. Support (accelerated) for the ViRGE, ViRGE/VX, ViRGE/DX, ViRGE/GX, ViRGE/GX2, ViRGE/MX, ViRGE/MX+ is provided by the XF86_S3V server. Support (accelerated) for the ViRGE chipsets, as well as the Trio3D and Trio3D/2X, is provided by the XF86_SVGA server with the s3v driver. Support (accelerated) for the Savage3D, Savage3D/MV, Savage4, and Savage2000, is provided by the XF86_SVGA server with the s3_savage driver on some OSes (Linux, *BSD).
4.3.0:
Support (accelerated) for the 964 (revisions 0 and 1), 968, Trio32, Trio64, Trio64, Trio64V+, Trio64UV+, Aurora64V+, Trio64V2, and PLATO/PX is provided by the "s3" driver (however, only models using the IBM RGB 524, Texas Instruments 3025, or an internal TrioDAC RAMDAC chip are supported). Support (accelerated) for the ViRGE, ViRGE/VX, ViRGE/DX, ViRGE/GX, ViRGE/GX2, ViRGE/MX, ViRGE/MX+, Trio3D and Trio3D/2X is provided by the "s3virge" driver. Support (accelerated) for the Savage3D, Savage3D/MV, Savage4, Savage2000, and SuperSavage, is provided by the "savage" driver. Support for the other S3 chipsets has not yet been ported.
Summary:
All hardware supported in 3.3.6 is also supported in 4.3.0 except for the 911, 924, 801, 805, 928, 864, and 868, and versions of the 964 and 968 that do not use the RAMDAC chips listed above. The SuperSavage chipset is supported only in 4.3.0.
Самая близкая модель - S3 Savage (более старая версия интегрированного видео). Вот что про нее написано:
savage is an XFree86 driver for the S3 Savage family video accelerator chips. The savage driver supports PCI and AGP boards with the following chips:
Savage3D
(8a20 and 8a21)
Savage4
(8a22)
Savage2000
(9102)
Savage/MX
(8c10 and 8c11)
Savage/IX
(8c12 and 8c13)
ProSavage PM133
(8a25)
ProSavage KM133
(8a26)
Twister (ProSavage PN133)
(8d01)
TwisterK (ProSavage KN133)
(8d02)
ProSavage DDR
(8d03)
ProSavage DDR-K
(8d04)
{Configuration Details}
Please refer to {XF86Config(5)} for general configuration details. This section only covers configuration details specific to this driver.
The following driver Options are supported:
Option "HWCursor" "boolean"
Option "SWCursor" "boolean"
These two options interact to specify hardware or software cursor. If the SWCursor option is specified, any HWCursor setting is ignored. Thus, either "HWCursor off" or "SWCursor on" will force the use of the software cursor. On Savage/MX and Savage/IX chips which are connected to LCDs, a software cursor will be forced, because the Savage hardware cursor does not correctly track the automatic panel expansion feature. Default: hardware cursor.
Option "NoAccel" "boolean"
Disable or enable acceleration. Default: acceleration is enabled.
Option "Rotate" "CW"
Option "Rotate" "CCW"
Rotate the desktop 90 degrees clockwise or counterclockwise. This option forces the ShadowFB option on, and disables acceleration. Default: no rotation.
Option "ShadowFB" "boolean"
Enable or disable use of the shadow framebuffer layer. See {shadowfb(4)} for further information. This option disables acceleration. Default: off.
Option "LCDClock" "frequency"
Override the maximum dot clock. Some LCD panels produce incorrect results if they are driven at too fast of a frequency. If UseBIOS is on, the BIOS will usually restrict the clock to the correct range. If not, it might be necessary to override it here. The frequency parameter may be specified as an integer in Hz (135750000), or with standard suffixes like "k", "kHz", "M", or "MHz" (as in 135.75MHz).
Option "UseBIOS" "boolean"
Enable or disable use of the video BIOS to change modes. Ordinarily, the savage driver tries to use the video BIOS to do mode switches. This generally produces the best results with the mobile chips (/MX and /IX), since the BIOS knows how to handle the critical but unusual timing requirements of the various LCD panels supported by the chip. To do this, the driver searches through the BIOS mode list, looking for the mode which most closely matches the XF86Config mode line. Some purists find this scheme objectionable. If you would rather have the savage driver use your mode line timing exactly, turn off the UseBios option. Default: on (use the BIOS).
Option "ShadowStatus" q*boolean"
Enables the use of a shadow status register. There is a chip bug in the Savage graphics engine that can cause a bus lock when reading the engine status register under heavy load, such as when scrolling text or dragging windows. The bug affects about 4% of all Savage users. If your system hangs regularly while scrolling text or dragging windows, try turning this option on. This uses an alternate method of reading the engine status which is slightly more expensive, but avoids the problem. Default: off (use normal status register).
Вижу, что выделено слово Console. Точно не знаю (по названию могу предположить, что для консоли устанавливается режим), а поэтому интересно, что же это за драйвер я скачал?Pigeon сказав(ла):
Останнє редагування:
