Radeon KMS disabled with latest kernel update?

[Robert2]

*EDIT* please see below this is not a Kernel or Radeon issue, but a plymouth issue. It just happens to get triggered the moment you install a newer kernel.

Hi,

I just updated from -126 to kernel-2.6.29.3-140.fc11.i586 on a ThinkPad T41 with radeon RV250 and on reboot I now get text mode bootup, instead of graphical.

Looking at the changelog I notice the following

* Wed May 06 2009 Dave Airlie <airlied@redhat.com> 2.6.29.2-129
- drm-next: update with latest patch queue for upstream + intel fixes
- drm-modesetting-radeon.patch: rebase onto drm-next
- drm-nouveau.patch: rebase onto drm-next

* Tue May 05 2009 Dave Airlie <airlied@redhat.com> 2.6.29.2-128
- radeon kms: backport some fixes - put back old internal interface

Is it the intention that the RV250 no longer gets KMS?

get the following in syslog with -126
[drm] Initialized drm 1.1.0 20060810
radeon 0000:01:00.0: power state changed by ACPI to D0
radeon 0000:01:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
[drm] Detected VRAM RAM=32768K, accessible=32768K, BAR=131072K
agpgart-intel 0000:00:00.0: AGP 2.0 bridge
agpgart-intel 0000:00:00.0: putting AGP V2 device into 4x mode
radeon 0000:01:00.0: putting AGP V2 device into 4x mode
[drm] setting agp_base to d0000000
[drm] setting agp_location to d0000000
[drm] DFP table revision: 3
[drm] Panel ID String: SXGA+ Single (85MHz)
[drm] Panel Size 1400x1050
[drm] Default TV standard: NTSC
[drm] 27.000000000 MHz TV ref clk
i2c-adapter i2c-0: unable to read EDID block.
radeon 0000:01:00.0: VGA-1: no EDID data
i2c-adapter i2c-1: unable to read EDID block.
radeon 0000:01:00.0: DVI-D-1: no EDID data
allocated f6758800 1400x1050 fb: 0x00040000, bo f677e180
fbcon: radeondrmfb (fb0) is primary device
Console: switching to colour frame buffer device 175x65
[drm] LVDS-9: set mode 1400x1050 c
fb0: radeondrmfb frame buffer device
registered panic notifier
[drm] Loading R200 Microcode
[drm] writeback test succeeded in 2 usecs
[drm] Initialized radeon 1.29.0 20080528 for 0000:01:00.0 on minor 0


I get the following in syslog with -140
[drm] Initialized drm 1.1.0 20060810
radeon 0000:01:00.0: power state changed by ACPI to D0
radeon 0000:01:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
[drm] Detected VRAM RAM=32768K, accessible=32768K, BAR=131072K
agpgart-intel 0000:00:00.0: AGP 2.0 bridge
agpgart-intel 0000:00:00.0: putting AGP V2 device into 4x mode
radeon 0000:01:00.0: putting AGP V2 device into 4x mode
[drm] setting agp_base to d0000000
[drm] setting agp_location to d0000000
[drm] DFP table revision: 3
[drm] Panel ID String: SXGA+ Single (85MHz)
[drm] Panel Size 1400x1050
[drm] Default TV standard: NTSC
[drm] 27.000000000 MHz TV ref clk
i2c-adapter i2c-0: unable to read EDID block.
radeon 0000:01:00.0: VGA-1: no EDID data
i2c-adapter i2c-1: unable to read EDID block.
radeon 0000:01:00.0: DVI-D-1: no EDID data
allocated f6758800 1400x1050 fb: 0x00040000, bo f677b180
fbcon: radeondrmfb (fb0) is primary device
Console: switching to colour frame buffer device 175x65
[drm] LVDS-9: set mode 1400x1050 e
fb0: radeondrmfb frame buffer device
registered panic notifier
[drm] Loading R200 Microcode
[drm] writeback test succeeded in 2 usecs
[drm] Initialized radeon 1.30.0 20080528 for 0000:01:00.0 on minor 0

The diff between them is
$ diff syslog.126 syslog.140
19c19
< allocated f6758800 1400x1050 fb: 0x00040000, bo f677e180
---
> allocated f6758800 1400x1050 fb: 0x00040000, bo f677b180
22c22
< [drm] LVDS-9: set mode 1400x1050 c
---
> [drm] LVDS-9: set mode 1400x1050 e
27c27
< [drm] Initialized radeon 1.29.0 20080528 for 0000:01:00.0 on minor 0
---
> [drm] Initialized radeon 1.30.0 20080528 for 0000:01:00.0 on minor 0

[XenoPL]

I think KMS works just fine, but last plymouth update killed plug-ins. Go to /usr/share/plymouth and check if there are any plugins left. For me the only one was text and some bitmaps without any plugin file.

[ultra magnus]

Seems that way, I experienced the missing plymouth too. Installing some themes and rebuilding initrd helped.

