![]() To do this - just edit /etc/grub.d/10_linux file. Solution is remove from grub $vt_handoff string. Model name: Intel(R) Pentium(R) CPU N3540 2.16GHzįlags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat Initialized Arguments for Method : (1 arguments defined for method invocation)Īrg0: 00000000fe968048 Integer 00000000000000D3ĪCPI Error: Aborting method \_SB.HKEY.DEVT due to previous error (AE_NOT_FOUND) (20210331/psparse-529) No Local Variables are initialized for Method I was also seeing the following ACPI error: ACPI BIOS Error (bug): Could not resolve symbol, AE_NOT_FOUND (20210331/psargs-330) The traces are: WARNING: CPU: 0 PID: 18016 at /var/lib/dkms/nvidia/510.47.03/build/nvidia/nv.c:3935 nv_restore_user_channels 0xce/0xe0 It is easy to know if you've hit the same bug or not, just look for the following stack traces on your dmesg.īecause you are likely shutting down the computer and restarting, you have to look for them in the dmesg of the previous boot as per : journalctl -b-1 ![]() Note that even non graphic stuff like NVIDIA's CUDA/OpenCL package was still breaking things, notably I couldn't suspend after removing the graphics but keeping them, related: PURGE EVERYTHING FROM NVIDIA: uninstall all nvidia packages ( dpkg -l | grep -i nvidia, sudo apt uninstall), and purge their configs as well ( sudo apt purge. Apparently this is broken on some setups and kernels. The 470 driver migrated to systemd method while previous versions relied on Kernel Driver Callback. In case you nuke it, the contents of nvidia.bak are: #!/bin/sh Sudo mv /lib/systemd/system-sleep/nvidia ~/nvidia.bak (tested for several days now, seems to be working) the bug report links to from heroic user humblebee which has workaround: sudo systemctl stop rvice If the display on your Acer Aspire laptop is blank and you are using a. Otherwise, the problem would only happen sometimes, and more commonly after suspending for a few hours. The Acer Aspire One D270 netbook is the first 10-inch Acer netbook to feature a 1. To reproduce the problem easily, I had to disconnect the power cable from my laptop and be on battery only. This started happening to me as soon as I moved to Ubuntu 21.10 on my Lenovo ThinkPad P51 NVIDIA Quadro M1200, and based on kernel traces, it is this exact bug: My duplicated investigation: NOTE: If you have no password set, locking won’t work no matter what you do.Ubuntu 21.10 NVIDIA 470/510 nv_restore_user_channels bug Set idle time to 1 minute and 5 seconds.Ticking 'Quick Power-off in Blank Only Mode' should auto shut down the screen immedaitely if Blank Screen Only is ticked. Set it to “Turn off the monitor(s)” when idle In the advanced tab of xscreensaver there's power management, enable that and set the screen to power down whenever you want.In the “Idle” section in lxqt-powermanagement:.check the box to lock the screen after 0 minutes.If you don’t ever want the screen to lock itself automatically, switch the Automatic Screen Lock switch to off. If Automatic Screen Lock is on, you can change the value in the Automatic Screen Lock Delay drop-down list. ![]() ![]() cycle after 0 minutes (probably unnecessary but it doesn’t hurt) Open the Activities overview and start typing Screen.If you can actually disable the monitor between the blanking and the screensaver starting, you’ll be set. You were on the right track, actually, but had too big of a time gap. I did some looking online and did the following: 1.With the power off, press and hold FN ESC then press the power button. Because of this, I have made an upstream feature request. It can “blank the screen” but all that means is that it basically rewrites the screen with blackness before starting the screensaver or just staying that way if it’s set to blank only.Īdditionally sucky is that lxqt-powermanagement can handle both locking and disabling the screen, but it cannot accomodate multiple actions. The thing that sucks here is that while xscreensaver has some power management features (none of which are actually enabled by default), disabling the screen is not one of them. ![]()
0 Comments
Leave a Reply. |