plymouth broken on radeon 7500

Here is the dmesg from the boot with KMS disabled and plymouth installed.

BTW, this will be a very serious bug if KMS is blacklisted for this card since the only known stable configuration for the radeon 7500 on Lucid is XAA/metacity/RenderAccel off/no KMS (see bug #513956, bug #507148 and bug #513950).

When gdm comes up half-corrupted, does using Alt+SysRq+K succeed in resetting it?

> ProcFB:
> 0 radeondrmfb
> 1 VGA16 VGA

This seems to indicate that you *are* using KMS, doesn't it?

Oh, sorry, you said that this was how you were booting.

Why are you using KMS *and* disabling splash in that test?

I'm having a good reading comprehension day!

So you're using KMS, you have 'splash' enabled, and you only get text, no splash? Can you get a screenshot of this?

If I enable KMS and use splash, then I only have text until gdm. The kernel did switch modes on boot to the smaller font in this setup.

If I disable KMS with radeon.modeset=0 and use splash, I get the half and half corruption with gdm. The mode is not switched on boot (the console font is big).

Do you still want a screenshot?

*sigh* I reinstalled plymouth and rebooted with KMS and I saw the ubuntu logo. I even tried with /forcefsck and saw the logo. Perhaps my initramfs didn't get updated for some reason. I can say when I uninstalled it after filing this bug that another package was removed related to 'crypt disks'. I'm sorry I don't recall the name and I can't seem to find it. :/

However, this time with KMS I could not get to the gnome login screen-- I only saw a cursor. I could login on tty1, then stop and start gdm and it worked.

Ok, booting without KMS and with plymouth will sometimes look ok when gdm starts, and other times has the split screen. Changing to tty1 and back seems to be enough to correct atm.

I forgot to mention: Alt+SysRq+K does work in resetting it.

It seems like every time I boot I see something different. Here is a summary for plymouth without KMS:

What always happens with radeon.modeset=0:
1. text mode is not changed (big fonts)
2. blue progress bars displayed at bottom

What has sometimes happened with radeon.modeset=0:
1. text outside of blue progress bar
2. gdm comes up ok
3. get the half and half gdm screen. Alt+SysRq+K fixes it
4. get the half and half gdm screen, changing to tty1 and back fixes it
5. gdm comes up ok, going to a tty that gdm is not running on shows the half and half screen (weird!) but going back to gdm seems ok. Alt+SysRq+K does not fix the tty
6. gdm comes up ok, going to a tty that gdm is not running on shows the half and half screen (weird!) but going back to gdm shows all kinds of 'twinkling artifacts' along the upper half inch of the screen, but gdm otherwise looks ok.

Yes, I want a screenshot of the text when booting with KMS + splash, to figure out what plugin is getting used instead of the graphical renderer.

Well, as I said in a later comment, the boot text issue doesn't appear
to be a problem anymore (possibly initramfs didn't get updated).

ok, then the remaining problem here is the master "plymouth changes VTs wrong" bug.

This bug was fixed in the package plymouth - 0.8.0~-13

---------------
plymouth (0.8.0~-13) lucid; urgency=low

  [ Steve Langasek ]
  * Don't attach /proc/cmdline to apport reports, this is already in the
    standard info that gets collected...

  [ Alberto Milone ]
  * ubuntu_logo theme:
    - New logo from Otto Greenslade.
    - Switch off dots starting from the ones on the left instead of
      switching them off all at once.

  [ Scott James Remnant ]
  * Move the Ubuntu logo up as discussed with Otto, this makes the mouse
    cursor appear between the logo and dots and solves the optical illusion
    of the logo being too low. LP: #535014.
  * Don't include message about disk checks, which can come from mountall.
  * Drop the rc script splash functions, we don't want the SysV-rc compat
    stuff messing around with the splash screen - this can be entirely
    managed by Upstart now. LP: #528787, #537262.

  * Plymouth Fix Mega Patch:
    - This hasn't yet been broken up into enough bits to send upstream, and
      doesn't *quite* address all the issues yet, but it's a major step.

    - Rewrite the VT handling, rather than abusing /dev/tty0 keep all VT
      operations on the actual VT (tty7), this avoids issues where we set
      the graphics mode of the wrong VT or put the wrong VT into VT_PROCESS
      mode. LP: #520460, #522598, #526321, #533135
    - Don't attempt VT switch when using non-VT consoles.
    - Make VT mandatory for renderer plugins, so we fallback gracefully to
      text when the console is not a VT. LP: #516825, #527083.
    - Restore VT when finished displaying the splash unless plymouth quit
      is called with --retain-splash. LP: #506297.
    - Activate VT from text and details plugins, rather than haphardly in
      the main code, this means the textual boot is also on VT7.
      LP: #518352, #520122.
    - Add a --has-active-vt command that can let gdm inquire whether it
      should reuse Plymouth's VT; fixes the issue where Plymouth has no
      visible splash screen and X ends up on VT1. LP: #519641, #533572.

    - Don't open terminal device in X11, fixes the issue where X will crash
      when debugging plugins using the X11 renderer.
    - Add --tty option to plymouthd for debugging when X is running and
      thus using an alternate VT.

    - Improve deactivate command so that the terminal is no longer watched
      for keyboard input, session is closed, etc. LP: #528787, #531650.
    - Ignore mode changes while deactivated, otherwise we can end up
      resetting the VT back into text mode while X is starting up.
      LP: #523788, #502509.

    - Fix races with simultaneous quit and deactivate commands, or multiples
      of those commands.
    - Ignore --show-splash, --hide-splash, etc. commands while deactivated.
    - Add reactivate command for testing purposes.

    - Don't scan out drm buffer contents to fbcon when not called with
      quit --retain-splash. LP: #527180.

    - Avoid resetting the terminal to unbuffered mode on every write, this
      results in setting X's VT into raw mode and results in the X server
      crashing on key presses. LP: #532047, #534861, #519460, #520...

Not fixed here. Plymouth falls to text-mode.
I've uploaded a video on youtube: http://www.youtube.com/watch?v=jzbt6wxLwWc

(Thinkpad T40, Mobility radeon 7500, fully updated Lucid.)

On Sat, 2010-03-13 at 19:54 +0000, Lucazade wrote:

> Not fixed here. Plymouth falls to text-mode.
> I've uploaded a video on youtube: http://www.youtube.com/watch?v=jzbt6wxLwWc
>
> (Thinkpad T40, Mobility radeon 7500, fully updated Lucid.)
>
This video looks fine to me (?), other than the known issue of console
messages appearing over top of the text plugin (#535108)

Scott
--
Scott James Remnant
<email address hidden>

I should see the full logo and rounded dots instead of text-mode.
Kms seems to run ok so i don't understand why it doesn't work.
Am i wrong?

On Mon, 2010-03-15 at 12:10 +0000, Lucazade wrote:

> I should see the full logo and rounded dots instead of text-mode.
> Kms seems to run ok so i don't understand why it doesn't work.
> Am i wrong?
>
Should you? If you don't see the full logo and see the text, it implies
that KMS isn't running ok.

Could you provide the output of "cat /proc/fb" for me?

Scott
--
Scott James Remnant
<email address hidden>

cat /proc/fb
0 radeondrmfb
1 VGA16 VGA

dmesg | grep drm
[ 6.315514] [drm] Initialized drm 1.1.0 20060810
[ 6.835265] [drm] radeon defaulting to kernel modesetting.
[ 6.835272] [drm] radeon kernel modesetting enabled.

KMS seems to run because the screen during system startup switch to 1024x768 (lcd native resolution)

On Mon, 2010-03-15 at 13:27 +0000, Lucazade wrote:

> cat /proc/fb
> 0 radeondrmfb
> 1 VGA16 VGA
>
> dmesg | grep drm
> [ 6.315514] [drm] Initialized drm 1.1.0 20060810
> [ 6.835265] [drm] radeon defaulting to kernel modesetting.
> [ 6.835272] [drm] radeon kernel modesetting enabled.
>
> KMS seems to run because the screen during system startup switch to
> 1024x768 (lcd native resolution)
>
How many monitors does your system have?

Also can you run "ls -l /lib/plymouth/themes /lib/plymouth/renderers"
for me?

Thanks

Scott
--
Scott James Remnant
<email address hidden>

luca@T40:~/Desktop$ ls -l /lib/plymouth/themes/ /lib/plymouth/renderers/

/lib/plymouth/renderers/:
totale 40
-rw-r--r-- 1 root root 22384 2010-03-13 00:52 drm.so
-rw-r--r-- 1 root root 13844 2010-03-13 00:52 frame-buffer.so

/lib/plymouth/themes/:
totale 32
lrwxrwxrwx 1 root root 32 2010-03-13 10:16 default.plymouth -> ubuntu-logo/ubuntu-logo.plymouth
drwxr-xr-x 2 root root 4096 2010-03-13 10:16 details
drwxr-xr-x 2 root root 4096 2010-03-13 10:16 fade-in
drwxr-xr-x 2 root root 4096 2010-03-13 10:16 glow
drwxr-xr-x 2 root root 4096 2010-03-13 10:16 script
drwxr-xr-x 2 root root 4096 2010-03-13 10:16 solar
drwxr-xr-x 2 root root 4096 2010-03-13 10:16 spinfinity
drwxr-xr-x 2 root root 4096 2010-03-13 10:16 text
drwxr-xr-x 2 root root 4096 2010-03-13 10:16 ubuntu-logo

I only use the internal lcd panel of the laptop, no external monitor.

On Mon, 2010-03-15 at 14:18 +0000, Lucazade wrote:

> I only use the internal lcd panel of the laptop, no external monitor.
>
Ok, you should be using the frame-buffer renderer then -- I have no idea
why that isn't working for you

Scott
--
Scott James Remnant
<email address hidden>

I am not sure if I am in the right bug report, I found several similar reports when trying to file a gub with ubuntu-bug. I have an R600 card (Radeon HD3450). KMS has been working fine in Lucid, but the latest update to plymouth killed it (boot up hangs at the plymouth screen). This is Kubuntu lucid:

leo@grisell:~$ dpkg -l |grep plym
ii libplymouth2 0.8.0~-14 graphical boot animation and logger - shared librar
ii plymouth 0.8.0~-14 graphical boot animation and logger - main package
ii plymouth-x11 0.8.0~-14 graphical boot animation and logger - X11 interface

Disabling KMS (in grub) works fine with plymouth, and so does of course removing the "splash" boot option. I can provide any extra information as needed.

Best of all
Leo

On Wed, 2010-03-17 at 01:44 +0000, Leo Milano wrote:

> I am not sure if I am in the right bug report, I found several similar
> reports when trying to file a gub with ubuntu-bug. I have an R600 card
> (Radeon HD3450). KMS has been working fine in Lucid, but the latest
> update to plymouth killed it (boot up hangs at the plymouth screen).
> This is Kubuntu lucid:
>
This is bug #538524 - a fix has just been accepted into lucid for it
(-15)

Scott
--
Scott James Remnant
<email address hidden>

Thanks Scott, and sorry for the misreport.

After today's updates i got a colorful plymouth...
it happens random: on startup or on reboot
http://www.youtube.com/watch?v=SrvKn3G-8Vk