Video summary

Untitled Linux Show 261

Main summary

Key takeaways

Technology

Tech/product news & analysis highlights

1) Valve “Steam Machine” (living-room Linux gaming PC) — pricing + hardware concept

  • Confirmed Steam Machine pricing & preorder details via big YouTubers getting units early.
  • Not a cheap console (US pricing):
    • 512GB base model: $1,049
    • 2TB model: $1,349
    • With Steam Controller bundle: $1,128 (512GB) or $1,428 (2TB)
  • Positioning: Valve frames it as a console-sized compact PC, not a typical console.
  • Key specs mentioned:
    • Semi-custom AMD Zen4 CPU
    • RDNA3 graphics
    • 16GB DDR5
    • 8GB video memory
    • NVMe storage
    • microSD expansion
    • Wi‑Fi 6 + Bluetooth + Ethernet
    • SteamOS
  • Why the pricing may “make sense”:
    • You’re paying for: small form factor, integrated hardware, Steam Deck–style experience, quiet “couch gaming,” and booting into SteamOS instead of Windows.
    • Linux fans also see it as supporting improvements for Linux gaming.
  • Upgradeability note: It’s more computer-like than fixed consoles; discussion suggests buying the cheaper model now and upgrading later (e.g., more RAM / larger SSD) as a rational move in the “AI pricing bubble” era.
  • Community interest: Hosts want to obtain/try one to support Valve’s Linux push.

2) “Steam Frame” (VR headset) — Snapdragon + standalone/wireless PC link concept

  • Discussion shifts to Steam Frame:
    • Expected to use a Snapdragon SoC.
    • Standalone mode for less demanding VR apps (e.g., VRChat-like workloads).
    • Wireless link mode to a desktop for full graphics / higher performance.
  • Emphasis: VR running Linux on Snapdragon with integration into the Steam ecosystem.

3) Academy Software Foundation (ASWF) working group: “Wayland for artists”

  • ASWF forms a new working group focused on Wayland adoption for professional creatives.
  • ASWF is described as a nonprofit (Oscars-adjacent) that standardizes open-source tech used in film/animation/VFX.
  • Examples of cited ASWF projects:
    • OpenVDB (volumetrics like smoke/clouds)
    • Open Shading Language (OSL)
    • OpenColorIO (color management)
    • OpenEXR (HDR image format)
  • Why Wayland matters: With X11 moving away, studios need to evaluate impact on:
    • GPU acceleration
    • graphics tablets
    • window management
    • input focus/key bindings
    • remote access solutions
    • color management and HDR displays
    • compatibility with professional tools (open-source, commercial, in-house)
  • Theme/quote: This transition could affect high-end content creation workflows, so the group coordinates stakeholders to map the best path forward.
  • Linux/VFX context: hosts note they didn’t realize how widely Linux and these open standards are used in studio pipelines.

4) Linux Foundation / “ACR/ACRites” AI-era security working group — incident response + coordinated disclosure

  • A new working group is described to establish:
    • a shared security incident response team
    • a standardized coordinated vulnerability disclosure (CVD) process
    • confidentiality-first principles
    • use of industry-standard tooling
  • Key operational idea: If a critical package has no active maintainer, the initiative acts as maintainer-of-last-resort (stepping in to ensure timely fixes).
  • Goal: Ensure fixes return to upstream and releases reach users quickly.
  • Hosts connect this to:
    • infrastructure fragility (the “single maintainer holds up many dependencies” problem)
    • the rise in vulnerabilities driven by AI-driven scrutiny/inputs
    • open-source sustainability and the need for process/coordination
  • Related ecosystem pressure mentioned:
    • example of curl maintainers pausing to triage security reports
    • discussion of the Linux community adapting to bug reports rather than treating them as purely adversarial