[Robert2]

It seems your right. When I boot -126 I still get plymouth graphical boot, but obviously that initrd was created prior to the latest plymouth updates.

I had a look in /usr/share/plymouth and I have the following layout

.
|-- default-boot-duration
`-- themes
    |-- charge
    |   |-- progress-00.png
    |   |-- progress-01.png
    |   |-- progress-02.png
    |   |-- progress-03.png
    |   |-- progress-04.png
    |   |-- progress-05.png
    |   |-- progress-06.png
    |   |-- progress-07.png
    |   |-- progress-08.png
    |   |-- progress-09.png
    |   |-- progress-10.png
    |   |-- progress-11.png
    |   |-- progress-12.png
    |   |-- progress-13.png
    |   |-- progress-14.png
    |   |-- progress-15.png
    |   |-- progress-16.png
    |   |-- progress-17.png
    |   |-- progress-18.png
    |   |-- throbber-00.png
    |   |-- throbber-01.png
    |   |-- throbber-02.png
    |   |-- throbber-03.png
    |   |-- throbber-04.png
    |   |-- throbber-05.png
    |   |-- throbber-06.png
    |   |-- throbber-07.png
    |   |-- throbber-08.png
    |   |-- throbber-09.png
    |   |-- throbber-10.png
    |   |-- throbber-11.png
    |   |-- throbber-12.png
    |   |-- throbber-13.png
    |   |-- throbber-14.png
    |   `-- throbber-15.png
    |-- default.plymouth -> text/text.plymouth
    |-- details
    |   `-- details.plymouth
    `-- text
        `-- text.plymouth

So yes it seems that the default has switched to text, and I just had not noticed it until a new kernel update came out which created a new initrd.
So how do I change it back?

[lizardkinger]

I have the same effect with an ATI Radeon X600 Mobile, which uses the radeon driver.

KMS worked very well until yesterday, after I updated to kernel 2.6.29.3

[kr4ey]

Almost same here. Blank screen after reboot with new kernel update. Using ATI driver. Video card is a HD 3300

[cougar618]

Almost same here. Blank screen after reboot with new kernel update. Using ATI driver. Video card is a HD 3300

I have the same issue, with a HD 3850. Boots right up and then monitor is put to sleep instantly. The only way I can use the comp is if I use the previous kernel.

[helloworld1]

The same with intel X4500HD card. If I change back to old kerenl. The graphical plymouth will come back again.

[Zlobniy Shurik]

The same problem with HD4850 (radeon driver)

with kernel 2.6.29.2-126.fc11.x86_64 - normal graphical boot with plymouth.
with kernel 2.6.29.3 - text boot and black screen at the end (no reaction on Ctrl+Alt+Fx)

[Robert2]

XenoPL is right, this has nothing to do with the Kernel, Radeon or Intel graphics card.

The problem is that plymouth is messed up, but since plymouth is put into the initrd which gets generated when you install a new kernel, the problem did not occur with the new plymouth install, but after when you installed a new kernel which in turn generated a new initrd with the broken plymouth.

Booting an older kernel, with an older initrd which still contains a valid plymouth will still work. But the moment you re-generate the initrd (mkinitrd) for the older kernel you will have the same problem.

[leigh123linux]

I believe it's a plymouth bug.

I updated to this version of plymouth

http://koji.fedoraproject.org/koji/b...buildID=102186


and ran

su -
plymouth-set-default-theme spinfinity
/usr/libexec/plymouth/plymouth-update-initrd

It works great now ( I used the solar plugin as the spinfinity look sucks)

[Robert2]

I believe it's a plymouth bug.

I updated to this version of plymouth

http://koji.fedoraproject.org/koji/b...buildID=102186


and ran

su -
plymouth-set-default-theme spinfinity
/usr/libexec/plymouth/plymouth-update-initrd

It works great now ( I used the solar plugin as the spinfinity look sucks)

Thanks leigh123linux, you put me on the correct path, unfortunately it still seems something is broken with spinfinity, as I still got the plymouth text mode theme after a reboot.

After some debugging I found that /usr/share/plymouth/themes/spinfinity/spinfinity.plymouth contains amongst others

[throbgress]
ImageDir=/usr/share/plymouth/themes/throbgress

that directory does not exist and that is probably why it is broken. After changing it to point to /usr/share/plymouth/themes/spinfinity and re-running plymouth-update-initrd it worked.

[Robert2]

I have opened a bugreport on the spinfinity issue

https://bugzilla.redhat.com/show_bug.cgi?id=500994

[mcmackin]

I noticed Koji's collection for plymouth didn't have a plugin-spinfinity package, could this be a problem?

[BassHead]

Just to add another 2p worth. I assume I had spinfinity installed at some point because it's there working on the previous kernels, but the theme was missing. (Re)install the theme then running plymouth-update-initrd, as suggested by leigh123linux, fixed the problem without me having to change anything else.