Plymouth dont work correctly

[volRot]

Binary package hint: kdm

Plymouth is not correctly work, because KMS with ATI X1600, kernel 2.6.32-16 64 Bit no working the picture is flickering horizontal.
In Plymouth is for a moment a System - Infomation with fsck

[Rohan Garg (rohangarg)]

changed to plymouth since this seems to be the cause of the problem

[Rohan Garg (rohangarg)]

Can you please describe the problem in detail?
Also which graphics drivers are you using? The default ones or the proprietary ATi ones?

[Steve Langasek (vorlon)]

plymouth uses the normal kernel video drivers; if the screen is corrupted, this is a kernel issue.

[volRot (info-rothert)]

ATI is only,
is KMS off ( kernel option radeon-modeset=0) ist the screen ok but plymouht isn't to see.
The screen flicker when the Notebook - Screen 1440*900 OK and the sec. Screen 1680*1050 flicker but is by KMS
KMS off screen's OK. In KMS i can't see the Plymouth is flicker.
Sorry my english oh oh.
Driver fbdev in xorg.conf

[Miroslav Hadzhiev (xtigyro)]

I have an ati mobility x1600 (rv515), Intel Core 2 Duo T7200 (my system is a HP NX9420 rh450ea laptop).

The picture is bearably visible and there is very heavy horizontal flickering. On the other hand, everything boots up normally and GNOME loads with no errors.

I'm attaching an exemplary video file, captured with my phone.

If "radeon.modeset=0" option is used, there is no problems.

I can also affirm you that the problem does not occur in Lucid Alpha 3.

[Miroslav Hadzhiev (xtigyro)]

And I'm using the default video driver - 'radeon' (Ati r5xx series is not supported by the proprietary driver so the open-source 'radeon' is actually the only available choice).

[Miroslav Hadzhiev (xtigyro)]

I reported the bug under Fedora, too.
This is the bug under Fedora 13: https://bugzilla.redhat.com/show_bug.cgi?id=579576

[Miroslav Hadzhiev (xtigyro)]

The bug was marked as duplicate and this is the original bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=571046

And the workaround is:

"As Dave Airlie suggests in bug 579576 radeon.new_pll=0 should work around it.
At least it does here on the same hardware.
FWIW 34-rc1 + rawhide kernels seem to also have this fixed."

I've also tried it (radeon.new_pll=0) and it really works well!

[Miroslav Hadzhiev (xtigyro)]

The only negative part of this workaround is that according to me the 3D performance is slightly worse (when using 'radeon.new_pll=0").

[Miroslav Hadzhiev (xtigyro)]

The bug is preventing the users from even trying Ubuntu. I am absolutely sure that a normal user does not know how to turn off KMS support or even what is KMS and X server. So I believe the bug is a show-stopper. It should have the high level of importance.

[Oliver Joos (oliver-joos)]

I am affected too, but only sometimes when I switch screen mode (e.g. with Ctrl+Alt+Fx) or suspend/resume my laptop.

Unfortunately "radeon.new_pll=0" does not fix it for me, although it seems to lower the probability and/or intensity of flickering.

I use Lucid LTS with kernel 2.6.35-22 on a HP nx8220 with an ATI X600 (RV380) and I added the kernel options "nomodeset radeon.modeset=0" (both, to be sure its disabled everywhere). This problem began in Jaunty or even earlier (don't remember atm).

[penalvch (penalvch)]

volRot, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.