Quote:
Originally Posted by jefro
Does a normal resume from keyboard also reboot?
|
Hi Jefro,
yes, the behavior with USB wake up was the same
...but I found a solution!
Solution:
I realized the reboot is the result of an not working wake up, beacause of an incomplete hibernation: the
image of the hibernation status was not written, so without the last known status, there's no "wake up" possible, just a reboot with "last known good" settings!
Goal: force the a image-write to ram and to hard disk, maybe swap-partition on hibernate ...
and force a load of the image on wake up.
## show disks to potentially write the hibernate image too ##
Code:
root@NAS:~# lsblk --output NAME,FSTYPE,LABEL,UUID,MODE
NAME FSTYPE LABEL UUID MODE
sda brw-rw----
|-sda1 ext4 1748b395-819b-4356-b2ad-0d2b697199a8 brw-rw----
|-sda2 brw-rw----
|-sda5 ext4 f2a82520-6b55-4a76-b713-204b1655cdd6 brw-rw----
|-sda6 swap 377438db-9374-40a5-8730-0f5827a131ec brw-rw----
|-sda7 ext4 59361bac-5777-49fe-a8f5-8b0cba191153 brw-rw----
`-sda8 ext4 bc2befe7-2381-4302-b61f-9a4ebf2eaddc brw-rw----
sdb brw-rw----
`-sdb1 ext4 Video cd5c5260-e0e7-4cff-a7e5-0180323a1bce brw-rw----
OK, my swap-partition is sda6 and here I can see the UUID which I need for the next step.
The GRUB setting can be edited quite simply with the "GRUB Customizer", and/or set. I did it in the GUI via a VNC session, Not the best tool, but it works...
Code:
apt-get install grub-customizer
I added the "nomodeset"-cmd to grub-config with the UUID of the swap-partition:
https://www.linux-community.de/wp-co...gs-300x224.jpg
## after editing, the actual writing in in to GRUB ##
Code:
root@NAS:~# update-grub
## written in the /boot/grub/grub.cfg after that ##
## cat /boot/grub/grub.cfg ##
Code:
GRUB_CMDLINE_LINUX
acpi_osi=Linux nomodeset resume=UUID=377438db-9374-40a5-8730-0f5827a131ec
## or open the grub.cfg with an editor ##
Code:
...snip
echo 'Linux 4.19.0-13-amd64 loading ...'
linux /boot/vmlinuz-4.19.0-13-amd64 root=UUID=1748b395-819b-4356-b2ad-0d2b697199a8 ro acpi_osi=Linux nomodeset resume=UUID=377438db-9374-40a5-8730-0f5827a131ec
echo 'Initiale Ramdisk loading...'
...snip
## check: is it a actual setting now ##
[CODE]
root@NAS:~# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.19.0-13-amd64 root=UUID=1748b395-819b-4356-b2ad-0d2b697199a8 ro acpi_osi=Linux nomodeset resume=UUID=377438db-9374-40a5-8730-0f5827a131ec
[CODE]
## check more ###
Code:
root@NAS:~# cat /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT="0"
GRUB_TIMEOUT="5"
GRUB_DISTRIBUTOR="`lsb_release -i -s 2> /dev/null || echo Debian`"
GRUB_CMDLINE_LINUX_DEFAULT="nomodeset resume=UUID=377438db-9374-40a5-8730-0f5827a131ec"
GRUB_CMDLINE_LINUX="acpi_osi=Linux nomodeset resume=UUID=377438db-9374-40a5-8730-0f5827a131ec"
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL="console"
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE="640x480"
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID="true"
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
GRUB_DISABLE_SUBMENU="y"
## After editing, now force hibernation via CMD ##
Code:
root@NAS:~# systemctl hibernate
Please see attached pictures, I couldn't found the logs to copy from, so I took screenshots ;-D
System closes programs & some services, writes the image to ram and then to disk and then goes into hibernate.
On start the same thing vice versa...
You'll find you last cmd in the shell, open folders & files in GUI resp. VNC aso.!!!
So, this problem is solved (for me) and I will set it to SOLVED.
Thx for your help & participation
SB