Bug#488094: marked as done (linux-image: splash does not work with uswsusp and X)
Your message dated Thu, 26 Jun 2008 14:09:34 +0200
with message-id <20080626120933.GU7212@baikonur.stro.at>
and subject line Re: Bug#488094: linux-image: splash does not work with uswsusp and X
has caused the Debian Bug report #488094,
regarding linux-image: splash does not work with uswsusp and X
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
488094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=488094
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image
Severity: normal
Hello
I tried to get a splash screen working on two Lenny machines with very
disapointing results.
I can get both splashy and usplash to display as long as the graphics
hardware is not too dodgy. However, for the two machines I use regularly
splash screen cannot be used.
The problem is that resuming with splash screen active locks up the
machine. It is possible to install usplash and resume with the nosplash
option, or edit the initramfs resume scripts to turn off usplash as
suggested in bug 468735. However, this turns off the splash screen in a
very early stage of the boot process.
I also tried splashy. This one needs to have the framebuffer set up
separately, and resume worked with just the framebuffer. It even works
if console is switched fast enough during boot so that the resume does
not happen with splash displayed. Still if I leave the splash screen on
the machine locks up. I use the hibernate option to switch to console so
there should be no difference .. but it does not work.
Since I tried an intel card and a mobile radeon card, usplash and
splashy, it looks like a more general problem. Unless there are so many
bus that no matter what I do I hit a different one ;-)
It would be nice to have this sorted out. It is certainly possible, it
tends to work in Ubuntu.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
On Thu, Jun 26, 2008 at 12:35:49PM +0200, Michal Suchanek wrote:
> Package: linux-image
> Severity: normal
>
>
> Hello
>
> I tried to get a splash screen working on two Lenny machines with very
> disapointing results.
>
> I can get both splashy and usplash to display as long as the graphics
> hardware is not too dodgy. However, for the two machines I use regularly
> splash screen cannot be used.
>
> The problem is that resuming with splash screen active locks up the
> machine. It is possible to install usplash and resume with the nosplash
> option, or edit the initramfs resume scripts to turn off usplash as
> suggested in bug 468735. However, this turns off the splash screen in a
> very early stage of the boot process.
>
> I also tried splashy. This one needs to have the framebuffer set up
> separately, and resume worked with just the framebuffer. It even works
> if console is switched fast enough during boot so that the resume does
> not happen with splash displayed. Still if I leave the splash screen on
> the machine locks up. I use the hibernate option to switch to console so
> there should be no difference .. but it does not work.
>
> Since I tried an intel card and a mobile radeon card, usplash and
> splashy, it looks like a more general problem. Unless there are so many
> bus that no matter what I do I hit a different one ;-)
>
> It would be nice to have this sorted out. It is certainly possible, it
> tends to work in Ubuntu.
right, please debug corresponding pieces.
all of these goodies are userspace stuff,
no kernel bug closing
best regards
--
maks
--- End Message ---
Reply to: