users July 2023

users@lists.genode.org

7 participants
5 discussions

Announcement: Genode OS Framework version 23.05 released
by Christian Helmuth 22 Aug '23

22 Aug '23

Today we released Genode 23.05 as a colorful bouquet of new features, improvements, and fixes. The most prominent change for developers is the update of our tool chain to GCC 12, binutils 2.40, and GDB 13.1. The new GCC version gave us the opportunity to switch from C++17 to C++20 as default setting and benefit from modern C++ language features. Another noteworthy addition falling into the same category is the release of the evolving Goa tool for Sculpt 23.04, which now enables the use of existing SDKs like Lomiri or Rust's cargo for Genode. Our Linux device-driver environment (DDE), which enables the use of Linux drivers as Genode components was upgraded to Linux 6.1.20. For example, the DDE now powers our cross-platform Wifi stack that works for the PC and ARM platforms as the PinePhone alike. Further, we integrated the initial use of our custom base-hw microkernel as x86 hypervisor, a profoundly reworked block-encryption stack, and updates of supported third-party software like the seL4 kernel and VirtualBox. Last but not least, we published our annual documentation update in form of "Genode Foundations" and "Genode Platforms" books. The current release contains the following changes and new features: - Goa tool updated to Sculpt OS 23.04 - Ubuntu-Touch-UI toolkit - Initial support for Rust cargo - New tool chain based on GCC 12.3 - C++20 enabled by default - Annual documentation update - Uniform Wifi stack across PC and ARM platforms - Revision of Genode's custom block-encryption infrastructure - Linux device-driver environment updated to Linux 6.1.20 - Improved USB, Intel display, and NVMe drivers - VirtualBox 6.1.44 - Initial x86 virtualization via the base-hw microkernel - Updated seL4 microkernel to version 12.1 - NetBSD rump kernel on RISC-V Read the complete release documentation for the version 23.05 here https://genode.org/documentation/release-notes/23.05 Best regards -- Christian Helmuth Genode Labs https://www.genode-labs.com/ · https://genode.org/ https://twitter.com/GenodeLabs · https://genodians.org/ Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

3 3

Screensaver for the PinePhone
by Norman Feske 02 Aug '23

02 Aug '23

To all Sculpt-OS-on-the-PinePhone testers, I have just published a new Sculpt OS image for the PinePhone that includes a screensaver mode to increase battery time. You can download the image with version 2023-06-30 at [1], or use Sculpt's built-in system update feature, selecting me (nfeske) as image provider, and download and install the latest entry of my index. [1] https://depot.genode.org/nfeske/image/ The screensaver kicks in after ten seconds of user inactivity in the administrative user interface. It also can be manually activated by pressing the power button. While the screen is blanked, a press of the power button enables the display again. Under the hood, Sculpt completely removes the drivers for the display and the touchscreen while the screen is blanked, which considerably reduces the power draw. The system also switches the CPU to economic mode while the screen is blanked. Here are some illustrative data points: Max brightness in performance mode: 2.8 W Max brightness in economic mode: 2.6 W Low brightness in economic mode: 1.7 W Screensaver: 1.0 W As a caveat, I noticed that the screen-flickering issue, we sporadically observed in the past, occurs quite often when returning from the screensaver (aka after restarting the drivers). The flickering disappears after a while. However, maybe this way of reproducing the issue gives us the chance to eventually solve it. Have fun with trying out the new image! 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

2 4

Feedback on 23.05
by ttcoder＠netcourrier.com 26 Jul '23

26 Jul '23

