Установка "мастера" на проблемное железо

Вопросы настройки и использования системы. Вопросы настройки и использования прикладного ПО.

Re: Установка "мастера" на проблемное железо

Сообщение Лимон » 29 янв 2010 15:39

ну нету драйвера!
покажи, что есть, командой: locate _drv.so
Лимон
Full Member
Full Member
 
Сообщения: 140
Зарегистрирован: 26 июн 2009 15:11
Откуда: Владивосток

Re: Установка "мастера" на проблемное железо

Сообщение hatred » 29 янв 2010 15:45

А согласно поиску в сизифе - Alt драйвер unichrome не предоставляют. Так что... http://unichrome.sf.net и собирать вручную. Возможно поможет. Кстати вывод lspci -nn | grep VGA тоже не помешает.
Прошли времена когда на элементарные вопросы можно было отвечать man <что-то там> (с) из сети
Hatred's Log Place | My GitHub repos | My Gitlab repos
Аватара пользователя
hatred
Global Moderator
Global Moderator
 
Сообщения: 1204
Зарегистрирован: 08 июн 2006 00:32
Откуда: Владивосток

Re: Установка "мастера" на проблемное железо

Сообщение Лимон » 29 янв 2010 16:35

unichrome не завелся потому, что он не установлен.
а openchrome потому, что
limberg писал(а):в xorg.conf пробовал ставить disable "glx", вместо "openhrome" писал "vesa" - не работает

openchrome надо, это описка только здесь или в конфиге ты тоже одну букву пропустил?
Лимон
Full Member
Full Member
 
Сообщения: 140
Зарегистрирован: 26 июн 2009 15:11
Откуда: Владивосток

Re: Установка "мастера" на проблемное железо

Сообщение limberg » 29 янв 2010 17:27

только здесь :)
как собирать? доступ к ссылке есть у тырнета?
сейчас логи выложу
"Где начало того конца, которое является этим началом?"
limberg
Advanced Newbie
Advanced Newbie
 
Сообщения: 49
Зарегистрирован: 07 дек 2009 14:54

Re: Установка "мастера" на проблемное железо

Сообщение limberg » 29 янв 2010 17:37

Лимон писал(а):ну нету драйвера!
покажи, что есть, командой: locate _drv.so

Нет такой команды :(

lspci -nn | grep VGA -дает следующее
01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc KM400/KN400/P4P800 [S3 Unichrome][1106:7205] (rev 01)
"Где начало того конца, которое является этим началом?"
limberg
Advanced Newbie
Advanced Newbie
 
Сообщения: 49
Зарегистрирован: 07 дек 2009 14:54

Re: Установка "мастера" на проблемное железо

Сообщение Лимон » 29 янв 2010 17:49

тогда
ls /usr/lib/xorg/modules/drivers/
кароче найти католог с файлами *_drv.so - это и есть установленные драйверы иксов.
предлагаю драйверы из дистрибутива использовать, самосборный х-драйвер может аукнуться в будущем (при обновлении ядра, например).
Лимон
Full Member
Full Member
 
Сообщения: 140
Зарегистрирован: 26 июн 2009 15:11
Откуда: Владивосток

Re: Установка "мастера" на проблемное железо

Сообщение limberg » 29 янв 2010 18:26

вОТ :)
Вложения
DC100129002.jpg
(226.08 КБ) Скачиваний: 0
"Где начало того конца, которое является этим началом?"
limberg
Advanced Newbie
Advanced Newbie
 
Сообщения: 49
Зарегистрирован: 07 дек 2009 14:54

Re: Установка "мастера" на проблемное железо

Сообщение hatred » 29 янв 2010 22:05

Лимон писал(а):предлагаю драйверы из дистрибутива использовать, самосборный х-драйвер может аукнуться в будущем (при обновлении ядра, например).


может, но в случае Альта они об унихроме не озаботились. Хотя... fbdev должен запуститься. хз, руками бы полапать
Прошли времена когда на элементарные вопросы можно было отвечать man <что-то там> (с) из сети
Hatred's Log Place | My GitHub repos | My Gitlab repos
Аватара пользователя
hatred
Global Moderator
Global Moderator
 
