users

users@lists.genode.org

1 participants
2310 discussions

CCC Camp 2023
by Stefan Kalkowski 14 Aug '23

14 Aug '23

Hello genodians, tomorrow the CCC Camp 2023 starts officially at Ziegeleipark Mildenberg [1]. If you attend the camp and if you are interested in a chat about Genode topics, or like to have a look at Sculpt OS running on top of PC, MNT Reform2, or Pinephone, please give me a sign. I'll be there from Tuesday afternoon to Saturday evening. Looking forward to see some of you there! Best regards Stefan [1] https://events.ccc.de/category/camp-2023/ -- Stefan Kalkowski Genode labs https://github.com/skalk | https://genode.org

1 0

23.05 image is good, still need help
by Johnny Nunez 11 Aug '23

11 Aug '23

Hi Genodians, I was running the latest image 23.05 but i can't seem to install anything? I get a lot of Error: HTTP response code said error (code=404), fail.... the only Depot that seem to work was ssumpf , and this one has Vbox , all I need, but then Vbox calls for other packages too that genodelabs and cnuke are not able to connect to. I guess i will keep trying.

2 1

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

Couple minor notes after upgrading to 23.02
by ttcoder＠netcourrier.com 30 Jun '23

30 Jun '23

Dear Genodians, Here are two (very minor) notes after my upgrading to 23.02 (plus cherry-picking the patch from #4785), regarding two "bugs" I had found, which ended up being mistakes on my side, not on Genode's side. These two don't justify opening tickets, but they might deserve a quick mention here on the mailing-list: * vfs_pipe: components that use the "pipe" plug-in should make sure to enable RTC (<libc rtc="/dev/rtc"...>) as of 23.02 -- previously it would work without specifying an RTC path. This probably has zero impact since everyone properly configures their libc config (unlike me in the one scenario that brought this up..!) * FS "stalls" when a vfs-handle fails read()ing in a specific way: Found out that when writing a vfs plug-in, and vfs handles, I ought to make sure not to return READ_ERR in the read() hook, error cases should be detected earlier, at the open() stage (-> return a nil vfs-handle and error code, obviously). Once a valid vfs-handle is returned in open() it's not ok to say "sorry, my bad, the file cannot actually be read and should not have been opened in the first place" every time read() is called... Otherwise this entails a bunch of consequences, the most visible of which is big red "packet operation failed" error messages in the LOG ! Again, others seem more careful, but I stumbled into making that mistake and thought I should post a cautionary tale about it ;-) Cédric P.S. If one is in need of a quick temporary hack before vfs-handle usage is cleaned up, it seems there is an alternative way for the stalls to be kept at bay or mitigated by modifying Genode's fs_file_system.h, adding a forced call to wakeup_vfs_user() (I'm still investigating... hopefully won't have to dig much though, fixing my code to fail earlier at the open() stage should do the trick).

2 2

Announcement: Sculpt OS 23.04 released
by Christian Helmuth 30 Jun '23

30 Jun '23

Hello Genodians, I'm proud to announce the release of Genode-based Sculpt OS 23.04. https://genode.org/news/sculpt-os-release-23.04 Today's release marks the first-time PinePhone support in addition to the PC version. We added two key features to Genode during the past months, which are the phone-oriented Sculpt user-interface variant and the system-update functionality. With these tools at hand, Sculpt versions can be switched by three easy steps directly in the integrated user interface: downloading system images to the software depot, install the desired version on the boot medium, and reboot the device. Further, the release supports so-called presets in the system menu UI, which are entire runtime scenarios. The user can load and switch between presets by just one click. Presets currently available in Sculpt are a simple GUI demo (nano3d), a simple desktop including background picture and window manager, and a ready to use Falkon web browser. Still, components can be integrated into the system (or the currently running preset) by the + menu of the component graph. As usual, the starting point is a ready-to-use disk image at the Sculpt download page. https://genode.org/download/sculpt Documentation including use and build instructions for Sculpt is available at the following pages. https://genode.org/documentation/articles/sculpt-23-04 https://genode.org/documentation/sculpt-23-04.pdf Happy sculpting -- 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

5 6

Setting up Child Policy explicitly for a child PD which will announce a service.
by Sid Agrawal 29 Jun '23

29 Jun '23

Hi, I am trying to setup a scenario where the parent starts a child PD in the C code, i.e., there is no <start> node for the child in the config file. It is similar to the rm_nested test example [1]. But in my scenario, I would like to start a server in the child and have the parent make RPC calls to it, and I need some help setting that up. I think the answer should be in some configuration of the ChildPolicy used to start the child, but I am missing something. My code is here [2,3] and is a hybrid of the hello_tutorial and the rm_nested test case. Like rm_nested, the parent starts a child with the same binary and uses the failure to reach the RM service to indicate that it is in the child. But then, in my scenario, I start a HelloServer in the child, and the parent tries to establish a connection to this service. I am seeing two errors: 1. An error that Genode complains that it wasn't expecting the child to announce a service. I tried fixing that by defining announce_service() in the Test_Child before starting the child, but that didn't fix it. TBH, I am wondering what to add to that function. 2. The parent cannot find the "Hello" service to connect to. I think that fixing (1) would fix two as well. Any help pointing me in the right direction would be very helpful. Thanks as always! Best, Sid sid-agrawal.ca [1] https://github.com/genodelabs/genode/blob/master/repos/base/src/test/rm_nes… [2] https://github.com/sid-agrawal/genode/blob/76af718937e9723ae6cf2212a4ae549e… [3] https://github.com/sid-agrawal/genode/blob/76af718937e9723ae6cf2212a4ae549e…

2 2

Customizing the Goa run-stage
by Duss Pirmin 27 Jun '23

27 Jun '23

Hello Genodians The direction Goa is evolving is really cool! The new and upcoming features address topics that are perfectly aligned with how we currently use, or plan to use Goa. In addition to what is already addressed in issue #44 [1], in order to run or test some more complex projects we use: - a source for random (this can be achieved using jitter_sponge) - accessing externally provided ROM modules - multiple Nic/uplink interfaces and a nic_router For the random source I have a working commit, that I will have to update to cleanly apply on top of staging. This will start jitter_sponge if <requires> <terminal label="random"/> is found. To make this available in general, the jitter_sponge binary would have to be published by genodelabs. Do you think this approach is reasonable? For accessing externally provided ROM modules I already have a patch that enables this feature. It uses a fs_rom and a lx_fs to access ROM modules listed in <requires> <rom label=""/>. If you think this could be a commonly useful feature, I can contribute it. Providing multiple Nic/Uplink interfaces and a nic_router will require some more engineering to do right. Our workaround instantiates a fixed configuration which matches what we need. This is obviously not usable in general. I see the following points that need to be considered: - number and names of interfaces? Probably each listed in <requires> by label. - when to start nic_router? Probably not as easy as start it when multiple interfaces are configured. - how should the nic_router config be provided? Here I don not see yet a satisfying and practical solution. Best regards, Pirmin [1] https://github.com/genodelabs/goa/issues/44

4 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users