Bug 85683 – Defective Screen Blanking by fbsplash/vesafb on 2005.0-rc5 Live CD

• Product: Gentoo Release Media
• Status: RESOLVED DUPLICATE

[Description Bob 2005-03-17 14:03:18 UTC]

Screenblanking is defective on the 2005.0 Live CD.  When the screen is forced blank, the screen fails to completely blank the framebuffers splash image.  

This is what happens:  1) the outer border of the screen display is blanked, 2) the color of the text is changed from white to black, 3) the text output remains turned on, so that screen updates are made with black text, and 4) the background image remains on at all times, 5) the cursor cell remains on at all times.

Reproducible: Always
Steps to Reproduce:
1.  Boot the 2005.0 Live CD
2.  Wait for screen blanking
3.

Actual Results:  
Incomplete screen blanking as described above.  The text continually updates
while the color is changed from white to black, and the central framebuffer
image is never turned off.

Expected Results:  
Complete screen blanking, with all screen elements turned off.

This problem with the 2005.0 Live CD was not present in the 2004.0 Live CD.

A previous bug report had been filed relating to this problem occurring with
later G-D-S kernels:  

http://bugs.gentoo.org/show_bug.cgi?id=79131

Unfortunately, this problem remains unsolved and has now found its way into the
Live CD, which is somewhat embarassing. :o

Related Links:
http://forums.gentoo.org/viewtopic-t-282370.html
http://forums.gentoo.org/viewtopic-t-308966.html

[Comment 1 Chris Gianelloni (RETIRED) 2005-03-17 14:40:08 UTC]

We do not accept bug reports on pre-release materials when there is already a tracker bug for such things.

Also, if it is obvious what the error is (the kernel) then why did you post a duplicate bug?  This one is a duplicate of both the x86 metabug and the kernel bug you posted as the URL.  There's no point in duplicating bugs as it just wastes developer time.

Thanks

*** This bug has been marked as a duplicate of 77881 ***

[Comment 2 Chris Gianelloni (RETIRED) 2005-04-20 11:20:38 UTC]

*** Bug 89802 has been marked as a duplicate of this bug. ***