Сообщения: 1204
Зарегистрирован: 08 июн 2006 00:32
Откуда: Владивосток

Re: Установка "мастера" на проблемное железо

Сообщение Лимон » 01 фев 2010 12:49

включай openchrome и логи сюда
Лимон
Full Member
Full Member
 
Сообщения: 140
Зарегистрирован: 26 июн 2009 15:11
Откуда: Владивосток

Re: Установка "мастера" на проблемное железо

Сообщение limberg » 02 фев 2010 14:24

поставил "openchrome"
X.Org X Server 1.6.5
Release Date: 2009-10-11
X Protocol Version 11, Revision 0
Build Operating System: Simply GNU/Linux 5.0.0 RC2 (Billy) i686
Current Operating System: Linux test01.gym2.local 2.6.30-std-def-alt14 #1 SMP Wed Oct 7 06:44:21 UTC 2009 i686
Build Date: 12 October 2009 08:23:12AM

Before reporting problems, check https://bugzilla.altlinux.org/
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Feb 2 13:33:10 2010
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Minimal layout"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Samsung SyncMaster 793DF/793MB|0"
(**) | |-->Device "Card0|0"
(==) Automatically adding devices
(==) Automatically enabling devices
(==) FontPath set to:
catalogue:/etc/X11/fontpath.d
(==) ModulePath set to "/usr/lib/X11/modules"
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable AllowEmptyInput.
(II) Loader magic: 0x1bc0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(++) using VT number 7

(--) PCI:*(0:1:0:0) 1106:7205:1106:7205 VIA Technologies, Inc. KM400/KN400/P4M800 [S3 UniChrome] rev 1, Mem @ 0xf4000000/67108864, 0xf8000000/16777216, BIOS @ 0x????????/65536
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[16] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[20] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[21] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[22] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[23] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[24] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[25] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[26] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[27] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[28] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[29] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[30] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[31] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[32] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[33] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[34] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[35] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(II) Executed /usr/libexec/X11/drv.d/x11
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded by default.
(II) "glx" will be loaded by default.
(II) "dri" will be loaded by default.
(II) "dri2" will be loaded by default.
(II) LoadModule: "extmod"
(II) Loading /usr/lib/X11/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.6.5, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/X11/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.6.5, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/X11/modules/extensions/libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.6.5, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/lib/X11/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.6.5, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/X11/modules/extensions/libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.6.5, module version = 1.1.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "openchrome"
(II) Loading /usr/lib/X11/modules/drivers/openchrome_drv.so
(II) Module openchrome: vendor="http://openchrome.org/"
compiled for 1.6.4, module version = 0.2.904
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 5.0
(II) OPENCHROME: Driver for VIA Chrome chipsets: CLE266, KM400/KN400,
K8M800/K8N800, PM800/PM880/CN400, VM800/P4M800Pro/VN800/CN700,
K8M890/K8N890, P4M900/VN896/CN896, CX700/VX700, P4M890, VX800, VX855
(II) Primary Device is: PCI 01@00:00:0
(!!) VIA Technologies does not support this driver in any way.
(!!) For support, please refer to http://www.openchrome.org/.
(!!) (development build, compiled on Fri Oct 9 06:29:45 2009)
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[16] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[20] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[21] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[22] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[23] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[24] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[25] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[26] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[27] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[28] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[29] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[30] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[31] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[32] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[33] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[34] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[35] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]

__________________ первая часть
"Где начало того конца, которое является этим началом?"
limberg
Advanced Newbie
Advanced Newbie
 
Сообщения: 49
Зарегистрирован: 07 дек 2009 14:54

Re: Установка "мастера" на проблемное железо

Сообщение limberg » 02 фев 2010 14:25

