Bug#584204: Both on framebuffer and KMS
Package: plymouth Version: 0.8.3-2 Severity: normal -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages plymouth depends on: ii initramfs-tools 0.94.4 tools for generating an initramfs ii libc6 2.10.2-9 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-4 The Cairo 2D vector graphics libra ii libdrm-intel1 2.4.18-5 Userspace interface to intel-speci ii libdrm-nouveau1 2.4.18-5 Userspace interface to nouveau-spe ii libdrm-radeon12.4.18-5 Userspace interface to radeon-spec ii libdrm2 2.4.18-5 Userspace interface to kernel DRM ii libglib2.0-0 2.24.1-1 The GLib library of C routines ii libpango1.0-0 1.28.0-1 Layout and rendering of internatio ii libpng12-01.2.43-1 PNG library - runtime Versions of packages plymouth recommends: ii plymouth-themes-all 0.8.3-2Graphical Boot Animation and Logge Versions of packages plymouth suggests: pn gdm none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584204: Both on framebuffer and KMS
Sorry for previous report, I thought I cancelled but reportbug sent it anyway... Well, since I better reply now... :) I'm running Debian AMD64 Squeeze with an ATI Radeon x1250 running with the open source module driver. Plymouth works both on framebuffer and KMS, but with the results mentioned in this bug. splash is enabled in the kernel command line, and KMS is started through /etc/modprobe.d/radeon-kms.conf. Boot concurrency mode is default (makefile). I checked boot logs and such, and I can't find anything. Just in case it helps as a tip, I can run Plymouth on KMS straight till kdm on Arch (I use gnome on Debian) with the old Grub. Does the boot process «steal» plymouth's screen? Is this a bug that should be filed against the boot process, or is plymouth missing integration into the new booting? Please, ask for more info if you need, I'll love to get this working :) Regards, -- Omar Campagne Polaino -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
