Bazzite on a tablet and Asahi Linux on a Macbook Oh My!

/

Hi there! Don’t worry, I’m still alive. I’ve had to move away yet again. From living in California for four years while working, to moving to Colorado for another four before relocating to Michigan, I’ve seen a good bit of the USA!

Today I’d like to talk about running Bazzite on a refurbished Minisforum V3 tablet I’ve received recently, as well as my adventures with Asahi Linux on an M1 Pro Macbook Pro that I’ve been testing every few weeks.

This here is the awesome Minisforum tablet! I love how thin it is and I think it’ll become my new multimedia device.

Looks like it came with a keyboard and kickstand attachment but no pen. I believe this refurbished model is known as the “Minisforum V3 standard” as I believe there is also an “SE” version.

Later in the evening I ended up getting Bazzite instaled. Turns out this guy shipped with a dead battery, which took me a little while to figure out. Charge first, install things later!

Bazzite has a “tips and tricks” section on their site that links to a github repo here, but it seems that no backlight control for the screen nor keyboard was functioning, and some odd graphical glitches would happen whenever I opened the power management menu or brightness controls from KDE’s lil bar duder. Might try pure Fedora Gnome on it next to see how things go, with maybe CachyOS after. Onwards!

On the Macbook Pro front, BLUE! I like Blue, per the keyboard cover. The flash drive was for prepping the Bazzite installer. This Macbook Pro has been in my possession for probably about a year now. Got it from a friend as they were selling off-lease equipment from a partner.


Anyway, good little bit of kit but it seems the 16GB unified memory can be a bit too small when both the cpu and gpu are fighting for it. I’m regularly using 80% or higher of the RAM just doing web things! May have needed to ask to see the higher spec models.

Sleep seems to work with some battery drain, and most steam games will crash due to memory limitations, but it’s definitely interesting to try Asahi on here. With the news that M2 and M3 chip Macbooks may be supported in the future, I might trade up to a quieter Macbook Air since it will mainly be utililzed for light web use and no gaming or rendering.

On another note, I’ve been going through my past hoard of tech gizmos and will be selling a bunch of things soon. Likely recycling the chromebooks I worked on in the past as well as selling any working and running systems on local marketplace apps soon.

This guy here was a ThinkCentre Chromebox from Lenovo that I eventually got Corebooted using this Chrultrabook guide and running Linux Mint. It was mainly a little smartphone flasher and chip programmer thin client, but it fulfilled its purpose prior to the move to Michigan. Now, it must go as I downsize!

As I’ve written in some previous posts, I’ll add a list of things I found interesting here. I know it’s been a while. I also have links throughout this post, so look for the slightly-different-colored words as you read.

Looking back on my 2024 Linux Gaming in 2025

/

Hi all! I’m sure it’s been a while since I’ve posted. With new jobs and undocumented side projects comes a loss of a track of time it seems. Nevertheless, I’d like to take a look back on the games I played in 2024 on Linux.

Looking back at 2024, it seems I picked up V Rising quite a bit this year. Sharing a server, hosted by a friend of mine, was quite fun. We’d all build up our castles and sack bosses together, as well as get minions and the like. The game ran flawlessly on Linux over the recommended Proton for most of that summer onwards and we played our hearts out.

Core Keeper and No Man’s Sky have been flawlessly working for my on Linux for years, through Proton, so I have no complaints there…outside of the fact that Core Keeper doesn’t optimize Unity. One of the last Unity holdouts, I think Core Keeper will run on it forever despite being a mostly 2D game. The backend chomps at your Steam Deck’s battery life despite you only seeing whats on your screen as you progress in the game. It only gets about 3-4 hours on a good day with the Steam Deck OLED due bloated Unity.

Streets of Rogue 1 has been an interesting story, as running it with the Linux Runtime seems to have you needing to tap around the main menu a bit with your fingers before it recognizes the Steam Deck controls, or Xbox controllers for that matter. When running it through Proton Experimental? Runs fine, but say goodbye to the saves you had in the Linux Runtime. I’ve only recently started playing the Demo for Streets of Rogue 2, and the developer only recently added controller support, so I’ll make a ProtonDB post in the future if the next game needs any tweaks.Steam Machine.

