fidzu : Operating Systems

Virtually all laptop speakers suck. It's the one area where even really expensive laptops tend to fall on their ass, leaving users with a tinny, harsh, and hollow sound experience. While you can't exactly overcome physics - laptop speakers are necessarily small and thus just cannot ever sound as good as proper speakers - there's a lot you can do with proper tuning and software magic. If you're a desktop Linux user, you actually already possess all the plumbing needed to fix your audio; it's just not exposed to you in any way. Luckily, an application called EasyEffects allows you to actually make use of desktop Linux' advanced audio features to massively improve the sound quality of your laptop's speakers. EasyEffects' own description on its GitHub page doesn't really explain what it does or what it's capable of, so here's the description from Wikipedia instead. EasyEffects uses PipeWire to process incoming and outgoing audio streams independently and can apply various sound effects in the form of plug-ins made by different developer teams such as Calf Studio Gear, MDA.LV2 and GStreamer. All plugins have their own presets and can be applicable inside the suite rather than having to use a different mixer or executing a script from the command line. Available output effects are limiter, auto volume, compressor of dynamic range, filter, 30 bands parametric equalizer, bass enhancer, exciter, reverbation, crossfeed, delay, maximizer and spectrum analyzer. Available input effects are WebRTC, limiter, compressor, filter, equalizer, de-esser, reverbation, pitch shift and spectrum analyzer. ↫ EasEffects' Wikipedia page None of this matters, and you can forget everything from these two paragraphs. What matters is that using EasyEffects, you can tune the audio coming out of your speakers to make them sound a lot better. The few laptops on the market that do have decent audio - MacBooks, some Dell XPS laptops, and surely a few more - aren't magically defying physics. While they probably do have objectively higher-quality speakers, the main difference between those laptops and laptops with crappy-sounding speakers is that the former come with built-in tuning from the factory to make them sound much better than they would without any software trickery. If you know your way around audio, you can very much use EasyEffects and tune your laptop speakers from scratch to massively improve how they sound. However, that requires time, experience, knowledge, and expertise that most people lack, including myself. Lucky for us, though, there are countless downloadable presets out there for EasyEffects designed specifically to make laptops sound better. In an ideal world, you'd pick a preset created specifically for your laptop make and model, but odds are you won't find one, so for most laptops you'll have to settle for a generic preset that tries to do its best. I've long settled on the Advanced Auto Gain.json preset from JackHack96, which greatly improves the audio performance on any laptops I've tried it on, but of course, there's countless other presets for you to try to see if there's anything that suits your particular laptop and ears better. Getting all of this up and running is really easy. EasyEffects is most likely packaged by your Linux distribution, and the latest version is always available as a Flatpak from Flathub. Download the preset(s) you want to try, copy them either to ~/.config/easyeffects (if you use your distribution's package) or to ~/.var/app/com.github.wwmm.easyeffects/data/easyeffects/output/ (if you use the Flatpak version). They'll show up right away in the Presets tab in EasyEffects, ready to be turned on and off whenever you want, making it very easy to compare and contrast to find the one you like best. EasyEffects can live in your system tray giving you easy access to your presets without having to open the main window, and it can be set to start automatically at boot. EasyEffects can also be turned on and off on the fly. There's obvious downsides to all of this, too, of course. First, since you're most likely going to be using a generic preset not specifically crafted for your laptop, there's no guarantee the results will be positive for you. Second, not every preset is ideal for every type of audio. Most of my audio consists of YouTube videos with mostly speech; if you listen mostly to music, different presets may yield better results. Third, audio quality is deeply subjective, and what sounds good to my ears may sound like total garbage to yours. Fourth, EasyEffects does take up a tiny fraction of CPU power (I'm talking 0.1-0.2% according to KDE's System Monitor), but I have never seen it have any noticeable performance impact on anything. Even the generic preset I use makes such a massive difference for me on every laptop I've ever tried it on, that I've become convinced EasyEffects and a few of the generic presets should be installed by default by any desktop-oriented Linux distribution. On top of that, Linux laptops OEMs like System76, Nova Custom, Star Labs, and so on, should really take the time to create proper presets for their laptops to improve their sound quality out of the box. I feel like if you're already designing and selling laptops, you probably also have the skills and means to create a decent preset. In fact, I'd take it a step further and urge desktop environments like KDE and GNOME to properly integrate EasyEffects into their sound settings. They shouldn't include the entire application and its user interface, but should make it so that you can configure and manage presets right from the sound settings panels, and switch between presets from their volume applets (as well as turn it off entirely, of course). This would leave the full EasyEffects application for people who need more control, manual tuning, and more advanced features. There's absolutely no reason why speakers on Linux laptops should sound tinny, harsh, and hollow. The Linux desktop has all the technologies and features built right in to make speakers sound much better than they do without any tuning,

27 Aug 2026 8:18pm GMT

Built on a 2 nanometer technology node, the processor's design will contain 11 high-performance cores operating at more than 5.7 GHz, AI inference accelerators for in-transaction fraud detection, a dedicated on-chip data processing unit for I/O acceleration, and a large cache architecture for demanding enterprise workloads. The chip is architected to not contain separate Arm and IBM cores: each processor core can natively execute Arm and IBM Z, or Arm and LinuxONE, instructions concurrently while prioritizing the platform's established performance, security, encryption, and availability characteristics. IBM Z and LinuxONE platforms are capable of scaling to hundreds of cores and tens of terabytes of memory. ↫ IBM press release IBM is still doing some amazing chip architecture design. ServeTheHome has more details of how this works: A key choice here is that IBM implemented AArch64 in full hardware rather than through translation. This design uses a little-endian Arm implementation alongside big-endian z/Architecture, with AArch64 v9.3, SVE and SVE2 support, and 2,792 implemented AArch64 instructions. IBM also claims Arm SystemReady compliance, which matters for how much off-the-shelf Arm software this core can absorb. This is absolutely crazy technology. Arm software sees a native Arm processor. Arm runs unmodified, out-of-the-box, and onto a standard Arm platform. IBM said the 2792 AArch64 instructions are more than twice the Z instructions. IBM made a funny quip about "reduced" in RISC. ↫ Patrick Kennedy at ServeTheHome This is bonkers technology. We can only dream of this ever serving a home.

27 Aug 2026 2:30pm GMT

It's always a special day on OSNews when Haiku has a new release. While OSNews was founded in 1997, it wasn't until 2001, when Eugenia took over and relaunched the site, that we really got going. Eugenia came from BeNews, a popular BeOS news website, which shut down in the wake of Be, Inc's infamous "focus shift" away from BeOS as a general purpose desktop operating system. BeOS continues to have a special place on OSNews ever since. Today marks the release of Haiku R1/beta6, the first official Haiku release in two years. As such, this new beta covers a monumental amount of progress since beta5, progress I've reported on diligently. The highlights of this new beta include a port of Firefox (including branding) and many of its forks, much improve support for Qemu, a new memory allocated largely based on the one from OpenBSD, and improved support for various filesystems. Of course, there's a massive list of performance improvements, memory management changes, as well as a truly massive number of new application ports. It's important to note, as I usually do, that while these Haiku beta releases serve as patches of calm in rough seas, Haiku is generally stable and capable enough that using the project's nightly releases is usually a totally acceptable way of installing and running the operating system. If you're not comfortable running nightly releases, however, and haven't tried Haiku since the previous beta, you're in for a massive overall improvement. Everybody loves Haiku.

27 Aug 2026 11:31am GMT

Right on schedule - as always - there's a new Genode OS Framework release, version 26.08. The highlights of Genode 26.08 are VirtualBox 7, improved PC performance of our custom microkernel, the new ability to transparently reconfigure virtual file systems, revised timing and timeout handling, and a Linux 6.18.19 device-driver environment for ARM. Furthermore, the first version of a Goa-based SDK has become natively available for Sculpt OS. ↫ Release announcement on the Genode website The release announcement linked above is a mere quick overview; if you want all the possible details you could want, the release notes got you covered.

25 Aug 2026 9:13pm GMT

Motif is great, I love how it looks and feels, and I want it to be actively maintained. I want a healthy ecosystem of Motif applications and even window managers and desktop environments, so I can run a real Motif environment. Sadly, while Motif has been open source for a while, the project itself stalled years ago, with little to no activity from anyone involved. That may be changing, as a number of developers decided to take matters into their own hands last year. This fork of Motif was born of a desire to keep Motif (and other X11 technologies) alive and well. The original upstream Sourceforge project hasn't had any activity in over two years, none of the project admins have been active for at least that amount of time, the official bug tracker has disappeared into the void; and the user forum was closed way back in 2017. Sadly, it appears that the original upstream has abandoned the project. I've incorporated some fixes from upstream that have laid dormant for years, a few others from Gentoo, and made a few improvements of my own. I intend to maintain this fork, and in doing so advocate for the continued use of the user interface toolkit that defined an era, and influenced many of the user interfaces that came after it. ↫ Tim Hentenaar at the Motif fork's GitHub page Some of the people involved are people I know online, so I have a bit of faith in this fork being able to stand the test of time, but of course, managing a complex project like this is hard, so who knows how long the enthusiasm remains. Still, this fork has seen five releases since its inception a little over a year ago, which seems promising. It may seem weird for some to have a love for Motif, but I'm the kind of person who installs weird, outdated corporate and industrial software I don't understand on my HP c8000 dual PA-RISC workstation running HP-UX just to enjoy the Motif interfaces they sometimes ship. We all have our quirks. From my experiences talking to people online, I know there's actually a rather solid number of people like me, and I hope that at some point the developers in this group can gain enough critical mass to build something like a basic Linux distribution or desktop environment using the disparate, actively-maintained Motif projects out there that yes, still exist. It's a long shot, but in today's computing landscape, where more and more people feel uncomfortable with "modern" software, I really feel like there's a niche for something like this to exist. A really small niche, surely, but a niche all the same.

24 Aug 2026 8:15pm GMT

AROS, the open source Amiga OS-compatible operating system, now has images available for the Raspberry Pi 3 (although some people state it also works on the Pi 4), in both 32bit and 64bit versions. According to the AROS team, they are quite stable, but not yet complete, so do know what you're getting into. Dan Wood posted a YouTube video about these new images, providing much more insight into how well they work if you want more insight into how well they work. The images are, of course, the basic AROS operating system, so expect a rather barebones experience. If you're used to some of the AROS distributions for x86, which come loaded with software and customisations, these images will feel quite bare to you. It's going to take some time to port over all of these applications and customisations to the ARM version of AROS, but if and once that happens, I expect more complete images to appear as well. Great news for AROS and the Amiga community in general.

24 Aug 2026 7:57pm GMT

Ah, Japan's TRON project - every few years someone discovers it anew and it bubbles back up the surface, and deservedly so, as it's an incredibly interesting operating system project that, like so many others, deserved a better fate. There's a version of computing history where the desktop OS that won wasn't Windows. Not because the alternative was Unix-based or because Apple pulled off something different, but because an operating system designed at the University of Tokyo in 1984 was ambitious enough to try to replace the file system with a hypermedia document model, run on a custom Japanese CPU architecture, and encode 1.5 million characters, only to have a US trade report single it out as an unfair trade barrier in 1989. That project was TRON (The Real-time Operating system Nucleus), a real, government-backed Japanese computing initiative whose desktop variant, BTRON, was named in a US trade barrier report and effectively killed before it could reach schools nationwide. Meanwhile, its embedded counterpart, ITRON, quietly became one of the most deployed operating systems in history. TRON's history has since attracted some genuinely wild conspiracy theories, including one claiming that Japan Airlines Flight 123 was deliberately crashed in order to target the TRON developers on board, despite there being no evidence that any TRON developers were even on the flight. But the strangest part of the story isn't even a conspiracy theory: BTRON's hypermedia desktop was decades ahead of what the market could support, and SoftBank founder Masayoshi Son may have helped sink it from the inside. ↫ Adam Conway at XDA The most interesting part of TRON for me was the different ways it treated files and documents compared to other operating systems. Instead of focusing on applications and files as the core interaction points for users, it focused on the document. While most operating systems associate specific files with specific applications, TRON associated individual components of documents with individual handlers. If you want to edit a Word document today, you open Word and do all your editing work inside Word, whether you're editing blocks of text or an image, or you open entirely different applications when Word's capabilities for a certain component in a document are too limited. In TRON, you'd open a document, and only once you wanted to edit specific components did it "open" an "application" to perform the editing, without actually leaving the document in question. Want to edit an image inside your document? In most operating systems, you'd have to open a separate image editor, load the relevant image file into it, make your edits, save the image file, and then paste said edited image file back into your document. There's a considerable amount of overhead here that shouldn't really exist; a computer is more than smart enough to open up just the editing controls from a different application if need be. In our current paradigm, applications often "solve" this by adding ever more features and controls and tools to cover every possible object or component you might have to deal with, but that just makes applications more complex, more bloated, and more difficult to use. TRON's approach has been tried in a variety of times and places, but it never caught on. My personal pet theory is that the application-first model is far better at wealth extraction and concentration than TRON's model, and as such, that's what we ended up with. If a user's document and all of its constituent parts are tied to and wrapped up into a single application from a single vendor, it's much easier to control said user and extract wealth from them than when that user can just pick and choose whatever handler they want to use for whatever object they happen to run into in a document, without having to open tons of different applications and move, copy, and paste stuff all the time. In fact, this is also why consistency in user interface design is now all but dead; application developers and vendors use their own weird, non-standard, custom user interfaces for branding purposes. Sticking to a platform's standards and conventions makes it harder to stand out and put your "brand" in people's faces. But I digress. Regardless, I'm not sure if all the stories about the US trying to bury TRON have any real value to them, as even the article itself notes (undoing its own clickbaity headline) that the project already seemed to be in dire straights even before it got a buried mention in some trade document. On top of that, ITRON, the embedded TRON variant, survived and thrives to this very day, powering untold numbers of devices. It seems to have done quite well for itself, supposed US government intervention or no. This article by Steven J. Searle also takes a look at the workstation-focused variant of TRON.

24 Aug 2026 3:29pm GMT

So that is the whole pipeline exercised end-to-end. GrandSlam authenticates the Apple Account and obtains the IDS delegate. authenticateDS and id-register turn the Linux process into a registered Apple messaging identity. The Friends sequence attaches that identity to the existing accepted relationship. A missing-key SubscribeAndFetch makes the sharing device deliver its current P-224 key over APNs/IDS, inside a sender-verified P-256 NGM envelope. A second SearchParty fetch returns the encrypted report, and the P-224 key opens it locally. So yeah, in one sentence: authenticate to Apple's private services, register the Linux machine as an IDS client, receive the existing Find My share key, and use it to fetch and decrypt a consented friend's latest location. ↫ Zerotistic I wonder if it would be possible to build a proper third-party client for Apple's Find My network like this, or if it would be trivial for the company to block it. I'm fairly sure quite a few people would love to be able to keep using Find My when moving away from Apple's operating systems.

24 Aug 2026 12:10pm GMT

When I wrote about using Windows 11 for a month as part of the ongoing OSNews fundraiser (keep donating to get me to do the same for macOS!), one of the things I mentioned was that "the modern desktop context menu has its own classic Win32 context menu". This is, in fact, a long-standing complaint I've repeatedly used as the perfect example of just how chaotic and low-quality Windows has become. Thankfully, and naturally I fully attribute this to my repeated complaints (*), Microsoft has been working on a brand new, faster, configurable context menu, and Neowin actually reviewed it. If you ask me, this revamped context menu addresses just about the biggest problem users had with the one in Windows 11, and that is the need to click through more buttons than necessary to do simple things like renaming a file or opening its properties. That problem is now basically gone. I have no issues with the new design. It looks modern, it feels more consistent with the rest of Windows, and even though all the new sections can still make it look a little busy, you now have the option to make it as simple or as button-packed as you want. That should cover most use cases and preferences well. I'd even say that when the new context menu becomes available to everyone, my guide on how to bring back the classic context menu might become obsolete. ↫ Ivan Jenic at Neowin The biggest reason I'm linking to this is not because I care about whatever monster of a context menu Windows users are having to deal with. No, I'm only linking to this because I never in my life imagined I'd be linking to a review of a context menu. I mean, at least it's not the chess application icon. That would be embarrassing. I get a perverse sense of joy out of this.

19 Aug 2026 9:58pm GMT

A great and concise history of the run-up to MS-DOS 2.0. Yet, there was a nagging feeling that a single-tasking CP/M clone was inadequate for the new generation of personal computers. Digital Research released multi-user, multitasking MP/M-86 in September 1981 and announced the single‑user multitasking Concurrent CP/M in early 1982. In response, Microsoft came up with a plan for tiered approach to its operating systems: single-user/single-tasking MS-DOS at the bottom; multi-user/multitasking XENIX at the top; and in the middle, something called XEDOS: a single-user version of XENIX. This "pyramid of upward-compatible operating systems" was announced in a Byte Magazine editorial in January 1982. ↫ Nemanja Trifunovic I've always found this tiered approach fascinating, and the world surely would've looked quite different had Microsoft been able to make it work. I doubt Windows NT would ever have existed, and most of the world would probably be running a XENIX-based Windows today (all else being equal, which is of course unlikely and silly). Regardless, MS-DOS 2.0 contained a few UNIX-like utilities to deal with its brand new support for directory trees and other new features, and even had a /dev directory.

18 Aug 2026 9:59am GMT

If you thought pervert glasses weren't bad enough, Apple is taking it up a notch by adding cameras to its AirPods. Apple is working on camera-equipped AirPods that appear to be nearly ready to launch, based on a video MacRumors found in the macOS Tahoe 26.7 release candidate. In a short demo, a man holds a book up so the camera in the AirPods can see the title. "With Visual Intelligence, your world becomes savable. See something you like? Just ask me to save it for later," says the voiceover text. ↫ Juli Clover at MacRumors AirPods are tiny. I've seen people use them at the gym. I've seen them on playgrounds. I've seen them around swimming pools. People use them at the beach. They're used at schools. In locker rooms. Tiny cameras in tiny AirPods that can photograph anything in front of the user are a pervert's wet dream. Abusers are going to love this. Why wear bulky glasses anyone can see and try to demand you take off, when you can wear tiny AirPods that have already been fully normalised in society? Was there not a single woman or parent on the team that made this? All over the United States, people are destroying Flock surveillance cameras. More and more communities are rising up and demanding these things removed from their streets and neighbourhoods. The awareness of just how pervasive mass government surveillance has become is growing, and Silicon Valley's complicity is not exactly a secret. And in this climate of rapidly growing concern and anger, Apple is going to add tiny cameras to its tiny AirPods. Was there not a single person of colour or protester on the team that made this? How detached from reality do you have to be to greenlight something like this? Does anyone - regardless of skin colour, gender, or political leaning - want even more cameras around them?

18 Aug 2026 9:41am GMT

I was around when Quake was launched, but I was entirely unaware of this story. By June 1996, after three years of hard work, id Software had completed their next title, Quake. As for their previous title, they were going to release both a shareware version and a full version of their game. Since it used a mere 22 MiB of storage, people at id Software had the idea of leveraging the remaining capacity of a CD-ROM. Why not include encrypted versions of the full id catalogue of games? Not only this would cut out the middlemen, it would give instant access to gamers with a simple phone call and a credit card. The concept was implemented. The CD was announced on July 3, 1996 and released on August 30th. The hacker group GNOMON released Quakecrk.zip only 39 days later. The archive contained QCRACK.EXE, a tool allowing to decrypt every single game on the CD-ROM. ↫ Fabien Sanglard The system id employed turned out to be incredibly primitive and simple, and hackers found out quite easily that the system required no secret sauce from id at all - the code you'd get over the phone contained no secret, and all the validation program on the disk did was check to ensure the code received over the phone matched the code generated by the disk. No wonder it took them only 39 days to crack this.

18 Aug 2026 9:24am GMT

Earlier this year, Natalie Vock made a splash with a set of patches to the Linux kernel that greatly increased performance on AMD GPUs with lower amounts of VRAM. With that work now accepted by upstream, Vock decided to turn their attention to another interesting problem: what if you run out of VRAM, and how can we improve performance when we do? Regardless, what I hope this blogpost can demonstrate is that even if you end up with some memory evicted to system RAM, the slowdown can be manageable. There's measures that drivers (particularly, the kernel driver) can take to make overcommit work as fast as possible, and even applications can do their part in coordinating with the driver stack to mitigate the effects of their memory being evicted. With everything in place, VRAM overcommit isn't really as big of a deal as one may think it is at first sight. ↫ Natalie Vock The work Vock has done has already been in SteamOS for a while, and they're currently in the process of upstreaming it to the vanilla kernel as well. Since this is a complex set of patches and changes, this may take a while, and as such, they've prepared custom kernel and Mesa branches for adventurous users. Do note that these branches won't be maintained much, and are entirely experimental, not as well-tested as the SteamOS kernel, and probably won't yield the same performance improvements. Still, this is the kind of work that has a material impact for users. Not everyone has a 16GB monster GPU, especially not today with supply chains ravaged and ruined by slopmakers, so it's great to see the Linux world working to improve performance for everyone, not just the wealthy few.

18 Aug 2026 9:13am GMT

The Touch Bar arrived in 2016 seemingly already pre-doomed, on a generation of machines that had a "we've run out of ideas" smell all around them. The arrow keys were reshaped, the keyboard got a slimming down, and even the beloved MagSafe wasn't, in fact, safe. All of these changes would prove unpopular and get reverted in time, and the axe would eventually come for the Touch Bar, too. With an enormous benefit of hindsight, a decade after its arrival, and on the (rumored) eve of fully multitouch MacBooks, I wanted to look critically at the Touch Bar in more detail. I put a spicy title above this post, and while I'm not sure I can answer it in the affirmative, I feel I got surprisingly close to that. ↫ Marcin Wichary I have never spent this much reading about and pondering a technology seemingly nobody liked and that I never really used. I still think there's merit to the idea of screen on a keyboard, but only if the screens are integrated into the individual keys (as some products have tried over the years). Of course, this would also be astronomically expensive, delicate, and virtually impossible to repair, so I'm not sure something like that can be reasonably made at an affordable price.

18 Aug 2026 8:48am GMT

Version 7.2 of the Linux kernel has been released. Significant features in this release include common attributes support in the bpf()vsystem call, cache-aware load balancing for the CPU scheduler, large-folio support in the Btrfs filesystem, further swap subsystem improvements, improvements to the Landlock security module, support for block devices with inline encryption hardware via the dm-inlinecrypt device-mapper target, and much more. ↫ corbet at LWN.net If you run Linux, you'll get it sooner or later.

17 Aug 2026 1:11pm GMT

We talked about the latest release of Delphi a few days ago, and that brought me to Hans Otten's website. This site is about my experience with the Wirth school of languages, based on the ideas and implementations of Prof Niklaus Wirth, Kenneth Bowles, Per Brinch Hansen, colleagues, and their students. And my experience with the various variants, from the P2 and P4 compilers originating in Zürich ETH, via UCSD Pascal P-System to the Borland compilers and Modula and Oberon systems. All applicable to small computers and device control. On this website you will find information on Pascal for small machines, like Wirth compilers, the UCSD Pascal system, many scanned books and other files on UCSD Pascal, Pascal on MSX and CP/M, Delphi programming on PC, Freepascal and Lazarus on Windows and Raspberry Pi, Oberon systems. Many sources of early Pascal compilers! And last but not least my Pascal-M system! ↫ Hans Otten If you're into Pascal and its related languages and technologies, this is a treasure trove of information.

17 Aug 2026 1:05pm GMT