Начало Вход/Регистрация Помощ Tazi stranica s latinski bukwi
Области
 Новини
 Актуална тема
 Linux портали
 Какво е Линукс?
 Въпроси-отговори
 Форуми
   •Трудова борса
   •Конкурс
 Статии
 Дистрибуции
   •Поръчка на CD
 Made In BG
 Файлове
 Връзки
 Галерия
 Конференции
Настройки
 Външен вид
 Предложения
 Направи си сам
И още ...
 За нас
 Линукс за българи ЕООД
 Линк към нас
 Предложения

Подкрепяно от:
TelePoint - Място за хора със свободни идеи

SiteGround

initLab

Adsys Group

SAP Bulgaria

Въпроси отговори
Въпрос: startx problem
[Търси: ]

ВНИМАНИЕ: Използвайте форумите на сайта за дa зададете вашите въпроси.

Към началото |Добави въпрос |Отговори
 
Въпрос
От: Freeze Дата: 01/13/2005
kato pusna startx premigva v cherno ekrana i mi dava greshka  
No screens found. v xorg.conf vsichko izglejda da si e  nared... 
imashe edna komanda za konfigurirane na xfree86 s  menuta 
ama ne moga da se setia koia beshe. Ako niakoi mi  kaje kak 
da si opravia problema ili pone koia beshe  komandata, shtot si 
e*alo maikata. Sega primerno go pisha tova s links


Отговор #1
От: Грешка Дата: 01/13/2005
Охххх!
Почва да ми омръзва сериозно.
Freeze пиши на кирилица, бе човек. 
 Тва не ти е чат, изразявай се разумно и спокойно обясни
 какъв точно е проблема. Грешката която ти дава може да е
 придизвикана от 1001 причини - като почнеш модули и свършиш
с хардуерен проблем. Погледни /var/log/xcorg.log
Кажи каква ти е дистрибуцията, какво си правил.
Ей такива дребни неща.


Отговор #2
От: Freeze Дата: 01/13/2005
 _XSERVTransSocketOpenCOTSServer: Unable to open socket for
inet6
_XSERVTransOpen: transport open failed for inet6/Doomer:0
 _XSERVTransMakeAllCOTSServerListeners: failed to open
listener for inet6

X Window System Version 6.8.1
Release Date: 17 September 2004
X Protocol Version 11, Revision 0, Release 6.8.1
Build Operating System: Linux 2.4.27 i686 [ELF] 
 Current Operating System: Linux Doomer 2.4.26 #6 Mon Jun 14
19:07:27 PDT 2004 i686
Build Date: 18 October 2004
	Before reporting problems, check http://wiki.X.Org
	to make sure that you have the latest version.
Module Loader present
 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: Thu Jan 13
14:30:06 2005
(==) Using config file: "/etc/X11/xorg.conf"
 Parse error on line 480 of section ServerLayout in file
/etc/X11/xorg.conf
	"Driver" is not a valid keyword in this section.
(EE) Problem parsing the config file
(EE) Error parsing the config file

Fatal server error:
no screens found

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

 Преди малко писах на текстовия браузър, а там кирилизатор
няма. Ето лог.



Отговор #3
От: Грешка Дата: 01/13/2005
Е това е друга работа.
Ето я грешката:
""Driver" is not a valid keyword in this section."
Имаш грешен xorg.conf. Дай го насам да го видим.


Отговор #4
От: Freeze Дата: 01/13/2005
# File generated by xf86config.

#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
 # Permission is hereby granted, free of charge, to any
person obtaining a
 # copy of this software and associated documentation files
(the "Software"),
 # to deal in the Software without restriction, including
without limitation
 # the rights to use, copy, modify, merge, publish,
distribute, sublicense,
 # and/or sell copies of the Software, and to permit persons
to whom the
 # Software is furnished to do so, subject to the following
conditions:
# 
 # The above copyright notice and this permission notice
shall be included in
# all copies or substantial portions of the Software.
# 
 # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
KIND, EXPRESS OR
 # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY,
 # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN
NO EVENT SHALL
 # THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY,
 # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF
 # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE
# SOFTWARE.
# 
 # Except as contained in this notice, the name of the
XFree86 Project shall
 # not be used in advertising or otherwise to promote the