Fellow Genodians, what follows is a minor observation and two (more serious) questions. 1) Suspend/resume The introduction of that feature in 23.02 triggered some "geek lust" in this aging geek, and now with 23.05 I got around to attempting system integration of suspend/resume in my stack. In Qemu it seems to all work fine (after I realized the vesa and input driver need to be restarted, reading acpi_suspend.run more carefully). However on bare metal (admittely years old), S3-suspend works well, but at resume time, the screen remains black. I thought maybe if the video driver causes trouble, I can try the "back door" (vnc), to validate the concept that everything works except vesa, and confirm I need to revisit my integration of vesa_drv. So I tried to connect via VNC, but no go, coming back from suspend. Could be that the nic_driver needs to be restarted as well (I didn't handle that, I only restart vesa and ps2_drv currently). I could persist, but this is not a feature I really need (just wanted it for "bragging rights" :^) so I'll probably wait for newer Genode releases, in case it's a matter of waiting for Genode upgrades. Very cool to have that feature almost at reach though. 2) Launching apps A newbie question ! (yes even after 5 years I still have those :-) How to launch components (applications). Grepping through the Genode repo, I came up with: - use a sub init with a generous RAM alotment (2 GB), and drive its config ROM through a report_rom: a list of launched apps has to be maintained by a "third actor" (not the sub-init, and not any of the client apps that require launching a process, but rather some sort of stand-by "registrar"), and its job would be to re-generate the sub's config ROM whenever that list grows as a new app is launched. Problem is, what happens when the user *quits* an application ? When that occurs, the app is still part of the sub-init's config, so next time sub reads its config, it's going to re-launch it, right ? This would otherwise seem to fit the bill well, if not for that problem of un-desired app relaunch. Maybe I can solve that problem by sending notifications every time an app is quit (if it's quit cleanly rather than crashing, at least), and the notification recipient (probably the "registrar" ?) would remove the relevant snippet from the sub-init's config. - loader_session: seems close enough too, and simplier to use, but the README says the ram/caps of the created child will be substracted from the caller, instead of from the launcher (i.e. the opposite of a sub-init). But I want to do the reverse. - fork/exec from libc : same as launcher_session, but seemingly with the (additional) awkwardness of old-style UNIX, where fork() creates a full duplicate of the caller, at least until exec() is called (so the caller app would need to have twice as much ram/caps as it needs, even if it just spawns something tiny like /bin/ls !). - sandbox.h : couldn't find a "tutorial" style usage of it via grep -r sandbox repos/, but maybe I should dive right in and experiment until I understand the gist of it, using the more complex use-cases in the repos ? - anything I missed ? 3) capability leak in pthread_create() (regression in 23.05 ?) Seems my stack triggers some sort of corner case that it did'nt before. This is a little more mission-critical, though it's a small leak and I haven't seen it really impact my apps so far. Anyway the observed behavior is, in many cases, pthread_create() behaves as it always had, allocates a new capability for the created thread, which is returned when the thread ends. But in some scenarios, the cap is not returned, so I'm leaking a cap for each created thread, or pthread_create() allocates _two_ caps instead of one ; this seems to depend on how soon the spawned thread is scheduled (i.e. before or after libc returns from create). Could be that the "corner case" is in my stack, not in Genode, of course. What angle to take to debug that ? I should probably create a ticket to discuss that issue. Cédric

3 2

openssl v3.X port for Genode
by Duss Pirmin 20 Jul '23

20 Jul '23

Hello Genodians Just a quick heads-up to avoid duplicate work. We need openssl v3.X support for a project we are working on. Therefore I'm currently creating a port of openssl 3.1.1. As some APIs have changed or were entirely replaced by new ones, I'm naming the port openssl3 so each component can choose which API version to use. Currently, I can build x86_64 and arm_v8a versions of libcrypto3.lib.so and libssl3.lib.so. Support for 32-bit platforms isn't required for us at the moment, so we have yet to enable support for other platforms. We plan to upstream the port to genode or genode-world eventually. Please let me know if someone is interested in the port so we can do the remaining steps. The port itself is relatively similar to openssl 1.1. It mainly is updated file lists. Regards, Pirmin

1 0

Update generated dummies for wireguard
by Duss Pirmin 04 Jul '23

04 Jul '23

Hello Genodians I'm currently adding a RTC-driver (see earlier question by Stefan Thöni https://lists.genode.org/pipermail/users/2023-May/008704.html). To achieve this I need some additional source files from the Kernel tree. This leads to some more unresolved symbols that can probably be covered by tool/dde_linux/create_dummies. To do this, I need a kernel successfully built kernel. My question is now, how can I get the kernel configuration that was used to build the wireguard port? I will have to tweak this to also build the RTC stub for Genode. Regards, Pirmin

3 6

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users July 2023