Plymouth garbles screen (ATI 200M)

Bug #519891 reported by Tom Louwrier
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Hi

Running Lucid Alpha AMD64 on a Dell 131L laptop with ATI 200M video card. Updates loaded once a day.

In the last 2 weeks+ the system breaks every other day, seemingly to do with changes to the video driver or associated changes to the kernel.
After the very first text based messages when booting the screen turns black, then I get all sorts of fine coloured vertical lines and that's about it. I can hear the rest of the booting process carrying on and see the wifi-light come up. Without gui, that still leaves me with an unusable system.
Shifting to tty with ctrl-alt-F1 etc does not help, because that gives me just another pattern of coloured bars.

First time this happened I had to wait a day and then reinstall from an alternative-daily CD.
That seemed to fix it. Fair enough, an update that hickupped.
However, since then this problem returns about every 2 days. Sometimes I can get around it by adding 'nomodeset' or 'radeon.modeset=0' to the boot line in grub. Other times it will only boot with this option removed.
Removing 'splash quiet' from the boot line makes no difference.
With the option 'nomodeset' I have also seen the screen with just the left hand half in use (right half blacked out) and 2 mouse cursors about 1/2 screen apart vertically. The left half of the screen is completely garbled but for the 2 cursors.

I have not seen any real pattern in which update to what packet seems to trigger of fix this issue. Xserver was there at one time, but also plymouth or nothing very much related to the gui or video subsystem at all (I think). Sometimes I find that the problem returns after a reboot, without any updates having been installed at all since the last boot.
Could this have to do with a race condition somewhere, making this problem intermittent and not easily reproduced?

Usually I wait for 24 hours and try to boot into rescue mode so I can update whatever has been released and *hope* for my system to get accessible again.
Of course I am quite aware that this is an alpha release, but this is getting really annoying. Also it keep driving me to use XP again (ugh!) and we don't want that, do we?

If I can do anything to give you more information about this issue, please ask.

regards
Tom
---
Architecture: amd64
CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b
CheckboxSystem: d00f84de8a555815fa1c4660280da308
DistroRelease: Ubuntu 10.04
InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info'
MachineType: Dell Inc. Latitude 131L
Package: plymouth 0.8.0~-10ubuntu1
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-13-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro nomodeset quiet splash
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-2.6.32-13-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro nomodeset quiet splash
ProcEnviron:
 LANGUAGE=en_GB.utf8
 LANG=en_GB.utf8
 SHELL=/bin/bash
ProcFB: 0 VGA16 VGA
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
Tags: lucid
Uname: Linux 2.6.32-13-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/30/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.1
dmi.board.name: 0PM607??????
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??????:rvr:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Latitude 131L
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

Revision history for this message
Tom Louwrier (tom-louwrier) wrote :

see also bug 516412

After solving the problems on my wife's laptop (Dell XPS 1530 with a NVidiia, not an ATI card) I decided to try removing Plymouth from my own laptop too. Booted into recovery mode using 'nomodeset' and kicked Plymouth. System restarted fine after that.

Uninstalling Plymouth seems to have solved it for now (although I think that is not what the devs of Plymouth aimed for...).

If you want me to help you getting more information about why Plymouth borked my system(s), please let me know.

cheers
Tom

Revision history for this message
Tom Louwrier (tom-louwrier) wrote :

removing Plymouth solved issue, so confirmed I think.

affects: ubuntu → plymouth (Ubuntu)
Changed in plymouth (Ubuntu):
status: New → Confirmed
Revision history for this message
Steve Langasek (vorlon) wrote :

Please try the plymouth-splash.conf job from https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/516412/comments/52 and report whether booting works more reliably for you with this version. Also, please mention whether you see the Ubuntu logo before gdm comes up.

Revision history for this message
Tom Louwrier (tom-louwrier) wrote : Re: [Bug 519891] Re: Lucid breaks every other day; no gui and no tty (ATI 200M)

Steve,

I will try that and give you feedback, but not the coming week. Right
now both ATI and NVidia systems are booting well -and faster!- without
Plymouth. It seems there are too many issues related to Plymouth and
given the consequences of that (unusable system) I prefer to wait a
while or even leave the splash gizmo out completely.

