users January 2025

users@lists.genode.org

14 participants
6 discussions

Kernel: Cpu 2 error: re-entered lock. Kernel exception
by Pirmin Duss 12 Feb '25

12 Feb '25

Hello Genodians Since we rolled out the update to 24.11 we see the above message about once or twicw a day in the logs of our testing pipeline. It happens on different hardware (Up-Xtreme and imx8mp_iot_gate in the last two days) and in different run scripts. The run scripts range from a fairly simple TPM run script to complicated run scripts that test the resilience of the operating system to stopping/starting of whole subsystems and reboots. Currently we don't have a case where this … [View More]

2 3

system shell NOT in foreground
by Larry Sevilla 28 Jan '25

28 Jan '25

Hi Genode people, I tried to follow the sculpt documentation up to "Tools -> system shell" The "system shell" displayed on screen,BUT I canNOT type any commands. when I click on the said shell/window, it canNOT be in the "foreground" or be an "active window". Sources: https://genode.org/documentation/articles/sculpt-24-10 File QEMU/KVM: https://genode.org/files/sculpt/sculpt-24-10.img File VirutalBox: https://genode.org/files/sculpt/sculpt-24-10.ova Host A Desktop: i7-8700 32Gb OS: … [View More]

2 1

Trying to modify Bit_array throws 'Invalid_index_access'
by Rumen Mitov 24 Jan '25

24 Jan '25

Hello, I am facing a problem when using the Bit_array class. I have a class called L1Dir which contains the property freemask which is a Bit_array with L1_SIZE bits. I want to initialize every bit to value 1 in freemask. However, when I try to call freemask.set(0, L1Dir) outside of the L1Dir default constructor the following error is thrown: 'Genode::Bit_array_base::Invalid_index_access'. I have tried changing the call to freemask.set(1,2) but I still get the same exception. I have also … [View More]

2 2

Roadmap 2025
by Norman Feske 22 Jan '25

22 Jan '25

Hello everyone, the turn of years is approaching, which prompts me to pick up our fine tradition of jointly brainstorming the topics of the year to come. Below, I'm not speaking for the project but share my personal perspective. Let me start with a brief reflection on 2024, followed by my ambitions for 2025. Review of 2024 Following our past year's discussion, we settled on "Sculpt OS usability" as the primary focus for 2024. The items on the roadmap envisioned a broad variety of … [View More]topics, ranging from challenging low-level mechanisms to end-user conveniences. From my perspective, the two biggest breakthroughs had been suspend/resume on x86 (added in May) and multi-monitor support (added in October). Both topics were not merely approached as singular features but as architectural enhancements. Suspend/resume challenged our perspective on driver life-cycles, externalizing state, device re-acquisition, up to the dynamic driver management by Sculpt OS. Our desire for multi-monitor support culminated in a largely redesigned GUI stack, as a system-holistic endeavor. Both lines of work made the architecture of Sculpt OS much stronger. Regarding my original plans for user conveniences (file browser etc.), I must declare defeat. Instead of working on these user-visible features, I turned a significant part of my attention to consolidation work: Gradually removing the use of C++ exceptions, cultivating C++20, improving code safety, and accelerating our workflows be refining our build system and tools. Outside my own working topics, I vastly enjoyed watching our team embracing DDE-Linux to full extent. Reflecting upon our small team's ability to track the current Linux kernel for our large driver base with such an agility makes me more than happy. A similar source of happiness is the way of how the Goa SDK and the new Applications book evolved. It reveals plainly and clearly how all the parts of the machinery fit super nicely together. Any regrets? Two things come into mind. First, my over-promising to deliver user conveniences. Topics like the on-target docs view or a file manager are user-visible and fun to build. But I was not able to justify prioritizing those over the work on framework internals as my core expertise. I somewhat regret having promised too much. Second, the PinePhone hasn't become a regular part of my life. That's not the fault of the PinePhone. But I came to terms that I may simply not be a phone person, never having owned a smart phone after all. Once I called the exciting ride of bringing Genode to the PinePhone a success, my personal motivation to push things further forward plummeted somewhat. My plans for 2025 I want to focus my Genode work on rigidity, clarity, and performance. 1. Following my consolidation work of 2024, I long for getting the C++ runtime removed from the base framework. Another tempting idea for simplification is the merging of core's CPU service into the PD service. This work will make Genode more simple and thereby more trustworthy. 2. I'm very curious to explore the idea of replacing XML, outlined at https://genodians.org/nfeske/2024-12-20-moving-on-from-xml If this goes as intended, Genode and Sculpt OS will gain in terms of interactive ergonomics, clarity, and joy to develop for. 3. Given how easy the porting of software has become, thanks to Goa, I'd strive for moving more of my work outside a Linux VM. For this, libraries like the libc and VFS require further optimization. This goes hand in hand with the need for better tools for analysing performance bottlenecks of complex dynamic workloads. As an iconic goal, it would be fantastic to have a simple version of Goa running directly on Sculpt OS by the end of 2025. In addition, I'd like to catch up on my plans of 2024 regarding user-visible Sculpt OS features, introducing a documentation view, a simple file manager, and a convenient way to save settings. I will also definitely wrap up the multi-monitor window management that I have built during the past two months. My wishes for 2025 Outside the realm of my own working topics, I'd love to eventually switch to the base-hw kernel on my Framework laptop. I'd also highly appreciate an update of the Chromium engine for the Falkon web browser. Don't we all want to participate in https://genode.discourse.group using a browser directly on Sculpt OS? ;-) What is your perspective on Genode in 2024 and for 2025? - Has Genode's development during 2024 been in your interest? - Or do you find important aspects neglected? - How was your practical experience with Genode in 2024? - Which directions would you regard as most exciting or pressing? - What are your personal interests and plans for 2025? I'm looking forward to learn about your experiences, plans, and ideas. Like every year, I'll do my best to distill a rough plan for 2025 out from our joint discussion. The road map will be finalized around mid of January. Cheers Norman Dr.-Ing. Norman Feske Genode Labs https://www.genode-labs.com · https://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth [View Less]

14 29

Announcement for the restructuring of the world repository
by Josef Söntgen 17 Jan '25

17 Jan '25

Hi, We plan to convert world from a Genode repository into a repository housing goa [1] projects and while doing so tidy things up. At the moment there is no ample schedule, so treat this announcement as a heads-up, but we would like to finish the restructuring process by the beginning of 2026. The following text briefly goes into the reasoning behind this decision and outlines the process. [1] https://github.com/genodelabs/goa The world repository was created as a gathering place for … [View More]

1 0

Minimal Goa Nitpicker / Dialog API Projects
by John J. Karcher 06 Jan '25

06 Jan '25

Hello, I have been trying to create a Goa project from the Dialog Test component, but I'm bumping into the limits of my Genode abilities. I'm trying to use "dialog.run" as a template for what to include, using the "import_from_depot" section as a rough guide to "used_apis" and the config for the "runtime" file. 1. Is this the right basic idea? 2. Is there already a minimal example of a Goa project for a Nitpicker and/or Dialog API component, so I don't have to reinvent the wheel? 3. I … [View More]

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users January 2025