porque vc nao usa o "sorgsetup" que é muito mais fácil ?!!? se loga no terminal como root e roda ele.
Lembre-se de escolher as configurações mais básicas... por exemplo: video -> VESA mcskiller wrote: > Ola, Ananias. Removendo o xorg.conf da uma tela preta com um cursor > parado no canto superior esquerdo da tela. > Consegui uma copia do xorg.conf. Vou colar a partir de onde esta > descomentado. > > Section "ServerLayout" > > # The Identifier line must be present > # Each Screen line specifies a Screen section name, and optionally > # the relative position of other screens. The four names after > # primary screen name are the screens to the top, bottom, left and > right > # of the primary screen. In this example, screen 2 is located to the > # right of screen 1. > # Each InputDevice line specifies an InputDevice section name and > # optionally some options to specify the way the device is to be > # used. Those options include "CorePointer", "CoreKeyboard" and > # "SendCoreEvents". > Identifier "Simple Layout" > Screen 0 "aticonfig-Screen[0]-0" 0 0 > InputDevice "Mouse1" "CorePointer" > InputDevice "Keyboard1" "CoreKeyboard" > EndSection > > Section "Files" > > # The location of the RGB database. Note, this is the name of the > # file minus the extension (like ".txt" or ".db"). There is normally > # no need to change the default. > # Multiple FontPath entries are allowed (which are concatenated > together), > # as well as specifying multiple comma-separated entries in one > FontPath > # command (or a combination of both methods) > # > # If you don't have a floating point coprocessor and emacs, Mosaic or > other > # programs take long to start up, try moving the Type1 and Speedo > directory > # to the end of this list (or comment them out). > # > # ModulePath can be used to set a search path for the X server > modules. > # The default path is shown here. > ModulePath "/usr/lib/xorg/modules" > # RgbPath "/usr/share/X11/rgb" > FontPath "/usr/share/fonts/local/" > FontPath "/usr/share/fonts/misc/" > FontPath "/usr/share/fonts/OTF/" > FontPath "/usr/share/fonts/TTF/" > FontPath "/usr/share/fonts/Type1/" > FontPath "/usr/share/fonts/CID/" > FontPath "/usr/share/fonts/Speedo/" > FontPath "/usr/share/fonts/75dpi/:unscaled" > FontPath "/usr/share/fonts/100dpi/:unscaled" > FontPath "/usr/share/fonts/75dpi/" > FontPath "/usr/share/fonts/100dpi/" > FontPath "/usr/share/fonts/cyrillic/" > EndSection > > Section "Module" > > # This loads the DBE extension module. > # This loads the miscellaneous extensions module, and disables > # initialisation of the XFree86-DGA extension within that module. > # This loads the font modules > # This loads the GLX module > # Load "type1" > # Load "freetype" > #Load "speedo" > Load "dbe" # Double buffer extension > SubSection "extmod" > Option "omit xfree86-dga" # don't initialise the DGA > extension > EndSubSection > Load "glx" > EndSection > > Section "ServerFlags" > Option "Xinerama" "off" > EndSection > > Section "InputDevice" > > # For most OSs the protocol can be omitted (it defaults to > "Standard"). > # When using XQUEUE (only for SVR3 and SVR4, but not Solaris), > # uncomment the following line. > # Option "Protocol" "Xqueue" > # Set the keyboard auto repeat parameters. Not all platforms > implement > # this. > # Option "AutoRepeat" "500 5" > # Specifiy which keyboard LEDs can be user-controlled (eg, with > xset(1)). > # Option "Xleds" "1 2 3" > # To disable the XKEYBOARD extension, uncomment XkbDisable. > # Option "XkbDisable" > # To customise the XKB settings to suit your keyboard, modify the > # lines below (which are the defaults). For example, for a European > # keyboard, you will probably want to use one of: > # > # Option "XkbModel" "pc102" > # Option "XkbModel" "pc105" > # > # If you have a Microsoft Natural keyboard, you can use: > # > # Option "XkbModel" "microsoft" > # > # If you have a US "windows" keyboard you will want: > # > # Option "XkbModel" "pc104" > # > # Then to change the language, change the Layout setting. > # For example, a german layout can be obtained with: > # > # Option "XkbLayout" "de" > # > # or: > # > # Option "XkbLayout" "de" > # Option "XkbVariant" "nodeadkeys" > # > # If you'd like to switch the positions of your capslock and > # control keys, use: > # > # Option "XkbOptions" "ctrl:swapcaps" > # These are the default XKB settings for X.Org > # > # Option "XkbRules" "xorg" > # Option "XkbModel" "pc105" > # Option "XkbLayout" "us" > # Option "XkbVariant" "" > # Option "XkbOptions" "" > Identifier "Keyboard1" > Driver "kbd" > EndSection > > Section "InputDevice" > > # Identifier and driver > # On platforms where PnP mouse detection is supported the following > # protocol setting can be used when using a newer PnP mouse: > # Option "Protocol" "Auto" > # The available mouse protocols types that you can set below are: > # Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2 > # Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2 > # MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse > # ThinkingMouse ThinkingMousePS/2 Xqueue > # which is usually a symbolic link to the real device. > # Option "Device" "/dev/ttyS0" > # Option "Device" "/dev/ttyS1" > # When using XQUEUE, comment out the above two lines, and uncomment > # the following line. > # Option "Protocol" "Xqueue" > # Baudrate and SampleRate are only for some Logitech mice. In > # almost every case these lines should be omitted. > # Option "BaudRate" "9600" > # Option "SampleRate" "150" > # Emulate3Buttons is an option for 2-button Microsoft mice > # Emulate3Timeout is the timeout in milliseconds (default is 50ms) > # Option "Emulate3Buttons" > # Option "Emulate3Timeout" "50" > # ChordMiddle is an option for some 3-button Logitech mice > # Option "ChordMiddle" > Identifier "Mouse1" > Driver "mouse" > Option "Protocol" "IMPS/2" > # The mouse device. The device is normally set to /dev/mouse, > Option "Device" "/dev/mouse" > # Option "Device" "/dev/psaux" > EndSection > > Section "Monitor" > > # HorizSync is in kHz unless units are specified. > # HorizSync may be a comma separated list of discrete values, or a > # comma separated list of ranges of values. > # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S > # USER MANUAL FOR THE CORRECT NUMBERS. > # HorizSync 30-64 # multisync > # HorizSync 31.5, 35.2 # multiple fixed sync frequencies > # HorizSync 15-25, 30-50 # multiple ranges of sync frequencies > # VertRefresh is in Hz unless units are specified. > # VertRefresh may be a comma separated list of discrete values, or a > # comma separated list of ranges of values. > # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S > # USER MANUAL FOR THE CORRECT NUMBERS. > Identifier "My Monitor" > HorizSync 31.5 - 50.0 > VertRefresh 40.0 - 90.0 > EndSection > > Section "Monitor" > Identifier "aticonfig-Monitor[0]-0" > Option "VendorName" "ATI Proprietary Driver" > Option "ModelName" "Generic Autodetecting Monitor" > Option "DPMS" "true" > EndSection > > Section "Device" > > #VideoRam 4096 > # Insert Clocks lines here if appropriate > Identifier "VESA Framebuffer" > Driver "vesa" > EndSection > > Section "Device" > Identifier "aticonfig-Device[0]-0" > Driver "fglrx" > BusID "PCI:1:5:0" > EndSection > > Section "Screen" > > # If your card can handle it, a higher default color depth (like 24 or > 32) > # is highly recommended. > # DefaultDepth 8 > # DefaultDepth 16 > # DefaultDepth 32 > # "1024x768" is also a conservative usable default resolution. If you > # have a better monitor, feel free to try resolutions such as > # "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever > your > # card/monitor can produce) > Identifier "Screen 1" > Device "VESA Framebuffer" > Monitor "My Monitor" > DefaultDepth 24 > SubSection "Display" > Depth 8 > Modes "1024x768" "800x600" "640x480" > EndSubSection > SubSection "Display" > Depth 16 > Modes "1024x768" "800x600" "640x480" > EndSubSection > SubSection "Display" > Depth 24 > Modes "1024x768" "800x600" "640x480" > EndSubSection > SubSection "Display" > Depth 32 > Modes "1024x768" "800x600" "640x480" > EndSubSection > EndSection > > Section "Screen" > Identifier "aticonfig-Screen[0]-0" > Device "aticonfig-Device[0]-0" > Monitor "aticonfig-Monitor[0]-0" > DefaultDepth 24 > SubSection "Display" > Viewport 0 0 > Depth 24 > EndSubSection > EndSection > > On 1 mar, 16:51, Ananias Filho <[email protected]> wrote: > >> olha so >> remove o xorg.conf e tenta iniciar o X >> ele vai usar uma configuracao generica desabilitando tudo que for possível. >> ai ve se rola >> >> 2010/3/1 mcskiller <[email protected]> >> >> >> >> >>> Ola, entendi, mas no meu xorg.conf nao tem nenhum modulo dri nem ABI, >>> to vendo um jeito de postar o xorg.conf aqui. >>> >>> On 1 mar, 16:25, Ananias Filho <[email protected]> wrote: >>> >>>> Então >>>> onde houver esses erros *(EE)* >>>> remove a entrada no xorg.conf >>>> ex. >>>> dri (remove ou comenta) >>>> entendeu? >>>> 2010/3/1 mcskiller <[email protected]> >>>> >>>>> Ola, Ananias, eu ja havia feito isso, fiz agora de novo, mas nao deu >>>>> certo, o x nao sobe. >>>>> Um parte do retorno é essa: >>>>> >>>>> Log file: "/var/log/Xorg.0.log" >>>>> Using config file: "/etc/X11/xorg.conf" >>>>> Parse error on line 165 of section Files in file /etc/X11/xorg.conf >>>>> Ignoring obsolete keyword "RgbPath". >>>>> (EE) module ABI major version (0) doesn't match the server's version >>>>> (2) >>>>> (EE) Failed to load module "dri" (module requirement mismatch, 0) >>>>> >>>>> waiting for X server to shut down error setting MTRR (base = >>>>> 0xc0000000, size = 0x01000000, type = 1) Invalid argument (22) >>>>> >>>>> On 1 mar, 15:48, Ananias Filho <[email protected]> wrote: >>>>> >>>>>> Era o que eu suspeitava >>>>>> >>>>>> Só por questão de praticidade pra voce, >>>>>> edita o xorg.conf e altera o driver fglrx por vesa >>>>>> reinicia o X >>>>>> e usa a interface grafica rabuja >>>>>> entra no site da ati >>>>>> baixa o driver mais novo e reinstala >>>>>> >>>>>> qq coisa manda as ordens >>>>>> >>>>>> 2010/3/1 mcskiller <[email protected]> >>>>>> >>>>>>> Nao vou conseguir postar o arquivo nem a saida do comando, Alisson. >>>>>>> Estou acessando o grupo de um rwindows velho de um desktop aqui em >>>>>>> casa e o slack ta no note. Da pra pegar pelo pendrive, mas eu nao >>>>>>> >>> me >>> >>>>>>> lembro como faz pelo terminal. >>>>>>> >>>>>>> Pois é, Molinero, atualizei para o 13. Tanto que o >>>>>>> >>> slackware-version >>> >>>>>>> no etc mudou para 13.0, mas o kernel permaneceu 2.6.27.7 e eu nem >>>>>>> tinha reparado. >>>>>>> >>>>>>> Eu usei o comando slapt-get --dist-upgrade o no meu slapt-getrc eu >>>>>>> coloquei o ftp.slackwarecom, mirror.etf.bg.ac.yu e o >>>>>>> darkstar.ist.utl.pt todos apontando pro diretorio slackware-13.0 >>>>>>> >>>>>>> On 1 mar, 15:01, Molinero <[email protected]> wrote: >>>>>>> >>>>>>>> Perae... >>>>>>>> >>>>>>>> Se vc atualizou para o Slackware 13... ent o est carregando o m >>>>>>>> >>> dulo >>> >>>>>>>> do kernel errado. >>>>>>>> >>>>>>>> FATAL: Error inserting fglrx (/lib/modules/2.6.27.7-smp/external/ >>>>>>>> fglrx.ko.gz): Unknown symbol in module, or unknown parameter (see >>>>>>>> dmesg) >>>>>>>> >>>>>>>> O kernel padr o do Slackware 13 o 2.6.29.6 >>>>>>>> >>>>>>>> Quais os comandos do slapt-get voc usou para atualizar?!?! E como >>>>>>>> >>> est >>> >>>>>>>> o seu /etc/slapt-get/slapt-getrc ? >>>>>>>> >>>>>>>> mcskiller wrote: >>>>>>>> >>>>>>>>> Ola, max. Movi o xorg.conf como vc disse e rodei o comando X - >>>>>>>>> configure, mas ficou uma tela escura com um cursor para do lado >>>>>>>>> esquerdo no canto superior. Reiniciei e executei o comando que >>>>>>>>> >>> o >>> >>>>>>>>> Ananias falou, modproble e a saida foi essa: >>>>>>>>> >>>>>>>>> FATAL: Error inserting fglrx >>>>>>>>> >>> (/lib/modules/2.6.27.7-smp/external/ >>> >>>>>>>>> fglrx.ko.gz): Unknown symbol in module, or unknown parameter >>>>>>>>> >>> (see >>> >>>>>>>>> dmesg) >>>>>>>>> >>>>>>>>> Rodei o dmesg e como ele quilometrico, coloquei so as ultimas >>>>>>>>> linhas: >>>>>>>>> >>>>>>>>> fglrx: Unknown symbol pci_disable_msi >>>>>>>>> fglrx: Unknown symbol pci_enable_msi >>>>>>>>> >>>>>>>>> As ultimas linhas do /var/log/messages: >>>>>>>>> >>>>>>>>> Mar 1 13:40:59 pimentinha /usr/sbin/gpm[3034]: *** info >>>>>>>>> [client.c(137)]: >>>>>>>>> Mar 1 13:40:59 pimentinha /usr/sbin/gpm[3034]: Connecting at fd >>>>>>>>> >>> 7 >>> >>>>>>>>> Mar 1 13:43:49 pimentinha /usr/sbin/gpm[3034]: *** info >>>>>>>>> [client.c(275)]: >>>>>>>>> Mar 1 13:43:49 pimentinha /usr/sbin/gpm[3034]: Request on 7 >>>>>>>>> >>>>> (console >>>>> >>>>>>>>> 2) >>>>>>>>> Mar 1 13:43:49 pimentinha /usr/sbin/gpm[3034]: *** info >>>>>>>>> [client.c(284)]: >>>>>>>>> Mar 1 13:43:49 pimentinha /usr/sbin/gpm[3034]: Closing >>>>>>>>> Mar 1 13:44:45 pimentinha /usr/sbin/gpm[3034]: *** info >>>>>>>>> [client.c(275)]: >>>>>>>>> Mar 1 13:44:45 pimentinha /usr/sbin/gpm[3034]: Request on 6 >>>>>>>>> >>>>> (console >>>>> >>>>>>>>> 1) >>>>>>>>> Mar 1 13:44:45 pimentinha /usr/sbin/gpm[3034]: *** info >>>>>>>>> [client.c(284)]: >>>>>>>>> Mar 1 13:44:45 pimentinha /usr/sbin/gpm[3034]: Closing >>>>>>>>> >>>>>>>>> On 1 mar, 11:29, Ananias Filho <[email protected]> wrote: >>>>>>>>> >>>>>>>>>> Olha s >>>>>>>>>> o driver pode estar l por m o log ai diz que n o pode ser >>>>>>>>>> >>>>> carregado o >>>>> >>>>>>>>>> driver. >>>>>>>>>> Loader Failed, 7 >>>>>>>>>> >>>>>>>>>> tenta isso aqui >>>>>>>>>> modprobe fglrx >>>>>>>>>> >>>>>>>>>> verifica se da erro e depois tenta >>>>>>>>>> >>>>>>>>>> tail /var/log/messages >>>>>>>>>> >>>>>>>>>> se deu erro ao subir o fglrx, manda pra gente a sainda do tail >>>>>>>>>> >>>>>>>>>> 2010/3/1 mcskiller <[email protected]> >>>>>>>>>> >>>>>>>>>>> Ola, max, vou fazer o que vc disse. >>>>>>>>>>> >>>>>>>>>>> Eu olhei o /var/log/Xorg.0.log e tinha entre outras coisas, >>>>>>>>>>> >>> isso >>> >>>>> aki: >>>>> >>>>>>>>>>> (EE)Faleid to load /usr/lib/xorg/modules/drivers/fglrx_drv.so >>>>>>>>>>> (EE)Faleid to load module "fglrx" (loader failed, 7) >>>>>>>>>>> (EE)No drivers available >>>>>>>>>>> Fatal server error: no screens found >>>>>>>>>>> xinit: No such file or directory (errno 2): unable to connect >>>>>>>>>>> >>> to >>> >>>>> x >>>>> >>>>>>>>>>> server. >>>>>>>>>>> xinit: No such process (errno3): unexpected signal 2. >>>>>>>>>>> >>>>>>>>>>> Mas o driver fglrx ta bonitinho la no diretorio, nao sei pq >>>>>>>>>>> >>> nao >>> >>>>> esta >>>>> >>>>>>>>>>> carregando. >>>>>>>>>>> >>>>>>>>>>> On 1 mar, 09:48, max <[email protected]> wrote: >>>>>>>>>>> >>>>>>>>>>>> 2010/3/1 Mariane Cardoso <[email protected]>: >>>>>>>>>>>> >>>>>>>>>>>>> Ola, pessoal. Eu acredito que talvez isso ja tenha sido >>>>>>>>>>>>> >>> postado >>> >>>>>>> aqui >>>>>>> >>>>>>>>>>>>> no grupo, mas estou meio impossibitada de procurar, pois >>>>>>>>>>>>> >>> estou >>> >>>>>>>>>>>>> navegando usando o links. >>>>>>>>>>>>> Atualizei meu slack pelo slapt-get para 13 e quando >>>>>>>>>>>>> >>> reiniciei >>> >>>>> meu >>>>> >>>>>>>>>>>>> computador cade o X... >>>>>>>>>>>>> A versao do x server eh 1.6.3 e o final do que o comando >>>>>>>>>>>>> >>> startx >>> >>>>>>> retorna >>>>>>> >>>>>>>>>>> eh esse: >>>>>>>>>>> >>>>>>>>>>>>> Fatal server error: no screens found >>>>>>>>>>>>> xinit: No such file or directory (errno 2): unable to >>>>>>>>>>>>> >>> connect >>> >>>>> to x >>>>> >>>>>>>>>>> server. >>>>>>>>>>> >>>>>>>>>>>>> xinit: No such process (errno3): unexpected signal 2. >>>>>>>>>>>>> >>>>>>>>>>>>> Nao consegui anexar o meu xorg pelo links, mas se alguem >>>>>>>>>>>>> >>> tiver >>> >>>>> uma >>>>> >>>>>>>>>>>>> luz. Nao sou mto conhecedora de configuracao de x. >>>>>>>>>>>>> >>>>>>>>>>>>> Obrigada, >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Mari >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> GUS-BR - Grupo de Usu rios de Slackware Brasil >>>>>>>>>>>>> http://www.slackwarebrasil.org/ >>>>>>>>>>>>> http://groups.google.com/group/slack-users-br >>>>>>>>>>>>> >>>>>>>>>>>>> Antes de perguntar: >>>>>>>>>>>>> http://www.istf.com.br/perguntas/ >>>>>>>>>>>>> >>>>>>>>>>>>> Para sair da lista envie um e-mail para: >>>>>>>>>>>>> [email protected]<slack-users-br%2bunsubscr...@go >>>>>>>>>>>>> oglegroups.com> >>>>>>>>>>>>> >>> <slack-users-br%2bunsubscr...@go oglegroups.com> >>> >>>>> <slack-users-br%2bunsubscr...@go oglegroups.com> >>>>> >>>>>>> <slack-users-br%2bunsubscr...@go oglegroups.com> >>>>>>> >>>>>>>>>>>> Move o /etc/X11/xorg.conf para algum lugar e roda o comando >>>>>>>>>>>> >>> X >>> >>>>>>>>>>>> -configure, que vai gerar o arquivo /root/xorg.conf.new. >>>>>>>>>>>> >>> Move >>> >>>>> este >>>>> >>>>>>>>>>>> novo arquivo para /etc/X11/xorg.conf e tu tem as configura >>>>>>>>>>>> >>> es b >>> >>>>>>> sicas >>>>>>> >>>>>>>>>>>> do X, depois disso tu pode ver com mais detalhes o que >>>>>>>>>>>> >>> aconteceu >>> >>>>> de >>>>> >>>>>>>>>>>> errado. >>>>>>>>>>>> >>>>>>>>>>>> Ou olha no /var/log/Xorg.0.log nas linhas com (EE). >>>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> GUS-BR - Grupo de Usu rios de Slackware Brasil >>>>>>>>>>> http://www.slackwarebrasil.org/ >>>>>>>>>>> http://groups.google.com/group/slack-users-br >>>>>>>>>>> >>>>>>>>>>> Antes de perguntar: >>>>>>>>>>> http://www.istf.com.br/perguntas/ >>>>>>>>>>> >>>>>>>>>>> Para sair da lista envie um e-mail para: >>>>>>>>>>> [email protected]<slack-users-br%2bunsubscr...@go >>>>>>>>>>> oglegroups.com> >>>>>>>>>>> >>> <slack-users-br%2bunsubscr...@go oglegroups.com> >>> >>>>> <slack-users-br%2bunsubscr...@go oglegroups.com> >>>>> >>>>>>> <slack-users-br%2bunsubscr...@go oglegroups.com> >>>>>>> >>>>>>>>>> -- >>>>>>>>>> kram3r >>>>>>>>>> >>>>>>> -- >>>>>>> GUS-BR - Grupo de Usuários de Slackware Brasil >>>>>>> http://www.slackwarebrasil.org/ >>>>>>> http://groups.google.com/group/slack-users-br >>>>>>> >>>>>>> Antes de perguntar: >>>>>>> http://www.istf.com.br/perguntas/ >>>>>>> >>>>>>> Para sair da lista envie um e-mail para: >>>>>>> [email protected]<slack-users-br%2bunsubscr...@go >>>>>>> oglegroups.com> >>>>>>> >>> <slack-users-br%2bunsubscr...@go oglegroups.com> >>> >>>>> <slack-users-br%2bunsubscr...@go oglegroups.com> >>>>> >>>>>> -- >>>>>> kram3r >>>>>> >>>>> -- >>>>> GUS-BR - Grupo de Usuários de Slackware Brasil >>>>> http://www.slackwarebrasil.org/ >>>>> http://groups.google.com/group/slack-users-br >>>>> >>>>> Antes de perguntar: >>>>> http://www.istf.com.br/perguntas/ >>>>> >>>>> Para sair da lista envie um e-mail para: >>>>> [email protected]<slack-users-br%2bunsubscr...@go >>>>> oglegroups.com> >>>>> >>> <slack-users-br%2bunsubscr...@go oglegroups.com> >>> >>>> -- >>>> kram3r >>>> >>> -- >>> GUS-BR - Grupo de Usuários de Slackware Brasil >>> http://www.slackwarebrasil.org/ >>> http://groups.google.com/group/slack-users-br >>> >>> Antes de perguntar: >>> http://www.istf.com.br/perguntas/ >>> >>> Para sair da... >>> >> mais » >> > > -- GUS-BR - Grupo de Usuários de Slackware Brasil http://www.slackwarebrasil.org/ http://groups.google.com/group/slack-users-br Antes de perguntar: http://www.istf.com.br/perguntas/ Para sair da lista envie um e-mail para: [email protected]