Palworld barely ran when it first came out, due to needing some optimizations. Nowadays, I tend to use the latest Proton-GE for Palworld to be on the safe side, in case any updates come through that break compatibility in some way. I’ve been playing Palworld on and off for probably the past month or so as I try to level up enough in my singleplayer save to access the new content without worries. Great game all around, and screw Nintendo for suing them.

Another game I’ve played a bit in 2024, which likely wasn’t tracked by Steam, was the Ship of Harkinian take on the Legend of Zelda Ocarina of Time. I’ll link to their website here, but wow it’s refreshing being able to play OoT on my Steam Deck and living room Steam Machine. It’s been running excellent.

I’ll be selling the Steam Machine build soon, and replacing it with a Minisforum hx99g.. It will still be running Bazzite, unless the previous audio issues pop back up, in which case it will likely run ChimeraOS. I don’t have any new images of the Steam Machine build, so here’s a previous one. The cables are only slightly more organized, and I bet custom-length sleeved cables would have likely helped immensely with the heat management in here, as the GPU keeps dumping heat into the CPU if ran for longer than four hours on high settings.

Throughout 2025, despite my A.D.D. and prone to getting distracted often in my free time, I’ll try to finish the other projects I’ve half-started. I’d like to finish my FPGA FunnyPlaying GameBoy Color build, 3D print some things with the AnkerMake3D from years back that I’ve just now setup, and eventually finish the Intel Meme Machine build when I can find a case that doesn’t use shitty proprietary fan controllers.

In other news, here’s some things I’ve been reading, watching or getting involved with this year:

Linux Mint on the Dell 13 7310 and building the Bazzite Meme Machine

/

Hello again! Two last little projects before I gear up to start selling off a bunch of projects and builds again soon, should I have to. Need to downsize a bit, as I may be selling my place in coming months. That aside, let’s jump in!

I recently acquired a Dell 13 7310 Chromebook from a prior student of a high school. I first noticed that it was Enterprise Locked, so I reached out to the head of IT for said school, only to receive no response. Fearing the worst, I went ahead and replaced the motherboard for $55 or so, to make sure I started from a clean slate. Enterprise Locking is usually either due to the IT team not properly unenrolling a device before a sale or a student possibly stealing a chromebook.

Next I replaced the 32GB NGFF-sized EMMC module with a 512gb SATA module, as I’ll be shipping this to a friend in need out in the UK. She’ll likely appreciate the larger storage. As I no longer have an Amazon account, due to not wanting to support them, I found a replacement locally.

Now to remove the Write Protect screw and get this baby “Chrultrabook’d” with coreboot!

Looks like Linux Mint Debian Edition is up and running on the main drive fine, so I’ll do another round of updates, preinstall some software for the friend and get it shipped out!
Hmm, may have had the normal Linux Mint distro on this USB for testing. Will make sure everything is working fine there, then wipe it and install LMDE for the friend before shipping out. Made sure to install the keyboard mapping script as well as audio fixes mentioned in this page of the Chrultrabook documentation.

Next up, I have an assortment of new and used parts (mostly new) to build what I’m calling my Bazzite Meme Machine. The naming is due to Intel having a long-running stereotype that their processors suck up too much wattage for what they actually do, and they were known as an oven by a few friends when I worked in California years ago. With this getting Bazzite put on it, I’d like to see how this Arc A580 performs with a 10th gen i5, from before Intel started adding nearly-useless E cores.

However, I think this desktop build will have to wait until the weekend, as I may have a pending interview this week. Here’s hoping I can find new employment before I’m forced to move out of this lovely place.

First Attempt of Alpine Linux on a Tegra K1 Chromebook (HP Nyan Blaze)

/

Hi there again! Here’s to another seemingly-one-off project.

While I’ve been getting quite a lot of traffic on my Linux on Nintendo Switch page recently, I’m sorry to say that my Nintendo Switch died and was harvested for parts by an e-recycler for fixing other switches (minus the bad RAM chips) so I won’t be able to work on that project again unless someone donated a 2017 Nintendo Switch for me to firmware mod or a Switch Lite for me to hardware mod.

That said, a neighbor recently gave me an HP Chromebook 14 also known amongst the Chromebook/Chrultrabook modding scene as nyan-blaze. This chromebook appears to have a physical write protect screw, which are fairly easy to undo, instead of a battery write protect method, so getting into developer mode and installing things shouldn’t be too difficult. The hard part comes when I want to install another distro.