On the ATI 200M machine when I did see the Ubuntu logo I knew it would
boot fine. When I didn't I would reach for the power button almost
straight away because that meant it was going to hang with the vertical
lines or garbled screen.
On the NVidia 8600M I would see the blue/white bar, broken up by text
messages, followed by the 'enter-freeze' issue.

Will report back later.

cheers
Tom

Revision history for this message
Tom Louwrier (tom-louwrier) wrote : Re: Lucid breaks every other day; no gui and no tty (ATI 200M)

hi Steve,

Gave Plymouth another try just now. Installed current version from the repository, checked the script you mentioned in #3 (it's the correct one) and rebooted.
I saw the blue/white bars, broken up by some messages. After that I got the garbled left hand side of the screen again, the right hand side being all black.
Rebooted into rescue mode, did 'apt-get remove plymouth' and rebooted into a usable system again.
Sorry, it's still not working as it should.

Tom

Revision history for this message
Lollerke (pumba88) wrote :

same bug ?!: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/509273
no tty and the nomodeset solution doesn't work with all the daily live CDs

Revision history for this message
Tom Louwrier (tom-louwrier) wrote : Re: [Bug 519891] Re: Lucid breaks every other day; no gui and no tty (ATI 200M)

No, not the same bug, but there are probably relations between them.
I've been having problems with Plymouth with and without disabling KMS
(booting with 'nomodeset') and also the other way around.

Uninstalling Plymouth gives me a usable system, but I'm pretty sure that
there are issues with KMS and my Xpress 200M as well, because of the
'nomodeset'.

Tom

Lollerke wrote:
> same bug ?!: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/509273
> no tty and the nomodeset solution doesn't work with all the daily live CDs
>
>

Revision history for this message
Steve Langasek (vorlon) wrote : Re: Lucid breaks every other day; no gui and no tty (ATI 200M)

Tom,

Please install the 0.8.0~-10ubuntu1 version of the plymouth and libplymouth2 packages and run 'apport-collect -p plymouth 519891'.

When booting to the garbled screen, please also test whether Alt+SysRq+K successfully resets it for you.

Revision history for this message
Tom Louwrier (tom-louwrier) wrote : BootDmesg.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Tom Louwrier (tom-louwrier) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Tom Louwrier (tom-louwrier) wrote : Dependencies.txt

apport information

Revision history for this message
Tom Louwrier (tom-louwrier) wrote : Lspci.txt

apport information

Revision history for this message
Tom Louwrier (tom-louwrier) wrote : Lsusb.txt

apport information

Revision history for this message
Tom Louwrier (tom-louwrier) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Tom Louwrier (tom-louwrier) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Tom Louwrier (tom-louwrier) wrote : ProcModules.txt

apport information

Revision history for this message
Tom Louwrier (tom-louwrier) wrote : UdevDb.txt

apport information

Revision history for this message
Tom Louwrier (tom-louwrier) wrote : UdevLog.txt

apport information

Revision history for this message
Tom Louwrier (tom-louwrier) wrote : Re: Lucid breaks every other day; no gui and no tty (ATI 200M)

Tried it.
- Installed plymouth and plymouth-x from repos. Never uninstalled libplymouth2 because that threatens to uninstall about all of the rest of my packages, so that was still there and up to date..
- Rebooted, with 'nomodeset' flag.
- Saw 2 fsck messages in std screen resolution
- Saw the blue/white bars, broken up by messages. No logo, no [ C ].
- Got the garbled screen (left) and blacked out (right)
- Alt-Sysreq-k gave me a normal login-screen straight away (thank you for that info)
- Ran the apport-collect, output is right above

- Closed down and rebooted, without the 'nomodeset' flag
- Got the vertical coloured lines straight away
- Alt-Sysreq-k gave me a different pattern of vertical lines several times, no usable system

- Rebooted once more, repeated the first try; so with 'nomodeset'
- Saw the blue/white bars, broken up by messages. Also saw a [ C ]. No Ubuntu logo.
- Got the garbled screen (left) and blacked out (right)
- Alt-Sysreq-k gave me a normal login-screen straight away.