sale, use or other
 # dealings in this Software without prior written
authorization from the
# XFree86 Project.
#

 #
**********************************************************************
 # Refer to the XF86Config(4/5) man page for details about
the format of 
# this file.
 #
**********************************************************************

 # NOTE:  This is a NEW IMPROVED version of XF86Config-fbdev
that uses the vesa
 # driver instead of the fbdev driver.  Thanks to Kenneth
Fanyo who pointed
# this out to me. :)

 # This XF86Config file is designed for use with the VESA
framebuffer.
 # This generic interface should work with nearly all video
cards
# (although not every card will support every resolution).

 # With the new driver, it should no longer be required to
have frame buffer
# support in the kernel, or to run it on the console.
#
# Enjoy! :)
# -- volkerdi@slackware.com
#

 #
**********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
 #
**********************************************************************
#
Section "Module"

# This loads the DBE extension module.

    Load        "dbe"  	# Double buffer extension

 # This loads the miscellaneous extensions module, and
disables
 # initialisation of the XFree86-DGA extension within that
module.
    SubSection  "extmod"
       Option    "omit xfree86-dga"   # don't initialise the
DGA extension
    EndSubSection

# This loads the font modules
    Load        "type1"
    Load        "freetype"
    Load        "speedo"

# This loads the GLX module
    Load       "glx"

EndSection

 #
**********************************************************************
 # Files section.  This allows default font and rgb paths to
be set
 #
**********************************************************************

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.

    RgbPath	"/usr/X11R6/lib/X11/rgb"

 # 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).
# 

    FontPath   "/usr/X11R6/lib/X11/fonts/local/"
    FontPath   "/usr/X11R6/lib/X11/fonts/misc/"
    FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
    FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
    FontPath   "/usr/X11R6/lib/X11/fonts/Type1/"
    FontPath   "/usr/X11R6/lib/X11/fonts/CID/"
    FontPath   "/usr/X11R6/lib/X11/fonts/Speedo/"
    FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/"
    FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/"
    FontPath   "/usr/X11R6/lib/X11/fonts/cyrillic/"

 # ModulePath can be used to set a search path for the X
server modules.
# The default path is shown here.

#    ModulePath "/usr/X11R6/lib/modules"

EndSection

 #
**********************************************************************
# Server flags section.
 #
**********************************************************************

Section "ServerFlags"

 # Uncomment this to cause a core dump at the spot where a
signal is
 # received.  This may leave the console in an unusable
state, but may
 # provide a better stack trace in the core dump to aid in
debugging

#    Option     "NoTrapSignals"

 # Uncomment this to disable the  VT switch
sequence
 # (where n is 1 through 12).  This allows clients to receive
these key
# events.

#    Option     "DontVTSwitch"

 # Uncomment this to disable the  server abort
sequence
# This allows clients to receive this key event.

#    Option     "DontZap"

 # Uncomment this to disable the /
mode switching
 # sequences.  This allows clients to receive these key
events.

#    Option     "DontZoom"

 # Uncomment this to disable tuning with the xvidtune client.
With
 # it the client can still run and fetch card and monitor
attributes,
 # but it will not be allowed to change them. If it tries it
will
# receive a protocol error.

#    Option     "DisableVidModeExtension"

 # Uncomment this to enable the use of a non-local xvidtune
client.

#    Option     "AllowNonLocalXvidtune"

 # Uncomment this to disable dynamically modifying the input
device
# (mouse and keyboard) settings.

#    Option     "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
 # change the keyboard or mouse settings (currently only
xset).

#    Option     "AllowNonLocalModInDev"

# Set the basic blanking screen saver timeout.

#    Option      "blank time"    "10"    # 10 minutes

 # Set the DPMS timeouts.  These are set here because they
are global
 # rather than screen-specific.  These settings alone don't
enable DPMS.
 # It is enabled per-screen (or per-monitor), and even then
only when
# the driver supports it.

#    Option      "standby time"  "20"
#    Option      "suspend time"  "30"
#    Option      "off time"      "60"

 # On some platform the server needs to estimate the sizes of
PCI
 # memory and pio ranges. This is done by assuming that PCI
ranges
 # don't overlap. Some broken BIOSes tend to set ranges of
