Re: Strange init 3 behavior,

From: Andy Green (andy_at_warmcat.com)
Date: 08/31/05

  • Next message: Thorsten Leemhuis: "Re: ATI Livna driver package"
    To: akonstam@trinity.edu, For users of Fedora Core releases <fedora-list@redhat.com>
    Date: Wed, 31 Aug 2005 18:54:09 +0100
    
    
    
    

    On Tuesday 30 August 2005 13:44, akonstam@trinity.edu wrote:

    > As I keep telling my students you need to ask even it shows your
    > ignorance. Maybe it is the early hour but I don't know how to try the
    > 'vesa' X driver or even what the 'vesa' X driver is. I would like to
    > know what it is if it potentially will solve our problem.
    > Could you clarify?

    Yep. X is the graphical display system, it keeps its configuration
    in /etc/X11/xorg.conf.

    If you make a backup of that, then have a look in there, you'll see it is made
    up of various stanzas which talk about your keyboard, mouse, monitor, display
    adapter and "screens", which are the association of these other things into a
    single monitor.

    You want to look for this:

    Section "Device"
    ...
            Driver "mydriver"
    ...
    EndSection

    mydriver is the name of your current X video driver. Comment out the old
    Driver line with a #

    # Driver "mydriver"

    and add in the vesa driver instead

          Driver "vesa"

    underneath it. Then save the file and restart X (Ctrl-Alt-Backspace will do
    it if you saved your stuff and are on VT7 (Ctrl-Alt-F7)).

    Now you should come up reasonably as before, but you are using a very boring,
    'safe' driver with no real accelleration. If the behaviours that you don't
    like persist, now you can rule out the X display driver as the source. But
    perhaps the behaviours will be gone, in which case you know it is likely
    coming from your old X display driver, whatever that was.

    -Andy

    
    

    
    

    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    


  • Next message: Thorsten Leemhuis: "Re: ATI Livna driver package"

    Relevant Pages

    • Re: Display Driver CETK
      ... be exposed by the display driver. ... 258164 PID:2a7000a TID:2bf000a Creating Global DirectDraw ... You know that Display driver is not a stream interface driver so it ...
      (microsoft.public.windowsce.platbuilder)
    • Re: Display driver drawing corruption
      ... Depending on driver capabilities, ... to the DrvXXX drawing functions. ... There used to be an display driver for a hardware being ... to draw on the primary surface. ...
      (microsoft.public.development.device.drivers)
    • Re: Correct Video Port Architecture
      ... your display driver is not responsible for initializing ... TV/audio out jacks to the video port output. ...
      (microsoft.public.windowsce.platbuilder)
    • Re: Display driver debug problem
      ... ; MGDI NOP Display driver ... ENDIF IMG_NODISPLAY! ... >> matching symbolic information found. ...
      (microsoft.public.windowsce.platbuilder)
    • Re: Artifacts left on screen while dragging icons around
      ... u said u hade problem with SH-based display driver, ... sometime and i get screens of death... ... the frame buffer is not used in my display driver... ... > The display driver is very simple, it's all based on the GPE classes ...
      (microsoft.public.windowsce.platbuilder)