I will leave Plymouth installed, since I now know how to get a usable system at logon.
Will report back if things change.

Obviously my system is also bitten by another bug concerning KMS / DRM and (older?) ATI cards. This does not always occurr but more often than not. I use the 'nomodeset' flag to prevent this one.

Thanx so far.

cheers
Tom

Revision history for this message
Steve Langasek (vorlon) wrote :

Tom,

You wrote:
> On the ATI 200M machine when I did see the Ubuntu logo I knew it would
> boot fine. When I didn't I would reach for the power button almost
> straight away because that meant it was going to hang with the vertical
> lines or garbled screen.

The attached information from apport shows that there's no way you could have seen the Ubuntu logo when booting this way (nomodeset, and VGA16 as the only available framebuffer). When you tested the latest version of plymouth in comment #5, were you testing it with 'nomodeset', or did you also test it with KMS enabled?

With the current version of plymouth, and KMS enabled, you should *always* see the Ubuntu logo (a bug that sometimes prevented it from being shown was fixed). If you don't, that's another bug that we probably need to figure out first.

Revision history for this message
Steve Langasek (vorlon) wrote :

Ah, seems our messages missed each other in transit.

> Obviously my system is also bitten by another bug concerning KMS / DRM
> and (older?) ATI cards. This does not always occurr but more often than
> not. I use the 'nomodeset' flag to prevent this one.

Ok, please file a separate bug report on the linux package about the KMS problem.

For the moment, I will assume the plymouth bug you're seeing is related to the use of 'nomodeset' (i.e., it only applies when using the VGA16 framebuffer driver), which seems to be consistent with what other bug reporters are seeing.

Revision history for this message
Tom Louwrier (tom-louwrier) wrote : Re: [Bug 519891] Re: Lucid breaks every other day; no gui and no tty (ATI 200M)

hi Steve.

I tried both with and without just now. With KMS (no 'nomodeset') the
screen went into vertical lines straight away and I did give that
another go. I rebooted again and used 'nomodeset'.
I have not put it in my grub.cfg permanently.

Since the KMS-related problem is intermittent, I have seen the logo on
some occasions when 'nomodeset' was not used. Those times I would get a
successful boot.

Problem is that when KMS plays up, after grub I get the vertical lines
almost immediately and no useful information can be seen anymore.
Might be that on the next try without 'nomodeset' the system does boot
correctly and that I will see the logo. I will let you know. Not much
more we can do until the KMS thing gets fixed I guess, unless you know
things for me to do to separate the effects of these two issues (see
als bug 509273).

cheers
Tom

Steve Langasek wrote:
> Tom,
>
> You wrote:
>
>> On the ATI 200M machine when I did see the Ubuntu logo I knew it would
>> boot fine. When I didn't I would reach for the power button almost
>> straight away because that meant it was going to hang with the vertical
>> lines or garbled screen.
>>
>
> The attached information from apport shows that there's no way you could
> have seen the Ubuntu logo when booting this way (nomodeset, and VGA16 as
> the only available framebuffer). When you tested the latest version of
> plymouth in comment #5, were you testing it with 'nomodeset', or did you
> also test it with KMS enabled?
>
> With the current version of plymouth, and KMS enabled, you should
> *always* see the Ubuntu logo (a bug that sometimes prevented it from
> being shown was fixed). If you don't, that's another bug that we
> probably need to figure out first.
>
>

Revision history for this message
Tom Louwrier (tom-louwrier) wrote :

OK

Steve Langasek wrote:
> Ah, seems our messages missed each other in transit.
>
>
>> Obviously my system is also bitten by another bug concerning KMS / DRM
>> and (older?) ATI cards. This does not always occurr but more often than
>> not. I use the 'nomodeset' flag to prevent this one.
>>
>
> Ok, please file a separate bug report on the linux package about the KMS
> problem.
>
> For the moment, I will assume the plymouth bug you're seeing is related
> to the use of 'nomodeset' (i.e., it only applies when using the VGA16
> framebuffer driver), which seems to be consistent with what other bug
> reporters are seeing.
>
>

summary: - Lucid breaks every other day; no gui and no tty (ATI 200M)
+ Plymouth garbles screen (ATI 200M)
Revision history for this message
Tom Louwrier (tom-louwrier) wrote :