So far it seems NVIDIA Tegra K1 chip support amongst ARM Linux distros is fairly limited. With that in mind, and seeing that the volunteeer postmarketOS community may have worked with this in the past, I’ll go ahead and try running that from a MicroSD card on this system.

Now it looks like the battery on this system my be dead or the cable may be shorted, as it seems to turn off immediately when unplugged. I may have to open it back up and check the battery, but first let’s try running through building and installing a postmarketOS image to a MicroSD card to chuck in here.

[12:39:39] EVERYTHING ON /dev/sdb WILL BE ERASED! CONTINUE? (y/n) [n]: y
(029929) [12:39:41] (native) calculate depends of cgpt (pmbootstrap -v for details)
(029929) [12:39:41] (native) install cgpt
(029929) [12:39:41] % sudo rm -f /home/s31bz/Documents/nyan-blaze/chroot_native/tmp/apk_progress_fifo
(029929) [12:39:41] % sudo mkfifo /home/s31bz/Documents/nyan-blaze/chroot_native/tmp/apk_progress_fifo
(029929) [12:39:41] (native) % cat /tmp/apk_progress_fifo
(029929) [12:39:41] (native) % sh -c exec 3>/tmp/apk_progress_fifo; apk --no-progress --progress-fd 3 add cgpt --no-interactive
(029929) [12:39:41] New background process: pid=36458, output=background
WARNING: opening /mnt/pmbootstrap/packages: No such file or directory
(1/1) Installing cgpt (6310032-r8)
Executing busybox-1.36.1-r25.trigger
OK: 23 MiB in 71 packages
(029929) [12:39:42] (native) partition /dev/install (boot: 256M, reserved: 0M, root: the rest)
(029929) [12:39:42] (native) % blockdev --getsz /dev/install
1048576000
(029929) [12:39:42] (native) % parted -s /dev/install mktable gpt
(029929) [12:39:42] (native) % cgpt create /dev/install
(029929) [12:39:43] (native) % cgpt add -i 1 -t kernel -b 8192 -s 32768 -l pmOS_kernel -S 1 -T 5 -P 10 /dev/install
(029929) [12:39:43] (native) % cgpt add -i 2 -t efi -b 40960 -s 524288 -l pmOS_boot /dev/install
(029929) [12:39:43] (native) % cgpt add -i 3 -t data -b 565248 -s 1048010719 -l pmOS_root /dev/install
WARNING: One of the GPT headers/entries is invalid

ERROR: please run 'cgpt repair' before adding anything.
(029929) [12:39:43] (native) % partx -a /dev/install
partx: /dev/install: error adding partitions 1-2
(029929) [12:39:43] % sudo touch /home/s31bz/Documents/nyan-blaze/chroot_native/dev/installp2
(029929) [12:39:43] % sudo mount --bind /dev/sdb2 /home/s31bz/Documents/nyan-blaze/chroot_native/dev/installp2
(029929) [12:39:43] % sudo touch /home/s31bz/Documents/nyan-blaze/chroot_native/dev/installp3
(029929) [12:39:43] % sudo mount --bind /dev/sdb3 /home/s31bz/Documents/nyan-blaze/chroot_native/dev/installp3
mount: /home/s31bz/Documents/nyan-blaze/chroot_native/dev/installp3: special device /dev/sdb3 does not exist.
       dmesg(1) may have more information after failed mount system call.