Вторая часть лога
(II) CHROME(0): VIAPreInit
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/X11/modules/libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 1.6.5, module version = 0.1.0
ABI class: X.Org Video Driver, version 5.0
(II) CHROME(0): VIAGetRec
(**) CHROME(0): Depth 24, (--) framebuffer bpp 32
(==) CHROME(0): RGB weight 888
(==) CHROME(0): Default visual is TrueColor
(--) CHROME(0): Chipset: KM400/KN400
(--) CHROME(0): Chipset revision: 0
(--) CHROME(0): Probed amount of VideoRAM = 1024 kB
(II) CHROME(0): Setting up default chipset options.
(II) CHROME(0): VIASetupDefaultOptions
(II) CHROME(0): Reading config file...
(II) CHROME(0): Starting to parse config file options...
(==) CHROME(0): Shadow framebuffer is disabled.
(==) CHROME(0): Hardware acceleration is enabled.
(==) CHROME(0): Using XAA acceleration architecture.
(==) CHROME(0): Using hardware two-color cursors and software full-color cursors.
(==) CHROME(0): GPU virtual command queue will be enabled.
(==) CHROME(0): DRI IRQ will be disabled if DRI is enabled.
(==) CHROME(0): AGP DMA will be enabled if DRI is enabled.
(==) CHROME(0): AGP DMA will be used for 2D acceleration.
(==) CHROME(0): PCI DMA will be used for XV image transfer if DRI is enabled.
(==) CHROME(0): Will not enable VBE modes.
(==) CHROME(0): VBE VGA register save & restore will not be used
if VBE modes are enabled.
(==) CHROME(0): Xv Bandwidth check is enabled.
(==) CHROME(0): Will not impose a limit on video RAM reserved for DRI.
(==) CHROME(0): Will try to allocate 32768 kB of AGP memory.
(==) CHROME(0): Digital output bus width is 12 bits.
(==) CHROME(0): DVI Center is disabled.
(==) CHROME(0): Panel size is not selected from config file.
(==) CHROME(0): Panel will not be forced.
(==) CHROME(0): TV dotCrawl is disabled.
(==) CHROME(0): TV deflicker is set to 0.
(==) CHROME(0): No default TV type is set.
(==) CHROME(0): No default TV output signal type is set.
(==) CHROME(0): No default TV output port is set.
(II) CHROME(0): VIAMapMMIO
(--) CHROME(0): mapping MMIO @ 0xf8000000 with size 0x9000
(--) CHROME(0): mapping BitBlt MMIO @ 0xf8200000 with size 0x200000
(II) CHROME(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(==) CHROME(0): Will not print VGA registers.
(==) CHROME(0): Will not scan I2C buses.
(II) CHROME(0): ...Finished parsing config file options.
(WW) CHROME(0): Manufacturer plainly copied main PCI IDs to subsystem/card IDs.
(--) CHROME(0): Detected VIA VT7205 (KM400A). Card-Ids (1106|7205)
(II) CHROME(0): Detected MemClk 6
(II) CHROME(0): ViaGetMemoryBandwidth. Memory type: 6
(II) CHROME(0): Detected TV standard: NTSC.
(==) CHROME(0): Using gamma correction (1.0, 1.0, 1.0)
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Module "i2c" already built-in
(II) CHROME(0): ViaI2CInit
(II) CHROME(0): ViaI2CBus1Init
(II) CHROME(0): I2C bus "I2C bus 1" initialized.
(II) CHROME(0): ViaI2cBus2Init
(II) CHROME(0): I2C bus "I2C bus 2" initialized.
(II) CHROME(0): ViaI2CBus3Init
(II) CHROME(0): I2C bus "I2C bus 3" initialized.
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) CHROME(0): I2C device "I2C bus 1:E-EDID segment register" registered at address 0x60.
(II) CHROME(0): I2C device "I2C bus 1:ddc2" registered at address 0xA0.
(II) CHROME(0): Manufacturer: SAM Model: 107 Serial#: 1279602999
(II) CHROME(0): Year: 2005 Week: 3
(II) CHROME(0): EDID Version: 1.3
(II) CHROME(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
(II) CHROME(0): Sync: Separate
(II) CHROME(0): Max Image Size [cm]: horiz.: 31 vert.: 23
(II) CHROME(0): Gamma: 2.20
(II) CHROME(0): DPMS capabilities: Off; RGB/Color Display
(II) CHROME(0): Default color space is primary color space
(II) CHROME(0): First detailed timing is preferred mode
(II) CHROME(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.600
(II) CHROME(0): blueX: 0.150 blueY: 0.060 whiteX: 0.312 whiteY: 0.329
(II) CHROME(0): Supported established timings:
(II) CHROME(0): 720x400@70Hz
(II) CHROME(0): 640x480@60Hz
(II) CHROME(0): 640x480@67Hz
(II) CHROME(0): 640x480@72Hz
(II) CHROME(0): 640x480@75Hz
(II) CHROME(0): 800x600@56Hz
(II) CHROME(0): 800x600@60Hz
(II) CHROME(0): 800x600@72Hz
(II) CHROME(0): 800x600@75Hz
(II) CHROME(0): 832x624@75Hz
(II) CHROME(0): 1024x768@60Hz
(II) CHROME(0): 1024x768@70Hz
(II) CHROME(0): 1024x768@75Hz
(II) CHROME(0): 1152x870@75Hz
(II) CHROME(0): Manufacturer's mask: 0
(II) CHROME(0): Supported standard timings:
(II) CHROME(0): #0: hsize: 1024 vsize 768 refresh: 85 vid: 22881
(II) CHROME(0): #1: hsize: 800 vsize 600 refresh: 85 vid: 22853
(II) CHROME(0): #2: hsize: 640 vsize 480 refresh: 85 vid: 22833
(II) CHROME(0): #3: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) CHROME(0): #4: hsize: 1152 vsize 864 refresh: 75 vid: 20337
(II) CHROME(0): Supported detailed timing:
(II) CHROME(0): clock: 94.5 MHz Image Size: 312 x 234 mm
(II) CHROME(0): h_active: 1024 h_sync: 1072 h_sync_end 1168 h_blank_end 1376 h_border: 0
(II) CHROME(0): v_active: 768 v_sync: 769 v_sync_end 772 v_blanking: 808 v_border: 0
(II) CHROME(0): Ranges: V min: 50 V max: 160 Hz, H min: 30 H max: 71 kHz, PixClock max 110 MHz
(II) CHROME(0): Monitor name: SyncMaster
(II) CHROME(0): Serial No: HVBY119782
(II) CHROME(0): EDID (in hex):
(II) CHROME(0): 00ffffffffffff004c2d07013731454c
(II) CHROME(0): 030f0103681f17782eee91a3544c9926
(II) CHROME(0): 0f5054bfee806159455931598180714f
(II) CHROME(0): 010101010101ea240060410028303060
(II) CHROME(0): 130038ea1000001e000000fd0032a01e
(II) CHROME(0): 470b000a202020202020000000fc0053
(II) CHROME(0): 796e634d61737465720a2020000000ff
(II) CHROME(0): 00485642593131393738320a20200018
(II) CHROME(0): EDID vendor "SAM", prod id 263
(II) CHROME(0): Using hsync ranges from config file
(II) CHROME(0): Using vrefresh ranges from config file
(II) CHROME(0): Printing DDC gathered Modelines:
(II) CHROME(0): Modeline "1024x768"x0.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz)
(II) CHROME(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
(II) CHROME(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
(II) CHROME(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
(II) CHROME(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz)
(II) CHROME(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
(II) CHROME(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
(II) CHROME(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
(II) CHROME(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
(II) CHROME(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
(II) CHROME(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
(II) CHROME(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
(II) CHROME(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
(II) CHROME(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
(II) CHROME(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
(II) CHROME(0): Modeline "1024x768"x0.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz)
(II) CHROME(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz)
(II) CHROME(0): Modeline "640x480"x0.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz)
(II) CHROME(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(II) CHROME(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
(II) CHROME(0): ViaOutputsDetect
(II) CHROME(0): VIATVDetect
(II) CHROME(0): ViaOutputsSelect
(II) CHROME(0): ViaOutputsSelect: X Configuration: 0x00
(II) CHROME(0): ViaOutputsSelect: BIOS Initialised register: 0x00
(II) CHROME(0): ViaOutputsSelect: CRT.
(II) CHROME(0): ViaModesAttach
(II) CHROME(0): Samsung SyncMaster 793DF/793MB|0: Using hsync range of 30.00-71.00 kHz
(II) CHROME(0): Samsung SyncMaster 793DF/793MB|0: Using vrefresh range of 50.00-160.00 Hz
(II) CHROME(0): Samsung SyncMaster 793DF/793MB|0: Using maximum pixel clock of 110.00 MHz
(II) CHROME(0): Clock range: 20.00 to 230.00 MHz
(II) CHROME(0): ViaValidMode: Validating 640x350 (Clock: 31500)
(II) CHROME(0): ViaFirstCRTCModeValid
(II) CHROME(0): ViaComputeDotClock 31500 : c558 : 050b
(II) CHROME(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan)
(II) CHROME(0): ViaValidMode: Validating 640x400 (Clock: 31500)
(II) CHROME(0): ViaFirstCRTCModeValid
"Где начало того конца, которое является этим началом?"
limberg
Advanced Newbie
Advanced Newbie
 
Сообщения: 49
Зарегистрирован: 07 дек 2009 14:54

Re: Установка "мастера" на проблемное железо

Сообщение limberg » 02 фев 2010 14:28

Третья часть

(II) CHROME(0): ViaComputeDotClock 31500 : c558 : 050b
(II) CHROME(0): Not using default mode "320x200" (bad mode clock/interlace/doublescan)
(II) CHROME(0): Not using default mode "720x400" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "360x200" (bad mode clock/interlace/doublescan)
(II) CHROME(0): Not using default mode "640x480" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
(II) CHROME(0): Not using default mode "640x480" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
(II) CHROME(0): Not using default mode "640x480" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
(II) CHROME(0): Not using default mode "640x480" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
(II) CHROME(0): Not using default mode "800x600" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
(II) CHROME(0): Not using default mode "800x600" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
(II) CHROME(0): Not using default mode "800x600" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
(II) CHROME(0): Not using default mode "800x600" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
(II) CHROME(0): Not using default mode "800x600" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
(II) CHROME(0): Not using default mode "1024x768" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(II) CHROME(0): Not using default mode "1024x768" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(II) CHROME(0): Not using default mode "1024x768" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(II) CHROME(0): Not using default mode "1024x768" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(II) CHROME(0): Not using default mode "1024x768" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(II) CHROME(0): Not using default mode "1152x864" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
(II) CHROME(0): Not using default mode "1280x960" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "640x480" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "1280x960" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "640x480" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "1280x1024" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "640x512" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "1280x1024" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "640x512" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "1280x1024" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "640x512" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "1600x1200" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "800x600" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "1600x1200" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "800x600" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "1600x1200" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "800x600" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "1600x1200" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "800x600" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "1600x1200" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "800x600" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "1792x1344" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "896x672" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "1792x1344" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "896x672" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "1856x1392" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "928x696" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "1856x1392" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "928x696" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "1920x1440" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "960x720" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "1920x1440" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "960x720" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "832x624" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "416x312" (bad mode clock/interlace/doublescan)
(II) CHROME(0): Not using default mode "1400x1050" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "700x525" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "1400x1050" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "700x525" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "1920x1440" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "960x720" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "1024x768" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "1024x768" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) CHROME(0): Not using default mode "1024x768" (insufficient memory for mode)
(II) CHROME(0): Not using driver mode "1024x768" (insufficient memory for mode)
(II) CHROME(0): Not using driver mode "800x600" (insufficient memory for mode)
(II) CHROME(0): Not using driver mode "800x600" (insufficient memory for mode)
(II) CHROME(0): Not using driver mode "640x480" (insufficient memory for mode)
(II) CHROME(0): Not using driver mode "640x480" (insufficient memory for mode)
(II) CHROME(0): Not using driver mode "640x480" (insufficient memory for mode)
(II) CHROME(0): Not using driver mode "640x480" (insufficient memory for mode)
(II) CHROME(0): Not using driver mode "720x400" (insufficient memory for mode)
(II) CHROME(0): Not using driver mode "1024x768" (insufficient memory for mode)
(II) CHROME(0): Not using driver mode "1024x768" (insufficient memory for mode)
(II) CHROME(0): Not using driver mode "1024x768" (insufficient memory for mode)
(II) CHROME(0): Not using driver mode "832x624" (insufficient memory for mode)
(II) CHROME(0): Not using driver mode "800x600" (insufficient memory for mode)
(II) CHROME(0): Not using driver mode "800x600" (insufficient memory for mode)
(II) CHROME(0): Not using driver mode "1152x864" (insufficient memory for mode)
(II) CHROME(0): Not using driver mode "1024x768" (insufficient memory for mode)
(II) CHROME(0): Not using driver mode "800x600" (insufficient memory for mode)
(II) CHROME(0): Not using driver mode "640x480" (insufficient memory for mode)
(II) CHROME(0): Not using driver mode "1280x1024" (insufficient memory for mode)
(II) CHROME(0): Not using driver mode "1152x864" (insufficient memory for mode)
(II) CHROME(0): Not using mode "1280x1024" (no mode of this name)
(II) CHROME(0): Not using mode "1280x960" (no mode of this name)
(II) CHROME(0): Not using mode "1280x854" (no mode of this name)
(II) CHROME(0): Not using mode "1280x800" (no mode of this name)
(II) CHROME(0): Not using mode "1280x768" (no mode of this name)
(II) CHROME(0): Not using mode "1280x720" (no mode of this name)
(II) CHROME(0): Not using mode "1152x870" (no mode of this name)
(II) CHROME(0): Not using mode "1152x864" (no mode of this name)
(II) CHROME(0): Not using mode "1120x840" (no mode of this name)
(II) CHROME(0): Not using mode "1024x768" (no mode of this name)
(II) CHROME(0): Not using mode "1024x736" (no mode of this name)
(II) CHROME(0): Not using mode "1024x600" (no mode of this name)
(II) CHROME(0): Not using mode "960x720" (no mode of this name)
(II) CHROME(0): Not using mode "848x480" (no mode of this name)
(II) CHROME(0): Not using mode "832x624" (no mode of this name)
(II) CHROME(0): Not using mode "800x600" (no mode of this name)
(II) CHROME(0): Not using mode "720x576" (no mode of this name)
(II) CHROME(0): Not using mode "640x480" (no mode of this name)
(II) CHROME(0): ViaValidMode: Validating 640x400 (Clock: 31500)
(II) CHROME(0): ViaFirstCRTCModeValid
(II) CHROME(0): ViaComputeDotClock 31500 : c558 : 050b
(II) CHROME(0): ViaValidMode: Validating 640x350 (Clock: 31500)
(II) CHROME(0): ViaFirstCRTCModeValid
(II) CHROME(0): ViaComputeDotClock 31500 : c558 : 050b
(--) CHROME(0): Virtual size is 640x400 (pitch 640)
(**) CHROME(0): Default mode "640x400": 31.5 MHz (scaled from -0.0 MHz), 37.9 kHz, 85.1 Hz
(II) CHROME(0): Modeline "640x400"x85.1 31.50 640 672 736 832 400 401 404 445 -hsync +vsync (37.9 kHz)
(**) CHROME(0): Default mode "640x350": 31.5 MHz (scaled from -0.0 MHz), 37.9 kHz, 85.1 Hz
(II) CHROME(0): Modeline "640x350"x85.1 31.50 640 672 736 832 350 382 385 445 +hsync -vsync (37.9 kHz)
(**) CHROME(0): Display dimensions: (310, 230) mm
(**) CHROME(0): DPI set to (52, 44)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/X11/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.6.5, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/lib/X11/modules/libxaa.so
(II) Module xaa: vendor="X.Org Foundation"
compiled for 1.6.5, module version = 1.2.1
ABI class: X.Org Video Driver, version 5.0
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) CHROME(0): VIAUnmapMem
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[16] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[20] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[21] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[22] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[23] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[24] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[25] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[26] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[27] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[28] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[29] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[30] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[31] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[32] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[33] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[34] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[35] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(II) CHROME(0): VIAScreenInit
(II) CHROME(0): VIAMapFB
(--) CHROME(0): mapping framebuffer @ 0xf4000000 with size 0x100000
(--) CHROME(0): Frame buffer start: 0xb7920000, free start: 0xfa000 end: 0x100000
(II) CHROME(0): VIAMapMMIO
(--) CHROME(0): mapping MMIO @ 0xf8000000 with size 0x9000
(--) CHROME(0): mapping BitBlt MMIO @ 0xf8200000 with size 0x200000
(II) CHROME(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) CHROME(0): VIASave
(II) CHROME(0): Primary
(II) CHROME(0): Primary Adapter! saving VGA_SR_ALL !!
(II) CHROME(0): Non-Primary Adapter! saving VGA_SR_MODE only !!
(II) CHROME(0): Crtc...
(II) CHROME(0): TVSave...
(II) CHROME(0): VIAWriteMode
(II) CHROME(0): ViaModePrimaryLegacy
(II) CHROME(0): Name: 640x400
(II) CHROME(0): Clock: 31500
(II) CHROME(0): VRefresh: 85.079948
(II) CHROME(0): HSync: 37.860577
(II) CHROME(0): HDisplay: 640
(II) CHROME(0): HSyncStart: 672
(II) CHROME(0): HSyncEnd: 736
(II) CHROME(0): HTotal: 832
(II) CHROME(0): HSkew: 0
(II) CHROME(0): VDisplay: 400
(II) CHROME(0): VSyncStart: 401
(II) CHROME(0): VSyncEnd: 404
(II) CHROME(0): VTotal: 445
(II) CHROME(0): VScan: 0
(II) CHROME(0): Flags: 6
(II) CHROME(0): CrtcHDisplay: 0x280
(II) CHROME(0): CrtcHBlankStart: 0x280
(II) CHROME(0): CrtcHSyncStart: 0x2a0
(II) CHROME(0): CrtcHSyncEnd: 0x2e0
(II) CHROME(0): CrtcHBlankEnd: 0x340
(II) CHROME(0): CrtcHTotal: 0x340
(II) CHROME(0): CrtcHSkew: 0x0
(II) CHROME(0): CrtcVDisplay: 0x190
(II) CHROME(0): CrtcVBlankStart: 0x190
(II) CHROME(0): CrtcVSyncStart: 0x191
(II) CHROME(0): CrtcVSyncEnd: 0x194
(II) CHROME(0): CrtcVBlankEnd: 0x1bd
(II) CHROME(0): CrtcVTotal: 0x1bd
(II) CHROME(0): ViaFirstCRTCSetMode
(II) CHROME(0): Setting up 640x400
(II) CHROME(0): ViaComputeDotClock 31500 : c558 : 050b
(II) CHROME(0): ViaTVPower: Off.
(II) CHROME(0): ViaSetPrimaryFIFO
(II) CHROME(0): ViaSetPrimaryExpireNumber
(II) CHROME(0): ViaSetDotclock to 0x00050b
(II) CHROME(0): ViaSetUseExternalClock
(II) CHROME(0): VIAAdjustFrame 0x0
(II) CHROME(0): VIAAdjustFrame 0x0
(II) CHROME(0): - Blanked
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: node name is /dev/dri/card0
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: drmOpenMinor returns 8
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
(II) [drm] loaded kernel module for "via" driver.
(II) [drm] DRM interface version 1.3
(II) [drm] DRM open master succeeded.
(II) CHROME(0): [drm] Using the DRM lock SAREA also for drawables.
(II) CHROME(0): [drm] framebuffer handle = 0xf4000000
(II) CHROME(0): [drm] added 1 reserved context for kernel
(II) CHROME(0): X context handle = 0x1
(II) CHROME(0): [drm] installed DRM signal handler
(II) CHROME(0): [dri] visual configs initialized.
(II) CHROME(0): [drm] register handle = 0xf8000000
(II) CHROME(0): [drm] framebuffer handle = 0xf4000000
(II) CHROME(0): [drm] mmio Registers = 0xf8000000
(II) CHROME(0): [dri] mmio mapped.
(II) CHROME(0): - Visuals set up
(II) CHROME(0): VIAInternalScreenInit
(II) CHROME(0): - B & W
(II) CHROME(0): CursorStart: 0x100000
(II) CHROME(0): Frame Buffer From (0,0) To (640,404)
(II) CHROME(0): Using 4 lines for offscreen memory.
(II) CHROME(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
8x8 color pattern filled rectangles
Solid Lines
Dashed Lines
Image Writes
Setting up tile and stipple cache:
32 8x8 color pattern slots
(==) CHROME(0): Backing store disabled
(II) CHROME(0): - Backing store set up
(II) CHROME(0): - SW cursor set up

Backtrace:
0: /usr/bin/X(xorg_backtrace+0x3b) [0x81220ab]
1: /usr/bin/X(xf86SigHandler+0x9e) [0x80c9abe]
2: [0xb7ff8400]
3: /usr/lib/X11/modules/drivers/openchrome_drv.so [0xb7a36baf]
4: /usr/bin/X(AddScreen+0x198) [0x806a958]
5: /usr/bin/X(InitOutput+0x3de) [0x80a8a4e]
6: /usr/bin/X(main+0x1cb) [0x806b06b]
7: /lib/libc.so.6(__libc_start_main+0xe6) [0xb7bcdb26]
8: /usr/bin/X [0x806a6e1]

Fatal server error:
Caught signal 11. Server aborting


Please consult the The X.Org Foundation support
at https://bugzilla.altlinux.org/
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

(II) CHROME(0): VIALeaveVT
"Где начало того конца, которое является этим началом?"
limberg
Advanced Newbie
Advanced Newbie
 
Сообщения: 49
Зарегистрирован: 07 дек 2009 14:54

Re: Установка "мастера" на проблемное железо

Сообщение hatred » 02 фев 2010 14:39

Слушай, есть мысль, отключить фрейм буфферную консоль. Попробуй отредактировать конфиг /etc/lilo.conf
и закоментировать все строчки vga (поставив # перед ними), после ОБЯЗАТЕЛЬНО дай команду lilo, иначе систему уже не загрузишь.

После чего перезагружаешься и пробуешь. Но вообще, если установка в графическом режиме прошла, запустить графику - реал.
Прошли времена когда на элементарные вопросы можно было отвечать man <что-то там> (с) из сети
Hatred's Log Place | My GitHub repos | My Gitlab repos
Аватара пользователя
hatred
Global Moderator
Global Moderator
 
Сообщения: 1204
Зарегистрирован: 08 июн 2006 00:32
Откуда: Владивосток

Re: Установка "мастера" на проблемное железо

Сообщение Лимон » 02 фев 2010 15:13

отключи курсоры:
Section "Device"
Option SWCursor false
Option HWCursor false
EndSection
если не заработает, логи сюда, только прикрепляй их, а не цитируй, они большие.
если так заработает, то по одному включай и пробуй - может какой из них заработает.
Лимон
Full Member
Full Member
 
Сообщения: 140
Зарегистрирован: 26 июн 2009 15:11
Откуда: Владивосток

Re: Установка "мастера" на проблемное железо

Сообщение limberg » 02 фев 2010 16:16

Так с чего начать?
"Где начало того конца, которое является этим началом?"
limberg
Advanced Newbie
Advanced Newbie
 
Сообщения: 49
Зарегистрирован: 07 дек 2009 14:54

Пред.След.

Вернуться в Linux в школе

Кто сейчас на конференции

Сейчас этот форум просматривают: нет зарегистрированных пользователей и гости: 1

cron