Re: [gentoo-user] hibernate... /bin/echo: write error: No such device
On Wed, 3 Aug 2022 17:30:54 -0400, Walter Dnes wrote:
> Next we look at file
> /usr/share/hibernate/scriptlets.d/sysfs_power_state which has a short
> function DoSysfsPowerStateSuspend(). Anyone remember ye old dayes of
> FORTRAN, where you'd throw in print statements to debug errors? I've
> added a few debug statements, like so...
>
> DoSysfsPowerStateSuspend() {
> if [ -z "$SYSFS_POWER_STATE_NO_SUSPEND" ] ; then
> vecho 1 "$EXE: Activating sysfs power state
> $USING_SYSFS_POWER_STATE ..." echo "1 ==> $USING_SYSFS_POWER_STATE"
> echo "2 ==> $SYSFS_POWER_STATE_POWERDOWN_METHOD"
> echo "3 ==> $SYSFS_POWERDOWN_METHOD_FILE"
> echo "4 ==> $SYSFS_POWER_STATE_FILE"
> [ -n "$SYSFS_POWER_STATE_POWERDOWN_METHOD" ] && \
> [ -f "$SYSFS_POWERDOWN_METHOD_FILE" ] && \
> /bin/echo $SYSFS_POWER_STATE_POWERDOWN_METHOD >
> $SYSFS_POWERDOWN_METHOD_FILE /bin/echo -n $USING_SYSFS_POWER_STATE >
> $SYSFS_POWER_STATE_FILE else
> vecho 1 "$EXE: Not actually suspending (--no-suspend given)"
> fi
> return 0
> }
>
> The output from hibernate is...
>
> 1 ==> disk
> 2 ==>
> 3 ==> /sys/power/disk
> 4 ==> /sys/power/state
> /bin/echo: write error: No such device
Which call to /bin/echo is failing? Instead of filling the script with
echo statements, add "set -x" near the top, then it will output each line
before executing it. That way you will not only see which echo call has
failed, but you will also see the values of the environments variables in
the call.
--
Neil Bothwick
Nothing is foolproof to a sufficiently talented fool.
pgptwQrkeZTPB.pgp
Description: OpenPGP digital signature
Re: [gentoo-user] hibernate... /bin/echo: write error: No such device
On 2022.08.03 17:30, Walter Dnes wrote:
Checking the obvious; "make menuconfig"...
> Power management and ACPI options
[ ] Suspend to RAM and standby
[*] Hibernation (aka 'suspend to disk')
[*] Userspace snapshot device
(/dev/sda2) Default resume partition
Checking where/how it'll suspend...
cat /sys/power/state
disk
So far, so good. I was ssh'd in and I shrank the font size to
"unreadable" and ran "hibernate --verbosity=4", to get debug level
output. It captured "only" the last 519 lines of output, attached as
errlog.txt.gz which I copy/pasted to vim on my desktop.
Line 305 is where "DoSysfsPowerStateSuspend" starts
Line 317 is the "/bin/echo -n disk" statement
Next we look at file
/usr/share/hibernate/scriptlets.d/sysfs_power_state
which has a short function DoSysfsPowerStateSuspend(). Anyone
remember
ye old dayes of FORTRAN, where you'd throw in print statements to
debug
errors? I've added a few debug statements, like so...
DoSysfsPowerStateSuspend() {
if [ -z "$SYSFS_POWER_STATE_NO_SUSPEND" ] ; then
vecho 1 "$EXE: Activating sysfs power state
$USING_SYSFS_POWER_STATE ..."
echo "1 ==> $USING_SYSFS_POWER_STATE"
echo "2 ==> $SYSFS_POWER_STATE_POWERDOWN_METHOD"
echo "3 ==> $SYSFS_POWERDOWN_METHOD_FILE"
echo "4 ==> $SYSFS_POWER_STATE_FILE"
[ -n "$SYSFS_POWER_STATE_POWERDOWN_METHOD" ] && \
[ -f "$SYSFS_POWERDOWN_METHOD_FILE" ] && \
/bin/echo $SYSFS_POWER_STATE_POWERDOWN_METHOD >
$SYSFS_POWERDOWN_METHOD_FILE
/bin/echo -n $USING_SYSFS_POWER_STATE >
$SYSFS_POWER_STATE_FILE
else
vecho 1 "$EXE: Not actually suspending (--no-suspend given)"
fi
return 0
}
The output from hibernate is...
1 ==> disk
2 ==>
3 ==> /sys/power/disk
4 ==> /sys/power/state
/bin/echo: write error: No such device
No powerdown method? I added "resume=/dev/sda2" to lilo.conf and
re-ran lilo. And now we cross the boundary from the ridiculous to the
totally utterly sublime.
[thimk][root][~] cat /sys/power/state
disk
[thimk][root][~] echo disk > /sys/power/state
-bash: echo: write error: No such device
[thimk][root][~] cat /sys/power/state
disk
WTF!!!
--
Walter Dnes
I don't run "desktop environments"; I run useful applications
No answers, but some thoughts. Remember the files in /sys/power are
not real files, they are created by sysfs (or something relying on
sysfs.) I wonder if something in the sysfstools package will let you
dig into why /sys seems or claims not to be there. The other
possibility is that whatever actual program is trying to do that write
has a bug and is recognizing some other condition as a "no such device"
error, but I suppose your last test disproves that.
Re: [gentoo-user] hibernate... /bin/echo: write error: No such device
Checking the obvious; "make menuconfig"...
> Power management and ACPI options
[ ] Suspend to RAM and standby
[*] Hibernation (aka 'suspend to disk')
[*] Userspace snapshot device
(/dev/sda2) Default resume partition
Checking where/how it'll suspend...
cat /sys/power/state
disk
So far, so good. I was ssh'd in and I shrank the font size to
"unreadable" and ran "hibernate --verbosity=4", to get debug level
output. It captured "only" the last 519 lines of output, attached as
errlog.txt.gz which I copy/pasted to vim on my desktop.
Line 305 is where "DoSysfsPowerStateSuspend" starts
Line 317 is the "/bin/echo -n disk" statement
Next we look at file /usr/share/hibernate/scriptlets.d/sysfs_power_state
which has a short function DoSysfsPowerStateSuspend(). Anyone remember
ye old dayes of FORTRAN, where you'd throw in print statements to debug
errors? I've added a few debug statements, like so...
DoSysfsPowerStateSuspend() {
if [ -z "$SYSFS_POWER_STATE_NO_SUSPEND" ] ; then
vecho 1 "$EXE: Activating sysfs power state $USING_SYSFS_POWER_STATE
..."
echo "1 ==> $USING_SYSFS_POWER_STATE"
echo "2 ==> $SYSFS_POWER_STATE_POWERDOWN_METHOD"
echo "3 ==> $SYSFS_POWERDOWN_METHOD_FILE"
echo "4 ==> $SYSFS_POWER_STATE_FILE"
[ -n "$SYSFS_POWER_STATE_POWERDOWN_METHOD" ] && \
[ -f "$SYSFS_POWERDOWN_METHOD_FILE" ] && \
/bin/echo $SYSFS_POWER_STATE_POWERDOWN_METHOD >
$SYSFS_POWERDOWN_METHOD_FILE
/bin/echo -n $USING_SYSFS_POWER_STATE > $SYSFS_POWER_STATE_FILE
else
vecho 1 "$EXE: Not actually suspending (--no-suspend given)"
fi
return 0
}
The output from hibernate is...
1 ==> disk
2 ==>
3 ==> /sys/power/disk
4 ==> /sys/power/state
/bin/echo: write error: No such device
No powerdown method? I added "resume=/dev/sda2" to lilo.conf and
re-ran lilo. And now we cross the boundary from the ridiculous to the
totally utterly sublime.
[thimk][root][~] cat /sys/power/state
disk
[thimk][root][~] echo disk > /sys/power/state
-bash: echo: write error: No such device
[thimk][root][~] cat /sys/power/state
disk
WTF!!!
--
Walter Dnes
I don't run "desktop environments"; I run useful applications
errlog.txt.gz
Description: application/gzip
Re: [gentoo-user] pulseaudio - pipewire
On Wednesday, 3 August 2022 17:22:13 BST Mark Knecht wrote: > On Wed, Aug 3, 2022 at 9:15 AM hitachi303 > > wrote: > > Hi, > > > > so there is a eselect news "2022-07-29-pipewire-sound-server" telling > > that changes have been made. > > > > I care about having sound but don't care to much about how it is > > working. Any suggestions which path will lead me to the goal of having > > the least trouble in future? > > Like is pulseaudio going to disappear so I will have do switch anyway? > > Is pipewire that new that it'll be buggy for the years to come? > > > > Regards > > Many other distros are using it without major problems. > > Ubuntu still ships PulseAudio for its long term version which is what I use > but I've > not heard of any problems with the leading edge version. I've been using pipewire with default settings and USE="-pulseaudio" in make.conf. It works fine for my basic needs. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] pulseaudio - pipewire
On Wed, Aug 3, 2022 at 9:15 AM hitachi303 wrote: > > Hi, > > so there is a eselect news "2022-07-29-pipewire-sound-server" telling > that changes have been made. > > I care about having sound but don't care to much about how it is > working. Any suggestions which path will lead me to the goal of having > the least trouble in future? > Like is pulseaudio going to disappear so I will have do switch anyway? > Is pipewire that new that it'll be buggy for the years to come? > > Regards Many other distros are using it without major problems. Ubuntu still ships PulseAudio for its long term version which is what I use but I've not heard of any problems with the leading edge version.
Re: [gentoo-user] pulseaudio - pipewire
On Wed, 2022-08-03 at 18:17 +0200, hitachi303 wrote: > I care about having sound but don't care to much about how it is > working. Any suggestions which path will lead me to the goal of having > the least trouble in future? If you're using pulse now and things are working, then stick with pulse. If nothing on your system is dependent on pipewire, you've nothing to gain (right now) from changing. That's my approach, I'm in a similar position of wanting the least friction.
[gentoo-user] pulseaudio - pipewire
Hi, so there is a eselect news "2022-07-29-pipewire-sound-server" telling that changes have been made. I care about having sound but don't care to much about how it is working. Any suggestions which path will lead me to the goal of having the least trouble in future? Like is pulseaudio going to disappear so I will have do switch anyway? Is pipewire that new that it'll be buggy for the years to come? Regards
