V F10 je graficke rozranni spusteno pod Ctrl+ALt+F1. Prvni textova konzole je pod Ctrl+Alt+F2. To ze se pri prepnuti na ctrl+alt+f1 nebo init 3 neni normalni. Otazka je, jak si se k F10 dostal. Pokud aktualizaci z predchozich verzi, muze tento stav nastat pokud se konzoli “1” pokousi obsadit zaroven textova konzole tak graficke rozhranni.
Zkus sem prosim dat vypis prikazu “ps ax | grep tty”.
ahoj
jj přesně tak na F10 jsem se dostal aktualizací z předchozí verze. dík
2193 tty4 Ss+ 0:00 /sbin/mingetty tty4
2194 tty5 Ss+ 0:00 /sbin/mingetty tty5
2195 tty2 Ss+ 0:00 /sbin/mingetty tty2
2196 tty3 Ss+ 0:00 /sbin/mingetty tty3
2197 tty6 Ss+ 0:00 /sbin/mingetty tty6
2230 tty1 Ss+ 2:56 /usr/bin/X -br -nolisten tcp :0 vt1 -auth /var/run/xauth/A:0-xFgq50
4250 pts/0 S+ 0:00 grep tty
Podle tohoto vypisu to nevypada. Bug ktery jsem odkazoval vyse je ale uz uzavreny jako opraveny, takze pokud mas vsechny aktualizace nainstalovane, pak bohuzel nevim.
No díkes za odpověd =)
dneska sem to znovu zkoušel a při ctrl-alt-f2 naskočila černá obrazovka s modrými vertikálními pruhy a totální zásek nic nepomohlo jen tvrdý vypnutí. Po znovu zapnutí pc však začala blikat celá obrazovka asi podsvícení lcd displeje. tak sem párkrát restartoval a bez úspěchu pomohlo až vypnutí na 5 minut.
ještě abych si odrovnal notase =(
Zkus si pridat na radek kernel do /etc/grub.conf nakonec “nomodeset”. V F10 je sice uzasna ficura prepinani rozliseni a modu grafiky bez blikani, ale na nekterych grafikach to nedela dobroru… doufam ze jsem ten parametr napsal dobre, kdyztak hledej tady na foru.
Ahoj.
Mám problém s rozchozením karty ATI Radeon 3650 pod Fedorou 10 s driverem fglrx.
Instalovat fedoru jsem musel v textovém modu, pak jsem nastavil driver na vesa, což je doposud jediná fungující varianta.
Zkusil jsem zdejší návod na rozchození, stejně tak jako i jeden z http://forums.fedoraforum.org/
Zkusil jsem kmod z rpm fusion i origo driver od ATI. Jediné co se stane po změně driveru v xorg.conf na fglrx je, že monitor při startu xserveru zhasne a parkrát mi dokonce zamrzl počítač uplně.
Prosím, pokud někdo víte jak, poraďtě co bych měl vyzkoušet, co zkontrolovat.
uname -r
2.6.27.19-170.2.35.fc10.x86_64
xorg.conf
Section "ServerLayout"
Identifier "blabla"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib64/xorg/modules/extensions/fglrx"
ModulePath "/usr/lib64/xorg/modules"
EndSection
Section "ServerFlags"
Option "AIGLX" "on"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
#DisplaySize 330 270 # mm
Identifier "Monitor0"
VendorName "IQT"
ModelName "L17T"
Option "DPMS"
EndSection
Section "Device"
Identifier "ATI"
Driver "fglrx"
Option "OpenGLOverlay" "off"
Option "VideoOverlay" "on"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "ATI"
Monitor "Monitor0"
DefaultDepth 24
EndSection
Section "Extensions"
Option "Composite" "Enable"
EndSection
Jeste dodavam vypis warningu z /var/log/Xorg.0.log. Error tam neni zadny.
Dokazal by mi nekdo prosim trochu vysvetlit, co ten log rika? Dik moc.
(WW) Disabling Keyboard0
(WW) fglrx: Force AIGLX enabled
(WW) Falling back to old probe method for fglrx
(WW) This ATI Proprietary Linux Driver does not guarantee support of video driver ABI higher than 2.0
(WW) Video driver ABI version of the X server is 4.1
(WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
(WW) AIGLX: 3D driver claims to not support visual 0x33
(WW) AIGLX: 3D driver claims to not support visual 0x34
(WW) AIGLX: 3D driver claims to not support visual 0x35
(WW) AIGLX: 3D driver claims to not support visual 0x36
(WW) AIGLX: 3D driver claims to not support visual 0x37
(WW) AIGLX: 3D driver claims to not support visual 0x38
(WW) AIGLX: 3D driver claims to not support visual 0x39
(WW) AIGLX: 3D driver claims to not support visual 0x3a
(WW) AIGLX: 3D driver claims to not support visual 0x3b
(WW) AIGLX: 3D driver claims to not support visual 0x3c
(WW) AIGLX: 3D driver claims to not support visual 0x3d
(WW) AIGLX: 3D driver claims to not support visual 0x3e
(WW) AIGLX: 3D driver claims to not support visual 0x3f
(WW) AIGLX: 3D driver claims to not support visual 0x40
(WW) AIGLX: 3D driver claims to not support visual 0x41
(WW) AIGLX: 3D driver claims to not support visual 0x42
(WW) AIGLX: 3D driver claims to not support visual 0x43
(WW) AIGLX: 3D driver claims to not support visual 0x44
(WW) AIGLX: 3D driver claims to not support visual 0x45
(WW) AIGLX: 3D driver claims to not support visual 0x46
(WW) AIGLX: 3D driver claims to not support visual 0x47
(WW) AIGLX: 3D driver claims to not support visual 0x48
(WW) AIGLX: 3D driver claims to not support visual 0x49
(WW) AIGLX: 3D driver claims to not support visual 0x4a
(WW) AIGLX: 3D driver claims to not support visual 0x4b
(WW) AIGLX: 3D driver claims to not support visual 0x4c
(WW) AIGLX: 3D driver claims to not support visual 0x4d
(WW) AIGLX: 3D driver claims to not support visual 0x4e
(WW) AIGLX: 3D driver claims to not support visual 0x4f
(WW) AIGLX: 3D driver claims to not support visual 0x50
(WW) AIGLX: 3D driver claims to not support visual 0x51
(WW) AIGLX: 3D driver claims to not support visual 0x52
(WW) AIGLX: 3D driver claims to not support visual 0x53
(WW) AIGLX: 3D driver claims to not support visual 0x54
(WW) AIGLX: 3D driver claims to not support visual 0x55
(WW) AIGLX: 3D driver claims to not support visual 0x56
(WW) AIGLX: 3D driver claims to not support visual 0x57
(WW) AIGLX: 3D driver claims to not support visual 0x58
(WW) AIGLX: 3D driver claims to not support visual 0x59
(WW) AIGLX: 3D driver claims to not support visual 0x5a
(WW) AIGLX: 3D driver claims to not support visual 0x5b
(WW) AIGLX: 3D driver claims to not support visual 0x5c
(WW) AIGLX: 3D driver claims to not support visual 0x5d
(WW) AIGLX: 3D driver claims to not support visual 0x5e
(WW) AIGLX: 3D driver claims to not support visual 0x5f
(WW) AIGLX: 3D driver claims to not support visual 0x60
(WW) AIGLX: 3D driver claims to not support visual 0x61
(WW) AIGLX: 3D driver claims to not support visual 0x62
(WW) AIGLX: 3D driver claims to not support visual 0x63
(WW) AIGLX: 3D driver claims to not support visual 0x64
(WW) AIGLX: 3D driver claims to not support visual 0x65
(WW) AIGLX: 3D driver claims to not support visual 0x66
(WW) AIGLX: 3D driver claims to not support visual 0x67
(WW) AIGLX: 3D driver claims to not support visual 0x68
(WW) AIGLX: 3D driver claims to not support visual 0x69
(WW) AIGLX: 3D driver claims to not support visual 0x6a
(WW) AIGLX: 3D driver claims to not support visual 0x6b
(WW) AIGLX: 3D driver claims to not support visual 0x6c
(WW) AIGLX: 3D driver claims to not support visual 0x6d
(WW) AIGLX: 3D driver claims to not support visual 0x6e
(WW) AIGLX: 3D driver claims to not support visual 0x6f
(WW) AIGLX: 3D driver claims to not support visual 0x70
(WW) AIGLX: 3D driver claims to not support visual 0x71
(WW) AIGLX: 3D driver claims to not support visual 0x72
Pokud nutne nepotrebujes fglrx zkousel si vychozi ovladace jako “radeonhd”?
Dík moc za odpověď. Zatím nezkoušel, takže jsem to teď zkusil:
Výsledek: (EE) RADEONHD(0): Output DVI-I_2/analog enabled but has no modes
S tím si bohužel opět nevím rady.
Nevim proc presne dochazi k tehle chybe ani co znamena. Muze to byt bud ze se nepovedlo pro prislusny vystup najit zadny kompatibilni mod (tedy prunik modu ktere podporuje monitor a karta je prazdny). Reseni muze byt bud nejaky parametr ovladace, nebo nadefinovat v xorg.conf aspon nejaky mode kompletni, neco jako:
Section "Monitor"
Identifier "Monitor0"
ModelName "Iiyama MA201D, VisionMaster Pro 511"
VendorName "Monitor Vendor"
HorizSync 30.0 - 110.0
VertRefresh 50.0 - 180.0
Option "dpms"
# ModeLine "1280x1024" 181.8 1280 1320 1448 1748 1024 1031 1046 1088 -hsync -vsync
# ModeLine "1400x1050" 198.0 1400 1464 1784 1912 1050 1052 1064 1090
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Modes "1400x1050" "1152x864" "1024x768" "800x600" "640x480"
Viewport 0 0
Depth 24
EndSubSection
EndSection
ModeLine by teoreticky pro LCD nemusel byt potreba. Podivej se do vypisu Xorg.0.log zda se pres grafickou kartu podari z monitoru vycist informace o podporovanych modech (hledej EDID a DDC).
Ahoj, ještě jednou díky, ale stále bez úspěchu. Zkusil jsem tento xorg conf a Xorg hlásí stále stejnou chybu.
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib64/xorg/modules"
FontPath "catalogue:/etc/X11/fontpath.d"
FontPath "built-ins"
EndSection
Section "Module"
Load "vnc"
Load "dri"
Load "dbe"
Load "extmod"
Load "glx"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "IQT"
ModelName "L17T"
DisplaySize 337 270
HorizSync 31.0 - 80.0
VertRefresh 56.0 - 75.0
Option "DPMS"
ModeLine "1280x1024" 181.8 1280 1320 1448 1748 1024 1031 1046 1088 -hsync -vsync
EndSection
Section "Device"
Identifier "Card0"
Driver "radeonhd"
VendorName "ATI Technologies Inc"
BoardName "Mobility Radeon HD 3600 Series"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Modes "1200x1024"
Viewport 0 0
Depth 24
EndSubSection
EndSection
grep EDID Xorg.0.log
(II) RADEONHD(0): EDID for output DVI-I_1/digital
(II) RADEONHD(0): EDID for output DVI-I_1/analog
(II) RADEONHD(0): EDID for output TV_7PIN_DIN
(II) RADEONHD(0): EDID for output DVI-I_2/digital
(II) RADEONHD(0): I2C device "RHD I2C line 0:E-EDID segment register" registered at address 0x60.
(II) RADEONHD(0): EDID data for L17T
(II) RADEONHD(0): EDID Version: 1.3
(II) RADEONHD(0): EDID (in hex):
(II) RADEONHD(0): EDID for output DVI-I_2/analog
(II) RADEONHD(0): EDID Version: 1.3
(II) RADEONHD(0): EDID (in hex):
grep DDC Xorg.0.log
(II) RADEONHD(0): Connector[0] {RHD_CONNECTOR_DVI_SINGLE, "HDMI_TYPE_A DFP1 CRT2", RHD_DDC_1, RHD_HPD_0, { RHD_OUTPUT_UNIPHYA, RHD_OUTPUT_DACB } }
(II) RADEONHD(0): Connector[1] {RHD_CONNECTOR_TV, "7PIN_DIN TV1 CV", RHD_DDC_0,RHD_HPD_NONE, { RHD_OUTPUT_DACB, RHD_OUTPUT_NONE } }
(II) RADEONHD(0): Connector[2] {RHD_CONNECTOR_DVI, "DUAL_LINK_DVI_I CRT1 DFP2",RHD_DDC_0, RHD_HPD_1, { RHD_OUTPUT_KLDSKP_LVTMA, RHD_OUTPUT_DACA } }
Kdyz nic jineho tak mas spatne definovany mod:
Modes “1200x1024” => Modes “1280x1024”
Zkousel si pouzit i jine konektory k pripojeni monitoru?
Ahoj, dík za postřeh, opravdu jsem tam měl chybu a po opravě už xserver naběhl. Sláva! Děkuju za pomoc.
Nicméně, přestože glxinfo vypíš direct rendering: yes, nejdou zapnout efekty v KDE4. Ne že bych o ně stál, ale chtěl jsem nějak zkusit, co z toho radeonhd driveru vymáčknu. Neznáš náhodou nějaký dobrý prográmek pro škálování grafické karty?
Ještě úvaha, myslíš, že s tímto funkčním xorg.conf (definovaný monitor a display mode), bych mohl rozjet i driver fglrx?
Pokud pouzivas radeonhd, tak je podle me jedna o softwarovou emulaci akcelerace. xorg.conf si zazalohuj, nainstaluj fglrx a uvidis…
Kdyztak ho zase odinstaluj a vrat config.
Zkusil jsem akmod s timhle xorg conf
# Xorg configuration created by livna-config-display
Section "ServerLayout"
Identifier "blabla"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib64/xorg/modules/extensions/fglrx"
ModulePath "/usr/lib64/xorg/modules"
EndSection
Section "ServerFlags"
Option "AIGLX" "on"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "us, cz_qwerty"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "IQT"
ModelName "L17T"
DisplaySize 337 270
HorizSync 31.0 - 80.0
VertRefresh 56.0 - 75.0
Option "DPMS"
ModeLine "1280x1024" 181.8 1280 1320 1448 1748 1024 1031 1046 1088 -hsync -vsync
EndSection
Section "Device"
Identifier "ATI"
Driver "fglrx"
Option "OpenGLOverlay" "off"
Option "VideoOverlay" "on"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "ATI"
Monitor "Monitor0"
SubSection "Display"
Modes "1280x1024"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "Extensions"
Option "Composite" "Enable"
EndSection
Section "DRI"
Mode 0666
EndSection
… a nefunguje.
grep EE Xorg.0.log
(EE) fglrx(0): Given depth (8) is not supported by fglrx driver
(EE) fglrx(0): PreInitVisual failed
(EE) fglrx(0): PreInit failed
(EE) Screen(s) found, but none have a usable configuration.
To vypadá, jak by nastavoval 8 bitové barvy ?!
Kdyby sis do konfigu pripsal DefaultDepth tak jak to je v mem prikladu o par prispevku vys, treba by to fungovalo.
Tak jsem nějakou dobu experimentoval s originálním driverem od ATI i s modulem kmod. Bez úspěchu. přes hlášku v logu ‘AIGLX: 3D driver claims to not support visual…’ nejede vlak. Asi mám holt smůlu, budu hledat jiné řešení. Ještě jednou díky za pomoc.