Skip to content

Commit 293b3f5

Browse files
committed
Initial commit.
- Completely rebuilt blog on Hugo - Migrated some of the old Jekyll posts to new blog.
0 parents  commit 293b3f5

File tree

140 files changed

+3706
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

140 files changed

+3706
-0
lines changed

.gitignore

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
# Generated files by hugo
2+
/public/
3+
/resources/_gen/
4+
/assets/jsconfig.json
5+
hugo_stats.json
6+
7+
# Executable may be added to repository
8+
hugo.exe
9+
hugo.darwin
10+
hugo.linux
11+
12+
# Temporary lock file while building
13+
/.hugo_build.lock

archetypes/default.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
+++
2+
categories = ['']
3+
tags = ['']
4+
date = '{{ .Date }}'
5+
draft = true
6+
title = '{{ replace .File.ContentBaseName "-" " " | title }}'
7+
author = '{{ .Site.Params.Author.name }}'
8+
summary = 'I show up on posts!!!'
9+
description = 'I show up in the post sidebar!!!'
10+
slug = 'I show up in the URL'
11+
+++
12+

archetypes/post.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
+++
2+
categories = ['']
3+
tags = ['']
4+
date = '{{ .Date }}'
5+
draft = true
6+
title = '{{ replace .File.ContentBaseName "-" " " | title }}'
7+
author = '{{ .Site.Params.Author.name }}'
8+
summary = 'I show up on posts!!!'
9+
description = 'I show up in the post sidebar!!!'
10+
slug = 'I show up in the URL'
11+
+++
12+

content/about.md

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
+++
2+
categories = ['Blog']
3+
tags = ['']
4+
date = '2025-04-16T11:00:00-00:00'
5+
title = 'Bobby Codes'
6+
author = "Bobby"
7+
+++
8+
9+
## About Me
10+
11+
Heyo! Bobby here!
12+
13+
Welcome to my space for jotting down this, that, etcetera and something or other!
14+
If you're here, I hope you find something useful in your journey.
15+
16+
I have no place for big egos or high horses.
17+
Technology is a gift, as is learning it.
18+
Everyone is somewhere in their journey and none of us have reached the end.
19+
Be curious.
20+
21+
---
22+
23+
About me:
24+
25+
- I talk too much about using Arch _(btw)_.
26+
- I will also talk way too much about Neovim and Vim motions.
27+
- `pwsh` is my default shell because I just love an object pipeline.
28+
* _)If you have beef with that see the section above!)_
29+
- I still love byte-streaming shells like `bash` and `zsh`!
30+
* _(When you need speed or ubiquity, you can't the classics)_
31+
- I love solving problems and customizing every little aspect of things.
32+
* _(hence Arch with Hyprland and Neovim)_
33+
- I have the attention span of a housefly sometimes.
34+
* _(But that power has is the reason why I have dabbled in to many different tech stacks and languages!)_
35+
36+
---
37+
38+
Zen of learning:
39+
40+
```text
41+
To the novice, mountains are mountains and waters are waters;
42+
To the intermediate student mountains are no longer mountains, and waters are no longer waters;
43+
To the master, mountains are once again mountains and waters are once again waters.
44+
```
Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
+++
2+
categories = ['Hardware']
3+
tags = ['Migrated Post']
4+
date = '2023-06-12T00:00:00-04:00'
5+
draft = false
6+
title = 'Corsair H100i AM4 Mounting Bracket Seems Loose'
7+
author = 'Bobby'
8+
summary = 'Are you doing a PC build and your H100i seems a little wiggly??'
9+
description = 'This drove me crazy for about half a day.'
10+
slug = 'I show up in the URL'
11+
+++
12+
13+
## H100i - New AM4 Mounting Bracket Seems Loose
14+
15+
### Table of Contents
16+
17+
<!-- vim-markdown-toc GFM -->
18+
19+
* [Overview](#overview)
20+
* [The Issue](#the-issue)
21+
* [Troubleshooting](#troubleshooting)
22+
* [Solution](#solution)
23+
24+
<!-- vim-markdown-toc -->
25+
26+
### Overview
27+
28+
I am writing this here because with the uncertainty of the future of Reddit I still wanted this information locatable if the Reddit post disappears.
29+
I built a new PC in the summer of 2022 and part of it included the [Corsair H100i Elite Capellix Liquid CPU Cooler](https://www.amazon.com/gp/product/B08G1NSG7F/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1)
30+
I had good luck with my prior Corsair cooler and figured why not?
31+
32+
Hardware items in play:
33+
34+
- **Cooler:** Corsair iCUE H100i Elite Capellix Liquid CPU Cooler
35+
- **Board:** ASUS Prime X570-Pro
36+
- **CPU:** AMD Ryzen 7 5800X
37+
38+
### The Issue
39+
40+
I ended up with the newer AM4 mounting bracket which had 4 standoffs instead of the prior 2 hooks/thumbscrew configuration.
41+
I went to assemble the cooler mounting hardware to the board and I noticed there was a lot of play with the back plate.
42+
43+
- Gif of my confusion as to why there would be that much play: [Watch me struggle](https://imgur.com/eQN7zju)
44+
45+
### Troubleshooting
46+
47+
Of course I re-read the Corsair instructions and validated all the steps were followed correctly, still had a lot of wiggle.
48+
I also found a video on the 'Corsair Lab' YouTube channel which walked through the process but frustratingly it made no mention of any wiggle.
49+
50+
- Video here if interested: [How to Install CORSAIR iCUE RGB ELITE Liquid CPU Cooler](https://www.youtube.com/watch?v=9swpPo-ey0w&t=85s).
51+
52+
I searched various materials but I only continued to find older references to a different H100i mounting bracket or unresolved questions similar to mine.
53+
54+
I eventually posted it on the "/r/Corsair" subreddit and had the answer confirmed!
55+
56+
### Solution
57+
58+
If anyone stumbles on this post or the Reddit thread you aren't crazy, sometime in 2022 Corsair changed the AM4 mounting bracket from the 2 hook to 4 screws on standoffs.
59+
If during the assembly you see the play between the back plate this is normal, everything tightens up nice when you screw down the thumb screws.
60+
Also it helps if you have someone help by pushing the plate to help you screw it the thumb screws on the other side.
61+
130 KB
Loading
Lines changed: 151 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,151 @@
1+
+++
2+
categories = ['Linux']
3+
tags = ['Commands', 'Migrated Post']
4+
date = '2022-11-29T12:00:00-04:00'
5+
draft = false
6+
title = 'Linux Laptop Brightness'
7+
author = 'Bobby'
8+
summary = 'So you went ahead and installed a trendy window manager and now you need to change your laptop screen brightness...'
9+
description = 'brightnessctl to the rescue!'
10+
slug = 'linux-laptop-brightness'
11+
+++
12+
13+
## Change Your Linux Laptop Backlight Brightness
14+
15+
### Table of Contents
16+
17+
<!-- vim-markdown-toc GFM -->
18+
19+
* [The Challenge](#the-challenge)
20+
* [Change the Backlight from the File](#change-the-backlight-from-the-file)
21+
* [brightnessctl](#brightnessctl)
22+
* [Basic Usage](#basic-usage)
23+
* [Changing Brightness](#changing-brightness)
24+
* [Reference Links](#reference-links)
25+
26+
<!-- vim-markdown-toc -->
27+
28+
### The Challenge
29+
30+
So you spent too much time looking at fancy configs on Reddit...
31+
32+
After looking at all the cool setups and decided to use a trendy window manager like **i3**, **dwm**, or even **Sway** if you're one of those fancy Wayland kids with an AMD card.
33+
You finally decided to use one of them and realized, some batteries aren't included and some assembly is required.
34+
35+
Trust me, I lived it. Granted I love it. Tweaking every knob and tuning every dial.
36+
You do need to figure some things out that you probably took for granted, simple things like changing your laptop screen brightness.
37+
38+
The laptop backlight on my Lenovo Thinkpad T480 was a bit of a learning journey for me.
39+
I finally got what I needed in the end, gather 'round and hear my tale, maybe it will save you some time.
40+
41+
**⚠️ DISCLAIMER**:[^1] <br />
42+
These are my specs:
43+
44+
* Laptop: Lenovo Thinkpad T480, i5-8250U, Intel UHD Graphics 620
45+
* OS: Arch Linux
46+
* WM: i3 (gaps)
47+
48+
_Obligatory Neofetch_... <br />
49+
![neofetch](/posts/linux-laptop-backlight-brightness/neofetch.png)
50+
51+
I started by manually editing my _brightness_ file found within _/sys/class/backlight/intel_backlight/_. Very un-fun.
52+
I attempted some other utilities like `xbacklight` before settling on `brightnessctl`.
53+
I don't have a compelling case to why I prefer `brightnessctl`, I just find it easy and simple.
54+
55+
### Change the Backlight from the File
56+
57+
If you [RTFM _(Backlight Hardware Interfaces)_](https://wiki.archlinux.org/title/backlight) you can get some detail on how this all works. I think the Arch wiki quotes it best:
58+
59+
> The brightness of the screen backlight is adjusted by setting the power level of the backlight LEDs or cathodes. The power level can often be controlled using the ACPI kernel module for video. An interface to this module is provided via a sysfs(5) directory at /sys/class/backlight/.
60+
61+
If you actually look at the contents of the backlight file you'll see it's just a number.
62+
_(Also in my case it is not just 0-100)_
63+
This is the number I was modifying when I was just manually changing the file.
64+
65+
Here we have my backlight _**intel_backlight**_. <br />
66+
We can see the _**brightness**_ of my intel_backlight and it is a not very intuitive _**"758"**_ currently on my system. <br />
67+
We can also view the _**max_brightness**_ which is _**"1515"**_. <br />
68+
69+
![brightnessfile](/posts/linux-laptop-backlight-brightness/brightnessfile.gif)
70+
71+
Given this we can deduce at the time of writing this my screen is at about 50% brightness.
72+
While we could edit the _**brightness**_ file it's probably easier to use a utility unless you want to feel like J.P. from Grandma's Boy.
73+
74+
### brightnessctl
75+
76+
Using `brightnessctl` is easy.
77+
I won't include any gifs here because you won't see the screen change.
78+
You will just have to trust me, a complete internet stranger!
79+
80+
**❗NOTE**: I am not using sudo because I added my user to the _video_ group.
81+
82+
Simple installation via `pacman` on Arch.
83+
84+
```bash
85+
sudo pacman -S brightnessctl
86+
```
87+
88+
#### Basic Usage
89+
90+
```bash
91+
# Check current device backlight, note this will match the file
92+
brightnessctl
93+
94+
# You can also list other devices with brightness controls with -l, --list
95+
brightnessctl -l
96+
97+
# If you plan to use the output elsewhere you can also use -m, --machine-readable
98+
# This will output in a comma separated form which can be parsed easily by other tools
99+
brightnessctl -l -m
100+
# Lets deserialize it (pwsh only for this example)
101+
brightnessctl -l -m | ConvertFrom-Csv
102+
103+
# Just get the brightness number from a device
104+
brightnessctl -d intel_backlight get
105+
106+
# Check the maximum brightness of a device
107+
brightnessctl -d intel_backlight max
108+
```
109+
110+
#### Changing Brightness
111+
112+
```bash
113+
# Set the backlight!
114+
# This sets the device (-d, --device=DEVICE) to 75%
115+
brightnessctl -d intel_backlight set 75%
116+
117+
# Increase from current value + or - 10%
118+
brightnessctl -d intel_backlight set +10%
119+
brightnessctl -d intel_backlight set -10%
120+
121+
# If you want to supress the output use -q, --quiet
122+
# This can be useful if you just don't care about the return or want to wire this into a script
123+
brightnessctl -d intel_backlight set 100% -q
124+
125+
# You can still set by number too, set to 1515 (max)
126+
brightnessctl -d intel_backlight set 1515
127+
128+
# You can test with the -p, --pretend switch which does a whatif/noop
129+
brightnessctl -d intel_backlight set 1% -p
130+
```
131+
132+
**✅TIP**: If you are going to wire `brightnessctl` into another process make sure to leverage the `-m` switch.
133+
Parsing the comma separated values is **MUCH** easier than trying to regex the default output.
134+
I learned this the hard way by not reading the help good. Always read the help good.
135+
136+
There you have it, hopefully it helps!
137+
138+
139+
### Reference Links
140+
141+
142+
* [Arch Wiki - Backlight](https://wiki.archlinux.org/title/backlight)
143+
* [Reddit Post on brightnessctl permissions](https://www.reddit.com/r/archlinux/comments/fpklbs/brightnessctl_only_works_as_root/)
144+
* [Github - brightnessctl](https://github.com/Hummer12007/brightnessctl)
145+
146+
[^1]:
147+
I am by no means an expert at all things Linux and laptop backlights. <br />
148+
There are more backlight utilities than I can count and more models of laptops that exist than I can even begin to imagine. <br />
149+
This is just what worked for me on my Thinkpad T480 running Arch Linux with i3. <br />
150+
Your mileage may vary! <br />
151+
57.5 KB
Loading
47.9 KB
Loading
Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
+++
2+
categories = ['Blog']
3+
tags = ['Announcements']
4+
date = '2025-04-17T11:00:43-04:00'
5+
draft = false
6+
title = 'New Blog Who Dis?'
7+
author = 'Bobby'
8+
summary = 'Welcome to the new experience!'
9+
description = 'Awwww yeah, no Javascript here!'
10+
+++
11+
12+
## Welcome to the Overhaul!
13+
14+
### Why?...
15+
16+
1. A little bit of boredom.
17+
2. A little bit of rebranding.
18+
3. I was a bit over Jekyll.
19+
4. I wanted a theme that was very easy to customize and extend...
20+
a. _...it's just HTML and CSS, no more JS_
21+
22+
**LONG LIVE!**
23+
24+
![hugo](/posts/new-blog-who-dis/hugo.png)
25+
26+
---
27+
28+
What's changing?
29+
30+
- More generalized coding and tech content.
31+
* New language content
32+
* New concepts like game engine building
33+
* More Linux content
34+
* More Neovim content
35+
36+
Q: _"Oh no! Is the PowerShell content done and over?"_
37+
A: Nope, not entirely, there may be a bit less of it and it might be more Linux specific.
38+
39+
Q: _Will the old posts and PowerShell content migrate?_
40+
A: YES! (Some of it). I'm pulling in the pages Google Analytics said got hit the most as well as my favs.
41+
42+
### Onto the Next Chapter!
43+
44+
_Annnnnnnd_ with that, let's light this candle!

0 commit comments

Comments
 (0)