Help!

PC-Problemen?
De vrijwilligers van Oplossing.be zoeken gratis met u mee!

Hulp bij posten

Recente topics

Auteur Topic: Foutmelding bij opstarten XServer in Fedora Core 1 op Dell Optiplex GF270  (gelezen 1686 keer)

0 leden en 1 gast bekijken dit topic.

Offline AquariusJK

  • Volledig lid
  • **
  • Berichten: 128
Hey allemaal,

Ik heb een vraagje ivm RedHat 9 en Fedora Core 1. Het probleem bestaat blijkbaar in beide Linux versie's. Ik heb geprobeerd om beide besturingssystemen op een Dell Optiplex GF270 te installeren. Dat lijkt allemaal goed te lukken tot ik probeer om de XServer te starten. In eerste instantie crasht deze met de foutmelding dat er geen videomodes kunnen gevonden worden voor deze videokaart. Bij nader onderzoek blijkt dat RH en FC de driver voor i810 gebruiken terwijl het eigenlijk i830 moet zijn. Als ik dit dan ook aanpas start de XServer op, maar de resolutie blijft op 640x480. Het lukt niet om deze te wijzigen.

Via de site van intel heb ik de nieuwste drivers gedownload. Bij compilatie op RH krijg ik allerlei foutmeldingen. Op FC lukt compilatie perfect. Nadien start de XServer totaal niet meer op. Hieronder heb ik een kopietje geplakt van de foutmelding :
Module Loader present

OS Kernel: Linux version 2.4.22-1.2115.nptl (bhcompile@daffy.perf.redhat.com) (gcc version 3.2.3 20030422 (Red Hat Linux 3.2.3-6)) #1 Wed Oct 29 15:42:51 EST 2003

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/XFree86.0.log", Time: Tue Nov 18 08:27:21 2003

(==) Using config file: "/etc/X11/XF86Config"

(==) ServerLayout "single head configuration"

(**) |-->Screen "Screen0" (0)

(**) |   |-->Monitor "Monitor0"

(**) |   |-->Device "Videocard0"

(**) |-->Input Device "Mouse0"

(**) |-->Input Device "Keyboard0"

(**) Option "XkbRules" "xfree86"

(**) XKB: rules: "xfree86"

(**) Option "XkbModel" "pc105"

(**) XKB: model: "pc105"

(**) Option "XkbLayout" "be"

(**) XKB: layout: "be"

(==) Keyboard: CustomKeycode disabled

(**) |-->Input Device "DevInputMice"

(**) FontPath set to "unix/:7100"