hi Steve,

Booted up just now and pulled in last night's s**tload of updates, many Xorg and libdrm related.
Rebooted and got lucky without using 'nomodeset'.
- saw the logo
- got the login screen OK
- rebooted to check this wasn't a fluke
- saw the logo during shutdown
After that KMS borked again (twice) and I had to use 'nomodeset' again.
- saw the blue/white bar broken up by some messages
- got the garbled half screen. :-(
- alt-sysreq-k fixed it
After that everything worked as it should.

So it seems that if KMS works, so will Plymouth.
Using the 'nomodeset' flag is a workaround for the KMS issue, but breaks Plymouth.

cheers
Tom

Revision history for this message
Lollerke (pumba88) wrote :

I have an X200M too.

2010.02.18. daily build: everything is perfect with nomodeset
2010.02.21. daily build: screen corruption (tiny black pixels in the upper-left corner and when I start to write something in any apps it gets bigger) with nomodeset

Revision history for this message
Tom Louwrier (tom-louwrier) wrote : Re: [Bug 519891] Re: Plymouth garbles screen (ATI 200M)

With 'nomodeset' I still get the garbled screen (and indeed tiny pixels
whenever I type something), but can fix it by using alt-sysreq-k.

Without 'nomodeset' I'm getting all vertical lines and cannot use my
system. Can't get past that with alt-sysreq-k or ctrl-alt-backspace.
Every once in a while it actually boots ok without the 'nomodeset' and
then Plymouth works ok, but at the moment I feel this is getting less
frequent.
Because I can't reproduce the behaviour without 'nomodeset' right or
wrong, I feel there is some issue to do with timing or a race condition
somewhere between the kernel and the radeon driver.
But I'm not a dev.

Updating Lucid twice a day. I'm not trying daily cd's unless I can't get
into my system even by booting into rescue mode.

cheers
Tom

Lollerke wrote:
> I have an X200M too.
>
> 2010.02.18. daily build: everything is perfect with nomodeset
> 2010.02.21. daily build: screen corruption (tiny black pixels in the upper-left corner and when I start to write something in any apps it gets bigger) with nomodeset
>
>

Revision history for this message
Lollerke (pumba88) wrote :

2010.02.22. daily build: everything is perfect (no screen corruption) with nomodeset

Revision history for this message
Tom Louwrier (tom-louwrier) wrote :

No change here.

Just loaded today's updates and was asked to reboot.
Was able to boot once without 'nomodeset' and everything worked just fine. Tried it again and got the vertical lines again. And again. And again.
So I booted with 'nomodeset' and got the -well known- garbled screen, so I gave that the alt-sysrq-k routine. After that I could log on and use my pc ok.

cheers
Tom

Revision history for this message
Tom Louwrier (tom-louwrier) wrote :

(hi Steve)
update:
Got a lot of upgraded packages over the last days, including X and a new kernel. Result is still the same, and still disappointing.
Loaded the new kernel and X yesterday, rebooted and everything worked fine. No screen corruption, vertical lines etc, Plymouth also doing exactly what it should.
Logged in, logged out, rebooted. No Plymouth, just vertical lines and unusable system. Killed X, but that would not help either.
So now I'm back at booting without KMS (using the 'nomodeset' option) which gives me a garbled screen. Luckily I can get past that by killing X and then everything works pretty well.

I really think the problems of this bug in combination with bug 509273 should be picked up and fixed, since it is the sort of 'does *not* work out of the box' issue that drives people away from Linux back to Winblows.

Importance = high
Serious regression

cheers
Tom

Revision history for this message
Steve Langasek (vorlon) wrote :

The fix for the plymouth problems is still in progress and will hopefully be resolved in the next few days; it's a deep issue that's been taking up all the time of one of our developers to get to the bottom of.

I certainly agree with you that we want to get the ATI KMS bug fixed also, but I'm not sure if anyone on the kernel team has a handle on it to do anything besides blacklisting this card in the driver. Best if you follow up to that bug report separately.

Revision history for this message
Steve Langasek (vorlon) wrote :

plymouth 0.8.0~-14 is now available in lucid. Please test to see whether this version fixes the problem when using nomodeset.

Changed in plymouth (Ubuntu):
status: Confirmed → Incomplete
importance: Undecided → Medium
Revision history for this message
Tom Louwrier (tom-louwrier) wrote :

hi Steve,

I wish I could.... ;-)
There were updates to X-core and the ATI/Radeon driver in the same batch that contained Plymouth 0.8.0~-14.
To my surprise I can now start up without the dreaded 'nomodeset' option. This works fine, Plymouth and X all doing what they should. So far, so good.

