[Hardware] xorg-drv-trident - не стартуют X с экраном 50"
x_empty_dragon
=?iso-8859-1?q?x=2Eempty=2Edragon_=CE=C1_gmail=2Ecom?=
Вт Мар 3 14:56:57 MSK 2009
продолжаю...
в chrooot/etc/lts.conf
[default]
USE_XFS=N
XKBLAYOUT="us,ru,uk"
XKBVARIANT=",winkeys,winkeys"
XKBOPTIONS="grp:ctrl_shift_toggle"
X_COLOR_DEPTH=24
X_FONTS=/usr/share/fonts/bitmap/misc:unscaled
* XF86CONFIG_FILE=/etc/xorg.conf*
NBD_SWAP=Y
ENCRYPT_SWAP=N
SOUND=Y
SOUND_DAEMON=pulseaudio
SOUND_VOL=80
LOCALDEV=Y
INFO=Y
POWER_BUTTON=Y
*в /etc/xorg.conf*
Section "ServerLayout"
Identifier "Minimal layout"
Screen "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "ttyS0" "CorePointer"
EndSection
Section "Module"
Load "glx"
Load "dri"
Load "dbe"
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "ttyS0"
Driver "mouse"
Option "Device" "/dev/ttyS0"
Option "Protocol" "microsoft"
EndSection
Section "Monitor"
Identifier "phl4244|0"
HorizSync 30-80
VertRefresh 50-85
Modeline "1024x768" 60.00 1024 1056 1080 1280 768 770 773 808
Option "DPMS"
EndSection
Section "Device"
Identifier "Card0|0"
Driver "trident"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0|0"
Monitor "phl4244|0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1024x768"
EndSubSection
EndSection
#end
HorizSync 30-80 VertRefresh 50-85 взял из руководства к монитору
моделайн с генерировал с помощью videogen указал разрешение итд...
*в логах клиента опять наблюдаю *
(--) TRIDENT(0): Revision is 106
(--) TRIDENT(0): Found CyberBlade/i1 chip
(--) TRIDENT(0): RAM type is SDRAM
(--) TRIDENT(0): Using SW cursor
(--) TRIDENT(0): VideoRAM: 8192 kByte
(--) TRIDENT(0): TFT Panel 800x600 found
(--) TRIDENT(0): Memory Clock is 57.27 MHz
(==) TRIDENT(0): Min pixel clock is 12 MHz
(--) TRIDENT(0): Max pixel clock is 115 MHz
(II) TRIDENT(0): phl4244|0: Using hsync value of 0.00 kHz
(II) TRIDENT(0): phl4244|0: Using vrefresh value of 0.00 Hz
(II) TRIDENT(0): Clock range: 12.00 to 115.00 MHz
(II) TRIDENT(0): Not using default mode "1600x1024" (hsync out of range)
(II) TRIDENT(0): Not using default mode "800x512" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "1680x1050" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "840x525" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "1680x1050" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "840x525" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "1680x1050" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "840x525" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "1680x1050" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "1920x1200" (insufficient memory for
mode)
(II) TRIDENT(0): Not using default mode "960x600" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "1920x1200" (insufficient memory for
mode)
(II) TRIDENT(0): Not using default mode "960x600" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "1920x1200" (insufficient memory for
mode)
(II) TRIDENT(0): Not using default mode "960x600" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "1024x768" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "2048x1536" (insufficient memory for
mode)
(II) TRIDENT(0): Not using default mode "1024x768" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "2560x1600" (insufficient memory for
mode)
(II) TRIDENT(0): Not using default mode "1280x800" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using driver mode "800x600" (hsync out of range)
(II) TRIDENT(0): Not using driver mode "800x600" (hsync out of range)
(II) TRIDENT(0): Not using driver mode "640x480" (hsync out of range)
(II) TRIDENT(0): Not using driver mode "640x480" (hsync out of range)
(II) TRIDENT(0): Not using driver mode "640x480" (hsync out of range)
(II) TRIDENT(0): Not using driver mode "640x480" (hsync out of range)
(II) TRIDENT(0): Not using driver mode "720x400" (hsync out of range)
(II) TRIDENT(0): Not using driver mode "1280x1024" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using driver mode "1024x768" (hsync out of range)
(II) TRIDENT(0): Not using driver mode "1024x768" (hsync out of range)
(II) TRIDENT(0): Not using driver mode "1024x768" (hsync out of range)
(II) TRIDENT(0): Not using driver mode "800x600" (hsync out of range)
(II) TRIDENT(0): Not using driver mode "800x600" (hsync out of range)
(II) TRIDENT(0): Not using driver mode "1152x864" (hsync out of range)
(II) TRIDENT(0): Not using driver mode "640x480" (hsync out of range)
(II) TRIDENT(0): Not using driver mode "800x600" (hsync out of range)
(II) TRIDENT(0): Not using driver mode "1024x768" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using driver mode "1024x768" (hsync out of range)
(II) TRIDENT(0): Not using driver mode "1024x768" (hsync out of range)
(II) TRIDENT(0): Not using driver mode "1280x720" (hsync out of range)
(II) TRIDENT(0): Not using driver mode "1280x1024" (hsync out of range)
(II) TRIDENT(0): Not using driver mode "1280x1024" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using driver mode "848x480" (hsync out of range)
(II) TRIDENT(0): Not using driver mode "1360x768" (hsync out of range)
(WW) TRIDENT(0): Mode pool is empty
(EE) TRIDENT(0): No valid modes found
(II) UnloadModule: "trident"
(II) UnloadModule: "int10"
(II) Unloading /usr/lib/X11/modules// libint10.so
(II) UnloadModule: "vbe"
(II) Unloading /usr/lib/X11/modules//libvbe.so
(II) UnloadModule: "vgahw"
(II) Unloading /usr/lib/X11/modules//libvgahw.so
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
почему он пытается перебирать разрешение экрана .....может он не берет то
что указано в lts.conf ??? ( я понимаю что это больше относится к рассылке
ALT-LTSP ... но просто создавать точно такуеже тему в другой рассылке
выглядит как то не гуммано!
----------- следующая часть -----------
Вложение в формате HTML было удалено...
URL: <http://lists.altlinux.org/pipermail/hardware/attachments/20090303/036575b6/attachment-0001.html>
Подробная информация о списке рассылки Hardware