EtherHam

Amateur Radio Over Internet

Random Wire 147: Hodgepodge from the hospital room

September 5, 2025: Topics in RW 147 include: a digital interface; trying to install Debian on a Chromebook; thoughts on MX Linux; M17 ideas; the M17 Net on Kansas City Wide; and some HF antennas.

AllStar node 578495 in a modular Raspberry Pi Zero case by Argon 40

Top of mind

Orange-colored content divider

Project: Debian and AllStarLink on a Chromebook

This is an in-progress report, not a summary of a completed project. And I don’t know that it’s going to work, but that’s the very nature of experimentation, isn’t it.

I picked up a couple of “grade B” Lenovo 300e Chromebooks with the intention of converting at least one of them to Debian 12 and installing AllStarLink on it. One was barely grade B, with one scratch on the keyboard. The other was closer to grade C. Both booted up to ChromeOS and seem mechanically sound, with working screens, keyboards, and mouse pads.

So far, the biggest challenges I’ve run into are:

  • There were three generations of the 300e, each called the 300e. One had an ARM CPU. Fortunately, I bought the MKII (mark two) model that runs on Intel chips, so Debian should run fine once I defeat the Chromebook safeguards.

  • Getting the bottom off of these laptops is proving to be quite a challenge. One of the ways to get around the Chromebook protections is to remove the bottom and disconnect the battery, then boot from a USB stick with the Debian image on it. I found a resource that speaks to removing the bottom cover of the laptop…but what I discovered is it is the keyboard that gets removed. I didn’t see that method in my research. They keyboard pops out easily with a couple of spudgers.

Why, oh why, would one do this? I know it can be done because I’ve done it with a few old Windows laptops. And I’ve seen Chromebooks converted to various Linux flavors available on eBay. So clearly, it can be done, but that doesn’t mean I can do it. Trying is enjoyable, even if I don’t succeed in defeating the Chromebook safeguards. I’ll try to ChromeOS with Debian 12. From there, it’s just a few more commands to install AllStarLink. What this means is for $60, I could have a working radio-less AllStar node with an attached keyboard and screen. Add in a microphone interface from AllScan.info and it would be a complete, working AllStar node…with a few scratches and scrapes because these are grade B used machines.

Do I need another node? Absolutely not. But I do enjoy repurposing old tech, and Chromebooks tend to be built pretty tough, so something like this could be a great choice for a radio amateur who doesn’t want to create a node made up of a whole bunch of individual pieces.

More on this as it progresses.

Orange-colored content divider

Would AllStarLink 3 work with MX Linux?

I’ve been reading great things about MX Linux, especially on older or resource-limited platforms. Would it, could it work with AllStarLink 3?

First, what is MX Linux?

It is a midweight desktop environment that aims to be fast and low-resource, while still being attractive and user-friendly…It supports a large range of hardware from older laptops to modern desktops. Available in Standard Debian Stable and “Advanced Hardware Support” enabled versions.

MX Linux rocks an XFCE desktop interface and is based on Debian Linux. I find myself wondering: has anyone tried MX Linux as the base for an AllStarLink 3 installation? This should be possible, although I might have to compile the packages needed for ASL 3.

As an aside for Raspberry Pi users, MX Linux also offers a version for Raspberry Pi 4, 400, and 5: MX-23.6_rpi_respin, a respin of Raspberry Pi OS with a MX setup and tool set, suitable for Pi4, Pi400, and Pi5 hardware.” MX Linux appears to be based on kernel version 6.1 which is the version Debian 12 Bookworm is built on.

Why even consider doing this? Because with a limited platform, a stripped down (presumably faster) operating system should make ASL 3 run even better. It might also allow older, limited hardware to successfully run ASL 3.