In order to find out what Plymouth would do when booting under 'nomodeset' I rebooted and tried that. Guess what..... the situation has reversed. 'Nomodeset' now gives me a screen with vertical coloured bars abd lines, and there it all ends.
To be precise:
- 2 messages about fsck
- a purple screen in text-mode with Ubuntu showing, no coloured horizontal bar at the bottom
- some messages about urearahead exiting with status 4, looking a bit messy like the ones that broke up the blue/white bar
- X kicks in and I'm looking at vertical lines.

I guess I can't complain about my system finally booting without setting extra options, but it sort of bothers me that I can't tell you whether Plymouth works OK now when KMS is disables.
Thanx for all your effort so far tho.

cheers
Tom

Revision history for this message
Tom Louwrier (tom-louwrier) wrote :

Spoke too soon.
Tried hibernating (worked) and resuming (crashed). Did a hard reboot and behaviour is back to where it was; 'nomodeset' when booting else vertical lines y nada mas.

Steve, the good news is that Plymouth now works OK for me even when booting with 'nomodeset'.
- 2 messages about fsck
- a purple screen in text-mode with Ubuntu showing, no coloured horizontal bar at the bottom
- a message about urearahead exiting with status 4, looking a bit messy like the ones that broke up the blue/white bar
- X kicks in and I'm looking at a normal login screen.

I do hate it when errors come and go at -seemingly- random moments. There must be a way to reliably reproduce this.

cheers Tom

Revision history for this message
Steve Langasek (vorlon) wrote :

Ok, it sounds like the remaining problems you're seeing - with or without nomodeset - are X driver problems, not plymouth problems, so closing this report. Thanks for following up.

Changed in plymouth (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Tom Louwrier (tom-louwrier) wrote :

That's OK by me.

see ya
Tom

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

On Sun, 2010-03-14 at 16:29 +0000, Tom Louwrier wrote:

> In order to find out what Plymouth would do when booting under 'nomodeset' I rebooted and tried that. Guess what..... the situation has reversed. 'Nomodeset' now gives me a screen with vertical coloured bars abd lines, and there it all ends.
> To be precise:
> - 2 messages about fsck
> - a purple screen in text-mode with Ubuntu showing, no coloured horizontal bar at the bottom
> - some messages about urearahead exiting with status 4, looking a bit messy like the ones that broke up the blue/white bar
> - X kicks in and I'm looking at vertical lines.
>
> I guess I can't complain about my system finally booting without setting extra options, but it sort of bothers me that I can't tell you whether Plymouth works OK now when KMS is disables.
>
From the sounds of it, Plymouth is actually working great with KMS
disabled (other than the spam of console messages over the top) - and
it's the X server that screws things up when it kicks in.

You'll want to file a bug on the non-KMS X driver, almost certainly.

Thanks,

Scott
--
Scott James Remnant
<email address hidden>

Revision history for this message
Tom Louwrier (tom-louwrier) wrote :

Agreed. I've been bitten by two separate bugs during boot, this one (now solved) and the KMS issue.
There's quite a discussion about the latter going on at 509273, which is what you mean I guess.

If not, plz point me in the right direction about filing a bug against the right driver (kms, non-kms, ati, radeon.... it's getting me confused a bit by now)

cheers
Tom

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

On Mon, 2010-03-15 at 13:58 +0000, Tom Louwrier wrote:

> Agreed. I've been bitten by two separate bugs during boot, this one (now solved) and the KMS issue.
> There's quite a discussion about the latter going on at 509273, which is what you mean I guess.
>
That looks like as good a place as any to discuss the X issues

Scott
--
Scott James Remnant
<email address hidden>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.