(029929) [12:39:43] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
(029929) [12:39:43] NOTE: The failed command's output is above the ^^^ line in the log file: /home/s31bz/Documents/nyan-blaze/log.txt
(029929) [12:39:43] ERROR: Command failed (exit code 32): % sudo mount --bind /dev/sdb3 /home/s31bz/Documents/nyan-blaze/chroot_native/dev/installp3
(029929) [12:39:43] See also: <https://postmarketos.org/troubleshooting>
(029929) [12:39:43] Traceback (most recent call last):
  File "/usr/lib/python3.12/site-packages/pmb/__init__.py", line 63, in main
    getattr(frontend, args.action)(args)
  File "/usr/lib/python3.12/site-packages/pmb/helpers/frontend.py", line 329, in install
    pmb.install.install(args)
  File "/usr/lib/python3.12/site-packages/pmb/install/_install.py", line 1295, in install
    install_system_image(args, 0, f"rootfs_", step, steps,
  File "/usr/lib/python3.12/site-packages/pmb/install/_install.py", line 836, in install_system_image
    pmb.install.partitions_mount(args, layout, disk)
  File "/usr/lib/python3.12/site-packages/pmb/install/partition.py", line 52, in partitions_mount
    pmb.helpers.mount.bind_file(args, source, target)
  File "/usr/lib/python3.12/site-packages/pmb/helpers/mount.py", line 72, in bind_file
    pmb.helpers.run.root(args, ["mount", "--bind", source,
  File "/usr/lib/python3.12/site-packages/pmb/helpers/run.py", line 52, in root
    return user(args, cmd, working_dir, output, output_return, check, env,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/pmb/helpers/run.py", line 30, in user
    return pmb.helpers.run_core.core(args, msg, cmd, working_dir, output,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/pmb/helpers/run_core.py", line 403, in core
    check_return_code(args, code, log_message)
  File "/usr/lib/python3.12/site-packages/pmb/helpers/run_core.py", line 251, in check_return_code
    raise RuntimeError(f"Command failed (exit code ): " +
RuntimeError: Command failed (exit code 32): % sudo mount --bind /dev/sdb3 /home/s31bz/Documents/nyan-blaze/chroot_native/dev/installp3

From the looks of things, it seems the postmarketOS python script may be having issues with the installed python packages as well as some other issues that I haven’t troubleshot before.

Hmm, I wonder if it’s the aspects of Python on this oddball Nobara 39 install? Perhaps I’ll go give it a try on my pure Fedora 40 install that runs on my Framework. After rebooting the Nobara desktop (after running updates) it seems it’s still failing, and I’m a bit too lazy to dig in deep and see what could be wrong on this install.

While waiting for the process of installing to a new microsd card after fully updating the Fedora 40 Framework 13 (7840U, 48gb ram) I went ahead and unscrewed all the screws that clamp the keyboard deck and bottom half together.

Looks like someone was in here previously! An electrical-taped battery connector doesn’t seem like a safe sight to behold, but that could also explain why it seems this guy doesn’t have a functioning battery. As I got this system for free, and it’s quite flimsy, I’m not about to invest any amount of money in replacing the battery etc, so I’ll just repaste the ARM CPU for now and take out that bottom-right write protect screw.

Now that I’ve removed the write protect screw, let’s see if we can finally install postmarketOS edge to this chromebook, per the instructions on the postmarketOS site.

Sadly, it looks to be that even after updating pmbootstrap and trying to install to an sdcard again on the Fedora 40 laptop, it’s a failure, possibly stemming from more python issues.

Arch Linux on the HP "DRAGONAIR" Chromebook x360 14c

/

Greetings again! Back in the new year with another cheap Chromebook I’ve “Chrultrabook’d” so to speak. Got rid of ChromeOS and the Google bootloader, then installed Arch Linux the easy way on this guy.

Having already gone through the removal of write protect documented here and having already installed the latest firmware from MrChromebox per his script, I’ve reconnected the battery and run through the “archinstall” install script for Arch Linux.

As I’m apparently not able to install the “asciinema” package during the “archinstall” script’s installation procedure due to some python errors, I’ll share this short recording of the initial part of the automated install process. Yes, call me lazy for using “archinstall” but it sure beats the hell out of constantly triple-checking whether I’ve gone through the same steps over and over. I’m a Fedora user at heart, but I’ll be testing some packages from the AUR on this converted ultrabook on and off.

Shame about the eMMC being there and not having a populated NVMe slot on this HP “DRAGONAIR” board though, otherwise I’d throw one of my spare tester NVMe drives in.

Next, I went ahead and ran through the automated scripts to enable proper keyboard button mapping, and to make sure Audio was functioning properly, then rebooted.

After that, I made sure to install the rua (linked) AUR helper to install packages through a safe Rust interface from the AUR. Two such packages I’m interested in are the Jottacloud backup utility and Tailscale…..however Tailscale is an official Arch package now apparently.

Last thing I did was gather some of the aforementioned packages as well as BIOS/mainboard info for others that are looking to turn this Chromebook into a Linux-native ultrabook.

hp dragonair with arch linux