Hello,
I see a weird problem with uvesafb and any recent Kernel. It seems like
the problem was introduced in some higher 2.6.24 version. I have more
information regarding this, but I will first explain the problem(s) I
experience.
After booting a faulty Kernel, these messages appear in my Kernel log
ring buffer ("dmesg"):
[ 112.816609] uvesafb: mode switch failed (eax=0x2104, err=0). Trying
again with default timings.
[ 112.819540] uvesafb: mode switch failed (eax=0x2104, err=0)
Please note, that these messages are the first ones after having booted
the box. (Due to the init scripts, the VT was automatically switched to
VT7 where X resides, after that I switched back to VT1.)
Switching to other VT's does *not* reproduce the warning/error messages.
Now to the interesting part.
When starting any program that needs framebuffer support (which is why
we use uvesafb, isn't it?), there messages re-appear. I have tested
mplayer with -vo fbdev or fbdev2 for example, on VT2. Starting it,
playing a (video) file for some seconds and looking at dmesg again,
these are the results:
[ 564.757398] uvesafb: mode switch failed (eax=0x338, err=0). Trying
again with default timings.
[ 564.758358] uvesafb: mode switch failed (eax=0x2104, err=0)
[ 564.838390] uvesafb: mode switch failed (eax=0x344, err=0). Trying
again with default timings.
[ 564.844749] uvesafb: mode switch failed (eax=0x2104, err=0)
[ 564.929364] uvesafb: mode switch failed (eax=0x104c, err=0). Trying
again with default timings.
[ 564.937509] uvesafb: mode switch failed (eax=0x2105, err=0)
[ 565.021358] uvesafb: mode switch failed (eax=0x42b, err=0). Trying
again with default timings.
[ 565.027047] uvesafb: mode switch failed (eax=0x2105, err=0)
[ 565.109331] uvesafb: mode switch failed (eax=0x32b, err=0). Trying
again with default timings.
[ 565.111679] uvesafb: mode switch failed (eax=0x2105, err=0)
[ 565.194323] uvesafb: mode switch failed (eax=0x2104, err=0). Trying
again with def...