(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"

(==) ModulePath set to "/usr/X11R6/lib/modules"

(++) using VT number 7



(II) Open APM successful

(II) Module ABI versions:

   XFree86 ANSI C Emulation: 0.2

   XFree86 Video Driver: 0.6

   XFree86 XInput driver : 0.4

   XFree86 Server Extension : 0.2

   XFree86 Font Renderer : 0.4

(II) Loader running on linux

(II) LoadModule: "bitmap"

(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a

(II) Module bitmap: vendor="The XFree86 Project"

   compiled for 4.3.0, module version = 1.0.0

   Module class: XFree86 Font Renderer

   ABI class: XFree86 Font Renderer, version 0.4

(II) Loading font Bitmap

(II) LoadModule: "pcidata"

(II) Loading /usr/X11R6/lib/modules/libpcidata.a

(II) Module pcidata: vendor="The XFree86 Project"

   compiled for 4.2.0, module version = 0.1.0

   ABI class: XFree86 Video Driver, version 0.5



   *** If unresolved symbols were reported above, they might not

   *** be the reason for the server aborting.



Fatal server error:

Caught signal 11.  Server aborting





If you encounter a server crash, please report the problem by filing a bug

report in the XFree86.org bugzilla at https://bugs.xfree86.org and/or Red Hat

bugzilla at https://bugzilla.redhat.com/bugzilla.  When filing your report, it

is very important that you explain your problem in as much detail as possible,

and include a complete description on how to reproduce the problem.  After

submitting the bug report, attach the following files as uncompressed

individual file attachments using the bugzilla file attachment feature:

   - X server log file: /var/log/XFree86.0.log

   - X server config file: /etc/X11/XF86Config

   - Kernel log file: /var/log/messages


Blijkbaar moet er dus een foutje zitten in deze drivers. Ondertussen heb ik ook geprobeerd om XServer aan de gang te krijgen d.m.v. de standaard vesa drivers (Driver "vesa" in /etc/X11/XF86Config). Jammergenoeg nog steeds dezelfde foutmelding als hierboven :(

Iemand enig idee ?

(het systeem uit mijn profiel is niet het systeem waarop ik Fedora Core 1 probeer te installeren. op die pc werkt het trouwens perfect :))

Aquarius
Win2K SP4 - ASUS A7V600 - AMD Athlon XP 2800+ Barton (333MHz) - 512 MB DDRRAM (400MHz) - Hercules Ati Radeon 9600SE - Maxtor 80GB HD - Pinnacle PCTV - Telenet

Test123456

  • Gast
Re:Foutmelding bij opstarten XServer in Fedora Core 1 op Dell Optiplex GF270
« Reactie #1 Gepost op: 21 januari 2004, 22:26:11 »
De correcte error messages staan in /var/log/XFree86.0.log dus typ in bash best vi /var/log/XFree86.0.log want daar
staat waarschijnlijk meer informatie.
Ik zou de onderstaande intstructies volgen (uit FreeBSD handbook) en als dit niet werkt XFree86 nog eens installeren. En dan misschien een betere distro proberen?
Citaat
Configuration of XFree86 4.X is a multi-step process. The first step is to build an initial configuration file with the -configure option to XFree86. As the super user, simply run:

# XFree86 -configure
This will generate a skeleton XFree86 configuration file in the /root directory called XF86Config.new (in fact the directory used is the one covered by the environment variable $HOME, and it will depend from the way you got the superuser rights). The XFree86 program will attempt to probe the graphics hardware on the system and will write a configuration file to load the proper drivers for the detected hardware on the target system.

The next step is to test the existing configuration to verify that XFree86 can work with the graphics hardware on the target system. To perform this task, the user needs to run:

# XFree86 -xf86config XF86Config.new
If a black and grey grid and an X mouse cursor appear, the configuration was successful. To exit the test, just press Ctrl+Alt+Backspace simultaneously.

Note: If the mouse does not work, be sure the device has been configured. See Section 2.9.10 in the FreeBSD install chapter.

Next, tune the XF86Config.new configuration file to taste. Open the file in a text editor such as emacs(1) or ee(1). First, add the frequencies for the target system's monitor. These are usually expressed as a horizontal and vertical synchronization rate. These values are added to the XF86Config.new file under the "Monitor" section:

Section "Monitor"
        Identifier   "Monitor0"
        VendorName   "Monitor Vendor"
        ModelName    "Monitor Model"
        HorizSync    30-107
        VertRefresh  48-120
EndSection
The HorizSync and VertRefresh keywords may not exist in the configuration file. If they do not, they need to be added, with the correct horizontal synchronization rate placed after the Horizsync keyword and the vertical synchronization rate after the VertRefresh keyword. In the example above the target monitor's rates were entered.

X allows DPMS (Energy Star) features to be used with capable monitors. The xset(1) program controls the time-outs and can force standby, suspend, or off modes. If you wish to enable DPMS features for your monitor, you must add the following line to the monitor section:

        Option       "DPMS"
While the XF86Config.new configuration file is still open in an editor, select the default resolution and color depth desired. This is defined in the "Screen" section:

Section "Screen"
        Identifier "Screen0"
        Device     "Card0"
        Monitor    "Monitor0"
        DefaultDepth 24
        SubSection "Display"
                Depth     24
                Modes     "1024x768"
        EndSubSection
EndSection
The DefaultDepth keyword describes the color depth to run at by default. This can be overridden with the -bpp command line switch to XFree86(1). The Modes keyword describes the resolution to run at for the given color depth. Note that only VESA standard modes are supported as defined by the target system's graphics hardware. In the example above, the default color depth is twenty-four bits per pixel. At this color depth, the accepted resolution is one thousand twenty-four pixels by seven hundred and sixty-eight pixels.

Finally, write the configuration file and test it using the test mode given above. If all is well, the configuration file needs to be installed in a common location where XFree86(1) can find it. This is typically /etc/X11/XF86Config or /usr/X11R6/etc/X11/XF86Config.

# cp XF86Config.new /etc/X11/XF86Config
Once the configuration file has been placed in a common location, configuration is complete. In order to start XFree86 4.X with startx(1), install the x11/wrapper port. XFree86 4.X can also be started with xdm(1).

Note: There is also a graphical tool for configuration, xf86cfg(1), that comes with the XFree86 4.X distribution. It allows to interactively define your configuration by choosing the appropiate drivers and settings. This program can be used under console as well, just use the command xf86cfg -textmode. For more details, refer to the xf86cfg(1) manual page.


 


www.combell.com