5) Pine64 “Pine Voice” smart speaker — Home Assistant–centric + privacy controls

  • Pine64 releases Pine Voice for $49.
  • Design goal: not another Alexa/Google-style cloud microphone clone.
  • Described as a “voice satellite” for Home Assistant:
    • listens for wake word locally
    • sends voice to Home Assistant using the Wyoming protocol (Home Assistant’s voice-satellite approach)
  • Privacy feature: a physical hardware microphone mute switch.
  • Wake word detection: runs locally using micro wakeword, with an “hey Jarvis” model referenced via ESPHome.
  • Hardware details (MCU-level):
    • Buffalo Lab BL606P RISC-V chip (includes a C906 plus companion cores)
    • memory/storage: 32MB PSRAM, 16MB flash
    • dual microphone array
    • Wi‑Fi/Bluetooth
    • speaker + volume buttons
  • Caveats: early-stage; may require tinkering and Home Assistant integration setup.
  • Source hosting mention: code on Codeberg (briefly down at the time).
  • Important clarification: it’s not running Linux on the chip—this is MCU/RTOS/bare-metal style territory (discussion mentions Zephyr/bare metal concepts).

Desktop environments & UI customization

6) KDE Plasma System Monitor — deep dashboard customization guide

  • Focus: customizing KDE Plasma system monitor using its internal layout model:
    • rows → columns → sections → widgets
  • In edit mode, hovering reveals which layer you’re interacting with.
  • Customization discussed:
    • add/rearrange widgets inside sections
    • add columns
    • use multiple pages (default + user-created)
  • Example dashboard ideas:
    • turn widgets into a horizontal CPU-per-core load bar
    • select sensors for CPU usage/temperature, disk activity, GPU load, memory, network throughput
    • show both current and historical data
    • use visual widgets like pie charts (e.g., RAM) and color grid widgets for extra metrics
  • Persistence and portability:
    • save custom pages and set a default page
    • delete/hide pages
    • export/import pages to replicate dashboards across machines
    • browse/share community-created pages inside the app
  • Hosts frame this as a tutorial-style walkthrough with diagrams/pictures in the referenced article.

7) Cosmic desktop “Epoch 1.1” — new system monitor + bug fixes + release cadence

  • Cosmic Epoch 1.1 (six-month update from Cosmic 1.0) includes:
    • many bug fixes and tweaks
    • new Cosmic system monitor UI (disk/process/CPU/RAM monitoring; “applications vs processes”)
    • a reported RAM leak fix
  • Release strategy signal: naming it Epoch 1.1.0 suggests they’ll ship smaller updates more frequently rather than long gaps.
  • Discussion comparison: aesthetics/maturity relative to KDE/GNOME.

Performance/Kernel/GPU display notes

8) Kernel & compiler performance tuning (cache-aware scheduling + GCC branch prediction)

  • Linux cache-aware scheduling improvement:
    • goes beyond only last-level cache
    • uses more detailed hardware topology so tasks align with the appropriate cache characteristics
    • reported outcomes: up to 360% improvement in certain cases (e.g., MySQL at 64 threads), with smaller but meaningful gains under load
    • expected in kernel 7.2
  • GCC optimization for modern x86_64:
    • a “one-line” change to branch prediction miss weight (+3)
    • reported around 12% improvement in some modern Intel/AMD scenarios
    • more conservative branch handling; may use branchless transformations and mitigations
    • applies to generic x86_64 builds, not CPU-specific compilation
    • expected in GCC 17 stable (later timeline)

9) Raspberry Pi kernel 6.18 LTS performance regressions (early feedback)

  • Raspberry Pi OS moved to Linux 6.18 LTS; users report:
    • performance regressions
    • debate around causes: could involve additional security mitigations, but not fully explained
    • leading theory: scheduler changes affecting Pi behavior (“scheduler is changed in the ARM world”)
  • Hardware symptom example:
    • impacts workloads involving I2C/SPI/GPIO timing
    • example: reliability for a 40MHz SPI bus when scheduling/timing differs
  • Hosts plan to watch for fixes vs issues that become persistent “quirks.”

10) HDMI 2.1 for AMDGPU in kernel 7.2 — FRL but initially disabled

  • News: kernel 7.2 DRM merge includes “long awaited” HDMI 2.1 fixed-rate link (FRL) support for amdgpu.
  • Initially disabled by default:
    • FRL is wired up, but full HDMI 2.1 implementation isn’t ready
    • VRR is a blocker: enabling FRL without VRR bits could cause VRR regressions for FRL displays
  • Expected timeline:
    • parts should land around kernel 7.2, affecting distributions later (e.g., Fedora 45 / Ubuntu 26.10 referenced)
  • Personal anecdote:
    • host uses a DisplayPort-to-HDMI dongle to get HDMI 2.1 features now; expects to remove it once upstream lands.

Browser & Linux desktop software

11) Brave “Brave Origin” — stripped-down Brave for Linux (free for Linux users)

  • Brave launches Brave Origin, described as a cleaner, stripped-down Brave.
  • Linux users get it free; Windows/macOS pay $59.99.
  • Features removed:
    • AI assistant
    • Brave Rewards
    • crypto wallet
    • VPN features
  • Kept: Brave’s core strength—built-in ad/tracking blocking.
  • Rationale: some distros already ship Brave builds with features disabled; Origin offers a consistent cross-Linux experience.

12) TUI email client “Harold” — Go install + terminal inbox UI

  • Harold is a TUI email inbox/client featuring:
    • folder list on the left and message list on the right
    • a demo mode flag mentioned (e.g., --demo)
    • keyboard shortcuts (compose via Ctrl+N, reply via Ctrl+R, delete via Del)
    • mouse support, including inside a container/LXC environment
    • extra sections: contacts, calendar, memories
  • Installation note:
    • Brew instructions on the page didn’t work for Linux, but the Go install link did.

Command-line tips (tutorial-style)

13) ss (socket statistics) as modern replacement for netstat

  • Tip: use ss instead of netstat.
  • Why it’s faster:
    • netstat parses large text from /proc (slow under heavy load)
    • ss uses Netlink to query the kernel with a binary protocol, fetching only requested data
  • Examples/flags covered:
    • ss (all socket connections)
    • ss -t TCP only, ss -u UDP only
    • ss -l listening sockets
    • ss -tl listening TCP
    • -n to avoid hostname resolution (raw IPs/ports)
    • -p to show process info owning the socket
    • ss -s summary counts by type/state
    • filtering by port; examples include SSH port and -L for UDP listening ports
    • mention of combining features in a TLNP-like style for listening TCP + process info

14) relayd — bridging Ethernet over Wi‑Fi using MAC-address translation “magic”

  • Tip: relayd (“relay D”) is discussed as a solution when bridging networks over Wi‑Fi doesn’t work normally.
  • Core issue:
    • Wi‑Fi headers carry only three MAC addresses (source, AP, destination)
    • it doesn’t map cleanly onto Ethernet-style bridging needing a fourth identity for multi-device downstream cases
  • Why relayd helps:
    • effectively performs MAC address translation (compared by hosts to NAT-style behavior)
    • enables more reliable bridging of two Ethernet networks over Wi‑Fi
  • Extra capabilities mentioned:
    • proxying
    • load balancing / round-robin style use
    • transparent proxying
  • Hosts describe it as a Swiss Army knife for networking setups.

Main speakers/sources

  • Jonathan Bennett (host)
  • Rob (co-host; leads several technical stories)
  • Jeff (co-host; contributes across VR/desktop/security/performance segments)

References/sources mentioned within the episode include:

  • Valve (Steam Machine announcements/pricing)
  • Academy Software Foundation (ASWF) (Wayland for artists working group)
  • Linux Foundation / ACR initiative participants (AI-era vulnerability disclosure/incident response group)
  • Pine64 (Pine Voice product details)
  • Brave (Brave Origin announcement)
  • Kernel 7.2 / AMDGPU / DRM (HDMI 2.1 FRL merge notes)
  • Go/harold, SS/Netlink, and relayD/relayd (tools discussed by hosts)

Original video