Page 2 of 3
Re: 'suspend' malfunctions on bionic32
Posted: Tue Nov 21, 2023 6:02 pm
by wizard
@mmmrr
@Chelsea80
If mmmrr has a "Mydesk" directory on the desktop, then it is "Friendly-Bionic32" from here: viewtopic.php?t=5188
It is a remaster of Bionic32 that includes many extras including a "suspend" icon on the desktop. In Friendly-Bionic32 the suspend.sh script is located /root/my-applications/bash/.
There are at least 3 suspend commands that I know of and you have to try them on different hardware to see which one works for you.
Here is a script file that includes all 3. You have to open it in Geany to changes commands, comment & uncomment lines as needed. Be sure to make the file executable.
wizard
Re: 'suspend' malfunctions on bionic32
Posted: Tue Nov 21, 2023 6:18 pm
by mmmrr
thanks wizard.
i'll give that a go
in a little while. mm
Re: 'suspend' malfunctions on bionic32
Posted: Tue Nov 21, 2023 10:11 pm
by mmmrr
ok wizard,
here's what geany displayed:
echo -n mem > /sys/power/state #this one works most of the time
#echo -n freeze > /sys/power/state #try this if the first one fails
#sleep 1 && xset dpms force off #try this third
the first one i did not need to try again.
it sleeps, on waking shows correct display,-keyboard, mouse-- is frozen.
the second did the same thing.
the third produced the flashing cursor at start of the next line in terminal.
in each case i copy/pasted/ran the separate command in terminal.
mm
Re: 'suspend' malfunctions on bionic32
Posted: Tue Nov 21, 2023 11:16 pm
by wizard
@mmmrr
Open your menu.lst file in Geany and at the end of the "kernel" line add: acpi=force
-save
-reboot
Try the suspend.sh commands and see it changes anything.
wizard
Re: 'suspend' malfunctions on bionic32
Posted: Wed Nov 22, 2023 2:30 am
by mmmrr
ok wizard, thanks.
i assumed that there would be a single space
with no punctuation before 'acpi=force'
unchanged behaviour with scripts 1 & 2
with 3 new behaviour: the compu slept then
woke up right away on its own with all displays
alive.
naturally the top display was the terminal window
showing that third code. i used the up arrow key
to reinvoke that code then pressed enter.
this time i got a message window. i don't recall
the message but there were 3 choice buttons
at the bottom of the messaage. the middle one
was 'suspend'. i pressed it. compu went to sleep.
pressed start button to wake. showed all displays.
all frozen. hard shtdown .
mm
Re: 'suspend' malfunctions on bionic32
Posted: Wed Nov 22, 2023 3:56 am
by wizard
mm
change: acpi=force to: rdrand=force
wizard
Re: 'suspend' malfunctions on bionic32
Posted: Wed Nov 22, 2023 6:49 am
by mmmrr
wizard
changed acpi=force to rdrand=force.
on reboot
2 slept, froze
3 produced the flashing cursor at start of the next line in terminal
just realized i should rerun 1 in case the menu.lst change has
altered its long-standing behaviour. great that reboot is quick.
i looked at content of /sys/power/state
geany shows 'freeze mem'
mm
Re: 'suspend' malfunctions on bionic32
Posted: Wed Nov 22, 2023 7:30 am
by mmmrr
no edit button, just quotes...
after rdrand=force:
1 = echo -n mem > /sys/power/state
sleeps,wakes frozen
2 = echo -n freeze > /sys/power/state
sleeps,wakes frozen
3 = sleep 1 && xset dpms force off
flashing cursor at start of the next line in terminal
have created empty ext2 partition :
early suggestion that existing install on vfat a poss.issue
have 'plain' bionic 32 on cd. runs well on target.
could install as poss sledge hammer fix!
mm
Re: 'suspend' malfunctions on bionic32
Posted: Wed Nov 22, 2023 1:39 pm
by wizard
mm
My Dell D400 with Pentium M Friendly-Bionic32 is working with menu.lst kernel line:
Code: Select all
kernel /puppyfb32/vmlinuz psubdir=puppyfb32 pmedia=atahd pfix=fsck forcepae acpi=off
NOTE that acpi=off
Then use: sleep 1 && xset dpms force off
Also it works with Friendly-Jammy32 from: viewtopic.php?t=9972
menu.lst kernel line:
Code: Select all
kernel /puppyfb32/vmlinuz psubdir=puppyfb32 pmedia=atahd pfix=fsck forcepae acpi=off
Then use: echo -n mem > /sys/power/state
This is of course subject to:
wizard's rule #12 "All computer hardware is not created equal"
wizard
Re: 'suspend' malfunctions on bionic32
Posted: Wed Nov 22, 2023 4:01 pm
by Phoenix
mmmrr wrote: ↑Tue Nov 21, 2023 3:53 am
thanks phoenix, for posting.
not sure what to make of it.
why might i want disable any on that list?
i chose 'reload'; seemed to
change nothing, including
the contents of 'wakeup'
and the message:
'the file 'wakeup' on the disk is more recent
than the current buffer. do you want to reload it?'
this time i'll try choosing 'overwrite' instead of 'reload'
'overwrite' gives same contents, same message.
....mm
edit1:
i want to turn the fan off in this laptop when i'm not using it,
without turning the machine off.
You may desire to disable these wakeup sources as sometimes you have a device that would otherwise repeatedly wake it up. For example, puppy linux on a USB will repeatedly wake up the system.
Or perhaps you don't like LAN packet wakeup, so you disable that.
Re: 'suspend' malfunctions on bionic32
Posted: Wed Nov 22, 2023 7:25 pm
by mmmrr
thanks, wizard, phoenix.
the grub.cfg for this 'celeron m' [sticker by keyboard]
looks like this:
menuentry "Puppy bionicpup32 8.0" {
insmod fat
search --no-floppy --fs-uuid --set 082A-1B73
echo "Loading vmlinuz"
linux /bionic-rc-a2/vmlinuz pmedia=atahd pdrv=082A-1B73 psubdir=/bionic-rc-a2 pfix=fsck,fsckp TZ=CST6CDT,M3.2.0,M11.1.0
echo "Loading initrd.gz"
initrd /bionic-rc-a2/initrd.gz
where do i find a line starting 'kernel', directing to 'vmlinuz'?
i see --echo "loading vmlinuz"
then --linux /bionic-rc-a2/vmlinuz...etc. is this the target line?
mm
Re: 'suspend' malfunctions on bionic32
Posted: Wed Nov 22, 2023 8:17 pm
by wizard
mm
Ok, this changes everything. You're not using grub4dos, but the grub2 bootloader.
I made assumptons and shouldn't have.
Let's double check that the hardware spec is correct. Run Menu>System>PupSysinfo
Make=Toshiba
model=Satellite M40X
cpu= Celeron(R) M processor 1.50GHz (370)
64-bit capable=no
ram=?
Change your grub2 entry to this:
Code: Select all
linux /bionic-rc-a2/vmlinuz pmedia=atahd pdrv=082A-1B73 psubdir=/bionic-rc-a2 pfix=fsck,fsckp TZ=CST6CDT,M3.2.0,M11.1.0 acpi=off
wizard
Re: 'suspend' malfunctions on bionic32
Posted: Wed Nov 22, 2023 9:14 pm
by mmmrr
hi wizard,
pupsysinfo opens a world of choices.
i start with sys-specs but it doesn't look like yr example.
what do i do after opening pupsysinfo?
thanks, mm
Re: 'suspend' malfunctions on bionic32
Posted: Wed Nov 22, 2023 9:54 pm
by wizard
mm
What I listed are just specs, not an example. just confirm what is listed with pupsysinfo, you should find that info in the mainboard & devices tabs.
wizard
Re: 'suspend' malfunctions on bionic32
Posted: Wed Nov 22, 2023 10:56 pm
by mmmrr
wizard
under mainboard there are six entries:
bios; cpu; dma; dmo; i/o; irq.
under devices, eleven entries,
five of which have arrows indicating sub entries.
i start looking under bios, i know what bios
stands for, i soon realise that if the info i seek
is here it is scattered in some piecemeal way.
profound respect for yr work with friendly.
profound thanks for yr help for me so far.
looking under mainboard and/or devices in
pupsysinfo is not finding me the info we want.
i try help tab in sysinfo, no response in local help.
other button says online forum, where i am.
mm
Re: 'suspend' malfunctions on bionic32
Posted: Wed Nov 22, 2023 11:29 pm
by wizard
mm
Memory>CPU, need this info:
Info on first line =
64bit capable line =
Devices>Memory, need this info:
Total Ram =
wizard
Re: 'suspend' malfunctions on bionic32
Posted: Thu Nov 23, 2023 1:03 am
by mmmrr
wizard
Memory>CPU, need this info:
can't find this entry
under mainboard>cpu
Info on first line =Intel(R) Celeron(R) M processor 1.50GHz
under mainboard >cpu
64bit capable line =64-bit capable: No
Devices>Memory, need this info:
Total Ram =Total RAM: 1497 MB
hope this helps, mm
Re: 'suspend' malfunctions on bionic32
Posted: Thu Nov 23, 2023 2:34 am
by wizard
nn
OK, now we're sure what the hardware is.
Did you try this:
Change your grub2 entry to this:
Code: Select all
linux /bionic-rc-a2/vmlinuz pmedia=atahd pdrv=082A-1B73 psubdir=/bionic-rc-a2 pfix=fsck,fsckp TZ=CST6CDT,M3.2.0,M11.1.0 acpi=off
Note the acpi=off at the end of the line
wizard
Re: 'suspend' malfunctions on bionic32
Posted: Thu Nov 23, 2023 2:47 am
by mmmrr
wizard
will try changing line when back from errands,
couple of hours. thanks.
mm
when i do a comparison of line you suggest
and existing line in my grub.cfg the only difference
i see is adding 'acpi=off' at the end. will do.
am i missing anything?
do i try the three proposed suspend commands again?
mm
Re: 'suspend' malfunctions on bionic32
Posted: Thu Nov 23, 2023 1:03 pm
by wizard
mm
no, that's the only change
do i try the three proposed suspend commands again?
yes, reboot first
wizard
Re: 'suspend' malfunctions on bionic32
Posted: Thu Nov 23, 2023 11:49 pm
by mmmrr
wizard
echo -n mem > /sys/power/state
--bash: echo: write error: Invalid argument
echo -n freeze > /sys/power/state
--screen goes black, compu sounds
like it's still running, will not wake,
needs hard shutdown.
sleep 1 && xset dpms force off
--returns unflashing cursor to start of next line
mm
using an external monitor for ages since laptop
display went bad. might that make a difference?
Re: 'suspend' malfunctions on bionic32
Posted: Fri Nov 24, 2023 3:48 pm
by wizard
mm
echo -n mem > /sys/power/state
--bash: echo: write error: Invalid argument
This one should not have thrown an error, you might try again to be sure.
If that doesn't work I''m out of ideas for Bionic32. Unfortunately, I can't duplicate your error on any of my hardware .
My last suggestion would be to try installing and running Friendly-Jammy32 from here: viewtopic.php?t=9972
wizard
Re: 'suspend' malfunctions on bionic32
Posted: Fri Nov 24, 2023 5:17 pm
by mmmrr
wizard
second try with
echo -n mem > /sys/power/state
gets same: write error invalid argument
thanks for yr persistence
and further suggestion.
mm
Re: 'suspend' malfunctions on bionic32
Posted: Fri Nov 24, 2023 5:57 pm
by amethyst
mmmrr wrote: ↑Fri Nov 24, 2023 5:17 pm
wizard
second try with
echo -n mem > /sys/power/state
gets same: write error invalid argument
thanks for yr persistence
and further suggestion.
mm
Leave the -n out of the command
Re: 'suspend' malfunctions on bionic32
Posted: Fri Nov 24, 2023 6:01 pm
by amethyst
mmmrr wrote: ↑Fri Nov 24, 2023 5:17 pm
wizard
second try with
echo -n mem > /sys/power/state
gets same: write error invalid argument
thanks for yr persistence
and further suggestion.
mm
Leave the -n out of the command and try. Are you running with harddrive? Usb pendrive will not work, I think. This problem can be kernel related too...
Re: 'suspend' malfunctions on bionic32
Posted: Fri Nov 24, 2023 8:33 pm
by mmmrr
amethyst, thanks:
# echo mem > /sys/power/state
bash: echo: write error: Invalid argument
removing -n = same response
running on hard drive
mm
Re: 'suspend' malfunctions on bionic32
Posted: Sat Nov 25, 2023 4:23 am
by amethyst
mmmrr wrote: ↑Fri Nov 24, 2023 8:33 pm
amethyst, thanks:
# echo mem > /sys/power/state
bash: echo: write error: Invalid argument
removing -n = same response
running on hard drive
mm
I'm also using Bionic32 most of the time. Running with ozsouth's kernel 5.4.158, try that. Did you check in BIOS which sleep states are available/activated for your hardware?
Re: 'suspend' malfunctions on bionic32
Posted: Sat Nov 25, 2023 4:48 am
by mmmrr
amethyst
when i'm back on target computer
i'll see what i can see in bios.
some homework re swapping
kernels ahead of me.
mm
Re: 'suspend' malfunctions on bionic32
Posted: Sat Nov 25, 2023 8:03 am
by amethyst
mmmrr wrote: ↑Sat Nov 25, 2023 4:48 am
amethyst
when i'm back on target computer
i'll see what i can see in bios.
some homework re swapping
kernels ahead of me.
mm
Check in /sys/power/state which states are available
Re: 'suspend' malfunctions on bionic32
Posted: Sat Nov 25, 2023 8:09 pm
by mmmrr
amethyst
i cannot find anything in bios regarding sleep states.
in '/sys/power/state/' geany shows 'freeze'.
in menu.lst, geany shows
timeout 0
default 0
title grub2
kernel /boot/grub/i386-pc/core.img rdrand=force
an earlier post referred to /proc/acpi/wakeup,
i looked in /proc/acpi/wakeup:
Device S-state Status Sysfs node
USB1 S3 *disabled pci:0000:00:1d.0
USB2 S3 *disabled pci:0000:00:1d.1
USB3 S3 *disabled pci:0000:00:1d.2
USB4 S3 *disabled pci:0000:00:1d.3
USB7 S3 *disabled pci:0000:00:1d.7
ELAN S0 *disabled pci:0000:06:01.0
MODM S3 *disabled pci:0000:00:1e.3
mm