path: root/TODO.org

=== ArchSetup Tasks ===

* ArchSetup v0.5
** DONE [#B] Screen Recording Solution
CLOSED: [2024-04-06 Sat 17:22]
*** 2024-04-06 Sat @ 17:22:37 -0500 Added recordnow script using ffmpeg
does everything:
- full screen recording
- all audio
- microphone

base configuration came from combining commands from https://trac.ffmpeg.org/wiki/Capture/Desktop

command is:

ffmpeg -framerate 30 -f x11grab -i :0.0+ -f pulse -i alsa_input.pci-0000_00_1b.0.analog-stereo -ac 1 -f pulse -i alsa_output.pci-0000_00_1b.0.analog-stereo.monitor -ac 2 "$LOCATION/$NAME".mkv

*** 2024-04-06 Sat @ 16:06:49 -0500 Tried OBS, but should try something simpler

** DONE [#B] Setup Virtualbox with ArchBase for Testing
CLOSED: [2024-04-11 Thu 08:49]
** TODO [#B] Fix 2 Errors in Archsetup Fresh Installation
** TODO [#C] No Wallpaper on First Boot
** TODO [#C] Quiet Login of Hostname No Longer Working
I think this is a dangerous thing to mess with and we should remove
** TODO [#B] Add Missing Emacs Dependencies
*** TODO Install Gist
...from the AUR Under Emacs Dependencies
for this particular dependency:
(use-package erc-yank
  :defer 1
  :after erc
  :bind
  (:map erc-mode-map
        ("C-y" . erc-yank)))

*** TODO Add Docker Image for Telega
** TODO [#B] v0.5 Scenario Test & Bugfixes
* ArchSetup v0.6
** TODO [#B] Allow Sleep/Suspend for Framework Laptop
*** Note: kernel parameter for sleep/suspend issue in Framework Laptop
#+BEGIN_QUOTE
Lastly, my findings… after bit of testing and measuring, it appears that with more or less up-to-date software (current linux kernel, systemd, etc.) it evens out (very scientifically measured:) at around 1.2-1.3 percent/hour in s2idle for the above described configuration (mainly 2x16 GB SO-DIMM sticks), independent of the distribution used (i.e. Fedora and NixOS) but with “rtc_cmos.use_acpi_alarm=1” added to the kernel command line (iiuc, which will become the default in a future systemd release thanks to @Mario_Limonciello et al.) and a “powertop --auto-tune” run at boot time. Considering that refreshing memory in sleep/stand-by mode is the main consumer of energy and that soldered memory consumes around 90% less energy (with the obvious caveats, of course) in sleep than non-soldered solutions, this boils down (again, very scientifically measured) to around 0.7/0.8 watts in s2idle, which is a (very) good result, imo. This would be the first laptop with which i’ve been able to achieve acceptable suspend results now that ACPI S3 appears to have gone everywhere. Thanks a bunch, everybody…
#+END_QUOTE
[[https://community.frame.work/t/battery-drain-on-suspend-sleep-with-linux/42395/7][Battery Drain on Suspend/Sleep with Linux - Framework Laptop 13 - Framework Community]]
Captured On: [2024-03-03 Sun 06:16]
*** Note: kernel parameter to solve battery drain with Sleep/Suspend on Framework
#+BEGIN_QUOTE
Adding the kernel parameter acpi_mask_gpe=0x1A has made sleep much closer to desired with decently low battery drain overnight. Still a bit unpredictable with manual suspend where it’ll just decide to wake up instantly for some reason, but once the automatic 15 minute inactivity is hit it seems to sleep with the lid closed.
#+END_QUOTE
[[https://community.frame.work/t/battery-drain-on-suspend-sleep-with-linux/42395/4][Battery Drain on Suspend/Sleep with Linux - Framework Laptop 13 - Framework Community]]
Captured On: [2024-03-03 Sun 06:14]
*** Note: Suspend Then Hibernate for Framework Laptop
#+BEGIN_QUOTE
In /etc/systemd/logind.conf I have the following relevant lines:

HandleLidSwitch=suspend-then-hibernate
HandleLidSwitchExternalPower=suspend-then-hibernate
IdleAction=suspend-then-hibernate

In /etc/systemd/sleep.conf I have these relevant lines:

#AllowSuspendThenHibernate=yes
HibernateDelaySec=720min
The AllowSuspendThenHibernate line is commented out but that is the default so it is fine.


#+END_QUOTE
[[https://community.frame.work/t/tracking-suspend-on-linux-drains-a-lot-of-battery-compared-to-other-laptop/24737/12][[TRACKING] Suspend on linux drains a lot of battery compared to other laptop - Framework Laptop 13 / Linux - Framework Community]]
Captured On: [2024-03-03 Sun 07:14]
** TODO [#B] Graphical Boot and Login
*** TODO SDDM
  then systemctl enable sddm.service
**** Move All Startup Apps to Startdwm and Call Startdwm From Xinitrc
**** 2024-04-02 Tue @ 18:51:04 -0500 xinit-xsession doesn't work
Steps I followed:
install xinit-xsession to run .xinitrc as a session
.xinitrc needs to be executable

**** Note: How to Add 'dwm.desktop' as an SDDM Session
#+BEGIN_QUOTE
In /usr/share/xsessions/ directory I created a dwm.desktop file:

[Desktop Entry]
Encoding=UTF-8
Name=DWM
Comment=Log in using the Dynamic Window Manager
Exec=/usr/local/bin/dwm
Icon=/usr/local/bin/dwm.png
TryExec=/usr/local/bin/dwm
Type=XSession
and in my ~/.xinitrc file I have added these lines:

# DWM Status
dwmstatus 2>&1 >/dev/null &

# Keyboard Layout
setxkbmap -layout us,gr -option grp:alt_caps_toggle &

# Compositor
picom -f &

#Add Wallpaper
nitrogen --restore &

#Execute DWM
exec dwm
Last edited by mikch (2022-05-15 18:11:34)

Offline

#22022-05-15 13:22:36
seth
Member

Registered: 2012-09-03
Posts: 50,327
Please use code tags, https://bbs.archlinux.org/help.php#bbcode

The xinitrc won't be sourced by SDDM, move that stuff (MINUS the "exec dwm"!) to ~/.xprofile

Edit: though it will then also be sourced by plasma.
In doubt create a /usr/local/bin/dwm.sh wrapper and run that instead.
#+END_QUOTE
[[https://bbs.archlinux.org/viewtopic.php?id=276424][[SOLVED]Cannot start DWM properly from SDDM session menu / Newbie Corner / Arch Linux Forums]]
Captured On: [2024-04-02 Tue 17:38]
**** Note: Starting DWM from SDDM
#+BEGIN_QUOTE
As root create a file like this:

$ cat /usr/share/xsessions/dwm.desktop
[Desktop Entry]
Encoding=UTF-8
Name=dwm
Comment=Dynamic window manager
Exec=dwm
Icon=dwm
Type=XSession
with these permissions

$ ls -l /usr/share/xsessions/dwm.desktop
-rw-r--r-- 1 root root 108 Jun 27 17:24 /usr/share/xsessions/dwm.desktop
Optionally rather than executing dwm directly you could execute a shell script instead that writes stdout / stderr to a file for logging purposes.

E.g.

Exec=startdwm
and

$ cat /usr/local/bin/startdwm
#!/bin/sh
echo "$(date): Starting dwn" >> /path/to/logs/$(date +%Y-%m-%d_%H.dwm.log)
dwm >> /path/to/logs/$(date +%Y-%m-%d_%H.dwm.log) 2>&1


$ ls -l /usr/local/bin/startdwm
-rwxr-xr-x 1 root root 204 Sep 19 14:12 /usr/local/bin/startdwm
#+END_QUOTE
[[https://www.reddit.com/r/suckless/comments/jj61py/how_do_i_make_dwm_appear_on_my_display_manager/][(3) How do I make dwm appear on my display manager? (lightDM) : suckless]]
Captured On: [2024-04-02 Tue 17:46]

*** TODO Plymouth
* ArchSetup Backlog
** TODO [#B] ZFS on Root Install
** TODO [#C] Cleanup Dotfiles
The .dotfiles repo has configuration for applications I no longer use.
** TODO [#C] Evaluate Hyprland to Duplicate DWM Workflow
** TODO [#D] Evaluate i3 / Sway to Duplicate DWM Workflows
** TODO [#D] Evaluate Rofi Menus
** TODO [#D] Evaluate Binding the Right Alt Key to Mod4 Using Xmodmap
#+BEGIN_QUOTE
Bind the right Alt key to Mod4
When using Mod4 (the Super/Windows Key) as the MODKEY, it may be equally convenient to have the right Alt key (Alt_R) act as Mod4. This will allow you to perform otherwise awkward keystrokes one-handed, such as zooming with Alt_R+Enter.

First, find out which keycode is assigned to Alt_R:

$ xmodmap -pke | grep Alt_R
Then simply add the following to the startup script (e.g. ~/.xinitrc), changing the keycode 113 if necessary to the result gathered by the previous xmodmap command:

Reassign Alt_R to Super_L:

xmodmap -e "keycode 113 = Super_L"
Make sure X keeps it out of the "mod1" group:

xmodmap -e "remove mod1 = Super_L"
After doing so, any functions that are triggered by the Super_L key press will also be triggered by an Alt_R key press.

Note: There is a #define option in config.h which also allows you to switch the modkey.
#+END_QUOTE
[[https://wiki.archlinux.org/title/Dwm][dwm - ArchWiki]]
Captured On: [2024-04-02 Tue 17:42]
** TODO Add pyenv to archsetup