Linux Fu: The Bluetooth Regression

There’s a line in a [Weird Al] (no relation) song that says, “I upgrade my system at least twice a day…” I know how that is. I primarily use a rolling distro, OpenSuse Tumbleweed, and if I’m having a problem that I’m too lazy to run down, it is extremely tempting to do an upgrade and see if it just happens to fix the problem.

Of course, the problem is often caused by a previous upgrade. Recently, I’ve been having a lot of trouble with the NVIDIA proprietary drivers, so I updated them yet again. After a huge amount of effort to sort out the video problems, I found that the latest kernel didn’t like my MediaTek Bluetooth adapter, which is built into the motherboard’s WiFi chipset.

This post isn’t about how to fix your Bluetooth problem. You probably don’t have the same setup I do, and even if you do, it will be sorted out in a week or two anyway. But how I temporarily fixed this issue is worth documenting. The details are going to apply to Tumbleweed and this particular adapter, but the general approach should work anywhere with any sort of kernel module problem.

My Own Fault

Part of my problem is my own fault, of course. I have a complex disk setup and do not use the recommended btrfs root file system. That means I can’t do the snapshot thing where I can just undo a bad upgrade. If I did, then sure, I should just roll back and wait for an upstream fix.

I do have “normal” backups, but they are not always totally up to date. Worse, I have found that for things like NVIDIA, the user stuff and the kernel module stuff have to match up. That makes it very hard to roll back a kernel with older modules. The modules themselves live with the kernel, but the user space stuff gets pushed out. Or, if you uninstall things, it uninstalls it for all kernels.

Truthfully, NVIDIA and others like that should keep all the user space stuff in a kernel-specific place, and then symlink it at boot to /usr/bin or wherever. But they don’t. In the end, I didn’t want to go through the trouble of rolling things back and decided to push ahead.

Continue reading “Linux Fu: The Bluetooth Regression”

Power From Gravity

Gravity batteries aren’t exactly a new idea. You can store energy by lifting something heavy, converting kinetic energy into potential energy. To get it back, you let the mass fall and convert that motion to electricity. [Valeriamayara22] shows how to build a working demonstration model of such a system.

This isn’t free energy. Something has to lift the weight. In this case, the height is 1.8 meters, and the mass is 15.65 kg. Even so, the model achieves 13 W peak output and 58% efficiency, according to the post. Reportedly, it takes 394 drops of the weight to fully charge an iPhone 16, so this isn’t a practical project, but it does show how a gravity battery works. One nice thing is that the system stores as much energy on its 1,000,000 th charge as it does on the first one, especially if you keep the chain lubricated. Try that with a chemical battery.

The mechanical part uses a bicycle chain and some sprockets. There is a battery to even things out since, like wind power, when you make energy with a mechanical battery, you either use it now or lose it.

The cost of the build is about $400, and there’s a GitHub repo with all the files if you want to take your own shot at it. The energy efficiency number references the potential energy stored versus the energy produced. Obviously, if you are using some other energy source to lift the weight, that’s another calculation.

As you might expect, a practical system like this can be very large.

Spacelab’s Mitra 125 MS

[Ken Shirriff] does some of the most interesting teardowns. This time, he’s looking at a French-built minicomputer called the Mitra 125 MS from around 1980. In particular, it was the computer inside Spacelab, a European lab that could fit in the back of the Space Shuttle.

As you might expect, the computer doesn’t contain a microprocessor. Instead, it is a series of cards and, in this post, [Ken’s] looking at the ALU that allows the computer to perform math operations.

Continue reading “Spacelab’s Mitra 125 MS”

Hackaday Podcast Episode 370: Softer Cyberdecks, A Simulated Clutch, And An Overstuffed Mailbox

With Elliot back from Hackaday Europe, he and Al Williams had a lot to talk about with two weeks of Hackaday posts to catch up on. Not to mention the mailbag was overflowing.

This week, the guys look at girlie cyberdecks, a 3D printed circuit board, and talk electric motorcycles. Is 3D printing safe? Want an accurate moon on your desk? How about modern punch cards? All of that and much more were on the menu this week.

For the can’t miss articles, Zoe Skyforest weighs in on file sharing via LAN while Al Williams talks about the surprising state-of-the-art in vacuum tube tech right before their end.

