[RESPONDED] Framework and PopOS

Worst case scenario I can boot from a live disk and mount the encrypted volume and recover my personal data before reinstalling. I’ve done it before - there was some funny business with getting the mount working with LUKS behaving properly, dont totally recall the specifics but I’m sure I can pull it off again if needs be.

Unfortunately I don’t get grub screen. I’m not sure how to drop into it but I’ll start trying that next.

EDIT: Ok I’m in recovery mode. For anyone following this, you can access your hidden grub menu by mashing Escape or Shift during power-on. Source

Gonna quickly back up my data before trying to repair my install. Not sure how to do this without blowing away my home directory.

LAST EDIT: We are back to normal! Recovery partition does a nice refresh of the OS up to latest (21.10 in my case) and kept all user files intact. Huge thanks to @Brunoais and @Levi_Sauerbrei for your help!

4 Likes

For those running PopOS 21.10 with secure boot enabled, was it just a case of re-enabling it after installation?

@Johnny_B If you “shake” the cursor, particularly at the sides of the screen, are you seeing the screen tear just for a second (almost like a second window) on Wayland?

I can confirm the same results, also noted here - PopOS keeps resetting the scaling setting · Issue #1885 · pop-os/pop · GitHub - disabling the HiDPI daemon seems to ensure fractional scaling doesn’t reset.

1 Like

I set scaling at 100%, and installed the gnome tweaks app to scale the font size instead. This works really well for me with a scaling factor of 1.5.

I also set things to use deep sleep and installed the package for fingerprint recognition from this thread, thanks!

The only problem I have is after the laptop sleeps and wakes the trackpad doesn’t work well, goes too fast and gestures stop working, as someone else reported above.

Overall though this is the first time I’ve used popos and I’m really impressed.

1 Like

Hi everyone - quick question regarding deep sleep. After enabling it, what is the expected behavior when closing the laptop lid and then subsequently opening?

Here is what I’ve noticed on my end:

  • I am unable to use the keyboard or trackpad to wake from sleep, and the only way to do so is through pressing the power button.
  • It seems like it is waking up from hibernation instead. All applications are closed and no state is saved. This is what I get from the kernel log though:
...
kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
kernel: PM: hibernation: Registered nosave memory: [mem 0x0009f000-0x000fffff]
...

I can confirm that it is set to deep:

$ cat /sys/power/mem_sleep
s2idle [deep]

I’m also using Pop!_OS. When the power button is pulsing (suspend, in my setup) and I wake my machine, I need to press the power button to bring things back online. When the machine is hibernated, the power button is off, and needs to be pressed to bring things back online. Resumption in either case returns to the state when the machine was suspended - applications and windows all are restored. What do you have the system set to do in the /etc/systemd/sleep.conf and /etc/systemd/logind.conf files? I have mine configured to suspend then hibernate. It looks like your system is trying to hibernate but failing to do so - I could be wrong, however.

Interesting. For me, when opening the lid back up, the power button does not pulse. The sleep.conf and logind.conf files are what came default with Pop_OS!:

// sleep.conf
[Sleep]
#AllowSuspend=yes
#AllowHibernation=yes
#AllowSuspendThenHibernate=yes
#AllowHybridSleep=yes
#SuspendMode=
#SuspendState=mem standby freeze
#HibernateMode=platform shutdown
#HibernateState=disk
#HybridSleepMode=suspend platform shutdown
#HybridSleepState=disk
#HibernateDelaySec=180min
// logind.conf
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#InhibitDelayMaxSec=5
#UserStopDelaySec=10
#HandlePowerKey=poweroff
#HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
#HandleLidSwitch=suspend
#HandleLidSwitchExternalPower=suspend
#HandleLidSwitchDocked=ignore
#HandleRebootKey=reboot
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#RebootKeyIgnoreInhibited=no
#HoldoffTimeoutSec=30s
#IdleAction=ignore
#IdleActionSec=30min
#RuntimeDirectorySize=10%
#RuntimeDirectoryInodes=400k
#RemoveIPC=yes
#InhibitorsMax=8192
#SessionsMax=8192

I’m going to try doing echo mem > /sys/power/state and report back to see if the system can even go into a deep sleep (aka. suspend-to-RAM) state.

If you’re using something like Gnome or KDE, you have to configure power stuff using their settings (they override systemd defaults).

After doing some more digging, it looks like I’m running into the issue here: Unable to wake from sleep

Putting it to sleep using echo mem > /sys/power/state, the power button starts to pulse but I cannot bring it out of sleep. Pressing the power button again makes the LED turn on fully, then off after a second. If I press it again, it looks like it just reboots.

I currently have scaling set to 150% and the tearing is getting annoying. When searching for solutions I found 2 common ways that people have fixed this:

Install xf86-video-intel which I can’t figure out how to do.

Or enable Wayland, but that doesn’t seem to be enabling:

Restarted and it’s still X11:

Here’s my display settings:

Has anyone been able to resolve the tearing at 150% in Pop 21.10?

Did you choose the right gnome session (with wayland) on GDM ?
Changing this config enables this option, but you still need to select it from login screen

3 Likes

Ah, there we go, selected Pop on Wayland from the little gear after clicking on my username and I’m all set now, thanks @fdr !

OK new question, with Wayland, the trackpad has a lot of inertia when scrolling, is there any way to disable this? It would make sense with a touchscreen, but I always end up scrolling past when I wants to stop.

I at least found a way to disable the inertia/kinetic scrolling in Firefox, but it’d be nice to disable it system-wide.

1 Like

I’m getting much better performance from Wayland, it seems to have fixed the issue of media playback above 1080p on an external monitor being super laggy and CPU heavy.

Fractional scaling seems better in terms of apps scaling properly, albeit blurry. I’d like to disable fractional scaling on a per app basis but I havent found a way yet, unfortunately this means apps like Discord are blurry.

I found a related bug for this with VS Code being blurry and it turns out to be related to electron, and should be fixed in an upcoming release.

Ah interesting, thats good to know. Thanks

I can second this, display performance is better on Wayland - not noticing any blurriness with apps. I typically keep video playback at 480/720p since I mostly view videos at 2x+. I had previously found scaling to 200% and then minimizing in app display to 80% to be helpful

Also didn’t need the screen tearing fix on Wayland

@Alex5 probably it’s a bit late to answer, but I had the same problems with touchpad after wake up and disabling PS/2 emulation (or I don’t know how exactly it’s called there) helped. Haven’t had any problems since then