inactive
 # devices wrong. Here one can adjust how aggressive the
assumptions
# should be. Default is 0.

# Option   "EstimateSizesAggresively" "0"

EndSection

 #
**********************************************************************
# Input devices
 #
**********************************************************************

 #
**********************************************************************
# Core keyboard's InputDevice section
 #
**********************************************************************

Section "InputDevice"

    Identifier	"Keyboard1"
    Driver	"Keyboard"
 # 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"      "pc101"
#    Option     "XkbLayout"     "us"
#    Option     "XkbVariant"    ""
#    Option     "XkbOptions"    ""

EndSection


 #
**********************************************************************
# Core Pointer's InputDevice section
 #
**********************************************************************

Section "InputDevice"

# Identifier and driver

    Identifier	"Mouse1"
    Driver	"mouse"

 # 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
    Option "Protocol"    "PS/2"

 # The mouse device.  The device is normally set to
/dev/mouse,
# which is usually a symbolic link to the real device.

    Option "Device"      "/dev/mouse"
#   Option "Device"      "/dev/psaux"
#   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"

EndSection

# Some examples of extended input devices

# Section "InputDevice"
#    Identifier "spaceball"
#    Driver     "magellan"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball2"
#    Driver     "spaceorb"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen0"
#    Driver     "microtouch"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "1412"
#    Option     "MaxX"          "15184"
#    Option     "MinY"          "15372"
#    Option     "MaxY"          "1230"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen1"
#    Driver     "elo2300"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "231"
#    Option     "MaxX"          "3868"
#    Option     "MinY"          "3858"
#    Option     "MaxY"          "272"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonThreshold"       "17"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection

 #
**********************************************************************
# Monitor section
 #
**********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

    Identifier  "My 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   31.5 - 50.0

#    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.

    VertRefresh 40-90

EndSection


 #
**********************************************************************
# Graphics device section
 #
**********************************************************************

# Any number of graphics device sections may be present

Section "Device"
    Identifier  "VESA Framebuffer"
    Driver      "vesa"
    #VideoRam    4096
    # Insert Clocks lines here if appropriate
EndSection

 #
**********************************************************************
# Screen sections
 #
**********************************************************************

 # Any number of screen sections may be present.  Each
describes
 # the configuration of a single screen.  A single specific
screen section
 # may be specified from the X server command line with the
"-screen"
# option.
Section "Screen"
    Identifier  "Screen 1"
    Device      "VESA Framebuffer"
    Monitor     "My Monitor"

 # If your card can handle it, a higher default color depth
(like 24 or 32)
# is highly recommended.

#   DefaultDepth 8
#   DefaultDepth 16
    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)

    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

 #
**********************************************************************
# ServerLayout sections.
 #
**********************************************************************

 # Any number of ServerLayout sections may be present.  Each
describes
 # the way multiple screens are organised.  A specific
ServerLayout
 # section may be specified from the X server command line
with the
 # "-layout" option.  In the absence of this, the first
section is used.
 # When now ServerLayout section is present, the first Screen
section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
    Identifier  "Simple Layout"

 # 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.

    Screen "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".

 
#  Driver       "Keyboard"  
  Driver       "kbd"
   InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection




Отговор #5
От: Грешка Дата: 01/13/2005
Коментирай реда:
Driver       "kbd"
т.е. 
# Driver       "kbd"
и да видим какво ще стане!



Отговор #6
От: Freeze Дата: 01/13/2005
Znachi komentirah go sega dava  (EE)Failed to to load module 
"Keyboard" (module does not exist, 0) (EE)No Input driver 
matching 'Keyboard' No core keyboard Fatal server error: failed 
to initialize core devices.  Ako niakoi mi kaje kak se kopira ot 
konzola... shtot se izmychih da go prepisha tova(da jivee links).


Отговор #7
От: Грешка Дата: 01/13/2005
Разкоментирай го тогава.
 Има някъде грешно използване на Driver, но сега няма време
да търся. Съжалявам. Утре пак.


Отговор #8
От: atan Дата: 01/13/2005
 Ето ти част от XFree86 config файл. Не е Xorg, но би ти
свършил работа.


 # XF86Config-4 (XFree86 X Window System server configuration