What do you think? Leave us a comment or record something and send it to our mailbag.

Download a copy of the podcast with an MP3 this week in glorious pink and purple.

Continue reading “Hackaday Podcast Episode 370: Softer Cyberdecks, A Simulated Clutch, And An Overstuffed Mailbox”

Tech In Plain Sight: The Mechanics Of String Trimmers

My old friend Jeff was always vocally upset that he didn’t come up with the idea of a string trimmer, commonly known as a Weed Eater or Weed Whacker. On the one hand, the idea is totally simple: spin some nylon line and cut grass and other relatively soft things. But, it turns out, that making the device actually usable requires a little bit of mechanical engineering.

Of course, the noisy part is a motor. The motor — driven by an engine, a battery, or a power cord — spins a flexible nylon line fast enough that the line becomes rigid from centrifugal force. That’s not the important part.

The humble spool at the bottom of the trimmer is where decades of mechanical engineering, questionable patents, consumer frustration, and genuine cleverness all meet. The earliest string trimmers were primitive. [George Ballas], who patented the Weed Eater in the early 1970s, reportedly got the idea from the rotating brushes in a car wash. Attach flexible cords to a spinning head, and they become cutting tools. In fact, the prototype used a tin can for the head. Elegant. But once the line wears down — which it does constantly — you need a way to expose fresh line. That turns out to be harder than it sounds.

The Simplest System

The easiest approach is fixed-length line. Some trimmers still work this way. You cut short pieces of heavy line (or buy it precut) and insert them into holes in the head. No spool. No springs. No moving parts.

These systems are rugged and are popular on commercial units designed to survive abuse. They also work well with thicker lines or even plastic blades. But they are annoying because every time the line wears out, you stop working and manually replace it. Spool-based systems became dominant very quickly.

The basic spool idea is straightforward enough. Wind a long nylon filament onto a reel. Some reels have two sections to feed line out on two sides of the rotating head. As the line wears away, feed out more line from the spool. But how do you do that while the thing is spinning at several thousand RPM?

Continue reading “Tech In Plain Sight: The Mechanics Of String Trimmers”

Spy Tech: A Quiet Radio For Spies

Normally, when you think of a radio transmitter, you want the strongest signal and range. But if your radio operator is secretly operating as a spy, broadcasting their position isn’t a feature; it is a liability. This fact didn’t escape World War II radio designers.

In late 1942, the British realized they needed a way for Special Operation Executive agents, resistance members, and other friendly forces to communicate with an aircraft without attracting undue attention. Two engineers from the Royal Corps of Signals developed a pair of transceivers — the S-Phone — operating around 380 MHz just for this purpose. Frequencies this high were unusual at the time, which further deterred enemy detection.

The output power was below 200 mW, and the ground equipment consisted of a dipole strapped to the operator. No transistors, so with rechargable batteries, the rig weighed about fifteen pounds and reused some parts of a paratrooper radio, Wireless Set Number 37. The other side of the connection was installed in an airplane.

Continue reading “Spy Tech: A Quiet Radio For Spies”

The 8-bit Web Server

Even [maurycyz] doesn’t think it is a good idea, but it is possible to use an AVR 8-bit CPU to serve web pages. Of course, it is a vastly simplified web server, but it does serve pages — OK, technically just one page — to the public Internet.

Working backward, it is fairly easy to get the microcontroller to note an HTTP request and then simply spit out a prerecorded HTTP response to provide the page. The hard part is connecting the little processor to the network. The server is dead simple, just a CPU and a scant number of components like filter caps and LEDs. The trick is to use SLIP, an ancient protocol used to connect dial-up modem terminals to the network.

Linux supports SLIP, so the MCU connects to a Linux computer via SLIP. Then the Linux computer uses WireGuard to network with the remote web server that serves [maurycyz’s] site. The SLIP implementation assumes that IP packets aren’t fragmented, which is normally true these days. TCP was a bit more complicated since you have to track the connection state and possibly re-transmit lost packets. Still, nothing the AVR with 8 K of RAM and 64 K of flash can’t handle.

Practical? No. Cool? Sort of. Funny that a disposable vape has more CPU power. Of course, something like an ESP32 is an obvious choice.