Re: Suspend to Disk + blacklisted module = still trouble

[Felix Natter <felix.natter@smail.inf.fh-brs.de>]

Camaleón <noelamac@gmail.com> writes:

> On Sat, 24 Apr 2010 20:33:59 +0200, Felix Natter wrote:
>
>> Camaleón writes:
>> 
>>> What does "/var/log/hibernate.log" say?
>> 
>> /var/log/hibernate* does not exist after a (succesful) resume, although
>> this is in common.conf:
>> 
>> Verbosity 0
>> LogFile /var/log/hibernate.log
>> LogVerbosity 1
>> 
>> Any idea?
>
> Yes, you can increase the log verbosity:
>
> Verbosity 4
> LogFile /var/log/hibernate.log
> LogVerbosity 4
>
> And check that file after suspending/restoring.

from man hibernate.conf:
      Verbosity N
                 Determines  how  verbose  the  output from the suspend script
                 should be: 0: silent except for  errors  1:  print  steps  2:
                 print  steps  in  detail  3: print steps in lots of detail 4:
                 print out every command executed (uses -x)

so verbosity 1 should output something, but I will try 4.

> But if you already got a success resume, why are you in the need of 
> blacklisting modules? :-?

Sometimes, it works, sometimes it doesn't.

Thanks,
-- 
Felix Natter