file)
#
 # This file was generated by dexconf, the Debian X
Configuration tool, using
# values from the debconf database.
#
 # Edit this file with caution, and see the XF86Config-4
manual page.
# (Type "man XF86Config-4" at the shell prompt.)
#
 # This file is automatically updated on xserver-xfree86
package upgrades *only*
 # if it has not been modified since the last upgrade of the
xserver-xfree86
# package.
#
 # If you have edited this file but would like it to be
automatically updated
# again, run the following commands as root:
#
#   cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom
 #   md5sum /etc/X11/XF86Config-4
>/var/lib/xfree86/XF86Config-4.md5sum
#   dpkg-reconfigure xserver-xfree86

Section "Files"
        FontPath        "/usr/X11R6/lib/X11/fonts/TrueType"
         FontPath        "unix/:7100"                    #
local font server
         # if the local font server has problems, we can fall
back on these
        FontPath        "/usr/lib/X11/fonts/misc"
        FontPath        "/usr/lib/X11/fonts/cyrillic"
         FontPath       
"/usr/lib/X11/fonts/100dpi/:unscaled"
         FontPath       
"/usr/lib/X11/fonts/75dpi/:unscaled"
        FontPath        "/usr/lib/X11/fonts/Type1"
        FontPath        "/usr/lib/X11/fonts/CID"
        FontPath        "/usr/lib/X11/fonts/Speedo"
        FontPath        "/usr/lib/X11/fonts/100dpi"
        FontPath        "/usr/lib/X11/fonts/75dpi"
EndSection

Section "Module"
        Load    "GLcore"
        Load    "bitmap"
        Load    "dbe"
        Load    "ddc"
        Load    "dri"
        Load    "extmod"
        Load    "freetype"
        Load    "glx"
        Load    "int10"
        Load    "record"
        Load    "speedo"
        Load    "type1"
        Load    "vbe"
EndSection

Section "InputDevice"
        Identifier      "Generic Keyboard"
        Driver          "keyboard"
        Option          "CoreKeyboard"
        Option          "XkbRules"      "xfree86"
        Option          "XkbModel"      "pc104"
        Option          "XkbLayout"     "us,bg"
        Option          "XkbVariant"    ",phonetic"
         Option          "XkbOptions"   
"grp:alt_shift_toggle,grp_led:scroll"
EndSection

Section "InputDevice"
        Identifier      "Configured Mouse"
        Driver          "mouse"
        Option          "CorePointer"
         Option          "Device"               
"/dev/psaux"
        Option          "Protocol"              "PS/2"
        Option          "Emulate3Buttons"       "true"
        Option          "ZAxisMapping"          "4 5"
EndSection
Section "InputDevice"
        Identifier      "Generic Mouse"
        Driver          "mouse"
        Option          "SendCoreEvents"        "true"
         Option          "Device"               
"/dev/input/mice"
        Option          "Protocol"              "ImPS/2"
        Option          "Emulate3Buttons"       "true"
        Option          "ZAxisMapping"          "4 5"
EndSection

Section "Device"
        Identifier      "GeForce2-Ti"
        Driver          "nv"
EndSection

Section "Monitor"
        Identifier      "PHILIPS 107E"
        HorizSync       30-85
        VertRefresh     50-85
        Option          "DPMS"
EndSection

Section "Screen"
        Identifier      "Default Screen"
        Device          "GeForce2-Ti"
        Monitor         "PHILIPS 107E"
        DefaultDepth    16
        SubSection "Display"
                Depth           1
                 Modes           "1024x768" "800x600"
"640x480"
        EndSubSection
        SubSection "Display"
                Depth           4
                 Modes           "1024x768" "800x600"
"640x480"
        EndSubSection
        SubSection "Display"
                Depth           8
                 Modes           "1024x768" "800x600"
"640x480"
        EndSubSection
        SubSection "Display"
                Depth           15
                 Modes           "1024x768" "800x600"
"640x480"
        EndSubSection
        SubSection "Display"
                Depth           16
                 Modes           "1024x768" "800x600"
"640x480"
        EndSubSection
        SubSection "Display"
                Depth           24
                 Modes           "1024x768" "800x600"
"640x480"
        EndSubSection
EndSection

