It seems that starting splashy later in the boot process caused other
problems. After moving splashy script back to init-top, I had not
experienced bug #505270, nor #505291
Also, I solved this bug on some of my machines (others resume perfectly)
by setting 'early writeout' to 'no' in /etc/uswsusp.
On Sun, 2008-10-26 at 21:50 -0400, Eric Doviak wrote:
> Hi Luis, Tim and Yves-Alexis,
[snip]
> Because I'm curious ... What change was made that corrected Splashy's
> behavior?
Tim changed the order at which Splashy is executed during resume to
allow uswsusp to start first.
We will release 0.3.1
Hi Luis, Tim and Yves-Alexis,
I received the notice that the Splashy hibernate bug has been closed,
but I promised to follow up, so I'm writing to follow up.
I just reinstalled and tested Splashy on my Dell Latitude C510. It
works fine now.
Because I'm curious ... What change was made that corre
Hi Yves-Alexis,
I am the person who originally submitted the bug report on Splashy's
troubles with hibernation. I encountered the problem a few months ago
on a Dell Latitude. Shortly thereafter, several other people wrote in
to say that they were experiencing similar difficulties.
At the moment,
I confirm that on all three machines I could test on, this bug is no
longer occuring. All three machines resumed successfully from suspend
and hibernate.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I will try again to reproduce it three machines I have running Debian.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Ok, I fail to reproduce this on at least two boxes, a desktop and a
laptop. In both case, resume from hibernation works perfectly.
Cheers,
--
Yves-Alexis
signature.asc
Description: This is a digitally signed message part
Hi,
I was “assigned” the RC bug as part of BugSprint
(http://wiki.debian.org/BugSprint). Looking at the bug log, it seems
there was a solution back in july, which was implemented in slashy
0.3.12. But this didn't fix the problem.
What is the current status of the bug, and what are the conclusions
Luis Mondesi schreef:
> On Mon, Oct 13, 2008 at 6:13 AM, Tim Dijkstra <[EMAIL PROTECTED]> wrote:
> We tried to fix this in various ways from Splashy's end but we were
> not successful. It looks like uswsusp starts (dfb init) the
> framebuffer again when resuming at boot. Meaning, /sbin/splashy sta
On Mon, Oct 13, 2008 at 6:13 AM, Tim Dijkstra <[EMAIL PROTECTED]> wrote:
> Luis,
>
> Unfortunately I haven't looked at splashy (or any other FOSS project for
> that matter) for a while, but I noticed this bug is RC. The bug log shows
> you've been commenting on it, do you know the status?
>
Hey Ti
Luis,
Unfortunately I haven't looked at splashy (or any other FOSS project for
that matter) for a while, but I noticed this bug is RC. The bug log shows
you've been commenting on it, do you know the status?
grts Tim
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe
Also see 497313. When splashy was installed running under my
custom kernel, initramfs for the stock kernel was not
rebuilt due to that bug.
So when I booted under the stock kernel, splashy never
loaded until after I unlocked the encrypted drives and
normal boot began.
Resume from hibernation wor
Package: splashy
Version: 0.3.10-2
Followup-For: Bug #486400
I also encounter the same problem using either the stock kernel
for 2.6.26 or my own custom kernel when resuming from hibernation.
The normal boot-up splash screen works fine and prompts me for
the passwords to the encrypted
On Wed, Aug 6, 2008 at 1:36 PM, Fabio Pugliese Ornellas
<[EMAIL PROTECTED]> wrote:
> Since you already know exactly what the problem is, please let me know where
> it is, so I won't waste time on something already known. Please drop me an
> email with it, and we keep in touch.
>
Ok, I'll send you
This is a very important bug; if you can get a fix for it, got for it.
I have not been able to do any FOSS work these last weekends. I guess
we will just miss Lenny...
On Fri, Aug 1, 2008 at 2:35 PM, Fabio Pugliese Ornellas
<[EMAIL PROTECTED]> wrote:
> If by any means I can help, please let me kn
If by any means I can help, please let me know. I was about to start
debugging it today...
Fabio Pugliese Ornellas
E-Mail: [EMAIL PROTECTED]
gTalk: [EMAIL PROTECTED]
ICQ: 6516089
MSN: [EMAIL PROTECTED]
WWW: http://ornellas.apanela.com/
On Fri, Aug 1, 2008 at 14:40, Luis Mondesi <[EMAIL PROT
On Aug 1, 2008, at 11:55 AM, "Fabio Pugliese Ornellas" <[EMAIL PROTECTED]
> wrote:
I had a look at uswsusp suspend command (called from within initrd)
and saw that it do interact with the framebuffer and makes some
splash-related initialization. Would'nt that be messing up with
splashy?
I had a look at uswsusp suspend command (called from within initrd) and saw
that it do interact with the framebuffer and makes some splash-related
initialization. Would'nt that be messing up with splashy? Shouldn't its code
get reviewed? Or you are sure the issue is splashy related only?
Fabi
On Aug 1, 2008, at 12:47 AM, "Fabio Pugliese Ornellas" <[EMAIL PROTECTED]
> wrote:
Hello,
I have just tested the newer 0.3.11 version asn my Asus EEE PC 900
still "freezes" if I use uswsusp + splashy, the bug still exists.
If I find time on the following days, I'll post here my findings
Hello,
I have just tested the newer 0.3.11 version asn my Asus EEE PC 900 still
"freezes" if I use uswsusp + splashy, the bug still exists.
If I find time on the following days, I'll post here my findings on the
topic.
Bye.
Fabio Pugliese Ornellas
E-Mail: [EMAIL PROTECTED]
gTalk: [EMAIL PR
This is fixed in Git and it will be released as 0.3.11 shortly.
The debian package for it will follow shortly after that.
On Fri, Jul 25, 2008 at 9:43 AM, Tim Richardson <[EMAIL PROTECTED]> wrote:
> Laptop top users can't really use splashy because of this bug; I'm
> surprised this is not an RC b
Laptop top users can't really use splashy because of this bug; I'm
surprised this is not an RC bug. I wouldn't want this to be in a stable
release because I'm a Debian enthusiast.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: splashy
Version: 0.3.10-2
Followup-For: Bug #486400
splashy works for a normal boot.
it also displays during a suspend to disk (hibernate).
But upon resume, the splash screen appears, and there is some disk
activity, but then the resume just stops. I can get no response from the
machine
Yet another typo! I forgot to send this to Debian Bugs!
Sorry for the double email!
- Eric
Luis Mondesi wrote:
if you pass "splashy" then Splashy won't work. You need to pass
"splash" as a kernel parameter. Is this a typo on this email or are
you actually using this keyword?
Back to the drawin
On Thu, Jul 3, 2008 at 10:39 PM, Eric Doviak <[EMAIL PROTECTED]> wrote:
> Luis Mondesi wrote:
>
> When $resume is not set, does Splashy start from initramfs init-top? Why
> does Splashy starts "late"?
>
> Hi Luis,
>
> I ran some diagnostics using the hack that I sent yesterday.
>
> Specifically, I
Luis Mondesi wrote:
When $resume is not set, does Splashy start from initramfs init-top?
Why does Splashy starts "late"?
Hi Luis,
I ran some diagnostics using the hack that I sent yesterday.
Specifically, I ran "splashy_config -s kubuntusplashy" but I did NOT run
"update-initramfs -u". That
Eric Doviak wrote:
Luis Mondesi wrote:
When $resume is not set, does Splashy start from initramfs init-top?
Why does Splashy starts "late"?
When "$resume" is not set, Splashy does not start from "init-top". It
appears to start from "init-bottom". My guess is that Splashy starts
"late" because
On Jul 3, 2008, at 0:38, Eric Doviak <[EMAIL PROTECTED]> wrote:
Hi Luis,
After days of struggling with the "resume bug," I have finally found
a hack that fixes the problem. It's not ideal, but it squashes the
bug and it provides laptop users with a boot splash without
compromising the qu
Hi Luis,
After days of struggling with the "resume bug," I have finally found a
hack that fixes the problem. It's not ideal, but it squashes the bug and
it provides laptop users with a boot splash without compromising the
quality that desktop users currently enjoy.
Specifically, I started by
On Tue, Jul 1, 2008 at 1:48 AM, Eric Doviak <[EMAIL PROTECTED]> wrote:
> I think I know how to fix this bug. ... Of course, knowing how to fix the
> bug and being able to fix the bug are two totally different things.
>
> If I understand correctly ... When the "vga=791 splash" arguments are passed
>
Just to clarify (in case my previous message was unclear) ...
In the "/usr/share/initramfs-tools/scripts/init-top" file, the lines:
for x in $(cat /proc/cmdline); do
case $x in
single)
SINGLE=true
;;
splash)
SPLASH=true
;;
nosplash)
I think I know how to fix this bug. ... Of course, knowing how to fix
the bug and being able to fix the bug are two totally different things.
If I understand correctly ... When the "vga=791 splash" arguments are
passed to the kernel, some of the first scripts that the initial RAM
disk runs is
Package: splashy
Version: 0.3.10-2
Followup-For: Bug #486400
Maybe I was wrong. I actually disabled splashy altogether for the
moment. I remember that removing splashy from grub but leaving it on in
uswsusp worked. I am not so sure anymore for the combination with
splashy being on in grub but not
This is interesting: Splashy really does work with hibernation!
I have Splashy (almost) completely configured. I left the "splash = y"
line in my /etc/uswsusp.conf file and I set the "vga=791" argument --
but NOT the "splash" argument -- on the kernel line of my
/boot/grub/menu.lst file.
Wh
Marcel Dischinger wrote:
> I have the same issue here. I found that the problem only occurs if
> splashy is activated in grub (add "splash" as a kernel parameter) _and_
> in uswsusp. Then, splashy hangs while resuming from hibernation.
> If I either remove splashy from grub or uswsusp, it works j
On Thu, Jun 26, 2008 at 11:08 AM, Marcel Dischinger <[EMAIL PROTECTED]> wrote:
> Package: splashy
> Version: 0.3.10-2
> Followup-For: Bug #486400
>
> I have the same issue here. I found that the problem only occurs if
> splashy is activated in grub (add "splash"
Package: splashy
Version: 0.3.10-2
Followup-For: Bug #486400
I have the same issue here. I found that the problem only occurs if
splashy is activated in grub (add "splash" as a kernel parameter) _and_
in uswsusp. Then, splashy hangs while resuming from hibernation.
If I either remove sp
Package: splashy
Version: 0.3.10-1
Same problem with my laptop using splashy and uswsusp.
System freezes during resume if splashy is in graphical mode.
If I press F2 in the very early stage of the resume, splashy goes to verbose
mode and the system resumes well from hibernation.
But If I wait too
Package: splashy
Version: 0.3.10-1
Severity: normal
I love watching Splashy's Debian-moreblue theme appear when I start my
computer, but I'd also like to
start my computer.
Splashy works well on a clean boot, but it doesn't allow the computer to resume
from hibernation.
I've tried appending
39 matches
Mail list logo
