Re: [Bugme-new] [Bug 9093] New: Framebuffer breakage with vesafb on x86_64

[Andrew Morton <akpm@linux-foundation.org>]

On Thu, 27 Sep 2007 17:04:55 -0700 (PDT)
bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=9093
> 
>            Summary: Framebuffer breakage with vesafb on x86_64
>            Product: Other
>            Version: 2.5
>      KernelVersion: 2.6.22.7
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Other
>         AssignedTo: other_other@kernel-bugs.osdl.org
>         ReportedBy: bug.hunter@gmx.net
> 
> 
> Most recent kernel where this bug did not occur: Don't recall!
> 
> Distribution: Gentoo-Linux
> 
> Hardware Environment: AMD Athlon 64 X2 5600+, Asus Crosshair MB, 4GB Kingston
> Sli-Ready Hyper-X RAM, 2 x XFX nVidia GeForce 7900 GS (sli-setup) etc.
> 
> Software Environment: Asus Crosshair Bios Rev. 702 (stable) ... first running
> terminal, then xorg-server build (on gentoo)
> 
> Problem Description: `vesafb' module is compiled into the kernel. No problems
> with current or virtual terminals. First run of `startx' command is also fine.
> After shutdown and restart of x-server problem appears in form of a blinking
> cursor image on top of the `desktop' area in the upper left corner (I'll attach
> a snapshot). It makes no difference if same or other user with a new login
> restarts X. It makes no difference if binary-nvidia driver, nv or whatever else
> is used. It makes no difference if kde, gnome, xfce or plain old twm
> environment is used to build a workspace. It has nothing to do with resolution,
> monitor, cables ... neither with my current sli-setup, I've had the same
> symptom on a previous x86_64 single video card box. This broken framebuffer
> image goes away if during an open X session any `ctrl+alt+Fx' sequence is
> called to switch to a virtual terminal and back.
> 
> Interestingly it differs when `vga16fb' is used instead?! No breakage, nothing!
> Besides that this out-dated module is ugly on the terminal, it also tends to
> mess up with current xorg-server builds ... my 11 year old son lost the video
> signal when he tried to quit an old DOS game running under `scummvm' ... which
> never happened with `vesafb' or a kernel build without any framebuffer device
> ... but that's another story, sigh!
> 
> Please ask for any further information you might need to investigate this
> problem...
> 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/