[lkml]   [2001]   [Jul]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Subject2.4.[56] kernel + xfree 4.1.0
    After upgrading to xfree 4.1.0, after switching back to the console after
    starting X, suspending, and resuming, the text-mode terminals are corrupt
    (but look like they're in text mode). There were some messages in the
    XFree lists about X no longer restoring previous graphics state (since it
    has no real way of knowing what graphics state the console you're
    switching to is in), but I was hoping this was an Xserver bug with my
    graphics chipset (savage ix) writing someplace it shouldn't.

    I just compiled framebuffer support in, though, and when switching to a
    console, it's initially corrupt (similar pretty impressionistic graphics
    that look like they're in the correct video mode for the
    framebuffer/console), but within a half a second the framebuffer fixes

    Also with framebuffer in use, after a suspend and resume from X 4.1.0, the
    mouse cursor is replaced by a large block. With regular text-mode
    consoles, this doesn't happen. Switching away and back to X restores the
    cursor properly. This may be completely X's fault though.

    Allegedly it's supposed to be bad to run non-framebuffer X-servers with
    framebuffer console, is this really not considered stable or am I
    mistaken? If X isn't going to restore previous graphics modes, it doesn't
    seem to matter what mode the console was in, framebuffer or not, it still
    needs to be fixed regardless.

    I'm presuming then that this is something the regular console driver needs
    to deal with?


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 12:56    [W:0.022 / U:0.060 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site