I found some attractive-sounding attributes of MX Linux in the MX Linux Facebook group, including these points:

  • It has multiple ways of running live, including with persistence. With a fast USB 3 drive, it’s almost as fast as installed.

  • Although it uses sysvinit as the initialisation service, it can optionally boot with systemd, if so desired.

  • It has the ability to run live from USB, make changes, then remaster so those changes are now part of the USB.

  • The MX Snapshot tool can be used for backing up a running system, or to create a new ISO for distribution to others.

  • It has the ability to be tested live, have additional software installed, be configured, then have those changes carried over to the install.

  • In addition to the software available in the Debian repositories, it has other curated software that can be installed in the MX Test Repo.

  • It has a range of simple tools to carry out tasks that would otherwise need to be done in a terminal.

  • It has a range of tools to help solve problems with things like non-working network or sound cards.

  • It is created and maintained by a team of developers who are Linux enthusiasts and who use MX Linux for their work and play.

My guess is that since MX Linux is based on Debian, it probably pulls some updates from standard Debian repositories. That gives me some confidence that ASL 3 would work with MX Linux.

Also, this message in the AllStarLink Community Forum by KX4ZU Tim in September 2024 provides even more confidence:

I have successfully installed ASL3 on LMDE (Linux Mint Debian Editions). LMDE aims to be as similar as possible to Linux Mint, but without using Ubuntu. The package base is provided by Debian instead. ASL3 also runs quite well on MX Linux.

I think this is worth experimenting with, plus I’d just like to try MX Linux and get familiar with it. This is an ongoing project that could also intersect with the Lenovo Chromebook experimentation mentioned above.

Orange-colored content divider

M17 meanderings

I could dedicate one of the two Lenovo Chromebooks to AllStar and use the other for M17. For M17, I’d probably try M17 Digital Voice.

I already set up an M17 reflector (using mrefd) on a cloud server in Seattle. You can see activity at http://m17pnw.net/#/ and the system dashboard at https://dvref.com/mrefd/m17-pnw.

I found a GitHub package that can link AllStar and M17. Since I’m interested in both systems (and I have an AllStar node in the cloud: https://kj7t.net) this looks particularly interesting. I like the idea of bridging AllStar and M17 as this might create more interest in M17 and help build community. Find it at https://github.com/juribeparada/MMDVM_CM/tree/master/USRP2M17.

Want to listen to M17 to see what the buzz is all about? You can do that in a browser with M17Web. I’ve not used this very much since I have bought M17 radios, built a hotspot, and stood up my own reflector, but the few times I tried it, it worked. Note that since M17 is relatively young, there may be relatively little traffic on M17. The example linked below connects to what is probably the most used reflector: M17-M17 C. Find M17Web at: https://m17project.org/2025/03/08/m17web-listen-to-m17-reflector-traffic-in-your-browser/.

Not new, but new to me, the M17 Florida Man Edition looks interesting: https://github.com/lwvmobile/m17-fme.

Orange-colored content divider

M17 Net on Kansas City Wide

While I’m with my wife in the hospital, I’m using DroidStar (the Windows version from pizzanbeer.net) to listen to the M17 Net on Saturday at noon Central.

To do that, I had to connect to reflector M17-KCW on Module A (source: https://www.facebook.com/share/1EchvHoXrq/). If I remember correctly (I rushed through this while at the hospital), here’s how to do that:

  • If you don’t already have a working instance of DroidStar, download it (already compiled) for Android or Windows from http://pizzanbeer.net/droidstar/ and install it.

  • Open DroidStar and add your callsign and your DMR ID number in Settings (if you are only going to use it for M17, you don’t need your Brandmeister password or your AllStarLink password).

  • If you don’t find M17-KCW in the list of reflectors available, update the list of hosts by going to Settings and scrolling down until you see the Update Hosts button. Click the button.

  • If you still don’t see it, you can add it manually in the Hosts tab: M17 M17-KCW 172.234.217.28 17000

  • Then back on the Main tab, select M17 as the mode, M17-KCW for the reflector, and Module A for the module.

  • Click Connect.

Here are screenshots of DroidStar that illustrate some of these points:

Leave a Reply

Your email address will not be published. Required fields are marked *

Tom Salzer

Tom is an Extra Class amateur radio operator licensed in the United States as KJ7T

Tom Salzer KJ7T