Doubled/Stacked vga16fb display on Sony VGN-S260

[Hezekiah Carty]

The new usplash bootup display shows up doubled on my laptop. By doubled, I
mean that the framebuffer image displays normally at the top of the screen, with
a black gap beneath it, and then displayed again. The bottom image is an exact
copy of the top image.

This is on a Sony VGN-S260 laptop, with an 32mb ATI 9200 chipset and 1280x800
display. I am fully up to date with the current Breezy debs as of this posting.

[Matthew Garrett (mjg59)]

Switching vga16fb to use 640x400 may well work better.

[Hezekiah Carty (hez)]

How do I do this?

[Hezekiah Carty (hez)]

An update to this - using Dapper's latest updates as of Dec. 17, 2005 - usplash
now causes a screen bloom on my laptop. This is using the xubuntu splash. I
will download a proper Flight2 install CD tonight and test with that as well.

[Ben Collins (ben-collins)]

(In reply to comment #3)
> An update to this - using Dapper's latest updates as of Dec. 17, 2005 - usplash
> now causes a screen bloom on my laptop. This is using the xubuntu splash. I
> will download a proper Flight2 install CD tonight and test with that as well.

Had a chance to test? What exactly is a "screen bloom"?

[Hezekiah Carty (hez)]

The problem persists with the default Flight 2 install CD framebuffer settings.
 However, if I use the 1024x768 resolution everything works well.

A screen bloom is when an LCD (laptop?) display is somehow overdriven or
something along those lines. The display starts out garbled, and gradually
brightens to all white. It's blotchy as it turns white, and from what I
understand it is bad for the display, though I am rather ignorant of the
technical details involved.

[Hezekiah Carty (hez)]

The screen bloom is gone, but the stacked screens are back. Again, this is fixed if you set a vga=792 (or some other setting) on the kernel boot line.

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Ralph Janke (txwikinger)]

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks