Wine 11.18 and the Ongoing NTOSKRNL Effort

on

Wine 11.18 has been released, and the headline technical development in this iteration is the continued expansion of its NTOSKRNL implementation. For Linux administrators and developers evaluating Wine as a production or development tool for running Windows binaries, this release is a signal about the project's long-term architectural direction rather than a single feature drop. Understanding what NTOSKRNL represents within Wine's codebase helps frame why incremental releases like this one matter more than they might first appear.

What NTOSKRNL Means in Wine's Architecture

In a real Windows system, ntoskrnl.exe is the core of the operating system kernel — it handles process management, memory management, I/O scheduling, synchronization primitives, and the interface between user-mode applications and hardware drivers. Wine does not run on Windows, so it cannot simply pass through to a real Windows kernel. Instead, Wine implements its own userspace emulation of the NT kernel API surface. The component that does this is referred to as NTOSKRNL within Wine's source tree.

This is not a thin compatibility shim. A large fraction of the Windows API that applications call — from CreateProcess to VirtualAlloc to synchronization objects like mutexes and events — ultimately routes through kernel-level semantics. Wine's NTOSKRNL layer must faithfully reproduce those semantics on top of Linux's own kernel (the Linux kernel, not a Windows one), translating Windows expectations about process isolation, memory protection, and timing into Linux syscalls and data structures. The fidelity of this layer determines how broadly the Windows application ecosystem can be supported.

Why "Continuing to Build Out" Is the Key Phrase

The Phoronix coverage of Wine 11.18 describes the NTOSKRNL work as ongoing — "continues building out" — rather than as a completion or a major milestone. This distinction is important. It tells the reader that the Wine project is treating the NTOSKRNL layer as a long-term investment, adding coverage for kernel subsystems that were previously missing or only partially implemented, release by release.

For a sysadmin or developer, the practical implication is that the set of Windows applications that will run correctly under Wine is expanding in a gradual, non-linear fashion. There is no single version after which "all Windows apps work." Instead, each release that touches NTOSKRNL may unlock a class of applications that were previously blocked by a missing or incorrect kernel-level behavior. An application that calls a synchronization primitive not yet implemented in Wine's NTOSKRNL will fail or misbehave; a release that adds that primitive may make the application functional without any change to the application itself.

Practical Implications for Linux Environments

For teams that have standardized on Wine in CI pipelines, containerized build environments, or as a stopgap for Windows-only tooling, the NTOSKRNL work stream is the primary factor to watch when deciding whether to upgrade. A release that adds NTOSKRNL coverage may resolve a long-standing compatibility blocker that no amount of application-level workarounds could fix, because the gap is at the kernel emulation layer, not in a specific Win32 API wrapper.

The reverse is also true: because NTOSKRNL is a foundational layer, changes to it can have broad and subtle effects. An adjustment to how Wine's NTOSKRNL handles a particular kernel object may alter the behavior of many applications simultaneously, some of which were previously working. Teams that pin Wine versions in their infrastructure should be aware that upgrading across a release with significant NTOSKRNL changes carries a wider regression surface than a release that only touches a specific DLL wrapper.

Wine 11.18 does not announce a specific new feature or a named application that now runs. Its significance is structural: the project is steadily closing the gap between the NT kernel API surface that Windows applications expect and what Wine provides on Linux. For anyone relying on Wine in a production or semi-production capacity, the NTOSKRNL commit history is a more reliable indicator of where compatibility is heading than any single changelog entry.

Source: phoronix.com

Read more
Post a Comment

Wine 11.16 Adds VA‑API Decoding and Improves ARM64 Compatibility

on

By the end of this article readers will understand the new capabilities introduced in Wine 11.16, how VA‑API hardware decoding integrates with existing Linux graphics stacks, and what adjustments may be required for administrators and developers working on x86_64 and ARM64 platforms.

What Wine 11.16 Introduces

The latest upstream release of Wine, version 11.16, expands its multimedia support by incorporating VA‑API (Video Acceleration API) for hardware‑accelerated video decoding. In addition, the release notes highlight enhanced compatibility for the ARM64 architecture, addressing long‑standing gaps in running Windows applications on 64‑bit ARM Linux systems.

VA‑API Hardware Decoding

VA‑API is the standard interface used by Intel, AMD and some ARM GPUs on Linux to expose video decode, encode and post‑processing capabilities to user‑space applications. By adding a VA‑API backend, Wine can now offload supported video codecs—such as H.264 and HEVC—to the GPU instead of relying on software decoding. This reduces CPU load, improves power efficiency, and can lead to smoother playback of Windows media applications under Wine.

Improved ARM64 Support

ARM64 support in Wine has historically lagged behind x86_64 due to differences in calling conventions, syscall translation, and the need for extensive testing across diverse hardware. Wine 11.16 includes a series of patches that refine the translation layer for ARM64, resulting in fewer crashes and better handling of Windows binaries compiled for 64‑bit ARM. The changes are incremental rather than a complete rewrite, but they represent a noticeable step forward for developers targeting ARM‑based Linux devices such as Raspberry Pi 4, Pine64 boards, and upcoming ARM servers.

Technical Implications for System Administrators

The addition of VA‑API changes the performance profile of Wine deployments that run video‑intensive Windows applications—media players, streaming clients, or games with cutscenes. Administrators should verify that the underlying GPU driver exposes VA‑API correctly. On distributions that ship the libva‑intel‑driver or libva‑amdgpu‑driver packages, the presence of the /dev/dri/renderD* nodes indicates that hardware decoding is available. If these nodes are missing, the system will fall back to software decoding, negating the benefit of the new Wine backend.

For ARM64 hosts, the updated translation layer reduces the need for work‑arounds that previously required running Wine in x86_64 emulation mode via QEMU. Administrators can now deploy native ARM64 Wine instances, simplifying container images and reducing the overhead associated with binary translation. This also aligns with the broader trend of moving workloads to ARM for energy efficiency.

Impact on Developers and Power Users

Developers testing Windows applications on Linux can now rely on hardware‑accelerated decoding when using Wine 11.16, which brings the test environment closer to typical Windows performance characteristics. This is particularly relevant for applications that embed video playback using DirectShow or Media Foundation, as those APIs will now route through the VA‑API backend where possible.

Power users who maintain personal Wine installations will notice lower CPU usage during video playback, especially on laptops with integrated graphics. On ARM64 devices, the improved compatibility means fewer crashes and a smoother user experience when running native ARM Windows binaries, expanding the practical use‑case for Wine beyond x86 emulation.

Operational Considerations

Enabling VA‑API in Wine does not require additional configuration beyond ensuring that the host system's graphics stack provides the necessary VA‑API libraries and device nodes. However, administrators should monitor the system logs for any fallback messages indicating that a particular codec is not supported by the GPU, as this may trigger a switch back to software decoding.

On ARM64 platforms, the updated Wine binary should be built against the latest libwine and libglib packages that include the ARM64 patches. Deployments that previously relied on cross‑architecture builds may need to adjust CI pipelines to pull the native ARM64 Wine package instead of the x86_64 version.

Source: phoronix.com

Read more
Post a Comment
Subscribe to: Posts (Atom)

Popular Posts

Install Ollama and Open WebUI on Ubuntu 24.04 with NVIDIA GPU Acceleration (Step-by-Step)

Overview Running a local large language model (LLM) is easier than ever thanks to Ollama and Open WebUI. Ollama handles model downloads and inference, while Open WebUI gives you a clean, chat-style interface in your browser. In this tutorial, you'll install both on Ubuntu 24.04 (works on 22.04 too), enable NVIDIA GPU acceleration, and deploy them with Docker Compose. The result is a fast, private AI stack you control. What You'll Need - Ubuntu 24.04 or 22.04 (fresh or existing server/desktop). - An NVIDIA GPU with recent drivers (Turing/RTX or newer recommended). - Root or sudo access. - Open ports 3000 (Open WebUI) and 11434 (Ollama) on your firewall if you access remotely. Step 1: Install NVIDIA Drivers and Verify CUDA First, update your system and install the recommended NVIDIA driver. On Ubuntu Desktop you can use Additional Drivers, but the CLI route is reliable: sudo apt update && sudo apt -y upgrade sudo ubuntu-drivers autoinstall sudo reboot After reboo...

Install a Local AI Chatbot on Ubuntu 24.04 with Ollama and Open WebUI (Step-by-Step)

Running a fast, private AI chatbot on your own computer or server is easier than ever. In this guide, you will install Ollama (a lightweight local LLM runtime) and Open WebUI (a modern web interface) on Ubuntu 24.04 . You will be able to chat with models like Llama 3 or Mistral without sending data to the cloud, and with optional GPU acceleration if you have an NVIDIA card. What you will need : an Ubuntu 22.04/24.04 machine (VM, bare metal, or WSL), at least 8 GB RAM (16 GB recommended for larger models), 15–30 GB free disk space for models, Internet access, and optional NVIDIA GPU drivers for acceleration. Why Ollama + Open WebUI? Ollama manages local large language models (LLMs) with simple commands and sensible defaults. Open WebUI gives you a clean, chat-style interface with features like prompt history, file uploads (for some models), and model switching. Together, they are a simple, reliable stack for a self-hosted AI experience. 1) Update Ubuntu and install basics First, ...

Install Ollama + Open WebUI on Ubuntu 24.04 with NVIDIA GPU Acceleration (Step-by-Step)

Overview This guide shows you how to install Ollama and Open WebUI on Ubuntu 24.04 with NVIDIA GPU acceleration. You will get a fast local AI stack that can run modern large language models (LLMs) like Llama 3 on your own hardware, secured and accessible in a web browser. We will cover GPU driver setup, Docker with the NVIDIA Container Toolkit, Ollama installation, Open WebUI deployment, basic security, and troubleshooting. Prerequisites - A machine running Ubuntu 24.04 (fresh or updated). - An NVIDIA GPU with at least 8 GB VRAM recommended for 8B models (more is better). - Internet access and sudo privileges. Step 1: Install the NVIDIA GPU Driver Install the recommended proprietary driver so CUDA becomes available to both Ollama and containers. sudo apt update && sudo apt install -y ubuntu-drivers-common sudo ubuntu-drivers autoinstall sudo reboot After reboot, verify the GPU is recognized: nvidia-smi You should see a driver version and your GPU model. If not, check...

Trending Now

Homogeneous Nucleation on Mars: A Textbook Process Finally Observed in Nature

on
By the end of this piece, you will understand what the Arsia Mons Elongated Cloud is, why it resisted explanation for several years after its first observation, and what the newly published model reveals about a physical process that has never been directly confirmed on any planet's atmosphere. The cloud that broke the model Every morning during Martian spring and summer, a thin, extremely long cloud forms near the Arsia Mons volcano and gradually elongates until it stretches to more than 1,000 miles before dissipating. The cycle then repeats for several months. The formation was first recorded by a probe in 2018, and from that point onward it became a persistent puzzle for atmospheric scientists working with Mars data. The cloud's geometry, its timing, and its seasonal recurrence all pointed to a real and reproducible physical process, yet no existing model could reproduce it. For a technical audience familiar with simulation work, the situation is analogous to a product...