Section "ServerLayout"
        Identifier      "Default Layout"
        Screen          "Default Screen"
        InputDevice     "Generic Keyboard"
        InputDevice     "Configured Mouse"
        InputDevice     "Generic Mouse"
EndSection

Section "DRI"
        Mode    0666
EndSection


Отговор #9
От: Fire_Ice Дата: 01/14/2005
 Freeze, а като използваш Framebuffer, компилирал ли си
ядрото за такава поддръжка, май не а???
 Проблема ти е в Graphics device section и Screen section.
 Искаш да използваш VESA Framebuffer, ама то и на ядрото
 трябва да му се каже това за да знае. А друг е въпроса защо
искаш да изпололзваш VESA Framebuffer.
 Ако съм ти помогнал с нещо се радвам, ако не си ме разбрал
 кво съм искал да кажа- питай, но според мен там ти е
 грижата- Искаш да използваш Framebuffer, а ядрото не е
компилирано с тая поддръжка.


Отговор #10
От: Грешка Дата: 01/14/2005
Само да добавя към Framebuffer-a.
 Section Screen е напълно разбъркана и този Driver "kbd" май
 не  му е там мястото.(прегледах и моята конфигурация - няма
 такова чудо като kbd) Освен това, втората грешка която ти
 даде след като коментира реда е неизвестен драйвър
 "Keyboard", според мен с секцията на клавиатурата трябва да
бъде:
Driver "keyboard"

 Не мога да си обясня защо са се получили толкова много
грешки - защо не опиташ наново да го конфигурираш? 
 Другия вариант е да боотнеш с LiveCD, да му копираш някъде
конфигурационния файл и да го използваш директно.


Отговор #11
От: Freeze Дата: 01/14/2005
 И как да разреша от ядрото??? И как да си компилирам ново
ядро. Четох статията, обаче ми дава, че няма такова нещо
като му дам
cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz
cp /src/linux/system.map /boot
 и ако може на една идея по-ниско ниво да обяснявате ще съм
 мнооого благодарен. Все пак още не съм мастър... (надали и
ще стана ;))



Отговор #12
От: Грешка Дата: 01/14/2005
 За компилирането никой не може да ти помогне освен самия
ти.
 В смисъл никой не може да те научи - възможните грешки са
 таолкова много, че ще трябва сам да си счупиш главата за да
ги научиш. 
 Има полезни материали, но ти ще трябва да установиш какъв ти
 е хардуера/софруера който ползваш и сам да си конфигурираш
ядрото.
Драмата не е голяма.
Успех!


Отговор #13
От: Fire_Ice Дата: 01/14/2005
 Абе я кажи каква ти е видеокартата и после вземи спомени кой
 ти е генерирал този файл или си го взел наготово от някъде.
 Коя е дистрибуцията, как си я инсталирал като на повечето
дистрибуции има конфигурация на видеото в инсталацията.
Тоя файл ми се струва парашутист.


Отговор #14
От: Freeze Дата: 01/14/2005
 Видеото е Saphire Radeon 9000 pro. Дистрибуциятра е слак
 10.0 файла сам се е генерирал. Никва видеокарта не е
споменавал при инсталиране.



Отговор #15
От: Fire_Ice Дата: 01/14/2005
http://www.slackware.com/config/x.php
Я влез като root и изпълни ей тва командченце:
xorgconfig
 Трябва да се появи едно такова и да те пита за разни неща,
 ти само му отговаряй правилно. Със Slackware съм се
 занимавал само 1 седмица, но принципа е еднакъв. Същата тази
 програма е трябвало да се запуска от инсталатора, поне така
си мисля.
 А с тази карта вземи забрави за framebuffer. Картата си е
съвременна.


<< Compilirane (1 ) | Oficial Linux support in BG (1 ) >>

 
© 2011-... Асоциация "Линукс за българи"
© 2007-2010 Линукс за българи ЕООД
© 1999-2006 Slavej Karadjov
Ако искате да препечатате или цитирате информация от този сайт прочетете първо това
Външния вид е направен от MOMCHE
Code Version: 1.0.8 H (Revision: 23-09-2011)
 
Изпълнението отне: 0 wallclock secs ( 0.08 usr + 0.00 sys = 0.08 CPU)