https://discovery.endeavouros.com Explore and own your Endeavour Sun, 06 Sep 2026 16:29:27 +0000 en-US 1.2 https://discovery.endeavouros.com https://discovery.endeavouros.com 1 10 12 11 26 22 20 76 68 7 64 8 71 5 209 72 130 81 58 75 4 138 92 1 57 66 73 3 67 207 60 74 63 77 61 210 184 79 62 42 140 133 173 152 84 39 191 90 34 154 171 33 109 119 211 100 194 155 193 199 142 118 166 95 176 116 229 189 159 143 126 32 38 150 222 41 201 206 111 125 168 106 208 185 186 230 161 107 147 131 225 226 227 174 175 123 110 82 88 179 183 127 86 203 202 167 164 169 108 165 223 187 197 44 135 35 200 151 105 93 144 94 188 204 132 205 198 112 43 40 91 139 37 224 136 83 87 172 114 190 128 122 115 228 120 162 124 157 156 134 160 129 195 196 113 212 85 121 192 178 181 182 141 96 99 97 98 148 149 177 180 146 137 145 101 153 89 36 214 220 219 218 216 217 221 215 213 80nav_menu 30nav_menu 31nav_menu https://wordpress.org/?v=7.1 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-discovery-w-search-wht-bg-4-32x32.png https://discovery.endeavouros.com 32 32 167494005 https://discovery.endeavouros.com/dicovery-logo-dark/ Thu, 19 Sep 2019 13:54:12 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/09/Dicovery-logo-dark.png 5 0 0 0 https://discovery.endeavouros.com/cropped-dicovery-logo-dark-png/ Thu, 19 Sep 2019 13:54:43 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/09/cropped-Dicovery-logo-dark.png 6 0 0 0 cropped-Dicovery-logo-dark.png]]> cropped-Dicovery-logo-dark.png]]> cropped-Dicovery-logo-dark.png]]> cropped-Dicovery-logo-dark.png]]> https://discovery.endeavouros.com/tekening-1/ Tue, 01 Oct 2019 10:02:53 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/tekening-1.png 10 0 0 0 https://discovery.endeavouros.com/cropped-tekening-1-png/ Tue, 01 Oct 2019 10:03:06 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-tekening-1.png 11 0 0 0 cropped-tekening-1.png]]> cropped-tekening-1.png]]> cropped-tekening-1.png]]> cropped-tekening-1.png]]> cropped-tekening-1.png]]> https://discovery.endeavouros.com/discovery-logo-light/ Tue, 01 Oct 2019 10:12:14 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Discovery-logo-light.png 12 0 0 0 https://discovery.endeavouros.com/cropped-discovery-logo-light-png/ Tue, 01 Oct 2019 10:12:56 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-Discovery-logo-light.png 13 0 0 0 cropped-Discovery-logo-light.png]]> cropped-Discovery-logo-light.png]]> cropped-Discovery-logo-light.png]]> cropped-Discovery-logo-light.png]]> https://discovery.endeavouros.com/cropped-discovery-logo-light-1-png/ Tue, 01 Oct 2019 10:13:59 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-Discovery-logo-light-1.png 15 0 0 0 cropped-Discovery-logo-light-1.png]]> cropped-Discovery-logo-light-1.png]]> cropped-Discovery-logo-light-1.png]]> cropped-Discovery-logo-light-1.png]]> cropped-Discovery-logo-light-1.png]]> https://discovery.endeavouros.com/cropped-tekening-1-1-png/ Tue, 01 Oct 2019 10:15:13 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-tekening-1-1.png 16 0 0 0 cropped-tekening-1-1.png]]> cropped-tekening-1-1.png]]> cropped-tekening-1-1.png]]> cropped-tekening-1-1.png]]> https://discovery.endeavouros.com/cropped-discovery-logo-light-2-png/ Tue, 01 Oct 2019 10:21:23 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-Discovery-logo-light-2.png 17 0 0 0 cropped-Discovery-logo-light-2.png]]> cropped-Discovery-logo-light-2.png]]> cropped-Discovery-logo-light-2.png]]> cropped-Discovery-logo-light-2.png]]> https://discovery.endeavouros.com/cropped-discovery-logo-light-3-png/ Tue, 01 Oct 2019 10:22:45 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-Discovery-logo-light-3.png 18 0 0 0 cropped-Discovery-logo-light-3.png]]> cropped-Discovery-logo-light-3.png]]> cropped-Discovery-logo-light-3.png]]> cropped-Discovery-logo-light-3.png]]> https://discovery.endeavouros.com/sea-418742_1920/ Fri, 20 Mar 2015 07:16:29 +0000 https://discovery.endeavouros.com/wp-content/uploads/2015/03/sea-418742_1920.jpg 50 0 0 0 https://discovery.endeavouros.com/cropped-discovery-logo-light-4-png/ Tue, 01 Oct 2019 12:52:52 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-Discovery-logo-light-4.png 56 0 0 0 cropped-Discovery-logo-light-4.png]]> cropped-Discovery-logo-light-4.png]]> cropped-Discovery-logo-light-4.png]]> cropped-Discovery-logo-light-4.png]]> https://discovery.endeavouros.com/discovery-logo-light-2/ Tue, 01 Oct 2019 13:05:21 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Discovery-logo-light-1.png 58 0 0 0 https://discovery.endeavouros.com/cropped-discovery-logo-light-1-1-png/ Tue, 01 Oct 2019 13:06:12 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-Discovery-logo-light-1-1.png 59 0 0 0 cropped-Discovery-logo-light-1-1.png]]> cropped-Discovery-logo-light-1-1.png]]> cropped-Discovery-logo-light-1-1.png]]> cropped-Discovery-logo-light-1-1.png]]> https://discovery.endeavouros.com/discovery-logo-light-3/ Tue, 01 Oct 2019 13:11:35 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Discovery-logo-light-2.png 61 0 0 0 https://discovery.endeavouros.com/cropped-discovery-logo-light-2-1-png/ Tue, 01 Oct 2019 13:12:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-Discovery-logo-light-2-1.png 62 0 0 0 cropped-Discovery-logo-light-2-1.png]]> cropped-Discovery-logo-light-2-1.png]]> cropped-Discovery-logo-light-2-1.png]]> cropped-Discovery-logo-light-2-1.png]]> https://discovery.endeavouros.com/discovery-logo-light-4/ Tue, 01 Oct 2019 13:15:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Discovery-logo-light-3.png 63 0 0 0 https://discovery.endeavouros.com/cropped-discovery-logo-light-3-1-png/ Tue, 01 Oct 2019 13:16:00 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-Discovery-logo-light-3-1.png 64 0 0 0 cropped-Discovery-logo-light-3-1.png]]> cropped-Discovery-logo-light-3-1.png]]> cropped-Discovery-logo-light-3-1.png]]> cropped-Discovery-logo-light-3-1.png]]> https://discovery.endeavouros.com/satelite/ Thu, 03 Oct 2019 13:10:51 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Satelite.png 75 0 0 0 https://discovery.endeavouros.com/cropped-satelite-png/ Thu, 03 Oct 2019 13:11:40 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-Satelite.png 76 0 0 0 https://discovery.endeavouros.com/cropped-discovery-logo-light-3-2-png/ Thu, 03 Oct 2019 13:12:57 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-Discovery-logo-light-3-2.png 78 0 0 0 https://discovery.endeavouros.com/cropped-satelite-2-png/ Fri, 18 Oct 2019 12:49:36 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-Satelite-2.png 82 0 0 0 https://discovery.endeavouros.com/bspwm/ Sat, 19 Oct 2019 12:06:17 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/BSPWM.png 91 0 0 0 https://discovery.endeavouros.com/discovery-w-search-wht-bg/ Sat, 19 Oct 2019 15:55:36 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/discovery-w-search-wht-bg.png 93 0 0 0 https://discovery.endeavouros.com/cropped-discovery-w-search-wht-bg-png/ Sat, 19 Oct 2019 15:56:13 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-discovery-w-search-wht-bg.png 94 0 0 0 https://discovery.endeavouros.com/cardboard_box-1/ Sat, 19 Oct 2019 16:16:56 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cardboard_box-1.jpg 98 0 0 0 https://discovery.endeavouros.com/applications/update-troubles-meet-timeshift/2019/11/attachment/timeshift/ Sat, 19 Oct 2019 16:58:28 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Timeshift.jpg 101 100 0 0 https://discovery.endeavouros.com/applications/update-troubles-meet-timeshift/2019/11/attachment/timeshift1/ Fri, 25 Oct 2019 12:21:36 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Timeshift1.png 103 100 0 0 https://discovery.endeavouros.com/applications/update-troubles-meet-timeshift/2019/11/attachment/timeshift2/ Fri, 25 Oct 2019 12:22:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Timeshift2.png 104 100 0 0 https://discovery.endeavouros.com/applications/update-troubles-meet-timeshift/2019/11/attachment/timeshift6/ Fri, 25 Oct 2019 12:30:17 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Timeshift6.png 105 100 0 0 https://discovery.endeavouros.com/applications/update-troubles-meet-timeshift/2019/11/attachment/timeshift3/ Fri, 25 Oct 2019 12:32:12 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Timeshift3.png 106 100 0 0 https://discovery.endeavouros.com/applications/update-troubles-meet-timeshift/2019/11/attachment/timeshift4/ Fri, 25 Oct 2019 12:39:13 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Timeshift4.png 107 100 0 0 https://discovery.endeavouros.com/applications/update-troubles-meet-timeshift/2019/11/attachment/timeshift7/ Fri, 25 Oct 2019 12:44:23 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Timeshift7.png 108 100 0 0 https://discovery.endeavouros.com/applications/update-troubles-meet-timeshift/2019/11/attachment/timeshift-8/ Fri, 25 Oct 2019 13:51:12 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Timeshift-8.png 111 100 0 0 https://discovery.endeavouros.com/gnome-dash-fix/ Fri, 25 Oct 2019 14:19:33 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Gnome-Dash-fix.png 114 0 0 0 https://discovery.endeavouros.com/tux-united/ Tue, 29 Oct 2019 10:47:34 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Tux-united.png 117 0 0 0 https://discovery.endeavouros.com/ubuntu-logo/ Tue, 29 Oct 2019 13:12:31 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Ubuntu-logo.jpg 122 0 0 0 https://discovery.endeavouros.com/app-image-logo-svg_/ Tue, 29 Oct 2019 14:23:45 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/App-image-logo.svg_.png 123 0 0 0 https://discovery.endeavouros.com/clamav/ Wed, 30 Oct 2019 10:24:33 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/clamav.png 131 0 0 0 https://discovery.endeavouros.com/clamtk/ Wed, 30 Oct 2019 12:43:12 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/clamtk.png 132 0 0 0 https://discovery.endeavouros.com/articles/does-endeavouros-frown-upon-gui-solutions-for-pacman/2019/11/attachment/arch-code/ Wed, 30 Oct 2019 12:47:29 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/arch-code.jpg 135 134 0 0 https://discovery.endeavouros.com/articles/does-endeavouros-frown-upon-gui-solutions-for-pacman/2019/11/attachment/kitchen/ Wed, 30 Oct 2019 18:51:14 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Kitchen.jpg 140 134 0 0 https://discovery.endeavouros.com/image/ Wed, 30 Oct 2019 19:20:26 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/image.png 143 0 0 0 https://discovery.endeavouros.com/image-1/ Wed, 30 Oct 2019 19:21:28 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/image-1.png 144 0 0 0 https://discovery.endeavouros.com/image-2/ Wed, 30 Oct 2019 19:23:18 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/image-2.png 145 0 0 0 https://discovery.endeavouros.com/image-3/ Wed, 30 Oct 2019 19:24:50 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/image-3.png 146 0 0 0 https://discovery.endeavouros.com/image-4/ Wed, 30 Oct 2019 19:26:09 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/image-4.png 147 0 0 0 https://discovery.endeavouros.com/fa97233a7c319532c6ee120b41e5eabaa5827ce2/ Wed, 30 Oct 2019 19:32:43 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/fa97233a7c319532c6ee120b41e5eabaa5827ce2.png 149 0 0 0 https://discovery.endeavouros.com/?attachment_id=151 Wed, 30 Oct 2019 19:44:21 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Nvidia.png 151 150 0 0 https://discovery.endeavouros.com/nvidia-1/ Wed, 30 Oct 2019 19:47:06 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Nvidia-1.png 155 0 0 0 https://discovery.endeavouros.com/intel/ Thu, 31 Oct 2019 08:15:02 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Intel.jpg 159 0 0 0 https://discovery.endeavouros.com/tux-b%e2%81%84w/ Thu, 31 Oct 2019 08:28:49 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/tux-b⁄w.jpg 162 0 0 0 https://discovery.endeavouros.com/sudo/ Thu, 31 Oct 2019 08:37:19 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/sudo.gif 165 0 0 0 https://discovery.endeavouros.com/1200px-gnomelogo-svg_/ Thu, 31 Oct 2019 08:46:28 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/1200px-Gnomelogo.svg_.png 168 0 0 0 https://discovery.endeavouros.com/xhelper-android-malware/ Thu, 31 Oct 2019 09:39:46 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/xhelper-android-malware.jpg 175 0 0 0 https://discovery.endeavouros.com/google-g-word-blue3-1920/ Thu, 31 Oct 2019 09:54:56 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/google-g-word-blue3-1920.jpg 180 0 0 0 https://discovery.endeavouros.com/gitlab-logo/ Thu, 31 Oct 2019 10:01:24 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/GitLab-logo.png 183 0 0 0 https://discovery.endeavouros.com/linux-inside/ Thu, 31 Oct 2019 10:05:34 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/linux-inside.jpg 187 0 0 0 https://discovery.endeavouros.com/chromelogo/ Thu, 31 Oct 2019 10:13:20 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/chromelogo.png 190 0 0 0 https://discovery.endeavouros.com/github1/ Thu, 31 Oct 2019 10:20:53 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/github1.png 193 0 0 0 https://discovery.endeavouros.com/systemd/ Thu, 31 Oct 2019 10:26:55 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/systemd.jpeg 196 0 0 0 https://discovery.endeavouros.com/amd/ Thu, 31 Oct 2019 10:30:04 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/AMD.jpg 200 0 0 0 https://discovery.endeavouros.com/landlock/ Thu, 31 Oct 2019 10:39:27 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Landlock.jpg 205 0 0 0 https://discovery.endeavouros.com/archlabs2017-12/ Thu, 31 Oct 2019 10:48:04 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/archlabs2017.12.png 211 0 0 0 https://discovery.endeavouros.com/pace/ Thu, 31 Oct 2019 14:45:09 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Pace.png 217 0 0 0 https://discovery.endeavouros.com/smartphone/ Thu, 31 Oct 2019 15:11:42 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/smartphone.jpg 221 0 0 0 https://discovery.endeavouros.com/pinta/ Thu, 31 Oct 2019 15:29:24 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/pinta.jpg 222 0 0 0 https://discovery.endeavouros.com/flags/ Thu, 31 Oct 2019 15:39:56 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/Flags.jpg 225 0 0 0 https://discovery.endeavouros.com/gimp-1/ Sat, 02 Nov 2019 07:25:18 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/GIMP-1.jpg 231 0 0 0 https://discovery.endeavouros.com/1200px-kde_logo-svg_/ Sat, 02 Nov 2019 07:48:22 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/1200px-KDE_logo.svg_.png 240 0 0 0 https://discovery.endeavouros.com/wine-logo/ Sat, 02 Nov 2019 07:56:51 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/wine-logo.png 243 0 0 0 https://discovery.endeavouros.com/vivaldi-logo/ Sat, 02 Nov 2019 08:08:29 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/vivaldi-logo.png 246 0 0 0 https://discovery.endeavouros.com/satelite-2/ Sat, 02 Nov 2019 14:09:42 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Satelite.jpg 278 0 0 0 https://discovery.endeavouros.com/cropped-discovery-w-search-wht-bg-1-png/ Sat, 02 Nov 2019 16:51:43 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-discovery-w-search-wht-bg-1.png 284 0 0 0 cropped-discovery-w-search-wht-bg-1.png]]> cropped-discovery-w-search-wht-bg-1.png]]> cropped-discovery-w-search-wht-bg-1.png]]> cropped-discovery-w-search-wht-bg-1.png]]> https://discovery.endeavouros.com/cropped-discovery-w-search-wht-bg-2-png/ Sat, 02 Nov 2019 16:52:51 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-discovery-w-search-wht-bg-2.png 286 0 0 0 cropped-discovery-w-search-wht-bg-2.png]]> cropped-discovery-w-search-wht-bg-2.png]]> cropped-discovery-w-search-wht-bg-2.png]]> cropped-discovery-w-search-wht-bg-2.png]]> https://discovery.endeavouros.com/discovery-logo2/ Sat, 02 Nov 2019 17:14:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Discovery-logo2.png 288 0 0 0 https://discovery.endeavouros.com/discovery-logo2-2/ Sat, 02 Nov 2019 17:15:24 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Discovery-logo2-1.png 289 0 0 0 https://discovery.endeavouros.com/cropped-discovery-logo2-1-png/ Sat, 02 Nov 2019 17:15:55 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/cropped-Discovery-logo2-1.png 290 0 0 0 cropped-Discovery-logo2-1.png]]> cropped-Discovery-logo2-1.png]]> cropped-Discovery-logo2-1.png]]> cropped-Discovery-logo2-1.png]]> https://discovery.endeavouros.com/pengu2560x1600/ Sun, 03 Nov 2019 11:34:44 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Pengu2560x1600.jpg 298 0 0 0 https://discovery.endeavouros.com/snapcraft/ Sun, 03 Nov 2019 13:24:54 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/snapcraft.png 304 0 0 0 https://discovery.endeavouros.com/firefox/ Sun, 03 Nov 2019 15:32:43 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Firefox.jpeg 306 0 0 0 https://discovery.endeavouros.com/eos-shadow/ Sun, 03 Nov 2019 16:20:37 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/EOS-shadow.jpeg 308 0 0 0 https://discovery.endeavouros.com/linux_tux_penguins_1600x1200_w_1920x1200_/ Mon, 04 Nov 2019 09:07:19 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/linux_tux_penguins_1600x1200_w_1920x1200_.jpg 319 0 0 0 https://discovery.endeavouros.com/darktable-logo/ Mon, 04 Nov 2019 09:31:33 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/darktable-logo.jpg 331 0 0 0 https://discovery.endeavouros.com/bauh/ Mon, 04 Nov 2019 12:45:11 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Bauh.png 337 0 0 0 https://discovery.endeavouros.com/edge-logo/ Wed, 06 Nov 2019 12:32:50 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Edge-logo.png 342 0 0 0 https://discovery.endeavouros.com/shadow-of-the-tomb-raider/ Wed, 06 Nov 2019 12:47:46 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Shadow-of-the-tomb-raider.jpg 345 0 0 0 https://discovery.endeavouros.com/gnulinux-logo/ Wed, 06 Nov 2019 12:54:49 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/gnulinux-logo.png 348 0 0 0 https://discovery.endeavouros.com/97926/ Wed, 06 Nov 2019 13:06:03 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/97926.jpg 351 0 0 0 https://discovery.endeavouros.com/openinvention/ Wed, 06 Nov 2019 13:20:18 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/openinvention.png 356 0 0 0 https://discovery.endeavouros.com/earth-from-space/ Thu, 07 Nov 2019 14:28:48 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Earth-from-space.jpg 371 0 0 0 https://discovery.endeavouros.com/libre-office4/ Thu, 07 Nov 2019 19:11:59 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/libre-office4.png 374 0 0 0 https://discovery.endeavouros.com/cropped-discovery-w-search-wht-bg-3-png/ Fri, 08 Nov 2019 09:24:40 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-discovery-w-search-wht-bg-3.png 382 0 0 0 cropped-discovery-w-search-wht-bg-3.png]]> cropped-discovery-w-search-wht-bg-3.png]]> cropped-discovery-w-search-wht-bg-3.png]]> cropped-discovery-w-search-wht-bg-3.png]]> cropped-discovery-w-search-wht-bg-3.png]]> https://discovery.endeavouros.com/cropped-discovery-logo2-1-1-png/ Fri, 08 Nov 2019 09:27:28 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/cropped-Discovery-logo2-1-1.png 383 0 0 0 cropped-Discovery-logo2-1-1.png]]> cropped-Discovery-logo2-1-1.png]]> cropped-Discovery-logo2-1-1.png]]> https://discovery.endeavouros.com/logo-gnome-1/ Fri, 08 Nov 2019 09:56:15 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Logo-GNOME-1.jpg 385 0 0 0 https://discovery.endeavouros.com/xfce-4-16-1/ Fri, 08 Nov 2019 18:09:53 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/XFCE-4.16-1.jpg 389 0 0 0 https://discovery.endeavouros.com/xfce-4-16-2/ Fri, 08 Nov 2019 18:11:10 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/XFCE-4.16-2.jpg 390 0 0 0 https://discovery.endeavouros.com/xfce-4-16-3/ Fri, 08 Nov 2019 18:11:35 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/XFCE-4.16-3.jpg 391 0 0 0 https://discovery.endeavouros.com/xfce_logo-lnx_tytobn/ Fri, 08 Nov 2019 18:15:05 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Xfce_logo-lnx_tytobn.png 392 0 0 0 https://discovery.endeavouros.com/birds-cold-fog-4037-825x550/ Fri, 13 Mar 2015 11:33:44 +0000 https://discovery.endeavouros.com/wp-content/uploads/2015/03/birds-cold-fog-4037-825x550.jpeg 395 0 0 0 https://discovery.endeavouros.com/adventure-forest-nature-4029-824x550/ Fri, 13 Mar 2015 11:37:52 +0000 https://discovery.endeavouros.com/wp-content/uploads/2015/03/adventure-forest-nature-4029-824x550.jpeg 396 0 0 0 https://discovery.endeavouros.com/curve-hills-mountains-4033-821x550/ Fri, 13 Mar 2015 11:39:49 +0000 https://discovery.endeavouros.com/wp-content/uploads/2015/03/curve-hills-mountains-4033-821x550.jpeg 397 0 0 0 https://discovery.endeavouros.com/forest-nature-snow-4058-824x550/ Fri, 13 Mar 2015 11:39:54 +0000 https://discovery.endeavouros.com/wp-content/uploads/2015/03/forest-nature-snow-4058-824x550.jpeg 398 0 0 0 https://discovery.endeavouros.com/idyllic-lake-landscape-4062-824x550/ Fri, 13 Mar 2015 11:39:57 +0000 https://discovery.endeavouros.com/wp-content/uploads/2015/03/idyllic-lake-landscape-4062-824x550.jpeg 399 0 0 0 https://discovery.endeavouros.com/imac-1500_750/ Fri, 20 Mar 2015 05:55:43 +0000 https://discovery.endeavouros.com/wp-content/uploads/2015/03/imac-1500_750.jpg 401 0 0 0 https://discovery.endeavouros.com/office-620817_1920/ Fri, 20 Mar 2015 06:12:54 +0000 https://discovery.endeavouros.com/wp-content/uploads/2015/03/office-620817_1920.jpg 402 0 0 0 https://discovery.endeavouros.com/solar-eclipse-152834_1280/ Tue, 24 Mar 2015 09:43:22 +0000 https://discovery.endeavouros.com/wp-content/uploads/2015/03/solar-eclipse-152834_1280.png 417 0 0 0 https://discovery.endeavouros.com/coffee-563797_1280/ Tue, 24 Mar 2015 09:48:59 +0000 https://discovery.endeavouros.com/wp-content/uploads/2015/03/coffee-563797_1280.jpg 418 0 0 0 https://discovery.endeavouros.com/headphones-15600_1280/ Tue, 24 Mar 2015 11:11:29 +0000 https://discovery.endeavouros.com/wp-content/uploads/2015/03/headphones-15600_1280.jpg 425 0 0 0 https://discovery.endeavouros.com/cropped-sea-418742_1920-jpg/ Mon, 30 Mar 2015 06:57:42 +0000 https://discovery.endeavouros.com/wp-content/uploads/2015/03/cropped-sea-418742_1920.jpg 433 0 0 0 cropped-sea-418742_1920.jpg]]> cropped-sea-418742_1920.jpg]]> cropped-sea-418742_1920.jpg]]> cropped-sea-418742_1920.jpg]]> https://discovery.endeavouros.com/cropped-discovery-logo2-1-2-png/ Fri, 08 Nov 2019 19:07:05 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/cropped-Discovery-logo2-1-2.png 497 0 0 0 cropped-Discovery-logo2-1-2.png]]> cropped-Discovery-logo2-1-2.png]]> cropped-Discovery-logo2-1-2.png]]> cropped-Discovery-logo2-1-2.png]]> cropped-Discovery-logo2-1-2.png]]> https://discovery.endeavouros.com/cropped-tekening-1-2-png/ Fri, 08 Nov 2019 19:08:13 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-tekening-1-2.png 499 0 0 0 cropped-tekening-1-2.png]]> cropped-tekening-1-2.png]]> cropped-tekening-1-2.png]]> cropped-tekening-1-2.png]]> https://discovery.endeavouros.com/cropped-discovery-logo2-1-3-png/ Fri, 08 Nov 2019 19:23:25 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/cropped-Discovery-logo2-1-3.png 501 0 0 0 cropped-Discovery-logo2-1-3.png]]> cropped-Discovery-logo2-1-3.png]]> cropped-Discovery-logo2-1-3.png]]> cropped-Discovery-logo2-1-3.png]]> https://discovery.endeavouros.com/cropped-tekening-1-3-png/ Fri, 08 Nov 2019 19:57:48 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-tekening-1-3.png 506 0 0 0 cropped-tekening-1-3.png]]> cropped-tekening-1-3.png]]> cropped-tekening-1-3.png]]> cropped-tekening-1-3.png]]> https://discovery.endeavouros.com/steam_stats-0/ Sat, 09 Nov 2019 08:51:44 +0000 https://discovery.endeavouros.com/wp-content/uploads/steam_stats.0.jpg 550 0 0 0 https://discovery.endeavouros.com/screenshot-bin-bash1/ Sat, 09 Nov 2019 13:12:46 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Screenshot-bin-bash1.png 557 0 0 0 https://discovery.endeavouros.com/microsoft-loves-linux/ Tue, 12 Nov 2019 11:23:37 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Microsoft-loves-linux.jpg 569 0 0 0 https://discovery.endeavouros.com/kde-plasma/ Tue, 12 Nov 2019 11:47:16 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/KDE-plasma.jpg 572 0 0 0 https://discovery.endeavouros.com/persepolis/ Tue, 12 Nov 2019 12:43:23 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Persepolis.jpg 578 0 0 0 https://discovery.endeavouros.com/persepolis-screenshot/ Tue, 12 Nov 2019 15:03:51 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Persepolis-screenshot.jpeg 581 0 0 0 https://discovery.endeavouros.com/persepolis-screenshot-2/ Tue, 12 Nov 2019 15:04:16 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Persepolis-screenshot-2.gif 582 0 0 0 https://discovery.endeavouros.com/cropped-discovery-w-search-wht-bg-4-png/ Wed, 13 Nov 2019 00:31:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-discovery-w-search-wht-bg-4.png 596 0 0 0 cropped-discovery-w-search-wht-bg-4.png]]> cropped-discovery-w-search-wht-bg-4.png]]> cropped-discovery-w-search-wht-bg-4.png]]> cropped-discovery-w-search-wht-bg-4.png]]> https://discovery.endeavouros.com/brave-browser/ Wed, 13 Nov 2019 16:34:29 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/brave-browser.jpg 604 0 0 0 https://discovery.endeavouros.com/opera-browser/ Thu, 14 Nov 2019 16:56:24 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/opera-browser.jpg 611 0 0 0 https://discovery.endeavouros.com/teachertenure/ Thu, 14 Nov 2019 17:25:38 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/teachertenure.jpg 614 0 0 0 https://discovery.endeavouros.com/2019-las-hero/ Fri, 15 Nov 2019 09:25:29 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/2019-LAS-hero.jpg 622 0 0 0 https://discovery.endeavouros.com/857895/ Tue, 19 Nov 2019 21:13:54 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/857895.jpg 635 0 0 0 https://discovery.endeavouros.com/screenshot_2019-11-26_15-03-11/ Tue, 26 Nov 2019 21:05:55 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Screenshot_2019-11-26_15-03-11.png 645 0 0 0 https://discovery.endeavouros.com/screenshot_2019-11-26_15-13-22/ Tue, 26 Nov 2019 21:15:20 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Screenshot_2019-11-26_15-13-22.png 646 0 0 0 https://discovery.endeavouros.com/screenshot_2019-11-26_15-16-20/ Tue, 26 Nov 2019 21:18:12 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Screenshot_2019-11-26_15-16-20.png 647 0 0 0 https://discovery.endeavouros.com/screenshot_2019-11-26_15-21-26/ Tue, 26 Nov 2019 21:23:15 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Screenshot_2019-11-26_15-21-26.png 648 0 0 0 https://discovery.endeavouros.com/photo_2019-09-17_01-29-06/ Tue, 26 Nov 2019 21:58:09 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/photo_2019-09-17_01-29-06.jpg 649 0 0 0 https://discovery.endeavouros.com/photo_2019-11-26_16-02-06/ Tue, 26 Nov 2019 22:04:21 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/photo_2019-11-26_16-02-06.jpg 650 0 0 0 https://discovery.endeavouros.com/screenshot_2019-11-26_16-22-21/ Tue, 26 Nov 2019 22:24:28 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/Screenshot_2019-11-26_16-22-21.png 651 0 0 0 https://discovery.endeavouros.com/photo_2019-10-20_16-46-17/ Wed, 27 Nov 2019 02:50:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/photo_2019-10-20_16-46-17.jpg 654 0 0 0 https://discovery.endeavouros.com/virtualbox_logo/ Tue, 03 Dec 2019 09:29:33 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/Virtualbox_logo.png 663 0 0 0 https://discovery.endeavouros.com/1200px-thunderbird_logo_2018-svg/ Wed, 04 Dec 2019 16:22:58 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/1200px-Thunderbird_Logo_2018.svg_.png 673 0 0 0 https://discovery.endeavouros.com/theqtcompany_logo_1200x630/ Wed, 04 Dec 2019 18:57:35 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/TheQtCompany_logo_1200x630.png 677 0 0 0 https://discovery.endeavouros.com/171205-hacking-experts-beginning-feature/ Fri, 06 Dec 2019 10:34:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/171205-hacking-experts-beginning-feature.jpg 681 0 0 0 https://discovery.endeavouros.com/europol-1200/ Fri, 06 Dec 2019 10:55:19 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/europol-1200.jpg 684 0 0 0 https://discovery.endeavouros.com/privacy-security-lock-ss-1920/ Sun, 08 Dec 2019 10:12:53 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/privacy-security-lock-ss-1920.jpg 693 0 0 0 https://discovery.endeavouros.com/duck-duck-go/ Sun, 08 Dec 2019 12:11:28 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/Duck-duck-go.jpg 694 0 0 0 https://discovery.endeavouros.com/qwant/ Sun, 08 Dec 2019 12:14:20 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/Qwant.png 695 0 0 0 https://discovery.endeavouros.com/startpage/ Sun, 08 Dec 2019 12:26:31 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/Startpage.jpg 696 0 0 0 https://discovery.endeavouros.com/swisscows/ Sun, 08 Dec 2019 12:31:11 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/Swisscows.jpg 697 0 0 0 https://discovery.endeavouros.com/searx/ Sun, 08 Dec 2019 12:38:03 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/SearX.jpg 698 0 0 0 https://discovery.endeavouros.com/peekier-best_privacy-oriented-search-engines/ Sun, 08 Dec 2019 12:40:04 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/peekier-best_privacy-oriented-search-engines.jpg 699 0 0 0 https://discovery.endeavouros.com/metager/ Sun, 08 Dec 2019 12:45:17 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/MetaGer.png 700 0 0 0 https://discovery.endeavouros.com/giburu/ Sun, 08 Dec 2019 12:48:28 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/Giburu.jpg 701 0 0 0 https://discovery.endeavouros.com/ecosia/ Sun, 08 Dec 2019 12:51:35 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/Ecosia.png 702 0 0 0 https://discovery.endeavouros.com/salute/ Sun, 08 Dec 2019 13:25:31 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/Salute.jpg 706 0 0 0 https://discovery.endeavouros.com/condres_os/ Sun, 08 Dec 2019 14:32:35 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/condres_os.png 707 0 0 0 https://discovery.endeavouros.com/screenshot_2019-12-08_17-27-42/ Sun, 08 Dec 2019 23:30:20 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/Screenshot_2019-12-08_17-27-42.png 712 0 0 0 https://discovery.endeavouros.com/plasma-emoji/ Mon, 09 Dec 2019 11:23:35 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/plasma-emoji.jpg 721 0 0 0 https://discovery.endeavouros.com/antergosblack_by_decluttermind-d87lw0v/ Mon, 09 Dec 2019 12:11:42 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/antergosblack_by_decluttermind-d87lw0v.png 724 0 0 0 https://discovery.endeavouros.com/microsoft-teams/ Wed, 11 Dec 2019 11:09:49 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/Microsoft-teams.png 734 0 0 0 https://discovery.endeavouros.com/microsoft-teams-2/ Wed, 11 Dec 2019 11:17:55 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/microsoft-teams.jpg 735 0 0 0 https://discovery.endeavouros.com/screenshot_2019-12-21_17-25-11/ Sat, 21 Dec 2019 23:25:59 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/Screenshot_2019-12-21_17-25-11.png 753 0 0 0 https://discovery.endeavouros.com/zstandard-hero/ Fri, 27 Dec 2019 12:47:42 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/ZStandard-Hero.jpg 759 0 0 0 https://discovery.endeavouros.com/zstandard2/ Fri, 27 Dec 2019 12:48:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/ZStandard2.png 760 0 0 0 https://discovery.endeavouros.com/libreoffice1020/ Fri, 27 Dec 2019 14:56:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/12/LibreOffice1020.png 765 0 0 0 https://discovery.endeavouros.com/covid-19-main-image/ Tue, 24 Mar 2020 10:01:02 +0000 https://discovery.endeavouros.com/wp-content/uploads/2020/03/COVID-19-MAIN-IMAGE.jpg 816 0 0 0 https://discovery.endeavouros.com/who2x/ Tue, 24 Mar 2020 10:10:37 +0000 https://discovery.endeavouros.com/wp-content/uploads/2020/03/WHO@2x.png 819 0 0 0 https://discovery.endeavouros.com/people/ Mon, 30 Mar 2020 08:14:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2020/03/People.jpg 834 0 0 0 https://discovery.endeavouros.com/flag_of_arch_dark_grey_scale_by_karl_schneider_dbtz6wd/ Mon, 30 Mar 2020 11:05:46 +0000 https://discovery.endeavouros.com/wp-content/uploads/2020/03/flag_of_arch_dark_grey_scale_by_karl_schneider_dbtz6wd.png 838 0 0 0 https://discovery.endeavouros.com/xorg-logo/ Mon, 30 Mar 2020 13:26:44 +0000 https://discovery.endeavouros.com/wp-content/uploads/2020/03/Xorg-logo.png 841 0 0 0 https://discovery.endeavouros.com/wg/ Tue, 31 Mar 2020 08:47:44 +0000 https://discovery.endeavouros.com/wp-content/uploads/2020/03/wg.jpeg 845 0 0 0 https://discovery.endeavouros.com/fx_design_blog_header_1400x770/ Tue, 31 Mar 2020 10:02:12 +0000 https://discovery.endeavouros.com/wp-content/uploads/2020/03/FX_Design_Blog_Header_1400x770.jpg 850 0 0 0 https://discovery.endeavouros.com/articles/root-partition-full-dont-panic-clear-pacmans-cache-first/2020/03/attachment/backlight_arch_by_karl_schneider_dazk2ky/ Tue, 31 Mar 2020 13:36:06 +0000 https://discovery.endeavouros.com/wp-content/uploads/2020/03/backlight_arch_by_karl_schneider_dazk2ky.jpg 853 852 0 0 https://discovery.endeavouros.com/800px-brown_bluff-2016-tabarin_peninsula-gentoo_penguin_pygoscelis_papua_03/ Sun, 26 Jul 2020 17:11:48 +0000 https://discovery.endeavouros.com/wp-content/uploads/2020/07/800px-Brown_Bluff-2016-Tabarin_Peninsula–Gentoo_penguin_Pygoscelis_papua_03.jpg 899 0 0 0 https://discovery.endeavouros.com/?attachment_id=905 Mon, 27 Jul 2020 22:13:02 +0000 https://discovery.endeavouros.com/wp-content/uploads/2020/07/Screenshot_2020-07-27_17-11-47.png 905 904 0 0 https://discovery.endeavouros.com/cropped-cropped-discovery-w-search-wht-bg-3-png/ Tue, 09 Mar 2021 08:41:29 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-cropped-discovery-w-search-wht-bg-3.png 968 0 0 0 cropped-cropped-discovery-w-search-wht-bg-3.png]]> cropped-cropped-discovery-w-search-wht-bg-3.png]]> cropped-cropped-discovery-w-search-wht-bg-3.png]]> https://discovery.endeavouros.com/cropped-cropped-discovery-w-search-wht-bg-png/ Tue, 09 Mar 2021 09:00:32 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-cropped-discovery-w-search-wht-bg.png 974 0 0 0 cropped-cropped-discovery-w-search-wht-bg.png]]> cropped-cropped-discovery-w-search-wht-bg.png]]> cropped-cropped-discovery-w-search-wht-bg.png]]> cropped-cropped-discovery-w-search-wht-bg.png]]> https://discovery.endeavouros.com/cropped-cropped-cropped-discovery-w-search-wht-bg-png/ Tue, 09 Mar 2021 10:49:36 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-cropped-cropped-discovery-w-search-wht-bg.png 995 0 0 0 cropped-cropped-cropped-discovery-w-search-wht-bg.png]]> cropped-cropped-cropped-discovery-w-search-wht-bg.png]]> cropped-cropped-cropped-discovery-w-search-wht-bg.png]]> https://discovery.endeavouros.com/cropped-cropped-cropped-discovery-w-search-wht-bg-3-png/ Tue, 09 Mar 2021 11:59:39 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-cropped-cropped-discovery-w-search-wht-bg-3.png 1021 0 0 0 cropped-cropped-cropped-discovery-w-search-wht-bg-3.png]]> cropped-cropped-cropped-discovery-w-search-wht-bg-3.png]]> cropped-cropped-cropped-discovery-w-search-wht-bg-3.png]]> https://discovery.endeavouros.com/cropped-discovery-logo2-1-4-png/ Tue, 09 Mar 2021 12:00:28 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/cropped-Discovery-logo2-1-4.png 1023 0 0 0 cropped-Discovery-logo2-1-4.png]]> cropped-Discovery-logo2-1-4.png]]> cropped-Discovery-logo2-1-4.png]]> https://discovery.endeavouros.com/cropped-cropped-discovery-logo2-1-4-png/ Tue, 09 Mar 2021 12:04:21 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/cropped-cropped-Discovery-logo2-1-4.png 1024 0 0 0 cropped-cropped-Discovery-logo2-1-4.png]]> cropped-cropped-Discovery-logo2-1-4.png]]> cropped-cropped-Discovery-logo2-1-4.png]]> cropped-cropped-Discovery-logo2-1-4.png]]> https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-discovery-w-search-wht-bg-png/ Tue, 09 Mar 2021 12:07:05 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-cropped-cropped-cropped-discovery-w-search-wht-bg.png 1026 0 0 0 cropped-cropped-cropped-cropped-discovery-w-search-wht-bg.png]]> cropped-cropped-cropped-cropped-discovery-w-search-wht-bg.png]]> cropped-cropped-cropped-cropped-discovery-w-search-wht-bg.png]]> cropped-cropped-cropped-cropped-discovery-w-search-wht-bg.png]]> https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-discovery-w-search-wht-bg-png/ Tue, 09 Mar 2021 12:08:25 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-cropped-cropped-cropped-cropped-discovery-w-search-wht-bg.png 1027 0 0 0 cropped-cropped-cropped-cropped-cropped-discovery-w-search-wht-bg.png]]> cropped-cropped-cropped-cropped-cropped-discovery-w-search-wht-bg.png]]> cropped-cropped-cropped-cropped-cropped-discovery-w-search-wht-bg.png]]> https://discovery.endeavouros.com/home/attachment/arm-a7-640x353/ Tue, 09 Mar 2021 16:37:04 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/arm-a7-640x353-1.jpg 1058 32 0 0 https://discovery.endeavouros.com/home/attachment/endeavour_1/ Tue, 09 Mar 2021 16:47:50 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/endeavour_1.jpg 1059 32 0 0 https://discovery.endeavouros.com/home/attachment/endeavour_3/ Tue, 09 Mar 2021 16:49:53 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/endeavour_3.jpg 1060 32 0 0 https://discovery.endeavouros.com/home/attachment/gnome-keyring/ Tue, 09 Mar 2021 17:10:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/Gnome-keyring.jpg 1061 32 0 0 https://discovery.endeavouros.com/home/attachment/linux-sudo/ Tue, 09 Mar 2021 17:14:02 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/linux-sudo.png 1062 32 0 0 https://discovery.endeavouros.com/home/attachment/546187/ Tue, 09 Mar 2021 17:51:19 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/546187.jpg 1069 32 0 0 https://discovery.endeavouros.com/home/attachment/movie-theatre/ Tue, 09 Mar 2021 18:56:28 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/Movie-theatre.jpg 1076 32 0 0 https://discovery.endeavouros.com/discovery-w-search-transparent/ Thu, 11 Mar 2021 16:10:38 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/discovery-w-search-transparent.png 1117 0 0 0 https://discovery.endeavouros.com/cropped-discovery-w-search-transparent-png/ Thu, 11 Mar 2021 16:10:49 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-discovery-w-search-transparent.png 1118 0 0 0 cropped-discovery-w-search-transparent.png]]> cropped-discovery-w-search-transparent.png]]> cropped-discovery-w-search-transparent.png]]> https://discovery.endeavouros.com/cropped-discovery-w-search-transparent-1-png/ Thu, 11 Mar 2021 16:25:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-discovery-w-search-transparent-1.png 1121 0 0 0 cropped-discovery-w-search-transparent-1.png]]> cropped-discovery-w-search-transparent-1.png]]> cropped-discovery-w-search-transparent-1.png]]> https://discovery.endeavouros.com/cropped-cropped-discovery-w-search-transparent-1-png/ Sun, 14 Mar 2021 22:20:12 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-discovery-w-search-transparent-1.png 1210 0 0 0 cropped-cropped-discovery-w-search-transparent-1.png]]> cropped-cropped-discovery-w-search-transparent-1.png]]> https://discovery.endeavouros.com/cropped-cropped-cropped-discovery-w-search-transparent-1-png/ Sun, 14 Mar 2021 22:24:01 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-discovery-w-search-transparent-1.png 1212 0 0 0 cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-discovery-w-search-transparent-1-png/ Sun, 14 Mar 2021 22:27:08 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png 1213 0 0 0 cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> https://discovery.endeavouros.com/cropped-earth-from-space-jpg/ Sun, 14 Mar 2021 22:28:14 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/cropped-Earth-from-space.jpg 1215 0 0 0 https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1-png/ Sun, 14 Mar 2021 22:48:12 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png 1216 0 0 0 cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1-png/ Sun, 14 Mar 2021 22:51:13 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png 1217 0 0 0 cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> https://discovery.endeavouros.com/cropped-cropped-earth-from-space-jpg/ Sun, 14 Mar 2021 23:03:03 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/cropped-cropped-Earth-from-space.jpg 1221 0 0 0 https://discovery.endeavouros.com/oin_member_stacked/ Mon, 15 Mar 2021 09:12:38 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/OIN_member_stacked.jpg 1226 0 0 0 https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1-png/ Tue, 16 Mar 2021 10:41:54 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png 1229 0 0 0 https://discovery.endeavouros.com/cropped-cropped-discovery-logo2-1-4-1-png/ Tue, 16 Mar 2021 10:43:06 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/cropped-cropped-Discovery-logo2-1-4-1.png 1231 0 0 0 https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1-png/ Tue, 16 Mar 2021 10:49:56 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png 1232 0 0 0 cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> https://discovery.endeavouros.com/home/attachment/audio_icon/ Tue, 16 Mar 2021 14:37:48 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/Audio_Icon.jpg 1251 32 0 0 https://discovery.endeavouros.com/home/attachment/audio/ Tue, 16 Mar 2021 14:40:44 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/audio.jpg 1252 32 0 0 https://discovery.endeavouros.com/home/attachment/applications/ Tue, 16 Mar 2021 14:43:04 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/Applications.png 1253 32 0 0 https://discovery.endeavouros.com/home/attachment/aur/ Tue, 16 Mar 2021 14:45:26 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/AUR.png 1254 32 0 0 https://discovery.endeavouros.com/home/attachment/bluetooth-logo-2-1024x614/ Tue, 16 Mar 2021 14:52:40 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/bluetooth-logo-2-1024x614-1.png 1255 32 0 0 https://discovery.endeavouros.com/home/attachment/install-png-file/ Tue, 16 Mar 2021 15:08:48 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/Install-PNG-File.png 1256 32 0 0 https://discovery.endeavouros.com/home/attachment/network/ Tue, 16 Mar 2021 15:12:34 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/Network.jpg 1257 32 0 0 https://discovery.endeavouros.com/home/attachment/print/ Tue, 16 Mar 2021 15:18:31 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/print.png 1258 32 0 0 https://discovery.endeavouros.com/home/attachment/hdd-ssd-icon/ Tue, 16 Mar 2021 15:21:54 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/HDD-SSD-icon.png 1259 32 0 0 https://discovery.endeavouros.com/home/attachment/cal/ Tue, 16 Mar 2021 15:37:44 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/CAl.jpg 1261 32 0 0 https://discovery.endeavouros.com/home/attachment/printer/ Tue, 16 Mar 2021 15:43:37 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/printer.jpg 1262 32 0 0 https://discovery.endeavouros.com/home/attachment/printers-2/ Tue, 16 Mar 2021 15:47:10 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/Printers.png 1263 32 0 0 https://discovery.endeavouros.com/coming-soon/ Wed, 17 Mar 2021 09:37:03 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/coming-soon.jpg 1289 0 0 0 https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1-png/ Wed, 17 Mar 2021 10:43:44 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png 1292 0 0 0 cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-discovery-w-search-wht-bg-3-png/ Wed, 17 Mar 2021 10:46:23 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-cropped-cropped-cropped-discovery-w-search-wht-bg-3.png 1294 0 0 0 cropped-cropped-cropped-cropped-discovery-w-search-wht-bg-3.png]]> cropped-cropped-cropped-cropped-discovery-w-search-wht-bg-3.png]]> https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1-png/ Wed, 17 Mar 2021 10:53:51 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png 1295 0 0 0 cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> https://discovery.endeavouros.com/cropped-cropped-cropped-discovery-logo2-1-4-1-png/ Wed, 17 Mar 2021 10:56:49 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/cropped-cropped-cropped-Discovery-logo2-1-4-1.png 1297 0 0 0 cropped-cropped-cropped-Discovery-logo2-1-4-1.png]]> cropped-cropped-cropped-Discovery-logo2-1-4-1.png]]> https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1-png/ Wed, 17 Mar 2021 10:57:14 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png 1298 0 0 0 cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> https://discovery.endeavouros.com/space/ Wed, 17 Mar 2021 11:06:01 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/Space.png 1299 0 0 0 https://discovery.endeavouros.com/cropped-space-png/ Wed, 17 Mar 2021 11:06:33 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-Space.png 1300 0 0 0 https://discovery.endeavouros.com/cropped-network-jpg/ Wed, 17 Mar 2021 11:09:29 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-Network.jpg 1301 0 0 0 https://discovery.endeavouros.com/cropped-cropped-cropped-discovery-logo2-1-4-1-1-png/ Wed, 17 Mar 2021 11:10:43 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/cropped-cropped-cropped-Discovery-logo2-1-4-1-1.png 1302 0 0 0 cropped-cropped-cropped-Discovery-logo2-1-4-1-1.png]]> cropped-cropped-cropped-Discovery-logo2-1-4-1-1.png]]> https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-discovery-logo2-1-4-1-1-png/ Wed, 17 Mar 2021 11:11:48 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/cropped-cropped-cropped-cropped-Discovery-logo2-1-4-1-1.png 1303 0 0 0 https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1-png/ Wed, 17 Mar 2021 11:26:40 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png 1304 0 0 0 cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> https://discovery.endeavouros.com/cropped-cropped-space-png/ Wed, 17 Mar 2021 11:28:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-Space.png 1306 0 0 0 https://discovery.endeavouros.com/cropped-cropped-cropped-space-png/ Wed, 17 Mar 2021 11:34:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-Space.png 1307 0 0 0 https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1-png/ Wed, 17 Mar 2021 11:35:28 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png 1309 0 0 0 cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> https://discovery.endeavouros.com/cropped-cropped-space-1-png/ Wed, 17 Mar 2021 11:40:15 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-Space-1.png 1311 0 0 0 https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-discovery-w-search-wht-bg-3-png/ Wed, 17 Mar 2021 11:41:17 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/cropped-cropped-cropped-cropped-cropped-discovery-w-search-wht-bg-3.png 1312 0 0 0 cropped-cropped-cropped-cropped-cropped-discovery-w-search-wht-bg-3.png]]> cropped-cropped-cropped-cropped-cropped-discovery-w-search-wht-bg-3.png]]> https://discovery.endeavouros.com/1/ Wed, 17 Mar 2021 11:43:01 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/1.png 1314 0 0 0 https://discovery.endeavouros.com/cropped-1-png/ Wed, 17 Mar 2021 11:44:17 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-1.png 1315 0 0 0 https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1-png/ Wed, 17 Mar 2021 11:56:05 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png 1317 0 0 0 cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> https://discovery.endeavouros.com/cropped-cropped-1-1-png/ Wed, 17 Mar 2021 11:57:47 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-1-1.png 1318 0 0 0 https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1-png/ Wed, 17 Mar 2021 12:08:02 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png 1319 0 0 0 cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1-png/ Wed, 17 Mar 2021 12:18:24 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png 1322 0 0 0 cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> https://discovery.endeavouros.com/cropped-cropped-cropped-1-1-png/ Wed, 17 Mar 2021 12:43:56 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-1-1.png 1324 0 0 0 https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1-png/ Wed, 17 Mar 2021 12:47:09 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png 1325 0 0 0 cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1-png/ Wed, 17 Mar 2021 18:44:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png 1345 0 0 0 cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-1-1-png/ Wed, 17 Mar 2021 18:45:13 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-1-1.png 1346 0 0 0 https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-1-1-png/ Wed, 17 Mar 2021 18:57:51 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-cropped-1-1.png 1348 0 0 0 https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1-png/ Wed, 17 Mar 2021 19:03:42 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png 1353 0 0 0 cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-discovery-w-search-transparent-1.png]]> https://discovery.endeavouros.com/cropped-cropped-cropped-space-1-png/ Wed, 17 Mar 2021 19:17:52 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-Space-1.png 1357 0 0 0 https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-cropped-1-1-png/ Wed, 17 Mar 2021 19:25:46 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-cropped-cropped-1-1.png 1360 0 0 0 https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-cropped-cropped-1-1-png/ Wed, 17 Mar 2021 20:19:13 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-cropped-cropped-cropped-1-1.png 1365 0 0 0 https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-discovery-logo2-1-4-1-png/ Wed, 17 Mar 2021 20:25:02 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/cropped-cropped-cropped-cropped-Discovery-logo2-1-4-1.png 1367 0 0 0 cropped-cropped-cropped-cropped-Discovery-logo2-1-4-1.png]]> cropped-cropped-cropped-cropped-Discovery-logo2-1-4-1.png]]> https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-cropped-cropped-1-1-1-png/ Wed, 17 Mar 2021 21:20:02 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-cropped-cropped-cropped-1-1-1.png 1371 0 0 0 https://discovery.endeavouros.com/cropped-1-2-png/ Wed, 17 Mar 2021 21:21:00 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-1-2.png 1372 0 0 0 https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-discovery-logo2-1-4-1-1-png/ Wed, 17 Mar 2021 21:44:56 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/cropped-cropped-cropped-cropped-cropped-Discovery-logo2-1-4-1-1.png 1374 0 0 0 https://discovery.endeavouros.com/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-1-1-1-png/ Wed, 17 Mar 2021 21:48:39 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-cropped-cropped-cropped-cropped-cropped-1-1-1.png 1375 0 0 0 https://discovery.endeavouros.com/cropped-cropped-cropped-space-1-1-png/ Wed, 17 Mar 2021 21:51:28 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-cropped-Space-1-1.png 1376 0 0 0 https://discovery.endeavouros.com/cropped-cropped-network-jpg/ Wed, 17 Mar 2021 21:52:27 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-Network.jpg 1377 0 0 0 https://discovery.endeavouros.com/cropped-endeavour_1-scaled-1-jpg/ Wed, 17 Mar 2021 21:59:31 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-endeavour_1-scaled-1.jpg 1379 0 0 0 https://discovery.endeavouros.com/endeavouros_6/ Wed, 17 Mar 2021 22:00:53 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/EndeavourOS_6.jpg 1380 0 0 0 https://discovery.endeavouros.com/cropped-endeavouros_6-jpg/ Wed, 17 Mar 2021 22:01:10 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-EndeavourOS_6.jpg 1381 0 0 0 https://discovery.endeavouros.com/stargazer_ns/ Wed, 17 Mar 2021 22:05:26 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/Stargazer_ns.png 1382 0 0 0 https://discovery.endeavouros.com/cropped-stargazer_ns-png/ Wed, 17 Mar 2021 22:05:56 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-Stargazer_ns.png 1383 0 0 0 https://discovery.endeavouros.com/cropped-stargazer_ns-1-png/ Wed, 17 Mar 2021 22:20:09 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-Stargazer_ns-1.png 1384 0 0 0 https://discovery.endeavouros.com/title_bar_bg-jpg/ Wed, 17 Mar 2021 23:20:13 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/title_bar_bg.jpg 1389 0 0 0 https://discovery.endeavouros.com/branding-design-png/ Wed, 17 Mar 2021 23:20:17 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/branding-design.png 1391 0 0 0 https://discovery.endeavouros.com/website-design-png/ Wed, 17 Mar 2021 23:20:18 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/website-design.png 1392 0 0 0 https://discovery.endeavouros.com/photography-png/ Wed, 17 Mar 2021 23:20:18 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/photography.png 1393 0 0 0 https://discovery.endeavouros.com/retail-shop-png/ Wed, 17 Mar 2021 23:20:19 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/retail-shop.png 1394 0 0 0 https://discovery.endeavouros.com/marketing-png/ Wed, 17 Mar 2021 23:20:21 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/marketing.png 1395 0 0 0 https://discovery.endeavouros.com/development-png/ Wed, 17 Mar 2021 23:20:22 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/development.png 1396 0 0 0 https://discovery.endeavouros.com/coffee-cup-png/ Wed, 17 Mar 2021 23:20:26 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/coffee-cup.png 1398 0 0 0 https://discovery.endeavouros.com/completed-projects-png/ Wed, 17 Mar 2021 23:20:27 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/completed-projects.png 1399 0 0 0 https://discovery.endeavouros.com/working-days-png/ Wed, 17 Mar 2021 23:20:28 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/working-days.png 1400 0 0 0 https://discovery.endeavouros.com/clients-png/ Wed, 17 Mar 2021 23:20:29 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/clients.png 1401 0 0 0 https://discovery.endeavouros.com/select-a-project-png/ Wed, 17 Mar 2021 23:20:36 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/select-a-project.png 1406 0 0 0 https://discovery.endeavouros.com/project-analysis-png/ Wed, 17 Mar 2021 23:20:38 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/project-analysis.png 1407 0 0 0 https://discovery.endeavouros.com/deliver-result-png/ Wed, 17 Mar 2021 23:20:39 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/deliver-result.png 1408 0 0 0 https://discovery.endeavouros.com/phone-icon-png/ Wed, 17 Mar 2021 23:20:43 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/phone-icon.png 1411 0 0 0 https://discovery.endeavouros.com/phone-icon-png-2/ Wed, 17 Mar 2021 23:20:43 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/phone-icon-1.png 1412 0 0 0 https://discovery.endeavouros.com/cropped-cropped-stargazer_ns-1-png/ Wed, 17 Mar 2021 23:28:15 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-cropped-Stargazer_ns-1.png 1433 0 0 0 https://discovery.endeavouros.com/neon_astronaut_endeavour/ Wed, 17 Mar 2021 23:47:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/neon_astronaut_endeavour.jpg 1435 0 0 0 https://discovery.endeavouros.com/cropped-neon_astronaut_endeavour-jpg/ Wed, 17 Mar 2021 23:47:16 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cropped-neon_astronaut_endeavour.jpg 1436 0 0 0 https://discovery.endeavouros.com/home/attachment/books/ Thu, 18 Mar 2021 11:20:34 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/Books.jpg 1458 32 0 0 https://discovery.endeavouros.com/home/attachment/stargazer_ns-1/ Thu, 18 Mar 2021 16:49:53 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/Stargazer_ns-1.png 1505 32 0 0 https://discovery.endeavouros.com/home/attachment/endeavour_2_nologo/ Sat, 20 Mar 2021 19:19:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/endeavour_2_nologo.png 1513 32 0 0 https://discovery.endeavouros.com/home/attachment/hardware-linux-preview/ Sat, 20 Mar 2021 19:26:04 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/hardware-linux.preview.jpeg 1516 32 0 0 https://discovery.endeavouros.com/wiki/attachment/eos_polygons_v2_rubber_twitter_1500x500_logo/ Sat, 20 Mar 2021 20:03:29 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/EOS_polygons_V2_rubber_twitter_1500x500_logo.png 1519 993 0 0 https://discovery.endeavouros.com/eos_polygons_v2_rubber_reddit_large_1920x256_no-logo/ Sat, 20 Mar 2021 20:18:22 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/EOS_polygons_V2_rubber_reddit_large_1920x256_no-logo.png 1523 0 0 0 https://discovery.endeavouros.com/cc4e012fc8d96cbe52d99dd863743823/ Wed, 24 Mar 2021 11:52:02 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/cc4e012fc8d96cbe52d99dd863743823.jpg 1551 0 0 0 https://discovery.endeavouros.com/stars/ Wed, 24 Mar 2021 12:17:49 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/stars.jpg 1559 0 0 0 https://discovery.endeavouros.com/fdisk/ Wed, 24 Mar 2021 15:24:22 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/fdisk.jpg 1583 0 0 0 https://discovery.endeavouros.com/home/attachment/start-teaching-online-courses-www-blog-grinfer-com/ Thu, 25 Mar 2021 07:38:38 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/Video_tutorial.jpg 1633 32 0 0 https://discovery.endeavouros.com/home/attachment/pexels-photo-6325984/ Thu, 25 Mar 2021 07:42:55 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/10/pexels-photo-6325984.jpeg Pexels.com]]> 1635 32 0 0 Pexels.com";s:17:"created_timestamp";s:1:"0";s:9:"copyright";s:0:"";s:12:"focal_length";s:1:"0";s:3:"iso";s:1:"0";s:13:"shutter_speed";s:1:"0";s:5:"title";s:39:"photo of professor teahcing his student";s:11:"orientation";s:1:"0";s:8:"keywords";a:0:{}}}]]> https://discovery.endeavouros.com/eos_poly_gradient_horizontal_v3_no-logo/ Thu, 25 Mar 2021 08:17:39 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/eos_poly_gradient_Horizontal_V3_no-logo.png 1639 0 0 0 https://discovery.endeavouros.com/home/attachment/endeavour-horizontal-black/ Thu, 25 Mar 2021 08:31:09 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/Endeavour-horizontal-black.png 1640 32 0 0 https://discovery.endeavouros.com/home/attachment/plus_sign/ Thu, 25 Mar 2021 16:28:26 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/Plus_sign.png 1645 32 0 0 https://discovery.endeavouros.com/home/attachment/video_tutorial/ Fri, 26 Mar 2021 10:18:28 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/video_tutorial-1.jpg 1662 32 0 0 https://discovery.endeavouros.com/home/attachment/304px-i3_window_manager_logo-svg_-300x286/ Fri, 26 Mar 2021 10:27:43 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/304px-I3_window_manager_logo.svg_-300x286-1.png 1666 32 0 0 https://discovery.endeavouros.com/virtual-machine-manager-logo/ Fri, 26 Mar 2021 10:55:24 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/virtual-machine-manager-logo.png 1676 0 0 0 https://discovery.endeavouros.com/mpd_logo/ Fri, 26 Mar 2021 10:57:47 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/mpd_logo.png 1678 0 0 0 https://discovery.endeavouros.com/aur/faq-what-is-the-aur/2021/03/attachment/yay/ Fri, 26 Mar 2021 11:00:16 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/yay.jpg 1680 1016 0 0 https://discovery.endeavouros.com/nvidia/nvidia-optional-enhancements-and-troubleshooting/2021/03/attachment/nvidialogo1/ Fri, 26 Mar 2021 11:07:54 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/nvidiaLogo1.jpg 1685 1037 0 0 https://discovery.endeavouros.com/nvidia/nouveau/2021/03/attachment/penguin-lone-emperor/ Fri, 26 Mar 2021 11:09:25 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/Penguin-lone-emperor.jpg 1686 1039 0 0 https://discovery.endeavouros.com/nvidia/nvidia-optimus-notebooks-hybrid-graphics/2021/03/attachment/nvidialogo2/ Fri, 26 Mar 2021 11:10:16 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/nvidiaLogo2.jpg 1687 1041 0 0 https://discovery.endeavouros.com/nvidia/bumblebee-for-nvidia-optimus-older-systems/2021/03/attachment/nvidialogo3/ Fri, 26 Mar 2021 11:10:53 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/nvidiaLogo3.jpg 1688 1043 0 0 https://discovery.endeavouros.com/hardware/optimus-manager-for-nvidia/2021/03/attachment/nvidialogo5/ Fri, 26 Mar 2021 11:12:47 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/nvidiaLogo5.jpg 1690 1045 0 0 https://discovery.endeavouros.com/nvidia/nvidia-intro/2021/03/attachment/1920px-nvidia_2020_logo-svg/ Fri, 26 Mar 2021 11:13:48 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/1920px-Nvidia_2020_logo.svg_.png 1692 1050 0 0 https://discovery.endeavouros.com/amd-logo-circuit-background-1200x628/ Fri, 26 Mar 2021 11:16:01 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/amd-logo-circuit-background-1200x628-1.jpg 1694 0 0 0 https://discovery.endeavouros.com/network/r8168-workaround/2021/03/attachment/wifi3/ Fri, 26 Mar 2021 11:19:28 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/wifi3.png 1695 1084 0 0 https://discovery.endeavouros.com/installation/get-broadcom-working-on-an-installed-system-and-on-live-usb/2021/03/attachment/wifi2/ Fri, 26 Mar 2021 11:20:17 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/wifi2.jpg 1696 1086 0 0 https://discovery.endeavouros.com/?attachment_id=1699 Fri, 26 Mar 2021 11:24:33 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/sambahero.jpg 1699 1097 0 0 https://discovery.endeavouros.com/grub-and-refind/how-to-install-refind/2021/03/attachment/refind/ Fri, 26 Mar 2021 11:30:26 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/refind.png 1701 1162 0 0 https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/attachment/linux-distro-usb-994x400/ Fri, 26 Mar 2021 11:37:35 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/linux-distro-usb-994x400-1.jpg 1703 1182 0 0 https://discovery.endeavouros.com/desktop-environments/lightdm/2021/03/attachment/lightdm-eos-1024x574/ Fri, 26 Mar 2021 11:46:15 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/Lightdm-EOS-1024x574-1.png 1706 1186 0 0 https://discovery.endeavouros.com/desktop-environments/font-management/2021/03/attachment/fonts/ Fri, 26 Mar 2021 11:48:02 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/fonts.jpg 1708 1191 0 0 https://discovery.endeavouros.com/pacman/automatically-ranking-the-mirror-list/2021/03/attachment/mirrorlist/ Fri, 26 Mar 2021 11:50:57 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/mirrorlist.jpg 1709 1203 0 0 https://discovery.endeavouros.com/pacman/mirrors-intro/2021/03/attachment/many-mirror-on-wall/ Fri, 26 Mar 2021 11:52:25 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/types-of-mirrors.jpeg 1711 1205 0 0 https://discovery.endeavouros.com/pacman/downgrade-packages-to-a-specific-date/2021/03/attachment/arch-pacman/ Fri, 26 Mar 2021 11:56:28 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/arch-pacman.jpg 1712 1240 0 0 https://discovery.endeavouros.com/pacman/downgrade-packages/2021/03/attachment/arch-pacman-invaders-1920x1080/ Fri, 26 Mar 2021 11:57:12 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/arch-pacman-invaders-1920x1080-1.png 1713 1244 0 0 https://discovery.endeavouros.com/pacman/desktop-managers/2021/03/attachment/pacman-arch-linux/ Fri, 26 Mar 2021 11:57:50 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/pacman-arch-linux.jpg 1714 1246 0 0 https://discovery.endeavouros.com/desktop-environments/removing-a-desktop-environment/2021/03/attachment/pacmarch/ Fri, 26 Mar 2021 12:00:23 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/pacmarch.jpg 1715 1248 0 0 https://discovery.endeavouros.com/pacman/pacman-basic-commands/2021/03/attachment/pacman-syu-archlinux-ghost1227-technology-ai2d/ Fri, 26 Mar 2021 12:02:21 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/pacman-syu-archlinux-ghost1227-technology-Ai2D.jpg 1716 1535 0 0 https://discovery.endeavouros.com/pacman/automatic-update-of-the-pacman-database/2021/03/attachment/arch/ Fri, 26 Mar 2021 12:03:02 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/arch.png 1717 1238 0 0 https://discovery.endeavouros.com/window-tiling-managers/i3-wm/2021/03/attachment/eos-i3-fresh/ Fri, 26 Mar 2021 12:08:31 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/eos-i3-fresh.png 1720 1594 0 0 https://discovery.endeavouros.com/arm/homeserver-use-fuse-and-sshfs-to-view-server-data-in-a-file-manager/2021/03/attachment/arm_endeavouros_xfce4/ Fri, 26 Mar 2021 12:12:03 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/arm_endeavouros_xfce4.png 1723 1598 0 0 https://discovery.endeavouros.com/next-generation-ssd/ Fri, 26 Mar 2021 12:15:19 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/next-generation-ssd.jpg 1725 0 0 0 https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/attachment/eos_polygons_v2_rubber_1920x1080_logo/ Fri, 26 Mar 2021 12:20:06 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/EOS_polygons_V2_rubber_1920x1080_logo.png 1728 1018 0 0 https://discovery.endeavouros.com/pacman/mirrors-intro/2021/03/attachment/mirrorlist2/ Fri, 26 Mar 2021 12:21:36 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/mirrorlist2.jpg 1729 1205 0 0 https://discovery.endeavouros.com/window-tiling-managers/bspwm-2/2021/03/attachment/bspwm_logo/ Sun, 28 Mar 2021 14:03:54 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/bspwm_logo.jpg 1735 1734 0 0 https://discovery.endeavouros.com/?attachment_id=1744 Mon, 29 Mar 2021 14:06:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/luks-logo-cropped.png 1744 1742 0 0 https://discovery.endeavouros.com/?attachment_id=1753 Mon, 29 Mar 2021 14:23:57 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/Btrfs-filesystem.jpg 1753 1750 0 0 https://discovery.endeavouros.com/nvidia/optimus-switch-another-solution-for-optimus-laptops/2021/04/attachment/flow3/ Tue, 13 Apr 2021 09:26:52 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/04/Flow3.jpg 1988 1987 0 0 https://discovery.endeavouros.com/applications/how-to-install-virt-manager-complete-edition/2021/09/attachment/virtmanager_logo/ Fri, 03 Sep 2021 13:41:35 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/virtManager_logo.png 2441 2440 0 0 https://discovery.endeavouros.com/applications/how-to-install-virt-manager-complete-edition/2021/09/attachment/virtmanager/ Fri, 03 Sep 2021 13:48:47 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/virtManager.png 2443 2440 0 0 https://discovery.endeavouros.com/applications/how-to-install-virt-manager-complete-edition/2021/09/attachment/qemu3derror/ Fri, 03 Sep 2021 14:38:37 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/qemu3dError.png 2461 2440 0 0 https://discovery.endeavouros.com/applications/how-to-install-virt-manager-complete-edition/2021/09/attachment/displayspicepreconfig/ Fri, 03 Sep 2021 14:41:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/displaySpicePreConfig.png 2463 2440 0 0 https://discovery.endeavouros.com/applications/how-to-install-virt-manager-complete-edition/2021/09/attachment/displayspiceafterconfig/ Fri, 03 Sep 2021 14:42:08 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/displaySpiceAfterConfig.png 2464 2440 0 0 https://discovery.endeavouros.com/applications/how-to-install-virt-manager-complete-edition/2021/09/attachment/vedioafterconfig/ Fri, 03 Sep 2021 14:42:58 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/vedioAfterConfig.png 2465 2440 0 0 https://discovery.endeavouros.com/applications/how-to-install-virt-manager-complete-edition/2021/09/attachment/virtmanagerabout/ Fri, 03 Sep 2021 14:45:49 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/virtManagerAbout.png 2468 2440 0 0 https://discovery.endeavouros.com/applications/how-to-install-virt-manager-complete-edition/2021/09/attachment/qemuconfuncomment/ Mon, 06 Sep 2021 14:17:49 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/qemuConfUncomment.png 2490 2440 0 0 https://discovery.endeavouros.com/xfceblackscreen/ Tue, 07 Sep 2021 14:58:08 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/xfceBlackScreen.png 2496 0 0 0 https://discovery.endeavouros.com/virtiono3d/ Tue, 07 Sep 2021 15:00:13 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/virtioNo3d.png 2497 0 0 0 https://discovery.endeavouros.com/virtioqxl/ Tue, 07 Sep 2021 15:05:16 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/virtioQxl.png 2498 0 0 0 https://discovery.endeavouros.com/enabledcomositor/ Tue, 07 Sep 2021 15:08:27 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/enabledComositor.png 2499 0 0 0 https://discovery.endeavouros.com/disabledcomositor/ Tue, 07 Sep 2021 15:08:56 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/disabledComositor.png 2500 0 0 0 https://discovery.endeavouros.com/sessionandstartup/ Tue, 07 Sep 2021 15:12:39 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/sessionAndStartup.png 2501 0 0 0 https://discovery.endeavouros.com/addtosessionstart/ Tue, 07 Sep 2021 15:14:41 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/addToSessionStart.png 2502 0 0 0 https://discovery.endeavouros.com/picomfullswing/ Tue, 07 Sep 2021 15:16:43 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/picomFullSwing.png 2503 0 0 0 https://discovery.endeavouros.com/picomfullswing-1/ Tue, 07 Sep 2021 15:17:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/picomFullSwing-1.png 2504 0 0 0 https://discovery.endeavouros.com/storage-and-partitions/how-to-permanently-mount-external-internal-drives-in-linux/2022/02/attachment/lsblkcommand/ Fri, 15 Oct 2021 12:41:03 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/10/lsblkCommand.png 2623 2622 0 0 https://discovery.endeavouros.com/storage-and-partitions/how-to-permanently-mount-external-internal-drives-in-linux/2022/02/attachment/diskuuid/ Fri, 15 Oct 2021 12:57:05 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/10/diskUUID.png 2627 2622 0 0 https://discovery.endeavouros.com/storage-and-partitions/how-to-permanently-mount-external-internal-drives-in-linux/2022/02/attachment/diskuuidusingls/ Fri, 15 Oct 2021 12:57:42 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/10/diskUUIDUsingLs.png 2628 2622 0 0 https://discovery.endeavouros.com/storage-and-partitions/how-to-permanently-mount-external-internal-drives-in-linux/2022/02/attachment/fstabinnvimwithoutextrenal/ Fri, 15 Oct 2021 13:38:16 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/10/fstabInNvimWithoutExtrenal.png 2629 2622 0 0 https://discovery.endeavouros.com/storage-and-partitions/how-to-permanently-mount-external-internal-drives-in-linux/2022/02/attachment/fstabinnvimwithoutextrenal-1/ Fri, 15 Oct 2021 13:48:56 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/10/fstabInNvimWithoutExtrenal-1.png 2630 2622 0 0 https://discovery.endeavouros.com/storage-and-partitions/how-to-permanently-mount-external-internal-drives-in-linux/2022/02/attachment/mountinfilemanager/ Fri, 15 Oct 2021 13:54:10 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/10/mountInFileManager.png 2632 2622 0 0 https://discovery.endeavouros.com/window-tiling-managers/qtile/2022/01/attachment/mod4/ Sun, 09 Jan 2022 09:08:05 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/mod4.png 3043 3031 0 0 https://discovery.endeavouros.com/gaming/gaming-101/2022/01/attachment/vulkan-wide/ Sun, 09 Jan 2022 10:42:18 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/Vulkan-Wide.png 3057 3047 0 0 https://discovery.endeavouros.com/audio/audiophile/2022/01/attachment/headphone-amplifier-g48f92e291_640/ Sun, 09 Jan 2022 12:01:38 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/headphone-amplifier-g48f92e291_640.jpg 3076 2970 0 0 https://discovery.endeavouros.com/applications/video-playback/2022/01/attachment/video-g4a0c8915a_640/ Sun, 09 Jan 2022 12:02:13 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/video-g4a0c8915a_640.png 3077 2992 0 0 https://discovery.endeavouros.com/window-tiling-managers/qtile/2022/01/attachment/qtile-2/ Sun, 09 Jan 2022 12:12:33 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/qtile.png 3080 3031 0 0 https://discovery.endeavouros.com/gaming/steam-lutris-wine/2022/01/attachment/lutris/ Sun, 09 Jan 2022 12:13:23 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/lutris.png 3081 3059 0 0 https://discovery.endeavouros.com/?attachment_id=3094 Mon, 10 Jan 2022 06:05:05 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/worm.png 3094 3088 0 0 https://discovery.endeavouros.com/window-tiling-managers/sway/2022/01/attachment/sway/ Mon, 10 Jan 2022 06:17:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/sway.png 3099 3086 0 0 https://discovery.endeavouros.com/applications/default-applications/2022/01/attachment/xfce4-mime-editor/ Mon, 10 Jan 2022 13:28:16 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/xfce4-mime-editor.png 3178 3153 0 0 https://discovery.endeavouros.com/wrenches-5971179_960_720/ Mon, 31 Jan 2022 03:45:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/wrenches-5971179_960_720.jpg 3307 0 0 0 https://discovery.endeavouros.com/window-tiling-managers/openbox/2022/03/attachment/endeavouros-openbox-icon/ Mon, 14 Nov 2022 13:56:41 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/03/endeavouros-openbox-icon.png 3814 3376 0 0 https://discovery.endeavouros.com/uefi-fdisk-terminal/ Sat, 03 Apr 2021 18:05:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/04/uefi-fdisk-terminal.png 1835 0 0 0 https://discovery.endeavouros.com/uefi-fdisk-terminal-1/ Sat, 03 Apr 2021 18:07:01 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/04/uefi-fdisk-terminal-1.png 1837 0 0 0 https://discovery.endeavouros.com/bios-fdisk-terminal/ Sat, 03 Apr 2021 18:20:40 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/04/bios-fdisk-terminal.png 1844 0 0 0 https://discovery.endeavouros.com/hardware/optimus-manager-for-nvidia/2021/03/attachment/nv_optimus_3d_large/ Sat, 03 Apr 2021 18:57:10 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/NV_Optimus_3D_large.jpg 1855 1045 0 0 https://discovery.endeavouros.com/hardware/optimus-manager-for-nvidia/2021/03/attachment/nvidia-optimus/ Sat, 03 Apr 2021 18:58:51 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/nvidia-optimus.png 1857 1045 0 0 https://discovery.endeavouros.com/audio/bluetooth/2021/03/attachment/bluetooth-2/ Wed, 07 Apr 2021 21:39:13 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/bluetooth.png 1920 1089 0 0 https://discovery.endeavouros.com/audio/bluetooth/2021/03/attachment/bluet-clipart-1/ Wed, 07 Apr 2021 21:44:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/bluet-clipart-1.png 1921 1089 0 0 https://discovery.endeavouros.com/audio/bluetooth/2021/03/attachment/bluetooth-logo-png-2/ Wed, 07 Apr 2021 21:45:36 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/bluetooth-logo-png-2.png 1922 1089 0 0 https://discovery.endeavouros.com/audio/bluetooth/2021/03/attachment/bluetooth-3/ Wed, 07 Apr 2021 21:48:52 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/bluetooth-1.png 1923 1089 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2021-04-11_18-15/ Sun, 11 Apr 2021 16:16:09 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/04/2021-04-11_18-15.png 1950 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2021-04-11_18-11/ Sun, 11 Apr 2021 16:16:22 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/04/2021-04-11_18-11.png 1951 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2021-04-11_18-12/ Sun, 11 Apr 2021 16:16:47 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/04/2021-04-11_18-12.png 1952 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2021-04-11_18-14/ Sun, 11 Apr 2021 16:17:05 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/04/2021-04-11_18-14.png 1953 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2021-04-11_18-14_1/ Sun, 11 Apr 2021 16:17:32 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/04/2021-04-11_18-14_1.png 1954 1184 0 0 https://discovery.endeavouros.com/video-tutorials/joekamprad-video-tutorials/2021/04/attachment/endeavouros-btrfs-thumbnail/ Sun, 18 Apr 2021 12:49:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/04/EndeavourOS-BTRFS-thumbnail.png 2015 2007 0 0 https://discovery.endeavouros.com/installation/add-packages-to-be-installed-in-addition-to-desktop-chosen/2021/04/attachment/2021-04-20_15-09/ Tue, 20 Apr 2021 13:13:53 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/04/2021-04-20_15-09.png 2019 2018 0 0 https://discovery.endeavouros.com/desktop-environments/gdm-gnome-desktop-manager/2021/05/attachment/2021-05-03_21-34/ Mon, 03 May 2021 19:35:19 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/05/2021-05-03_21-34.png 2044 2043 0 0 https://discovery.endeavouros.com/window-tiling-managers/openbox/2022/03/attachment/openbox-2/ Mon, 14 Nov 2022 13:57:43 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/03/Openbox.png 3815 3376 0 0 https://discovery.endeavouros.com/cropped-cropped-discovery-logo2-1-4-2-png/ Sun, 09 Aug 2026 11:05:52 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/cropped-cropped-Discovery-logo2-1-4-2.png 5301 0 0 0 cropped-Discovery-logo2-1-4.png]]> https://discovery.endeavouros.com/cropped-discovery-logo2-1-4-png/attachment/cropped-cropped-discovery-logo2-1-4-3-png/ Sun, 09 Aug 2026 11:10:25 +0000 https://discovery.endeavouros.com/wp-content/uploads/2019/11/cropped-cropped-Discovery-logo2-1-4-3.png 5303 1023 0 0 cropped-Discovery-logo2-1-4.png]]> https://discovery.endeavouros.com/desktop-environments/gdm-gnome-desktop-manager/2021/05/attachment/2021-05-03_21-54/ Mon, 03 May 2021 19:56:20 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/05/2021-05-03_21-54.png 2047 2043 0 0 https://discovery.endeavouros.com/applications/uniform-theme-and-fonts-for-qt-apps-in-gtk-environments/2021/05/attachment/2021-05-18_19-01/ Tue, 18 May 2021 18:42:25 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/05/2021-05-18_19-01.png 2063 2062 0 0 https://discovery.endeavouros.com/applications/uniform-theme-and-fonts-for-qt-apps-in-gtk-environments/2021/05/attachment/2021-05-18_21-00/ Tue, 18 May 2021 19:05:14 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/05/2021-05-18_21-00.png 2064 2062 0 0 https://discovery.endeavouros.com/applications/uniform-theme-and-fonts-for-qt-apps-in-gtk-environments/2021/05/attachment/2021-05-18_21-01/ Tue, 18 May 2021 19:06:00 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/05/2021-05-18_21-01.png 2065 2062 0 0 https://discovery.endeavouros.com/applications/uniform-theme-and-fonts-for-qt-apps-in-gtk-environments/2021/05/attachment/2021-05-18_21-02/ Tue, 18 May 2021 19:07:03 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/05/2021-05-18_21-02.png 2066 2062 0 0 https://discovery.endeavouros.com/applications/uniform-theme-and-fonts-for-qt-apps-in-gtk-environments/2021/05/attachment/2021-05-18_21-03/ Tue, 18 May 2021 19:08:10 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/05/2021-05-18_21-03.png 2067 2062 0 0 https://discovery.endeavouros.com/applications/uniform-theme-and-fonts-for-qt-apps-in-gtk-environments/2021/05/attachment/2021-05-18_21-14/ Tue, 18 May 2021 19:15:21 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/05/2021-05-18_21-14.png 2068 2062 0 0 https://discovery.endeavouros.com/applications/uniform-theme-and-fonts-for-qt-apps-in-gtk-environments/2021/05/attachment/2021-05-18_19-13/ Tue, 18 May 2021 19:41:02 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/05/2021-05-18_19-13.png 2072 2062 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/avahi-hostname-resolution/ Sat, 05 Jun 2021 13:05:28 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/06/avahi-hostname-resolution.png 2089 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2021-06-22_23-24/ Tue, 22 Jun 2021 21:24:53 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/06/2021-06-22_23-24.png 2118 1029 0 0 https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/attachment/rufus-1-ong_/ Wed, 14 Jul 2021 06:38:00 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/07/rufus-1.ong_.png 2203 1182 0 0 https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/attachment/rufus-2/ Wed, 14 Jul 2021 06:38:58 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/07/rufus-2.png 2204 1182 0 0 https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/attachment/usb-writer-windows/ Wed, 14 Jul 2021 06:41:27 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/07/usb-writer-windows.png 2205 1182 0 0 https://discovery.endeavouros.com/gnu-head-sm/ Tue, 27 Jul 2021 22:03:36 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/07/gnu-head-sm.jpg 2222 0 0 0 https://discovery.endeavouros.com/nvidia/nvidia-intro/2021/03/attachment/nvidia-2/ Thu, 02 Sep 2021 10:04:54 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/nvidia.webp 2432 1050 0 0 https://discovery.endeavouros.com/nvidia/nvidia-intro/2021/03/attachment/nvidialogo2-2/ Thu, 02 Sep 2021 10:06:09 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/nvidiaLogo2.webp 2433 1050 0 0 https://discovery.endeavouros.com/nvidia/nvidia-intro/2021/03/attachment/nvidia-3/ Thu, 02 Sep 2021 10:10:00 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/nvidia-1.webp 2434 1050 0 0 https://discovery.endeavouros.com/nvidia/nvidia-intro/2021/03/attachment/nvidia-4/ Thu, 02 Sep 2021 10:16:20 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/nvidia-2.webp 2435 1050 0 0 https://discovery.endeavouros.com/window-tiling-managers/i3-wm/2021/03/attachment/i3wm-eos-banner/ Mon, 06 Sep 2021 10:11:45 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/i3wm-eos-banner.png 2479 1594 0 0 https://discovery.endeavouros.com/window-tiling-managers/i3-wm/2021/03/attachment/i3wm-eos/ Mon, 06 Sep 2021 10:14:56 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/i3wm-eos.png 2480 1594 0 0 https://discovery.endeavouros.com/window-tiling-managers/i3-wm/2021/03/attachment/i3wm-eos-transparency/ Mon, 06 Sep 2021 10:23:06 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/i3wm-eos-transparency.png 2482 1594 0 0 https://discovery.endeavouros.com/window-tiling-managers/i3-wm/2021/03/attachment/i3wm-eos-2/ Mon, 06 Sep 2021 10:24:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/i3wm-eos-1.png 2483 1594 0 0 https://discovery.endeavouros.com/audio/pipewire/2021/09/attachment/config-pipewire-headset-switch/ Tue, 14 Sep 2021 01:35:06 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/config-pipewire-headset-switch.png 2520 2519 0 0 https://discovery.endeavouros.com/audio/pipewire/2021/09/attachment/headphone/ Tue, 14 Sep 2021 01:35:08 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/headphone.png 2521 2519 0 0 https://discovery.endeavouros.com/audio/pipewire/2021/09/attachment/headsetbt/ Tue, 14 Sep 2021 01:35:10 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/headsetbt.png 2522 2519 0 0 https://discovery.endeavouros.com/audio/pipewire/2021/09/attachment/pipewire-logo/ Tue, 14 Sep 2021 01:37:24 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/pipewire-logo.png 2523 2519 0 0 https://discovery.endeavouros.com/1280px-grub_logo_large/ Tue, 14 Sep 2021 13:00:06 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/07/1280px-Grub_logo_large.png 2529 0 0 0 https://discovery.endeavouros.com/grub_logo/ Tue, 14 Sep 2021 13:02:04 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/07/Grub_logo.png 2531 0 0 0 https://discovery.endeavouros.com/btrfs-subvols-terminal/ Fri, 17 Sep 2021 16:23:49 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/btrfs-subvols-terminal.png 2541 0 0 0 https://discovery.endeavouros.com/system-rescue/repair-a-non-booting-grub/2021/03/attachment/2021-09-22_20-24/ Wed, 22 Sep 2021 18:24:31 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/2021-09-22_20-24.png 2555 1588 0 0 https://discovery.endeavouros.com/system-rescue/repair-a-non-booting-grub/2021/03/attachment/2021-09-22_20-40/ Wed, 22 Sep 2021 18:55:59 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/2021-09-22_20-40.png 2557 1588 0 0 https://discovery.endeavouros.com/system-rescue/repair-a-non-booting-grub/2021/03/attachment/2021-09-22_20-36/ Wed, 22 Sep 2021 18:56:34 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/2021-09-22_20-36.png 2558 1588 0 0 https://discovery.endeavouros.com/2021-09-24_11-32/ Fri, 24 Sep 2021 09:32:45 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/2021-09-24_11-32.png 2562 0 0 0 https://discovery.endeavouros.com/2021-09-24_11-39/ Fri, 24 Sep 2021 09:39:51 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/2021-09-24_11-39.png 2565 0 0 0 https://discovery.endeavouros.com/audio/pipewire/2021/09/attachment/pipewire-autoswitch/ Fri, 24 Sep 2021 17:10:24 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/pipewire-autoswitch.png 2571 2519 0 0 https://discovery.endeavouros.com/audio/pipewire/2021/09/attachment/headphone-mode/ Fri, 24 Sep 2021 17:10:42 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/headphone-mode.png 2572 2519 0 0 https://discovery.endeavouros.com/audio/pipewire/2021/09/attachment/headset-mode/ Fri, 24 Sep 2021 17:10:56 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/headset-mode.png 2573 2519 0 0 https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/attachment/2021-10-05_21-38/ Tue, 05 Oct 2021 19:40:59 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/10/2021-10-05_21-38.png 2602 1018 0 0 https://discovery.endeavouros.com/endeavouros-tools/telegram-helpchat-and-reddit-discussion-rules/2021/11/attachment/telegram-reddit/ Tue, 09 Nov 2021 18:33:53 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/11/telegram-reddit.png 2680 2679 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2021-11-24_14-37/ Wed, 24 Nov 2021 13:37:37 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/11/2021-11-24_14-37.png 2712 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2021-11-24_14-40/ Wed, 24 Nov 2021 13:40:34 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/11/2021-11-24_14-40.png 2713 1184 0 0 https://discovery.endeavouros.com/audio/pulseaudio/2021/12/attachment/pulseaudio/ Wed, 08 Dec 2021 21:44:50 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/12/pulseaudio.png 2739 2737 0 0 https://discovery.endeavouros.com/system-rescue/fix-arch-linux-boot-with-arch-chroot/2021/12/attachment/2021-12-13_18-32/ Mon, 13 Dec 2021 17:32:45 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/12/2021-12-13_18-32.png 2747 2745 0 0 https://discovery.endeavouros.com/system-rescue/fix-arch-linux-boot-with-arch-chroot/2021/12/attachment/2021-12-13_18-33/ Mon, 13 Dec 2021 17:35:59 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/12/2021-12-13_18-33.png 2748 2745 0 0 https://discovery.endeavouros.com/video-tutorials/install-endeavouros/2021/12/attachment/2021-12-13_18-37/ Mon, 13 Dec 2021 17:40:05 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/12/2021-12-13_18-37.png 2749 2730 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2021-12-19_23-39/ Sun, 19 Dec 2021 22:47:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/12/2021-12-19_23-39.png 2759 1029 0 0 https://discovery.endeavouros.com/hibernate-icon-13-512/ Tue, 28 Dec 2021 00:42:11 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/12/hibernate-icon-13-512.png 2786 0 0 0 https://discovery.endeavouros.com/hibernate-btrfs/ Tue, 28 Dec 2021 00:47:33 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/12/hibernate-btrfs.png 2787 0 0 0 https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/attachment/2022-01-05_12-56_1/ Wed, 05 Jan 2022 11:58:11 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/2022-01-05_12-56_1.png 2879 1018 0 0 https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/attachment/2022-01-05_12-56/ Wed, 05 Jan 2022 11:58:13 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/2022-01-05_12-56.png 2880 1018 0 0 https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/attachment/2022-01-05_12-54_1/ Wed, 05 Jan 2022 11:58:15 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/2022-01-05_12-54_1.png 2881 1018 0 0 https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/attachment/2022-01-05_12-54/ Wed, 05 Jan 2022 11:58:16 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/2022-01-05_12-54.png 2882 1018 0 0 https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/attachment/popsicle/ Thu, 13 Jan 2022 19:48:43 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/popsicle.png 3230 1182 0 0 https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/attachment/popsicle-1/ Thu, 13 Jan 2022 19:49:59 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/popsicle-1.png 3231 1182 0 0 https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/attachment/suse-imagewriter/ Thu, 13 Jan 2022 19:59:14 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/suse-imagewriter.png 3232 1182 0 0 https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/attachment/gnome-disks/ Thu, 13 Jan 2022 19:59:47 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/gnome-disks.png 3233 1182 0 0 https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/attachment/ventoy-gui/ Thu, 13 Jan 2022 20:09:00 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/ventoy-gui.png 3236 1182 0 0 https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/attachment/ventoy-gui-1/ Thu, 13 Jan 2022 20:10:10 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/ventoy-gui-1.png 3237 1182 0 0 https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/attachment/ventoy-folder/ Thu, 13 Jan 2022 20:11:25 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/ventoy-folder.png 3238 1182 0 0 https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/attachment/suse-imagewriter-1/ Thu, 13 Jan 2022 20:13:37 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/suse-imagewriter-1.png 3240 1182 0 0 https://discovery.endeavouros.com/audio/pipewire/2021/09/attachment/2022-01-29_11-17/ Sat, 29 Jan 2022 10:20:54 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/2022-01-29_11-17.png 3289 2519 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2022-02-01_11-51/ Tue, 01 Feb 2022 10:56:18 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/02/2022-02-01_11-51.png 3317 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2022-02-01_11-52_1/ Tue, 01 Feb 2022 10:56:18 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/02/2022-02-01_11-52_1.png 3318 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2022-02-01_11-52/ Tue, 01 Feb 2022 10:56:18 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/02/2022-02-01_11-52.png 3319 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2022-02-01_11-54/ Tue, 01 Feb 2022 10:56:19 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/02/2022-02-01_11-54.png 3320 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2022-02-01_11-53/ Tue, 01 Feb 2022 10:56:19 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/02/2022-02-01_11-53.png 3321 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2022-02-01_11-55_1/ Tue, 01 Feb 2022 10:56:22 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/02/2022-02-01_11-55_1.png 3322 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2022-02-01_11-55/ Tue, 01 Feb 2022 10:56:22 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/02/2022-02-01_11-55.png 3323 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2022-02-01_11-54_1/ Tue, 01 Feb 2022 10:56:22 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/02/2022-02-01_11-54_1.png 3324 1029 0 0 https://discovery.endeavouros.com/encrypted-installation/btrfs-with-timeshift-snapshots-on-the-grub-menu/2022/02/attachment/2022-02-09_20-26_1/ Tue, 15 Feb 2022 08:30:37 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/02/2022-02-09_20-26_1.png 3347 3346 0 0 https://discovery.endeavouros.com/encrypted-installation/btrfs-with-timeshift-snapshots-on-the-grub-menu/2022/02/attachment/2022-02-09_20-26/ Tue, 15 Feb 2022 08:31:02 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/02/2022-02-09_20-26.png 3348 3346 0 0 https://discovery.endeavouros.com/encrypted-installation/btrfs-with-timeshift-snapshots-on-the-grub-menu/2022/02/attachment/btrfs-timeshift-grub/ Tue, 15 Feb 2022 08:43:52 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/02/btrfs-timeshift-grub.png 3350 3346 0 0 https://discovery.endeavouros.com/2022-03-20_19-32/ Sun, 20 Mar 2022 18:33:37 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2022-03-20_19-32.png 3392 0 0 0 https://discovery.endeavouros.com/2022-03-20_19-29/ Sun, 20 Mar 2022 18:34:35 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/03/2022-03-20_19-29.png 3395 0 0 0 https://discovery.endeavouros.com/2022-03-20_19-28/ Sun, 20 Mar 2022 18:43:33 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/03/2022-03-20_19-28.png 3397 0 0 0 https://discovery.endeavouros.com/2022-03-20_19-45/ Sun, 20 Mar 2022 18:45:32 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/03/2022-03-20_19-45.png 3398 0 0 0 https://discovery.endeavouros.com/2022-03-20_19-47/ Sun, 20 Mar 2022 18:47:33 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/03/2022-03-20_19-47.png 3399 0 0 0 https://discovery.endeavouros.com/2022-03-20_19-46/ Sun, 20 Mar 2022 18:47:46 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/03/2022-03-20_19-46.png 3400 0 0 0 https://discovery.endeavouros.com/audio/bluetooth/2021/03/attachment/bluetoothctl/ Sat, 26 Mar 2022 18:47:43 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/03/bluetoothctl.png 3415 1089 0 0 https://discovery.endeavouros.com/applications/firewalld/2022/03/attachment/firewall-2/ Sun, 27 Mar 2022 11:52:35 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/03/firewall.webp 3422 3421 0 0 https://discovery.endeavouros.com/applications/firewalld/2022/03/attachment/firewalld-2/ Sun, 27 Mar 2022 11:57:57 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/03/firewalld.png 3428 3421 0 0 https://discovery.endeavouros.com/applications/firewalld/2022/03/attachment/firewalld-1/ Sun, 27 Mar 2022 12:29:40 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/03/firewalld-1.png 3431 3421 0 0 https://discovery.endeavouros.com/applications/firewalld/2022/03/attachment/firewalld-tray-info-hover/ Sun, 27 Mar 2022 13:03:12 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/03/firewalld-tray-info-hover.png 3434 3421 0 0 https://discovery.endeavouros.com/applications/firewalld/2022/03/attachment/firewalld-tray-info/ Sun, 27 Mar 2022 13:03:12 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/03/firewalld-tray-info.png 3435 3421 0 0 https://discovery.endeavouros.com/applications/firewalld/2022/03/attachment/firewalld-tray-menu/ Sun, 27 Mar 2022 13:03:12 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/03/firewalld-tray-menu.png 3436 3421 0 0 https://discovery.endeavouros.com/applications/firewalld/2022/03/attachment/menu/ Sun, 27 Mar 2022 13:14:44 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/03/menu.png 3437 3421 0 0 https://discovery.endeavouros.com/applications/firewalld/2022/03/attachment/firewalld-remove/ Sun, 10 Apr 2022 13:15:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/04/firewalld-remove.png 3474 3421 0 0 https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/attachment/endeavouros-log-tool/ Tue, 26 Apr 2022 16:12:06 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/04/endeavouros-log-tool.png 3496 1018 0 0 https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/attachment/eoslogtool-showurl/ Tue, 26 Apr 2022 16:12:21 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/04/eoslogtool-showurl.png 3497 1018 0 0 https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/attachment/endeavouros-log-tool-1/ Tue, 26 Apr 2022 16:19:47 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/04/endeavouros-log-tool-1.png 3501 1018 0 0 https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/attachment/endeavouros-log-tool-2/ Tue, 26 Apr 2022 16:24:08 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/04/endeavouros-log-tool-2.png 3503 1018 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/system-config-printer-1/ Sun, 08 May 2022 13:33:55 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/05/system-config-printer-1.png 3516 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/system-config-printer-3/ Sun, 08 May 2022 13:34:45 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/05/system-config-printer-3.png 3517 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/system-config-printer-2/ Sun, 08 May 2022 13:35:24 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/05/system-config-printer-2.png 3518 1029 0 0 https://discovery.endeavouros.com/hardware/webcam-setup/2022/05/attachment/ernest-ojeh-cjgdrjl0tes-unsplash/ Sun, 15 May 2022 14:31:18 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/05/ernest-ojeh-cJGDRjl0TEs-unsplash.jpg 3536 3535 0 0 https://discovery.endeavouros.com/hardware/webcam-setup/2022/05/attachment/v4l2-test-bench-view/ Sun, 15 May 2022 16:05:28 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/05/v4l2-test-bench-view.png 3537 3535 0 0 https://discovery.endeavouros.com/hardware/webcam-setup/2022/05/attachment/guvcview/ Sun, 15 May 2022 16:24:44 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/05/guvcview.png 3538 3535 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/open-firewall-for-network-printing/ Fri, 10 Jun 2022 11:14:17 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/06/open-firewall-for-network-printing.png 3564 1029 0 0 https://discovery.endeavouros.com/toggle-log/ Sat, 18 Jun 2022 23:15:28 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/06/toggle-log.png 3574 0 0 0 https://discovery.endeavouros.com/unselect-packages/ Sat, 18 Jun 2022 23:15:44 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/06/unselect-packages.png 3575 0 0 0 https://discovery.endeavouros.com/desktop-chooser/ Sat, 18 Jun 2022 23:15:58 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/06/desktop-chooser.png 3576 0 0 0 https://discovery.endeavouros.com/online-offline/ Sat, 18 Jun 2022 23:16:14 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/06/online-offline.png 3577 0 0 0 https://discovery.endeavouros.com/legacy-bootloader-location-erase/ Sat, 18 Jun 2022 23:17:43 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/06/legacy-bootloader-location-erase.png 3578 0 0 0 https://discovery.endeavouros.com/legacy-bootloader-location-manuall/ Sat, 18 Jun 2022 23:18:40 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/06/legacy-bootloader-location-manuall.png 3579 0 0 0 https://discovery.endeavouros.com/eos-log-tool/ Sat, 18 Jun 2022 23:30:42 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/06/eos-log-tool.png 3582 0 0 0 https://discovery.endeavouros.com/calamares-installer/ Sat, 18 Jun 2022 23:40:56 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/calamares-installer.png 3585 0 0 0 https://discovery.endeavouros.com/aur/yay-an-aur-helper-written-in-go/2021/03/attachment/yay-search-output/ Fri, 12 Aug 2022 10:27:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/08/yay-search-output.png 3657 1014 0 0 https://discovery.endeavouros.com/aur/yay-an-aur-helper-written-in-go/2021/03/attachment/yay-search-output-1/ Fri, 12 Aug 2022 10:29:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/08/yay-search-output-1.png 3658 1014 0 0 https://discovery.endeavouros.com/system-rescue/repair-a-non-booting-grub/2021/03/attachment/2022-09-09_15-12/ Fri, 09 Sep 2022 13:13:04 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/09/2022-09-09_15-12.png 3685 1588 0 0 https://discovery.endeavouros.com/2022-09-11_18-28/ Sun, 11 Sep 2022 16:28:59 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/09/2022-09-11_18-28.png 3690 0 0 0 https://discovery.endeavouros.com/2022-09-25_19-24/ Sun, 25 Sep 2022 17:25:48 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/09/2022-09-25_19-24.png 3704 0 0 0 https://discovery.endeavouros.com/2022-09-25_19-44/ Sun, 25 Sep 2022 17:45:20 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/09/2022-09-25_19-44.png 3709 0 0 0 https://discovery.endeavouros.com/2022-09-25_19-46/ Sun, 25 Sep 2022 17:46:42 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/09/2022-09-25_19-46.png 3711 0 0 0 https://discovery.endeavouros.com/2022-09-25_19-44-1/ Sun, 25 Sep 2022 17:47:01 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/09/2022-09-25_19-44-1.png 3712 0 0 0 https://discovery.endeavouros.com/2022-09-25_19-53/ Sun, 25 Sep 2022 17:53:21 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/09/2022-09-25_19-53.png 3714 0 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2022-10-04_11-54/ Tue, 04 Oct 2022 09:54:22 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/10/2022-10-04_11-54.png 3719 1029 0 0 https://discovery.endeavouros.com/applications/firewalld/2022/03/attachment/2022-10-04_11-54-1/ Tue, 04 Oct 2022 09:55:43 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/10/2022-10-04_11-54-1.png 3721 3421 0 0 https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/attachment/lsblk-f/ Sun, 04 Dec 2022 14:05:32 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/12/lsblk-f.png 3824 3823 0 0 https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/attachment/arch-chroot/ Sun, 04 Dec 2022 14:07:34 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/12/arch-chroot.png 3825 3823 0 0 https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/attachment/gparted-crypt-open/ Sun, 04 Dec 2022 17:43:06 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/12/gparted-crypt-open.png 3837 3823 0 0 https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/attachment/gparted-mapper-info/ Sun, 04 Dec 2022 17:45:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/12/gparted-mapper-info.png 3838 3823 0 0 https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/attachment/arch-chroot-livesession/ Sun, 04 Dec 2022 17:53:02 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/12/arch-chroot-livesession.png 3842 3823 0 0 https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/attachment/2022-12-05_11-17/ Mon, 05 Dec 2022 10:18:20 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/12/2022-12-05_11-17.png 3848 1182 0 0 https://discovery.endeavouros.com/system-rescue/dracut/2022/12/attachment/dracut/ Sun, 18 Dec 2022 16:26:58 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/12/dracut.png 3856 3855 0 0 https://discovery.endeavouros.com/system-rescue/systemd-boot/2022/12/attachment/systemd-boot/ Sun, 18 Dec 2022 16:47:17 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/12/systemd-boot.png 3860 3859 0 0 https://discovery.endeavouros.com/system-rescue/systemd-boot/2022/12/attachment/systemd-boot-2/ Sun, 18 Dec 2022 16:49:22 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/12/systemd-boot-1.png 3863 3859 0 0 https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/attachment/cassini-arch-chroot/ Sun, 18 Dec 2022 17:10:55 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/12/cassini-arch-chroot.png 3870 3823 0 0 https://discovery.endeavouros.com/encrypted-installation/encrypted-installation/2021/03/attachment/2023-01-03_22-36/ Tue, 03 Jan 2023 21:45:01 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/01/2023-01-03_22-36.png 3914 1170 0 0 https://discovery.endeavouros.com/encrypted-installation/encrypted-installation/2021/03/attachment/2023-01-03_22-37/ Tue, 03 Jan 2023 21:45:14 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/01/2023-01-03_22-37.png 3916 1170 0 0 https://discovery.endeavouros.com/encrypted-installation/encrypted-installation/2021/03/attachment/2023-01-03_22-38/ Tue, 03 Jan 2023 21:45:32 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/01/2023-01-03_22-38.png 3917 1170 0 0 https://discovery.endeavouros.com/encrypted-installation/encrypted-installation/2021/03/attachment/2023-01-03_22-38_1/ Tue, 03 Jan 2023 21:45:53 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/01/2023-01-03_22-38_1.png 3918 1170 0 0 https://discovery.endeavouros.com/encrypted-installation/encrypted-installation/2021/03/attachment/2023-01-03_22-41/ Tue, 03 Jan 2023 21:46:21 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/01/2023-01-03_22-41.png 3919 1170 0 0 https://discovery.endeavouros.com/encrypted-installation/encrypted-installation/2021/03/attachment/2023-01-03_22-41_1/ Tue, 03 Jan 2023 21:46:39 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/01/2023-01-03_22-41_1.png 3920 1170 0 0 https://discovery.endeavouros.com/encrypted-installation/encrypted-installation/2021/03/attachment/2023-01-03_23-02/ Tue, 03 Jan 2023 22:07:20 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/01/2023-01-03_23-02.png 3923 1170 0 0 https://discovery.endeavouros.com/encrypted-installation/encrypted-installation/2021/03/attachment/2023-01-03_22-41-1/ Tue, 03 Jan 2023 22:09:18 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/01/2023-01-03_22-41-1.png 3924 1170 0 0 https://discovery.endeavouros.com/nvidia/nvidia-optional-enhancements-and-troubleshooting/2021/03/attachment/2023-01-07_14-52/ Sat, 07 Jan 2023 13:53:12 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/01/2023-01-07_14-52.png 3936 1037 0 0 https://discovery.endeavouros.com/audio/pulseaudio/2021/12/attachment/2023-01-25_14-24/ Wed, 25 Jan 2023 13:47:55 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/01/2023-01-25_14-24.png 3952 2737 0 0 https://discovery.endeavouros.com/hardware/envy-control/2023/03/attachment/light/ Tue, 14 Mar 2023 11:58:57 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/03/light.png 3996 3994 0 0 https://discovery.endeavouros.com/hardware/envy-control/2023/03/attachment/envycontrol/ Tue, 14 Mar 2023 12:05:31 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/03/envycontrol.png 4000 3994 0 0 https://discovery.endeavouros.com/applications/beginners-guide-to-mpd-config-and-clients/2021/08/attachment/mpd/ Thu, 23 Mar 2023 13:42:21 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/08/mpd.webp 4029 2383 0 0 https://discovery.endeavouros.com/applications/how-to-install-virt-manager-complete-edition/2021/09/attachment/bildschirmfoto-vom-2023-04-03-19-18-04/ Mon, 03 Apr 2023 17:20:12 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/04/Bildschirmfoto-vom-2023-04-03-19-18-04.png 4070 2440 0 0 https://discovery.endeavouros.com/applications/how-to-install-virt-manager-complete-edition/2021/09/attachment/bildschirmfoto-vom-2023-04-03-19-19-06/ Mon, 03 Apr 2023 17:21:21 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/04/Bildschirmfoto-vom-2023-04-03-19-19-06.png 4071 2440 0 0 https://discovery.endeavouros.com/applications/how-to-install-virt-manager-complete-edition/2021/09/attachment/bildschirmfoto-vom-2023-04-03-19-24-50/ Mon, 03 Apr 2023 17:25:31 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/04/Bildschirmfoto-vom-2023-04-03-19-24-50.png 4072 2440 0 0 https://discovery.endeavouros.com/applications/how-to-install-virt-manager-complete-edition/2021/09/attachment/virtmanager-2/ Mon, 03 Apr 2023 17:35:06 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/04/virtManager.png 4079 2440 0 0 https://discovery.endeavouros.com/system-rescue/how-to-boot-without-a-graphical-environment/2021/03/attachment/2023-04-15_21-38/ Sat, 15 Apr 2023 19:42:50 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/04/2023-04-15_21-38.png 4091 1580 0 0 https://discovery.endeavouros.com/system-rescue/how-to-boot-without-a-graphical-environment/2021/03/attachment/2023-04-15_21-44/ Sat, 15 Apr 2023 19:45:23 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/04/2023-04-15_21-44.png 4092 1580 0 0 https://discovery.endeavouros.com/applications/uniform-theme-and-fonts-for-qt-apps-in-gtk-environments/2021/05/attachment/2023-04-18_08-06/ Tue, 18 Apr 2023 06:07:16 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/04/2023-04-18_08-06.png 4102 2062 0 0 https://discovery.endeavouros.com/2023-04-25_09-33/ Tue, 25 Apr 2023 07:45:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/04/2023-04-25_09-33.png 4115 0 0 0 https://discovery.endeavouros.com/2023-04-25_09-50/ Tue, 25 Apr 2023 07:57:32 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/04/2023-04-25_09-50.png 4116 0 0 0 https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/attachment/2023-06-01_12-46/ Thu, 01 Jun 2023 10:49:13 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/06/2023-06-01_12-46.png 4138 1182 0 0 https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/attachment/2023-06-01_12-50/ Thu, 01 Jun 2023 10:50:12 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/06/2023-06-01_12-50.png 4140 1182 0 0 https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/attachment/2023-06-01_12-53/ Thu, 01 Jun 2023 10:53:42 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/06/2023-06-01_12-53.png 4142 1182 0 0 https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/attachment/2023-06-14_22-42/ Wed, 14 Jun 2023 20:57:16 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/06/2023-06-14_22-42.png 4147 1018 0 0 https://discovery.endeavouros.com/system-rescue/systemd-boot/2022/12/attachment/2023-07-11_14-49/ Tue, 11 Jul 2023 12:50:15 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/07/2023-07-11_14-49.png 4165 3859 0 0 https://discovery.endeavouros.com/system-rescue/systemd-boot/2022/12/attachment/2023-07-11_15-10/ Tue, 11 Jul 2023 13:11:14 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/07/2023-07-11_15-10.png 4168 3859 0 0 https://discovery.endeavouros.com/btrfs/btrfs-basic-information-and-troubleshooting/2023/07/attachment/btrfs_logo/ Tue, 11 Jul 2023 13:24:09 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/07/Btrfs_logo.png 4173 4171 0 0 https://discovery.endeavouros.com/system-rescue/systemd-boot/2022/12/attachment/2023-07-11_15-10-1/ Tue, 11 Jul 2023 15:33:03 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/07/2023-07-11_15-10-1.png 4179 3859 0 0 https://discovery.endeavouros.com/encrypted-installation/btrfs-with-timeshift-snapshots-on-the-grub-menu/2022/02/attachment/2023-07-30_10-06/ Sun, 30 Jul 2023 08:25:38 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/07/2023-07-30_10-06.png 4188 3346 0 0 https://discovery.endeavouros.com/encrypted-installation/btrfs-with-timeshift-snapshots-on-the-grub-menu/2022/02/attachment/2023-07-30_10-06-1/ Sun, 30 Jul 2023 08:26:14 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/07/2023-07-30_10-06-1.png 4190 3346 0 0 https://discovery.endeavouros.com/encrypted-installation/btrfs-with-timeshift-snapshots-on-the-grub-menu/2022/02/attachment/2023-07-30_10-07/ Sun, 30 Jul 2023 08:26:14 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/07/2023-07-30_10-07.png 4191 3346 0 0 https://discovery.endeavouros.com/encrypted-installation/btrfs-with-timeshift-snapshots-on-the-grub-menu/2022/02/attachment/2023-07-30_10-30/ Sun, 30 Jul 2023 08:34:26 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/07/2023-07-30_10-30.png 4192 3346 0 0 https://discovery.endeavouros.com/encrypted-installation/btrfs-with-timeshift-snapshots-on-the-grub-menu/2022/02/attachment/2023-07-30_10-32/ Sun, 30 Jul 2023 08:34:26 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/07/2023-07-30_10-32.png 4193 3346 0 0 https://discovery.endeavouros.com/encrypted-installation/btrfs-with-timeshift-snapshots-on-the-grub-menu/2022/02/attachment/2023-07-30_10-33/ Sun, 30 Jul 2023 08:34:27 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/07/2023-07-30_10-33.png 4194 3346 0 0 https://discovery.endeavouros.com/encrypted-installation/btrfs-with-timeshift-snapshots-on-the-grub-menu/2022/02/attachment/2023-07-30_14-01/ Sun, 30 Jul 2023 12:01:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/07/2023-07-30_14-01.png 4197 3346 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2023-08-13_21-27/ Sun, 13 Aug 2023 19:28:57 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/08/2023-08-13_21-27.png 4200 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2023-08-13_21-26_1/ Sun, 13 Aug 2023 19:28:57 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/08/2023-08-13_21-26_1.png 4201 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2023-08-13_21-28/ Sun, 13 Aug 2023 19:28:57 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/08/2023-08-13_21-28.png 4202 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2023-08-13_21-28_1/ Sun, 13 Aug 2023 19:28:58 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/08/2023-08-13_21-28_1.png 4203 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2023-08-13_21-32/ Sun, 13 Aug 2023 19:33:09 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/08/2023-08-13_21-32.png 4204 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2023-08-13_21-33/ Sun, 13 Aug 2023 19:35:24 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/08/2023-08-13_21-33.png 4205 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2023-08-13_21-36/ Sun, 13 Aug 2023 19:36:14 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/08/2023-08-13_21-36.png 4206 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2023-08-13_21-34/ Sun, 13 Aug 2023 19:36:32 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/08/2023-08-13_21-34.png 4207 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2023-08-13_21-39/ Sun, 13 Aug 2023 19:39:53 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/08/2023-08-13_21-39.png 4208 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2023-08-13_21-38_1/ Sun, 13 Aug 2023 19:40:13 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/08/2023-08-13_21-38_1.png 4209 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/2023-08-13_21-38/ Sun, 13 Aug 2023 19:40:23 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/08/2023-08-13_21-38.png 4210 1029 0 0 https://discovery.endeavouros.com/applications/firewalld/2022/03/attachment/2023-08-22_15-02/ Tue, 22 Aug 2023 13:05:34 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/08/2023-08-22_15-02.png 4221 3421 0 0 https://discovery.endeavouros.com/applications/firewalld/2022/03/attachment/2023-08-22_15-08/ Tue, 22 Aug 2023 13:09:25 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/08/2023-08-22_15-08.png 4223 3421 0 0 https://discovery.endeavouros.com/applications/firewalld/2022/03/attachment/2023-08-22_15-05/ Tue, 22 Aug 2023 13:09:41 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/08/2023-08-22_15-05.png 4224 3421 0 0 https://discovery.endeavouros.com/applications/flatpak-enabling-and-application-management/2021/03/attachment/2023-09-15_07-56/ Fri, 15 Sep 2023 05:56:44 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/09/2023-09-15_07-56.jpg 4257 1760 0 0 https://discovery.endeavouros.com/endeavouros-tools/telegram-helpchat-and-reddit-discussion-rules/2021/11/attachment/telegra-rules/ Thu, 28 Sep 2023 22:11:51 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/11/telegra-rules.png 4266 2679 0 0 https://discovery.endeavouros.com/endeavouros-tools/telegram-helpchat-and-reddit-discussion-rules/2021/11/attachment/telegra-rules-2/ Thu, 28 Sep 2023 22:15:53 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/11/telegra-rules-1.png 4267 2679 0 0 https://discovery.endeavouros.com/encrypted-installation/btrfs-with-timeshift-snapshots-on-the-grub-menu/2022/02/attachment/snap4/ Sun, 01 Oct 2023 20:38:43 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/10/snap4.png 4282 3346 0 0 https://discovery.endeavouros.com/encrypted-installation/btrfs-with-timeshift-snapshots-on-the-grub-menu/2022/02/attachment/snap5/ Sun, 01 Oct 2023 20:38:43 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/10/snap5.png 4283 3346 0 0 https://discovery.endeavouros.com/encrypted-installation/btrfs-with-timeshift-snapshots-on-the-grub-menu/2022/02/attachment/snap2/ Sun, 01 Oct 2023 20:38:43 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/10/snap2.png 4284 3346 0 0 https://discovery.endeavouros.com/encrypted-installation/btrfs-with-timeshift-snapshots-on-the-grub-menu/2022/02/attachment/snap3/ Sun, 01 Oct 2023 20:38:44 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/10/snap3.png 4285 3346 0 0 https://discovery.endeavouros.com/encrypted-installation/btrfs-with-timeshift-snapshots-on-the-grub-menu/2022/02/attachment/snap1/ Sun, 01 Oct 2023 20:38:44 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/10/snap1.png 4286 3346 0 0 https://discovery.endeavouros.com/encrypted-installation/btrfs-with-timeshift-snapshots-on-the-grub-menu/2022/02/attachment/btrfs-snap-sysd/ Sun, 01 Oct 2023 20:41:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/10/btrfs-snap-sysd.png 4287 3346 0 0 https://discovery.endeavouros.com/applications/how-to-install-virtualbox/2021/03/attachment/2023-10-05_12-51/ Thu, 05 Oct 2023 11:01:49 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/10/2023-10-05_12-51.png 4298 997 0 0 https://discovery.endeavouros.com/applications/how-to-install-virtualbox/2021/03/attachment/2023-10-05_13-13/ Thu, 05 Oct 2023 11:13:40 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/10/2023-10-05_13-13.png 4299 997 0 0 https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/attachment/2023-11-10_16-12/ Fri, 10 Nov 2023 15:12:52 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/2023-11-10_16-12.png 4314 1182 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2023-11-11_11-02/ Sat, 11 Nov 2023 10:02:47 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/2023-11-11_11-02.png 4320 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2023-11-11_11-04/ Sat, 11 Nov 2023 10:04:20 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/2023-11-11_11-04.png 4322 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2023-11-11_11-05/ Sat, 11 Nov 2023 10:06:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/2023-11-11_11-05.png 4323 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2023-10-17_12-08/ Sat, 11 Nov 2023 10:07:29 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/2023-10-17_12-08.png 4324 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2023-11-11_11-07/ Sat, 11 Nov 2023 10:07:48 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/2023-11-11_11-07.png 4325 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2023-11-11_11-08_1/ Sat, 11 Nov 2023 10:09:00 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/2023-11-11_11-08_1.png 4326 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2023-11-11_11-11/ Sat, 11 Nov 2023 10:11:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/2023-11-11_11-11.png 4327 1184 0 0 https://discovery.endeavouros.com/encrypted-installation/encrypted-installation/2021/03/attachment/2023-11-11_11-13/ Sat, 11 Nov 2023 10:14:27 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/2023-11-11_11-13.png 4329 1170 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2023-11-11_11-19/ Sat, 11 Nov 2023 10:20:58 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/2023-11-11_11-19.png 4332 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2023-11-11_11-19_1/ Sat, 11 Nov 2023 10:21:24 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/2023-11-11_11-19_1.png 4334 1184 0 0 https://discovery.endeavouros.com/installation/customizing-the-endeavouros-install-process/2022/03/attachment/2023-11-11_11-44/ Sat, 11 Nov 2023 10:44:25 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/03/2023-11-11_11-44.png 4339 3449 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2023-11-11_12-38/ Sat, 11 Nov 2023 11:40:18 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/2023-11-11_12-38.png 4341 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2023-11-11_12-40/ Sat, 11 Nov 2023 11:40:34 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/2023-11-11_12-40.png 4342 1184 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/openprinting-1/ Mon, 20 Nov 2023 13:30:31 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/openprinting-1.png 4391 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/printer-setup1/ Mon, 20 Nov 2023 13:31:06 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/printer-setup1.png 4392 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/printer-setup2/ Mon, 20 Nov 2023 13:31:19 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/printer-setup2.png 4393 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/printer-setup3/ Mon, 20 Nov 2023 13:31:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/printer-setup3.png 4395 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/printer-setup4/ Mon, 20 Nov 2023 13:31:36 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/printer-setup4.png 4396 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/printer-setup3-1/ Mon, 20 Nov 2023 13:31:48 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/printer-setup3-1.png 4397 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/printer-setup2-1/ Mon, 20 Nov 2023 13:32:47 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/printer-setup2-1.png 4398 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/printer-setup3-2/ Mon, 20 Nov 2023 13:32:55 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/printer-setup3-2.png 4399 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/printer-setup5/ Mon, 20 Nov 2023 13:33:02 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/printer-setup5.png 4400 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/printer-setup4-1/ Mon, 20 Nov 2023 13:33:09 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/printer-setup4-1.png 4401 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/printer-setup6/ Mon, 20 Nov 2023 13:33:16 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/printer-setup6.png 4402 1029 0 0 https://discovery.endeavouros.com/network/printers/2021/03/attachment/printer-22040/ Mon, 20 Nov 2023 13:48:39 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/printer-22040.png 4404 1029 0 0 https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/attachment/2023-11-20_15-13/ Mon, 20 Nov 2023 14:14:22 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/2023-11-20_15-13.png 4410 1018 0 0 https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/attachment/2023-11-20_15-13-1/ Mon, 20 Nov 2023 14:17:23 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/2023-11-20_15-13-1.png 4414 1018 0 0 https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/attachment/2023-11-20_15-26/ Mon, 20 Nov 2023 14:27:16 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/2023-11-20_15-26.png 4416 1018 0 0 https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/attachment/2023-11-20_15-25/ Mon, 20 Nov 2023 14:27:31 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/2023-11-20_15-25.png 4417 1018 0 0 https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/attachment/2023-11-20_15-26-1/ Mon, 20 Nov 2023 14:27:53 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/2023-11-20_15-26-1.png 4419 1018 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/3-keyboard/ Tue, 21 Nov 2023 19:17:01 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/3-keyboard.png 4427 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/1-language/ Tue, 21 Nov 2023 19:17:01 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/1-language.png 4428 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2-timezone/ Tue, 21 Nov 2023 19:17:02 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/2-timezone.png 4429 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/5-packages-selection/ Tue, 21 Nov 2023 19:17:02 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/5-packages-selection.png 4430 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/4-desktop-selection/ Tue, 21 Nov 2023 19:17:02 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/4-desktop-selection.png 4431 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/6-bootloader/ Tue, 21 Nov 2023 19:17:03 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/6-bootloader.png 4432 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/7-erase-swap/ Tue, 21 Nov 2023 19:17:03 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/7-erase-swap.png 4433 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/8-erase-format/ Tue, 21 Nov 2023 19:17:03 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/8-erase-format.png 4434 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/9-user/ Tue, 21 Nov 2023 19:17:04 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/9-user.png 4435 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/10-summary/ Tue, 21 Nov 2023 19:17:04 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/10-summary.png 4436 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/11-really-want-to-install/ Tue, 21 Nov 2023 19:17:04 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/11-really-want-to-install.png 4437 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/12-donation-slide/ Tue, 21 Nov 2023 19:17:05 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/12-donation-slide.png 4438 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/14-wiki-slide/ Tue, 21 Nov 2023 19:17:05 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/14-wiki-slide.png 4439 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/13-apps-slide/ Tue, 21 Nov 2023 19:17:05 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/13-apps-slide.png 4440 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/15-forum-slide/ Tue, 21 Nov 2023 19:17:05 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/15-forum-slide.png 4441 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/16-log-view/ Tue, 21 Nov 2023 19:17:06 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/16-log-view.png 4442 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/17-all-done/ Tue, 21 Nov 2023 19:17:06 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/17-all-done.png 4443 1184 0 0 https://discovery.endeavouros.com/hardware/envy-control/2023/03/attachment/2023-11-24_23-53/ Fri, 24 Nov 2023 22:54:26 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/11/2023-11-24_23-53.png 4446 3994 0 0 https://discovery.endeavouros.com/system-rescue/dracut/2022/12/attachment/dracut-2/ Mon, 11 Dec 2023 00:05:19 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/12/dracut.webp 4453 3855 0 0 https://discovery.endeavouros.com/installation/customizing-the-endeavouros-install-process/2022/03/attachment/2023-12-20_15-49/ Wed, 20 Dec 2023 14:53:49 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/12/2023-12-20_15-49.png 4459 3449 0 0 https://discovery.endeavouros.com/installation/customizing-the-endeavouros-install-process/2022/03/attachment/2023-12-20_15-50/ Wed, 20 Dec 2023 14:54:35 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/12/2023-12-20_15-50.png 4460 3449 0 0 https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/attachment/rufus-windows/ Tue, 19 Mar 2024 22:56:27 +0000 https://discovery.endeavouros.com/wp-content/uploads/2024/03/rufus-windows.png 4529 1182 0 0 https://discovery.endeavouros.com/system-rescue/repair-a-non-booting-grub/2021/03/attachment/2024-03-24_15-47/ Sun, 24 Mar 2024 14:48:00 +0000 https://discovery.endeavouros.com/wp-content/uploads/2024/03/2024-03-24_15-47.png 4532 1588 0 0 https://discovery.endeavouros.com/system-rescue/repair-a-non-booting-grub/2021/03/attachment/2024-03-24_15-57/ Sun, 24 Mar 2024 14:57:25 +0000 https://discovery.endeavouros.com/wp-content/uploads/2024/03/2024-03-24_15-57.png 4536 1588 0 0 https://discovery.endeavouros.com/system-rescue/repair-a-non-booting-grub/2021/03/attachment/2024-03-24_16-00/ Sun, 24 Mar 2024 15:01:03 +0000 https://discovery.endeavouros.com/wp-content/uploads/2024/03/2024-03-24_16-00.png 4537 1588 0 0 https://discovery.endeavouros.com/system-rescue/repair-a-non-booting-grub/2021/03/attachment/2024-03-24_15-57-1/ Sun, 24 Mar 2024 15:02:27 +0000 https://discovery.endeavouros.com/wp-content/uploads/2024/03/2024-03-24_15-57-1.png 4538 1588 0 0 https://discovery.endeavouros.com/bash/bash-customizations/2024/04/attachment/bash/ Thu, 04 Apr 2024 11:19:05 +0000 https://discovery.endeavouros.com/wp-content/uploads/2024/04/bash.png 4562 4561 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-47/ Wed, 08 May 2024 11:24:36 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-47.png 4628 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-32_7/ Wed, 08 May 2024 11:24:38 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-32_7.png 4629 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-32_6/ Wed, 08 May 2024 11:24:39 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-32_6.png 4630 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-32_5/ Wed, 08 May 2024 11:24:41 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-32_5.png 4631 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-32_4/ Wed, 08 May 2024 11:24:42 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-32_4.png 4632 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-32_3/ Wed, 08 May 2024 11:24:43 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-32_3.png 4633 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-32_2/ Wed, 08 May 2024 11:24:45 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-32_2.png 4634 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-32_1/ Wed, 08 May 2024 11:24:46 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-32_1.png 4635 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-32/ Wed, 08 May 2024 11:24:47 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-32.png 4636 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-31_3/ Wed, 08 May 2024 11:24:47 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-31_3.png 4637 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-31_2/ Wed, 08 May 2024 11:24:48 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-31_2.png 4638 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-31_1/ Wed, 08 May 2024 11:24:49 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-31_1.png 4639 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-31/ Wed, 08 May 2024 11:24:49 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-31.png 4640 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-30_7/ Wed, 08 May 2024 11:24:50 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-30_7.png 4641 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-30_6/ Wed, 08 May 2024 11:24:51 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-30_6.png 4642 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-30_5/ Wed, 08 May 2024 11:24:52 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-30_5.png 4643 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-30_4/ Wed, 08 May 2024 11:24:53 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-30_4.png 4644 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-30_3/ Wed, 08 May 2024 11:24:54 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-30_3.png 4645 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-30_2/ Wed, 08 May 2024 11:24:57 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-30_2.png 4646 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-30_1/ Wed, 08 May 2024 11:24:59 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-30_1.png 4647 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-30/ Wed, 08 May 2024 11:25:00 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-30.png 4648 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-29_2/ Wed, 08 May 2024 11:25:02 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-29_2.png 4649 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-29_1/ Wed, 08 May 2024 11:25:03 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-29_1.png 4650 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-29/ Wed, 08 May 2024 11:25:05 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-29.png 4651 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-28_1/ Wed, 08 May 2024 11:25:06 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-28_1.png 4652 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-04-23_20-28/ Wed, 08 May 2024 11:25:08 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-04-23_20-28.png 4653 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-06-26_13-15/ Wed, 26 Jun 2024 11:15:46 +0000 https://discovery.endeavouros.com/wp-content/uploads/2024/06/2024-06-26_13-15.png 4728 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-06-26_14-17/ Wed, 26 Jun 2024 12:18:54 +0000 https://discovery.endeavouros.com/wp-content/uploads/2024/06/2024-06-26_14-17.png 4729 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-06-26_14-17_1/ Wed, 26 Jun 2024 12:19:20 +0000 https://discovery.endeavouros.com/wp-content/uploads/2024/06/2024-06-26_14-17_1.png 4730 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-06-26_14-41/ Wed, 26 Jun 2024 12:42:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2024/06/2024-06-26_14-41.png 4731 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-06-26_14-40/ Wed, 26 Jun 2024 12:42:32 +0000 https://discovery.endeavouros.com/wp-content/uploads/2024/06/2024-06-26_14-40.png 4732 1184 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/2024-06-26_14-55/ Wed, 26 Jun 2024 12:56:04 +0000 https://discovery.endeavouros.com/wp-content/uploads/2024/06/2024-06-26_14-55.png 4733 1184 0 0 https://discovery.endeavouros.com/audio/getting-information-while-having-sound-issues/2021/03/attachment/screenshot_20240704_011257/ Wed, 03 Jul 2024 23:13:28 +0000 https://discovery.endeavouros.com/wp-content/uploads/2024/07/Screenshot_20240704_011257.png 4762 1160 0 0 https://discovery.endeavouros.com/endeavouros-tools/welcome/2021/03/attachment/2024-09-15_00-26/ Sat, 14 Sep 2024 22:48:19 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-09-15_00-26.png 4783 1001 0 0 https://discovery.endeavouros.com/endeavouros-tools/welcome/2021/03/attachment/2024-09-15_00-47/ Sat, 14 Sep 2024 22:48:19 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/2024-09-15_00-47.png 4784 1001 0 0 https://discovery.endeavouros.com/applications/kde-plasma/2024/09/attachment/kde/ Fri, 20 Sep 2024 16:48:12 +0000 https://discovery.endeavouros.com/wp-content/uploads/2024/09/kde.png 4802 4799 0 0 https://discovery.endeavouros.com/desktop-environments/gnome-desktop/2024/09/attachment/gnome/ Fri, 20 Sep 2024 17:42:23 +0000 https://discovery.endeavouros.com/wp-content/uploads/2024/09/gnome.png 4807 4804 0 0 https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/attachment/no-efi-error/ Sat, 28 Sep 2024 12:34:28 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/no-efi-error.png 4825 1182 0 0 https://discovery.endeavouros.com/signature-and-keyring/how-to-check-and-trust-key-and-signature-for-the-endeavouros-iso/2025/01/attachment/2025-01-02_19-15/ Thu, 02 Jan 2025 18:15:47 +0000 https://discovery.endeavouros.com/wp-content/uploads/2025/01/2025-01-02_19-15.png 4865 4864 0 0 https://discovery.endeavouros.com/signature-and-keyring/how-to-check-and-trust-key-and-signature-for-the-endeavouros-iso/2025/01/attachment/2025-01-02_19-19/ Thu, 02 Jan 2025 18:22:21 +0000 https://discovery.endeavouros.com/wp-content/uploads/2025/01/2025-01-02_19-19.png 4866 4864 0 0 https://discovery.endeavouros.com/signature-and-keyring/how-to-check-and-trust-key-and-signature-for-the-endeavouros-iso/2025/01/attachment/2025-01-02_19-20/ Thu, 02 Jan 2025 18:23:26 +0000 https://discovery.endeavouros.com/wp-content/uploads/2025/01/2025-01-02_19-20.png 4867 4864 0 0 https://discovery.endeavouros.com/signature-and-keyring/how-to-check-and-trust-key-and-signature-for-the-endeavouros-iso/2025/01/attachment/2025-01-02_19-25/ Thu, 02 Jan 2025 18:25:16 +0000 https://discovery.endeavouros.com/wp-content/uploads/2025/01/2025-01-02_19-25.png 4868 4864 0 0 https://discovery.endeavouros.com/signature-and-keyring/how-to-check-and-trust-key-and-signature-for-the-endeavouros-iso/2025/01/attachment/screenshot_20250203_211806/ Mon, 03 Feb 2025 20:19:44 +0000 https://discovery.endeavouros.com/wp-content/uploads/2025/01/Screenshot_20250203_211806.png 4883 4864 0 0 https://discovery.endeavouros.com/encrypted-installation/btrfs-with-timeshift-snapshots-on-the-grub-menu/2022/02/attachment/btrfs-snapdhots-grub/ Tue, 18 Feb 2025 16:22:16 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/02/btrfs-snapdhots-grub.png 4894 3346 0 0 https://discovery.endeavouros.com/hardware/switcheroo-control/2025/02/attachment/2025-02-21_00-13/ Thu, 20 Feb 2025 23:14:54 +0000 https://discovery.endeavouros.com/wp-content/uploads/2025/02/2025-02-21_00-13.png 4907 4904 0 0 https://discovery.endeavouros.com/hardware/switcheroo-control/2025/02/attachment/2025-02-21_00-41/ Thu, 20 Feb 2025 23:42:16 +0000 https://discovery.endeavouros.com/wp-content/uploads/2025/02/2025-02-21_00-41.png 4909 4904 0 0 https://discovery.endeavouros.com/hardware/switcheroo-control/2025/02/attachment/hybrid/ Fri, 21 Feb 2025 00:14:24 +0000 https://discovery.endeavouros.com/wp-content/uploads/2025/02/hybrid.png 4913 4904 0 0 https://discovery.endeavouros.com/gaming/steam-lutris-wine/2022/01/attachment/2025-02-26_21-56/ Wed, 26 Feb 2025 21:23:54 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/01/2025-02-26_21-56.png 4920 3059 0 0 https://discovery.endeavouros.com/signature-and-keyring/how-to-check-and-trust-key-and-signature-for-the-endeavouros-iso/2025/01/attachment/2025-03-04_23-47/ Tue, 04 Mar 2025 22:47:44 +0000 https://discovery.endeavouros.com/wp-content/uploads/2025/01/2025-03-04_23-47.png 4929 4864 0 0 https://discovery.endeavouros.com/installation/customizing-the-endeavouros-install-process/2022/03/attachment/2025-04-29_16-21/ Tue, 29 Apr 2025 14:23:52 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/03/2025-04-29_16-21.png 4972 3449 0 0 https://discovery.endeavouros.com/installation/customizing-the-endeavouros-install-process/2022/03/attachment/2025-04-29_16-51/ Tue, 29 Apr 2025 14:51:40 +0000 https://discovery.endeavouros.com/wp-content/uploads/2022/03/2025-04-29_16-51.png 4974 3449 0 0 https://discovery.endeavouros.com/endeavouros-tools/akm/2021/08/attachment/2025-05-01_01-30/ Wed, 30 Apr 2025 23:30:45 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/08/2025-05-01_01-30.png 4976 2330 0 0 https://discovery.endeavouros.com/endeavouros-tools/akm/2021/08/attachment/2025-05-01_01-31/ Wed, 30 Apr 2025 23:31:38 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/08/2025-05-01_01-31.png 4978 2330 0 0 https://discovery.endeavouros.com/arm/homeserver-5-configure-a-windows-client-for-samba/2021/04/attachment/image-5/ Sun, 04 Apr 2021 01:35:32 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/04/image.png 1865 1864 0 0 https://discovery.endeavouros.com/endeavouros-tools/welcome/2021/03/attachment/assistant/ Thu, 30 Sep 2021 19:23:34 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/assistant.png 2590 1001 0 0 https://discovery.endeavouros.com/endeavouros-tools/welcome/2021/03/attachment/after-install/ Tue, 30 May 2023 14:51:38 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/05/after-install.png 4131 1001 0 0 https://discovery.endeavouros.com/endeavouros-tools/welcome/2021/03/attachment/assistant-2/ Tue, 30 May 2023 14:52:51 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/05/assistant.png 4133 1001 0 0 https://discovery.endeavouros.com/endeavouros-tools/welcome/2021/03/attachment/install/ Tue, 30 May 2023 14:55:22 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/05/install.png 4134 1001 0 0 https://discovery.endeavouros.com/endeavouros-tools/welcome/2021/03/attachment/general-info/ Tue, 30 May 2023 14:56:17 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/05/general-info.png 4135 1001 0 0 https://discovery.endeavouros.com/endeavouros-tools/welcome/2021/03/attachment/add-more-apps/ Tue, 30 May 2023 15:46:31 +0000 https://discovery.endeavouros.com/wp-content/uploads/2023/05/add-more-apps.png 4136 1001 0 0 https://discovery.endeavouros.com/audio/pipewire/2021/09/attachment/da98457ec756fdc5c05ecfcb97110c033a206f12/ Mon, 12 May 2025 10:45:45 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/da98457ec756fdc5c05ecfcb97110c033a206f12.png 4993 2519 0 0 https://discovery.endeavouros.com/audio/pipewire/2021/09/attachment/65c0b089e9d8e8683fc642107c1e270262e1935b/ Mon, 12 May 2025 10:46:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/65c0b089e9d8e8683fc642107c1e270262e1935b.png 4994 2519 0 0 https://discovery.endeavouros.com/audio/pipewire/2021/09/attachment/2269f9b2a98206143e5781dbdf4bed89e0e6d0b1/ Mon, 12 May 2025 10:46:49 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/09/2269f9b2a98206143e5781dbdf4bed89e0e6d0b1.jpeg 4995 2519 0 0 https://discovery.endeavouros.com/applications/how-to-install-virtualbox/2021/03/attachment/screenshot_2025-06-14_12-46-45/ Sat, 14 Jun 2025 10:50:03 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/screenshot_2025-06-14_12-46-45.png 5019 997 0 0 https://discovery.endeavouros.com/applications/how-to-install-virtualbox/2021/03/attachment/screenshot_2025-06-14_12-49-13/ Sat, 14 Jun 2025 10:51:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/screenshot_2025-06-14_12-49-13.png 5020 997 0 0 https://discovery.endeavouros.com/applications/how-to-install-virtualbox/2021/03/attachment/screenshot_2025-06-14_12-58-31/ Sat, 14 Jun 2025 11:00:02 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/screenshot_2025-06-14_12-58-31.png 5022 997 0 0 https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/attachment/logs-logs-logs/ Thu, 07 Aug 2025 00:46:31 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/logs-logs-logs.png 5043 1018 0 0 https://discovery.endeavouros.com/audio/bluetooth/2021/03/attachment/screenshot_20250921_141730/ Sun, 21 Sep 2025 12:20:26 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/Screenshot_20250921_141730.png 5075 1089 0 0 https://discovery.endeavouros.com/audio/bluetooth/2021/03/attachment/screenshot_20250921_141253/ Sun, 21 Sep 2025 12:21:24 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/Screenshot_20250921_141253.png 5076 1089 0 0 https://discovery.endeavouros.com/audio/bluetooth/2021/03/attachment/screenshot_20250921_141625/ Sun, 21 Sep 2025 12:21:42 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/Screenshot_20250921_141625.png 5077 1089 0 0 https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/attachment/online-offline-2/ Thu, 25 Sep 2025 08:48:26 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/online-offline.png 5088 1184 0 0 https://discovery.endeavouros.com/endeavouros-tools/endeavouros-update-notifier/2021/03/attachment/eos-update-notifier-config/ Sat, 04 Apr 2026 18:00:12 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/eos-update-notifier-config.png 5243 1008 0 0 https://discovery.endeavouros.com/endeavouros-tools/endeavouros-update-notifier/2021/03/attachment/eos-update-notifier-scheduler/ Sat, 04 Apr 2026 18:00:26 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/03/eos-update-notifier-scheduler.png 5244 1008 0 0 https://discovery.endeavouros.com/arm/homeserver-5-configure-a-windows-client-for-samba/2021/04/attachment/image-1-2/ Sun, 04 Apr 2021 01:45:35 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/04/image-1.png 1866 1864 0 0 https://discovery.endeavouros.com/arm/homeserver-5-configure-a-windows-client-for-samba/2021/04/attachment/image-2-2/ Sun, 04 Apr 2021 01:48:06 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/04/image-2.png 1867 1864 0 0 https://discovery.endeavouros.com/arm/homeserver-6-install-and-setup-a-minidlna-media-server/2021/04/attachment/image-3-2/ Sun, 04 Apr 2021 02:29:42 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/04/image-3.png 1873 1872 0 0 https://discovery.endeavouros.com/arm/homeserver-6-install-and-setup-a-minidlna-media-server/2021/04/attachment/image-4-2/ Sun, 04 Apr 2021 02:38:59 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/04/image-4.png 1874 1872 0 0 https://discovery.endeavouros.com/arm/homeserver-6-install-and-setup-a-minidlna-media-server/2021/04/attachment/image-5-2/ Sun, 04 Apr 2021 02:48:05 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/04/image-5.png 1878 1872 0 0 https://discovery.endeavouros.com/arm/homeserver-6-install-and-setup-a-minidlna-media-server/2021/04/attachment/image-6/ Sun, 04 Apr 2021 02:51:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/04/image-6.png 1879 1872 0 0 https://discovery.endeavouros.com/desktop-environments/xfce-hi-dpi-screens/2021/06/attachment/set-all2/ Tue, 22 Jun 2021 19:48:47 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/06/Set-all2.png 2108 2107 0 0 https://discovery.endeavouros.com/desktop-environments/xfce-hi-dpi-screens/2021/06/attachment/set-disp/ Tue, 22 Jun 2021 19:49:40 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/06/set-disp.png 2109 2107 0 0 https://discovery.endeavouros.com/desktop-environments/xfce-hi-dpi-screens/2021/06/attachment/set-set/ Tue, 22 Jun 2021 19:50:54 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/06/set-set.png 2110 2107 0 0 https://discovery.endeavouros.com/desktop-environments/xfce-hi-dpi-screens/2021/06/attachment/set-wmg/ Tue, 22 Jun 2021 19:54:19 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/06/set-wmg.png 2111 2107 0 0 https://discovery.endeavouros.com/desktop-environments/xfce-hi-dpi-screens/2021/06/attachment/set-app/ Wed, 23 Jun 2021 04:48:37 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/06/set-app.png 2120 2107 0 0 https://discovery.endeavouros.com/pacman/easy-downgrade-by-date/2021/06/attachment/date-choose/ Fri, 25 Jun 2021 18:08:10 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/06/date-choose.png 2126 2123 0 0 https://discovery.endeavouros.com/pacman/easy-downgrade-by-date/2021/06/attachment/date-choose-1/ Fri, 25 Jun 2021 18:17:05 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/06/date-choose-1.png 2128 2123 0 0 https://discovery.endeavouros.com/?attachment_id=2167 Wed, 30 Jun 2021 14:03:09 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/06/start.png 2167 2166 0 0 https://discovery.endeavouros.com/?attachment_id=2168 Wed, 30 Jun 2021 14:06:22 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/06/Timeshift6.png 2168 2166 0 0 https://discovery.endeavouros.com/applications/beginners-guide-to-mpd-config-and-clients/2021/08/attachment/mpd_1_cantata_welcome_screen/ Fri, 27 Aug 2021 15:05:42 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/08/mpd_1_cantata_welcome_screen.png 2393 2383 0 0 https://discovery.endeavouros.com/applications/beginners-guide-to-mpd-config-and-clients/2021/08/attachment/mpd_2_server_config/ Fri, 27 Aug 2021 15:06:44 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/08/mpd_2_server_config.png 2394 2383 0 0 https://discovery.endeavouros.com/applications/beginners-guide-to-mpd-config-and-clients/2021/08/attachment/mpd_3_covers/ Fri, 27 Aug 2021 15:10:07 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/08/mpd_3_covers.png 2395 2383 0 0 https://discovery.endeavouros.com/applications/beginners-guide-to-mpd-config-and-clients/2021/08/attachment/cantata-play-screen/ Fri, 27 Aug 2021 15:15:37 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/08/cantata-play-screen.png 2396 2383 0 0 https://discovery.endeavouros.com/applications/beginners-guide-to-mpd-config-and-clients/2021/08/attachment/malp_android/ Fri, 27 Aug 2021 15:24:13 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/08/malp_android.jpg 2397 2383 0 0 https://discovery.endeavouros.com/news/pacify/2019/11/ Sat, 02 Nov 2019 13:40:31 +0000 https://discovery.endeavouros.com/uncategorized/pacify/ 262 0 0 0 https://discovery.endeavouros.com/news/colormag/2016/12/ Thu, 08 Dec 2016 09:06:40 +0000 http://demo.themegrill.com/colormag/2016/12/08/colormag/ 456 0 0 0 https://discovery.endeavouros.com/news/endeavouros/2021/03/ Fri, 08 Nov 2019 19:52:38 +0000 https://discovery.endeavouros.com/uncategorized/endeavouros/ 502 0 1 0 https://discovery.endeavouros.com/news/forum/2021/03/ Fri, 08 Nov 2019 19:52:40 +0000 https://discovery.endeavouros.com/uncategorized/forum/ 504 0 3 0 https://discovery.endeavouros.com/news/donate/2021/03/ Thu, 14 Nov 2019 09:53:37 +0000 https://discovery.endeavouros.com/news/donate/2019/11/ 609 0 6 0 https://discovery.endeavouros.com/news/1469/2021/03/ Thu, 18 Mar 2021 12:09:51 +0000 https://discovery.endeavouros.com/news/1469/2021/03/ 1469 0 7 0 https://discovery.endeavouros.com/news/telegram/2021/03/ Thu, 18 Mar 2021 12:56:32 +0000 https://discovery.endeavouros.com/news/telegram/2021/03/ 1484 0 4 0 https://discovery.endeavouros.com/news/1494/2021/03/ Thu, 18 Mar 2021 16:03:01 +0000 https://discovery.endeavouros.com/news/1494/2021/03/ 1494 0 1 0 https://discovery.endeavouros.com/news/1495/2021/03/ Thu, 18 Mar 2021 16:03:03 +0000 https://discovery.endeavouros.com/news/1495/2021/03/ 1495 0 6 0 https://discovery.endeavouros.com/news/endeavouros-2/2021/03/ Thu, 18 Mar 2021 16:03:05 +0000 https://discovery.endeavouros.com/news/endeavouros-2/2021/03/ 1496 0 3 0 https://discovery.endeavouros.com/?attachment_id=2169 Wed, 30 Jun 2021 14:08:01 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/06/choose-dest.png 2169 2166 0 0 https://discovery.endeavouros.com/?attachment_id=2170 Wed, 30 Jun 2021 14:09:40 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/06/chose-dest4.png 2170 2166 0 0 https://discovery.endeavouros.com/?attachment_id=2171 Wed, 30 Jun 2021 14:10:40 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/06/choose-dest-1.png 2171 2166 0 0 https://discovery.endeavouros.com/?attachment_id=2172 Wed, 30 Jun 2021 14:12:36 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/06/daily.png 2172 2166 0 0 https://discovery.endeavouros.com/?attachment_id=2173 Wed, 30 Jun 2021 14:16:08 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/06/done.png 2173 2166 0 0 https://discovery.endeavouros.com/?attachment_id=2174 Wed, 30 Jun 2021 14:18:30 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/06/Timeshift-8.png 2174 2166 0 0 https://discovery.endeavouros.com/endeavouros-tools/akm/2021/08/attachment/akm/ Tue, 17 Aug 2021 06:52:56 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/08/akm.png 2332 2330 0 0 https://discovery.endeavouros.com/endeavouros-tools/akm/2021/08/attachment/akminwelcome/ Tue, 17 Aug 2021 06:56:32 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/08/akmInWelcome.png 2333 2330 0 0 https://discovery.endeavouros.com/endeavouros-tools/akm/2021/08/attachment/akmistallfromterminal/ Tue, 17 Aug 2021 08:47:41 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/08/akmIstallFromTerminal.png 2355 2330 0 0 https://discovery.endeavouros.com/endeavouros-tools/akm/2021/08/attachment/akm-added-repo/ Tue, 17 Aug 2021 09:36:40 +0000 https://discovery.endeavouros.com/wp-content/uploads/2021/08/akm-added-repo.png 2372 2330 0 0 https://discovery.endeavouros.com/ Tue, 01 Oct 2019 11:53:46 +0000 https://discovery.endeavouros.com/?page_id=32

Boost up your knowledge during the exploration of your Endeavour

This is the EndeavourOS knowledge base, the place where you can find our ever-growing wiki articles and some in-depth articles to expand your knowledge for both x86-64 and ARM-based systems.

To enhance the experience, you can also find video tutorials from the Youtube channels Distrotube, Chris Titus Tech, Eric Adams and EF Linux all in one place. The videos of these renowned content creators are here to add an extra layer of convenience in your search for solutions, helping to boost up your knowledge and confidence so you can persevere in the challenges your journey can bring.

So put on your jet pack to get ready for your spacewalk and enjoy the full Endeavour experience with Discovery at your side. And just remember, don't hesitate to ask for help on our forum, Telegram or Reddit page if something isn't clear for you, the community is your living and breathing lifeline, no matter how far you've ventured in the exploration of your Endeavour.

Categories

ACPI kernel parameters

Articles related to the kernel.

Applications

Articles related to apps like Timeshift, Flatpak, etc.

ARM

Tutorials on how to set up EndeavourOS ARM.

Articles

Various in-depth articles.

Audio

Articles on general sound, Pulseaudio and Pipewire.

AUR

Explanation about the AUR and a yay tutorial.

Bluetooth

Articles for setting up Bluetooth and wireless audio related articles.

BTRFS

Tutorials for BTRFS.

Desktop environments

Removing, adding and improving performance Linux DEs and articles about display managers.

Encrypted installation

How to install EndeavourOS with encryption, LUKS and LUKS on BTRFS.

EndeavourOS tools

Articles on our own EOS tools and a community guideline for our social media channels.

Forum log tool option

An easy tool to help the forum community solve issues.

Gaming

How to set up EndeavourOS for Gamers.

Grub and Refind

Articles on Grub and the alternative to Grub, Refind.

Hardware

A tutorial to lower power consumption and cooling.

Installation

Articles on our Live ISO, Calamares and more.

Intel GPU

An article related to the Intel integrated GPU.

Network

Articles related to troubleshooting various network issues.

Nvidia

Articles on Nvidia GPU.

Pacman

Articles to give you a better understanding of Pacman and its commands.

Printers

A how-to on installing printers on EndeavourOS.

Signature and keyring

Article on what to do when Pacman warns you about signature and keyring issues.

Storage and partitions

Various articles to prolong or troubleshoot your HDD, SSD, NVME.

System rescue

Troubleshooting the system using Arch-chroot etc.

Video tutorials

Various video tutorials by Chris Titus Tech, Eric Adams and EFLinux.

Window managers

Articles on several Window Managers.

]]> 32 0 1 0 https://discovery.endeavouros.com/?p=150 Sat, 02 Nov 2019 08:34:10 +0000 https://discovery.endeavouros.com/?p=150

How to enable Nvidia Optimus

_{<by community member Wimmetje>}

[icon name="flag" prefix="fas"] NOTE: This needs a review and may not work properly anymore (12.11.2021 joekamprad)

For who?
This guide is purely for hybrid graphics laptops with Intel/Nvidia graphics cards, so no need for installing it on desktops.

The Nvidia installer that comes with EOS is just fine to use and works with no problem with the Bumblebee service to switch between Intel en Nvidia graphics. So you can save some battery when mobile.

So why use Optimus Manager instead of Bumblebee?
The Optimus Manager has the same functionality as Bumblebee, (despite the technical differences) it allows you to switch between Intel and Nvidia graphics on hybrid laptops.

The difference is that Optimus Manager has better performance for gaming and has support for the Vulkan drivers so you can properly game with the latest games on Linux (Lutris, Steam, Wine).

First step

Nvidia-installer-dkms
Endeavour OS has its own Nvidia-installer script that is ported from Antergos, with this script you can get the latest Nvidia proprietary drivers and the Bumblebee option to switch between Intel and Nvidia.
This install script with the Bumblebee is necessary to get the Nvidia driver working next to the Intel graphics.

Run in Terminal

nvidia-installer-dkms -b

(-b is bumblebee option)

1. reboot
2. After reboot check the Nvidia-settings in the Menu launcher or via Terminal:

nvidia-settings

If correct it will be showing the driver version and all the Nvidia graphics information.

At this point you got the Nvidia driver installed with the bumblebee option, so basically, you can switch between the two graphics cards.
The only downside is that Bumblebee is lacking in performance and doesn’t support Vulkan drivers to proper run games with Wine, Lutris, Steam, etc.

Second step

Optimus-manager
Now we are going to install Optimus Manager and disable Bumblebee so there is no interference.
Optimus Manager has basically the same function as Bumblebee but does it with better performance and Vulkan support.

Run in Terminal

yay optimus-manager-qt

(this will install the Optimus Manager + Tray application to easy switch between Intel/Nvidia)

Don’t reboot

sudo systemctl disable bumblebeed.service

(By this we disabled the bumblebee daemon)

1. Go to /etc/X11/xorg.conf.d/ and disable any graphic related configs. Instead of deleting them, just rename them by adding .bak. (Possible that there aren’t any related files, so you can go to the next step)
2. Go to /etc/X11/ and disable any related graphics configs (The same situation as above, Probably there isn’t any related files, so you can get to the next step)
3. Reboot
4. After the reboot open Optimus Manager via the Menu launcher, a tray icon will appear with the “Intel” logo in it. Richt-click, go in settings and check “Launch at startup”.
   
5. In Terminal:

systemctl status optimus-manager.service

check if it runs correctly and with no errors

1. Now switch to Nvidia GPU, right-click on the Tray and select “Switch to Nvidia “
2. After login again, type in the terminal

nvidia-settings

If correct it will be showing the driver version and all the Nvidia graphics information.

Here it is, you installed the Nvidia drivers with all the potential unlocked.
After this, you can install all the supported Vulkan drivers and play games with Wine, Lutris, and Steam with full performance.

Troubleshooting:

If you have trouble booting into the graphical system on bumblebee you can blacklist Nvidia and nouveau drivers from the grub kernel boot line:

adding modprobe.blacklist=nouveau if you do not have Nvidia drivers installed, so it will boot with intel GPU only.

adding both: modprobe.blacklist=nouveau modprobe.blacklist=nvidia if you have Nvidia drivers installed, as it may load nouveau-driver from the kernel (if not already blacklisted).

Simple press “e” (for edit) when you reach the grub boot menu:

• Use the arrow keys to find the line looks like this: linux /vmlinuz=linux root=UUID=…… rw quiet resume=…. (… = long snake of numbers)
• put systemd.unit=multi-user.target right after rw like this: rw modprobe.blacklist=nouveau modprobe.blacklist=nvidia resume=....
• Press Ctrl+X to boot with this parameter.

For EFI/UEFI boot:

Press “e” use the right arrow key to reach the end of the line and add the parameter at the end press enter to boot.

All Nvidia entries: https://discovery.endeavouros.com/?s=nvidia

]]> 150 0 53 0 https://discovery.endeavouros.com/?p=904 https://discovery.endeavouros.com/?p=904

In this article we hope to show you how not to install software.

First of all, let me say that this has been a long time coming. There are many otherwise good projects, on github and elsewhere, and many "online guides" posted in forums and even articles which instruct users to do something like this:

As root:

1.) Download release archive

2.) Extract binary files and chmod +x

3.) Move them to /usr/bin

Quite often this is merely the first part of a longer configuration and setup process.

This, my friends, is exactly how not to install software in linux. Perhaps there was a time when my Downloads folder was full of binaries downloaded from the internet, but there was also a time in human history when man rubbed two sticks together to make fire. We have come a long way since that time.

]]> 904 0 15 0 https://discovery.endeavouros.com/wiki/ Tue, 09 Mar 2021 10:48:20 +0000 https://discovery.endeavouros.com/?page_id=993 993 0 4 0 https://discovery.endeavouros.com/?p=1091 Thu, 11 Mar 2021 11:14:10 +0000 https://discovery.endeavouros.com/?p=1091

Get Bluetooth auto-connected with A2DB

_{by joekamprad}

Unpair your headphone first. (With the DE Bluetooth-Settings or bluetoothctl)

To make your headphone auto connect each time you enable it, you need to enable the switch-on-connect module from Pulseaudio:

sudo nano /etc/pulse/default.pa

 Then put these two lines to the end:

# automatically switch to newly-connected devices 
load-module module-switch-on-connect

Are you using GDM?

Then do this:
Prevent systemd from starting Pulseaudio anyway with socket activation :

These two commands will do the trick:

sudo -ugdm mkdir -p /var/lib/gdm/.config/systemd/user sudo -ugdm ln -s /dev/null /var/lib/gdm/.config/systemd/user/pulseaudio.socket

You can also use the solution to address this problem with this:

pulseaudio-bluetooth-a2dp-gdm-fix [yay -S pulseaudio-bluetooth-a2dp-gdm-fix]

Continue for everyone:

Now it is time to connect and recognize your headphone:

bluetoothctl is the tool we use here from the terminal:

bluetoothctl
power on
agent on
default-agent
scan on
pair XX:XX:XX:XX:XX:XX < your headphones "ID"
trust XX:XX:XX:XX:XX:XX
connect XX:XX:XX:XX:XX:XX
scan off
exit

Check if your headphone is listed under sound devices and is connected via A2DP profile:

If you’re menu only displays Headset Head Unit (HSP/HFP) then this means it also covers the additional microphone that’s built-in with your headphone, for HIFI Headphone choose High Fidelity Playback A2DP.

As far as I can see it will take the last state for each new automatic connection.

And it is done!

To see if it works > reboot system if you do it right and for sure you are lucky to have chosen good hardware, or the right one working together

Now, each time you power on your headphone, just system auto-connecting it with High Definition Audioprofile [A2DP]. 

Troubleshooting:

It happens after updates or if you use dual-booting with Windows that the headset only connects HSB/HFP.

Sometimes it helps to simple disable and re-enable device.

If that does not help try to remove the disable device and reinitialize it.

And last if all of that do not work try rfkill:

sudo rfkill block bluetooth
sudo rfkill unblock bluetooth
sudo systemctl restart bluetooth

]]> 1091 0 22 0 https://discovery.endeavouros.com/?p=1097 Thu, 11 Mar 2021 12:05:22 +0000 https://discovery.endeavouros.com/?p=1097

Samba sharing

_{by joekamprad}

Installation:

Install samba and needed apps:
sudo pacman -S samba gvfs-smb --needed

stop the samba smb nmb services…

sudo systemctl stop samba smb nmb

Configuration:

Verify if smb.conf file exist…
ls /etc/samba

if not then copy the file examples/smb.conf from https://git.samba.org to smb.conf  (this fix also sharing printer troubleshooting)…

Just take this content.
https://git.samba.org/samba.git/?p=samba.git;a=blob_plain;f=examples/smb.conf.default;hb=HEAD

and place the file in /etc/samba/smb.conf

create a group sambashare…
sudo groupadd -r sambashare

create usershare folder…
sudo mkdir -p /var/lib/samba/usershare

change group of usershare folder…
sudo chown root:sambashare /var/lib/samba/usershare

change mode w/sticky bit on usershare folder…
sudo chmod 1770 /var/lib/samba/usershare

verify if your user is in samba DB…
sudo pdbedit -L -v

if not then add your user to samba (then create new sharing password)…
sudo smbpasswd -a "your-user-name"

if you would prefer to use tdbsam rather than smbpasswd:
sudo pdbedit -a -u "your-user-name"

then add you user to sambashare group:
sudo gpasswd -a "your-user-name" sambashare

edit smb.conf…
sudo gedit /etc/samba/smb.conf

Use any editor you want instead of gedit. nano will be easy to use and runs inside terminal.

uncomment following line in /etc/samba/smb.conf file under [global] settings section…
include = /etc/samba/smb.conf

if you are using tdbsam rather than smbpasswd uncomment the line in /etc/samba/smb.conf file under [global] settings section…
passdb backend = tdbsam

add following lines at the end of [global] section of smb.conf file then save file and exit the editor…

usershare path = /var/lib/samba/usershare
usershare max shares = 100
usershare allow guests = yes
usershare owner only = yes

Starting:

make sure following services are enabled (to start at boot):
sudo systemctl enable samba smb nmb

Firewall:

If you use a firewall (which is recommended!) then you must set a couple of ports open to allow the Netbios service (nmbd) to reach your PC.

Check if you have gufw installed…
pacman -Qs gufw

if not then install it…
sudo pacman -S gufw

then enable it…
sudo systemctl enable ufw

Now you must enable the firewall following ports related to nmbd service:
137/udp to everyone
138/udp to everyone

and following ports related to smbd service:
139/tcp to everyone
445/tcp to everyone

For firewall settings and troubleshooting see internet documentations:
https://help.ubuntu.com/community/Gufw (except for installation instructions that concern to ubuntu!!).

Now reboot the system…

For Gnome:

sudo pacman -S nautilus-share gnome-user-share

then, when your system is ready, try to open nautilus (Files)
choose a folder to share, right click on it, then
choose Properties –> Sharing and check Sharing this folder…

now – for test – view network resource in nautilus, click on icon with
your PC name, click on it, then click on shared folder and enter
the sharing password previously set…

…and joy!

For XFCE:

For XFCE use thunar and make sure you have package: thunar-shares-plugin installed

System Config Samba:

• The Samba configuration tool by Red Hat

is also working on an Arch-based distro like EndeavourOS:

https://aur.archlinux.org/packages/system-config-samba/

To build and install it from the AUR:

yay -S system-config-samba

Get config available:

https://git.samba.org/samba.git/?p=samba.git;a=blob_plain;f=examples/smb.conf.default;hb=HEAD

copy from the website and paste it inside this file:

sudo nano /etc/samba.conf

save with [Ctrl+o] end exit with [ctrl+x]

then start and enable (to get it started automatic on boot)

sudo systemctl start samba smb nmb

sudo systemctl enable samba smb nmb

Now you can use system-config-samba!

Notes:

1) Sometimes sharing isn’t working immediately, and it takes some time to work after boot.

2) We advise to use Samba only if necessary, like in a home server environment or NAS, or to connect to a Windows system. It is more stable to use NFS that is already integrated with the Linux kernel.

]]> 1097 0 20 0 https://discovery.endeavouros.com/privacy-policy/ Thu, 18 Mar 2021 00:07:13 +0000 https://discovery.endeavouros.com/?page_id=1440

Who we are

This Privacy Policy governs the manner in which EndeavourOS collects, uses, maintains and discloses information collected from users (each, a “User”) of the website.

What information do we collect?

We collect information from you when you register on our site and gather data when you participate in the forum by reading, writing, and evaluating the content shared here.

When registering on our site, you may be asked to enter your name and e-mail address. You may, however, visit our site without registering. Your e-mail address will be verified by an email containing a unique link. If that link is visited, we know that you control the e-mail address.

When registered and posting, we record the IP address that the post originated from. We also may retain server logs which include the IP address of every request to our server.

What do we use your information for?

Any of the information we collect from you may be used in one of the following ways:

• To personalize your experience — your information helps us to better respond to your individual needs.
• To improve our site — we continually strive to improve our site offerings based on the information and feedback we receive from you.
• To improve customer service — your information helps us to more effectively respond to your customer service requests and support needs.
• To send periodic emails — The email address you provide may be used to send you information, notifications that you request about changes to topics or in response to your user name, respond to inquiries, and/or other requests or questions.

How do we protect your information?

We implement a variety of security measures to maintain the safety of your personal information when you enter, submit, or access your personal information.

What is your data retention policy?

We will make a good faith effort to:

• Retain server logs containing the IP address of all requests to this server no more than 90 days.
• Retain the IP addresses associated with registered users and their posts no more than 5 years.

Contact forms

Using our contact forms will use our mail server hosted by Strato located in Germany. Your data will be only processed internally and not shared with any 3rd-party group in that case.

Cookies

Our Site may use “cookies” to enhance User experience. User’s web browser places cookies on their hard drive for record-keeping purposes and sometimes to track information about them. The user may choose to set their web browser to refuse cookies or to alert you when cookies are being sent. If they do so, note that some parts of the Site may not function properly.

If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.

If you have an account and you log in to this site, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.

When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.

If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.

Sharing your personal information

We do not sell, trade, or rent User’s personal identification information to others. We may share generic aggregated demographic information not linked to any personal identification information regarding visitors and users with our business partners and trusted affiliates for the purposes outlined above. We may use third-party service providers to help us operate our business and the Site or administer activities on our behalfs, such as sending out newsletters or surveys. We may share your information with these third parties for those limited purposes provided that you have given us your permission.

How long do we retain your data

If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.

For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.

Embedded content from other websites

Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.

These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracing your interaction with the embedded content if you have an account and are logged in to that website.

Media

If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.

Payment Services

We offer to donate to our project via Open Collective and Open Collective Europe ASBL acts as our fiscal host. You can read their terms of service over here.

Anti-virus software

Our server runs clamav anti-virus software, to protect you from viruses and malware on any computer platform. (Linux, Windows and Macos) Our WordPress server is also using Akismet, an anti-spam comment service. You can read their terms of services over here.

Free software

EndeavourOS develops free software. All our tools (eos-welcome-greeter, reflector-auto and eos-update-notifier ) are and will always be free software. EndeavourOS is part of OIN since July 2019. The current license can be viewed here. Additional information about packages covered by this license can be viewed here.

If you want to check the license of a package, you can do so with Pacman. Also, check if there is a folder called /usr/share/licenses/ in your system; if so, it should contain license information for that package.

What rights you have over your data

If you have an account on this site or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.

Where we send your data

Visitor comments may be checked through an automated spam detection service.

Where do I find the privacy policy of the forum

The usage of our forums may vary slightly. Please read here about the conditions, which will apply to the usage of our forums.

Changes to this privacy policy

Our website has the discretion to update this privacy policy at any time. When we do, we will post a notification on the main page of our Site, revise the updated date at the bottom of this page. We encourage Users to frequently check this page for any changes to stay informed about how we are helping to protect the personal information we collect. You acknowledge and agree that it is your responsibility to review this privacy policy periodically and become aware of modifications.

Your acceptance of these terms

By using this Site, you signify your acceptance of this policy. If you do not agree to this policy, please do not use our Site. Your continued use of the Site following the posting of changes to this policy will be deemed your acceptance of those changes.

Contacting us

If you have any questions about this Privacy Policy, the practices of this site, or your dealings with this site, please contact us via email.

This privacy policy has been updated on October 29th 2019.

]]> 1440 0 0 0 .wp-block-themeisle-blocks-advanced-columns-overlay{opacity:.5;mix-blend-mode:normal;border-radius:0}#wp-block-themeisle-blocks-advanced-column-55ab884f{padding:20px;margin-top:20px;margin-right:0;margin-bottom:20px;margin-left:0;border:0 solid #000;border-radius:0}@media (min-width:960px){#wp-block-themeisle-blocks-advanced-column-55ab884f{flex-basis:100%}}]]> https://discovery.endeavouros.com/news/endeavouros-arm-2/2021/03/ Thu, 18 Mar 2021 16:03:07 +0000 https://discovery.endeavouros.com/news/endeavouros-arm-2/2021/03/ 1497 0 4 0 https://discovery.endeavouros.com/news/forum-2/2021/03/ Thu, 18 Mar 2021 16:03:10 +0000 https://discovery.endeavouros.com/news/forum-2/2021/03/ 1498 0 2 0 https://discovery.endeavouros.com/news/donate-2/2021/03/ Thu, 18 Mar 2021 18:26:03 +0000 https://discovery.endeavouros.com/news/donate-2/2021/03/ 1510 0 5 0 https://discovery.endeavouros.com/?p=1742 Mon, 29 Mar 2021 14:06:44 +0000 https://discovery.endeavouros.com/?p=1742

by 2000

(We recommend this tutorial for advanced Linux users)

Full disk encryption: LVMonLUKS with a separate home partition and hibernation with a swapfile

Note: If you don’t necessarily need a separate home partition the tutorial provided in the wiki article “Encrypted installation” may suffice. With the exception of the swapfile creation it fully relies on GUI-tools.

What you’ll end up getting:

• LVMonLUKS – fully LUKS encrypted single partition containing two logical volumes (“virtual” partitions)
  (1) a logical volume (lv) holding a ext4 filesystem with /boot, /‘root’ and
  (2) a separate lv (ext4) for /home
• optional free space in the volume group to hold lvm-snapshots and/or potentially extend/shrink the logical volumes later on
• swapfile, with the ability to hibernate

---

e. g. end result with a 500GiB drive on a UEFI system

+--------------+-----------------------------------------------------------------------+
 Boot  512MiB | LV 1      40GiB    | LV 2     430GiB      |  free 30GiB 
 /boot/efi          | /   (+swapfile)     | /home                     |                    
                        | /dev/vg0/lvroot   | /dev/vg0/lvhome     |                    
                        |_ _ _ _ _ _ _ _ _ |_ _ _ _ _ _ _ _ _ _ _ |_ _ _ _ _ _ _
 /dev/sda1       |       LUKS (dm-crypt) encrypted /dev/sda2               
+--------------+------------------------------------------------------------------------+

---

e. g. end result with a 500GiB drive on a BIOS (legacy) system

+-----------+-------------------------------------------------------------------+
      8MiB     | LV 1      40GiB | LV 2     430GiB       | free 30GiB  
 bios_grub  | /   (+swapfile)    | /home                    |                      
                   | /dev/vg0/lvroot  | /dev/vg0/lvhome    |                    
                   |_ _ _ _ _ _ _ _ _|_ _ _ _ _ _ _ _ _ _ _|_ _ _ _ _ _ _ 
 /dev/sda1  |      LUKS (dm-crypt) encrypted /dev/sda2       
+-----------+--------------------------------------------------------------------+

---

The following is a tutorial on setting up this type of system with the help of calamares (the EOS installer) and the cli.

++++++++++++++++++++++++++++++++++++++++++

#01 – Boot into Live-CD environment & set up partitions

With the help of GParted, just follow the steps described below.

---

(a) for UEFI systems:

• create a GPT partition table
• create sda1 with 300 to 512MiB, format fat32 and set boot & esp flag
• create sda2 with xGiB unformatted
• leave a rest of 8GiB unallocated (on the far right)

+---------------------+-------------------------+---------------------+
 300-512MiB       |      rest          xGiB |        8GiB     
 flag: boot & esp |      unformatted      | unallocated 
 format: fat32      |                               |                    
 /dev/sda1           |      /dev/sda2         |                    
+---------------------+-------------------------+---------------------+

---

(b) for BIOS (legacy boot) systems:

• create a GPT partition table
• create sda1 with 8MiB, leave unformatted and set bios_grub flag
• create sda2 with xGiB unformatted
• leave a rest of 8GiB unallocated (on the far right)

+-----------------+-------------------------+--------------------------+
8MiB                 |      rest          xGiB     |        8GiB 
flag: bios_grub  |      unformatted         | unallocated 
unformatted      |                                  |             
/dev/sda1         |      /dev/sda2             |             
+------------------+----------------------------+----------------------+

---

The unallocated 8GiB of space will hold a temporary installation. We will later reclaim this space by adding it to the LUKS partition on /dev/sda2 and then assign it to e. g. our home volume. For this to work the LUKS partition must reside to the left of the temporary partition because growing a LUKS partition on the right is easy to achieve.

With other storage types, /dev/sda1 could also be called /dev/nvme0n1p1 for example; in this case just substitute sda1 with nvme0n1p1.

---

#02 – Install temporary system with calamares

Set up calamares like you usually would (Location, Keyboard, Users, …) but
choose Manual partioning and edit (double-click the partition(s) in the list view) to the specifications given below …

---

(a) for UEFI systems:

1. /dev/sda1

• Mount point -> /boot/efi
• set boot flag
• keep fat32

2. free space

• Mount point -> /
• File system -> ext4
• Encrypt: choose short password as this is only temporary

Let Calamares finish the installation. If you get a warning about missing esp or boot flag(s) on /dev/sda1 just add them with GParted and continue with the install.

---

(b) for BIOS (legacy boot) systems:

1. free space

• Mount point -> /
• File system -> ext4
• Encrypt: choose short password as this is only temporary

Let Calamares finish the installation. Ignore the window notice “Option to use GPT on BIOS”. We had that set up by gparted already. Continue with the install.

---

---

#03 – Reboot & test; reboot into live-cd

After the install finishes reboot and check if you can access the encrypted system.
You should now have a LUKS encrypted system (without the fun stuff like logical volumes, separate /home partition etc.).
Reboot into the Live-Cd environment.

---

#04 – Open (unencrypt) and mount temporary system

In the live-CD environment, open a Terminal and type (or mark and copy line with ctrl-c and paste in terminal with shift-ctrl-v) …

sudo cryptsetup luksOpen /dev/sda3 crypttemp
sudo mkdir -p /media/crypttemp
sudo mount /dev/mapper/crypttemp /media/crypttemp

Our temporary installation data is now accessible under /media/crypttemp and can be copied to the new system we will be setting up in the next steps.

---

#05 – Set up new LVMonLUKS system

sudo su
cryptsetup luksFormat --type luks1 /dev/sda2

The –type luks1 is crucial because GRUB does not support LUKS2 yet. If your /boot directory is on a LUKS-encrypted device and you use GRUB as your bootloader, it won’t work with LUKS2.
Choose a secure password (https://xkcd.com/936/)

cryptsetup luksOpen /dev/sda2 crypt
pvcreate /dev/mapper/crypt
vgcreate vg0 /dev/mapper/crypt

A good starting size for the root volume (lvroot) is about 30GiB. If you’re planning on using a swapfile residing on root later on, you should factor that in.
Resizing the volumes later on is quite easy, so don’t give this too much thought.
You could assign all the free space left to the home volume with
lvcreate --extents 100%FREE vg0 -n lvhome
but for growing the volumes later on and for snapshots one needs empty space inside the volume group, so I usually choose a size for lvhome that leaves about 30GiB overall unused space in the volume group (assuming a 500GB drive e. g. 500 – 0.512 – 40 – 430 = 29.488)

lvcreate -L 40G vg0 -n lvroot
lvcreate -L 430G vg0 -n lvhome

Create a ext4 filesystem on the logical volumes.

mkfs.ext4 -L root /dev/mapper/vg0-lvroot
mkfs.ext4 -L home /dev/mapper/vg0-lvhome
exit

---

#06 – Mount new system to /mnt

sudo mount /dev/mapper/vg0-lvroot /mnt
sudo mkdir -p /mnt/home
sudo mount /dev/mapper/vg0-lvhome /mnt/home

---

(*) additionally for UEFI systems:

sudo mkdir -p /mnt/boot/efi
sudo mount /dev/sda1 /mnt/boot/efi

---

lsblk

should now provide a similar output to the following (ignore the sizes, these come from a test install) …

---

(a) for UEFI systems:

NAME             MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
loop0              7:0    0  1.7G  1 loop  /run/archiso/sfs/airootfs
sda                8:0    0   20G  0 disk  
├─sda1             8:1    0  512M  0 part  /mnt/boot/efi
├─sda2             8:2    0 12.7G  0 part  
│ └─crypt        254:1    0 12.7G  0 crypt 
│   ├─vg0-lvroot 254:2    0   10G  0 lvm   /mnt
│   └─vg0-lvhome 254:3    0    1G  0 lvm   /mnt/home
└─sda3             8:3    0  6.9G  0 part  
  └─crypttemp    254:0    0  6.9G  0 crypt /media/crypttemp
sr0               11:0    1  1.8G  0 rom   /run/archiso/bootmnt

---

(b) for BIOS (legacy boot) systems:

NAME             MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
loop0              7:0    0  1.7G  1 loop  /run/archiso/sfs/airootfs
sda                8:0    0   20G  0 disk  
├─sda1             8:1    0    8M  0 part  
├─sda2             8:2    0 12.2G  0 part  
│ └─crypt        254:1    0 12.2G  0 crypt 
│   ├─vg0-lvroot 254:2    0   10G  0 lvm   /mnt
│   └─vg0-lvhome 254:3    0    1G  0 lvm   /mnt/home
└─sda3             8:3    0  7.8G  0 part  
  └─crypttemp    254:0    0  7.8G  0 crypt /media/crypttemp
sr0               11:0    1  1.8G  0 rom   /run/archiso/bootmnt

---

---

#07 – Copy temporary system to empty new mount points

sudo rsync -avA /media/crypttemp/ /mnt

---

#08 – Unmount temporary system

sudo umount /media/crypttemp
sudo cryptsetup luksClose crypttemp

---

#09 – Add existing keyfile to Slot 1 of our LUKS-partition

See which slots have keys

sudo cryptsetup luksDump /dev/sda2 | grep Slot

A LUKS-partition can store and be opened by up to eight different passwords. Right now only Slot 0 contains a key (your chosen password) to decrypt. We will now add a second key which was generated by the temporary install. We will reference this key in the next step.

sudo cryptsetup luksAddKey /dev/sda2 /mnt/crypto_keyfile.bin

---

#10 – Set up /etc/crypttab

sudo cryptsetup luksUUID /dev/sda2

for example returns 384fb0a7-101a-4c58-8ed7-4ea177a761e0. Your UUID will be different, so make sure you use your UUID in the next step!

sudo leafpad /mnt/etc/crypttab

contains an uncommented line starting with luks-…
Change this line to the following; remember to use your UUID.

cryptlvm UUID=384fb0a7-101a-4c58-8ed7-4ea177a761e0 /crypto_keyfile.bin luks

Save and exit.

---

#11 – Set up /etc/mkinitcpio.conf

sudo leafpad /mnt/etc/mkinitcpio.conf

Change the HOOKS=… line by adding lvm2 and resume (before filesystems).

HOOKS="base udev autodetect modconf block keyboard keymap encrypt lvm2 resume filesystems fsck"

Save and exit.

---

#12 – Set up /etc/fstab

sudo blkid -s UUID -o value /dev/mapper/vg0-lvroot

returns the UUID of the root volume. For example 5bd28f54-6804-423c-a8c5-f13913793b9a.

sudo blkid -s UUID -o value /dev/mapper/vg0-lvhome

returns the UUID of the home volume. For example de5f20c7-6d53-4f0b-a2c4-8cd8a64eb454.

sudo leafpad /mnt/etc/fstab

contains a line starting with /dev/mapper/luks-…
Remove this line and add the following; remember to use your UUIDs.

UUID=5bd28f54-6804-423c-a8c5-f13913793b9a / ext4 defaults,acl,noatime,discard 0 0

UUID=de5f20c7-6d53-4f0b-a2c4-8cd8a64eb454 /home ext4 defaults,acl,noatime,discard 0 0

Save and exit.

---

#13 – Set up /etc/default/grub

sudo cryptsetup luksUUID /dev/sda2

returns the UUID of the cryptdevice. For example 384fb0a7-101a-4c58-8ed7-4ea177a761e0.

sudo leafpad /mnt/etc/default/grub

In the line starting with GRUB_CMDLINE_LINUX_DEFAULT=…

• change cryptdevice= entry to the following; remember to use your UUID

cryptdevice=UUID=<YOUR-UUID>:cryptlvm:allow-discards rd.luks.options=discard

• change root=… to

root=/dev/mapper/vg0-lvroot

It should now resemble the following:

GRUB_CMDLINE_LINUX_DEFAULT="quiet cryptdevice=UUID=384fb0a7-101a-4c58-8ed7-4ea177a761e0:cryptlvm:allow-discards rd.luks.options=discard root=/dev/mapper/vg0-lvroot loglevel=3 nowatchdog"

Save and exit.

---

#14 – Repair GRUB system

sudo su

arch-chroot /mnt
mkinitcpio -p linux
grub-mkconfig -o /boot/grub/grub.cfg

---

(a) for UEFI systems:

grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=EndeavourOS-grub
rm -rf /boot/efi/EFI/EndeavourOS
cp /boot/efi/EFI/EndeavourOS-grub/grubx64.efi /boot/efi/EFI/boot/bootx64.efi

---

(b) for BIOS (legacy boot) systems:

grub-install --target=i386-pc /dev/sda

---

exit

---

#15 – Reboot & test new encrypted LVMonLUKS system

sudo umount -R /mnt
sudo reboot

DONE! You should now have a functioning LVMonLUKS system with a separate logical volume for /home.

++++++++++++++++++++++++++++++++++++++++++

# OPTIONAL – Add space of temporary partition to LUKS-partition

You could simply reformat /dev/sda3 and use it as unencrypted storage, but here we will reclaim the space and assign it to e. g. our home volume.

---

#16 – Reboot into the Live-Cd environment.

---

#17 – Delete sda3 (temporary EndeavourOS Install)

sudo fdisk -l

displays some information regarding our disks and partitions.

We will now delete /dev/sda3. Just enter the characters below in the given order.

sudo fdisk /dev/sda

> p
> d
> 3 (delete partition 3)
> w (write changes to disk)

---

#18 – Extend /dev/sda2 (LUKS-partition) and the volume group

sudo fdisk /dev/sda

> d
> 2 (delete partition 2)
> n
> 2 (recreate partition 2)
>   (first sector is 'default'; press enter)
>   (last sector is 'default'; press enter)
> n (keep existing filesystem signature)
> w (write changes to disk)

sudo cryptsetup luksOpen /dev/sda2 crypt
sudo cryptsetup resize crypt -v

sudo e2fsck -f /dev/mapper/vg0-lvroot
sudo e2fsck -f /dev/mapper/vg0-lvhome

sudo pvresize /dev/mapper/crypt

The volume group vg0 now contains the space we freed up by deleting /dev/sda3. It was added as free space one could use for snapshots or future assigning to the root or home volume (which we’ll do in the next step) or to additional (new) volumes.

---

#19 – Grow home volume

Theoretically you should be able to resize logical volumes with KDE Partition Manager. I’ve actually never tried this and will stick to the cli.

---

Some information on how to convert/calculate sectors, MB, PE’s:

• sectors / 2048 / 4 = PE
• PE *4 = MiB *2048 = sectors
  If your calculations return a non-integer of PE’s, you have to round it down!

sudo fdisk -l
sudo vgdisplay
sudo lvdisplay
will provide information regarding used (allocated) and free space.

Examples for different growing possibilities:

• grow lvroot by 32326 PE
  sudo lvextend -l+32326 /dev/mapper/vg0-lvroot
• extend the volume to 150GB
  sudo lvextend -L150G /dev/mapper/vg0-lvroot
• extend the volume by 10GB
  sudo lvextend -L+10G /dev/mapper/vg0-lvroot
• fill all of the unallocated space in the volume group
  sudo lvextend -l +100%FREE /dev/vg0-lvroot

---

But we will now add the formerly freed up space (8GiB) to the home volume.

sudo lvextend -L+8G /dev/mapper/vg0-lvhome

adds 8GB to the logical home volume.

The filesystem residing in our logical volume needs to be adjusted as well. We will grow the filesystem to the maximum size to add the 8GB.

sudo resize2fs -p /dev/mapper/vg0-lvhome

Let’s check the resized logical volumes filesystem …

sudo e2fsck -f /dev/mapper/vg0-lvhome

DONE! You can leave the live-cd environment and reboot into your LVMonLUKS-system.

++++++++++++++++++++++++++++++++++++++++++

# OPTIONAL – Add a swapfile (with working hibernation)

---

#20 – Make a swapfile

Note: If you want to use hibernation, then you must add swap because the content of the RAM will be written to the swap partition/file. This also means that the swap size should be at least the size of RAM. Read here about choosing swap sizes for example.

Choose you swapfile size (e. g. “8” for 8GB).

swapsizeGB=8

The following commands will produce a swapfile with your chosen size:

swapsize=$(( swapsizeGB * 1024 ))
sudo dd if=/dev/zero of=/swapfile count=$swapsize bs=1MiB status=progress

sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile

To check …

swapon --show

---

#21 – Edit /etc/fstab to enable the swapfile after reboot

sudo leafpad /etc/fstab

Add the following line …

/swapfile none swap defaults,pri=-2 0 0

Save and exit.

---

#22 – Activate hibernation

sudo blkid -s UUID -o value /dev/mapper/vg0-lvroot

returns the UUID of the root volume. For example 53d2a76e-13b8-4a29-affc-197b33a706c1.

sudo filefrag -v /swapfile | awk '{if($1=="0:"){print $4}}'

returns the swapfile offset. For example 997376.., which means 997376.

sudo leafpad /etc/default/grub

Add the resume=UUID= and resume_offset= entry to the end of GRUB_CMDLINE_LINUX_DEFAULT=; remember to use your UUID and offset.

GRUB_CMDLINE_LINUX_DEFAULT="[...] resume=UUID=53d2a76e-13b8-4a29-affc-197b33a706c1 resume_offset=997376"

Save and exit.

---

If you didn’t already follow step #11 and add resume to /etc/mkinitcpio.conf, do this now …

sudo leafpad /etc/mkinitcpio.conf

Change the HOOKS=… line by adding resume (before filesystems).

HOOKS="base udev autodetect modconf block keyboard keymap encrypt lvm2 resume filesystems fsck"

Save and exit.

---

Let the system know that some things have changed …

sudo mkinitcpio -p linux
sudo grub-mkconfig -o /boot/grub/grub.cfg

DONE! You should now have a swapfile and be able to hibernate.

++++++++++++++++++++++++++++++++++++++++++

Initially posted on the forum: 2019-08-19
Wiki version: 2020-07-29

]]> 1742 0 0 0 https://discovery.endeavouros.com/?p=1750 Mon, 29 Mar 2021 14:23:10 +0000 https://discovery.endeavouros.com/?p=1750

by 2000

Full disk encryption: BTRFSonLUKS with separate root, home and pkg subvolumes; hibernation with a swapfile; auto-snapshots with easy system rollback (GUI); boot into snapshots

This tutorial assumes EndeavourOS will be the only OS on the device.

What you’ll end up getting:

• BTRFSonLUKS (fully LUKS encrypted single partition containing a btrfs filesystem with /boot, /‘root’ and /home)
• /, /home, swapfile, pkg cache as separate subvolumes to allow easy and storage space saving of snapshots of the root system
• automated creation of snapshots (on system upgrade & daily & boot)
• ability to boot into a working snapshot from the grub menu (automated creation of boot entries) and then setting this or other snapshot as new default system (from GUI)
• swapfile, with the ability to hibernate

Not everybody always has the time, knowledge and/or will to go through the process of chrooting, downgrading, and repairing if something breaks.
With this low-maintenance type of setup it should be possible to recover/rollback from a problematic upgrade by simply booting into a working snapshot (these snapshots are created automatically) and setting this as the new default from within the booted system. You could then just wait a couple of days and then check if the upgrade problems still persist. Most of the time the problem will be fixed upstream by then. Note that the creation or restore of a snapshot takes about a second!

The following is a tutorial on setting up this type of system with the help of calamares (the EOS installer) and a little cli.

Note: The provided cli commands can be copied and pasted/run in bulk, adding only a couple of minutes to your normal install time. If you really need to know what is actually happening, I have provided a step-by-step explanation of the used commands in the “BTRFSonLUKS – verbose version” of this tutorial.

Note: For a +++ non-encrypted version +++ of this setup follow the instructions provided in this forum post or see the bottom of this article.

++++++++++++++++++++++++++++++++++++++++++

#01 – Boot into Live-CD environment & set up partitions

With the help of GParted, assuming you have an empty disk …

---

(a) for UEFI systems:

• create a GPT partition table
• create sda1 with 300 to 512MiB, format as fat32 and set boot & esp flag
• leave rest unallocated

+--------------------------+----------------------------------+
 300-512MiB             |      rest                   xGiB 
 flag: boot & esp       |      unallocated          
 format: fat32            |                           
 /dev/sda1                 |                           
+--------------------------+-----------------------------------+

---

(b) for BIOS (legacy boot) systems:

• create a GPT partition table
• create sda1 with 8MiB, leave unformatted and set bios_grub flag
• leave rest unallocated

+---------------------+---------------------------------+
 8MiB                  |      rest                 xGiB
flag: bios_grub    |      unallocated          
unformatted        |                           
/dev/sda1            |                            
+---------------------+----------------------------------+

---

With other storage types, /dev/sda1 could also be called /dev/nvme0n1p1 for example; in this case just substitute sda1 with nvme0n1p1.

---

#02 – OPTIONAL – Change default btrfs calamares settings for fstab

Open a Terminal and type (or mark and copy the commands below with ctrl-c and paste in terminal with shift-ctrl-v | you can always copy&paste all the lines shown in one block at once)

sudo sed -i 's/compress=lzo/compress=zstd/' /usr/share/calamares/modules/fstab.conf
sudo sed -i 's/autodefrag/autodefrag,compress=zstd/' /usr/share/calamares/modules/fstab.conf

---

#03 – Install system with calamares (off- or online install)

Set up calamares like you usually would (Location, Keyboard, Users, …) but
choose Manual partioning and edit (double-click the partition(s) in the list view) to the specifications given below …

---

(a) for UEFI systems:

1. /dev/sda1

• Mount point -> /boot/efi
• set boot flag
• keep fat32

2. free space

• Mount point -> /
• File system -> btrfs
• Encrypt: choose a secure password

Let Calamares finish the installation. If you get a warning about missing esp or boot flag(s) on /dev/sda1 just add them with GParted and continue with the install.

---

(b) for BIOS (legacy boot) systems:

1. free space

• Mount point -> /
• File system -> btrfs
• Encrypt: choose a secure password

Let Calamares finish the installation. Ignore the window notice “Option to use GPT on BIOS”. We had that set up by gparted already. Continue with the install.

---

After the install finishes, do NOT check the “Restart now” checkbox.

---

#04 – Choose your swapfile size

Note: If you want to use hibernation, then you must add swap because the content of the RAM will be written to the swap file. This also means that the swap size should be at least the size of RAM. Read here about choosing swap sizes.

e. g. “8G” or “8192M”

swapsize=8G

---

#05 – Run the following

Just copy&paste all the lines in the terminal at once.

Note: Some of the commands below may report an error if you’re setting up a non uefi system. Just ignore any errors at this stage.

sudo mkdir /mnt/btrfs
btrfsonluks=`sudo blkid -o device | grep luks`
sudo mount -o subvolid=5 $btrfsonluks /mnt/btrfs
sudo sed -i 's/compress=zstd 0 1/compress=zstd 0 0/' /mnt/btrfs/@/etc/fstab
sudo sed -i 's/compress=zstd 0 2/compress=zstd 0 0/' /mnt/btrfs/@/etc/fstab
sudo btrfs subvolume create /mnt/btrfs/@var-cache-pacman-pkg
fstabstr=`grep "/home" /mnt/btrfs/@/etc/fstab`
fstabstr=${fstabstr//\/home/\/var\/cache\/pacman\/pkg}
fstabstr=${fstabstr//@home/@var-cache-pacman-pkg}
sudo sh -c "echo $fstabstr >> /mnt/btrfs/@/etc/fstab"
sudo btrfs subvolume create /mnt/btrfs/@swap
sudo mkdir /mnt/btrfs/@/swap
sudo sh -c "printf '\n$btrfsonluks /swap          btrfs   subvol=@swap,defaults,compress=no 0 0\n' >> /mnt/btrfs/@/etc/fstab"
sudo truncate -s 0 /mnt/btrfs/@swap/swapfile
sudo chattr +C /mnt/btrfs/@swap/swapfile
sudo btrfs property set /mnt/btrfs/@swap/swapfile compression none
sudo fallocate -l $swapsize /mnt/btrfs/@swap/swapfile
sudo chmod 600 /mnt/btrfs/@swap/swapfile
sudo mkswap /mnt/btrfs/@swap/swapfile
sudo swapon /mnt/btrfs/@swap/swapfile
sudo sh -c "echo '/swap/swapfile none swap defaults 0 0' >> /mnt/btrfs/@/etc/fstab"
wget https://raw.githubusercontent.com/osandov/osandov-linux/master/scripts/btrfs_map_physical.c
gcc -O2 -o btrfs_map_physical btrfs_map_physical.c
offset=`sudo ./btrfs_map_physical /mnt/btrfs/@swap/swapfile`
offset_arr=(`echo ${offset}`)
offset_pagesize=(`getconf PAGESIZE`)
offset=$(( offset_arr[25] / offset_pagesize ))
sudo sed -i "s/loglevel=3/loglevel=3 resume_offset=$offset/" /mnt/btrfs/@/etc/default/grub
sudo sed -i "s#loglevel=3#resume=$btrfsonluks loglevel=3#" /mnt/btrfs/@/etc/default/grub
sudo sed -i 's/keymap encrypt filesystems/keymap encrypt filesystems resume/' /mnt/btrfs/@/etc/mkinitcpio.conf
sudo mkdir /mnt/chroot
sudo mount -o compress=zstd,subvol=@ $btrfsonluks /mnt/chroot
efidevice=`sudo blkid -o device -l -t TYPE=vfat`
sudo mount $efidevice /mnt/chroot/boot/efi
sudo arch-chroot /mnt/chroot
sudo pacman --noconfirm -S cronie
sudo systemctl enable cronie.service
sudo grub-mkconfig -o /boot/grub/grub.cfg
sudo mkinitcpio -p linux

---

#06 – REBOOT into your new system

Run the following …

sudo pacman --noconfirm -Syy &&
yay --noconfirm -S timeshift timeshift-autosnap grub-btrfs

Then run …

sudo cp /etc/timeshift/default.json /etc/timeshift/timeshift.json &&
fs_uuid=`sudo blkid -o device | grep luks` &&
fs_uuid=`sudo blkid -o value -s UUID $fs_uuid` &&
sudo sed -i "s/backup_device_uuid\" : \"/backup_device_uuid\" : \"$fs_uuid/" /etc/timeshift/timeshift.json &&
fs_uuid=`sudo blkid -o device -l -t TYPE=crypto_LUKS` &&
fs_uuid=`sudo blkid -o value -s UUID $fs_uuid` &&
sudo sed -i "s/parent_device_uuid\" : \"/parent_device_uuid\" : \"$fs_uuid/" /etc/timeshift/timeshift.json &&
sudo sed -i 's/run" : "true/run" : "false/' /etc/timeshift/timeshift.json &&
sudo sed -i 's/btrfs_mode" : "false/btrfs_mode" : "true/' /etc/timeshift/timeshift.json &&
sudo sed -i 's/  "include_btrfs_home" : "false",/  "include_btrfs_home_for_backup" : "false",\n  "include_btrfs_home_for_restore" : "false",/' /etc/timeshift/timeshift.json &&
sudo sed -i 's/schedule_daily" : "false/schedule_daily" : "true/' /etc/timeshift/timeshift.json &&
sudo sed -i 's/schedule_boot" : "false/schedule_boot" : "true/' /etc/timeshift/timeshift.json &&
sudo sed -i 's/count_boot" : "5/count_boot" : "3/' /etc/timeshift/timeshift.json
sudo timeshift --create --comments "1st"

---

#07 – OPTIONAL – Limit the amount of maximum snapshots

IMPORTANT: Skip this step if you are using grub-btrfs. Otherwise, it can create situation where you are permanently booting off of a snapshot.

Timeshift cleans the automatically created snapshots but the ones you create manually aren’t handled by Timeshift and would be kept indefinetily. Just choose a high number if you prefer to delete these manually and not let the system only keep the newest (e. g.) 15 snapshots.

Note that a large number of snapshots could cause system slowdowns.

Choose the amount of maximum snapshots your system will allow and keep.

max_snapshots=15

Then execute …

sudo sh -c '
cat > /etc/systemd/system/limit-timeshift-snapshots-update-grub.service <<- "EOF"
[Unit]
Description=Keep only latest max_snapshots timeshift snapshots and update grub.cfg before shutdown
Before=poweroff.target

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/bin/true
ExecStop=

[Install]
WantedBy=multi-user.target
EOF
' &&
sudo sed -i "s#max_snapshots#$max_snapshots#" /etc/systemd/system/limit-timeshift-snapshots-update-grub.service &&
sudo sed -i "s#ExecStop=#ExecStop=/usr/bin/sh -c \"cd /run/timeshift/backup/timeshift-btrfs/snapshots/ \&\& rm -rf \`ls -1r | awk 'NR>$max_snapshots'\` \&\& /usr/bin/grub-mkconfig -o /boot/grub/grub.cfg\"#" /etc/systemd/system/limit-timeshift-snapshots-update-grub.service &&
sudo systemctl enable limit-timeshift-snapshots-update-grub.service &&
sudo systemctl start limit-timeshift-snapshots-update-grub.service

---

#08 – OPTIONAL – Create desktop shortcuts for Timeshift

If your Desktop Environment allows desktop shortcuts then running the following will create shortcuts to (1) “Timeshift” and a command to (2) generate a manual snapshot of root.

Note: to get rid of these later on just delete the shortcuts from your desktop

sh -c '
cat > ~/Desktop/timeshift-gtk.desktop <<- "EOF"
[Desktop Entry]
Name=Timeshift
MimeType=
Exec=timeshift-launcher
Type=Application
GenericName=System Restore Utility
Terminal=false
Icon=timeshift
Comment=System Restore Utility
X-KDE-StartupNotify=false
Categories=System;
X-GNOME-UsesNotifications=true
EOF
chmod +x ~/Desktop/timeshift-gtk.desktop
'
sh -c '
cat > ~/Desktop/create_snapshot.desktop <<- "EOF"
[Desktop Entry]
Name=Create Snapshot
Comment=Create btrfs snapshot of root
Exec=
Icon=timeshift
StartupNotify=false
Terminal=true
Type=Application
EOF
' 
sed -i "s#Exec=#Exec=sudo sh -c \'timeshift --create --comments \"manual\" \&\& sleep 2\'#" ~/Desktop/create_snapshot.desktop
chmod +x ~/Desktop/create_snapshot.desktop

---

DONE! You should now have a fully encrypted system with the ability to rollback to automatically (and manually) created snapshots and be able to hibernate.

Note that this setup isn’t meant to be a backup strategy replacement! The snapshots are stored on the same disk as your system; if this fails the snapshots won’t be accessible. At least your /home subvolume should be backuped to another physical device. So, just apply your normal backup strategy of choice.

++++++++++++++++++++++++++++++++++++++++++

# – How to RESTORE a snapshot

---

A – If you ever need to reset your system to a stored state, just

1. Launch Timeshift from the menu (or desktop shortcut)
2. Select a snapshot and hit restore
3. Reboot

That’s all. Takes mere seconds and doesn’t get any easier.
BTW, you could also restore a snapshot from the cli!

---

B – In case you can’t boot into your desktop environment try to

1. Boot directly into a snapshot from the GRUB (boot) menu
2. see A (above) …

---

C – In case you need to restore a snapshot from a live system (e. g. EndeavourOS Install medium)

1. Boot into the live environment
2. Install Timeshift into the live environment by executing

sudo pacman --noconfirm -Syy cronie
yay --noconfirm -S timeshift
 

3. see A (above) …

---

D – In case you need to chroot from a live system (e. g. EndeavourOS Install medium)

1. Boot into the live environment
2. Decrypt and mount your luks partition (e. g. /dev/sda2)

sudo cryptsetup luksOpen /dev/sda2 crypt &&
sudo mount -o compress=zstd,subvol=@ /dev/mapper/crypt /mnt
 

3. Only on UEFI systems: Mount your EFI boot folder (e. g. /dev/sda1)

sudo mount /dev/sda1 /mnt/boot/efi

4. chroot into your system

sudo arch-chroot /mnt

5. Do some root stuff …

#######################################################

+++ non-encrypted version +++

For a “non-encrypted version” of this setup follow the instructions provided above, but …

---

#03
Don’t choose encrypt.

---

#05

• change

btrfsonluks=`sudo blkid -o device | grep luks`

-to-

btrfsonluks=/dev/sda2

---

#06

• change

fs_uuid=`sudo blkid -o device | grep luks` &&

-to-

fs_uuid=`sudo blkid -o device | grep sda2` &&

• delete (do not run) …

fs_uuid=`sudo blkid -o device -l -t TYPE=crypto_LUKS` &&
fs_uuid=`sudo blkid -o value -s UUID $fs_uuid` &&
sudo sed -i "s/parent_device_uuid\" : \"/parent_device_uuid\" : \"$fs_uuid/" /etc/timeshift/timeshift.json &&

---

You should now have an equivalent system to the guide, without the benefit of full disk encryption.

#######################################################

Initially posted on the forum: 2020-03-03
Wiki version: 2020-07-27
2020-09-29 – changed some wording; added info on non-encrypted version
2020-11-29 – addressed timeshift/xapp build bug; undid these changes after an upstream fix; addressed timeshift config location change
2021-12-19 - added warning to step #7

---

]]> 1750 0 0 0 https://discovery.endeavouros.com/?p=1755 Mon, 29 Mar 2021 14:34:06 +0000 https://discovery.endeavouros.com/?p=1755

by 2000

Full disk encryption: BTRFSonLUKS with separate root, home and pkg subvolumes; hibernation with a swapfile; auto-snapshots with easy system rollback (GUI); boot into snapshots

Note: If you’re installing to a dedicated HDD/SSD just copy & paste the commands provided in the wiki article BTRFSonLUKS – quick copy&paste version. The result should be identical but with far less reading ;-).

The following information is just for the technical interested and/or in the event you have a more complicated setting (e. g. dual boot and/or already have multiple vfat or luks partitions); in which case the provided commands in the copy&paste version may mess up your existing setup and need to be adjusted according to the info below.

What you’ll end up getting:

• BTRFSonLUKS (fully LUKS encrypted single partition containing a btrfs filesystem with /boot, /‘root’ and /home)
• /, /home, swapfile, pkg cache as separate subvolumes to allow easy and storage space saving of snapshots of the root system
• automated creation of snapshots (on system upgrade & daily & boot)
• ability to boot into a working snapshot from the grub menu (automated creation of boot entries) and then setting this or other snapshot as new default system (from GUI)
• swapfile, with the ability to hibernate

Not everybody always has the time, knowledge and/or will to go through the process of chrooting, downgrading, and repairing if something breaks.
With this low-maintenance type of setup it should be possible to recover/rollback from a problematic upgrade by simply booting into a working snapshot (these snapshots are created automatically) and setting this as the new default from within the booted system. You could then just wait a couple of days and then check if the upgrade problems still persist. Most of the time the problem will be fixed upstream by then. Note that the creation or restore of a snapshot takes about a second!

The following is a tutorial on setting up this type of system with the help of calamares (the EOS installer) and the cli.

++++++++++++++++++++++++++++++++++++++++++

#01 – Boot into Live-CD environment & set up partitions

With the help of GParted, just follow the steps described below or adjust to your needs.

---

(a) for UEFI systems:

• create a GPT partition table
• create sda1 with 300 to 512MiB, format as fat32 and set boot & esp flag
• leave rest unallocated

+---------------------+-------------------------------+
300-512MiB        |      rest            xGiB 
flag: boot & esp  |      unallocated          
format: fat32       |                           
/dev/sda1            |                           
+---------------------+--------------------------------+

---

(b) for BIOS (legacy boot) systems:

• create a GPT partition table
• create sda1 with 8MiB, leave unformatted and set bios_grub flag
• leave rest unallocated

+------------------+-----------------------------+
8MiB                 |      rest            xGiB 
flag: bios_grub  |      unallocated          
unformatted      |                           
/dev/sda1          |                           
+--------------------+---------------------------+

---

With other storage types, /dev/sda1 could also be called /dev/nvme0n1p1 for example; in this case just substitute sda1 with nvme0n1p1.

---

#02 – OPTIONAL – Change default btrfs calamares settings for fstab

By default the Calamares installer only uses btrfs compression (lzo method) if it detects a ssd.
One can change the used compression method(s) in the installed system itself later on, but this would only compress new files and require recompression of all old files. So why not skip these extra steps and let the installer get it right in one go without adding any extra time to the install.

The following will force calamares to assign and use compression on all btrfs installation devices; regardless of being ssd or hdd. We’ll use zstd compression.

You can find some information about btrfs compression here.

Edit /usr/share/calamares/modules/fstab.conf by running

sudo nano /usr/share/calamares/modules/fstab.conf

and change compress=lzo to compress=zstd in the ssdExtraMountOptions: [...] btrfs: section.

If you want to use compression on a hdd also, just add compress=zstd after autodefrag in the mountOptions: [...] btrfs: section. Save & exit.

_{How to use nano
“nano” is a text editor which aims to introduce a simple interface and intuitive command options to console based text editing.
Some useful keyboard shortcuts:
to copy marked text in nano -> Ctrl+Shift+c
to paste copied text in nano -> Ctrl+Shift+v
to save -> Ctrl+x, then y, followed by Enter}

---

#03 – Install system with calamares (off- or online install)

Set up calamares like you usually would (Location, Keyboard, Users, …) but
choose Manual partioning and edit (double-click the partition(s) in the list view) to the specifications given below …

---

(a) for UEFI systems:

1. /dev/sda1

• Mount point -> /boot/efi
• set boot flag
• keep fat32

2. free space

• Mount point -> /
• File system -> btrfs
• Encrypt: choose a secure password

Let Calamares finish the installation. If you get a warning about missing esp or boot flag(s) on /dev/sda1 just add them with GParted and continue with the install.

---

(b) for BIOS (legacy boot) systems:

1. free space

• Mount point -> /
• File system -> btrfs
• Encrypt: choose a secure password

Let Calamares finish the installation. Ignore the window notice “Option to use GPT on BIOS”. We had that set up by gparted already. Continue with the install.

---

After the install finishes, do NOT check the “Restart now” checkbox.

---

#04 – Mount newly installed btrfs system to temporary directory /mnt/btrfs

sudo mkdir /mnt/btrfs

Find your still unlocked luks device which contains the newly installed system.

sudo blkid -o device | grep luks

The command should produce something like /dev/mapper/luks-4e2dc3d4-16ce-44b9-a6be-a4a73a06e854. Your luks-… device UUID will differ though.

If the command returns more than one /dev/mapper/luks-… line you may have to run lsblk and/or sudo blkid and identify the right one.

Now mount the decrypted device to /mnt/btrfs. Be sure to use the right luks-… device!

sudo mount -o subvolid=5 /dev/mapper/luks-4e2dc3d4-16ce-44b9-a6be-a4a73a06e854 /mnt/btrfs

---

#05 – Adjust/repair fstab for brtfs

If the root file system is btrfs, the fsck order should be set to 0 instead of 1 or higher. The standard fsck has no effect on btrfs partitions and therefore can/should be disabled. Calamares doesn’t set this up right for btrfs partitions and subvolumes so we’ll correct this.

Edit /mnt/btrfs/@/etc/fstab by running

sudo nano /mnt/btrfs/@/etc/fstab

Change the last number of all lines that start with your /dev/mapper/luks-… device (the one from above) to 0. Save & exit.

---

#06 – Create a top-level subvolume for the pacman cache

Calamares has automatically set up / (root) and /home as separate top-level subvolumes. This has the advantage that although /home being mounted under /, if we snapshot the root subvolume /, the /home data and all other subvolumes won’t be stored in that snapshot. We can later restore any root snapshot without affecting the /home or other subvolume data.

On Arch Linux, a subvolume for /var/cache/pacman/pkg is often recommended to make sure the large pacman cache, which often contains GB’s of changing but easily downloadable data, is excluded from snapshots. (Other candidates for exclusion, e. g. /var/abs, /var/tmp, /srv, aren’t part of this tutorial.)
I ran into some trouble during testing when restoring snapshots while setting this up as nested subvolumes, so I decided to stick to top-level subvolumes for this. The downside is we’ll need an entry in fstab for each top-level subvolume.

Create a top-level subvolume named @var-cache-pacman-pkg that will hold all future data stored in /var/cache/pacman/pkg.

sudo btrfs subvolume create /mnt/btrfs/@var-cache-pacman-pkg

As we have a newly installed system, /var/cache/pacman/pkg is still empty, so we don’t need to move any existing data.
We just need to add an entry to /etc/fstab to mount our newly created subvolume to /var/cache/pacman/pkg on the next system start.

• 1. Edit /mnt/btrfs/@/etc/fstab with

sudo nano /mnt/btrfs/@/etc/fstab

• 2. Duplicate the line starting with /dev/mapper/luks-... that contains /home

In this newly created duplicate entry

• 3. replace /home with /var/cache/pacman/pkg
• 4. replace @home with @var-cache-pacman-pkg

Save & exit.

ALTERNATIVELY, you can substitute steps 1. – 4. by running the following commands

fstabstr=`grep "/home" /mnt/btrfs/@/etc/fstab`
fstabstr=${fstabstr//\/home/\/var\/cache\/pacman\/pkg}
fstabstr=${fstabstr//@home/@var-cache-pacman-pkg}
sudo sh -c "echo $fstabstr >> /mnt/btrfs/@/etc/fstab"

---

#07 – Optional – Make a swap file in it’s own top-level subvolume & activate hibernation

Note: If you want to use hibernation, then you must add swap because the content of the RAM will be written to the swap partition/file. This also means that the swap size should be at least the size of RAM. Read here about choosing swap sizes for example.

Swap files in btrfs are supported since Linux kernel 5.x but the swap file cannot be on a snapshotted subvolume. The proper procedure is to create a new subvolume to place the swap file in.

---

#- Create subvolume named @swap (which will be mounted as /swap in the future)

sudo btrfs subvolume create /mnt/btrfs/@swap

#- Create mountpoint /swap

sudo mkdir /mnt/btrfs/@/swap

#- Create an entry in /etc/fstab to mount the subvolume @swap to /swap on every boot

sudo nano /mnt/btrfs/@/etc/fstab

Add the following line …

/dev/mapper/luks-4e2dc3d4-16ce-44b9-a6be-a4a73a06e854 /swap btrfs subvol=@swap,defaults,compress=no 0 0

Make sure to use your luks-UUID! The compress=no makes sure that that there won’t be any btrfs-compression applied to this subvolume holding our swap file. Swap files and btrfs compression don’t do well together!

Save and exit.

---

#- Create the actual swap file

The following will create and activate a swap file of e. g. 8GB size named swapfile in the subvolume @swap. Read here about general swap file creation. Don’t forget to adjust the size to your needs.

sudo truncate -s 0 /mnt/btrfs/@swap/swapfile
sudo chattr +C /mnt/btrfs/@swap/swapfile
sudo btrfs property set /mnt/btrfs/@swap/swapfile compression none

sudo fallocate -l 8G /mnt/btrfs/@swap/swapfile

sudo chmod 600 /mnt/btrfs/@swap/swapfile
sudo mkswap /mnt/btrfs/@swap/swapfile
sudo swapon /mnt/btrfs/@swap/swapfile

---

#- Edit /etc/fstab to enable the swap file after reboot

sudo nano /mnt/btrfs/@/etc/fstab

Add the following line …

/swap/swapfile none swap defaults 0 0

Save and exit.

---

#- Optional: Set up Hibernation into swap file on Btrfs

We need to let the system know the physical offset of our newly created swap file. This wiki entry describes how to do this for btrfs.

1. Download and compile a tool to calculate the physical offset of the swap file …

wget https://raw.githubusercontent.com/osandov/osandov-linux/master/scripts/btrfs_map_physical.c
gcc -O2 -o btrfs_map_physical btrfs_map_physical.c

2. Now run the tool …

sudo ./btrfs_map_physical /mnt/btrfs/@swap/swapfile

3. Note the the first physical offset returned by this tool (the last number of the first line containing numbers). In this example, we use 5749440512.
4. Also note the pagesize (usually 4096) that can be found with

getconf PAGESIZE

5. To compute the resume_offset value, divide the physical offset by the pagesize. In this example, it is 5749440512 / 4096 = 1403672 .
6. We need to add the resume_offset to /etc/default/grub

sudo nano /mnt/btrfs/@/etc/default/grub

Add resume_offset=1403672 (be sure to use your calculated offset!) after loglevel=3 on the line starting with GRUB_CMDLINE_LINUX_DEFAULT= .

7. We also need to add the resume device to /etc/default/grub
   Copy the entry starting with root=/dev/mapper/luks-... and paste before loglevel=3 on the line starting with GRUB_CMDLINE_LINUX_DEFAULT= but substitute root= with resume=.

Save & exit.

8. Configure the initramfs
   When an initramfs with the base hook is used, which is the default, the resume hook is required in /etc/mkinitcpio.conf . Whether by label or by UUID, the swap partition is referred to with a udev device node, so the resume hook must go after the udev hook.

sudo nano /mnt/btrfs/@/etc/mkinitcpio.conf

Add resume after filesystems on the line starting with HOOKS= . Save & exit.

You will need to let the system know that your grub and initramfs settings have changed. This is covered in the next section.

---

#08 – Let the system know that some things have changed & install some needed software

#- chroot into your system

1. make a temporary folder and mount your root system and efi folder

sudo mkdir /mnt/chroot

Mount the root system to the newly created folder. Use your luks-… device (see #04).

sudo mount -o compress=zstd,subvol=@ /dev/mapper/luks-4e2dc3d4-16ce-44b9-a6be-a4a73a06e854 /mnt/chroot

Only on UEFI systems: Mount the partition containing your EFI data (e. g. /dev/sda1) to /mnt/chroot/boot/efi

sudo mount /dev/sda1 /mnt/chroot/boot/efi

2. now chroot into the mounted system

sudo arch-chroot /mnt/chroot

---

#- While we’re in the chroot environment we’ll just install some software we’ll need later on to our newly installed system.

sudo pacman --noconfirm -S cronie
sudo systemctl enable cronie.service

#- Now we’ll update Grub and generate updated kernel images.

sudo grub-mkconfig -o /boot/grub/grub.cfg
sudo mkinitcpio -p linux

---

#09 – REBOOT into your new system & run …

sudo pacman --noconfirm -Syy &&
yay --noconfirm -S timeshift timeshift-autosnap grub-btrfs

This will install the following:

• timeshift => A system restore utility for Linux
• timeshift-autosnap => Timeshift auto-snapshot script which runs before package upgrades using Pacman hook.
• grub-btrfs => Includes btrfs snapshots in GRUB boot options

---

#10 – Configure Timeshift (/etc/timeshift/timeshift.json)

1. Open Timeshift from the menu
2. Select “BTRFS” as the “Snapshot Type”; continue with “Next”
3. Choose your btrfs system partition as “Snapshot Location”; continue with “Next”
4. “Select Snapshot Levels” (type and number of snaphots that will be automatically created and managed/deleted by Timeshift)
   Recommendation:

• Keep “Daily” at 5
• Activate “Boot”, but change to 3; continue with “Finish”

5. Optional: “Create” a manual first snapshot & exit Timeshift

Timeshift will now check on every full hour if snapshots (hourly, daily, weekly, monthly) need to be created or deleted. Note that boot snapshots will actually be created about 10 minutes after boot, not directly at system startup!

---

#11 – Configure timeshift-autosnap (/etc/timeshift-autosnap.conf)

Timeshift-autosnap creates timeshift snapshots whenever it detects a pacman (and yay invoked) upgrade. This way you should be able to rollback to a state right before the package upgrades.

sudo nano /etc/timeshift-autosnap.conf

By default only the last 3 snapshots are kept. You may want to increase the number somewhat (e. g. maxSnapshots=6) because if you invoke a system update by yay for example, there will often be two snapshots created. If you keep a maximum of 6 snapshots you’ll make sure to have at least 3 upgrade cycles worth of snapshots to revert to.

---

#12 – Configure grub-btrfs (/etc/default/grub-btrfs/config)

Grub-btrfs creates Grub boot entries for your snapshots. I recommend leaving the configuration as is and to continue with step #13.

Grub-btrfs is also able to monitor the snapshot folder for changes and automatically update grub if it detects such a change. If you want this behaviour please see grub-btrf’s instructions on how to “Automatically update grub” for use with Timeshift. I decided against this and to just update the grub boot entries on every system shutdown (see #13).

---

#13 – Limit the maximum amount of snapshots & update grub boot entries

IMPORTANT: Skip this step if you are using grub-btrfs. Otherwise, it can create situation where you are permanently booting off of a snapshot.

Timeshift cleans the automatically created snapshots and timeshift-autosnap has a default limit of 3 snapshots after upgrades, BUT the ones you create manually aren’t handled by Timeshift and would be kept indefinetily. High amounts of old snapshots could potentially cause slowdowns, so we’re going to limit the amount of maximum snapshots your system will allow and keep.

For this we will create a systemd service that runs right before you shutdown or restart the system and

• keeps only the newest (e. g. 15) snapshots and deletes all the older ones
• updates grub to contain only these snapshots as boot entries

I recommend to limit the amount of snapshots to about 13 to 15.

Create a systemd service called “limit-timeshift-snapshots-update-grub”:

sudo nano /etc/systemd/system/limit-timeshift-snapshots-update-grub.service

Now add the following content (you can adjust the number of snapshots to keep by changing the number from 15 to whatever in the ExecStop=... line; just choose a high number if you prefer to delete these manually):

[Unit]
Description=Keep only latest 15 timeshift snapshots and update grub.cfg before shutdown
Before=poweroff.target

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/bin/true
ExecStop=/usr/bin/sh -c "cd /run/timeshift/backup/timeshift-btrfs/snapshots/ && rm -rf `ls -1r | awk 'NR>15'` && /usr/bin/grub-mkconfig -o /boot/grub/grub.cfg"


[Install]
WantedBy=multi-user.target

Save & exit.

Next we’ll enable and start the newly created service.

sudo systemctl enable limit-timeshift-snapshots-update-grub.service &&
sudo systemctl start limit-timeshift-snapshots-update-grub.service

---

DONE! You should now have a fully encrypted system with the ability to rollback to automatically (and manually) created snapshots and be able to hibernate.

Note that this setup isn’t meant to be a backup strategy replacement! The snapshots are stored on the same disk as your system; if this fails the snapshots won’t be accessible. At least your /home subvolume should be backuped to another physical device. So, just apply your normal backup strategy of choice.

++++++++++++++++++++++++++++++++++++++++++

# – How to RESTORE a snapshot

---

A – If you ever need to reset your system to a stored state, just

1. Launch Timeshift from the menu (or desktop shortcut)
2. Select a snapshot and hit restore
3. Reboot

That’s all. Takes mere seconds and doesn’t get any easier.
BTW, you could also restore a snapshot from the cli!

---

B – In case you can’t boot into your desktop environment try to

1. Boot directly into a snapshot from the GRUB (boot) menu
2. see A (above) …

---

C – In case you need to restore a snapshot from a live system (e. g. EndeavourOS Install medium)

1. Boot into the live environment
2. Install Timeshift into the live environment by executing

sudo pacman --noconfirm -Syy cronie
yay --noconfirm -S timeshift
 

3. see A (above) …

---

D – In case you need to chroot from a live system (e. g. EndeavourOS Install medium)

1. Boot into the live environment
2. Decrypt and mount your luks partition (e. g. /dev/sda2)

sudo cryptsetup luksOpen /dev/sda2 crypt &&
sudo mount -o compress=zstd,subvol=@ /dev/mapper/crypt /mnt
 

3. Only on UEFI systems: Mount your EFI boot folder (e. g. /dev/sda1)

sudo mount /dev/sda1 /mnt/boot/efi

4. chroot into your system

sudo arch-chroot /mnt

5. Do some root stuff …

++++++++++++++++++++++++++++++++++++++++++

Initially posted on the forum: 2020-03-03
Wiki version: 2020-07-27
2020-09-29 – changed some wording; updated grub-btrfs information regarding adjusting watchfolder
2020-11-08 – changed text editor from leafpad to nano
2020-11-29 – addressed timeshift/xapp build bug; undid these changes after an upstream fix; addressed timeshift config location change
2021-12-19 - added warning on step #13

]]> 1755 0 0 0 https://discovery.endeavouros.com/?p=1789 https://discovery.endeavouros.com/?p=1789

https://youtu.be/2qVx4TNZaao

https://youtu.be/r7meKJsjqfY

]]> 1789 0 0 0 https://discovery.endeavouros.com/?p=1806 https://discovery.endeavouros.com/?p=1806

https://youtu.be/nrE_MW8nftA

https://youtu.be/Sc-L5egqz1g

https://youtu.be/8PQr055Cn4s

https://youtu.be/7GZ5Er3ZNrQ

https://youtu.be/2jlhqZ1b1-A

https://youtu.be/mMfI415RNEs

]]> 1806 0 0 0 https://discovery.endeavouros.com/?p=1831 https://discovery.endeavouros.com/?p=1831 1831 0 0 0 https://discovery.endeavouros.com/?p=2004 https://discovery.endeavouros.com/?p=2004

Overview

You can personalize Welcome by adding new command buttons in the Welcome app. They will appear under tab Personal Commands.

To personalize Welcome, add your new commands into file
$HOME/.config/welcome-own-cmds.conf

Command syntax

The Welcome app uses yad forms and bash language to create a simple GUI.
^{Note that you don't need to be familiar with yad nor bash (but it may help!) to add your own commands. Simply follow this short tutorial.
(More info with terminal commands: man yad, man bash).}

Let's start with a simple Firefox example (this already works for Welcome!):

local welcome_own_commands=(
    --field=" Firefox web browser!!":fbtn "firefox"
)
You will add commands to Welcome by adding yad form fields to a bash array variable named

welcome_own_commands

This variable (and possible other variables in this file) should be marked as a local variable in bash.

Buttons for Welcome are defined using specially crafted fields. Each field defines a command for a button, for example:

--field=" Firefox web browser!firefox-default!Browse the web with Firefox":fbtn  "firefox"

A field definition consists of the following elements:

Element	Purpose	Value in the example above
name	button name	Firefox web browser
icon	name of an icon on the button (optional)	firefox-default
description	useful info for the user (optional)	Browse the web with Firefox
command string	actual command the button executes (can have parameters)	firefox

As you see, yad (together with bash) wants the field to be in a specific format.

Between --field= and :fbtn you'll write most of the button information.
The name, icon, and description are separated with exclamation (!) marks.

And because the added strings may contain space characters, always use quotes ("a string") around the strings.

^{Tip: to find useful icon names you can use e.g. command yad-icon-browser. It is included in the yad package.
Tip (advanced): the command string can be e.g. a bash function with parameters (see the examples below).
Tip (more advanced): take a look at file /usr/bin/eos-welcome about using bash functions in the command strings.}

]]> 2004 0 0 0 https://discovery.endeavouros.com/?p=2166 https://discovery.endeavouros.com/?p=2166

I love running EndeavourOS because of its flexibility and its abundant of package choices. Apps and packages are continuously updated and you don’t have to worry that you’re working on a system that’s out of date or has security risks. The perfect system right?

Well, I have to admit that running a bleeding-edge distro can be a pain from time to time. Don’t get me wrong, I’m not confirming that big claim by non-Arch users that Arch and it’s derivatives constantly break because that is a big myth and we all know it.

No, the thing I’m referring to is when that DE release finally hits the repo after weeks and weeks of hype and you can’t wait for all the packages to arrive, so against your better judgement, you type yes after that sudo command and after installation you reboot the system, Grub boots fine and then you’re greeted with the all dreaded blinking cursor in a black screen. Or you can log into your system to find out that the window manager isn’t reacting on any command or click, no matter how hard you push that poor trackpad/mouse or how loudly you shout at your screen.

We’ve all been there and in the case, as described above, there’s no other way than to roll back and downgrade the culprit packages. You can do it manually - but with Timeshift, you can go back in time and put back the previous snapshot of your system that did work. That’s all that Timeshift does, making a snapshot of your system on a regular basis, so you can revert back without a hassle.

How do you install it?

Make sure that your system is up-to-date - if you’re in doubt then run:

sudo pacman -Syu

Then run:

yay -S timeshift

After install Timeshift isn’t enabled by default, to enable it, type the following command:

systemctl enable cronie.service

systemctl start cronie.service

Now you’re ready to activate Timeshift (in its settings menu), so open the app and you’ll be greeted with a wizard that looks like this:

Select RSYNC and then click on Next:

Then Timeshift runs to estimate the size of the system, depending on the size it can take some time.

In this screen, you’re prompted to choose the partition or disk where Timeshift can store the snapshots. Choose the desired destination and click on Next.

In this screen, you can select the interval you wish Timeshift to use for making automated snapshots, and how many snapshots you want to keep, Select one or more options and click Next. NOTE: Boot snapshots will delay the booting process until the snapshot is completed.

In this screen, you can choose whether you want to include the Home folder (or just parts of it) in the snapshot. This can be useful in case you need full recovery. Choose as you desire and click Next.

If you wish to create snapshots manually instead of a schedule, you can skip the previous schedule setup steps and click on the left button to create a snapshot and the delete button to remove a snapshot.

How to revert back to a snapshot?

To revert back you have three options:

When Grub is booting you can follow the instructions over here and after that type:

timeshift --restore

Select the desired snapshot date and let Timeshift do its work.

In case of a non-booting system, boot the device with the Live USB or another Arch-based Live USB and use Arch-chroot then follow the same instructions as above. When Timeshift is finished, you can reboot the system.

In case you don’t have the EndeavourOS or another Arch-based Live USB at hand and only another Linux Live USB, you could boot that one instead and install Timeshift in the Live environment using the that distro’s own repo. After install start the application and it will search automatically for your snapshots. Select the desired snapshot and reboot after completion.

Having Timeshift installed and working gives you, whilst exploring the system, some ease of mind.

So, go and explore the system and if it goes wrong, you know you have a reliable tool to fall back on.

]]> 2166 0 0 0 https://discovery.endeavouros.com/?p=3088 Mon, 10 Jan 2022 06:14:23 +0000 https://discovery.endeavouros.com/?p=3088

Worm is a tiny, dynamic, tag-based window manager written in the Nim language. It supports both a floating mode and master-stack tiling with gaps and struts.

---

About community edition

[icon name="share" prefix="fas"] Github | Forum

• Terminal: xfce4-terminal
• File manager: thunar
• Launcher: rofi
• Bar: polybar
• Keybinds: sxhkd
• Wallpaper: feh

Configuration

• Main config file: ~/.config/worm/rc
• Keybindings: ~/.config/sxhkd/sxhkdrc
• Bar: ~/.config/polybar/config

Keybindings

super + Return
	xfce4-terminal
super + q
	wormc close-active-client
super + {1-9}
	wormc switch-tag {1-9}
super + shift + {1-9}
	wormc move-active-tag {1-9}
super + r
	rofi -show combi

Documentation:
https://github.com/codic12/worm/blob/main/docs/wormc.md

]]> 3088 0 0 0 https://discovery.endeavouros.com/?p=3248 Fri, 14 Jan 2022 19:14:46 +0000 https://discovery.endeavouros.com/?p=3248

EndeavourOS doesn't enable Bluetooth by default because of several security risks.

If you haven't set up Bluetooth already, follow the steps in this tutorial to do so.

After you're finished with the tutorial, Bluetooth should be installed and enabled by default at startup. To disable it at startup, open this file:

# sudo nano /etc/bluetooth/main.conf

Find this section:

[Policy]

and go down a bit to find this line:

AutoEnable=false

If the line above has a # before it, it means the line is commented. Remove the hashtag. If there is a true instead of false, change it to false. Save the file now (Ctrl + s shortcut for nano).

If you want to enable Bluetooth at startup again, change the line to this:

AutoEnable=true

]]> 3248 0 0 0 https://discovery.endeavouros.com/applications/update-troubles-meet-timeshift/2019/11/ Sat, 02 Nov 2019 08:29:39 +0000 https://discovery.endeavouros.com/?p=100

I love running EndeavourOS because of its flexibility and its abundant of package choices. Apps and packages are continuously updated and you don't have to worry that you're working on a system that's out of date or has security risks. The perfect system right?

Well, I have to admit that running a bleeding-edge distro can be a pain from time to time. Don't get me wrong, I'm not confirming that big claim by non-Arch users that Arch and it's derivatives constantly break because that is a big myth and we all know it.

No the thing I'm referring to is when that DE release finally hits the repo after weeks and weeks of hype and you can't wait for all the packages to arrive, so against better judgement, you type yes after that sudo command and after installation you reboot the system, Grub boots fine and then you're greeted with the all dreaded blinking cursor in a black screen. Or you can log into your system to find out that the window manager isn't reacting on any command or click, no matter how hard you push that poor trackpad/mouse or how hard you shout at your screen.

We've all been there and in the case, as described above, there's no other way than roll back and downgrade the culprit packages. You can do it manually but with Timeshift, you can go back in time and put back the previous snapshot of your system that did work. That's all that Timeshift does, making a snapshot of your system on a regular base, so you can revert back without a hassle.

How do you install it?

Make sure that your system is up-to-date if you're in doubt run:

sudo pacman -Syu

Then run:

yay -S timeshift

The system asks you to choose RSYNC or BTRFS, choose RSYNC. (The BTRFS option only works on systems running on the BTRFS filesystem, and is usually quite different in its setup. This is covered in a separate article.) Cronie is then required and will be installed as a dependency for automatic scheduling.

After install Timeshift isn't enabled by default, to enable it, type the following command:

systemctl enable --now cronie.service (--now will start and enable in one command)

Now you're ready to activate Timeshift in its settings menu, so open the app and you'll be greeted with a wizard that looks like this:

Select RSYNC and go to next

Then Timeshift is running to estimate the size of the system, according to the size it can take some time.

In this screen, you're prompted to choose the partition or disk where Timeshift can store the snapshots. Choose the desired destination and click on next.

In this screen, you can select the interval you wish Timeshift will make automated snapshots and how many snapshots you want to keep, select one or more options and click next. NOTE: Boot snapshots will delay the booting process until the snapshot is completed.

In this screen, you can choose whether you want to include the Home folder in the snapshot. This can be useful in case you need full recovery. Choose as you desire and click next.

The final screen gives you some extra information, close the window and Timeshift is scheduled.

Creating a snapshot manually

If you wish to create snapshots manually instead of a schedule, you can skip the previous steps and click on the left button to create a snapshot and the delete button to remove a snapshot.

How to revert back to a snapshot?

To revert back you have three options:

When Grub is booting you can follow the instructions over here and after that type:

timeshift --restore

Select the desired snapshot date and let Timeshift do its work.

In case of a non-booting system, boot the device with the Live USB or another Arch-based Live USB and use Arch-chroot then follow the same instructions as above. When Timeshift is finished, you can reboot the system.

In case you don't have the EndeavourOS or another Arch-based Live USB at hand and only another Linux Live USB, you can boot that one also and install Timeshift in the Live environment using the distro's repo. After install start the application and it will search automatically for your snapshots. Select the desired snapshot and reboot after completion.

Having Timeshift installed and working gives yourself, whilst exploring the system, some ease of mind.

So, go and explore the system and if it goes wrong, you know you have a reliable tool to fall back on.

]]> 100 0 55 0 https://discovery.endeavouros.com/articles/does-endeavouros-frown-upon-gui-solutions-for-pacman/2019/11/ Sat, 02 Nov 2019 08:33:12 +0000 https://discovery.endeavouros.com/?p=134

'Hi, I'm really trying to like your distro, but I really don't understand why you aren't shipping Pamac by default. Don't you know that Pamac is the standard and therefore mandatory for every Arch-based distro out there?'

'Hi, I'm a former Antergos user and thank you for deceiving the entire Antergos community by excluding Pamac. Antergos was a topnotch system and EndeavourOS is a poor reflection of it. How dare you to call yourselves the Antergos successor?'

'Hey, you terminal friggin' freaks!!! I have a message for you: EndeavourOS sucks big time!!! I've tried it in a VM, thank God for that, and your system is worthless, how do you expect me to install stuff if you haven't got Pamac installed!!! You won't be seeing me running this shitty system, Hail Manjaro, ArcoLinux and Namib, bury EndeavourOS, because you won't be missed!!!'

These comments are not a product of my creative writing that was hidden in a dark corner of my brain. These are a small collection of actual messages sent to us, the only creative writing I did, was cleaning up the language.

To be honest, I do understand these comments and if they were written in the way I 'translated' them over here, I would be happy to continue the discussion.

The absence of a GUI solution in our distro has a few reasons, first of all, we want you to give you the freedom of choice right from the start. The second reason is in relation to the first: most GUI solutions don't implement very well on every single Desktop Environment.

And the third one is quite a bit hard to explain without sounding elitist, so let me paint you the following picture.

You're living in a rented apartment that has a kitchen equipped with all the conveniences you wished for. Because of all these conveniences, you're used to eating takeaway food or ready-made food set to be prepared in the microwave or oven. There's nothing wrong with that, especially these days microwave or frozen food has improved a lot since the bland dishes they were, back in the seventies and eighties.

You're living a busy but happy life when all of a sudden the microwave and the oven simultaneously break down. No problem, you call the landlord to report the problem and, for the sake of the story you have a landlord that reacts quick and correctly, the day after tomorrow a brand new oven and microwave will be delivered and installed and in the meantime you order food in, no problem!

Basic kitchen

Well, on the day of delivery 'the guy' who's going to install the appliances discovers that the wiring in the kitchen needs to be redone because it doesn't meet the modern standards anymore. He has called the landlord and he has permission to redo the wiring, but therefore he needs to book in a certified electrician and there isn't one available sooner than 4 weeks from now.

You're screaming and throwing a tantrum at everyone who crosses your path because this is insane!! How is it possible that in this day and age simple appliances can't be installed and working within a matter of hours! This is simply out of order, how are you suppose to eat now?!?

I think a lot of people would agree with you that the situation you're in is uncomfortable but no one can actually help you expedite the operation. Until your snarky sister comes along and says: 'Stop shouting to each and everyone in the world, anyway what's the fuzz all about? You have running water, a cooker, knives, spoons, pots and pans, then prepare dinner you lazy cow and I know you can't cook but you can get a cookbook or call friends and mum to help you learn, you Drama Queen!!!'

You don't want to admit it at that time, but you know in your heart your sister had struck the chord that lies at the root of your anger: This situation is slamming you, with the fact that you can't cook, in your face with brutal force.

This situation is similar to when you run a powerful Arch-based distro solely relying on a GUI solution for Pacman. It is a convenient tool to have, but a little understanding of what that GUI solution actually does is highly recommendable on a system like ours.

Why should you look and learn it the hard way, if we provided that tool right from the start? By giving you the choice to run the system with the tools you feel comfortable with, we also make you aware of the responsibility those choices bring.

By installing it yourself, your attitude changes towards that tool, so when it breaks and you asked the community for help, your approach will be more open to search for a solution, instead of fixating on the fact why this tool that came by default doesn't work anymore.

That's what an Arch-based distro is all about, it's not the knowledge (that comes with experience) but it's the open attitude to think in solutions to make an Arch-based distro run successfully.

Go and explore this great foundation we brought you and there's no shame in using a GUI tool, but whilst using them, visit the forum for inspiration. The forum is your cookbook to prepare you in case your convenient microwave breaks down or try one of those recipes and I'm sure you will get enthusiastic for doing it manually.

]]> 134 0 54 0 https://discovery.endeavouros.com/articles/pacman-actions-explained/2019/12/ Fri, 27 Dec 2019 16:22:48 +0000 https://discovery.endeavouros.com/?p=767

By Pudge

We are based on Arch which uses Pacman as the package manager and it comes with a man.. as in the manual page. But what exactly is it? Well, here’s what the man page says about the man page.

To access the man pages, the dreaded Command Line Interface must be used, so open a terminal window and enter:

$ man man

MAN(1) Manual pager utils MAN(1) NAME man - an interface to the system reference manuals SYNOPSIS man

man -k [apropos options] regexp ...

man -K [man options] [section] term ...

man -f [whatis options] page ...

man -l [man options] file ...

man -w|-W [man options] page ...

DESCRIPTION

man is the system's manual pager. Each page argument given to man is normally the name of a program, utility or function.

The manual page associated with each of these arguments is then found and displayed. A section, if provided, will direct man to look only in that section of the manual. The default action is to search in all of the available sections following a pre-defined order (see DEFAULTS) and to show only the first page found, even if the page exists in several sections.

Every man page should follow a prescribed format. NAME, SYNOPSIS, and DESCRIPTION should always be first. These should be self-explanatory. Notice in the SYNOPSIS the line:

man -k [apropos options] regexp

Parsing the command gives

“man” invokes the man command

“-k” specifies to use the apropos option

[apropos options] anything in brackets is optional, in this case, options for apropos may be specified. If no options are specified, don’t include the empty brackets “regexp” is the target that man operates on, in this case, the target is the regexp command.

I chose this particular line to parse since apropos was covered in “Linux commands demystified Part one”. If you need to see the options available for apropos, then enter

$ man apropos

The man pages are very flexible in how it displays things. Most of the time, a simple

$ man regexp

would yield results that would be satisfactory. If not, then explore some of the display options.

The first page of the man command is displayed above. Here is how to navigate in the man pages.

By default, man redirects the output through less command. To navigate in the less output, up and down arrows move the text up and down one line at a time. The space bar moves text forward one page, b moves the text backwards one page. h displays movement options for less. q exits the less command. For further info on less, do a

$ man less

Scroll down until the following appears

The table below shows the section numbers of the manual followed by the types of pages they contain. 1 Executable programs or shell commands 2 System calls (functions provided by the kernel) 3 Library calls (functions within program libraries) 4 Special files (usually found in /dev) 5 File formats and conventions, e.g. /etc/passwd 6 Games 7 Miscellaneous (including macro packages and conventions), e.g. man(7), groff(7) 8 System administration commands (usually only for root) 9 Kernel routines [Non-standard] A manual page consists of several sections. Conventional section names include NAME, SYNOPSIS, CONFIGURATION, DESCRIPTION, OPTIONS, EXIT STATUS, RETURN VALUE, ERRORS, ENVIRONMENT, FILES, VERSIONS, CONFORMING TO, NOTES, BUGS, EXAMPLE, AUTHORS, and SEE ALSO.

As stated above in the DESCRIPTION

The manual page associated with each of these arguments is then found and displayed. A section, if provided, will direct man to look only in that section of the manual.

How is this useful? In the SEE ALSO section, you will often be referred to other man pages such as pacman.conf(5) This will display section 5 of the pacman.conf man page, thus limiting the size of the displayed man page. In this case section 5 is File formats and conventions. Enter as:

$ man pacman.conf 5

Now we can open a man page, and navigate around in the man page. At this point, you are probably saying to yourself, “Man, that is just a bunch of gobbledygook. Why do I need this?” Quite often when asking for help on a Linux forum, or while reading Linux Blogs, someone will throw a CLI command at you. You may or may not understand what the command does or what the options mean.

Rather than blindly typing in the command and hoping for the best, you can research the command with the man pages.

We will start by examining the most used CLI command, pacman. Everyone using EndeavourOS has seen pacman -S packagename and pacman -Syu

Open the man page for pacman and we’ll dissect these commands.

$ man pacman

PACMAN(8) Pacman Manual PACMAN(8) NAME pacman - package manager utility SYNOPSIS pacman <operation> [options] [targets] DESCRIPTION Pacman is a package management utility that tracks installed packages on a Linux system. It features dependency support, package groups, install and uninstall scripts, and the ability to sync your local machine with a remote repository to automatically upgrade packages. Pacman packages are a zipped tar format. Since version 3.0.0, pacman has been the front-end to libalpm(3), the “Arch Linux Package Management” library. This library allows alternative front-ends to be written (for instance, a GUI front-end). Invoking pacman involves specifying an operation with any potential options and targets to operate on. A target is usually a package name, file name, URL, or a search string. Targets can be provided as command-line arguments. Additionally, if stdin is not from a terminal and a single hyphen (-) is passed as an argument, targets will be read from stdin.

From above, “Invoking pacman involves specifying an operation with any potential options and targets to operate on.” For:

pacman -S package-name

-S is the operation, there are no options, and the package name is the target. -S with no options will synchronize packages and install the target package name. The -S operation is defined as:

OPERATIONS -S, --sync Synchronize packages. Packages are installed directly from the remote repositories, including all dependencies required to run the packages. For example, pacman -S qt will download and install qt and all the packages it depends on. If a package name exists in more than one repository, the repository can be explicitly specified to clarify the package to install: pacman -S testing/qt. You can also specify version requirements: pacman -S "bash>=3.2". Quotes are needed, otherwise, the shell interprets ">" as redirection to a file.

The above is a snippet, see man pacman for further details on the -S operation.

On to pacman -Syu. The -S operation has been examined, time to check out the options. For:

pacman -Syu

-S is the operation, y and u are the options, and there is no target. Scroll down to the

SYNC OPTIONS (APPLY TO -S)

section to find the option definitions.

-y, --refresh Download a fresh copy of the master package database from the server(s) defined in pacman.conf(5). This should typically be used each time you use --sysupgrade or -u. Passing two --refresh or -y flags will force a refresh of all package databases, even if they appear to be up-to-date.

-y downloads a fresh copy of the master package database from the server(s)

This should typically be used each time you use –sysupgrade or -u

-yy will force a refresh of all package databases, even if they appear to be up to date.

I’ve seen the -yy option used to repair a local package database that has become corrupt.

-u, --sysupgrade Upgrades all packages that are out-of-date. Each currently-installed package will be examined and upgraded if a newer package exists. A report of all packages to upgrade will be presented, and the operation will not proceed without user confirmation. Dependencies are automatically resolved at this level and will be installed/upgraded if necessary. Pass this option twice to enable package downgrades; in this case, pacman will select sync packages whose versions do not match with the local versions. This can be useful when the user switches from a testing repository to a stable one. Additional targets can also be specified manually, so that -Su foo will do a system upgrade and install/upgrade the "foo" package in the same operation.

-u upgrades all packages that are out of date.

-uu will enable package downgrades. This would probably rarely be used. See the wiki entries about downgrading to a specific date.

Since the -u option was specified, there is no target.

pacman -S -y -u

pacman -Syu

pacman -S - -sysupgrade - -refresh

Are all equivalent and will run just fine. pacman -Syu is just easier to type.

A few useful pacman commands using -Q (query) and we will wrap this up.

-Q, --query Query the package database. This operation allows you to view installed packages and their files, as well as meta-information about individual packages (dependencies, conflicts, install date, build date, size). This can be run against the local package database or can be used on individual package files. In the first case, if no package names are provided in the command line, all installed packages will be queried. Additionally, various filters can be applied on the package list. See Query Options below.

pacman -Q

If no package names are provided in the command line, all installed packages will be queried. This will provide a list of ALL packages installed. Most of the time this is not real useful. However, during troubleshooting if someone on a forum asks if you have a certain package installed, you can do the following;

pacman -Q | grep packagename

or just part of package name. Such as

pacman -Q | grep xf86-video

xf86-video-amdgpu 19.1.0-1

xf86-video-ati 1:19.1.0-1

xf86-video-fbdev 0.5.0-1

xf86-video-intel 1:2.99.917+897+g0867eea6-1

xf86-video-vesa 2.4.0-2

Yields anything that starts with xf86-video Which is the above on my EndeavourOS Gnome system.


To parse this command:

pacman is the command, -Q is the operation, no options, and no target, will list all installed packages.

This output is “piped” or sent to the grep command which limits the output to anything starting with xf86-video. Might be a good time to do a man grep. Also, the “pipe” command is the two vertical dashes that are the shifted \ (backslash) key on a US keyboard layout.

Over time, orphan or ghost packages will start to accumulate. To find them:

pacman -Qdt

-d, --deps Restrict or filter output to packages installed as dependencies. This option can be combined with -t for listing real orphans - packages that were installed as dependencies but are no longer required by any installed package.

The -d option restricts the query output to packages installed as dependencies. Sure enough, “This option can be combined with -t for listing real orphans."

-t, --unrequired Restrict or filter output to print only packages neither required nor optionally required by any currently installed package. Specify this option twice to include packages which are optionally, but not directly, required by another package.

-t Restrict or filter output to print only packages neither required nor optionally required by any currently installed package.

-tt Specify this option twice to include packages which are optionally, but not directly, required by another package.

We want the -t option. Packages not required by any package, in any way.

If some orphans were found, how to eliminate them? As per the Arch Wiki**, use:

pacman -Rns $(pacman -Qtdq)

In the (pacman -Qtdq) part, everthing has been covered this far exept the q option.

-q, --quiet Show less information for certain query operations. This is useful when Pacman’s output is processed in a script. Search will only show package names and not a version, group, and description information; own will only show package names instead of "file is owned by pkg" messages; group will only show package names and omit group names; list will only show files and omit package names; check will only show pairs of package names and missing files; a bare query will only show package names rather than names and versions.

This should be self-explanatory. Now about the first part of the command.

pacman -Rns $(pacman -Qtdq)

The OPERATION is

-R, --remove Remove package(s) from the system. Groups can also be specified to be removed, in which case every package in that group will be removed. Files belonging to the specified package will be deleted and the database will be updated. Most configuration files will be saved with a .pacsave extension unless the --nosave option is used. See Remove Options below.

This removes packages from the system.

Scroll to

REMOVE OPTIONS (APPLY TO -R)

-n, --nosave Instructs pacman to ignore file backup designations. Normally, when a file is removed from the system, the database is checked to see if the file should be renamed with a .pacsave extension.

-s, --recursive Remove each target specified including all of their dependencies, provided that (A) they are not required by other packages; and (B) they were not explicitly installed by the user. This operation is recursive and analogous to a backwards --sync operation, and it helps keep a clean system without orphans. If you want to omit condition (B), pass this option twice.

$(COMMAND) is shorthand for substitute the output of the enclosed command
To parse the command.
pacman -Rns $(pacman -Qtdq)
run pacman with -Rns which recursively removes target files without saving config files, and use the output of  the $(pacman -Qtdq) command as the targets.  

That last command sure warped my brain.  Time to shut this party down.

I want to give a shout out to EndeavourOS forum member CMarch for his assistance with this article.

A big thank you to bryanpwo for everything Bryan did to get this edited and formatted for the Discovery magazine.  

** Cited reference from the Arch Wiki
https://wiki.archlinux.org/index.php/Pacman/Tips_and_tricks#Removing_unused_packages_(orphans)

To give credit where credit is due for the pacman man page, scroll to the very bottom of the man page to AUTHORS

Since pacman was written from scratch by Judd Vinet, I am reasonably sure Judd wrote the original man page for his creation.  His name is listed under "Past major contributors".  Thank you to Judd and all the current maintainers and past major contributors to this man page, and to everyone who keeps Arch Linux what it is today.

]]> 767 0 48 0 https://discovery.endeavouros.com/articles/root-partition-full-dont-panic-clear-pacmans-cache-first/2020/03/ Tue, 31 Mar 2020 14:59:38 +0000 https://discovery.endeavouros.com/?p=852

After some time, the system might give you a warning that your root partition is almost full.

You might panic about this and you're either tempted to do a reinstall and increase your root partition or even worse, trying to use Gparted to decrease your partition, move it and increase your Root partition.

STOP!!! Don't do that, especially the latter option, as it can break your system. My advice is just to stay calm, there's a much less radical solution to this problem.

/var/cache/pacman/pkg/

When you install a package with Pacman, it stores all downloaded packages in /var/cache/pacman/pkg/ folder. The package manager doesn't remove old and uninstalled packages automatically by default and after a while, the cache size can consume a substantial amount of real estate on your HDD or SDD.

Fortunately, Pacman has a built-in function to clear the cache, by typing "sudo pacman -Sc" the cache will be entirely cleared. Problem solved, right?!?

Well... yes and no. Yes, your cache is cleared and you will have free space on the partition regained, yay...

So, what's the problem, you might ask me? The problem now is by using the above-described command, you have cleared your entire cache, including the cache of your installed packages. This cache is needed when a package-update doesn't work and you have to downgrade until the issue is solved upstream. This is not a big disaster, because you can also downgrade a package using the Arch repo, but falling back on your local cache is so much easier.

Paccache

Don't worry, there's a solution and it's called paccache. Now, before you go open your terminal and use yay to look for this nifty package, don't bother, because it isn't a package, it is already present on your system.

The Paccache script is provided by the Pacman package itself. So, you don’t have to bother with installation steps. Paccache will keep the three most recent package versions by default. Except for the three most recent package versions, It will delete all cached versions of each package regardless of whether they’re installed or not.

How to use it

To check how many packages are in the paccache just type in:

$ sudo ls /var/cache/pacman/pkg/ | wc -l

This will give you the number of packages that are in your cache if you want to know how much space the cache is taking, type:

$ du -sh /var/cache/pacman/pkg/

Now the system is telling you how big the size of your cache is.

Now you can clear the cache, except the last three versions of each package by typing

$ sudo paccache -r

Depending on your cache history, this may give a lot of space back on your root partition, but now you're at it, why not clear the cache from your uninstalled packages? To do that type the following:

$ sudo paccache -ruk0

U in this command stands for all the uninstalled package and depending on your history of uninstalled packages, this also can give your system a lot of space back. Another method to clear uninstalled packages is using:

$ sudo pacman -Sc

Or to completely remove it use:

$ sudo pacman -Scc

Just be careful with cleaning the cache and packages with this command, it seems tempting to use it, but once deleted there's no turning back.

Automatic cache removal

You can automate this task using pacman hooks. The pacman hook will automatically clean the package cache after every pacman transaction.

To do so, create a file /etc/pacman.d/hooks/clean_package_cache.hook by doing the following:

$ sudo mkdir -p /etc/pacman.d/hooks

$ sudo nano /etc/pacman.d/hooks/clean_package_cache.hook

Then add the following lines:

[Trigger]
Operation = Upgrade
Operation = Install
Operation = Remove
Type = Package
Target = *
[Action]
Description = Cleaning pacman cache...
When = PostTransaction
Exec = /usr/bin/paccache -r

Close and save by pressing CTRL + x and from now on your system will automatically clear the cache after each pacman update, removal or update.

EDIT: Since the writing of this article EndeavourOS ships with an automated script that is part of the Welcome app that performs these operations with a couple of mouse clicks.

]]> 852 0 47 0 https://discovery.endeavouros.com/applications/how-to-install-virtualbox/2021/03/ Tue, 09 Mar 2021 10:56:01 +0000 https://discovery.endeavouros.com/?p=997

_{by joekamprad}

VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product

These are the steps you need to install it:

1. Install kernel headers (linux-headers)

sudo pacman -Syu --needed linux-headers

OR for LTS Kernels install the linux-lts-headers

sudo pacman -Syu --needed linux-lts-headers

2. Install Virtualbox

sudo pacman -S virtualbox virtualbox-guest-iso

You will be asked for installing the core-packages:

• for linux kernel choose virtualbox-host-modules-arch
• for other kernels (like LTS) choose virtualbox-host-dkms

3. Install net-tools if you want to use host-only or bridged networking (optional)

sudo pacman -S net-tools

4. Install virtualbox-ext-vnc if you need VNC server support (optional)

As you want to access the VM from external Systems…

sudo pacman -S virtualbox-ext-vnc

5. load the needed module:

sudo modprobe vboxdrv

6. Add your user(s) to the vboxusers group

sudo gpasswd -a username vboxusers

7. Add Oracle extensions (optional, but needed for USB function p.e.)

This neds to be builded from AUR::

yay -S virtualbox-ext-oracle

After installing the extensions will be enabled automatically.

It is also possible to use the VirtualBox-package directly downloaded from oracle instead:

VirtualBox_Extension_Pack

Then you need to open VirtualBox and go to

File --> Preferences --> Extensions

enable the package that has been downloaded.

Notes / Troubleshooting:

Add shared folder to be shared between host and guest:

Open the Settings and click on shared Folders.

Add a share [1] and give the needed path to the host folder [2] finally mark it to automount [3]

On the booted guest (inside the VM):
sudo pacman -S virtualbox-guest-utils
sudo systemctl enable vboxservice.service
→ reboot vm
sudo modprobe vboxsf
sudo usermod -aG vboxsf $USER

After a reboot of the VM you should be able to access the shared folder as the normal user inside the VM.

You will see it created a folder named sf_<hostfoldername> under /media/sf_<hostfoldername>

Graphics Memory:

From that screen you can set Memory for Graphics bigger than 125 MB what is recommended to set, same for 3d what should be checked.

Click on the MB value [1] it will open a popup [2] slide it to maximum of 246 MB and hit OK.

3d should be enabled for wayland guests in case it is causing issues... disable it again.

As it happens in some circumstances, that Live ISO per example does not show display if enabled.

]]> 997 0 45 0 https://discovery.endeavouros.com/endeavouros-tools/welcome/2021/03/ Tue, 09 Mar 2021 11:07:30 +0000 https://discovery.endeavouros.com/?p=1001

By: @manuel
Created: 2019-Jul
Updates of this document: go to the end of this doc.

The EndeavourOS Welcome app is one of the first apps to encounter, both while installing EndeavourOS, and when starting the installed system.

The purpose of the Welcome app is to help users

• find relevant information about EndeavourOS
• provide an easy way to do some useful operations on the system

Note that the Welcome app is under constant development, and will include more features, as well as bug fixes, over time.

Enabling or disabling Welcome

To have Welcome app started when you log in, make sure

• Welcome app is selected in the Autostart feature of the DE
  or
• Hidden=false is set in file /etc/xdg/autostart/welcome.desktop

On DEs that do not work well with system's Autostart feature, you may also disable the Welcome app from the app itself

• with the --disable option
• with a button in the app (some DEs only)

To re-enable the app, click the Welcome app icon, or use the terminal command: eos-welcome --enable

To run Welcome once even if it is already disabled, use option --once: eos-welcome --once

Welcome will stay disabled after using option --once.

Note: check also settings in the configuration file ~/.config/EOS-greeter.conf.

Below we’ll go through the window tabs of the Welcome app.

INSTALL

This window is what you’ll see when starting to install EndeavourOS:

This is the contents of the INSTALL tab. The tab is available only in the install phase.
Note: some buttons may not show as above, depending on the installed software or new/changed features of Welcome.

To start the install process, simply click the Start the Installer button. This will allow selecting from a few popular desktop environments, or even no desktop at all. In addition to the installer window, it starts a terminal window that shows plenty of detail of the install process.

Another installer button Install community editions allows installing editions with a window manager (currently: Sway, Bspwm) instead of a desktop environment. Also, you can start ARM version install on ARM hardware.

Button Update Mirrors (toolname) starts program reflector-simple or rate-mirrors which helps you select the Arch mirrors to use. This is very useful for the online install mode (that you may choose a bit later during the install) as it can speed up the install process quite dramatically. Another button can update the EndeavourOS mirrors.

The Change Display Resolution button (added in Welcome version 3.4.7) helps you to change display resolution. Note that, by default, this button is active only in a virtual machine (supports VirtualBox, VMware, and QEMU). This may be useful if you want to change the VM window size and your display is large enough. It is also useful in the live session if you have a high resolution monitor, and text and other things look too small to work with.
The above feature is implemented on top of the xrandr command, so package xorg-xrandr must be installed.

If certain disk management functions like special partitioning or partition formatting is needed, button Partition manager may help you.

The Bluetooth notes button shows information how to enable bluetooth functionality. We do not enable bluetooth by default due to reasons mentioned in the page the button opens.

Buttons Latest release info, Installation tips, and How to share system logs should be self explanatory – they will show you related EndeavourOS web pages in a browser. Note that the last of these 3 buttons is a useful tool for troubleshooting.

Button Fetch your install customization file (advanced) is meant for power users to customize the install to a certain degree (like adding/removing packages, customizing features, etc.). This feature is explained in more details in other Discovery articles.

The bottom line buttons are:

• Software News button shows important "last minute" information about the EndeavourOS software and its changes. Be sure to click this! The button goes here.
  Note that it will be available also in the installed system.
• Changelog button provides a view to version history of the Welcome app.
• Help button shows the discovery article about Welcome.
• Don’t show me anymore button is meant to silence (i.e. not start automatically) the Welcome app until you explicitly enable it again. To enable the Welcome app is easy – just click the Welcome icon in the start menu.
• See you later button closes this window. Note: this button is no more available.

Note that if you want to customize the install process, see this.

General Info

The next tab contains links to general information about EndeavourOS. This may be quite useful for users that know very little or nothing about EndeavourOS.

The General Info tab contents look like this:

As you can probably guess, the buttons contain links to much more information at the EndeavourOS web site.

And since developing and maintaining a distribution takes resources that the development team must pay for, we’d appreciate any size of donation (the Donate button) to help us cover the mandatory costs.

After Install

Note you’ll see the following Welcome tabs after you have installed EndeavourOS, rebooted, and logged in to your new system. The General Info tab has the same contents now as while installing.

The next tab is (as some might say) where the real fun starts!

This tab (and the last tab) are meant to be used (mainly) in the installed system.

On the picture you can see text above the tabs. This is an embedded notification area in Welcome, and is meant for informing users about important events or matters. To see the contents of the notification, simply click the Software News button. Note that the notification are can be empty too, but the Software News button is still available.

The Update Mirrors (repo, tool) button may be good to click as the first thing after logging in the first time, especially if software updates seems (see the Update System button below) very slow, or even break. It creates a list of "good" mirrors for your system. And you’ll use precisely those mirrors when updating the system, or installing new packages to it. Note that you may use this button also at a later time, for example if any of the listed mirrors is no more available, or should you have other problems with mirrors.
These buttons run commands reflector-simple, rate-mirrors, and eos-rankmirrors respectively. You can run them from the terminal as well.

The next buttons, Update System (command), are important buttons. Click any of them right after booting to the installed system (maybe after “Update Mirrors” operation has finished), and your system will be up-to-date (and may need to be rebooted). These buttons can be used later as well, always when a system update is needed.

Tip for NVIDIA graphics hardware users: the eos-update command can check on kernel (with option --nvidia) updates (linux and linux-lts) that the required NVIDIA driver (nvidia or nvidia-lts) will also be updated! This helps preventing problems when a kernel is updated but the required NVIDIA driver is not.
In addition, eos-update will take care of updating Arch and EndeavourOS keyrings before updating other packages. This should help handling the situation when either of the keyring packages are updated.

Tip: it is recommended to update system software at least about once a week. Note that new package updates will be available very frequently, often many times a day. Systems that haven't been updated for a very long time (like months or even years) usually can be updated, but may require extra work. The EndeavourOS forum will help you in case of any trouble.

After updating all packages your system is ready to be used.

After you have been using your EndeavourOS system for a while, your disk (more precisely, the package cache) may fill up with old packages that are stored there for convenience. Eventually it may contain gigabytes of old packages that are no more used! So in order to remove the unneeded old packages automatically, button Package cleanup configuration was added. It helps configuring the service that automatically removes old packages, and saves the number of packages that you want to keep. By default it keeps 3 versions of each package, but for many purposes 2 would be enough, and even 1 if your disk doesn't have much free space.

Another useful maintenance button is Configure eos-update-notifier. It helps configure the app that, by default, notifies about available updates according to a schedule, and lets you do the actual system update as well. You can, for example, schedule update checks to occur weekly instead of daily (=default).

You may change the Display Manager by clicking the Change Display Manager button. Usually this is not needed, but you may have a reason for doing so.

The EndeavourOS default wallpaper button assigns the default EndeavourOS wallpaper back. This may be handy after experimenting with other wallpapers. Note also that this button uses the program eos-wallpaper-set, and that program can be used to set the wallpaper directly on the command line.

There are two related wallpaper buttons. Choose one of the EndeavourOS wallpapers lets you choose another wallpaper from a predefined location of wallpapers. You may browse with this application and select other wallpapers as well.

Then Download more EndeavourOS wallpapers gives a possibility to download and use the legacy EndeavourOS wallpapers, or wallpapers made by the EndeavourOS community members. So, if you are artistically oriented, you have the opportunity to contribute!

Logs for troubleshooting helps you create many logs at once, and send them to a pastebin service on the internet. These logs are very useful in troubleshooting issues especially if you want other fellow users to help you e.g. on the EndeavourOS forum. Note that you may look at the logs before sending them to pastebin - any personal information should be hidden in the logs.

Select initial Welcome tab lets you choose the tab Welcome open to. Often users want to open to the next tab, the Assistant, which will be explained a bit later.

If you installed Xfce as your desktop, then you’ll see the related Xfce buttons. They can be used for changing the theming (appearance) of the desktop. The Xfce vanilla theme puts the vanilla theming in place. The Xfce EndeavourOS default theme sets up our default theming. Note that the offline install mode provides the latter, but the online install mode results in the vanilla theming. Note also that both options will bring the default theming, and your own modifications are not included – but your old theming is saved if you want to go back. The buttons will give more instructions about that.

Assistant

This tab consists of a collection of most useful buttons. Some buttons have already been explained, and some are new, which are explained here.

The Pacdiff & <diff-app> button is meant for managing certain configuration files (e.g. *.pacnew) and their changes. Pacdiff is a program that walks through the changed configuration files one by one, and lets you view the changes with the <diff-app> to possibly merge the changes you'd like to include. The <diff-app> is typically meld but can be changed to e.g. kdiff3 or another suitable for you.
Related configuration: EOS_WELCOME_PACDIFFERS, see more about this later in this document.

The following picture shows pacdiff in action:

Button Latest Arch news will open a web page showing the latest Arch news. This is useful e.g. for finding out latest developments or potential need for manual intervention because of recent changes by the Arch devs.

Buttons to browse Arch or AUR packages, and the Application categories button are links to web pages that contain valuable information about various applications in a well organized manner.

You may also see a button (above: xfce: information) which will show information about the currently used DE (Desktop Environment).

Tips

Buttons under this tab include more links to information about either useful or more advanced things. All users (unless already familiar with the topics) are recommended to check the links under Package management and AUR & yay! buttons. Buttons related to hardware may also be very useful if you have that particular hardware. And Forum tips provides general tips for Forum usage.

The EndeavourOS & ARM button shows information about the ARM software provided by EndeavourOS.

Then there’s information about personalizing the Welcome app.
Button Tutorial: Personal Commands explains how you can easily create new command buttons into Welcome. They will appear on a new tab Personal Commands. Button Personal Commands drag&drop shows a small window where user can drop items that will appear under the Personal commands tab.

More about the Personal Commands is explained below under Personalizing Welcome.

Add More Apps

The last default tab includes buttons for installing some popular applications.

Button Choose popular apps to install opens an app that helps you to install apps from a curated list. Other buttons should be familiar from the Assistant tab explanation above.
Even though the apps in the curated list are popular and useful, we’ve chosen not to install them by default. This gives users a better opportunity to “tailor” their system, but still, have an easy way to install these apps.

By the way, do you remember that the previous tab included a button AUR & yay!? As you (should!) know by now, pacman is the main package manager in EndeavourOS. It manages packages that are available from the Arch Linux repositories. But there is a huge amount of more apps available in the AUR (Arch User Repository). AUR is not managed by pacman. That’s why EndeavourOS provides another package manager, yay. It is like pacman, but supports AUR applications in addition to Arch Linux repositories.

Personalizing Welcome

Welcome version 3.0 introduced a new feature: users can personalize Welcome by adding their own command buttons.

Here’s an example what it might look like:

You can see a new tab Personal Commands and some command buttons are already added in the picture above.

The new tab will be activated only if the configuration file

$HOME/.config/welcome-own-commands.conf

exists, and the file contains command definitions.

The first button Tutorial: Personal Commands will be automatically created, and it shows a short tutorial about how to create new Welcome commands. Check that out!

The next button, Personal Commands drag&drop starts a window (called a dnd window) where items can be dropped. As you probably remember, the same two buttons appeared also under the Tips tab. They are on both tabs for convenience.

There are two ways to create the configuration file. One is to manually write the file, and the other (the easier way) is to use button Personal Commands drag&drop and drop items to the dnd window.

If you don’t already have the Personal Commands tab available, click the same button under the Tips tab.

Dropping items to the dnd window will cause

• the configuration file to be created if it doesn’t exist
• the configuration file to be updated with button definitions
• the Welcome app to instantly contain the new buttons!

Now your part begins! All additional buttons on this tab are there because you (the user) will add or have added them there.

A bit more about the configuration file

Here’s a very simple example configuration file:

#!/bin/bash

# Own commands:
# - Create a local array variable 'welcome_own_commands'.
# - Add yad form fields as in the example below.

local welcome_own_commands=(
    # Legend: --field=" name!icon!description":fbtn "command"

    --field=" Firefox!firefox-default!Web browser":fbtn "firefox"
    --field=" Mousepad!accessories-text-editor!Text editor":fbtn "mousepad"
)

# To have own commands activated initially, set local variable
# 'activate_own_commands_tab' to "yes";
# otherwise the default tab is active from the start.

local activate_own_commands_tab=yes    # "yes" or "no"

If you don’t want to drop items to the drag&drop window, you can simply copy the above configuration into the configuration file mentioned above. Then just restart the Welcome app. Now you have enabled this new feature!

The Tutorial button shows more details about the configuration file.

Known issues

Cinnamon

Community member and Moderator Ricklinux discovered a bug that affects the Welcome app on the Cinnamon desktop and it looks like this:

Until now a solution hasn’t been found but the workaround is simple. Go to the preferences menu and disable window effects like this:

Yad and Wayland

Yad is not fully working with Wayland, and this affects Welcome in particular (e.g. on KDE/Wayland). The reason is Wayland does not support a protocol that yad is using for its notebook feature. And Welcome is built on the notebook feature of the yad program. So if you want to use Welcome, you must use X11 instead of Wayland.

More information here:

https://github.com/v1cont/yad/issues/109#issuecomment-719887730

Special note about the code

The welcome app includes code that is directly used by some other apps, like eos-update-notifier. The shared code files are:

/usr/share/endeavouros/scripts/eos-script-lib-yad

• contains functions common for the using programs

/etc/eos-script-lib-yad.conf contains the following settings for the using programs:

• EOS_YAD_TERMINAL: name of the terminal program. With this you can force your favorite terminal to be used with the apps welcome and update notifier. But please note that it is possible that the terminal you select may not be compatible with the way the above programs use it, especially if it is not on the list of compatible terminals. By default this is commented out, and one of the supported terminals is used. See list of supported terminals in file /usr/share/endeavouros/scripts/eos-script-lib-yad.
• EOS_ROOTER: chooses the program to give elevated privileges for running programs in the terminal. Supported programs are
  • su (default)
  • su-c_wrapper
  • sudo
  • pkexec
• EOS_WELCOME_CONNECTION_WARNING: specifies whether the welcome app shows the warning about missing internet connection or not. Values are simple “yes” or “no”.
• EOS_CONNECTION_CHECKER: configures the program to be used for checking if internet connection is available. Supported values are “ping” or “curl”.
• TERMINAL_AT_START: if properly set, makes the welcome app to start a terminal whenever the welcome app is started. See details at the config file.
• EOS_WIFIDEV_CHECK: enable or disable certain ad hoc checks about the wifi driver. The checks are made by clicking the Detect system issues button of the welcome app.
• EOS_KEEP_PKGS: lists the name of packages that shouldn’t be removed when the Detect system issues button is clicked.
• EOS_AUR_HELPER: name of the AUR helper program. Supported values: “yay” and “paru”. Yay is the default.
• EOS_WELCOME_PACDIFFERS: array of diff program names that can be used with pacdiff via a button in Welcome. The array is in preference order, the first one found is used. Supported values: kdiff3, kompare, diffuse, meld, vim, code, and more. Other diff programs may work but haven’t been tested.
• EOS_SUDO_EDITORS is a list of editor names to choose the editor for changing files that require root permissions. Currently used only by eos-update-notifier-configure.
• EOS_WALLPAPER_FETCHER selects the program that is used for downloading additional wallpapers. By default git is used, alternatively curl can be used.

Please look at file /etc/eos-script-lib-yad.conf for the latest settings and up-to-date explanations.

Note for the translators

The Welcome app has already been translated to many languages. If you (yes, you!) feel like translating Welcome to your language, this is the way to proceed:

• Take the latest English translation file https://raw.githubusercontent.com/endeavouros-team/PKGBUILDS/master/eos-translations/translation-en.bash
  as the base for your translation.
  Or, if you have a github account, clone the PKGBUILDS repo:
  git clone https://github.com/endeavouros-team/PKGBUILDS.git.
• In the beginning of this file, change the language id (e.g. en) of the variable _tr_lang to your language (for example pt_BR or de). You can get the value with command: echo $LANG. Note that the language id is two letters for some languages, but more letters for some other languages.
• If you need certain special characters (to show them properly in Welcome), look how variables _exclamation, _and and _question are defined (search the internet for the value codes). You can create new such variables if needed.
• Then simply change the quoted strings on lines starting with _tr_add2. This is of course the biggest part of this task.
• Keep the line numbers as they are in the English translation file; this helps with future changes.

Testing is an important part in creating translations. You can do it in many ways, but a straightforward way is to copy your translation file to folder

/usr/share/endeavouros/scripts

Then you can start Welcome with command:

eos-welcome --lang=<your-language-id>

For example: eos-welcome --lang=de

If you see error messages (see below), or some translations are not right, you can make required changes and test again.

When your new translation file is ready for publishing, you have many options how to deliver it to us:

• If you have a github account (or want to create one), simply make a pull request. This assumes you have cloned the EndeavourOS PKGBUILDS repo, and make all your translation work in this context.
• Create an account into the EndeavourOS forum: https://forum.endeavouros.com, and send the translation as a public forum message (or a private message to @manuel).
• You can also use command:
  cat "translation-xx.bash" | eos-sendlog
  and send the returned URL in the EndeavourOS forum like above.

Please note that not everything is translated in Welcome or in Welcome’s helper programs. We are working on it, but obviously it takes time.

How to know when more stuff needs to be translated?

There are some symptoms to notice when there are more stuff to be translated:

• The contents of the English translation file (mentioned above) has changed.
• When you start Welcome at the terminal (command: eos-welcome), you’ll see a “warning” like this:
  Info: translation issues detected, see file '/tmp/translations-X3yzK.errlog'.

Note that the warnings in the log file only indicate that some text translations are missing. By default, English translations are provided for those texts.

How to know if an earlier translation has been changed?

See here: https://github.com/endeavouros-team/PKGBUILDS/blob/master/eos-translations/Translation_changes.md

Conclusions

The Welcome app will become more powerful over time.
The purpose of Welcome is not to give all possible help in all possible situations, but simply help to go in the right direction without a great hassle. And Welcome should provide more useful features in the future, so it is not a helper only in the beginning, but a truly useful app to have and keep using.

So, enjoy!

Document updates

Update: 2020-Jul-15: added info about personalizing Welcome
Update: 2020-Jul-25: new pictures and more info
Update: 2020-Aug-11: added info for the translators
Update: 2020-Sep-04: text fixes, new button: Change Display Resolution
Update: 2020-Dec-11: added info about the Pacdiff button
Update: 2020-Dec-12: minor change to Pacdiff support
Update: 2020-Dec-15: updated file paths at Note for translators
Update: 2021-Apr-12: bring this document up to date
Update: 2021-Apr-14: clarified translation instructions
Update: 2021-Sep-30: added a tip for NVIDIA users on kernel updates; updated docs in general
Update: 2021-Nov-12: added yad/wayland known issue
Update: 2021-Dec-21: added a link to list of changed translations
Update: 2023-Feb-02: minor doc additions update Update: 2023-Mar-16: added enabling and disabling Welcome
Update: 2023-May-30: updated explanations of apps in the Welcome tabs

]]> 1001 0 44 0 https://discovery.endeavouros.com/endeavouros-tools/endeavouros-update-notifier/2021/03/ Tue, 09 Mar 2021 11:28:13 +0000 https://discovery.endeavouros.com/?p=1008

By: Manuel
Created: 2019-Dec
Updated: 2020-Apr-23, 2020-Aug-24, 2021-Jan-18, 2021-Feb-07, 2026-April-04

Note: eos-update-notifier is not installed/used by default anymore and not maintained its as is, but uasable.

What is it?

EndeavourOS Update Notifier as the name suggests, is a notifier for software updates. As is true for many other notifiers, it can also start the update process.

In addition to notifying about updates, it can

• show news about important software changes (from Arch web pages)
• call an external program for other updating (e.g. updating flatpaks)
• show if a reboot is recommended after updating certain core system packages (e.g. kernel)

Getting started

Note: newer versions of eos-update-notifier do not start automatically after install. Instead, you need to manually start the service (once) using a terminal command:

eos-update-notifier -init

By default, it checks for software updates very soon (in about a minute) after login, and then after every two hours. So that’s it for basic operation.

But if you want to change the times when to check for updates, see paragraph Configuration below.

Notifier in action

When the notifier detects any available software updates, it starts a terminal and shows what the updates are. Then it starts command pacman to do the actual update — it asks the password for elevated privileges and so on.

The notifier checks for both upstream (Arch repos) and AUR updates. But it does so in two phases: first, it handles all upstream updates, and then it handles all AUR updates. This phasing is designed to keep the basic (upstream) system in good order before updating any other software.

Note that packages in the EndeavourOS repo are updated in the first phase.

Additional services

Arch news for you

The notifier can check for Arch news. The Arch news may contain very important information about software updates, especially when user actions are required beyond the normal update process.
The Arch news checker tries to keep the amount of information as small as possible, thus avoiding news that is not relevant to the particular system. It does so by checking if the package mentioned in the Arch news is currently installed. If not, then that piece of news is skipped. That’s why the feature is referred to as “Arch news for you”.
Please note that this ad hoc method is not “foolproof”, so some relevant news might be skipped. That’s why it is recommended to check the Arch news with a browser as well at times.

Version 0.9-1 added a new alternative Arch news checker. It does not use the ad hoc method, but simply remembers the date of the last news it has shown. See /etc/eos-update-notifier.conf below.

Reboot recommended

If during the upgrade process the packages upgraded are those that will require a reboot, the notifier will show it using the system’s notification feature.

Call an external updater

If you have other software that needs updating, eos-update-notifier can call an external program, like your script, to do so. To enable that, you can write your external script name as the value of variable AdditionalEosUpdater in file /etc/eos-update-notifier.conf. See more below.

Configurator of eos-update-notifier

A small GUI program for configuring the EOS update-notifier is eos-update-notifier-configure. It can:

• edit the configuration file /etc/eos-update-notifier.conf
• start the scheduler that defines when updates are checked (see below)
• reset the scheduling timer to the factory default
• show the timer status
• run eos-update-notifier once to see if changes are OK

It can also show the changelog (git) of the eos-update-notifier program.

Configuration

Schedule checking: the GUI way (v1.8-2)

eos-update-notifier -conf

The configuration window looks like this:

Schedule checking: the manual way

To manually configure the systemd timer that sets the checking schedule, you need to modify the file

~/.config/systemd/user/eos-update-notifier.timer

The manual configuration provides more detailed configuration possibilities. Note that in the current implementation it is a user-specific systemd service. To get the modifications in effect, the service daemon should be reloaded (or alternatively simply reboot).
The commands could be something like this:

cd ~/.config/systemd/user
nano eos-update-notifier.timer # modify settings with any editor, here with 'nano'

[Unit]
Description=EOS update notifier runs periodically, and optionally after each boot, or if missed.

[Timer]
OnCalendar=weekly
# OnStartupSec=
Persistent=false
RandomizedDelaySec=10min

[Install]
WantedBy=timers.target


systemctl --user daemon-reload

To modify the values with the editor, please check the manual page first:

man systemd.time # especially: CALENDAR EVENTS

For example, there can be lines that specify when the notifier is called:

OnStartupSec=30sec
OnCalendar=0/2:25:00

The first one tells when the first check is started after login.
The second line tells the schedule of future checks. The format is

hour-spec:minute-spec:second-spec

The hour-spec here is 0/2. The tail ‘/2’ is easier to explain: it means every two hours. The 0 means the start is at 00:00. So it checks for updates at 00:25, 02:25, 04:25, etc.

Now that you know the syntax, it should be easy to change it to your liking.

Note that this file may be overwritten with certain options given to eos-update-notifier. Fortunately, eos-update-notifier makes a backup, but only one!
So if you want to keep using your modified schedule, please make a backup of your modifications.

And if you want to revert back to the default schedule, you can use the command:

eos-update-notifier -init-force

/etc/eos-update-notifier.conf

The configuration file currently includes these (bash) variables:

• CheckAurUpdates
• AdditionalEosUpdater
• CheckArchNewsForYou
• ShowWhatAboutUpdates
• ArchNewsProg

The default values (note the bash syntax: no spaces around the “=” mark!) in this file are:

CheckAurUpdates=yes
AdditionalEosUpdater=""
CheckArchNewsForYou=yes
ArchNewsProg=eos-arch-news
ShowHowAboutUpdates=notify
ShowWhatAboutUpdates=number

If CheckAurUpdates is yes, then also AUR updates are checked, otherwise, they are not checked.

The AdditionalEosUpdater variable is an advanced feature. It may contain the name of your external script. The script is meant for performing other tasks related to updating your software. It is called right after updating Arch, EndeavourOS, and possibly AUR packages. One useful example of this is to have a script that updates your flatpacks. The script gets the name of a log file as a parameter and can add log information if needed. The script should provide an exit code similar to the checkupdates program (0, 1 or 2).

If CheckArchNewsForYou is yes, then the Arch news is checked, otherwise, they are not checked.

If ShowWhatAboutUpdates is, then a simple number of available updates is shown in the notification window. Value package means the notification window includes a list of package names to be updated, including changes in the version number.

ShowHowAboutUpdates can have the following values: notify, notify+tray, tray, or window. Their meanings are:

• notify: show a simple notification using standard notification services
• notify+tray: same as above + a tray icon that can start the actual updating
• tray: show only a tray icon like above
• window: show a simple popup window that shows info about updates and allows to update or dismiss

ArchNewsProg selects the Arch news checker program. Possible values are eos-arch-news and arch-news-for-you. The first one is simpler and more reliable in showing the latest Arch news. The latter uses an ad hoc method to determine if the latest Arch news is relevant to the machine; however, this method may skip showing some relevant news, so an alternative program was added in version 0.9-1.

Some useful command line options

You may give various options to the eos-update-notifier, but probably the most useful options are:

-init	Initialize the service. Must be executed (once) in order to start checking for updates.
-conf	Configure the schedule of the update check timer.
-show-timer	Show the status of the update check timer.
-q	Be quiet: don’t show the popup that tells there are no updates.

About supported terminals

The eos-update-notifier supports (= have been tested) the following terminals:

• xfce4-terminal
• konsole
• gnome-terminal
• mate-terminal
• lxterminal
• deepin-terminal
• terminator
• qterminal
• tilix
• termite
• xterm
• kitty

Other terminals have not been tested and thus they are not supported.
Note: you might want to check the Welcome app documentation, especially the chapter Special note about the code.

]]> 1008 0 43 0 https://discovery.endeavouros.com/aur/yay-an-aur-helper-written-in-go/2021/03/ Tue, 09 Mar 2021 11:42:55 +0000 https://discovery.endeavouros.com/?p=1014

yay – _{an AUR Helper Written in Go}

by Bryanpwo

Warning: Installing packages built from the AUR is at your own risk. These build instructions are user-provided content and not supported by Arch Linux, so be aware that installing from it can cause system failures.

Although the official Arch repo houses a lot of useful packages, some packages aren’t included in it because of various reasons like being closed source, custom-made packages by Arch users, or because the original package creator dropped support for it and it’s being maintained by Arch users.

Unlike the packages in the Arch repo, the AUR build instructions are being maintained by Arch users and the majority are doing this on the side as a hobby next to their regular lives. Therefore package updates aren’t tested extensively and can cause trouble by a non-responding app or even can cause breakage to the system, so using it is your own responsibility. However, don’t hesitate to ask the community for help if an update has caused problems, we will help you anyway.

Having informed you of that, you can use yay to install packages from the AUR and Pacman easily.

Installing packages

To install packages with yay is basically the same as with using pacman itself:

yay -S package_name

With yay you can also get a choice and let it search if there are alternatives:

yay package_name

After that, you will see a numbered list of the package names in the installed repos of your system. Simply type in the number of the package version you want to install and yay is going to install it on your system.

If you want some more information on a package you can type in:

yay -Si package_name

Yay can also update both Pacman and AUR packages at once by this command:

yay

_{This will call yay -Syu which is set as default on running yay.}

Again, think twice before using built from AUR and ask yourself if you really need the package you want to install.

If you use yay to install and search, it will always show both real packages from the repositories and the AUR build options you can be built with yay using the built instructions and files it will download from the AUR.

You can search and install or remove normal packages from the repositories using yay.

You can identify where it finds the search term as a package or AUR build-instructions-files in the output:

Troubleshooting

In some cases it happens that the yay package in the EndeavorOS repository is not completely up to date. In such cases, you can also build and install it yourself, as is preferred in the Archwiki:

git clone https://aur.archlinux.org/yay.git
cd yay
makepkg -si

This is not magic, everyone who uses an Archlinux based system should get the knowledge about some basic commands.

It will indeed replace the package from EndeavourOS repository, but this generally build with the same PKGBUILD.

_{If we update it after this, you will again receive the newer package from the repository, you can also force in case it is updated run: sudo pacman -Syu yay ... but that's not needed.}

Building complex packages, Parallel compilation:

By default arch do not set to use all CPU cores to compile packages, this can be an issue if you want to build bigger packages like kernels and other stuff.

The make build system uses the MAKEFLAGS environment variable to specify additional options for make. The variable can also be set in the makepkg.conf file.

Users with multi-core/multi-processor systems can specify the number of jobs to run simultaneously. This can be accomplished with the use of nproc(1) to determine the number of available processors:

MAKEFLAGS="--jobs=$(nproc)"

Simply add this to you /etc/makepkg.conf file to use all CPUs.

See the links above for more Information:

More information:

AUR official Website: https://aur.archlinux.org/

Sourcecode: https://github.com/Jguer/yay

About AUR helpers: https://wiki.archlinux.org/index.php/AUR_helpers

About building packages: https://wiki.archlinux.org/index.php/Makepkg

]]> 1014 0 40 0 457 https://dryusdan.space/decouverte-de-endeavouros 0 0 https://discovery.endeavouros.com/aur/faq-what-is-the-aur/2021/03/ Tue, 09 Mar 2021 11:45:11 +0000 https://discovery.endeavouros.com/?p=1016

by Jonathon

The Arch User Repository (AUR) is a collection of user-submitted package description files ( PKGBUILDfiles). These description files can be used to create package archive files ( .pkg.tar.zst files).

These PKGBUILD files can be used by an AUR helper (e.g. yay , aurman , Pamac) or manually built using makepkg. The resulting package archive file can then be installed in the normal way.

All content on the AUR is uploaded by ordinary users and very little checking of their content is done – it is up to you to verify the content is safe to use.

The best (most detailed and accurate) source of information about the AUR is the Arch wiki page: https://wiki.archlinux.org/index.php/Arch_User_Repository 

Please read it – especially the AUR FAQ 3 section. There’s no need to repeat it all here. 

---

Some frog [icon name="frog" prefix="fas"] thinking about that too at the forum:

_{originally written by kresimir here: https://forum.endeavouros.com/t/aur-pkgbuilds/6669/18}

The AUR is one of the safest ways to install software, just because it is so transparent. But it does not tolerate just looking up the package in Pamac and clicking on the Build button, or doing yay package_name blindly. It requires that the user knows what’s going on. That’s why I recommend trying to build at least one package manually, to understand what’s going on, before using an AUR helper like pamac or yay.

yay has a nice feature that allows you to inspect a PKGBUILD file before installing, and to see the differences in the PKGBUILD file when updating a package from the AUR. Do not ignore this feature, it is very useful and will make your AUR usage much safer.

Here are some tips on how to be safe using the AUR.

• First of all, look up the package on aur.archlinux.org 25, see the comments, upvotes, popularity, name of the packager, etc… If it is not a popular package, be extra careful when inspecting the PKBUILD file. Look at the date the package was last updated. If it is fairly old, or updated by the same person, and people are using it, it’s almost certainly safe. If there is anything fishy going on, it will be removed from the AUR fairly quickly.

What to look for in the PKGBUILD file? You’ll have to learn some elementary shell scripting to understand what’s going on. This is easier than it sounds.

• Inspect even the PKGBUILD files for completely trustworthy packages, just so you learn to recognise a good PKGBUILD file. When you see a dozen good PKGBUILD files and you understand what’s going on there, you’ll already have the feeling for anything that is out of place.
• Look for anything obviously malicious, like rm, mv commands, any output redirection, any mention of /dev (like /dev/null, /dev/sda, /dev/zero, /dev/random), mkfs, any call to pacman, systemctl, anything that touches grub… stuff like that.
• Look for any command that does stuff in your home directory. Typically, building and installing packages should not touch anything in the home directory. If you find something like that, be very suspicious and make sure you completely understand what that command does.
• Look for anything that looks intentionally obfuscated. Anything that is written in an unclear way, with many semicolons, &&s and ||s, lots of brackets, sed, awk, etc… Typically, good PKGBUILDs contain very simple instructions.
• Make sure the software comes from a trustworthy place, whether it’s a binary distribution or the source code. Check all the URLs in the script, make sure they are official pages for the software you’re installing. All URLs should be listed neatly in the beginning of the file. Look for any downloads of external scripts, with curl or wget, there should not be anything like that. Beware of random Github places.
• Use common sense.

Also, when you install something from the AUR, consider upvoting it on aur.archlinux.org 25, just to let everyone know it’s a good package. Votes are one of the criteria for package inclusion in the official repos. If you notice anything malicious, do not neglect to report it. Upvoting good packages and reporting bad ones is the easiest way to improve the AUR for everyone.

]]> 1016 0 39 0 https://discovery.endeavouros.com/hardware/intel/2021/03/ Tue, 09 Mar 2021 12:48:19 +0000 https://discovery.endeavouros.com/?p=1031

First of all, a link to the detailed ArchWiki:

https://wiki.archlinux.org/index.php/Intel_graphics

Since Intel provides and supports robust open-source drivers in the Linux kernel and Mesa, Intel graphics are essentially plug-and-play on EndeavourOS.

That’s why it is strongly recommended not to install the legacy xf86-video-intel driver package unless you are troubleshooting extremely old pre-Gen4 hardware. The built-in modesetting driver which comes bundled with the Xorg server and Wayland compositors rely directly on the kernel Direct Rendering Manager (DRM) and Mesa, offering superior performance, stability, and power management.

More options on the arch package man page:

Intel Arch Manpage

or directly intel informations on the linux driver:

https://01.org/linuxgraphics

Understanding Intel Kernel Drivers: i915 vs. xe

Depending on the age and generation of your Intel processor or discrete GPU, your system will use one of two kernel drivers:

1. i915 Driver: The mature, stable driver for older and current Intel integrated graphics (from Haswell / Broadwell up through Comet Lake, and still handling display/audio or legacy fallbacks on newer chips).
2. xe Driver: Intel’s modern, high-performance DRM driver designed for modern integrated graphics (Tiger Lake and newer, including Alder Lake, Raptor Lake, Meteor Lake, Lunar Lake, Arrow Lake) and Intel Arc discrete GPUs (Alchemist, Battlemage, etc.).

Checking Your Current Driver

You can check which graphics driver is currently handling your GPU by running:

lspci -nnk | grep -A 3 VGA

Look at the Kernel driver in use: line in the output. It will show either i915 or xe.

Testing and Forcing the New xe Driver

On many processors (such as Tiger Lake, Alder Lake, and Raptor Lake) and discrete GPUs (such as Intel Arc cards like the A740/A750/A770), the older i915 driver may still claim the hardware by default, even when the modern xe driver is fully available in the kernel.

If auto-detection falls back to i915 or you want to explicitly force the xe driver on supported hardware, you can prevent i915 from probing your device and instruct xe to take over using kernel parameters.

1. First, find your GPU’s PCI device ID using lspci:lspci -nn | grep -i vga Or for discrete graphics / Arc cards:lspci -nn | grep -i display Example output: 00:02.0 VGA compatible controller [0300]: Intel Corporation Raptor Lake-S GT1 [UHD Graphics 770] [8086:a780] (rev 04)
   In this example, the PCI ID is a780.
2. Add the force-probe kernel parameters (detailed below in the bootloader section):i915.force_probe=!a780 xe.force_probe=a780

(Note: The xe driver is under active development. While it brings significant performance improvements, some features or stability on specific laptops/motherboards may still vary.)

Adding Kernel Parameters to set options

EndeavourOS provides flexibility with bootloaders, supporting both systemd-boot (default for UEFI installations) and GRUB. Depending on which bootloader your system uses, apply kernel parameters as follows:

1. If using systemd-boot (Default)

On EndeavourOS UEFI installations using systemd-boot, kernel parameters are managed globally via /etc/kernel/cmdline.

1. Open the command line file with your preferred text editor (e.g. nano):sudo nano /etc/kernel/cmdline
2. Add your desired kernel options (such as disabling Panel Self Refresh i915.enable_psr=0 or forcing the Xe driver) to the single line of text:quiet rwloglevel=3 i915.enable_psr=0 i915.force_probe=!a780 xe.force_probe=a780
3. Save the file and regenerate your boot entries/UKIs by running the EndeavourOS helper command:sudo reinstall-kernels

2. If using GRUB

If your system is configured with GRUB:

1. Open /etc/default/grub in an editor:sudo nano /etc/default/grub
2. Locate the GRUB_CMDLINE_LINUX_DEFAULT line and add your parameters inside the quotes:GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=3 i915.enable_psr=0"
3. Save the file and update GRUB:sudo grub-mkconfig -o /boot/grub/grub.cfg

Common Intel Graphics Troubleshooting Options & Module Parameters

If you experience graphical flickering, screen corruption, or freezing on Intel graphics, here are some common parameters to test. You can find comprehensive lists of available module parameters and tuning options in the official documentation:

• ArchWiki: Intel Graphics Kernel Parameters
• Linux Kernel DRM/i915 Documentation
• Linux Kernel DRM/xe Documentation

Common Parameters to Know:

• Disable Panel Self Refresh (PSR): PSR can cause screen flickers, micro-stutters, or temporary black screens on some laptop panels when content is static. You can disable it with:
  • For i915: i915.enable_psr=0
  • For xe: xe.enable_psr=0
• Driver Force Probe:
  • i915.force_probe=... / i915.force_probe=!device_id
  • xe.force_probe=device_id

]]> 1031 0 36 0 https://discovery.endeavouros.com/nvidia/nvidia-installer/2021/03/ Tue, 09 Mar 2021 12:56:56 +0000 https://discovery.endeavouros.com/?p=1035

nvidia-installer-dkms

This article here will get removed soon and is not working anymore

the old nvidia-installer-dkms is replaced with a rewritten new tool nvidia-inst go here please:

https://discovery.endeavouros.com/nvidia/new-nvidia-driver-installer-nvidia-inst/2022/03/

_{by joekamprad}

We do offer a script that was developed for Antergos by karasu and we forked it to use it for EndeavourOS.

nvidia-installer-dkms can be used easily to install and remove proprietary Nvidia drivers.

The package is available from EndeavourOS Repository to install it:

sudo pacman -S nvidia-installer-dkms

We ship the dkms version by default so the drivers can be kept up-to-date, regardless of the kernel version you're using. Using the dkms version also means, you need to install the kernel header packages that match to your installed kernel(s).If you are using our AKM tool, the headers will be installed by default.

// example for linux-lts: sudo pacman -S linux-lts-headers

The Nvidia-installer includes a tool nvidia-installer-check that can be used for checking which of the Nvidia-driver version is supported by your NVidia graphics card. Here are some examples of its output:

$ nvidia-installer-check 
Your graphics card (id 1dba) is supported by the nvidia-dkms driver.

$ nvidia-installer-check 
Your graphics card (id 06c4) is supported by the nvidia-390xx-dkms driver.
Use the --force option with nvidia-installer-dkms.
Then, BEFORE rebooting, install nvidia-390xx-dkms from the AUR, for example:
  yay -S nvidia-390xx-dkms

$ nvidia-installer-check 
Sorry, your Nvidia card (id: aaaa) is not supported by nvidia-dkms nor nvidia-390xx-dkms.

More info on dkms:

https://wiki.archlinux.org/index.php/Dynamic_Kernel_Module_Support

Workaround for NVidia cards that require 390xx series driver

• Use nvidia-installer-dkms to install nvidia-dkms (may need to use the --force option)
• If you get a warning about card is not in our database, then, before rebooting, install nvidia-390xx-dkms from the AUR:

yay -S nvidia-390xx-dkms

This is a list of all options for the script:

nvidia-installer-dkms -h (shows help)

usage: nvidia-installer-dkms [-h] [-b] [-f] [-t] [-q] [-n]
 EndeavourOS Nvidia Installer v2.1
 optional arguments:
   -h, --help       show this help message and exit
   -b, --bumblebee  For Nvidia Optimus cards (Bumblebee + proprietary Nvidia drivers)
   -f, --force      Force driver installation even if a nvidia card is not detected
   -t, --test       Test mode. Nothing in your system will be modified
   -q, --quiet      Supress log messages
   -n, --nouveau    Restores nouveau (open) nvidia driver

Install Nvidia proprietary drivers

test run for installation (It will perform a dry run without making any changes to the system)

nvidia-installer-dkms -t

When there are no errors reported, then run:

sudo nvidia-installer-dkms

This will install Nvidia proprietary drivers and performs some configuration inside /etc/X11/xorg.conf.d/

Then run:

sudo systemctl reboot

And you are running Nvidia drivers!

Bumblebee for older Nvidia-Intel Optimus notebooks:

If you need to set up Bumblebee as detailed here: EndeavourOS Bumblebee wiki the nvidia-installer script can do that automatically too:

sudo nvidia-installer-dkms -b

This will look like this:

nvidia-installer -b
2017-12-17 17:02:29 [INFO]: EndeavourOS Nvidia Installer v2.1
2017-12-17 17:02:29 [INFO]: All logs will be stored in /tmp/nvidia-installer.log
2017-12-17 17:02:29 [INFO]: Installing bumblebee driver...
2017-12-17 17:02:29 [INFO]: Removing conflicting packages...
2017-12-17 17:02:29 [INFO]: Downloading and installing driver packages, please wait...
2017-12-17 17:04:43 [INFO]: Adding user username to bumblebee group...
2017-12-17 17:04:43 [INFO]: gpasswd -a username bumblebee
2017-12-17 17:04:43 [INFO]: Adding user username to video group...
2017-12-17 17:04:43 [INFO]: gpasswd -a username video
2017-12-17 17:04:43 [INFO]: Enabling bumblebeed.service service...
2017-12-17 17:04:43 [INFO]: systemctl enable bumblebeed.service
2017-12-17 17:04:43 [INFO]: Patching /usr/share/applications/nvidia-settings.desktop...
2017-12-17 17:04:43 [INFO]: /etc/X11/xorg.conf.d/20-nvidia.conf not found. That's ok.
2017-12-17 17:04:43 [INFO]: Installation finished. You need to reboot now!

[icon name="flag" prefix="fas"]

Workaround in case Xorg fails to load on DE sessions

and Optimus hybrid graphics Notebooks:

Remove the file:

/etc/X11/xorg.conf.d/20-nvidia.conf

It is not needed per default as Xorg will use default detected settings automatically in most cases.

This can also affect systems using Wayland sessions like GNOME or Plasma and sway.

As Wayland uses settings it takes over from Xorg in cases.

You may need the nvidia Xorg file to enable some features for the Nvidia GPU Driver like:

nvidia-optional-enhancements-and-troubleshooting

---

All Nvidia entries: https://discovery.endeavouros.com/?s=nvidia

]]> 1035 0 35 0 Nvidia Optional Enhancements and Troubleshooting]]> New Nvidia driver installer, nvidia-inst]]> https://discovery.endeavouros.com/nvidia/nvidia-optional-enhancements-and-troubleshooting/2021/03/ Tue, 09 Mar 2021 13:01:56 +0000 https://discovery.endeavouros.com/?p=1037

Nvidia Optional Enhancements and Troubleshooting

It can happen that you will fail to load the Nvidia driver in some cases, such as the presence of an integrated intel GPU (build-in on Motherboard). The system can get confused and fail to properly load on the Nvidia Driver, in this case, there is a workaround to force loading Nvidia Driver in the early boot (KMS) state and forcing the loading of modules on the kernel boot option. Mainly for use on dedicated GPU-Cards (PCIe Cards on Desktop PC or Notebooks with only Nvidia GPU [non-hybrid] ). It can cause issues for hybrid systems (optimus)!

• For example: On Cinnamon you will see a message that you run in Software Rendering Mode, or the system simply boots to a black screen.. not starting X ... no Login Manager starting

If you have this issue there are two ways to load the needed modules early in the boot process to have them fully initialized when reaching X. Adding it to grub kernel line or using kernel-images (Force early load [KMS]):

With the latest Nvidia driver and module packages on Archlinux we do not need to add drm modestting nor any of the systemd-services manually all is enabled by default now.

Force early load (KMS)

In most cases when you can not reach the DM (loginmanager lightdm/GDM/SDDM) it needs to force to load nvidia drivers on early boot. To do so:

For dracut installs (deafult up from cassini release):

create a dropin config:

sudo nano /etc/dracut.conf.d/nvidia.conf

and add the following line:

add_drivers+=" nvidia nvidia-drm nvidia-modeset nvidia-uvm "

rebuild kernel images:

sudo reinstall-kernels

for mkinitcpio usage:

edit mkinitcpio.conf to get the module inside:

sudo nano /etc/mkinitcpio.conf

and edit like this:

# vim:set ft=sh

# MODULES

# The following modules are loaded before any boot hooks are

# run. Advanced users may wish to specify all system modules

# in this array. For instance:

# MODULES="piix ide_disk"

MODULES="nvidia nvidia_modeset nvidia_uvm nvidia_drm"

# BINARIES ....

save the file as above…

rebuild kernel image

dracut (default)
sudo reinstall-kernels (systemd-boot)

sudo dracut-rebuild (grub Bootloader)

mkinitcpio:

sudo mkinitcpio -P

reboot again and you should have early boot enabled…

Enhancement avoid screen tearing (only on X11)

Have nvidia-settings installed and run it on login with tagging option FullCompositingPipeline to get better video quality, this works for a single display setup. If you have more, you need to add them to the command or option line, for this take a look at the arch-wiki page linked here.

nvidia-settings --assign CurrentMetaMode="nvidia-auto-select +0+0 { ForceFullCompositionPipeline = On }"

https://wiki.archlinux.org/index.php/NVIDIA/Troubleshooting#Avoid_screen_tearing

You can add this to /etc/X11/xorg.conf.d/20-nvidia.conf like this:

Section "Device"
    Identifier "Nvidia Card"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
EndSection

Section "Screen"
        Identifier      "nvidia"
        Option         "metamodes" "nvidia-auto-select +0+0 { ForceFullCompositionPipeline = On }"
        Option          "TripleBuffer"                  "on"
        Option          "AllowIndirectGLXProtocol"      "off"
EndSection

In some cases like using Plasma and SDDM it can be that you need to set DPI settings on multi-display setups.

The easiest way around this is to set DPI in .Xresources to do so:

sudo nano ~/.Xrescources and add DPI settings.

Xft.dpi:     96

On KDE, this can be achieved by adding the following section to /etc/sddm.conf (create the file if it does not exist) :

[X11]
ServerArguments=-nolisten tcp -dpi 96

Replace 96 by your desired DPI value.

There is also a PKGBUILD at AUR to build a simple auto starter for full-compositing-pipeline:

https://github.com/Askannz/nvidia-force-comp-pipeline

you can build and install:

yay -S nvidia-force-comp-pipeline nvidia-settings

It will check display setup and enable it automatically using nvidia-settings on login to the session.

---

All Nvidia entries: https://discovery.endeavouros.com/?s=nvidia

]]> 1037 0 34 0 https://discovery.endeavouros.com/nvidia/nouveau/2021/03/ Tue, 09 Mar 2021 13:03:56 +0000 https://discovery.endeavouros.com/?p=1039

by Bryanpwo

If your Nvidia card isn’t supported anymore by the proprietary nvidia driver, you can use the open-source driver provided by Linux.

Only in case you have a very old Nvidia GPU use the nouveau driver provided by the package xf86-video-nouveau, It is most likely this package will cause tearing and bad performance on GPU from the last 6 years, so it is better to use the modesetting driver shipped by default in the Linux kernel. To enable it, you just have to uninstall the unneeded package and change the following configuration.

sudo pacman -R xf86-video-nouveau

sudo nano /etc/kernel/cmdline

Add nouveau to the line as an additional option.

Save it with [CTRL+X]

To add the option to initramfs image, run: sudo reinstall-kernels (if using systemd-boot)

For Grub use sudo dracut-rebuild

Reboot and your system is running with nouveau modesetting driver.

In some cases, the video quality has a delay or glitches, especially with DRM encoded videos on services as Netflix for example.

In that case, try to install the nouveau-fw package (AUR) - after install reboot the system.

]]> 1039 0 33 0 https://discovery.endeavouros.com/nvidia/nvidia-optimus-notebooks-hybrid-graphics/2021/03/ Tue, 09 Mar 2021 13:05:45 +0000 https://discovery.endeavouros.com/?p=1041

Find out if you are on such system run this from terminal:

lspci -vnn | grep '\''[030[02]\]'

if it gives out something like this with two devices:

00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller])

01:00.0 3D controller [0302]: NVIDIA Corporation GK107M [GeForce GT 750M] [10de:0fe4] (rev ff) (prog-if ff)

It will be that you have such hybrid system with a combination of NVIDIA and intel GPU.

Some basic information on that: https://wiki.archlinux.org/index.php/Hybrid_graphics

DRM Modesetting:

As of 2021 the proprietary Nvidia Driver supports handling of Optimus hybrid systems per default.

It will boot on intel integrated per default. Modesetting DRM needs to be enabled Archlinux packaging does this by default for latest Nvidia drivers.

Only the old legacy drivers nvidia-470xx-dkms and older would need to have it added to boot kernel options to get loaded:

With systemd-boot:

create a dropin config:

sudo nano /etc/dracut.conf.d/nvidia.conf

and add the following line:

add_drivers+=" nvidia nvidia-drm nvidia-modeset nvidia-uvm "

rebuild kernel images:

sudo reinstall-kernels

With Grub Bootloader:

sudo nano /etc/default/grub

and add it to the CMD line (adding not removing anything thats already there):

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia_drm.modeset=1 nvidia nvidia-drm nvidia-modeset nvidia-uvm" (only example line yours may look different)

sudo dracut-rebuild

Switching decent GPU on:

To be able to switch between the two GPUs usage, you can use one of the options to have this available in different ways:

Switcheroo-Control D-Bus service to check the availability of dual-GPU, integrates with the settings of KDE/plasma Gnome, and Cinnamon: “Launch using Dedicated Graphics Card” menu item appears on application starter contextual menu per example. switcheroo-control

Supergfxctl is a useful utility provided by ASUS Linux. It helps with managing GPU switching functionality on hybrid laptops. _{(While supergfxctl was originally designed with ASUS Optimus laptops in mind, it has since evolved into a standalone tool that functions with any laptops with hybrid graphics.)}

Supergfxctl

EnvyControl is a CLI tool that provides an easy way to switch between GPU modes on Nvidia Optimus systems:

Envy-Control

Optimus-manager is one solution currently where you can switch between the two GPU’s:

Optimus-Manager

Optimus Switch is completely powerdown Nvidia GPU and will save more power, but needs to reboot system to do so:

Optimus-Switch

Render Offload is a new mechanism build inside the Nvidia Driver:

Render-Offload

Overview (may more recent) on Archwiki: https://wiki.archlinux.org/title/NVIDIA_Optimus#Available_methods

Some helpful links to tutorials:

https://github.com/linesma/Optimus-indicator

https://forum.endeavouros.com/t/optimus-manager-issues/7403/15

https://github.com/Askannz/optimus-manager

https://wiki.archlinux.org/index.php/PRIME

https://forum.endeavouros.com/t/optimus-switch-another-solution-for-optimus-laptops

]]> 1041 0 32 0 How to enable Nvidia Optimus]]> How to enable Nvidia Optimus]]> Nvidia Optional Enhancements and Troubleshooting]]> https://discovery.endeavouros.com/nvidia/bumblebee-for-nvidia-optimus-older-systems/2021/03/ Tue, 09 Mar 2021 13:07:50 +0000 https://discovery.endeavouros.com/?p=1043

Bumblebee for NVIDIA Optimus (older systems)

This is candidate for removal, as of only needed for devices already gone legacy for long times.

Introduction

For some older Optimus hardware it is still useful to have bumblebee to handle switching between discrete and integrated GPU.

On newer Nvidia Optimus systems it is recommended to take optimus-manager, optimus-switch, or render-offload.

Some computers may need BIOS adjustments before Bumblebee installation.  See the Two BIOS types section.

Bumblebee installation and removal are simple and straightforward processes.  See Installation and Remove Bumblebee sections.

The text speaks about a fresh Bumblebee installation.  It is also a repairing tool.  If Bumblebee is already installed but you’re unsure about its state, simply install Bumblebee again.  It does not hurt a system in any way.

Bumblebee’s power-saving feature was missing in the mid of 2015.  See Missing power-off section.

Do I have an Optimus card?

First things first.  An excerpt from Bumblebee Project Wiki  Troubleshooting section:

“Only laptops have these kinds of Nvidia Optimus card, so this project won’t apply to desktops (for now).  Cards from the 4xxM and newer series are all Optimus-enabled. The M stands for “Mobile”. But having a 4xxM card isn’t enough to be sure that you’re having an Optimus laptop. There must also be an integrated video controller in your processor. To check that, run this command in a terminal:

lspci -vnn | grep '\''[030[02]\]'

If it outputs two lines, then you’re likely to have an Optimus laptop.  Else…“

…this article is of no help for your card.

On NVIDIA Optimus two output lines look like this:

00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller])

and

01:00.0 3D controller [0302]: NVIDIA Corporation GK107M [GeForce GT 750M] [10de:0fe4] (rev ff) (prog-if ff)

The first line starts with 00:02.0.  It corresponds to Intel GPU.

The second line starts with 01:00.0.  It corresponds to Nvidia GPU.

Your Intel and Nvidia make and model will obviously be different from this example.

Take note of your Nvidia model because the driver version you install will depend on it

(see the section, Do I Have Legacy or Current Hardware?).

Two BIOS types

For the purpose of this guide let’s distinguish two BIOS types:

1. BIOS doesn’t control video card and doesn’t mention it
2. BIOS tries to control integrated and/or discrete video cards

1st type BIOS is the most Bumblebee-friendly.  It doesn’t require to enter BIOS Setup utility, to configure or change anything in BIOS.  Just boot the computer normally and, if possible, make sure it runs on xf86-video-intel video driver.  It should be so by default.  Nothing else is required.

2nd type of BIOS is less Bumblebee-friendly.  It requires entering the BIOS Setup utility and make some adjustments within it.  Before and after Bumblebee installation.  All BIOS changes in the guide refer only to the 2nd BIOS type.  Make sure the computer runs on xf86-video-intel.

Briefly.  Bumblebee installation on:

1. 1st type BIOS doesn’t require any change in BIOS setup
2. 2nd type BIOS may require some changes in BIOS setup before and after Bmb installation

Manual Installation

see: nvidia-installer-dkms for instructions on how to install bumblebee automatic

Disable and remove Nouveau

Edit 2017-07-14:  Intel + Nouveau combination is deprecated.  It is not supported by Bumblebee anymore.  Intel + Nouveau support can be dropped from Bumblebee at any time.  Bumblebee supports Intel + Nvidia combination only.

Nouveau video driver causes many troubles on NVIDIA Optimus cards.  Unbootable system, crashes during boot, a system that boots into unresponsive black screen with a white text cursor blinking in the top left corner, Cnchi and LiveDE freezes are only a few of Nouveau effects.

If you don’t experience any of these issues, you may safely skip this section.  Otherwise, keep reading on.

Three steps are needed to remove Nouveau.

1. Disable it during a boot from LiveMedia, to be able to start LiveDE with Calamares and complete the installation

2. Disable it on the first boot of the installed system, to be able to reach the graphical DE

3. Physical Nouveau package uninstallation on the first boot; the system will use Intel GPU on subsequent boots until Bumblebee installation

Steps in detail.

1. Use the default LiveMedia boot menu option.  Edit the boot line and add to it the following parameter:

modprobe.blacklist=nouveau

Continue to boot normally.

2. Disable Nouveau on the first boot of the installed system, exactly the same way as in the previous step.

3. Once you’ve reached the graphical DE, open the terminal and run the following command, to remove Nouveau completely:

sudo pacman -Rc xf86-video-nouveau

It is a common mistake to use nouveau.modeset=0 parameter in an attempt to exclude Nouveau. The parameter only shifts the responsibility for setting up the graphical mode from Xorg to the kernel. It doesn’t prevent the nouveau module from being loaded and used.

Install EndeavourOS without Nvidia drivers

Doing a fresh EndeavourOS installation, make sure to not install proprietary Nvidia drivers.  The option installs drivers for single-GPU, non-hybrid video cards, with NVIDIA GPU only.  It does not install drivers for double-GPU, hybrid video cards with NVIDIA, and Intel GPUs.

Do not choose to install NVidia at the package/DE selection page!!

Failing to do so will result in an unbootable NVIDIA Optimus system.

With Graphic drivers (Proprietary) not installed EndeavourOS will install Intel drivers only and make use of the nouveau driver shipped with the kernel (modesetting driver)

By default, Nvidia GPU is never active, or switched on, in Optimus computers with the 1st type BIOS. Nvidia GPU remains unused and switched off until it is activated by proprietary Nvidia or by free Nouveau drivers.

Bumblebee switches Nvidia GPU ON and OFF automatically, whichever is needed.

Disable Optimus, 2nd type BIOS only

The owners of the 1st type of BIOS may safely skip this section.

After the installation has been completed reboot your system, and enter the BIOS configuration utility. Most Nvidia Optimus cards run alongside Intel integrated graphics. Find your display settings, and select “Intel Integrated”, or something similar – just make sure that Optimus and Discrete are not enabled.  Also, make sure that the setting below it, the “Detection by OS” setting is disabled. After this step has been completed, you may reboot, and enter your new install of EndeavourOS.

Enable [multilib] repo

The repo is already enabled by default in recent EndeavourOS releases.  If you install on native Arch Linux, Arcolinux, or other systems which use unmodified Arch repos, then edit the /etc/pacman.conf file and uncomment the repo.

Fully upgrade the system

yay -Syua

Install Bumblebee

On modern hardware, with current drivers:

sudo pacman -S bumblebee mesa xf86-video-intel nvidia lib32-nvidia-utils lib32-virtualgl nvidia-settings bbswitch

On older hardware, with 390xx legacy drivers:

yay -S --needed bumblebee mesa xf86-video-intel nvidia-390xx nvidia-390xx-utils lib32-nvidia-390xx-utils lib32-virtualgl bbswitch

On even older hardware, with 340xx legacy drivers:

yay -S --needed bumblebee mesa xf86-video-intel nvidia-340xx nvidia-340xx-utils lib32-nvidia-340xx-utils lib32-virtualgl bbswitch

Add yourself to bumblebee group

Any user that is supposed to use Bumblebee must be added to this group.  The user must also be a member of the video group – it is usually so by default, but not always.

sudo gpasswd -a $USER bumblebee

sudo gpasswd -a $USER video

Enable bumblebeed service

Notice the final d (from daemon) letter in the service’s name.  The step may be skipped if the next step will be executed.

sudo systemctl enable bumblebeed.service

Reboot the system

sudo shutdown -r now

Enable Optimus, 2nd type BIOS only

The owners of the 1st type of BIOS may safely skip this section.

Startup your computer, and once again, enter your BIOS utility configuration. Find the Display configuration and change it from “integrated graphics” to “Optimus”. Leave the “Detected by OS” in the “Disabled” position.

Missing power off

Edit 2016.07:  Somewhere in 2016.06 the issue has been solved upstream.  If you install after this date, most probably the problem will not be present.  Check it with the test described here.  There’s no need to install the patch.

Most time NVIDIA Optimus cards run on Intel GPU.  It is done for power saving.  Nvidia GPU is used only when explicitly instructed to do so – by placing the optirun command in front of the program’s name.  When optirun exits it should immediately switch Nvidia GPU off and turn back to Intel GPU. It does not happen recently. Nvidia is not switched off.  The system continues to run on Nvidia.

There’s no power saving, computer becomes overheated, cooling fans are constantly spinning at max speed. Technically speaking, the issue is caused by the fact that nvidia_drm,  nvidia_modeset and nvidia modules are not unloaded upon optirun termination.

When the system runs on Intel GPU, three modules are not used and are not loaded.  All are loaded only when optirun starts running.  And should be unloaded on optirun termination.  Which doesn’t happen.

Check if your system is affected by the issue.  After startup open a terminal and run three commands, one after another:

optirun --status

Bumblebee status: Ready (3.2.1). X inactive. Discrete video card is off.

optirun pwd ~/

optirun --status

Bumblebee status: Ready (3.2.1). X inactive. Discrete video card is off.

If after the last (third) command the Discrete video card is off, like in the example above, then the system is not affected by the issue.  You may skip this section.

If after the last (third) command the Discrete video card is on, then the system is affected by the issue.  You may wish to solve it, either manually or automatically.  Below is described how to do it.

Turning Off Nvidia Manually

First, let’s try to shut down Nvidia by hand.  To be sure that we’re facing the issue described here; three modules must be listed exactly in the same order as in this example:

sudo rmmod nvidia_drm nvidia_modeset nvidia

sudo tee <<<OFF /proc/acpi/bbswitch

The first command forces three modules to be unloaded.  The second one switches Nvidia GPU off.  Check Nvidia status again:

optirun --status

Bumblebee status: Ready (3.2.1). X inactive. Discrete video card is off

Let’s run a bit more complicated test.  It will switch Nvidia on and then back off, in one command:

optirun pwd && sleep 1 && sudo rmmod nvidia_drm nvidia_modeset nvidia && sudo tee <<<OFF /proc/acpi/bbswitch

This method may be used to switch Nvidia off by hand.  

Turning Off Nvidia Automatically

The method to solve the issue automatically was discussed in Arch Linux bug-tracker here.  It applies the same two commands seen in the previous section.

The advantage of the method is that there’s no need to enter any command by hand in the terminal, with elevated privileges.  Optirun turns to work normally, as usual, automatically switching Nvidia ON and OFF when it starts and exits.

The disadvantage is that you’ll need to install a “homemade” package, unknown to regular Arch repos.

Download the file and install it normally with pacman, like any other package:

sudo pacman -U /path/to/package/bumblebee-3.2.1-11-x86_64.pkg.tar.xz

The package has no dependencies.  During installation, it will issue three informational messages.  They may be safely ignored.

With the package installed, pacman and pamac will issue the warning on subsequent system upgrades.  It may be safely ignored as well:

warning: bumblebee: local (3.2.1-11) is newer than community (3.2.1-10)

Important.  Once the package is installed, the computer must be rebooted.  A simple logout-login is not enough.

Fine tuning NVIDIA Optimus settings

It is possible to fine-tune NVIDIA settings, by running the nvidia-settings utility on NVIDIA GPU

optirun -b none nvidia-settings -c :8

The command is the only correct way to execute nvidia-settings on Optimus computers. Any attempt to run nvidia-settings utility with a different syntax will fail.

Adjust menu to run NVIDIA settings

Once Bumblebee and proprietary NVIDIA drivers are installed, the menu entry to launch nvidia-settings utility is automatically created.  It is called NVIDIA X Server Settings in the menu.

This menu entry is wrong for NVIDIA Optimus.

The menu is not configured correctly right after the installation.  It executes the simple nvidia-settings command.

If you select NVIDIA X Server Settings menu entry with the default content (command), you will be advised to run nvidia-xconfig utility, to fix the problem.  Never do that.  The problem does not exist.  See the Warning section below for more info.

If you want to run NVIDIA X Server Settings from menu, you have to edit the menu entry by hand, and replace the default incorrect command with the correct one.

From:

/usr/bin/nvidia-settings

To:

optirun -b none nvidia-settings -c :8

Warning

There’s nvidia-xconfig utility, installed with Bumblebee among NVIDIA tools. 

Never run it on Optimus computers. 

It was designed for and works correctly on single-GPU NVIDIA cards only.  It doesn’t detect hybrid NVIDIA Optimus cards. It’s a perfect Bumblebee killer.  If executed, it immediately breaks Bumblebee configuration.  

Known Issues

GeForce GTX 960M

When rebooting your computer might not start again. To solve that issue add acpi_osi=”!Windows 2015″ as a kernel parameter. See issue #764(comment) on github.

To make that change permanent in grub add in /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=\"!Windows 2015\""

 and create grub config after with the command

sudo grub-mkconfig -o /boot/grub/grub.cfg

Cards used

The article was written and is being continuosly tested on three Nvidia Optimus video cards:

• GeForce GT 555M
• GeForce GT 650M
• GeForce GT 750M

It was not tested on recent Optimus cards, like GeForce GTX 10-Series Notebooks.  There are reports about successful Bumblebee installation on modern GeForce Optimus, though they still may present some problems which are not covered here.

The article was written and tested on PC laptops only.  It was never tested on Mac hardware.  It may or may not work on Mac computers.

The guide was successfully applied also on the following cards.

• NVS 4200M
• GeForce GT 640M
• GeForce 820M
• GeForce GTX 850M
• GeForce GTX 860M
• GeForce 920M
• GeForce 930M
• GeForce 940M
• GeForce 940MX
• GeForce GTX 960M
• GeForce GTX 970M

Uninstall Bumblebee

Bumblebee and proprietary Nvidia driver may be removed from Arch and EndeavourOS.Stop running bumblebee service:

sudo systemctl stop bumblebeed

Disable bumblebee service from being started on subsequent boot-ups:

sudo systemctl disable bumblebeed

Delete all users from bumblebee group. If only the current user was added to it, he may be removed with

sudo gpasswd --delete $USER bumblebee

When all users have been removed from bumblebee group, the group may be deleted

sudo groupdel bumblebee

Remove all packages that were installed for Bumblebee and Nvidia, and their dependencies

sudo pacman -Rcnsu bumblebee nvidia lib32-nvidia-utils lib32-virtualgl nvidia-settings bbswitch --noconfirm

(Optional) Re-install xf86-video-intel driver without unneeded Bumblebee dependencies

sudo pacman -Syu xf86-video-intel --noconfirm

Regenrate initramfs running Dracut (default on EndeavourOS):

With systemd-boot in use:

sudo reinstall-kernels

Running Grub as Bootloader:

sudo dracut-rebuild

(Regenerate initramfs (if using mkinitcpio)

sudo mkinitcpio --preset linux

Shutdown the system

sudo shutdown -h now

Done

All Nvidia entries: https://discovery.endeavouros.com/?s=nvidia

]]> 1043 0 31 0 https://discovery.endeavouros.com/hardware/optimus-manager-for-nvidia/2021/03/ Tue, 09 Mar 2021 13:09:24 +0000 https://discovery.endeavouros.com/?p=1045

Optimus-Manager for Nvidia

[for nvidia-latest driver and newer systems supported by that driver]

[icon name="info" prefix="fas"]

The state of optimus-manager

If you have a newer Nvidia-Intel hybrid Notebook, or also AMD-Nvidia combination:

You can simply switch the intel and NVidia GPU with optimus-manager tool.

For this you will need the proprietary NVidia driver installed.

Boot LiveISO and install EndeavourOS with optimus device.

—> go to step 4. if you already installed system and Nvidia Drivers:

1. Boot on the NVidia boot option
2. Install system of your choice (NVidia drivers will be installed automatically)
3. Boot into your newly installed system
4. install optimus-manager:

yay -S optimus-manager

Install optimus-manager-qt what is working on top of optimus-manager to get a tray icon to switch:

yay -S optimus-manager-qt

If you have a combo if AMD and Nvidia, you need currently the git version to support AMD GPU’s:

yay -S optimus-manager-qt-git

And if you want to use it under KDE/Plasma it is recommended to build with _plasma=true to set inside the PKGBUILD:

https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=optimus-manager-qt-git

That makes it needed to build manually with makepkg or have an AUR-Helper that can handle editing PKGBUILD before building.

If choosing to manually build:

git clone https://aur.archlinux.org/optimus-manager-qt-git
then open the folder optimus-manager-qt-git with filebrowser open the file PKGBUILD with Texteditor and change false to true here:

# Use KDE API features (recommended for Plasma users)

_with_plasma=true

save the file.
open a terminal inside the same folder (optimus-manager-qt-git) and run makepkg:
makepkg -si

This is the manual way to build and install packages from AUR.

5. reboot system
6. check optimus manager service (should be running)

systemctl status optimus-manager

To start and enable it run (if it is not running):

sudo systemctl enable --now optimus-manager

7. Now switch to Nvidia GPU, right-click on the Tray and select “Switch to Nvidia“

On KDE/Plasma it will look like this:

8. You can switch manually with commands also:

You can also use it without tray icon:

Run from terminal:

optimus-manager --switch nvidia
to switch to the Nvidia GPU
optimus-manager --switch integrated
to switch to the integrated GPU and power the Nvidia GPU off
optimus-manager --switch hybrid
to switch to the iGPU but leave the Nvidia GPU available for on-demand offloading, similar to how Optimus works on Windows.

See the Wiki 1 at the source of it at GitHub for more details.

---

Warning:

• be careful with the packages “acpi_call” and “bbswitch“.
  they will make the system unstable or it will not boot anymore.

• optimus-manager will only work on Xorg (X11) session not on Wayland.
• If you are running Gnome with GDM you need to install gdm-prime.

For more information read at the source for optimus-manager:

https://github.com/Askannz/optimus-manager

https://github.com/Shatur95/optimus-manager-qt

https://youtu.be/OlIXQRpfJQ4

All Nvidia entries: https://discovery.endeavouros.com/?s=nvidia

]]> 1045 0 30 0 https://discovery.endeavouros.com/network/firewall/2021/03/ Thu, 11 Mar 2021 10:53:59 +0000 https://discovery.endeavouros.com/?p=1081

By Bryanpwo

You can simply install GUFW, which stands for Graphical Uncomplicated Firewall. It is a personal firewall with a graphical settings menu that is easy to use.

[icon name="info" prefix="fas"]

It is recommended to not use UFW anymore nowadays firewalld is a way more versatile tool to manage your security. See here on how to use and set it up:

https://discovery.endeavouros.com/news/firewalld/2022/03/

Make sure your system is up to date before installing it. So just enter

sudo pacman -Syu

to make sure it is updated, then install needed packages :

sudo pacman -S gufw

Even though we provide the graphical settings app for UFW, I will show you the command line settings to help you understand UFW better.

You can put these settings in the graphical app also.

After installation UFW isn’t enabled by default, so the first step is to enable the firewall with this command:

sudo systemctl start ufw.service

Now you’ve enabled the firewall for this session. I’m going to give you some basic settings.

UFW and in general all firewall tools use “rules” to enable or disable package arrive/receive to any computer.so by default, you must allow any outgoing traffic to be streamed and reject any incoming traffic by:

sudo ufw default allow outgoing
sudo ufw default deny incoming

Adding rules

Rules can be added in two ways: By denoting the port number or by using the service name.

For example, to allow both incoming and outgoing connections on port 22 for SSH, you can run:

sudo ufw allow ssh

or:

sudo ufw allow 22

and these are other samples:

sudo ufw allow 80/tcp
sudo ufw allow http/tcp
sudo ufw allow 1725/udp
sudo ufw allow 1725/udp
sudo ufw allow from 123.45.67.89/24
sudo ufw allow from 123.45.67.89 to any port 22 proto tcp

Removing rules

To remove a rule, add delete before the rule implementation. If you no longer wish to allow HTTP traffic, you could run:

sudo ufw delete allow 22

You can check the status of UFW at any time with the command: sudo ufw status. This will show a list of all rules, and whether or not UFW is active:

Status: active

To                         Action      From
--                         ------      ----
22                         ALLOW       Anywhere
80/tcp                     ALLOW       Anywhere
443                        ALLOW       Anywhere
22 (v6)                    ALLOW       Anywhere (v6)
80/tcp (v6)                ALLOW       Anywhere (v6)
443 (v6)                   ALLOW       Anywhere (v6)

Now you’re almost ready, the last step you have to do is to enable firewall with every boot by typing this command:

sudo systemctl enable ufw.service

GUI interface

If you prefer a GUI interface for your settings you can use the graphical app GUFW which only needs to get installed:

sudo pacman -S gufw

and enable the firewall service:

systemctl enable --now ufw.service

This will enable and start the needed firewall service.

Now you can start the GUI and start or stop the firewall on your needs:

]]> 1081 0 26 0 FirewallD]]> FirewallD]]> https://discovery.endeavouros.com/network/r8168-workaround/2021/03/ Thu, 11 Mar 2021 10:58:17 +0000 https://discovery.endeavouros.com/?p=1084

By Manuel

Realtek 8168 Ethernet card gets r8169 kernel module by default. There is another kernel module package, r8168, for situations where r8169 does not work properly.

To check which of these is in use, the following command should show it:

lsmod | grep r816

To use r8168, install package r8168 and reboot.

To use r8169, uninstall package r8168 and reboot.

]]> 1084 0 25 0 https://discovery.endeavouros.com/installation/get-broadcom-working-on-an-installed-system-and-on-live-usb/2021/03/ Thu, 11 Mar 2021 11:02:24 +0000 https://discovery.endeavouros.com/?p=1086

_{By community member Archy}

This method pretty much works with all arch distros for those individuals unfortunate enough to choose computers that include Broadcom wifi.
First, since 5x kernel’s , some arch distros that previously needed wifi installed post os-install, seem to work without doing so. I’m not sure which one’s.

Procedure:
BEFORE installing or trying live usb of an arch distro!
(rolling release, so that means minutes before)

1. go to /www.archlinux.org/packages/
2. download latest linux-headers package onto usb separate from iso.
3. download latest dkms package onto usb separate from iso.
4. download latest broadcom-wl-dkms onto usb separate from iso.

Reboot into live USB ISO or perform install of arch distro (Endeavour OS)

1. with your driver USB files inserted either cd to or enter path to drivers in following commands in order listed.
2. sudo pacman -U dkms
3. sudo pacman -U linux-headers
4. sudo pacman -U broadcom
5. sudo modprobe wl
6. sudo depmod -a
7. Wait a few moments then connect to your wifi network if live USB.
8. If a new install, wait a minute if the system doesn’t find wifi network within 5 minutes reboot to a working wifi connection.

]]> 1086 0 24 0 https://discovery.endeavouros.com/hardware/envy-control/2023/03/ Tue, 14 Mar 2023 11:58:13 +0000 https://discovery.endeavouros.com/?p=3994

Envy Control

EnvyControl is a CLI tool that provides an easy way to switch between GPU modes on Nvidia Optimus systems (i.e laptops with hybrid Intel + Nvidia or AMD + Nvidia graphics configurations) under Linux.

https://github.com/bayasdev/envycontrol

Features

• Written in Python 3+ for portability and compatibility
• Supports GDM, SDDM and LightDM display managers
• Save battery with integrated graphics mode
• PCI-Express Runtime D3 (RTD3) Power Management support for Turing and later
• Coolbits support for GPU overclocking
• Fix screen tearing with ForceCompositionPipeline
• works for both dracut and mkinitcpio

The tool offers 3 Graphics modes:

Integrated: The integrated Intel or AMD iGPU is used exclusively

Hybrid: Enables PRIME render offloading

Nvidia: The Nvidia dGPU is used exclusively

detailed info here: README.md#-graphics-modes

You will find an AUR PKGBUILD and can install it over yay:

yay -S envycontrol

to run it use this commandline and check the usage box for options (graphics modes):

sudo envycontrol -s <MODE>

Usage:

usage: envycontrol.py [-h] [-v] [-q] [-s MODE] [--dm DISPLAY_MANAGER] [--force-comp] [--coolbits [VALUE]] [--rtd3 [VALUE]] [--reset-sddm] [--reset] [--verbose]

options:
  -h, --help            show this help message and exit
  -v, --version         Output the current version
  -q, --query           Query the current graphics mode
  -s MODE, --switch MODE
                        Switch the graphics mode. Available choices: integrated, hybrid, nvidia
  --dm DISPLAY_MANAGER  Manually specify your Display Manager for Nvidia mode. Available choices: gdm, gdm3, sddm, lightdm
  --force-comp          Enable ForceCompositionPipeline on Nvidia mode
  --coolbits [VALUE]    Enable Coolbits on Nvidia mode. Default if specified: 28
  --rtd3 [VALUE]        Setup PCI-Express Runtime D3 (RTD3) Power Management on Hybrid mode. 
                    Available choices: 0, 1, 2, 3. Default if specified: 2
  --reset-sddm          Restore default Xsetup file
  --reset               Revert changes made by EnvyControl
  --verbose             Enable verbose mode

for detailed help and info on how to use this awesome tool read the detailed wiki at the source:

https://github.com/bayasdev/envycontrol/blob/main/README.md

EnvyControl Frequently-Asked-Questions have also a lot of good information.

Thank's @VictorBayas at the telegram chat to hint me on his helpful tool perfectly fitting for EndeavourOS indeed!

EnvyControl-PyQt:

https://github.com/MatveyM11/EnvyControl-PyQt

PyQt5 widget for the EnvyControl, program aimed to provide an easy way to switch GPU modes on Nvidia Optimus systems under Linux.
Widget supports both windowed and system tray mode.

]]> 3994 0 0 0 https://discovery.endeavouros.com/acpi-kernel-parameters/acpi-kernel-parameters-and-how-to-choose-them/2021/03/ Thu, 11 Mar 2021 11:50:17 +0000 https://discovery.endeavouros.com/?p=1095

ACPI Kernel Parameters and how to choose them

The introduction of Optimus laptops and other power-saving features have created new challenges for Linux users. Some of the issues include having the proprietary graphics card work when the system boots, improper CPU scaling, and general system instability. Many times the advice given is to add an Advanced Configuration and Power Interface (ACPI) kernel parameter to grub. While a specific ACPI kernel parameter may be given, it is sometimes not appropriate to the hardware it is being applied to. This can cause system instability and some functions of the laptop to not work properly. Once the user does find a parameter that works, they are told to add it to their grub config file so it will be automatically loaded at boot. This can cause its own problems. If the user does not use the proper syntax when adding this parameter, it will be ignored and not work. Let’s take a look at how to choose the proper ACPI kernel parameter and then how to properly add it to the grub config file.

Before you decide which ACPI kernel parameter you need, you have to ask yourself one question.

Do I even need an ACPI kernel parameter?

Short of digging through logs and looking for ACPI errors, there are several ways to see if an ACPI kernel parameter is needed.

1. This is probably the easiest way to tell if you need an ACPI kernel parameter. This problem can be seen whether you are running Linux from a Live USB or it is installed on a local hard drive. When you shut down your computer and it hangs before shutting down, or it hangs and you have to push the power button to shut it down, you may need an ACPI kernel parameter.

2. You are using an Optimus laptop and you have installed the Nvidia proprietary driver. You boot your laptop and it hangs on the following steps:

• “Started TLP system startup/shutdown”
• “reached target graphical interface”
• An error message about configuring “Backlight”
• Your laptop just boots to a black screen and the fans start to run constantly.

If any of these behaviors are noticed, you may need to add an ACPI kernel parameter.

3. This requires a little more effort on the user. Press “E” on the grub screen and remove the “quiet” kernel parameter before you boot your computer. As your computer boots, you will be presented with a list of what is being loaded. Before the kernel starts loading, it does a quick hardware check. If it has a problem with powering up any hardware, it will list an ACPI error. If you see an ACPI error, you may need an ACPI kernel parameter.

Choosing an ACPI kernel parameter.

The bios or UEFI in use by your laptop looks for certain “identifiers” in how to handle your hardware based on the Operating System (OS) it was designed to operate. It does this through ACPI “calls” from the operating system to the bios. When you see problems such as listed above, that means the bios does not understand the calls being sent to it by the OS. The good thing is since ACPI used by both Windows and Linux follow the UEFI specifications1, they both use the same OSI strings to identify what OS is used. Unlike the Windows kernel, the Linux kernel can determine what “power calls” are sent to the bios by the use of these OSI Strings in the ACPI kernel parameter. By adding these parameters, you can basically tell Linux to “mimic” the ACPI calls sent by another OS.

When you purchased your laptop, it probably came with Windows pre-installed. The version of Windows that was installed is your first clue in figuring out which OSI String your ACPI kernel parameter needs. From Windows 2000 to Windows 8.1, you can use the Windows release name to find the OSI String you should use. Windows 10, however, since it uses a “rolling-release” model, finding the OSI String you need to use requires a little more work. To find your Windows install version number, open a command prompt in Windows and type, winver. This will give your Windows version in the following manner, Windows 10 version 1607. That is the information you need to determine the OSI String your kernel parameter needs.

Once you have your version of Windows, use the below chart to find how your version of Windows needs to be represented in the kernel parameter.

OSI Arguments for Windows ²

OSI String	Target OS
Windows 2000	Windows 2000
Windows 2001	Windows XP
Windows 2001 SP1	Windows XP SP1
Windows 2001.1	Windows Server 2003
Windows 2001 SP2	Windows XP SP2
Windows 2001.1 SP1	Windows Server 2003 SP1
Windows 2006	Windows Vista
Windows 2006 SP1	Windows Vista SP1
Windows 2006.1	Windows Server 2008
Windows 2009	Windows 7, Win Server 2008 R2
Windows 2012	Windows 8, Win Server 2012
Windows 2013	Windows 8.1
Windows 2015	Windows 10
Windows 2016	Windows 10, version 1607
Windows 2017	Windows 10, version 1703
Windows 2017.2	Windows 10, version 1709
Windows 2018	Windows 10, version 1803
Windows 2018.2	Windows 10, version 1809
Windows 2019	Windows 10, version 1903
Windows 2020	Windows 10, version 2004

Once you have your OSI string, you now have all the information needed for your kernel parameter.

To have Linux mimic your version of Windows, you need to add the following kernel parameter, acpi_osi='OSI String'³

Examples

Windows 7 – acpi_osi='Windows 2009'

Windows 10 ver. 1709 – acpi_osi='Windows 2017'

You will notice that Windows 10 version 1709 has an OSI String of Windows 2017.2 and I used Windows 2017 instead. In my testing, I found that Windows 2017.2 was not recognized as a valid argument.

Note on acpi_osi=!

This argument disables all vendor strings that may be present. It should only be used if one of the above OSI strings does not work on its own. If you use it when it is not needed, you may be able to boot without any ACPI errors, but your touchpad or wifi will not work. It also must be used in combination with one of the above OSI strings.

Example

acpi_osi=! acpi_osi='Windows 2012'

This will disable all the vendor strings and then tell the kernel to “mimic” Windows 8 when it talks to the BIOS.

Note for Dell Laptops

Sometimes the above kernel parameters will not work properly on some Dell laptops. If that is the case, you can try the following: acpi_rev_override=# replace the “#” with a number between 1 to 5. In order to have this kernel parameter applied properly, cold booting (shutting your system down completely before restarting) your laptop twice may be required.

Testing your ACPI kernel parameter

1. Press “E” on the grub screen and find the line with the “quiet” parameter.
2. Replace the word “quiet” with the parameter you have determined you need.
3. Press F-10 to boot your computer.

Adding the ACPI kernel to grub

Once you have found the kernel argument that works the best for your hardware, you need to add it to grub in order to have it applied every time you boot your system. This is easier than it sounds. The problem most users have is a syntax or how to type it on the appropriate line. The key to having the argument recognized is to only use “single quotes”, or as we call them in the United States, the apostrophe. To add the argument to grub, open a terminal and type the following:

1. sudo nano /etc/default/grub
2. Add the kernel argument to the following line: GRUB_CMDLINE_LINUX_DEFAULT .

Example

GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi='Windows 2018' rd.udev.log-priority=3 nvme_core.default_ps_max_latency_us=5500"

3. ctrl+x to exit and “Y” to save.
4. sudo update-grub or if you do not have update-grub installed from the AUR, run sudo grub-mkconfig -o /boot/grub/grub.cfg

Now your kernel argument has been added to grub and will be loaded every time you boot your laptop.

This is by no means an exhaustive guide in the use of ACPI kernel parameters. That would require a much longer document. Instead, it gives some basic instructions that one can follow to get their system up and running. If you are still having ACPI issues, and need help solving them, there are a couple of options open to you. First off, search the forum to see if your problem has been solved before. If that does not solve your issue, create a new support thread on the forum discussing your issue.

Additional Notes

I will use this section for minor updates and additional information.

The kernel parameter apci_osi=Linux can be used in newer (late 2019 and later) Asus laptops to fix an issue where the external HDMI port is not working. Use this one instead of a Windows related parameter.

Sources

¹ https://uefi.org/specifications

² https://docs.microsoft.com/en-us/windows-hardware/drivers/acpi/winacpi-osi

³ https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt

]]> 1095 0 21 0 https://discovery.endeavouros.com/hardware/tools-to-lower-power-consumption-and-device-cooling/2021/03/ Thu, 11 Mar 2021 12:15:04 +0000 https://discovery.endeavouros.com/?p=1101

Tools to lower power consumption and device cooling

• CPU frequency scaling and battery optimization for Notebook and PC systems

Since the Atlantis release, in December 2021, every new install has power-profile-daemon installed by default.

Why power-profiles-daemon

The power-profiles-daemon project was created to help provide a solution for two separate use cases, for desktops, laptops, and other devices running a “traditional Linux desktop”.

The first one is a "Low Power" mode, that users could toggle themselves, or have the system toggle for them, with the intent to save battery. Mobile devices running iOS and Android have had a similar feature available to end-users and application developers alike.

The second use case was to allow a "Performance" mode on systems where the hardware maker would provide and design such a mode. The idea is that the Linux kernel would provide a way to access this mode which usually only exists as a configuration option in some machines' "UEFI Setup" screen.

This second use case is the reason why we didn't implement the "Low Power" mode in UPower, as was originally discussed.

As the daemon would change kernel settings, we would need to run it as root, and make its API available over D-Bus, as has been customary for more than 10 years. We would also design that API to be as easily usable to build graphical interfaces as possible.

Introduction

power-profiles-daemon offers to modify system behaviour based upon user-selected power profiles. There are 3 different power profiles, a "balanced" default mode, a "power-saver" mode, as well as a "performance" mode. The first 2 of those are available on every system. The "performance" mode is only available on select systems and is implemented by different "drivers" based on the system or systems it targets.

In addition to those 2 or 3 modes (depending on the system), "actions" can be hooked up to change the behaviour of a particular device. For example, this can be used to disable the fast charging for some USB devices when in power-saver mode.

GNOME's Settings and shell both include interfaces to select the current mode, but they are also expected to adjust the behaviour of the desktop depending on the mode, such as turning the screen off after inaction more aggressively when in power-saver mode.

How to use

There are interfaces to switch profiles in the latest versions of KDE and GNOME. Those desktops also include more thorough integration with its low-power mode. Please check the user guides for each of them for details.

power-profiles-daemon also ships with a command-line utility called powerprofilesctl which can be used for scripting, as it allows getting and setting the active profile, listing the available profiles, and launching commands while holding the performance or the power-saver profile.

For example, this will be useful to avoid manual switching profiles while compiling large projects:

powerprofilesctl launch make

If you're a developer, you might also want to use GLib's GPowerProfileMonitor through C or one of its bindings, so your application can react to the user requesting a low-power mode.

Debugging

You can now check which mode is in use, and which ones are available by running:

powerprofilesctl get

You can change the selected profile by running (change power-saver for the chosen profile):

powerprofilesctl set power-saver

You can check the current configuration which will be restored on reboot in /var/lib/power-profiles-daemon/state.ini.

Those commands are also available through the D-Bus interface:

gdbus introspect --system --dest net.hadess.PowerProfiles --object-path /net/hadess/PowerProfiles
gdbus call --system --dest net.hadess.PowerProfiles --object-path /net/hadess/PowerProfiles --method org.freedesktop.DBus.Properties.Set 'net.hadess.PowerProfiles' 'ActiveProfile' "<'power-saver'>"

If that doesn't work, please file an issue, attach the output of:

sudo G_MESSAGES_DEBUG=all /usr/libexec/power-profiles-daemon -r -v

Testing

If you don't have hardware that can support the performance mode or the degraded mode you can manually run the power-profiles-daemon binary as root with the environment variable POWER_PROFILE_DAEMON_FAKE_DRIVER set to 1. For example:

sudo POWER_PROFILE_DAEMON_FAKE_DRIVER=1 /usr/libexec/power-profiles-daemon -r -v

power-profiles-daemon source text and more info over here.

Thermald

is a Linux daemon used to prevent the overheating of platforms? This daemon monitors temperature and applies compensation using available cooling methods.

By default, it monitors Intel CPU temperature using available CPU digital temperature sensors and maintains CPU temperature under control, before HW takes aggressive correction action. If there is a skin temperature sensor in thermal sysfs, then it tries to keep skin temperature under 45C.

Source: https://wiki.archlinux.org

Code Source:

https://01.org/linux-thermal-daemon/documentation/introduction-thermal-daemon

https://github.com/intel/thermal_daemon

As each update of the thermald-package will overwrite the service file we need to move this to

/etc/systemd/system/

So that it will not stop working after thermald updates.

install needed:

sudo pacman -S --needed thermald

sudo cp /usr/lib/systemd/system/thermald.service /etc/systemd/system/
sudo nano /etc/systemd/system/thermald.service

change the line:

ExecStart=/usr/bin/thermald --systemd --dbus-enable --adaptive

like so:

ExecStart=/usr/bin/thermald --systemd --dbus-enable --adaptive --ignore-cpuid-check

save the file by pressing [Ctrl+Alt+x] and confirm by typing “y”

The last two things to do is enable the systemd service for Thermald to automatic start it on every boot of your system:

sudo systemctl enable thermald

and now please reboot the system to make it start working.

As EndeavourOS is installing power-profiles-daemon per default you will need to mask its service or uninstall it.

sudo systemctl mask power-profiles-daemon

It will need some time to measure and then really control to hold the temperature down, so be patient and wait to see the effect for some time ( may need one or two hours before working for the first time)

Alternative to thermald (auto-cpufreq)

https://github.com/AdnanHodzic/auto-cpufreq

Not available on the official repository, so it needs to be built from AUR:

https://aur.archlinux.org/packages/auto-cpufreq-git/

yay -S auto-cpufreq-git

On how to enable and use this read the documentation on GitHub:

https://github.com/AdnanHodzic/auto-cpufreq#aur-package-archmanjaro-linux

Cpupower

is a set of userspace utilities designed to assist with CPU frequency scaling.

full list of available modules:

sudo ls /usr/lib/modules/$(uname -r)/kernel/drivers/cpufreq/

Load the appropriate module (see Kernel modules for details). Once the appropriate cpufreq driver is loaded, detailed information about the CPU(s) can be displayed by running

sudo cpupower frequency-info

Scaling governors

Governors (see table below) are power schemes for the CPU. Only one may be active at a time. For details, see the kernel documentation in the kernel source.

NOTE: If you want to use this method, make sure you disable CPU-scaling from TLP (as this is enabled by default on EndeavourOS and using both together for the same mechanism will cause failure)

Governor	Description
performance	Run the CPU at the maximum frequency.
powersave	Run the CPU at the minimum frequency.
userspace	Run the CPU at user-specified frequencies.
OnDemand	Scales the frequency dynamically according to the current load. Jumps to the highest frequency and then possibly back off as the idle time increases.
conservative	Scales the frequency dynamically according to the current load. Scales the frequency more gradually than onDemand.
schedutil ………………………..	Scheduler-driven CPU frequency selection [1], [2].

set one for all cores:
(replace governor with e.g. what you want ondemand p.e…)

sudo echo *governor* > /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor

see live output:

watch grep \"cpu MHz\" /proc/cpuinfo

making one permanent:

sudo systemctl enable cpupower.service

]]> 1101 0 19 0 https://discovery.endeavouros.com/storage-and-partitions/adding-swap-after-installation/2021/03/ Thu, 11 Mar 2021 12:18:04 +0000 https://discovery.endeavouros.com/?p=1103

Adding swap after installation

_{by Bryanpwo edited by joekamprad (12.08.2020) + (24.02.2021) + (28.09.2023) + (09.09.2025)}

To add after installation there are two options:

1. creating a swap partition by shrinking space and adding a partition using Gparted on the Live ISO

2. creating a swap file.

[icon name="info" prefix="fas"]

Early SSDs had a reputation for failing after fewer writes than HDDs.

This might be why you heard it could be bad to use an SSD for swap.

Modern SSDs don't have this issue

Making a swap partition with Gparted

Boot your machine with the Live ISO and open Gparted. Select the last partition on your HDD (this can either be the Root partition or the Home partition, depending on how you partitioned your disk) and shrink the partition by leaving a disk space free equal to the size of your RAM or double the size, that’s up to you. Then select the free space and mark it as a swap partition, let Gparted do its work, and boot back into your installed system and swap should be recognized by systemd. To check enter:

swapon --show

Making a swap file

The above method is the easiest one, but it can damage the partition that you’ve shrunk. So you can also make a swap file.

Commands like cp(1) or truncate(1) create files with holes. These files will be rejected by swapon.

Preallocated files created by fallocate(1) may be interpreted as files with holes too depending of the filesystem.

As documented here: swapon.8#Files_with_holes

So as Archwiki recommends better use dd command with some danger of using a Destroyer of Disks.

!! This following step is only needed if you run on Btrfs filesystem !!

_{Notes if you are using Btrfs}

Note: Swap files on file systems spanning multiple devices are not supported. See btrfs(5) § SWAPFILE SUPPORT for all limitations.

To properly initialize a swap file, first create a non-snapshotted subvolume to host the file, e.g.

sudo btrfs subvolume create /swap

Tip: Consider creating the subvolume directly below the top-level subvolume, e.g. @swap. Then, make sure the subvolume is mounted to /swap (or any other accessible location).

Create the swap file:

sudo btrfs filesystem mkswapfile --size 8g --uuid clear /swap/swapfile

If --size is omitted, the default of 2GiB is used.

Further for all file systems:

Use mkswap to create a swap file the size of your choosing. For example, creating a 8 GiB swap file:

sudo mkswap -U clear --size 8G --file /swapfile

To make the file as swap space and finally to enable the file:

sudo swapon /swapfile

Edit the fstab configuration to add an entry for the swap file:

/etc/fstab

/swapfile none swap defaults 0 0

Note: The swap file must be specified by its location on the file system, not by its UUID or LABEL.

to check:

swapon --show

Remove swap file:

To remove a swap file, it must be turned off first and then can be removed:

sudo swapoff /swapfile
sudo rm -f /swapfile

Finally, remove the relevant entry from /etc/fstab.

For more details about swap usage in general and options:

https://wiki.archlinux.org/title/Swap

Swappiness: https://wiki.archlinux.org/title/Swap#Swappiness

zswap: https://wiki.archlinux.org/title/Zswap

zram: https://wiki.archlinux.org/title/Zram

]]> 1103 0 18 0 https://discovery.endeavouros.com/storage-and-partitions/periodic-trim/2021/03/ Thu, 11 Mar 2021 12:25:20 +0000 https://discovery.endeavouros.com/?p=1107

Set-up Periodic TRIM

[Source: Periodic_TRIM]

Warning: Users need to be certain that their SSD supports TRIM before attempting to use it. Data loss can occur otherwise!

check if your drive support it:

sudo hdparm -I /dev/sdx | grep TRIM 

(change to the drive letter (x) you want to check)

make sure util-linux is installed:

sudo pacman -S util-linux hdparm --needed

check what you have already running:

cat /etc/fstab

if your drive shows like this:

/dev/sda1 / ext4 defaults,discard 0 1

continous TRIM is enabled! what in my opinion is bad to use as it will put system under continous load…

enable periodic TRIM:

remove discard option from your device inside fstab that it looks like this:

/dev/sda1 / ext4 defaults 0 1

Starting the scheduler to trim device/s once a week::

sudo systemctl start fstrim.timer

sudo systemctl enable fstrim.timer

to check if it works see:

systemctl status fstrim.timer

---

]]> 1107 0 16 0 https://discovery.endeavouros.com/audio/getting-information-while-having-sound-issues/2021/03/ Fri, 12 Mar 2021 18:37:18 +0000 https://discovery.endeavouros.com/?p=1160

Getting information while having sound issues

_{by <joekamprad>}

Sometimes it is a puzzle to get around with a new soundcard, or getting a mix to work, I give some hints on getting information about devices and system here:

First check if alsamixer is enabled so you can use it as a simple source to solve most mute problems, and get a view of what is available:

https://youtu.be/LAspViAl9Hs

Pipewire is used by default but it still lags of tools, but most pulseaudio tools will work.

Pavucontrol and mainly the Configuration tab, can resolve most of the common issues with audio:

Some other tools:

• GTK GUIs: paprefs, pavucontrol and helvum

• KDE plasma applet: kmix, plasma-pa and qpwgraph
• Xfce4 plugin: xfce4-pulseaudio-plugin, pa-applet-git

Configs are here: ~/.config/pulse ~/.local/state/wireplumber ~/.local/state/pipewire and can easily reset by removing the files and log in again in the DE (rm -R ~/.config/pulse ~/.local/state/wireplumber ~/.local/state/pipewire) as a normal user.

Auto-Mute:

If the Mode is enabled, it can cause problems for multiple users:

It can be disabled by using alsamixer.

See http://superuser.com/questions/431079/how-to-disable-auto-mute-mode for more.

pacmd list-sinks

will show info about connected output-input-devices

Some more tools:

wget http://www.alsa-project.org/alsa-info.sh && sh alsa-info.sh

will give you advanced info about the Soundcards + system and outputs an URL where the info is posted.

pactl list sinks

Lists your active devices.

speaker-test -c 6

The number needs to be changed to your situation.

More info on pipewire:

https://discovery.endeavouros.com/audio/pipewire/2021/09

In case you are reverted to use Pulseaudio:

https://discovery.endeavouros.com/audio/pulseaudio/2021/12

And indeed check the Archwiki:

https://wiki.archlinux.org/title/PipeWire

]]> 1160 0 13 0 Pipewire]]> Pulseaudio]]> Pipewire]]> Pulseaudio]]> https://discovery.endeavouros.com/grub-and-refind/how-to-install-refind/2021/03/ Fri, 12 Mar 2021 18:45:16 +0000 https://discovery.endeavouros.com/?p=1162

_{by Freebird54
Added: 2020-Mar-28
Updated: 2020-Apr-09
Updated: 2020-Jul-25: Fixed some slashes to backslashes.}

_{Updated: 2021-Jun-14: Clarified some additional options} .

rEFInd is a boot manager, forked and reworked from the EFI boot control program called rEFIt. It allows the easy control of multi-boot systems, regardless of what those systems might be.

Note: It will simplify your life, and the setup, if SECURE BOOT (and FAST boot if present) have been disabled in your UEFI BIOS.

These are the steps you need to install it:

1. Install the Program

yay refind

It will probably show you several packages – number 1 from the extras repository should be your choice. It may even already be installed. After it has been installed,

2. run the install script

refind-install

The chances are excellent that you now have already the capability to boot with rEFInd in control. If you try it right away, you will most likely see 2 entries for each bootable system on your computer. If you have only 2, for instance Ubuntu and EndeavourOS, there should be 4 choices on the screen. If you see a lot more than that, did you remember to remove the USB stick you installed from? Reset and try without the stick plugged in! OK, you’re back (or never left). As you use the arrow keys to highlight each of your choices, you will notice that a description of the file that will be booted shows up underneath the row of logos. One entry for each will be for grubx64.efi and the other will be similar to the vmlinuz-linux as EndeavourOS uses. Either icon will work. There are other easy things you can do to simplify, or beautify it from here.

• Give it a customized logo to display for EndeavourOS
• Hide the alternative boot choices you won’t be using
• Add special boot options (such as microcode and kernel options) to direct boot

3. Customize your displayed logo (optional)

Because EndeavourOS is relatively new, the displayed logo for your system is likely to be Tux – the Linux penguin. If you would rather have the EndeavourOS logo, then you need to have a copy of it. You can easily find it as EndeavourOS-icon.png in /usr/share/endeavouros. Copy it into place with the following:

sudo cp /usr/share/endeavouros/EndeavourOS-icon.png /boot/efi/EFI/refind/icons/os_endeavourOS.png

When that has been done, the icon you copied will be shown with each of the EnOS choices that rEFInd recognizes.

There are other ways to accomplish this (you can even have different logos for different setups of one OS!), but this method is pretty much automatic from here.

4. Hide the extra entries (optional)

If you want to simplify your visible boot options, you should decide which method of booting suits you better – either by starting up the grub system that was created on the original installation (or by subsequent updates) or by directly booting the OS. As you highlight each choice, under it is a description of the boot file it will use. If it says the file to boot will be \EFI\endeavouros\grub64.efi, it will select and boot the grub entry, from which you can choose the item you wish. If it says that it will boot from \boot\vmlinuz-linux, it will do a direct boot. Highlight the item of your choice that you wisk to hide, and hit the DELETE key and it won’t be seen again. To UNhide an entry if you change your mind, choose the recycle tool (Manage Hidden Tags menu) on the lower line.

5. Add special boot options (optional) to direct boot

To do this you will need to edit some configuration files. In this case, I will describe setting up the booting with the microcode for your processor. First thing to edit is the refind.conf file. This is usually found (at least on EndeavourOS) in the /boot/efi/EFI/refind directory. You will need to locate the line containing extra_kernel_version_strings and uncomment it. Then edit it to match:

extra_kernel_version_strings linux-hardened,linux-zen,linux-lts,linux

Save and Exit. These are the most commonly used alternate kernels in use on Arch systems. This will allow rEFInd to support correctly the naming scheme that Arch and EndeavourOS use for kernels and their matching initramfs images. This will be made use of in the refind_linux.conf file, that should be located in the same place as your kernel. When refind-install ran, it probably set up a copy of this file in the correct place, leaving you only to do some editing. If not, there should be copy of an example file found as /usr/share/refind/refind_linux-sample.conf. Alternatively, running

sudo mkrlconf

in /boot will create one for you. It will still need editing. I will assume that you have already obtained your copy of the appropriate microcode image file if you have an Intel or AMD processor – intel-ucode.img or amd-ucode.img (install using yay if not). If you are working from a generated copy (rather than the sample) refind_linux.conf, it will already contain the identifiers for your boot UUID. If not, then you will need to see what the UUID is - using SUDO blkid is one easy way. Edit the refind_linux.conf to match this example for an amd-ucode.img system:

"Boot using default options"     "root=UUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX rw add_efi_memmap initrd=\boot\amd-ucode.img initrd=\boot\initramfs-%v.img"
"Boot using fallback initramfs"  "root=UUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX rw add_efi_memmap initrd=\boot\amd-ucode.img initrd=\boot\initramfs-%v-fallback.img"
"Boot to terminal"               "root=UUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX rw add_efi_memmap initrd=\boot\amd-ucode.img initrd=\boot\initramfs-%v.img systemd.unit=multi-user.target"

Notice that the directory character is \ rather than / – that is the standard in UEFI. Yes, I think Microsoft had a large say in setting the standards.

You could add kernel parameters inline on each item, such asquiet, after rw, if you don’t want to see the boot messages, but I like to know what happened in the background, so I didn’t add it here.

That should do it. One of the advantages of rEFInd is that you should only need to do this once, and that even the fallback option will include your microcode – unlike even ‘official’ grub2 entries. This means you do not need to go into your /boot/grub/grub.cfg file and add in the initrd entry for loading microcode, especially you do not need to do it again with every kernel update!

Notes / Troubleshooting:

There are a LOT of other capabilities of rEFInd that I haven’t touched on here. Everything about its appearance and theming can be changed, for example. An example shown in the documentation puts your contact information on the boot screen, should you be running a laptop and want to make it easy for a 'finder' to return it if lost etc. Many other things are built in for handling special cases as well. On top of that, there are other ways of achieving the same things we have set up here, but I think these are the easiest I’ve found so far. I find it the simplest way to run a machine with 5 distros on it!

One of the things I appreciate is that it can pick up and display boot options for USB sticks that have ISO’s on them – whether you are distro hopping, or just needing a live environment for troubleshooting. No need to enter the BIOS for that!

One problem, however, that you may run into is what the program’s author calls a ‘boot coup’, where the installation procedure or a change that causes grub to be updated (in any of your distros) can include a routine that replaces rEFInd as the boot manager run first in the BIOS NVRAM boot order. This can be repaired by efibootmgr – or even more easily in many BIOS setups by going into the BIOS and reselecting rEFInd as the first boot method in the list in NVRAM. It certainly simplifies keeping things separate and up-to-date on a system like mine with all those distros on it!

More can be found in the Arch Wiki under rEFInd and microcode – and of course, the most comprehensive information available, direct from the original source of it all:

https://www.rodsbooks.com/refind/

Case Studies

https://github.com/endeavouros-team/User-contributions/blob/master/Freebird54/wiki-pt2.md

https://github.com/endeavouros-team/User-contributions/blob/master/manuel/rEFInd/rEFInd-use-case.md

]]> 1162 0 12 0 https://discovery.endeavouros.com/system-rescue/grub-how-to-fix-booting-of-other-arch-based-systems/2021/03/ Fri, 12 Mar 2021 18:47:56 +0000 https://discovery.endeavouros.com/?p=1164

_{By: Manuel
Date: 2020-Jan-03
Updated: 2020-Mar-21
Updated: 2022-Nov-09}

Fixing a grub & os-prober issue

This article deals with the situation where there are other Arch based operating systems already installed onto a machine, and EndeavourOS is then installed to that machine.

There is a long-standing and annoying issue with co-operation between packages grub and os-prober. The generated /boot/grub/grub.cfg file fails to boot some Arch based operating systems!

The reason for the issue is how grub-mkconfig command generates the initrd lines into /boot/grub/grub.cfg. On Arch based systems there may be more parameters for the initrd line than simply the initramfs image: especially the microcode image. And that is not generated properly along with the initramfs image.

For example, when using a microcode image, this kind of initrd line should be generated by grub-mkconfig:

initrd /boot/intel-ucode.img /boot/initramfs-linux.img

but instead, this is generated:

initrd /boot/intel-ucode.img

And that particular boot menu entry, or course, fails to boot.

This problem can be fixed manually by adding the missing entry or entries to the initrd line, as shown above.

At next reboot the menu entries should work as expected.

A more permanent workaround for the problematic menu entries is to manually copy them from file /boot/grub/grub.cfg into file /boot/grub/custom.cfg after fixing them like above. Note that a menu entry consists of one or more lines. A menu entry starts with a word menuentry and stops with the closing } character for that menu entry.

Entries in custom.cfg will not be overwritten by a later call to grub-mkconfig.

More info about grub menu entries: https://www.gnu.org/software/grub/manual/grub/grub.html

]]> 1164 0 11 0 https://discovery.endeavouros.com/encrypted-installation/encrypted-installation/2021/03/ Fri, 12 Mar 2021 18:56:54 +0000 https://discovery.endeavouros.com/?p=1170

_{by anonym :)}

Install EndeavourOS with disk-encryption and swapfile, as the only OS on a Notebook/Laptop (mobile used systems) or on your Desktop.

If you want to create a dual-boot first get knowledge on how to do this!

This tutorial is for installing EndeavourOS as the only OS on the device.

Boot the Live ISO

Following the installer and choose what you want as the Desktop and for the Bootloader in the same way you would follow the installer for unencrypted installs. The only step you need to change is to enable encryption on the partition screen:

Enable (check) Encrypt System and give the passphrase you want to use (second one to validate).

Click Next and follow the other settings as usual. you will see the LUKS marking on the partition that shows encryption is used.

If using the systemd-boot method this is how the unlock prompt will show up:

Enter your encryption passphrase and hit enter to unlock the encryption and proceed to boot into your newly installed OS.

]]> 1170 0 10 0 https://discovery.endeavouros.com/applications/installing-endeavouros-on-virtualbox/2021/03/ Sun, 14 Mar 2021 13:34:59 +0000 https://discovery.endeavouros.com/?p=1180

_{Big thanks to DevNul for writing this at the forum !}

Create a new machine with your favorite name, for example –> EndeavourOS
Machine Folder: as you like
Type: Linux
Version: Arch Linux (64-Bit)

Memory size: (minimum 2000MB, recommended 2500MB - 4000MB)
Hard Disk: “Create a virtual hard disk now”

Hit “Create”

File location: Where do you want to save your virtual machine? Be aware that you need enough space for the virtual hard drive.

File size: with about 15GB you’re good to go – depends on the plans for your virtual machine. Definitely enough for a little test-drive.

Hard disk file type: What you prefer, VDI is absolutely ok.

Storage on physical disk: Dynamically allocated (The virtual machine takes only the amount of space that is needed. Your chosen file size is the maximum.)

After the wizard, you have to change one or two settings. First, you click on [Optical Drive] Empty. Then you choose the downloaded EndeavourOS-ISO to mount it in the virtual optical drive.

If you plan to activate the 3D acceleration for the GPU (graphics card) you have to change the graphics controller to “VBoxSVGA”. And you want to maximize the “Video Memory” to 128MB.

Notes / Troubleshooting (currently VMSVGA is working fine!):

It helps to change display settings to use the older better implemented  VBoxVGA as controller device in the settings. But as VirtualBOX now give a Warning that you have wrong settings if you choose this and it seems that VMSVGA (what VirtualBox set as default on Linux guests) is still not working nicely with Arch-based Guests, it reverts to its default on leaving the settings window and you need to set it from the main overview of the Box:

It will set back sometimes so check if Graphic-Controller is set to VBoxSVGA before starting an ArchBox! from that screen you can also set Memory for Graphics bigger than 125 MB:

All steps for getting graphic controller working in a slideshow:

(Thanks to FLVAL for providing this here at the forum installing-endeavouros-on-virtualbox-6-1)

Setup to 256MB with scroller or button then click ok

First check the 3D inside your VM Name settings, and let whatever graphic controller you want then click OK.

Close the window settings and click as below directly on the name VMSVGA of your VM

Then a little window appears so change it for VboxSVGA and click OK.

Now the VboxSVGA with 3D checked keeps right.

Click on the 128Mo (could be another value) then a little window appears

Setup to 256Mo with scroller or button then click ok

First, check the 3D inside your VM Name settings, and let whatever graphic controller you want then click OK.

That’s it… time to start the virtual machine and try EndeavourOS.

]]> 1180 0 8 0 https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/ Sun, 14 Mar 2021 13:53:26 +0000 https://discovery.endeavouros.com/?p=1182

What NOT To Do

Some USB Writing utilities alter the labels of the partitions included in the ISO image. This causes the boot to fail. There are workarounds to fix the failure, but that is beyond the scope of this article. For best results, it is recommended that you NOT use these types of utilities to create your Live USB. Some of the more widely known utilities that fall into this category are:

• UNetbootin
• Linux Live USB Creator
• Universal USB Installer
• Live USB Creator

Get the latest ISO

https://endeavouros.com/latest-release/

Create Live USB From Linux

There are many methods of creating Live USB images using Linux. This article lists only some options. Recommendation is always to use copy as it is methods like dd. But Suse image writer and also rufus or ventoy are widely used for the EndeavourOS ISO.

The one and most done error is to not wait for the USB flash drive to get fully syncing the ISO file data in the process, this can in worse case take up to 10 minutes!

A common issue is with the legacy options on modern EFI systems being enabled. Make sure to set USB boot option to not be set to CSM / legacy Bios. Make sure you are booted ISO in EFI mode if your system is EFI and not over 10y old legacy Bios device!

On the Live Session check from terminal:

efibootmgr

this will show your EFI boot entries in case you are booted in EFI mode, if not it will show an error message:

Read here for more information:

https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/

Command Line

The dd command will almost always result in a working Live USB. Just change the paths to the correct paths for your system.

NOTE: The USB drive is specified as /dev/sdx and not /dev/sdxX. The most common path of a USB drive is /dev/sdb, BUT yours might be different depending on your system.

To view a list of all drives currently attached to your system, run this command:

sudo fdisk -l

Another command to show information about the drives:

lsblk -f

Note: the USB drive may not be mounted when writing an ISO to it! So make sure you unmount it first:

sudo umount /dev/sdX

To write the Live Install image to your USB, run the following command:

sudo dd bs=4M if=/path/to/endeavouros-x86_64.iso of=/dev/sdX conv=fsync oflag=direct status=progress

But indeed, Linux has possibilities without ending:

using cat (with progress)

su
cat /path/to/endeavouros-x86_64.iso | pv > /dev/sdX

or even cp:

su
cp /path/to/endeavouros-x86_64.iso /dev/sdX

And exactly tee can do it too:

su
tee < /path/to/endeavouros-x86_64.iso > /dev/sdX

But keep in mind and check your command 3 times before executing, as putting something wrong will possibly destroy personal data!

GUI’S

All GUI writers can be installed using yay -Syu packagename as mentioned below:

---

Suse Image Writer

Available in the AUR as imagewriter

---

Popsicle

Popsicle is a Linux utility for flashing multiple USB devices in parallel, written in Rust.

And known to work nicely for EndeavourOS ISO.

Available as popsicle-bin from the AUR

---

GNOME Disk Utility

Linux distributions running GNOME can easily make a live CD through nautilus and gnome-disk-utility. Simply right-click on the .iso file, and select Open With Disk Image Writer. When GNOME Disk Utility opens, specify the flash drive from the Destination drop-down menu and click Start Restoring.

---

Ventoy

Ventoy is an open source tool to create bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files.
With ventoy, you don't need to format the disk over and over, you just need to copy the ISO/WIM/IMG/VHD(x)/EFI files to the USB drive and boot them directly.
You can copy many files at a time and ventoy will give you a boot menu to select them.

[icon name="exclamation-triangle" prefix="fas"] _{currently (in some cases) ventoy fails to boot EndeavourOS ISO (up from January 2023) possible to boot only if you use grub2 mode from Ventoy when selected the ISO.}

And make sure you are using the latest ventoy on the stick!

Available from AUR as ventoy-bin

After creating the ventoy USB stick, starting the GUI with ventoygui from terminal:

Always make sure the ventoy version on the USB stick is the latest, outdated versions may cause issues with the ISO.

Use the web-ui in your browser by starting this in terminal like so:

sudo ventoyweb

The gui is to be started with: `ventoygui` also from terminal, or from your menu...

You can also run the install on your usb stick with the commandline.

See ventoy --help in your terminal to see the options.

After creating the ventoy-stick with one of the tools, you simply need to copy the ISO file/s into the ventoy folder on the USB stick to be able to boot them from the ventoy-stick.

After copy the ISO file/s you need to make sure the USB device is fully syncing the files! File manager should do that in most cases, but to make sure open a terminal and run sync-command there till it frees the prompt again:

---

Etcher (https://www.balena.io/etcher/)

[icon name="exclamation-triangle" prefix="fas"]

Warning!

We do not recommend using etcher anymore as there are privacy concerns, etcher is Anonymously reporting errors and usage information. It is not clear if this is done. Also, it wants you to validate that you agree with it. Lately, users reporting also burned sticks does not work properly for the latest ISO.

Burn ISO to DVD:

And indeed, you still can burn the same ISO to a DVD using any common burner tool available.

On Linux, there is Brasero for GTK environments and the all mighty K3B using QT.

• Brasero: https://wiki.gnome.org/Apps/Brasero

• K3B: https://apps.kde.org/de/k3b/

And the command line would be something like:

growisofs -dvd-compat -Z /dev/sr0=endeavouros-2023.03.25-x86_64.iso

Create Live USB From Windows

USBWriter, and Rufus are free USB image writers that support .iso files (which EndeavourOS uses) with ease. Just head to the Source Forge link for USBWriter for Windows and download the program. Once downloaded, follow the similar instructions for them below:

USBWriter for Windows

USBWriter is the easiest solution to burn ISO images to USB on Windows, it has no options to confuse users or prevent stick from booting.

• “browse” to the .iso image of EndeavourOS, select the target USB drive and click the “Write” button and it will properly format the drive and write the image.

Rufus:

Rufus has a lot of options to create bootable USB-Sticks for different situations, our ISO does not need any modifications and should be "burned" as it is a so-called hybrid ISO ready to boot in all cases, from Stick or burned DVD-Rom.

Leave all settings from Rufus window as they are and click Start, this will pop up a question window that asks to burn hybrid ISO in ISO-mode or DD-mode, choose DD-mode to be sure it will not be modified at all.

]]> 1182 0 7 0 Latest release]]> Latest release]]> Live ISO installer info tricks & tips]]> Live ISO Installation Info Tricks & Tips]]> https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/ Sun, 14 Mar 2021 14:05:38 +0000 https://discovery.endeavouros.com/?p=1184

Our installation medium is already very stable and covers some hardware-specific peculiarities, but it is not an egg-laying wool milk sow. With this, it is possible to install the OS in many different ways, related to partition, format, encryption.

But there are limitations of what is possible to provide over the used framework.

Always keep in mind that EndeavourOS install and enable some stuff by default:

https://endeavouros.com/#packages

Other things are disabled by default for your security and to keep things simple:

https://discovery.endeavouros.com/audio/bluetooth/2021/03

Here we collect some information to resolve common issues with the installation process:

Online and Offline Installation Methods

Generel Warning: _{Online is the default option to be used, offline installs are only a fallback option in case of network/internet connection issues (or hardware driver issues with network devices)}

Online installation method

This is the recommended way to use the installer. It provides all available desktop environment options and allows you to deselect packages or add extras such as the LTS kernel or printing/scanner support.
With this method, the system is built and configured in a way very similar to a manual Arch Linux installation: everything is created and installed from scratch, using EndeavourOS configuration and packages freshly pulled from the mirrors.
The result is a fully up-to-date system with your preferred desktop environment.

Offline installation method

This is only a fallback option. It installs package versions from the point in time when the ISO was created. It can only install the KDE/Plasma desktop and does not allow you to choose another desktop environment in the installer.
The offline method runs entirely without an internet connection, which helps in cases of slow/unreliable connections or network hardware/driver issues.
⚠️ Important warning: The system will not be up-to-date after installation. On the first update, you may need to resolve issues manually due to changes that happened between the ISO creation and the current package versions.
Before running the first update on a fresh offline install, it is recommended to check for known update issues.

Important-news (on GitHub)

Important-news (on GitLab)

Preliminary remarks on installation in general (EFI, Bios, legacy, CSM, fastboot, secure-boot)

64-bit only: The ISO itself can be used as it is to boot on most Computers supporting x86-64 (x64, x86_64, AMD64, Intel 64) known as 64-bit. From old systems running on legacy Bios [Basic Input systems] to modern UEFI (EFI) [Unified Extensible Firmware Interface].

EFI/BIOS: In case, modern EFI systems can provide the option to support legacy boot so called CSM mode (Compatibility Support Module) Best is to disable this feature if possible, as the installer is not always detecting this correctly. In case you are dual booting with Windows installed in legacy mode, the options are indeed limited to go reinstall Windows in EFI mode or try to add EndeavourOS in CSM legacy mode.

Secureboot: The main downside is that we do still not support secure-boot, so this feature must be disabled to be able to install EndeavourOS in most cases. There are some Firmware opting to add secure-boot keys manually, but these are rare.

Fastboot: The fastboot feature from Windows (in case you want to dual boot) needs to be disabled as it will cause issues with hardware like Bluetooth or Wireless devices would not show up.

Create the install media (USB key)

https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03

Slow Internet unstable Connections

In some places, you do have not that stable internet connection, or you are connected over Wi-Fi with a bad bandwidth. Another reason can be restrictions from ISP so that you can not reach servers.

We have some implementations built in to detect and rank mirrors, but the procedure is known to not work in some parts of the world where you have only some not stable mirrors (India, Pakistan, Brazil p.e.).

In this case, the best to do is to use the "update mirrors" tool from the welcome application:

Make sure the resulting mirrorlist has at least 8 mirrors showing up, and save it.

Now start the installer, and you will be able to install via the online option.

Partition

The easiest way is to use the automatic options to partition your drive/s, you will find 3 main options to apply that:

Alongside: this will shrink the main system partition of the drive selected and add all needed partitions automatically, in case you can choose to create a new ESP in any case too also an existing one already would fit the minimum requirements:

Replace: useful in case of reinstall to overwrite one partition only and leave the rest intact.

Erase: this will simply use the complete drive and create everything new, deleting everything ion the selected drive!

Manual partitioning:

This is advanced usage! Handle with care.

The requirements for modern EFI (UEFI) systems:

Partition Table must be GPT here.

1. ESP (Efi System Partition) :

If you take systemd-bootloader:

Fat32, flagged as boot, Mount Point: /efi, Minimum size: 2048MB (2GB)

If you choose Grub Bootloader:

Fat32, flagged as boot, Mount Point: /boot/efi, Minimum size 300MB.

2. System Partition

Possible format ext4 or BTRFS Mount Point /

Older (legacy) Bios Systems:

If you can only boot into CSM (Compatibility Support Module) or on real older non-efi Bios systems.

_{This could be the case if Windows is installed in that mode already, and you do not want to reinstall Windows in EFI mode.}

You have 2 Options here:

First Option: is the old standard using the MBR (Master Boot Record, first sector of a hard disk):

Bootloader will get written into the MBR of a msdos partition table, here you need only one System Partition,

mounted as /, flagged as boot.

The Second Option: is to use a GPT partition table, and create an 8MB sized **empty** partition, flagged as bios-grub.

[September 2025] ]As of the moment this Method can result in non-booting system, so it is currently noit recommended to use this for older Bios/legacy installs.

In this case, Bootloader will get installed onto the "grub-drive".

BTRFS

If you choose BTRFS it will create a preset of subvolumes with automate partition options, and on manual partitions it will resolve subvolumes too.

Recommendation is to only take BTRFS if you know why you would need to, it is not only another faster more fancy filesystem, and needs some knowledge to earn beforehand!

https://archive.kernel.org/oldwiki/btrfs.wiki.kernel.org

Installer can not create partition

In some cases, it is a good thing to delete the partitions you want to use for EndeavourOS before starting the installation. You can simply use KDE partition Manager, which you can start with the button in the welcome app or via the menu of the live environment.

In 2024, we added GParted in addition, to the ISO for your convenience.

Advanced installer options

You can unselect packages you do not need:

This option is only available for online install method!

EndeavourOS Desktop Fixes and Theming

EndeavourOS has preset small changes to the settings and themes for all desktop installations to fix problems with the default settings and smooth the interfaces. In addition, installs for other environments (like i3 or sway) will offer some more complete setups to be able to start with a usable Desktop.

If you want an unchanged installation, you can easily turn off these changes by deselecting the appropriate subgroup:

What to do if install fails or i have issues?

In case the installation is not successful, do not reboot or exit the live session! Please send us the installer log on the forum, or over telegram chat, we can always make great use of them to fix issues and bugs with the installer:

You ca use the log tool from the panel and send log to Pastebin (internet connection required).

Run the log tool with inxi and install log tagged:

And post the URL it creates in this little popup window on forum, chat or send it via email:

Connect with us, we will be happy to help in any way:

https://endeavouros.com/contact/

For encrypted installation help/info go here

More info about encrypted installation.

Installer process slideshow:

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

]]> 1184 0 6 0 Graphic cards (GPU) driver and setup]]> Enable and setup Bluetooth devices]]> Create install media (USB key)]]> Create install media (USB key)]]> https://discovery.endeavouros.com/desktop-environments/lightdm/2021/03/ Sun, 14 Mar 2021 14:15:32 +0000 https://discovery.endeavouros.com/?p=1186

LightDM is a cross-desktop display manager. A display manager is a daemon that:

• Runs display servers (e.g. X) where necessary.
• Runs greeters to allow users to pick which user account and session type to use.
• Allows greeters to perform authentication using PAM.
• Runs session processes once authentication is complete.
• Provides remote graphical login options.

Key features of LightDM are:

• Cross-desktop – supports different desktop technologies.
• Supports different display technologies (X, Mir, Wayland …).
• Lightweight – low memory usage and fast performance.
• Guest sessions.
• Supports remote login (incoming – XDMCP, VNC, outgoing – XDMCP, pluggable).
• Comprehensive test suite.

Source: https://github.com/canonical/lightdm

Setup LightDM to work nicely on Multidisplay systems

Use Arandr to fix the display setup on multi-display systems for LightDM

For EndeavourOS (and other Archlinux based):

https://youtu.be/AiD042zOME4

1. Install arandr from repositories: sudo pacman -S arandr
2. setup displays with arandr.
3. save the setup as monitor in the given directory.
4. copy the saved script to lightdm directory:
   sudo cp ~/.screenlayout/monitor.sh /etc/lightdm/
5. make it executable:
   sudo chmod +x /etc/lightdm/monitor.sh
6. edit lightdm.conf:
   sudo nano /etc/lightdm/lightdm.conf
   uncomment the display setup option and add the path to the script:
   display-setup-script=/etc/lightdm/monitor.sh
   (you can also add this line at the end of the file)
   save the file [Ctrl+X]
7. restart lightdm to see if it is working:
   sudo systemctl restart lightdm

Troubleshooting:

1. Lightdm fails to start at all (black screen with no login GUI showing up)

lightdm has an issue where it sometimes happens that it starts too fast - before X is ready, or even before the GPU driver is fully loaded. One solution is to set logind-check-graphical=true inside lightdm.conf

uncomment the line #set logind-check-graphical=false and change from false to true like so:

logind-check-graphical=true

There are several different cases where Lightdm can fail to start, most often it is the case that the GPU driver is not loading at all or too late. that makes X system fail to be available for lightdm.

It can be also be a typo or a wrong setting in the config file/s, as EndeavourOS is using lightdm-gtk-greeter - per default it can be missing one of the needed packages ( lightdm lightdm-gtk-settings lightdm-gtk-greeter) causing it to fail to start.

Lightdm has also build-in debugging mode you can start from CLI if it fails:

lightdm --test-mode --debug

You can also run this from terminal if X is running.

Maybe you need to install Xephyr:

sudo pacman -S xorg-server-xephyr

will give a debugging log like this:

Going through the debugging output you can usually find the culprit that may be causing the issue for you.

As the status mostly do not give helpful output:

systemctl status lightdm

]]> 1186 0 5 0 https://discovery.endeavouros.com/desktop-environments/font-management/2021/03/ Sun, 14 Mar 2021 14:36:13 +0000 https://discovery.endeavouros.com/?p=1191

_{By Cmarch}

Many unwanted fonts get installed on Linux systems, and that can make the font scroll list in editors and word processors painfully long. There are many methods and apps to trim font lists, but somehow those unwanted fonts always creep back in when your back is turned, or you do a reinstallation.

An easy solution to tame those unwanted fonts is to use a ~/.config/fontconfig/fonts.conf file to whitelist and blacklist fonts. It’s easy to implement, can be easily modified, and can be saved and used over and over. Another benefit is the fonts are not deleted, they just don’t show up in your user session. All fonts listed in the <rejectfont> section are blacklisted, while fonts listed in the <acceptfont> section are whitelisted as subsets of the rejected fonts you want to allow. Think of the rejects as a larger parent set and the accepts as a smaller, select sub-set of that parent.

Edit or create a ~/.config/fontconfig/fonts.conf file and:

1. Put the fonts you do not want to see in the rejectfont section.
2. Put any fonts from the above <rejectfont> section that you might want to keep in the <acceptfont> section.
3. Fonts not added to the <rejectfont> section will not be affected.

A sample ~/.config/fontconfig/fonts.conf file might look like this:

<?xml version='1.0'?>
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
<fontconfig>
 <!-- Local settings -->
 <selectfont>
    <rejectfont>
       <glob>/usr/share/fonts/noto/Noto*</glob>
       <glob>/usr/share/fonts/gsfonts/*</glob>
       <glob>/usr/share/fonts/TTF/DejaVuMathTeX*</glob>
       <glob>/usr/share/fonts/TTF/odo*</glob>
       <glob>/usr/share/fonts/mathjax2/*</glob>
       <glob>/usr/share/fonts/croscore/*</glob>
    </rejectfont>
    <acceptfont>
       <glob>/usr/share/fonts/noto/NotoSans-*</glob>
       <glob>/usr/share/fonts/noto/NotoSerif-*</glob>
       <glob>/usr/share/fonts/gsfonts/NimbusMono*</glob>
       <glob>/usr/share/fonts/gsfonts/NimbusRoman*</glob>
       <glob>/usr/share/fonts/gsfonts/NimbusSans*</glob>
       <glob>/usr/share/fonts/gsfonts/URW*</glob>
    </acceptfont>
 </selectfont>
</fontconfig>

In this fonts.conf file all the Noto fonts were initially rejected and then later NotoSans and NotoSerif were added back by whitelisting them.

Note:

• Your fonts.conf file may contain other useful stuff, that’s ok, leave it there.
• Be sure and save a backup of this file for future use. If your working fonts.conf file gets deleted or disappears on a reinstallation of your OS, you can always recover it.

In this fonts.conf file all the Noto fonts were initially rejected and then later NotoSans and NotoSerif were added back by whitelisting them.

For reference see:

• Font Management – https://wiki.archlinux.org/title/Fonts
• Whitelist and blacklist fonts. – https://wiki.archlinux.org/index.php/Font_configuration#Whitelisting_and_blacklisting_fonts

]]> 1191 0 4 0 https://discovery.endeavouros.com/endeavouros-tools/a-gui-app-for-selecting-arch-mirrors/2021/03/ Sun, 14 Mar 2021 15:25:04 +0000 https://discovery.endeavouros.com/?p=1201

Mirror ranking or selecting the best mirrors (package servers) can be done with a command line utility called reflector. A GUI wrapper for reflector is reflector-simple. It provides a simple graphical user interface:

All countries having Arch mirrors are shown, and any combination of them can be selected. The typical selection includes your country (if available on the list) and/or countries near your country because usually, the closest mirrors are the fastest. And note the word Worldwide at the beginning of this list, which means (as far as I know) it should work reasonably well in most geographical areas.

After the list of countries, there are some ranking options. Most of these options have a counterpart in reflector. For example, selecting Include https mirrors means using the -p https option with reflector.

The following table shows the correspondence between the selections and reflector:

Selection	Related reflector option	Purpose
Include https mirrors	--protocol	Include mirrors that use https protocol.
Include http mirrors	--protocol	Include mirrors that use http protocol.
Use /etc/reflector-auto.conf		If package reflector-auto is installed, you may automatically re-use its configuration file. More information under Configuration file(s) below. Note: starting with version 1.5-1 this selection is no more available.
Max hours from latest mirror sync	--age	Accept only mirrors that have been synchronized with the master mirror within the last given number of hours.
Sort by	--sort	How to sort/rank the resulting list of mirrors. The best mirrors will be placed in the beginning of the list of mirrors.
Max number of mirrors	--number	Return at most the given number of mirrors.

Command

reflector --help

gives more information about reflector’s options.

Configuration file(s)

reflector-simple supports a configuration file

/etc/reflector-simple.conf

if it exists. That file can contain command line options of the reflector command (see the example below).

The reflector options given in this file are used as the “starting point” (in version 1.5-1 and later) for the features that can be changed with the GUI. (Earlier versions overwrote the values of the GUI, which was confusing.)

About the contents of the configuration file:

• options can be on several lines
• options can be on the same line(s)
• the file can have empty lines, or comment lines starting with the # character

Use command reflector --list-countries to see supported country names and country codes.

A (somewhat random) example configuration file:

# Example /etc/reflector-simple.conf:

--sort age
--age 5
--number 20
--country Canada,US,"United Kingdom"

As the example shows, the country specifications can be country names (Canada, "United Kingdom") or country codes (US). Note the usage of quotes when the country name contains spaces.

Note also that file /etc/reflector-auto.conf (from the obsolete command reflector-auto) is supported if it exists and /etc/reflector-simple.conf does not. Support for the other configuration file was removed at the end of the year 2020.

More information about the configuration file(s) is here:
https://github.com/endeavouros-team/PKGBUILDS/tree/master/reflector-simple

---

Editing history:

• _{created 2019-Dec-12 by Manuel}
• _{edited: 2020-Oct-9 by Manuel}
• _{edited: 2020-Oct-12 by Manuel}
• _{edited: 2020-Dec-10 by JoeKamprad}

]]> 1201 0 3 0 https://discovery.endeavouros.com/pacman/automatically-ranking-the-mirror-list/2021/03/ Sun, 14 Mar 2021 16:12:17 +0000 https://discovery.endeavouros.com/?p=1203

New solution to auto rank and update mirror list:

When downloading packages, pacman uses the mirrors in the order they are listed in /etc/pacman.d/mirrorlist and /etc/pacman.d/endeavouros-mirrorlist The order in which servers appear in the list sets their priority.

It is not optimal to only rank mirrors based on speed since the fastest servers might be out-of-sync. Instead, make a list of mirrors sorted by their speed, then remove those from the list that are out of sync according to their status.

It is recommended to repeat this process periodically.

The Arch wiki has some instructions to do all this manually:

https://wiki.archlinux.org/index.php/Mirrors#Ranking_an_existing_mirror_list

At the moment of writing, the EndeavourOS mirrors are in a modest amount, but we are already future proof by a package in our repo to automatically rank our own mirror list.

Steps to enable automatic mirror-rank for Archlinux mirrors with a timer (systemd):

install the package:

sudo pacman -S reflector

Uses reflector to rank your Archlinux mirror list once a week.

The reflector package now includes a systemd-timer, so you can use it to automatically update your mirror list once a week:

sudo nano /etc/xdg/reflector/reflector.conf

sample output of setting this file up:

save the file by pressing this key-combination:

[Ctrl]+[X] and say yes to save the file.

The last step is to enable the reflector timer to run this once a week:

sudo systemctl enable --now reflector.timer

check if it is running:

systemctl status reflector.timer

This will give something like this:

It shows the following: enabled and 3 days left Triggers: reflector.service This means it is working and will now update the mirrorlist automatically for you.

---

Editing history:

• Edited by Manuel at 2020-Aug-26
• Edited by JoeKamprad at 2020-Dec-10

If you do not get this working just post at the forum and if you want to add something :
Don't hesitate to tag our moderators or admins.
Join us at the forum, you are more than welcome!

]]> 1203 0 2 0 https://discovery.endeavouros.com/pacman/mirrors-intro/2021/03/ Sun, 14 Mar 2021 17:22:32 +0000 https://discovery.endeavouros.com/?p=1205

What are mirrors and why are they important?

Mirrors are the package servers we use when installing or updating packages. There are lots of mirrors (for Arch) around the world, and to keep package updates running smoothly, the mirrors should be both:

• fast (high data rate and responsiveness)
• up to date

On an EndeavourOS system, Arch mirror addresses are gathered as a list into file /etc/pacman.d/mirrorlist.

In the /etc/pacman.d/mirrorlist file, lines that begin with a # are ignored, and then the order (from top to bottom) is respected. If a problem exists with the first entry, pacman defaults to using the next active line down.

Usually (but not always) the closest mirrors are the fastest. That’s why we usually want to use mirrors from the user’s current location (country) or some nearby countries.

Another important factor is that the mirrors we use are up to date, meaning they have been synced with the master Arch package server recently. Better to use a mirror that has the latest Arch packages.

Yet another (temporary) concern may be that a particular mirror is offline, e.g. under maintenance. Sometimes a mirror may even be permanently offline.

That’s why having a decent list of mirrors on your machine is important.

Note that the list of mirrors can (and usually should) be ranked to get the best experience when updating or installing packages. Ranking mirrors organizes the list of mirrors so that the best mirrors for your location are at the beginning of the list.

Mirror ranking tools

EndeavourOS has the following tools directly available for ranking the Arch mirrors (in alphabetic order):

• rate-mirrors
• reflector
• reflector-simple

Each of them has pros and cons, so experimenting in your location may be needed to have a good result.

What about EndeavourOS mirrors?

EndeavourOS has its own packages as well, thus EndeavourOS has its own list of mirrors and you can find the mirror list is in file /etc/pacman.d/endeavouros-mirrorlist.

To be able to rank EndeavourOS mirrors, first you need to install eos-rankmirrors package if not already installed.

yay -S --needed eos-rankmirrors

EndeavourOS mirrors can now be ranked with a terminal command (note: call without sudo!)

eos-rankmirrors

It fetches the latest EndeavourOS mirrorlist from the EndeavourOS development site, and ranks the mirrors found in that list. Then it shows you the ranking result, and prepares to write the ranked list to file /etc/pacman.d/endeavouros-mirrorlist. For writing the file it needs elevated privileges, and asks you the required password.

Note that eos-rankmirrors can be configured with file /etc/eos-rankmirrors.conf. For example, to make the ranking process significantly faster, you can exclude mirrors you know are very slow or not always working well. Use variable EOS_IGNORED_MIRRORS for that by adding unique partial names of mirrors to the variable (using bash syntax).

Alternatively, rate-mirrors can rank EndeavourOS mirrors as well.

]]> 1205 0 1 0 https://discovery.endeavouros.com/pacman/automatic-update-of-the-pacman-database/2021/03/ Wed, 24 Mar 2021 11:07:43 +0000 https://discovery.endeavouros.com/?p=1238

by Joekamprad

A corrupted Pacman database usually is caused by sudden power loss when the system is running or during a system update. There is a way to prevent this from happening.

Backup automatically with systemd:

Automated backup In order to keep the back up up-to-date; automation of the aforementioned backup command makes sense.

This can be realized with the tool pakbak-git [AUR]
Pakbak is a bash script that is triggered by a Systemd service once the contents of the /var/lib/pacman/local directory have been changed.

After installing Pakbak, the destination and the number of backups to be kept in rotation can be set.

sudo nano /etc/pakbak.conf

# Backup the database to this folder
target_folder = /var/local/pakbak
# Define how long backups should be kept
keep_days = 5
# Define how many backups should be kept
keep_number = 5

Note:

The target directory must be created or already exist.
Environment variables in the path, such as $HOME will not be processed.

test if it is working

To test whether the bash script works as expected, you can manually initiate the execution with root privileges:

sudo sh /usr/lib/systemd/scripts/pakbak

Then enable the Systemd service, which is the directory /var/lib/pacman/local automatically monitored for changes:

sudo systemctl enable pakbak.path

Conclusion

Now you will have created regularly: pakbak-year-month-day-220137.tar.xz archives in the path you specified inside config file (target_folder = /var/local/pakbak)

You can easely unpack and replace to /var/lib/pacman/local in case of pamac databse corruption.

]]> 1238 0 0 0 https://discovery.endeavouros.com/pacman/downgrade-packages-to-a-specific-date/2021/03/ Tue, 16 Mar 2021 12:58:01 +0000 https://discovery.endeavouros.com/?p=1240

by Bryanpwo

Warning: Don’t do this unless it is completely necessary!

• Having old and outdated packages in your Arch Linux is not recommended. Read our news articles on the website and our forum to see if users have reported any problems. In case there is a problem don’t update and wait for one or two days to see if the problem is fixed upstream.
• If this kind of downgrade fails for any reason, you will end up with a broken system.

I already have covered how to downgrade a single package and the kernel. This article is about how to downgrade all packages to a specific date. The reason for doing this can be because the system might be broken after a recent system upgrade. In such a case, you might have to downgrade more than one packages to a previously working version.

If you have no choice and want to fix your unstable system you can downgrade all packages to a previous specific version and date.

In this example we’re going to set the system back to the version that was installed on 20 June 2019

One way to do this, is to make temporary changes to your /etc/pacman.conf file. To do so, first backup your pacman.conf:

sudo cp /etc/pacman.conf /etc/pacman.conf.bak

Then, edit file /etc/pacman.conf:

sudo nano /etc/pacman.conf

Replace the existing content under these headings with the following lines:

[core]
SigLevel = PackageRequired
Server=https://archive.archlinux.org/repos/2019/06/20/$repo/os/$arch

[extra]
SigLevel = PackageRequired Server=https://archive.archlinux.org/repos/2019/06/20/$repo/os/$arch

[community]
SigLevel = PackageRequired Server=https://archive.archlinux.org/repos/2019/06/20/$repo/os/$arch

If you have other repos enabled, they need the same treatment, or you risk having some things running a version from a different date!

You can instead (and with less effort) temporarily change /etc/pacman.d/mirrorlist. Because all the usual /etc/pacman.conf entries use it already there's much less editing (and fewer chances of a typo).

sudo cp /etc/pacman.d/mirrorlist /etc/pacman.d/mirrorlist.normal
sudo nano /etc/pacman.d/mirrorlist

The only line the replacement needs is as follows: Enter it as shown, remembering to have the date refer to the date you want to revert to!

Server=https://archive.archlinux.org/repos/2019/06/20/$repo/os/$arch

Save and close the file with ctrl+o and ctrl+x

Then update the system with:

sudo pacman -Syyuu

After that completes, then change the mirrorlist file back to normal.

sudo cp /etc/pacman.d/mirrorlist.normal /etc/pacman.d/mirrorlist

Rebooting the system right away is wise (in case of important system changes) and it will now boot into the versions from the date given.

If you want the process to be 'automated' a bit, there is another Wiki entry that will help.

https://discovery.endeavouros.com/pacman/easy-downgrade-by-date/2021/06/

]]> 1240 0 0 0 How to backup Pacman database automatically]]> Easy Downgrade by Date]]> Easy Downgrade by Date]]> https://discovery.endeavouros.com/pacman/downgrade-packages/2021/03/ Tue, 16 Mar 2021 13:04:18 +0000 https://discovery.endeavouros.com/?p=1244

by Bryanpwo

If a package update causes problems don’t worry, Pacman has the previous version stored in the /var/cache/pacman/pkg/ unless the Pacman cache has been cleaned. Downgrading using this method then can’t be done.

This process will remove the current package and install the older version. Dependency changes will be handled, but Pacman will not handle version conflicts. If a library or other package needs to be downgraded with the packages, please be aware that you will have to downgrade this package yourself as well.

sudo pacman -U /var/cache/pacman/pkg/package-old_version.pkg.tar.xz

Once the package is reverted, temporarily add it to the IgnorePkg list of pacman.conf until the difficulty with the updated package is resolved.

Downgrading the kernel

If a kernel update causes problems you can use this command as well, but keep in mind that you also have to downgrade all the kernel-related packages like the linux-kernel-header and kernel-related VirtualBox, if installed. For example:

sudo pacman -U linux-5.2.arch2-1-x86_64.pkg.tar.xz linux-headers-5.2.arch2-1-x86_64.pkg.tar.xz virtualbox-host-modules-arch-6.0.8-2-x86_64.pkg.tar.xz

If you can’t boot the system after a kernel update, go to the chroot wiki article to get into the system, then commence the process as described above.

Alternatives

Other alternatives exist for this procedure. It is possible that the AUR package downgrade is on your system, and can be used in the same manner (except that it will offer to mark as 'Ignore package' for you). Another method is to downgrade to a specific date (previous to your problem) as shown here:

https://discovery.endeavouros.com/pacman/downgrade-packages-to-a-specific-date/2021/03/

]]> 1244 0 0 0 Downgrade packages to a specific date]]> Downgrade packages to a specific date]]> https://discovery.endeavouros.com/pacman/desktop-managers/2021/03/ Tue, 16 Mar 2021 13:10:21 +0000 https://discovery.endeavouros.com/?p=1246

by Bryanpwo

If you don’t have automatic login enabled, the Desktop Manager is the first thing you’ll see after your system has been through Grub and the kernel start-up.

Most people call it a greeter, but it’s so much more than that, it also is responsible for a smooth desktop experience. That’s why it’s key to install the Desktop Environment with the corresponding Desktop Manager.

Gnome

Gnome recommends GDM as their DM. If you installed the Gnome group, GDM is already installed, but not enabled by default. If you’re coming from the offline installer do the following:

sudo systemctl -f enable gdm

(the -f option forces to disable the already enabled one and enables the new one)

Then reboot the system and GDM will appear on your login screen.

KDE Plasma

KDE uses SDDM, to install it enter the following

sudo pacman -S sddm

Then follow the disable/enable instructions described under Gnome, replacing gdm for sddm.

Deepin

Deepin uses Lightdm, but with a customized script (DDE) to make the DM more in sync with the DE. This DDE is already shipped when you’ve installed the deepin group, you only have to change the Lightdm file to enable it.

sudo nano /etc/lightdm/lightdm.conf

And change the next line to look like this:

greeter-session=lightdm-deepin-greeter

Be careful to look for the line without the # in front of it (there’s also a line that starts with # greeter-session=) don’t change that line. After you’ve done that save and close the file with ctrl+o and ctrl+x and reboot.

Budgie

Budgie doesn’t have a specific designated DM, but since it’s recommended to install the Gnome group with this DE, you can use GDM. To enable it read the Gnome section.

Cinnamon

Cinnamon uses Lightdm, but if you want to make the DM look more like Linux Mint you can install lightdm-slick-greeter and to customize it to your liking. You can also install lightdm-settings. Since both packages are in the AUR, you can use yay to install them.

After install you have to change the lightdm config file, just read the deepin section for this and change the line into this:

greeter-session=lightdm-slick-greeter

Save and close the file (see Deepin) and reboot. To customize Lightdm just open the lightdm-settings app so you can change the position of the login box and change the background picture.

EDIT March 16 2021: EndeavourOS installations from 2020 or newer have this procedure simplified with a button on the Welcome app.

]]> 1246 0 0 0 https://discovery.endeavouros.com/desktop-environments/removing-a-desktop-environment/2021/03/ Wed, 24 Mar 2021 10:58:56 +0000 https://discovery.endeavouros.com/?p=1248

If you have changed to another DE (Desktop Environment) after initially installing the offline edition (XFCE4) or you just decided to move over to your freshly discovered DE, you might want to remove the unused one.

In most cases, this isn't easy to do, especially when you switch from GTK to QT, or vice-versa, there are still some dependencies you might need.

So I try to give an example here, the best practice is to update your system first:

sudo pacman -Syu

Use desktop installer helper script eos-packageslist:

We have little helper script for handling DE/WM installs eos-packageslist that makes the handling more convenient for you:

example:

eos-packagelist --install "GNOME-Desktop"

more options on the tool: eos-packagelist --help

To list available groups eos-packagelist --list

A trick to uninstall per example a fresh offline XFCE4 after you installed an alternative Desktop:

create packages list for default xfce4:

eos-packagelist "XFCE4-Desktop" > xfce4

remove packages from that list:

sudo pacman -Rc - < xfce4

But check exactly what will get removed here too dependencies can be a hell ;)

Most save way to handle is from TTY!

login to TTY4:

Ctrl + Alt + F4

give username and password to login as user.

now follow these steps:

1. uninstall old Desktop: eos-packagelist "XFCE4-Desktop" > xfce followed by: sudo pacman -Rc - < xfce4
2. install new Desktop: eos-packagelist --install "GNOME-Desktop"
3. Make sure base system is intact: eos-packagelist --install "Desktop-Base + Common packages"
4. change Display Manager: sudo systemctl -f enable GDM

You can do this also while logged in to your current Desktop, but uninstalling it while using it can cause freezing.

Unfortunately, there isn't a full-proof way to do this, so always take a look at the exact terminal output, and be careful you do not uninstall certain system relevant packages or packages you have installed manually like a preferred browser or other apps.

If you remove an DE make sure to enable the new DM (LoginManager) before rebooting the system or you will boot into TTY without graphical login like this:

In that case, you will need to enable the DM manually:

sudo systemctl -f enable --now GDM

To get the graphical Login-Manager show up again.

This is only one example of the situation you could run into, but most of the time these steps will be enough for any DE change.

In case you are encountering issues, don't forget to ask our helpful community.

You can find the lists also in this GitHub Repo:

reinstall DE commands at GitHub

So choose your new DE and copy and paste the command in your Terminal:

In this example I use GNOME:

git clone https://github.com/endeavouros-team/EndeavourOS-packages-lists.git

cd EndeavourOS-packages-lists

ls will list the files

sudo pacman -S --needed - < gnome

will install Gnome packages.

]]> 1248 0 0 0 https://discovery.endeavouros.com/pacman/pacman-basic-commands/2021/03/ Wed, 24 Mar 2021 11:03:44 +0000 https://discovery.endeavouros.com/?p=1535

by Bryanpwo

The Pacman package manager is a powerful tool at the center of the system, that allows you to maintain, expand and update the system.

In this section, I give you the basic commands to keep your system up and running. Keep in mind that these commands only install packages from the Arch repository and not packages from the AUR.

Archlinux pacman manual

Updating the system

EndeavourOS is a rolling release distro based on Arch Linux. This means your system always receives the latest packages, so you’re always ensured of an up-to-date system without installing a major release once or twice a year.

To update the system you can use this command

sudo pacman -Syu

You will notice that Arch releases updates daily and we strongly recommend doing a full system update instead of a partial one, so install updates at a time in the day you’re able to read and look upon the updates on our forum, so not when you’re thirty minutes from an important presentation.

The community often warns you if an update is broken, so you know it's better to wait to perform the update, with big issues, Arch usually fixes those within hours. You can also install the updates once a week and keep an eye out on the forum every day to keep yourself informed. Don’t delay installing the updates longer than that, because this can break your system.

Searching for packages

To search for packages in Pacman you can use the command

pacman -Ss package_name

When you’ve found the package you can install it according to the instructions in the paragraph here below.

When you can’t find the desired package, this means it isn’t in the Arch repo, but you’ll find it most likely in the AUR. For searching and installing packages in the AUR we refer to the yay article.

Installing packages

To install a single package from the Arch repository you can use the following command in the terminal.

sudo pacman -S package_name

You can also use this command to install several packages by just hitting the space bar after the first package name and enter the other package name(s).

Installing package groups.

Suppose, you have read on our forum or on the internet an article or review of a Desktop Environment that has caught your interest. Instead of installing all the separate packages that the DE depends on, you can also install the entire group by the following style of command

sudo pacman -S plasma

This installs all the packages that belong to the DE, in this case, I used KDE plasma as an example, just replace plasma with the DE you wish to install. You will notice that Pacman first displays all the packages and asks for your permission to install them. If you want to exclude packages from the DE group you can do so by the following.

Enter a selection (default=all): 1-15 20

In this case it will install packages 1 through 15 and package number 20.

Enter a selection (default=all): ^5-8 ^15

This will install everything that belongs to the DE group, except packages 5 through 8 and package number 15.

Removing packages

A package is always installed with other packages that it depends on, called dependencies. Quite often those dependencies are already, or partially installed on your system because other packages also depend on it.

To remove a package without the dependencies use the following command.

sudo pacman -R package_name

If you rather want to avoid a cluttered system you can remove a package and its dependencies, without removing dependencies that are used by other installed packages, use the following command.

sudo pacman -Rs package_name

Refreshing mirrors

Sometimes it can happen that your system can’t find the updates or packages in the Arch repo, when using -Syu. In that case, it could be that there’s a problem with the mirrors you’re trying to connect to. Only if this happens you can try force refreshing the local package database (Passing two --refresh or -y flags will force a refresh of all package databases, even if they appear to be up-to-date.) :

sudo pacman -Syy

Skipping package updates

Although we do not recommend partially update your system, sometimes it is needed, because there’s a problem with the updated package upstream and Pacman isn’t able to perform the daily or weekly update, because of this certain package or the specific package causes to break the system. In that case, you can put that package on the Ignore list.

sudo nano /etc/pacman.conf

Ad the line IgnorePkg = package_name like this.

# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
 #IgnorePkg =
 IgnorePkg = package_name
 #IgnoreGroup =

Save and close the file by hitting ctrl + o and then ctrl+x

In this case, Pacman will always inform you that there’s an update for a certain package on the Ignore list like this.

:: package_name is in IgnorePkg/IgnoreGroup. Install anyway? [Y/n]

You can also put an entire group on the ignore list by adding the line IgnoreGroup = gnome

To remove the package or group from the ignore list just open the file as described above and remove the added lines, save and close the file, then type the following command.

sudo pacman -S package_name

The above method will permanently stop the specified package from being upgraded until you remove it from the ignore list

To do this temporarily, you can simply run:

sudo pacman -Syu --ignore=package_name

This command will skip the package from being updated. Similarly, to skip a package group, just run:

sudo pacman -Syu --ignoregroup=gnome

If you’re interested in a more detailed tutorial, you can also read the following article:

https://discovery.endeavouros.com/articles/pacman-actions-explained/2019/12/

]]> 1535 0 0 0 Pacman actions explained]]> Pacman actions explained]]> https://discovery.endeavouros.com/desktop-environments/how-to-install-desktop-environments-next-to-your-existing-ones/2021/03/ Wed, 24 Mar 2021 11:02:34 +0000 https://discovery.endeavouros.com/?p=1538

by Bryanpwo

I’ve already told you how to install a group, in this section I’m going to give you the specific commands you need to enter to install a specific Desktop Environment and also remove an installed Desktop Environment.

Gnome

sudo pacman -S gnome

This installs the basic Gnome DE, for the extra’s like games etc. install

sudo pacman -S gnome-extra

The reason why I didn’t put it behind the first command is that you might want to choose which extra packages you want to install on your system. Doing it this way you have a clear overview of which packages you want, without worrying to select a must-needed package by accident. If you don’t mind having the complete extra’s, you can put the two groups in one command. (with a space between the two groups.)

If you want to exclude packages from the DE group you can do so by the following.

Enter a selection (default=all): 1-15 20

In this case, it will install packages 1 through 15 and package number 20.

Enter a selection (default=all): ^5-8 ^15

This will install everything that belongs to the DE group, except packages 5 through 8 and package number 15.

For the last two steps, I’m going to refer to this one in the other DE sections.

Xfce

sudo pacman -S xfce4

This will install the basic XFCE4 DE if you desire the extra packages as the Whisker menu, then do the this

sudo pacman -S xfce4-goodies

If you don't want to install all the goodies, you can select the desired apps by following the steps described in Gnome.

Deepin

sudo pacman -S deepin deepin-extra

For selecting packages in the deepin-extra group see Gnome.

Budgie

sudo pacman -S budgie-desktop

Budgie doesn’t have an extra package, but it is recommended that you install the Gnome group as well for a better experience.

sudo pacman -S gnome

Cinnamon

sudo pacman -S cinnamon system-config-printer gnome-keyring blueberry cinnamon-translations

The install packages I give you for Cinnamon are recommended, but in my opinion it’s almost mandatory to have a better DE experience.

Mate

sudo pacman -S mate mate-extra system-config-printer blueman 

Like Cinnamon the packages I added are recommended, but for a better experience it’s almost mandatory. (my opinion)

KDE Plasma

Installing KDE differs a bit from the other DE’s, since there are a few choices to install it the way you like it.

For a minimal Plasma desktop install

sudo pacman -S plasma-desktop

For a full Plasma desktop install

sudo pacman -S plasma

or

sudo pacman -S plasma-meta

for the extra packages install

sudo pacman -S kde-applications 

or

sudo pacman -S kde-applications-meta

And remove qt5ct (tool to configure qt apps in gtk environments)

sudo pacman -R qt5ct

remove the configuration:

sudo nano /etc/environment

comment the line:

QT_QPA_PLATFORMTHEME=qt5ct

to look like this

#QT_QPA_PLATFORMTHEME=qt5ct

save the file with [**Ctrl+X**]

To use the Discover installation tool install

packagekit-qt5

Removing an installed DE

To remove a Desktop Environment and its extra group simply use this command.

sudo pacman -Rs package_group_name package_group_name-extra

More detailed help on uninstalling an unneeded DE completely is provided here:

Removing a desktop environment

Install DE/WM like it would be installed from the ISO on installed systems:

We have a package in the EndeavourOS repo called eos-packagelist that can provide you with a list of packages we use for a particular edition. To list available editions use this command:

eos-packagelist --list

Then to list the packages for that edition, for example Openbox Edition:

eos-packagelist "Openbox Edition"

Finally to install an edition, use the --install option.

eos-packagelist --install "Openbox Edition"

]]> 1538 0 0 0 https://discovery.endeavouros.com/system-rescue/how-to-boot-without-a-graphical-environment/2021/03/ Wed, 24 Mar 2021 13:37:16 +0000 https://discovery.endeavouros.com/?p=1580

by joekamprad

On using systemd-boot:

Press e on the boot menu and end to reach end of the bootline sperate with space and add 1.

To boot into rescue shell press enter:

1 stands for Boot into emergency rescue mode (single user mode)

Once booted it will present the following prompt:

Give your root password to enter the system.

If you are using grub and the graphical interface won't boot up, just restart your machine and follow the next steps:

• Press e when the grub-boot menu appears.
• Use the arrow keys to find the line that looks like this:
  linux /vmlinuz=linux root=UUID=...... rw quiet resume=.... (… = long snake of numbers)
• put systemd.unit=multi-user.target right after rw like this:
  rw systemd.unit=multi-user.target resume=....
•  I recommend removing quiet to get more informational output on boot (leave the rest untouched!!!)
• Press Ctrl+X to boot with this parameter.
• Now your machine is able to boot up without starting a graphical environment, and you can log in to proceed with repairing the system…

]]> 1580 0 0 0 https://discovery.endeavouros.com/system-rescue/repair-a-non-booting-grub/2021/03/ Wed, 24 Mar 2021 18:09:39 +0000 https://discovery.endeavouros.com/?p=1588

Repair a non-booting GRUB

EndeavourOS comes with systemd-boot as default install option, but in case you opted to install using Grub.

It happens sometimes due to an update or perhaps because of your tinkering with the system, Grub refuses to boot.

Don't worry there are only a couple of steps needed to repair GRUB, so you can get into the system as you're used to.

First, you have to Chroot into the system, just follow the steps described in these articles:

Arch-Chroot wiki on discovery

To validate if you are on UEFI or not run:

efibootmgr

Before you proceed, these instructions are made for a standard automatic installation, if you installed the system with a modified manual partition scheme, just ask our community on the forum and make sure you provide them with the needed logs with our log tools.

Repair GRUB on EFI/UEFI systems (Most modern systems)

Before you are going to repair GRUB, you should also check your EFI-boot-settings, this also can be the reason why GRUB isn't booting.

1. reinstall GRUB files:

Only grub-install is needed no need to add any options, at least on EndeavourOS where we use the default efi-path /boot/efi what is the default used for the command already. The --bootloader-id option will create a new entry with the given ID that in some cases will not get set as the default boot entry in the firmware.

If not used it will use the GRUB_DISTRIBUTOR= entry from the grub main config in /etc/default/grub, in case this is not the same as used before for bootloader-id it will create a new entry.

2. Rebuild the grub.cfg configuration file:

grub-mkconfig -o /boot/grub/grub.cfg

Now GRUB should be repaired, and you should be able to boot into your system again.

If you have more than one operating system installed on your machine, and enabled the usage of os-prober in your /etc/default/grub config, grub-mkconfig will scan for other IOS and add them to boot menu in case.

Repair GRUB on BIOS systems (older systems or legacy boot enabled CSM)

1. reinstall GRUB:

grub-install --target=i386-pc /dev/sdX

Remember, the X must be replaced with the letter that is marked in your situation, for instance, /dev/sda

2. Rebuild grub.cfg configuration file:

grub-mkconfig -o /boot/grub/grub.cfg

Now, GRUB is repaired, and you should be able to boot into your system again.

If you have more than one operating system installed on your machine, and enabled the usage of os-prober in your /etc/default/grub config, grub-mkconfig will scan for other OS and add them to boot menu in case.

[icon name="info" prefix="fas"]

Grub no longer has os-prober enabled per default:

https://wiki.archlinux.org/title/GRUB#Detecting_other_operating_systems

os-prober is troublesome in some cases, but it is used to autodetect other OS to add them to boot menu.

To re-enable os-prober usage for grub:

edit /etc/default/grub and change this:

GRUB_DISABLE_OS_PROBER=true
to false:
GRUB_DISABLE_OS_PROBER=false

save the file and regenerate grub.cfg again:

sudo grub-mkconfig -o /boot/grub/grub.cfg

Alternative to GRUB

There is an alternative for using GRUB, it is called rEFInd, and you can read more about it over here:

https://discovery.endeavouros.com/installation/how-to-install-refind/2021/03/

]]> 1588 0 0 0 Arch-chroot for Bios (legacy) systems]]> How to install rEFInd?]]> How to install rEFInd?]]> https://discovery.endeavouros.com/signature-and-keyring/pacman-keyring-issues/2021/03/ Wed, 24 Mar 2021 18:32:23 +0000 https://discovery.endeavouros.com/?p=1592

Written by Jonathon

If you’re getting an error similar to “Can’t update: signature from *** is marginal trust” or “invalid or corrupted package” you probably just need to update your package signing keys:

sudo pacman -Sy archlinux-keyring endeavouros-keyring
sudo pacman -Syu

Also make sure your system clock is correct!

Of course, it’s also possible that the package file actually is corrupt. Remove it from /var/cache/pacman/pkg/ so pacman will download it again.

If no package file is explicitly mentioned then you may have an incomplete download. Run sudo rm /var/cache/pacman/pkg/*.part to remove any partial downloads.

---

If you have any other errors, you can clear out the pacman keyring and start fresh:

sudo mv /etc/pacman.d/gnupg /root/pacman-key.bak
sudo pacman-key --init
sudo pacman-key --populate archlinux endeavouros
sudo pacman -Syy archlinux-keyring endeavouros-keyring
sudo pacman -Syyu

And if this still doesn’t work, and you trust that the packages are actually correct and not corrupt and haven’t been interfered with, then you can force (re)installation of the keyring packages:

sudo pacman -U /var/cache/pacman/pkg/{archlinux,endeavouros}-keyring*.pkg.tar.zst

then try again.

---

If you’re installing an AUR package a PGP key can be used to verify the source files. You will need to import this into your personal keyring before it can be verified. If you don’t you’ll get an error similar to:

[...]
llvm-5.0.0.src.tar.xz ... FAILED (unknown public key 0FC3042E345AD05D)
libcxx-5.0.0.src.tar.xz ... FAILED (unknown public key 0FC3042E345AD05D)
libcxxabi-5.0.0.src.tar.xz ... FAILED (unknown public key 0FC3042E345AD05D)
[...]

To “fix” this, simply import the key:

gpg --recv-key 0FC3042E345AD05D

]]> 1592 0 0 0 https://discovery.endeavouros.com/window-tiling-managers/i3-wm/2021/03/ Wed, 24 Mar 2021 18:52:30 +0000 https://discovery.endeavouros.com/?p=1594

EndeavourOS implementation:

The configuration Source for EndeavourOS initial configuration after fresh install:

https://github.com/endeavouros-team/endeavouros-i3wm-setup

endeavouros-i3wm-setup

maintainer: joekamprad ---> setup for i3-wm under EndeavourOS new config 2022 <---

Tutorial for i3-wm settings:

• background handled by feh
• gtk3 theme handled by lxappearance-gtk3
• Filebrowser = Thunar
• default Terminal-Emulator = xfce4-terminal
  • This is set also inside ~/.profile (export TERMINAL=xfce4-terminal) so remind to change it there too if you want to change4 default terminal.
• Text-Editor = xed
• dex : autostarting apps from /etc/xdg/autostart/ (*)
• Notifications are done with dunst: CONFIG FILE = ~/.config/dunst/dunstrc

dex is enabled by default in config to autostart like on a DE. To disable, comment out the line:

exec --no-startup-id dex --autostart --environment i3

inside ~/.config/i3/config.

Main shortcuts:

[mod] key is set to the win-key (or should i call it linkey?)

default EndeavourOS i3-wm keycodes:

Keybindings are different from the i3 defaults to fit into the setup.

There are 2 tools that helps you to check them:

The keyboard icon on panel open a little GUI helper and by pressing [F1]

Display setup with arandr

• open arandr and setup display/s as you need.
• save the setup from arandr menu or button exactly with filename monitor. ---> on i3 EndeavourOS we have a starter line in the ~/.config/i3/config

# start a script to setup displays
# put `monitor.sh` into the location specified by this line:
exec --no-startup-id ~/.screenlayout/monitor.sh

this will handle to set display on each login. alternatively, you could manually make a script with xrandr.

Tiling:

is set to default for i3wm and can be changed to:

• stacking: Only the focused window in the container is displayed. You get a list of windows at the top of the container.

• tabbed: so each new window will open fullscreen as a tab, you can change between window-tabs with mouse or shortcut: [mod]+Left focus left (left arrow key) [mod]+Right focus right (right arrow key)

i3blocks:

• pulseaudio (mousewheel volume level, rightclick open pulseaudio control)
• weather (openweather you need to get city code and apikey first [adding it to ~/.config/i3/scripts/openweather.sh]) get your api key here: https://openweathermap.org/appid and City code: https://openweathermap.org/find?q= (search your city and take the city code from the url in your browser [7 numbers at the end of the url])
• tray-icons (showing network-manager and update-icon)
• logout button (poweroff, logout, suspending, hibernate e.t.c.)

panel bar (i3-blocks):

• CONFIG FILE = ~/.config/i3/i3blocks.conf

Logout Menu (rofi):

• CONFIG FILE = ~/.config/i3/scripts/powermenu

application menu (rofi):

• rofi color-schemes: ~/.config/rofi/arc_dark_transparent_colors.rasi

power-profiles handler menu:

• let you easely switch powermodes from the i3-bar.

theming/colorshemes:

for rofi menus (application menu and Logout menu):

They can be adjust and chenged inside ~/.config/rofi directory:

Configurations for the menus:

• ~/.config/rofi/rofidmenu.rasi
• ~/.config/rofi/powermenu.rasi

colorschemes:

• ~/.config/rofi/arc_dark_transparent_colors.rasi
• ~/.config/rofi/arc_dark_colors-ori.rasi

colors are in rgba calling transparency in the last colum:

rgba ( 26, 28, 35, 100 % )

General theming // gtk3 and icons:

• ~/.config/gtk-3.0
• ~/.Xresources
  There is installed where you can browse and set GTK3 theme, icons and Xcursortheme.
  But Xcursor needs to be set inside the ~/.Xresources manually if you change it in LXAppearance to get applied for all apps.

Tutorial to install EndeavourOS-i3 setup from scratch

for later installs, if you have installed another DE on initial install from the ISO

1. get the dot files:

git clone https://github.com/endeavouros-team/endeavouros-i3wm-setup.git

cd endeavouros-i3wm-setup

2. copy files to the right directories (.config of your user):

cp .Xresources ~/.Xresources

cp -R .config/* ~/.config/

3. Scripts inside ~/.config/i3/scripts must be executable:

chmod -R +x ~/.config/i3/scripts

4. set theming for xed texteditor:

dbus-launch dconf load / < xed.dconf

5. install needed packages:

wget https://raw.githubusercontent.com/endeavouros-team/EndeavourOS-packages-lists/master/i3

sudo pacman -S --needed - < i3

or use the packages tool from our repo: eos-packagelist --install "i3-Window-Manager"

Use the i3_install script from the git for automatic install it to your users home: This script will setup configurations needed and install all needed packages:

wget https://raw.githubusercontent.com/endeavouros-team/endeavouros-i3wm-setup/main/i3_install and run it: ./i3_install

warning i3_install will overwrite existing files Make sure you backup users configs before running it on your own.

screenshot:

https://youtu.be/dwSHX-pEe3o

---

Links:

I3 docs:

https://i3wm.org/docs/

Sources for EndeavourOS i3wm setup:

https://github.com/endeavouros-team/endeavouros-i3wm-setup

If you have a question ask at our Forum:

https://forum.endeavouros.com/c/desktop-environments/i3wm/23

]]> 1594 0 0 0 https://discovery.endeavouros.com/arm/homeserver-automatically-mount-server-at-log-in/2021/03/ Wed, 24 Mar 2021 18:55:39 +0000 https://discovery.endeavouros.com/?p=1596

By Pudge

It would be nice to have AutoMountServer run every time you log in.
Here is how to do this in XFCE, but most Desktop Managers have a GUI for Auto Startup

click on the Start button in the panel, click on “Settings”, click on “Session and Startup”
Select “Application Autostart” and hit the +Add.
Name: MountServer
Description: Auto Mount enosServer
Command: Navigate to /home/$USER/bin/AutoMountServer.sh
Trigger: on login

Reboot, and enosServer should be automatically mounted at login. Extremely simple for any
level of Linux user. Once set up for a user, all that user has to do is log in and enosServer is
ready to use. Using a File Manager, check that enosServer is mounted.

This is how I set up my server access for my convenience.

The variations are many. If you don’t want the server mounted without entering a password, then don’t create any SSH keys. Now when the server is auto-mounted or mounted by clicking on the launcher, you will be prompted for pshare’s password.

If you don’t want the server to auto-mount at login, don’t add it to Session and Startup. With no SSH Keys and no auto-mount at log in, the server would not mount until you manually launched it and then entered the password.

At least in LibreOffice, if someone else has a file open when you try to open it you get:

This is a good thing if multiple people in the household share files. If this happens, I would suggest clicking Cancel.

Try to avoid shutting down the computer with a file open on the server. Next time you try to open that file, you may get a similar warning as above saying the file is locked for editing by you. Improper shut downs can leave a lot of things hanging.

Configure any other Linux machines you have exactly like we did this one. Yes, all Linux Client machines will mount the server as user pshare. You could create different users on the server that match the user names of all users accessing the server. In fact, that is what you would want to do in an Enterprise environment. But that can make administration a nightmare, plus this can cause a lot of permission problems between users. We want to keep our home file server as KISS as possible. This way every file and every directory on the server will have pshare as the owner and pshare as group.

When we set up the Samba server, we will mount SMB shares as user pshare. That way when someone writes files from a Windows machine, the files will still have pshare as the owner and pshare as a group.

Everything will be very homogeneous on the Data Drive. Out of the box, SSH will allow up to ten simultaneous connections per SSH server IP address, in this case 192.168.0.1.150. Most households don’t have ten Linux boxes. But if you need more, edit the sshd_config file on the server and change MaxSessions to something higher than ten. I don’t know how many simultaneous SSH sessions a single user (pshare) can have, but I have never exceeded it so far.

As an experiment, I had 3 Windows computers and 4 Linux computers simultaneously on the server, all 7 streaming music, and performing other server tasks. The server never missed a beat. For a simple home server, it works great.

]]> 1596 0 0 0 https://discovery.endeavouros.com/arm/homeserver-use-fuse-and-sshfs-to-view-server-data-in-a-file-manager/2021/03/ Wed, 24 Mar 2021 18:57:59 +0000 https://discovery.endeavouros.com/?p=1598

By Pudge

Now we will set up FUSE and sshfs to utilize a terminal window to access the files on the server.
In the Linux CLIENT COMPUTER open a terminal window, as user install sshfs.

$ sudo pacman -S --needed sshfs

Make a new directory to act as a mount point

$ mkdir /home/$USER/enosServer

The /home/$USER/enosServer directory is a Mount Point for the enosServer. You should never add any directories or files locally in this directory. If enosServer is not mounted, the enosServer directory should always be empty.

Here is the part you’ve been waiting for. In the CLIENT Linux computer, as user

$ sshfs pshare@enosServer:/server /home/$USER/enosServer

It should complete without any errors.

Launch your file manager, then Click on Home and click on enosServer. You should see the lost+found directory that was created when the DATA SSD was formatted. Ideally, the enosServer folder should have nothing but subfolders to organize your data.

Eventually, as the enosServer folder is filled up, it could look something like this.

Also notice in the left column under the DEVICES, the enosServer Icon. Click on that, or click on username under PLACES then click on enosServer folder. Under DEVICES the enosServer Icon also has a unmount icon at the right side. DO NOT try to unmount the enosServer by clicking on this.

sshfs uses the FUSE kernel module to fool your client computer into thinking the /server directory on enosServer is a local directory named /home/$USER/enosServer. Anything you can do on a local directory, you can now do on the remote computer’s directory.

This is how you will manage the content on the enosServer’s DATA drive. Add files, delete files, add /delete folders just like you do on your local Drive.

So, manage data files with sshfs, and do maintenance on the Operating System by using ssh pshare@enosServer. Once set up maintenance is usually just doing updates with pacman -Syu and data backups.

Use the following to unmount enosServer. In the Client computer terminal type in the following:

$ fusermount -u /home/$USER/enosServer

Direct your terminal manager to the /home/$USER/enosServer directory, and it should be empty. Because
there isn’t a remote directory mounted there anymore.

AUTOMATE THE MOUNTING PROCESS

This is all fine and dandy, but who wants to type in these commands all the time, much less remember the exact Syntax for the commands? Let’s automate this process. Here are the instructions for XFCE, it should be doable in Most Desktop Environments.

Mount enosServer with a desktop launcher

In the client computer as user in user’s home directory

$ ls -l /home/$USER
drwx------. 2 username username 4096 Jan 31 20:34 bin

Look for a directory named bin. If bin doesn’t appear, use mkdir to create one

$ mkdir /home/$USER/bin

After creating bin, you may want to change the permissions for security reasons

$ chmod 700 /home/$USER/bin
$ cd /home/$USER/bin

Using your favorite text editor, create a file named AutoMountServer.sh and add these lines

$ vi /home/$USER/bin/AutoMountServer.sh
#!/bin/bash
sshfs pshare@enosServer:/server /home/$USER/enosServer
exit

Type in exit as the last line of the file, then close the file

$ chmod 754 /home/$USER/bin/AutoMountServer.sh
$ ls -l /home/$USER/bin
-rwxr-xr- - don don 47 Jan 8 AutoMountServer.sh
$ sudo pacman -Syu --needed alacarte

On the Desktop, click on Start button at the left of the panel. Go to Settings – Main Menu
In the left-hand column, select System – then click on + New Item

Fill in Name: with what ever you want to call this launcher
Fill in Command: Browse to /home/username/bin/AutoMountServer.sh
Fill in Comment: with whatever you want
Launch in Terminal? Leave it unchecked
Click on image at the left and navigate to a desired icon

+ Other Locations – Computer – usr – share – icons – Adwatia – 32×32 – devices – drive-harddisk.png

select the icon, back in Launcher Properties click OK
For convenience, highlight AutoMount Server. then click on ^Move up until it is the first entry at the top.

Log off, then Log in so XFCE4 can detect the changes.
/home/$USER/enosServer should be empty.
Click on the Start button – System – AutoMountServer
The server should be mounted on the enosServer directory
You could right-click on the launcher and add it to the Desktop or the Panel.

]]> 1598 0 0 0 https://discovery.endeavouros.com/arm/homeserver-set-up-a-linux-client-computer/2021/03/ Wed, 24 Mar 2021 19:00:09 +0000 https://discovery.endeavouros.com/?p=1600

By Pudge

On a CLIENT Linux Computer with a Desktop Environment or Window Manager, open a terminal window. Use the static IP address you established for the server and the hostname you decided on. This will establish the route to the server. For configuration files owned by root, use vi or nano to edit these files.

Add the following line to the end of /etc/hosts Your info may be different from the example.

$ sudo nano /etc/hosts
192.168.0.150  enosServer.localdomain    enosServer

This establishes a relationship between the hostname of enosServer and it’s IP address, kind of like a DNS service. Otherwise, you would have to address the server by it’s IP address and port number, which can be awkward and hard to remember.

Since the SSH port that the enosServer listens on was changed from the default port 22, the Client computer needs to know which port to use.

$ sudo nano /etc/ssh/ssh_config 

(change the following line.)
FROM
#Port 22
TO
Port 9XXX
(Use the same port # as in the server)

Connect to enosServer with SSH

In a terminal window, as a user try to connect to enosServer

$ ssh pshare@enosServer
(if you happen to be at root, don't try to SSH as root)

If you successfully communicated with enosServer, you will get something similar to:

The authenticity of host '[enosserver]:9XXX ([192.168.0.XXX]:9XXX)' can't be established.
ECDSA key fingerprint is 54:fa:20:25:c1:91:d3:3d:4c:8c:47:02:32:f2:5e:8e.
Are you sure you want to continue connecting (yes/no)?

The above dialogue is a one-time thing. Type in “yes”, the connection should be completed and you will be asked for pshare’s password. You should then have a terminal prompt of

[pshare@enosServer ~]$

You are now logged into enosServer as user pshare. Pay attention to the prompt, it will always let you know which computer you are in and the user name. The SSH server on enosServer was configured to NOT allow login as root. If you need to use root for administration, type in su and enter your server’s root password. Anything you type in the Terminal window will now be executed in the enosServer computer. You can execute
pacman -Syu or perform other administrative routines. Type in

# exit            (if you are in as root)
$ exit            (exit again as user)
(This is the proper way to log out of a network connection.)

You should be back to your client computers prompt. On the LINUX Client Computer, do not terminate your enosServer session by clicking on the X (close) button at the top right of your terminal window. After properly disconnecting from the enosServer you should return to your local prompt in the terminal window. Now you can close your Client side terminal window by typing in exit once more.

SSH into enosServer and bypass the password

This is all and good, but it is a pain to have to enter the password all the time. Now ssh keys may need to be generated in our client computer as user.

$ ls -l .ssh
     -rw-------. 1 don don 1831 Jun 8 2019 id_something
     -rw-r--r--. 1 don don 406 Jun 8 2019 id_something.pub

If the ls -l command produces the above results, you already have ssh keys. You can skip the next section. If you don’t have ssh keys, enter the following commands. For "message" you can use the computer's hostname or any message that will easily
Identify your Client computer.

$ ssh-keygen -t ed25519 -C "message"
(create ssh keys for user, hit enter 3 times for defaults )

$ ls -al
     drwx------ don don 4096 Jan 5 1309 .ssh

( .ssh should be drwx------ if not $ chmod 700 .ssh then recheck)

$ ls -l .ssh
     -rw-------. 1 don don 1831 Jun 8 2019 id_ed25519
     -rw-r--r--. 1 don don 406 Jun 8 2019 id_ed25519.pub

The id_ed25519 file is your PRIVATE SSH Key and you should never do anything with it. Don’t copy, move, or otherwise mess with it. Just leave it alone. The id_ed25519.pub file is your PUBLIC SSH Key. We need to export your PUBLIC SSH Key to the enosServer.

In a terminal as user

$ ssh-copy-id -i ~/.ssh/id_ed25519.pub pshare@enosServer

enter pshare’s password when requested.
You will be returned to your client’s prompt. Now try to log into enosServer

$ ssh pshare@enosServer

You should now be logged in to enosServer as pshare without having to enter your password. To do administration, just ssh into the server from a client terminal window. Once in enosServer change to root and do most anything you want from a nice GUI terminal window with mouse, scroll bars, cut and paste, etc. The server and client are now configured to remotely administer the server.

[pshare@enosServer ~]$ exit

repeat exit until back in the client computer.

Go to the next tutorial in the series:
Homeserver 2 - Use FUSE and SSHFS to view server data in a file manager

]]> 1600 0 0 0 https://discovery.endeavouros.com/window-tiling-managers/bspwm-2/2021/03/ Sun, 28 Mar 2021 14:04:16 +0000 https://discovery.endeavouros.com/?p=1734

By Flying cakes

Bspwm is Binary Space Partitioning Window Manager. This is a tiling window manager. If you come from a traditional desktop environment like Xfce, you notice that the primary way of managing open windows is the mouse. Those are floating window managers.

Then there are tiling window managers, where all windows are visible on the desktop and are automatically arranged so as to fill the complete screen real estate. A tiling window manager doesn’t mean it needs to be controlled via the keyboard, however, the way they function, it is very efficient to use keyboard shortcuts to control your windows.

Bspwm only manages your windows. The keyboard shortcuts are handled by a different program called sxhkd. This is different from i3wm, where the window manager manages your keyboard shortcuts also.

Functioning

bspwm is a tiling window manager that represents windows as the leaves of a full binary tree.

bspc is a program that writes messages on bspwm’s socket.

When a program is run, it is placed in a tree, splitting the current branch. Windows can have 4 states - tiled, pseudo_tiled, floating and full screen.

• Tiled means the window’s size will fill up the maximum area possible without overlapping other windows around it. It will stay in it’s set location based on it’s position in the window tree.
• Pseudo Tiled is the same as tiled except the window can be resized at will. The position stays the same though.
• Floating means the window can be placed anywhere on the desktop and resized at will.
• Fullscreen is pretty self explanatory.

Configuration

Bspwm settings are modified via running shell commands. If you run the same commands every time bspwm starts up, you will get the same configuration. You surely do want some commands to be run whenever bspwm starts, like window border related settings, startup apps etc. These are defined in ~/.config/bspwm/bspwmrc. This file will contain the bspc commands that will be run at startup. It is actually a shell script that bspwm runs at startup so you can put any other shell command you want. You can also use loops, if-else constructs in case you want to do something complex and fancy. (like applying different settings based on the display resolution - that way you can run the same config file across all your systems and still get pixel values tailored to the specific monitor it runs on).

Keybindings are defined in ~/.config/sxhkd/sxhkdrc. Apart from bspwm related keybindings, you can also put keybindings for commonly used commands. For eg. I am usually ssh-ing into a system on my network, so I add a command to open terminal and run the ssh command. This is bound to a keyboard shortcut. You can also bind shortcuts to launch commonly used applications. Another thing I recommend binding is the music controls if you use Mpd.

Its totally up to you. Different people have different uses and you can bind whatever you regularly use. Makes your workflow faster.

Bspwm is very feature rich. This is just an introduction; look up on the internet for lot more things you can do with it.

Extra reading :

1. Readme at https://github.com/baskerville/bspwm 1 explains well how windows are managed.
2. https://github.com/IntrepidPig/bspwm-doc/blob/master/getting-started.md

Polybar

The official wiki on their GitHub is pretty good. You just need to copy-paste the relevant module code in your config file and change the values of variables.

In the config bundled with our Bspwm edition, there is a section at the beginning where all the colors are defined. You can directly put in hex codes wherever a color value is required, but having them all defined at one place as variables make it a bit easier to manage.

How it works?

Polybar config consists of bar definitions and module definitions. You can have multiple bars defined in one config file. Each bar has settings about its size, border, padding, position etc.

Modules are the units that you place on the bar. They can show basic system info like CPU usage, Ram usage, or WM related info like workspaces. You can also create custom modules to show the output of a script on the bar.

Each bar can have one or more modules place in one of the three alignments - left, center or right. (modules-left, modules-center and modules-right) The bar does not need to have all the modules place on it. You can define many modules and use only a few of them if you like. In fact, the Polybar config with our Bspwm edition has three modules that are defined but are not there on the bar by default.

Start/Re-start Polybar

Polybar can be started from the terminal using the command below:

polybar [bar-name] -c /path/to/config 

Add the -r flag if you are editing/testing config. This flag makes polybar automatically restart when the config file is updated.

In our Bspwm edition, we have used a launch script to first terminate any running instances of polybar and then start a new instance of polybar. The file can be seen here on GitHub.

So if you’re running our configs, then all you need to do is to run ~/.config/polybar/launch.sh in a terminal.

System Tray

In Polybar, system tray is not a module. It can be aligned to left, right or center. But it cannot be positioned between other modules. Also, you will notice that it is not there in active modules list. System tray is enabled by adding a value to tray-position property.

Disabled modules

In the Bspwm edition, there are some disabled modules. I added them because many people like to use it, but kept them disabled since its not something I wanted on a default config. To enable them, you just need to add the corresponding module name where the active modules are listed.

• Network speed indicator - Displays real-time network speed on the bar. You need to set the correct interface name for your network in the module definition. (modules are defined in the same config file).
  Module name is netspeed. Add this to the modules list and restart Polybar.
• Mpd Info - Shows current playing track info in Artist - Track format. You need to have a running Mpd instance. In the module definition, you need to set the correct host and port for Mpd.
  Module name is mpd.
  Note that Mpd or its configs are not bundled with our Bspwm edition. If you are new to Mpd and want to set it up, you can read the relevant Arch Wiki entry, or create a thread on our forum. I’ll be happy to help you in case you face any roadblocks.
• Mpd Controls - Shows previous, play/pause, next button to control music playback via Mpd. Again, you need to set the correct host and port in the module definition.
  Module name is mpd_control.
• Pending Updates - This module shows a number on your bar indicating the number of packages that can be updated.
  Module name is checkupdates.
  Note that this module is different from the eos-update-notifier.

For PC Users

Our config comes with a backlight and battery module by default. They are for laptop users. On a PC with AC supply, those modules are automatically disabled by Polybar on startup. So you don’t need to worry about having redundant modules on your bar. You can go ahead and remove them too if you like.

Extra Modules

There are GitHub repositories that collect user-written modules/scripts that are meant to be used with Polybar.
Two such popular repos are polybar/polybar-scripts and TiagoDanin/Awesome-Polybar.

External links:

1. Polybar Wiki Home: https://github.com/polybar/polybar/wiki
2. https://github.com/polybar/polybar-scripts
3. https://github.com/TiagoDanin/Awesome-Polybar

More Configs

Rofi

Rofi is used to show the app launcher and powermenu. Rofi settings are defined in ~/.config/rofi/config.rasi. The default config is pretty basic and you can customize Rofi very much.

Powermenu script is in the same folder, with name powermenu.sh. At the beginning of script, you have the options defined as variables. You may edit them if you want a different icon or different text for the options. This script also lets you change the order in which the options are displayed, by changing the order in echo statement.

Dunst

Dunst shows your notifications. Config is located in ~/.config/dunst/dunstrc. You can change the colors, position etc.

One important setting you may want to change is the binding for Ctrl + grave. By default, this is used to show notification history. Useful in case you miss a notification or want to see the details again. The keybinding may conflict with other applications. For example, the same keybinding is also used in Code-OSS/VSCode. To disable the behaviour in dunst, open dunstrc file and comment out line 270.
https://github.com/EndeavourOS-Community-Editions/bspwm/blob/main/.config/dunst/dunstrc#L270
To comment it, you simply put a pound symbol at beginning of line.

Wallpapers

We use Nitrogen to set/change wallpaper.

To change the wallpaper, open Nitrogen application. Click on "Preferences" and on the pop up, add your wallpaper directory to the list. Save it and now Nitrogen will display your wallpapers from which you can choose the one to set.

In case you want to use a different application to set wallpaper, open ~/.config/bspwm/bspwmrc file and comment out or remove the line that says nitrogen --restore &. Then you can go forward to setting up whichever wallpaper setter you want to use.

Transparency/ Compositor

We use picom for compositing. Config file is ~/.config/picom.conf. You may want to change the transparency values or enable background blur.

Resolution and Arandr

When you log in for first time, resolution may be too less. You can use “Change Display Resolution” on welcome app. Resolution will increase, but you need to reload Bspwm now. Press Mod+Alt+r.

To make it permanent, open Arandr, and save your resolution (last button on toolbar). Save it in ~/.screenlayout/ as file name monitor.sh

Now when you reboot and log in, your resolution will be reloaded.

]]> 1734 0 0 0 https://discovery.endeavouros.com/applications/flatpak-tweaking-the-visuals/2021/03/ Mon, 29 Mar 2021 14:39:57 +0000 https://discovery.endeavouros.com/?p=1758

One of the downsides to using Flatpaks instead of traditional applications is theming. Sometimes the theme used by the application does not always match the system theme. This is caused by the Flatpak application running in its own container. There are a couple of options available to the user to correct this issue.

Option #1 – Install a theme directly from the Flathub repository.

This is the officially support method of theming a Flatpak application. There are, at the time writing, 201 of the most common GTK themes available in the Flathub repository. To list the themes available, open a terminal and type the following:

flatpak remote-ls flathub | grep org.gtk.Gtk3theme

This will list all the themes available in the Flathub repository. Read through the list and install the theme that matches the system theme in use.

Important: The theme installed using this method must be the same as the system theme. If a different theme is installed, the Flatpak application will use its default theme of Adwaita.

Example

For this example, the system theme in use is the Greybird-Geeko Dark theme.

1. Open a terminal and type:

flatpak remote-ls flathub | grep org.gtk.Gtk3theme

You will see a screen similar to the following. I have edited the results to keep this article short.

[mark@FX504GD ~]$ flatpak remote-ls | grep org.gtk.Gtk3theme
Adapta-Brila-Eta Gtk+ theme org.gtk.Gtk3theme.Adapta-Brila-Eta 3.22 x86_64
Adapta-Brila Gtk+ theme org.gtk.Gtk3theme.Adapta-Brila 3.22 x86_64
Adapta-Eta Gtk+ theme org.gtk.Gtk3theme.Adapta-Eta 3.22 x86_64
Adapta-Nokto-Eta Gtk+ theme org.gtk.Gtk3theme.Adapta-Nokto-Eta 3.22 x86_64
....... (edited)
Flat-Remix-GTK-Yellow org.gtk.Gtk3theme.Flat-Remix-GTK-Yellow 3.22 x86_64
Greybird-Geeko GTK+ Theme org.gtk.Gtk3theme.Greybird-Geeko-Dark 3.22 x86_64
Greybird-Geeko GTK+ Theme org.gtk.Gtk3theme.Greybird-Geeko-Light 3.22 x86_64
Greybird-dark GTK+ Theme org.gtk.Gtk3theme.Greybird-dark 3.22 x86_64
....... (edited)
Deepin Gtk+ theme (dark) org.gtk.Gtk3theme.deepin-dark 3.22 x86_64
Deepin Gtk+ theme org.gtk.Gtk3theme.deepin 3.22 x86_64
elementary stylesheet org.gtk.Gtk3theme.elementary 3.22 x86_64

2. Find the theme that matches the system theme and install it by typing:

flatpak install org.gtk.Gtk3theme.Graybird-Geeko-Dark

3. (Optional) Log out or reboot the computer. Sometimes this is needed to make sure that the theme is applied properly to the Flatpak application.

The visual theme used by the Flatpak application should now look the same as the system theme in use.

Option #2 – Use a script to copy the needed theme information to the Flatpak application’s folder directly.

If the theme used by the system is not available from the Flathub repository, there is another option available. One can use a script to copy the needed settings to the Flatpak application’s folder.¹ This script only needs to be run once and it will apply the fix to all Flatpak applications installed on the system.

Warning: This method is not officially supported by the developers of Flatpaks. Use at your own risk.

1. Open your favorite text editor.

2. Copy the below text and paste it into your text editor.

#!/usr/bin/env bash

for dir in $HOME/.var/app/*/
do
    confdir="${dir}config/gtk-3.0"
    mkdir -p $confdir
    cp $HOME/.config/gtk-3.0/settings.ini $confdir/settings.ini
done

3. Save the file in the home folder as flatheme.sh

4. Make the script executable so it can be used. Open a terminal and type:

chmod a+x flatheme.sh

5. Run the script by typing ./flatheme.sh

Now when a Flatpak application is run, it will use the same theme as the system theme.

NOTE: This script needs to be run every time a new Flatpak application is installed. It does not need to be run when existing Flatpak applications are updated.

Doing one of the above solutions should allow Flatpak applications to blend in with traditionally installed applications. However, these will not “fix” parts of an application’s interface that are not modified by the chosen theme. In those cases, the Flatpak application will do the same thing as traditionally installed applications and use the system default theme settings.

¹Thank you to GitHub user abiosoft for this script. The original script can be found at https://github.com/abiosoft/dotfiles/blob/master/flatpak/fixflatpaktheme.sh

]]> 1758 0 0 0 https://discovery.endeavouros.com/applications/flatpak-enabling-and-application-management/2021/03/ Mon, 29 Mar 2021 14:44:07 +0000 https://discovery.endeavouros.com/?p=1760

Installing Flatpak Support

Because Flatpak support is not installed by default, some package installation from the repositories and configuration must be done first.

1. Open a terminal and make sure your installation is up to date by typing:

sudo pacman -Syu

2. Once the update is complete, we need to install Flatpak support.

sudo pacman -S flatpak

Be aware to check the right xdg-desktop-platform package in the install process!

In cases on some Desktops (aside from Gnome and KDE) it will install xdg-desktop-platform-gnome as default selected, and you ma yneed the one fitting your Desktop/WM in use.

[icon name="flag" prefix="fas"]

xdg-desktop-portal-gnome will only work on GNOME Desktops and can cause a lot of issues in other Desktops!

3. To make installation of software easier, we need to add the default Flatpak repository. Please note that sudo is no longer needed. If sudo is used, the user will not have access to the repository or any applications that are installed.

flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo

Unlike Snaps, developers can host their own repository. It can be added by doing the following command.

flatpak remote-add --if-not-exists (repository name) (repository url)

Make sure to replace the items enclosed in brackets with the required information. For example:

flatpak remote-add --if-not-exists fubar https://dl.fubar.edu/repo/fubarrepo

4. Restart the system to have the Flatpak support enabled.

systemctl reboot

Installing Applications

Now you are ready to install a Flatpak application. To do this, we need to know the name of the package you want to install. For this example, we will be installing the Spotify application.

1. To find the name of the package, open a terminal and type:

flatpak search spotify

The result will look similar to this:

[mark@FX504GD ~]$ flatpak search spotify
Name               Description                    Application ID               Version    Branch Remotes
Spotify            Online music streaming service com.spotify.Client           1.1.42.622 stable flathub
nuclear music pla… A electron based music player  org.js.nuclear.Nuclear       0.6.6      stable flathub
Clementine Music … Plays music files and Interne… …lementine_player.Clementine 1.4.0rc2   stable flathub
Tauon Music Box    Play your music collection wi… com.github.taiko2k.tauonmb   6.4.2      stable flathub

From the search results, we see that the package name for Spotify is com.spotify.Client

You can also go to the Flathub website, https://flathub.org/home, and search for the application there. On the application’s page, it will list the name of the package for that program.

2. Now that we know the name of the package, we can install it by typing:

flatpak install com.spotify.Client

Remember, do not use sudo when running the above command. If root privileges are needed for the install, you will be prompted to enter your root password.

3. You can now run the program in the normal manner from your programs menu.

NOTE:

During the install process, an icon for the program should be placed in your programs menu. If it does not, you may need to run the program from the terminal one time. To do this, in the terminal type:

flatpak run com.spotify.Client

This should place an icon in the programs menu. If it does not, a log out or a reboot may be required.

Updating and Uninstalling Applications

To update an application installed using Flatpak, open a terminal and type:

flatpak update

This will update all Flatpak applications and their related libraries.

To uninstall an application installed using Flatpak, open a terminal and type:

flatpak uninstall (application package name)

For our example using Spotify, we would type:

flatpak uninstall com.spotify.Client

More Information

The steps above are only the basics needed to install and manage Flatpak applications on a system. For more information, take a look at the Flatpak Command Reference located here: https://docs.flatpak.org/en/latest/flatpak-command-reference.html

]]> 1760 0 0 0 https://discovery.endeavouros.com/arm/installing-an-external-ssd-for-the-home-partition-manual/2021/03/ Mon, 29 Mar 2021 15:10:46 +0000 https://discovery.endeavouros.com/?p=1764

Here are the instructions to install an external USB SSD enclosure as your /home directory on your new EndeavourOS SBC.

Install a SSD in a USB 3 enclosure as an external home partition. This SSD can be any size you want. Then this USB 3 SSD can be mounted during boot up in /etc/fstab as /home. This also makes this data easily backed up with rsync along with config files.

Power off the computer and connect a USB 3 external enclosure with a SSD installed.

IMPORTANT: To transfer the contents of /home then empty /home, there should not be anyone logged into a Desktop Environment. Way too many conflicts if someone is logged in.

Boot the computer, at the Desktop Manager, do NOT login.

Press Ctrl-ALT-F2 to open a Console window (tty2).

Login to the console window as root and enter your root password.

# lb (Odroid N2 & RPi4 will look similar to this, Odroid XU4 will have one mmcblk partition)

NAME FSTYPE FSSIZE LABEL MOUNTPOINT

sda

└─sda1 ext4 XXXXX

mmcblk0

├──mmcblk0p1 vfat 252M BOOT /boot

└──mmcblk0p2 ext4 56.8G ROOT /

/dev/mmcblk0 is our OS device. The /dev/sda is our target device. If the SSD device is brand new and has never been partitioned it may look different. Now we have determined that /dev/sda is our new device (your setup may be different such as /dev/sdb etc)

/dev/sda1 should not show a MOUNTPOINT. It is remotely possible /dev/sda1 will be mounted and show a mount point. If so, we have to un-mount it, and any other partition on /dev/sda that shows up as being mounted. Such as possibly /dev/sda2, /dev/sda3, etc. until all are un-mounted. Of course, do not un-mount anything on mmcblk1.

# umount /dev/sda1 and possibly # umount /dev/sda2 etc. (If necessary)

Next partition the USB SSD as one partition that uses all the space in the SSD

CAUTION: This WILL erase ALL DATA on your SSD.

# fdisk /dev/sda ( or adjust to /dev/sdb or whatever is relevant )

Command o (That's lower case o...create a new empty DOS partition table)

Command n (add a new partition)

Partition type: p (p = primary)

partition number: 1

First sector: enter to accept default

Last sector: enter to accept default

Partition #1 contains a ext4 signature. (this warning may not appear, if so yes)

do you want to remove the signature? yes

Command: w (write table to disk and exit)

# mkfs.ext4 -L HOME /dev/sda1 (format our new partition to ext4, -L HOME is the label)

Now that /dev/sda is partitioned and formatted, we need to mount it on /mnt

# mount -t ext4 /dev/sda1 /mnt

# la /mnt (should see the directory lost+found created by mkfs.ext4 )

# rm -rf /mnt/lost+found

# la /mnt ( should see lost+found has been removed )

# cp -rp /home/* /var (make a backup of your current home directory or directories)

# cp -rp /home/* /mnt (copy contents of home to /mnt using recursive & preserve options)

# la /mnt/username ( should see the copied contents of home )

# rm -rf /home/* (empty the original home folder to be used as a mount point)

# la /home ( home should be empty, if not repeat above command)

# umount /dev/sda1 ( un-mount /dev/sda1 from mount point /mnt )

# mount -t ext4 /dev/sda1 /home ( mount /dev/sda1 to now empty home folder)

# la /home/username ( should see the home directories and dot files )

Modify /etc/fstab

Now that the dirty work is done, finish this up by exiting out of the console window.

Switch to the GUI mode by pressing Ctrl-Alt-F7, F6 , or maybe F1. Log into the desktop.

Open a terminal window

$ su then enter root password

# cp /etc/fstab /etc/fstab.orig (backup fstab)

Find the UUID for the home SSD partition.

# lsblk -f /dev/sda

NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT

sda

└─sda1 ext4 1.0 HOME b6bd3cd3-c666-4259-9ad9-125a003ff231 221.7G 0%

you should see /dev/sda1 with a nice label of "HOME" and its UUID number.

Highlight the UUID number, then right click and click copy.

Using your favorite text editor, add the following line at the end of the /etc/fstab file

# gedit /etc/fstab &

UUID=PASTE-Your-UUID-Number /home ext4 defaults,noatime 0 2

# mount -a (should show no errors if fstab is correct, if not edit /etc/fstab again)

# lb /dev/sda1 (should show our new /home )

NAME FSTYPE FSSIZE LABEL MOUNTPOINT

sda1 ext4 457.4G HOME /home

Reboot the computer and log into your Desktop.

After reboot, in a terminal window

$ lb /dev/sda1

NAME FSTYPE FSSIZE LABEL MOUNTPOINT

sda1 ext4 457.4G HOME /home

I would recommend removing the home directory backup(s) from /var.

This frees up storage space and it is better security to not have your home directory in /var.

From now on the home folder will be on the SSD. The SBC device and the USB external SSD enclosure are now married and should always be used together.

]]> 1764 0 0 0 https://discovery.endeavouros.com/arm/an-endeavouros-based-simple-home-server/2021/03/ Mon, 29 Mar 2021 15:23:03 +0000 https://discovery.endeavouros.com/?p=1766

Backing up enosServer.

Preparing an External Storage Device

rsync should have been installed during OS installation. If the external DATA SSD was partitioned, formatted, and mounted by the script, then the /serverbkup mount point should have been created.

From a Linux client Computer, ssh into enosServer and login as root

# pacman -Q rsync (should list rsync as installed, if not install with pacman)

rsync 3.2.2-2

Partition and format the BKUP USB3 SSD

Ideally, the external USB 3 backup SSD drive should be the same size as the DATA SSD drive. If you try to rsync a 500 GB SSD with 130 GB of data on it TO a 250 GB backup SSD, things will not go well. Even though the data to be backed up is less than the 250 GB BKUP SSD. Trust me on this. The backup SSD must be the same size or larger than the DATA SSD.

Connect the external USB 3.0 backup SSD to the enosServer SBC.

# lsblk -f

NAME FSTYPE FSSIZE LABEL MOUNTPOINT

sda

└─sda1 ext4 233.7G DATA /server

sdb

└─sdb1 ext4 XXXG XXXX

mmcblk1

└─mmcblk1p1 ext4 58.3G Odroid-XU4 /

The Micro SD card or eMMC card has a partition mmcblk1p1 labeled Odroid-XU4 and has a mount point of / (root). That is the partition that contains the OS.

The device named sda has a partition of sda1 labeled DATA and has a mount point of /server. That is the DATA SSD.

The device named sdb has a partition of sdb1 with a random label and no mount point. That will become our BKUP SSD. Take note of the SSD’s name. In this case sdb. Yours may be slightly different.

Format the external USB 3 BKUP SSD

# fdisk /dev/sdb (change device name if necessary)

Command: o (thats lower case letter o --create an new empty DOS partition table)

Command: n (add a new partition)

Partition type: p (primary partition)

Partition number: 1 (first partition)

First sector: (Enter to accept default)

Last sector: (Enter to accept default)

Partition #1 contains a xxxx signature. (this warning may not appear, if so yes)

Do you want to remove the signature? yes

Command: w (write table to disk and exit)

# mkfs.ext4 -L BKUP /dev/sdb1 (the -L option sets the volume label for the partition)

The BKUP USB 3 SSD is now partitioned as a single partition and formatted to ext4.

# mount -t ext4 /dev/sdb1 /serverbkup

# ls -l /

drwxrwxr-- root users server (edited for clarity)

drwxrwxr-- root users serverbkup

IMPORTANT:

Check /server and /serverbkup for ownership (root users) and permissions drwxrwxr--

If /serverbkup does not exist

# mkdir /serverbkup

If the permissions and ownership are incorrect:

# chown root:users /serverbkup

# chmod 774 /serverbkup

# lb

NAME FSTYPE FSSIZE LABEL MOUNTPOINT

sda

└─sda1 ext4 233.7G DATA /server

sdb

└─sdb1 ext4 228.2G BKUP /serverbkup

mmcblk1

└─mmcblk1p1 ext4 58.3G Odroid-XU4 /

The BKUP SSD is now ready to use for backups. To clean things up for the next step.

# umount /serverbkup

Next, on it’s own page so it makes a good cheat sheet, Performing a Backup.

PERFORMING A BACKUP OF THE DATA DRIVE

To do a backup connect the external BKUP SSD drive to an available USB port.

In a Linux client computer, ssh into enosServer as root.

# ll /server

should show a bunch of folders on your DATA SSD as it was mounted to /server at boot up

# ll /serverbkup

Total 0

Should show “Total 0” since the BKUP SSD is not mounted yet

As connecting USB Drives to different connectors may alter the device name, always determine which device name is being used for the USB BKUP Drive.

# lb

NAME FSTYPE LABEL MOUNTPOINT

sda

└─sda1 ext4 DATA /server

sdb

└─sdb1 ext4 BKUP

mmcblk1

└─mmcblk1p1 ext4 Odroid-XU4 /

Now you know why specific Volume labels were suggested to be used when formatting the partitions on the storage devices. This easily shows which SSD has which device name.

Now we need to mount the BKUP SSD to /serverbkup. In this case /dev/sdb1

# mount -t ext4 /dev/sdb1 /serverbkup (adjust device name as required)

# ll /serverbkup

The first time the device is used after a format, you will only see the lost+found file.

# rm -rf /serverbkup/lost+found

If this device has been used previously for backups, you should see a lot of directories.

This proves the mount command was successful.

# su pshare (IMPORTANT: preform the backup as user pshare Do not backup as root)

$ rsync -av - -delete /server/ /serverbkup (a slash at the end of /server/ is very important)

$ exit (Exit back to root)

# umount /serverbkup

# ll /serverbkup

Total 0

Shows that the BKUP drive was un-mounted and safe to remove

unplug the BKUP SSD from the USB port.

]]> 1766 0 0 0 https://discovery.endeavouros.com/video-tutorials/back-up/2021/04/ Mon, 05 Apr 2021 11:19:50 +0000 https://discovery.endeavouros.com/?p=1782

https://youtu.be/Ne_hHj8S1QQ

In this video, I cover backing up data or the full system using Grsync, the Graphical front end of Rsync. In the coming videos, I am going also to explore Rsync from the terminal.

https://youtu.be/G2gbun8LEC4

In this video, I cover backing up data or the full system using Rsync from Terminal. There will be two scenarios is this video. One, a backup to an external drive and the second one will be on an external server via SSH.

https://youtu.be/dPwssteyDXU

In this video, we combine the rsync command from the previous video with the Crontab scheduler to produce personalized backups. In the next video, we're going to cover also rsync with SSH and Crontab.

https://youtu.be/cREJHcu5G80

In this video, we combine the rsync command with SSH from the previous video with the Crontab scheduler to produce personalized backups on an external server.

https://youtu.be/Mnfz6gBFhi8

In this video, we're looking at Back In Time as a backup solution for your personal files and home directory. We'll install the program from the AUR, backup the Home directory and restore it with a snapshot. Back In Time is usually used to back up personal files rather than system files.

https://youtu.be/3YSeMxiXi7c

In this video, we're looking at Timeshift as a backup solution for your system. We'll install the program from the AUR, backup the Home directory, the system and restore them. Timeshift is usually used to back up the system files rather than files and folders.

https://youtu.be/gnNIhIrhzNU

In this video, we're looking at the Duplicati backup solution for backing up your files and folders. We'll install the service, backup the Home directory and restore it.

https://youtu.be/qrGc_anbodU

In this video I am going to show you how you can restore your machine from dotfiles you have on GitLab or GitHub (or another repository). In this case, it is going to be from my dotfiles of the i3 window manager. Dotfiles: https://gitlab.com/eflinux/main-deskt...

https://youtu.be/oWrRcjj29Iw

In this video, I am going to talk about two of my favorite tools in Linux: cron and rsync. Cron is a job scheduler and rsync is used mostly as a powerful backup tool.

Cron Wiki: https://wiki.archlinux.org/index.php/...​

Rsync Wiki: https://wiki.archlinux.org/index.php/...

https://youtu.be/7wtxnlWwP7w

In this video, I am going to install Timeshift on a fresh installation with the latest ISO of Endeavour OS. I am going to also show you automatic snapshots and how to restore one.

Timeshift Source: https://github.com/teejee2008/timeshift

]]> 1782 0 0 0 https://discovery.endeavouros.com/video-tutorials/pacman-aur-tutorials/2021/04/ Mon, 05 Apr 2021 11:19:22 +0000 https://discovery.endeavouros.com/?p=1786

https://youtu.be/TQaHfQrwnXo

In this video I am going to cover the basic Pacman commands for Arch Linux.

https://youtu.be/WhKVY4-t4Vk

In this video I am covering how to install AUR packages with the Yay helper.

https://youtu.be/h6UkjRl9dNE

In this video I am going to cover how to install packages from the AUR using the 'git clone' command.

]]> 1786 0 0 0 https://discovery.endeavouros.com/video-tutorials/general-linux-tutorials/2021/04/ Mon, 05 Apr 2021 11:18:51 +0000 https://discovery.endeavouros.com/?p=1791

https://youtu.be/NJpHKpdRZxc

This video goes over how to use sudo su root or use sudo no password to avoid getting prompted all the time. It covers why people new to Linux like to use sudo su and why this messes up their installs.

https://youtu.be/XK81cfvrElg

In this video, I go over 15 Useful Linux Commands Every Linux User Needs in my Learning Terminal Series. 15 Commands are explained in this video of part 1 and will be introducing EVEN MORE commands in part 2. However, before that, you have to know these 15 as they are vital to everyday life in Linux Terminal.

https://youtu.be/kVlkgiwiY6w

Here are 11 More Linux commands every linux user needs in Learning Terminal Part 2.

https://youtu.be/3s7qBJ-H7vw

In this video, I show you how to make a custom boot menu with graphics in GRUB2.

https://youtu.be/mA08E59-zo8

In this video, I go over Symbolic links in Linux. I use symlink for anything where I need certain files to show up at a spot in the file system. This can be incredible useful for linking game save file that you might share through an online cloud storage service like Dropbox without moving the file.

https://youtu.be/U_MBJcD3SFI

This video goes over what Wayland and Xorg do. It pits Wayland vs Xorg but each has their place. I also break down what the differences are between them and my personal experiences with each.

https://youtu.be/HdEozE2gN9I

Let's go over File Systems in this video. We will determine which one is the best ZFS, BTRFS, and EXT4. Each one might work for you based on YOUR needs!

https://youtu.be/7pBFbROYYdg

In our first tutorial on terminal commands and their usage, we will discuss the following: pwd, cd, ls, man…and we will also talk about the --help flag. We learn how to change directories and move around in our system, how to list contents of directories, and (most importantly) how to view manpages.

https://youtu.be/ZsLg7eLkYbs

In this part of our terminal commands series of videos, we discuss how to make, move, copy and delete files and directories using the following commands: touch, mkdir, mv, cp, rm, rmdir.

https://youtu.be/JyZhYr-2uZ4

In this video on terminal commands and their usage I take a look at a few commands you can use to search for programs on your system and search for files. I discuss the which, whereis, locate and find commands.

https://youtu.be/s2bsE7MJTQg

In this video I show you how to create and edit text documents from the terminal. The commands covered include the cat and echo commands as well as the text editors nano and vi(m).

https://youtu.be/ibEX5kY7WIU

In this video I am going to have a look at how we can manage processes by using the Top utility, which comes preinstalled on every Linux system.

https://youtu.be/drwg1XWXCY8

In this video I am going to talk about basic permissions for files and directories in Linux.

https://youtu.be/lNb50OpfEMs

In this video I am going to cover the basics of SSH and SFTP on Linux. It is by no means a full video on the topic, but it should be enough to get you started!

https://youtu.be/j9F92m1F3z0

In this video I am going to encrypt a partition on a second drive. The procedure is not too complex, and it can be handy in certain situations.

]]> 1791 0 0 0 https://discovery.endeavouros.com/video-tutorials/maintenance/2021/04/ Sat, 03 Apr 2021 09:51:55 +0000 https://discovery.endeavouros.com/?p=1793

https://youtu.be/iAV1aVsMvp4

Do you need Antivirus for Linux? In this video, I go over Linux security and best practices for desktop Linux users out there.

https://youtu.be/qPEA6J9pjG8

In this video, I go over how to set up a firewall on Linux using the built-in iptables that is in every Linux distribution. SSH Tarpit is something many people miss.

https://youtu.be/wwSkFi3h2nI

NOTE 1: at 09:30​ pacman -Qtdq or pacman -Qtdq doesn't make any difference. It's just the order of the switches are different, but the effect is the same.

NOTE 2: at 09:35​ in the fish shell you can write sudo pacman -Rns (pacman -Qtdq) without the $ before the opening parenthesis.

In this video I am going through the tasks I perform to maintain my Arch Linux installation. These are just a few steps I perform regularly. It is important to read through the Arch Wiki and find which routine you need for your PC.

Arch Wiki Maintenance: https://wiki.archlinux.org/index.php/...​

Arch Wiki Pacman: https://wiki.archlinux.org/index.php/...

https://youtu.be/JINRru-W1_s

NOTE: Sorry about the typo at 08:00​. The zone is obviously libvirt.

In this video we're going to install and explore Firewalld, a powerful firewall utility for Linux. We are going to see how it works from the CLI, the GUI and from the Cockpit.

Arch Wiki: https://wiki.archlinux.org/index.php/...

https://youtu.be/WTJw21XQjCc

In this video I am going to explore the Tuned service. Installed by default on RHEL and CentOS, it is a system tuning service for Linux. It monitors connected devices using the udev device manager, tunes system settings according to a selected profile and supports various types of configuration like sysctl, sysfs, or kernel boot command line parameters, which are integrated in a plug-in architecture.

AUR Package: https://aur.archlinux.org/packages/tu...​ RedHat docs: https://red.ht/2EEXrlr

https://youtu.be/2vbrFZiq2Hc

In this video I am going to show you how you can "reset" Arch Linux to the base system if your system becomes unstable, or you want to change DE or WM (although it's possible to have multiple DE's and WM's in one installation). I wanted to use my personal project on GitLab as it contains all the packages I usually install in the base. The only data I changed are the passwords, which were replaced with "new" ones.

Arch Wiki: https://wiki.archlinux.org/index.php/...

https://youtu.be/9l7vr3FHsdo

In this video I am going to install the Cockpit. The Cockpit is a systemd web based user interface for Linux servers, but can be used on desktops as well to monitor the system and change settings from a GUI.

Arch Linux package: https://www.archlinux.org/packages/co...​

The Cockpit Project: https://cockpit-project.org/

]]> 1793 0 0 0 https://discovery.endeavouros.com/video-tutorials/gui-applications/2021/04/ Mon, 05 Apr 2021 11:18:12 +0000 https://discovery.endeavouros.com/?p=1798

https://youtu.be/gs9I1gPGn9A

In this video, I am going over alsamixer and pulseaudio. I will show how to use them and fix any Linux sound issues you might have.

https://youtu.be/lI09QLkqZiE

In this video I am going over Windows Programs on Linux using Wine, what it does, and how you can use almost any Windows program on Linux.

https://youtu.be/vC8NZH3ZRb0

In this video I show you how to use KDE Connect to control your phone from your computer or vice versa.

Source: https://community.kde.org/KDEConnect

https://youtu.be/kJ5PKkhl6vw

In this video, I go over improving WINE performance in games. When I noticed substantial frame drops, I used the following to drastically increase my performance.

https://youtu.be/7CcOdY_eso0

Stacer is an open source Electron application that combines the power of a system cleaner, system monitor, startup manager, and a package remover all in one easy-to-use program.

https://github.com/oguzhaninan/Stacer

https://youtu.be/Wkrw_kyXfhg

I take a quick look at a cool, little app launcher named Rofi. It is simple-to-use and highly configurable. A perfect launcher program or run command utility for minimal desktop environments or window managers.

https://github.com/DaveDavenport/rofi/​

]]> 1798 0 0 0 https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/ Tue, 09 Mar 2021 11:48:43 +0000 https://discovery.endeavouros.com/?p=1018

How to include systemlogs in your post?

by joekamprad (taken over from Antergos and expanding it)

In the majority of cases, simply describing your issue will not provide enough information for someone to identify its cause and advise you on how to resolve it. It is important to include any system logs that may be relevant to your issue to ensure that neither your time nor the other person’s time is wasted. The following is a list of the most common system logs and where/how to obtain them. The logs are listed in order of importance.

Essential: we need to be able to reproduce the issue, so exact steps are needed.

These two outputs from your system should be included in most cases if you want help on a specific system/hardware related issue:

Hardware information:

inxi -Fxxc0z | eos-sendlog

Using the "z" option filters out most of the privacy related stuff like IP serial numbers e.t.c :
-z, --filter Adds security filters for IP/MAC addresses, serial numbers,
location (-w), user home directory name, host name. Default on
for IRC clients.

Boot log:

See journalctl for options.

journalctl -k -b -0 | eos-sendlog

Run the commands and share the short-url in your post.

It will show like so in your terminal:

Partition and format info:

lsblk -o name,type,size,PTTYPE,FSTYPE

Provide Installer Logs (calamares ISO LiveSession):

While you are still on the ISO Live Session logs are stored inside livusers home:

/home/liveuser/endeavour-install.log

You can open with text editor or from file browser, or send via tools (needs internet connection):

cat ~/endeavour-install.log | eos-sendlog

You can simply share the short URL it produces inside a terminal.

On an installed system, the log from the installation process is stored under:

/var/log/endeavour-install.log you can also send it but needs admin to read:

sudo cat /var/log/endeavour-install.log | eos-sendlog

In addition, you can use the log GUI tool from EndeavourOS:

[icon name="info" prefix="fas"]

A general warning about logs:

If sending/posting system journal, please keep in mind that it could include personal data!!

So consider using something like

journalctl -b -0 | grep fail | eos-sendlog

So it will only show the lines including the search term "fail" per example.

Or send the log in a P.M to a user you trust in that matter, so your log will not be visible in public.

Info on different logs and tools you can use to fetch and share system information:

Systemd Journal:

The systemd journal can only be accessed using the journalctl command.

journalctl -b -0 # System journal, most recent

journalctl -b -1 # System journal, 2nd most recent

journalctl -b -2 # System journal, 3rd most recent

The most interesting one is the last boot in most cases.

Learn more about the Pastebin command further down.

Note that EndeavourOS has a simpler way to Pastebin. For example:

cat file | eos-sendlog

The program eos-sendlog will (by default) save the received URLs to ~/.config/eos-sendlog.txt for later inspection.

Xsession:

Your session log is located in your /home directory:

~/.xsession-errors

~/.xsession-errors.old

Xorg (X11):

You can find your Xorg logs here:

/var/log/Xorg.0.log

/var/log/Xorg.0.log.old

Lightdm:

LightDM’s logs can be found here:

/var/log/lightdm/lightdm.log

/var/log/lightdm/x-0-greeter.log

Other log providers and options:

journalctl --since "10 minutes ago"

To get the journal from a given timespan (works also with hours seconds, days)

A good way to get information about a particular program:

journalctl -f /usr/bin/"Executable"

Journal from an exact timespan:

journalctl --since "2025-11-08 10:00:00" --until "2025-11-08 11:00:00"

also:

journalctl --since "2 hours ago" --until "30 minutes ago"

and yes:

journalctl --since "2025-11-08 10:00"

You do not need to add hours/minutes too:

journalctl --since "2025-11-08 10" --until "11:30"

And nice to post a Pastebin the smart way:

"command" | curl -F 'file=@-' 0x0.st

or using EndeavourOS tools:

"command" | eos-sendlog

System summary and boot log example:

lspci > log.txt && lsusb >> log.txt && journalctl -b -0 >> log.txt && cat log.txt | curl -F 'file=@-' 0x0.st

Or use eos-sendlog:

lspci > log.txt && lsusb >> log.txt && journalctl -b -0 >> log.txt && cat log.txt | eos-sendlog

The program eos-log-tool is a GUI for various logs and system files.

Other systemd logs/analyze:

systemd-analyze blame

will show times of systemd stuff needed to proceed on boot up

https://www.freedesktop.org/software/systemd/man/systemd-analyze.html

Pastebinit:

install pastebinit with package manager or sudo pacman -S pastebinit

the command should be passed like this:

journalctl -b -0 > ~/journal.txt && pastebinit -i ~/journal.txt -b lpaste.net

Where you can change journalctl -b -0 with any other command like dmesg from below, his will write to a text file: ~/journal.txt under your home you can change this name (journal) to something related to the command you pass.

pastebinit will auto-upload this to the Pastebin service you can choose (list all available by pastebinit -l

then it gives the link to it as output, so that you can just copy t to paste inside a post.

System summary and boot-journal example:

lspci > log.txt && lsusb >> log.txt && journalctl -b -0 >> log.txt && pastebinit -i log.txt -b lpaste.net

This will give out a link (like this:http://lpaste.net/7802695579456241664) you can post onto the forum, this will include all the output of:

lspci (list your pci devices) lsusb (same for USB) and dmesg (boot up messages) and make it available.

The dmesg command:

An alternative to the above command (or if your system is not using systemd) is the good old dmesg command. This is potentially less informative than journalctl above, but not if you have filtered it as I advised you to. So they are essentially equivalent.

sudo dmesg

Again, If you look in its man page or type invoke dmesg --help you’ll learn about the always useful -l flag, which filters dmesg potentially long output to print only certain message levels. And the -r flag which prints the message level. So, likewise, many of us will thank you if you do the following instead of the above:

sudo dmesg -rl warn,err,crit

Or at the very least:

sudo dmesg -r

Trivia: The dmesg command is basically the same as journalctl with the -k flag added to it

Hardware Information Systems:

INXI: smxi.org

inxi -Fxxc0z

all inxi options in detail:

https://smxi.org/docs/inxi-options.htm

Or to auto-pastebin it and get a URL to post:

inxi -Fxxc0z | curl -F 'f:1=<-' ix.io

inxi -Fxxc0z | eos-sendlog

using the "z" option filters out most of the privacy related stuff like IP serial numbers e.t.c : _{-z, --filter Adds security filters for IP/MAC addresses, serial numbers, location (-w), user home directory name, host name. Default on for IRC clients.}

So also if you use inxi for showing only parts of the info like inxi -Aa to show audio hardware details you should always add `-z` to the used command if you want to share the output:

inxi -Aaz

EndeavourOS log tool

We also have a GUI app to handle logs which will come in handy if you are not that firm on using all the commands from terminal:

After selecting the logs you want to share, it will create the log and Pastebin this for you so that you easily can share this URL on the Forum or in the Help chat:

[icon name="info" prefix="fas"] Final Note:

Very important! Do not paste only the printed contents of the command.

Always show also the command you used to get that output.

And better to use an external Pastebin if the output is very large because it is hard to get the overall question visible, inside your post, or for the discussion, if it is interrupted by large logs!

At the Forum, you can use also the summary option to hide the text/log itself and instead show an arrow to open it:

]]> 1018 0 38 0 https://discovery.endeavouros.com/network/printers/2021/03/ Tue, 09 Mar 2021 12:45:24 +0000 https://discovery.endeavouros.com/?p=1029

• _{updated by joekamprad 23. August 2026}

Printers

To get your printer working you will mainly need to install and setup CUPS.

If you choose the printer support option on the installer you will already have a working cups setup (for locally connected printers [usb] ) and only need to add your printer.

To install cups and an usb connected printer if you do not installed the printing option:

sudo pacman -Syu --needed cups cups-filters cups-pdf avahi nss-mdns ipp-usb ghostscript gsfonts poppler poppler-glib qpdf

To get full cups with support for many different printers per default. Install this packages on top of that:

sudo pacman -Syu --needed foomatic-db-engine foomatic-db foomatic-db-ppds foomatic-db-nonfree foomatic-db-nonfree-ppds gutenprint foomatic-db-gutenprint-ppds

For QT environments (like KDE/plasma LXQT):

sudo pacman -Syu print-manager --needed

On GTK based xfce4, cinnamon and others there is system-config-printer Gui:

sudo pacman -Syu --needed system-config-printer cups-pk-helper python-notify2 python-pysmbc

Now enable only the socket, which will listen if print-job is calling and then enable the service:

sudo systemctl enable --now cups.socket

or using the service, which will be running constantly.

sudo systemctl enable --now cups.service

note: Most modern Network Printers should support Driverless Printing. Those supporting IPP Everywhere or AirPrint should work out of the box. see: #network-printer

Read at the bottom about finding drivers for common printers (skip Network Printers):

Find printer drivers

Note:

in case you have a Multidevice including a scanner, you may want scanning support installed:

sudo pacman -S sane

Add sane-airscan for AirScan (eSCL) and WSD document scanners.

In case you want a Frontend (GUI) to scan documents, install simple-scan package.

General info on supported scanner devices:

https://wiki.archlinux.org/title/SANE

Network Printer

It is required to enable local hostname resolution for avahi to be able to connect to your network printer, up from EndeavourOS Galileo we set up mdns to work out of the box after you changed firewall to allow mdns traffic.

So the following is only needed if you have an installation with older ISO, or you are not using EndeavourOS at all.

https://wiki.archlinux.org/title/Avahi#Hostname_resolution

Avahi provides local hostname resolution using a “hostname.local” naming scheme. To enable it, make sure the nss-mdns package is installed and avahi-daemon.service is running:

pacman -Qs nss-mdns to see if it is installed

Make sure avahi-daemon is running:

systemctl status avahi-daemon.service

If not install and enable it:

sudo pacman -Syu avahi --needed
sudo systemctl enable --now avahi-daemon

In case, you do not have local hostname resolution enabled (EndeavourOS has enabled this by default.)

Edit the file /etc/nsswitch.conf and change the hosts line to include

mdns_minimal [NOTFOUND=return]

before resolve and dns:

Restart avahi-daemon and NetworkManager after this, or reboot machine:

sudo systemctl restart avahi-daemon NetworkManager

Forward for all users (mdns is enabled):

Automatically add network printers:

CUPS can use Avahi browsing to discover unknown shared printers in your network. This can be useful in large setups where the server is unknown. To use this feature, set up local hostname resolution, and start avahi-daemon.service

Most modern Network Printers should support Driverless Printing. Those supporting IPP Everywhere or AirPrint should work out of the box.

Check if yours is supported here: https://openprinting.github.io/printers/

This is also very usefull for mobile devices, or for usage in offices where a number of changing network printers is used.

But you can use this at home too, it can be less troublesome in case, as you do not need to set up drivers and URI.

With this you will see local network printers actively showing op as print options when triggering a print from any app, it will not create a printer queue that shows permanently in printer settings.

Automatic Queue Discovery (Zero-Config)

Automatic Print Queues via cups-browsed

By enabling cups-browsed, your system listens for mDNS/Bonjour broadcasts from printers on your local network. It automatically creates and removes local CUPS print queues in the background without requiring any manual setup.

Install additional required package:

sudo pacman -Syu --needed cups-browsed

And enable the service: sudo systemctl enable cups-browsed.service

To have this working firewall needs to allow mdns and avahi-deamon have to be enabled (as mentioned before)

Note on Security & Laptops:
_{If you frequently use your laptop in public/shared networks (universities, cafes, hotels), cups-browsed may automatically register every discovered public printer. In that case, keep cups-browsed disabled. Having cups-browsed enabled could also cause security risks: CVE-2024-47176 it is patched in actual versions, but could still call in risk in insecure networks.}

Firewall is blocking mdns:

To make use of local hostname resolution (mdns) you need to change firewalld from public to home (zone change).

Assigning a Zone to a device will also be remembered on network changes, so if you leave home network and per example connect to a Wi-Fi network outside it will always use the default set public zone as long as you do not change that manually.

To make these permanent you need to set Configuration to Permanent and run the change to home zone, if Runtime is used it will get reset after logout. Now you should see network printers in printer setup tools showing up.

https://youtu.be/9MCdy8ZGQ1I?si=XW4yzwTTiFgn5TNX

Procedure to find the right driver for your printer

Go to the open printing website and search for whether your printer is supported on Linux at all, and what driver options are available.

This is what the result will look like:

• On top you will see whether or not there is a working driver for your printer
• second it will show available driver options, in the example, you see Type: Ghostscript built-in, so go to package search on Archlinux (or use the tool of your choice) you will find GhostScript (already installed if you followed the tutorial from top to bottom)

So install the driver available for your device, and proceed to install and configure the printer. But take a look at these links first, as it could be that your printer needs some extra configuration done to work properly:

Some links to common printers' information on Archwiki:

• Canon printers
• Epson printers
• HP printers
• Lexmark printers
• Oki printers
• Samsung printers
• Brother printers

Notes on Common ways to install printer drivers:

Mostly all printers will be using cups as a backend to communicate with your system, but different brands will be needing different ways to get printers fully functional:

Hewlett and Packard (HP) printers:

Some of the HP-printers needs a proprietary plugin to work, this can be installed by hplip.

Here is an overview of some common printers and working drivers on Archwiki:

Printer-specific_problems#HP

Most drivers for hp-printers come with the HPLIP package you can install this with:

sudo pacman -S hplip

Notice that if lpinfo -m tells you that the driver "requires proprietary plugin", you need to build/install hplip-plugin:

yay -S hplip-plugin

check https://developers.hp.com/hp-linux-imaging-and-printing/binary_plugin.html for mor information

install python-pyqt5 to run GUI and hp-toolbox:

sudo pacman -S python-pyqt5

now run the program to install new printer queue and the possibly needed proprietary plugin for some hp-printers:

sudo hp-setup -i for CLI install without a GUI

or run hp-setup from menu.

The tool guides you through the installation - simply read the instructions.

You have your printer added now, so you do not need to set it up again as what follows, but you can use system-config-printer to setup configuration for papersize e.t.c.

HP printers alternative driver (foo2zjs-nightly)

Uninstall hplip package: sudo pacman -Rsc hplip

install foo2zjs-nightly from AUR:

yay -S foo2zjs-nightly

Use system-config-printer to set up your HP Printer.

Some may use hpoj (https://hpoj.sourceforge.net/), while for multifunction laser printers hpuld (HP Unified Linux Driver) might be required.

Common printer setup (not if hplip is used):

Use the system-config-printer tool to find and set up your printer:

]]> 1029 0 37 0 Printers]]> ]]> https://discovery.endeavouros.com/nvidia/nvidia-intro/2021/03/ Tue, 09 Mar 2021 15:10:03 +0000 https://discovery.endeavouros.com/?p=1050

Nvidia intro

_{Latest update: 12-jan-2026}

As most newer cards will work with the latest drivers, older cards are no longer supported by the latest drivers. Nvidia is sorting out older GPU to legacy branch this cards are not supported by the latest driver.

nvidia-open: open source NVIDIA kernel modules package best for all cards up from 16xx

The first thing you should do is get knowledge about your card and supported driver:

NVIDIA Turing GPU, GTX 16xx RTX 20xx and newer.

These are supported by the main nvidia packages nvidia-open, nvidia-open-lts and nvidia-open-dkms

You always need at minimum nvidia-open and nvidia-utils packages installed, in addition you may need lib32 support packages for Gaming on Steam or Wine: lib32-nvidia-utils per example.

_{If these packages do not work, nvidia-beta^AUR may have a newer driver version that offers support.}

For older Legacy Devices, read here: about-legacy-gpu on Nvidia Website.

Overview over the legacy branches:

_{(unsupported means no package for driver at the repositories)}

GPU family	Driver	Nvidia (proprietary) Status
Blackwell (GBXXX) and newer	nvidia-open (linux) nvidia-open-lts (linux-lts) nvidia-open-dkms (any kernel)	Recommended by upstream Current, supported
Turing (NV160/TUxxx) and newer * GTX 1650 and newer	nvidia-open (linux) nvidia-open-lts (linux-lts) nvidia-open-dkms (any kernel) Also supported by: nvidia-580xx-dkmsAUR (prperietary) Alternative open source Nouveau NVK: vulkan-nouveau	Recommended by upstream Current, supported No RTD3 power management on Turing Crashes on some laptops nvidia-open has no RTD3 Power Management on Turing, possible crashes on Ampere-equiped laptops.
Maxwell (NV110/GMxxx) * GTX 745, GTX 970	nvidia-580xx-dkms (AUR) Alternative: open-source nouveau	Legacy, supported
Kepler (NVE0/GKxxx) * GTX 660, Quadro K6000	nvidia-470xx-dkms (AUR) Alternative: open-source nouveau	Legacy, unsupported
Fermi (NVC0/GF1xx) * GTX 465, Quadro NVS 4200M	nvidia-390xx-dkms (AUR) Alternative: open-source nouveau	Legacy, unsupported
Tesla (NV50/G80–90–GT2xx) * 8300 GS, Quadro FX 4600	nvidia-340xx-dkms (AUR) Alternative: open-source nouveau	Legacy, unsupported
Curie (NV40/G70) and older * GT 6800, Quadro FX 1400	No longer packaged, open-source nouveau	Legacy, unsupported

You will need the related nvidia-580xx-utils [AUR] (example branch) package installed in addition to got the driver working.

In case you also may want lib32 support packages for Gaming (steam/wine) lib32-nvidia-580xx-utils [AUR] (example branch), and you also need the same version of nvidia-settings if you want that installed: nvidia-580xx-settings [AUR]

Find your Cards Codenames here: https://nouveau.freedesktop.org/CodeNames.html

The EndeavourOS tool for Nvidia Drivers: nvidia-installer (nvidia-inst) only supports the latest driver

To see what driver version support your card go here:

Nvidia Driver Search

Put in the info for your card, and choose Linux-64bit as OS.

Or see here main Nvidia packages supported card list: https://www.nvidia.com/

For GeForce it seems to show all drivers only on this page:

Nvidia-geforce

You can also use our tool to check your card:

nvidia-inst --test

This will show info about your GPU, related installed packages, and gives the commands to install Nvidia packages, but will not actually change anything itself, usefull in case you have no clue to show someone helping you.

If you have PC with a dedicated card plugged in you can use nvidia-inst to get latest driver installed, for more info go here:

nvidia-inst

With the introduction of the eos-hwtool you can easily get drivers installed with one simple command:

eos-hwtool --no32 --install-recommended

If you do plan to install steam best is to install 32 bit libs too: eos-hwtool --install-recommended

For other Nvidia settings choose the right article for your hardware:

https://discovery.endeavouros.com/category/nvidia/

Notes:

_{No RTD3 power management on Turing
Crashes on some laptops: The proprietary NVIDIA Linux driver supports RTD3 runtime power management only in specific configurations and treats it as experimental on Turing GPUs. Documentation notes initial experimental support for Turing notebook GPUs, and real-world reports show that RTD3 is often disabled by default or leads to instability (e.g., ‘Runtime D3 status: Not supported’ or system hangs/crashes) on some laptops. For details, see the official NVIDIA README on dynamic power management and user reports on Arch and Fedora forums.}

]]> 1050 0 29 0 https://discovery.endeavouros.com/audio/bluetooth/2021/03/ Thu, 11 Mar 2021 11:08:35 +0000 https://discovery.endeavouros.com/?p=1089

Enable and setup Bluetooth devices

On EndeavourOS we do not enable Bluetooth by default, because of several security risks, and to prevent unneeded power consumption.

Needed packages are installed by default, but it is in their default disabled state.

To be able to use Bluetooth you need to start the service or enable it if you need Bluetooth running on every boot:

sudo systemctl start bluetooth # to start it for the session will stay disabled after reboot.

sudo systemctl enable bluetooth # to enable per default, will run after every boot.

With this, you can handle Bluetooth devices over CLI tool bluetoothctl most Desktops will have some setup in there setting tools, if not see at the bottom about And install graphical GUI tools to configure and manage Bluetooth.

In case you want to make sure all packages are still installed or you may remove some, using custom install e.t.c. install it manually:

If you are using pipewire (default since Atlantis release):

sudo pacman -S --needed bluez bluez-utils

If you are using pulseaudio (older installs or manual switching to pulseaudio):

sudo pacman -S --needed bluez bluez-utils pulseaudio-bluetooth

And install graphical GUI tools to configure and manage Bluetooth over a GUI application:

blueman (gtk) recommended for GTK based [can be used in Desktop Environments independent]
bluedevil (qt) [Integrate the Bluetooth technology within KDE workspace and applications]

blueberry (gtk) _{no longer developed}

sudo pacman -S blueman per example

DEs like KDE/plasma and GNOME ship their own Bluetooth GUI by default.

To use Bluetooth, you will mainly need to enable it for use by default to start on every boot, or start it for a single session to use it only once:

sudo systemctl start bluetooth –> This is only for single session use.

If you want to have Bluetooth enabled by default (on every boot) and start the service immediately:

sudo systemctl enable --now bluetooth

The default CLI tool to manage Bluetooth connected devices is bluetoothctl:

bluetoothctl

In some cases, it helps to run this as root for first connecting devices to be able to use them. But first try as normal user indeed!

https://wiki.archlinux.org/title/Bluetooth#Console

the usual schedule to connect a new device with it is running it like so:

bluetoothctl ----> scan on ------> trust ----> pair ---> connect

Bluetooth File Transfer (Obex)

_{share files with other devices via Bluetooth}

To enable the option you need to install the needed support package first:

sudo pacman -Syu bluez-obex

And make the service available to your user:

systemctl --user enable --now obex-service

This will enable the service by default, in case you do not want it to run every boot you can start it if you need before sending/receiving files via Bluetooth: systemctl --user start obex-service

After this you have the option on most file-browser (right click on a file) to send files via bluetooth. Only devices once paired and may also trusted, can be used to send files to.

It can be smart to use the external device to pair the device from you want to use to send files, this will make sure the client device will trust the obex-send files.

To do so open your Bluetooth settings and make sure the host is visible, after this use the remote device to add your host.

Once setup is done you can use file-browser right click menu to send files directly to the remote device:

It will ask to allow still and may verify by showing a number on both devices, the first time you use it.

Tips and Tricks

In case you have issues with using same device on dualbooting with another OS or it simply fails to connect, it could help to remove the Bluetooth database of known devices in the system path:

#sudo rm -R /var/lib/bluetooth

This will remove all known Bluetooth devices and their settings!

]]> 1089 0 23 0 458 https://kaneis.wordpress.com/2025/03/02/enable-and-setup-bluetooth-devices-in-endeavouros-or-other-linux/ 0 0 https://discovery.endeavouros.com/nvidia/optimus-switch-another-solution-for-optimus-laptops/2021/04/ Tue, 13 Apr 2021 09:29:56 +0000 https://discovery.endeavouros.com/?p=1987

Optimus Switch - Another Solution for Optimus Laptops

_{By Linesma}

Introduction

Since their introduction, getting Optimus (Intel/ nVidia) laptops to work properly has been an issue under Linux. The two most common solutions are Bumblebee and Optimus Manager. Both have their limitations and not every user can get them working properly. Optimus Switch, written by user @dglt, is another option for users to switch between graphics cards on Optimus based (Intel/ nVidia) laptops. By following this guide, the user will install and properly configure Optimus Switch and the GUI indicator/ switcher for it.

Optimus Switch vs. Optimus Manager.

1. By default, Optimus Switch will completely power down your nVidia card when you are using the Intel iGPU. This allows for longer battery life. While this function can be enabled in Optimus Manager, it is not enabled by default and does not always work properly.
2. Optimus Switch sets up the nVidia card in “Prime Mode” when the user is in “nVidia” mode. This allows the user full access to their nVidia card without using terminal commands or modifying shortcut parameters to run programs.
3. Optimus Switch does not require a “patched” version of GDM from the AUR. Less chance of instability when Gnome is updated.
4. Optimus Switch, unlike Optimus Manager, does not allow for the switching of GPU’s on demand. The user needs to reboot their laptop whenever they “switch” between GPU’s.

Optimus Switch vs. Bumblebee

The same comparisons for Optimus Manager apply to Bumblebee as well. The only difference is the use of the proprietary nVidia driver instead of the Open Source Nouveau driver. By using the driver from nVidia, the user is able to use the full capabilities of their nVidia card.

All the above solutions require the use of Xorg instead of Wayland.

Where to find Optimus Switch

Optimus Switch can be found at the links below. Because of differences in Display Managers, make sure that you use the version appropriate for the Display Manager you are using.

Gnome (GDM) - https://github.com/dglt1/optimus-switch-gdm 28

KDE (SDDM) - https://github.com/dglt1/optimus-switch-sddm 23

LightDM - https://github.com/dglt1/optimus-switch 33

While originally written for Manjaro installs, Optimus Switch can easily be used on other Arch-based distros. For EndeavourOS, we need to follow the instructions below.

Installation

1. Install EndeavourOS. Make sure to install the nVidia Drivers package. This will install the nVidia driver. I know it says that it is not for legacy cards or hybrid solutions. The system will still boot, but it may not initialize the Display Manager.
2. Upon reboot, you may be presented with a black screen and a blinking cursor. If you are presented with a log in screen, DO NOT LOG IN. In both cases, hit ctrl-alt-F3 to enter a TTY session. Now log in to your system.
3. Make sure that the nVidia driver is installed.

pacman -Q | grep nvidia

You should get a result that looks similar to this:

$ pacman -Q | grep nvidia
lib32-nvidia-utils 450.66-1
nvidia-dkms 450.66-1
nvidia-installer-db 2.4.6-1
nvidia-installer-dkms 3.3.7-1
nvidia-settings 450.66-1
nvidia-utils 450.66-1

3a. If the Nvidia driver did not install, do the following.

sudo nvidia-installer-dkms

4. Install the needed dependencies.

sudo pacman -S linux-headers acpi_call-dkms mesa-demos xorg-xrandr xf86-video-intel git

4a. Be sure to change the linux-headers package to match the kernel you are using. For example the zen kernel uses the linux-zen-headers package and the lts kernel uses the linux-lts-headers package.

5. Enable acpi_call by typing sudo modprobe acpi_call
6. Make sure that there are no video related config files on your system. Look in the following folders:

/etc/X11/
/etc/X11/xorg.conf.d/
/etc/modprobe.d/
/etc/modules-load.d/

6a. Any conf file that deals with the keyboard, touchpad, or networking can stay. Anything else, you can manually delete. For example, if you have a conf file name 20-nvidia.conf, it needs to be removed. You can remove it by typing sudo rm /etc/X11/xorg.conf.d/20-nvidia.conf

Now we can follow the readme on the GitHub page for the project directly. Make sure you follow the proper instructions for the Display Manager you are using.

7. From your home directory (~/) do the following. If you do not do this from the home directory, the script will not install files properly.

Gnome (GDM)

git clone https://github.com/dglt1/optimus-switch-gdm.git
cd ~/optimus-switch-gdm
chmod +x install.sh
sudo ./install.sh

Now we need to make sure that Gnome is using Xorg by default.

sudo nano /etc/gdm/custom.conf

Remove the # before the line that reads WaylandEnable=false . Hit ctrl-x to exit and Y to save the changes.

KDE (SDDM)

git clone https://github.com/dglt1/optimus-switch-sddm.git
cd ~/optimus-switch-sddm
chmod +x install.sh
sudo ./install.sh

LightDM

git clone https://github.com/dglt1/optimus-switch.git
cd ~/optimus-switch-sddm
chmod +x install.sh
sudo ./install.sh

8. Optimus Switch is now installed. You can now reboot your laptop. After your laptop finishes starting up, you will be in nVidia Prime “Mode”.

To switch modes, open a terminal and type the following:

For nVidia mode – sudo set-nvidia.sh
For Intel mode – sudo set-intel.sh

Then restart the laptop.

Reminder: When switching modes, you have to restart your laptop for the changes to take effect.

Powering down the nVidia card in Intel Mode

Optimus Switch uses the functions in the acpi_call package to turn off the nVidia card when the laptop is in Intel Mode. This allows for longer use time while on battery. To properly setup up acpi_call, we need to do the following.

1. The laptop needs to be in Intel Mode . If the user is in nVidia Mode, the laptop will freeze.
2. Open a terminal and type sudo /etc/switch/gpu_switch_check.sh . This will display a list of options that acpi_call can use to turn off the nVidia card.
3. Read through the list of options displayed looking for the line that says “works!”
4. Highlight and copy that line.
5. Open the file /etc/switch/intel/no-optimus.sh by typing sudo nano /etc/switch/intel/no-optimus.sh
6. Near the end of the file, two lines are commented out (#). Remove the (#) and replace the first
   line with what you copied above.

Example:

In the default file /etc/switch/intel/no-optimus.sh, the two lines look like this:

#echo '\_SB.PCI0.PEG0.PEGP._OFF' > /proc/acpi/call
#echo -n 1 > '/sys/bus/pci/devices/0000:01:00.0/remove'

Remove the (#) before each of these lines so it looks like this:

echo '\_SB.PCI0.PEG0.PEGP._OFF' > /proc/acpi/call
echo -n 1 > '/sys/bus/pci/devices/0000:01:00.0/remove'

Change the '\_SB.PCI0.PEG0.PEGP._OFF' with what you copied in step 4.

7. Save and exit the file by hitting ctrl-x and answering Y to save the changes.
8. Type sudo set-intel.sh and reboot the system.

The nVidia card should now be powered off when you are using the Intel iGPU to render graphics. To test this, open a terminal and type one of the two commands.

a. glxinfo|grep "OpenGL vendor|OpenGL renderer"

b. inxi -G

You should only see the Intel iGPU listed.

Installing the GUI Indicator/ Switcher Optimus-Indicator

If you are like me, you prefer doing things with a GUI. Also, it would be nice to have an indicator of some sort in the system tray. Because of this, I wrote a program for Optimus Switch that provides not only an indicator, but a way to switch “modes” right from the system tray. It is called Optimus-Indicator. It works with all major Desktop Environments and can be found here:`

https://github.com/linesma/Optimus-indicator 12

Installation

NOTE: This program relies on python. When python updates, a reinstall may be required.

1. Make sure that all the dependencies are installed.

sudo pacman -S libappindicator-gtk3 libappindicator-gtk2 libnotify

Additional requirement for Gnome – Make sure you have the KStatusNotifierItem/AppIndicator Support
extension link installed and activated. Without this extension, the icon will not display in the top bar’s system tray or in the system tray if you use the Dash to Panel extension.

Additional requirement for LXQT – The GTK3 package needs to be installed.

sudo pacman -S gtk3

2. Clone the repository the repository to your computer and go to its folder.

git clone https://github.com/linesma/Optimus-indicator.git
cd Optimus-indicator

For Gnome

Gnome requires slightly modified scripts to switch between the GPU’s. While they are the same scripts in dglt’s Optimus-Switch GDM repository, I have included them here for ease of installation.

3. Make the install script executable.

chmod a+x setupgn.py

4. Run the install script.

sudo ./setupgn.py install

5. The install script will install the needed files.
6. Once the installation is complete, reboot your laptop. Optimus-Indicator will start automatically when the laptop boots.

For all other Desktop Environments

3. Make the install script executable.

chmod a+x setup.py

4. Run the install script.

sudo ./setup.py install

5. The install script will install the needed files.
6. Once the installation is complete, reboot your laptop. Optimus-Indicator will start automatically when the laptop boots.

All Desktop Environments

There should now be an icon displayed showing which GPU is in use. Click on the icon and it will bring up a menu allowing you to switch GPU’s and automatically reboot your system.

Conclusion

While Optimus Switch is not as easy to setup, ie. Click and Go, as other solutions are, it is very stable. It reliably gives the user the flexibility to choose which GPU they want to use.

Personal Thoughts

I have been using it for the last year and a half, and have not had it break due to updates. I first used it on a Manjaro install. When I later switched to Arch itself, I tried the other options first and ended up going back to using it. I have never had it break due to a system update.

All Nvidia entries: https://discovery.endeavouros.com/?s=nvidia

]]> 1987 0 0 0 https://discovery.endeavouros.com/video-tutorials/joekamprad-video-tutorials/2021/04/ Sun, 18 Apr 2021 12:38:54 +0000 https://discovery.endeavouros.com/?p=2007

I do create some simple tutorials for common tasks on EndeavourOS involving our own apps.

https://youtu.be/-8wS31tzSZY

https://youtu.be/AiD042zOME4

https://youtu.be/7J4k_0JaXKc

https://youtu.be/KxhXL0O3-dQ

https://youtu.be/-1fCnqZ-Crw

https://youtu.be/5xLbge6iHtU

]]> 2007 0 0 0 https://discovery.endeavouros.com/installation/add-packages-to-be-installed-in-addition-to-desktop-chosen/2021/04/ Tue, 20 Apr 2021 13:16:21 +0000 https://discovery.endeavouros.com/?p=2018

Since the ISO publication of March 2021, there has been the option of entering additional packages in a list, which will then be installed in addition to the selected desktop environment.

This will only proceed if you choose online install method, as it needs to fetch the packages.
Simply edit and save the user_pkgfile file in the live environment.

After this you can simply start installation as usual.

Watch this little video to see how it looks like:

https://youtu.be/1-h0xFW3ruY

]]> 2018 0 0 0 https://discovery.endeavouros.com/desktop-environments/gdm-gnome-desktop-manager/2021/05/ Mon, 03 May 2021 19:40:33 +0000 https://discovery.endeavouros.com/?p=2043

The GNOME Display Manager (GDM) is a program that manages graphical display servers and handles graphical user logins.

More information:

https://help.gnome.org/admin/gdm/stable/

https://wiki.archlinux.org/title/GDM

Tips and Tricks:

• there is gdm-settings application in the AUR: gdm-settings

let you set theming wallpaper and other options for the really bare GDM login screen.

Troubleshooting:

GDM shows black screen with blinking white cursor

After booting, GDM may present you with a black screen with a blinking white cursor in the top left. This may be caused by GDM starting up before the graphics drivers are fully initialized. One possible workaround is to start KMS early. Another possible workaround is to edit the systemd service and either set its type to "idle" or add a small delay:

 [Service]
 Type=idle

or

 [Service]
 ExecStartPre=/bin/sleep 2

If a longer delay is required, increase the delay time.

to do so:

The easiest way to do this is to run:

sudo systemctl edit gdm.service

This opens the file /etc/systemd/system/unit.d/override.conf in your text editor (creating it if necessary) and automatically reloads the unit when you are done editing.

]]> 2043 0 0 0 https://discovery.endeavouros.com/applications/uniform-theme-and-fonts-for-qt-apps-in-gtk-environments/2021/05/ Tue, 18 May 2021 19:17:20 +0000 https://discovery.endeavouros.com/?p=2062

Uniform theme and fonts for Qt apps in GTK environments

_{By @joekamprad}

There are many ways to get a uniform look and feel working, and here we show only one or two solutions.

QGnomePlatform

The easiest way to set a uniform appearance for QT applications under GTK environments is using QGnomePlatform

Sources are marked unmaintained: https://github.com/FedoraQt/QGnomePlatform#qgnomeplatform-project-is-unmaintained-a-no-longer-actively-developed as of August 2023.

But still simply possible to build and install from AUR:

yay -Syu qgnomeplatform-qt5 qgnomeplatform-qt6

This will bring in adwaita-qt5 adwaita-qt6 can be replaced with other themes that supports both gtk and qt these two will use adwaita (default gtk theme) and making qt apps following adwaita dark and light theme.

( per example breeze and breeze-gtk will work too)

Add the environment variable either systemwide at /etc/environment or user specific into a ~/.config/environment.d/envvars.conf file or ~/.profile depending on the used Desktop or WM setup it could be zthe one or the other needs to be used.

QT_QPA_PLATFORMTHEME=gnome

Note: this variable is set per default for Gnome and if you are using Gnome you do not need to set the vatriable.

After a reboot qt apps should use adwaita same as set for gtk in settings.

To set font sice and some opther setting qt5ct and qt6ct will come in handy: sudo pacman -Syu qt5ct qt6ct

qt5/6ct gui let you set theming for qt apps per example set adwaita dark if it does not apply per default..

Kvantum:

Another way will be to use Kvantum and QT5/6CT:

Install both packages:

sudo pacman -Syu kvantum qt5ct qt6ct

Both applications are required because kvantum does not allow the font settings. Therefore qt5ct is also set as an environment variable, as it works in most desktop environments or when using a window manager as a user. In some cases, e.g. when using Cinnamon, it is necessary to set the variable system-wide, because Cinnamon seems to ignore variables that are set as users. Then we set qt5ct to use the kvantum theme and set fonts inside qt5ct.

Per-user variable will be configured like so:

It seems this method is not working on XFCE4 where using ~/.profile usage is working!

Same counts for Cinnamon.

Create the needed directory

mkdir ~/.config/environment.d

and the needed config file with the needed variable:

echo "QT_QPA_PLATFORMTHEME=qt5ct" > ~/.config/environment.d/qt-theme.conf

To use ~/.profile method:

echo "export QT_QPA_PLATFORMTHEME=qt5ct" >> ~/.profile

To set this systemwide (if per user variable does not work at all):

su

echo "QT_QPA_PLATFORMTHEME=qt5ct" >> /etc/environment

exit

If you use per user settings log out and back in to make it work, for systemwide settings reboot the system.

Now use the Apps to set your Theme, Fonts, and Icons:

Changes will work without the need to log out or reboot, only apps already running need to be restarted to take the theme changes.

for QT6 applications install qt6ct and setup the same with qt6ct tool.

Notes:

Some applications may have their own theme settings like kdenlive:

Do you want to descend into the sources of endless information and possibilities? … Consult the Archwiki:

https://wiki.archlinux.org/title/Uniform_look_for_Qt_and_GTK_applications

---

]]> 2062 0 0 0 https://discovery.endeavouros.com/endeavouros-tools/akm/2021/08/ Tue, 17 Aug 2021 15:40:26 +0000 https://discovery.endeavouros.com/?p=2330

A Kernel Manager

_{Author: @sandmaan
Update: @manuel 2023-Jan-07}

AKM is a simple GUI to manage the kernels. AKM is part of the EndeavourOS tool kit. But it can be used with any other Arch-based distribution. The letters AKM stands for “A Kernel Manager” according to the main developer who created this wonderful app.

AKM supplies the user with a Graphical User Interface with a list of kernels. The user can select a kernel version he/she wants to install.

Installing AKM

AKM doesn’t come preinstalled due to the minimalistic philosophy followed by the EndeavourOS team. So users who want to use AKM have to install it over pacman in the terminal

Installing from terminal

To install AKM via the terminal, you can use sudo pacman -S akm

Using AKM GUI

Using AKM is straightforward. From the GUI, a user can check the checkbox in front of the kernel package name which will mark that kernel to be installed. If the user wishes to uninstall a particular kernel then he/she just has to uncheck the kernel package from the list. Once they have selected or unselected the kernel package to change the status of, they only have to click on Execute to apply the changes. Refer to the image above for clarity.

Terminal Usage

You can use AKM via the terminal, with or without options. Using akm will launch the main AKM GUI. But a user can use the below options to change some characteristics of AKM.

• --connect-header - Which will bind the kernel header package and the selected kernel into one unit. As an example, if a user chose to install or uninstall the kernel linux-zen then using --connect-header option will bind the linux-zen-headers to the install or uninstall.
• --scroll - It allows the kernel list to be scrollable. By default, the list is scrollable (default changed in 2022).
• --small - Make the akm window smaller, suitable for low resolution screens.

Advanced Configuration

By using the AKM configuration file users can customize how AKM works. You can find the configuration file at /etc/akm.conf. Below is the example code of the mentioned file.

#!/bin/bash

### Config file for akm.

# When installing/uninstalling a kernel, you may configure to
# install/uninstall the related header too.
# Values: "yes" or "no"
# Default: no
local KERNEL_HEADER_WITH_KERNEL=no

# List of kernel and header names when using additional repos.
# Example:
#   local AKM_KERNELS_HEADERS=(
#       reponame/linux-xxx  reponame/linux-xxx-headers
#       reponame/linux-yyy  reponame/linux-yyy-headers
#       ...
#   )
# where
#    reponame   The name of an additional repository.
#    linux-xxx  The name of a kernel.
#
local AKM_KERNELS_HEADERS=(
)

# Width of the akm window in pixels.
# Default: 900
local AKM_WINDOW_WIDTH=900

Variable	Description	Supported Value
KERNEL_HEADER_WITH_KERNEL	Provides the same function asthe --connect-header option, binding the header package with the kernel package.	no(default) or yes
AKM_KERNELS_HEADERS	Lists the additional kernel and header names when using additional repositories.	List of reponame/pkgname entries.
AKM_WINDOW_WIDTH	Predefines the width of the akm GUI window.	A positive integer (number) in pixels. Default is 900

Adding a New (unofficial) Package Repository

If you want more kernels you can add the corresponding repository to the /etc/pacman.conf. After adding the repository user must perform a database sync using sudo pacman -Syy or sudo pacman -Syyu. Once this is done, if the repository contains any kernel packages then AKM will try to add them to the list and show them.

Example:
Unofficial Repository entry inside /etc/pacman.conf:

[archzfs]
Server = http://archzfs.com/$repo/$arch

Using Caveat Method to Add Kernels

This method of automatically detecting kernel names is limited because kernels can be named in various ways. Use the configuration variable AKM_KERNELS_HEADERS (mentioned above) to add a list of kernel and header names from an additional repository. This is useful if the automatic kernel name detection does not recognize certain kernel names.

Just as an example, to use the info from the picture above, your /etc/akm.conf could look something like this:

#!/bin/bash

### Config file for akm.

# When installing/uninstalling a kernel, you may configure to
# install/uninstall the related header too.
# Values: "yes" or "no"
# Default: no
local KERNEL_HEADER_WITH_KERNEL=yes

# List of kernel and header names when using additional repos.
# Example:
#   local AKM_KERNELS_HEADERS=(
#       reponame/linux-xxx  reponame/linux-xxx-headers
#       reponame/linux-yyy  reponame/linux-yyy-headers
#       ...
#   )
# where
#    reponame   The name of an additional repository.
#    linux-xxx  The name of a kernel.
#
local AKM_KERNELS_HEADERS=(
    kernel-lts/linux-lts414  kernel-lts/linux-lts414-headers
    kernel-lts/linux-lts419  kernel-lts/linux-lts419-headers
    kernel-lts/linux-lts44   kernel-lts/linux-lts44-headers
    # and so on...
)

# Width of the akm window in pixels.
# Default: 900
local AKM_WINDOW_WIDTH=1000

]]> 2330 0 0 0 ]]> https://discovery.endeavouros.com/applications/how-to-install-virt-manager-complete-edition/2021/09/ Tue, 07 Sep 2021 13:45:33 +0000 https://discovery.endeavouros.com/?p=2440

_{Written by s4ndm4n
Cleaned up by joekamprad 10 nov. 2022
joekamprad Added user mode setup and some cleanup (3.4.2023) thanks at Prathamesh on telegram for the hint and the code lines!}

_{joekamprad cleaned off confusing user setupand 3d fix to keep the wiki easy to understand (9.1.2023).}

_{joekamprad bridge-utils moved to AUR (29 january. 2026).}

How to install Virt-Manager

Since its introduction virtualization has come a long way. Nowadays hypervisors are used for almost everything from running enterprise-level servers to testing different operating systems on a local user computer. There are many paid and free hypervisor solutions available in the world.

But in this guide, we are looking at installing one of these best free toolsets used for virtualization and it consists of Virt-Manager, KVM, and QEMU. This guide will show you how to install these tools correctly and with less hassle. Before starting let's get to know this software a bit better.

What is Virt-Manager?

Virt-Manager is a graphical user front end for the library which provides virtual machine management services. The Virt-manager interface makes it easy for the user to create, delete and manipulate virtual machines without going through the terminal.

Virt-manager mainly supports KVM but it can also work with other hypervisors such as Xen and LXC.

When virt-manager is installed it comes with the below-listed tool-set.

• virt-install: Command-line utility to provision OS
• virt-viewer: The UI interface with graphical features
• virt-clone: Command-line tool to clone existing inactive hosts
• virt-xml: Command-line tool for easily editing libvirt domain XML using virt-install’s command-line options.
• virt-bootstrap: Command tool providing an easy way to set up the root file system for libvirt-based containers.

KVM

The letters KVM stands for Kernel-based Virtual Machines. KVM is a Linux full virtualization solution for x86 architecture processors which has the virtualization extension (Intel VT and AMD-V).

KVM is a free (as free beer) and open-source software. The support for KVM is included in all the new Linux kernels by design.

QEMU

QEMU is the shortened version of Quick EMUlator which is a free open-source emulator that can perform hardware virtualization. It emulates the host machine processor through dynamic binary translation. This provides different sets of hardware and device models for the host machine, which enables it to run a variety of guest systems.

KVM can be used with QEMU which allows virtual machines to be run nearly to native speeds. Not just hardware emulation, QEMU is capable of emulating user-level processors which enable applications compiled for one architecture to run on another.

Installing virt-manager

1. Installing all the packages to run virt-manager.

Basic install:

sudo pacman -Syu virt-manager qemu-desktop dnsmasq iptables-nft

Full-featured install:

sudo pacman -Syu --needed virt-manager qemu-desktop libvirt edk2-ovmf dnsmasq vde2 iptables-nft dmidecode

• edk2-ovmf: ovmf is an EDK II based project to enable UEFI support for Virtual Machines.
• iptables-nft: Linux kernel packet control tool (using nft interface).
• Ethernet bridge: https://wiki.archlinux.org/title/Network_bridge (bridge-utils are obsolete)

Note: there is also a package called: qemu-emulators-full

what will install all QEMU user mode and system emulators:

sudo pacman -S qemu-emulators-full

2. After installation completes you need to enable libvirtd service, if you need LXC to be available. For defaul qemu session alone this is not needed.

sudo systemctl enable --now libvirtd.service

3. Check for the status to make sure the service is running.

systemctl status libvirtd.service

Now you will be able to start creating your VM setup over the application.

QEMU connection does not require libvirtd.service running!

Optional Functionality

Package for extra functionality:

• qemu-arch-extra – extra architectures support
• qemu-block-gluster – Glusterfs block support
• qemu-block-iscsi – iSCSI block support
• qemu-block-rbd – RBD block support

Network:

If Network is disabled after rebooting the host machine and you do not find a way to enable it, you can have it enabled per default from the command line. This will work after rebooting the host:

sudo virsh net-autostart default

libguestfs

If you wish to edit the created virtual machine disk images you can install libguestfs. These are set of tools that allow the user to view and edit files inside guest systems, change VM script changes, monitor disk space, create new guests, P2V, V2V, perform backups, clone VMs, and much more.

To install.

sudo pacman -S libguestfs

qemu-block-gluster

Glusterfs is a scalable network filesystem. This adds Glusterfs block support to QEMU.

To install.

sudo pacman -S qemu-block-gluster

qemu-block-iscsi

iSCI enables storage access via a network. qemu-block-iscsi enables QEMU to block this.

To install.

sudo pacman -S qemu-block-iscsi

samba

This would add support to SMB/CIFS support to QEMU.

To install.

sudo pacman -S samba

Installing virtio guest drivers for Windows

RedHat supplies a set of guest drivers for virtio which covers the graphic drivers for the guest system. You can download the latest drivers from their GitHub virtio-win-pkg-scripts page here.

]]> 2440 0 0 0 https://discovery.endeavouros.com/audio/pipewire/2021/09/ Tue, 14 Sep 2021 01:38:13 +0000 https://discovery.endeavouros.com/?p=2519

Pipewire

https://pipewire.org/

Up from the 4th release in 2021 called Atlantis new installs will have pipewire enabled per default.

If you are on older installs you can easily switch to pipewire from pulseaudio:

Installation:

sudo pacman -S --needed pipewire-pulse pipewire-alsa pipewire-jack wireplumber

You can also stay with pipewire-media-session but it is recommended to use wireplumber as pipewire-media-session is/was only there to start creating Session managers like wireplumber:

PipeWire#Session_manager (archwiki)

[icon name="flag" prefix="fas"]

Switching between pipewire-media-session and wireplumber:

In case you want to do so, it is recommended to remove old created configs from using pipewire-media-session, inside your user's configurations:

rm -R ~/.config/pulse ~/.local/state/wireplumber ~/.local/state/pipewire

In addition to clean of stuff not needed under pipewire:

You may need to remove pulseaudio-alsa and pulseaudio-jack packages before that.

The main pipewire package is installed already.

Pipewire uses systemd on userlevel not systemwide for management of the server and automatic socket activation

• pipewire-media-session.service
• wireplumber.service
• pipewire-pulse.socket
• pipewire.socket
• pipewire-pulse.service
• pipewire.service

• pipewire-pulse.socket
• pipewire.socket
• pipewire-pulse.service
• pipewire.service

So nothing else is needed to enable manually it will get enabled automatically on the next boot or if you want to run it without rebooting your system run:

systemctl --user start pipewire-pulse.service

Check if pipewire is running:

pactl info

Server Name should show this:

Server Name: PulseAudio (on PipeWire 0.3.35)

or with inxi:

inxi -Aa

Sound Server-2: PulseAudio v: 15.0 running: no
Sound Server-3: PipeWire v: 0.3.51 running: yes

To complete for different use cases, there are these packages that could be needed in addition:

easyeffects

pipewire-zeroconf

Low-latency audio/video router and processor - Zeroconf support

pipewire-jack

Low-latency audio/video router and processor - JACK support

pipewire-docs

Low-latency audio/video router and processor - documentation

pipewire-alsa

Low-latency audio/video router and processor - ALSA configuration

Cable
https://github.com/magillos/Cable

PyQT GUI application to dynamically modify Pipewire and Wireplumber settings at runtime. Now, with side by side connections manager

Coppwr

https://github.com/dimtpap/coppwr

Low level control GUI for PipeWire

Hdajackretask

https://github.com/alsa-project/alsa-tools/tree/master/hdajackretask
part of alsa-tools package (only for hda_intel driver audio chips)

Automatic switching Bluetooth Headphone into Headset mode if you need Headset mode for microphone usage:

https://forum.endeavouros.com/t/pipewire-stable-enough/16944/29?u=joekamprad

it will not switch automatically, this needs to be enabled..

This will only work if pipewire-media-session is installed for wireplumber you need to use a different setup.

mkdir -p ~/.config/pipewire/media-session.d

cp /usr/share/pipewire/media-session.d/bluez-monitor.conf ~/.config/pipewire/media-session.d/bluez-monitor.conf

nano ~/.config/pipewire/media-session.d/bluez-monitor.conf

and uncomment the line bluez5.autoswitch-profile = true and set it to true ….

save the file .. restart system or services:

systemctl --user restart pipewire pipewire-pulse

Working exactly as it says... if you start recording it enables Headset profile and seamlessly turns it back of, when you are stop recording…

Switch from pipewire to pulseaudio:

https://discovery.endeavouros.com/audio/pulseaudio/2021/12/

]]> 2519 0 0 0 Pulseaudio]]> Pulseaudio]]> Pulseaudio]]> https://discovery.endeavouros.com/storage-and-partitions/how-to-permanently-mount-external-internal-drives-in-linux/2022/02/ Tue, 01 Feb 2022 10:08:08 +0000 https://discovery.endeavouros.com/?p=2622

When using external drives we have to manually mount them every time we log in to our Linux distribution or every time we want to use them. If you don't remove them and use the drives as permanently connected external storage devices it would be great if we could auto-mount them every time we log in to the system.

In this article, we will be looking at how to configure these external drives as automounted permanent storage devices. Using this method you can mount almost all external drives (Externalahrd drives, USB Sticks .... etc.) or your internal drives.

NOTE1: Please replace all the values within < > with your own values.

NOTE2: All commands should be used in the terminal.

1. Identifying the drive and its device label. To achieve this you can use the command lsblk in your terminal. !

• In the above image the main three letters at the top of each tree view is the device label. Ex: sda.

• The three letters followed by a number under the main three letters above the tree view are the partitions. Ex: sda1, sda2, .... etc.

• In the above image I already have my externals mounted. The drives from sdc below are my externals. In your case, you would only see the drive label and the partition without a mount point in front of the partition details. So don't panic it will get listed once we finish the mounting steps.

2. After identifying the drive label make note of it or remember the correct label. Now we have to make a new folder as the mount point for our external drive. You can use /mnt or /run/media (Becarfule using this because It is usually a temporary file system not intended to hold persistent data) or any other location but I'm going to use `/mnt` for this tutorial. To make the new folder we can use the mkdir command.

sudo mkdir /mnt/<your mount folder name>

• You have to use sudo otherwise you will get a permission denied error.

3. We still can't use the new folder we created in the above step. Due to using sudo the new folder belongs to root not to your user. So we have to get ownership of the folder before continuing to other steps. To do this we use the chown command.

sudo chown -R <your user name>: <your user group> /mnt/<folder name you created>

• User group is similar to your user name. Ex: if your user name is ben then your user group will be ben. Unless you changed the user group.
• -R switch makes the command operate on a file or a directory recursively.

4. After owning the folder we still can't write to the folder so we need to give the folder read and write permissions. To do that, we can use the chmod command.

sudo chmod -R 744 /mnt/<folder name you created>

• Number 744 means you have assigned read/write/execute permissions to your user account. You have given read/write permissions to your group and others.

5. There are many ways we can use to mount drives using fstab but the best way is to use UUID to map the drives. So before we continue to the next step we need to find the UUID s of the drive/s that you're mounting. To find the IDs, we can use `ls` or blkid. I personally prefer blkid.

Using sudo blkid <your mount device lablel>

Using sudo ls-l /dev/disk/by-uuid

6. After finding the UUID of your drive it is time to move on to editing the fstab file. Before starting the edit it's always good to make a backup of the file. We can use the cp command to make back up.

sudo cp /etc/fstab /etc/fstab.bkp

• Above command will make another copy named fstab.bkp so if anything goes wrong you can use that file to restore the original file.

7. Open the fstab file in your favorite text editor.

sudo nvim /etc/fstab or sudo nano /etc/fstab or sudo vim /etc/fstab

The file should look something like below,

8. Add the below code to the end of the fstab file.

UUID=<UUID of your external device> /mnt/<your mount point>       <file system Ex: ext4>    noatime,x-systemd.automount,x-systemd.device-timeout=10,x-systemd.idle-timeout=1min 0 2

• I'm using systemd.automount and systemd.device-timeout.

• system.automount: Automount units may be used to implement on-demand mounting as well as parallelized mounting of file systems. You can find more information here.

• systemd.device-timeout: Configures an idle timeout. Once the mount has been idle for the specified time, systemd will attempt to unmount. For more detail go here.

• Using systemd is much better because using other methods sometimes the boot gets stuck if the external device fails to mount. But using this method boot continues after the time mount times out.

After editing fstab should look like below,

9. Once making sure everything in the fstab is correct save and exit the editor. To make sure there are no errors mount the drives using the below command.

sudo mount -a

• Above command will automount all the unmounted drives in the fstab file.

• If there's an issue with the file you will see error output in the terminal.

10. If there are no errors then it's all good. You can test your new mounted drive now. Afterward, you can do a system reboot and verify that the automount is working. The newly mounted drives should show up in your file manager.

Conclusion

This brings us to the conclusion of this tutorial. I hope this tutorial is simple enough so anyone can understand and follow it without any issue. Using UUID and systemd is the best way I found to mount drives.

]]> 2622 0 0 0 https://discovery.endeavouros.com/audio/audiophile/2022/01/ Sat, 08 Jan 2022 09:06:06 +0000 https://discovery.endeavouros.com/?p=2970

This article covers configuring audio for optimal playback quality in Arch Linux.

---

Table of contents:

1. Changing sample rate
2. Resampling quality
3. USB DAC's
4. Recommended software

---

Changing sample rate

By default PipeWire sets a global sample rate of 48kHz. If you need to change it (e.g. you own a DAC supporting a higher value) you can do it by editing the line default.clock.rate = 48000 in the configuration file ~/.config/pipewire/pipewire.conf. For example, if you want 192kHz, uncomment and change value 48000 to default.clock.rate = 192000.

PipeWire can also change output sample rates supported by your DAC. To configure, uncomment and set the line default.clock.allowed-rates = [ 48000 ], for example, [ 44100 48000 88200 96000 ]. The sample rate follows the sample rate of the audio stream being played when the card is idle.

To check out which output sample rate and sample format are the data sent to DAC (probably you need to change digits):

cat /proc/asound/card0/pcm0p/sub0/hw_params

To check out which input sample rate is used, change pcm0p to pcm0c (c is short for "capture", p is for "playback").

---

Resampling quality

If you used PulseAudio with resample-method = speex-float-10 or soxr-vhq, then you might consider uncommenting and changing resample.quality = 4 to 10 or the maximum 15 in stream.properties block in both ~/.config/pipewire/client.conf and ~/.config/pipewire/pipewire-pulse.conf (copy them from /usr/share/pipewire/ if they do not exist). Do not forget to restart PipeWire (without sudo): systemctl --user restart pipewire.service pipewire-pulse.socket (never forget pipewire-pulse.socket if you want your config changes to be applied).

There is a very little quality difference between 10 and 15, but the CPU load difference is 2-3x. And the latency difference between 4, 10, 15 is yet to be investigated by anybody. resample.quality = 15 on 44100→48000 Hz on Ryzen 2600 causes pipewire or pipewire-pulse processes to cause 4.0% one CPU core load.

PipeWire uses its own resampling algorithm called Spa. Like with SoX's sox, Speex's speexenc, PipeWire includes its standalone version: spa-resample. Usage:

spa-resample -q 15 -f s24 -r 48000 input16bit44100orAnythingElse.wav output24bit48000hz.wav

It is probably somehow possible to use other resamplers by creating your own sink. Or just use a plugin in your music player (e.g., Qmmp has SoX plugin).

[icon name="lightbulb" prefix="fas"]

TIP: Try to use ALSA output when possible, and avoid unnecessary resampling. Check the current status with pw-top. If the "RATE" column of the default sink matches that of the application outputting audio, pipewire is not resampling the signal.

USB DAC's

Changing sample rates or formats might help reduce latency with some DACs.

wireplumber (default):

Using matching rules using wireplumber (package) we can set properties for devices.

mkdir -p ~/.config/wireplumber/main.lua.d
cp /usr/share/wireplumber/main.lua.d/50-alsa-config.lua ~/.config/wireplumber/main.lua.d/50-alsa-config.lua

And edit the file accordingly to your needs.

~/.config/wireplumber/main.lua.d/50-alsa-config.lua

--["audio.rate"] = 96000,
--["audio.allowed-rates"] = "32000,96000",

pipewire-media-session:

Using matching rules using pipewire-media-session (package) we can set properties for devices.

Copy the default configuration of alsa-monitor.conf for pipewire-media-session into ~/.config/pipewire/media-session.d. Then append a new rule-block similar to the following one:

~/.config/pipewire/media-session.d/alsa-monitor.conf

rules = {
…
{
matches = [
{
node.name = "alsa_output."
}
]
actions = {
update-props = {
audio.format = "S24_3LE"
audio.rate = 96000
# Following value should be doubled until audio doesn't cut out or other issues stop occurring
api.alsa.period-size = 128
}
}
}
…
}

alsa_output.<name of node> node can be obtained using pw-top.

Your DAC might support a different format or sample rate. You can check what your DAC supports by querying ALSA:

First get the card number of your DAC:

aplay -l

…
card 3: S2 [Schiit Hel 2], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
…

So in this example it would be card 3. Get all supported sample rates and formats:

cat /proc/asound/cardX/streamX

…
Playback:
…
Interface 1
Altset 1
Format: S16_LE
Channels: 2
Endpoint: 0x05 (5 OUT) (ASYNC)
Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
Data packet interval: 125 us
Bits: 16
…
Interface 1
Altset 2
Format: S24_3LE
Channels: 2
Endpoint: 0x05 (5 OUT) (ASYNC)
Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
Data packet interval: 125 us
Bits: 24
…
Interface 1
Altset 3
Format: S32_LE
Channels: 2
Endpoint: 0x05 (5 OUT) (ASYNC)
Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
Data packet interval: 125 us
Bits: 32
…
…

In this case S16_LE, S24_3LE, S32_LE are the supported formats and 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000 are the supported sample rates across all formats.

---

Recommended software

deadbeef: Modular GTK audio player for GNU/Linux.

yay -S deadbeef

audacious: Lightweight, advanced audio player focused on audio quality.

pacman -Syu audacious

strawberry: A music player aimed at audio enthusiasts and music collectors.

pacman -Syu strawberry

Sources / Further reading:

https://wiki.archlinux.org/title/PipeWire

https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/home

]]> 2970 0 0 0 https://discovery.endeavouros.com/applications/video-playback/2022/01/ Sun, 09 Jan 2022 05:28:44 +0000 https://discovery.endeavouros.com/?p=2992

This article provides some background on video playback in Arch Linux.

---

Table of contents:

1. Introduction
2. Verification
3. Configuring mpv
4. Recommended software

---

Introduction

Hardware video acceleration makes it possible for the video card to decode/encode video, thus offloading the CPU and saving power.

There are several ways to achieve this on Linux:

• VA-API - is a specification and open source library to provide both hardware accelerated video encoding and decoding, developed by Intel.
• VDPAU - is an open source library and API to offload portions of the video decoding process and video post-processing to the GPU video-hardware, developed by NVIDIA.
• NVDECODE/NVENCODE - NVIDIA's proprietary APIs for hardware video acceleration, used by NVIDIA GPUs from Fermi onwards.

---

Verification

Your system may work perfectly out-of-the-box without needing any configuration. Therefore it is a good idea to start with this section to see that it is the case.

• mpv with its command-line support is great for testing hardware acceleration. Look at the log of mpv --hwdec=auto video_filename and see hwdec for more details.
• For Intel GPU, use intel-gpu-tools and run intel_gpu_top as root to monitor the GPU activity during video playback for example. The video bar being above 0% indicates GPU video decoder/encoder usage.
• For AMD GPU, use radeontop to monitor GPU activity. Unlike intel-gpu-tools, there is currently no way to see decode/encode usage on radeontop.
• For any GPU, you can compare CPU usage with a tool like htop. Especially for higher resolution videos (4k+), CPU usage when VA-API is enabled and working should be dramatically lower on laptops and other relatively low-power devices.

[icon name="lightbulb" prefix="fas"] TIP: When watching a YouTube video, right-click the video and select "stats for nerds". This pop-up displays useful information like media codecs, dropped frames, etc.

VA-API

Verify the settings for VA-API by running vainfo, which is provided by libva-utils:

vainfo

VAEntrypointVLD means that your card is capable to decode this format, VAEntrypointEncSlice means that you can encode to this format.

In this example the i965 driver is used, as you can see in this line:

vainfo: Driver version: Intel i965 driver for Intel(R) Skylake - 1.7.3 

If the following error is displayed when running vainfo you need to configure the correct driver:

libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

VDPAU

Install vdpauinfo to verify if the VDPAU driver is loaded correctly and retrieve a full report of the configuration:

vdpauinfo

---

Configuring mpv

Example configuration file:
~/.config/mpv/mpv.conf

# Use GPU-accelerated video output by default.
vo=gpu
# Use quotes for text that can contain spaces:
term-status-msg="Time: ${time-pos}"

Hardware accelerated video decoding is available via hwdec=API option. For list of all supported APIs and other required options see relevant manual section.

For Wayland use gpu-context=wayland option. For list of other available GPU APIs see manual.

---

Recommended software

vlc: Multi-platform MPEG, VCD/DVD, and DivX player.

pacman -S vlc

mpv: a free, open source, and cross-platform media player.

pacman -S mpv

ff2mpv: This is a Firefox addon for playing URLs in MPV.

yay -S ff2mpv-native-messaging-host-git

https://addons.mozilla.org/en-US/firefox/addon/ff2mpv/

enhanced-h264ify: Extension for Firefox/Chrome which blocks YouTube VP8/VP9 codecs, to use H264 only.

https://addons.mozilla.org/en-US/firefox/addon/enhanced-h264ify/

https://chrome.google.com/webstore/detail/enhanced-h264ify/omkfmpieigblcllmkgbflkikinpkodlk

youtube-dl-git: A small command-line program to download videos from YouTube and a few more sites.
yt-dlp: A youtube-dl fork with additional features and fixes.

yay -S youtube-dl-git

yay -S yt-dlp-drop-in

Sources / Further reading:
https://wiki.archlinux.org/title/Hardware_video_acceleration

]]> 2992 0 0 0 https://discovery.endeavouros.com/window-tiling-managers/qtile/2022/01/ Sun, 09 Jan 2022 09:12:32 +0000 https://discovery.endeavouros.com/?p=3031

A full-featured, hackable tiling window manager written and configured in Python.

---

About community edition

[icon name="share" prefix="fas"] Github | Forum

• Terminal: xfce4-terminal
• File manager: pcmanfm-gtk3
• Launcher: rofi
• Notifications: dunst
• Wallpaper: feh
• Compositor: picom

Configuration

• Main config file: ~/.config/qtile/config.py
• Keybindings: ~/.config/qtile/modules/keys.py
• Bar: ~/.config/qtile/modules/screens.py
• Widgets: ~/.config/qtile/modules/widgets.py
• Auto-start: ~/.config/qtile/autostart.sh

Keybindings

Documentation:
https://docs.qtile.org/en/latest/

]]> 3031 0 0 0 https://discovery.endeavouros.com/gaming/gaming-101/2022/01/ Sun, 09 Jan 2022 11:31:52 +0000 https://discovery.endeavouros.com/?p=3047

The following article will help you take the first steps towards gaming on Arch Linux.

---

Table of contents:

1. Requirements
2. Additional Software
3. G-Sync
4. Glossary
5. Resources

Sources:
Linux gaming guide by @keybreak

Requirements

1. Check if your GPU supports Vulkan

Search for your GPU in the database;

[icon name="check" prefix="fas"] If there's an entry you're good to go!
[icon name="times" prefix="fas"] Not on the list? That means your GPU is too old to support Vulkan. Without it, DXVK won't work and performance and compatibility will be worse. However you still can game;

• Skip next steps: 3. Install Vulkan and 4. Install Vulkan driver for your GPU driver.
• Make sure to disable DXVK/D3DVK globally in Lutris and Steam.

2. Install Vulkan

vulkan-icd-loader
lib32-vulkan-icd-loader

3. Install GPU specific Vulkan

Nvidia

nvidia-utils
lib32-nvidia-utils

AMD AMDVLK

amdvlk
lib32-amdvlk

AMD RADV

vulkan-radeon
lib32-vulkan-radeon

Intel

vulkan-intel
lib32-vulkan-intel

Hybrid / Optimus GPU

ArchWiki

---

Additional Software

GameMode is a daemon that automatically optimizes your system while playing games.

pacman -S gamemode

MangoHud is an in-game overlay, it can display useful information and cap FPS.

yay -S mangohud

ProtonUp-Qt is a GUI tool to manage different versions of GE Proton.

yay -S protonup-qt

DOSBox is an emulator for MS-DOS games.

pacman -S dosbox

EmulationStation is a front-end for emulating retro games.

yay -S emulationstation

---

G-Sync

Getting Nvidia G-sync to work properly on Linux may require some additional steps.

The most important consideration is the window manager's compositor, specifically the ability to re-direct fullscreen windows. Most compositors are capable of doing this, those that cannot will need to be either disabled temporarily or swapped out.

Besides this, usage of a frame limiter is neccassary to ensure all rendered frames stay within the G-Sync range of the monitor, slightly below the maximum refresh rate. For example if your monitor is 144 Hz, cap it at approximately 142 fps. MangoHud is the easiest way to accomplish this, execute it as a run command within Lutris or Steam.

How to tell if G-Sync is actually enabled? Open nvidia-settings, navigate to "OpenGL settings" then tick the boxes "enable G-sync visual indicator" and "enable graphics API visual indicator". Now launch a game and check the top left corner overlay, it should say "FLIP" and "G-SYNC" in green letters. In-game V-Sync should also be enabled.

Compatible compositors:

• Compton / Picom
• Compiz
• KWin
• Mutter
• Muffin

Config files

Check the following config files and set the values as indicated;

~/.config/picom.conf

unredir-if-possible = true;
vsync = true;
refresh-rate = 0;

~/.config/MangoHud/MangoHud.conf

#change to your desired fps cap
fps_limit=60
#to hide the overlay
no_display

XFCE users

Make sure that xfwm vblank mode is set to glx, by typing this command in terminal:

xfconf-query -c xfwm4 -p /general/vblank_mode -t string -s "glx" --create

To prevent flickering on the desktop, add a new rule under "application profiles" in nvidia-settings:

This feature = process name (procname)
Matches this string = xfwm4
Profile name = no_gsync
Key = GLGSYNCAllowed
Value = false

---

Glossary

Platforms

Platform	Pros	Cons
Linux Steam	• Very easy to use • Performance same or better than Windows & Native • Big community	• Based on proprietary Steam client made by Valve • Game library and saves depends on Valve (unless manually backup)
Linux Wine	• Easy when you know how • Performance same or better than Windows & Native • Big community • FOSS • Gives you 100% control of your engine, data and games	• Requires some knowledge or tools for ease of use • May break on updates if always using latest engine (not recommended practice!)
Linux Native	• Best performance	• May break on updates, unless sandboxed • Currently limited number of games

Common terms

Term	Description
PREFIX / WINEPREFIX	Separate directory inside your Linux, which represents a "Windows" machine, it's drives, folders, registry, etc.
Engine / (Wine / Proton)	• Allows you to run Windows programs on Linux • Downgrade / update engine version for any PREFIX
ARCH	Architecture of PREFIX is win64 or win32 based on chosen Engine [icon name="exclamation" prefix="fas"] You can use only one ARCH for PREFIX since it's created, in most cases you should use win64!
dll override / WINEDLLOVERRIDES	It's not always possible to run an application on builtin DLLs. Sometimes native DLLs simply work better. You can override any dll in your PREFIX, these DLL overrides can be set using winecfg or use the WINEDLLOVERRIDES environment variable to set them. Options available: • native (=n) • builtin (=b) • disable (=) • native, builtin (=n,b) • builtin, native (=b,n)
Winetricks / Protontricks	Very important tool in your arsenal to tweak PREFIX and overcome some known problems, or install Windows libraries, to cover unfinished parts of Wine.
DXVK	Vulkan-based translation layer for DirectX 9 / 10 / 11 Probably the most important project for gaming on Linux!
VKD3D	Aims to implement the full DirectX 12 API on top of Vulkan. [icon name="exclamation-triangle" prefix="fas"] Early in development, may have lots of bugs and performance problems.
Esync	Removes wineserver overhead for synchronization objects. This can increase performance for some games, especially ones that rely heavily on the CPU.
Fsync	More recent alternative with even better performance improvements, then Esync. However, you do need an Engine and Kernel that supports it.

Engines

Engine	Description
Wine	The most important project for the topic at hand, in 1993 there were bunch of absolutely insane people who decided to reverse-engineer Windows proprietary software and redirect it to Linux native FOSS style for future compatibility.
Wine staging	It contains bug fixes and features, which have not been integrated into the development branch yet. The idea of Wine Staging is to provide experimental features faster to end users and to give developers a way to test their patches before being integrated into the main branch.
Proton	A fork of Wine maintained by Valve / Steam. And what a great boost it gave for Linux gaming! It is basically a set of patches; • DXVK enabled by default • Esync ready • Fsync ready Made to work with Steam, so keep this in mind when hearing term "Protonified"! Although it's not officially recommended, you can easily use Proton with Wine directly.
Wine-TKG  Proton-TKG	Custom bleeding edge builds by Tk-Glitch, may greatly improve compatibility or performance, especially with new games! • Esync ready • Fsync ready If you have new game which doesn't work from day 1 - try this, most likely will be the first build to run your game.
Wine-GE Proton-GE	Custom bleeding edge builds by GloriousEggroll "the most patched Wine", may greatly improve compatibility or performance, especially with new games! • Esync ready • Fsync ready • vkd3d ready If you have new game which doesn't work from day 1 - try this, it most likely will be the first build to run your game.

---

Resources

Project	Repository	Devs	Bugs	Wiki	Support
DXVK	GitHub	doitsujin, Joshua-Ashton	GitHub	Wiki
VKD3D	GitHub (Proton) Git (Wine)	Józef Kucia (RIP), Alexandre Julliard, Hans-Kristian Arntzen	GitHub	Wiki
Lutris	Website, Database	Mathieu Comandon	GitHub	Wiki	Donate
Wine	Website, Database	army of them	Bugzilla	Wiki, Docs	Donate
Wine staging	GitHub	zfigura, alesliehughes	Bugzilla	Wiki	Patreon
Proton	GitHub, Database	Valve	GitHub	Wiki, Options	Patreon (protondb)
Wine-TKG Proton-TKG	GitHub	Frogging-Family	Bugs	GitHub	Patreon
Wine-GE Proton-GE	GitHub (Wine) GitHub (Proton)	GloriousEggroll, Credits		GitHub	Patreon
PlayOnLinux (Phoenicis)	Website, Binaries	qparis, plata	GitHub (Winebuild)

]]> 3047 0 0 0 https://discovery.endeavouros.com/gaming/steam-lutris-wine/2022/01/ Sun, 09 Jan 2022 11:33:04 +0000 https://discovery.endeavouros.com/?p=3059

This article will guide you through the setup of game launchers on Arch Linux.

---

Table of contents:

1. Steam
2. Lutris
3. Wine

Sources:
Linux gaming guide by @keybreak

Steam

[icon name="book" prefix="fas"] TL;DR

1. Enable Proton in Steam play.
2. Check your game in protondb for game state / recommendations.
3. Problems? Try GloriousEggroll or TK-Glitch engines or see full 4.4 Problems section.

• Config location: ~/.steam
• Proton engines location: ~/.steam/steam/steamapps/common

Keep in mind that Proton will be installed in the same library as the first Steam Play game you try to launch, and will only be installed in one location.

• Game PREFIX location, where [appid] is your game id: (look up steamdb if in doubt)
  ~/.steam/steam/steamapps/compatdata/[appid]/pfx/

More Proton FAQ

1. Setup

1. Install package:

pacman -S steam

Make sure to select a valid vulkan package fitting your used GPU (graphics-card) it will show up like this:

And read the output of the install process to make sure inserting the correct number.

2. If using a controller, also install:

yay -S game-devices-udev

3. Launch client and login to your account.
4. Enable Proton to play Windows games with Linux Steam;
   • Steam -> Settings -> Steam Play
   • [icon name="check" prefix="fas"] Enable Steam Play for supported titles.
   • [icon name="check" prefix="fas"] Enable Steam Play for all other titles.
   • [icon name="caret-square-down" prefix="fas"] Run other titles with...
     (here you can choose a Proton version which will be used globally)

2. Install games

Now you're ready to install games!

1. Download game.
2. Go to Library tab.
3. Select your game title on left panel.
4. Hit Play!

3. Configuration

To configure Proton through Environment variables, which you may see in protondb reports;
(see available options)

1. Select game title on left panel.
2. Right [icon name="mouse" prefix="fas"] Button -> Properties -> Set launch options…
3. Enter desired variables, separated by a space and ending with %command%

• To disable variable, add =0 after
• To enable, use non 0 values
• For example, let's enable DXVK HUD
  DXVK_HUD=full %command%
• Install additional original Windows libraries with Winetricks (if required), where [appid] is your game id:
  (look up steamdb if in doubt)
  WINEPREFIX="~/.steam/root/steamapps/compatdata/[appid]/pfx/" winetricks "win7"

To use specific version of Proton for specific game (may be useful if latest has problems);

1. Select game title on left panel.
2. Right [icon name="mouse" prefix="fas"] Button -> Properties
   • [icon name="check" prefix="fas"] Force the use of a specific Steam Play compatibility tool.
   • [icon name="caret-square-down" prefix="fas"] From dropdown menu choose Proton engine.

Install custom Proton engine;
(eg. GloriousEggroll or TK-Glitch)

1. Create ~/.steam/root/compatibilitytools.d directory, if it does not exist.
2. Extract archive to ~/.steam/root/compatibilitytools.d
3. Restart Steam.
4. Select custom Proton engine for specific game or globally.

• Change default location for games library;
  • Steam -> Settings -> Downloads -> Steam library folders
  • Add library folder
    (you can choose for example another drive)
  • Right [icon name="mouse" prefix="fas"] Button -> Make Default folder
    (if you want it as default)

• If you want to use NTFS disks with Linux Steam: Using a NTFS disk with Linux and Windows
• Create log file to check if everything fine or file a bug, use Environment variable:
  PROTON_LOG=1 %command%
• Log will be saved at this location, where [appid] is your game id (look up steamdb if in doubt):
  ~/steam-[appid].log

4. Problems

• Game doesn't launch or crash:
  • See if there are some known solutions to problems of this game at protondb or lutris.
  • Try to disable DXVK PROTON_USE_WINED3D=1 %command% If it works without DXVK.
  • Still doesn't work? Check Requirements and Proton bugs. If you have an AMD GPU check this.
• Game stuttering on first launch:
  • This is normal, because shaders have to be loaded first. They are written directly into shader cache.

---

Lutris

Best all-around game launcher, can be used for: Wine, Steam, Native, Emulators
See how at 2. Configuration and 4. Game configuration.

• Config locations:
  ~/.config/lutris
~/.local/share/lutris
• Icons created by Lutris (might be useful to backup / transfer your library):
  ~/.local/share/icons/hicolor/128x128/apps
• Wine / Proton engines location:
  ~/.local/share/lutris/runners/wine
• A lot of useful libraries & runtimes which for example allow to easily run Proton without steam client!
  ~/.local/share/lutris/runtime

1. Setup

Install package:

pacman -S lutris

2. Configuration

You can configure Defaults for each runner (default settings when you add new game).

1. On left panel hover [icon name="mouse" prefix="fas"] over Wine tab and select [icon name="cog" prefix="fas"] cog.
2. [icon name="check" prefix="fas"] Show advanced options on bottom left.
3. Runner options tab:
   • Wine version - most important, here you can set / update the default Engine which will be used for all games. It can use anything installed: System, PlayOnLinux, Steam, or any Engine put in:
     text ~/.local/share/lutris/runners/wine
text ~/.PlayOnLinux/wine/linux-amd64
   • [icon name="check" prefix="fas"] Enable DXVK/VKD3D - useful to turn off globally, if your GPU doesn't support Vulkan.
4. System options tab:
   • [icon name="check" prefix="fas"] Restore resolution on game exit. (may be useful in some cases)
   • [icon name="check" prefix="fas"] Switch to US keyboard layout. (may solve problems for multi-lingual inputs)

3. Add game

1. Press [icon name="plus" prefix="fas"] to add a game, let's do a minimal setup required to start.
2. Game info tab
   • Name - enter name of your game, you can name it whatever makes sense for you.
   • Runner - select Wine.
   • Release year - optional, but nice in case you have big library.
     (you can look up year of your game in PCgamingWiki)
3. Game options tab
   • Executable
     Some games have multiple executables, prefer x64 ones first!
     text ~/.PlayOnLinux/wineprefix/Crysis/drive_c/Games/Crysis/Bin64/Crysis.exe
   • Wine prefix
     text ~/.PlayOnLinux/wineprefix/Crysis
4. Save - your game will now be available on the list.
5. If there's no game image, that's caused by Name not being exactly identical to its database one.
   Fix with Identifier. Look up the game on Lutris db
   Get this ID: https://lutris.net/games/crysis/ and paste it into Game settings.
6. Select game, Right [icon name="mouse" prefix="fas"] Button -> Configure
7. Identifier Change and paste crysis.
8. Apply
9. Save

4. Game configuration

Here are some essential configuration options to know.

1. Select game, Right [icon name="mouse" prefix="fas"] Button -> Configure
2. Runner options tab:
   • Wine version - you can force Engine for a specific game (will be used even if you change global, so don't forget to change that option back if needed).
   • [icon name="check" prefix="fas"] Enable DXVK/VKD3D in most cases it's best to use, but can be toggled in case of problems.
   • DXVK version - you can force specific DXVK version for a specific game, in case of problems.
   • [icon name="check" prefix="fas"] Enable Esync - best to enable in most games which heavily use CPU or to avoid stuttering.
   • [icon name="check" prefix="fas"] Enable Fsync - same as Esync. Should be better, but Engine and Kernel must support it! (Lutris will alert you if it's not supported by Engine in use)

3. System options tab:
   • [icon name="check" prefix="fas"] Disable Lutris runtime
4. Game options tab:
   • Arguments - a very useful option to pass game command-line options.
     (for example in Crysis to force DirectX 10 mode: -dx10)
5. Install game.

Lutris can auto-install the required Engine and Winetricks. Also you can download an Install script.
[icon name="exclamation" prefix="fas"] Install scripts are not always a recommended method of installation;

• Scripts are made by regular users and can be outdated or not follow current best practices.
• Scripts can use a win32 Engine. (you can change Wine / Proton version later, but not it's ARCH!)

1. Find your game from Lutris (or on Lutris db) Search -> Search Lutris.net
2. Select game, Install
3. Choose Installer script to use, it can be either of; Wine / Steam / Emulator - choose wisely!
4. From now on follow dialogs and install whatever is offered to you.
5. Turn off Lutris search mode, now it will be available in your games library and you can begin playing.

[icon name="lightbulb" prefix="fas"] TIP: When using Proton or Protonified engine with Lutris you MUST use option:
Disable Lutris runtime either globally or for specific game.

---

Wine

[icon name="book" prefix="fas"] TL;DR

1. Create non-system WINEPREFIX with non-system Wine (amd64):
   POL (staging-linux-amd64, upstream-linux-amd64)
   [icon name="exclamation" prefix="fas"] It's better to use separate prefix for each game.
2. Check protondb and lutris for game state / recommendations.
3. Install game. (prefer DRM-free installers like GOG)
4. Use Lutris as launcher.
5. Enable DXVK and Esync.
6. Problems? Try GloriousEggroll or TK-Glitch engines, or see full 7. Problems section.

[icon name="lightbulb" prefix="fas"] TIP: Do NOT launch wine / winetricks directly from launcher or terminal without ENVIRONMENT VARIABLES, as this will add unnecessary stuff and mess with your mime-associations, icons, etc.

• Default WINEPREFIX for system version of Wine:
  (not needed for games, can be safely removed if not used by anything else)
  ~/.wine
• Mono (FOSS .NET by Wine) & Gecko (FOSS Internet Explorer by Wine) installers location:
  (both auto-installed while creating WINEPREFIX)
  ~/.cache/wine
• Winetricks downloaded installers location:
  ~/.cache/winetricks

1. Prepare

Create the following bash scripts and make them executable with chmod;

create-structure.sh

#!/bin/bash
title=$(basename "$0")
echo -n -e "\033]0;$title\007"

# Colors
c0=

\e[0m'
c1=$(tput setaf 202)
c2=$(tput setaf 154)
b0=

\e[25m'
b1=

\e[5m'

# Force output in english
export LC_ALL=en_US.UTF-8

# OPTIONS
WINE_ROOT="$HOME/.PlayOnLinux"

STRUCTURE=(
    "$WINE_ROOT"
    "$WINE_ROOT/wineprefix"
    "$WINE_ROOT/wine"
    "$WINE_ROOT/wine/linux-amd64"
    "$WINE_ROOT/wine/linux-x86"
)


main() {

    create_structure
}


create_structure() {

    echo
    echo "   ---------------   Create structure   ---------------   "
    echo

    for path in "${STRUCTURE[@]}";
    do
        if [ ! -e "$path" ];
        then
            mkdir -p "$path" \
            && echo "${c2}[+]${c0} ${path}" \
            || echo "${c1}[${b1} ${b0}]${c0} ${path}"
        else
            echo "${c2}[x]${c0} ${path}"
        fi
    done

    echo
    echo "${c2}Script finished!${c0}"
}

main "$@"

create-prefix.sh

#!/bin/bash
title=$(basename "$0")
echo -n -e "\033]0;$title\007"

# Colors
c0=

\e[0m'
c1=$(tput setaf 202)
c2=$(tput setaf 154)
b0=

\e[25m'
b1=

\e[5m'

# Force output in english
export LC_ALL=en_US.UTF-8

# OPTIONS
NAME="GameName"
ENGINE="5.11-staging"
ARCH="amd64"

WINE_ROOT="$HOME/.PlayOnLinux"
PREFIX="${WINE_ROOT}/wineprefix/${NAME}"
WINE="${WINE_ROOT}/wine/linux-${ARCH}/${ENGINE}"
LOADER="${WINE}/bin/wine"
SERVER="${WINE}/bin/wineserver"


main() {

    create_prefix
}


create_prefix() {

    echo
    echo "   ----------------   Create prefix   -----------------   "
    echo

    ARCH=$([ "$ARCH" == "amd64" ] && echo "win64" || echo "win32")

    env WINEARCH="$ARCH" WINEPREFIX="$PREFIX" WINELOADER="$LOADER" WINESERVER="$SERVER" WINEDEBUG="-all" wineboot
    env WINEPREFIX="$PREFIX" WINE="$LOADER" WINESERVER="$SERVER" winetricks isolate_home mimeassoc=off

    echo
    echo "${c2}Script finished!${c0}"
}

main "$@"

install.sh

#!/bin/bash
title=$(basename "$0")
echo -n -e "\033]0;$title\007"

# Colors
c0=

\e[0m'
c1=$(tput setaf 202)
c2=$(tput setaf 154)
b0=

\e[25m'
b1=

\e[5m'

# Force output in english
export LC_ALL=en_US.UTF-8

# OPTIONS
SETUP="Setup.exe"
NAME="GameName"
ENGINE="5.11-staging"
ARCH="amd64"

WINE_ROOT="$HOME/.PlayOnLinux"
PREFIX="${WINE_ROOT}/wineprefix/${NAME}"
WINE="${WINE_ROOT}/wine/linux-${ARCH}/${ENGINE}"
LOADER="${WINE}/bin/wine"
SERVER="${WINE}/bin/wineserver"


main() {

    run "${SETUP}"
}


run() {

    echo
    echo "   ---------------------   Run   ----------------------   "
    echo

    local file="$1"
    [ -f "$file" ] || exit_error "$file doesn't exist"

    if echo "$file" | grep -iq '.msi';
    then
        echo "${c2}[>] run .msi ${c0} $file"
        env WINEPREFIX="$PREFIX" WINELOADER="$LOADER" WINESERVER="$SERVER" WINEDEBUG="-all" WINEDLLOVERRIDES="winemenubuilder.exe=d" msiexec /i "$file"
    else
        echo "${c2}[>] run .exe ${c0} $file"
        env WINEPREFIX="$PREFIX" WINELOADER="$LOADER" WINESERVER="$SERVER" WINEDEBUG="-all" WINEDLLOVERRIDES="winemenubuilder.exe=d" "$LOADER" "$file"
    fi

    echo
    echo "${c2}Script finished!${c0}"
}

main "$@"

tricks.sh

#!/bin/bash
title=$(basename "$0")
echo -n -e "\033]0;$title\007"

# Colors
c0=

\e[0m'
c1=$(tput setaf 202)
c2=$(tput setaf 154)
b0=

\e[25m'
b1=

\e[5m'

# Force output in english
export LC_ALL=en_US.UTF-8

# OPTIONS
TRICKS=(
    win7
)
NAME="GameName"
ENGINE="5.11-staging"
ARCH="amd64"

WINE_ROOT="$HOME/.PlayOnLinux"
PREFIX="${WINE_ROOT}/wineprefix/${NAME}"
WINE="${WINE_ROOT}/wine/linux-${ARCH}/${ENGINE}"
LOADER="${WINE}/bin/wine"
SERVER="${WINE}/bin/wineserver"


main() {

    tricks
}


tricks() {

    echo
    echo "   --------------------   Tricks   --------------------   "
    echo

    printf "%s\n" "${TRICKS[@]}"

    env WINEPREFIX="$PREFIX" WINE="$LOADER" WINESERVER="$SERVER" winetricks "${TRICKS[@]}"

    echo
    echo "${c2}Script finished!${c0}"
}

main "$@"

2. Setup

1. Install Wine package (it doesn't really matter which one you use as system version):

pacman -S wine

pacman -S wine-staging

2. Install Winetricks package:

pacman -S winetricks

3. Run create-structure.sh script, it will create folder structure in:
   ~/.PlayOnLinux ├── wine │ ├── linux-amd64 │ └── linux-x86 └── wineprefix

3. Engine

With Wine you can use any Engine! Few things to know;

• Usually it's best to use the latest version, unless there is a known problem or an update has broken compatibility for a specific game.
• You can upgrade or downgrade to any Engine and Version without problems. Just note that if you go from Wine to Proton your new user directory will move to: drive_c/users/steamuser/

If your game configs / saves are in an old user directory, just move them to steamuser or create a symlink. Do the opposite to update from Proton to Wine.

• You can use only one ARCH for PREFIX since it’s created, and in most cases you should use amd64!

Best to choose engines in the given order, in case of problems;

• PlayOnLinux (staging-linux-amd64, upstream-linux-amd64)
  (best place for compiled versions of original Wine / Wine-staging)
• TK-Glitch (Wine version)
• GloriousEggroll
• Proton Compile source or if you have Steam client download it and copy this dir:
  ~/.steam/root/steamapps/common/Proton 5.0/dist
  ...to your Engines path and rename it 5.0-proton:
  ~/.PlayOnLinux/wine/linux-amd64/5.0-proton

Once downloaded, put engine in: ~/.PlayOnLinux/wine/linux-amd64

4. Create prefix

To now demonstrate a complex case, let's install Crysis from GOG.
After all, this is the most important question of gaming: "But can it run Crysis?!"

1. Open create-prefix.sh with a text editor of your choice, and change these options:
   # OPTIONS NAME="Crysis" ENGINE="5.11-staging"
2. Run create-prefix.sh script. This will create your prefix at:
   bash ~/.PlayOnLinux/wineprefix/Crysis

[icon name="lightbulb" prefix="fas"] TIP: Such a PREFIX is fully portable, if you remove this dir with symlinks to devices:
~/.PlayOnLinux/wineprefix/Crysis/dosdevices
Now it's safe to copy / backup PREFIX.
It will be auto-created next time you run anything in PREFIX - so it's safe!

5. Install game

1. Open install.sh with a text editor of your choice, and change these options:
   # OPTIONS SETUP="setup_crysis_2.0.0.7.exe" NAME="Crysis" ENGINE="5.11-staging"
   You can use absolute or relative to Setup executable, if you use relative, like i did here - just copy script to your setup directory. Make sure your NAME and ENGINE variables are same as on 4. Create prefix.
2. Run install.sh script.
3. Follow installer steps and install to some simple location like C:\Games\Crysis
   if possible avoid and disable;
   Any redistributable software like DirectX, Microsoft Visual C++, etc.
   Create desktop icon / link.

[icon name="lightbulb" prefix="fas"] TIP: If you don't want auto-installed proprietary software (GOG installers don't ask you about installing redistributables);
Create temporary PREFIX CrysisTemp.
Install game as usual.
Move game folder to clean Crysis PREFIX.
Remove CrysisTemp PREFIX.

4. This is a rare case, but if you look on Lutris db see Wine GOG version.
   Install -> dropdown [icon name="caret-square-down" prefix="fas"] -> Views install script.
   You will see some winetricks recommendations:

d3dx10_43
d3dcompiler_43
vcrun2005

You can try without, but in general Lutris has good recommendations.

• d3d stuff - see more on unfinished DirectX 10 effects API.
• vcrun2005 is needed for some things like game saves (without it game will crash).

[icon name="exclamation" prefix="fas"] Always recommended to add win7 at the end of tricks, because sometimes winetricks reset OS to install some software properly!

5. Open tricks.sh with text editor of your choice, and change this value:
   # OPTIONS TRICKS=( d3dx10_43 d3dcompiler_43 vcrun2005 win7 ) NAME="Crysis" ENGINE="5.11-staging"
   Make sure your NAME and ENGINE variables are same as on 4. Create prefix.
6. Run tricks.sh script.
   Just proceed with installers windows-style, if asked about Sending anonymous information or something along those lines - select NO.

6. Configuration

Use Lutris as a launcher, it will make things much easier!
Read from Lutris up to 4. Game configuration.

7. Problems

• Installer gives errors such as:
  Runtime Error (at -1:0): Cannot Import dll: C:\users\user\Temp\is-VADAE.tmp\isskin.dllerr:module:import_dll Library MFC42.DLL (which is needed by L"C:\\users\\ready2rumbelx\\Temp\\is-L6E45.tmp\\isskin.dll") not found
  • To solve, install those winetricks with tricks.sh: mfc42 vcrun6
• Installer fails;
  • Prefer simple installers and no DRM if possible, these are main points of failure. (for example GOG)
  • If a retail game (CD / DVD) fails to install directly in Wine, then install on a Windows VM and copy installed game folder in your WINEPREFIX.
  • Still doesn’t work? Please report bug to Wine.
• Launch fails or crashes during gameplay;
  • Disable DXVK / VKD3D
  • If it works without DXVK, report bug to DXVK
  • [icon name="check" prefix="fas"] Disable Lutris runtime.
  • Try another Engine or version.
• Multiplayer games might not work because of anti-cheat.

[icon name="lightbulb" prefix="fas"] TIP: To disable network for WINEPREFIX use Firewall.

]]> 3059 0 0 0 https://discovery.endeavouros.com/window-tiling-managers/sway/2022/01/ Mon, 10 Jan 2022 06:32:33 +0000 https://discovery.endeavouros.com/?p=3086

Sway is a tiling Wayland compositor and a drop-in replacement for the i3 window manager for X11. It works with your existing i3 configuration and supports most of i3's features, plus a few extras.

---

About community edition

[icon name="share" prefix="fas"] Github | Forum

• Wallpaper: swaybg
• Theme: lxappearance
• File manager: thunar
• Terminal: xfce4-terminal or termite
• Bar: waybar

Configuration

• Keybindings: ~/.config/sway/cheatsheet
• Main config file: ~/.config/sway/config.d/default
• Auto-start: ~/.config/sway/config.d/autostart_applications
• Bar: ~/.config/waybar/config

Keybindings

[mod] key is set to the winkey (or should i call it linkey?)

    [mod]+Return = open floating terminal (XFCE4-Terminal)
    [mod]+(Shift)+Return = open fixed terminal (Termite)
    [mod]+o = open Browser (firefox)
    [mod]+n = open File Manager (thunar)
    [mod]+d = app menu (wofi)
    [mod]+q = close focused app [kill]
    (Shift)+(Print-Key) = screenshot/bring up screenshot menu
    [mod]+(Shift)+e = power-menu
    [mod]+r = resize mode
    [mod]+(Shift)+(Space) = float window
        {HOLD DOWN} [mod] = drag floating window
    [mod]+(Arrow Keys) = switch focus respectively
    [mod]+(Shift)+(Minus) = send to scratchpad
    [mod]+(Minus) = cycle through scratchpad

Display/login manager

Some login managers support Wayland, and others don't. The following are confirmed to work with Sway;

Ly: a lightweight TUI (ncurses-like) display manager for Linux and BSD.

yay -S ly

greetd: a minimal and flexible login manager daemon that makes no assumptions about what you want to launch.

yay -S greetd

Documentation:
https://github.com/swaywm/sway/wiki

]]> 3086 0 0 0 https://discovery.endeavouros.com/applications/default-applications/2022/01/ Mon, 10 Jan 2022 13:33:35 +0000 https://discovery.endeavouros.com/?p=3153

This article will discuss how default applications are set and ways to change them.

---

Table of contents:

1. Override default applications
2. MIME types format

---

Introduction

The /usr/local/share/applications/mimeapps.list & /usr/share/applications/mimeapps.list files specify which application is registered to open specific MIME types by default. These files are provided by the distribution. To override the system defaults for individual users, you need to create a ~/.config/mimeapps.list file with a list of MIME types for which you want to override the default registered application.

Override default applications

1. Consult the /usr/share/applications/mimeapps.list file to determine the MIME types for which you want to change the default registered application. For example, the following sample of the mimeapps.list file specifies the default registered application for the text/html and application/xhtml+xml MIME types:

[Default Applications]
text/html=firefox.desktop
application/xhtml+xml=firefox.desktop

• The default application (Firefox) is defined by specifying its corresponding .desktop file (firefox.desktop). The system default location for other applications’ .desktop files is /usr/share/applications/. Individual users’ .desktop files can be stored in ~/.local/share/applications/.

2. Create the ~/.config/mimeapps.list file. In the file, specify the MIME types and their corresponding default registered applications:

[Default Applications]
text/html=myapplication1.desktop
application/xhtml+xml=myapplication2.desktop

[Added Associations]
text/html=myapplication1.desktop;
application/xhtml+xml=myapplication2.desktop;

• This sets the default registered application for the text/html MIME type to myapplication1.desktop, and the default registered application for the application/xhtml+xml MIME type to myapplication2.desktop.
• For these settings to function properly, ensure that both the myapplication1.desktop and myapplication2.desktop files are placed in the /usr/share/applications/ directory. Individual users’ .desktop files can be stored in ~/.local/share/applications/.

3. You can use the gio mime command to verify that the default registered application has been set correctly:

$ gio mime text/html
Default application for “text/html”: myapplication1.desktop
Registered applications:
	myapplication1.desktop
	firefox.desktop
Recommended applications:
	myapplication1.desktop
	firefox.desktop

---

MIME types format

Consider the following example:
mimeapps.list

[Added Associations]
image/jpeg=bar.desktop;baz.desktop
video/H264=bar.desktop

[Removed Associations]
video/H264=baz.desktop

[Default Applications]
image/jpeg=ristretto.desktop
inode/directory=thunar.desktop

Each section assigns one or more desktop entries to MIME types;

• Added Associations indicates that the applications support opening that MIME type. For example, bar.desktop and baz.desktop can open JPEG images. This might affect the application list you see when right-clicking a file in a file browser.
• Removed Associations indicates that the applications do not support that MIME type. For example, baz.desktop cannot open H.264 video.
• Default Applications indicates that the applications should be the default choice for opening that MIME type. For example, JPEG images should be opened with ristretto.desktop. This implicitly adds an association between the application and the MIME type. If there are multiple applications, they are tried in order.

[icon name="lightbulb" prefix="fas"] TIP: Although deprecated, several applications still read/write to ~/.local/share/applications/mimeapps.list. To simplify maintenance, simply symlink it to ~/.config/mimeapps.list:

$ ln -s ~/.config/mimeapps.list ~/.local/share/applications/mimeapps.list

Sources / Further reading:
https://wiki.archlinux.org/title/Default_applications
https://wiki.archlinux.org/title/XDG_MIME_Applications
https://help.gnome.org/admin/system-admin-guide/stable/mime-types-application-user.html.en

]]> 3153 0 0 0 https://discovery.endeavouros.com/arm/install-and-setup-a-samba-server/2021/04/ Thu, 01 Apr 2021 01:01:33 +0000 https://discovery.endeavouros.com/?p=1815

On a Linux Client computer, in a Terminal window, SSH into the headless enosServer.
$ ssh pshare@enosServer
$ su
# pacman -Syu samba

A smb.conf file is not supplied as part of the samba package.
EndeavourOS includes a /etc/samba/smb.conf file during the script installation.
ls -l /etc/samba
-rw-r- - r- - 1 root root 8105 Mar 27 03:55 smb.conf

look for a smb.conf file. Check the permissions and ownership compared to above.
If so, all our necessary config files are in place.
# vi /etc/samba/smb.conf
Find the following lines

#=================== Global Settings======================
[global]

# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
   workgroup = WORKGROUP

Change
workgroup = WORKGROUP
to
workgroup = YOURWORKGROUPNAME

Still in "Global Settings" find the following line
hosts allow = 127. 192.168.0.
if necessary, adjust 192.168.0. to the first three triads of your router's address.

Find the following lines at the very end of the the file

[ENOSshare]
comment = Samba Share
path = /server
valid users = pshare
public = no
writeable = yes
printable = no
create mask = 0765

If desired, change the share name [ENOSshare] to something else.
The share name ENOSshare is case sensitive.
Change valid users = pshare to your username if you chose to change it.
Possibly change the path name of the server's data partition in the path = section.
Don’t change anything else except the lines mentioned above.
Close the editor. After editing, test the changes that were made.
# testparm
Should not be any errors. If errors occur check the smb.conf file for typos or other mistakes.

Set a samba password to access this share from a Windows machine.
# smbpasswd -a pshare
New SMB password: EnterAPassword
Retype new SMB password: Re-enter the same password
password can be whatever you want and does not need to be an existing password.

It is assumed firewalld was installed on the headless server.
Next we set up the Server's firewall for samba.

firewall-cmd --reload
firewall-cmd --permanent --zone=public --add-service=samba
firewall-cmd --reload
systemctl restart firewalld.service
systemctl enable --now smb.service
systemctl enable --now nmb.service

The headless server is now ready to serve a Windows client.
Restart the enosServer computer.
#systemctl reboot

]]> 1815 0 0 0 https://discovery.endeavouros.com/arm/homeserver-5-configure-a-windows-client-for-samba/2021/04/ Sun, 04 Apr 2021 01:52:37 +0000 https://discovery.endeavouros.com/?p=1864

We will be setting up a Windows 10 computer as a client to share files on our LAN server.
This assumes that Homeserver 4 - Install and setup a SAMBA server
https://discovery.endeavouros.com/arm/install-and-setup-a-samba-server/2021/04/
has been completed.

Make sure that your Windows 10 computer has “Network Discovery” turned on as follows:
Settings – Network and Internet – Network and Sharing Center – Advanced Sharing Settings

Since this Windows computer will be a Client, an entry must be made in the “hosts” file.
Click on the Windows button in the panel then Windows Accessories,
Right click on Notepad, –> more –> Run as Administrator.
In Notepad, Click on file –> open.
This PC –> Local Disk (C:) –> Windows –> System32 –> drivers –> etc
In the lower right, change “Text Documents (*.txt)” to “All Files”
open the file hosts at the end of the file, add the following
192.168.0.155 enosServer
adjust the IP address and host name as necessary.
File –> Save

In Windows 10, Right click on “This PC” then click on “Properties” and find the workgroup. In Windows 10 WORKGROUP is the default work group. If you have an existing work group that is not WORKGROUP you can use that. Otherwise choose a work group name of your choice. All Windows computers wanting to access the enosServer must have the same work group name. To change a work group name in Windows 10:
Right click “This PC” then “properties” to the right of the work group section click on “Change settings” See this document for the work group naming rules and help changing it. https://www.tenforums.com/tutorials/36133-change-workgroup-windows-10-a.html

Click on the “This PC” icon --> Computer Tab --> “Map Network Drive” to get the following:

In the “Drive” pull down, select S: for the drive letter to mount Samba Share to, or any other drive letter of your choice.

In the "Folder" pull down enter \\enosServer\ENOSshare
ENOSshare is case sensitive
Make sure "Reconnect at sign-in" is checked

Click Finish. You will get a dialog box saying Trying to connect
Then a box asking for username and password.
Enter pshare for user and pshare's Samba password that we established with # smbpasswd -a pshare
Make sure “Remember my credentials” is checked.

Go back to “This PC” and in addition to Local Disk (C:) you should see the ENOSshare mounted as Drive S: under the Network Locations header.

If you have the ENOSshare mounted and listed as above, restart Windows and see if the SMBshare is automatically mounted after logging in. If it automatically mounts at boot up, we are done with Samba. Sometimes after login, the Icon for enosServer will look like the following.

Just double click on it, and it will usually go find the enosServer and mount it.

Now Setup any other Windows machines in the exact same manner.

]]> 1864 0 0 0 https://discovery.endeavouros.com/arm/homeserver-6-install-and-setup-a-minidlna-media-server/2021/04/ Sun, 04 Apr 2021 02:41:53 +0000 https://discovery.endeavouros.com/?p=1872

If you want to play your MP3s, display Pictures, and view videos, on your Smart TV or any other DLNA device, a minidlna server will need to be installed.

IN A LINUX CLIENT computer, from a Terminal window, SSH into the headless enosServer and become root.

# pacman -Syu minidlna
# vi /etc/minidlna.conf

In the second line, make sure port is set to 8200
port=8200

You can tell minidlna what directories on enosServer it will share.
Scroll to the section that begins with # set this to the directory you want scanned.
There are directions and examples given. Here is how I set up my directories.

media_dir=A,/server/MP3
media_dir=A,/server/Ogg
media_dir=P,/server/Pictures
media_dir=V,/server/Movies

The A, indicates the following directory will contain Audio. P, = Pictures V, = Videos
which are the three media formats that minidlna supports.

In my case the directory /server/MP3 and all sub-directories contains my MP3 Audio.
The directory /server/Ogg and all sub-directories contains my Ogg Audio.
The directory /server/Pictures and all sub-directories contains my Pictures (images).
The directory /server/Movies and all sub-directories contains my MP4 videos.

All directories specified must exist on the enosServer Data drive. Adjust the paths to whatever you set up for your media.

(Right under this section is the Friendly Name section. I uncommented and changed it to:
friendly_name=EndeavourOS DLNA server

Save and close minidlna.conf

# systemctl enable --now minidlna.service
# systemctl status minidlna.service (ensure minidlna is active, running, and no errors)

Add required groups

# gpasswd -a minidlna pshare
# gpasswd -a minidlna users
# groups minidlna
minidlna users pshare (should see these results)

Setup the server firewall.
When the Client computer issues a request, it does so on port 8200 with TCP protocol.
The Server computer responds on port 1900 with UDP protocol.
We need to open port 8200 on the enosServer firewall

firewall-cmd --reload
firewall-cmd --permanent --zone=public --add-service=minidlna
firewall-cmd --reload
systemctl reboot (don't skip this server reboot)

In your Linux Client computer, open port 1900 UPD to let in your server's communications.
In a Client Linux computer terminal window:

sudo firewall-cmd --zone=public --list-services
dhcpv6-client ssh upnp-client

If upnp-client is listed, your are good to go. If not:

sudo firewall-cmd --reload
sudo firewall-cmd --permanent --zone=public --add-service=upnp-client
sudo systemctl restart firewalld.service

Using a Smart TV, Windows MediaPlayer, VLC, or other DLNA enabled device on your LAN, see if it will recognize the EndeavourOS DLNA Server. To use Rhythmbox, ensure grilo-plugins and dleyna-server are installed. Then enable grilo plugins in Rhythmbox's Options --> Plugins tab.

To use DLNA with VLC, if the Playlist column is not visible on the left side, click on the "View" tab and click "Playlist". Scroll down to "Universal Plug'n'Play" and click. EndeavourOS DLNA Server should be listed.

For audio, I know mp3, ogg, flac, and wma are supported, as long as the DLNA client supports those formats. VLC on a PC supports all four. My SMART TV, not so much.

For Pictures (images), jpeg and png are supported, not sure about any others

For Video, mp4 is supported, not sure about any others.

These are the major formats. Experiment around and see what else is supported.
You can also select and view your MP4 movies on VLC.

Lastly, you can set up your vacation pictures in a folder on enosServer. Then have a slide show on your Smart TV in the family room and bore your friends to death.

]]> 1872 0 0 0 https://discovery.endeavouros.com/endeavouros-tools/telegram-helpchat-and-reddit-discussion-rules/2021/11/ Tue, 09 Nov 2021 18:34:48 +0000 https://discovery.endeavouros.com/?p=2679

EndeavourOS-Rules for Telegram:

https://t.me/Endeavouros

1. Keep it civil:

Please treat this Telegram group with the same respect you would a public park. We, too, are a shared community resource — a place to share skills, knowledge, and interests through ongoing conversation.

2. Improve the Discussion:

Help us make this a great place for discussion by always working to improve the discussion in some way, however small. If you are not sure your post adds to the conversation, think over what you want to say and try again later.

One way to improve the discussion is by discovering ones that are already happening. Spend time browsing the topics here before replying or starting your own, and you’ll have a better chance of meeting others who share your interests.

3. Be Agreeable, Even When You Disagree:

You may wish to respond to something by disagreeing with it. That’s fine. But remember to criticize ideas, not people. Please avoid:

• Name-calling
• Ad hominem attacks
• Responding to a post’s tone instead of its actual content
• Knee-jerk contradiction

Instead, provide reasoned counter-arguments that improve the conversation.

4. Your Participation Counts:

The conversations we have here set the tone for every new arrival. Help us influence the future of this community by choosing to engage in discussions that make this the chat an interesting place to be — and avoiding those that do not.

Let’s leave our community better than we found it.

5. If You See a Problem, Report It:

When you see bad behavior, don’t reply. It encourages bad behavior by acknowledging it, consumes your energy, and wastes everyone’s time. Bring it to the notice of the mods or Telegram admins.

6. Always be Friendly:

Nothing sabotages a healthy conversation like rudeness:

• Avoid polarizing content. We have a diverse member base spanning many geographies and cultures so please do not post content related to politics, religion or other controversial subjects.
• Don’t post anything that a reasonable person would consider offensive, abusive, or hate speech.
• Don’t post anything obscene or sexually explicit.
• Don’t harass or grief anyone, impersonate people, or expose their private information.

7. Helping others on issues with EndeavourOS has priority over chit-chat:

We do like to have conversations and discussions about stuff not directly related to the OS itself or Linux in general.

This lets us get to know each other better and keeps users active and entertained, so it's just fun to be logged in.

It is desirable that we exchange information on all possible topics, but if a user comes with a problem, the help on the user's issue has priority and all chit-chat must be put back.

8. You will be banned after 3 warnings:

Warnings will be caused be disrespecting the ruleset. Admins do not need to justify themselves, they only try to keep the chat clean. Same for the use of offensive avatars or text in profiles that are offensive or glorifying violence, these are part of the actual stock for warnings or direct ban.

In cases, warning can get removed in discussion with the admin giving it (please use private message for this, not the main chat)

9. The Chat is in English only:

The only allowed language in chat is English. There are chats to get help for EndavourOS in other language, ​​if necessary for you.

Go to https://endeavouros.com/community to find these.

]]> 2679 0 0 0 https://discovery.endeavouros.com/video-tutorials/install-endeavouros/2021/12/ Wed, 08 Dec 2021 09:32:23 +0000 https://discovery.endeavouros.com/?p=2730

https://youtu.be/q3LuPQ5-dXY

]]> 2730 0 0 0 https://discovery.endeavouros.com/audio/pulseaudio/2021/12/ Wed, 08 Dec 2021 21:45:08 +0000 https://discovery.endeavouros.com/?p=2737

https://www.freedesktop.org/wiki/Software/PulseAudio/

EndeavourOS is using Pipewire per default up from Atlantis Release, but in case you do not want to use Pipewire, or you need to use Pulseaudio in case apps you need to use only work with PulseAudio, you can switch back to it:

sudo pacman -S pulseaudio

what will replace pipewire-pulse

In addition, you may need:

sudo pacman -S pulseaudio-alsa pulseaudio-jack pulseaudio-bluetooth

Depending on what is installed on your system it will be needed to remove some Pipewire packages before installing pulseaudio, or it will five you dependency errors:

sudo pacman -S jack2 pulseaudio-alsa pulseaudio-jack

It is currently possible again to completely remove pipewire too as I just tested (January 2023):

In this case you could use -Rc to take the dependencies with it as I want exactly this, but keep care to check the exact output to not remove half the system with it !!

sudo pacman -Rc pipewire

I would recommend using something like this instead:

sudo pacman -R pipewire wireplumber libwireplumber gst-plugin-pipewire

To use pulseaudio simply reboot your system or if you can not do that unload pipewire and load pulseaudio:

systemctl --user stop pipewire-pulse.service

systemctl --user start pulseaudio

inxi -Aaz will show if it is all working fine:

For the other way around switching from Pulseaudio to Pipewire:

https://discovery.endeavouros.com/audio/pipewire/2021/09/

]]> 2737 0 0 0 Pipewire]]> Pipewire]]> Pipewire]]> https://discovery.endeavouros.com/system-rescue/fix-arch-linux-boot-with-arch-chroot/2021/12/ Mon, 13 Dec 2021 17:31:36 +0000 https://discovery.endeavouros.com/?p=2745

https://youtu.be/43dpS35Hzq8

]]> 2745 0 0 0 https://discovery.endeavouros.com/encrypted-installation/btrfs-with-timeshift-snapshots-on-the-grub-menu/2022/02/ Tue, 15 Feb 2022 08:34:59 +0000 https://discovery.endeavouros.com/?p=3346

BTRFS with timeshift snapshots on the grub menu

• _{Reviewed corrected and expanded by nick_0189 (october 2023)}
• _{corrected timeshift not in AUR anymore (joekamprad)}

It is easy to add backup snapshots with Timeshift and make them available in Grub’s boot menu!

1. Install EndeavourOS using automatic partitioning and the BTRFS filesystem (with or without encryption).

2. Timeshift is a GUI tool from the Linux Mint developers to manage system backups using rsync or BTRFS. Install Timeshift:
sudo pacman -Syu timeshift

3. The cronie service is a service used by Timeshift to run services periodically, but is not enabled by default. Cronie was installed as a dependency of Timeshift and should be enabled:
sudo systemctl enable --now cronie.service

4. Launch Timeshift and set it up to use BTRFS. Optionally enable automated snapshots at the intervals provided and choose if you would like your home folder included in snapshots (home folders are often not backed up using snapshots). Then create the first snapshot by clicking the “Create“ button in the top left corner of the window.

5. timeshift-autosnap provides a script which creates a snapshot before each package/system update using a Pacman hook. The default number of snapshots kept is three. Older snapshots are then deleted to make room for newer ones.

If you want this functionality, timeshift-autosnap can be installed from the AUR for automated snapshots:
yay -S timeshift-autosnap

Otherwise, snapshots will only be taken manually (they will still show up in the boot loader though).

6. Now install the grub-btrfs package from the community repository:
sudo pacman -S grub-btrfs

To include Timeshift’s BTRFS snapshots in the boot options, grub-btrfs needs to be reconfigured as it is using /.snapshots as the default snapshot directory and Timeshift uses a different directory:
sudo systemctl edit --full grub-btrfsd

Add the --timeshift-auto option by changing the following line:

ExecStart=/usr/bin/grub-btrfsd --syslog /.snapshots

to

ExecStart=/usr/bin/grub-btrfsd --syslog --timeshift-auto

Save the service file by pressing Ctrl+X and answering the prompts shown.

7. The final step is to rebuild the grub configuration file:
sudo grub-mkconfig -o /boot/grub/grub.cfg

and enable the service:
sudo systemctl enable --now grub-btrfsd

For more information on grub-btrfs go to its source:

Sources:

grub-btrfs
https://github.com/Antynea/grub-btrfs
Information on the grub-btrfs program.

timeshift-autosnap
https://gitlab.com/gobonja/timeshift-autosnap
Information on the timeshift-autosnap program.

Timeshift
https://github.com/linuxmint/timeshift
Information on Timeshift.

BTRFS
https://btrfs.readthedocs.io/en/latest/Introduction.html
Introduction to BTRFS, snapshots, and COW.

]]> 3346 0 0 0 https://discovery.endeavouros.com/applications/firewalld/2022/03/ Sun, 27 Mar 2022 11:52:59 +0000 https://discovery.endeavouros.com/?p=3421

FirewallD

Some info on FirewallD to read:

Official FirewallD Documentation

Archwiki entry about FirewallD

A beginners Guide into FirewallD on RedHat

opensource.com firewall-cheat-sheet

Why EndeavourOS is using FirewallD now?

After some discussion dev team come to the conclusion that it would be a good idea to enable a decent firewall per default on all installations for EndeavourOS.

Also, a more experienced user may already is used to set up firewall rules from some saved rules, the majority of users still forget to secure the system after the initial installation.

Nowadays this is nothing we can ignore anymore from the side of offering an Operating system for you.

So there you are up from now (Apollo release 2022) FirewallD will be installed for all EndeavourOS installs and the service is enabled per default.

This will give a secure basic firewall using the default public zone running.

From there users can decide to disable and install a firewall of choice or set up rules manually as they like.

It is also possible to untag FirewallD inside the installation process if you do not want it to get installed.

General Info on how to install and handle FirewallD:

How to install and enable:

Enable and start firewalld.service.

sudo systemctl enable --now firewalld.service

You can control the firewall rules with the firewall-cmd console utility.

firewall-offline-cmd the CLI (Terminal based) utility can be used to configure when firewalld is not running. It features similar syntax to firewall-cmd.

GUI is available as firewall-config which comes with firewall-config package.

You will find the GUI inside the menu as firewall:

The GUI can look a bit intimidating at the first look, but once you understand it has anything you need right at your fingertips.

In the end, for normal Desktop usage, you do not need to change anything, and if you want to use something like open your system for remote access via ssh a simple click on the ssh services and you open the needed port for it to work.

Other things like network connections for Qemu (VirtManager) will get enabled automatically on the run if needed.

Aside from the GUI FirewallD also enables a tray icon with some info and menu to reach settings:

Remove/Replace FirewallD

If you want to remove FirewallD to install another one or use your own set of rules manually you can do that by the following steps, it is needed to stop firewall before removing it as it could block installing a new one later.

Disable temporarily (this will stop the service immediately)

sudo systemctl stop firewalld

Disable permanently (this will stop the service immediately and disable the automatic start on boots)

sudo systemctl disable --now firewalld

Remove:

sudo pacman -R firewalld python-firewall firewall-config firewall-applet firewalld-test 

Related packages:

• firewalld [needed]
• python-firewall: Python bindings for firewallD [dependency]
• firewall-config: Graphical user interface for firewallD configuration [optional]
• firewall-applet: Systray applet for firewallD [optional]
• firewalld-test: firewallD test suite [optional]

Open FirewallD for network printing:

If you missed that and want to open the firewall manually for Network printing support use the firewalld-application:

Switch to permanent configuration and change zone to home. You will see mdns Services are enabled with it.

https://youtu.be/9MCdy8ZGQ1I

To switch the zone for your current location (Network) click options > change zones of connections > select the used network connectiona nd select home from the dropdown in the popup:

This will be permanent over reboots, as long as you are connected to the same Network (location).

https://discovery.endeavouros.com/printers/printers/2021/03/

Open firewalld for kdeconnect:

The easy way is using the terminal and the firewalld-cmd commandline tool:

sudo firewall-cmd --permanent --zone=public --add-service=kdeconnect

sudo firewall-cmd --reload

[icon name="info" prefix="fas"]

--zone=public must be changed to the used zone for the network (location) you want this to be used in.

This will permanently open the firewall for the kdeconnect service to allow to connect to mobile device and receive messages on the desktop.

]]> 3421 0 0 0 Printers]]> Printers]]> https://discovery.endeavouros.com/installation/customizing-the-endeavouros-install-process/2022/03/ Wed, 30 Mar 2022 09:34:55 +0000 https://discovery.endeavouros.com/?p=3449

EndeavourOS provides users a couple of ways to customize what to install. Just boot up the installer USB drive and prepare your customized features!

User Packagelist

File /home/liveuser/user_pkglist.txt

This is the easy way to add your favorite package names to be installed. After booting up the installer USB:

• open a terminal
• run command
  nano ~/user_pkglist.txt
  and add the names of packages you want to install to the file
• close the Welcome window
• start Welcome again with command
  eos-welcome

Note that there are some rules/restrictions:

• Use only package names from the configured repositories (see /etc/pacman.conf), not from AUR
• Write only one package name per line.
• The Installer will add them to be installed, and will error message if package is not available or you have a typo per example.

You will find a group added on the package screen of the installer where you can see the added packages too:

User Commands

This is a much more advanced feature. Basically it provides user the opportunity to modify the installer and the installed system in various ways using bash language and usual commands (like pacman). Note that a reasonable knowledge of the bash language and typical linux commands is needed.

For example, this feature makes possible to
- configure calamares settings
- add new package sources
- install or remove packages
- start or stop systemd services
- change settings for the user created at install
and much more.

Note that the usage of this feature changed slightly from Galileo neo to Gemini.

Galileo neo and older

File /home/liveuser/user_commands.bash

You can write various bash language commands to this file. This script file will be executed (as root) in two phases:

1. in the beginning of install before starting calamares
2. in the end of the install process (in calamares)

Note: phase 1. is a new feature implemented in Cassini neo (beginning of Feb 2023). Phase 2. has been around in a few ISOs already.

In the beginning (phase 1.) you can configure calamares settings, for example set the default filesystem type to be used in the installed system. In file user_commands.bash phases are recognized by parameters. In phase 1. user_commands.bash gets parameters --iso-config and install-mode. The first parameter tells that only your phase 1. commands should be executed, nothing more. The second parameter tells what you selected as the install mode, and this value is one of: online or offline.

In the end of install (phase 2.) you can customize the installed system in many ways. For example:

• install and/or remove packages
• enable and disable systemd services
• write and/or customize files in the $HOME folder of the new user (e.g. ~/.bashrc)
• add third party repositories into /etc/pacman.conf (may help e.g. with unusual drivers!)
• customize grub features (e.g. blacklist unnecessary drivers)
• modify various app or system configuration files
• and more!

In phase 2. user_commands.bash will be called with the new user name you gave during the install.

Note that file user_commands.bash on the liveuser contains more details and many usage examples.

Gemini and later

Now we have two files instead of one:
1) ~/user-commands-before.bash
2) ~/user_commands.bash

The first file is meant for making user defined configurations to calamares before starting the installer. It takes one parameter, the install mode (either online or offline).

The second file is meant for running user defined commands in the end of the install process. It takes one parameter, the user name that was created by the installer.

So these two files do the same things that only one file did in Galileo neo. The separation should make their function and usage more clear.

Note that templates of both files exist on the liveuser. They include more details and tips.

Tip: if you already have file user_commands.bash for Galileo neo, you can use it as follows:
- remove file ~/user-commands-before.bash on the liveuser
- symlink ~/user-commands-before.bash to ~/user_commands.bash
provided the parameter handling is fixed to comply with the explanation above.

For example:
cd $HOME
rm user-commands-before.bash
ln -s user_commands.bash user-commands-before.bash

Limitations for the commands

The commands are run as the root user, so

• AUR packages cannot be installed
• some commands do not run properly as root
• files modified under $HOME need to be chown'ed from root to the real user

In addition, commands written into this file must never stop e.g. for asking any confirmation. So, for example, pacman must be used with option --noconfirm to prevent stopping.

How to start a customized install

Simply write your commands into user_commands.bash and restart Welcome.

Or, you can use your personal URL file which contains your commands! To use the URL, re-start welcome with a terminal command:

eos-welcome --ni="URL"

and welcome will fetch your command file and use it as user_commands.bash.
Note that the URL must start with either https:// or http:// because only these protocols are supported.

Conclusion

Please look at the files mentioned above on the ISO. They contain more tips and details, which should help you use them.
Hope you’ll enjoy these customization possibilities!

---

Edits:

• _{20. dec 2023: joekamprad: added some details to user Packege option and two pictures to make it visually easier to understand. Plus some format fixes (needed caused by changes to the CMS)}
• 27. mar 2024: manuel: added Gemini info
• 20 apr 2024: manuel: slightly more details in the beginning

]]> 3449 0 0 0 https://discovery.endeavouros.com/nvidia/new-nvidia-driver-installer-nvidia-inst/2022/03/ Thu, 31 Mar 2022 13:21:10 +0000 https://discovery.endeavouros.com/?p=3451

_{By Manuel, 2022-Mar-31
Latest update: 2026-Jan-12}

Important for older Nvidia GPUs!

_{Up from (2023-Feb) nvidia-inst does not support installing (older) legacy drivers. This means certain older Nvidia GPUs should use either the nouveau kernel driver or install the appropriate legacy driver from the AUR (with yay).}

_{IMPORTANT NOTE: if you have added repository [kernel-lts] into file /etc/pacman.conf, please remove it from the file because this repository may include outdated packages.}

_{Tip: you can still use command nvidia-inst -t to find the needed commands, just be sure to change the package names according to the version (for example, change nvidia-dkms to nvidia-580xx-dkms etc.).}

Overview

nvidia-inst helps to install and uninstall driver (and related) packages for Nvidia GPUs.

Here's the output of the nvidia-inst command with the help option:

$ nvidia-inst --help

nvidia-inst - help installing drivers for Nvidia GPU

Usage: nvidia-inst [options]

Options:
-h, --help       This help.
-b, --bumblebee  Install bumblebee and Nvidia drivers for optimus cards (only very old cards).
-f, --force      Force driver installation even if a nvidia card is not detected.
-n, --nouveau    Install (open source) nouveau driver instead of nvidia-dkms.
-o, --open       Install package nvidia-open-dkms instead of nvidia-dkms.
-p, --prime      Install also prime render offload.
-q, --quiet      Suppress log messages.
-t, --test       Test mode. Nothing in your system will be modified.
-v, --version    Show version of this software.
--32             Install also support for 32-bit apps.
--switcheroo     Install switcheroo-control and enable its service. Use this option separately.
--conf           Create also file /etc/X11/xorg.conf.d/20-nvidia.conf (might be needed on some older systems).
--no-dkms        Install only non-dkms packages (e.g. 'nvidia-open' instead of 'nvidia-open-dkms').
--show-gpu-info  Show information about your GPU. Use this option separately.
--listseries     List Nvidia driver versions supported by nvidia-inst.
--ignore         Ignore all errors (useful for testing only).
--series=X       (Advanced) Use the given Nvidia driver version X (for testing).
--remove-nothing (Advanced) Do not remove any existing package (for testing).
--listopts       List options supported by nvidia-inst.

Notes:
* By default, nvidia-inst detects the Nvidia GPU family and selects automatically between
Nvidia's open source driver, or the nouveau kernel driver.
* NVIDIA no longer actively supports older than Turing family GPUs. Thus using
the nouveau driver (or a driver from the AUR) with them may provide a solution.
See also: https://wiki.archlinux.org/title/NVIDIA#Installation
* By default, dkms packages are preferred and will be selected for install if none of options
--no-dkms
--nouveau
--bumblebee
is used.
* If you have more than one GPU in the system, then you may need a tool to choose the GPUs to use.
There are several popular tools in the AUR, e.g.
- envycontrol
- optimus-manager
- supergfxctl
to mention a few.
See also:
- https://discovery.endeavouros.com/?s=nvidia
- https://wiki.archlinux.org/title/NVIDIA_Optimus

Options

With nvidia-inst you can install drivers for your Nvidia GPU. nvidia-inst detects which driver packages are needed. Additional features will be installed based on given options.

Likely the most important new options in nvidia-inst are

--test

Use this to see the suggested commands. Nothing will be changed in your system.
Note: without this option nvidia-inst will start running the commands it suggests.

--prime

This option will install the package nvidia-prime in addition to the Nvidia drivers.

--32

Also includes support for 32-bit apps. Typically, gamers need this.

--nouveau

This is needed for Nvidia GPUs older than the Turing family.

--no-dkms

Use this option if you don't want to install the dkms version of the driver package. The dkms version is slower to install and upgrade, but is compatible with additional kernels (like e.g. linux-zen and linux-hardened).

Other new options should be rather self-explanatory. Some options are mainly meant for internal testing of nvidia-inst.

Removing conflicting packages

If nvidia-inst is executed e.g. with option --nouveau, it will remove conflicting packages like the default nvidia driver, and then install the nouveau driver. A similar idea is used with all options that need to take care of conflicting packages and/or certain settings: conflicting stuff will be removed first, and then the new packages/settings will be installed.

This also means that if you have Nvidia related packages or settings that you want to save, you need to do that manually before using nvidia-inst.

References

Nvidia install on Discovery

Examples

Enable legacy drivers (older Nvidia cards)

Older Nvidia cards like GT 700 or GT 10xx series are not supported by the latest Nvidia driver available from the official Arch repositories. For those cards, there are alternatives:

• the nouveau open source kernel driver
• a legacy Nvidia driver from the AUR (for example, nvidia-580xx-dkms for Maxwell, Pascal, and Volta family GPUs)

For the older, Nvidia GPUs nvidia-inst supports the nouveau driver (option -n).
If legacy Nvidia drivers from the AUR are needed, the user can install them from the AUR, using e.g. yay. Then install them manually.

Example:

yay -S nvidia-580xx-dkms

After rebooting, the drivers should be active. You will get driver updates as expected using pacman or yay.

Bumblebee (for very old machines)

If you need to set up Bumblebee as detailed here: EndeavourOS Bumblebee wiki the nvidia-inst script can do that automatically too:

nvidia-inst -b

]]> 3451 0 0 0 EndeavourOS Nvidia Installer]]> https://discovery.endeavouros.com/hardware/webcam-setup/2022/05/ Sun, 15 May 2022 16:32:49 +0000 https://discovery.endeavouros.com/?p=3535

webcam setup

Setting up a webcam on Linux is easy.

In most cases, the device should be detected without any extra steps needed.

Check it:

v4l2-ctl --list-devices

_{needs v4l-utils installed}

Per default you have at minimum two apps installed you can use to check how the webcam is working basically: v4l2-view ( a simple viewer) and v4l2-test-bench a qt-based config tool:

In most cases setting done here will get used if you use the cam in other applications like Jitsi or even zoom skype or other crap you have to use ;)

B.T.W if you need to use zoom Jitsi or skype... Before you go through all the hassle of installing it, try using the web app, it's usually easier and takes less effort.

https://meet.jit.si/

https://www.skype.com/en/features/skype-web/

https://web.whatsapp.com/

_{Only to show some examples...}

There are a bunch of webcam clients/apps you can use on Linux on my testing a lot of them do not work properly, but I find GUVCView working smooth and without issues right out of the box.

And the app has both GTK and QT versions to choose from for installation:

community/guvcview
Simple GTK+ interface for capturing and viewing video from v4l2 devices

community/guvcview-qt
Simple Qt interface for capturing and viewing video from v4l2 devices

If you got any trouble or need some special setup the arch wiki will be the first read for you:

https://wiki.archlinux.org/title/Webcam_setup

Or if you want to follow deep into the rabbit hole:

https://www.linuxtv.org // https://www.kernel.org/ // V4L2_camera_overview

]]> 3535 0 0 0 https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/ Mon, 19 Dec 2022 10:59:54 +0000 https://discovery.endeavouros.com/?p=3823

Arch-chroot

If your machine doesn’t boot caused of a Bootloader or update issue, there is a way to get into your system through the terminal with Change of root also known as Chroot.

This is a rescue mode where you mount the partitions of the installed system, as it would happen on a real OS boot, and with the help of a chroot helper, you can log in to the installed system and run some rescue tasks.

In our case, we have arch-chroot which helps to make the process of mounting some needed stuff into the chroot needed to be able to maintain rescue-related stuff inside the chroot properly.

To be able to use arch-chroot these are the steps to follow:

1. Boot into the EndeavourOS installer ISO (archiso itself will work too).

2. Mount needed partitions.

3. Run arch-chroot to log in to the installed system. Run rescue tasks like you would be booted into the system itself.

Boot into the EndeavourOS installer ISO

Boot the installer ISO in the same way you have done on installing EndeavourOS but do not run the installer.

Mount needed partitions

To be able to chroot, you need to know how the partitions and format are set up.

To uncover that information, open the terminal, and type:

sudo lsblk -f

Depending on the way you installed the OS you will have different scenarios.

It can be ext4, BTRFS, or xfs formatted and you may set up encryption.

On most modern systems, and if you do not set legacy Bios Mode on the Firmware, you will run in EFI mode, and in this case, you will have a fat32 partition (ESP = EFI-System-Partition) and your system partition if using ext4 or xfs. If you are using BTRFS you have a subvolume scheme running.

---

[icon name="info" prefix="fas"]

If you are running CSM/Bios/legacy installs:

In the case of old or legacy-enabled Bios systems (if Firmware is set to CSM mode), you will mostly have only one partition so you will not need to mount the ESP in addition. In this case you will not find any fat32 partition, and only need to mount the system partition.

---

If you set up LUKS encryption you need to unlock the encryption to be able to mount them.

In this example, we use a default ext4 setup with the ESP mounted under /efi ( you will find other models at the end of the article).

So we need to mount /dev/sda2 and the ESP (/dev/sda1) make sure to know your ESP mount point on your installed system can be /efi or /boot/efi (older installs, or if you are using grub instead of systemd-boot).

You will see in the /etc/fstab file of the installed system if you cannot remember.

sudo mount /dev/sda2 /mnt

sudo cat /mnt/etc/fstab (to check the mount point of your ESP)

sudo mount /dev/sda1 /mnt/efi (or /mnt/boot/efi)

Now your installed system is mounted.

Run arch-chroot to login to the installed system

With this information, you are able to arch-chroot, so type the following command:

sudo arch-chroot /mnt

Now you’ve chrooted into your installed system, and you are able to access your files, install packages, or alter scripts to rescue your system.

To make sure arch-chroot is working check after your user’s home folder ls /home that should give your username from the installed system.

All commands you run into this terminal will now run as you would run them on a real boot of the system.

You can rerun a failed update, rebuild kernel images or reinstall uninstalled packages and fix configs, etc.

Useful links:

• Video tutorial about arch-chroot: https://discovery.endeavouros.com/system-rescue/fix-arch-linux-boot-with-arch-chroot/2021/12/
• Arch-Wiki: Using arch-chroot
• Wikipedia article about Chroot in general.
• Repair non booting Grub from arch-chroot
• About Systemd-Boot
• About Dracut

---

Other mounting examples

BTRFS filesystem installs

you need to know your subvol names and their associated mount points inside the system path.

Per default EndeavourOS uses this scheme:

btrfsSubvolumes:
- mountPoint: /
subvolume: /@
- mountPoint: /home
subvolume: /@home
- mountPoint: /var/cache
subvolume: /@cache
- mountPoint: /var/log
subvolume: /@log

_{Not all subvolumes need to get mounted to use arch-chroot it needs mainly the / (@) if you only want to repair grub per example}

sudo mount -o subvol=@ /dev/sdXn /mnt

sudo mount -o subvol=@log /dev/sdXn /mnt/var/log

sudo mount -o subvol=@cache /dev/sdXn /mnt/var/cache

sudo mount -o subvol=@home /dev/sdXn /mnt/home

And your ESP needs to get mounted also .. as it is not inside your BTRFS scheme and using its own fat32 partition:

sudo mount /dev/sdXn /mnt/efi

where in all cases /dev/sdXn needs to be changed according to what is used on your install as partition/device path and the mount path for the ESP needs to get changed according to your installed system in case. If it is /efi you need to mount on /mnt/efi if it is /boot/efi it would be /mnt/boot/efi ...

Now you will be able to arch-chroot into your BTRFS system, as you can see above under Run arch-chroot to login to the installed system.

Encrypted installs

In case /dev/sda2 is the encrypted root partition you need to unlock:

sudo cryptsetup open /dev/sda2 mycryptdevice

It will ask for your LUKS passphrase and unlocks the device into the path /dev/mapper/mycryptdevice

This path can be used to mount the device:

sudo mount /dev/mapper/mycryptdevice /mnt

Followed by mounting the ESP (EFI-System-Partition) into the already mounted system:

sudo mount /dev/sdXn /mnt/efi

where in all cases /dev/sdXn needs to be changed according to what is used on your install as partition/device path and the mount path for the ESP needs to get changed according to your installed system in case. If it is /efi you need to mount on /mnt/efi if it is /boot/efi it would be /mnt/boot/efi ...

You can also use Gparted to open encryption...

After this right-click on the partition and show "information" to get the mapper path you need to mount it:

Open encryption for BTRFS installs:

The mounting process would change from using the device name itself to /dev/mapper/mycryptdevice

example:

sudo mount -o subvol=@ /dev/mapper/mycryptdevice /mnt

For other subvols follow the same scheme as above on the BTRFS example replacing the device with /dev/mapper/mycryptdevice

]]> 3823 0 0 0 https://discovery.endeavouros.com/btrfs/btrfs-basic-information-and-troubleshooting/2023/07/ Tue, 11 Jul 2023 13:21:42 +0000 https://discovery.endeavouros.com/?p=4171

Links to official documentation:

https://btrfs.readthedocs.io/en/latest/Introduction.html

https://wiki.archlinux.org/title/btrfs

https://wiki.gentoo.org/wiki/Btrfs

Introduction:

BTRFS is a modern copy on write (COW) filesystem for Linux aimed at implementing advanced features while also focusing on fault tolerance, repair and easy administration. Its main features and benefits are:

• Snapshots which do not make a full copy of the files
• Built-in volume management, support for software-based RAID 0, RAID 1, RAID 10 and others
• Self-healing - checksums for data and metadata, automatic detection of silent data corruptions

In some cases, we see that users simply start installing BTRFS because they think it's new, fast, fancy, the next big must-have, or whatever. That's a link to trouble! If you do not have any clue about the four points described beforehand, you should not use BTRFS, at least not without first reading about what exactly it is and how it basically works, as it is different from traditional file systems in many ways.

Tips and Tricks:

To handle BTRFS there is a nice GUI tool you can install:

yay -S btrfs-assistant

AUR: https://aur.archlinux.org/packages/btrfs-assistant

SOURCE: https://gitlab.com/btrfs-assistant/btrfs-assistant

]]> 4171 0 0 0 https://discovery.endeavouros.com/bash/bash-customizations/2024/04/ Thu, 04 Apr 2024 11:47:17 +0000 https://discovery.endeavouros.com/?p=4561

EndeavourOS do ship only default .bashrc (bash configuration) but as you may know there are endless.

https://www.gnu.org/software/bash

https://wiki.archlinux.org/title/Bash

Here you will find some basic settings and hints on customizing your bash prompt and behavior of the shell.

~/.bashrc Per-user config file, applied after /etc/bash.bashrc

~/.bash_profile Per-user, after /etc/profile. If this file does not exist, ~/.bash_login and ~/.profile are checked in that order. The skeleton file /etc/skel/.bash_profile also sources ~/.bashrc.

~/.bash_logout Per-user, after exit of a login shell.

/etc/profile Sources application settings in /etc/profile.d/*.sh and /etc/bash.bashrc.

Most requested is the history search function added on top of up/down keys showing the history roll of input:

Add these two lines to users .bashrc:

bind '"\e[A":history-search-backward' # history with arrow up key
bind '"\e[B":history-search-forward' # history with arrow down key

With this you can start typing per example sudo and with up and down keys it will show all commands used starting with sudo...

The prompt itself can be configured and as you like in many many ways also for some examples see this online tool per example:

https://wiki.archlinux.org/title/Bash/Prompt_customization

https://ezprompt.net

https://bash-prompt-generator.org

]]> 4561 0 0 0 https://discovery.endeavouros.com/applications/kde-plasma/2024/09/ Fri, 20 Sep 2024 16:47:39 +0000 https://discovery.endeavouros.com/?p=4799

KDE Plasma

Use Plasma to surf the web, keep in touch with colleagues, friends and family manage your files, enjoy music and videos, and get creative and productive at work.
Do it all in a beautiful environment that adapts to your needs,and with the safety, privacy-protection and peace of mind that the best Free Open Source Software has to offer.

https://wiki.archlinux.org/title/KDE#Plasma

https://kde.org/de/plasma-desktop

The installation and preinstalled packages you got with the default EndeavourOS KDE Plasma install are a bare minimal setup, ready to set up to your personal needs.

In case you want to add some additional features and functionality, we collect some common extra options here.

Gdrive (google):

to browse your Google Drive in Dolphin, install kio-gdrive

sudo pacman -Syu kio-gdrive

Dolphin (filebrowser) extras:

https://wiki.archlinux.org/title/Dolphin#File_previews

File indexer Baloo:

In case you do not need the functionality, or it is using too many resources on older hardware:

https://wiki.archlinux.org/title/Baloo#Disabling_the_indexer

balooctl6 suspend
balooctl6 disable
balooctl6 purge

Overview of all apps KDE Plasma offers:

https://apps.kde.org

Most of they are inside the package group for kde-applications.

Extra functionality for the settings manager are called kcm:

https://develop.kde.org/docs/features/configuration/kcm

Some are in the repository: https://archlinux.org/packages/?sort=&q=kcm&maintainer=&flagged=

Some more or less usefull options can be found in the AUR:

https://aur.archlinux.org/packages?O=0&K=kcm

]]> 4799 0 0 0 https://discovery.endeavouros.com/desktop-environments/gnome-desktop/2024/09/ Fri, 20 Sep 2024 17:41:40 +0000 https://discovery.endeavouros.com/?p=4804

GNOME Desktop

Get things done with ease, comfort, and control.
An easy and elegant way to use your computer, GNOME is designed to help you have the best possible computing experience.

https://www.gnome.org

https://wiki.archlinux.org/title/GNOME

The installation and preinstalled packages you got with the default EndeavourOS Gnome install are a bare minimal setup, ready to set up to your personal needs.

In case you want to add some additional features and functionality, we collect some common extra options here.

Online accounts

Some online accounts, such as ownCloud, require gvfs-goa to be installed for full functionality in GNOME applications such as GNOME Files and GNOME Documents.

sudo pacman -Syu gvfs-goa

Extensions

The catalogue of extensions is available at https://extensions.gnome.org, they can be installed either through official repositories (only a few), the AUR or through the browser:

To be able to install themfrom inside your Browser you need https://archlinux.org/packages/extra/any/gnome-browser-connector/

pacman -Syu gnome-browser-connector

And the Browser extension (add-on), what will be asked for while opening the extensions webpage:

https://extensions.gnome.org

(after you have the connector package installed)

Gnome applications are to found in the gnome-extra group:

https://archlinux.org/groups/x86_64/gnome-extra

https://apps.gnome.org/en

]]> 4804 0 0 0 https://discovery.endeavouros.com/signature-and-keyring/how-to-check-and-trust-key-and-signature-for-the-endeavouros-iso/2025/01/ Thu, 02 Jan 2025 18:27:09 +0000 https://discovery.endeavouros.com/?p=4864

Download .ISO file and .SIG file and save them in the same directory.

Check here to use the correct key ID and files, used key here is an example, it could change in the future.

https://endeavouros.com

Open a terminal in that directory and run:

gpg --recv-key CDF595A1

in case, use a specified key-server, if the one default on your OS is not holding the key:

gpg --keyserver keyserver.ubuntu.com --recv-keys CDF595A1
gpg --keyserver pgp.mit.edu --recv-keys CDF595A1

To trust the key run:

gpg --edit-key CDF595A1

In the GPG prompt, enter trust

It will ask you to enter a trust level number 1 the lowest, 5 the highest trust level.

If you fully trust the key (in case of EndeavourOS I do) enter 5

If you enter a lower number, the trust is still there but at a lower level. A warning will pop up saying this trust is only partial. This is to be expected as it depends on your trust level choice.

Enter will save, and exit gpg with quit

To verify the ISO itself, run:

gpg --verify EndeavourOS_Endeavour_neo-2024.09.22.iso.sig

This should output something like:

All done, you have now imported the key, set its trust level and verified the .ISO with the .SIG file.

And what is about checking sha512sum?

Under Linux, sha512sum should be installed on most Distributions:

To check the ISO file with sha512:

sha512sum -c EndeavourOS_Mercury-2025.02.08.iso.sha512sum

In the terminal of your choice in the path where both the shasum file and the ISO is stored.

In case you are on Windows, it is also possible to check the sha512sum from terminal:

certutil -EndeavourOS_Mercury-2025.02.08.iso.sha512sumEndeavourOS_Mercury-2025.02.08.iso SHA512

You need to be in the path of the two downloaded files too here.

You can also use a graphical tool to check for correct shasum:

https://github.com/tedsmith/quickhash

]]> 4864 0 0 0 https://discovery.endeavouros.com/hardware/switcheroo-control/2025/02/ Thu, 20 Feb 2025 23:14:03 +0000 https://discovery.endeavouros.com/?p=4904

Switcheroo-Control D-Bus service to check the availability of dual-GPU, integrates with the settings of KDE/plasma Gnome, and Cinnamon: “Launch using Dedicated Graphics Card” menu item appears on application starter contextual menu per example.

https://youtu.be/NJqktGagD9E

Install it and enable the needed systemd-service:

sudo pacman -Syu switcheroo-control
sudo systemctl enable --now switcheroo-control

It has CLI tool:

switcherooctl list

List the known GPUs. The device number can be used to specify the GPU to launch on for the launch command. This is the default command if no commands are passed to switcherooctl.

switcherooctl launch [OPTION] COMMAND

on a specific GPU. If no GPU are specified the first discrete (non-default) GPU is used, or the default GPU if there's no discrete GPU.

Options

-g --gpu=GPU
The GPU to launch on. The GPU identifier can be gathered using the list command.

Some desktops have it integrated, providing settings in launchers for convenience:

GNOME

https://wiki.archlinux.org/title/PRIME#GNOME_integration

GNOME will respect the PrefersNonDefaultGPU property in the desktop entry. Alternatively, you can launch applications with GPU by right-clicking on the icon and choosing Launch using Discrete Graphics Card.

KDE/plasma

It will show the option on Launcher settings:

Cinnamon

The same option in Launcher Settings to tag "Use Dedicated GPU if available" will show up there.

https://discovery.endeavouros.com/nvidia/nvidia-optimus-notebooks-hybrid-graphics/2021/03/

---

credits:

_{Hilmy Abiyyu A.}

_{Good Ware}

_Freepik

]]> 4904 0 0 0 Optimus Notebooks (hybrid graphics)]]> Optimus Notebooks (hybrid graphics)]]> https://discovery.endeavouros.com/hardware/framework-13-amd-dyi-amd-ryzen-7-7840u/2025/08/ Tue, 05 Aug 2025 15:28:20 +0000 https://discovery.endeavouros.com/?p=5040

Framework 13 AMD DYI AMD Ryzen™ 7 7840U

General Things

Framework Laptop13

• With Fwupd you can simply update the UEFI Firmware on the device
• Sleep and Hibernate, working out of the box.
• All Hardware, including add-on cards, are working without the need for extra driver packages.
• Power-Profiles-Daemon is good to go with it! No need for extra power saving options.
• Kernel Boot option/s: amd_pstate=active
• fingerprint Sensor inside Power button is also working out of the box using Fprint With KDE (SDDM) you can set it easily to be used on login and sudo actions (read about the PAM settings with cause) https://wiki.archlinux.org/title/SDDM#Using_a_fingerprint_reader

System:

Machine:
Type: Laptop System: Framework product: Laptop 13 (AMD Ryzen 7040Series)
v: A7

Mobo: Framework model: FRANMDCP07 v: A7

CPU:
Info: 8-core model: AMD Ryzen 7 7840U w/ Radeon 780M Graphics bits: 64
type: MT MCP arch: Zen 4 rev: 1 cache: L1: 512 KiB L2: 8 MiB L3: 16 MiB
Speed (MHz): avg: 1100 min/max: 400/5134

Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Phoenix1 vendor: Framework
driver: amdgpu v: kernel arch: RDNA-3 pcie: speed: 16 GT/s lanes: 16 ports:

Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Rembrandt Radeon High Definition
Audio vendor: Framework driver: snd_hda_intel v: kernel pcie:
speed: 16 GT/s lanes: 16 bus-ID: c1:00.1 chip-ID: 1002:1640
Device-2: Advanced Micro Devices [AMD] ACP/ACP3X/ACP6x Audio Coprocessor
vendor: Framework driver: snd_pci_ps v: kernel pcie: speed: 16 GT/s
lanes: 16 bus-ID: c1:00.5 chip-ID: 1022:15e2
Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
vendor: Framework driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
lanes: 16 bus-ID: c1:00.6 chip-ID: 1022:15e3

Network:
Device-1: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
driver: mt7921e v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 01:00.0
chip-ID: 14c3:0616

Bluetooth:
Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1
speed: 480 Mb/s lanes: 1 bus-ID: 1-5:3 chip-ID: 0e8d:e616

WIFI:

I do not have issue in general with the wifi but seems it does have a small power management issue so i try to disable that feature:

with iw installed you can check if powersave mode is active:

iw dev wlan0 get power_save

mkdir -p /etc/NetworkManager/conf.d/

sudo nano /etc/NetworkManager/conf.d/disable-wifi-powersave.conf

adding this in the config:

[connection]
wifi.powersave = 2

and restart NetworkManager:

sudo systemctl restart NetworkManager

joekamprad has a blog about anything else on that device as of he got one to test EndeavourOS on it from Framework:

https://www.kamprad.net/index.php/framework-13-running-endeavouros-2

There you can find tutorials on adding plymouth boot splash per example, and other things.

]]> 5040 0 0 0 #Framework 13 running EndeavourOS]]> #Framework 13 running EndeavourOS]]> #Framework 13 running EndeavourOS]]> https://discovery.endeavouros.com/desktop-environments/xfce-hi-dpi-screens/2021/06/ Wed, 23 Jun 2021 15:09:50 +0000 https://discovery.endeavouros.com/?p=2107

Some things to do with a Hi-DPI screen on XFCE

To begin - here is a screenshot of the Settings app for XFCE.

First off, there is a possibility that you would be happy with a simple scaling change, that changes the effective resolution to a value other than what you actually have. If you would be happy with such a change, there are two ways to achieve it. One is to use the Settings/Display application,

and select the resolution you consider correct for your use. If you have, for example, a 3840x2160 monitor, you could choose 1920x1080 as your resolution - giving you half the screen real-estate, with items on it at double the size. Another choice might be (depending on your hardware) 2560x1440, which would give you about 75% of the original resolution - or an increase in size of about 150% of the features (and fonts!) on your screen.

There is also a Scale option there that allows changing apparent size as well (this is shown as the active choice in the screenshot above). The choices are 1x, 1.5x, 2x and Custom. Strangely, it works the opposite way to what you would expect - choosing 2x will seem to shrink your windows and fonts to half-size, for example, giving you lots of screen real estate, but requiring a magnifying glass to read anything! If I were using this method, I would choose Custom, and a value of perhaps 0.7 - growing the size of the screen contents to about 150%.

This works well, and the system can remember your settings and fire up graphic sessions in that mode thereafter.

However - if you want to keep your full resolution (especially for graphics), but still want to be able to see and use the features of the User Interface (UI) and the text on the screen, there are other ways. Take a look here at the Settings/Appearance/Settings screen:

Again, there is a Scaling option in the Settings/Appearance/Settings/Window Scaling. This one works the right way around, a scale factor of 2 will double the size of the screen elements. This enables a scaling factor for the system to apply, but it only takes whole numbers (1 or 2 or 3 etc.) which keeps your choices limited. This may be made more flexible in the future, but for now… other options are better.

Assuming neither of these appeal to you, there are a number of steps you can take which will give you more flexibility - keeping your full resolution - while still allowing you to see the UI and the text clearly. The example I use is what I actually run with on my 28 inch 3840x2160 monitor.

The Steps to a more nuanced setting for HI-DPI screens

In Settings/Appearance/Fonts/DPI there is an opportunity to make a change. Most setups first come up with 96 dpi selected as standard. One of the most useful settings is to change to 120 dpi - which is a substantial step up without trying to double everything. Just above this, on the same screen, is the rendering setting - where I would recommend you check the "Enable anti-aliasing" box, and select Slight for the font hinting. Experiment if you wish, it can vary.

Now that you can see a bit better, you can choose a font size that works for you in the Default Font and Default Monospace Font categories. Increase these until you are reading comfortably. 12 might do it, 13 is probably OK, but I'm a bit older so I choose 14 on both as a workable and non-tiring option.

Now, in the Window Manager app, under the Style tab, there are a couple of more changes worth doing. The Window Manager handles the Titlebars and their text, and the 'outside envelope' of the window. Again, you can set the font appropriately, probably to the same size (12, 13, 14) as you opted for in the previous section.

This leaves only the size of such things as toolbars (play. pause and stop buttons in a music player for example) to be set up. There are many themes that can be downloaded, and some of them specify the size in pixels of the toolbar. I run with an assortment of XFCE-38px (Found on XFCE-look.org and Gnome-look.org - I like the ones by Ollifri for example - found dated from about April 2018) options, which, again, I find comfortable - and allow sufficient room for the upsized font you chose in the step before. By the way - this is also where you can choose which window control buttons you wish to use, and where they are located on the titlebar. As you see, I move them left (where they were before Windows degraded workflow), and I hide the menu button.

The final 'tweak' is a global setting to inform those applications that use the QT decoration scheme that you wish a size increase of its UI elements. XFCE is a GTK-based setup, and it can be better to have the QT apps looking similar if you can. There are several ways of making this happen (see the Archwiki https://wiki.archlinux.org/title/Uniform_look_for_Qt_and_GTK_applications for more) - my solution involves adding 3 statements entered in a file that will be executed when you start up - such as .bashrc - or from a file that .bashrc calls (perhaps .bashrc-personal or .bash_aliases), or even in ~.profile. These statements are:

export QT_QPA_PLATFORMTHEME=qt5ct
export QT_SCALE_FACTOR=1.5
export QT_STYLE_OVERRIDE=kvantum

and they can be added to the .bashrc file (or another as you choose) using any text-capable editor. (nano, micro, leafpad, mousepad, featherpad, gedit - whatever you have or like for the task). They will most simply take effect after a relogin.

These effectively cause a resizing of QT UI elements. It also allows you (in Settings/Kvantum Manager) to pick a colour theme etc that you like and matches adequately to your GTK settings. IF you happen not to have the necessary packages already on your system then pacman -S qt5ct kvantum-qt5 will add them in.

A few applications may need their own settings to fit in properly (Chromium-based browsers come to mind). They often need an entry with their startup command - probably by putting it in their .desktop file (in /usr/share/applications). The addition of

--force-device-scale-factor=1.5

to end of the Exec= entry of the .desktop file will cause the browser to grow all elements by the specified factor, greatly increasing readability.

Enjoy your new Hi-dpi screen - and now having the familiarity with the possible settings you can use to make it yours - and to change it as you need to suit your wishes.

Freebird54

]]> 2107 0 0 0 https://discovery.endeavouros.com/pacman/easy-downgrade-by-date/2021/06/ Fri, 25 Jun 2021 20:25:05 +0000 https://discovery.endeavouros.com/?p=2123

Actually - this item has been upgraded and error-checked into an actual EndeavourOS application, eos-shifttime. This has been left here for the sake of those who want to know how it works, for those who want to see how to add mini-apps to the Welcome Personal Commands tab, and as an explanation for the uses it might be put to.

This a little setup I have made to ease usage of the Arch Archives. You can think of it as an alternative to the downgrade of a single package (which may need multiple packages downgraded to match!) and is often used to temporarily 'hold' updates until a more suitable time, while ensuring that packages are correctly in sync for use together.

This item is essentially a script that can be run on its own! However, I decided I would try to make the script even more easily accessible, so here I will also describe setting it up as a button in the Welcome app - although of course it works fine if just called from the command line.

Alternatively, of course, you could carefully read the Archwiki entry on reverting your package status to a previous date, and follow the steps as they describe them. Also, somewhat more accessible, is the entry in the EndeavourOS Wiki. I have called my script ShiftTime, as one of the main uses of TimeShift is to recover from a "bad" upgrade. What this does essentially, is take your system packages back to the date that you specify - by reverting, or internally downgrading all the packages that have been updated after that date to the state (version) they were in ON that date. This has the advantage over downgrade that all packages that interact with each other are taken to the same level at the same time (no dependencies missed).

There are 2 pieces to the setup - the script itself, and the .desktop file that describes it and can launch it. The locations they need to be in may have to be created if they do not already exist. The .desktop file is only needed if you intend to access it from the Menu, or add it to the Welcome app as a Personal Command.

$ mkdir -p ~/.local/share/applications

This command will create the directory if it does not already exist. The following .desktop file goes into it - with the name ShiftTime.desktop suggested.

------------copy between dashed lines only, and paste into a text editor -----------
[Desktop Entry]
Name=ShiftTime
Comment=Revert pkg state to a previous date.
GenericName=Revert pkg state to a previous date
Exec=RunInTerminal shifttime
Icon=system-software-install
Type=Application
NoDisplay=true
StartupNotify=true
Categories=Utility
------------------Do not include the dashes, and Save As shifttime.desktop -------

Then you create a file called shifttime with the following content:

---------------Copy between the dashed lines, and paste into text editor ------
#!/bin/bash
# This script enables an after-the-fact timeshift equivalent for Arch systems
# Give it a date (as in 2020-09-20) and it will use the Arch archive repos 
# to revert to the package state that applied on that date.
#
# 21 September 2020 - freebird54

echo "Select the date to revert your packages to. Press ENTER when ready"
read
REVERTDATE=`yad --calendar --title "Select Date" --date-format=%C%y/%m/%d`
echo " "
echo "Packages will be reverted to the state they were in on $REVERTDATE."
echo " "
echo "Ready to copy /etc/pacman.d/mirrorlist to backup"
sudo mv /etc/pacman.d/mirrorlist /etc/pacman.d/mirrorlist.backup_st
# building the repo entry for the specified date, and temporarily making it the mirrorlist 
echo "Server=https://archive.archlinux.org/repos/$REVERTDATE/\$repo/os/\$arch"  > /tmp/mirrorlistchk
sudo cp /tmp/mirrorlistchk /etc/pacman.d/mirrorlist
rm /tmp/mirrorlistchk
echo " "
echo "Here is the reversion mirrorlist"
cat /etc/pacman.d/mirrorlist
echo "If the date shown is correct please press ENTER"
read
echo " "
# run the 'downdate' command
sudo pacman -Syyuu
echo " "
echo "Restoring the backup mirrorlist..."
sudo cp /etc/pacman.d/mirrorlist.backup_st /etc/pacman.d/mirrorlist
echo " "
echo "Done. Press ENTER to exit."
read
# end of ShiftTime script

---------------Save As shifttime --------------------------

Make the file executable:

$ chmod +x shifttime

Copy the file to somewhere on your path:

$ sudo cp shifttime /usr/bin

At this point, the command is accessible, and will work fine from the command line.

Here is the date selection screen: Using it should be obvious… Click on the date desired, then OK.

Now to add it to the Welcome "Personal Commands" tab if desired. Start up the Welcome app, choose the ‘Tips’ tab, and click on the Personal Command drag&drop button - which will open up a window. Open your File Browser, navigate to ~/.local/share/applications, and click on, hold and drag ShiftTime.desktop over to and drop it in the window that Welcome opened up.

That’s it! Once Welcome comes back, it will have a Personal Commands tab (if it didn’t already) and ShiftTime will be waiting for you. Click on the button that shows its name to easily run the script.

How it works

Pacman will be called to determine which packages will need to be downgraded to revert your system to the way it was on the date you specified. You can interact with pacman as usual to decide whether or not to proceed with the downgrade. The pacman ‘control’ files that the script modifies will be returned to normal after the modified ones have been used.

Again, this does nothing you could not do directly yourself by following the Wiki (Arch or EndeavourOS) instructions - but it saves typing (or looking it up again for the exact format) if you happen to need it. This also shows how easy it is to add your own ideas to the buttons on the Welcome app! Essentially, for most things, all you need to do is create an appropriate .desktop file, and drop it in the drag&drop window.

Another use case I have come up with (beyond 'bad' update recovery) is for keeping a server updated "safely", despite the rolling release nature of Arch based systems. I run a mirror server, and I want it to be 'up' as much as possible. By running this little script, once a week, and choosing a date that is each time one week in the past - I end up with a system that is up-to-date as of a week prior - all the time! This allows time for any glitches caused by updates to have been 'fixed', and sets the system to a date where everything was fine. Of course, if something comes up that takes longer to fix - just hold off on updating until things are working again.

The final use case that I have in mind is for system updating when (for whatever reason) an Arch-based setup has been left without updates for a LOONGG time - maybe months. If you choose intermediate dates to update to, perhaps every 2 weeks forward in time, you greatly reduce the likelihood of major changes causing you problems over the timespan the system has been left unupdated.

]]> 2123 0 0 0 https://discovery.endeavouros.com/applications/beginners-guide-to-mpd-config-and-clients/2021/08/ Fri, 27 Aug 2021 16:06:21 +0000 https://discovery.endeavouros.com/?p=2383

Beginner's Guide to MPD - Config and Clients

Music Player Daemon (MPD) is a flexible, powerful, server-side application for playing music. Through plugins and libraries it can play a variety of sound files while being controlled by its network protocol.

This guide is for users who store music on their device and want an efficient way to manage it.

VLC does a great job of basic playback. But for proper music libraries, using a dedicated music player app can help you manage and find music easily. We can get one step further by using MPD, which supercharges the experience. While it required some editing of text based configuration file, it is not difficult to set up. Should take less that 10-15 minutes at most while following this guide.

Enter MPD

MPD (music player daemon) is an audio player that has a server-client architecture. It can easily manage large music libraries. To put “large” into perspective, we are talking about libraries with over 50k tracks or almost a terabyte of music. Even such huge libraries are no sweat for MPD. Add to that, the server-client architecture allows many applications to control music playback - even you can write an app to control the MPD server!

Installing MPD

The package is available in Arch Linux repository. You can install it via Pacman.

sudo pacman -S mpd

Configuration

Get the example configuration file at /usr/share/doc/mpd/mpdconf.example or from this link.

Save it in ~/.config/mpd/ with name mpd.conf.

Uncomment some options at the beginning of this file. music_directory, db_file, pid_file and state_file. Set a location for all these as you like. At the very least I suggest changing the music_directory from “~/music” to “~/Music”. (notice the capital ‘M’). This is because the pre-created music folder starts with a capital 'M'. It is not a restriction though. Often people store their music collection on an HDD, while the distro is installed on SSD. Having a state file isn't necessary, however, enabling it will allow you to retain play queue when you restart MPD server.

Scroll down to about line 78 and uncomment bind_to_address. Change the value to “localhost” or to a different address if you want. Next uncomment port a few lines below. Let it stay at the default value, which is “6600”. You can also add a password if you want. This will prevent unauthorized users on your network from being able to control your MPD instance.

At around line 97, uncomment restore_paused and set value to “yes”. This will ask MPD to start in "paused" state, otherwise music playback will start right on startup. However, you may want to have it disabled if you are installing on something like a Raspberry Pi, which will be used specially for music playback.

Now we will enable ALSA output. Scroll down to around line 200, where you will see option for ALSA audio output. Uncomment the opening and closing line (audio_output{ and }). Inside the block, uncomment type and name. You also want to uncomment mixer_type and change it from "hardware" to "software". This will allow you to control music playback volume separate from system volume.

Save the file, and we are ready to move forward.

In this post, I have suggested edits in the config multiple times. Every time you edit the config file, you need to restart the MPD server for the changes to take effect.

mpd --kill
mpd

Copying your Music Library

Copy your music folders/songs to ~/Music/. As simple as that! Remember we set the music_directory value to this folder? You can set that value to a different one if you don’t want to copy your library to a new place.

What do I do?

I will describe two set ups that I use.

On my PC - I have access to multiple external drives; no need to copy music to internal HDD. So I utilize symlinks on my PC. At around line 134 in mpd.conf I uncomment follow_outside_symlinks and set it to "yes". (should be "yes" by default). It tells MPD that it should follow symlinks while searching the music directory even if the symlink target leads out of your music directory. Next, I create symlinks from my music directories on external locations. These symlinks are all stored in ~/Music. Now, MPD can discover music from external drives as well and you don’t need to copy all the music to your installation root. If I have unplugged a specific drive, then MPD will simply skip over the songs from that drive.

On my laptop - it needs to be carried around; I can’t have my external drives always with me. So all my music is copied onto the internal HDD. This location is defined in the MPD config. The HDD is mounted automatically on boot since I have it added to my fstab.

Launch The Server!

Now, you are ready to launch the server! Open a terminal and run mpd. Exceptions about Tidal and wildmidi can be ignored. You can add this command to your startup script to have the server launch automatically when you log in. I have it in my i3wm config.

There is also a systemd service that you can use.

systemctl --user enable mpd.service

This will start the server automatically when you log in.

Important : MPD can be launched as root also, but don’t do that please!

Adding a Frontend - Cantata

What do you do after you have set up a server? You need a client software that can interact with your server. MPD, because its open source and has libraries in multiple languages, enjoys support for multiple frontends. A very popular one is ncmpcpp. It's console based, and while I do like console applications, I also prefer managing music via a graphical application. So, I use Cantata, as it is feature rich and does a good job of interacting with MPD server. It also has an inbuilt tag editor and support for streaming from SoundCloud, Jamendo etc. It can also work without an MPD server by reading files directly off your storage.

When you start Cantata for first time, you should see such a window. Choose "Standard multi-user/server setup" and hit next.

[icon name="exclamation-triangle" prefix="fas"]

According to the MPD webside canata and others are gone unmaintained: https://www.musicpd.org/clients/

Next, you will be asked about server connection details. Use "localhost" for Host and "6600" for port. Alternatively, if mpd is running, then you can click on Discover button and choose your server. Enter a password if you configured it earlier. Set the music folder path to the folder you specified in mpd.conf. Now, hit Connect button. It should give success immediately, and you can now click Next at bottom of window.

You can enable/disable cover fetching as per your wish. Do note that enabling this feature will make Cantata connect to the internet and send basic track info online.

Click Next, and now Cantata is ready for use.

You can use any other client - GUI or CLI - instead of Cantata.

Alternatives:

MPDevil:

Mpdevil is a simple music browser for the Music Player Daemon (MPD) which is focused on playing local music without the need of managing playlists. Instead of maintaining a client side database of your music library, mpdevil loads all tags and covers on demand. So you'll never see any outdated information in the browser. Mpdevil strongly relies on tags.

https://github.com/SoongNoonien/mpdevil ---> https://aur.archlinux.org/packages/mpdevil

Ymuse:

Ymuse is an easy, functional, and snappy GTK front-end (client) for Music Player Daemon written in Go. It supports both light and dark desktop theme.

https://github.com/yktoo/ymuse ----> https://aur.archlinux.org/packages/ymuse-bin

Get to know MPC

MPC is a simple command line client to mpd. It is used to issue commands to MPD and get info about the current track, queue etc. You can install it from your package manager or compile from source.

One command you should know right now is mpc update. This re-scans your music directory and creates a database of stored tracks. I bind it to Mod+Shift+m. Cantata also has option to update database, but I prefer using wm keybindings.

Some more commands that I have in my config:

mpc seekthrough +00:00:10:	Seek the current playing track 10s forward. Replace argument with a different time duration or use minus instead of plus to seek backwards.
mpc next:	Skip to the next track
mpc prev	Play the previous track
mpc toggle	Play queue if paused, and pause if playing
mpc volume +2	Raise volume by 2%. Use a different value for different percentage
mpc volume -2	Lower volume by 2%. Use a different value for different percentage

I have bound these commands to different wm keybindings and it lets me control playback right from the keyboard without leaving my active application. Note that its not necessary to use mpc. I mentioned it in this post because it allows easy control with terminal commands which can be used in your configs or wrapped in shell scripts.

Controlling MPD with your Android Phone

Now this is where the real fun starts. You can control MPD playback via your smartphone. This makes an easy set up, where you can have your MPD server on a Raspberry Pi and you control playback using your smartphone. And yeah, without using any spooky closed source proprietary applications.

Install one of the many MPD controlling apps available on the Play Store. I used MALP because it is open source and has a decent UI. On first launch, you will be on the profiles page. Tap the plus icon on top right and enter your server details. You can know your system IP address by running the ifconfig command. Note the IP address of the interface you are connected to (wifi, ethernet, etc).

You should now have your phone connected to your MPD server!

Utilizing HTTP Streams

This is another superpower of MPD, that you can stream music over a network (even the internet!).

Go into your mpd.conf and around line 270, uncomment httpd audio output.

audio_output {
    type        "httpd"
    name        "My HTTP Stream"
    encoder        "lame"        # optional, vorbis or lame
    port        "8000"
#    bind_to_address    "0.0.0.0"        # optional, IPv4 or IPv6
#    quality        "5.0"            # do not define if bitrate is defined
    bitrate        "128"            # do not define if quality is defined
    format        "44100:16:1"
    max_clients    "0"            # optional 0=no limit
}

You can increase the bitrate if you like. 256 is a sweet spot for http streaming of mp3 audio, but keep in mind that your FLAC/WAV music will be down-scaled before streaming. Also, I highly suggest changing the max_clients value to the number of simultaneous connections you would expect. In my configs, I set it to 1 because that’s what I need. If you are streaming music to multiple devices at once, set it to a higher value.

On your other device, open a terminal, and run the following command to start playback.

mpv http://<host-name>:8000

For example, I run the following:

mpv http://192.168.29.129:8000

The host machine should be reachable via the other machine. If they are on same local network, all well and good. If not, you can still access the server outside your local network by port forwarding on your router.

You can also stream via icecast if you want. Here is the link to relevant Arch wiki entry. https://wiki.archlinux.org/title/Icecast

Music info/controls on your bar

Polybar has an MPD module that can display current track info and controls on your bar.

You can find the module code here: https://github.com/polybar/polybar/wiki/Module:-mpd

Suggestions/Changes

In case you want to suggest additions or changes to this entry, you can create a post under this forum thread : https://forum.endeavouros.com/t/beginner-s-guide-to-setting-up-and-using-mpd/16831

]]> 2383 0 0 0 https://discovery.endeavouros.com/news/wp-global-styles-neve/2022/01/ Sat, 29 Jan 2022 10:19:39 +0000 https://discovery.endeavouros.com/news/wp-global-styles-neve/2022/01/ 3286 0 0 0 https://discovery.endeavouros.com/window-tiling-managers/openbox/2022/03/ Thu, 10 Mar 2022 07:29:48 +0000 https://discovery.endeavouros.com/?p=3376

Introduction

Openbox is a highly configurable and minimal floating window manager. This lets you manage your windows with your mouse the way you would do on a traditional DE like Xfce, but Openbox allows much more configuration, as is the case with most standalone window managers. An expected side effect is that Openbox is very light on system resources.

Main Configuration

Openbox main config is at ~/.config/openbox/rc.xml. You usually don't need to edit it manually. You can use the bundled obconf utility to make changes to the config via a GUI. This rc.xml file contains

• Keyboard shortcuts
• Theming
• Desktop and Virtual Desktop settings
• Application Window settings

The right click menu config is stored at ~/.config/openbox/menu.xml. This file provides a static menu.

Autostart applications are defined in ~/.config/openbox/autostart.

Under ~/.config/openbox/scripts/ you'll find the various scripts Openbox CE uses to function.

Application launcher menu

The menu activated by clicking the bottom left button is jgmenu. Its config is stored at ~/.config/openbox/jgmenu/jgmenurc.

Dunst

Dunst shows your notifications. Config is located in ~/.config/dunst/dunstrc. You can change the colours, position etc.

One important setting you may want to change is the binding for Ctrl + grave. By default, this is used to show notification history. Useful in case you miss a notification or want to see the details again. The keybinding may conflict with other applications. For example, the same keybinding is also used in Code-OSS/VSCode. To disable the behaviour in dunst, open dunstrc file and comment out line 274.

https://github.com/EndeavourOS-Community-Editions/openbox/blob/main/.config/dunst/dunstrc#L274

To comment it, you simply put a pound symbol at beginning of line.

Panel

The panel we use is Tint2. Its config is stored at ~/.config/tint2/tint2rc. The panel too can be configured via the bundled Tint2 settings application.

Contribute

Development happens over at our GitHub repo. The repository is at https://github.com/EndeavourOS-Community-Editions/openbox/

Feel free to discuss issues and suggestions on our forum : https://forum.endeavouros.com/c/desktop-environments/openbox/24

]]> 3376 0 0 0 https://discovery.endeavouros.com/system-rescue/dracut/2022/12/ Mon, 19 Dec 2022 11:00:26 +0000 https://discovery.endeavouros.com/?p=3855

Dracut

Overview

dracut is a highly modular tool for generating initramfs images.

As of the Cassini release in 2022, it is the default for EndeavourOS.

In general, it is superior to mkinitcpio in it’s ability to autodetect needed modules and for most use cases will work without any further configuration.

Regenerating the initrds

You can regenerate the initrds with the command sudo dracut-rebuild

Customizing dracut

Dracut is configured via drop-in conf files in the /etc/dracut.conf.d

Making the initramfs smaller

For example, if you wanted to limit the size of your initrd, you could add a file named smaller.conf with the contents of:

hostonly_mode=strict

Adding a dracut module

Another common item might be to add a module manually. While most modules will be automatically configured, there may be times you want to add a module.

For example, if you wanted to forcibly add support for mdraid, you could use a file with the contents of:

add_dracutmodules+=" mdraid "

It is worth noting that this is not generally needed as dracut will automatically detect when mdraid support is needed.

Removing a module

If you want to ensure that a module doesn’t get added to the initramfs image, you can do so like this:

omit_dracutmodules+=" i18n "

This would remove i18n support from the initrd. This is another way to reduce the size if you don’t need support for internationalization.

Early KMS loading

If you need early KMS loading for nvidia that can be done with a this content:

force_drivers+=" nvidia nvidia_modeset nvidia_uvm nvidia_drm "

For Intel:

force_drivers+=" i915 "

For modern AMD:

force_drivers+=" amdgpu "

Making dracut less verbose

Edit config file located at /etc/eos-dracut.conf or /etc/kernel-install-for-dracut.conf and set DRACUT_QUIET to DRACUT_QUIET="true"

This will enable dracut's quiet mode, which will suppress most output.

Disable the generation of the fallback initrd

Edit config file located at /etc/eos-dracut.conf or /etc/kernel-install-for-dracut.conf and set NO_DRACUT_FALLBACK to NO_DRACUT_FALLBACK="true"

This will stop future fallback initrds from being generated.

Please note that this will not remove any existing fallback initrds that already exist. When using kernel-install-for-dracut (systemd-boot), this will change automatically as new kernel updates happen. For eos-dracut (grub), you will need to remove them manually.

Update (rebuild) kernel boot images

When using default systemd-boot and dracut:

sudo reinstall-kernels

When using Grub and dracut:

sudo dracut-rebuild

Converting to dracut from mkinitcpio

If you would like to convert an existing system to dracut, the process is very simple. You can use the following commands depending on if you are using systemd-boot or grub.

systemd-boot with kernel-install

If you use systemd-boot, this process is fairly simple

sudo pacman -S kernel-install-for-dracut

If you receive an error about the package mkinitcpio-openswap, uninstall it with sudo pacman -R mkinitcpio-openswap and run the command again.

If you have any LUKS encrypted file systems, you must create a dracut drop-in config for that. Create the file /etc/dracut.conf.d/encryption.conf with the following content:

install_items+=" /etc/crypttab "

If you have an encrypted swap partition, you must also add a line that looks like this to the encryption.conf file created above:

add_device+=" /dev/disk/by-uuid/ad44a367-09ec-4f74-bf66-f284438280db "

However, be sure to replace ad44a367-09ec-4f74-bf66-f284438280db with the UUID for your swap luks partition.

Last run sudo reinstall-kernels and reboot

grub (or any other bootloader)

For any other bootloader, this process should be followed.

sudo pacman -S dracut

sudo pacman -S eos-dracut

sudo pacman -Rc mkinitcpio

If you have any LUKS encrypted file systems you must create a dracut drop-in config for that. Create the file /etc/dracut.conf.d/encryption.conf with the following content:

install_items+=" /etc/crypttab /crypto_keyfile.bin "

If you have an encrypted swap partition, you must also add a line that looks like this to the encryption.conf file created above:

add_device+=" /dev/disk/by-uuid/ad44a367-09ec-4f74-bf66-f284438280db "

However, be sure to replace ad44a367-09ec-4f74-bf66-f284438280db with the UUID for your swap LUKS partition.

sudo dracut-rebuild

Optional: Install the EOS defaults for dracut

EOS ships with some custom default settings for dracut. If you would like to install these, you can do so with this command:

curl https://raw.githubusercontent.com/endeavouros-team/EndeavourOS-ISO/main/airootfs/etc/dracut.conf.d/eos-defaults.conf | sudo tee /etc/dracut.conf.d/eos-defaults.conf

These will take effect next time your initrds are regenerated.

Dracut and the bootloaders systemd-boot and grub

To mangage kernel handling related to the two bootloader options, EndeavourOS uses two helper tools:

systemd-boot uses: kernel-install-for-dracut package/tool

grub uses eos-dracut package/tool

Make sure to have the correct package tool installed to pair with the bootloader you are using.

More information

There are a few other good sources of information on dracut.

• One of the best sources of information on dracut modules is the Gentoo wiki.
• Likewise the Arch wiki contains some good information on dracut.
• The official dracut wiki is also a good source of reference information.

]]> 3855 0 0 0 https://discovery.endeavouros.com/system-rescue/systemd-boot/2022/12/ Mon, 19 Dec 2022 11:00:30 +0000 https://discovery.endeavouros.com/?p=3859

systemd-boot

Overview

Systemd-boot is a simple UEFI boot manager that is part of systemd. It has several advantages over other boot managers:

• It is uncomplicated and uses simple text file which only contain a few lines
• It is less prone to breakage, easy to troubleshoot and doesn’t require any process to rebuild config files
• It allows each Linux install to manage their own configuration files and doesn’t require detection between different installs

EndeavourOS uses kernel-install with systemd-boot to manage the process. This has a few advantages:

• A more modern approach
• Completely automates the process of entry creation and removal
• Safe for multi-booting since it moves your kernels and images to a installation specific subdirectory

Usage

In general, you shouldn’t need to do anything special to manage systemd-boot in our default configuration as everything should be managed automatically. Here are a few tips and trips to help you along the way.

Understanding reinstall-kernels

The script reinstall-kernels both regenerate the initrds and create/update the boot entries. It works with both dracut and mkinitcpio as long as you have either kernel-install-for-dracut(The default) or kernel-install-mkinitcpio(AUR) installed.

How to modify kernel options

In systemd-boot, it is actually quite simple. You edit the appropriate entry file which can be found on your EFI partition in the loader/entries directory. Each entry is a boot option on the menu and each has a line called options. You can modify these entries directly, however, these changes may be overwritten when packages are installed or updated.

To make the changes, instead of modifying the entries, modify the file /etc/kernel/cmdline which is a one-line file containing a list of kernel options. Then run sudo reinstall-kernels which will populate the entries and regenerate the initrds.

If you would prefer to use the current kernel options from the running system, you can instead rm the file /etc/kernel/cmdline and then run sudo reinstall-kernels.

How to change the default entry to boot

There is a default entry inside /efi/loader/loader.conf that determine the default boot entry.

On a new install, it will look something like this:

default 665eca4ae83246df8ec17d1cbc6a1763*

That first string of characters is you entry token which identifies the install. That is important if you are dual-booting with another Linux, otherwise it can be replaced with *. That line supports wildcards and so if you want to boot the LTS kernel by default you could use something like this:

default 665eca4ae83246df8ec17d1cbc6a1763*lts.conf

Alternatively, if you want to boot the mainline kernel by default, something like this should work:

default 665eca4ae83246df8ec17d1cbc6a1763-*-arch?-?.conf

These changes will take effect on the next reboot and nothing else is required except modifying the file.

More information

There are a few other good sources of information on systemd-boot.

• Not to forget the Arch-Wiki
• Freedesktop with all basic Information on handling and Options
• General info and links can be found also in Wikipedia
• And the Sourcecode git can come in handy too
• man systemd-boot and man loader.conf for all possible options

]]> 3859 0 0 0 https://discovery.endeavouros.com/news/wp-global-styles-twentytwentyfive/2026/08/ Sun, 09 Aug 2026 10:59:48 +0000 https://discovery.endeavouros.com/news/wp-global-styles-twentytwentyfive/2026/08/ 5300 0 0 0 https://discovery.endeavouros.com/news/wp-global-styles-exs/2026/08/ Sun, 09 Aug 2026 11:47:55 +0000 https://discovery.endeavouros.com/news/wp-global-styles-exs/2026/08/ 5312 0 0 0